Business processing methods, devices, electronic equipment and storage media

Abstract

This application discloses a service processing method, apparatus, electronic device, and storage medium. The service processing method includes: receiving a processing request for a target service; determining a target number corresponding to the target service based on subscription data information on a 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 processing request. Applying the technical solution provided in this application helps improve the efficiency and accuracy of service processing.

Description

Technical Field

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

[0002] With the rapid development of mobile communication technologies, the 5th Generation (5G) network, as a new generation of communication technology, provides users with higher data transmission rates and lower latency. During the deployment and operation of the 5G network, user service acceptance has become a key link. User service acceptance includes, but is not limited to, service processes such as new installation, SIM card replacement, and disconnection, and the efficiency and accuracy of these processes directly affect the user experience and the service level of the operator.

[0003] Currently, when the acceptance system receives service handling requests such as new installation, SIM card replacement, and disconnection, it mostly processes the corresponding services based on the number information recorded by itself. However, the number information recorded by the acceptance system itself may be inaccurate, resulting in lower service processing efficiency and accuracy. Summary of the Invention

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

[0005] To solve the above technical problems, this application provides the following technical solutions:

[0006] In a first aspect, a service processing method is provided, including:

[0007] Receiving a handling request for a target service;

[0008] Based on the subscribed data information on the user data management network element, determining the target number corresponding to the target service;

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

[0010] Executing the target instruction set to respond to the handling request.

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

[0012] A receiving module, configured to receive a handling request for a target service;

[0013] A determining module, configured to determine the target number corresponding to the target service based on the subscribed 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 in response to the processing request.

[0016] Thirdly, an electronic device is provided, comprising:

[0017] Memory, used to store computer programs;

[0018] A processor for implementing the steps of the business processing method as described in the first aspect when executing the computer program.

[0019] Fourthly, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the steps of the business processing method as described in the first aspect.

[0020] Fifthly, a computer program product is provided, the computer program product including computer instructions stored in a computer-readable storage medium and adapted to be read and executed by a processor to cause a computer device having the processor to perform the steps of the business processing method as described in the first aspect.

[0021] By applying the technical solution provided in the embodiments of this application, upon receiving a processing request for a target service, the target number corresponding to the target service is determined based on the contractual data information on the user data management network element. Based on the target number, a target instruction set corresponding to the target service is generated and 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 contractual data information on it is more accurate. Therefore, the target number corresponding to the target service determined based on the contractual data information on the user data management network element is also more accurate, and consequently, the target instruction set generated based on the target number is more effective, helping to improve business processing efficiency and accuracy.

[0022] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0023] To more clearly illustrate the technical solutions in the embodiments or related technologies of this application, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1 This is a flowchart illustrating the implementation of a business processing method in one embodiment of this application.

[0025] Figure 2 This is a schematic diagram of the new installation service processing procedure in the embodiments of this application;

[0026] Figure 3 This is a schematic diagram of the card replacement service process in the embodiments of this application;

[0027] Figure 4 This is a schematic diagram of the disassembly process in an embodiment of this application;

[0028] Figure 5 This is a schematic diagram of the structure of a service processing device according to an embodiment of this application;

[0029] Figure 6 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0030] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0031] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: 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 scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0032] The core of this application is to provide a service processing method that can be applied to user service acceptance scenarios in mobile communication networks, such as new installations, SIM card replacements, and handset removals. This method can be executed by the acceptance system.

[0033] In related technologies, for the opening of Voice over Long-Term Evolution (VoLTE) user accounts in 4th Generation (4G) networks, the decision on whether the current user meets the opening conditions can be made by comprehensively obtaining the VoLTE account opening tag on the Home Subscriber Server (HSS), the status of service operation support data, and the terminal adaptation status, and then executing the VoLTE account opening instruction for users who meet the opening conditions.

[0034] However, this method only applies to 4G network VoLTE user account opening and relies on the VoLTE account opening label on the HSS to determine whether the number meets the account opening requirements. That is, it uses the Mobile Directory Number (MDN) to determine the user's VoLTE account opening label, without checking the usage and consistency of the International Mobile Subscriber Identity (IMSI). Due to factors such as abnormal execution of service orders and abnormal resource record information, mismatches between user network data and service system data resources, as well as abnormal service instructions, have persisted for a long time. Specifically, the IMSI recorded by the service system is incorrect, or the MDN and IMSI recorded on the network element side do not match the information recorded by the service system. For example, during new installation, if the IMSI provided by the service system is actually already occupied in the network element, the new installation instruction sent to the network element will fail. During SIM card replacement and device removal, if the IMSI provided by the service system for the SIM card to be replaced or the device to be removed is not occupied in the network element (i.e., the IMSI is actually an invalid number on the network element side), the SIM card replacement or device removal instruction sent to the network element will fail.

[0035] In view of the problems existing in related technologies, this application provides a business processing method. Upon receiving a processing request for a target business, the method determines the target number corresponding to the target business based on the contract data information on the user data management network element. Based on the target number, a target instruction set corresponding to the target business is generated and executed to respond to the processing request. The user data management network element, as a unified data management functional network element, can perform centralized data management. The contract data information on it is more accurate, so the target number corresponding to the target business determined based on the contract data information on the user data management network element is also more accurate. Consequently, the target instruction set generated based on the target number is more effective, helping to improve business processing efficiency and accuracy.

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

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

[0038] In this embodiment, the processing system can receive processing requests for a target service, which can be initiated by the user based on actual needs. The target service may include at least one of the following: new installation service, SIM card replacement service, and device removal service.

[0039] S120: Based on the contracted data information on the user data management network element, determine the target number corresponding to the target service.

[0040] When the target service includes new service installations, the target number includes the Mobile Catalog Number (MDN) and the International Mobile Subscriber Identity (IMSI) to be installed.

[0041] When the target business includes card replacement, the target number includes the MDN, old IMSI, and new IMSI of the card to be replaced;

[0042] In cases where the target business includes disconnection services, the target number includes the MDN and IMSI of the number to be disconnected.

[0043] In this embodiment of the application, after receiving a processing request for a target service, the acceptance system can provide the MDN and IMSI corresponding to the target service, and then obtain the subscription data information on the User Data Management (UDM) network element in real time through interface calls, so as to obtain the usage status of the provided MDN and IMSI on the User Data Management network element.

[0044] Based on the contracted 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 contracted data information on it is more accurate. Therefore, the target number corresponding to the target service determined based on the contracted data information on the user data management network element is also more accurate.

[0045] S130: Based on the target number, generate the target instruction set corresponding to the target service.

[0046] After determining the target number corresponding to the target service based on the contracted data information on the user data management network element, a target instruction set corresponding to the target service can be generated based on the target number. Different types of target services correspond to different target instruction sets. Optionally, the parameters required to process the target service can be determined first, a target instruction set can be generated based on the parameters required by the target service, and the values ​​of the parameters representing the target number contained in the target instruction set can be filled with the target number.

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

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

[0049] Applying the method provided in this application, upon receiving a processing request for a target service, the method determines the target number corresponding to the target service based on the contract data information on the user data management network element. Based on the target number, a target instruction set corresponding to the target service is generated and 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. Therefore, 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 consequently, the target instruction set generated based on the target number is more effective, helping to improve the efficiency and accuracy of service processing.

[0050] In some embodiments of this application, when the target service includes a new subscription service, the target number corresponding to the target service is determined based on the subscription data information on the user data management network element, including:

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

[0052] Based on the contract data information on the user data management network element, determine whether the first IMSI and the first MDN have account opening data.

[0053] If no account opening data exists for the first IMSI, then the first IMSI will be identified as the IMSI to be installed for the target service.

[0054] If the first MDN does not have account opening data, then the first MDN will be identified as the MDN to be newly installed for the target business.

[0055] For ease of description, the above steps will be combined for explanation.

[0056] In this embodiment, after receiving a processing request for a target service, if the target service includes a new installation service, the processing system can provide a first IMSI and a first MDN for the target service. Optionally, the processing system can select an unused first IMSI and first MDN based on its own recorded number information.

[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 business, after providing the first IMSI and the first MDN, the acceptance system can query the contract data information on the user data management network element to determine whether the first IMSI and the first MDN have account opening data.

[0058] If no account opening data exists for the first IMSI, it is considered that the first IMSI is not occupied and can be identified as the IMSI to be newly installed for the target service.

[0059] If the first IMSI has account opening data, it can be considered that the first IMSI has been occupied and cannot be used as the IMSI to be newly installed for the target service. Optionally, if the first IMSI has account opening data, the first IMSI can be re-provided for the target service; then, based on the subscription 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; 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 contain account opening data, it is considered that the first MDN is not occupied and can be identified as the MDN to be newly installed for the target business.

[0061] If the first MDN has account opening data, it can be considered that the first MDN has been occupied and cannot be used as the new MDN to be 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 subscription 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 identified as the new MDN to be 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] For new installation services, when it is found that the IMSI provided by the acceptance system has account opening data on the user data management network element, the acceptance system provides a new IMSI number, and then re-executes the data query for the new IMSI on the user data management network element, repeating the above judgment logic steps until no account opening data is found for that IMSI on the user data management network element; when it is found that the MDN provided by the acceptance system has account opening data on the user data management network element, the acceptance system provides a new MDN number, and then re-executes the data query for the new MDN on the user data management network element, repeating the above judgment logic steps until no account opening data is found for that MDN on the user data management network element; finally, the final IMSI and MDN to be installed are output.

[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. After identifying the IMSI to be newly installed corresponding to the target service, then determine whether the first MDN has account opening data on the user data management network element to further identify the MDN to be newly installed corresponding to the target service. Alternatively, first determine whether the first MDN has account opening data on the user data management network element. After identifying the MDN to be newly installed corresponding to the target service, then determine whether the first IMSI has account opening data on the user data management network element to further identify 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 new installation service have account opening data on the user data management network element. If account opening data exists in the provided IMSI or MDN, the system re-provides the IMSI or MDN, which can accurately determine the IMSI and MDN to be installed for the target service.

[0065] In some embodiments of this application, when the target service includes SIM card replacement service, the target number corresponding to the target service is determined based on the subscription data information on the user data management network element, including:

[0066] Provide the target business with a second MDN, a second old IMSI, and a second new IMSI for the card to be replaced;

[0067] Based on the contract data information on the user data management network element, determine whether there is account opening data for the second new IMSI and the second MDN respectively;

[0068] If no account opening data exists for the second new IMSI, then the second new IMSI will be identified as the new IMSI of the card to be replaced corresponding to the target business.

[0069] If the second MDN contains account opening data, then the second MDN is identified as the MDN of the card to be replaced corresponding to the target business, and it is determined whether the IMSI contained in the account opening data of the second MDN is consistent with the second old IMSI.

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

[0071] For ease of description, the above steps will be combined for explanation.

[0072] In this embodiment of the application, after receiving a processing request for a target service, if the target service includes card replacement, the processing system can provide the second MDN, second old IMSI, and second new IMSI of the card to be replaced. Optionally, the processing system can provide the second MDN and second old IMSI of the card to be replaced based on its own recorded number information, and select an unused second new IMSI.

[0073] It is understandable that the number information recorded by the acceptance system itself may deviate from the contracted 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, after providing the second MDN, second old IMSI and second new IMSI of the card to be replaced, the acceptance system can query the contracted data information on the user data management network element to determine the accuracy of the second MDN, second old IMSI and second new IMSI respectively.

[0074] Based on the contract 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 no account opening data exists for the second new IMSI, it is considered that the second new IMSI is not occupied and can be identified as the new IMSI of the card to be replaced corresponding to the target business.

[0076] If account opening data exists for the second new IMSI, it can be considered that the second new IMSI has been used and cannot be used as the new IMSI for the SIM card to be replaced for the target service. Optionally, if account opening data exists for the second new IMSI, a new second new IMSI can be provided for the target service. Then, based on the subscription data information on the user data management network element, it is determined whether the newly provided second new IMSI has account opening data. If the newly provided second new IMSI does not have account opening data, it is determined as the new IMSI for the SIM card to be replaced for the target service. If the newly provided second new IMSI has account opening data, the step of providing a new second new IMSI for the target service is repeated until the newly provided second new IMSI does not have account opening data.

[0077] If the second MDN does not contain account opening data on the user data management network element, it is considered that the second MDN is not in use, and this second MDN cannot be the MDN of the card 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 error message and prohibit the card replacement operation.

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

[0079] If account opening data exists in the user data management network element of the second MDN, it can be further determined whether the IMSI contained in the account opening data of the second MDN is consistent with the second old IMSI.

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

[0081] If the IMSI contained in the account opening data of the second MDN on the user data management network element is inconsistent with the second old IMSI, then the second old IMSI can be considered to be incorrect. The second old IMSI can be corrected to the IMSI contained 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] For SIM card replacement services, the acceptance system provides the MDN, old IMSI, and new IMSI. When account opening data for the new IMSI is found to exist on the user data management network element, the acceptance system provides a new IMSI, re-executes the data query for the new IMSI on the user data management network element, and repeats the above judgment logic steps until no account opening data is found for the new IMSI on the user data management network element. When account opening data for the MDN is found to exist on the user data management network element, the IMSI on the MDN is compared with the old IMSI. If they do not match, the old IMSI value is corrected to the IMSI retrieved based on the MDN. The final MDN, old IMSI, and new IMSI of the SIM card to be replaced are then output.

[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. After determining the new IMSI of the SIM card to be replaced corresponding to the target service, then determine whether the second MDN has account opening data on the user data management network element. If account opening data exists on the second MDN, the old IMSI of the SIM card to be replaced corresponding to the target service can be further determined based on the IMSI contained in the account opening data of the second MDN. Alternatively, it can be that the existence of account opening data on the second MDN is determined first. If no account opening data exists on the second MDN, the SIM card replacement process is stopped. If account opening data exists on the second MDN, the old IMSI of the SIM card to be replaced corresponding to the target service is determined based on the IMSI contained in the account opening data of the second MDN. Then, the existence of the second new IMSI on the user data management network element is determined to further determine the new IMSI of the SIM card to be replaced corresponding to the target service.

[0084] The acceptance system determines the validity of the MDN, old IMSI, and new IMSI provided for the card replacement service based on the contracted data information on the user data management network element, and makes corresponding corrections if there are errors, thereby accurately determining the MDN, old IMSI, and new IMSI of the card to be replaced corresponding to the target service.

[0085] In some embodiments of this application, when the target service includes disconnection services, the target number corresponding to the target service is determined based on the subscription data information on the user data management network element, including:

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

[0087] Based on the contract signing data information on the user data management network element, determine whether the third MDN has account opening data;

[0088] If account opening data exists in the third MDN, then the third MDN is identified as the MDN to be disconnected corresponding to the target business, and it is determined whether the IMSI contained in the account opening data of the third MDN is consistent with the third IMSI.

[0089] If the IMSI contained in the account opening data of the third MDN is consistent with the third IMSI, then the third IMSI will be identified as the IMSI to be disconnected for the target service.

[0090] For ease of description, the above steps will be combined for explanation.

[0091] In this embodiment, after receiving a processing request for a target service, if the target service includes disconnection / removal services, the processing system can provide a third MDN and a third IMSI for the target service. Optionally, the processing system can provide the third MDN and third IMSI to be disconnected based on the number information it has recorded.

[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, after providing the third MDN and the third IMSI, the acceptance system can query the contract data information on the user data management network element to determine the validity of the third MDN and the third IMSI.

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

[0094] If no account opening data exists for the third MDN on the user data management network element, it is considered that the third MDN is not in use, and this third MDN cannot be the MDN to be disconnected. The third MDN provided by the processing system is invalid, and disconnection services cannot be carried out. In this case, the processing system can output an error message and prohibit the disconnection operation.

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

[0096] If account opening data exists on the user data management network element of the third MDN, it can be further determined whether the IMSI contained in the account opening data of the third MDN is consistent with the third IMSI.

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

[0098] If the IMSI contained 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. The third IMSI can be corrected to the IMSI contained in the account opening data of the third MDN, and the corrected third IMSI can be determined as the IMSI to be disconnected corresponding to the target service.

[0099] For disconnection services, the processing system provides the MDN and IMSI. It retrieves the data of this MDN on the user data management network element, compares the IMSI obtained from the MDN with the IMSI provided by the processing system, and if they are inconsistent, corrects the IMSI value provided by the processing system to the IMSI obtained from the MDN, and outputs the final IMSI and MDN for the disconnection service.

[0100] The acceptance system determines the validity of the IMSI and MDN provided for the disconnection service based on the contracted data information on the user data management network element, and makes corresponding corrections if there are errors. It can accurately determine the IMSI and MDN of the target service to be disconnected.

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

[0102] Based on the standard instruction set template corresponding to the target business, perform key parameter verification on the target instruction set;

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

[0104] For ease of description, the above steps will be combined for explanation.

[0105] In this embodiment, after accurately determining the target number corresponding to the target service based on the subscription data information on the user data management network element, a target instruction set corresponding to the target service can be generated based on the target number. Before executing the target instruction set, the completeness of its key parameters can be verified. This verification can be performed based on a standard instruction set template corresponding to the target service.

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

[0107] In some embodiments of this application, it can be first determined whether the target instruction set contains all the key parameters contained in the standard instruction set template corresponding to the target service; if the target instruction set contains all the key parameters contained in the standard instruction set template corresponding to the target service, it is determined whether the value of the target parameter in the target instruction set matches the target number, where the target parameter is a key parameter representing 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 this embodiment, the standard instruction set template corresponding to the target service can be determined first. Different services correspond to different standard instruction set templates. The standard instruction set template contains at least one key parameter.

[0109] After generating the target instruction set, the key parameters contained in the target instruction set can be compared with the key parameters contained in the standard instruction set template corresponding to the target service.

[0110] If the target instruction set contains all the key parameters contained in the standard instruction set template corresponding to the target service, then the key parameters contained in the target instruction set can be considered complete.

[0111] If the target instruction set does not contain all the key parameters contained in the standard instruction set template corresponding to the target service, it is considered that the key parameters contained in the target instruction set are incomplete. The target instruction set corresponding to the target service can be regenerated until the regenerated target instruction set contains all the key parameters contained in the standard instruction set template corresponding to the target service.

[0112] For example, for new installation services, there are four scenarios, each with its own standard instruction set template and key parameters. (1) UDM network element adds IMSI authentication scenario: carry out consistency verification and correction of UDM serial number (UDMSN), IMSI, authentication key value (Key Identifier VALUE, KIVALUE), K4 serial number (K4SNO), algorithm (ALG) (used to indicate the authentication algorithm type), operational cipher key (OPC) value (OPCVALUE), access and mobility management function (AMF) serial number (AMF Serial Number, AMFSNO) parameters; (2) 5G number adds account opening scenario: carry out UDMSN, IMSI, MDN, NGSUSERTPLID (used to identify the account opening template of 5G users), NGSUSERTPLID (used to identify the roaming restriction template of 5G users), EPSUSERTPLID (used to identify the Evolved Packet System (EPSS)). System (EPS) user template), SHRDUSERTPLID (used to identify shared data template), INSTALLTYPE (used to represent 5G account type) parameters consistency verification and correction; (3) 5G VoLTE new account opening scenario: carry out UDMSN, IMSI, MDN, IP Multimedia Private Identity (IMPI), IP Multimedia Public Identity (IMPU) list (IMPULIST), SIFCLIST (used to represent the initial filtering rule list of Serving-Call Session Control Function (S-CSCF)), VOLTETAG (used to represent VoLTE user identifier) ​​parameters consistency verification and correction; (4) VoLTE Grouped User Service Switching (GUSS) new account opening scenario: carry out IMPI, GSID (used to represent Generic Authentication Architecture (GAA) service type identifier), LIFETIME parameters consistency verification and correction;

[0113] For the card replacement service, there are three scenarios, and each scenario has a corresponding standard instruction set template and corresponding key parameters. (1) UDM network element adds IMSI authentication scenario: carry out consistency verification and correction of parameters UDMSN, IMSI, KIVALUE, K4SNO, ALG, OPCVALUE, AMFSNO; (2) 5G user old IMSI replaces new IMSI scenario: carry out consistency verification and correction of parameters MDN, IMSI, NEWIMSI (used to represent new IMSI), IMPI, NEWIMPI (used to represent new IMPI), IMPU; (3) Deletion of old IMSI authentication scenario: verify and correct the consistency of IMSI parameters.

[0114] For the dismantling service, there are two scenarios, and each scenario has a corresponding standard instruction set template and corresponding key parameters. (1) 5G VoLTE account cancellation scenario: conduct consistency verification and correction of MDN, IMSI, IMPPI, and IMPULIST parameters; (2) 5G account cancellation: conduct consistency verification and correction of key parameters of MDN and IMSI.

[0115] Further steps can be taken to determine whether the value of the target parameter in the target instruction set matches the target number. The target parameter is a key parameter representing the target number. If the value of the target parameter in the target instruction set matches the target number, the verification of the target instruction set is considered successful. 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, and the verification is considered successful.

[0116] Based on the standard instruction set template corresponding to the target business, the key parameters of the target instruction set are verified. Only after the verification is passed will the target instruction set be executed. 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 this application have been described above. For ease of understanding, specific examples will be used to illustrate the solutions below.

[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 Service

[0120] The new installation service involves four scenarios and steps in the UDM network element: adding IMSI authentication to the UDM network element, adding new 5G numbers, adding new 5G VoLTE numbers, and adding new VoLTE GUSS numbers. Before the new installation service is carried out, the consistency comparison of number data between scenario 1 and scenario 2 is carried out.

[0121] Taking the IMSI 46011A and MDN 189A that will soon be added to the acceptance system as an example, the details are as follows:

[0122] Scenario 1: Adding IMSI authentication to UDM network elements

[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 can be selected to fill in. The interface input parameter value is {'46011A', ''}, which means that the configuration of IMSI on the UDM network element is obtained through the input parameter with IMSI of 46011A. The output result is RESULT_IMSI.

[0124] Result Acquisition: Obtain relevant parameters from the RESULT information returned by the interface, and extract the value corresponding to {RESULTCODE} in RESULT, which represents the result code.

[0125] Data preprocessing: The value of the RESULTCODE result is used to determine whether the newly added IMSI is already in use. The operation method is as follows:

[0126] If the RESULTCODE value is 0, it indicates that the query was successful, meaning that the current IMSI is already in use and account opening data exists. All new scenarios are terminated, and the processing system will reallocate a new IMSI, such as 46011B, for use by number 189A. The consistency comparison process of scenario 1 will be repeated until the RESULTCODE value is not 0. If the RESULTCODE value is not 0, it indicates that the query failed, meaning that the current IMSI is not in use and there is no account opening data. The data consistency comparison of scenario 1 is successful.

[0127] Scenario 2: New 5G Number Account Openings

[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 MDN 189A. The output result is RESULT_MDN.

[0129] Result Acquisition: Obtain relevant parameters from the RESULT information returned by the interface, and extract the value corresponding to {RESULTCODE} in RESULT, which represents the result code.

[0130] Data preprocessing: The value of the RESULTCODE result is used to determine whether the newly added MDN is already in use. The operation method is as follows:

[0131] If the RESULTCODE value is 0, it indicates that the query was successful, meaning that the current MDN is already in use and account opening data exists. In this case, the MDN_USED value is set to 0, all new scenarios are terminated, and the processing 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 indicates that the query failed, meaning that the current MDN is not in use and account opening data does not exist. In this case, the data consistency comparison of scenario 2 is successful.

[0132] Since the operations of adding a new 5G VoLTE account in Scenario 3 and adding a new VoLTE GUSS in Scenario 4 are contingent upon the successful execution of Scenario 1 and Scenario 2 (i.e., account opening has been completed in Scenario 1 and Scenario 2), if no account opening data exists in Scenario 1 and Scenario 2, it means that no account opening data can exist in Scenario 3 and Scenario 4. Therefore, when no account opening data exists in Scenario 1 and Scenario 2, the processing system generates the corresponding new installation instruction sets for Scenario 1, Scenario 2, Scenario 3, and Scenario 4.

[0133] Example 2: Card replacement service

[0134] The SIM card replacement service involves three steps in the UDM network element: authentication and number allocation with the new IMSI, replacement of the old IMSI with the new IMSI for 5G users, and deletion of the old IMSI authentication. Before performing the SIM card replacement, the main task is to conduct a consistency comparison of the data in the two scenarios: authentication and number allocation with the new IMSI and replacement of the old IMSI with the new IMSI for 5G users.

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

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

[0137] The specific steps are the same as in scenario 1 for new installation business, and will not be repeated here.

[0138] Scenario 2: 5G users replacing their old IMSI with the new IMSI

[0139] Information Acquisition: Account opening information is retrieved in real time from UDM network elements based on the UDM information query interface. The interface input parameters include the key: {IMSI, MDN}, where IMSI and MDN can be selected. If the interface input parameter value is {'46011A', ''}, it means that the configuration of IMSI on the UDM network element is retrieved through the input parameter of IMSI 46011A, and the output result is RESULT_IMSI; if the interface input parameter value is {'', '189A'}, it means that the configuration of MDN on the UDM network element is retrieved through the input parameter of MDN 189A, and the output result is RESULT_MDN.

[0140] Result Acquisition: The UDM account opening information interface was called simultaneously with MDN input parameter 189A and new IMSI input parameter 46011B. The returned results RESULT_MDN and RESULT_IMSI_NEW were obtained respectively. The values ​​corresponding to {RESULTCODE, IMSI} in RESULT_MDN were extracted and re-marked as {RESULTCODE_MDN_OLD, IMSI_MDN_OLD}, representing: result code and IMSI. The values ​​corresponding to {RESULTCODE} in RESULT_IMSI_NEW were extracted and re-marked as {RESULTCODE_IMSI_NEW}.

[0141] Data preprocessing:

[0142] Step 1: When the RESULTCODE_MDN_OLD value is not 0, it indicates that the number of the card to be replaced does not exist in the UDM network element, that is, the provided MDN number is invalid, and the card replacement service cannot be carried out. An error message is displayed 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 equals 46011A, it means that the IMSI corresponding to MDN 189A matches the old IMSI, that is, the data comparison of 46011A is consistent, 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: If the RESULTCODE_IMSI_NEW value 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 the consistency comparison in Scenario 2 is passed; if the RESULTCODE_IMSI_NEW value 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 system needs to reassign a new IMSI number, such as 46011D, and repeat the check of whether the IMSI number is occupied in Step 2 until the RESULTCODE_IMSI_NEW value is not 0 and the consistency comparison in Scenario 2 is passed.

[0144] Once the consistency comparison between scenario 1 and scenario 2 passes, the acceptance system generates card replacement instruction sets corresponding to scenario 1, scenario 2, and scenario 3.

[0145] Example 3: Disassembly / Removal Services

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

[0147] Taking the device with MDN number 189A and corresponding IMSI number 46011A that is about to be dismantled 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, 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 can be selected. 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 input parameter 189A, and obtain the returned result RESULT_MDN. Extract the value corresponding to {RESULTCODE, IMSI} in RESULT_MDN and re-mark it as {RESULTCODE_MDN, IMSI_MDN}, which represents: result code and IMSI number.

[0151] Data preprocessing:

[0152] Step 1: When the RESULTCODE_MDN value is not 0, it means that there is no data for the number to be disconnected on the UDM network element, that is, the provided MDN number is an empty number and the disconnection service cannot be carried out. An abnormal prompt will be displayed on the acceptance system interface and the disconnection 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 UMD element, and a corresponding disconnection 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 and the IMSI number 46011A do not match on the core network UDM element. The IMSI number to be disconnected is changed from 46011A to the IMSI_MDN value in RESULT_MDN, and the 5G VoLTE account cancellation consistency comparison is performed.

[0154] The prerequisite for 5G VoLTE account opening is that a 5G user has already opened an account. Therefore, if it is confirmed that a 5G VoLTE account has been opened, there is no need to determine whether the 5G user has opened an account. When the consistency comparison of Scenario 1 passes, the processing system generates the disconnection instruction sets for Scenario 1 and Scenario 2.

[0155] 2) An example of conducting consistency verification of key parameters of the acceptance instruction set based on the standard instruction set template is as follows:

[0156] Based on the real-time data acquisition of UDM network elements, the data consistency comparison operation of the acceptance number is carried out. After obtaining the correct user MDN number and IMSI number of the business to be accepted, the acceptance system generates the input instruction of the business to be accepted according to the relevant business rules and calls the UDM network element acceptance interface to send the parameters. Therefore, before the acceptance instruction is sent, the completeness of the key parameters of the instruction set needs to be verified.

[0157] Example 1: New Installation Service

[0158] New service installations in the UDM network element involve four scenarios and steps: adding IMSI authentication to the UDM network element, adding new 5G numbers, adding new 5G VoLTE numbers, and adding new VoLTE GUSS numbers.

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

[0160] Scenario 1: Adding IMSI authentication to UDM network elements

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

[0162] Information Acquisition: The set of new installation instructions 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: If any of the parameters UDMSN_B, IMSI_B, KIVALUE_B, K4SNO_B, ALG_B, OPCVALUE_B, or AMFSNO_B in ADD_AUTH_B is empty (e.g., NULL or None), it indicates an error in the generation of the acceptance instruction set. The acceptance system will then regenerate the new installation instruction set ADD_AUTH_C and repeat the above judgment operation until all parameters are no longer NULL or None. Then proceed to 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, then change the value of the parameter IMSI_B in ADD_AUTH_NEW to 46011A and determine it as the final instruction set, and at the same time pass the completeness verification of the instruction set of scenario 1.

[0166] Scenario 2: New 5G Number Account Openings

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

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

[0169] Data preprocessing:

[0170] Step 1: If any of the parameters UDMSN_B, IMSI_B, MDN_B, NGSUSERTPLID_B, NGCODETPLID_B, EPSUSERTPLID_B, SHRDUSERTPLID_B, or INSTALLTYPE_B in ADD_5G_B is NULL or None, it indicates an error in the instruction set generation. The receiving system will then regenerate a new installation instruction set ADD_5G_C and repeat the above judgment operation until all the above parameters are not NULL or None. Then proceed to Step 2.

[0171] Step 2: Define the instruction set obtained in Step 1 as ADD_5G_NEW. If the value of 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 in the current scenario 2 has passed the verification, and its instruction set is determined to be ADD_5G_NEW. If the value of parameter IMSI_B in ADD_5G_NEW is not equal to 46011A, then change the value of parameter IMSI_B in ADD_5G_NEW to 46011A. If the value of parameter MDN_B in ADD_5G_NEW is not equal to 189A, then change the value of parameter MDN_B in ADD_5G_NEW to 189A, and determine it as the final instruction set, while passing the completeness verification of the instruction set in scenario 2.

[0172] Scenario 3: New 5G VoLTE Account Openings

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

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

[0175] Data preprocessing:

[0176] Step 1: If any of the parameters UDMSN_B, IMSI_B, MDN_B, IMPI_B, IMPULIST_B, SIFCLIST_B, or VOLTETAG_B in ADD_VOLTE_B is NULL or None, it indicates that the instruction set generation is abnormal. The receiving system will regenerate a new installation instruction set ADD_VOLTE_C and repeat the above judgment operation until all the above parameters are not NULL or None, and then proceed to Step 2.

[0177] Step 2: Redefine the instruction set obtained in Step 1 as ADD_VOLTE_NEW. If the value of 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 in the current scenario 2 has passed the verification, and its instruction set is determined to be ADD_5G_NEW. If the value of parameter IMSI_B in ADD_VOLTE_NEW is not equal to 46011A, then change the value of parameter IMSI_B in ADD_VOLTE_NEW to 46011A. If the value of parameter MDN_B in ADD_VOLTE_NEW is not equal to 189A, then change the value of parameter MDN_B in ADD_VOLTE_NEW to 189A, and determine it as the final instruction set. At the same time, the completeness verification of the instruction set in scenario 3 is passed.

[0178] Scenario 4: New VoLTE GUSS Account Openings

[0179] The standard instruction set template for opening a new 5G number account 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 any of the parameters IMPI_B, GSID_B, and LIFETIME_B in ADD_VOLTE_GUSS_B is NULL or None, it indicates that the instruction set generation is abnormal. The receiving system will regenerate a new installation instruction set ADD_VOLTE_GUSS_C and repeat the above judgment operation until all the above parameters are not NULL or None, and then proceed to 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 in 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 change the value of parameter IMPI_B in ADD_VOLTE_NEW to 46011A and determine it as the final instruction set. At the same time, the completeness verification of the instruction set in scenario 4 is passed.

[0184] Once the integrity checks of the instruction sets for scenarios 1 to 4 are all passed, the instruction sets ADD_AUTH_NEW, ADD_5G_NEW, ADD_VOLTE_NEW, and ADD_VOLTE_GUSS_NEW are executed sequentially to complete the new service application.

[0185] Example 2: Card replacement service

[0186] The SIM card replacement service involves three steps in the UDM network element: authentication and number allocation with the new IMSI, replacement of the old IMSI with the new IMSI for 5G users, and deletion of the old IMSI authentication. Before the SIM card replacement is performed, a consistency comparison of the SIM card number data to be replaced is conducted.

[0187] Taking the final determined user MDN number as 189A, the old IMSI number as 46011A, and the new IMSI as 46011B as an example.

[0188] Scenario 1: Adding IMSI authentication to UDM network elements

[0189] The new 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: If any of the parameters UDMSN_B, IMSI_B, KIVALUE_B, K4SNO_B, ALG_B, OPCVALUE_B, or AMFSNO_B in CHG_AUTH_B is NULL or None, it indicates an error in the generation of the acceptance instruction set. The acceptance system will then regenerate the card replacement instruction set CHG_AUTH_C and repeat the above judgment operation until all parameters are no longer NULL or None. Then proceed to 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, then change the value of the parameter IMSI_B in CHG_AUTH_NEW to 46011B and determine it as the final instruction set, and at the same time pass the completeness verification of the instruction set of scenario 1.

[0194] Scenario 2: 5G users replacing their old IMSI with the new IMSI

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

[0196] Information Acquisition: The set of new installation instructions 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 any of the parameters NEWIMSI_B, IMPI_B, NEWIMSI_B, or IMPI_B in CHG_5G_B is NULL or None, it indicates that the instruction set generation is abnormal. The acceptance system will regenerate the card replacement instruction set CHG_5G_C and repeat the above judgment operation until all the above parameters are not NULL or None. Then proceed to Step 2.

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

[0200] Scenario 3: Deleting the 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 by the acceptance system is DEL_AUTH_B = IMSI_B.

[0203] Data preprocessing:

[0204] Step 1: When the value of parameter IMSI_B in DEL_AUTH_B is not equal to 46011A, change the value of parameter IMSI_B in DEL_AUTH_B to 46011A and determine it as the final instruction set, while passing the instruction set completeness check of scenario 3.

[0205] Once the integrity checks of the instruction sets for scenarios 1 to 3 are all passed, the instruction sets ADD_AUTH_NEW, CHG_5G_NEW, and DEL_AUTH_B are executed sequentially to complete the card replacement service.

[0206] Example 3: Disassembly / Removal Services

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

[0208] Taking the final determined 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, IMPPI, IMPULIST}.

[0211] Information Acquisition: The set of disconnection instructions to be issued generated by the acceptance system is DEL_VOLTE_B = {MDN_B, IMSI_B, IMPPI_B, IMPULIST_B}.

[0212] Data preprocessing:

[0213] Step 1: When any of the parameters MDN_B, IMSI_B, IMPPI_B, and IMPULIST_B in DEL_VOLTE_B is NULL or None, it indicates that the instruction set generation is abnormal. The receiving system will regenerate the disassembly instruction set DEL_VOLTE_C and repeat the above judgment operation until all the above parameters are not NULL or None, and then proceed to 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 in 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, then change the value of parameter IMSI_B in DEL_VOLTE_NEW to 46011A. If the value of parameter MDN_B in DEL_VOLTE_NEW is not equal to 189A, then change the value of parameter MDN_B in DEL_VOLTE_NEW to 189A, and determine it as the final instruction set, while passing the completeness verification of the instruction set in scenario 1.

[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 set of disassembly instructions 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, then the value of parameter IMSI_B in DEL_5G_B is changed to 46011A. If the value of parameter MDN_B in DEL_5G_B is not equal to 189A, then the value of parameter MDN_B in DEL_5G_B is changed to 189A, and this is determined as the final instruction set. At the same time, the completeness check of the instruction set in Scenario 2 is passed.

[0220] Once the integrity checks of the instruction sets for scenarios 1 to 2 have all passed, the DEL_VOLTE_NEW and DEL_5G_B instruction sets will be executed sequentially to complete the disconnection service.

[0221] like Figure 2 As shown, the new installation service processing procedure is as follows:

[0222] Receive requests for new installation services;

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

[0224] Based on the IMSI, obtain UDM network data and determine whether the IMSI is occupied. If it is not occupied, identify the IMSI as the IMSI to be newly installed. If it is occupied, repeat the steps of providing an IMSI for new service installation to provide the IMSI again.

[0225] Based on the MDN, obtain UDM network data and determine whether the MDN is occupied. If it is not occupied, identify the MDN as the MDN to be newly installed. If it is occupied, repeat the steps of providing MDN for new service installation to provide MDN again.

[0226] Based on the finalized IMSI and MDN to be installed, generate instruction sets for scenarios 1 to 4.

[0227] The key parameters of the instruction sets for scenarios 1 to 4 are verified. If the verification fails, the instruction sets are corrected, regenerated, and the key parameter verification steps are repeated. If the verification passes, the instruction sets for scenarios 1 to 4 are issued sequentially.

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

[0229] like Figure 3 As shown, the card replacement service 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] Based on the new IMSI, obtain UDM network data and determine whether the new IMSI is occupied. If it is not occupied, then identify the new IMSI as the new IMSI for the card replacement. If it is occupied, repeat the step of providing a new IMSI for the card replacement service to provide a new IMSI again.

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

[0234] The key parameters of the instruction sets for scenarios 1 to 3 are verified. If the verification fails, the instruction sets are corrected, regenerated, and the key parameter verification steps are repeated. If the verification passes, the instruction sets for scenarios 1 to 3 are issued sequentially.

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

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

[0237] Receive requests for processing dismantling / removal services;

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

[0239] Based on the MDN, 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. 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 sets of scenario 1 to scenario 2 are generated according to the finally determined MDN and IMSI to be disconnected.

[0240] The key parameters of the instruction sets for scenarios 1 to 2 are verified. If the verification fails, the instruction sets are corrected, regenerated, and the key parameter verification steps are repeated. If the verification passes, the instruction sets for scenarios 1 to 2 are issued sequentially.

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

[0242] This application addresses the installation, SIM card replacement, and handset removal services for 5G users. It obtains relevant subscription data from the core network UDM side of the user seeking service, compares the consistency between the data from the corresponding service number acceptance system and the network element data for each service scenario, and provides corresponding data correction schemes. Ultimately, it obtains the correct user's key MDN and IMSI information and generates corresponding instruction sets based on the correct MDN and IMSI. Before issuing the instruction sets to the network elements, it audits and confirms the key indicators of the instruction sets, ensuring correct instruction issuance. This method solves the long-standing problem of mismatch between user network data and acceptance system data resources, and abnormal generated acceptance instructions, caused by factors such as abnormal work order execution and abnormal resource record information. Specifically, it addresses the problem of failures in accepting installation, SIM card replacement, and handset removal services due to incorrect MDN and IMSI information recorded by the acceptance system, thereby improving the success rate of 5G user service acceptance.

[0243] Corresponding to the above method embodiments, this application also provides a business processing apparatus, and the business processing apparatus described below can be referred to in correspondence with the business processing method described above.

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

[0245] The receiving module 510 is used to receive processing requests for the target business.

[0246] The determination module 520 is used to determine the target number corresponding to the target service based on the contracted data information on the user data management network element.

[0247] The generation module 530 is used to generate a target instruction set corresponding to the target service based on the target number;

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

[0249] The apparatus provided in this application, upon receiving a processing request for a target service, determines the target number corresponding to the target service based on the contractual data information on the user data management network element. Based on the target number, it generates a target instruction set corresponding to the target service 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 contractual data information on it is more accurate. Therefore, the target number corresponding to the target service determined based on the contractual data information on the user data management network element is also more accurate, and consequently, the target instruction set generated based on the target number is more effective, helping to improve the efficiency and accuracy of service processing.

[0250] In some embodiments of this application, when the target service includes a new installation service, the determining module 520 is specifically used for:

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

[0252] Based on the contract data information on the user data management network element, determine whether the first IMSI and the first MDN have account opening data.

[0253] If no account opening data exists for the first IMSI, then the first IMSI will be identified as the IMSI to be installed for the target service.

[0254] If the first MDN does not have account opening data, then the first MDN will be identified as the MDN to be newly installed for the target business.

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

[0256] If account opening data exists in the first IMSI, the first IMSI will be re-provided for the target business;

[0257] Based on the contract data information on the user data management network element, determine whether the re-provided first IMSI has account opening data;

[0258] If the first IMSI that is resubmitted does not contain account opening data, then the first IMSI that is resubmitted will be identified as the IMSI to be newly installed for the target service.

[0259] If the first IMSI that is resubmitted has account opening data, repeat the step of resubmitting the first IMSI for the target business until the first IMSI that is resubmitted does not have account opening data.

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

[0261] If account opening data exists in the first MDN, the first MDN will be re-provided for the target business;

[0262] Based on the contract data information on the user data management network element, determine whether the re-provided first MDN contains account opening data;

[0263] If the newly provided first MDN does not contain account opening data, then the newly provided first MDN will be identified as the MDN to be newly installed for the target business.

[0264] If the newly provided first MDN contains account opening data, repeat the steps of reproviding the first MDN for the target business until the newly provided first MDN no longer contains account opening data.

[0265] In some embodiments of this application, when the target service includes card replacement service, the determining module 520 is specifically used for:

[0266] Provide the target business with a second MDN, a second old IMSI, and a second new IMSI for the card to be replaced;

[0267] Based on the contract data information on the user data management network element, determine whether there is account opening data for the second new IMSI and the second MDN respectively;

[0268] If no account opening data exists for the second new IMSI, then the second new IMSI will be identified as the new IMSI of the card to be replaced corresponding to the target business.

[0269] If the second MDN contains account opening data, then the second MDN is identified as the MDN of the card to be replaced corresponding to the target business, and it is determined whether the IMSI contained in the account opening data of the second MDN is consistent with the second old IMSI.

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

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

[0272] If account opening data exists for the second new IMSI, a new second IMSI will be provided for the target business.

[0273] Based on the contract data information on the user data management network element, determine whether the second new IMSI provided has account opening data;

[0274] If the second new IMSI provided does not contain account opening data, then the second new IMSI provided will be identified as the new IMSI of the card to be replaced corresponding to the target business;

[0275] If the second new IMSI provided has account opening data, repeat the steps of providing the second new IMSI for the target business until the second new IMSI provided does not have account opening data.

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

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

[0278] The revised 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 this application, when the target service includes a disconnection service, the determining module 520 is specifically used for:

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

[0281] Based on the contract signing data information on the user data management network element, determine whether the third MDN has account opening data;

[0282] If account opening data exists in the third MDN, then the third MDN is identified as the MDN to be disconnected corresponding to the target business, and it is determined whether the IMSI contained in the account opening data of the third MDN is consistent with the third IMSI.

[0283] If the IMSI contained in the account opening data of the third MDN is consistent with the third IMSI, then the third IMSI will be identified as the IMSI to be disconnected for the target service.

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

[0285] The third IMSI will be corrected to the IMSI included in the account opening data of the third MDN;

[0286] The revised third IMSI is determined as the IMSI of the target service to be dismantled.

[0287] In some embodiments of this application, the execution module 540 is specifically used for:

[0288] Based on the standard instruction set template corresponding to the target business, perform key parameter verification on the target instruction set;

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

[0290] In some embodiments of this application, the execution module 540 is specifically used for:

[0291] Determine whether the target instruction set contains all the key parameters contained in the standard instruction set template corresponding to the target service;

[0292] If the target instruction set contains all the key parameters contained in the standard instruction set template corresponding to the target service, then determine whether the value of the target parameter in the target instruction set matches the target number. The target parameter is a key parameter that represents the target number.

[0293] If the value of the target parameter in the target instruction set matches the target number, then the verification of the target instruction set is considered successful.

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

[0295] If the target instruction set does not contain all the key parameters contained in the standard instruction set template corresponding to the target service, the target instruction set corresponding to the target service will be regenerated until the regenerated target instruction set contains all the key parameters contained in the standard instruction set template corresponding to the target service.

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

[0297] If the value of the target parameter in the target instruction set does not match the target number, update the value of the target parameter in the target instruction set to the target number.

[0298] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0299] Corresponding to the above method embodiments, this application also provides an electronic device, including:

[0300] Memory, used to store computer programs;

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

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

[0303] In this embodiment, 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.

[0304] The processor 10 can call programs stored in the memory 11. Specifically, the processor 10 can execute operations in the embodiments of the business processing method.

[0305] The memory 11 is used to store one or more programs. The programs may include program code, which includes computer operation instructions. In this embodiment, the memory 11 stores at least a program for implementing the following functions:

[0306] Receive processing requests for the target service;

[0307] Based on the contracted data information on the user data management network element, determine the target number corresponding to the target service;

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

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

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

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

[0312] Communication interface 12 can be an interface for the communication module, used to connect with 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 embodiments of this application. In practical applications, the electronic device may include more than Figure 6 More or fewer components as shown, or combinations of certain components.

[0314] Corresponding to the above method embodiments, this application embodiment also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the above-described business processing method.

[0315] Furthermore, it should be noted that this application also provides a computer program product or computer program, which may include computer instructions, which may be stored in a computer-readable storage medium. The processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the business processing methods described in the corresponding embodiments above. Therefore, these will not be repeated here. Additionally, the beneficial effects of using the same method will also not be repeated. For technical details not disclosed in the embodiments of the computer program product or computer program involved in this application, please refer to the description of the method embodiments of this application.

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

[0317] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0318] Through the above description of the embodiments, those skilled in the art will clearly understand that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of functionality in the above description. Whether these functions are implemented 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 beyond the scope of this application.

[0319] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disk, removable disk, compact disc read-only memory (CD-ROM), or any other form of storage medium known in the art, and includes several instructions for executing the methods described in the various embodiments of this application.

[0320] The embodiments of this application have been described above with reference to the accompanying drawings. The description of the embodiments above is only for the purpose of helping to understand the technical solutions and core ideas of this application. It should be noted that this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. For those skilled in the art, many other embodiments can be made without departing from the spirit and scope of protection of the claims, and several improvements and modifications can be made to this application. All such embodiments, improvements and modifications are within the protection scope of this application.

Claims

1. A business processing method, characterized in that, include: Receive processing requests for the target service; Based on the contracted data information on the user data management network element, determine the target number corresponding to the target service; Based on the target number, generate the target instruction set corresponding to the target service; Execute the target instruction set in response to the processing request; Wherein, if the target service includes a new subscription service, the target number includes the Mobile Directory Number (MDN) and the International Mobile Subscriber Identity (IMSI) to be newly subscribed; determining the target number corresponding to the target service based on the subscription data information on the user data management network element includes: Provide a first IMSI and a first MDN for the target service; Based on the contract data information on the user data management network element, determine whether the first IMSI and the first MDN have account opening data. If the first IMSI does not have account opening data, then the first IMSI is determined as the IMSI to be newly installed corresponding to the target service; If the first MDN does not have account opening data, then the first MDN is determined as the MDN to be newly installed corresponding to the target service; If account opening data exists in the first IMSI, the method further includes: Re-provide the first IMSI for the target service; Based on the contract data information on the user data management network element, determine whether the re-provided first IMSI has account opening data; If the first IMSI that is resubmitted does not contain account opening data, then the first IMSI that is resubmitted will be determined as the IMSI to be newly installed for the target service. If the re-provided first IMSI contains 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 contain account opening data.

2. The method according to claim 1, characterized in that, If account opening data exists in the first MDN, the method further includes: Re-provide the first MDN for the target service; Based on the contract data information on the user data management network element, determine whether the re-provided first MDN contains account opening data; If the first MDN that is re-provided does not contain account opening data, then the first MDN that is re-provided will be identified as the MDN to be newly installed for the target service. If the newly provided first MDN contains account opening data, the step of re-providing the first MDN for the target service is repeated until the newly provided first MDN does not contain account opening data.

3. The method according to claim 1, characterized in that, When the target service includes card replacement service, the target number includes the MDN, old IMSI, and new IMSI of the card to be replaced; The determination of 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 the second MDN, second old IMSI, and second new IMSI of the card to be replaced; Based on the contract data information on the user data management network element, determine whether the second new IMSI and the second MDN have account opening data; If the second new IMSI does not have account opening data, then the second new IMSI will be determined as the new IMSI of the card to be replaced corresponding to the target service; If the second MDN contains account opening data, then 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 contained in the account opening data of the second MDN is consistent with the second old IMSI. If the IMSI contained in the account opening data of the second MDN is consistent with the second old IMSI, then the second old IMSI is determined as the old IMSI of the card to be replaced corresponding to the target service.

4. The method according to claim 3, characterized in that, If account opening data exists for the second new IMSI, the method further includes: To provide a second new IMSI for the target service; Based on the contract data information on the user data management network element, determine whether the second new IMSI provided has account opening data; If the second new IMSI provided does not contain account opening data, then the second new IMSI provided will be determined as the new IMSI of the card to be replaced corresponding to the target service; If the second new IMSI provided has account opening data, repeat the step of providing the second new IMSI for the target service until the second new IMSI provided does not have account opening data.

5. The method according to claim 3, characterized in that, If the IMSI included in the account opening data of the second MDN is inconsistent with the second old IMSI, the method further includes: The second old IMSI is corrected to the IMSI contained in the account opening data of the second MDN; The revised 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 1, characterized in that, If the target service includes disconnection services, the target number includes the MDN and IMSI of the device to be disconnected; The determination of the target number corresponding to the target service based on the subscription data information on the user data management network element includes: Provide a third MDN and a third IMSI for the target service; Based on the contract data information on the user data management network element, determine whether the third MDN has account opening data; If the third MDN has account opening data, then the third MDN is identified as the MDN to be disconnected corresponding to the target service, and it is determined whether the IMSI contained in the account opening data of the third MDN is consistent with the third IMSI. If the IMSI contained in the account opening data of the third MDN is consistent with the third IMSI, then the third IMSI is determined as the IMSI to be disconnected corresponding to the target service.

7. The method according to claim 6, characterized in that, If the IMSI included in the account opening data of the third MDN is inconsistent with the third IMSI, the method further includes: The third IMSI is corrected to the IMSI included in the account opening data of the third MDN; The revised third IMSI is determined as the IMSI of the target service to be disassembled.

8. The method according to any one of claims 1 to 7, characterized in that, The execution of the target instruction set includes: Based on the standard instruction set template corresponding to the target service, the key parameters of the target instruction set are verified. If the verification passes, the target instruction set is executed.

9. The method according to claim 8, characterized in that, The step of performing key parameter verification on the target instruction set based on the standard instruction set template corresponding to the target service includes: Determine whether the target instruction set contains all the key parameters contained in the standard instruction set template corresponding to the target service; If the target instruction set contains all the key parameters contained in the standard instruction set template corresponding to the target service, then it is determined whether the value of the target parameter in the target instruction set matches the target number, where the target parameter is a key parameter characterizing the target number; If the value of the target parameter in the target instruction set matches the target number, then the verification of the target instruction set is deemed successful.

10. The method according to claim 9, characterized in that, If the target instruction set does not contain all the key parameters included in the standard instruction set template corresponding to the target service, the method further includes: Regenerate the target instruction set corresponding to the target service until the regenerated target instruction set contains all the key parameters contained in the standard instruction set template corresponding to the target service.

11. The method according to claim 9, characterized in that, If the value of the target parameter in the target instruction set does not match the target number, the method further includes: Update the value of the target parameter in the target instruction set to the target number.

12. A business processing apparatus, characterized in that, include: The receiving module is used to receive processing requests for the target business. The determination module is used to determine the target number corresponding to the target service based on the contracted data information on the user data management network element. The generation module is used 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 in response to the processing request; Wherein, when the target service includes new installation services, the determining module is specifically used for: Provide a first IMSI and a first MDN for the target service; Based on the contract data information on the user data management network element, determine whether the first IMSI and the first MDN have account opening data. If the first IMSI does not have account opening data, then the first IMSI is determined as the IMSI to be newly installed corresponding to the target service; If the first MDN does not have account opening data, then the first MDN is determined as the MDN to be newly installed corresponding to the target service; The determining module is further configured to: If account opening data exists in the first IMSI, the first IMSI will be re-provided for the target service; Based on the contract data information on the user data management network element, determine whether the re-provided first IMSI has account opening data; If the first IMSI that is resubmitted does not contain account opening data, then the first IMSI that is resubmitted will be determined as the IMSI to be newly installed for the target service. If the re-provided first IMSI contains 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 contain account opening data.

13. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the steps of the business processing method as described in any one of claims 1 to 11.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the business processing method as described in any one of claims 1 to 11.

Images