Method and device for reserving mobile phone number, electronic equipment and medium

Abstract

The present disclosure provides a method and device for processing reserved mobile phone numbers, electronic equipment, medium and computer program product. The above-mentioned method and device can be used in the field of artificial intelligence technology. The method for processing reserved mobile phone numbers is applied to a server, which includes: receiving a risk reserved mobile phone number, wherein the risk reserved mobile phone number is identified by a client calling a risk identification model; obtaining state information and network access time of the risk reserved mobile phone number according to the risk reserved mobile phone number; determining a judgment rule to be called in a secondary number release identification model according to the state information; and marking the risk reserved mobile phone number according to the judgment rule, and transmitting the marking result to the client.

Description

Technical Field

[0001] This disclosure relates to the field of artificial intelligence technology, and more specifically, to a method, apparatus, electronic device, and medium for processing a reserved mobile phone number. Background Technology

[0002] Bank card quick payment is a commonly used online payment product. It involves a pre-signed deduction authorization agreement between the bank customer, the target institution, and the issuing bank. Subsequently, when making electronic payments under the agreed-upon payment scenarios and rules, the bank customer no longer needs to enter their bank card PIN. This payment design avoids the need to enter a PIN in front of others for every payment, protecting personal privacy and account security, while also improving the electronic payment experience for bank customers. Signing a quick payment agreement is a prerequisite for bank card quick payment.

[0003] Due to the limited availability of mobile phone numbers, when a user deactivates a mobile phone number, the number is reclaimed by the telecommunications operator. After a period of suspension, it is re-entered into the network and reintroduced into the market—a process known as re-issuance. Currently, the national regulation stipulates a minimum suspension period of 90 days for mobile phone numbers.

[0004] During the process of signing up for bank card quick payment, verifying the customer's registered mobile phone number is a crucial basis for confirming that the customer is indeed signing up. If a customer registers their mobile phone number with the bank's system and then fails to update or cancel the number in a timely manner after deactivating or canceling it, the re-registered "second-hand" mobile phone number can still receive SMS verification codes from the corresponding bank account and complete the bank card quick payment agreement due to information asynchrony between the operator and the bank. This poses a risk of financial loss to others. Summary of the Invention

[0005] In view of this, the present disclosure provides a method, apparatus, electronic device, computer-readable storage medium, and computer program product for processing reserved mobile phone numbers that are fast-responding and simple in process.

[0006] One aspect of this disclosure provides a method for processing reserved mobile phone numbers, applied to a server, comprising: receiving a risky reserved mobile phone number, wherein the risky reserved mobile phone number is identified by a risk identification model called by a client; obtaining the status information and network access time of the risky reserved mobile phone number based on the risky reserved mobile phone number; determining the judgment rule to be called in the secondary number release identification model based on the status information; and marking the risky reserved mobile phone number according to the judgment rule, and transmitting the marking result to the client.

[0007] According to the method for processing reserved mobile phone numbers in this disclosure, the server identifies the risky reserved mobile phone numbers by the client, performs status recognition and secondary number release judgment, and then sends the marked risky reserved mobile phone numbers back to the client. The client can then process the risky reserved mobile phone numbers based on the marking results, thereby reducing losses to users due to secondary number release. Compared with the prior art, this disclosure has a shorter transaction chain, enabling rapid response; furthermore, this disclosure does not require the operator to actively push mobile phone number status, avoiding the problems of operator omissions or complex push processes.

[0008] In some embodiments, the status information includes normal and abnormal states. The step of determining the judgment rule to be invoked in the secondary number release identification model based on the status information specifically includes: when the status information is normal, invoking the first judgment rule in the secondary number release identification model, wherein the first judgment rule is a comparison between the network access time and the registration time of the risk-reserved mobile phone number on the client; and when the status information is abnormal, invoking the second judgment rule in the secondary number release identification model.

[0009] In some embodiments, marking the risk-reserved mobile phone number according to the first determination rule and transmitting the marking result to the client specifically includes: marking the risk-reserved mobile phone number as non-secondary number release when the network access time is earlier than the registration time of the risk-reserved mobile phone number on the client; marking the risk-reserved mobile phone number as secondary number release when the network access time is later than the registration time of the risk-reserved mobile phone number on the client; and transmitting the marking result (non-secondary number release or marking result secondary number release) to the client.

[0010] In some embodiments, marking the risk-reserved mobile phone number according to the second determination rule and transmitting the marking result to the client specifically includes: marking the risk-reserved mobile phone number as abnormal; and transmitting the abnormal marking result to the client.

[0011] Another aspect of this disclosure provides a processing apparatus for reserved mobile phone numbers, applied to a server, comprising: a server receiving module for receiving risky reserved mobile phone numbers, wherein the risky reserved mobile phone numbers are identified by a risk identification model invoked by a client; a server obtaining module for obtaining the status information and network access time of the risky reserved mobile phone number; a server determining module for determining the judgment rule to be invoked in the secondary number release identification model based on the status information; and a server marking module for marking the risky reserved mobile phone number according to the judgment rule and transmitting the marking result to the client.

[0012] Another aspect of this disclosure provides a method for processing reserved mobile phone numbers, comprising: a client identifying a risky reserved mobile phone number through a risk identification model; the client transmitting the risky reserved mobile phone number to a server; the server obtaining the status information and network access time of the risky reserved mobile phone number; the server determining the judgment rule to be invoked in the secondary number release identification model based on the status information; marking the risky reserved mobile phone number according to the judgment rule and transmitting the marking result to the client; and the client processing the risky reserved mobile phone number based on the marking result.

[0013] In some embodiments, the marking result is a secondary number release, a non-secondary number release, or an abnormal state. The client processes the risk-reserved mobile phone number according to the marking result, specifically including: when the marking result is a secondary number release or an abnormal state, adding the corresponding risk-reserved mobile phone number to the blacklist.

[0014] Another aspect of this disclosure provides a processing apparatus for reserved mobile phone numbers, comprising: an identification module, wherein a client identifies a risky reserved mobile phone number through a risk identification model in the identification module; a transmission module, wherein the client transmits the risky reserved mobile phone number to a server through the transmission module; an acquisition module, wherein the server acquires the status information and network access time of the risky reserved mobile phone number through the acquisition module; a determination module, wherein the server determines the judgment rule to be invoked in the secondary number release identification model based on the status information through the determination module; a marking module, wherein the marking module is used to mark the risky reserved mobile phone number according to the judgment rule and transmit the marking result to the client; and a processing module, wherein the client processes the risky reserved mobile phone number based on the marking result through the processing module.

[0015] Another aspect of this disclosure provides an electronic device including one or more processors and one or more memories, wherein the memories are used to store executable instructions that, when executed by the processor, implement the method described above.

[0016] Another aspect of this disclosure provides a computer-readable storage medium storing computer-executable instructions that, when executed, are used to implement the method described above.

[0017] Another aspect of this disclosure provides a computer program product including a computer program comprising computer executable instructions that, when executed, implement the method described above. Attached Figure Description

[0018] The above and other objects, features and advantages of this disclosure will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0019] Figure 1 This illustration schematically shows an exemplary system architecture to which methods and apparatus can be applied according to embodiments of the present disclosure;

[0020] Figure 2 A flowchart illustrating a method for processing a reserved mobile phone number according to an embodiment of the present disclosure is shown schematically.

[0021] Figure 3 This schematically illustrates a flowchart of determining the judgment rule to be invoked in the secondary number issuance identification model based on state information according to an embodiment of the present disclosure;

[0022] Figure 4 This illustration schematically shows a flowchart of marking risky reserved mobile phone numbers according to a first determination rule and transmitting the marking result to a client, based on an embodiment of the present disclosure.

[0023] Figure 5 This illustration schematically shows a flowchart of marking risky reserved mobile phone numbers according to a second determination rule and transmitting the marking result to the client, based on an embodiment of the present disclosure.

[0024] Figure 6 This schematic diagram illustrates a structural block diagram of a device for processing reserved mobile phone numbers according to an embodiment of the present disclosure;

[0025] Figure 7 A flowchart illustrating a method for processing a reserved mobile phone number according to an embodiment of the present disclosure is shown schematically.

[0026] Figure 8 This illustration schematically shows a flowchart of a method for a client to identify a risky reserved mobile phone number through a risk identification model according to an embodiment of the present disclosure;

[0027] Figure 9 This illustration schematically shows a flowchart of a client processing risk-reserved mobile phone numbers based on the marking results according to an embodiment of the present disclosure;

[0028] Figure 10 A flowchart illustrating a method for processing a reserved mobile phone number according to an embodiment of the present disclosure is shown schematically.

[0029] Figure 11 This schematic diagram illustrates a structural block diagram of a device for processing reserved mobile phone numbers according to an embodiment of the present disclosure;

[0030] Figure 12 A schematic diagram illustrating the structure of the determining module according to an embodiment of the present disclosure is shown.

[0031] Figure 13A schematic diagram illustrating the structure of a marking module according to an embodiment of the present disclosure is shown.

[0032] Figure 14 A schematic diagram illustrating the structure of a marking module according to an embodiment of the present disclosure is shown.

[0033] Figure 15 A schematic diagram illustrating the structure of a processing module according to an embodiment of the present disclosure is shown.

[0034] Figure 16 This schematic diagram illustrates a structural block diagram of a device for processing reserved mobile phone numbers according to an embodiment of the present disclosure;

[0035] Figure 17 A block diagram of an electronic device according to an embodiment of the present disclosure is shown schematically. Detailed Implementation

[0036] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0037] In the technical solution disclosed herein, the acquisition, storage, and application of user personal information all comply with relevant laws and regulations, necessary confidentiality measures have been taken, and there is no violation of public order and good morals. In the technical solution disclosed herein, the acquisition, collection, storage, use, processing, transmission, provision, disclosure, and application of data all comply with relevant laws and regulations, necessary confidentiality measures have been taken, and there is no violation of public order and good morals.

[0038] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0039] When using expressions such as "at least one of A, B, or C," it should generally be interpreted in accordance with the meaning commonly understood by those skilled in the art (e.g., "a system having at least one of A, B, or C" should include, but is not limited to, systems having A alone, having B alone, having C alone, having A and B, having A and C, having B and C, and / or having A, B, and C, etc.). The terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, features defined with "first" or "second" may explicitly or implicitly include one or more of the stated features.

[0040] Bank card quick payment is a commonly used online payment product. It involves a pre-signed deduction authorization agreement between the bank customer, the target institution, and the issuing bank. Subsequently, when making electronic payments under the agreed-upon payment scenarios and rules, the bank customer no longer needs to enter their bank card PIN. This payment design avoids the need to enter a PIN in front of others for every payment, protecting personal privacy and account security, while also improving the electronic payment experience for bank customers. Signing a quick payment agreement is a prerequisite for bank card quick payment.

[0041] Due to the limited availability of mobile phone numbers, when a user deactivates a mobile phone number, the number is reclaimed by the telecommunications operator. After a period of suspension, it is re-entered into the network and reintroduced into the market—a process known as re-issuance. Currently, the national regulation stipulates a minimum suspension period of 90 days for mobile phone numbers.

[0042] During the process of signing up for bank card quick payment, verifying the customer's registered mobile phone number is a crucial basis for confirming that the customer is indeed signing up. If a customer registers their mobile phone number with the bank's system and then fails to update or cancel the number in a timely manner after deactivating or canceling it, the re-registered "second-hand" mobile phone number can still receive SMS verification codes from the corresponding bank account and complete the bank card quick payment agreement due to information asynchrony between the operator and the bank. This poses a risk of financial loss to others.

[0043] Existing methods for identifying secondary number allocations include two approaches: first, internet applications directly extract risk features from transaction-related data to train models that identify account theft through secondary number allocations; second, operators proactively notify service provider systems when a secondary number is activated, allowing these systems to unlink previously associated services for the new user. The first method relies heavily on proprietary transaction data to build the model, which is invoked upon transaction initiation, lengthening the transaction chain and hindering rapid response in online transactions. The second method involves operators proactively pushing the information to service provider systems, but operators cannot confirm whether the number is within the bank's pre-registered number range. The bank's system, upon receiving the secondary number, needs to match it with its pre-registered numbers, a complex process.

[0044] This disclosure provides a method, apparatus, electronic device, computer-readable storage medium, and computer program product for processing reserved mobile phone numbers. The method for processing reserved mobile phone numbers includes: receiving a risky reserved mobile phone number, wherein the risky reserved mobile phone number is identified by a client calling a risk identification model; obtaining the status information and network access time of the risky reserved mobile phone number based on the risky reserved mobile phone number; determining the judgment rule to be invoked in the secondary number allocation identification model based on the status information; marking the risky reserved mobile phone number according to the judgment rule; and transmitting the marking result to the client.

[0045] It should be noted that the methods, devices, electronic devices, computer-readable storage media, and computer program products for processing reserved mobile phone numbers disclosed herein can be used in the field of artificial intelligence technology, or in any field other than the field of artificial intelligence technology, such as the financial field. The field of this disclosure is not limited here.

[0046] Figure 1 This illustration schematically depicts an exemplary system architecture 100 applicable to methods, apparatuses, electronic devices, computer-readable storage media, and computer program products for processing reserved mobile phone numbers according to embodiments of this disclosure. It should be noted that... Figure 1 The examples shown are merely examples of system architectures that can be applied to the embodiments of this disclosure, in order to help those skilled in the art understand the technical content of this disclosure, but do not mean that the embodiments of this disclosure cannot be used in other devices, systems, environments or scenarios.

[0047] like Figure 1 As shown, the system architecture 100 according to this embodiment may include terminal devices 101, 102, and 103, a network 104, and a server 105. The network 104 serves as a medium for providing a communication link between the terminal devices 101, 102, and 103 and the server 105. The network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0048] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, and 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0049] Terminal devices 101, 102, and 103 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0050] Server 105 can be a server that provides various services, such as a backend management server that supports websites browsed by users using terminal devices 101, 102, and 103 (for example only). The backend management server can analyze and process data such as received user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices.

[0051] It should be noted that the method for processing reserved mobile phone numbers provided in this embodiment can generally be executed by server 105. Correspondingly, the device for processing reserved mobile phone numbers provided in this embodiment can generally be located in server 105. The method for processing reserved mobile phone numbers provided in this embodiment can also be executed by a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103 and / or server 105. Correspondingly, the device for processing reserved mobile phone numbers provided in this embodiment can also be located in a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103 and / or server 105.

[0052] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0053] The following will be based on Figure 1 The described scene, through Figures 2-5 , Figures 7-10 The method for processing the reserved mobile phone number according to the embodiments of this disclosure will be described in detail.

[0054] Figure 2 A flowchart illustrating a method for processing a reserved mobile phone number according to an embodiment of the present disclosure is shown.

[0055] like Figure 2 As shown, the method for processing the reserved mobile phone number in this embodiment is applied to the server and includes operations S210 to S240.

[0056] In operation S210, the system receives risk-preserved mobile phone numbers. These risk-preserved mobile phone numbers are identified by the client using a risk identification model. The client can be understood as a banking system. Within the banking system, there is a risk of secondary number allocation among the mobile phone numbers reserved by customers. The risk identification model can identify these risky reserved mobile phone numbers. Of course, the client can also be understood as other business systems; no specific restrictions are made here. The following example primarily uses a banking system as the client. The server can be understood as a service provider system, which provides mobile phone number activation and maintenance services. Of course, the server can also be understood as other business systems providing services; no specific restrictions are made here.

[0057] When operating S220, based on the risk-reserved mobile phone number, obtain the status information and network access time of the risk-reserved mobile phone number.

[0058] In operation S230, based on the status information, the judgment rule to be invoked in the secondary number issuance recognition model is determined.

[0059] As one possible implementation method, state information includes normal and abnormal states, such as Figure 3 As shown, operation S230 determines the judgment rule to be called in the secondary number release recognition model based on the status information, specifically including operation S231 and operation S232.

[0060] In operation S231, when the status information is normal, the first judgment rule in the secondary number release identification model is called. The first judgment rule is to compare the network access time with the registration time of the risk reserved mobile phone number on the client.

[0061] In operation S232, when the status information is abnormal, the second judgment rule in the secondary number release identification model is invoked. An abnormal status can be understood as the phone number being cancelled or not being re-registered. Operations S231 and S232 facilitate the server in determining the judgment rule to be invoked in the secondary number release identification model based on the status information.

[0062] In operation S240, risk-reserved mobile phone numbers are marked according to the judgment rules, and the marking results are transmitted to the client.

[0063] As an feasible approach, such as Figure 4 As shown, operation S240 marks the risk-reserved mobile phone number according to the first judgment rule and transmits the marking result to the client, specifically including operations S241 to S243.

[0064] In operation S241, when the network access time is earlier than the registration time of the risky reserved mobile number on the client, the risky reserved mobile number is marked as not being reissued. Here, the network access time can be understood as the time when the mobile number was opened with the operator; the registration time can be understood as the time when the mobile number was registered as a reserved mobile number on the client.

[0065] In operation S242, when the network access time is later than the registration time of the risk-reserved mobile number on the client, the risk-reserved mobile number is marked as a secondary number. It can be understood that if the network access time is later than the registration time, it means that the mobile number was first authenticated and registered in the bank's system, and then accessed the network on the operator's side. This means that after registering in the bank's system, the mobile number was at least re-cancelled, re-accessed, and reactivated once, thus the mobile number is definitely a secondary number. If the network access time is earlier than the registration time, it means that the mobile number was first accessed in the operator's system, and then registered in the bank's system, and the current status of the mobile number is normal, consistent with the status of a normal mobile number, then the mobile number is not a secondary number. The registration time of the risk-reserved mobile number on the client can be characteristic information carried with the risk-reserved mobile number.

[0066] In operation S243, the marking result (either non-secondary number release or secondary number release) is transmitted to the client. It can be understood that when the marked risk-preserved mobile number is not subject to secondary number release, the marking result is transmitted to the client; when the marked risk-preserved mobile number is subject to secondary number release, the marking result is transmitted to the client.

[0067] By operating S241 to S243, it is easy to mark the risk-reserved mobile phone number according to the first judgment rule and transmit the marking result to the client.

[0068] As another feasible approach, such as Figure 5 As shown, operation S240 marks the risk-reserved mobile phone number according to the second judgment rule and transmits the marking result to the client, specifically including operation S244 and operation S245.

[0069] In operation S244, the risk-reserved mobile phone number is marked as abnormal.

[0070] In operation S245, the abnormal status of the marking result is transmitted to the client. It is understood that when the status information of the risk-reserved mobile phone number is abnormal, the second judgment rule is to mark the risk-reserved mobile phone number as abnormal. Operations S244 and S245 facilitate marking the risk-reserved mobile phone number according to the second judgment rule and transmitting the marking result to the client.

[0071] According to the method for processing reserved mobile phone numbers in this disclosure, the server identifies the risky reserved mobile phone numbers by the client, performs status recognition and secondary number release judgment, and then sends the marked risky reserved mobile phone numbers back to the client. The client can then process the risky reserved mobile phone numbers based on the marking results, thereby reducing losses to users due to secondary number release. Compared with the prior art, this disclosure has a shorter transaction chain, enabling rapid response; furthermore, this disclosure does not require the operator to actively push mobile phone number status, avoiding the problems of operator omissions or complex push processes.

[0072] Based on the above-described method for processing reserved mobile phone numbers, this disclosure also provides a processing device 20 for reserved mobile phone numbers. The following will be combined with... Figure 6 The processing device 20 for the reserved mobile phone number is described in detail.

[0073] Figure 6 The diagram illustrates the structure of a pre-reserved mobile phone number processing apparatus 20 according to an embodiment of the present disclosure.

[0074] like Figure 6 As shown, the processing device 20 for reserved mobile phone numbers includes a server receiving module 21, a server obtaining module 22, a server determining module 23, and a server marking module 24.

[0075] The server receiving module 21 is used to perform operation S210: receiving the risk reserved mobile phone number, wherein the risk reserved mobile phone number is identified by the client calling the risk identification model.

[0076] The server-side acquisition module 22 is used to perform operation S220: based on the risk-reserved mobile phone number, obtain the status information and network access time of the risk-reserved mobile phone number.

[0077] Server-side determination module 23 is used to perform operation S230: determine the judgment rule to be called in the secondary number release identification model based on the status information.

[0078] The server-side marking module 24 is used to perform operation S240: mark the risk-reserved mobile phone number according to the judgment rules, and transmit the marking result to the client.

[0079] According to the reserved mobile phone number processing device 20 of this disclosure, the server identifies the risky reserved mobile phone numbers identified by the client, performs status recognition and secondary number release judgment, and then sends the marked risky reserved mobile phone numbers back to the client. The client can then process the risky reserved mobile phone numbers according to the marking results, thereby reducing losses to users due to secondary number release. Compared with the prior art, this disclosure has a shorter transaction chain, enabling rapid response; furthermore, this disclosure does not require the operator to actively push mobile phone number status, avoiding the problems of operator omissions or complex push processes.

[0080] Furthermore, according to embodiments of this disclosure, any and multiple modules among the server receiving module 21, server obtaining module 22, server determining module 23, and server marking module 24 can be combined into one module, or any one of these modules can be split into multiple modules. Alternatively, at least some of the functions of one or more of these modules can be combined with at least some of the functions of other modules and implemented in one module.

[0081] According to embodiments of this disclosure, at least one of the server receiving module 21, server acquiring module 22, server determining module 23, and server marking module 24 can be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging the circuitry, or implemented in any one of the three methods of software, hardware, and firmware, or in a suitable combination of any of these.

[0082] Alternatively, at least one of the server receiving module 21, server obtaining module 22, server determining module 23, and server marking module 24 can be implemented at least partially as a computer program module, which can perform corresponding functions when the computer program module is run.

[0083] Figure 7 A flowchart illustrating a method for processing a reserved mobile phone number according to an embodiment of the present disclosure is shown.

[0084] like Figure 7 As shown, the method for processing the reserved mobile phone number in this embodiment includes operations S410 to S460.

[0085] When operating S410, the client identifies risky reserved mobile phone numbers through a risk identification model. Here, the client can be understood as a banking system. Within the banking system, there is a risk of secondary number allocation among the mobile phone numbers reserved by customers. The risk identification model can identify these risky reserved mobile phone numbers. Of course, the client can also be understood as other business systems; no specific limitation is made here. The following explanation primarily uses a banking system as an example.

[0086] Existing methods for identifying risky phone numbers primarily rely on two types of risk characteristics: those based on the phone's address book and those based on the client's account communication information. Understandably, these methods mainly compare the differences between the user names in the phone's address book and the client's account system. Since the client's account system is closely tied to the application it belongs to—for example, when a client uses a shared account to log in to an application—the account system tends to include colleague information; while the address book provides more comprehensive information. Therefore, this approach has some limitations.

[0087] As one possible way to achieve this, such as Figure 8 As shown, the S410 client identifies the risk-reserved mobile phone number through the risk identification model, specifically including operations S411 to S413.

[0088] When operating S411, the risk identification model periodically retrieves the registered mobile phone number. This period can be configured via parameters, allowing for different periods such as weekly, monthly, or quarterly.

[0089] In operation S412, the reserved mobile phone number is compared with the judgment conditions in the risk identification model.

[0090] In operation S413, when the reserved mobile phone number meets the judgment conditions, the reserved mobile phone number is regarded as a risk reserved mobile phone number.

[0091] The main criteria for judgment can be established using customer information and historical transaction data within the banking system. Because the banking system has a large customer base and a large number of registered mobile phone numbers, a multi-level screening method can be employed.

[0092] First, the system can obtain the most recent modification time and SMS verification information of the mobile phone number. The most recent modification time of the mobile phone number, that is, the time when the customer last modified the mobile phone number in the bank system (or the registration time if it is the first registration), and whether the customer has successfully completed SMS verification in the bank system recently, are used to initially screen the reserved mobile phone numbers.

[0093] The most recent modification time can be freely configured. For example, a mobile number that has been reissued needs to be frozen for at least 90 days before being reissued, so the most recent modification time can be set to 90 days. Mobile numbers whose most recent modification time is within 90 days or whose SMS verification has been completed in the bank's system within 90 days can be directly excluded. Then, by using indicators such as the most recent modification time of the mobile number and the most recent login time through bank channels, corresponding values ​​are assigned according to different time intervals and different weights, ultimately obtaining the total risk of the mobile number. The total risk is then compared with a risk threshold to determine whether the reserved mobile number should be regarded as a risky reserved mobile number.

[0094] Secondly, the region where the mobile phone number was registered can be obtained. According to information released by relevant departments, such as the concentration of many risky behaviors in a certain area, if the region where the mobile phone number was registered is the same as the concentration of such risky behaviors, then the reserved mobile phone number can be used as a risk reserved mobile phone number.

[0095] Additionally, transaction information related to the mobile phone number can be obtained. For example, transaction records within the banking system showing customers using that mobile phone number for authentication or associated with it can be retrieved. This allows for comparison of past transactions with recent transactions from multiple perspectives, such as spending habits, frequency, merchant affiliation, and region. The difference between the characteristics of recent transactions using that mobile phone number and those of past transactions is then compared to a threshold to determine whether the reserved mobile phone number should be considered a risky reserved mobile phone number.

[0096] Finally, login information for mobile phone numbers can be obtained. Based on various online and offline channels within the banking system, the login information of customers on various channels within the banking system can be obtained, including indicators such as login time, frequency, and frequently used devices. For example, if the device that was recently logged in is not a frequently used device registered in the system, then the reserved mobile phone number will be regarded as a risk reserved mobile phone number.

[0097] Therefore, by operating S411 to S413, it is easy to call the risk identification model to identify the risk-reserved mobile phone number.

[0098] When operating the S420, the client transmits the risk-preserving mobile phone number to the server. The server can be understood as the service provider's system, which provides the mobile phone number activation and maintenance services. Of course, the server can also be understood as other business systems that provide services; no specific limitations are made here.

[0099] When operating S430, the server obtains the status information and network access time of the risk-reserved mobile phone number based on the risk-reserved mobile phone number.

[0100] When operating S440, the server determines the judgment rules to be invoked in the secondary number issuance identification model based on the status information.

[0101] When operating the S450, risk-preserved mobile phone numbers are marked according to the judgment rules, and the marking results are transmitted to the client.

[0102] When operating S460, the client processes the risk-reserved mobile phone numbers based on the tagging results.

[0103] According to the method for processing reserved mobile phone numbers in this disclosure, the client identifies risky reserved mobile phone numbers through a risk identification model and transmits them to the server. The server can perform status identification and secondary number release judgment on the risky reserved mobile phone numbers, and then return the marked risky reserved mobile phone numbers to the client. The client can then process the risky reserved mobile phone numbers according to the marking results, thereby reducing losses to users caused by secondary number release. Compared with the prior art, this disclosure has a shorter transaction chain, enabling rapid response; furthermore, this disclosure does not require operators to actively push mobile phone number status updates, avoiding the problems of operators missing updates or complex update processes.

[0104] In some specific examples, the marking result can be a secondary number release, a non-secondary number release, or an abnormal state, such as... Figure 9 As shown, the S460 client processes the risk-reserved mobile phone number based on the marking results, specifically including operation S461.

[0105] In operation S461, when the marking result is a secondary number release or an abnormal state, the corresponding risky reserved mobile phone number is added to the blacklist. This facilitates subsequent measures to be taken against reserved mobile phone numbers added to the blacklist, such as... Figure 10 As shown, operation S470 is executed: business restrictions are imposed on the risky reserved mobile phone numbers in the blacklist, thereby protecting the customer's property security.

[0106] Based on the above-described method for processing reserved mobile phone numbers, this disclosure also provides a processing device 40 for reserved mobile phone numbers. The following will be combined with... Figures 11-16 The processing device 40 for the reserved mobile phone number is described in detail.

[0107] Figure 11 The diagram illustrates the structure of a pre-reserved mobile phone number processing apparatus 10 according to an embodiment of the present disclosure.

[0108] The processing device 40 for the reserved mobile phone number includes an identification module 1, a transmission module 2, an acquisition module 3, a determination module 4, a marking module 5, and a processing module 6.

[0109] Identification Module 1: The client identifies the risk-reserved mobile phone number through the risk identification model in Identification Module 1.

[0110] Transmission module 2: The client transmits the risk-preserved mobile phone number to the server through transmission module 2.

[0111] Module 3 is used by the server to obtain the status information and network access time of the risk-reserved mobile phone number based on the risk-reserved mobile phone number.

[0112] Module 4 is used by the server to determine the judgment rules to be invoked in the secondary number release identification model based on the status information.

[0113] The marking module 5 is used to mark risk-reserved mobile phone numbers according to the judgment rules and transmit the marking results to the client.

[0114] Processing module 6 allows the client to process the risk-reserved mobile phone numbers based on the marking results.

[0115] Figure 12 A schematic block diagram of the determining module 4 according to an embodiment of the present disclosure is shown. The determining module 4 includes a first calling unit 41 and a second calling unit 42. The status information includes normal and abnormal states.

[0116] When the status information is normal, the first calling unit 41 calls the first judgment rule in the secondary number release identification model. The first judgment rule is to compare the network access time with the registration time of the risk reserved mobile phone number on the client.

[0117] When the status information is abnormal, the second calling unit 42 calls the second judgment rule in the secondary number release recognition model.

[0118] Figure 13 A schematic block diagram of a marking module 5 according to an embodiment of the present disclosure is shown. The marking module 5 includes a first marking unit 51, a second marking unit 52, and a first transmission unit 53.

[0119] When the network access time is earlier than the registration time of the risk-reserved mobile number on the client, the first marking unit 51 marks the risk-reserved mobile number as not being reissued.

[0120] When the network access time is later than the registration time of the risk-reserved mobile phone number on the client, the second marking unit 52 marks the risk-reserved mobile phone number as a secondary number release.

[0121] The first transmission unit 53 transmits the marking result (either non-secondary numbering or secondary numbering) to the client.

[0122] Figure 14 A schematic block diagram of a marking module 5 according to an embodiment of the present disclosure is shown. The marking module 5 includes a third marking unit 54 and a second transmission unit 55.

[0123] The third marking unit 54 marks the risk-reserved mobile phone number as an abnormal state.

[0124] The second transmission unit 55 transmits the abnormal status of the marking result to the client.

[0125] Figure 15 A schematic block diagram of a processing module 6 according to an embodiment of the present disclosure is shown. The processing module 6 includes a processing unit 61.

[0126] When the marking result is a secondary number release or an abnormal state, the processing unit 61 adds the corresponding risk-preserved mobile phone number to the blacklist.

[0127] Figure 16 A schematic block diagram of a reserved mobile phone number processing apparatus 40 according to an embodiment of the present disclosure is shown. The reserved mobile phone number processing apparatus 40 also includes a limiting module 7.

[0128] Restriction Module 7 restricts the business of risky reserved mobile phone numbers in the blacklist.

[0129] According to the reserved mobile phone number processing device 40 of this disclosure, the client identifies risky reserved mobile phone numbers through a risk identification model and transmits them to the server. The server can perform status identification and secondary number release judgment on the risky reserved mobile phone numbers, and then return the marked risky reserved mobile phone numbers to the client. The client can then process the risky reserved mobile phone numbers according to the marking results, thereby reducing losses to users caused by secondary number release. Compared with the prior art, this disclosure has a shorter transaction chain, enabling rapid response; furthermore, this disclosure does not require operators to actively push mobile phone number status updates, avoiding the problems of operators missing updates or complex update processes.

[0130] Furthermore, according to embodiments of this disclosure, any multiple modules among the identification module 1, transmission module 2, acquisition module 3, determination module 4, marking module 5, and processing module 6 can be combined into one module, or any one of these modules can be split into multiple modules. Alternatively, at least some of the functions of one or more of these modules can be combined with at least some of the functions of other modules and implemented in one module.

[0131] According to embodiments of this disclosure, at least one of the identification module 1, transmission module 2, acquisition module 3, determination module 4, marking module 5, and processing module 6 can be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging the circuitry, or implemented in any one of the three methods of software, hardware, and firmware, or in a suitable combination of any of these.

[0132] Alternatively, at least one of the identification module 1, transmission module 2, acquisition module 3, determination module 4, marking module 5, and processing module 6 can be at least partially implemented as a computer program module, which can perform corresponding functions when the computer program module is run.

[0133] The processing apparatus for a reserved mobile phone number according to embodiments of the present disclosure is described in detail below. It is to be understood that the following description is merely illustrative and not intended to limit the scope of the present disclosure.

[0134] This disclosure provides a processing device for reserved mobile phone numbers based on bank card quick payment agreements, used for identifying secondary number issuance. The device includes: an identification module for identifying reserved mobile phone numbers within the bank system that may pose a risk of secondary issuance; a query module for querying the status of the reserved mobile phone number on the operator's side; a notification module for notifying the customer to change the mobile phone number if it is confirmed as a secondary issuance number; and a transaction control module for controlling the business operations of the corresponding mobile phone number before the number change. This allows for full-process pre-emptive risk control of secondary issuance mobile phone numbers within the bank system. The reserved mobile phone number processing device of this disclosure executes a processing method for reserved mobile phone numbers based on bank card quick payment agreements, used for identifying secondary issuance numbers. This includes: identifying mobile phone numbers within the bank system that may pose a risk of secondary issuance; querying the status of the mobile phone number on the operator's side; if it is confirmed as a secondary issuance number, notifying the customer to change the mobile phone number; and controlling the business operations of the corresponding mobile phone number before the number change, thereby allowing for full-process pre-emptive risk control of secondary issuance mobile phone numbers within the bank system.

[0135] The identification module identifies mobile phone numbers within the bank's system that may pose a risk of secondary number allocation. This module periodically identifies mobile phone numbers within the bank's internal reserved mobile phone number system that are at risk of secondary number allocation. The identification period can be configured via parameters, supporting different periods such as monthly or weekly. The criteria for identifying mobile phone numbers at risk of secondary number allocation are freely configurable and can be implemented by constructing a secondary number allocation risk identification model.

[0136] The query module checks the status of mobile phone numbers at risk of being re-issued by the operator. The bank's system sends a request to the operator's system, providing the mobile phone number and its registration date with the bank. After receiving and verifying the request, the operator compares the registration date from the bank with the number's network access date on the operator's side. If the registration date is earlier than the network access date, the number is considered a re-issued number; if the registration date is later than the network access date, the number is not considered a re-issued number. If the mobile phone number is in a canceled and not re-registered state on the operator's side, the status of the mobile phone number is returned synchronously.

[0137] The notification module, if confirmed as a reissued phone number, will notify the customer to change their phone number. After receiving the phone number's status from the carrier system, the bank system will determine if the number is reissued, cancelled, or not re-registered. If so, the bank will notify the customer to change their registered phone number and add the number to a suspicious phone number list. Notification methods can include phone call, SMS, and mobile banking app messages; the notification phone number will be one of the customer's registered phone numbers with the bank, excluding the original number.

[0138] The transaction control module controls business operations for the corresponding mobile number before the mobile number is changed. When a transaction involves judging the mobile number, it first checks the suspicious mobile number list to determine if the mobile number belongs to the list. If the mobile number involved in the transaction belongs to the suspicious mobile number list, the transaction is rejected, and the customer is prompted to change the reserved mobile number.

[0139] The following steps, Steps 1 to 12, detail the process for handling the reserved mobile phone number.

[0140] Step 1: The bank system identifies mobile phone numbers among the reserved mobile phone numbers that have the risk of being reissued, based on a pre-set cycle and a secondary number issuance risk identification model.

[0141] Step 2: The bank sends the selected mobile phone numbers with the risk of being reissued to the operator's system along with their registration time.

[0142] Step 3: The operator receives the mobile phone number and registration time from the bank.

[0143] Step 4: The operator checks the status and registration time of the mobile number.

[0144] Step 5: The operator determines the correct phone number status to return based on the queried phone number status and network access time.

[0145] A. The mobile phone number is in normal status. Compare the network access time with the registration time.

[0146] A1. If the network access time is earlier than the registration time, then the mobile number is not a secondary number.

[0147] A2. If the network access time is later than the registration time, then the mobile number is a secondary number.

[0148] B. If the mobile number is not in a normal state, the current status of the mobile number will be returned directly.

[0149] Step 6: The bank system receives the results returned by the operator, including information such as the mobile number status and the time of network access.

[0150] Step 7: The bank determines the status of the mobile phone number based on the received results.

[0151] A. If the mobile number is in normal status, then the mobile number is a normal mobile number and no operation is required.

[0152] B. If the mobile number is in an abnormal state such as being reissued or canceled, proceed to Step 8.

[0153] Step 8: The bank adds the mobile phone number to the list of suspicious mobile phone numbers, restricting the processing of business transactions that require verification of that mobile phone number.

[0154] Step 9: The bank checks the customer's other registered mobile phone numbers and sends a text message to remind the customer to change their registered mobile phone number.

[0155] Step 10: The customer receives an SMS notification.

[0156] Step 11: Customers complete operations such as changing or deleting their reserved mobile phone number in the bank's system.

[0157] Step 12: After the customer completes the operation, the bank system will remove the mobile phone number from the list of suspicious mobile phone numbers.

[0158] The aforementioned secondary number issuance risk identification model primarily establishes risk identification indicators based on customer information and historical transaction data within the banking system. Due to the large customer base and numerous registered mobile phone numbers within the banking system, a multi-level screening method is employed. First, mobile phone numbers are initially screened based on two indicators: the most recent modification time of the mobile phone number (the time when the customer last modified the mobile phone number within the banking system; if it's the initial registration, then the registration time) and whether the number has recently successfully completed SMS verification within the banking system. The judgment period can be configurable; for example, mobile phone numbers subject to secondary issuance must be frozen for at least 90 days before re-issuance, and a 90-day period can be selected. Mobile phone numbers whose most recent modification time is within the last 90 days or whose number has completed SMS verification within the last 90 days can be directly excluded. Then, indicators such as the most recent modification time of the mobile phone number and the most recent login time through banking channels are assigned corresponding values ​​and weights according to different time intervals, ultimately yielding the total risk of the mobile phone number.

[0159] The method of identifying whether a mobile number has been reissued by the operator mainly involves comparing the registration time (or registration date) of the mobile number in the bank's system with the network access time (or network access time) of the mobile number on the operator's side. If the registration time is earlier than the network access time, it means that the mobile number was first registered and authenticated in the bank's system, and then accessed by the operator. This indicates that the mobile number was at least canceled, reissued, and activated once after being registered in the bank's system, thus confirming that the mobile number has been reissued. If the registration time is later than the network access time, it means that the mobile number was first accessed by the operator, and then registered in the bank's system. Furthermore, if the mobile number is currently in normal status, consistent with the typical status of a mobile number, then the mobile number has not been reissued.

[0160] The banking system uses different methods to remind customers to change their phone numbers based on how long the number has been on the suspicious list. First, it sends an SMS reminder. Second, it can reach customers through the bank's own channels, such as the mobile banking app. Finally, it provides targeted voice customer service prompts to customers who have not changed their phone numbers for a long time, until the phone number is changed or deleted, and then the phone number is removed from the suspicious list.

[0161] Figure 17 A block diagram schematically illustrates an electronic device suitable for implementing the above-described method according to an embodiment of the present disclosure.

[0162] like Figure 17 As shown, an electronic device 900 according to an embodiment of the present disclosure includes a processor 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage portion 908 into a random access memory (RAM) 903. The processor 901 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 901 may also include onboard memory for caching purposes. The processor 901 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0163] RAM 903 stores various programs and data required for the operation of electronic device 900. Processor 901, ROM 902, and RAM 903 are interconnected via bus 904. Processor 901 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 902 and / or RAM 903. It should be noted that the programs may also be stored in one or more memories other than ROM 902 and RAM 903. Processor 901 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in said one or more memories.

[0164] According to embodiments of this disclosure, the electronic device 900 may further include an input / output (I / O) interface 905, which is also connected to a bus 904. The electronic device 900 may also include one or more of the following components connected to the I / O interface 905: an input section 906 including a keyboard, mouse, etc.; an output section 907 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN card, modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the input / output (I / O) interface 905 as needed. A removable medium 911, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 910 as needed so that computer programs read from it can be installed into the storage section 908 as needed.

[0165] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0166] According to embodiments of this disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as including, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 902 and / or RAM 903 and / or one or more memories other than ROM 902 and RAM 903 described above.

[0167] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to cause the computer system to implement the methods of the embodiments of this disclosure.

[0168] When the computer program is executed by the processor 901, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0169] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and downloaded and installed via the communication section 909, and / or installed from a removable medium 911. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0170] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 909, and / or installed from the removable medium 911. When the computer program is executed by the processor 901, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0171] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0172] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0173] Those skilled in the art will understand that the features described in the various embodiments and / or claims of this disclosure can be combined and / or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure can be combined and / or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0174] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A method for processing reserved mobile phone numbers, applied to the server side, characterized in that, include: Receive the risk-reserved mobile phone number, wherein the risk-reserved mobile phone number is identified by the client calling the risk identification model; Based on the risk-reserved mobile phone number, obtain the status information and network access time of the risk-reserved mobile phone number; Based on the aforementioned status information, determine the judgment rules to be invoked in the secondary number issuance identification model; and The risk-reserved mobile phone number is marked according to the judgment rules, and the marking result is transmitted to the client. The status information includes normal and abnormal states. The step of determining the judgment rule to be invoked in the secondary number issuance identification model based on the status information specifically includes: When the status information is normal, the first judgment rule in the secondary number allocation identification model is invoked, wherein the first judgment rule is a comparison between the network access time and the registration time of the risk-reserved mobile phone number on the client; and When the status information is abnormal, the second judgment rule in the secondary number release identification model is invoked, wherein the second judgment rule is to mark the risk reserved mobile phone number as abnormal.

2. The method according to claim 1, characterized in that, The step of marking the risk-reserved mobile phone number according to the first determination rule and transmitting the marking result to the client specifically includes: When the network access time is earlier than the registration time of the risk-reserved mobile number on the client, the risk-reserved mobile number is marked as not being reissued. When the network access time is later than the registration time of the risky reserved mobile number on the client, the risky reserved mobile number is marked as a secondary number release; and The marking result (either non-secondary or secondary marking result) is transmitted to the client.

3. The method according to claim 2, characterized in that, The step of marking the risk-reserved mobile phone number according to the second determination rule and transmitting the marking result to the client specifically includes: Mark the aforementioned risk-reserved mobile phone number as abnormal; and The abnormal status of the marked result is transmitted to the client.

4. A processing device for reserved mobile phone numbers, applied to a server, characterized in that, include: A server-side receiving module is used to receive risk-reserved mobile phone numbers, wherein the risk-reserved mobile phone numbers are identified by the client calling the risk identification model; The server-side acquisition module is used to obtain the status information and network access time of the risk-reserved mobile phone number based on the risk-reserved mobile phone number. The server-side determination module is used to determine the judgment rules to be invoked in the secondary number release identification model based on the status information; and The server-side marking module is used to mark the risk-reserved mobile phone number according to the judgment rules and transmit the marking result to the client. The status information includes normal and abnormal states. The step of determining the judgment rule to be invoked in the secondary number issuance identification model based on the status information specifically includes: When the status information is normal, the first judgment rule in the secondary number allocation identification model is invoked, wherein the first judgment rule is a comparison between the network access time and the registration time of the risk-reserved mobile phone number on the client; and When the status information is abnormal, the second judgment rule in the secondary number release identification model is invoked, wherein the second judgment rule is to mark the risk reserved mobile phone number as abnormal.

5. A method for processing reserved mobile phone numbers, characterized in that, include: The client identifies risky reserved mobile phone numbers through a risk identification model; The client transmits the risk-preserving mobile phone number to the server. The server obtains the status information and network access time of the risk-reserved mobile phone number based on the risk-reserved mobile phone number. The server determines the judgment rule to be invoked in the secondary number release identification model based on the status information. The risk-reserved mobile phone number is marked according to the judgment rules, and the marking result is transmitted to the client; as well as The client processes the risk-reserved mobile phone number based on the tagging result. The status information includes normal and abnormal states. The step of determining the judgment rule to be invoked in the secondary number issuance identification model based on the status information specifically includes: When the status information is normal, the first judgment rule in the secondary number allocation identification model is invoked, wherein the first judgment rule is a comparison between the network access time and the registration time of the risk-reserved mobile phone number on the client; and When the status information is abnormal, the second judgment rule in the secondary number release identification model is invoked, wherein the second judgment rule is to mark the risk reserved mobile phone number as abnormal.

6. The method according to claim 5, characterized in that, The marking result is categorized as secondary number release, non-secondary number release, or abnormal status. The client processes the risk-reserved mobile phone number based on the marking result, specifically including: When the marking result is a secondary number release or an abnormal state, the corresponding risky reserved mobile phone number will be added to the blacklist.

7. A processing device for a reserved mobile phone number, characterized in that, include: The identification module allows the client to identify the risky reserved mobile phone number using the risk identification model within the module. The client transmits the risk-preserved mobile phone number to the server through the transmission module. The server obtains the status information and network access time of the risk-reserved mobile phone number based on the risk-reserved mobile phone number through the acquisition module. The determination module allows the server to determine the judgment rules to be invoked in the secondary number release identification model based on the status information. The marking module is used to mark the risk-reserved mobile phone number according to the judgment rules and transmit the marking result to the client; as well as The processing module allows the client to process the risk-reserved mobile phone number based on the tagging results. The status information includes normal and abnormal states. The step of determining the judgment rule to be invoked in the secondary number issuance identification model based on the status information specifically includes: When the status information is normal, the first judgment rule in the secondary number allocation identification model is invoked, wherein the first judgment rule is a comparison between the network access time and the registration time of the risk-reserved mobile phone number on the client; and When the status information is abnormal, the second judgment rule in the secondary number release identification model is invoked, wherein the second judgment rule is to mark the risk reserved mobile phone number as abnormal.

8. An electronic device, characterized in that, include: One or more processors; One or more memories are provided for storing executable instructions that, when executed by the processor, implement the method according to any one of claims 1 to 3 or any one of claims 5 to 6.

9. A computer-readable storage medium, characterized in that, The storage medium stores executable instructions that, when executed by a processor, implement the method according to any one of claims 1 to 3 or any one of claims 5 to 6.

10. A computer program product, characterized in that, The method includes a computer program comprising one or more executable instructions that, when executed by a processor, implement the method according to any one of claims 1 to 3 or any one of claims 5 to 6.

Images