Processing mechanism method for number portability number short message pushing

Abstract

The invention discloses a processing mechanism method for pushing a number portability number short message, which belongs to the field of short-term load prediction, and comprises the following steps of: S1, creating a central database, and recording and regularly updating number portability numbers and new operator information thereof; s2, identifying a number which may fail to send due to number portability by intelligently analyzing the receipt code; s3, inquiring number information in a number portability library; if no local record exists, an external number portability interface is called, latest number information is obtained, and a database is updated; s4, resending the short message through a corresponding new operator channel according to the latest operator information, and monitoring the resent receipt; and S5, processing the receipt according to a reissuing result, and ensuring that final successful receipt information is transmitted to a downstream platform. Beneficial effects are as follows. (1) a distributed database architecture is adopted; and (2) introducing a real-time notification and confirmation machine of a user side. And (3) establishing a cross-operator cooperation protocol.

Description

Technical Field

[0001] The present invention relates to the field of number portability, and more specifically, to a processing mechanism method for pushing text messages of number portability numbers. Background Art

[0002] The introduction of the number portability service allows users to freely choose operators without changing their phone numbers. This policy has greatly enhanced users' right to choose independently. However, the popularity of number portability has also brought new technical challenges, especially in the field of SMS push. Since the number portability databases of various operators are not shared in real time, the SMS channel of the original operator will continue to send SMS to the number after the user completes the number portability. Such SMS cannot be delivered correctly, resulting in interruption of information transmission. Traditional SMS push systems lack the ability to identify and process number portability numbers in real time, and often rely on outdated operator information, resulting in a large number of SMS failures or delays.

[0003] To address this problem, a new processing mechanism has emerged. This mechanism intelligently identifies the error code in the SMS receipt, preliminarily determines that the sending failure may be caused by number portability, and obtains the latest number-to-carrier information by querying a unified number portability database or an external real-time interface, thereby ensuring the success rate of SMS push. This method has obvious advantages in improving the success rate of SMS sending and user experience, but it also faces some shortcomings, such as real-time query may increase system burden and delay. In addition, the maintenance and update of the number portability database also requires additional resources. Therefore, although this mechanism has outstanding performance in improving the efficiency of number portability SMS processing, it still needs to be further improved in terms of system performance optimization and database management. Summary of the invention

[0004] The present invention proposes a processing mechanism method for SMS push of number portability numbers to solve the above-mentioned problems: The popularity of number portability has also brought new technical challenges, especially in the field of SMS push. Since the number portability databases of various operators cannot be shared in real time, after the user completes the number portability, the SMS channel of the original operator will continue to send SMS to the number. Such SMS cannot be delivered correctly, resulting in interruption of information transmission. Traditional SMS push systems lack the ability to identify and process number portability numbers in real time, and often rely on outdated operator information, resulting in a large number of SMS failures or delays.

[0005] Technical solution: A method for processing SMS push of a number portability number, a method for processing SMS push of a number portability number includes the following steps:

[0006] S1. Create a central database to record and regularly update the ported numbers and their new operators;

[0007] S2. Through intelligent analysis of receipt codes, identify numbers that may have failed to send due to number portability;

[0008] S3. First, query the number information in the number portability database; if there is no local record, call the external number portability interface to obtain the latest number information and update the database;

[0009] S4. Resend the SMS through the corresponding new operator channel according to the latest operator information and monitor the receipt after resending;

[0010] S5. Process the receipt according to the resending result, including if the resending is successful, then pass the successful receipt to the downstream platform; including if the resending fails, analyze the cause of the error again, decide whether further processing is needed and inform the downstream platform of the specific reason for the failure.

[0011] Preferably, when S2 receives the receipt code sent by SMS, it analyzes the error code in the receipt, identifies which errors may be caused by number portability, and excludes error codes indicating invalid number and sending failure;

[0012] Configure a mapping table of error codes and number portability correlations to quickly match and identify numbers that may be involved in number portability.

[0013] Preferably, configuring a mapping table of error codes and number portability correlations comprises the following steps:

[0014] S2-1. Obtain all possible receipt error codes from the SMS sending platform, especially those related to SMS sending failures;

[0015] S2-2. Analyze the meaning of each error code, especially the codes related to number status, including "Invalid Number", "Unreachable", and "Carrier Unavailable";

[0016] S2-3. Associate the error code with situations that may be caused by number portability, including situations where the number has been ported but the transmission is still on the original operator's channel, and the number has been transferred to another operator but has not been updated in a timely manner;

[0017] S2-4. Assign a weight and mark related to number portability to each of the error codes to identify whether a number portability query is required;

[0018] S2-5. Use Excel to create a table containing the error code, error description, and number portability relevance mark; use "high", "medium", and "low" to mark the relevance of number portability;

[0019] S2-6. Integrate the mapping table into the SMS processing system. When the system receives the receipt code, it automatically searches for the relevance mark in the mapping table; if the relevance mark corresponding to the receipt code reaches the preset threshold "high", the number portability query process is triggered.

[0020] Preferably, after the S3 performs a preliminary number portability database query for the identified number and identifies the number that may be ported, it first queries the local number portability database to check whether the number has been ported and obtains the new operator information;

[0021] If the query yields a result, the new operator information of the number is obtained and the SMS is prepared to be resent;

[0022] If there is no result in the query, the external number portability interface is called to perform real-time query;

[0023] The new information retrieved through the external interface is recorded in the number portability database for subsequent query.

[0024] Preferably, an intelligent caching mechanism is introduced to temporarily store the number portability information recently queried locally. For text messages repeatedly sent to the same number within a short period of time, the operator information in the cache is directly used; the cache content is dynamically adjusted according to the frequency of number use and the query success rate to ensure that high-frequency numbers always have the latest operator information.

[0025] Preferably, building the intelligent cache mechanism includes the following steps:

[0026] Design cache data structures, including hash tables and bidirectional linked lists, for fast query and update of cache data; each record in the cache contains the number, operator information, last query timestamp, and expiration time;

[0027] Use in-memory data structures to cache frequently used phone number information, read it with the fastest response time, and store the cached information in a local database to retain some cached data after the system restarts;

[0028] Set up scheduled tasks to refresh the cache regularly based on the last query timestamp and expiration time of the number, and update and delete expired data; dynamically adjust the cache size and strategy based on system load and cache hit rate.

[0029] Preferably, constructing the intelligent caching mechanism further comprises the following steps:

[0030] Before sending a text message, first check whether the number exists in the cache, including if the number exists in the cache and has not expired, directly use the operator information in the cache to send the text message to avoid real-time query; including if the number is not in the cache, trigger a real-time query, update the query result to the cache, and continue to send the text message;

[0031] The number operator information queried in real time and the number change information obtained through other channels should be updated to the cache immediately;

[0032] Set an expiration time for each cache record, and automatically delete and update the record when it expires to prevent the use of outdated data; when a failure to send an SMS is detected, the cache invalidation mechanism can be actively triggered to force the deletion and update of related number information from the cache.

[0033] Preferably, the number portability information is stored in multiple nodes through a distributed database architecture to improve the speed and reliability of data query; for operator users in different regions, the system implements regional data synchronization and gives priority to querying database nodes in the same region as the target number.

[0034] Preferably, a text message notification function is introduced on the user side. When the number is identified as a number for number portability and the text message needs to be resent, the user receives a confirmation text message, allowing the user to choose whether to receive the text message; when the user completes the number portability, the update mechanism of the text message push system is immediately triggered to ensure that the information in the number portability library is synchronized to the latest status, thereby reducing sending failures caused by delayed updates.

[0035] Preferably, a cross-operator cooperation agreement is established to directly share the data of number portability users and reduce the number of times reliance on real-time queries.

[0036] Compared with the prior art, the advantages of the present invention are:

[0037] (1) A distributed database architecture is used to store number portability information on multiple nodes, which improves query speed and system scalability. The distributed architecture also improves the fault tolerance of the system. Even if some nodes fail, the system can continue to operate, ensuring the continuity and reliability of SMS push.

[0038] (2) Introduce a real-time notification and confirmation mechanism on the user side. When the system identifies that the number may have been ported, it sends a confirmation SMS to the user, and the user can choose whether to receive the SMS. This mechanism not only improves the user experience, but also effectively reduces unnecessary SMS sending and avoids wasting resources.

[0039] (3) By establishing a cross-operator cooperation agreement, direct sharing of number portability information can be achieved. This direct data sharing can obtain the latest operator information of users more quickly, reduce dependence on external queries, and further improve the success rate and efficiency of SMS sending.

[0040] (4) Intelligent error receipt processing can be classified and processed according to the type of error code and historical data. For example, for error codes that may involve number portability, the system automatically triggers further query and reissue processes, while for other error codes, different processing strategies are adopted. This refined processing can reduce unnecessary reissue operations and improve overall processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 The present invention is a schematic diagram of the overall process of a method for processing a number portability number SMS push. DETAILED DESCRIPTION

[0042] For examples, see Figure 1 In a method for processing a mobile number portability number SMS push, the method comprises:

[0043] S1. Create a central database to record and regularly update the ported numbers and their new operators;

[0044] S2. Through intelligent analysis of receipt codes, identify numbers that may have failed to send due to number portability;

[0045] S3. First, query the number information in the number portability database; if there is no local record, call the external number portability interface to obtain the latest number information and update the database;

[0046] S4. Resend the SMS through the corresponding new operator channel according to the latest operator information and monitor the receipt after resending;

[0047] S5. Process the receipt according to the resending result, including if the resending is successful, then pass the successful receipt to the downstream platform; including if the resending fails, analyze the cause of the error again, decide whether further processing is needed and inform the downstream platform of the specific reason for the failure.

[0048] When S2 receives the receipt code sent by SMS, it analyzes the error code in the receipt, identifies which errors may be caused by number portability, and excludes error codes indicating invalid number and sending failure;

[0049] Configure a mapping table of error codes and number portability correlations to quickly match and identify numbers that may be involved in number portability.

[0050] Configuring a mapping table of error codes and number portability correlations includes the following steps:

[0051] S2-1. Obtain all possible receipt error codes from the SMS sending platform, especially those related to SMS sending failures;

[0052] S2-2. Analyze the meaning of each error code, especially the codes related to number status, including "Invalid Number", "Unreachable", and "Carrier Unavailable";

[0053] S2-3. Associate the error code with situations that may be caused by number portability, including situations where the number has been ported but the transmission is still on the original operator's channel, and the number has been transferred to another operator but has not been updated in a timely manner;

[0054] S2-4. Assign a weight and tag related to number portability to each error code to identify whether a number portability query is required;

[0055] S2-5. Use Excel to create a table containing the error code, error description, and number portability relevance mark; use "high", "medium", and "low" to mark the relevance of number portability;

[0056]

[0057] S2-6. Integrate the mapping table into the SMS processing system. When the system receives the receipt code, it automatically searches for the relevance mark in the mapping table; if the relevance mark corresponding to the receipt code reaches the preset threshold "high", the number portability query process is triggered.

[0058] S3: After the number that may be ported is identified, the local number portability database is first queried to check whether the number has been ported and obtain the new operator information;

[0059] If the query yields a result, the new operator information of the number is obtained and the SMS is prepared to be resent;

[0060] If there is no result in the query, the external number portability interface is called to perform real-time query;

[0061] The new information retrieved through the external interface is recorded in the number portability database for subsequent query.

[0062] An intelligent caching mechanism is introduced to temporarily store the recently queried number portability information locally. For text messages sent repeatedly to the same number within a short period of time, the operator information in the cache is used directly. The cache content is dynamically adjusted according to the frequency of number use and the query success rate to ensure that high-frequency numbers always have the latest operator information.

[0063] Building an intelligent caching mechanism includes the following steps:

[0064] Design cache data structures, including hash tables and bidirectional linked lists, for fast query and update of cache data; each record in the cache contains the number, operator information, last query timestamp, and expiration time;

[0065] Use in-memory data structures to cache frequently used phone number information, read it with the fastest response time, and store the cached information in a local database to retain some cached data after the system restarts;

[0066] Set up scheduled tasks to refresh the cache regularly based on the last query timestamp and expiration time of the number, and update and delete expired data; dynamically adjust the cache size and strategy based on system load and cache hit rate.

[0067] Building an intelligent caching mechanism also includes the following steps:

[0068] Before sending a text message, first check whether the number exists in the cache, including if the number exists in the cache and has not expired, directly use the operator information in the cache to send the text message to avoid real-time query; including if the number is not in the cache, trigger a real-time query, update the query result to the cache, and continue to send the text message;

[0069] The number operator information queried in real time and the number change information obtained through other channels should be updated to the cache immediately;

[0070] Set an expiration time for each cache record, and automatically delete and update the record when it expires to prevent the use of outdated data; when a failure to send an SMS is detected, the cache invalidation mechanism can be actively triggered to force the deletion and update of related number information from the cache.

[0071] Through the distributed database architecture, number portability information is stored in multiple nodes, improving the speed and reliability of data query; for operator users in different regions, the system realizes regional data synchronization and gives priority to querying database nodes in the same region as the target number.

[0072] Specifically, a distributed database architecture is designed, and a distributed database system such as Cassandra, MongoDB, or Amazon DynamoDB is used to distribute the number portability data on multiple nodes.

[0073] Data sharding and synchronization: Data is sharded and stored by region or number segment to ensure fast response to data queries. Automated data synchronization and load balancing are achieved through cluster management tools (such as Kubernetes) to ensure high availability and fault tolerance.

[0074] Fault handling: Design an automatic fault detection and switching mechanism. When a problem occurs on a node, the system can automatically switch to other nodes to ensure the continuity and reliability of data query.

[0075] A user-side SMS notification function is introduced. When a number is identified as a number for number portability and the SMS needs to be resent, the user receives a confirmation SMS, allowing the user to choose whether to receive the SMS. When the user completes the number portability, the update mechanism of the SMS push system is immediately triggered to ensure that the information in the number portability library is synchronized to the latest status, reducing the sending failure caused by delayed updates.

[0076] Specifically, a user notification module is added to the SMS push system. When the system detects that a number may not be able to receive SMS due to number portability, a confirmation SMS is sent to the user to notify the user that their number status has changed and ask the user to confirm whether to accept the SMS.

[0077] User feedback processing: Based on the user's feedback (accept or reject the SMS), the system will dynamically adjust the sending strategy. If the user confirms to receive the SMS, the operator information in the cache is updated and resent. If the user rejects, the system terminates the subsequent operations.

[0078] Privacy protection: Ensure that the user's privacy is protected. When implementing the confirmation mechanism, use encrypted channels and double verification mechanisms to prevent user information leakage.

[0079] Establish cross-operator cooperation agreements to directly share data on number portability users and reduce the number of times they rely on real-time queries.

[0080] Specifically, negotiate with major operators to develop a number portability data sharing agreement. The agreement should include the frequency, format and security requirements of data updates to ensure that all parties can obtain accurate data in a timely manner.

[0081] Data interface development: Develop API interfaces across operators to achieve real-time data sharing and synchronization. The interface should support high concurrent access to ensure the stability of data synchronization during peak hours.

[0082] Data security and compliance: Develop and implement strict data security measures to prevent number portability data from being tampered with or leaked during transmission and storage. Ensure that protocols and system designs comply with local privacy protection regulations.

[0083] The above shows and describes the basic principles, main features and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited by the above embodiments. The above embodiments and descriptions are only preferred examples of the present invention and are not intended to limit the present invention. Without departing from the spirit and scope of the present invention, the present invention may have various changes and improvements, which fall within the scope of the present invention. The scope of protection of the present invention is defined by the attached claims and their equivalents.

Claims

1. A method for processing a number portability SMS push, characterized in that: A method for processing a number portability SMS push includes the following steps: S1. Create a central database to record and regularly update the ported numbers and their new operators; S2. Through intelligent analysis of receipt codes, identify numbers that may have failed to send due to number portability; S3. First, query the number information in the number portability database; if there is no local record, call the external number portability interface to obtain the latest number information and update the database; S4. Resend the SMS through the corresponding new operator channel according to the latest operator information and monitor the receipt after resending; S5. Process the receipt according to the resending result, including if the resending is successful, then pass the successful receipt to the downstream platform; including if the resending fails, analyze the cause of the error again, decide whether further processing is needed and inform the downstream platform of the specific reason for the failure.

2. According to claim 1, a method for processing a number portability SMS push, characterized in that: When the S2 receives the receipt code sent by the SMS, it analyzes the error code in the receipt, identifies which errors may be caused by number portability, and excludes error codes indicating invalid number and sending failure; Configure a mapping table of error codes and number portability correlations to quickly match and identify numbers that may be involved in number portability.

3. A method for processing a number portability SMS push according to claim 2, characterized in that: Configuring a mapping table of error codes and number portability correlations includes the following steps: S2-1. Obtain all possible receipt error codes from the SMS sending platform, especially those related to SMS sending failures; S2-2. Analyze the meaning of each error code, especially the codes related to number status, including "Invalid Number", "Unreachable", and "Carrier Unavailable"; S2-3. Associate the error code with situations that may be caused by number portability, including situations where the number has been ported but the transmission is still on the original operator's channel, and the number has been transferred to another operator but has not been updated in a timely manner; S2-4. Assign a weight and mark related to number portability to each of the error codes to identify whether a number portability query is required; S2-5. Use Excel to create a table containing the error code, error description, and number portability relevance mark; use "high", "medium", or "low" to mark the relevance of number portability; S2-6. The mapping table is integrated into the SMS processing system. When the system receives the receipt code, it automatically searches for the relevance tag in the mapping table; including the relevance tag corresponding to the receipt code reaches the preset threshold "high", which triggers the number portability query process.

4. A method for processing a number portability SMS push according to claim 1, characterized in that: After the S3 searches the preliminary number portability database for the identified number and identifies the number that may be ported, it first searches the local number portability database to check whether the number has been ported and obtains the new operator information; If the query yields a result, the new operator information of the number is obtained and the SMS is prepared to be resent; If there is no result in the query, the external number portability interface is called to perform real-time query; The new information retrieved through the external interface is recorded in the number portability database for subsequent query.

5. A method for processing a number portability SMS push according to claim 1, characterized in that: An intelligent caching mechanism is introduced to temporarily store the recently queried number portability information locally. For text messages repeatedly sent to the same number within a short period of time, the operator information in the cache is directly used. The cache content is dynamically adjusted according to the frequency of number use and the query success rate to ensure that high-frequency numbers always have the latest operator information.

6. A method for processing a number portability SMS push according to claim 5, characterized in that: Building the intelligent caching mechanism includes the following steps: Design cache data structures, including hash tables and bidirectional linked lists, for fast query and update of cache data; each record in the cache contains the number, operator information, last query timestamp, and expiration time; Use in-memory data structures to cache frequently used phone number information, read it with the fastest response time, and store the cached information in a local database to retain some cached data after the system restarts; Set up scheduled tasks to refresh the cache regularly based on the last query timestamp and expiration time of the number, and update and delete expired data; dynamically adjust the cache size and strategy based on system load and cache hit rate.

7. A method for processing a number portability SMS push according to claim 5, characterized in that: The construction of the intelligent caching mechanism also includes the following steps: Before sending a text message, first check whether the number exists in the cache, including if the number exists in the cache and has not expired, directly use the operator information in the cache to send the text message to avoid real-time query; including if the number is not in the cache, trigger a real-time query, update the query result to the cache, and continue to send the text message; The number operator information queried in real time and the number change information obtained through other channels should be updated to the cache immediately; Set an expiration time for each cache record, and automatically delete and update the record when it expires to prevent the use of outdated data; when a failure to send an SMS is detected, the cache invalidation mechanism can be actively triggered to force the deletion and update of related number information from the cache.

8. A method for processing a number portability SMS push according to claim 5, characterized in that: Through a distributed database architecture, number portability information is stored in multiple nodes, improving the speed and reliability of data query; for operator users in different regions, the system implements regional data synchronization and gives priority to querying database nodes in the same region as the target number.

9. A method for processing a number portability SMS push according to claim 1, characterized in that: Introducing the SMS notification function on the user side. When a number is identified as a ported number and SMS needs to be resent, the user receives a confirmation SMS, allowing the user to choose whether to receive the SMS; When the user completes the number portability, the SMS push system's update mechanism is immediately triggered to ensure that the information in the number portability database is synchronized to the latest status, reducing sending failures caused by delayed updates.

10. A method for processing a number portability SMS push according to claim 1, characterized in that: Establish cross-operator cooperation agreements to directly share data on number portability users and reduce the number of times they rely on real-time queries.

Images