Secondary number identification method and device, electronic equipment and storage medium
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- BEIJING BAIDU NETCOM SCI & TECH CO LTD
- Filing Date
- 2026-05-18
- Publication Date
- 2026-08-07
AI Technical Summary
由于互联网平台的账号体系普遍采用手机号码作为核心身份凭证,因此二次放号会导致新用户继承原来的用户的账号绑定关系,从而引发账号盗用、隐私泄露、资产损失等安全风险
[0018]应当理解,本部分所描述的内容并非旨在标识本公开的实施例的关键或重要特征,也不用于限制本公开的范围。本公开的其它特征将通过以下的说明书而变得容易理解。
Smart Images

Figure CN122534419A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of artificial intelligence technology, particularly to the fields of internet platforms, information security and cloud computing, and especially to secondary number identification methods, devices, electronic devices and storage media. Background Technology
[0002] Re-issuance of phone numbers refers to the process by which mobile operators reassign a user's canceled phone number to a new user after a freeze period. Since internet platforms commonly use phone numbers as core identity credentials, re-issuance can lead to new users inheriting the original user's account bindings, potentially causing security risks such as account theft, privacy breaches, and asset losses. Summary of the Invention
[0003] This disclosure provides a method, apparatus, electronic device, and storage medium for identifying secondary number issuance.
[0004] A method for identifying secondary number allocation includes:
[0005] Obtain the business requests sent by users to the target platform's services;
[0006] In response to determining that the service request carries a mobile phone number and that the mobile phone number needs to be re-identified, a pre-identification strategy is used to perform pre-identification on the mobile phone number;
[0007] In response to identifying the mobile phone number as a suspected secondary number through the pre-identification, the operator detection interface is called to perform post-identification on the mobile phone number to obtain the target identification result of whether the mobile phone number is a secondary number.
[0008] A secondary number issuance identification device includes: a request acquisition module, a pre-identification module, and a post-identification module;
[0009] The request acquisition module is used to acquire the business requests sent by the user for the target platform's business.
[0010] The pre-identification module is used to respond to determining that the service request carries a mobile phone number and that the mobile phone number needs to be identified for secondary number allocation, and to perform pre-identification of the mobile phone number using a pre-identification strategy;
[0011] The post-recognition module is used to respond to the fact that the mobile phone number is identified as a suspected secondary number through the pre-recognition, and to perform post-recognition on the mobile phone number by calling the operator detection interface to obtain the target recognition result of whether the mobile phone number is a secondary number.
[0012] An electronic device, comprising:
[0013] At least one processor; and
[0014] A memory communicatively connected to the at least one processor; wherein,
[0015] The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method described above.
[0016] A non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the methods described above.
[0017] A computer program product includes a computer program / instructions that, when executed by a processor, implement the method described above.
[0018] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description
[0019] The accompanying drawings are provided to better understand this solution and do not constitute a limitation of this disclosure. Wherein:
[0020] Figure 1 This is a flowchart of an embodiment of the secondary number identification method described in this disclosure;
[0021] Figure 2 A flowchart illustrating an embodiment of the pre-filtering process described in this disclosure;
[0022] Figure 3 This is a flowchart of an embodiment of the method for pre-identifying mobile phone numbers using a pre-identification strategy as described in this disclosure;
[0023] Figure 4 This is a flowchart illustrating an embodiment of the method for generating target identification results for suspected secondary number releases as described in this disclosure;
[0024] Figure 5 This is a schematic diagram of the composition structure of Embodiment 500 of the secondary number identification device described in this disclosure;
[0025] Figure 6 A schematic block diagram of an electronic device 600 that can be used to implement embodiments of the present disclosure is shown. Detailed Implementation
[0026] The exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments to aid understanding, and should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this disclosure. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.
[0027] Furthermore, it should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.
[0028] Figure 1 This is a flowchart illustrating an embodiment of the secondary number identification method described in this disclosure. Figure 1 As shown, the specific implementation methods are as follows.
[0029] In step 101, the service requests sent by the user to the target platform are obtained.
[0030] In step 102, in response to determining that the service request carries a mobile phone number and that the mobile phone number needs to be re-identified, the mobile phone number is pre-identified using a pre-implementation strategy.
[0031] In step 103, in response to identifying the mobile phone number as a suspected secondary number through pre-identification, the mobile phone number is identified by calling the operator detection interface to obtain the target identification result of whether the mobile phone number is a secondary number.
[0032] Traditionally, identifying phones reissued through secondary number distribution typically involves offline batch scanning, which periodically scans and compares all users to determine which numbers are being reissued. However, this method cannot cover real-time business request scenarios, has poor timeliness, and therefore offers limited protection against security risks.
[0033] The solution described in the above method embodiment can determine in real time whether the corresponding mobile phone number is a secondary number issued by a user for a business request, thereby improving timeliness and reducing security risks. Moreover, considering that the cost of calling the operator's detection interface is usually high (e.g., requiring high payment costs), a pre-identification strategy can be used to identify the mobile phone number in advance. The operator's detection interface is only called when the mobile phone number is identified as a suspected secondary number issued by the pre-identification, thereby reducing implementation costs. In addition, for suspected secondary numbers, the accuracy of the target identification result can be improved by calling the operator's detection interface to generate the final target identification result, thereby further reducing security risks.
[0034] It should be noted that the mobile phone numbers and other information mentioned in the embodiments of this disclosure are not targeted at any specific user and are not intended to reflect the personal information of any specific user. Furthermore, the entity executing the method described in this disclosure can obtain the aforementioned information through various public, legal, and compliant means, such as obtaining it from the user with their authorization. The collection, storage, use, processing, transmission, provision, and disclosure of any type of information, such as user personal information, involved in the technical solutions of this disclosure comply with relevant laws and regulations and do not violate public order and good morals.
[0035] The execution entity of the method described in this disclosure can be a secondary number allocation identification system, and the service request can refer to an identity verification request, etc. In practical applications, after obtaining the service request issued by the user, the system's degradation switch status can be queried first. If it is determined that the degradation switch status is on, that is, the system is in degradation mode (such as when the operator detects a large-scale interface failure), the subsequent secondary number allocation identification process can be skipped directly, and the service request processing process can be executed directly to ensure service availability. The degradation switch status can be manually set.
[0036] If it is determined that the system is not in degraded mode, the subsequent secondary number allocation identification process can continue. If the response confirms that the business request includes a mobile phone number and it is determined that secondary number allocation identification is required, a pre-emptive strategy can be used to perform pre-emptive identification of the mobile phone number.
[0037] In some embodiments of this disclosure, the service request may be verified first. The verification includes at least: verifying whether the service request includes a mobile phone number and whether the format of the mobile phone number meets the requirements. In response to determining that the verification is successful, it may be determined whether the mobile phone number needs to be reissued for identification based on the type of the mobile phone number.
[0038] For example, it can verify whether the business request includes a mobile phone number (mobile phone number non-empty verification), whether the mobile phone number format meets the requirements (format compliance verification), and the validity of the business scenario identifier. If any verification fails, the verification is considered failed, and an error type can be returned to the user, rejecting the business request. If the verification is successful, it can be determined whether the mobile phone number needs to be re-identified based on its type.
[0039] The above processing can quickly filter out invalid and illegal requests, avoid invalid identification processes, improve identification efficiency, and reduce resource waste.
[0040] In some embodiments of this disclosure, the method for determining whether a mobile phone number needs to be re-issued based on its type may include: in response to determining that a mobile phone number is associated with an account, identifying the type of the mobile phone number through a number prefix identification method and / or an operator number segment database query identification method; and in response that the type of the mobile phone number is not the target type, determining that the mobile phone number needs to be re-issued.
[0041] For example, user information corresponding to a mobile phone number can be obtained, which may include various information related to the user. If the user information is empty, it means that the mobile phone number is not associated with an account, and it can be determined that there is no need to perform secondary number recognition on the mobile phone number, and the business request processing process can be directly executed.
[0042] If it is determined that a mobile phone number is associated with an account, the type of the mobile phone number can be identified. If the type of the mobile phone number is identified as not being the target type, it can be determined that the mobile phone number needs to be re-identified for secondary number release. The target type may include overseas numbers, virtual operator numbers, and IoT card numbers, etc.
[0043] By using the above processing method, by first determining whether the mobile phone number is associated with an account, numbers without account binding can be directly filtered out, avoiding the need to perform subsequent identification processes on risk-free numbers. Then, by combining the number type for further filtering, only mobile phone numbers with account association and belonging to non-target types are identified, thereby significantly reducing invalid identification and improving identification efficiency.
[0044] The process described above, after confirming that the system is not in degraded mode, can be called the pre-filtering process. Based on the above introduction, Figure 2 This is a flowchart illustrating an embodiment of the pre-filtering process described in this disclosure. Figure 2 As shown, the specific implementation methods are as follows.
[0045] In step 201, the business request is validated to determine whether the validation passes. If not, step 202 is executed; if yes, step 203 is executed.
[0046] For example, it can verify whether the business request includes a mobile phone number and whether the format of the mobile phone number meets the requirements.
[0047] In step 202, an error type is returned, the current business request is rejected, and the process ends.
[0048] In step 203, it is determined whether the mobile phone number carried in the service request is associated with an account. If not, step 204 is executed; if so, step 205 is executed.
[0049] In step 204, the business request processing flow is executed, and then the flow ends.
[0050] In step 205, the mobile phone number is identified as an overseas number by using the number prefix identification method. If it is, step 204 is executed; otherwise, step 206 is executed.
[0051] For example, the prefix of a mobile phone number can be extracted and matched with a preset database of overseas number segments. If a match is found, the number can be identified as an overseas number.
[0052] In step 206, the mobile phone number is identified by querying the operator number segment database. If it is, step 204 is executed; otherwise, step 207 is executed.
[0053] For example, the first few digits of a mobile phone number can be matched with a locally maintained database of operator number segments to check whether the number segment belongs to a virtual operator. If so, it can be determined to be a virtual operator number.
[0054] In step 207, the mobile phone number is identified as an IoT card number by using the number prefix identification method. If it is, step 204 is executed; otherwise, step 208 is executed.
[0055] For example, the prefix of a mobile phone number can be extracted and compared with a pre-set database of IoT card-specific number segments. If a match is found, the number can be identified as an IoT card number.
[0056] In step 208, it is determined that the mobile phone number needs to be reissued for identification, and then the process ends.
[0057] Mobile phone numbers from overseas, virtual operators, and IoT cards may not require secondary number identification due to the lack of support from the operator's detection interface or the special nature of the business.
[0058] If it is determined that secondary identification of mobile phone numbers is required, a pre-identification strategy can be used first to identify the mobile phone numbers.
[0059] In some embodiments of this disclosure, the method of pre-identifying mobile phone numbers using a pre-selection strategy may include: determining the target device used by the user to issue the service request, and pre-identifying the mobile phone number based on the interaction information between the target device, the mobile phone number, and the target platform. The target device may refer to the mobile phone used by the user, etc.
[0060] Specifically, in some embodiments of this disclosure, in response to determining that the target device is a verified and frequently used device corresponding to a mobile phone number, the mobile phone number can be determined as a non-reissued number. In response to determining that the target device is not a verified and frequently used device, the device fingerprint of the target device can be obtained. In response to determining that the device fingerprint is in the user's trusted device list, the mobile phone number can be determined as a non-reissued number. In response to determining that the device fingerprint is not in the trusted device list, but determining that the mobile phone number has undergone SMS verification code verification on the target platform within the first time window, the mobile phone number can be determined as a non-reissued number. The end time of the first time window is the current time. In response to determining that the device fingerprint is not in the trusted device list and determining that the mobile phone number has not undergone SMS verification code verification within the first time window, the mobile phone number can be determined as a suspected reissued number.
[0061] By adopting the above processing method, through multi-factor serial judgment based on verified commonly used devices, trusted device lists, and recent SMS verification records, a large number of normal users can be efficiently identified and filtered out without calling high-cost operator detection interfaces, thereby significantly reducing the identification cost. Moreover, this multi-factor progressive judgment method can reduce misjudgments caused by a one-size-fits-all approach, thereby further improving the accuracy of the pre-identification results.
[0062] Based on the above introduction, Figure 3 This is a flowchart illustrating an embodiment of the method for pre-identifying mobile phone numbers using a pre-identification strategy as described in this disclosure. Figure 3 As shown, the specific implementation methods are as follows.
[0063] In step 301, the target device used by the user to send the service request is determined, and it is determined whether the target device is a verified and frequently used device corresponding to the mobile phone number. If so, step 302 is executed; otherwise, step 303 is executed.
[0064] Device identity mapping detection can then be performed. The device identity mapping system can be used to query the association between the target device and the mobile phone number. If it is determined that the target device is a verified and frequently used device corresponding to the mobile phone number, it can be determined that the holder of the mobile phone number has not changed, and step 302 can be executed.
[0065] In step 302, the mobile phone number is determined to be a non-secondary number, and then the process ends.
[0066] For numbers that are not reissued, the normal business request processing procedure can be followed.
[0067] In step 303, the device fingerprint of the target device is obtained, and it is determined whether the device fingerprint is in the user's trusted device list. If so, step 302 is executed; otherwise, step 304 is executed.
[0068] For example, the trusted device service can be invoked to determine whether the target device's device fingerprint is in the user's trusted device list. If the target device is trusted, the mobile phone number can also be determined to be a non-reissued number.
[0069] In step 304, it is determined whether the mobile phone number has been verified by SMS verification code on the target platform within the first time window. If so, step 302 is executed; otherwise, step 305 is executed.
[0070] The specific duration of the first time window can be determined according to actual needs, and the end time can be the current time.
[0071] If it is confirmed that the mobile phone number has been verified by SMS verification code on the target platform within the first time window, that is, if a recent verification record exists, it means that the holder of the mobile phone number is still using the number normally during this period. Therefore, the mobile phone number can be identified as a non-reissued number.
[0072] In step 305, the mobile phone number is identified as a suspected secondary number, and then the process ends.
[0073] In addition, in some embodiments of this disclosure, after determining that the mobile phone number is not a secondary number, in response to determining that the mobile phone number is a secondary number through offline verification, the reason for the identification error can be analyzed, and the pre-processing strategy can be optimized based on the reason.
[0074] In other words, after a mobile phone number is determined to be a non-reissued number through pre-identification, the determination result can be verified offline by asynchronously calling operator data or other authoritative data. If the offline verification finds that the mobile phone number is actually a reissued number, it indicates that the pre-identification strategy has missed a judgment. Accordingly, the specific reasons for the missed judgment can be analyzed (such as delayed updates to the trusted device list, unreasonable first-time window settings, etc.), and the pre-identification strategy can be adjusted based on the analysis results, thereby reducing the subsequent missed judgment rate and forming a closed-loop path of "identification-verification-optimization" to achieve continuous optimization, so that the accuracy of the pre-identification result continues to improve with the increase of running time.
[0075] If a mobile phone number is identified as a suspected secondary number, the operator's detection interface can be called to perform post-processing identification on the mobile phone number to obtain the target identification result of whether the mobile phone number is a secondary number.
[0076] In some embodiments of this disclosure, the baseline comparison time corresponding to the mobile phone number can be determined first. Then, the mobile phone number and the baseline comparison time can be sent to the operator detection interface, and the returned target identification result can be obtained. The target identification result is determined by querying whether the mobile phone number has been canceled and re-entered after the baseline comparison time.
[0077] By determining the baseline comparison time corresponding to the mobile phone number and using that time as the anchor point to query the operator's detection interface to see if there has been any subsequent cancellation and re-entry behavior, accurate and reliable identification results can be obtained by relying on the operator's authoritative data. This can effectively avoid meaningless full comparisons and information interference, thereby improving query efficiency and further enhancing the accuracy of the identification results.
[0078] In some embodiments of this disclosure, the method for determining the benchmark comparison time corresponding to the mobile phone number may include: obtaining the binding time of the mobile phone number on the target platform, obtaining the most recent SMS verification code verification time of the mobile phone number on the target platform, and determining the time closer to the current time between the binding time and the SMS verification code verification time as the benchmark comparison time.
[0079] The above processing ensures that the determined benchmark comparison time is more closely aligned with the actual usage status of the mobile phone number, laying a solid foundation for subsequent processing.
[0080] In some embodiments of this disclosure, after determining the baseline comparison time, in response to determining that the baseline comparison time is within the second time window, the mobile phone number can be identified as a non-secondary number. The end time of the second time window is the current time. In response to determining that the baseline comparison time is not within the second time window, the mobile phone number and the baseline comparison time can be sent to the operator detection interface. Alternatively, the mobile phone number can be intermediately identified. In response to determining that the mobile phone number is still a suspected secondary number through intermediate identification, the mobile phone number and the baseline comparison time can be sent to the operator detection interface.
[0081] The specific duration of the second time window can be determined according to actual needs. If the baseline comparison time is determined to be within the second time window, the user can be identified as a safe user, and the mobile phone number can be identified as a non-reissued number. This enables rapid exemption and release for recently active or recently bound safe users, effectively reducing reliance on operator detection interfaces and call overhead.
[0082] If it is determined that the baseline comparison time is not within the second time window, the mobile phone number and the baseline comparison time can be sent directly to the operator's detection interface. Alternatively, the mobile phone number can be identified first through intermediate identification. If the mobile phone number is still identified as a suspected secondary number through intermediate identification, then the mobile phone number and the baseline comparison time can be sent to the operator's detection interface.
[0083] In some embodiments of this disclosure, for the latter case, the integrated circuit card identification number (ICCID) of the user identity module (SIM) corresponding to the mobile phone number can be obtained. In response to determining that the integrated circuit card identification number meets a predetermined first requirement, the mobile phone number can be determined as a non-reissued number. In response to determining that the integrated circuit card identification number does not meet the first requirement, the comprehensive confidence assessment result corresponding to the mobile phone number can be obtained. In response to determining that the comprehensive confidence assessment result meets a predetermined second requirement, the mobile phone number can be determined as a non-reissued number. In response to determining that the comprehensive confidence assessment result does not meet the second requirement, the mobile phone number and the benchmark comparison time can be sent to the operator detection interface.
[0084] This allows for supplementary detection of the integrated circuit card identification code strategy. For example, if it is determined that the card issuance time of the user identification module corresponding to the obtained integrated circuit card identification code is consistent with the binding time of the integrated circuit card identification code and the mobile phone number, then the first requirement can be met, and the mobile phone number can be identified as a non-reissued number. Otherwise, the comprehensive confidence assessment result corresponding to the mobile phone number can be obtained. For example, a comprehensive confidence score can be generated based on the multi-dimensional predetermined information corresponding to the mobile phone number through rules or evaluation models. The comprehensive confidence score can be compared with a predetermined threshold. If the comprehensive confidence score is greater than the threshold, the second requirement can be met, and the mobile phone number can be identified as a non-reissued number. Otherwise, the mobile phone number and the benchmark comparison time can be sent to the operator's detection interface. The specific value of the threshold can be determined according to actual needs.
[0085] Through the above processing, a portion of normal mobile phone numbers can be further filtered out before calling the operator's detection interface, thereby further reducing the number of calls to the operator's detection interface, significantly reducing identification costs while ensuring identification accuracy.
[0086] After sending the mobile phone number and the benchmark comparison time to the operator's detection interface, the target identification result of whether the returned mobile phone number is a reissued number can be obtained. The target identification result can be determined by querying whether the mobile phone number has been canceled and re-entered after the benchmark comparison time.
[0087] Based on the above introduction, Figure 4 This is a flowchart illustrating an embodiment of the method for generating target identification results for suspected secondary number releases as described in this disclosure. Figure 4 As shown, the specific implementation methods are as follows.
[0088] In step 401, the baseline comparison time corresponding to the mobile phone number is determined.
[0089] If the binding time of the mobile phone number on the target platform can be obtained, and the time of the last SMS verification code verification of the mobile phone number on the target platform can be obtained, then the time closer to the current time between the binding time and the SMS verification code verification time can be determined as the benchmark comparison time.
[0090] In step 402, it is determined whether the benchmark comparison time is within the second time window. If so, step 403 is executed; otherwise, step 404 is executed.
[0091] In step 403, the mobile phone number is determined to be a non-secondary number, and then the process ends.
[0092] In step 404, the integrated circuit card identification code of the user identification module corresponding to the mobile phone number is obtained, and it is determined whether the integrated circuit card identification code meets the predetermined first requirement. If yes, step 403 is executed; otherwise, step 405 is executed.
[0093] In step 405, the comprehensive confidence assessment result corresponding to the mobile phone number is obtained, and it is determined whether the comprehensive confidence assessment result meets the predetermined second requirement. If yes, step 403 is executed; otherwise, step 406 is executed.
[0094] In step 406, the mobile phone number and the benchmark comparison time are sent to the operator's detection interface to obtain the returned target recognition result.
[0095] In step 407, it is determined whether the mobile phone number is a secondary number based on the target recognition result. If not, step 403 is executed; if yes, step 408 is executed.
[0096] In step 408, the mobile phone number is identified as a secondary number, and then the process ends.
[0097] If the mobile number is determined to be a non-reissued number, the normal business request processing procedure can be followed. If the mobile number is determined to be a reissued number, there are no restrictions on how to handle it. For example, business requests can be intercepted and warnings can be issued.
[0098] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this disclosure is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this disclosure. Secondly, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this disclosure. Furthermore, for parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.
[0099] The above is an introduction to the method embodiments. The following describes the solution described in this disclosure further through device embodiments.
[0100] Figure 5 This is a schematic diagram of the structural composition of Embodiment 500 of the secondary number identification device described in this disclosure. Figure 5 As shown, it includes: a request acquisition module 501, a pre-recognition module 502, and a post-recognition module 503.
[0101] The request acquisition module 501 is used to acquire business requests issued by users for the target platform's business.
[0102] The pre-identification module 502 is used to perform pre-identification of the mobile phone number in response to the determination that the business request carries a mobile phone number and that the mobile phone number needs to be identified for secondary numbering.
[0103] The post-recognition module 503 is used to respond to the fact that the mobile phone number is identified as a suspected secondary number through the pre-recognition, and to perform post-recognition on the mobile phone number by calling the operator detection interface to obtain the target recognition result of whether the mobile phone number is a secondary number.
[0104] In some embodiments of this disclosure, the pre-identification module 502 may determine whether a mobile phone number is carried in a service request and whether a secondary number recognition is required for the mobile phone number in response to the determination that the service request carries a mobile phone number. The verification may include at least verifying whether the service request contains a mobile phone number and whether the format of the mobile phone number meets the requirements. In response to the determination that the verification is successful, the module may determine whether a secondary number recognition is required for the mobile phone number based on the type of the mobile phone number.
[0105] In some embodiments of this disclosure, the pre-identification module 502 may determine whether a secondary numbering identification is required for a mobile phone number based on its type by: in response to determining that a mobile phone number is associated with an account, identifying the type of the mobile phone number through a number prefix identification method and / or an operator number segment database query identification method; and in response to the mobile phone number being a non-target type, determining that a secondary numbering identification is required for the mobile phone number.
[0106] In some embodiments of this disclosure, the pre-identification module 502 may perform pre-identification of mobile phone numbers using a pre-identification strategy by: determining the target device used by the user to issue the service request, and performing pre-identification of the mobile phone number based on the interaction information between the target device, the mobile phone number, and the target platform.
[0107] In some embodiments of this disclosure, the pre-identification module 502 may perform pre-identification of a mobile phone number based on the target device and the interaction information between the mobile phone number and the target platform in the following ways: in response to determining that the target device is a verified and frequently used device corresponding to the mobile phone number, the mobile phone number is determined to be a non-reissued number; in response to determining that the target device is not a verified and frequently used device, the device fingerprint of the target device is obtained; in response to determining that the device fingerprint is in the user's trusted device list, the mobile phone number is determined to be a non-reissued number; in response to determining that the device fingerprint is not in the trusted device list, but the mobile phone number has been verified by SMS verification code on the target platform within the first time window, the mobile phone number is determined to be a non-reissued number, where the end time of the first time window is the current time; in response to determining that the device fingerprint is not in the trusted device list and the mobile phone number has not been verified by SMS verification code within the first time window, the mobile phone number is determined to be a suspected reissued number.
[0108] In some embodiments of this disclosure, after the pre-identification module 502 determines that the mobile phone number is not a secondary number, in response to determining that the mobile phone number is a secondary number through offline verification, the reason for the identification error can be analyzed, and the pre-identification strategy can be optimized according to the reason.
[0109] In some embodiments of this disclosure, the post-identification module 503 performs post-identification on the mobile phone number by calling the operator detection interface to obtain the target identification result of whether the mobile phone number is a reissued number. The method may include: determining the benchmark comparison time corresponding to the mobile phone number, sending the mobile phone number and the benchmark comparison time to the operator detection interface, obtaining the returned target identification result, and the target identification result is determined by querying whether the mobile phone number has been canceled and re-entered the network after the benchmark comparison time.
[0110] In some embodiments of this disclosure, the method by which the post-identification module 503 determines the benchmark comparison time corresponding to the mobile phone number may include: obtaining the binding time of the mobile phone number on the target platform, obtaining the most recent SMS verification code verification time of the mobile phone number on the target platform, and determining the time closer to the current time between the binding time and the SMS verification code verification time as the benchmark comparison time.
[0111] In some embodiments of this disclosure, after the post-identification module 503 determines the benchmark comparison time, in response to determining that the benchmark comparison time is within the second time window, the mobile phone number can be identified as a non-secondary number. The end time of the second time window is the current time. In response to determining that the benchmark comparison time is not within the second time window, the mobile phone number and the benchmark comparison time can be sent to the operator detection interface. Alternatively, the mobile phone number can be identified in the intermediate stage. In response to determining that the mobile phone number is still a suspected secondary number through the intermediate stage, the mobile phone number and the benchmark comparison time can be sent to the operator detection interface.
[0112] In some embodiments of this disclosure, the post-identification module 503 performs intermediate identification on the mobile phone number. In response to the mobile phone number still being identified as a suspected secondary number through intermediate identification, the method of sending the mobile phone number and the benchmark comparison time to the operator detection interface may include: obtaining the integrated circuit card identification code of the user identity recognition module corresponding to the mobile phone number; in response to determining that the integrated circuit card identification code meets a predetermined first requirement, identifying the mobile phone number as a non-secondary number; in response to determining that the integrated circuit card identification code does not meet the first requirement, obtaining the comprehensive confidence assessment result corresponding to the mobile phone number; in response to determining that the comprehensive confidence assessment result meets a predetermined second requirement, identifying the mobile phone number as a non-secondary number; in response to determining that the comprehensive confidence assessment result does not meet the second requirement, sending the mobile phone number and the benchmark comparison time to the operator detection interface.
[0113] The specific workflow of the above-described device embodiments can be found in the relevant descriptions in the foregoing method embodiments, and will not be repeated here.
[0114] In summary, the proposed solution presents a hierarchical governance approach for identifying secondary number releases. It employs an overall architecture of "multi-layer funnel filtering + multi-factor comprehensive decision-making + closed-loop verification of missed calls and recalls," decomposing the secondary number release identification process into multiple progressive layers. Each layer gradually narrows the detection range and improves detection accuracy based on the previous layer. This approach can significantly reduce the calls to operator detection interfaces, lower identification costs, and balance identification efficiency and accuracy, achieving a balance between risk control and business smoothness.
[0115] The solutions described in this disclosure can be applied to the field of artificial intelligence, particularly in areas such as internet platforms, information security, and cloud computing. Artificial intelligence is the study of enabling computers to simulate certain human thought processes and intelligent behaviors (such as learning, reasoning, thinking, and planning). It involves both hardware and software technologies. Artificial intelligence hardware technologies generally include sensors, dedicated AI chips, cloud computing, distributed storage, and big data processing. Artificial intelligence software technologies mainly include computer vision, speech recognition, natural language processing, machine learning / deep learning, big data processing, and knowledge graph technologies.
[0116] According to embodiments of this disclosure, this disclosure also provides an electronic device, a readable storage medium, and a computer program product.
[0117] Figure 6 A schematic block diagram of an electronic device 600 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.
[0118] like Figure 6 As shown, the electronic device 600 includes a computing unit 601, which can perform various appropriate actions and processes based on a computer program stored in a read-only memory (ROM) 602 or a computer program loaded from a storage unit 608 into a random access memory (RAM) 603. The RAM 603 may also store various programs and data required for the operation of the electronic device 600. The computing unit 601, ROM 602, and RAM 603 are interconnected via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.
[0119] Multiple components in electronic device 600 are connected to I / O interface 605, including: input unit 606, such as keyboard, mouse, etc.; output unit 607, such as various types of displays, speakers, etc.; storage unit 608, such as disk, optical disk, etc.; and communication unit 609, such as network card, modem, wireless transceiver, etc. Communication unit 609 allows electronic device 600 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.
[0120] The computing unit 601 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 601 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any suitable processor, controller, microcontroller, etc. The computing unit 601 performs the various methods and processes described above, such as those described in this disclosure. For example, in some embodiments, the methods described in this disclosure can be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 608. In some embodiments, part or all of the computer program can be loaded and / or installed on the electronic device 600 via ROM 602 and / or communication unit 609. When the computer program is loaded into RAM 603 and executed by the computing unit 601, one or more steps of the methods described in this disclosure can be performed. Alternatively, in other embodiments, the computing unit 601 may be configured to perform the methods described herein by any other suitable means (e.g., by means of firmware).
[0121] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard parts (ASSPs), systems-on-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.
[0122] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.
[0123] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory, read-only memory, erasable programmable read-only memory (EPROM), flash memory, optical fiber, compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.
[0124] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).
[0125] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.
[0126] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.
[0127] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this disclosure can be achieved, and this is not limited herein.
[0128] The specific embodiments described above do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.
Claims
1. A method for identifying secondary number allocation, comprising: Obtain the business requests sent by users to the target platform's services; In response to determining that the service request carries a mobile phone number and that the mobile phone number needs to be re-identified, a pre-identification strategy is used to perform pre-identification on the mobile phone number; In response to identifying the mobile phone number as a suspected secondary number through the pre-identification, the operator detection interface is called to perform post-identification on the mobile phone number to obtain the target identification result of whether the mobile phone number is a secondary number.
2. The method according to claim 1, wherein, The response to determining that the service request carries a mobile phone number and determining that the mobile phone number needs to be reissued includes: The service request is validated, and the validation includes at least: validating whether the service request includes the mobile phone number and whether the format of the mobile phone number meets the requirements; In response to the confirmation that the verification is successful, it is determined whether the mobile phone number needs to be reissued for identification based on the type of the mobile phone number.
3. The method according to claim 2, wherein, The step of determining whether a secondary number allocation identification is needed for the mobile phone number based on its type includes: In response to determining that the mobile phone number is associated with an account, the type of the mobile phone number is identified through a number prefix identification method and / or a carrier number segment database query identification method; In response to the fact that the mobile phone number is a non-target type, it is determined that the mobile phone number needs to be re-identified for secondary number allocation.
4. The method according to claim 1, wherein, The pre-identification of the mobile phone number using the pre-identification strategy includes: Determine the target device used by the user to issue the service request; The pre-identification of the mobile phone number is performed based on the target device and the interaction information between the mobile phone number and the target platform.
5. The method according to claim 4, wherein, The pre-identification of the mobile phone number based on the target device and the interaction information between the mobile phone number and the target platform includes: In response to determining that the target device is a verified frequently used device corresponding to the mobile phone number, the mobile phone number is determined to be a non-secondary number; In response to determining that the target device is not one of the verified commonly used devices, the device fingerprint of the target device is obtained; In response to determining that the device fingerprint is in the user's trusted device list, the mobile phone number is determined to be a non-reissued number; In response to determining that the device fingerprint is not in the list of trusted devices, but determining that the mobile phone number has been verified by SMS verification code on the target platform within the first time window, the mobile phone number is determined to be a non-reissued number, and the end time of the first time window is the current time; In response to determining that the device fingerprint is not in the list of trusted devices and that the mobile phone number has not been verified by the SMS verification code within the first time window, the mobile phone number is identified as the suspected secondary number.
6. The method according to claim 5, further comprising: After determining that the mobile phone number is not a secondary number, the system responds by verifying that the mobile phone number is a secondary number through offline verification, analyzing the reasons for the identification error, and optimizing the pre-processing strategy based on the reasons.
7. The method according to claim 1, wherein, The step of performing post-processing identification on the mobile phone number by calling the operator detection interface to obtain the target identification result of whether the mobile phone number is a reissued number includes: Determine the baseline comparison time corresponding to the mobile phone number; The mobile phone number and the benchmark comparison time are sent to the operator detection interface to obtain the returned target identification result. The target identification result is determined by querying whether the mobile phone number has been canceled and re-entered after the benchmark comparison time.
8. The method according to claim 7, wherein, The determination of the benchmark comparison time corresponding to the mobile phone number includes: Obtain the binding time of the mobile phone number on the target platform, and obtain the time of the most recent SMS verification code verification performed by the mobile phone number on the target platform; The time closer to the current time between the binding time and the SMS verification code verification time is determined as the benchmark comparison time.
9. The method according to claim 7, further comprising: After determining the baseline comparison time, in response to determining that the baseline comparison time is within the second time window, the mobile phone number is determined to be a non-secondary number, and the end time of the second time window is the current time; In response to determining that the benchmark comparison time is not within the second time window, the mobile phone number and the benchmark comparison time are sent to the operator detection interface; or, the mobile phone number is subjected to intermediate identification. In response to determining that the mobile phone number is still the suspected secondary number through the intermediate identification, the mobile phone number and the benchmark comparison time are sent to the operator detection interface.
10. The method according to claim 9, wherein, The intermediate identification of the mobile phone number, in response to the intermediate identification still identifying the mobile phone number as the suspected secondary number, sending the mobile phone number and the benchmark comparison time to the operator detection interface includes: Obtain the integrated circuit card identification code of the user identity recognition module corresponding to the mobile phone number, and in response to determining that the integrated circuit card identification code meets a predetermined first requirement, identify the mobile phone number as a non-secondary number; In response to determining that the integrated circuit card identification code does not meet the first requirement, the comprehensive confidence assessment result corresponding to the mobile phone number is obtained; In response to determining that the comprehensive confidence assessment result meets the predetermined second requirement, the mobile phone number is identified as a non-secondary number; In response to determining that the comprehensive confidence assessment result does not meet the second requirement, the mobile phone number and the benchmark comparison time are sent to the operator detection interface.
11. A secondary number issuance identification device, comprising: The system includes a request acquisition module, a pre-recognition module, and a post-recognition module. The request acquisition module is used to acquire the business requests sent by the user for the target platform's business. The pre-identification module is used to respond to determining that the service request carries a mobile phone number and that the mobile phone number needs to be identified for secondary number allocation, and to perform pre-identification of the mobile phone number using a pre-identification strategy; The post-recognition module is used to respond to the fact that the mobile phone number is identified as a suspected secondary number through the pre-recognition, and to perform post-recognition on the mobile phone number by calling the operator detection interface to obtain the target recognition result of whether the mobile phone number is a secondary number.
12. An electronic device, comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-10.
13. A non-transitory computer-readable storage medium storing computer instructions, wherein, The computer instructions are used to cause the computer to perform the method according to any one of claims 1-10.
14. A computer program product comprising a computer program / instructions that, when executed by a processor, implement the method of any one of claims 1-10.