WO2020181914A1 - 手机号换绑验证方法、装置、设备及存储介质 - Google Patents

手机号换绑验证方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2020181914A1
WO2020181914A1 PCT/CN2020/070719 CN2020070719W WO2020181914A1 WO 2020181914 A1 WO2020181914 A1 WO 2020181914A1 CN 2020070719 W CN2020070719 W CN 2020070719W WO 2020181914 A1 WO2020181914 A1 WO 2020181914A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobile phone
phone number
rebinding
verification
target account
Prior art date
Application number
PCT/CN2020/070719
Other languages
English (en)
French (fr)
Inventor
王岳晨
Original Assignee
北京字节跳动网络技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京字节跳动网络技术有限公司 filed Critical 北京字节跳动网络技术有限公司
Publication of WO2020181914A1 publication Critical patent/WO2020181914A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • the embodiments of the present disclosure relate to the field of computer technology, for example, to a method, device, device, and storage medium for verifying mobile phone number binding.
  • a standard set of binding procedures is required. That is: verify the original mobile phone number according to the original mobile phone number entered by the user through the mobile APP and the verification code sent by the system to the original mobile phone number. After the verification is passed, it will be sent to the new mobile phone according to the new mobile phone number re-entered by the user and the system The verification code of the number to complete the binding operation.
  • the disadvantage of the related technology is that if the user has lost the original mobile phone or canceled the original mobile phone number, the verification code sent to the original mobile phone number cannot be received, and the binding cannot be changed automatically, and the user needs to complain manually And wait for the result.
  • the embodiments of the present disclosure provide a method, device, device, and storage medium for verifying the binding of a mobile phone number, so as to ensure the security and reliability of the binding change process, simplify the operation process, and reduce user operations and waiting time.
  • the embodiment of the present disclosure provides a method for verifying the binding of a mobile phone number, including:
  • the embodiment of the present disclosure also provides a mobile phone number rebinding verification device, which includes:
  • the binding acquisition module is set to obtain the original bound mobile phone number corresponding to the target account in the case of detecting the mobile phone number replacement verification request for the target account;
  • the condition verification module is configured to verify whether the current use state of the original bound mobile phone number meets the conditions for safe rebinding: in the case that the current use state of the original bound mobile phone number does not meet the conditions for safe rebinding, obtain the target account number The corresponding third-party associated account;
  • the binding swap processing module is configured to call a third-party authentication interface matching the third-party associated account to verify the target account, and perform a corresponding binding swap processing operation according to the verification result fed back by the third-party authentication interface.
  • the embodiment of the present disclosure also provides a terminal device, which includes:
  • One or more processing devices are One or more processing devices;
  • Storage device set to store one or more programs
  • the one or more processing apparatuses When the one or more programs are executed by the one or more processing apparatuses, the one or more processing apparatuses implement the mobile phone number rebinding verification method as described in any of the embodiments of the present disclosure.
  • the embodiment of the present disclosure also provides a computer-readable storage medium, and a computer program is stored on the computer-readable storage medium.
  • the program is executed by the processing device, the mobile phone number replacement verification as described in any of the embodiments of the present disclosure is implemented. method.
  • FIG. 1 is a schematic flowchart of a method for verifying mobile phone number binding provided by Embodiment 1 of the present disclosure
  • FIG. 2 is a schematic flowchart of a method for verifying mobile phone number binding provided by Embodiment 2 of the present disclosure
  • FIG. 3 is a schematic flowchart of a method for verifying mobile phone number binding provided by Embodiment 3 of the present disclosure
  • FIG. 4 is a schematic structural diagram of a mobile phone number rebinding verification device provided by Embodiment 4 of the present disclosure
  • FIG. 5 is a schematic diagram of the hardware structure of a terminal device provided by Embodiment 5 of the present disclosure.
  • FIG. 1 is a schematic flowchart of a method for verifying mobile phone number rebinding according to Embodiment 1 of the present disclosure. This method can be applied to the situation where the mobile phone number is bound to the application program.
  • the method can be executed by a terminal device such as a mobile phone or a tablet computer that installs the application program, and includes the following steps:
  • the target account may be the login account registered and used when the user logs in to the APP configured on the terminal device.
  • users can choose to log in to the APP through the mobile phone number bound to the login account and the temporary verification code sent to the mobile phone.
  • the original mobile phone number needs to be verified according to the original mobile phone number entered by the user through the APP and the verification code sent to the original mobile phone number by the system. After the verification is passed, the new mobile phone number re-entered by the user and the system sent to the new mobile phone The verification code of the number to complete the binding operation. If the user’s original mobile phone number cannot be verified, the binding operation can only be completed through a manual appeal.
  • this embodiment provides a new way of rebinding of mobile phone number and login account.
  • the mobile phone number rebinding verification request for the target account can be monitored in real time.
  • the mobile phone number swapping verification request may be a request triggered when the user clicks the mobile phone swapping button on the APP interface after logging in to the APP with the target account.
  • the mobile phone number rebinding verification request may also be that when the user needs to enter the mobile phone verification code corresponding to the original bound mobile phone number in the conventional rebinding process, the mobile phone verification code cannot be entered.
  • the generated request is triggered to trigger the application to select a new binding replacement method other than manual processing, that is, the binding replacement method provided by the technical solution of the embodiment of the present application.
  • a "help" button is provided to the user on the page where the application program enters the mobile phone verification code of the originally bound mobile phone, and the user generates the mobile phone number replacement verification request by selecting the "help" button.
  • the binding relationship corresponding to the target account can be obtained from the server corresponding to the APP, and the original bound mobile phone number can be obtained according to the binding relationship.
  • the safe binding swap condition may be a condition for determining that the current binding swap operation is a safe operation when the bound mobile phone number is changed.
  • the security rebinding condition may be the set usage state of the original bound mobile phone number. When the current use status of the originally bound mobile phone number meets the security swap condition, it means that the current swap operation is a safe operation; when the current use status of the originally bound mobile phone number does not meet the security swap condition, it means the current The binding change operation is a non-safe operation.
  • the current usage status of the originally bound mobile phone number includes but is not limited to whether it is in use and the corresponding usage status.
  • the third-party associated account corresponding to the target account is obtained to verify the target account through the third-party platform corresponding to the third-party associated account. Determine whether the binding replacement operation for the target account is a safe operation, eliminating the review process of manual appeals, and simplifying the binding replacement operation process while ensuring the security of the binding replacement operation.
  • the third-party associated account may be a login account of another application that is bound to the target account, or may also be a login account of another application that has been accessed using the APP corresponding to the target account. Wait.
  • the binding relationship corresponding to the target account can be obtained from the server corresponding to the APP, and the corresponding third-party associated account can be obtained according to the binding relationship.
  • after verifying whether the current use state of the original bound mobile phone number meets the conditions for safe rebinding it further includes: providing a new binding if the current use state of the original bound mobile phone number meets the conditions for safe rebinding
  • the mobile phone number input interface is used to obtain the newly bound mobile phone number to complete the mobile phone number rebinding for the target account.
  • the current use status of the original bound mobile phone number meets the security rebinding conditions, it means that the current rebinding operation is a safe operation.
  • S130 Invoke a third-party authentication interface matching the third-party associated account to verify the target account, and perform a corresponding binding swap processing operation according to the verification result fed back by the third-party authentication interface.
  • the third-party platform corresponding to the third-party associated account can provide a third-party authentication interface, and the APP client can verify the target account by calling the third-party authentication interface.
  • the third-party authentication interface can be directly opened by calling the third-party authentication interface. Client, and jump to the authentication interface of the third-party platform.
  • the user can verify the legality of the target account by clicking the confirmation button in the interface; if the client of the third-party platform is not installed in the APP corresponding to the target account In the device where the client is located, the third-party authentication interface can be invoked to send an authentication request to the third-party platform client with the third-party associated account, and the corresponding authentication interface pops up on the device where the third-party platform's client is located.
  • the user can verify the validity of the target account by clicking the confirm button or the reject button in the interface, and send the verification result to the APP client corresponding to the target account.
  • the APP client corresponding to the target account receives the verification result fed back by the third-party authentication interface, it can perform a corresponding binding swap processing operation according to the verification result.
  • different verification results may correspond to different binding swap processing operations.
  • the technical solution of this embodiment obtains the original bound mobile phone number corresponding to the target account when the mobile phone number replacement verification request for the target account is detected, and verifies whether the current use state of the original bound mobile phone number satisfies the security swap.
  • Bind conditions when the current use status of the originally bound mobile phone number does not meet the security rebinding conditions, obtain the third-party associated account corresponding to the target account, and call the third-party authentication interface that matches the third-party associated account to perform the target account Verification, and execute the corresponding re-binding processing operation based on the feedback verification result, and use third-party authentication to perform re-binding security verification on the target account whose original bound mobile phone number does not meet the security re-binding conditions, which solves the need for users to pass manual procedures in related technologies.
  • the method of appealing can only be used to change the mobile phone number, which leads to the complicated operation process, user operation and long waiting time, which realizes the simplification of the operation process and the reduction of users while ensuring the safety and reliability of the change of binding process. Operation and waiting time.
  • FIG. 2 is a schematic flowchart of a method for verifying mobile phone number rebinding according to Embodiment 2 of the present disclosure.
  • verifying whether the current usage status of the original bound mobile phone number satisfies the conditions for safe rebinding includes: judging whether the operator interface matching the original bound mobile phone number can be obtained; in the case where the operator interface can be obtained In the next step, call the operator interface to query the status of the mobile phone originally bound to the mobile phone number; if the query result is that the original bound mobile phone number is not in the state of secondary number allocation, or the current replacement device is not a trusted verification device, verify the original The current usage status of the bound mobile phone number does not meet the conditions for safe rebinding; if the query result is that the original bound mobile phone number is in the second allocation state, and the current rebinding device is a trusted verification device, verify the original bound mobile phone The current usage status of
  • S220 Determine whether the operator interface matching the original bound mobile phone number can be obtained, and if the operator interface can be obtained, execute S240; if the operator interface cannot be obtained, execute S230.
  • the current use state of the original bound mobile phone number may include the state of the mobile phone bound to the original mobile phone number and the credibility of the current swapped device (that is, the device where the target account belongs to the APP). Since different mobile phone numbers may belong to different operators, and the usage status of the mobile phone number is generally managed by the operator, therefore, when obtaining the current usage status of the original bound mobile phone number, it is possible to determine whether the original mobile phone number can be obtained. Bind the operator interface that matches the mobile phone number. In an embodiment, the operator interface may be an interface provided by the operator specifically for querying the current usage status of the mobile phone number.
  • the operator that matches the original bound mobile phone number is authorized to provide the corresponding query interface to the APP to which the target account belongs, it can be determined that the operator interface that matches the original bound mobile phone number can be obtained; If the operator whose bound mobile phone number matches is not authorized to provide the corresponding query interface to the APP to which the target account belongs, it can be determined that the operator interface matching the original bound mobile phone number cannot be obtained.
  • the state of the mobile phone with the original bound mobile phone number cannot be determined through the mobile phone number query, and it is impossible to verify whether the user's mobile phone is in normal logout.
  • the mobile phone status acquisition request carrying the original bound mobile phone number can be sent to the operator by calling the operator interface, so that the operator can query the corresponding mobile phone status according to the original bound mobile phone number, and return the Phone status.
  • the state of the mobile phone includes but is not limited to: use state, shutdown state, secondary number allocation state, etc.
  • the trusted verification device may be a device that has completed the login of the target account using the original bound mobile phone number.
  • the device identification code of the device where the mobile phone number is located can be recorded, so that device verification can be performed when the mobile phone number is changed.
  • the original bound mobile phone number is in the second allocation state, it means that the original bound mobile phone number has been cancelled by the user, and the number has been allocated to others for the second time.
  • the user changes the bound mobile phone it usually happens in a relatively short time.
  • the secondary number allocation process takes place in a relatively short period of time, which can then indirectly show that the above-mentioned binding replacement operation is a normal phone number replacement operation of the user.
  • the original bound mobile phone number is no longer available, it is impossible to change the binding operation by entering the original bound mobile phone number and the login verification code.
  • the current swap device is also determined to be a trusted verification device, it means that although the original binding mobile phone number can no longer be directly used for security verification of the swap operation, the current swap device has used the original authentication device. Bind the mobile phone number to log in to the target account, indicating that the user currently using the device for rebinding operation is a legitimate user, that is, verifying that the current use status of the originally bound mobile phone number meets the security rebinding conditions.
  • the originally bound mobile phone number is not in the secondary number allocation state, or the current rebinding device is not a trusted verification device, verify that the current use state of the original bound mobile phone number does not meet the security rebinding condition.
  • S270 Provide a newly bound mobile phone number input interface to obtain the newly bound mobile phone number to complete the mobile phone number rebinding for the target account.
  • the technical solution of this embodiment first determines whether the operator interface that matches the original bound mobile phone number can be obtained, and when the operator interface can be obtained, the operator interface is called to query the mobile phone status of the original bound mobile phone number, and By judging whether the query result is the secondary number allocation status and whether the current rebinding device is a trusted verification device, it is verified whether the current usage status of the original bound mobile phone number meets the security rebinding conditions, and then the current binding of the original bound mobile phone number When the usage status does not meet the security rebinding conditions, the third-party associated account corresponding to the target account is used for security verification, and finally the corresponding rebinding processing operation is executed according to the verification result.
  • This embodiment uses the mobile phone status of the original bound mobile phone number and The credibility of the current device to be re-bonded, and the security confirmation operation of the original-bound mobile phone number is performed, so that only when the original-bound mobile phone number is confirmed to be unavailable and the current re-bonded device is a trusted device, the re-bonding operation will be performed directly.
  • third-party verification is also required to ensure the safety and reliability of the binding replacement operation.
  • FIG. 3 is a schematic flowchart of a method for verifying mobile phone number rebinding provided in Embodiment 3 of the present disclosure.
  • This embodiment is described on the basis of the foregoing embodiment, and provides an optional verification method for mobile phone number swapping.
  • performing the corresponding rebinding processing operation according to the verification result fed back by the third-party authentication interface includes: providing a new binding mobile phone number input in the case where it is determined that the verification result fed back by the third-party authentication interface is an authentication pass response Interface to obtain the newly bound mobile phone number to complete the mobile phone number rebinding for the target account.
  • performing the corresponding rebinding processing operation based on the verification result fed back by the third-party authentication interface also includes: in the case where it is determined that the verification result fed back by the third-party authentication interface is an authentication failure response, detecting whether a preset corresponding to the target account is set Verification password; in the case of pre-setting the verification password, provide a verification password input interface, and after detecting that the correct verification password is entered, provide a newly bound mobile phone number input interface to obtain the newly bound mobile phone number to complete the target account Re-bind the mobile phone number of the target account; without pre-setting and verifying the password, jump to the manual processing page to complete the mobile phone number re-binding for the target account.
  • the method provided in this embodiment includes the following steps:
  • S340 Determine whether the verification result fed back by the third-party authentication interface is an authentication pass response, and if the verification result fed back by the third-party authentication interface is an authentication pass response, execute S350; the verification result fed back by the third-party authentication interface is an authentication failure response In the case of S360, execute S360.
  • the verification result that can be received through the third-party authentication interface is the authentication pass response; if the user is on the authentication interface corresponding to the third-party platform If you choose to click the cancel button or exit the authentication interface directly, the verification result that can be received through the third-party authentication interface is an authentication failure response.
  • the third-party authentication interface By determining whether the verification result fed back by the third-party authentication interface is an authentication pass response, it can be judged that when the use status of the original bound mobile phone number does not meet the security rebinding conditions, that is, the security verification using the original bound mobile phone number cannot In the case of passing, whether the replacement operation is still safe, compared with the direct manual appeal method when the original mobile phone number cannot be verified, the third-party authentication can be completed quickly by the user himself, without the participation of the background reviewer, thus simplifying The review operation process is improved, and user operation and waiting time are reduced.
  • S350 Provide a newly bound mobile phone number input interface to obtain the newly bound mobile phone number to complete the mobile phone number rebinding for the target account.
  • the verification result fed back by the third-party authentication interface is a pass-through response, it indicates that the current rebinding operation is a safe operation, and the mobile phone number rebinding can be directly performed.
  • the preset verification password corresponding to the target account may be the answer information about the set prompt question entered in advance by the user of the target account.
  • the verification password may be the answer information "May 20" input by the user corresponding to the prompt question "What is your birthday?"
  • the verification result fed back by the third-party authentication interface is not an authentication pass response, that is, an authentication failure response, it means that the third-party authentication cannot be verified either, or the verification fails.
  • it can be set in advance with the target
  • the verification password is used to verify whether the user is a legitimate user of the target account.
  • S370 Provide a verification password input interface, and after detecting that the correct verification password is entered, provide a newly bound mobile phone number input interface to obtain the newly bound mobile phone number to complete the mobile phone number rebinding for the target account.
  • the verification password corresponding to the target account preset by a legitimate user is "May 20th".
  • the verification result fed back by the third-party authentication interface is not a response to the authentication, and it is detected that the target account is preset with
  • the answer entered by the user in the answer input area is "May 20”
  • the verification result fed back by the third-party authentication interface is not an authentication pass response, and the preset verification password corresponding to the target account is not detected, it means that the security verification of the user's independent completion of the binding replacement operation has not been detected.
  • the target account is verified by invoking the third-party authentication interface that matches the third-party associated account corresponding to the target account, it is determined whether the verification result fed back by the third-party authentication interface is an authentication pass response. If the verification result fed back by the third-party authentication interface is a response to the authentication, the mobile phone number is directly rebind. In the case that the verification result fed back by the third-party authentication interface is not a response to the authentication, the test has a preset and target account. When the corresponding verification password is used, the verification password entered by the user and the preset verification password are used to verify whether the user is a legitimate user, and then when the correct verification password is entered, the mobile phone number is re-bound.
  • the verification password corresponding to the target account is converted to manual processing and review
  • the verification password is used to verify whether the user performing the swap operation is a legitimate user of the target account, so as to automatically complete the security review of the swap operation and realize the process of guaranteeing the swap.
  • the manual review operation process is eliminated as much as possible, thereby reducing user operation and waiting time.
  • FIG. 4 is a schematic structural diagram of a mobile phone number rebinding verification device provided in the fourth embodiment of the disclosure.
  • the mobile phone number rebinding verification device includes: a binding acquisition module 410, a condition verification module 420, and a rebinding processing module 430. The following describes multiple modules.
  • the binding obtaining module 410 is configured to obtain the original binding mobile phone number corresponding to the target account in the case of detecting the mobile phone number binding verification request for the target account;
  • the condition verification module 420 is configured to verify the original binding Whether the current usage status of the mobile phone number satisfies the security swap condition, and in the case that the current usage status of the originally bound mobile phone number does not meet the security swap condition, obtain the third-party associated account corresponding to the target account;
  • the swap processing module 430 It is set to invoke a third-party authentication interface matching the third-party associated account to verify the target account, and perform a corresponding binding swap processing operation according to the verification result fed back by the third-party authentication interface.
  • the mobile phone number rebinding verification device obtains the original bound mobile phone number corresponding to the target account when the mobile phone number rebinding verification request for the target account is detected, and verifies the current use of the original bound mobile phone number Whether the status meets the security swap condition, when the current usage status of the originally bound mobile phone number does not meet the security swap condition, obtain the third-party associated account corresponding to the target account, and call the third-party authentication interface matching the third-party associated account The target account is verified, and the corresponding rebinding processing operation is performed according to the feedback verification result.
  • the third-party authentication is used to perform rebinding security verification on the target account whose original binding mobile phone number does not meet the security rebinding conditions, which solves the need for users
  • the mobile phone number can only be changed by means of manual appeals, which leads to complicated operation procedures, user operations and long waiting time. It realizes that while ensuring the safety and reliability of the changing process, the operation process is simplified and reduced The user operation and waiting time are reduced.
  • the device may further include: an interface providing module configured to verify whether the current use state of the original bound mobile phone number satisfies the security rebinding condition, and the current use state of the original bound mobile phone number satisfies the security In the case of changing the binding conditions, a new bound mobile phone number input interface is provided to obtain the newly bound mobile phone number to complete the mobile phone number rebinding for the target account.
  • the condition verification module 420 is configured to: determine whether the operator interface matching the original bound mobile phone number can be obtained; if the operator interface can be obtained, call the operator interface to query the office The state of the mobile phone with the original bound mobile phone number; in the case where the query result is that the original bound mobile phone number is not in the secondary number allocation state, or the current rebinding device is not a trusted verification device, verify the original binding The current usage status of the mobile phone number does not meet the conditions for safe rebinding; if the query result is that the original bound mobile phone number is in the second allocation state, and the current rebinding device is a trusted verification device, verify the original binding The current usage status of the fixed mobile phone number meets the conditions for safe binding.
  • condition verification module 42 is further configured to: after judging whether the operator interface matching the original bound mobile phone number can be obtained, and if the operator interface cannot be obtained, jump to manual processing The page completes the rebinding of the mobile phone number of the target account.
  • the binding swap processing module 430 is configured to provide a newly bound mobile phone number input interface to obtain the newly bound mobile phone when it is determined that the verification result fed back by the third-party authentication interface is an authentication pass response. Complete the rebinding of the mobile phone number for the target account.
  • the binding swap processing module 430 is further configured to detect whether a verification password corresponding to the target account is preset in a case where it is determined that the verification result fed back by the third-party authentication interface is an authentication failure response;
  • the verification password is set in advance, the verification password input interface is provided to the user, and after the correct verification password is detected, the newly bound mobile phone number input interface is provided to obtain the newly bound mobile phone number to complete the target account Rebind the mobile phone number of the mobile phone number; without pre-setting the verification password, jump to the manual processing page to complete the mobile phone number rebinding for the target account.
  • the above-mentioned device can execute the method provided by any embodiment of the present disclosure.
  • FIG. 5 shows a schematic structural diagram of a terminal device 500 suitable for implementing embodiments of the present disclosure.
  • the terminal devices in the embodiments of the present disclosure may include, but are not limited to, mobile phones, notebook computers, digital broadcast receivers, personal digital assistants (Personal Digital Assistant, PDA), tablet computers (Portable Android Device, PAD), and portable multimedia players.
  • Mobile terminals such as Portable Media Player (PMP), in-vehicle terminals (for example, in-vehicle navigation terminals), and fixed terminals such as digital televisions (television, TV), desktop computers, etc.
  • PMP Portable Media Player
  • in-vehicle terminals for example, in-vehicle navigation terminals
  • fixed terminals such as digital televisions (television, TV), desktop computers, etc.
  • the terminal device shown in FIG. 5 is only an example, and should not bring any limitation to the function and scope of use of the embodiments of the present disclosure.
  • the terminal device 500 may include a processing device (such as a central processing unit, a graphics processor, etc.) 501.
  • the processing device may be based on a program stored in a read-only memory (Read-Only Memory, ROM) 502 or from a storage device.
  • the device 508 loads a program in a random access memory (Random Access Memory, RAM) 503 to perform various appropriate actions and processes.
  • RAM Random Access Memory
  • various programs and data required for the operation of the terminal device 500 are also stored.
  • the processing device 501, the ROM 502, and the RAM 503 are connected to each other through a bus 504.
  • An input/output (I/O) interface 505 is also connected to the bus 504.
  • the following devices can be connected to the I/O interface 505: including input devices 506 such as touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; including, for example, a liquid crystal display (LCD) Output devices 507 such as speakers, vibrators, etc.; storage devices 508 such as magnetic tapes, hard disks, etc.; and communication devices 509.
  • the communication device 509 may allow the terminal device 500 to perform wireless or wired communication with other devices to exchange data.
  • FIG. 5 shows a terminal device 500 with various devices, it should be understood that it is not required to implement or have all of the illustrated devices. It may alternatively be implemented or provided with more or fewer devices.
  • the process described above with reference to the flowchart may be implemented as a computer software program.
  • the embodiments of the present disclosure include a computer program product.
  • the computer program product includes a computer program carried on a computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart.
  • the computer program may be downloaded and installed from the network through the communication device 509, or installed from the storage device 508, or installed from the ROM 502.
  • the processing device 501 the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed.
  • the aforementioned computer-readable medium in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two.
  • the computer-readable storage medium may be, for example, but not limited to, an electric, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections with one or more wires, portable computer disks, hard disks, RAM, ROM, Erasable Programmable Read-Only Memory, EPROM) or flash memory, optical fiber, compact Disc Read-Only Memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the foregoing.
  • CD-ROM compact Disc Read-Only Memory
  • a computer-readable storage medium may be any tangible medium that contains or stores a program, and the program may be used by or in combination with an instruction execution system, apparatus, or device.
  • a computer-readable signal medium may include a data signal propagated in a baseband or as a part of a carrier wave, and a computer-readable program code is carried therein. This propagated data signal can take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • the computer-readable signal medium may also be any computer-readable medium other than the computer-readable storage medium.
  • the computer-readable signal medium may send, propagate, or transmit the program for use by or in combination with the instruction execution system, apparatus, or device .
  • the program code contained on the computer-readable medium can be transmitted by any suitable medium, including but not limited to: wire, optical cable, radio frequency (RF), etc., or any suitable combination of the above.
  • the above-mentioned computer-readable medium may be included in the above-mentioned terminal device; or it may exist alone without being assembled into the terminal device.
  • the above-mentioned computer-readable medium carries one or more programs.
  • the terminal device obtains at least two Internet protocol addresses; and sends to the node evaluation device including the at least two A node evaluation request for an Internet Protocol address, wherein the node evaluation device selects an Internet Protocol address from the at least two Internet Protocol addresses and returns it; receives the Internet Protocol address returned by the node evaluation device; wherein, the obtained The Internet Protocol address indicates the edge node in the content distribution network.
  • the computer-readable medium described above carries one or more programs, and when the one or more programs are executed by the terminal device, the terminal device: in the case of detecting a mobile phone number replacement verification request for the target account , Obtain the original bound mobile phone number corresponding to the target account; verify whether the current use status of the original bound mobile phone number meets the conditions for safe rebinding: Obtain if the current use status of the original bound mobile phone number does not meet the conditions for safe rebinding The third-party associated account corresponding to the target account; the third-party authentication interface that matches the third-party associated account is called to verify the target account, and the corresponding rebinding processing operation is performed according to the verification result fed back by the third-party authentication interface.
  • the computer program code used to perform the operations of the present disclosure may be written in one or more programming languages or a combination thereof.
  • the above-mentioned programming languages include object-oriented programming languages—such as Java, Smalltalk, C++, and also conventional Procedural programming language-such as "C" language or similar programming language.
  • the program code can be executed entirely on the user's computer, partly on the user's computer, executed as an independent software package, partly on the user's computer and partly executed on a remote computer, or entirely executed on the remote computer or server.
  • the remote computer can be connected to the user's computer through any kind of network-including Local Area Network (LAN) or Wide Area Network (WAN)-or it can be connected to an external computer (for example, use an Internet service provider to connect via the Internet).
  • LAN Local Area Network
  • WAN Wide Area Network
  • each block in the flowchart or block diagram can represent a module, program segment, or part of code, and the module, program segment, or part of code contains one or more for realizing the specified logical function Executable instructions.
  • the functions marked in the block may also occur in a different order from the order marked in the drawings. For example, two blocks shown in succession can actually be executed substantially in parallel, or they can sometimes be executed in the reverse order, depending on the functions involved.
  • each block in the block diagram and/or flowchart, and the combination of the blocks in the block diagram and/or flowchart can be implemented by a dedicated hardware-based system that performs the specified functions or operations Or it can be realized by a combination of dedicated hardware and computer instructions.
  • the modules or units involved in the described embodiments of the present disclosure can be implemented in software or hardware. Among them, the name of the module or unit does not constitute a limitation on the module or unit itself under certain circumstances.
  • the binding acquisition module can also be described as "used to verify the binding of the mobile phone number for the target account. Upon request, obtain the module of the original bound mobile phone number corresponding to the target account".

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephone Function (AREA)

Abstract

本公开实施例公开了一种手机号换绑验证方法、装置、设备及存储介质。所述方法包括：在检测到针对目标账号的手机号换绑验证请求的情况下，获取与目标账号对应的原绑定手机号；验证所述原绑定手机号的当前使用状态是否满足安全换绑条件：在所述原绑定手机号的当前使用状态不满足安全换绑条件的情况下，获取与所述目标账号对应的第三方关联账号；调用与所述第三方关联账号匹配的第三方认证接口对所述目标账号进行验证，并根据第三方认证接口反馈的验证结果执行对应的换绑处理操作。

Description

手机号换绑验证方法、装置、设备及存储介质
本申请要求在2019年03月13日提交中国专利局、申请号为201910189551.X的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本公开实施例涉及计算机技术领域，例如涉及一种手机号换绑验证方法、装置、设备及存储介质。
背景技术
很多移动应用程序(Application，APP)为了使用户便捷、快速的登录并使用应用服务，大都将手机号码与登录账号进行绑定，并采用手机号码登录的方式代替了用户名加密码的登录方式以简化用户的登录操作。
相关技术中，一个用户使用某一个手机号码绑定了该用户在移动APP中的登录账号后，如果该用户希望为该登录账号换绑新的手机号码，则需要执行一套标准的换绑流程，也即：根据用户通过移动APP输入的原手机号码以及系统发送至原手机号码的验证码对原手机号码进行验证，验证通过后，根据用户重新输入的新的手机号码以及系统发送至新手机号码的验证码，完成换绑操作。
相关技术的缺陷在于，如果用户已经丢失了原有的手机或者注销了原有的手机号码，则无法接收到发送至原手机号码的验证码，进而也就无法自动换绑成功，需要用户人工申诉并等待结果。
发明内容
本公开实施例提供一种手机号换绑验证方法、装置、设备及存储介质，以实现在保证换绑过程安全性以及可靠性的同时，简化操作流程，并减少用户操作及等待时间。
本公开实施例提供了一种手机号换绑验证方法，包括：
在检测到针对目标账号的手机号换绑验证请求的情况下，获取与目标账号对应的原绑定手机号；
验证所述原绑定手机号的当前使用状态是否满足安全换绑条件：在原绑定手机号的当前使用状态不满足安全换绑条件的情况下，获取与所述目标账号对 应的第三方关联账号；
调用与所述第三方关联账号匹配的第三方认证接口对所述目标账号进行验证，并根据第三方认证接口反馈的验证结果执行对应的换绑处理操作。
本公开实施例还提供了一种手机号换绑验证装置，该装置包括：
绑定获取模块，设置为在检测到针对目标账号的手机号换绑验证请求的情况下，获取与目标账号对应的原绑定手机号；
条件验证模块，设置为验证所述原绑定手机号的当前使用状态是否满足安全换绑条件：在原绑定手机号的当前使用状态不满足安全换绑条件的情况下，获取与所述目标账号对应的第三方关联账号；
换绑处理模块，设置为调用与所述第三方关联账号匹配的第三方认证接口对所述目标账号进行验证，并根据第三方认证接口反馈的验证结果执行对应的换绑处理操作。
本公开实施例还提供了一种终端设备，该设备包括：
一个或多个处理装置；
存储装置，设置为存储一个或多个程序；
当所述一个或多个程序被所述一个或多个处理装置执行，使得所述一个或多个处理装置实现如本公开实施例中任一所述的手机号换绑验证方法。
本公开实施例还提供了一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该程序被处理装置执行时实现如本公开实施例中任一所述的手机号换绑验证方法。
附图说明
图1是本公开实施例一提供的一种手机号换绑验证方法的流程示意图；
图2是本公开实施例二提供的一种手机号换绑验证方法的流程示意图；
图3是本公开实施例三提供的一种手机号换绑验证方法的流程示意图；
图4是本公开实施例四提供的一种手机号换绑验证装置的结构示意图；
图5是本公开实施例五提供的一种终端设备的硬件结构示意图。
具体实施方式
下面结合附图和实施例对本公开进行说明。可以理解的是，此处所描述的具体实施例仅仅用于解释本公开，而非对本公开的限定。另外还需要说明的是，为了便于描述，附图中仅示出了与本公开相关的部分而非全部结构。
实施例一
图1为本公开实施例一提供的一种手机号换绑验证方法的流程示意图。该方法可适用于对应用程序所绑定的手机号进行手机号换绑的情况，该方法可以由安装该应用程序的手机、或者平板电脑等终端设备来执行，包括如下步骤：
S110、在检测到针对目标账号的手机号换绑验证请求的情况下，获取与目标账号对应的原绑定手机号。
本实施例中，目标账号可以是用户登录终端设备上配置的APP时所注册使用的登录账号。通常情况下，为了给用户提供多元化的登录方式，用户可选择通过与登录账号绑定的手机号和发送至手机的临时验证码来登录APP，相关技术中，当用户需要更换绑定新的手机号码时，需要根据用户通过APP输入的原手机号码以及系统发送至原手机号码的验证码对原手机号码进行验证，验证通过后，根据用户重新输入的新的手机号码以及系统发送至新手机号码的验证码，完成换绑操作，如果用户原手机号码无法进行验证，则只能通过人工申诉来完成换绑操作。
本实施例为了减少用户操作及等待时间，简化换绑操作流程，提供了一种新的手机号与登录账号的换绑方式。在一实施例中，首先可实时监测针对目标账号的手机号换绑验证请求。在一实施例中，手机号换绑验证请求可以是用户使用目标账号登录APP后，在APP界面上点击手机换绑按键时所触发的请求。
在一实施例中，所述手机号换绑验证请求还可以为，用户在常规的换绑流程中，进行需要输入原绑定手机号对应的手机验证码时，由于无法输入该手机验证码而触发生成的请求，以触发应用程序选择一种除了人工处理之外的新的换绑方式，也即本申请实施例的技术方案提供的换绑方式。例如，在应用程序输入原绑定手机的手机验证码的页面中向用户提供一个“帮助”按钮，用户通过选中该“帮助”按钮生成该手机号换绑验证请求。
示例性的，当检测到针对目标账号的手机号换绑验证请求时，可从APP对应的服务器中获取与目标账号对应的绑定关系，并根据该绑定关系来获取原绑定手机号。
S120、验证原绑定手机号的当前使用状态是否满足安全换绑条件：在原绑定手机号的当前使用状态不满足安全换绑条件的情况下，获取与目标账号对应的第三方关联账号。
本实施例中，安全换绑条件可以是更换绑定手机号时确定当前换绑操作为安全操作的条件。在一实施例中，安全换绑条件可以为原绑定手机号的设定使用状态。当原绑定手机号的当前使用状态满足该安全换绑条件时，则说明当前换绑操作为安全操作；当原绑定手机号的当前使用状态不满足该安全换绑条件时，则说明当前换绑操作为非安全操作。在一实施例中，原绑定手机号的当前使用状态包括但不限于是否在使用以及相应的使用情况等。
示例性的，若原绑定手机号的当前使用状态不满足安全换绑条件，则获取与目标账号对应的第三方关联账号，以通过第三方关联账号对应的第三方平台对该目标账号进行验证，确定针对目标账号的换绑操作是否为安全操作，免去人工申诉的审核流程，在保证换绑操作安全性的同时，简化换绑操作流程。在一实施例中，第三方关联账号可以为与该目标账号进行绑定的其他应用程序的登录账号，或者也可以为使用与该目标账号对应的APP登录或者访问过的其他应用程序的登录账号等。在一实施例中，可以从APP对应的服务器中获取与目标账号对应的绑定关系，并根据该绑定关系来获取对应的第三方关联账号。
在一实施例中，在验证原绑定手机号的当前使用状态是否满足安全换绑条件之后，还包括：在原绑定手机号的当前使用状态满足安全换绑条件的情况下，提供新绑定手机号输入界面，以获取新绑定手机号完成针对目标账号的手机号重绑定。
示例性的，若原绑定手机号的当前使用状态满足安全换绑条件，说明当前换绑操作为安全操作，此时，可跳过输入原绑定手机号及登录验证码的过程，直接提供新绑定手机号的输入界面给用户，以便于用户输入新绑定手机号，并基于该新绑定手机号输入对应的验证码，进而完成目标账号与新绑定手机号之间的绑定操作，并将新的绑定关系发送至服务器进行更新存储。
S130、调用与第三方关联账号匹配的第三方认证接口对目标账号进行验证，并根据第三方认证接口反馈的验证结果执行对应的换绑处理操作。
本实施例中，第三方关联账号对应的第三方平台可提供有第三方认证接口，APP客户端可通过调用该第三方认证接口对目标账号进行验证。
在一实施例中，在进行验证的过程中，若该第三方平台的客户端与该目标账号对应的APP客户端安装于同一设备中，则可通过调用第三方认证接口直接开启第三方平台的客户端，并跳转至第三方平台的认证界面，用户可通过点击 界面中的确认按键对目标账号进行合法性验证；若该第三方平台的客户端没有被安装在与该目标账号对应的APP客户端所在的设备中，则可通过调用第三方认证接口向登录有第三方关联账号的第三方平台客户端发送认证请求，并在第三方平台的客户端所在的设备中弹出对应的认证界面，用户可通过点击界面中的确认按键或者拒绝按键对目标账号进行合法性验证，并将验证结果发送给目标账号对应的APP客户端。
示例性的，当目标账号对应的APP客户端接收到第三方认证接口反馈的验证结果后，可根据该验证结果执行对应的换绑处理操作。本实施例中，不同的验证结果可对应于不同的换绑处理操作。
本实施例的技术方案，通过在检测到针对目标账号的手机号换绑验证请求时，获取与目标账号对应的原绑定手机号，验证该原绑定手机号的当前使用状态是否满足安全换绑条件，在原绑定手机号的当前使用状态不满足安全换绑条件时，获取与该目标账号对应的第三方关联账号，调用与该第三方关联账号匹配的第三方认证接口对该目标账号进行验证，并根据反馈的验证结果执行对应的换绑处理操作，利用第三方认证对原绑定手机号不满足安全换绑条件的目标账号进行换绑安全验证，解决了相关技术中需要用户通过人工申诉的方式才能进行手机号换绑，从而导致操作流程复杂、用户操作及等待时间较长的问题，实现了在保证换绑过程安全性以及可靠性的同时，简化了操作流程，并减少了用户操作及等待时间。
实施例二
图2为本公开实施例二提供的一种手机号换绑验证方法的流程示意图。本实施例以上述实施例为基础进行说明，提供了可选的手机号换绑验证方法。在本实施例中，将验证原绑定手机号的当前使用状态是否满足安全换绑条件，包括：判断是否能够获取与原绑定手机号匹配的运营商接口；在能够获取运营商接口的情况下，调用运营商接口查询原绑定手机号的手机状态；在查询结果为原绑定手机号未处于二次放号状态，或者当前换绑设备不为可信验证设备的情况下，验证原绑定手机号的当前使用状态不满足安全换绑条件；在查询结果为原绑定手机号处于二次放号状态，且当前换绑设备为可信验证设备的情况下，验证原绑定手机号的当前使用状态满足安全换绑条件。本实施例提供的方法包括如下步骤：
S210、在检测到针对目标账号的手机号换绑验证请求的情况下，获取与目标账号对应的原绑定手机号。
S220、判断是否能够获取与原绑定手机号匹配的运营商接口，在能够获取运营商接口的情况下，执行S240；在不能够获取运营商接口的情况下，执行S230。
本实施例中，原绑定手机号的当前使用状态可包括原绑定手机号的手机状态以及当前换绑设备(也即目标账号所属APP所在的设备)的可信程度。由于不同的手机号可能属于不同的运营商，而手机号的使用状态一般是由运营商进行管理，因此，可在获取原绑定手机号的当前使用状态时，先判断是否能够获取到与原绑定手机号相匹配的运营商接口。在一实施例中，运营商接口可以是运营商提供的专门用于查询手机号当前使用状态的接口。
示例性的，若与原绑定手机号匹配的运营商授权提供有相应的查询接口给目标账号所属的APP，则可确定能够获取到与原绑定手机号匹配的运营商接口；若与原绑定手机号匹配的运营商没有授权提供相应的查询接口给目标账号所属的APP，则可确定无法获取到与原绑定手机号匹配的运营商接口。
S230、跳转至人工处理页面完成针对目标账号的手机号重绑定。
本实施例中，若确定无法获取到与原绑定手机号匹配的运营商接口，则无法通过手机号查询确定原绑定手机号的手机状态，也就无法验证用户的手机是否处于正常的注销流程，此时，为了保证安全性，可跳转至人工处理页面，指示用户完成相应的信息填写，以通过人工审核方式完成对目标账号的手机号重绑定。
S240、调用运营商接口查询原绑定手机号的手机状态。
示例性的，可将携带有原绑定手机号的手机状态获取请求，通过调用运营商接口发送至该运营商，以使运营商根据该原绑定手机号查询对应的手机状态，并返回该手机状态。在一实施例中，手机状态包括但不限于：使用状态、停机状态、二次放号状态等。
S250、判断查询结果是否为原绑定手机号处于二次放号状态：在查询结果为原绑定手机号处于二次放号状态的情况下，执行S260；在查询结果为原绑定手机号未处于二次放号状态的情况下的情况下，执行S280。
S260、判断当前换绑设备是否为可信验证设备；在当前换绑设备为可信验证设备的情况下，执行S270；在当前换绑设备为不可信验证设备的情况下，执行S280。
在一实施例中，可信验证设备可以是使用原绑定手机号完成过目标账号的登录的设备。在一实施例中，可以在使用手机号登录目标账号的过程中，记录该手机号所在设备的设备识别码，以便在手机号换绑时进行设备验证。
示例性的，若原绑定手机号处于二次放号状态，说明该原绑定手机号已经 被用户注销，并二次放号给了别人，由于用户换绑手机一般会发生在比较短时间内，则可以说明该二次放号过程发生在一个较短的时间内，进而可以间接说明上述换绑操作是用户正常的换手机号操作。此时，由于该原绑定手机号已不可用，无法通过输入原绑定手机号以及登录验证码来进行换绑操作。若与此同时，当前换绑设备也同时被确定为可信验证设备，则说明虽然原绑定手机号已无法直接用于进行换绑操作安全性验证，但当前换绑设备曾经使用过该原绑定手机号进行目标账号登录，表明当前使用该设备进行换绑操作的用户为合法用户，也即验证原绑定手机号的当前使用状态满足安全换绑条件。
在原绑定手机号未处于二次放号状态，或者当前换绑设备不为可信验证设备的情况下，验证原绑定手机号的当前使用状态不满足安全换绑条件。
S270、提供新绑定手机号输入界面，以获取新绑定手机号完成针对目标账号的手机号重绑定。
S280、获取与目标账号对应的第三方关联账号。
S290、调用与第三方关联账号匹配的第三方认证接口对目标账号进行验证，并根据第三方认证接口反馈的验证结果执行对应的换绑处理操作。
本实施例的技术方案，通过先判断是否能够获取与原绑定手机号匹配的运营商接口，在能够获取运营商接口的情况下，调用运营商接口查询原绑定手机号的手机状态，并通过判断查询结果是否为二次放号状态，以及当前换绑设备是否为可信验证设备，来验证原绑定手机号的当前使用状态是否满足安全换绑条件，进而在原绑定手机号的当前使用状态不满足安全换绑条件时，使用与目标账号对应的第三方关联账号进行安全性验证，最后根据验证结果执行对应的换绑处理操作，本实施例利用原绑定手机号的手机状态以及当前换绑设备的可信程度，进行原绑定手机号的安全性确认操作，使得只有在原绑定手机号确认无法使用且当前换绑设备为可信设备时，才会直接进行换绑操作，在原绑定手机号可以使用或当前换绑设备为不可信设备的情况下，还需要进行第三方验证，从而保证了换绑操作的安全性和可靠性。
实施例三
图3为本公开实施例三提供的一种手机号换绑验证方法的流程示意图。本实施例以上述实施例中为基础进行说明，提供了可选的手机号换绑验证方法。在本实施例中，根据第三方认证接口反馈的验证结果执行对应的换绑处理操作，包括：在确定第三方认证接口反馈的验证结果为认证通过响应的情况下，提供新绑定手机号输入界面，以获取新绑定手机号完成针对目标账号的手机号重绑 定。另外，将根据第三方认证接口反馈的验证结果执行对应的换绑处理操作，还包括：在确定第三方认证接口反馈的验证结果为认证失败响应的情况下，检测是否预先设置与目标账号对应的验证密码；在预先设置验证密码的情况下，提供验证密码输入界面，并在在检测到输入正确的验证密码后，提供新绑定手机号输入界面，以获取新绑定手机号完成针对目标账号的手机号重绑定；在未预先设置与验证密码的情况下，跳转至人工处理页面完成针对目标账号的手机号重绑定。本实施例提供的方法包括如下步骤：
S310、在检测到针对目标账号的手机号换绑验证请求的情况下，获取与目标账号对应的原绑定手机号。
S320、验证原绑定手机号的当前使用状态是否满足安全换绑条件，在原绑定手机号的当前使用状态不满足安全换绑条件的情况下，获取与目标账号对应的第三方关联账号。
S330、调用与第三方关联账号匹配的第三方认证接口对目标账号进行验证。
S340、确定第三方认证接口反馈的验证结果是否为认证通过响应，在第三方认证接口反馈的验证结果是认证通过响应的情况下，执行S350；在第三方认证接口反馈的验证结果是认证失败响应的情况下，执行S360。
示例性的，若用户在第三方平台对应的认证界面上选择点击确认按键，则可通过第三方认证接口接收到的反馈的验证结果为认证通过响应；若用户在第三方平台对应的认证界面上选择点击取消按键或直接退出该认证界面，则可通过第三方认证接口接收到的反馈的验证结果为认证失败响应。
通过确定第三方认证接口反馈的验证结果是否为认证通过响应，可判断在原绑定手机号的使用状态不满足安全换绑条件的情况下，也即利用原绑定手机号进行的安全性验证无法通过的情况下，换绑操作是否还具有安全性，与原手机号无法验证的情况下直接进行人工申诉的方式相比，第三方认证可通过用户自己快速完成，无需后台审核人员参与，从而简化了审核操作的流程，降低了用户操作及等待时间。
S350、提供新绑定手机号输入界面，以获取新绑定手机号完成针对目标账号的手机号重绑定。
示例性的，若确定第三方认证接口反馈的验证结果为认证通过响应，则说明当前换绑操作为安全操作，可直接进行手机号重绑定。
S360、检测是否预先设置与目标账号对应的验证密码，在预先设置验证密码的情况下，执行S370；在未预先设置验证密码的情况下，执行S380。
本实施例中，预先设置的与目标账号对应的验证密码可以是，针对目标账 号用户预先输入的关于设定提示性问题的答案信息。例如，该验证密码可以是设定提示性问题“你的生日是哪天？”对应的用户输入的答案信息“5月20日”。
示例性的，若确定第三方认证接口反馈的验证结果不为认证通过响应，即认证失败响应，则说明该第三方认证也无法进行验证，或者验证失败，此时，可在预先设置有与目标账号对应的验证密码的情况下，通过该验证密码来验证该用户是否为目标账号的合法用户。
S370、提供验证密码输入界面，并在检测到输入正确的验证密码后，提供新绑定手机号输入界面，以获取新绑定手机号完成针对目标账号的手机号重绑定。
举一个实际例子，合法用户预先设置的与目标账号对应的验证密码为“5月20日”，当确定第三方认证接口反馈的验证结果不为认证通过响应，且检测到该目标账号预先设置有验证密码时，可在当前换绑设备上向用户提供显示有“你的生日是哪天？”以及对应答案输入区域的验证密码输入界面。当检测到用户在答案输入区域输入的答案为“5月20日”时，则可确定用户输入了正确的验证密码，当前换绑操作为合法操作，从而可直接进行手机号重绑定。
S380、跳转至人工处理页面完成针对目标账号的手机号重绑定。
示例性的，若确定第三方认证接口反馈的验证结果不为认证通过响应，且没有检测到预先设置的与目标账号对应的验证密码，则说明已经无法通过用户自主完成换绑操作的安全性验证，此时，可再跳转至人工处理页面，通过用户填写的相关信息，借助后台人员进行人工申诉完成该安全性验证，并在验证通过时完成针对目标账号的手机号重绑定。
本实施例的技术方案，通过在调用与目标账号对应的第三方关联账号相匹配的第三方认证接口，对目标账号进行验证时，确定第三方认证接口反馈的验证结果是否为认证通过响应，在第三方认证接口反馈的验证结果为认证通过响应的情况下，直接进行手机号重绑定，在第三方认证接口反馈的验证结果不为认证通过响应的情况下，在检测有预先设置与目标账号对应的验证密码时，对用户输入的验证密码与预先设置的验证密码来验证该用户是否为合法用户，进而在输入正确的验证密码时，进行手机号重绑定，在检测未有预先设置与目标账号对应的验证密码时，转为人工处理审核，利用验证密码来认证进行换绑操作的用户是否为目标账号的合法用户，以自动完成换绑操作安全性审核，实现了在保证换绑过程安全性和可靠性的同时，尽量省去人工审核操作流程，从而减少了用户操作及等待时间。
实施例四
图4为本公开实施例四提供的一种手机号换绑验证装置的结构示意图。参考图4，手机号换绑验证装置包括：绑定获取模块410、条件验证模块420以及换绑处理模块430，下面对多个模块进行说明。
绑定获取模块410，设置为在检测到针对目标账号的手机号换绑验证请求的情况下，获取与目标账号对应的原绑定手机号；条件验证模块420，设置为验证所述原绑定手机号的当前使用状态是否满足安全换绑条件，在原绑定手机号的当前使用状态不满足安全换绑条件的情况下，获取与所述目标账号对应的第三方关联账号；换绑处理模块430，设置为调用与所述第三方关联账号匹配的第三方认证接口对所述目标账号进行验证，并根据第三方认证接口反馈的验证结果执行对应的换绑处理操作。
本实施例提供的手机号换绑验证装置，通过在检测到针对目标账号的手机号换绑验证请求时，获取与目标账号对应的原绑定手机号，验证该原绑定手机号的当前使用状态是否满足安全换绑条件，在原绑定手机号的当前使用状态不满足安全换绑条件时，获取与该目标账号对应的第三方关联账号，调用与该第三方关联账号匹配的第三方认证接口对该目标账号进行验证，并根据反馈的验证结果执行对应的换绑处理操作，利用第三方认证对原绑定手机号不满足安全换绑条件的目标账号进行换绑安全验证，解决了需要用户通过人工申诉的方式才能进行手机号换绑，从而导致操作流程复杂、用户操作及等待时间较长的问题，实现了在保证换绑过程安全性以及可靠性的同时，简化了操作流程，并减少了用户操作及等待时间。
在一实施例中，该装置还可以包括：界面提供模块，设置为在验证所述原绑定手机号的当前使用状态是否满足安全换绑条件之后，在原绑定手机号的当前使用状态满足安全换绑条件的情况下，提供新绑定手机号输入界面，以获取新绑定手机号完成针对所述目标账号的手机号重绑定。
在一实施例中，条件验证模块420是设置为：判断是否能够获取与所述原绑定手机号匹配的运营商接口；在能够获取运营商接口的情况下，调用所述运营商接口查询所述原绑定手机号的手机状态；在查询结果为所述原绑定手机号未处于二次放号状态，或者当前换绑设备不为可信验证设备的情况下，验证所述原绑定手机号的当前使用状态不满足安全换绑条件；在查询结果为所述原绑定手机号处于二次放号状态，且当前换绑设备为可信验证设备的情况下，验证所述原绑定手机号的当前使用状态满足安全换绑条件。
在一实施例中，条件验证模块42还设置为：在判断是否能够获取与所述原绑定手机号匹配的运营商接口之后，在不能够获取运营商接口的情况下，跳转 至人工处理页面完成针对所述目标账号的手机号重绑定。
在一实施例中，换绑处理模块430是设置为：在确定所述第三方认证接口反馈的验证结果为认证通过响应的情况下，提供新绑定手机号输入界面，以获取新绑定手机号完成针对所述目标账号的手机号重绑定。
在一实施例中，换绑处理模块430还设置为：在确定所述第三方认证接口反馈的验证结果为认证失败响应的情况下，检测是否预先设置与所述目标账号对应的验证密码；在预先设置验证密码的情况下，将验证密码输入界面提供给用户，并在检测到输入正确的验证密码后，提供新绑定手机号输入界面，以获取新绑定手机号完成针对所述目标账号的手机号重绑定；在未预先设置验证密码的情况下，跳转至人工处理页面完成针对所述目标账号的手机号重绑定。
上述装置可执行本公开任意实施例所提供的方法。
实施例五
下面参考图5，图5示出了适于用来实现本公开实施例的终端设备500的结构示意图。本公开实施例中的终端设备可以包括但不限于诸如移动电话、笔记本电脑、数字广播接收器、个人数字助理(Personal Digital Assistant，PDA)、平板电脑(Portable Android Device，PAD)、便携式多媒体播放器(Portable Media Player，PMP)、车载终端(例如车载导航终端)等等的移动终端以及诸如数字电视(television，TV)、台式计算机等等的固定终端。图5示出的终端设备仅仅是一个示例，不应对本公开实施例的功能和使用范围带来任何限制。
如图5所示，终端设备500可以包括处理装置(例如中央处理器、图形处理器等)501，处理装置可以根据存储在只读存储器(Read-Only Memory，ROM)502中的程序或者从存储装置508加载到随机访问存储器(Random Access Memory，RAM)503中的程序而执行多种适当的动作和处理。在RAM 503中，还存储有终端设备500操作所需的各种程序和数据。处理装置501、ROM 502以及RAM 503通过总线504彼此相连。输入/输出(I/O)接口505也连接至总线504。
通常，以下装置可以连接至I/O接口505：包括例如触摸屏、触摸板、键盘、鼠标、摄像头、麦克风、加速度计、陀螺仪等的输入装置506；包括例如液晶显示器(Liquid Crystal Display，LCD)、扬声器、振动器等的输出装置507；包括例如磁带、硬盘等的存储装置508；以及通信装置509。通信装置509可以允许终端设备500与其他设备进行无线或有线通信以交换数据。虽然图5示出了具有各种装置的终端设备500，但是应理解的是，并不要求实施或具备所有示出的 装置。可以替代地实施或具备更多或更少的装置。
根据本公开的实施例，上文参考流程图描述的过程可以被实现为计算机软件程序。例如，本公开的实施例包括一种计算机程序产品，计算机程序产品包括承载在计算机可读介质上的计算机程序，该计算机程序包含用于执行流程图所示的方法的程序代码。在这样的实施例中，该计算机程序可以通过通信装置509从网络上被下载和安装，或者从存储装置508被安装，或者从ROM 502被安装。在该计算机程序被处理装置501执行时，执行本公开实施例的方法中限定的上述功能。
需要说明的是，本公开上述的计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质或者是上述两者的任意组合。计算机可读存储介质例如可以是——但不限于——电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子可以包括但不限于：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、RAM、ROM、可擦式可编程只读存储器(Erasable Programmable Read-Only Memory，EPROM)或闪存、光纤、便携式紧凑磁盘只读存储器(Compact Disc Read-Only Memory，CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。在本公开中，计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。而在本公开中，计算机可读信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。计算机可读信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读信号介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。计算机可读介质上包含的程序代码可以用任何适当的介质传输，包括但不限于：电线、光缆、射频(Radio Frequency，RF)等等，或者上述的任意合适的组合。
上述计算机可读介质可以是上述终端设备中所包含的；也可以是单独存在，而未装配入该终端设备中。
上述计算机可读介质承载有一个或者多个程序，当上述一个或者多个程序被该终端设备执行时，使得该终端设备：获取至少两个网际协议地址；向节点评价设备发送包括所述至少两个网际协议地址的节点评价请求，其中，所述节点评价设备从所述至少两个网际协议地址中，选取网际协议地址并返回；接收所述节点评价设备返回的网际协议地址；其中，所获取的网际协议地址指示内容分发网络中的边缘节点。
或者，上述计算机可读介质承载有一个或者多个程序，当上述一个或者多个程序被该终端设备执行时，使得该终端设备：在检测到针对目标账号的手机号换绑验证请求的情况下，获取与目标账号对应的原绑定手机号；验证原绑定手机号的当前使用状态是否满足安全换绑条件：在原绑定手机号的当前使用状态不满足安全换绑条件的情况下，获取与目标账号对应的第三方关联账号；调用与第三方关联账号匹配的第三方认证接口对目标账号进行验证，并根据第三方认证接口反馈的验证结果执行对应的换绑处理操作。
可以以一种或多种程序设计语言或其组合来编写用于执行本公开的操作的计算机程序代码，上述程序设计语言包括面向对象的程序设计语言—诸如Java、Smalltalk、C++，还包括常规的过程式程序设计语言—诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算机上执行、部分地在用户计算机上执行、作为一个独立的软件包执行、部分在用户计算机上部分在远程计算机上执行、或者完全在远程计算机或服务器上执行。在涉及远程计算机的情形中，远程计算机可以通过任意种类的网络——包括局域网(Local Area Network，LAN)或广域网(Wide Area Network，WAN)—连接到用户计算机，或者，可以连接到外部计算机(例如利用因特网服务提供商来通过因特网连接)。
附图中的流程图和框图，图示了按照本公开多种实施例的系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上，流程图或框图中的每个方框可以代表一个模块、程序段、或代码的一部分，该模块、程序段、或代码的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。也应当注意，在有些作为替换的实现中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个接连地表示的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图和/或流程图中的每个方框、以及框图和/或流程图中的方框的组合，可以用执行规定的功能或操作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
描述于本公开实施例中所涉及到的模块或单元可以通过软件的方式实现，也可以通过硬件的方式来实现。其中，模块或单元的名称在某种情况下并不构成对该模块或单元本身的限定，例如，绑定获取模块还可以被描述为“用于在检测到针对目标账号的手机号换绑验证请求时，获取与目标账号对应的原绑定手机号的模块”。

Claims (10)

  1. 一种手机号换绑验证方法，包括：
    在检测到针对目标账号的手机号换绑验证请求的情况下，获取与所述目标账号对应的原绑定手机号；
    验证所述原绑定手机号的当前使用状态是否满足安全换绑条件：在所述原绑定手机号的当前使用状态不满足所述安全换绑条件的情况下，获取与所述目标账号对应的第三方关联账号；
    调用与所述第三方关联账号匹配的第三方认证接口对所述目标账号进行验证，并根据第三方认证接口反馈的验证结果执行对应的换绑处理操作。
  2. 根据权利要求1所述的方法，在验证所述原绑定手机号的当前使用状态是否满足安全换绑条件之后，还包括：
    在所述原绑定手机号的当前使用状态满足所述安全换绑条件的情况下，提供新绑定手机号输入界面，以获取新绑定手机号完成针对所述目标账号的手机号重绑定。
  3. 根据权利要求1或2所述的方法，其中，验证所述原绑定手机号的当前使用状态是否满足安全换绑条件，包括：
    判断是否能够获取与所述原绑定手机号匹配的运营商接口；在能够获取所述运营商接口的情况下，调用所述运营商接口查询所述原绑定手机号的手机状态；
    在查询结果为所述原绑定手机号未处于二次放号状态，或者当前换绑设备不为可信验证设备的情况下，验证所述原绑定手机号的当前使用状态不满足安全换绑条件；
    在查询结果为所述原绑定手机号处于二次放号状态，且当前换绑设备为可信验证设备的情况下，验证所述原绑定手机号的当前使用状态满足安全换绑条件。
  4. 根据权利要求3所述的方法在判断是否能够获取与所述原绑定手机号匹配的运营商接口之后，还包括：
    在不能够获取所述运营商接口的情况下，跳转至人工处理页面完成针对所述目标账号的手机号重绑定。
  5. 根据权利要求1-4任一项所述的方法，其中，根据第三方认证接口反馈的验证结果执行对应的换绑处理操作，包括：
    在确定所述第三方认证接口反馈的验证结果为认证通过响应的情况下，提供新绑定手机号输入界面，以获取新绑定手机号完成针对所述目标账号的手机 号重绑定。
  6. 根据权利要求5所述的方法，其中，根据第三方认证接口反馈的验证结果执行对应的换绑处理操作，还包括：
    在确定所述第三方认证接口反馈的验证结果为认证失败响应的情况下，检测是否预先设置与所述目标账号对应的验证密码；
    在预先设置与所述目标账号对应的验证密码的情况下，提供验证密码输入界面，并在在检测到输入正确的验证密码后，提供所述新绑定手机号输入界面，以获取新绑定手机号完成针对所述目标账号的手机号重绑定；
    在未预先设置与所述目标账号对应的验证密码的情况下，跳转至人工处理页面完成针对所述目标账号的手机号重绑定。
  7. 一种手机号换绑验证装置，包括：
    绑定获取模块，设置为在检测到针对目标账号的手机号换绑验证请求的情况下，获取与所述目标账号对应的原绑定手机号；
    条件验证模块，设置为验证所述原绑定手机号的当前使用状态是否满足安全换绑条件：在所述所述原绑定手机号的当前使用状态不满足所述安全换绑条件的情况下，获取与所述目标账号对应的第三方关联账号；
    换绑处理模块，设置为调用与所述第三方关联账号匹配的第三方认证接口对所述目标账号进行验证，并根据第三方认证接口反馈的验证结果执行对应的换绑处理操作。
  8. 根据权利要求7所述的装置，还包括：
    界面提供模块，设置为在验证所述原绑定手机号的当前使用状态是否满足安全换绑条件之后，在所述原绑定手机号的当前使用状态满足所述安全换绑条件的情况下，提供新绑定手机号输入界面，以获取新绑定手机号完成针对所述目标账号的手机号重绑定。
  9. 一种终端设备，包括：
    至少一个个处理装置；
    存储装置，设置为存储至少一个程序；
    当所述至少一个程序被所述至少一个处理装置执行，使得所述至少一个处理装置实现如权利要求1-6中任一所述的手机号换绑验证方法。
  10. 一种计算机可读存储介质，存储有计算机程序，所述计算机程序被处理装置执行时实现如权利要求1-6中任一所述的手机号换绑验证方法。
PCT/CN2020/070719 2019-03-13 2020-01-07 手机号换绑验证方法、装置、设备及存储介质 WO2020181914A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910189551.X 2019-03-13
CN201910189551.XA CN109905398B (zh) 2019-03-13 2019-03-13 手机号换绑验证方法、装置、设备及存储介质

Publications (1)

Publication Number Publication Date
WO2020181914A1 true WO2020181914A1 (zh) 2020-09-17

Family

ID=66952146

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/070719 WO2020181914A1 (zh) 2019-03-13 2020-01-07 手机号换绑验证方法、装置、设备及存储介质

Country Status (2)

Country Link
CN (1) CN109905398B (zh)
WO (1) WO2020181914A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112788603A (zh) * 2021-01-27 2021-05-11 维沃移动通信有限公司 验证码转发方法、装置、设备及介质
CN112822676A (zh) * 2021-01-15 2021-05-18 中国银联股份有限公司 一种访问应用的方法及装置
CN114125139A (zh) * 2021-11-18 2022-03-01 维沃移动通信有限公司 信息处理方法和电子设备
CN115134117A (zh) * 2022-05-25 2022-09-30 中国信息通信研究院 用于验证互联网注册用户身份的方法及装置、服务器、存储介质
CN115134119A (zh) * 2022-05-25 2022-09-30 中国信息通信研究院 用于验证互联网注册用户身份的方法及装置、服务器、存储介质

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109905398B (zh) * 2019-03-13 2020-07-24 北京字节跳动网络技术有限公司 手机号换绑验证方法、装置、设备及存储介质
CN110602676B (zh) * 2019-09-09 2021-04-27 飞天诚信科技股份有限公司 一种防止硬件钱包被恶意配对的方法
CN111132128B (zh) * 2019-12-30 2022-04-29 维沃移动通信有限公司 一种账户控制方法及装置
CN111832007A (zh) * 2020-01-20 2020-10-27 北京嘀嘀无限科技发展有限公司 账号找回方法、装置、设备及计算机可读存储介质
CN111835701B (zh) * 2020-01-20 2023-05-30 北京嘀嘀无限科技发展有限公司 账号管理方法、装置、设备及计算机可读存储介质
CN115314372B (zh) * 2022-07-26 2023-10-10 珠海格力电器股份有限公司 设备配网方法、系统、计算机设备和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103746792A (zh) * 2013-12-31 2014-04-23 郑盈盈 一种第三方应用账号与手机号码绑定、解除和更新方法
US20140136704A1 (en) * 2011-08-03 2014-05-15 Tencent Technology (Shenzhen) Company Limited Method and system for registration or login
CN105959293A (zh) * 2016-06-17 2016-09-21 阿里巴巴集团控股有限公司 电子账号的管理方法和装置
CN108449727A (zh) * 2018-06-05 2018-08-24 中国联合网络通信集团有限公司 短消息处理方法及系统
CN109905398A (zh) * 2019-03-13 2019-06-18 北京字节跳动网络技术有限公司 手机号换绑验证方法、装置、设备及存储介质

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090078758A1 (en) * 2007-09-26 2009-03-26 First Data Corporation Systems and methods for cardless transactions using a telephone number
CN104243524B (zh) * 2013-06-19 2016-04-13 腾讯科技（深圳）有限公司 实现联系人多平台同步的方法和装置
CN104917749B (zh) * 2015-04-15 2018-10-02 腾讯科技（深圳）有限公司 帐号注册方法及装置
CN105306733B (zh) * 2015-11-13 2018-11-09 深圳正品创想科技有限公司 基于手机app的第三方登录绑定手机号方法
CN106878970B (zh) * 2015-12-14 2020-05-05 阿里巴巴集团控股有限公司 变更手机号码的业务请求的识别方法及装置
CN105897873A (zh) * 2016-04-01 2016-08-24 努比亚技术有限公司 一种更换绑定手机号的装置和方法
CN107276970B (zh) * 2016-04-08 2020-06-09 阿里巴巴集团控股有限公司 一种解绑、绑定方法和装置
CN107346490A (zh) * 2016-05-05 2017-11-14 阿里巴巴集团控股有限公司 电子账号的管理方法和装置
CN107659931B (zh) * 2016-07-25 2020-11-24 中国移动通信集团上海有限公司 一种变更绑定手机号码的方法和装置
CN108512803A (zh) * 2017-02-23 2018-09-07 中兴通讯股份有限公司 提醒更改账号绑定电话号码的方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140136704A1 (en) * 2011-08-03 2014-05-15 Tencent Technology (Shenzhen) Company Limited Method and system for registration or login
CN103746792A (zh) * 2013-12-31 2014-04-23 郑盈盈 一种第三方应用账号与手机号码绑定、解除和更新方法
CN105959293A (zh) * 2016-06-17 2016-09-21 阿里巴巴集团控股有限公司 电子账号的管理方法和装置
CN108449727A (zh) * 2018-06-05 2018-08-24 中国联合网络通信集团有限公司 短消息处理方法及系统
CN109905398A (zh) * 2019-03-13 2019-06-18 北京字节跳动网络技术有限公司 手机号换绑验证方法、装置、设备及存储介质

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112822676A (zh) * 2021-01-15 2021-05-18 中国银联股份有限公司 一种访问应用的方法及装置
CN112822676B (zh) * 2021-01-15 2023-06-30 中国银联股份有限公司 一种访问应用的方法及装置
CN112788603A (zh) * 2021-01-27 2021-05-11 维沃移动通信有限公司 验证码转发方法、装置、设备及介质
CN112788603B (zh) * 2021-01-27 2023-09-19 维沃移动通信有限公司 验证码转发方法、装置、设备及介质
CN114125139A (zh) * 2021-11-18 2022-03-01 维沃移动通信有限公司 信息处理方法和电子设备
CN115134117A (zh) * 2022-05-25 2022-09-30 中国信息通信研究院 用于验证互联网注册用户身份的方法及装置、服务器、存储介质
CN115134119A (zh) * 2022-05-25 2022-09-30 中国信息通信研究院 用于验证互联网注册用户身份的方法及装置、服务器、存储介质
CN115134117B (zh) * 2022-05-25 2023-10-27 中国信息通信研究院 用于验证互联网注册用户身份的方法及装置、服务器、存储介质
CN115134119B (zh) * 2022-05-25 2024-03-26 中国信息通信研究院 用于验证互联网注册用户身份的方法及装置、服务器、存储介质

Also Published As

Publication number Publication date
CN109905398B (zh) 2020-07-24
CN109905398A (zh) 2019-06-18

Similar Documents

Publication Publication Date Title
WO2020181914A1 (zh) 手机号换绑验证方法、装置、设备及存储介质
CN111639319B (zh) 用户资源授权方法、装置及计算机可读存储介质
US11671826B2 (en) Voice control and telecommunications service integration
US20210319091A1 (en) Multiple device credential sharing
WO2021077833A1 (zh) 信息推送方法、设备、电子设备及计算机可读存储介质
CN110351269B (zh) 通过第三方服务器登录开放平台的方法
US20070157310A1 (en) Security ensuring by program analysis on information device and transmission path
US10623410B2 (en) Multi-level, distributed access control between services and applications
US8811944B2 (en) Authentication request management
US9118686B2 (en) Per process networking capabilities
TWI575398B (zh) A terminal verification registration system, a terminal verification registration method, and a recording medium
US20140006598A1 (en) Methods, apparatuses and computer program products for facilitating dynamic origin-based domain allocation
US11303596B2 (en) Method and a device for processing information
WO2021147455A1 (zh) 消息处理方法、装置及电子设备
CN1499359A (zh) 通信设备、程序和记录介质
US20150012973A1 (en) Methods and apparatus for sharing a service between multiple virtual machines
US20230124149A1 (en) Method and apparatus for establishing multimedia call, and electronic device
CN111737687A (zh) 网页应用系统的访问控制方法、系统、电子设备和介质
WO2023193572A1 (zh) 一种数据管理方法、装置、服务器和存储介质
US20150128129A1 (en) Method and device for installing application
WO2023185514A1 (zh) 传输消息的方法、装置、存储介质及电子设备
US20150012918A1 (en) Methods and apparatus for sharing a physical device between multiple virtual machines
US20150012654A1 (en) Methods and apparatus for sharing a physical device between multiple physical machines
US20240177200A1 (en) Business service interaction method and apparatus, device, and storage medium
CN111367590A (zh) 中断事件处理方法及其装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20770702

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 21/01/2022)

122 Ep: pct application non-entry in european phase

Ref document number: 20770702

Country of ref document: EP

Kind code of ref document: A1