Number portability management method and system, electronic equipment and medium

Abstract

The invention provides a number portability management method and system, electronic equipment and a storage medium, and aims to solve the problem of how to check and manage a number portability process, the method comprises the following steps: after receiving an NP application request, a provincial SOA (I) initiates an NP application request to a CSMS through a headquarter SOA (I), so that the NP application request is confirmed to be accepted or not, if the NP application request is accepted, the request is forwarded to the provincial SOA (O), and if the NP application request is accepted, the NP application request is sent to the CSMS through the headquarter SOA (I); enabling the provincial SOA (O) to initiate qualification judgment to the provincial CRM, sending a qualification result to the CSMS by the provincial SOA (O) after the carrier-out CRM confirms qualification, and sending an application result to the provincial SOA (I) by the CSMS; informing the carry-in provincial score CRM NP of application confirmation, and realizing product ordering of the NP customer through the carry-in provincial score CRM; nP effective processing is completed through interaction between the headquarter SOA (I) and the CSMS. According to the invention, coordinated management of NP services among operators can be realized.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular, to a management method for number portability, a management system for number portability, an electronic device, and a computer-readable storage medium. Background Art

[0002] Mobile phone users can carry their numbers (Number Portability, NP) to switch between different operators. During the process of number portability, the database needs to be adjusted, which requires a relatively high level of data maintenance work. The requirements for modifying and updating user data are highly timely and unified. According to the user's choice of changing their network access provider (i.e., the mobile telecommunications operator to be transferred to), the user's data needs to be modified, and this process will involve multiple interactive authentications with other operators. How to perform data synchronization and process interaction, how to audit and manage the entire number portability process, ensure that users can conveniently and quickly switch between different operators, and ensure normal use after the switch, are currently existing problems. Summary of the Invention

[0003] To at least solve the above technical problems existing in the prior art, the present disclosure provides a management method for number portability, a management system for number portability, an electronic device, and a computer-readable storage medium, which can realize the coordinated management of NP services among operators and support the management of number portability acceptance processes and service data.

[0004] In a first aspect, the present disclosure provides a management method for number portability, the method

[0005] includes:

[0006] After receiving a request for an NP application, the Service Order Administration (SOA) of the receiving province sends an NP application request to the Central Service Management System (CSMS) through the SOA of the receiving headquarters, so that after receiving the NP application request, the CSMS confirms whether to accept this application. If it accepts, it forwards the application request message to the SOA of the sending province through the SOA of the sending headquarters, so that the SOA of the sending province initiates a judgment on the eligibility of the user's porting to the Customer Relationship Management (CRM) system of the sending province. After the CRM of the sending province confirms that the application is qualified, the SOA of the sending province sends the qualified result to the CSMS through the SOA of the sending headquarters, and the CSMS sends the application result to the SOA of the receiving province through the SOA of the receiving headquarters;

[0007] The receiving provincial branch SOA notifies the receiving provincial branch CRM of the confirmation of the NP application by the receiving party, and realizes the product ordering of NP customers through the order management module of the receiving provincial branch CRM;

[0008] The receiving provincial branch SOA completes the NP activation process through the interaction between the receiving headquarters SOA and the CSMS.

[0009] Furthermore, the process that the receiving provincial branch SOA completes the NP activation process through the interaction between the receiving headquarters SOA and the CSMS includes:

[0010] The receiving provincial branch SOA sends an activation request message to the CSMS through the receiving headquarters SOA, causing the CSMS to package the NP data of the received activation request message, and send an activation broadcast indication message to the LSMS (Local Service Management System) of all local operators, causing each operator's LSMS to synchronize data to all NPDBs (Number Portability Databases) within the network, and causing the CSMS to send a successful activation result notification message to the receiving provincial branch SOA and the sending provincial branch SOA respectively after receiving the successful activation broadcast confirmation from all LSMSs, causing the sending provincial branch SOA to send an activation result confirmation message after receiving the activation result notification message and delete the service data of this user within its own network, and notify the sending provincial branch CRM that the number portability is successful and perform the completion process for the sending party;

[0011] After receiving the activation result notification message, the receiving provincial branch SOA sends back an activation result confirmation and notifies the user that the NP service has been successfully processed;

[0012] The receiving provincial branch SOA notifies the receiving provincial branch CRM that the number portability is successful and performs the completion process for the receiving party.

[0013] Furthermore, the method further includes:

[0014] During the process of message forwarding between the receiving headquarters SOA and the sending headquarters SOA, a timer is used to monitor the timeliness of message processing.

[0015] Furthermore, the method further includes:

[0016] If the CSMS determines to reject the NP application after receiving the NP application request, the receiving provincial branch SOA receives the application rejection response message sent by the CSMS to the receiving provincial branch SOA through the receiving headquarters SOA, and the reason for rejection is carried in the application rejection response message;

[0017] The receiving provincial branch SOA records the result of this NP application and notifies the receiving provincial branch CRM.

[0018] Further, the completion processing of the porting-in party includes:

[0019] After the provincial SOA of the porting-in party notifies the CRM of the porting-in party that the number porting is successful, the CRM of the porting-in party establishes formal user information and subscription relationships based on the pre-acceptance information;

[0020] The provincial SOA of the porting-in party calls the NPHLR (Number Portability Home Location Register) account opening interface through the CRM system of the porting-in party to complete the binding relationship between the IMSI (International Mobile Subscriber Identity) number and the ported-in mobile phone number;

[0021] If the user applies for a pre-paid subscription service, the provincial SOA of the porting-in party calls the SCP (Service Control Point) / OCS (Online Charging System) interface through the CRM system of the porting-in party to activate the pre-paid service on the SCP / OCS.

[0022] In a second aspect, the present disclosure provides a method for managing number porting, the method including:

[0023] The provincial SOA of the porting-out party receives the application request message forwarded by the CSMS through the headquarter SOA of the porting-out party. The application request message is sent by the CSMS after receiving the NP application request and confirming the receipt of this application. The NP application request is initiated by the provincial SOA of the porting-in party to the CSMS through the headquarter SOA of the porting-in party after receiving the NP application request;

[0024] Initiate a judgment on the eligibility of the user for porting to the provincial CRM;

[0025] After the CRM of the porting-out party confirms that the application is qualified, the provincial SOA of the porting-out party sends the qualified result to the CSMS through the headquarter SOA of the porting-out party. The CSMS sends the application result to the provincial SOA of the porting-in party through the headquarter SOA of the porting-in party, enabling the provincial SOA of the porting-in party to notify the provincial CRM of the porting-in party of the NP application confirmation, and realizing the product subscription of the NP customer through the order management module of the provincial CRM of the porting-in party, and completing the NP activation process through the interaction between the provincial SOA of the porting-in party and the CSMS through the headquarter SOA of the porting-in party.

[0026] Further, the method further includes:

[0027] The outporting provincial SOA receives the successful activation result notification message sent by the CSMS. The successful activation result notification message is sent by the CSMS to the outporting provincial SOA and the inporting provincial SOA after receiving the successful activation broadcast confirmations from all LSMSs. The activation broadcast confirmations are sent after the inporting provincial SOA sends an activation request message to the CSMS through the inporting headquarters SOA, causing the CSMS to package the NP data of the received activation request message and send an activation broadcast indication message to all local operators' LSMSs. After each operator's LSMS synchronizes the data to all NPDBs within the network, the inporting provincial SOA sends the activation result confirmation message after receiving the activation result notification message, notifies the user that the NP service has been successfully processed, and notifies the inporting CRM that the number porting has been successful, and performs the inporting completion process;

[0028] Send an activation result confirmation message back to the CSMS, delete the user's service data within the local network, and notify the outporting CRM that the number porting has been successful, and perform the outporting completion process.

[0029] Furthermore, the outporting completion process includes:

[0030] Perform a restricted call operation on the corresponding IMSI for the outporting user on the NPMSC (Number Portability Mobile Switching Center); call an online instruction through the outporting CRM to update the status of the IMSI on the corresponding NPMSC, and at the same time perform corresponding processing on the user information in the CRM / OCS / SCP.

[0031] On the third aspect, the present disclosure provides a number porting management system, which includes an inporting provincial SOA, and the inporting provincial SOA includes:

[0032] A first sending module, which is configured to initiate an NP application request to the CSMS through the inporting headquarters SOA after receiving the request for the NP application. After the CSMS receives the NP application request, it confirms whether to accept this application. If it accepts, it forwards the application request message to the outporting provincial SOA through the outporting headquarters SOA, causing the outporting provincial SOA to initiate a user porting eligibility judgment to the outporting provincial CRM. After the outporting provincial CRM confirms that the application is qualified, the outporting provincial SOA sends the qualified result to the CSMS through the outporting headquarters SOA, and the CSMS sends the application result to the inporting provincial SOA through the inporting headquarters SOA;

[0033] A product ordering module, which is configured to notify the inporting provincial CRM of the NP application confirmation and implement the product ordering of the NP customer through the order management module of the inporting provincial CRM;

[0034] The NP activation module is configured to complete the NP activation process through the interaction between the SOA of the province where the number porting-in party is located and the CSMS via the SOA of the headquarters of the number porting-in party.

[0035] Fourthly, the present disclosure provides a management system for number portability, which includes the SOA of the province where the number porting-out party is located. The SOA of the province where the number porting-out party is located includes:

[0036] A receiving module, which is configured to receive an application request message forwarded by the CSMS through the SOA of the headquarters of the number porting-out party. The application request message is sent by the CSMS after receiving the NP application request and confirming the receipt of this application. The NP application request is initiated by the SOA of the province where the number porting-in party is located to the CSMS through the SOA of the headquarters of the number porting-in party after receiving the request for the NP application.

[0037] A judging module, which is configured to initiate a judgment on the eligibility of the user for number porting to the provincial CRM.

[0038] A second sending module, which is configured to, after the provincial CRM of the number porting-out party confirms that the application is qualified, send the qualified result to the CSMS through the SOA of the headquarters of the number porting-out party. The CSMS sends the application result to the SOA of the province where the number porting-in party is located through the SOA of the headquarters of the number porting-in party, so that the SOA of the province where the number porting-in party is located notifies the provincial CRM of the number porting-in party of the confirmation of the NP application, and realizes the product ordering of the NP customer through the order management module of the provincial CRM of the number porting-in party. And the SOA of the province where the number porting-in party is located completes the NP activation process through the interaction between the SOA of the headquarters of the number porting-in party and the CSMS.

[0039] Fifthly, the present disclosure provides an electronic device, including a memory and a processor. A computer program is stored in the memory. When the processor runs the computer program stored in the memory, the processor executes the management method for number portability as described in any one of the first aspect or the second aspect.

[0040] Sixthly, the present disclosure provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the management method for number portability as described in any one of the first aspect or the second aspect is realized.

[0041] Advantageous effects:

[0042] The management method for number portability, the management system for number portability, the electronic device and the storage medium provided by the present disclosure complete the hub function of message forwarding in the business process between the provincial CRM system and the CSMS system of the Ministry of Industry and Information Technology through the SOA of the headquarters, realize data synchronization and process interaction with the Ministry of Industry and Information Technology, realize the coordinated management of the NP service among operators, and ensure that users can conveniently and quickly carry out number porting between different operators. Description of the drawings

[0043] Figure 1 Schematic flowchart of a method for managing number portability provided in the first embodiment of the present disclosure;

[0044] Figure 2 Network architecture diagram of the number portability service provided in the embodiment of the present disclosure;

[0045] Figure 3 Schematic diagram of the transmission working mode of the NP service provided in the embodiment of the present disclosure

[0046] Figure 4 Schematic flowchart of a normal NP service application process provided in the embodiment of the present disclosure;

[0047] Figure 5 Schematic diagram of a normal NP service activation process provided in the embodiment of the present disclosure;

[0048] Figure 6 Schematic flowchart of a method for managing number portability provided in the second embodiment of the present disclosure;

[0049] Figure 7 Schematic architecture diagram of the receiving province SOA provided in the third embodiment of the present disclosure;

[0050] Figure 8 Schematic architecture diagram of the sending province SOA provided in the fourth embodiment of the present disclosure;

[0051] Figure 9 Architecture diagram of an electronic device provided in the fifth embodiment of the present disclosure. Detailed implementation manners

[0052] To enable those skilled in the art to better understand the technical solutions of the present disclosure, the present disclosure will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments and accompanying drawings described herein are only for explaining the present invention and not for limiting the present invention.

[0053] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above accompanying drawings are used to distinguish similar objects and do not necessarily need to describe a specific order or sequence; and, without conflict, the embodiments and features in the embodiments of the present disclosure can be combined with each other arbitrarily.

[0054] Among them, the terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure. The singular forms "a", "the", and "said" used in the embodiments of the present disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0055] In the following description, suffixes such as "module", "component", or "unit" used to represent elements are only for facilitating the description of the present disclosure, and have no specific meaning in themselves. Therefore, "module", "component", or "unit" can be used interchangeably.

[0056] The technical solutions of the present disclosure and how the technical solutions of the present disclosure solve the above technical problems existing in the prior art will be described in detail below with specific embodiments. It can be understood that in the embodiments of the present application, the execution subject can execute some or all of the steps in the embodiments of the present application. These steps or operations are only examples, and the embodiments of the present application can also execute other operations or various deformations of the operations. In addition, the various steps can be executed in different orders presented in the embodiments of the present application, and it is possible not to execute all the operations in the embodiments of the present application. And, the following several specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0057] Figure 1 It is a schematic flowchart of a method for managing number portability provided in Embodiment 1 of the present disclosure. As Figure 1 shown, the method includes:

[0058] Step S101: After receiving the request for the NP application, the SOA of the port-in province sends an NP application request to the CSMS through the SOA of the port-in headquarters, so that after receiving the NP application request, the CSMS confirms whether to accept this application. If it accepts, it forwards the application request message to the SOA of the port-out province through the SOA of the port-out headquarters, so that the SOA of the port-out province initiates a user portability eligibility judgment to the CRM of the port-out province. After the CRM of the port-out province confirms that the application is qualified, the SOA of the port-out province sends the qualified result to the CSMS through the SOA of the port-out headquarters, and the CSMS sends the application result to the SOA of the port-in province through the SOA of the port-in headquarters;

[0059] Step S102: The SOA of the port-in province notifies the CRM of the port-in province of the NP application confirmation, and realizes the product ordering of the NP customer through the order management module of the CRM of the port-in province;

[0060] Step S103: The SOA of the port-in province completes the NP activation process through the interaction with the CSMS through the SOA of the port-in headquarters.

[0061] By means of number portability, the mobile phone number will be completely unbound from the operator, which promotes competition among operators. Users have more autonomy and bargaining power, which is conducive to the development of the current mobile Internet ecosystem. However, due to this, the core network can no longer determine the operator to which a number belongs solely based on the number segment. Therefore, a database needs to be established to specifically store and manage the information of ported users. Currently, the number portability scheme adopted in China is based on location update. To implement number portability, the Ministry of Industry and Information Technology and major operators need to jointly build new network elements.

[0062] The network architecture of the number portability system is as Figure 2 shown. The Ministry of Industry and Information Technology builds a centralized database management center CSMS (including the centralized database CNPDB (Centralized Number Portalility Database) for number portability), which has NP database and service management functions, is responsible for the review and management of the entire NP process, realizes the coordinated management of NP services among operators, realizes the review of NP data of operators, and serves as the interface of the centralized database CNPDB for number portability to the outside world. CSMS is connected to each operator through dedicated lines.

[0063] In the operator, in the embodiment of the present disclosure, a new SOA and LNPDB (Local Number Portability Database) / LSMS system are built at the operator's headquarters. The SOA at the headquarters is responsible for the hub function of message forwarding in the business process between the provincial CRM system and the CSMS system of the Ministry of Industry and Information Technology, and the inspection function of the integrity and rationality of the business logic. The headquarters LSMS is responsible for the receiving function of the broadcast message of the number portability service data from the Ministry of Industry and Information Technology, the data auditing function between the CNPDB in the CSMS system of the Ministry of Industry and Information Technology and the LNPDB in the operator's network, the management function of the in-network number portability database LNPDB, the data synchronization function between the horizontal systems of the headquarters LNPDB, and the vertical synchronization function between the headquarters LNPDB and the provincial LNPDB, etc.

[0064] As Figure 3 shown, the transmission of the system includes several aspects: 1. Transmission between the provincial SOA and the headquarters SOA: The transmission method is WEBSERVICE. The message is transmitted in a synchronous manner.

[0065] 2. Transmission between the headquarters SOA and CSMS: The transmission protocol is SOAP1.1. The message is transmitted in a synchronous manner.

[0066] 3. Transmission between the headquarters SOA and the headquarters ENUMDNS: The transmission protocol is SOAP1.1.

[0067] The business process is processed synchronously: the provincial SOA <——> the headquarters SOA <——> CSMS adopt a synchronous method. The province initiates the function of the timer. The headquarters SOA does not provide the SOA function and directly forwards the requests sent by the province. The headquarters SOA checks whether its data can be correctly parsed. If it cannot be correctly parsed, then it feedbacks the corresponding information of ACK to the requester. For the data that the headquarters SOA checks to be okay, it is directly forwarded to the corresponding other party.

[0068] When a user submits an NP service porting application at the business acceptance point in the porting party province, the process from initiating a business application in the porting party business acceptance system to finally confirming the acceptance of the application is as Figure 4 shown, including:

[0069] 0: After the test province receives the user's NP service porting application, it judges whether the application meets the business requirements and the customer is not on the blacklist of this group. It enters the NP customer application information for the customer in the porting party CRM system. The CRM submits the NP application to the SOA of the porting party province in this province (SOA(I) represents the porting party SOA).

[0070] 1: After receiving the request for the NP application, the SOA(I) of the test province initiates an application request to CSMS through the headquarters SOA(I), and at the same time starts the timer T0.

[0071] 2: After receiving the application request, CSMS sends ACK(100) to the provincial SOA(I) through the headquarters SOA(I) within the T0 timer, indicating that the request has been successfully received. After receiving the ACK(100) from the headquarters, the SOA(I) of the test province starts the timer T1-1 and waits for the application response (acceptance) sent from the CSMS system.

[0072] 3: If CSMS confirms to accept this application according to the set management policy, it sends an application response (acceptance) to SOA(I) within the T1-1 timer. At the same time, CSMS forwards the application request message to the provincial SOA(O) through the headquarters SOA(O) (SOA(O) represents the carried-out party SOA). SOA(I) and SOA(O) send a successful ACK to CSMS within the T0 timer. After receiving the successful ACK sent by SOA(O), CSMS starts the T1-2 timer.

[0073] 4: The provincial SOA(O) initiates a judgment on the legality of the user's porting to the provincial CRM.

[0074] 5: The CRM of the porting-out party confirms with the SOA(O) that this application complies with the relevant regulations. In the business regulations, the possible reasons for rejection by the porting-out party are: the applicant's identity does not match, the user has not signed the contract with the porting-out party for a sufficient period, there is a phone bill dispute between the user and the porting-out party, the number for the applied service is out of service or does not exist, the number for the applied service has been reported lost, a network failure of the porting-out party, etc.

[0075] 6: The provincial SOA(O) sends the application result to the CSMS through the headquarters SOA(O) within the T1-2 timer and starts the T0 timer to wait for the successful ACK feedback from the CSMS.

[0076] 7: The CSMS sends a successful ACK to the provincial SOA(O) within the T0 timer. At the same time, the CSMS sends the application result notification (accepted by the porting-out party) to the provincial SOA(I). At the same time, it starts the timer T0 to wait for the successful ACK from the SOA(I), and starts the timer T1-3 to wait for the activation request from the SOA(I). The provincial SOA(I) sends a successful ACK to the CSMS through the headquarters SOA(I) within the T0 timer.

[0077] 8: The provincial SOA(I) notifies the provincial CRM of the NP application confirmation. The porting-in party realizes the product ordering of NP customers through the order management module of the CRM.

[0078] 9: The porting-in party sends an NP activation processing application to the CSMS.

[0079] The SOA(I) of the operator headquarters and the SOA(O) of the operator headquarters play the functions of recording Log and data forwarding here. The recorded Log is used for post-event statistical analysis.

[0080] Note: In this process and the following processes, each time the message sender sends a message, it should start the timer T0 and wait for the ACK message.

[0081] This embodiment of the present disclosure completes the hub function of message forwarding for the business processes between the provincial CRM system and the CSMS system of the Ministry of Industry and Information Technology through the headquarters SOA, realizes data synchronization and process interaction with the Ministry of Industry and Information Technology, realizes the coordinated management of NP services among operators, and ensures that users can conveniently and quickly transfer between different operators.

[0082] Further, the process by which the provincial SOA of the porting-in party completes the NP activation processing through interaction with the CSMS via the headquarters SOA of the porting-in party includes:

[0083] The provincial SOA of the incoming party sends an effectiveness request message to the CSMS through the SOA of the incoming party's headquarters, so that the CSMS packages the NP data of the received effectiveness request message and sends an effectiveness broadcast indication message to the LSMS of all local operators, so that the LSMS of each operator synchronizes data with all NPDBs in the network, and after receiving the successful effectiveness broadcast confirmation from all LSMS, the CSMS sends a successful effectiveness result notification message to the provincial SOA of the incoming party and the provincial SOA of the outgoing party respectively, so that after receiving the effectiveness result notification message, the provincial SOA of the outgoing party sends back an effectiveness result confirmation message and deletes the service data of the user in the local network, and notifies the outgoing party's CRM that the number has been successfully transferred to another network, and the outgoing party completes the processing;

[0084] After receiving the validation result notification message, the provincial SOA of the importing party returns the validation result confirmation and notifies the user that the NP service has been successfully processed;

[0085] The provincial SOA of the carrier notifies the carrier's CRM that the number has been successfully transferred to another network and completes the process.

[0086] After the NP application is accepted, the carrier initiates the NP service validation process within the T1-3 timer to activate the NP service. The carrier initiates the validation request, and the validation process is required to be completed within the T1-5 timer. The service interaction flow chart is as follows: Figure 5 As shown:

[0087] 1: After the NP application request is successfully confirmed, the carrier completes the network data production and activation within the timer T1-3, and the carrier's provincial SOA (I) sends a validation request message to CSMS through the headquarters SOA (I). After receiving the successful ACK feedback from CSMS, SOA (I) starts timer T1-4.

[0088] 2: CSMS turns off the T1-3 timer and sends a validation response to the provincial SOA(I) via the headquarters SOA(I) within the T1-4 timer (CSMS accepts). After receiving the message, the provincial SOA(I) sends a successful ACK to the CSMS via the headquarters SOA(I) within the T0 timer.

[0089] 3: CSMS packages the NP data of the validation request message received before 24:00 on the same day, starts T1-5 at 1:00 am the next day, sends a validation broadcast indication message to all local operators' LSMS, and starts T2-1 timer after receiving a successful ACK. The operator's LSMS synchronizes data to all NPDBs in the network.

[0090] 4: Each operator's LSMS synchronizes this user data to all NPDBs within its own network at time T2-1. After the LSMS completes the synchronization, it sends a successful activation broadcast confirmation (success) message to the CSMS within the T2-1 timer and receives a successful ACK reply from the CSMS.

[0091] Carrier out: Network elements that need to update NP data include NPDBs under the headquarters LSMS, NPDBs under the provincial LSMS where the NP number belongs, and the headquarters EnumDNS.

[0092] Carrier in: Network elements that need to update data include NPDBs under the headquarters LSMS, NPDBs under the provincial LSMS where the NP number belongs, and the headquarters EnumDNS.

[0093] Third party: Network elements that need to update data include NPDBs under the headquarters LSMS, NPDBs under the provincial LSMS where the NP number belongs, and the headquarters EnumDNS.

[0094] 5: After the CSMS receives successful activation broadcast confirmations from all LSMSs, it stops the T1-5 timer and sends successful activation result notification messages to SOA(I) and SOA(O) respectively.

[0095] After receiving the activation result notification message, SOA(O) sends back an activation result confirmation and immediately deletes the service data of this user within its own network (including data of related devices such as SCP and HLR). The service application and activation process end. After receiving the activation result notification message, SOA(I) sends back an activation result confirmation and notifies the user that the NP service has been successful at an appropriate time.

[0096] 6. The operator's SOA(I) and SOA(O) notify the CRM that the number has been successfully transferred and perform the completion process.

[0097] Through the service activation process, the user can retain the original mobile phone number, transfer between operators, and ensure that the user information is accurately synchronized to other operators.

[0098] The LSMS should be able to manage the data in the LNPDB database, including: adding, deleting, modifying, querying, and statistics.

[0099] Adding NP data

[0100] When the NP request of a number becomes effective, the LSMS should be able to store the NP information of this number into the LNPDB database according to the requirements of the service process. The NP data of a number includes: NP number, the network of the porting-out party, the network of the porting-in party, the network owning the number, service type, service process ID number, NP service application time, NP actual effective date, user information (user name, document type, document number, contact phone number, name of the proxy, document type of the proxy, document number of the proxy), etc.

[0101] Delete NP data

[0102] When an NP number returns to the original network or is cancelled, the LSMS should be able to delete the NP information of this number from the NP database according to the requirements of the service process and transfer it to the historical table for archiving.

[0103] Modify NP data

[0104] When an NP number is ported to another network, the LSMS should be able to modify the NP information of the number according to the requirements of the service process.

[0105] Query NP data

[0106] The LSMS should support the function of querying NP data using any field or combination of fields. Field queries support range queries and batch queries. For example, it can query all NP data with an effective date from January 1, 2007 to December 31, 2007, or query all NP data of the 139 number segment. The query results are displayed in a list, and any field of each NP data can be viewed.

[0107] Statistical analysis of NP data

[0108] The LSMS should support the statistical function of NP data. The statistical methods include range statistics, time period statistics, and violation statistics. The statistical results can be exported in ways such as html, excel, and txt.

[0109] Range statistics refers to counting the numerical values of all NP data entries within a certain range. For example, counting the NP quantities within each number segment from 130 to 139; counting the number of users ported from China Mobile to China Unicom and from China Unicom to China Mobile, etc.

[0110] Time period statistics refers to counting the changes in NP quantities within different time periods. For example, counting the daily, weekly, and monthly NP increase amounts and total amounts in 2007 and calculating the month-on-month or year-on-year change rates, etc.

[0111] Violation statistics refers to the statistics of the number of violations within a certain time period according to the requirements of relevant management regulations. For example, it can be used to count the number of user applications rejected due to network failures in CSMS or a certain provincial branch, the number of user applications not processed by a provincial branch within the specified time limit, the number of user applications processed by a provincial branch in a certain month, the number of applications rejected due to incorrect judgments by the porting party, and so on.

[0112] In the embodiments of the present disclosure, the management part of the NP database and the forwarding of service acceptance messages are completed at the headquarters, realizing the NP data management function at the headquarters level.

[0113] NP service management function

[0114] NP broadcast management

[0115] The role of LSMS in the NP broadcast process is as follows: after CSMS broadcasts the activation notice to the headquarters LSMS, the headquarters LSMS broadcasts to the provincial LSMSs and starts timers respectively. If a response from a provincial LSMS is received within this time, the timer is turned off. If the response from a province times out, the headquarters LSMS resends the broadcast message to that province and restarts the timer for that province. After receiving correct responses from all provinces, it notifies CSMS of the structure of NP activation or cancellation.

[0116] The management functions of LSMS for NP broadcasts include: setting the number of retransmissions of the broadcast and alarming the management personnel when the provincial LSMS does not receive a successful broadcast response.

[0117] Audit management

[0118] Receive the audit requirements sent by CSMS to the headquarters LSMS. The headquarters LSMS ensures the integrity of the NP database of the relevant network elements at the headquarters level and sends an audit request to the provincial LSMSs, requesting the integrity of the NP databases on the provincial-level related devices (such as HLR, NPHLR, NPMSC).

[0119] Synchronization management

[0120] The headquarters LSMS should be able to receive the NP data synchronization file from CSMS. And at the agreed time, it packages and compresses the data and publishes it to the provincial branches through FTP for the provincial LSMSs to perform data recovery.

[0121] In addition, the headquarters LSMS also receives the NP data increment record and the MD5 verification file generated by CSMS at 3:30 am every day up to the current time, packages and compresses them, and publishes them to the provincial LSMSs through FTP.

[0122] Fault tolerance function

[0123] When restarting the headquarters LSMS in case of process hang, hardware crash, etc., it should be ensured that the messages received but not yet processed are not lost.

[0124] Timer management

[0125] LSMS should be able to set all timers used in the headquarters LSMS and SOA.

[0126] Log management

[0127] The headquarters LSMS should have a perfect log management function, which can record all operations performed on the headquarters LSMS and can also export the log content.

[0128] Account management

[0129] LSMS should be able to manage the login accounts of the devices. Account management includes permission allocation, username management, password management, etc.

[0130] Overload protection

[0131] When the CPU occupancy rate of LSMS reaches 70% or the memory occupancy rate reaches 90%, overload protection should be enabled.

[0132] Alarm function

[0133] When errors such as overload protection or incorrect response to broadcasts occur, the device should provide audible and visual alarm functions.

[0134] Historical records

[0135] All NP process information within 12 months should be queryable from the LSMS device itself.

[0136] After CSMS sends an effective broadcast to all LSMSs in the local network, if it receives a failed effective broadcast response from a certain LSMS, CSMS starts the manual intervention process. After the fault is resolved, CSMS re-sends an effective broadcast to the failed LSMS for this data within the timer T1-5.

[0137] Process description:

[0138] 1-3: Same as Figure 5 Effective process.

[0139] 4: After the LSMS(C) at the headquarters of a certain operator C receives the broadcast data and fails to update the user data in the local NPDB, it returns the result of the effective broadcast (failure) to the CSMS within the timer T2-1. At the same time, the LSMS at the operator's headquarters needs to ensure that the NP records in each NP database within the local network are consistent and are the values before the effective broadcast. The CSMS replies with a successful ACK within the T0 timer and immediately issues an alarm for manual intervention to troubleshoot the system failure.

[0140] 4’: Before the timeout of T1-5, if the failure can be resolved, manual control is required for the CSMS to resend the effective broadcast instruction to the failed LSMS, and the subsequent process is automatically completed by the system.

[0141] 5-6: Same as Figure 5 Effective process.

[0142] Note: For the same effective broadcast instruction message, as long as one data update fails, the current effective process fails. For the resent effective broadcast instruction, the LSMS cannot reject the message due to duplicate NP data. After the effective broadcast fails, the CSMS system will automatically generate an audit request for the relevant number. After the failure is resolved, it is determined whether to manually trigger the number audit according to the requirements of the maintenance regulations.

[0143] In addition, the SOA(I) at the operator's headquarters and the SOA(O) at the operator's headquarters perform the functions of recording Log and data forwarding here. The recorded Log is used for post-event statistical analysis.

[0144] 1.1.12 Successful effective broadcast rollback process

[0145] After the CSMS sends the effective broadcast instruction to all LSMSs in the local network, if it receives a failed effective broadcast confirmation returned by a certain LSMS and the failure cannot be eliminated within the T1-5 timer, the CSMS needs to initiate the effective broadcast rollback process. If the failure cannot be eliminated within the T1-5 timer, the CSMS sends an effective cancellation broadcast instruction to the LSMS and completes the effective broadcast rollback process.

[0146] Furthermore, the method further includes:

[0147] During the message forwarding process between the SOA at the headquarters of the porting-in party and the SOA at the headquarters of the porting-out party, the timer is used to monitor the timeliness of message processing.

[0148] The headquarters SOA is the management center for operators to accept the number portability service. It is mainly responsible for completing the function of message forwarding in the business process between the provincial CRM and the CSMS system of the Ministry of Industry and Information Technology, the function of checking the integrity and rationality of business logic, the marketing management function of the number portability service in the whole network market, and the customer service function of resolving disputes arising during the number portability process for the Ministry of Industry and Information Technology and the provinces.

[0149] The hub function of message forwarding in the business process

[0150] The headquarters SOA mainly receives NP application, cancellation, revocation, activation, suspension, and restoration business messages from the CSMS system of the Ministry of Industry and Information Technology and the provincial CRM system, and according to the processing requirements of various messages, forwards the messages to the corresponding system for processing and starts a timer for message management. After receiving the processing results of the corresponding system, it feeds back the result information to the message originator system. During the entire message forwarding process, the headquarters SOA should use the timer to monitor the timeliness of message processing.

[0151] In addition to forwarding messages, the headquarters SOA should record operation logs, which are used for statistical analysis and process query. It is required that the headquarters SOA can work continuously for 7×24 hours. When the headquarters SOA restarts due to situations such as process hanging or hardware crashing, it should ensure that the messages received but not yet processed are not lost. When the CPU occupancy rate of the machine where the SOA is located reaches 70%, or the memory occupancy rate reaches 90%, it should be able to perform overload protection, respond to all message requests with an error ACK, and alarm the maintenance personnel.

[0152] The function of checking the integrity and rationality of business logic

[0153] The headquarters SOA can also expand some logical judgments. It includes checking the integrity of business processing according to the serial number carried in the message, providing an alarm to the operator for incomplete business processing, and starting an artificial process verification. According to the predetermined business rules of number portability, it conducts a rationality check of business logic. For example, for the overdue suspension application number sent by the province, it can check whether the ported number information is correct according to the business processing log, and then send a suspension application to the CSMS.

[0154] Furthermore, the method further includes:

[0155] If the CSMS determines to reject the NP application request after receiving the NP application request, the SOA of the porting-in province receives the application rejection response message sent by the CSMS to the SOA of the porting-in province through the headquarters SOA of the porting-in party, and the reason for rejection is carried in the application rejection response message;

[0156] The provincial SOA of the carrier records the result of the NP application and notifies the provincial CRM of the carrier.

[0157] According to regulations, CSMS can reject NP applications and send an application response (rejection) message to the provincial SOA (I) through the headquarters SOA (I).

[0158] After receiving the user's NP service application, the carrier should enter the customer's NP application information into the carrier's CRM system if it determines that the application meets the NP service porting conditions and the customer is not on the group's blacklist. Then, the NP application is submitted to the provincial SOA (I) through CRM.

[0159] 1: The provincial SOA (I) initiates an application request to the CSMS through the headquarters SOA. After receiving the application request, the CSMS responds with a success ACK.

[0160] 2: CSMS determines to reject the application based on the set business rules, and sends an application response (rejection) message to the provincial SOA (I) through the headquarters SOA (I), carrying the reason for rejection.

[0161] When CSMS receives an application request, the situations in which it can be rejected and the return codes for rejection are as follows:

[0162] (1) The time interval from the user's last number portability does not reach the value specified by the law (600);

[0163] (2) One number, multiple transfers (601);

[0164] (3) The number of number portability applications received on the same day exceeds the upper limit (602);

[0165] (4) According to policy, this number is not allowed to be ported (603).

[0166] 3: The provincial SOA (I) receives the application response (rejection) message from CSMS, records it and notifies the provincial CRM (I), and at the same time needs to send a success ACK to CSMS to indicate that the message was successfully received. After the provincial CRM (I) receives the application response (rejection) message, the carrier that carries the service is responsible for notifying the user of the application result, and the application process ends.

[0167] In addition, SOA (I) of the operator headquarters and SOA (O) of the operator headquarters play the role of recording logs and forwarding data. The recorded logs are used for post-event statistical analysis.

[0168] After CSMS rejects the application request, the application process ends. If the user's application needs to be reprocessed, SOA(I) needs to re-initiate the application with a new FlowID.

[0169] 2: After receiving the application request, CSMS determines to accept this application according to the set management rules, sends an application response (acceptance) to SOA(I) within the T1-1 timer, and starts timer T0 to wait for the successful ACK feedback from SOA(I). After receiving the application response (acceptance) sent by CSMS, SOA(I) needs to feedback a successful ACK within the T0 timer.

[0170] 3: CSMS sends an application request to SOA(O), and starts timer T0 to wait for SOA(O) to send a successful ACK. After receiving the application request, SOA(O) needs to send a successful ACK within the T0 timer and start timer T1-2. After receiving the successful ACK sent by SOA(O), CSMS starts timer T1-2 to wait for the application response from SOA(O).

[0171] 3’ / 4’: The provincial SOA(O) sends a request to the outgoing CRM to check the legality of the outgoing. The outgoing CRM confirms to SOA(O) that the user does not meet the conditions for moving out, and the application is rejected.

[0172] When SOA(O) receives the application request, the situations where it can reject and the rejection return codes are as follows:

[0173] (1) The NP area of the Message ID does not correspond to the number (653);

[0174] (2) The user identity information does not match (610);

[0175] (3) The user's signing time with the outgoing party is less than the required time (611);

[0176] (4) There is a phone bill dispute between the user and the outgoing party (612);

[0177] (5) The number for applying the service is a suspended number or does not exist (613);

[0178] (6) The number for applying the service has been reported lost (614);

[0179] (7) The outgoing party's network fails (615).

[0180] 4: The provincial SOA(O) forwards the application response (rejection) to CSMS through the headquarter SOA(O) within the T1-2 timer, and starts timer T0 to wait for the successful ACK sent by CSMS. CSMS feedbacks a successful ACK to SOA(O) within the T0 timer.

[0181] 5: The CSMS sends the application result notification (rejection) to the provincial SOA(I) through the headquarters SOA(I), points out the reasons for the rejection by the porting-out party, and starts the timer T0 to wait for the successful ACK feedback from the SOA(I). The SOA(I) shall feedback the successful ACK within the T0 timer after receiving the application result notification (rejection).

[0182] 6: The SOA(I) notifies the CRM: NP application rejected. The salesperson notifies the customer of the application result and the process ends.

[0183] In addition, the SOA(I) of the operator headquarters and the SOA(O) of the operator headquarters function as recording Logs and data forwarding here. The recorded Logs are used for post-event statistical analysis.

[0184] After the SOA(O) rejects the application request of the SOA(I), the process ends. If it is necessary to continue processing the application of this user, the SOA(I) needs to initiate a new application with a new Flow ID.

[0185] During the NP process, multiple interactive authentications will be carried out between operators. The embodiments of the present disclosure complete the management part of the NP database and the forwarding of service acceptance messages by design, are responsible for the review and management of the entire NP process, realize the coordinated management of the NP service among operators, realize the review of the NP data of operators, and ensure that users can transfer networks between different operators conveniently and quickly.

[0186] Further, the completion processing of the porting-in party includes:

[0187] After the provincial SOA of the porting-in party notifies the CRM of the porting-in party that the number transfer is successful, the CRM of the porting-in party establishes formal user information and subscription relationships based on the pre-acceptance information;

[0188] The provincial SOA of the porting-in party calls the NPHLR account opening interface through the CRM system of the porting-in party to complete the binding relationship between the IMSI number and the porting-in mobile phone number;

[0189] If the user applies for a prepaid service contract, the provincial SOA of the porting-in party calls the SCP\OCS interface through the CRM system of the porting-in party to activate the prepaid service on the SCP\OCS. Completion processing of the porting-in party.

[0190] The CRM of the porting-in party establishes formal user information and subscription relationships based on the pre-acceptance information.

[0191] The SOA(I) calls the NPHLR account opening interface through the CRM system to complete the binding relationship between the IMSI number and the porting-in mobile phone number (i.e., complete the IMSI data update on the NPHLR). The main parameters of the account opening interface are described as follows:

[0192]

[0193]

[0194] If a user applies for a pre-paid signing service, SOA(I) calls the SCP / OCS interface through the CRM system to activate the pre-paid service on the SCP / OCS.

[0195] The releasing party completes the processing.

[0196] According to the rules formulated by the network department and the business department, for users to be released, corresponding operations such as restricted calls need to be performed on the corresponding IMSI on the NPMSC. It is necessary to call the online instruction through the CRM to update the status of the IMSI on the corresponding NPMSC, and at the same time perform corresponding processing on the user information in the CRM / OCS / SCP.

[0197] In addition, SOA(I) of the operator's headquarters and SOA(O) of the operator's headquarters play the functions of recording Log and data forwarding here. The recorded Log is used for post-event statistical analysis.

[0198] To ensure the integrity and consistency of NP data in each level of NPDB, CSMS and each level of LSMS must be able to support the auditing of NP data. And when data inconsistency occurs during the audit, the data can be corrected through data synchronization.

[0199] NP data auditing is divided into two parts: external data auditing and internal data auditing. When external data auditing fails, the correctness of the data in the headquarters LSMS is subject to CSMS; when internal auditing fails, the data in the provincial LSMS is subject to the headquarters LSMS.

[0200] Data synchronization between the headquarters LSMS and the provincial LSMS adopts the method of ftp file transfer. The synchronization files are stored in separate directories by province.

[0201] The provincial LSMS should download this file to the local for storage within the daily data synchronization time (i.e., after 4:30 am every day) after the headquarters LSMS generates the full data file or incremental data file, for use in case of audit failure.

[0202] During the data synchronization process of the provincial LSMS, filter out the NP records that are different between the synchronization data files provided by the provincial LSMS and the headquarters LSMS, generate data update instructions for the NPHLR based on the new NP data, and send them to the NPHLR interface for data update operations. After the NPHLR executes the instructions to update the NP data and returns the instruction execution result, the provincial headquarters LSMS records the update result, and the NPHLR data update process ends.

[0203] Data synchronization of the NPHLR is carried out by using the instruction interface provided by the NPHLR.

[0204] The embodiments of the present disclosure support the management of the number portability service acceptance process.

[0205] The SOA of the headquarters is not responsible for business functions such as directly facing customers for service acceptance and customer complaints. It is mainly responsible for completing the hub function of message forwarding for business processes between the provincial CRM system and the CSMS system of the Ministry of Industry and Information Technology, as well as the inspection function for the integrity and rationality of business logic. It supports the management of number portability service data.

[0206] The LSMS of the headquarters is mainly responsible for the function of receiving broadcast messages of number portability service data from the Ministry of Industry and Information Technology, completing the data audit function between the CNPDB in the CSMS system of the Ministry of Industry and Information Technology and the LNPDB within China Unicom's network, the management function of the in-network number portability database LNPDB, the data synchronization function between the horizontal systems of the headquarters LNPDB, and the vertical synchronization function between the headquarters LNPDB and the provincial LNPDB, etc.

[0207] The embodiments of the present disclosure complete the hub function of message forwarding for business processes between the provincial CRM system and the CSMS system of the Ministry of Industry and Information Technology through the headquarters SOA, realize data synchronization and process interaction with the Ministry of Industry and Information Technology, realize the coordinated management of NP services among operators, realize the audit of NP data of operators, enable users to keep their original mobile phone numbers and switch between operators, and ensure that user information is accurately synchronized to other operators; ensure that users can conveniently and quickly switch between different operators.

[0208] Figure 6 It is a schematic flowchart of a method for managing number portability provided for Embodiment 2 of the present disclosure, as Figure 6 shown, the method includes:

[0209] Step S201: The provincial SOA of the porting-out party receives the application request message forwarded by CSMS through the headquarters SOA of the porting-out party. The application request message is sent by CSMS after receiving the NP application request and confirming the acceptance of this application. The NP application request is initiated by the provincial SOA of the porting-in party to CSMS through the headquarters SOA of the porting-in party after receiving the request for the NP application.

[0210] Step S202: Initiate a judgment on the eligibility of the user's number porting to the provincial CRM.

[0211] Step S203: After the CRM of the porting-out party confirms that the application is qualified, the provincial SOA of the porting-out party sends the qualified result to the CSMS via the headquarter SOA of the porting-out party. The CSMS then sends the application result to the provincial SOA of the porting-in party via the headquarter SOA of the porting-in party, enabling the provincial SOA of the porting-in party to notify the provincial CRM of the porting-in party of the NP application confirmation, and realizing the product ordering of NP customers through the order management module of the provincial CRM of the porting-in party. Additionally, the provincial SOA of the porting-in party completes the NP activation process through the interaction between the headquarter SOA of the porting-in party and the CSMS.

[0212] Further, the method further includes:

[0213] The provincial SOA of the porting-out party receives the successful activation result notification message sent by the CSMS. The successful activation result notification message is sent by the CSMS to the provincial SOA of the porting-out party and the provincial SOA of the porting-in party after receiving the successful activation broadcast confirmations from all LSMSs. The activation broadcast confirmations are sent after the provincial SOA of the porting-in party sends an activation request message to the CSMS via the headquarter SOA of the porting-in party, causing the CSMS to package the NP data of the received activation request message and send an activation broadcast instruction message to all local operators' LSMSs. After each operator's LSMS synchronizes the data to all NPDBs within the network, the provincial SOA of the porting-in party receives the activation result notification message, sends back an activation result confirmation, notifies the user that the NP service has been successfully processed, and notifies the CRM of the porting-in party that the number porting has been successful, and proceeds with the completion process for the porting-in party;

[0214] Send back an activation result confirmation message to the CSMS and delete the user's service data within this network, and notify the CRM of the porting-out party that the number porting has been successful, and proceed with the completion process for the porting-out party.

[0215] Further, the completion process for the porting-out party includes:

[0216] Perform a restricted call operation on the corresponding IMSI on the NPMSC for the porting-out user; call an online instruction through the CRM of the porting-out party to update the status of the IMSI on the corresponding NPMSC, and simultaneously perform corresponding processing on the user information in the CRM / OCS / SCP.

[0217] This embodiment of the present disclosure corresponds to Embodiment 1. For specific details, reference can be made to the relevant descriptions in Embodiment 1, which will not be elaborated here.

[0218] This embodiment of the present disclosure also provides a management system for number porting. The system includes the provincial SOA of the porting-in party, as Figure 7 shown, and the provincial SOA of the porting-in party includes:

[0219] The first sending module 11 is configured to, after receiving a request for an NP application, initiate an NP application request to the CSMS through the home SOA of the bringing-in party, so that after the CSMS receives the NP application request, it confirms whether to accept this application. If it accepts, it forwards the application request message to the provincial SOA of the carrying-out party through the home SOA of the carrying-out party, enabling the provincial SOA of the carrying-out party to initiate a user porting eligibility judgment to the CRM of the provincial branch of the carrying-out party. After the CRM of the provincial branch of the carrying-out party confirms that the application is qualified, the provincial SOA of the carrying-out party sends the qualified result to the CSMS via the home SOA of the carrying-out party, and the CSMS sends the application result to the provincial SOA of the bringing-in party through the home SOA of the bringing-in party;

[0220] The product ordering module 12 is configured to notify the CRM of the provincial branch of the bringing-in party of the NP application confirmation and implement the product ordering for NP customers through the order management module of the CRM of the provincial branch of the bringing-in party;

[0221] The NP activation module 13 is configured to complete the NP activation process through the interaction between the provincial SOA of the bringing-in party and the CSMS via the home SOA of the bringing-in party.

[0222] Furthermore, the NP activation module 13 includes:

[0223] A sending unit, which is configured to send an activation request message to the CSMS through the home SOA of the bringing-in party, enabling the CSMS to package the NP data in the received activation request message and send an activation broadcast indication message to all local LSMSs of the operators, causing each operator's LSMS to synchronize data to all NPDBs within the network, and enabling the CSMS to send a successful activation result notification message to the provincial SOA of the bringing-in party and the provincial SOA of the carrying-out party respectively after receiving successful activation broadcast confirmations from all LSMSs. After receiving the activation result notification message, the provincial SOA of the carrying-out party sends back an activation result confirmation message and deletes the service data of this user within its own network, and notifies the CRM of the carrying-out party that the number porting is successful and performs the completion process for the carrying-out party;

[0224] A notification unit, which is configured to, after receiving the activation result notification message, send back an activation result confirmation and notify the user that the NP service has been successfully processed; and,

[0225] Notify the CRM of the bringing-in party that the number porting is successful and perform the completion process for the bringing-in party.

[0226] Furthermore, the provincial SOA of the bringing-in party further includes a first receiving module 14 and a recording module 15:

[0227] The first receiving module 14 is configured to, if the CSMS determines to reject this NP application after receiving the NP application request, receive the application rejection response message sent by the CSMS to the provincial SOA of the bringing-in party through the home SOA of the bringing-in party, and the reason for rejection is carried in the application rejection response message;

[0228] The recording module 15 is set to record the result of this NP application and notify the CRM of the porting-in provincial branch.

[0229] Furthermore, the porting-in completion process includes:

[0230] After the SOA of the porting-in provincial branch notifies the CRM of the porting-in party that the number porting is successful, the CRM of the porting-in party establishes formal user information and subscription relationships based on the pre-acceptance information;

[0231] The SOA of the porting-in provincial branch calls the NPHLR account opening interface through the CRM system of the porting-in party to complete the binding relationship between the IMSI number and the porting-in mobile number;

[0232] If the user applies for a pre-paid subscription service, the SOA of the porting-in provincial branch calls the SCP / OCS interface through the CRM system of the porting-in party to activate the pre-paid service on the SCP / OCS.

[0233] Embodiment 4 of the present disclosure further provides a management system for number porting. The system includes the SOA of the porting-out provincial branch, as Figure 8 shown. The SOA of the porting-out provincial branch includes:

[0234] A second receiving module 21, which is set to receive the application request message forwarded by the CSMS through the SOA of the porting-out headquarters. The application request message is sent by the CSMS after receiving the NP application request and confirming the receipt of this application. The NP application request is initiated by the SOA of the porting-in provincial branch to the CSMS through the SOA of the porting-in headquarters after receiving the NP application request;

[0235] A judgment module 22, which is set to initiate a judgment on the eligibility of the user for porting to the provincial branch CRM;

[0236] A second sending module 23, which is set to, after the CRM of the porting-out party confirms that the application is qualified, send the qualified result to the CSMS through the SOA of the porting-out headquarters. The CSMS sends the application result to the SOA of the porting-in provincial branch through the SOA of the porting-in headquarters, so that the SOA of the porting-in provincial branch notifies the provincial branch CRM of the porting-in party of the NP application confirmation, and realizes the product subscription of the NP customer through the order management module of the provincial branch CRM of the porting-in party, and the SOA of the porting-in provincial branch completes the NP activation process through the interaction with the CSMS through the SOA of the porting-in headquarters.

[0237] Furthermore,

[0238] The second receiving module 21 is further configured to receive the successful effectiveness result notification message sent by the CSMS. The successful effectiveness result notification message is sent by the CSMS to the out-carrying provincial SOA and the in-carrying provincial SOA after receiving the successful effectiveness broadcast confirmations from all LSMSs. The effectiveness broadcast confirmation is sent after the in-carrying provincial SOA sends an effectiveness request message to the CSMS through the in-carrying headquarters SOA, causing the CSMS to pack the NP data of the received effectiveness request message and send an effectiveness broadcast indication message to all local operators' LSMSs. After each operator's LSMS synchronizes the data to all NPDBs within the network and sends the confirmation, when the in-carrying provincial SOA receives the effectiveness result notification message, it sends back an effectiveness result confirmation, notifies the user that the NP service has been successfully processed, and notifies the in-carrying CRM that the number portability has been successful, and performs the in-carrying completion process;

[0239] The second sending module 23 is further configured to send back an effectiveness result confirmation message to the CSMS, delete the service data of the user within the local network, and notify the out-carrying CRM that the number portability has been successful, and perform the out-carrying completion process.

[0240] Further, the out-carrying completion process includes:

[0241] Performing a restricted call operation on the corresponding IMSI on the NPMSC for the out-carrying user; invoking an online instruction through the out-carrying CRM to update the status of the IMSI on the corresponding NPMSC, and at the same time performing corresponding processing on the user information in the CRM / OCS / SCP.

[0242] The number portability management system of the embodiments of the present disclosure is used to implement the number portability management methods in Embodiment 1 and Embodiment 2 of the method. Therefore, the description is relatively simple. For specific details, reference can be made to the relevant descriptions in Embodiment 1 to Embodiment 3 of the previous method, and details will not be repeated here.

[0243] In addition, as Figure 9 shown, Embodiment 5 of the present disclosure further provides an electronic device, including a memory 100 and a processor 200. A computer program is stored in the memory 100. When the processor 200 runs the computer program stored in the memory 100, the processor 200 executes the above various possible methods.

[0244] Among them, the memory 100 is connected to the processor 200. The memory 100 can be a flash memory, a read-only memory, or other memories. The processor 200 can be a central processing unit or a single-chip microcomputer.

[0245] In addition, the embodiments of the present disclosure further provide a computer-readable storage medium, on which a computer program is stored, and the computer program is executed by the processor to implement the above various possible methods.

[0246] The computer-readable storage medium includes volatile or non-volatile, removable or non-removable media implemented in any method or technology for storing information such as computer-readable instructions, data structures, computer program modules, or other data. The computer-readable storage medium includes, but is not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory), flash memory or other memory technologies, CD-ROM (Compact Disc Read-Only Memory), digital versatile disc (DVD, Digital Video Disc) or other optical disc storage, magnetic cassette, tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer.

[0247] It can be understood that the above embodiments are merely exemplary embodiments adopted to illustrate the principles of the present disclosure. However, the present disclosure is not limited thereto. For those of ordinary skill in the art, various modifications and improvements can be made without departing from the spirit and essence of the present disclosure, and these modifications and improvements are also regarded as the protection scope of the present disclosure.

Claims

1. A management method for number portability, characterized in that, the method includes: After the service request management SOA of the number portability business in the province of the incoming party receives the request for the number portability (NP) application, it initiates an NP application request to the centralized service management system (CSMS) through the SOA of the headquarters of the incoming party, so that after the CSMS receives the NP application request, it confirms whether to accept this application. If it accepts, it forwards the application request message to the SOA of the province of the outgoing party through the SOA of the headquarters of the outgoing party, so that the SOA of the province of the outgoing party initiates a judgment on the eligibility of the user's number portability to the customer relationship management (CRM) of the province of the outgoing party. After the CRM of the province of the outgoing party confirms that this application is qualified, the SOA of the province of the outgoing party sends the qualified result to the CSMS through the SOA of the headquarters of the outgoing party, and the CSMS sends the application result to the SOA of the province of the incoming party through the SOA of the headquarters of the incoming party; The SOA of the province of the incoming party notifies the CRM of the province of the incoming party of the confirmation of the NP application, and realizes the product ordering of the NP customer through the order management module of the CRM of the province of the incoming party; The SOA of the province of the incoming party completes the NP effect processing through the interaction between the SOA of the headquarters of the incoming party and the CSMS.

2. The method according to claim 1, characterized in that, the process that the SOA of the province of the incoming party completes the NP effect processing through the interaction between the SOA of the headquarters of the incoming party and the CSMS includes: The SOA of the province of the incoming party sends an effect request message to the CSMS through the SOA of the headquarters of the incoming party, so that the CSMS packs the NP data of the received effect request message and sends an effect broadcast indication message to the local service management systems (LSMSs) of all local operators, so that each operator's LSMS synchronizes the data to all the number portability databases (NPDBs) in the network, and the CSMS sends a successful effect result notification message to the SOA of the province of the incoming party and the SOA of the province of the outgoing party respectively after receiving the successful effect broadcast confirmations of all LSMSs, so that after the SOA of the province of the outgoing party receives the effect result notification message, it sends back an effect result confirmation message and deletes the service data of this user in its own network, and notifies the CRM of the outgoing party that the number portability is successful and performs the completion processing of the outgoing party; After the SOA of the province of the incoming party receives the effect result notification message, it sends back an effect result confirmation and notifies the user that the NP service has been successfully processed; The SOA of the province of the incoming party notifies the CRM of the province of the incoming party that the number portability is successful and performs the completion processing of the incoming party.

3. The method according to claim 1, characterized in that, the method further includes: During the process of message forwarding between the SOA of the headquarters of the incoming party and the SOA of the headquarters of the outgoing party, a timer is used to monitor the timeliness of message processing.

4. The method according to claim 1, characterized in that, the method further includes: If the CSMS determines to reject this NP application after receiving the NP application request, the SOA of the province of the incoming party receives the application rejection response message sent by the CSMS to the SOA of the province of the incoming party through the SOA of the headquarters of the incoming party, and the reason for the rejection is carried in the application rejection response message; The SOA of the province of the incoming party records the result of this NP application and notifies the CRM of the province of the incoming party.

5. The method according to claim 2, characterized in that, The completion processing of the port-in party includes: After the provincial SOA of the port-in party notifies the port-in party CRM that the number has been successfully transferred, the port-in party CRM establishes formal user information and subscription relationships based on the pre-acceptance information; The provincial SOA of the port-in party calls the number portability home location register NPHLR account opening interface through the port-in party CRM system to complete the binding relationship between the international mobile subscriber identity IMSI number and the ported-in mobile phone number; If the user applies for a pre-paid subscription service, the provincial SOA of the port-in party calls the service control point SCP / real-time charging system OCS interface through the port-in party CRM system to activate the pre-paid service on the SCP / OCS.

6. A management method for number portability Characterized in that The method includes: The provincial SOA of the port-out party receives the application request message forwarded by the CSMS through the headquarters SOA of the port-out party. The application request message is sent by the CSMS after receiving the NP application request and confirming the receipt of this application. The NP application request is initiated by the provincial SOA of the port-in party to the CSMS through the headquarters SOA of the port-in party after receiving the NP application request; Initiate a judgment on the eligibility of the user for number portability to the provincial CRM; After the port-out party CRM confirms that the application is qualified, the provincial SOA of the port-out party sends the qualified result to the CSMS through the headquarters SOA of the port-out party. The CSMS sends the application result to the provincial SOA of the port-in party through the headquarters SOA of the port-in party, enabling the provincial SOA of the port-in party to notify the provincial CRM of the port-in party of the NP application confirmation, and realizing the product subscription of the NP customer through the order management module of the provincial CRM of the port-in party. In addition, the provincial SOA of the port-in party completes the NP activation process through the interaction with the CSMS through the headquarters SOA of the port-in party.

7. The method according to claim 6 Characterized in that The method further includes: The provincial SOA of the port-out party receives the successful activation result notification message sent by the CSMS. The successful activation result notification message is sent by the CSMS to the provincial SOA of the port-out party and the provincial SOA of the port-in party after receiving the successful activation broadcast confirmations from all LSMSs. The activation broadcast confirmation is sent after the provincial SOA of the port-in party sends an activation request message to the CSMS through the headquarters SOA of the port-in party, enabling the CSMS to package the NP data of the received activation request message and send an activation broadcast indication message to all LSMSs of local operators. After each operator LSMS synchronizes the data to all NPDBs within the network and sends it out, and after the provincial SOA of the port-in party receives the activation result notification message, it sends back an activation result confirmation, notifies the user that the NP service has been successfully processed, and notifies the port-in party CRM that the number has been successfully transferred, and performs the completion processing of the port-in party; Send back an activation result confirmation message to the CSMS, delete the service data of this user within the local network, and notify the port-out party CRM that the number has been successfully transferred, and perform the completion processing of the port-out party.

8. The method according to claim 7 Characterized in that The completion processing of the port-out party includes: For the outgoing user, perform restricted call operations on the corresponding IMSI at the Number Portability Mobile Switching Center (NPMSC); call the online instruction through the CRM of the outgoing party to update the status of the IMSI on the corresponding NPMSC, and at the same time perform corresponding processing on the user information in the CRM / OCS / SCP.

9. A management system for number portability Characterized in that The system includes the provincial SOA of the incoming party, and the provincial SOA of the incoming party includes: The first sending module is configured to, after receiving the request for NP application, initiate an NP application request to the CSMS through the headquarter SOA of the incoming party, so that after the CSMS receives the NP application request, it confirms whether to accept this application. If it accepts, it forwards the application request message to the provincial SOA of the outgoing party through the headquarter SOA of the outgoing party, so that the provincial SOA of the outgoing party initiates a user portability eligibility judgment to the provincial CRM of the outgoing party. After the provincial CRM of the outgoing party confirms that the application is qualified, the provincial SOA of the outgoing party sends the qualified result to the CSMS through the headquarter SOA of the outgoing party, and the CSMS sends the application result to the provincial SOA of the incoming party through the headquarter SOA of the incoming party; The product ordering module is configured to notify the provincial CRM of the incoming party of the NP application confirmation and implement the product ordering of the NP customer through the order management module of the provincial CRM of the incoming party; The NP activation module is configured to complete the NP activation process through the interaction between the provincial SOA of the incoming party and the CSMS via the headquarter SOA of the incoming party.

10. A management system for number portability Characterized in that The system includes the provincial SOA of the outgoing party, and the provincial SOA of the outgoing party includes: The receiving module is configured to receive the application request message forwarded by the CSMS through the headquarter SOA of the outgoing party. The application request message is sent by the CSMS after receiving the NP application request and confirming to accept this application. The NP application request is initiated by the provincial SOA of the incoming party to the CSMS through the headquarter SOA of the incoming party after receiving the request for NP application; The judgment module is configured to initiate a user portability eligibility judgment to the provincial CRM; The second sending module is configured to, after the provincial CRM of the outgoing party confirms that the application is qualified, send the qualified result to the CSMS through the headquarter SOA of the outgoing party, and the CSMS sends the application result to the provincial SOA of the incoming party through the headquarter SOA of the incoming party, so that the provincial SOA of the incoming party notifies the provincial CRM of the incoming party of the NP application confirmation, implements the product ordering of the NP customer through the order management module of the provincial CRM of the incoming party, and completes the NP activation process through the interaction between the provincial SOA of the incoming party and the CSMS via the headquarter SOA of the incoming party.

11. An electronic device Characterized in that It includes a memory and a processor. A computer program is stored in the memory. When the processor runs the computer program stored in the memory, the processor executes the management method for number portability as described in any one of claims 1-5 or claims 6-8.

12. A computer-readable storage medium Characterized in that A computer program is stored on the computer-readable storage medium. When the computer program is executed by a processor, it implements the method for managing number portability as described in any one of claims 1-5 or claims 6-8.

Images