WO2025252052A1 - 用于验证码处理的方法、装置、设备和存储介质 - Google Patents

用于验证码处理的方法、装置、设备和存储介质

Info

Publication number
WO2025252052A1
WO2025252052A1 PCT/CN2025/098663 CN2025098663W WO2025252052A1 WO 2025252052 A1 WO2025252052 A1 WO 2025252052A1 CN 2025098663 W CN2025098663 W CN 2025098663W WO 2025252052 A1 WO2025252052 A1 WO 2025252052A1
Authority
WO
WIPO (PCT)
Prior art keywords
verification
verification code
recognition control
captcha
response
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
PCT/CN2025/098663
Other languages
English (en)
French (fr)
Inventor
杨一帆
谈瑞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Zitiao Network Technology Co Ltd
Original Assignee
Beijing Zitiao Network Technology Co Ltd
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 Beijing Zitiao Network Technology Co Ltd filed Critical Beijing Zitiao Network Technology Co Ltd
Publication of WO2025252052A1 publication Critical patent/WO2025252052A1/zh
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
    • G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • 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/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials

Definitions

  • the exemplary embodiments disclosed herein generally relate to the field of computers, and particularly to methods, apparatus, devices, and computer-readable storage media for CAPTCHA processing.
  • CAPTCHAs are used for authentication, to prevent accidental operations, to prevent batch processing, and to prevent brute-force attacks, etc.
  • verification codes are typically sent to terminal devices via SMS, email, or notification messages. Users usually need to record the verification code and then manually enter it, which easily leads to errors.
  • a method for processing CAPTCHAs includes: in response to receiving a verification request for a CAPTCHA, presenting a verification page, the verification page including a first input box for inputting a CAPTCHA and at least one CAPTCHA recognition control; in response to receiving a trigger operation of a CAPTCHA recognition control in the at least one CAPTCHA recognition control, acquiring verification information containing a CAPTCHA through the triggered CAPTCHA recognition control; identifying a target CAPTCHA from the verification information; and presenting the identified target CAPTCHA in the first input box.
  • an apparatus for CAPTCHA processing includes: a verification page presentation module configured to present a verification page in response to receiving a verification request for a CAPTCHA, the verification page including a first input box for inputting a CAPTCHA and at least one CAPTCHA recognition control; an acquisition module configured to acquire verification information containing a CAPTCHA through the triggered CAPTCHA recognition control in response to receiving a trigger operation from the at least one CAPTCHA recognition control; a recognition module configured to recognize a target CAPTCHA from the verification information; and a CAPTCHA presentation module configured to present the recognized target CAPTCHA in the first input box.
  • an electronic device in a third aspect of this disclosure, includes at least one processor; and at least one memory coupled to the at least one processor and storing instructions for execution by the at least one processor. When executed by the at least one processor, the instructions cause the electronic device to perform the method of the first aspect.
  • a computer-readable storage medium stores computer-executable instructions that, when executed by a processor, implement the method of the first aspect.
  • a computer program product including computer-executable instructions, wherein when executed by a processor, the computer-executable instructions implement the method according to a first aspect of this disclosure.
  • Figure 1 shows a schematic diagram of an example environment in which embodiments of the present disclosure can be implemented
  • Figure 2 shows a flowchart of a process for CAPTCHA processing according to some embodiments of the present disclosure
  • FIGS. 3A to 3F illustrate schematic diagrams of example pages according to some embodiments of the present disclosure
  • FIGS. 4A to 4C illustrate schematic diagrams of example pages according to other embodiments of the present disclosure
  • Figure 5 shows a schematic structural block diagram of an apparatus for CAPTCHA processing according to some embodiments of the present disclosure.
  • Figure 6 shows a block diagram of an electronic device that can implement one or more embodiments of the present disclosure.
  • performing a step in response to A does not mean that the step is performed immediately after A, but may include one or more intermediate steps.
  • relevant users should be informed of the type, scope of use, and usage scenarios of the information involved in this disclosure through appropriate means in accordance with relevant laws and regulations, and authorization should be obtained from the relevant users.
  • relevant users may include any type of rights holder, such as individuals, enterprises, and groups.
  • a prompt message is sent to the relevant user to clearly inform the user that the requested operation will require obtaining and using the user's information, thereby enabling the relevant user to choose whether to provide information to the software or hardware such as the electronic device, application, server, or storage medium that performs the operation of the technical solution disclosed herein based on the prompt message.
  • a prompt message in response to a user's active request, can be sent to the user, such as a pop-up window, where the prompt message can be presented in text format.
  • the pop-up window can also include a selection control allowing the user to choose "agree” or "disagree” to provide information to the electronic device.
  • Figure 1 illustrates a schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented.
  • an application 120 is installed on a terminal device 110.
  • a user 140 can interact with the application 120 via the terminal device 110 and/or an attached device of the terminal device 110.
  • application 120 can be any suitable application associated with a verification code operation.
  • application 120 can be an application for user login, or an application that user 140 browses or operates.
  • terminal device 110 can display page 150 of application 120.
  • Page 150 can include various types of pages that application 120 can provide, such as a page for verifying a verification code, a page for displaying a verification code, etc.
  • terminal device 110 communicates with server 130 to provide services to application 120.
  • Terminal device 110 can be any type of mobile terminal, fixed terminal, or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, personal communication system (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio/video players, digital cameras/camcorders, positioning devices, television receivers, radio receivers, e-book devices, gaming devices, or any combination thereof, including accessories and peripherals of these devices or any combination thereof.
  • terminal device 110 can also support any type of user-facing interface (such as "wearable" circuitry).
  • Server 130 can be various types of computing systems/servers capable of providing computing power, including but not limited to mainframes, edge computing nodes, computing devices in cloud environments, etc.
  • CAPTCHA verification is typically required. For example, when a user logs in, a CAPTCHA can be used for authentication, after which a page containing the user's personal information is displayed. CAPTCHAs can also be used to prevent accidental operations, prevent batch processing, or prevent brute-force attacks, among other things.
  • verification codes are sent to devices via SMS, email, or notifications when verification is required. Users typically need to remember the code and then manually enter it, which is not only cumbersome but also prone to errors. For example, when a verification code is sent via SMS and needs to be entered on an app's page, the user must switch to the page displaying the SMS to view the code, and then switch back to the app to enter it. If the code is entered incorrectly or the user fails to remember the complete code, repeated page switching is necessary. This not only affects the efficiency of the verification process but also impacts the user experience.
  • an improved scheme for CAPTCHA processing is provided.
  • a verification page in response to receiving a verification request for a CAPTCHA, a verification page is presented.
  • the verification page includes a first input box for entering a CAPTCHA and at least one CAPTCHA recognition control.
  • verification information containing the CAPTCHA is obtained through the triggered CAPTCHA recognition control; a target CAPTCHA is identified from the verification information; and the identified target CAPTCHA is presented in the first input box.
  • the solution presents a verification page including a primary input field and a verification code recognition control. Users can trigger either control to identify the target verification code from the verification information and display it in the primary input field. This eliminates the need for manual code input, reducing user complexity and preventing errors.
  • Figure 2 illustrates a flowchart of a process 200 for CAPTCHA processing according to some embodiments of the present disclosure.
  • Figures 3A to 4C illustrate schematic diagrams of example pages 300A to 400C (also referred to simply as examples 300A to 400C) according to some embodiments of the present disclosure.
  • the pages shown in the drawings are merely examples, and various page designs may actually exist.
  • the various graphic elements on the page may have different arrangements and different visual representations, one or more elements may be omitted or replaced, and one or more other elements may also be present.
  • the embodiments of the present disclosure are not limited in this respect.
  • Examples 300A to 400C can be displayed on terminal device 110 or terminal device 120.
  • process 200 will be described with reference to environment 100 of FIG1, and explained in conjunction with Examples 300A to 400C.
  • operations performed by terminal device 110 can specifically be performed by relevant applications (e.g., application 120) installed on terminal device 110.
  • operations performed on the electronic device can be completed with the assistance of server 130.
  • terminal device 110 may present a verification page in response to receiving a verification request for a verification code.
  • This verification page may include, for example, a first input box for entering a verification code and at least one verification code recognition control.
  • Example 300A illustrates an example of a user login page.
  • Example 300A includes an account input field 301 and an account confirmation control 302.
  • Terminal device 110 can display a login account in the account input field 301 in response to input from user 140 via an input device (e.g., keyboard, touchscreen, handwriting pad, etc.).
  • Terminal device 110 can send a login request to server 130 in response to a triggering operation of the account confirmation control 302.
  • Server 130 can send a verification request for a CAPTCHA to terminal device 110 in response to the login request.
  • Server 130 can also send verification information containing a CAPTCHA to terminal device 110 or other terminal devices based on the login account.
  • Terminal device 110 can display a verification page in response to the verification request.
  • terminal device 110 may display a specific operation page of application 120 (e.g., shopping page, transfer page, recharge page, etc.) in response to the operation of user 140.
  • a specific operation page of application 120 e.g., shopping page, transfer page, recharge page, etc.
  • terminal device 110 may obtain a verification request for a verification code and present a verification page in response to the specific operation page triggering a specific operation.
  • CAPTCHAs can be applied in various scenarios, not just the two mentioned above.
  • the process of receiving verification requests for CAPTCHAs may differ depending on the scenario in which they are applied, and will not be elaborated upon here.
  • the first input box can be any suitable input box.
  • the first input box can be a rectangular input box, which can hold a multi-digit verification code.
  • the first input box can include multiple boxes with the same number of digits as the verification code, and these multiple boxes can be arranged regularly on the verification page.
  • Example 300B illustrates an example of a verification page.
  • Example 300B includes a first input box 310 for entering the verification code.
  • the first input box 310 includes six boxes, each of which can be filled with one verification symbol, and the six boxes can hold a total of six verification symbols, which together form the verification code.
  • the verification code recognition control here can be any suitable control, including but not limited to input boxes, options, operation controls, etc.
  • terminal device 110 in response to receiving a trigger operation of a CAPTCHA recognition control in at least one CAPTCHA recognition control, obtains verification information containing a CAPTCHA through the triggered CAPTCHA recognition control.
  • the verification information may include verification information of various data types (e.g., text, images, audio, etc.).
  • the verification page may include a CAPTCHA recognition control.
  • the terminal device 110 may, in response to a triggering operation on the CAPTCHA recognition control, present a verification information selection page.
  • the verification information selection page may also include multiple data type selection controls, each corresponding to a different type of verification information.
  • the terminal device 110 may, in response to a triggering operation on any one of the multiple data type selection controls, obtain verification information of the corresponding type through the triggered data type selection control.
  • the verification page may include multiple CAPTCHA recognition controls, which can be used to obtain verification information of different data types.
  • the terminal device 110 can respond to a triggering operation on any one of the multiple CAPTCHA recognition controls, and obtain the corresponding type of verification information through the triggered CAPTCHA recognition control.
  • the user 140 can directly trigger the corresponding CAPTCHA recognition control on the verification page according to the data type of the verification information.
  • At least one CAPTCHA recognition control may include a first CAPTCHA recognition control.
  • the terminal device 110 may, in response to receiving a trigger operation from the first CAPTCHA recognition control, obtain verification text containing the CAPTCHA through the first CAPTCHA recognition control.
  • the verification text may have multiple forms, and the specific type of verification text is not limited here.
  • Example 300B includes a first CAPTCHA recognition control (e.g., CAPTCHA recognition control 320).
  • CAPTCHA recognition control 320 When terminal device 110 receives verification information containing verification text, terminal device 110 may, in response to an operation by user 140, receive a request to copy the verification text and add the verification text to the system clipboard. Subsequently, user 140 may trigger CAPTCHA recognition control 320 via terminal device 110 or an attached device of terminal device 110. Terminal device 110 may, in response to the triggering operation of CAPTCHA recognition control 320, use CAPTCHA recognition control 320 to retrieve the verification text located in the system clipboard.
  • terminal device 110 may also, in response to receiving a trigger operation from the first verification code recognition control, present at least one text type selection control on the verification page.
  • Terminal device 110 may, in response to a selection operation on any one of the at least one text type selection controls, obtain verification text of the corresponding type through the selected text type selection control.
  • the first verification code recognition control includes a paste recognition control and a second input box.
  • the terminal device 110 can, in response to receiving a trigger operation from the paste recognition control, display the verification text in the second input box. This allows the user to intuitively experience the pasting process of the verification text, thus improving the user experience.
  • the CAPTCHA recognition control 320 may include a second input box (i.e., input box 321) and a paste recognition control (i.e., control 322).
  • the terminal device 110 may determine that a trigger operation of control 322 has been received in response to a click operation on control 322 presented on the verification page.
  • the terminal device 110 may retrieve verification text 323 from the system clipboard and present the verification text 323 in input 321, as shown in Figure 3C.
  • the first CAPTCHA recognition control may also adopt other design schemes or layout methods.
  • the first CAPTCHA recognition control may include a paste input control, and the terminal device 110 may, in response to receiving a click operation on the paste input control, obtain the verification text from the system clipboard and display at least a portion of the verification text in the area of the paste input control.
  • At least one CAPTCHA recognition control includes a second CAPTCHA recognition control.
  • Terminal device 110 may, in response to receiving a trigger operation from the second CAPTCHA recognition control, acquire a verification image containing a CAPTCHA through the second CAPTCHA recognition control.
  • the verification image may include various types of images, as long as they contain a CAPTCHA; the type of verification image is not limited here.
  • Example 300B includes a second CAPTCHA recognition control (e.g., CAPTCHA recognition control 330).
  • Terminal device 110 can receive a verification image containing a CAPTCHA from server 130 or other electronic devices.
  • Terminal device 110 can also receive verification text containing a CAPTCHA from server 130 or other electronic devices.
  • Terminal device 110 can acquire a verification image containing a CAPTCHA in response to a photo capture or screenshot operation on a page displaying the verification text.
  • Terminal device 110 can acquire the verification image using the CAPTCHA recognition control 330 in response to a trigger operation.
  • the terminal device 110 may, in response to receiving a trigger operation from a second verification code recognition control, present at least one image acquisition control on the verification page.
  • the terminal device 110 may, in response to receiving a trigger operation for any one of the at least one image acquisition controls, acquire a verification image based on the image acquisition mode corresponding to the triggered image acquisition control. This provides users with multiple selectable image acquisition methods, thereby improving the user experience.
  • terminal device 110 may, in response to a click operation on the CAPTCHA recognition control 330 in Example 300B, present image acquisition control 331, image acquisition control 332, and image acquisition control 333 on the verification page.
  • Image acquisition control 331 is used to trigger the camera to take a picture and acquire the verification image.
  • Image acquisition control 332 is used to switch to the album page and select the verification image from the album.
  • Image acquisition control 333 is used to switch to the application interface and acquire the verification image from the application interface.
  • server 130 can send verification information to other terminal devices.
  • Terminal device 110 can respond to the trigger operation of image acquisition control 331, start the camera, and take a picture of the verification information display page of other terminal devices to obtain a photo containing the verification code.
  • the terminal device 110 can click the image acquisition control 332. Upon receiving a click operation on the image acquisition control 332, the terminal device 110 can switch to the photo album page. On the photo album page, the user 140 can click on the verification image containing the verification code, and the terminal device 110 can, upon receiving a selection operation for any verification image, acquire the corresponding verification image.
  • terminal device 110 can receive a verification image from server 130 or other electronic devices via an application.
  • a user can click on the image acquisition control 333.
  • terminal device 110 can switch to an application selection interface, which may include at least one application icon.
  • Terminal device 110 can respond to the selection of any application icon in the application selection interface and display the corresponding application interface.
  • Terminal device 110 can also respond to the selection of any image in the application interface and acquire that image as a verification image.
  • terminal device 110 can identify the target verification code from the verification information. In some embodiments, if the verification page presents multiple verification code recognition controls, terminal device 110 can identify the target verification code from the verification information of the corresponding type based on the recognition pattern corresponding to the triggered verification code recognition control.
  • terminal device 110 may, in response to receiving a trigger operation on paste recognition control 322, present verification text 323 in second input box 321.
  • Terminal device 110 may, in response to the presentation of verification text 323 in second input box 321, recognize the target verification code from the verification text 323 in second input box 321 based on a text recognition mode.
  • terminal device 110 may, in response to receiving a trigger operation on CAPTCHA recognition control 330, acquire a verification image through CAPTCHA recognition control 330.
  • terminal device 110 may display an image identifier 334 (e.g., the image name of the verification image or at least a portion of the verification image) in the area where CAPTCHA recognition control 330 is located.
  • Terminal device 110 may also, in response to acquiring the verification image, identify the target CAPTCHA from the verification image based on an image recognition mode. For example, terminal device 110 may identify text content from the verification image based on an image recognition algorithm, and then identify the target CAPTCHA from the text content.
  • the terminal device 110 may identify the target verification code from the verification information based on preset rules. For example, the terminal device 110 may identify the target verification code from the verification information based on regular expression methods or keyword recognition methods.
  • the terminal device 110 can display the recognized target verification code in the first input box. This allows the user to intuitively observe that the verification code has been successfully obtained, providing a clear experience of the automatic verification code recognition process and improving user experience.
  • the target verification code can include various forms, such as numbers, text, punctuation marks, and mathematical characters.
  • the terminal device 110 may, in response to recognizing the target verification code 311 from the verification text in the second input box 321, sequentially display the six verification symbols of the target verification code 311 in the six boxes of the first input box 310.
  • the terminal device 110 may respond to recognizing the target verification code 311 from the verification image, and may also present the six verification symbols of the target verification code 311 in sequence in the six boxes of the first input box 311.
  • the terminal device 110 may also trigger a verification operation on the target verification code in response to the first input box receiving a target verification code that meets the target conditions. This simplifies the verification process and improves the user experience.
  • the target verification code that meets the target conditions may include a verification code that meets the target number of characters or a verification code that meets the target format.
  • terminal device 110 may display the target verification code 311 in the first input box 310 in response to recognizing the target verification code 311 from the verification text 323 in the second input box 321.
  • Terminal device 110 may also trigger a verification operation for the target verification code 311 in response to obtaining the target verification code 311 that meets the target conditions from the first input box 310.
  • Terminal device 110 may also display a verification waiting indicator 340 on the verification page, so that the user knows that terminal device 110 is performing a verification operation for the target verification code 311, thus preventing the verification operation of the target verification code 311 from being interrupted due to accidental operation.
  • the verification page may also have a verification code confirmation control.
  • the terminal device 110 can obtain the target verification code that meets the target conditions in the first input box and trigger the verification operation of the target verification code when it receives the trigger operation of the verification code confirmation control.
  • the problems of easy errors and cumbersome operation associated with manually entering verification codes are solved in scenarios requiring user input.
  • This solution presents a verification page including a first input box and a verification code recognition control.
  • the user can trigger the verification recognition control to identify the target verification code from the verification information and display it in the first input box. This eliminates the need for manual input of the verification code, reduces the difficulty of user operation, and avoids verification code input errors.
  • the verification operation for the target verification code in response to the input of the target verification code into the first input box, the verification operation for the target verification code can be automatically triggered, further simplifying the user operation.
  • the verification information includes a verification link, which contains a target verification code.
  • Terminal device 110 in response to receiving a trigger operation for the verification link, identifies the target verification code from the verification link and triggers a verification operation for the target verification code.
  • the verification link can include various links capable of carrying verification codes (e.g., URL links, webpage links, etc.).
  • the target verification code can include various forms of verification codes; for example, it can include at least one of numbers, text, punctuation marks, and mathematical characters.
  • the target verification code can be encoded in the target link using various protocols conforming to the verification link. For example, the target verification code can be part of a URL link or added to the header information of an HTTP request.
  • Example 400A illustrates an example of a verification information display page.
  • Example 400A includes verification information 401, which contains a verification link 402, and the verification link 402 contains a target verification code 403.
  • Terminal device 110 can, in response to receiving a click operation on verification link 402, determine that a trigger operation has been received on verification link 402, identify the target verification code 403 from verification link 402, and trigger a verification operation for the target verification code 403.
  • terminal device 110 may present a verification page in response to receiving a trigger operation for a verification link.
  • This verification page includes at least a first input field.
  • Terminal device 110 may identify a target verification code from the verification link and present the target verification code in the first input field.
  • Terminal device 110 may also trigger a verification operation for the target verification code in response to obtaining a target verification code that meets the target conditions from the first input field. This allows users to intuitively experience the verification code recognition and input process, thus improving the user experience.
  • Example 400B illustrates an example of a verification page.
  • Example 400B includes a first input box 410 for entering a verification code, which may include six boxes.
  • Terminal device 110 may, in response to recognizing a target verification code 403 from verification link 402, sequentially present the six verification characters of the target verification code 403 in the six boxes.
  • Terminal device 110 may, in response to the target verification code 403 meeting the target conditions, trigger a verification operation for the target verification code 403 and present a verification waiting indicator 440 on the verification page.
  • the verification page may also include a verification code recognition control 420 and a verification code recognition control 430 for obtaining verification information and recognizing the target verification code from the verification information.
  • the terminal device 110 may present not only a verification page, but also a verification waiting page, or a verification passed page or a verification failed page.
  • example 400C illustrates an example of a verification waiting page, which may include a verification waiting identifier 450.
  • FIG. 5 shows a schematic structural block diagram of an apparatus 500 for CAPTCHA processing according to certain embodiments of this disclosure.
  • the apparatus 500 may be implemented as or included in the terminal device 110.
  • the various modules/components in the apparatus 500 may be implemented by hardware, software, firmware, or any combination thereof.
  • the device 500 includes a verification page presentation module 510, an acquisition module 520, an identification module 530, and a verification code presentation module 540.
  • the verification page presentation module 510 is configured to present a verification page in response to receiving a verification request for a verification code.
  • the verification page includes a first input box for entering a verification code and at least one verification code identification control.
  • the acquisition module 520 is configured to acquire verification information containing the verification code through the triggered verification code identification control in response to receiving a trigger operation from the verification code identification control at least one of the verification code identification controls.
  • the identification module 530 is configured to identify the target verification code from the verification information.
  • the verification code presentation module 540 is configured to present the identified target verification code in the first input box.
  • At least one verification recognition control includes multiple verification recognition controls.
  • the acquisition module 520 is further configured to acquire verification information of the corresponding type through the triggered verification code recognition control.
  • the recognition module 530 is further configured to recognize the target verification code from the verification information of the corresponding type based on the recognition mode corresponding to the triggered verification code recognition control.
  • At least one CAPTCHA recognition control includes a first CAPTCHA recognition control.
  • the acquisition module 520 is further configured to: in response to receiving a trigger operation from the first CAPTCHA recognition control, acquire verification text containing the CAPTCHA through the first CAPTCHA recognition control.
  • the first verification code recognition control includes a paste recognition control and a second input box.
  • the acquisition module 520 is further configured to: in response to receiving a trigger operation of the paste recognition control, present the verification text in the second input box.
  • At least one CAPTCHA recognition control includes a second CAPTCHA recognition control.
  • the acquisition module 520 is further configured to: in response to receiving a trigger operation from the second CAPTCHA recognition control, acquire a verification image containing a CAPTCHA through the second CAPTCHA recognition control.
  • the acquisition module 520 is further configured to: in response to receiving a trigger operation from a second verification code recognition control, present at least one image acquisition control on the verification page; and in response to receiving a trigger operation from an image acquisition control among the at least one image acquisition controls, acquire a verification image based on the image acquisition mode corresponding to the triggered image acquisition control.
  • the device 500 further includes a triggering module configured to trigger a verification operation on the target verification code in response to the first input box obtaining a target verification code that meets the target conditions.
  • the verification information includes a verification link containing a target verification code; the apparatus 500 further includes: a link response module configured to, in response to receiving a trigger operation for the verification link, identify the target verification code from the verification link; and trigger a verification operation for the target verification code.
  • the link response module is further configured to: in response to receiving a trigger operation for a verification link, present a verification page, the verification page including at least a first input box; identify a target verification code from the verification link; and present the target verification code in the first input box.
  • the units and/or modules included in device 500 can be implemented in various ways, including software, hardware, firmware, or any combination thereof.
  • one or more units and/or modules can be implemented using software and/or firmware, such as machine-executable instructions stored on a storage medium.
  • some or all of the units and/or modules in device 500 can be implemented at least partially by one or more hardware logic components.
  • exemplary types of hardware logic components include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-chips (SoCs), complex programmable logic devices (CPLDs), and so on.
  • Such electronic devices or combinations of electronic devices may, for example, include the terminal device 110 in FIG1.
  • Figure 6 shows a block diagram of an electronic device 600 in which one or more embodiments of the present disclosure may be implemented. It should be understood that the electronic device 600 shown in Figure 6 is merely exemplary and should not constitute any limitation on the functionality and scope of the embodiments described herein. The electronic device 600 shown in Figure 6 can be used to implement the terminal device 110 of Figure 1 or the apparatus 500 of Figure 5.
  • the electronic device 600 is in the form of a general-purpose electronic device.
  • Components of the electronic device 600 may include, but are not limited to, one or more processors or processing units 610, memory 620, storage devices 630, one or more communication units 640, one or more input devices 650, and one or more output devices 660.
  • the processor 610 may be a physical or virtual processor and is capable of performing various processes according to programs stored in memory 620. In a multiprocessor system, multiple processors execute computer-executable instructions in parallel to improve the parallel processing capability of the electronic device 600.
  • Electronic device 600 typically includes multiple computer storage media. Such media can be any available media accessible to electronic device 600, including but not limited to volatile and non-volatile media, removable and non-removable media.
  • Memory 620 can be volatile memory (e.g., registers, cache, random access memory (RAM)), non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof.
  • Storage device 630 can be removable or non-removable media and can include machine-readable media, such as flash drives, disks, or any other media capable of storing information and/or data and accessible within electronic device 600.
  • Electronic device 600 may further include additional removable/non-removable, volatile/non-volatile storage media.
  • disk drives for reading from or writing to removable, non-volatile disks (e.g., "floppy disks") and optical disk drives for reading from or writing to removable, non-volatile optical disks may be provided.
  • each drive may be connected to a bus (not shown) via one or more data media interfaces.
  • Memory 620 may include computer program product 625 having one or more program modules configured to perform various methods or actions of various embodiments of the present disclosure.
  • the communication unit 640 enables communication with other electronic devices via a communication medium. Additionally, the functionality of the components of the electronic device 600 can be implemented using a single computing cluster or multiple computing machines capable of communicating via communication connections. Therefore, the electronic device 600 can operate in a networked environment using logical connections to one or more other servers, network personal computers (PCs), or another network node.
  • PCs network personal computers
  • Input device 650 can be one or more input devices, such as a mouse, keyboard, trackball, etc.
  • Output device 660 can be one or more output devices, such as a monitor, speaker, printer, etc.
  • Electronic device 600 can also communicate with one or more external devices (not shown) via communication unit 640 as needed. These external devices include storage devices, display devices, etc., and can communicate with one or more devices that enable user interaction with electronic device 600, or with any device that enables electronic device 600 to communicate with one or more other electronic devices (e.g., network card, modem, etc.). Such communication can be performed via input/output (I/O) interface (not shown).
  • I/O input/output
  • a computer-readable storage medium that stores computer-executable instructions thereon, wherein the computer-executable instructions are executed by a processor to implement the methods described above.
  • a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, which are executed by a processor to implement the methods described above.
  • These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions/actions specified in one or more blocks of the flowchart and/or block diagram.
  • These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and/or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions/actions specified in one or more blocks of the flowchart and/or block diagram.
  • Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions that execute on the computer, other programmable data processing apparatus, or other device to perform the functions/actions specified in one or more boxes of a flowchart and/or block diagram.
  • each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing the specified logical function.
  • the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved.
  • each block in the block diagrams and/or flowcharts, and combinations of blocks in the block diagrams and/or flowcharts may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Human Computer Interaction (AREA)
  • Computer Hardware Design (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

根据本公开的实施例，提供了用于验证码处理的方法、装置、设备和存储介质。该方法包括：响应于接收到针对验证码的验证请求，呈现验证页面，验证页面包括用于输入验证码的第一输入框和至少一个验证码识别控件；响应于接收到至少一个验证码识别控件中的验证码识别控件的触发操作，通过所触发的验证码识别控件获取包含验证码的验证信息；从验证信息中识别目标验证码；以及将所识别的目标验证码呈现在第一输入框中。

Description

用于验证码处理的方法、装置、设备和存储介质
本申请要求2024年6月5日递交的、标题为“用于验证码处理的方法、装置、设备和存储介质”、申请号为202410726193.2的中国发明专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本公开的示例实施例总体涉及计算机领域，特别地涉及用于验证码处理的方法、装置、设备和计算机可读存储介质。
背景技术
随着计算机及互联网技术的发展，验证码的应用也越来越普遍。例如，利用验证码进行鉴权，利用验证码防止误操作，利用验证码防止批量化处理，利用验证码防止暴力破解等等。
常规技术中，通常通过短信息、邮件或通知信息等方式向终端设备发送验证码。用户通常需要记录验证码，然后将验证码手动输入验证码，很容易出现验证码输入错误。
发明内容
在本公开的第一方面，提供了一种用于验证码处理的方法。该方法包括：响应于接收到针对验证码的验证请求，呈现验证页面，所述验证页面包括用于输入验证码的第一输入框和至少一个验证码识别控件；响应于接收到所述至少一个验证码识别控件中的验证码识别控件的触发操作，通过所触发的验证码识别控件获取包含验证码的验证信息；从所述验证信息中识别目标验证码；以及将所识别的所述目标验证码呈现在所述第一输入框中。
在本公开的第二方面，提供了一种用于验证码处理的装置。该装置包括：验证页面呈现模块，被配置为响应于接收到针对验证码的验证请求，呈现验证页面，所述验证页面包括用于输入验证码的第一输入框和至少一个验证码识别控件；获取模块，被配置为响应于接收到所述至少一个验证码识别控件中的验证码识别控件的触发操作，通过所触发的验证码识别控件获取包含验证码的验证信息；识别模块，被配置为从所述验证信息中识别目标验证码；以及验证码呈现模块，被配置为将所识别的所述目标验证码呈现在所述第一输入框中。
在本公开的第三方面，提供了一种电子设备。该设备包括至少一个处理器；以及至少一个存储器，至少一个存储器被耦合到至少一个处理器并且存储用于由至少一个处理器执行的指令。指令在由至少一个处理器执行时使电子设备执行第一方面的方法。
在本公开的第四方面，提供了一种计算机可读存储介质。介质上存储有计算机可执行指令，计算机可执行指令被处理器执行时实现第一方面的方法。
在本公开的第五方面，提供了一种计算机程序产品，包括计算机可执行指令，其中计算机可执行指令被处理器执行时实现根据本公开的第一方面的方法。
应当理解，该部分中所描述的内容并非旨在限定本公开的实施例的关键特征或重要特征，也不用于限制本公开的范围。本公开的其他特征将通过以下的描述而变得容易理解。
附图说明
结合附图并参考以下详细说明，本公开各实施例的上述和其他特征、优点及方面将变得更加明显。在附图中，相同或相似的附图标记表示相同或相似的元素，其中：
图1示出了能够在其中实现本公开的实施例的示例环境的示意图；
图2示出了根据本公开的一些实施例的用于验证码处理的过程的流程图；
图3A至图3F示出了根据本公开的一些实施例的示例页面的示意图；
图4A至图4C示出了根据本公开的另一些实施例的示例页面的示意图；
图5示出了根据本公开的一些实施例的用于验证码处理的装置的示意性结构框图；以及
图6示出了可以实现本公开的一个或多个实施例的电子设备的框图。
具体实施方式
下面将参照附图更详细地描述本公开的实施例。虽然附图中示出了本公开的某些实施例，然而应当理解的是，本公开可以通过各种形式来实现，而且不应该被解释为限于这里阐述的实施例，相反，提供这些实施例是为了更加透彻和完整地理解本公开。应当理解的是，本公开的附图及实施例仅用于示例性作用，并非用于限制本公开的保护范围。
在本公开的实施例的描述中，术语“包括”及其类似用语应当理解为开放性包含，即“包括但不限于”。术语“基于”应当理解为“至少部分地基于”。术语“一个实施例”或“该实施例”应当理解为“至少一个实施例”。术语“一些实施例”应当理解为“至少一些实施例”。下文还可能包括其他明确的和隐含的定义。
在本文中，除非明确说明，“响应于A”执行一个步骤并不意味着在“A”之后立即执行该步骤，而是可以包括一个或多个中间步骤。
可以理解的是，本技术方案所涉及的数据(包括但不限于数据本身、数据的获得、使用、存储或删除)应当遵循相应法律法规及相关规定的要求。
可以理解的是，在使用本公开各实施例公开的技术方案之前，均应当根据相关法律法规通过适当的方式对本公开所涉及信息的类型、使用范围、使用场景等告知相关用户并获得相关用户的授权，其中，相关用户可以包括任何类型的权利主体，例如个人、企业、团体。
例如，在响应于接收到用户的主动请求时，向相关用户发送提示信息，以明确地提示相关用户，其请求执行的操作将需要获得和使用到相关用户的信息，从而使得相关用户可以根据提示信息来自主地选择是否向执行本公开技术方案的操作的电子设备、应用程序、服务器或存储介质等软件或硬件提供信息。
作为一种可选的但非限制性的实现方式，响应于接收到相关用户的主动请求，向相关用户发送提示信息的方式，例如可以是弹窗的方式，弹窗中可以以文字的方式呈现提示信息。此外，弹窗中还可以承载供用户选择“同意”或“不同意”向电子设备提供信息的选择控件。
可以理解的是，上述通知和获得用户授权过程仅是示意性的，不对本公开的实现方式构成限定，其他满足相关法律法规的方式也可应用于本公开的实现方式中。
图1示出了本公开的实施例能够在其中实现的示例环境100的示意图。在该示例环境100中，终端设备110中安装有应用120。用户140可以经由终端设备110和/或终端设备110的附接设备来与应用120进行交互。
在本公开的实施例中，应用120可以是任意适当的、与验证码的验证操作相关联的应用。例如，应用120可为进行用户登录的应用，或用户140浏览或操作的应用。在图1环境中，如果应用120处于活动状态，终端设备110可以呈现应用120的页面150。页面150可以包括应用120所能够提供的各类页面，诸如对验证码进行验证的页面、呈现验证码的页面等等。
在一些实施例中，终端设备110与服务器130通信，以实现对应用120的服务的供应。终端设备110可以是任意类型的移动终端、固定终端或便携式终端，包括移动手机、台式计算机、膝上型计算机、笔记本计算机、上网本计算机、平板计算机、媒体计算机、多媒体平板、个人通信系统(PCS)设备、个人导航设备、个人数字助理(PDA)、音频/视频播放器、数码相机/摄像机、定位设备、电视接收器、无线电广播接收器、电子书设备、游戏设备或者前述各项的任意组合，包括这些设备的配件和外设或者其任意组合。在一些实施例中，终端设备110也能够支持任意类型的针对用户的接口(诸如“可佩戴”电路等)。服务器130可以是能够提供计算能力的各种类型的计算系统/服务器，包括但不限于大型机、边缘计算节点、云环境中的计算设备，等等。
应当理解，仅出于示例性的目的描述环境100中各个元素的结构和功能，而不暗示对于本公开的范围的任何限制。
常规情况下，在很多场景下需要进行验证码的验证操作。例如，用户登录时，可通过验证码进行鉴权，鉴权通过后呈现包含用户的个人信息的页面。还例如，可利用验证码防止误操作，或者可利用验证码防止批量化处理，亦或者可利用验证码防止暴力破解等等。
传统上，在需要进行验证码的验证操作时，通过短信息、邮件或通知信息等方式向终端设备发送验证码。用户通常需要记录验证码，然后将验证码手动输入验证码，不仅操作繁琐，而且很容易出现验证码输入错误。例如，在通过短信息发送验证码，且需要将验证码输入到应用的页面的情况下，用户需要切换到呈现短信息的页面查看验证码，之后需要切换至应用的页面进行验证码的输入。如果验证码输入错误，或者用户未能记忆完整的验证码，还需要反复的进行页面切换。这不仅会影响验证码的验证操作的效率，而且会影响用户对应用的使用体验。
根据本公开的实施例，提供了一种用于验证码处理的改进方案。根据本公开实施例的方案，响应于接收到针对验证码的验证请求，呈现验证页面，验证页面包括用于输入验证码的第一输入框和至少一个验证码识别控件；响应于接收到至少一个验证码识别控件中的验证码识别控件的触发操作，通过所触发的验证码识别控件获取包含验证码的验证信息；从验证信息中识别目标验证码；以及将所识别的目标验证码呈现在第一输入框中。
以此方式，在输入验证码的场景下，解决了用户手动输入验证码容易出错且操作繁琐的问题。通过该方案能够呈现包括第一输入框和验证码识别控件的验证页面，用户可触发任意一个验证识别控件，通过验证识别控件从验证信息中识别目标验证码，并将目标验证码呈现在第一输入框中。这省却了用户手动输入验证码的过程，能够降低用户操作难度，且能够避免验证码输入错误。
以下将继续参考附图描述本公开的一些示例实施例。图2示例了根据本公开的一些实施例的用于验证码处理的过程200的流程图。在描述过程200时，将结合图3A至图4C所示的示例来帮助理解。图3A至图4C示出了根据本公开的一些实施例的示例页面300A至400C(也可简称为示例300A至示例400C)的示意图。应当理解，附图中示出的页面仅仅是示例，实际可以存在各种页面设计。页面中的各个图形元素可以具有不同的布置和不同的视觉表示，其中的一个或多个元素可以省略或被替换，并且还可以存在一个或多个其他元素。本公开的实施例在此方面不受限制。
示例300A至示例400C所示的页面可以被呈现在终端设备110处，也可被呈现在终端设备120出。为便于讨论，将参考图1的环境100来描述过程200，并结合示例300A至示例400C对过程200进行解释说明。需要说明的是，前述终端设备110所执行的操作以及后续表述的终端设备110所执行的操作，具体可以是安装在终端设备110上的相关应用程序(例如应用120)执行的。在一些实施例中，在电子设备上执行的操作可以在服务器130的协助下完成。
在过程200中的框210，终端设备110可响应于接收到针对验证码的验证请求，呈现验证页面。这个验证页面例如可包括用于输入验证码的第一输入框和至少一个验证码识别控件。
关于针对验证码的验证请求的接收过程，可以根据验证码的应用场景不同而不同。示例性地，如图3A所示，示例300A示出了用户登录页面的一个示例。示例300A中包括账户输入框301和账户确认控件302。终端设备110可响应于用户140经由输入设备(例如键盘、触控屏、手写板等等)的输入操作，在账户输入框301中呈现登录账户。终端设备可响应于账户确认控件302的触发操作，向服务器130发送登录请求。服务器130可响应于登录请求，向终端设备110发送针对验证码的验证请求。服务器130还可基于登录账户，向终端设备110或其他终端设备发送包含验证码的验证信息。终端设备110可响应于验证请求，呈现验证页面。
示例性的，终端设备110可响应于用户140的操作，显示应用120的一个特定操作页面(例如购物页面、转账页面、充值页面等等)。为了防止用户误触在该特定操作页面触发特定操作(例如购物、转账、充值等等)，终端设备110可响应于针对该特定操作页面触发特定操作，获取针对验证码的验证请求，呈现验证页面。
可以理解的是，验证码可以应用于多种场景，不仅限于上述两种场景。在验证码应用于不同场景时，针对验证码的验证请求的接收过程可能并不相同，此处不在一一赘述。
关于验证页面的页面设计，第一输入框可以是任意适当的输入框。可选地，第一输入框可以是一个矩形输入框，该矩形输入框内可输入多位验证码。可选地，该第一输入框可包括与验证码的位数相同数量的多个方框，该多个方框可规则排布在验证页面。示例性地，如图3B所示，示例300B示出了验证页面的一个示例。示例300B中包括用于输入验证码的第一输入框310。第一输入框310包括六个方框，每个方框可填入一位验证符号，六个方框共计可填入六位验证符号，这六位验证符号共同组成了验证码。这里的验证码识别控件可以是任意适当的控件，包括但不限于输入框、选项、操作控件等。
在过程200的框220中，终端设备110响应于接收到至少一个验证码识别控件中的验证码识别控件的触发操作，通过所触发的验证码识别控件获取包含验证码的验证信息。这里的验证信息可包括多种数据类型的验证信息(例如，文本、图片、音频等等)。
在一些实施例中，验证页面可包括一个验证码识别控件。终端设备110可响应于对该验证码识别控件的触发操作，呈现验证信息选取页面。验证信息选取页面也可包括与不同数据类型的验证信息一一对应的多个数据类型选取控件。终端设备110可响应于对多个数据类型选取控件中任意一个的触发操作，通过所触发的数据类型选取控件获取相应类型的验证信息。
在一些实施例中，验证页面可包括多个验证码识别控件，多个验证码识别控件可用于获取不同数据类型的验证信息。终端设备110可响应于对多个验证码识别控件中任意一个的触发操作，通过所触发的验证码识别控件，获取相应类型的验证信息。如此，用户140可根据验证信息的数据类型，在验证页面直接触发对应的验证码识别控制。
在一些实施例中，至少一个验证码识别控件可包括第一验证码识别控件，终端设备110可响应于接收到第一验证码识别控件的触发操作，通过第一验证码识别控件获取包含验证码的验证文本。这里的验证文本可以有多重形式，此处并不对验证文本的具体类型进行限定。
示例性的，如图3B所示，示例300B中包括第一验证码识别控件(例如验证码识别控件320)。在终端设备110接收到包含验证文本的验证信息的情况下，终端设备110可响应于用户140操作，接收对验证文本的复制请求，将验证文本添加至系统剪切板。之后，用户140可经由终端设备110或终端设备110的附接设备触发验证码识别控件320。终端设备110可响应于验证码识别控件320的触发操作，利用验证码识别控件320获取位于系统剪切板中的验证文本。
示例性的，终端设备110也可响应于接收到第一验证码识别控件的触发操作，在验证页面呈现至少一个文本类型选取控件。终端设备110可响应于针对该至少一个文本类型选取控件中任意一个文本选取控件的选取操作，通过所选取的文本类型选取控件获取对应类型的验证文本。
在一些实施例中，第一验证码识别控件包括粘贴识别控件和第二输入框。终端设备110可响应于接收到粘贴识别控件的触发操作，将验证文本呈现在第二输入框中。这样，能够使用户直观的感受验证文本的粘贴过程，有利于提高用户体验。
示例性的，如图3B所示，验证码识别控件320可包括第二输入框(也即输入框321)和粘贴识别控件(也即控件322)。终端设备110可响应于接收到对验证页面所呈现的控件322的点击操作，确定接收到控件322的触发操作。终端设备110可响应于控件322的触发操作，从系统剪切板获取验证文本323，将验证文本323呈现在输入321中，如图3C所示。
可以理解的是，第一验证码识别控件也可采用其他设计方案或布局方式。例如，第一验证码识别控件可包括粘贴输入控件，终端设备110可响应于接收到对粘贴输入控件的点击操作，从系统剪切板获取验证文本，将至少部分验证文本呈现在粘贴输入控件的区域中。
在一些实施例中，至少一个验证码识别控件包括第二验证码识别控件。终端设备110可响应于接收到第二验证码识别控件的触发操作，通过第二验证码识别控件获取包含验证码的验证图像。这里的验证图像可包括多种类型的图像，只要包含验证码即可，此处并不对验证图像的类型进行限定。
示例性的，如图3B所示，示例300B中包括第二验证码识别控件(例如验证码识别控件330)。终端设备110可从服务器130或其他电子设备接收包含验证码的验证图像。终端设备110也可从服务器130或其他电子设备接收包含验证码的验证文本，终端设备110可响应于对呈现验证文本的页面的拍照或截屏操作，获取包含验证码的验证图像。终端设备110可响应于验证识别控件330的触发操作，利用验证识别控件330获取验证图像。
在一些实施例中，终端设备110可响应于接收到第二验证码识别控件的触发操作，在验证页面呈现至少一个图像获取控件。终端设备110可响应于接收到针对该至少一个图像获取控件中任意一个图像获取控件的触发操作，基于所触发的图像获取控件对应的图像获取模式获取验证图像。如此，能够为用户提供多种可选择的图像获取方式，有利于提高用户体验。
示例性的，如图3B和图3D所示，终端设备110可响应于对示例300B中验证码识别控件330的点击操作，在验证页面呈现图像获取控件331、图像获取控件332和图像获取控件333。图像获取控件331用于触发相机，通过相机拍照来获取验证图像。图像获取控件332用于切换至相册页面，从相册中选取验证图像。图像获取控件333用于切换至应用界面，从应用界面中获取验证图像。
在一些应用场景下，服务器130可将验证信息发送至其他终端设备。终端设备110可响应于对图像获取控件331的触发操作，启动相机，通过相机拍摄其他终端设备对验证信息的显示页面，获取包含验证码的照片。
在另一些应用场景下，如果终端设备110已经将包含验证码的验证图像保存在相册，用户140可点击图像获取控件332。终端设备110可响应于接收到图像获取控件332的点击操作，切换至相册页面。在相册页面用户140可点击包含验证码的验证图像，终端设备110可响应于接收到对任意一个验证图像的选取操作，获取对应的验证图像。
在有一个应用场景下，终端设备110可通过应用程序从服务器130或其他电子设备接收验证图像。用户可点击图像获取控件333，终端设备110可响应于接收到图像获取控件333的点击操作，切换至应用选取界面，应用选取界面可包括至少一个应用图标。终端设备110可响应于对应用选取界面中任意一个应用图标的选取操作，呈现对应的应用界面。终端设备110可响应于对应用界面中任意一个图像的选取操作，获取该图像作为验证图像。
在过程200中的框230中，终端设备110可从验证信息中识别目标验证码。在一些实施例中，如果验证页面呈现多个验证码识别控件，终端设备110可基于所触发的验证码识别控件对应的识别模式，从该相应类型的验证信息中识别目标验证码。
示例性的，如图3C所示，终端设备110可响应于接收到对粘贴识别控件322的触发操作，将验证文本323呈现的第二输入框321中。终端设备110可响应于验证文本323呈现在第二输入框321中，基于文本识别模式，从第二输入框321中的验证文本323中识别目标验证码。
示例性的，如图3E所示，终端设备110可响应于接收到对验证码识别控件330的触发操作，通过验证码识别控件330获取验证图像。终端设备110可响应于获取到验证图像，在验证码识别控件330所在区域显示验证图像的图像标识334(例如验证图像的图像名称或至少部分验证图像)。终端设备110还可响应于获取到验证图像，基于图像识别模式，从验证图像中识别目标验证码。例如，终端设备110可基于图像识别算法从验证图像中识别文本内容，之后从文本内容中识别目标验证码。
在一些实施例中，终端设备110可基于预设规则从验证信息中识别目标验证码。例如，终端设备110可基于正则表达式方法或关键词识别方法从验证信息中识别目标验证码。
在过程200的框240中，终端设备110可将所识别的目标验证码呈现在第一输入框中。如此，用户可以直观的观察到验证码已经获取成功，使得用户能够直观的体验到验证码自动识别的识别过程，有利于提高用户体验。这里的目标验证码可包括各种形式的验证码，例如，目标验证码可包括数字、文字、标点符号、数学字符中的至少一种。
示例性的，如图3C所示，终端设备110可响应于从第二输入框321中的验证文本识别到目标验证码311，可将目标验证码311的六个验证符号依次呈现在第一输入框310的六个方框中。
示例性的，如图3E所示，终端设备110可响应于从验证图像中识别到目标验证码311，也可将目标验证码311的六个验证符号依次呈现在第一输入框311的六个方框中。
在一些实施例中，终端设备110还可响应于第一输入框获取到符合目标条件的目标验证码，触发针对目标验证码的验证操作。如此，有利于简化验证码的验证过程，进而有利于提高用户体验。这里的符合目标条件的目标验证码可以包括符合目标位数的验证码，也可包括符合目标格式的验证码。
示例性的，如图3C和图3F所示，终端设备110可响应于从第二输入框321内的验证文本323中识别到目标验证码311，将目标验证码311呈现在第一输入框310。终端设备110可响应于第一输入框310获取到符合目标条件的目标验证码311，触发针对目标验证码311的验证操作。终端设备110还可在验证页面呈现验证等待标识340，使得用户知晓终端设备110正在执行目标验证码311的验证操作，避免因误操作导致目标验证码311的验证操作被中断。
可以理解的是，验证页面也可设置有验证码确认控件，终端设备110可在第一输入框获取到符合目标条件的目标验证码，且接收到验证码确认控件的触发操作的情况下，触发对目标验证码的验证操作。
综上所述，根据本公开的实施例，在输入验证码的场景下，解决了用户手动输入验证码容易出错且操作繁琐的问题。通过该方案能够呈现包括第一输入框和验证码识别控件的验证页面，用户可触发验证识别控件，通过验证识别控件从验证信息中识别目标验证码，并将目标验证码呈现在第一输入框中。这省却了用户手动输入验证码的过程，能够降低用户操作难度，且能够避免验证码输入错误。此外，在一些实施例中，还可响应于目标验证码输入第一输入框中，自动触发对目标验证码的验证操作，进一步简化用户操作。
在本公开的实施例中，验证信息包括验证链接，验证链接中包含目标验证码。终端设备110可响应于接收到针对验证链接的触发操作，从验证链接中识别目标验证码，触发针对目标验证码的验证操作。这样，在对验证码进行验证的场景下，也能够解决用户手动输入验证码容易出错且操作繁琐的问题。这里的验证链接可包括各种能够携带验证码的链接(例如URL链接、网页链接等等)。这里的目标验证码可包括各种形式的验证码，例如，目标验证码可包括数字、文字、标点符号、数学字符中的至少一种。这里的目标验证码可采用各种符合验证链接的协议的方式编码在目标链接中。例如，可将目标验证码作为URL链接的一部分，或者可将目标验证码添加到HTTP请求的头信息中。
示例性的，如图4A所示，示例400A示出了验证信息的显示页面的一个示例。示例400A中包括验证信息401，验证信息401中包含验证链接402，验证链接402中包含目标验证码403。终端设备110可响应于接收到对验证链接402的点击操作，确定接收到对验证链接402的触发操作，从验证链接402中识别目标验证码403，触发针对目标验证码403的验证操作。
在一些实施例中，终端设备110可响应于接收到针对验证链接的触发操作，呈现验证页面。这里的验证页面至少包括第一输入框。终端设备110可从验证链接中识别目标验证码，将目标验证码呈现在第一输入框中。终端设备110还可响应于第一输入框获取到符合目标条件的目标验证码，触发针对目标验证码的验证操作。如此，能够使用户直观的体会到验证码的识别和输入过程，有利于提高用户体验。
示例性的，如图4B所示，示例400B示出了验证页面的一个示例。示例400B中包括用于输入验证码的第一输入框410，第一输入框可包括六个方框。终端设备110可响应于从验证链接402中识别到目标验证码403，将目标验证码403的六个验证字符依次呈现在六个方框中。终端设备110可响应于目标验证码403符合目标条件，触发对目标验证码403的验证操作，并且在验证页面呈现验证等待标识440。可选地，该验证页面还可包括用于获取验证信息并从验证信息中识别目标验证码的验证码识别控件420和验证码识别控件430。
需要说明的是，终端设备110响应于接收到针对验证链接的触发操作，不仅限于呈现验证页面，也可呈现验证等待页面，或者也呈现验证通过页面或验证失败页面。示例性的，如图4C所示，示例400C示出了验证等待页面的一个示例，示例400C可包括验证等待标识450。
本公开的实施例还提供了用于实现上述方法或过程的相应装置。图5示出了根据本公开的某些实施例的用于验证码处理的装置500的示意性结构框图。装置500可以被实现为或者被包括在终端设备110中。装置500中的各个模块/组件可以由硬件、软件、固件或者它们的任意组合来实现。
如图5所示，装置500包括验证页面呈现模块510、获取模块520、识别模块530和验证码呈现模块540。验证页面呈现模块510，被配置为响应于接收到针对验证码的验证请求，呈现验证页面，验证页面包括用于输入验证码的第一输入框和至少一个验证码识别控件。获取模块520，被配置为响应于接收到至少一个验证码识别控件中的验证码识别控件的触发操作，通过所触发的验证码识别控件获取包含验证码的验证信息。识别模块530，被配置为从验证信息中识别目标验证码。验证码呈现模块540，被配置为将所识别的目标验证码呈现在第一输入框中。
在一些实施例中，至少一个验证识别控件包括多个验证识别控件。获取模块520被进一步配置为：通过所触发的验证码识别控件，获取相应类型的验证信息。识别模块530被进一步配置为：基于所触发的验证码识别控件对应的识别模式，从该相应类型的验证信息中识别目标验证码。
在一些实施例中，至少一个验证码识别控件包括第一验证码识别控件。获取模块520被进一步配置为：响应于接收到第一验证码识别控件的触发操作，通过第一验证码识别控件获取包含验证码的验证文本。
在一些实施例中，第一验证码识别控件包括粘贴识别控件和第二输入框。获取模块520被进一步配置为：响应于接收到粘贴识别控件的触发操作，将验证文本呈现在第二输入框中。
在一些实施例中，至少一个验证码识别控件包括第二验证码识别控件。获取模块520被进一步配置为：响应于接收到第二验证码识别控件的触发操作，通过第二验证码识别控件获取包含验证码的验证图像。
在一些实施例中，获取模块520被进一步配置为：响应于接收到第二验证码识别控件的触发操作，在验证页面呈现至少一个图像获取控件；响应于接收到针对该至少一个图像获取控件中的图像获取控件的触发操作，基于所触发的图像获取控件对应的图像获取模式获取验证图像。
在一些实施例中，装置500还包括：触发模块，被配置为响应于第一输入框获取到符合目标条件的目标验证码，触发针对目标验证码的验证操作。
在一些实施例中，验证信息包括验证链接，验证链接中包含目标验证码；装置500还包括：链接响应模块，被配置为响应于接收到针对验证链接的触发操作，从验证链接中识别目标验证码；触发针对目标验证码的验证操作。
在一些实施例中，链接响应模块被进一步配置为：响应于接收到针对验证链接的触发操作，呈现验证页面，验证页面至少包括第一输入框；从验证链接中识别目标验证码；将目标验证码呈现在第一输入框中。
装置500中所包括的单元和/或模块可以利用各种方式来实现，包括软件、硬件、固件或其任意组合。在一些实施例中，一个或多个单元和/或模块可以使用软件和/或固件来实现，例如存储在存储介质上的机器可执行指令。除了机器可执行指令之外或者作为替代，装置500中的部分或者全部单元和/或模块可以至少部分地由一个或多个硬件逻辑组件来实现。作为示例而非限制，可以使用的示范类型的硬件逻辑组件包括现场可编程门阵列(FPGA)、专用集成电路(ASIC)、专用标准品(ASSP)、片上系统(SOC)、复杂可编程逻辑器件(CPLD)，等等。
应当理解，以上方法中的一个或多个步骤可以由适当的电子设备或电子设备的组合来执行。这样的电子设备或电子设备的组合例如可以包括图1中的终端设备110。
图6示出了其中可以实施本公开的一个或多个实施例的电子设备600的框图。应当理解，图6所示出的电子设备600仅仅是示例性的，而不应当构成对本文所描述的实施例的功能和范围的任何限制。图6所示出的电子设备600可以用于实现图1的终端设备110或图5的装置500。
如图6所示，电子设备600是通用电子设备的形式。电子设备600的组件可以包括但不限于一个或多个处理器或处理单元610、存储器620、存储设备630、一个或多个通信单元640、一个或多个输入设备650以及一个或多个输出设备660。处理器610可以是实际或虚拟处理器并且能够根据存储器620中存储的程序来执行各种处理。在多处理器系统中，多个处理器并行执行计算机可执行指令，以提高电子设备600的并行处理能力。
电子设备600通常包括多个计算机存储介质。这样的介质可以是电子设备600可访问的任何可以获得的介质，包括但不限于易失性和非易失性介质、可拆卸和不可拆卸介质。存储器620可以是易失性存储器(例如寄存器、高速缓存、随机访问存储器(RAM))、非易失性存储器(例如，只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、闪存)或它们的某种组合。存储设备630可以是可拆卸或不可拆卸的介质，并且可以包括机器可读介质，诸如闪存驱动、磁盘或者任何其他介质，其可以能够用于存储信息和/或数据并且可以在电子设备600内被访问。
电子设备600可以进一步包括另外的可拆卸/不可拆卸、易失性/非易失性存储介质。尽管未在图6中示出，可以提供用于从可拆卸、非易失性磁盘(例如“软盘”)进行读取或写入的磁盘驱动和用于从可拆卸、非易失性光盘进行读取或写入的光盘驱动。在这些情况中，每个驱动可以由一个或多个数据介质接口被连接至总线(未示出)。存储器620可以包括计算机程序产品625，其具有一个或多个程序模块，这些程序模块被配置为执行本公开的各种实施例的各种方法或动作。
通信单元640实现通过通信介质与其他电子设备进行通信。附加地，电子设备600的组件的功能可以以单个计算集群或多个计算机器来实现，这些计算机器能够通过通信连接进行通信。因此，电子设备600可以使用与一个或多个其他服务器、网络个人计算机(PC)或者另一个网络节点的逻辑连接来在联网环境中进行操作。
输入设备650可以是一个或多个输入设备，例如鼠标、键盘、追踪球等。输出设备660可以是一个或多个输出设备，例如显示器、扬声器、打印机等。电子设备600还可以根据需要通过通信单元640与一个或多个外部设备(未示出)进行通信，外部设备诸如存储设备、显示设备等，与一个或多个使得用户与电子设备600交互的设备进行通信，或者与使得电子设备600与一个或多个其他电子设备通信的任何设备(例如，网卡、调制解调器等)进行通信。这样的通信可以经由输入/输出(I/O)接口(未示出)来执行。
根据本公开的示例性实现方式，提供了一种计算机可读存储介质，其上存储有计算机可执行指令，其中计算机可执行指令被处理器执行以实现上文描述的方法。根据本公开的示例性实现方式，还提供了一种计算机程序产品，计算机程序产品被有形地存储在非瞬态计算机可读介质上并且包括计算机可执行指令，而计算机可执行指令被处理器执行以实现上文描述的方法。
这里参照根据本公开实现的方法、装置、设备和计算机程序产品的流程图和/或框图描述了本公开的各个方面。应当理解，流程图和/或框图的每个方框以及流程图和/或框图中各方框的组合，都可以由计算机可读程序指令实现。
这些计算机可读程序指令可以提供给通用计算机、专用计算机或其他可编程数据处理装置的处理器，从而生产出一种机器，使得这些指令在通过计算机或其他可编程数据处理装置的处理器执行时，产生了实现流程图和/或框图中的一个或多个方框中规定的功能/动作的装置。也可以把这些计算机可读程序指令存储在计算机可读存储介质中，这些指令使得计算机、可编程数据处理装置和/或其他设备以特定方式工作，从而，存储有指令的计算机可读介质则包括一个制造品，其包括实现流程图和/或框图中的一个或多个方框中规定的功能/动作的各个方面的指令。
可以把计算机可读程序指令加载到计算机、其他可编程数据处理装置、或其他设备上，使得在计算机、其他可编程数据处理装置或其他设备上执行一系列操作步骤，以产生计算机实现的过程，从而使得在计算机、其他可编程数据处理装置、或其他设备上执行的指令实现流程图和/或框图中的一个或多个方框中规定的功能/动作。
附图中的流程图和框图显示了根据本公开的多个实现的系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上，流程图或框图中的每个方框可以代表一个模块、程序段或指令的一部分，模块、程序段或指令的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。在有些作为更新的实现中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个连续的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图和/或流程图中的每个方框、以及框图和/或流程图中的方框的组合，可以用执行规定的功能或动作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
以上已经描述了本公开的各实现，上述说明是示例性的，并非穷尽性的，并且也不限于所公开的各实现。在不偏离所说明的各实现的范围和精神的情况下，对于本技术领域的普通技术人员来说许多修改和变更都是显而易见的。本文中所用术语的选择，旨在最好地解释各实现的原理、实际应用或对市场中的技术的改进，或者使本技术领域的其他普通技术人员能理解本文公开的各个实现方式。

Claims (13)

  1. 一种用于验证码处理的方法，包括：
    响应于接收到针对验证码的验证请求，呈现验证页面，所述验证页面包括用于输入验证码的第一输入框和至少一个验证码识别控件；
    响应于接收到所述至少一个验证码识别控件中的验证码识别控件的触发操作，通过所触发的验证码识别控件获取包含验证码的验证信息；
    从所述验证信息中识别目标验证码；以及
    将所识别的所述目标验证码呈现在所述第一输入框中。
  2. 根据权利要求1所述的方法，其中，所述至少一个验证识别控件包括多个验证识别控件；
    其中，通过所触发的验证码识别控件获取包含验证码的验证信息，包括：
    通过所触发的验证码识别控件，获取相应类型的验证信息；
    其中，从所述验证信息中识别目标验证码，包括：
    基于所触发的验证码识别控件对应的识别模式，从该相应类型的验证信息中识别所述目标验证码。
  3. 根据权利要求1所述的方法，其中，所述至少一个验证码识别控件包括第一验证码识别控件；
    响应于接收到所述至少一个验证码识别控件中的验证码识别控件的触发操作，通过所触发的验证码识别控件获取包含验证码的验证信息，包括：
    响应于接收到所述第一验证码识别控件的触发操作，通过所述第一验证码识别控件获取包含验证码的验证文本。
  4. 根据权利要求3所述的方法，其中，所述第一验证码识别控件包括粘贴识别控件和第二输入框；
    响应于接收到所述第一验证码识别控件的触发操作，通过所述第一验证码识别控件获取包含验证码的验证文本，包括：
    响应于接收到所述粘贴识别控件的触发操作，将所述验证文本呈现在所述第二输入框中。
  5. 根据权利要求1所述的方法，其中，所述至少一个验证码识别控件包括第二验证码识别控件；
    响应于接收到所述至少一个验证码识别控件中的验证码识别控件的触发操作，通过所触发的验证码识别控件获取包含验证码的验证信息，包括：
    响应于接收到所述第二验证码识别控件的触发操作，通过所述第二验证码识别控件获取包含验证码的验证图像。
  6. 根据权利要求5所述的方法，其中，响应于接收到所述第二验证码识别控件的触发操作，通过所述第二验证码识别控件获取包含验证码的验证图像，包括：
    响应于接收到所述第二验证码识别控件的触发操作，在所述验证页面呈现至少一个图像获取控件；
    响应于接收到针对该至少一个图像获取控件中的图像获取控件的触发操作，基于所触发的图像获取控件对应的图像获取模式获取所述验证图像。
  7. 根据权利要求1所述的方法，还包括：
    响应于所述第一输入框获取到符合目标条件的所述目标验证码，触发针对所述目标验证码的验证操作。
  8. 根据权利要求1所述的方法，其中，所述验证信息包括验证链接，所述验证链接中包含目标验证码；其中，所述方法还包括：
    响应于接收到针对所述验证链接的触发操作，从所述验证链接中识别所述目标验证码；
    触发针对所述目标验证码的验证操作。
  9. 根据权利要求8所述的方法，其中，响应于接收到针对所述验证链接的触发操作，从所述验证链接中识别所述目标验证码，包括：
    响应于接收到针对所述验证链接的触发操作，呈现验证页面，所述验证页面至少包括第一输入框；
    从所述验证链接中识别所述目标验证码；
    将所述目标验证码呈现在所述第一输入框中。
  10. 一种用于验证码处理的装置，包括：
    验证页面呈现模块，被配置为响应于接收到针对验证码的验证请求，呈现验证页面，所述验证页面包括用于输入验证码的第一输入框和至少一个验证码识别控件；
    获取模块，被配置为响应于接收到所述至少一个验证码识别控件中的验证码识别控件的触发操作，通过所触发的验证码识别控件获取包含验证码的验证信息；
    识别模块，被配置为从所述验证信息中识别目标验证码；以及
    验证码呈现模块，被配置为将所识别的所述目标验证码呈现在所述第一输入框中。
  11. 一种电子设备，包括：
    至少一个处理器；以及
    至少一个存储器，所述至少一个存储器被耦合到所述至少一个处理器并且存储用于由所述至少一个处理器执行的指令，所述指令在由所述至少一个处理器执行时使所述电子设备执行根据权利要求1至9中任一项所述的方法。
  12. 一种计算机可读存储介质，其上存储有计算机可执行指令，所述计算机可执行指令可由处理器执行以实现根据权利要求1至9中任一项所述的方法。
  13. 一种计算机程序产品，包括计算机可执行指令，其中所述计算机可执行指令/被处理器执行时实现根据权利要求1至9中任一项所述的方法。
PCT/CN2025/098663 2024-06-05 2025-05-30 用于验证码处理的方法、装置、设备和存储介质 Pending WO2025252052A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202410726193.2 2024-06-05
CN202410726193.2A CN121070239A (zh) 2024-06-05 2024-06-05 用于验证码处理的方法、装置、设备和存储介质

Publications (1)

Publication Number Publication Date
WO2025252052A1 true WO2025252052A1 (zh) 2025-12-11

Family

ID=97840998

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/098663 Pending WO2025252052A1 (zh) 2024-06-05 2025-05-30 用于验证码处理的方法、装置、设备和存储介质

Country Status (2)

Country Link
CN (1) CN121070239A (zh)
WO (1) WO2025252052A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110532186A (zh) * 2019-08-29 2019-12-03 中国工商银行股份有限公司 利用验证码进行测试的方法、装置、电子设备和存储介质
CN111966432A (zh) * 2020-06-30 2020-11-20 北京百度网讯科技有限公司 验证码处理方法、装置、电子设备以及存储介质
KR20220083988A (ko) * 2021-06-08 2022-06-21 아폴로 인텔리전트 커넥티비티 (베이징) 테크놀로지 씨오., 엘티디. 인증코드의 동기화 방법, 장치, 전자 기기 및 저장 매체
CN115378606A (zh) * 2022-08-16 2022-11-22 中国银行股份有限公司 一种图形验证码的验证方法、装置、设备及存储介质
CN117349806A (zh) * 2022-06-27 2024-01-05 Oppo广东移动通信有限公司 验证码输入方法、装置、终端设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110532186A (zh) * 2019-08-29 2019-12-03 中国工商银行股份有限公司 利用验证码进行测试的方法、装置、电子设备和存储介质
CN111966432A (zh) * 2020-06-30 2020-11-20 北京百度网讯科技有限公司 验证码处理方法、装置、电子设备以及存储介质
KR20220083988A (ko) * 2021-06-08 2022-06-21 아폴로 인텔리전트 커넥티비티 (베이징) 테크놀로지 씨오., 엘티디. 인증코드의 동기화 방법, 장치, 전자 기기 및 저장 매체
CN117349806A (zh) * 2022-06-27 2024-01-05 Oppo广东移动通信有限公司 验证码输入方法、装置、终端设备及存储介质
CN115378606A (zh) * 2022-08-16 2022-11-22 中国银行股份有限公司 一种图形验证码的验证方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN121070239A (zh) 2025-12-05

Similar Documents

Publication Publication Date Title
EP3567476B1 (en) Application data processing method and apparatus, and storage medium
US9329810B2 (en) Secure federation of cloud print services
WO2018108059A1 (zh) 模板数据处理、请求模板数据、模板数据展示的方法和装置
CN111949192A (zh) 密码输入提示方法、装置和电子设备
CN115878195A (zh) 操作系统批量部署方法及装置、计算机设备及存储介质
WO2022156606A1 (zh) 信息处理方法、装置及电子设备
CN107370874B (zh) 应用的启动方法、移动终端及存储介质
CN106330458A (zh) 一种验证码的处理方法及装置
WO2026051427A1 (zh) 用于电子支付的方法、装置、设备和存储介质
WO2026040862A1 (zh) 创建模板的方法、装置、设备和存储介质
WO2025050883A1 (zh) 微端生成方法、装置、计算机设备及存储介质
US20230388266A1 (en) Method, apparatus, device and storage medium for reposting
US20250298573A1 (en) Terminal control method, electronic device, and storage medium
WO2021227922A1 (zh) 通信对象添加方法、装置及电子设备
CN111752398A (zh) 验证码输入方法、装置、电子设备及可读存储介质
WO2026067727A1 (zh) 处理媒体内容的方法、装置、设备、存储介质和程序产品
WO2026046251A1 (zh) 用于信息搜索方法、装置、设备和存储介质
WO2026021383A1 (zh) 密码验证方法、装置、电子设备及可读存储介质
WO2025252052A1 (zh) 用于验证码处理的方法、装置、设备和存储介质
US11893199B2 (en) Systems and methods for viewing incompatible web pages via remote browser instances
WO2026001095A1 (zh) 故事创作方法、装置、设备和存储介质
CN114500426B (zh) 消息提醒方法、装置、计算机设备和存储介质
CN111817944A (zh) 图片分享的方法、装置及电子设备
CN117827068A (zh) 交互控制方法、装置、设备和存储介质
US11467958B2 (en) Cache management method, cache management system, and information processing apparatus

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: 25819167

Country of ref document: EP

Kind code of ref document: A1