Risk prevention method, device and system for secondary number allocation of telephone number, and medium
Through the collaborative work of the telecom operator business system and the SMS platform, the secondary number is obtained and unbinding, which solves the risks brought by secondary number release, achieves full coverage and security, and avoids the hidden dangers brought by secondary number release and dispute.
Patent Information
- Application Number
- CN202411132159.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-16
- Publication Date
- 2024-11-15
AI Technical Summary
When solving the risks brought by secondary number release of telephone numbers, the existing technology lacks coverage and limited applicable scenarios, and cannot completely avoid hidden dangers and disputes brought about by secondary number release.
Obtain the secondary number that needs to be cleaned through the telecom operator business system and send it to the SMS platform, add the secondary number to clean the whitelist library, and obtain the number from the database regularly or irregularly, and perform account unbinding processing. Ensure full coverage and security.
Full coverage of secondary number distribution users has been achieved, unnecessary burdens for individual users has been reduced, simple, convenient, comprehensive and completely eliminated the hidden dangers of secondary number distribution, and solved the problem of insufficient coverage and limited applicable scenarios.
Smart Images

Figure CN118972828A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of network technology, and in particular to a method, device, system and medium for preventing the risk of secondary release of telephone numbers. Background Art
[0002] In the Internet era, various applications have begun to penetrate into all aspects of people's work and life, bringing great convenience and efficiency to individuals while also promoting the progress of the entire society. Correspondingly, mobile phones have evolved from simple communication tools to indispensable primary necessities. As operators gradually put in place the real-name management of mobile phone users, mobile phone numbers have also begun to carry functions such as Internet application registration and verification, security software marking, etc., becoming the identity of the Internet world.
[0003] "Secondary release of numbers" means that after old users deactivate or abandon their mobile phone numbers, the numbers are taken back by the operators, left vacant for a period of time, and then put on the market again for new users to choose. As of the beginning of 2024, the total number of mobile phone users of China's three major operators has exceeded 2 billion. In the face of a large number of users, mobile phone numbers are also a scarce resource. "Secondary release of numbers" can recycle number resources and is a necessary means to effectively activate idle communication resources. This has also been a common practice internationally. The reality brought about by this is that for various reasons, when users give up their original numbers, they often forget to unbind or cancel the various Internet application accounts that have been registered and bound to their mobile phone numbers. With the emergence of "secondary release of numbers", the privacy of old users may face great risks, and new users may also suffer endless harassment left by old users. While causing unnecessary disputes to new and old users, telecom operators are also facing corresponding user complaints.
[0004] However, existing solutions have problems such as insufficient coverage, limited applicable scenarios or user groups, and the inability to completely avoid the risks brought by secondary release of numbers. Summary of the invention
[0005] The technical problem to be solved by the present invention is to address the above-mentioned deficiencies in the prior art and to provide a method, device, system and medium for preventing the risks of secondary release of telephone numbers, so as to solve the problems that the existing solutions for secondary release of numbers have insufficient coverage, limited applicable scenarios or user groups, and cannot completely avoid the risks brought by secondary release of numbers.
[0006] In a first aspect, the present invention provides a method for preventing the risk of secondary release of a telephone number, which is applied to a business system of a telecommunications operator, and the method comprises:
[0007] Get the secondary number that needs to be cleaned;
[0008] The secondary numbers that need to be cleaned are sent to the telecommunications operator's SMS platform, so that the telecommunications operator's SMS platform adds the secondary numbers that need to be cleaned to the secondary number cleaning whitelist library, and enables the application service provider to obtain the secondary numbers that need to be cleaned in the secondary number cleaning whitelist library regularly / irregularly, and unbind the secondary numbers that need to be cleaned and the corresponding accounts.
[0009] Further, the obtaining of the secondary number to be cleared includes at least one of the following:
[0010] In response to the number selected by the current user when opening a new card being a secondary number, the number selected by the current user when opening a new card is used as the secondary number that needs to be cleared;
[0011] In response to receiving a complaint from a current user of the secondary number regarding failure of the user of the original number to unbind the relevant application account, taking the secondary number corresponding to the complaint as the secondary number that needs to be cleared;
[0012] In response to the number confirmed by the current user during porting or transfer, the confirmed number is used as the secondary number that needs to be cleared;
[0013] In response to the number after the cancellation of the account exceeding the freezing period, the number after the cancellation of the account is used as the secondary number that needs to be cleared;
[0014] In response to the number corresponding to the user who is forced to dismantle the phone having exceeded the freezing period, the number corresponding to the user who is forced to dismantle the phone is used as the secondary number that needs to be cleared.
[0015] In a second aspect, the present invention provides a method for preventing the risk of secondary release of a telephone number, which is applied to a short message platform of a telecommunications operator, and the method comprises:
[0016] Receiving the secondary number to be cleared sent by the telecommunications operator's business system after acquiring the secondary number to be cleared;
[0017] The secondary numbers that need to be cleaned are added to the secondary number cleanup whitelist library, so that the application service provider can obtain the secondary numbers that need to be cleaned in the secondary number cleanup whitelist library regularly / irregularly, and unbind the secondary numbers that need to be cleaned and the corresponding accounts.
[0018] Further, the adding of the secondary number to be cleaned up to the secondary number cleanup whitelist library specifically includes:
[0019] The secondary numbers that need to be cleared and the corresponding joining time are saved in the secondary number clearing whitelist library.
[0020] Furthermore, the method further comprises:
[0021] receiving a first return code returned by the application service provider indicating that the binding has been untied; or,
[0022] receiving a second return code returned by the application service provider to indicate that the application service provider is not involved;
[0023] The first return code and the second return code are the same.
[0024] Furthermore, the method further comprises:
[0025] Receive a text message sending request from an application service provider, wherein the text message sending request carries a target number;
[0026] Determine whether the target number is a second-time number;
[0027] In response to the target number being a second-time released number, determining whether the application service provider has already processed the target number;
[0028] In response to the application service provider's feedback that the target number has been processed, sending a text message according to the text message sending request, and feeding back to the application service provider that the text message has been successfully sent;
[0029] In response to the application service provider not feeding back the processing of the target number, feeding back to the application service provider that the SMS sending failed.
[0030] In a third aspect, the present invention provides a method for preventing the risk of secondary release of a telephone number, which is applied to an application service provider, and the method comprises:
[0031] Obtaining secondary numbers that need to be cleaned from a secondary number cleanup whitelist library from a telecommunications operator's SMS platform at regular / irregular times; wherein the telecommunications operator's business system obtains the secondary numbers that need to be cleaned, and sends the secondary numbers that need to be cleaned to the telecommunications operator's SMS platform, so that the telecommunications operator's SMS platform adds the secondary numbers that need to be cleaned to the secondary number cleanup whitelist library;
[0032] The secondary number that needs to be cleared and the corresponding account are unbound.
[0033] Further, the timing / irregularity of obtaining the secondary numbers that need to be cleared from the secondary number clearing whitelist library from the telecommunications operator's SMS platform specifically includes:
[0034] Obtain the secondary numbers that need to be cleared from the secondary number clearing whitelist library and the corresponding joining time from the telecom operator's SMS platform on a regular / irregular basis;
[0035] The unbinding process of the secondary number to be cleared and the corresponding account specifically includes:
[0036] Determine whether the secondary number to be cleared is bound to the corresponding account according to the local account mobile phone number binding relationship;
[0037] In response to the secondary number that needs to be cleared being bound to a corresponding account, and the binding time is earlier than the joining time corresponding to the secondary number that needs to be cleared, unbinding the secondary number that needs to be cleared and the corresponding account;
[0038] A first return code indicating unbinding is returned to the telecommunications operator SMS platform.
[0039] Furthermore, the method further comprises:
[0040] In response to the secondary number that needs to be cleared not being bound to a corresponding account, returning a second return code indicating that it is not involved to the SMS platform;
[0041] The first return code and the second return code are the same.
[0042] Furthermore, the method further comprises:
[0043] Sending a text message sending request carrying a target number to the telecommunications operator's text message platform, so that after receiving the text message sending request, the telecommunications operator's text message platform determines whether the target number is a number that has been released for the second time; and in response to the target number being a number that has been released for the second time, determining whether the application service provider has fed back and processed the target number; and in response to the application service provider having fed back and processed the target number, sending a text message according to the text message sending request, and feeding back to the application service provider that the text message has been successfully sent; or in response to the application service provider not feeding back and processing the target number, feeding back to the application service provider that the text message has failed to be sent;
[0044] Receive a message from the telecommunications operator's SMS platform indicating that the SMS is sent successfully or fails to be sent.
[0045] In a fourth aspect, the present invention provides a risk prevention device for secondary release of a telephone number, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to implement the risk prevention method for secondary release of a telephone number as described in the first aspect, the second aspect, or the third aspect.
[0046] In a fifth aspect, an embodiment of the present invention provides a risk prevention system for secondary release of telephone numbers, including a telecom operator business system, a telecom operator SMS platform, and an application service provider;
[0047] The telecommunications operator business system is used to execute the risk prevention method for secondary release of telephone numbers described in the first aspect above;
[0048] The telecommunications operator SMS platform is used to execute the risk prevention method for secondary release of telephone numbers described in the second aspect above;
[0049] The application service provider is used to execute the risk prevention method for secondary release of telephone numbers described in the third aspect above.
[0050] In a sixth aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the risk prevention method for secondary release of a telephone number as described in the first aspect, the second aspect, or the third aspect above is implemented.
[0051] The present invention provides a method, device, system and medium for preventing the risk of secondary release of telephone numbers. First, the business system of the telecommunications operator obtains the secondary numbers that need to be cleaned; then the secondary numbers that need to be cleaned are sent to the SMS platform of the telecommunications operator, so that the SMS platform of the telecommunications operator adds the secondary numbers that need to be cleaned to the secondary number cleanup whitelist library, and enables the application service provider to obtain the secondary numbers that need to be cleaned in the secondary number cleanup whitelist library regularly / irregularly, and unbinds the secondary numbers that need to be cleaned and the corresponding accounts. The present invention makes full use of the existing systems of telecommunications operators for upgrading and improvement, and can achieve full coverage of users involved in secondary release, fundamentally solving the problems of the existing solutions for secondary release, such as insufficient coverage, limited applicable scenarios or limited user groups, and the inability to completely avoid the risks brought by secondary release, etc. It can not only reduce unnecessary burdens on individual users, but also simply, conveniently, comprehensively, thoroughly and controllably eliminate the hidden dangers of secondary release. BRIEF DESCRIPTION OF THE DRAWINGS
[0052] Figure 1 This is the first scenario involved in the existing solution for secondary number release;
[0053] Figure 2 This is the second scenario involved in the existing solution for secondary number release;
[0054] Figure 3 This is the third scenario involved in the existing solution for secondary number release.
[0055] Figure 4 This is a flow chart of a method for preventing the risk of secondary release of a telephone number according to Embodiment 1 of the present invention;
[0056] Figure 5 This is an interactive schematic diagram of a method for preventing the risk of secondary release of a telephone number according to Embodiment 1 of the present invention;
[0057] Figure 6 This is a flow chart of a method for preventing the risk of secondary release of a telephone number according to Embodiment 2 of the present invention;
[0058] Figure 7 This is a flow chart of a method for preventing the risk of secondary release of a telephone number according to Embodiment 3 of the present invention;
[0059] Figure 8 This is a schematic diagram of the structure of a device for preventing the risk of secondary release of telephone numbers according to Embodiment 4 of the present invention;
[0060] Fig. 9 This is a schematic diagram of the structure of a system for preventing the risk of secondary release of telephone numbers according to Embodiment 5 of the present invention. DETAILED DESCRIPTION
[0061] In order to enable those skilled in the art to better understand the technical solution of the present invention, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.
[0062] It should be understood that the specific embodiments and drawings described herein are only used to explain the present invention rather than to limit the present invention.
[0063] It can be understood that, in the absence of conflict, the various embodiments of the present invention and the various features in the embodiments can be combined with each other.
[0064] It can be understood that, for the convenience of description, the drawings of the present invention only show the parts related to the present invention, while the parts irrelevant to the present invention are not shown in the drawings.
[0065] It can be understood that each unit and module involved in the embodiments of the present invention may correspond to only one physical structure, or may be composed of multiple physical structures, or multiple units and modules may be integrated into one physical structure.
[0066] It can be understood that the terms "first", "second", etc. in the embodiments of the present invention are used to distinguish different objects, or to distinguish different processing of the same object, rather than to describe a specific order of objects.
[0067] It can be understood that, without conflict, the functions and steps marked in the flowcharts and block diagrams of the present invention may occur in an order different from that marked in the drawings.
[0068] It is understood that the flowcharts and block diagrams of the present invention illustrate the possible architectures, functions, and operations of the systems, devices, equipment, and methods according to the various embodiments of the present invention. Each box in the flowchart or block diagram may represent a unit, module, program segment, or code, which contains executable instructions for implementing the specified functions. Moreover, each box or combination of boxes in the block diagram and flowchart may be implemented by a hardware-based system that implements the specified functions, or may be implemented by a combination of hardware and computer instructions.
[0069] It can be understood that the units and modules involved in the embodiments of the present invention can be implemented by software or hardware. For example, the units and modules can be located in a processor.
[0070] Application Overview
[0071] At present, there are two mainstream approaches in the market to solve the problem of secondary number release:
[0072] 1. Providing services to enterprises: Telecom operators or information service providers (including application service providers and some other service providers) provide interfaces for checking whether a number is a mobile phone number that has been released for the second time. Alternatively, telecom operators can manage / connect to the account registration information system of a third-party system. When it comes to the second release of numbers, they can call the corresponding interface to notify the corresponding system service provider to perform corresponding processing.
[0073] 2. Application services for individuals: After individuals enter the corresponding identity information, they can query the account binding status that has been managed by the system, and unbind the corresponding account with the user's confirmation.
[0074] Specifically, the three scenarios involved in the existing solutions and their corresponding shortcomings are as follows:
[0075] Scene 1
[0076] Telecom operators connect with application service providers, obtain the bound phone number simultaneously, and establish a corresponding database between phone numbers and application service providers. When opening a new account, if it is found that the number is a second-time number, the previously established database is searched to obtain the corresponding application service provider, and the corresponding interface is called to notify the other party to process the account corresponding to the second-time number.
[0077] Specifically, Figure 1 As shown, when a new account is opened, the telecom operator determines whether to issue the number for the second time; if so, it notifies the number user of the change through the account data of the managed application service provider and handles the account phone number binding relationship.
[0078] Main Disadvantages:
[0079] (1) Insufficient coverage. Telecom operators can only manage a limited number of application service providers and cannot integrate and manage all relevant service providers. In addition, not all telecom operators provide this capability, so there is also the problem of insufficient coverage for application service providers.
[0080] (2) The applicable scenarios are limited. Users do not actively participate and cannot choose to retain the binding relationship for special scenarios. There is a problem of insufficient applicable scenarios.
[0081] (3) There is a risk of the core business data of application service providers spreading. In this scenario, application service providers are required to synchronize the relevant number information with telecom operators, which expands their scope of control. In particular, the core data of multiple application service providers is concentrated, which poses security risks and commercial rights issues. This also indirectly reduces the willingness of application service providers to be regulated.
[0082] Scene 2
[0083] Application service providers regularly check the bound phone number corresponding to their accounts, call the interface provided by the telecom operator, and process their own accounts based on the returned information.
[0084] Specifically, Figure 2 As shown, the application service provider confirms whether the phone number is issued for the second time through the telecom operator's secondary number issuance database periodically or through event triggering. If it is a secondary number issuance, the account phone number binding relationship is processed.
[0085] Main Disadvantages:
[0086] (1) Insufficient coverage. Not all telecom operators provide this capability, which results in insufficient coverage for application service providers.
[0087] (2) Limited timeliness: Because it is initiated by the application service provider, there is a time difference between the operator's secondary number issuance and the timeliness is limited, and the risks brought by the secondary number issuance cannot be completely avoided.
[0088] (3) There is a risk of the application service provider's core business data spreading. In this scenario, the application service provider needs to synchronize the number information involved with the telecom operator, which indirectly expands its control scope and poses security risks and commercial rights issues.
[0089] (4) Commercial impact: Telecom operators or integrators providing similar services will charge for access calls, which indirectly reduces the willingness of application service providers to use it.
[0090] Scene 3
[0091] Authoritative departments and units act as application service integrators and centralize the account and phone number data of application service providers. Users can access the applications of application service integrators and query the registered and bound applications. After confirming that unbinding is required, the application service integrator will call the application service provider capability interface to complete the unbinding and cancellation of the relevant numbers.
[0092] Specifically, Figure 3 As shown, the application service integrator collects the account phone number data of application service providers 1, ..., n and stores them in the account phone number database. The user queries the bound application account and determines whether to unbind. If so, the corresponding application is called to unbind, and the corresponding application service provider handles the account phone number binding relationship.
[0093] Main Disadvantages:
[0094] (1) Insufficient coverage. The application service providers’ management is limited in scope and cannot guarantee the integration of all relevant applications.
[0095] (2) The user group is limited, and only old users can apply for operations. If old users cannot operate for various reasons, new users cannot be processed, and the problem of secondary number release cannot be completely solved.
[0096] (3) There is a risk of the application service provider's core business data spreading. In this scenario, the application service provider needs to synchronize the relevant number information with the application service integrator, which indirectly expands its control scope and poses security risks and commercial rights issues.
[0097] In summary, existing solutions have at least problems such as insufficient coverage, limited applicable scenarios or user groups, and the inability to completely avoid the risks brought by secondary release of numbers.
[0098] In view of the above technical problems, the concept of this application is to provide a method, device, system and medium for preventing the risk of secondary release of telephone numbers. First, the telecom operator's business system obtains the secondary number that needs to be cleaned; then the secondary number that needs to be cleaned is sent to the telecom operator's SMS platform, so that the telecom operator's SMS platform adds the secondary number that needs to be cleaned to the secondary number cleanup whitelist library, and enables the application service provider to obtain the secondary number that needs to be cleaned in the secondary number cleanup whitelist library regularly / irregularly, and unbinds the secondary number that needs to be cleaned and the corresponding account. The present invention makes full use of the existing system of the telecom operator for upgrading and improvement, and can achieve full coverage of users involved in secondary release, fundamentally solving the problems of insufficient coverage, limited applicable scenarios or limited user groups, and inability to completely avoid the risks brought by secondary release in existing solutions for secondary release, etc., which can not only reduce unnecessary burdens on individual users, but also simply, conveniently, comprehensively, thoroughly and controllably eliminate the hidden dangers of secondary release.
[0099] After introducing the basic principles of the present application, various non-limiting embodiments of the present application will be described in detail with reference to the accompanying drawings.
[0100] Embodiment 1:
[0101] This embodiment provides a method for preventing the risk of secondary release of telephone numbers, which is applied to the business system of telecommunications operators, such as Figure 4 As shown, the method includes:
[0102] Step S101: Obtain the secondary number that needs to be cleared.
[0103] In this embodiment, the secondary number that needs to be cleared refers to the secondary number that needs to be confirmed whether there is an application account binding relationship with the original number user, and the secondary number that needs to be unbound if there is an application account binding relationship.
[0104] Optionally, the obtaining of the secondary number to be cleared includes at least one of the following:
[0105] In response to the number selected by the current user when opening a new card being a secondary number, the number selected by the current user when opening a new card is used as the secondary number that needs to be cleared;
[0106] In response to receiving a complaint from a current user of the secondary number regarding failure of the user of the original number to unbind the relevant application account, taking the secondary number corresponding to the complaint as the secondary number that needs to be cleared;
[0107] In response to the number confirmed by the current user during porting or transfer, the confirmed number is used as the secondary number that needs to be cleared;
[0108] In response to the number after the cancellation of the account exceeding the freezing period, the number after the cancellation of the account is used as the secondary number that needs to be cleared;
[0109] In response to the number corresponding to the user who is forced to dismantle the phone having exceeded the freezing period, the number corresponding to the user who is forced to dismantle the phone is used as the secondary number that needs to be cleared.
[0110] In this embodiment, when a user goes to the business hall to open a new card, the business system checks whether the number selected by the current user is a secondary number. If not, the card can be opened directly. If it is a secondary number, the number selected by the current user when opening the new card will be used as the secondary number that needs to be cleared, and the current user will be reminded that this number is a secondary number. It may take n working days to unbind the relevant account of the original number user.
[0111] In this embodiment, the current user of the secondary number complains that he or she has received harassing information because the user of the original number has not cancelled the application. At this time, after confirming with the user that all binding information of the old user and the current user of the number needs to be unbound, the salesperson directly operates in the business system and sets the secondary number corresponding to the complaint as the secondary number that needs to be cleared.
[0112] In this embodiment, when the current user transfers or changes the number, the salesperson and the current user confirm and use the confirmed number as the secondary number that needs to be cleared.
[0113] In this embodiment, when a user cancels his account, the business system automatically detects whether the number has exceeded the freezing period, and if it has, the number is treated as a secondary number that needs to be cleared.
[0114] In this embodiment, the business system automatically detects whether the number of the user who is forced to dismantle the phone has exceeded the freezing period, and if it has exceeded the period, the number is treated as a secondary number that needs to be cleared.
[0115] It should be noted that the above-mentioned new card opening, complaints, portability or transfer, account cancellation, and forced dismantling cover all scenarios for new and old users. For secondary numbers, both new and old users can actively apply for operations.
[0116] Step S102: Send the secondary number that needs to be cleaned to the telecommunications operator's SMS platform, so that the telecommunications operator's SMS platform adds the secondary number that needs to be cleaned to the secondary number cleaning whitelist library, and enables the application service provider to obtain the secondary number that needs to be cleaned in the secondary number cleaning whitelist library regularly / irregularly, and unbind the secondary number that needs to be cleaned and the corresponding account.
[0117] It should be noted that application service providers generally access the SMS platform of telecom operators as SP (Service Provider: direct provider of Internet service content application services). Therefore, based on the SP information that has been connected to the SMS platform, telecom operators can grasp the full information of existing applications and achieve full coverage management. Application service providers can obtain the secondary numbers that need to be cleaned from the secondary number cleaning whitelist library of the SMS platform at regular / irregular times, and unbind the secondary numbers that need to be cleaned and the corresponding accounts, thereby realizing full-scenario management and fundamentally eliminating the risks brought by secondary number release.
[0118] In this embodiment, when the telecommunications operator SMS platform receives the secondary number to be cleared sent by the telecommunications operator business system, the secondary number to be cleared and the corresponding joining time are saved in the secondary number clearing whitelist library.
[0119] In this embodiment, each application service provider connected to the telecommunications operator's SMS platform as an SP will periodically / irregularly obtain the secondary numbers that need to be cleaned up in the secondary number cleanup whitelist library and the corresponding joining time from the telecommunications operator's SMS platform. Then, the application service provider determines whether the secondary number that needs to be cleaned up is bound to the corresponding account based on the local account mobile phone number binding relationship; and in response to the secondary number that needs to be cleaned up being bound to the corresponding account, and the binding time is earlier than the joining time corresponding to the secondary number that needs to be cleaned up, the secondary number that needs to be cleaned up and the corresponding account are unbound; and the first return code indicating that the unbinding has been returned to the telecommunications operator's SMS platform. Or, in response to the secondary number that needs to be cleaned up not being bound to the corresponding account, a second return code indicating that it is not involved is returned to the SMS platform.
[0120] It should be noted that "unbound" means that the secondary number to be cleared and the corresponding account have been unbound, and "not involved" means that the secondary number to be cleared does not have an account bound to it in the current application service provider. In order to protect the core data rights and interests of the application service provider to the greatest extent, the first return code and the second return code are the same, so that the telecom operator's SMS platform does not know whether the secondary number is bound to an account, but only knows that the application service provider has provided feedback.
[0121] In this embodiment, the telecommunications operator's SMS platform confirms, based on the first return code and the second return code returned by the application service provider, that the application service provider has fed back and processed the secondary number that needs to be cleared.
[0122] In this embodiment, when the application service provider needs to send a text message to the user, the application service provider sends a text message sending request carrying the target number to the telecommunications operator's text message platform. The telecommunications operator's text message platform receives the text message sending request from the application service provider, determines whether the target number is a number that has been released twice, and in response to the target number being a number that has been released twice, further determines whether the application service provider has fed back and processed the target number; the telecommunications operator's text message platform responds to the application service provider's feedback that the target number has been processed, sends a text message according to the text message sending request, and feeds back to the application service provider that the text message is successfully sent; or, in response to the application service provider's failure to feed back and process the target number, the telecommunications operator's text message platform feeds back to the application service provider that the text message fails to be sent. The application service provider receives the message of successful or failed text message sending fed back by the telecommunications operator's text message platform.
[0123] It should be noted that in the process of research and practice of the prior art, the inventor found that the intersection of the operation of application service providers and telecom operators is mainly concentrated in SMS services, and the application scenarios are mainly account registration and password retrieval, as well as message push reminders, etc. Therefore, as long as the sending link of SMS is grasped, most of the risks caused by secondary number release can be solved. Application service providers generally access the SMS platform of telecom operators as SP (Service Provider: the direct provider of Internet service content application services). Every time a text message is sent, the SMS platform will verify the validity of the accessed SP identity, and then verify the validity of the number. Only when there is no problem will the actual SMS be sent. Therefore, based on the SP information that has been accessed by the SMS platform, telecom operators can grasp the full amount of information of surviving applications and achieve full coverage management, that is, market management is feasible; in addition, when sending SMS, there is a basic business check of the number, which can be expanded and the processing of the secondary number release logic can be added, that is, technical management can be achieved. By combining market management and technical management, and then optimizing and transforming the business system functions of telecom operators, full-scenario management can be achieved, and the risks brought by secondary number release can be fundamentally eliminated.
[0124] In a specific embodiment, reference Figure 5 , showing an interactive schematic diagram of a method for preventing the risk of secondary release of a telephone number provided by an embodiment of the present invention. In this embodiment, the following steps are included:
[0125] 1. When a user comes to the hall to open a new card, the business system will check whether the number selected by the current user is a secondary number. If not, the card can be opened directly. If it is a secondary number, the user will be reminded that this number is a secondary number. It may take n working days to unbind the relevant account of the original number user. At the same time, the number is added to the secondary number cleanup whitelist library as a special number and pushed to the SMS platform. After completion, the subsequent card opening work will be completed for the user.
[0126] 2. The current user of the secondary number complained that he received harassing messages that the original number user had not cancelled the application. At this time, the salesperson confirmed with the user that the number needed to be unbound from the old user and all binding information of the current user. Then, he directly operated in the business system, added the number to the secondary number cleanup whitelist library, pushed it to the SMS platform, and completed the cleanup. At the same time, the user was informed that he could start registering a new application binding relationship after n working days.
[0127] 3. When a user transfers or changes the number, the salesperson and the user confirm and add the number to the secondary number cleanup whitelist database, push it to the SMS platform, and complete the cleanup. At the same time, the user is informed that they can start registering a new application binding relationship after n working days.
[0128] It should be noted that mobile number portability means that when users change operators, they retain their original mobile phone numbers. When users port their numbers, they can clear or not. It is optional. In a special scenario, after a user port is transferred, the new operator may not be able to clear the historical binding relationship. At this time, the existing telecom operator can provide "hospice care", which is also an opportunity to demonstrate differentiated service capabilities. It may improve customer perception to a certain extent and play a role in maintaining relationships.
[0129] 4. When a user cancels his account, the business system automatically detects whether the number has exceeded the freezing period. If it has, the number will be added to the secondary number cleanup whitelist and pushed to the SMS platform to complete the cleanup.
[0130] It should be noted that the freezing period refers to the period of time during which the number is temporarily reserved after the user cancels the account. During this period, the number will not be reallocated to other users. The freezing period is mainly set to prevent the number from being reused immediately, thereby protecting the privacy and rights of the original number user.
[0131] 5. For users who are forced to dismantle their phones, the business system will automatically detect whether the number has exceeded the freezing period. If it has, the number will be added to the secondary number cleanup whitelist and pushed to the SMS platform to complete the cleanup work.
[0132] It should be noted that forced dismantling users refer to those users whose services are forcibly terminated by telecom operators due to some reasons (for example, arrears, illegal use, fraud, etc.).
[0133] 6. Application service providers connect to the SMS platform of telecom operators, regularly obtain the secondary numbers that need to be cleaned up and the time they were added, compare them with the binding relationship and time of the local account mobile phone number, and after corresponding processing, reply to the SMS platform to feedback that the relevant numbers have been processed. For numbers not involved, the same feedback can be given that they have been processed, so as to protect the core data rights and interests of application service providers to the greatest extent.
[0134] It should be noted that the application service provider can also obtain the secondary numbers that need to be cleaned up and the joining time from time to time. For example, when the SMS platform finds that the secondary numbers that need to be cleaned up have accumulated a certain amount of data, but the application service provider has not processed them, the SMS platform can also directly send processing instruction information, so that the application service provider can process them according to the instruction information. Alternatively, the application service provider can obtain and process them from time to time according to its own free time.
[0135] It should be noted that if the secondary number to be cleaned up has been bound to the corresponding account, and the binding time is earlier than the joining time corresponding to the secondary number to be cleaned up, the binding relationship is released, otherwise, if the binding time is later than the joining time corresponding to the secondary number to be cleaned up, it is directly ignored. At this time, the second return code indicating that it is not involved can also be fed back.
[0136] It should be noted that application service providers periodically access the SMS platform's secondary number cleanup whitelist database through the interface provided by telecom operators to obtain the secondary numbers that need to be cleaned. Data queries can be performed by time period to reduce the amount of data accessed at a time. At the same time, after the application service provider has processed the data related to its own user account, when it reports that the relevant number on the SMS platform has been unbound or not involved, in order to protect the core data of the application service provider, the same return code can be used for not involved and processed.
[0137] It should be noted that the SMS platform updates the secondary number cleanup whitelist database based on the feedback from each application service provider, and only updates the data of the corresponding application service provider, which is logically isolated from the feedback from other application service providers. That is, each secondary number in the secondary number cleanup whitelist database will record which application service providers have responded to the processing and which application service providers have not responded to the processing.
[0138] 7. The application service provider requests to send a text message. The SMS platform determines whether the relevant number is a secondary release number. If not, the SMS is directly pushed to the user, and the feedback is successful. Otherwise, check whether the application service provider has already fed back and processed the secondary release number. If the feedback is successful, the SMS is pushed to the user, and the application service provider is fed back that the SMS was sent successfully; if the secondary release number has not been fed back, the application service provider is fed back that the SMS failed to be sent, and the reason for the failure is that the secondary release number was not processed. At this time, the application service provider can process the relevant historical binding relationship, and then feedback the processing results to the SMS platform based on the actual situation, and then send the SMS again to complete the relevant SMS sending work.
[0139] It should be noted that in order to avoid missing some secondary numbers that need to be cleaned up, telecom operators extend the existing SMS platform interface / protocol, add access and feedback to the secondary number cleanup whitelist library and the extension of the SMS sending related to the return results of the secondary number release. That is, the application service provider calls the telecom operator's SMS platform interface to apply for sending SMS, and the SMS platform verifies whether the number is a secondary number release number, and whether the SP has fed back and processed the account related to this number, and sends SMS or feedbacks the relevant failure reasons according to the actual situation.
[0140] 8. The initial data of the secondary number cleanup whitelist library of the SMS platform can be imported into historical data once or multiple times according to the specific situation. When the application service provider visits, the start and end time can be set to obtain the relevant secondary number data.
[0141] It should be noted that since this is a newly built / renovated system, there may be a lot of historical data accumulated. If it is imported all at once, the application service provider may have problems processing it. In this way, it will be smoother to obtain and process it in batches / segments.
[0142] 9. For some number identification systems, there is no need to send SMS. You can also refer to the access of ordinary application service providers and directly access the secondary number cleanup whitelist library to perform relevant data processing.
[0143] It should be noted that the risk prevention method for secondary release of telephone numbers provided by the present invention has the following characteristics:
[0144] a) Relying on the SP access management mode and SMS sending process of the telecom operator's SMS platform, expand and establish a secondary number cleanup whitelist database, and maintain the secondary number cleanup whitelist database by receiving the telecom operator's business system number whitelist;
[0145] b) SP (i.e. application service provider) regularly obtains and feedbacks the data in the secondary number cleanup whitelist database, and the SMS platform maintains the feedback results between the number and the SP;
[0146] c) Expand the existing SMS sending protocol, introduce a secondary number release, and an SP processing feedback result check mechanism. For the numbers involved, if the SP does not provide feedback, the SMS will be intercepted when it is sent and the specific reason for the failure will be fed back.
[0147] The risk prevention method for secondary release of telephone numbers provided in the embodiment of the present invention first obtains the secondary numbers that need to be cleaned by the business system of the telecommunications operator; then the secondary numbers that need to be cleaned are sent to the SMS platform of the telecommunications operator, so that the SMS platform of the telecommunications operator adds the secondary numbers that need to be cleaned to the secondary number cleanup whitelist library, and enables the application service provider to obtain the secondary numbers that need to be cleaned in the secondary number cleanup whitelist library regularly / irregularly, and unbinds the secondary numbers that need to be cleaned and the corresponding accounts. The present invention makes full use of the existing systems of telecommunications operators for upgrading and improvement, and can achieve full coverage of users involved in secondary release, fundamentally solving the problems of insufficient coverage, limited applicable scenarios or limited user groups, and inability to completely avoid the risks brought by secondary release in existing solutions for secondary release, etc. It can not only reduce unnecessary burdens on individual users, but also simply, conveniently, comprehensively, thoroughly, and controllably eliminate the hidden dangers of secondary release.
[0148] Embodiment 2:
[0149] like Figure 6 As shown, this embodiment provides a method for preventing the risk of secondary release of a telephone number, which is applied to a short message platform of a telecommunications operator, and the method includes:
[0150] Step S201: receiving the secondary number to be cleared sent by the telecom operator's business system after acquiring the secondary number to be cleared;
[0151] Step S202: Add the secondary number to be cleaned to the secondary number cleanup whitelist library, so that the application service provider can obtain the secondary number to be cleaned in the secondary number cleanup whitelist library regularly / irregularly, and unbind the secondary number to be cleaned from the corresponding account.
[0152] It should be noted that application service providers generally access the SMS platform of telecom operators as SPs. Therefore, based on the SP information that has been connected to the SMS platform, telecom operators can grasp the full information of existing applications and achieve full coverage management. Application service providers can obtain the secondary numbers that need to be cleaned from the secondary number cleaning whitelist library of the SMS platform at regular / irregular times, and unbind the secondary numbers that need to be cleaned and the corresponding accounts, thereby realizing full-scenario management and fundamentally eliminating the risks brought by secondary number release.
[0153] Optionally, the adding the secondary number to be cleaned up to a secondary number cleanup whitelist library specifically includes:
[0154] The secondary numbers that need to be cleared and the corresponding joining time are saved in the secondary number clearing whitelist library.
[0155] Optionally, the method further comprises:
[0156] receiving a first return code returned by the application service provider indicating that the binding has been untied; or,
[0157] receiving a second return code returned by the application service provider to indicate that the application service provider is not involved;
[0158] The first return code and the second return code are the same.
[0159] It should be noted that "unbound" means that the secondary number to be cleared and the corresponding account have been unbound, and "not involved" means that the secondary number to be cleared does not have an account bound to it in the current application service provider. In order to protect the core data rights and interests of the application service provider to the greatest extent, the first return code and the second return code are the same, so that the telecom operator's SMS platform does not know whether the secondary number is bound to an account, but only knows that the application service provider has provided feedback.
[0160] In this embodiment, the telecommunications operator's SMS platform confirms, based on the first return code and the second return code returned by the application service provider, that the application service provider has fed back and processed the secondary number that needs to be cleared.
[0161] Optionally, the method further comprises:
[0162] Receive a text message sending request from an application service provider, wherein the text message sending request carries a target number;
[0163] Determine whether the target number is a second-time number;
[0164] In response to the target number being a second-time released number, determining whether the application service provider has already processed the target number;
[0165] In response to the application service provider's feedback that the target number has been processed, sending a text message according to the text message sending request, and feeding back to the application service provider that the text message has been successfully sent;
[0166] In response to the application service provider not feeding back the processing of the target number, feeding back to the application service provider that the SMS sending failed.
[0167] Embodiment 3:
[0168] like Figure 7 As shown, this embodiment provides a method for preventing the risk of secondary release of a telephone number, which is applied to an application service provider, and the method includes:
[0169] Step S301: obtaining secondary numbers that need to be cleaned up from a secondary number cleanup whitelist library from a telecommunications operator's SMS platform at regular or irregular intervals; wherein the telecommunications operator's business system obtains the secondary numbers that need to be cleaned up, and sends the secondary numbers that need to be cleaned up to the telecommunications operator's SMS platform, so that the telecommunications operator's SMS platform adds the secondary numbers that need to be cleaned up to the secondary number cleanup whitelist library;
[0170] Step S301: unbinding the secondary number to be cleared and the corresponding account.
[0171] It should be noted that application service providers generally access the SMS platform of telecom operators as SPs. Therefore, based on the SP information that has been connected to the SMS platform, telecom operators can grasp the full information of existing applications and achieve full coverage management. Application service providers can obtain the secondary numbers that need to be cleaned from the secondary number cleaning whitelist library of the SMS platform at regular / irregular times, and unbind the secondary numbers that need to be cleaned and the corresponding accounts, thereby realizing full-scenario management and fundamentally eliminating the risks brought by secondary number release.
[0172] Optionally, the periodic / irregular acquisition of the secondary numbers to be cleared from the secondary number clearing whitelist library from the telecommunications operator's SMS platform specifically includes:
[0173] Obtain the secondary numbers that need to be cleared from the secondary number clearing whitelist library and the corresponding joining time from the telecom operator's SMS platform on a regular / irregular basis;
[0174] The unbinding process of the secondary number to be cleared and the corresponding account specifically includes:
[0175] Determine whether the secondary number to be cleared is bound to the corresponding account according to the local account mobile phone number binding relationship;
[0176] In response to the secondary number that needs to be cleared being bound to a corresponding account, and the binding time is earlier than the joining time corresponding to the secondary number that needs to be cleared, unbinding the secondary number that needs to be cleared and the corresponding account;
[0177] A first return code indicating unbinding is returned to the telecommunications operator SMS platform.
[0178] Optionally, the method further comprises:
[0179] In response to the secondary number that needs to be cleared not being bound to a corresponding account, returning a second return code indicating that it is not involved to the SMS platform;
[0180] The first return code and the second return code are the same.
[0181] It should be noted that "unbound" means that the secondary number to be cleared and the corresponding account have been unbound, and "not involved" means that the secondary number to be cleared does not have an account bound to it in the current application service provider. In order to protect the core data rights and interests of the application service provider to the greatest extent, the first return code and the second return code are the same, so that the telecom operator's SMS platform does not know whether the secondary number is bound to an account, but only knows that the application service provider has provided feedback.
[0182] In this embodiment, the telecommunications operator's SMS platform confirms, based on the first return code and the second return code returned by the application service provider, that the application service provider has fed back and processed the secondary number that needs to be cleared.
[0183] Optionally, the method further comprises:
[0184] Sending a text message sending request carrying a target number to the telecommunications operator's text message platform, so that after receiving the text message sending request, the telecommunications operator's text message platform determines whether the target number is a number that has been released for the second time; and in response to the target number being a number that has been released for the second time, determining whether the application service provider has fed back and processed the target number; and in response to the application service provider having fed back and processed the target number, sending a text message according to the text message sending request, and feeding back to the application service provider that the text message has been successfully sent; or in response to the application service provider not feeding back and processing the target number, feeding back to the application service provider that the text message has failed to be sent;
[0185] Receive a message from the telecommunications operator's SMS platform indicating that the SMS is sent successfully or fails to be sent.
[0186] In this embodiment, when the application service provider needs to send a text message to the user, the application service provider sends a text message sending request carrying the target number to the telecommunications operator's text message platform. The telecommunications operator's text message platform receives the text message sending request from the application service provider, determines whether the target number is a number that has been released twice, and in response to the target number being a number that has been released twice, further determines whether the application service provider has fed back and processed the target number; the telecommunications operator's text message platform responds to the application service provider's feedback that the target number has been processed, sends a text message according to the text message sending request, and feeds back to the application service provider that the text message is successfully sent; or, in response to the application service provider's failure to feed back and process the target number, the telecommunications operator's text message platform feeds back to the application service provider that the text message fails to be sent. The application service provider receives the message of successful or failed text message sending fed back by the telecommunications operator's text message platform.
[0187] Embodiment 4:
[0188] refer to Figure 8 This embodiment provides a risk prevention device for secondary release of a telephone number, including a memory 11 and a processor 12, wherein the memory 11 stores a computer program, and the processor 12 is configured to run the computer program to execute the risk prevention method for secondary release of a telephone number in Example 1, Example 2, or Example 3.
[0189] The memory 11 is connected to the processor 12. The memory 11 may be a flash memory, a read-only memory or other memory. The processor 12 may be a central processing unit or a single-chip microcomputer.
[0190] Embodiment 5:
[0191] refer to Fig. 9 , this embodiment provides a risk prevention system for secondary release of telephone numbers, including a telecommunications operator business system 21, a telecommunications operator SMS platform 22 and an application service provider 23;
[0192] The telecommunications operator business system 21 is used to execute the risk prevention method for secondary release of telephone numbers in Example 1;
[0193] The telecommunications operator SMS platform 22 is used to execute the risk prevention method for secondary release of telephone numbers in Example 2;
[0194] The application service provider 23 is used to execute the risk prevention method of secondary release of telephone number in Example 3.
[0195] Embodiment 6:
[0196] This embodiment provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the method for preventing the risk of secondary release of a telephone number in the above-mentioned embodiment 1, embodiment 2 or embodiment 3 is implemented.
[0197] 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). Computer-readable storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable read only memory), flash memory or other memory technology, CD-ROM (Compact Disc Read-Only Memory), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, 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.
[0198] In summary, the risk prevention method, device, system and medium for secondary release of telephone numbers provided in the embodiments of the present invention first obtains the secondary numbers that need to be cleaned by the business system of the telecommunications operator; then the secondary numbers that need to be cleaned are sent to the SMS platform of the telecommunications operator, so that the SMS platform of the telecommunications operator adds the secondary numbers that need to be cleaned to the secondary number cleanup whitelist library, and enables the application service provider to obtain the secondary numbers that need to be cleaned in the secondary number cleanup whitelist library regularly / irregularly, and unbinds the secondary numbers that need to be cleaned and the corresponding accounts. The present invention makes full use of the existing systems of telecommunications operators for upgrading and improvement, and can achieve full coverage of users involved in secondary release, fundamentally solving the problems of insufficient coverage, limited applicable scenarios or limited user groups, and inability to completely avoid the risks brought by secondary release in existing solutions for secondary release, etc. It can not only reduce unnecessary burdens on individual users, but also simply, conveniently, comprehensively, thoroughly and controllably eliminate the hidden dangers of secondary release.
[0199] It is to be understood that the above embodiments are merely exemplary embodiments used to illustrate the principles of the present invention, but the present invention 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 invention, and these modifications and improvements are also considered to be within the scope of protection of the present invention.
Claims
1. A method for preventing the risk of secondary release of telephone numbers, characterized in that: Applied to a telecommunications operator's business system, the method comprises: Get the secondary number that needs to be cleaned; The secondary numbers that need to be cleaned are sent to the telecommunications operator's SMS platform, so that the telecommunications operator's SMS platform adds the secondary numbers that need to be cleaned to the secondary number cleaning whitelist library, and enables the application service provider to obtain the secondary numbers that need to be cleaned in the secondary number cleaning whitelist library regularly / irregularly, and unbind the secondary numbers that need to be cleaned and the corresponding accounts.
2. The method according to claim 1, characterized in that The obtaining of the secondary number to be cleared includes at least one of the following: In response to the number selected by the current user when opening a new card being a secondary number, the number selected by the current user when opening a new card is used as the secondary number that needs to be cleared; In response to receiving a complaint from a current user of the secondary number regarding failure of the user of the original number to unbind the relevant application account, taking the secondary number corresponding to the complaint as the secondary number that needs to be cleared; In response to the number confirmed by the current user during porting or transfer, the confirmed number is used as the secondary number that needs to be cleared; In response to the number after the cancellation of the account exceeding the freezing period, the number after the cancellation of the account is used as the secondary number that needs to be cleared; In response to the number corresponding to the user who is forced to dismantle the phone having exceeded the freezing period, the number corresponding to the user who is forced to dismantle the phone is used as the secondary number that needs to be cleared.
3. A method for preventing the risk of secondary release of telephone numbers, characterized in that: Applied to a telecommunications operator's SMS platform, the method includes: Receiving the secondary number to be cleared sent by the telecommunications operator's business system after acquiring the secondary number to be cleared; The secondary numbers that need to be cleaned are added to the secondary number cleanup whitelist library, so that the application service provider can obtain the secondary numbers that need to be cleaned in the secondary number cleanup whitelist library regularly / irregularly, and unbind the secondary numbers that need to be cleaned and the corresponding accounts.
4. The method according to claim 3, characterized in that The adding the secondary number to be cleaned up into the secondary number cleanup whitelist library specifically includes: The secondary numbers that need to be cleared and the corresponding joining time are saved in the secondary number clearing whitelist library.
5. The method according to claim 4, characterized in that The method further comprises: receiving a first return code returned by the application service provider indicating that the binding has been untied; or, receiving a second return code returned by the application service provider to indicate that the application service provider is not involved; The first return code and the second return code are the same.
6. The method according to claim 3, characterized in that The method further comprises: Receive a text message sending request from an application service provider, wherein the text message sending request carries a target number; Determine whether the target number is a second-time number; In response to the target number being a second-time released number, determining whether the application service provider has already processed the target number; In response to the application service provider's feedback that the target number has been processed, sending a text message according to the text message sending request, and feeding back to the application service provider that the text message has been successfully sent; In response to the application service provider not feeding back the processing of the target number, feeding back to the application service provider that the SMS sending failed.
7. A method for preventing the risk of secondary release of telephone numbers, characterized in that: Applied to an application service provider, the method includes: Obtaining secondary numbers that need to be cleaned from a secondary number cleanup whitelist library from a telecommunications operator's SMS platform at regular / irregular times; wherein the telecommunications operator's business system obtains the secondary numbers that need to be cleaned, and sends the secondary numbers that need to be cleaned to the telecommunications operator's SMS platform, so that the telecommunications operator's SMS platform adds the secondary numbers that need to be cleaned to the secondary number cleanup whitelist library; The secondary number that needs to be cleared and the corresponding account are unbound.
8. The method according to claim 7, characterized in that The timing / irregularity of obtaining the secondary numbers that need to be cleared from the secondary number clearing whitelist library from the telecommunications operator's SMS platform specifically includes: Obtain the secondary numbers that need to be cleared from the secondary number clearing whitelist library and the corresponding joining time from the telecom operator's SMS platform on a regular / irregular basis; The unbinding process of the secondary number to be cleared and the corresponding account specifically includes: Determine whether the secondary number to be cleared is bound to the corresponding account according to the local account mobile phone number binding relationship; In response to the secondary number that needs to be cleared being bound to a corresponding account, and the binding time is earlier than the joining time corresponding to the secondary number that needs to be cleared, unbinding the secondary number that needs to be cleared and the corresponding account; A first return code indicating unbinding is returned to the telecommunications operator SMS platform.
9. The method according to claim 8, characterized in that The method further comprises: In response to the secondary number that needs to be cleared not being bound to a corresponding account, returning a second return code indicating that it is not involved to the SMS platform; The first return code and the second return code are the same.
10. The method according to claim 7, characterized in that The method further comprises: Sending a text message sending request carrying a target number to the telecommunications operator's text message platform, so that after receiving the text message sending request, the telecommunications operator's text message platform determines whether the target number is a number that has been released for the second time; and in response to the target number being a number that has been released for the second time, determining whether the application service provider has fed back and processed the target number; and in response to the application service provider having fed back and processed the target number, sending a text message according to the text message sending request, and feeding back to the application service provider that the text message has been successfully sent; or in response to the application service provider not feeding back and processing the target number, feeding back to the application service provider that the text message has failed to be sent; Receive a message from the telecommunications operator's SMS platform indicating that the SMS is sent successfully or fails to be sent.
11. A device for preventing the risk of secondary release of telephone numbers, characterized in that: It includes a memory and a processor, the memory stores a computer program, and the processor is configured to run the computer program to implement the risk prevention method for secondary allocation of telephone numbers as described in any one of claims 1-2, or to implement the risk prevention method for secondary allocation of telephone numbers as described in any one of claims 3-6, or to implement the risk prevention method for secondary allocation of telephone numbers as described in any one of claims 7-10.
12. A risk prevention system for secondary release of telephone numbers, characterized in that: Including telecom operators' business systems, telecom operators' SMS platforms and application service providers; The telecommunications operator business system is used to execute the risk prevention method for secondary release of telephone numbers according to any one of claims 1-2; The telecommunications operator SMS platform is used to execute the risk prevention method for secondary release of a telephone number as described in any one of claims 3 to 6; The application service provider is used to execute the risk prevention method for secondary release of telephone numbers as described in any one of claims 7-10.
13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the risk prevention method for secondary release of a telephone number as described in any one of claims 1-2, or implements the risk prevention method for secondary release of a telephone number as described in any one of claims 3-6, or implements the risk prevention method for secondary release of a telephone number as described in any one of claims 7-10.
