Business processing method and device, electronic equipment and storage medium

Abstract

The invention discloses a business processing method and device, electronic equipment and a storage medium. The business processing method comprises the following steps: receiving a handling request for a target business; determining a target number corresponding to the target service based on subscription data information on the user data management network element; generating a target instruction set corresponding to the target service based on the target number; and executing the target instruction set to respond to the handling request. By applying the technical scheme provided by the invention, the business processing efficiency and accuracy can be improved.

Description

Technical Field

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

[0002] With the rapid development of mobile communication technology, the 5th generation (5 th As a new generation of communication technology, 5G network provides users with higher data transmission rate and lower latency. In the deployment and operation of 5G network, user service acceptance has become a key link. User service acceptance includes but is not limited to new installation, card replacement, disassembly and other business processes. The efficiency and accuracy of these processes directly affect the user experience and the service level of operators.

[0003] At present, when the acceptance system receives a request for new installation, card replacement, or machine disassembly, it usually processes the request based on the number information it has recorded. However, the number information recorded by the acceptance system itself may be inaccurate, which results in low efficiency and accuracy in processing the request. Summary of the invention

[0004] The purpose of this application is to provide a business processing method, device, electronic device and storage medium to improve business processing efficiency and accuracy.

[0005] In order to solve the above technical problems, this application provides the following technical solutions:

[0006] In a first aspect, a business processing method is provided, comprising:

[0007] Receive processing requests for target businesses;

[0008] Determine the target number corresponding to the target service based on the subscription data information on the user data management network element;

[0009] Based on the target number, generating a target instruction set corresponding to the target service;

[0010] The target instruction set is executed in response to the processing request.

[0011] In a second aspect, a service processing device is provided, including:

[0012] A receiving module, used for receiving a processing request for a target business;

[0013] A determination module, configured to determine a target number corresponding to the target service based on the subscription data information on the user data management network element;

[0014] A generating module, configured to generate a target instruction set corresponding to the target service based on the target number;

[0015] An execution module is used to execute the target instruction set to respond to the processing request.

[0016] In a third aspect, an electronic device is provided, including:

[0017] Memory for storing computer programs;

[0018] A processor is used to implement the steps of the business processing method as described in the first aspect when executing the computer program.

[0019] In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the business processing method described in the first aspect are implemented.

[0020] In a fifth aspect, a computer program product is provided, which includes computer instructions, which are stored in a computer-readable storage medium and are suitable for being read and executed by a processor, so that a computer device having the processor performs the steps of the business processing method described in the first aspect.

[0021] By applying the technical solution provided in the embodiment of the present application, after receiving a processing request for a target service, the target number corresponding to the target service is determined based on the contract data information on the user data management network element, and a target instruction set corresponding to the target service is generated based on the target number, and the target instruction set is executed to respond to the processing request. As a functional network element for unified data management, the user data management network element can perform centralized data management, and the contract data information on it is more accurate, so the target number corresponding to the target service determined based on the contract data information on the user data management network element is also more accurate, and then the target instruction set generated based on the target number is more effective, which helps to improve the efficiency and accuracy of business processing.

[0022] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0024] Figure 1 This is an implementation flow chart of a business processing method in an embodiment of the present application;

[0025] Figure 2 This is a schematic diagram of the new installation service processing process in the embodiment of the present application;

[0026] Figure 3 This is a schematic diagram of the card replacement service processing process in the embodiment of the present application;

[0027] Figure 4 This is a schematic diagram of the disassembly service processing process in the embodiment of the present application;

[0028] Figure 5 This is a structural diagram of a service processing device in an embodiment of the present application;

[0029] Figure 6 It is a schematic diagram of the structure of an electronic device in an embodiment of the present application. DETAILED DESCRIPTION

[0030] The technical solutions in the embodiments of the present application will be described in detail below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the present application belong to the scope of protection of the present application.

[0031] The terms "first", "second", etc. of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of one type, and the number of objects is not limited, for example, the first object can be one or more. In addition, "or" in the present application represents at least one of the connected objects. For example, the protection scope of "A or B" covers at least three schemes, that is, scheme one: including A and excluding B; scheme two: including B and excluding A; scheme three: including both A and B. In addition, the terms "A and / or B", "at least one of A and B", and "at least one of A or B" also cover at least the above three schemes respectively. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0032] The core of this application is to provide a service processing method, which can be applied to user service acceptance related application scenarios in mobile communication networks, such as new installation, card replacement, disassembly and other service acceptance scenarios. The method can be executed by the acceptance system.

[0033] In the related technology, for the account opening of Voice over Long-Term Evolution (VoLTE) users in the 4th Generation (4G) network, it is possible to comprehensively decide whether the current user meets the account opening conditions by obtaining the VoLTE account opening tag, business operation support data status, and terminal adaptation status on the Home Subscriber Server (HSS), and execute the VoLTE account opening instruction for users who meet the account opening conditions.

[0034] However, this method is only for the account opening of 4G network VoLTE users, and relies on the VoLTE account opening tag on the HSS to determine whether the number meets the account opening conditions, that is, the user's VoLTE account opening tag is determined by the mobile directory number (MDN), and the use and consistency of the International Mobile Subscriber Identity (IMSI) are not judged. Due to factors such as abnormal execution of acceptance work orders and abnormal resource record information, the user network data and acceptance system data resources do not match, and the acceptance instruction is abnormal. The problem exists for a long time. That is, the IMSI recorded by the acceptance system is incorrect, or the MDN and IMSI recorded on the network element side do not match the information recorded by the acceptance system. For example, when the new installation is performed, if the IMSI to be used provided by the acceptance system is actually occupied in the network element, the new installation instruction sent to the network element will fail to execute; when changing the card or disassembling the machine, if the IMSI of the card to be replaced or disassembled provided by the acceptance system is not occupied in the network element, that is, the IMSI is actually an empty number on the network element side, the card replacement instruction or disassembly instruction sent to the network element will fail to execute.

[0035] In view of the problems existing in the related art, the embodiment of the present application provides a service processing method, which determines the target number corresponding to the target service based on the contract data information on the user data management network element after receiving the processing request for the target service, generates the target instruction set corresponding to the target service based on the target number, and executes the target instruction set to respond to the processing request. As a functional network element for unified data management, the user data management network element can perform centralized data management, and the contract data information on it is more accurate, so the target number corresponding to the target service determined based on the contract data information on the user data management network element is also more accurate, and then the target instruction set generated based on the target number is more effective, which helps to improve the efficiency and accuracy of service processing.

[0036] See also Figure 1 FIG. 1 is a flowchart of an implementation of a business processing method provided in an embodiment of the present application. The method may include the following steps:

[0037] S110: Receive a processing request for a target business.

[0038] In the embodiment of the present application, the acceptance system can receive a processing request for a target service, which can be issued by a user according to actual needs. The target service can include at least one of a new installation service, a card replacement service, and a disassembly service.

[0039] S120: Determine a target number corresponding to the target service based on the subscription data information on the user data management network element.

[0040] In the case where the target service includes a newly installed service, the target number includes the mobile directory number MDN and the international mobile subscriber identity IMSI to be newly installed;

[0041] In the case where the target service includes a card replacement service, the target number includes the MDN, old IMSI and new IMSI of the card to be replaced;

[0042] In the case where the target service includes a disassembly service, the target number includes the MDN and IMSI of the device to be disassembled.

[0043] In an embodiment of the present application, after the acceptance system receives a processing request for the target service, it can provide the MDN and IMSI corresponding to the target service, and then obtain the contract data information on the user data management (UDM) network element in real time through an interface call to obtain the usage status of the provided MDN and IMSI on the user data management network element.

[0044] Based on the contract data information on the user data management network element, the target number corresponding to the target service can be determined. As a functional network element for unified data management, the user data management network element can perform centralized data management, and the contract data information on it is more accurate, so the target number corresponding to the target service determined based on the contract data information on the user data management network element is also more accurate.

[0045] S130: Generate a target instruction set corresponding to the target service based on the target number.

[0046] After determining the target number corresponding to the target service based on the contract data information on the user data management network element, a target instruction set corresponding to the target service can be further generated based on the target number. Different types of target services have different corresponding target instruction sets. Optionally, the parameters required for processing the target service can be determined first, a target instruction set can be generated based on the parameters required for the target service, and the value of the parameter used to represent the target number contained in the target instruction set can be filled in as the target number.

[0047] S140: Execute the target instruction set to respond to the processing request.

[0048] After the target instruction set corresponding to the target service is generated, the target instruction set can be executed to send corresponding instructions for the target service to the user data management network element to respond to the processing request for the target service.

[0049] By applying the method provided in the embodiment of the present application, after receiving a processing request for a target service, the target number corresponding to the target service is determined based on the contract data information on the user data management network element, and a target instruction set corresponding to the target service is generated based on the target number, and the target instruction set is executed to respond to the processing request. As a functional network element for unified data management, the user data management network element can perform centralized data management, and the contract data information on it is more accurate, so the target number corresponding to the target service determined based on the contract data information on the user data management network element is also more accurate, and then the target instruction set generated based on the target number is more effective, which helps to improve the efficiency and accuracy of business processing.

[0050] In some embodiments of the present application, when the target service includes a newly installed service, determining the target number corresponding to the target service based on the subscription data information on the user data management network element includes:

[0051] Provide the first IMSI and the first MDN for the target service;

[0052] Determine whether account opening data exists for the first IMSI and the first MDN respectively according to the subscription data information on the user data management network element;

[0053] If the first IMSI does not have account opening data, the first IMSI is determined as the IMSI to be newly installed corresponding to the target service;

[0054] If the first MDN does not have account opening data, the first MDN is determined as the MDN to be newly installed corresponding to the target service.

[0055] For the convenience of description, the above steps are combined for explanation.

[0056] In the embodiment of the present application, after receiving the processing request for the target service, if the target service includes a new service, the acceptance system can provide the target service with a first IMSI and a first MDN. Optionally, the acceptance system can select an unoccupied first IMSI and a first MDN based on the number information recorded by itself.

[0057] It is understandable that the number information recorded by the acceptance system itself may deviate from the contract data information on the user data management network element. Therefore, in order to ensure the accuracy of the target number corresponding to the target service finally determined, the acceptance system can determine whether the first IMSI and the first MDN have account opening data by querying the contract data information on the user data management network element after providing the first IMSI and the first MDN.

[0058] If the first IMSI does not have account opening data, it is considered that the first IMSI is not occupied, and the first IMSI can be determined as the IMSI to be newly installed corresponding to the target service.

[0059] If the first IMSI has account opening data, it can be considered that the first IMSI has been occupied and can no longer be used as the IMSI to be newly installed for the target service. Optionally, in the case where the first IMSI has account opening data, the first IMSI can be re-provided for the target service; then, based on the contract data information on the user data management network element, it is determined whether the re-provided first IMSI has account opening data; if the re-provided first IMSI does not have account opening data, the re-provided first IMSI is determined as the IMSI to be newly installed for the target service, and if the re-provided first IMSI has account opening data, the step of re-providing the first IMSI for the target service is repeated until the re-provided first IMSI does not have account opening data.

[0060] If the first MDN does not have account opening data, it is considered that the first MDN is not occupied, and the first MDN can be determined as the MDN to be newly installed corresponding to the target service.

[0061] If the first MDN has account opening data, it can be considered that the first MDN has been occupied and can no longer be used as the MDN to be newly installed for the target service. Optionally, if the first MDN has account opening data, the first MDN can be re-provided for the target service; then, based on the contract data information on the user data management network element, it is determined whether the re-provided first MDN has account opening data; if the re-provided first MDN does not have account opening data, the re-provided first MDN is determined as the MDN to be newly installed for the target service; if the re-provided first MDN has account opening data, the step of re-providing the first MDN for the target service is repeated until the re-provided first MDN does not have account opening data.

[0062] That is, for newly installed services, when it is verified that the IMSI provided by the acceptance system has account opening data on the user data management network element, the acceptance system will re-provide a new IMSI number, and then re-execute the data query of the new IMSI on the user data management network element, and repeat the above judgment logic steps until the IMSI has no account opening data on the user data management network element; when it is verified that the MDN provided by the acceptance system has account opening data on the user data management network element, the acceptance system will re-provide a new MDN number, and then re-execute the data query of the new MDN on the user data management network element, and repeat the above judgment logic steps until the MDN has no account opening data on the user data management network element; output the final IMSI and MDN to be newly installed.

[0063] It should be noted that the determination of whether the first IMSI and the first MDN have account opening data can be performed simultaneously or sequentially. For example, first determine whether the first IMSI has account opening data on the user data management network element, and after determining the IMSI to be newly installed corresponding to the target service, determine whether the first MDN has account opening data on the user data management network element to further determine the MDN to be newly installed corresponding to the target service. Alternatively, it can be determined whether the first MDN has account opening data on the user data management network element first, and after determining the MDN to be newly installed corresponding to the target service, determine whether the first IMSI has account opening data on the user data management network element to further determine the IMSI to be newly installed corresponding to the target service.

[0064] Based on the contract data information on the user data management network element, the acceptance system determines whether the IMSI and MDN provided for the newly installed service have account opening data on the user data management network element, and if the IMSI or MDN provided by it has account opening data, it will re-provide the IMSI or MDN, so as to accurately determine the IMSI and MDN to be newly installed corresponding to the target service.

[0065] In some embodiments of the present application, when the target service includes a card replacement service, determining a target number corresponding to the target service based on the subscription data information on the user data management network element includes:

[0066] Provide the target service with the second MDN, the second old IMSI and the second new IMSI of the card to be replaced;

[0067] According to the subscription data information on the user data management network element, determine whether the second new IMSI and the second MDN have account opening data;

[0068] If the second new IMSI does not have account opening data, the second new IMSI is determined as the new IMSI of the card to be replaced corresponding to the target service;

[0069] If the second MDN has account opening data, the second MDN is determined as the MDN of the card to be replaced corresponding to the target service, and it is determined whether the IMSI included in the account opening data of the second MDN is consistent with the second old IMSI;

[0070] If the IMSI included in the account opening data of the second MDN is consistent with the second old IMSI, the second old IMSI is determined as the old IMSI of the card to be replaced corresponding to the target service.

[0071] For the convenience of description, the above steps are combined for explanation.

[0072] In the embodiment of the present application, after the acceptance system receives the processing request for the target service, if the target service includes a card replacement service, the second MDN, the second old IMSI and the second new IMSI of the card to be replaced can be provided for the target service. Optionally, the acceptance system can provide the second MDN and the second old IMSI of the card to be replaced based on the number information recorded by itself, and select the unoccupied second new IMSI.

[0073] It is understandable that the number information recorded by the acceptance system itself may deviate from the contract data information on the user data management network element. Therefore, in order to ensure the accuracy of the target number corresponding to the target service finally determined, the acceptance system can determine the accuracy of the second MDN, second old IMSI and second new IMSI respectively by querying the contract data information on the user data management network element after providing the second MDN, second old IMSI and second new IMSI of the card to be replaced.

[0074] According to the subscription data information on the user data management network element, it can be determined whether the second new IMSI and the second MDN have account opening data.

[0075] If the second new IMSI does not have account opening data, it is considered that the second new IMSI is not occupied, and the second new IMSI can be determined as the new IMSI of the card to be replaced corresponding to the target service.

[0076] If the second new IMSI has account opening data, it can be considered that the second new IMSI has been occupied and can no longer be used as the new IMSI of the card to be replaced corresponding to the target service. Optionally, in the case where the second new IMSI has account opening data, the second new IMSI can be re-provided for the target service; then, based on the contract data information on the user data management network element, it is determined whether the re-provided second new IMSI has account opening data; if the re-provided second new IMSI does not have account opening data, the re-provided second new IMSI is determined as the new IMSI of the card to be replaced corresponding to the target service, and if the re-provided second new IMSI has account opening data, the step of re-providing the second new IMSI for the target service is repeated until the re-provided second new IMSI does not have account opening data.

[0077] If the second MDN does not have account opening data on the user data management network element, it is considered that the second MDN is not occupied, and the second MDN cannot be the MDN to be replaced. The second MDN provided by the acceptance system is invalid and the card replacement service cannot be carried out. In this case, the acceptance system can output an abnormal prompt message and prohibit the card replacement operation.

[0078] If the second MDN has account opening data on the user data management network element, the second MDN of the card to be replaced provided by the acceptance system can be considered valid, and the second MDN can be determined as the MDN of the card to be replaced corresponding to the target service.

[0079] In the case that the second MDN has account opening data on the user data management network element, it can be further determined whether the IMSI included in the account opening data of the second MDN is consistent with the second old IMSI.

[0080] If the IMSI included in the account opening data of the second MDN on the user data management network element is consistent with the second old IMSI, the second old IMSI can be considered valid and can be determined as the old IMSI of the card to be replaced corresponding to the target service.

[0081] If the IMSI included in the account opening data of the second MDN on the user data management network element is inconsistent with the second old IMSI, it can be considered that the second old IMSI is incorrect, and the second old IMSI can be corrected to the IMSI included in the account opening data of the second MDN, and the corrected second old IMSI can be determined as the old IMSI of the card to be replaced corresponding to the target service.

[0082] That is, for the card replacement service, the acceptance system provides the MDN, old IMSI, and new IMSI. When it is verified that the new IMSI has account opening data on the user data management network element, the acceptance system will re-provide the new IMSI, and then re-execute the data query of the new IMSI on the user data management network element, and repeat the above judgment logic steps until the new IMSI has no account opening data on the user data management network element. When it is verified that the MDN has account opening data on the user data management network element, the IMSI of the MDN on the user data management network element is compared with the old IMSI. When the comparison is inconsistent, the old IMSI value is corrected to the IMSI queried based on the MDN. Output the final MDN, old IMSI, and new IMSI of the card to be replaced.

[0083] It should be noted that the determination of whether the second new IMSI and the second MDN have account opening data can be performed simultaneously or sequentially. For example, first determine whether the second new IMSI has account opening data on the user data management network element, and after determining the new IMSI of the card to be replaced corresponding to the target service, determine whether the second MDN has account opening data on the user data management network element, so that if the second MDN has account opening data, the old IMSI of the card to be replaced corresponding to the target service can be further determined according to the IMSI included in the account opening data of the second MDN. Alternatively, it can be determined whether the second MDN has account opening data on the user data management network element first, and if the second MDN does not have account opening data, stop the card replacement process. If the second MDN has account opening data, after determining the old IMSI of the card to be replaced corresponding to the target service according to the IMSI included in the account opening data of the second MDN, determine whether the second new IMSI has account opening data on the user data management network element, so as to further determine the new IMSI of the card to be replaced corresponding to the target service.

[0084] The acceptance system determines whether the MDN, old IMSI and new IMSI provided for the card replacement service are valid based on the contract data information on the user data management network element, and makes corresponding corrections if there are any errors, so as to accurately determine the MDN, old IMSI and new IMSI of the card to be replaced corresponding to the target service.

[0085] In some embodiments of the present application, when the target service includes a disassembly service, determining a target number corresponding to the target service based on subscription data information on a user data management network element includes:

[0086] Provide a third MDN and a third IMSI for the target service;

[0087] Determine whether the third MDN has account opening data according to the contract data information on the user data management network element;

[0088] If the third MDN has account opening data, the third MDN is determined as the MDN to be disassembled corresponding to the target service, and it is determined whether the IMSI included in the account opening data of the third MDN is consistent with the third IMSI;

[0089] If the IMSI included in the account opening data of the third MDN is consistent with the third IMSI, the third IMSI is determined as the IMSI of the to-be-disassembled device corresponding to the target service.

[0090] For the convenience of description, the above steps are combined for explanation.

[0091] In the embodiment of the present application, after receiving the processing request for the target service, if the target service includes a disassembly service, the acceptance system can provide a third MDN and a third IMSI for the target service. Optionally, the acceptance system can provide the third MDN and the third IMSI to be disassembled based on the number information recorded by itself.

[0092] It is understandable that the number information recorded by the acceptance system itself may deviate from the contract data information on the user data management network element. Therefore, in order to ensure the accuracy of the target number corresponding to the target service finally determined, the acceptance system can determine the validity of the third MDN and the third IMSI by querying the contract data information on the user data management network element after providing the third MDN and the third IMSI.

[0093] According to the contract data information on the user management network element, it can be determined whether the third MDN has account opening data.

[0094] If the third MDN does not have account opening data on the user data management network element, it is considered that the third MDN is not occupied and cannot be the MDN to be disassembled. The third MDN provided by the acceptance system is invalid and the disassembly service cannot be carried out. In this case, the acceptance system can output an abnormal prompt message and prohibit the disassembly operation.

[0095] If the third MDN has account opening data on the user data management network element, the third MDN to be disassembled provided by the acceptance system can be considered valid, and the third MDN can be determined as the MDN to be disassembled corresponding to the target service.

[0096] In the case that the third MDN has account opening data on the user data management network element, it can be further determined whether the IMSI included in the account opening data of the third MDN is consistent with the third IMSI.

[0097] If the IMSI included in the account opening data of the third MDN on the user data management network element is consistent with the third IMSI, the third IMSI can be considered valid and the third IMSI can be determined as the IMSI to be removed corresponding to the target service.

[0098] If the IMSI included in the account opening data of the third MDN on the user data management network element is inconsistent with the third IMSI, it can be considered that the third IMSI provided by the acceptance system is incorrect, and the third IMSI can be corrected to the IMSI included in the account opening data of the third MDN, and the corrected third IMSI can be determined as the IMSI of the machine to be disassembled corresponding to the target service.

[0099] That is, for the disassembly service, the acceptance system provides MDN and IMSI. The data of the MDN on the user data management network element is obtained, and the consistency of the IMSI obtained based on the MDN and the IMSI provided by the acceptance system is compared. If they are inconsistent, the IMSI value provided by the acceptance system is corrected to the IMSI obtained based on the MDN, and the final IMSI and MDN of the device to be disassembled are output.

[0100] The acceptance system determines whether the IMSI and MDN provided for the disassembly service are valid based on the contract data information on the user data management network element, and makes corresponding corrections if they are incorrect. It can accurately determine the IMSI and MDN of the device to be disassembled corresponding to the target service.

[0101] In some embodiments of the present application, executing the target instruction set may include the following steps:

[0102] Based on the standard instruction set template corresponding to the target business, key parameters of the target instruction set are verified;

[0103] If the verification passes, the target instruction set is executed.

[0104] For the convenience of description, the above steps are combined for explanation.

[0105] In the embodiment of the present application, after accurately determining the target number corresponding to the target service based on the contract data information on the user data management network element, the target instruction set corresponding to the target service can be further generated based on the target number. Before executing the target instruction set, the key parameters of the target instruction set can be checked for completeness. The key parameters of the target instruction set can be checked based on the standard instruction set template corresponding to the target service.

[0106] If the verification passes, the target instruction set is executed. If the verification fails, corresponding adjustments can be made to improve the success rate of instruction execution.

[0107] In some embodiments of the present application, it can be determined first whether the target instruction set includes all key parameters included in the standard instruction set template corresponding to the target business; if the target instruction set includes all key parameters included in the standard instruction set template corresponding to the target business, it is determined whether the value of the target parameter in the target instruction set matches the target number, and the target parameter is a key parameter that characterizes the target number; if the value of the target parameter in the target instruction set matches the target number, it is determined that the verification of the target instruction set has passed.

[0108] In the embodiment of the present application, the standard instruction set template corresponding to the target service may be determined first. Different services correspond to different standard instruction set templates. The standard instruction set template includes at least one key parameter.

[0109] After the target instruction set is generated, key parameters included in the target instruction set may be compared with key parameters included in the standard instruction set template corresponding to the target business.

[0110] If the target instruction set includes all key parameters included in the standard instruction set template corresponding to the target service, it can be considered that the key parameters included in the target instruction set are complete.

[0111] If the target instruction set does not include all the key parameters included in the standard instruction set template corresponding to the target business, it is considered that the key parameters included in the target instruction set are incomplete, and the target instruction set corresponding to the target business can be regenerated until the regenerated target instruction set includes all the key parameters included in the standard instruction set template corresponding to the target business.

[0112] For example, for the new installation business, there are four corresponding scenarios, and different scenarios have corresponding standard instruction set templates and corresponding key parameters. (1) New IMSI authentication scenario for UDM network elements: consistency check and correction of parameters including UDM Serial Number (UDMSN), IMSI, Key Identifier VALUE (KIVALUE), K4 Serial Number (K4SNO), Algorithm (ALG) (used to indicate the type of authentication algorithm), Operational Ciphering Key (OPC) value (OPCVALUE), and Access and Mobility Management Function (AMF) Serial Number (AMF Serial Number, AMFSNO); (2) New account opening scenario for 5G numbers: consistency check and correction of parameters including UDMSN, IMSI, MDN, NGSUSERTPLID (account opening template for identifying 5G users), NGCNODETDPLID (roaming restriction template for identifying 5G users), and EPSUSERTPLID (for identifying Evolved Packet System (EPS)). (3) New 5G VoLTE account opening scenario: consistency check and correction of UDMSN, IMSI, MDN, IP Multimedia Private Identity (IMPI), IP Multimedia Public Identity (IMPU) list (IMPULIST), SIFCLIST (used to indicate the initial filtering rule list of the Serving-Call Session Control Function (S-CSCF)), and VOLTETAG (used to indicate the VoLTE user identity) parameters; (4) New VoLTE Grouped User Service Switching (GUSS) account opening scenario: consistency check and correction of IMPI, GSID (used to indicate the generic authentication architecture (GAA) service type identifier), and validity period (LIFETIME) parameters;

[0113] For the card replacement service, there are three corresponding scenarios, and different scenarios have corresponding standard instruction set templates and corresponding key parameters. (1) UDM network element adds IMSI authentication scenario: perform consistency check and correction of UDMSN, IMSI, KIVALUE, K4SNO, ALG, OPCVALUE, and AMFSNO parameters; (2) 5G user's old IMSI is replaced with a new IMSI scenario: perform consistency check and correction of MDN, IMSI, NEWIMSI (used to indicate the new IMSI), IMPI, NEWIMPI (used to indicate the new IMPI), and IMPU parameters; (3) Deletion of old IMSI authentication scenario: consistency check and correction of IMSI parameters;

[0114] For the disassembly service, there are two corresponding scenarios, and different scenarios have corresponding standard instruction set templates and corresponding key parameters. (1) 5G VoLTE account cancellation scenario: perform consistency check and correction of MDN, IMSI, IMPI, and IMPULIST parameters; (2) 5G account cancellation: perform consistency check and correction of MDN and IMSI key parameters.

[0115] It can be further determined whether the value of the target parameter in the target instruction set matches the target number. The target parameter is a key parameter that characterizes the target number. If the value of the target parameter in the target instruction set matches the target number, it is determined that the verification of the target instruction set has passed. If the value of the target parameter in the target instruction set does not match the target number, the value of the target parameter in the target instruction set can be updated to the target number to determine that the verification has passed.

[0116] Based on the standard instruction set template corresponding to the target business, the key parameters of the target instruction set are verified. The target instruction set is executed only after the verification is passed. This can ensure the correctness of the issued instruction set, help improve the success rate of instruction execution, and effectively improve the success rate of business acceptance.

[0117] The technical solutions provided in the embodiments of the present application are described above. For ease of understanding, they are further described below with specific examples.

[0118] 1) An example of consistency comparison of acceptance number data obtained based on real-time data from UDM network elements is as follows:

[0119] Example 1: New Installation Business

[0120] New services involve four scenario steps in the UDM network element: new IMSI authentication in the UDM network element, new account opening for 5G numbers, new account opening for 5G VoLTE, and new account opening for VoLTE GUSS. Before carrying out new services, a consistency comparison of the number data in scenario 1 and scenario 2 is carried out.

[0121] Take the IMSI 46011A and MDN 189A that will be newly activated in the acceptance system as an example, the details are as follows:

[0122] Scenario 1: UDM network element adds IMSI authentication

[0123] Information acquisition: Based on the UDM information query interface, IMSI information is obtained from the UDM network element in real time. The interface input parameters include the key: {IMSI, MDN}, where IMSI and MDN are selected and filled in. The interface input parameter value is {'46011A', ''}, which means that the configuration of the IMSI on the UDM network element is obtained through the input parameter of IMSI 46011A. The output result is RESULT_IMSI.

[0124] Result acquisition: Get relevant parameters through the information result RESULT returned by the interface, and extract the value corresponding to {RESULTCODE} in RESULT, which means: result code.

[0125] Data preprocessing: Use the value of the RESULTCODE result to determine whether the newly added IMSI is currently occupied. The operation method is as follows:

[0126] If the RESULTCODE value is 0, it means the query is successful, that is, the current IMSI is occupied and there is account opening data. All new scenarios are terminated, and the acceptance system reallocates a new IMSI, such as 46011B for number 189A, and repeats the consistency comparison process of scenario 1 until the RESULTCODE value is not 0; if the RESULTCODE value is not 0, it means the query failed, indicating that the current IMSI is not occupied, there is no account opening data, and the data consistency comparison of scenario 1 passes.

[0127] Scenario 2: Opening a new account with a 5G number

[0128] Information acquisition: Based on the UDM information query interface, MDN information is obtained from the UDM network element in real time. The interface input parameter value is {'', '189A'}, which means that the configuration of the MDN on the UDM network element is obtained through the input parameter of MDN 189A. The output result is RESULT_MDN.

[0129] Result acquisition: Get relevant parameters through the information result RESULT returned by the interface, and extract the value corresponding to {RESULTCODE} in RESULT, which means: result code.

[0130] Data preprocessing: Use the value of the RESULTCODE result to determine whether the newly added MDN is currently occupied. The operation method is as follows:

[0131] If the RESULTCODE value is 0, it means the query is successful, that is, the current MDN is occupied and there is account opening data. MDN_USED is assigned to 0, all new scenarios are terminated, and the acceptance system reallocates a new MDN, such as 189B, and repeats the consistency comparison process of scenario 2 until the RESULTCODE value is not 0; if the RESULTCODE value is not 0, it means the query failed, indicating that the current MDN is not occupied and there is no account opening data, and the data consistency comparison of scenario 2 passes.

[0132] Since the premise of the operation of adding a new 5G VoLTE account in scenario 3 and adding a new VoLTE GUSS in scenario 4 is that scenario 1 and scenario 2 have been successfully executed, that is, scenario 1 and scenario 2 have completed account opening. Therefore, when there is no account opening data in scenario 1 and scenario 2, it means that there is no account opening data in scenario 3 and scenario 4. Therefore, when there is no account opening data in scenario 1 and scenario 2, the acceptance system generates new installation instruction sets corresponding to scenario 1, scenario 2, scenario 3, and scenario 4.

[0133] Example 2: Card replacement service

[0134] The card replacement service involves three scenarios in the UDM network element: new IMSI authentication and number release, replacement of the old IMSI of 5G users with the new IMSI, and deletion of the old IMSI authentication. Before executing the card replacement, the consistency comparison of the data of the two scenarios of new IMSI authentication and number release and replacement of the old IMSI of 5G users with the new IMSI is mainly carried out.

[0135] Take the MDN as 189A and the old IMSI as 46011A changed to 46011C as an example, the details are as follows:

[0136] Scenario 1: New IMSI authentication and number release

[0137] The specific steps are the same as those in the new installation scenario 1 and are not repeated here.

[0138] Scenario 2: 5G user's old IMSI is replaced with a new IMSI

[0139] Information acquisition: Based on the UDM information query interface, the account opening information is obtained from the UDM network element in real time. The interface input parameters include the key: {IMSI, MDN}, where IMSI and MDN are selected and filled in. The interface input parameter value is {'46011A', ''}, which means that the configuration of the IMSI on the UDM network element is obtained through the input parameter of IMSI 46011A, and the output result is RESULT_IMSI; the interface input parameter value is {'', '189A'}, which means that the configuration of the MDN on the UDM network element is obtained through the input parameter of MDN 189A, and the output result is RESULT_MDN.

[0140] Result acquisition: Call the UDM account opening information interface with MDN input parameter 189A and new IMSI input parameter 46011B respectively, and obtain the return results RESULT_MDN and RESULT_IMSI_NEW respectively. Extract the value corresponding to {RESULTCODE, IMSI} in RESULT_MDN and re-mark it as {RESULTCODE_MDN_OLD, IMSI_MDN_OLD}, which means: result code, IMSI; extract the value corresponding to {RESULTCODE} in RESULT_IMSI_NEW, and re-mark it as {RESULTCODE_IMSI_NEW}.

[0141] Data preprocessing:

[0142] Step 1: When the value of RESULTCODE_MDN_OLD is not 0, it means that the number of the card to be replaced does not have data in the UDM network element, that is, the provided MDN number is empty and the card replacement service cannot be carried out. An abnormal prompt is given on the acceptance system interface and the card replacement operation is prohibited, ending the current process; when RESULTCODE_MDN_OLD is 0, IMSI_MDN_OLD is compared with 46011A. When IMSI_MDN_OLD is equal to 46011A, it means that the IMSI corresponding to MDN 189A is consistent with the old IMSI, that is, 46011A data, and step 2 is carried out; if IMSI_MDN_OLD is not equal to 46011A, the old IMSI of the card to be replaced is changed to the value of IMSI_MDN_OLD, and step 2 is carried out.

[0143] Step 2: When the value of RESULTCODE_IMSI_NEW is not 0, it means that there is no account opening data for the IMSI number 46011C on the UDM, and the new IMSI number 46011C can be used and passes the consistency comparison in scenario 2; if the value of RESULTCODE_IMSI_NEW is 0, it means that there is account opening data for the IMSI number 46011C on the UDM, and the new IMSI number 46011C has been occupied. The acceptance system needs to reallocate a new IMSI number, such as 46011D, and re-perform the check in step 2 to see if the IMSI number is occupied, until the value of RESULTCODE_IMSI_NEW is not 0 and passes the consistency comparison in scenario 2.

[0144] When the consistency comparison between scene 1 and scene 2 is passed, the acceptance system generates the card replacement instruction set corresponding to scene 1, scene 2, and scene 3.

[0145] Example 3: Disassembly business

[0146] The device disassembly service in the UDM network element involves two scenario steps: 5G VoLTE account cancellation and 5G user account cancellation. Before the device is disassembled, a consistency comparison of the data of the number to be disassembled is carried out.

[0147] Take the MDN number of the device to be disassembled as 189A and the corresponding IMSI number as 46011A as an example, the details are as follows:

[0148] Scenario 1: 5G VoLTE account cancellation

[0149] Information acquisition: Based on the UDM information query interface, the account opening information is obtained from the UDM network element in real time. The interface input parameters include the key: {IMSI, MDN}, where IMSI and MDN are selected and filled in. The corresponding interface input parameter value is {'46011A', ''}, which means that the configuration of the IMSI number on the UDM network element is obtained through the input parameter of IMSI 46011A, and the output result is RESULT_IMSI; the interface input parameter value is {'', '189A'}, which means that the configuration of the MDN number on the UDM network element is obtained through the input parameter of MDN 189A, and the output result is RESULT_MDN.

[0150] Result acquisition: Call the UDM information interface with MDN as input parameter 189A, obtain the returned result RESULT_MDN respectively, extract the value corresponding to {RESULTCODE, IMSI} in RESULT_MDN and re-mark it as {RESULTCODE_MDN, IMSI_MDN}, which means: result code, IMSI number.

[0151] Data preprocessing:

[0152] Step 1: When the value of RESULTCODE_MDN is not 0, it means that there is no data for the number to be disassembled on the UDM network element, that is, the MDN number provided is empty and the disassembly service cannot be carried out. An abnormal prompt will be given on the acceptance system interface and the disassembly operation will be prohibited, ending the current process; when RESULTCODE_MDN is 0, proceed to step 2.

[0153] Step 2: If the IMSI_MDN value in RESULT_MDN is equal to 46011A, it indicates that the MDN number 189A provided by the acceptance system matches the IMSI number 46011A on the core network UDM network element, and a corresponding disassembly instruction set is generated; (2) If the IMSI_MDN value in RESULT_MDN is not equal to 46011A, it indicates that the MDN number 189A does not match the IMSI number 46011A on the core network UDM network element. The IMSI number to be disassembled is changed from 46011A to the IMSI_MDN value in RESULT_MDN, and the 5G VoLTE cancellation consistency comparison is performed.

[0154] The basic premise of 5G VoLTE account opening is that 5G users have opened accounts. Therefore, if it is determined that 5G VoLTE has been opened, there is no need to determine whether 5G users have opened accounts. When the consistency comparison of scenario 1 passes, the acceptance system generates the disassembly instruction sets for scenario 1 and scenario 2.

[0155] 2) An example of performing consistency check of key parameters of accepted instruction sets based on standard instruction set templates is as follows:

[0156] Based on the consistency comparison operation of the acceptance number data obtained from the real-time data of the UDM network element, after obtaining the final correct user MDN number and IMSI number for the service to be accepted, the acceptance system generates the input instructions for the service to be accepted according to the relevant business rules, and calls the UDM network element acceptance interface to issue parameters. Therefore, before the acceptance instruction is issued, the completeness of the key parameters of the instruction set needs to be verified.

[0157] Example 1: New Installation Business

[0158] The new service involves four scenario steps in the UDM network element: new IMSI authentication of the UDM network element, new account opening of 5G number, new account opening of 5G VoLTE, and new account opening of VoLTE GUSS.

[0159] Take the final user MDN number as 189A and IMSI number as 46011A as an example:

[0160] Scenario 1: UDM network element adds IMSI authentication

[0161] The newly added standard instruction set template for IMSI authentication is: ADD_AUTH={UDMSN, IMSI, KIVALUE, K4SNO, ALG, OPCVALUE, AMFSNO}.

[0162] Information acquisition: The new installation instruction set to be issued generated by the acceptance system is ADD_AUTH_B = {UDMSN_B, IMSI_B, KIVALUE_B, K4SNO_B, ALG_B, OPCVALUE_B, AMFSNO_B}.

[0163] Data preprocessing:

[0164] Step 1: When the value of any parameter UDMSN_B, IMSI_B, KIVALUE_B, K4SNO_B, ALG_B, OPCVALUE_B, AMFSNO_B in ADD_AUTH_B is empty, such as NULL or None, it indicates that the acceptance instruction set is generated abnormally. The acceptance system regenerates a new instruction set ADD_AUTH_C and repeats the above judgment operation until all parameters are not NULL or None, and then executes step 2.

[0165] Step 2: Define the instruction set obtained in step 1 as ADD_AUTH_NEW. If the value of the parameter IMSI_B in ADD_AUTH_NEW is equal to 46011A, it means that the completeness of the instruction set of the current scenario 1 has passed the verification, and its instruction set is determined to be ADD_AUTH_NEW; if the value of the parameter IMSI_B in ADD_AUTH_NEW is not equal to 46011A, the value of the parameter IMSI_B in ADD_AUTH_NEW is replaced with 46011A and determined as the final instruction set, and the completeness check of the instruction set of scenario 1 is passed.

[0166] Scenario 2: Opening a new account with a 5G number

[0167] The standard instruction set template for opening a new account with a 5G number is: ADD_5G = {UDMSN, IMSI, MDN, NGSUSERTPLID, NGCNODETPLID, EPSUSERTPLID, SHRDUSERTPLID, INSTALLTYPE}.

[0168] Information acquisition: The new installation instruction set to be issued generated by the acceptance system is ADD_5G_B = {UDMSN_B, IMSI_B, MDN_B, NGSUSERTPLID_B, NGCNODETPLID_B, EPSUSERTPLID_B, SHRDUSERTPLID_B, INSTALLTYPE_B}.

[0169] Data preprocessing:

[0170] Step 1: When the value of any parameter among UDMSN_B, IMSI_B, MDN_B, NGSUSERTPLID_B, NGCNODETPLID_B, EPSUSERTPLID_B, SHRDUSERTPLID_B, and INSTALLTYPE_B in ADD_5G_B is NULL or None, it indicates that the instruction set generation is abnormal. The acceptance system regenerates a new installation instruction set ADD_5G_C and repeats the above judgment operation until the above parameters are not NULL or None, and then executes step 2;

[0171] Step 2: Define the instruction set obtained in step 1 as ADD_5G_NEW. If the value of the parameter IMSI_B in ADD_5G_NEW is equal to 46011A and the value of MDN_B is equal to 189A, it means that the completeness of the instruction set of the current scenario 2 has passed the verification, and its instruction set is determined to be ADD_5G_NEW; if the value of the parameter IMSI_B in ADD_5G_NEW is not equal to 46011A, the value of the parameter IMSI_B in ADD_5G_NEW is replaced with 46011A. If the value of the parameter MDN_B in ADD_5G_NEW is not equal to 189A, the value of the parameter MDN_B in ADD_5G_NEW is replaced with 189A, and it is determined as the final instruction set, and the completeness check of the instruction set of scenario 2 is passed.

[0172] Scenario 3: 5G VoLTE new account opening

[0173] The standard instruction set template for opening a new account with a 5G number is: ADD_VOLTE = {UDMSN, IMSI, MDN, IMPI, IMPULIST, SIFCLIST, VOLTETAG}.

[0174] Information acquisition: The new installation instruction set to be issued generated by the acceptance system is ADD_VOLTE_B = {UDMSN_B, IMSI_B, MDN_B, IMPI_B, IMPULIST_B, SIFCLIST_B, VOLTETAG_B}.

[0175] Data preprocessing:

[0176] Step 1: When the value of any parameter among UDMSN_B, IMSI_B, MDN_B, IMPI_B, IMPULIST_B, SIFCLIST_B, and VOLTETAG_B in ADD_VOLTE_B is NULL or None, it indicates that the instruction set generation is abnormal. The acceptance system regenerates a new instruction set ADD_VOLTE_C and repeats the above judgment operation until the above parameters are not NULL or None, and then executes step 2;

[0177] Step 2: Redefine the instruction set obtained in step 1 as ADD_VOLTE_NEW. If the value of the parameter IMSI_B in ADD_VOLTE_NEW is equal to 46011A and the value of MDN_B is equal to 189A, it means that the completeness of the instruction set of the current scenario 2 has passed the verification, and its instruction set is determined to be ADD_5G_NEW; if the value of the parameter IMSI_B in ADD_VOLTE_NEW is not equal to 46011A, the value of the parameter IMSI_B in ADD_VOLTE_NEW is replaced with 46011A. If the value of the parameter MDN_B in ADD_VOLTE_NEW is not equal to 189A, the value of the parameter MDN_B in ADD_VOLTE_NEW is replaced with 189A, and it is determined as the final instruction set, and the instruction set completeness check of scenario 3 is passed.

[0178] Scenario 4: VoLTE GUSS new account opening

[0179] The standard instruction set template for opening a new account with a 5G number is: ADD_VOLTE_GUSS = {IMPI, GSID, LIFETIME}.

[0180] Information acquisition: The new installation instruction set to be issued generated by the acceptance system is ADD_VOLTE_GUSS_B = {IMPI_B, GSID_B, LIFETIME_B}.

[0181] Data preprocessing:

[0182] Step 1: When the value of any parameter among IMPI_B, GSID_B, LIFETIME_B in ADD_VOLTE_GUSS_B is NULL or None, it indicates that the instruction set is generated abnormally. The acceptance system regenerates a new instruction set ADD_VOLTE_GUSS_C and repeats the above judgment operation until the above parameters are not NULL or None, and then executes step 2;

[0183] Step 2: Redefine the instruction set obtained in step 1 as ADD_VOLTE_GUSS_NEW. If the value of parameter IMPI_B in ADD_VOLTE_NEW is equal to 46011A, it means that the completeness of the instruction set of the current scenario 2 has passed the verification, and its instruction set is determined to be ADD__VOLTE_GUSS_NEW; if the value of parameter IMPI_B in ADD_VOLTE_GUSS_NEW is not equal to 46011A, then replace the value of parameter IMSI_B in ADD_VOLTE_NEW with 46011A, and determine it as the final instruction set, and pass the completeness check of the instruction set of scenario 4.

[0184] When the completeness checks of the instruction sets for scenarios 1 to 4 are passed, execute the ADD_AUTH_NEW, ADD_5G_NEW, ADD_VOLTE_NEW, and ADD_VOLTE_GUSS_NEW instruction sets in sequence to complete the processing of the new service.

[0185] Example 2: Card replacement service

[0186] The card replacement service involves three scenarios in the UDM network element: new IMSI authentication and number release, replacement of the old IMSI of 5G users with the new IMSI, and deletion of the old IMSI authentication. Before executing the card replacement, the consistency comparison of the card number data to be replaced is carried out.

[0187] For example, the final user MDN number is 189A, the old IMSI number is 46011A, and the new IMSI number is 46011B.

[0188] Scenario 1: UDM network element adds IMSI authentication

[0189] The newly added standard instruction set template for IMSI authentication is: CHG_AUTH={UDMSN, IMSI, KIVALUE, K4SNO, ALG, OPCVALUE, AMFSNO}.

[0190] Information acquisition: The card replacement instruction set to be issued generated by the acceptance system is CHG_AUTH_B = {UDMSN_B, IMSI_B, KIVALUE_B, K4SNO_B, ALG_B, OPCVALUE_B, AMFSNO_B}.

[0191] Data preprocessing:

[0192] Step 1: When the value of any parameter UDMSN_B, IMSI_B, KIVALUE_B, K4SNO_B, ALG_B, OPCVALUE_B, and AMFSNO_B in CHG_AUTH_B is NULL or None, it indicates that the acceptance instruction set is generated abnormally. The acceptance system regenerates the card replacement instruction set CHG_AUTH_C and repeats the above judgment operation until all parameters are not NULL or None, and then executes step 2.

[0193] Step 2: Define the instruction set obtained in step 1 as CHG_AUTH_NEW. If the value of the parameter IMSI_B in CHG_AUTH_NEW is equal to 46011B, it means that the completeness of the instruction set of the current scenario 1 has passed the verification, and its instruction set is determined to be CHG_AUTH_NEW; if the value of the parameter IMSI_B in CHG_AUTH_NEW is not equal to 46011B, the value of the parameter IMSI_B in CHG_AUTH_NEW is replaced with 46011B and determined as the final instruction set, and the completeness check of the instruction set of scenario 1 is passed.

[0194] Scenario 2: 5G user's old IMSI is replaced with a new IMSI

[0195] The standard instruction set template for 5G number IMSI replacement is: CHG_5G = {MDN, IMSI, NEWIMSI, IMPI, NEWIMPI, IMPU, NEWIMPU}.

[0196] Information acquisition: The new installation instruction set to be issued generated by the acceptance system is CHG_5G_B = {MDN_B, IMSI_B, NEWIMSI_B, IMPI_B, NEWIMPI_B, IMPU_B}.

[0197] Data preprocessing:

[0198] Step 1: When the value of any parameter among NEWIMSI_B, IMPI_B, NEWIMPI_B, and IMPU_B in CHG_5G_B is NULL or None, it indicates that the instruction set is generated abnormally, and the acceptance system regenerates the card replacement instruction set CHG_5G_C and repeats the above judgment operation until the above parameters are not NULL or None, and then executes step 2;

[0199] Step 2: Define the instruction set obtained in step 1 as CHG_5G_NEW. (1) If the values ​​of the parameters IMSI_B and MDN_B in CHG_5G_NEW are both equal to NULL or None, set the parameter IMSI_B in CHG_5G_NEW to 46011B, determine it as the final instruction set, and pass the completeness check of the instruction set of scenario 2. (2) If the values ​​of the parameters IMSI_B and MDN_B in CHG_5G_NEW are not equal to NULL or None, set the parameter IMSI_B in CHG_5G_NEW to 46011B, set the value of the parameter MDN_B in CHG_5G_NEW to NULL or None, determine it as the final instruction set, and pass the completeness check of the instruction set of scenario 2.

[0200] Scenario 3: Deleting old IMSI authentication

[0201] The standard instruction set template for deleting IMSI authentication is: DEL_AUTH={IMSI}.

[0202] Information acquisition: The card replacement instruction set to be issued generated by the acceptance system is DEL_AUTH_B=IMSI_B.

[0203] Data preprocessing:

[0204] Step 1: When the value of the parameter IMSI_B in DEL_AUTH_B is not equal to 46011A, the value of the parameter IMSI_B in DEL_AUTH_B is replaced with 46011A and determined as the final instruction set, and the integrity check of the instruction set of scenario 3 is passed.

[0205] When the completeness checks of the instruction sets for scenarios 1 to 3 are passed, the ADD_AUTH_NEW, CHG_5G_NEW, and DEL_AUTH_B instruction sets are executed in sequence to complete the card replacement service.

[0206] Example 3: Disassembly business

[0207] The device disassembly service in the UDM network element involves two scenario steps: 5G VoLTE account cancellation and 5G user account cancellation. Before the device is disassembled, a consistency comparison of the data of the number to be disassembled is carried out.

[0208] Take the final MDN number of the device to be disassembled as 189A and the corresponding IMSI number as 46011A as an example, the details are as follows:

[0209] Scenario 1: 5G VoLTE account cancellation

[0210] The standard instruction set template for 5G VoLTE account cancellation is: DEL_VOLTE = {MDN, IMSI, IMPI, IMPULIST},

[0211] Information acquisition: The disassembly instruction set to be issued generated by the acceptance system is DEL_VOLTE_B = {MDN_B, IMSI_B, IMPI_B, IMPULIST_B}.

[0212] Data preprocessing:

[0213] Step 1: When the value of any parameter among MDN_B, IMSI_B, IMPI_B, IMPULIST_B in DEL_VOLTE_B is NULL or None, it indicates that the instruction set is generated abnormally. The acceptance system regenerates the disassembly instruction set DEL_VOLTE_C and repeats the above judgment operation until the above parameters are not NULL or None, and then executes step 2;

[0214] Step 2: Redefine the instruction set obtained in step 1 as DEL_VOLTE_NEW. If the value of parameter IMSI_B in DEL_VOLTE_NEW is equal to 46011A and the value of MDN_B is equal to 189A, it means that the completeness of the instruction set of the current scenario 1 has passed the verification, and its instruction set is determined to be DEL_VOLTE_NEW; if the value of parameter IMSI_B in DEL_VOLTE_NEW is not equal to 46011A, the value of parameter IMSI_B in DEL_VOLTE_NEW is replaced with 46011A. If the value of parameter MDN_B in DEL_VOLTE_NEW is not equal to 189A, the value of parameter MDN_B in DEL_VOLTE_NEW is replaced with 189A, and it is determined as the final instruction set, and the completeness check of the instruction set of scenario 1 is passed.

[0215] Scenario 2: 5G account cancellation

[0216] The standard instruction set template for 5G account cancellation is: DEL_5G = {MDN, IMSI}.

[0217] Information acquisition: The disassembly instruction set to be issued generated by the acceptance system is DEL_5G_B = {MDN_B, IMSI_B}.

[0218] Data preprocessing:

[0219] If the value of parameter IMSI_B in DEL_5G_B is not equal to 46011A, the value of parameter IMSI_B in DEL_5G_B is replaced with 46011A; if the value of parameter MDN_B in DEL_5G_B is not equal to 189A, the value of parameter MDN_B in DEL_5G_B is replaced with 189A, and it is determined as the final instruction set, and the integrity check of the instruction set of scenario 2 is passed.

[0220] When the completeness checks of the instruction sets from scenario 1 to scenario 2 are passed, execute the DEL_VOLTE_NEW and DEL_5G_B instruction sets in sequence and complete the disassembly service.

[0221] like Figure 2 As shown in the figure, the new installation business processing process is as follows:

[0222] Receive processing requests for new installation business;

[0223] The acceptance system provides IMSI and MDN for new services;

[0224] Obtaining UDM network element data based on the IMSI, determining whether the IMSI is occupied, if not occupied, determining the IMSI as the IMSI to be newly installed, and if occupied, repeating the step of providing the IMSI for the newly installed service to re-provide the IMSI;

[0225] Acquire UDM network element data based on the MDN, determine whether the MDN is occupied, if not occupied, determine the MDN as the MDN to be newly installed, if occupied, repeat the step of providing the MDN for the newly installed service to re-provide the MDN;

[0226] Generate instruction sets for scenarios 1 to 4 according to the finally determined IMSI and MDN to be newly installed;

[0227] Verify the key parameters of the instruction sets of scenes 1 to 4. If the verification fails, modify the instruction set, regenerate the instruction set, and repeat the key parameter verification steps. If the verification passes, send the instruction sets of scenes 1 to 4 in sequence.

[0228] Scenarios 1 to 4 here refer to the four scenarios corresponding to the new installation business.

[0229] like Figure 3 As shown in the figure, the card replacement service processing process is as follows:

[0230] Receive requests for card replacement services;

[0231] The acceptance system provides MDN, old IMSI, and new IMSI for card replacement services;

[0232] Obtaining UDM network element data based on the new IMSI, determining whether the new IMSI is occupied, if not occupied, determining the new IMSI as the new IMSI to be replaced, if occupied, repeating the step of providing a new IMSI for the card replacement service to re-provide a new IMSI;

[0233] Based on the MDN, the UDM network data is obtained to determine whether the MDN has account opening data. If not, the process ends. If so, the IMSI contained in the account opening data of the MDN is compared with the old IMSI for consistency. If the comparison fails, the old IMSI is corrected. If the comparison passes or the old IMSI is corrected, the instruction set for scenarios 1 to 3 is generated based on the final MDN, old IMSI, and new IMSI of the card to be replaced.

[0234] Verify the key parameters of the instruction sets of scenes 1 to 3. If the verification fails, modify the instruction set, regenerate the instruction set, and repeat the key parameter verification steps. If the verification passes, send the instruction sets of scenes 1 to 3 in sequence.

[0235] Scenarios 1 to 3 here refer to the three scenarios corresponding to the card replacement service.

[0236] like Figure 4 As shown in the figure, the disassembly business processing process is as follows:

[0237] Receive requests for dismantling services;

[0238] The acceptance system provides MDN and IMSI for the disassembly business;

[0239] Based on the MDN, the UDM network data is obtained, and the IMSI contained in the account opening data of the MDN is compared with the IMSI provided by the acceptance system for consistency. If the comparison fails, the IMSI provided by the acceptance system is corrected. If the comparison passes or the IMSI correction is completed, the instruction set from scenario 1 to scenario 2 is generated according to the final MDN and IMSI of the device to be disassembled.

[0240] Verify the key parameters of the instruction set from scene 1 to scene 2. If the verification fails, modify the instruction set, regenerate the instruction set, and repeat the key parameter verification steps. If the verification passes, send the instruction sets from scene 1 to scene 2 in sequence.

[0241] Scenario 1 and Scenario 2 here refer to the two scenarios corresponding to the disassembly business.

[0242] The embodiment of the present application is aimed at the new installation, card replacement, and disassembly services of 5G users. By obtaining the relevant contract data information of the user of the service to be accepted on the UDM side of the core network, the consistency comparison of the corresponding service number acceptance system data and the network element side data is carried out according to the service scenario, and the corresponding data correction plan is provided, and finally the correct user key MDN and IMSI information is obtained, and the corresponding instruction set is generated according to the correct MDN and IMSI. Before the instruction set is issued to the network element, the key indicator information of the instruction set is audited and determined, and finally the correct issuance of the instruction is achieved. Through this method, the long-standing problems of mismatch between user network data and acceptance system data resources and abnormal generated acceptance instructions caused by abnormal execution of acceptance work orders and abnormal resource record information can be solved, that is, the problem of failure in accepting new installation, card replacement, and disassembly services due to incorrect MDN and IMSI information recorded by the acceptance system can be solved, thereby improving the success rate of 5G user service acceptance.

[0243] Corresponding to the above method embodiment, the embodiment of the present application further provides a service processing device. The service processing device described below and the service processing method described above can refer to each other.

[0244] See also Figure 5As shown, the service processing device 500 may include the following modules:

[0245] The receiving module 510 is used to receive a processing request for a target business;

[0246] A determination module 520, configured to determine a target number corresponding to a target service based on the subscription data information on the user data management network element;

[0247] A generating module 530, configured to generate a target instruction set corresponding to a target service based on a target number;

[0248] The execution module 540 is used to execute the target instruction set in response to the processing request.

[0249] By using the device provided in the embodiment of the present application, after receiving a processing request for a target service, the target number corresponding to the target service is determined based on the contract data information on the user data management network element, and a target instruction set corresponding to the target service is generated based on the target number, and the target instruction set is executed to respond to the processing request. As a functional network element for unified data management, the user data management network element can perform centralized data management, and the contract data information on it is more accurate, so the target number corresponding to the target service determined based on the contract data information on the user data management network element is also more accurate, and then the target instruction set generated based on the target number is more effective, which helps to improve the efficiency and accuracy of business processing.

[0250] In some embodiments of the present application, when the target service includes a newly installed service, the determination module 520 is specifically configured to:

[0251] Provide the first IMSI and the first MDN for the target service;

[0252] Determine whether account opening data exists for the first IMSI and the first MDN respectively according to the subscription data information on the user data management network element;

[0253] If the first IMSI does not have account opening data, the first IMSI is determined as the IMSI to be newly installed corresponding to the target service;

[0254] If the first MDN does not have account opening data, the first MDN is determined as the MDN to be newly installed corresponding to the target service.

[0255] In some embodiments of the present application, the determination module 520 is further configured to:

[0256] If the first IMSI has account opening data, re-provide the first IMSI for the target service;

[0257] Determine whether the re-provided first IMSI has account opening data according to the subscription data information on the user data management network element;

[0258] If the newly provided first IMSI does not have account opening data, the newly provided first IMSI is determined as the IMSI to be newly installed corresponding to the target service;

[0259] If the newly provided first IMSI has account opening data, the step of re-providing the first IMSI for the target service is repeated until the newly provided first IMSI has no account opening data.

[0260] In some embodiments of the present application, the determination module 520 is further configured to:

[0261] If the first MDN has account opening data, re-provide the first MDN for the target service;

[0262] Determine whether the re-provided first MDN has account opening data according to the subscription data information on the user data management network element;

[0263] If the newly provided first MDN does not have account opening data, the newly provided first MDN is determined as the MDN to be newly installed corresponding to the target service;

[0264] If the re-provided first MDN has account opening data, the step of re-providing the first MDN for the target service is repeated until the re-provided first MDN does not have account opening data.

[0265] In some embodiments of the present application, when the target service includes a card replacement service, the determination module 520 is specifically configured to:

[0266] Provide the target service with the second MDN, the second old IMSI and the second new IMSI of the card to be replaced;

[0267] According to the subscription data information on the user data management network element, determine whether the second new IMSI and the second MDN have account opening data;

[0268] If the second new IMSI does not have account opening data, the second new IMSI is determined as the new IMSI of the card to be replaced corresponding to the target service;

[0269] If the second MDN has account opening data, the second MDN is determined as the MDN of the card to be replaced corresponding to the target service, and it is determined whether the IMSI included in the account opening data of the second MDN is consistent with the second old IMSI;

[0270] If the IMSI included in the account opening data of the second MDN is consistent with the second old IMSI, the second old IMSI is determined as the old IMSI of the card to be replaced corresponding to the target service.

[0271] In some embodiments of the present application, the determination module 520 is further configured to:

[0272] In the case where the second new IMSI has account opening data, re-provisioning the second new IMSI for the target service;

[0273] Determine whether the second new IMSI provided again has account opening data according to the subscription data information on the user data management network element;

[0274] If the second new IMSI provided again does not have account opening data, the second new IMSI provided again is determined as the new IMSI of the card to be replaced corresponding to the target service;

[0275] If the second new IMSI that is newly provided has account opening data, the step of re-providing the second new IMSI for the target service is repeated until the second new IMSI that is newly provided has no account opening data.

[0276] In some embodiments of the present application, the determination module 520 is further configured to:

[0277] If the IMSI included in the account opening data of the second MDN is inconsistent with the second old IMSI, the second old IMSI is corrected to the IMSI included in the account opening data of the second MDN;

[0278] The corrected second old IMSI is determined as the old IMSI of the card to be replaced corresponding to the target service.

[0279] In some embodiments of the present application, when the target service includes a disassembly service, the determination module 520 is specifically configured to:

[0280] Provide a third MDN and a third IMSI for the target service;

[0281] Determine whether the third MDN has account opening data according to the contract data information on the user data management network element;

[0282] If the third MDN has account opening data, the third MDN is determined as the MDN to be disassembled corresponding to the target service, and it is determined whether the IMSI included in the account opening data of the third MDN is consistent with the third IMSI;

[0283] If the IMSI included in the account opening data of the third MDN is consistent with the third IMSI, the third IMSI is determined as the IMSI of the to-be-disassembled device corresponding to the target service.

[0284] In some embodiments of the present application, when the IMSI included in the account opening data of the third MDN is inconsistent with the third IMSI, the determination module 520 is further configured to:

[0285] Correct the third IMSI to the IMSI included in the account opening data of the third MDN;

[0286] The corrected third IMSI is determined as the IMSI of the to-be-disassembled device corresponding to the target service.

[0287] In some embodiments of the present application, the execution module 540 is specifically configured to:

[0288] Based on the standard instruction set template corresponding to the target business, key parameters of the target instruction set are verified;

[0289] If the verification passes, the target instruction set is executed.

[0290] In some embodiments of the present application, the execution module 540 is specifically configured to:

[0291] Determine whether the target instruction set includes all key parameters included in the standard instruction set template corresponding to the target business;

[0292] If the target instruction set includes all key parameters included in the standard instruction set template corresponding to the target service, determining whether the value of the target parameter in the target instruction set matches the target number, the target parameter being a key parameter characterizing the target number;

[0293] If the value of the target parameter in the target instruction set matches the target number, it is determined that the verification of the target instruction set has passed.

[0294] In some embodiments of the present application, the execution module 540 is further configured to:

[0295] In the case that the target instruction set does not include all the key parameters included in the standard instruction set template corresponding to the target business, the target instruction set corresponding to the target business is regenerated until the regenerated target instruction set includes all the key parameters included in the standard instruction set template corresponding to the target business.

[0296] In some embodiments of the present application, the execution module 540 is further configured to:

[0297] When the value of the target parameter in the target instruction set does not match the target number, the value of the target parameter in the target instruction set is updated to the target number.

[0298] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0299] Corresponding to the above method embodiment, the present application embodiment further provides an electronic device, including:

[0300] Memory for storing computer programs;

[0301] The processor is used to implement the steps of the above-mentioned business processing method when executing the computer program.

[0302] like Figure 6 , which is a schematic diagram of the composition structure of an electronic device, the electronic device may include: a processor 10, a memory 11, a communication interface 12 and a communication bus 13. The processor 10, the memory 11 and the communication interface 12 all communicate with each other through the communication bus 13.

[0303] In the embodiment of the present application, the processor 10 may be a central processing unit (CPU), an application specific integrated circuit, a digital signal processor, a field programmable gate array or other programmable logic devices, etc.

[0304] The processor 10 may call a program stored in the memory 11. Specifically, the processor 10 may execute operations in an embodiment of the service processing method.

[0305] The memory 11 is used to store one or more programs, which may include program codes, and the program codes include computer operation instructions. In the embodiment of the present application, the memory 11 at least stores programs for implementing the following functions:

[0306] Receive processing requests for target businesses;

[0307] Determine the target number corresponding to the target service based on the subscription data information on the user data management network element;

[0308] Based on the target number, generate a target instruction set corresponding to the target service;

[0309] Executes the target instruction set in response to the processing request.

[0310] In a possible implementation, the memory 11 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application required for at least one function, etc.; the data storage area may store data created during use.

[0311] In addition, the memory 11 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device or other volatile solid-state storage device.

[0312] The communication interface 12 may be an interface of a communication module, and is used to connect to other devices or systems.

[0313] Of course, it should be noted that Figure 6 The structure shown does not constitute a limitation on the electronic device in the embodiment of the present application. In actual applications, the electronic device may include Figure 6 More or fewer components than shown, or combinations of certain components.

[0314] Corresponding to the above method embodiment, the embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above business processing method are implemented.

[0315] In addition, it should be noted that: the embodiment of the present application also provides a computer program product or a computer program, which may include computer instructions, and the computer instructions may be stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor may execute the computer instructions so that the computer device executes the description of the business processing method in the corresponding embodiment above, so it will not be repeated here. In addition, the description of the beneficial effects of using the same method will not be repeated. For technical details not disclosed in the computer program product or computer program embodiment involved in this application, please refer to the description of the method embodiment of this application.

[0316] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0317] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0318] Through the description of the above implementation methods, those skilled in the art can also clearly understand that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0319] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein can be directly implemented using hardware, a software module executed by a processor, or a combination of the two. The software module can be placed in a random access memory (RAM), a memory, a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a register, a hard disk, a removable disk, a compact disc read-only memory (CD-ROM), or any other form of storage medium known in the art, including several instructions to execute the methods described in the various embodiments of the present application.

[0320] The embodiments of the present application are described above in conjunction with the accompanying drawings, and the description of the above embodiments is only used to help understand the technical solution and its core idea of ​​the present application. It should be pointed out that the present application is not limited to the above-mentioned specific implementation methods, which are merely illustrative and not restrictive. For ordinary technicians in this field, many forms of implementation methods can be made without departing from the scope of protection of the purpose of the present application and the claims, and the present application can also be improved and modified in a number of ways, and these implementation methods, improvements and modifications are all within the scope of protection of the present application.

Claims

1. A business processing method, characterized in that: include: Receive processing requests for target businesses; Determine the target number corresponding to the target service based on the subscription data information on the user data management network element; Based on the target number, generating a target instruction set corresponding to the target service; The target instruction set is executed in response to the processing request.

2. The method according to claim 1, characterized in that In the case where the target service includes a newly installed service, the target number includes a mobile directory number MDN and an international mobile subscriber identity IMSI to be newly installed; and determining the target number corresponding to the target service based on the subscription data information on the user data management network element includes: Providing a first IMSI and a first MDN for the target service; Determine, according to the subscription data information on the user data management network element, whether the first IMSI and the first MDN have account opening data; If the first IMSI does not have account opening data, determining the first IMSI as the IMSI to be newly installed corresponding to the target service; If the first MDN does not have account opening data, the first MDN is determined as the MDN to be newly installed corresponding to the target service.

3. The method according to claim 2, characterized in that In the case where the first IMSI has account opening data, the method further includes: re-providing the first IMSI for the target service; Determine whether the re-provided first IMSI has account opening data according to the subscription data information on the user data management network element; If the newly provided first IMSI does not have account opening data, determining the newly provided first IMSI as the IMSI to be newly installed corresponding to the target service; If the newly provided first IMSI has account opening data, the step of re-providing the first IMSI for the target service is repeated until the newly provided first IMSI has no account opening data.

4. The method according to claim 2, characterized in that: In the case where the first MDN has account opening data, the method further includes: Re-providing the first MDN for the target service; Determine whether the re-provided first MDN has account opening data according to the subscription data information on the user data management network element; If the newly provided first MDN does not have account opening data, determining the newly provided first MDN as the MDN to be newly installed corresponding to the target service; If the re-provided first MDN has account opening data, the step of re-providing the first MDN for the target service is repeated until the re-provided first MDN does not have account opening data.

5. The method according to claim 1, characterized in that In the case where the target service includes a card replacement service, the target number includes the MDN, the old IMSI and the new IMSI of the card to be replaced; The determining the target number corresponding to the target service based on the subscription data information on the user data management network element includes: Provide the target service with a second MDN, a second old IMSI and a second new IMSI of the card to be replaced; Determine, according to the subscription data information on the user data management network element, whether the second new IMSI and the second MDN have account opening data; If the second new IMSI does not have account opening data, determining the second new IMSI as the new IMSI of the card to be replaced corresponding to the target service; If the second MDN has account opening data, determine the second MDN as the MDN of the card to be replaced corresponding to the target service, and determine whether the IMSI included in the account opening data of the second MDN is consistent with the second old IMSI; If the IMSI included in the account opening data of the second MDN is consistent with the second old IMSI, the second old IMSI is determined as the old IMSI of the card to be replaced corresponding to the target service.

6. The method according to claim 5, characterized in that In the case where the second new IMSI has account opening data, the method further includes: Re-provisioning a second new IMSI for the target service; Determine whether the second new IMSI provided again has account opening data according to the subscription data information on the user data management network element; If the second new IMSI provided again does not have account opening data, the second new IMSI provided again is determined as the new IMSI of the card to be replaced corresponding to the target service; If the second new IMSI that is newly provided has account opening data, the step of re-providing the second new IMSI for the target service is repeated until the second new IMSI that is newly provided has no account opening data.

7. The method according to claim 5, characterized in that In a case where the IMSI included in the account opening data of the second MDN is inconsistent with the second old IMSI, the method further includes: Correcting the second old IMSI to the IMSI included in the account opening data of the second MDN; The corrected second old IMSI is determined as the old IMSI of the card to be replaced corresponding to the target service.

8. The method according to claim 1, characterized in that In the case where the target service includes a disassembly service, the target number includes the MDN and IMSI of the device to be disassembled; The determining the target number corresponding to the target service based on the subscription data information on the user data management network element includes: Providing a third MDN and a third IMSI for the target service; Determining whether the third MDN has account opening data according to the subscription data information on the user data management network element; If the third MDN has account opening data, determine the third MDN as the MDN to be disassembled corresponding to the target service, and determine whether the IMSI included in the account opening data of the third MDN is consistent with the third IMSI; If the IMSI included in the account opening data of the third MDN is consistent with the third IMSI, the third IMSI is determined as the IMSI of the to-be-disassembled device corresponding to the target service.

9. The method according to claim 8, characterized in that In a case where the IMSI included in the account opening data of the third MDN is inconsistent with the third IMSI, the method further includes: Correcting the third IMSI to the IMSI included in the account opening data of the third MDN; The corrected third IMSI is determined as the IMSI of the to-be-disassembled device corresponding to the target service.

10. The method according to any one of claims 1 to 9, characterized in that The executing the target instruction set comprises: Based on the standard instruction set template corresponding to the target business, performing key parameter verification on the target instruction set; If the verification passes, the target instruction set is executed.

11. The method according to claim 10, characterized in that The performing key parameter verification on the target instruction set based on the standard instruction set template corresponding to the target service includes: Determining whether the target instruction set includes all key parameters included in the standard instruction set template corresponding to the target service; If the target instruction set includes all key parameters included in the standard instruction set template corresponding to the target service, determining whether the value of the target parameter in the target instruction set matches the target number, the target parameter being a key parameter characterizing the target number; If the value of the target parameter in the target instruction set matches the target number, it is determined that the verification of the target instruction set passes.

12. The method according to claim 11, characterized in that In the case that the target instruction set does not include all key parameters included in the standard instruction set template corresponding to the target service, the method further includes: Regenerate a target instruction set corresponding to the target business until the regenerated target instruction set includes all key parameters included in the standard instruction set template corresponding to the target business.

13. The method according to claim 11, characterized in that In the case where the value of the target parameter in the target instruction set does not match the target number, the method further comprises: The value of the target parameter in the target instruction set is updated to the target number.

14. A service processing device, characterized in that: include: A receiving module, used for receiving a processing request for a target business; A determination module, configured to determine a target number corresponding to the target service based on the subscription data information on the user data management network element; A generating module, configured to generate a target instruction set corresponding to the target service based on the target number; An execution module is used to execute the target instruction set to respond to the processing request.

15. An electronic device, characterized in that: include: Memory for storing computer programs; A processor, configured to implement the steps of the business processing method according to any one of claims 1 to 13 when executing the computer program.

16. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the business processing method according to any one of claims 1 to 13 are implemented.

Images