CN113115238B

CN113115238B - Short message verification code filling method and electronic equipment

Info

Publication number: CN113115238B
Application number: CN202110406414.4A
Authority: CN
Inventors: 杨畅; 余吉
Original assignee: Beijing Zitiao Network Technology Co Ltd
Current assignee: Beijing Zitiao Network Technology Co Ltd
Priority date: 2021-04-15
Filing date: 2021-04-15
Publication date: 2022-07-19
Anticipated expiration: 2041-04-15
Also published as: CN113115238A

Abstract

The invention relates to a short message verification code filling method and electronic equipment, when a first application provides a page needing to be filled with a short message verification code for a user, the first application can take an input box as a first response object without considering interactive complexity, the user does not need to execute the operation of focusing the input box, after the user inputs the short message verification code into the input box, the short message verification code can be automatically filled into the input box, the operation of filling the short message verification code is simplified, the user is prevented from executing unnecessary operation, and the experience of the user using an application program is improved.

Description

Short message verification code filling method and electronic equipment

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a short message verification code filling method and an electronic device.

Background

In the application process of an Application (APP), a user often encounters a scene that a short message verification code needs to be input, such as a scene that the user logs in the APP, a scene that the user binds a bank card, or a scene that the user transacts in the APP, and the user can complete the short message verification code only by switching between the short message APP and the currently used APP.

The apple company adds the function of security code automatic fill to the operating system of the terminal device, and can realize the automatic fill of the short message verification code. The specific implementation process is as follows: when the input box is the first responder, the electronic equipment deduces the verification code carried in the short message transmitted by the server by using the data detector, and displays the deduced short message verification code in the QuickType Bar of the keyboard application. After a user clicks the short message verification code in the QuickType Bar applied to the keyboard, the short message verification code is automatically filled into the input box, so that the electronic equipment can obtain the short message verification code input by the user.

The short message verification code can be deduced by the functions, operation of developers is not required, the conversion rate of the short message verification code is improved, privacy of users is effectively protected, the APP is not required to be switched back and forth by the users, and experience of the users in using the APP is improved.

However, in a scenario where the service interaction of the APP is complex, the input box often cannot serve as the first responder, and the short message verification code cannot be automatically filled into the input box after the user clicks the short message verification code. At this moment, the user needs to manually execute the operation of focusing the input box and calling up the keyboard, and the input box can be used as a first responder, so that the short message verification code is automatically filled into the input box, the user needs to execute excessive operations, and the experience of the user in using the APP is reduced.

Disclosure of Invention

In order to solve the technical problems or at least partially solve the technical problems, the present disclosure provides a short message verification code filling method and an electronic device.

In a first aspect, the present disclosure provides a method for filling a short message verification code, where the method is applied to an electronic device, and the electronic device includes: a first application and a system component. The method comprises the following steps: the system component receives an operation executed by a user on a first page of the first application and used for acquiring a short message verification code; the system component responds to the operation for acquiring the short message verification code and sends a first notice to the first application, wherein the first notice is used for informing the first application that the short message verification code needs to be acquired; the first application responds to the operation of receiving the short message verification code and sends a first request to the server, wherein the first request is used for requesting to obtain the short message verification code; the system component receives a first response from the server, wherein the first response carries a first verification code; the system component sends a second notification to the first application; the first application focuses on an input frame of the short message verification code through the system component in response to receiving the second notification, obtains the first verification code, starts the keyboard application in the system component, and displays a second page corresponding to the input frame and the keyboard application, wherein the second page carries the first verification code; the system component sends a third notice to the first application after receiving the operation of the second verification code input by the user on the second page; the first application responds to the third notice and acquires a second verification code from the third notice through the system component; the first application displays the second verification code in the input box.

By the method of the first aspect, when the first application provides the page needing to be filled with the short message verification code for the user, the first application can take the input box as the first response object without considering interactive complexity, the user does not need to execute the operation of focusing the input box, and after the user inputs the short message verification code into the input box, the short message verification code can be automatically filled into the input box, so that the operation of filling the short message verification code is simplified, the user is prevented from executing unnecessary operation, and the experience of the user in using the application program is improved.

In one possible design, the method further includes: the first application sends a second request to the server, wherein the second request is used for requesting the server to verify a second verification code, and the second request carries the second verification code; after receiving a fourth notification from the server, the fourth notification is used for indicating that the second verification code is not expired and the first verification code is consistent with the second verification code, the first application sends a fifth notification to the system component; the system component closes the first page and the second page or opens a third page in response to the fifth notification, the third page being different from the first page and the second page.

In one possible design, the method further includes: after receiving a sixth notification from the server indicating that the second verification code is not expired and the first verification code is inconsistent with the second verification code, the first application sends a seventh notification to the system component; the system component responds to the seventh notice and displays first prompt information, and the first prompt information is used for prompting the second verification code error; the system component receives the second verification code re-entered by the user on the second page, and repeatedly performs the operation after the operation of receiving the second verification code entered by the user on the second page.

In one possible design, the method further includes: the first application sends a ninth notification to the system component after receiving an eighth notification from the server indicating that the second verification code is expired; the system component responds to the ninth notice and displays second prompt information, and the second prompt information is used for prompting to obtain the short message verification code from the server again; and the system component receives the operation of the user on the first page for reacquiring the first verification code, and repeatedly executes the operation after receiving the operation of the user on the first page for acquiring the short message verification code.

In one possible design, the method further includes: the system component displays a first control, and the first control is used for acquiring a first verification code from the server; the system component determines an operation performed by the user on the first control as an operation performed by the user on the first page to retrieve the first verification code.

In one possible design, the first application includes: the device comprises a page component, a first module interface, a second module interface and a third module interface.

The method specifically comprises the following steps: the system component receives an operation executed by a user on a first page of the first application and used for acquiring a short message verification code; the system component responds to the operation for acquiring the short message verification code and sends a first notice to the page component; the page component responds to the operation of receiving the short message verification code and sends a first request to the server; the system component receives a first response from the server; the system component sends a second notice to the page component through the first module interface; the page component calls the first module interface to pass through the system component in response to receiving the second notification, focuses on the input box, obtains the first verification code, starts the keyboard application, and displays the input box and the second page; after receiving the operation of a second verification code input by the user on a second page, the system component sends a third notice to the page component through a second module interface; the page component calls a second module interface to obtain a second verification code from the third notice through the system component in response to receiving the third notice; the page component calls the first module interface and displays the second verification code in the input box.

In a possible design, the method specifically further includes: the page component sends a second request to the server; after receiving the fourth notification from the server, the page component sends a fifth notification to the system component through the third module interface; the system component closes the first module interface and closes the first page and the second page, or closes the first module interface and opens the third page, in response to the fifth notification.

In one possible design, the method specifically further includes: after receiving the sixth notification from the server, the page component sends a seventh notification to the system component through the third module interface; the system component displays the first prompt message in response to the seventh notification; the system component receives the second verification code re-entered by the user on the second page, and repeatedly performs the operation after the operation of receiving the second verification code entered by the user on the second page.

In one possible design, the method further includes: after receiving the eighth notification from the server, the page component sends a ninth notification to the system component through the third module interface; the system component displays the second prompt message in response to the ninth notification; the system component receives the operation of the user on the first page for reacquiring the first verification code, and repeatedly executes the operation after receiving the operation of the user on the first page for acquiring the short message verification code.

In a second aspect, the present disclosure provides an electronic device comprising: a memory and a processor; the memory is used for storing program instructions; the processor is configured to invoke the program instructions in the memory to cause the electronic device to execute the short message verification code filling method in any one of the possible designs of the first aspect and the first aspect.

In a third aspect, the present disclosure provides a chip system applied to an electronic device including a memory, a display screen, and a sensor; the chip system comprises: a processor; when the processor executes the computer instructions stored in the memory, the electronic device executes the short message verification code filling method in any one of the possible designs of the first aspect and the first aspect.

In a fourth aspect, the present disclosure provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to enable an electronic device to implement the method for filling a short message verification code in any one of the possible designs of the first aspect and the first aspect.

In a fifth aspect, the present disclosure provides a computer program product comprising: the execution instructions are stored in the readable storage medium, and the at least one processor of the electronic device can read the execution instructions from the readable storage medium, and the execution instructions executed by the at least one processor enable the electronic device to implement the short message verification code filling method in any one of the possible designs of the first aspect and the first aspect.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.

In order to more clearly illustrate the embodiments or technical solutions in the prior art of the present disclosure, the drawings used in the description of the embodiments or prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.

FIGS. 1A-1M are schematic diagrams of human-computer interaction interfaces provided by embodiments of the present disclosure;

fig. 2 is a schematic diagram of a partial software architecture of an electronic device according to an embodiment of the present disclosure;

fig. 3 is an interaction diagram of a short message verification code filling method according to an embodiment of the present disclosure;

fig. 4 is an interaction diagram of a short message verification code filling method according to an embodiment of the present disclosure.

Detailed Description

In order that the above objects, features and advantages of the present disclosure may be more clearly understood, aspects of the present disclosure will be further described below. It should be noted that the embodiments and features of the embodiments of the present disclosure may be combined with each other without conflict.

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure, but the present disclosure may be practiced in other ways than those described herein; it is to be understood that the embodiments disclosed in the specification are only a few embodiments of the present disclosure, and not all embodiments.

Illustratively, the disclosure provides a short message verification code filling method and electronic equipment, which configure a page requiring frequent iteration/update in an APP or a page requiring frequent change in style and function as an H5 page, and maintain bidirectional communication between an application component of the H5 page and a system component (native) in the electronic equipment by using a newly added module interface (bridge) in the APP. Under the scene that a short message verification code needs to be filled in an H5 page in an APP, the input box of the short message verification code can be automatically focused, so that the input box can become a first responder, the short message verification code can be automatically picked up through a system component (native) in electronic equipment, a keyboard application is called, and the layout of the H5 page is completed, so that the electronic equipment can present the page of the keyboard application of the short message verification code, and the interaction between the H5 page and the keyboard application is favorably realized. Therefore, the short message verification code can be automatically filled into the input box without the need of manually focusing the input box by a user, the automatic filling operation of the short message verification code is simplified, and the experience of the user using the APP is improved.

The electronic device may be a tablet computer, a mobile phone (e.g., a folding screen mobile phone, a large screen mobile phone, etc.), a wearable device, a vehicle-mounted device, an Augmented Reality (AR)/Virtual Reality (VR) device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a Personal Digital Assistant (PDA), a smart television, a smart screen, a high-definition television, a 4K television, a smart speaker, a smart projector, and other internet of things (IOT) devices, and the specific type of the electronic device is not limited by the present disclosure.

The present disclosure does not limit the type of operating system of the electronic device. For example, an Android system, a Linux system, a Windows system, an iOS system, etc.

H5 (i.e. HTML5, HyperText Markup Language 5, fifth version of HyperText Markup Language) is a Language description method for constructing Web content, and is a specification of core Language HTML in Web, and content viewed by a user when browsing a Web page by any means is originally in HTML format, and is converted into information for identification by some technical processing in a browser.

The system component (native) mainly provides functions of page layout, automatic verification code picking, keyboard application and the like.

The module interface (bridge) can be understood as a bridge between the H5 page and the system component (native). Bridge is used for intercommunication between the H5 page and the system component (native), so that the H5 page and the system component (native) can call each other and transfer information to each other. Bridge is also used for realizing the function required by the automatic filling of the short message verification code.

Based on the foregoing description, the embodiment of the present disclosure will use an electronic device as an example, and details a short message verification code filling method provided by the present disclosure are set forth in conjunction with the accompanying drawings and application scenarios.

With reference to fig. 1A to 1M, a specific implementation process of the short message verification code filling method is described. For convenience of description, in fig. 1A to 1M, an electronic device is taken as a mobile phone, an application 1 is installed in the mobile phone, and a scene filled with a short message verification code is taken as an example of a scene in which the application 1 needs to bind a bank card.

Referring to fig. 1A to 1M, fig. 1A to 1M are schematic diagrams of a human-computer interaction interface provided by an embodiment of the disclosure.

The application 1 can display a user interface 11 exemplarily shown in fig. 1A on the mobile phone, and the user interface 11 is used for displaying a page corresponding to adding a bank card in the application 1. Among other things, the user interface 11 may include: an input box 101, wherein the input box 101 is used for inputting a bank card number of a bank card.

After the application 1 receives that the user performs an operation of entering the bank card number "6225880184884843" into the input box 101 in the user interface 11 shown in fig. 1A, the application 1 may display the user interface 12 exemplarily shown in fig. 1B on the mobile phone, where the user interface 12 is used for displaying a page corresponding to the bank card number entered in the application 1. Wherein the user interface may include: and a control 102, wherein the control 102 is used for entering a page corresponding to the detailed content of the added bank card in the application 1.

After the application 1 receives an operation of the user, such as clicking the control 102, in the user interface 12 shown in fig. 1B, the application 1 may display the user interface 13 exemplarily shown in fig. 1C on the mobile phone, where the user interface 13 is used to display a page corresponding to the detailed content of the bank card added in the application 1.

Among other things, the user interface 13 may include: the system comprises an input box 103, an input box 104 and an input box 105, wherein the input box 103 is used for inputting a card holder of the bank card, the input box 104 is used for inputting an identity card number of the card holder of the bank card, and the input box 105 is used for inputting a reserved mobile phone number of the card holder of the bank card.

After application 1 receives the user and executes operations such as entering the name "yang" into input box 103, entering the identification number "3 x" into input box 104, and entering the mobile phone number "13 x 3" into input box 105, application 1 may display user interface 14 exemplarily shown in fig. 1D on the mobile phone, where user interface 14 is used to display pages of application 1 for entering the name, identification number, and reserved mobile phone number of the transactor corresponding to the bank card. Among other things, user interface 14 may include: and the control 106, wherein the control 106 is used for acquiring a page corresponding to the short message verification code sent by the server.

After the application 1 receives an operation that the user performs, for example, clicking the control 106 in the user interface 14 shown in fig. 1D, the application 1 may send a request for obtaining the short message verification code to the server, and display a window 200 exemplarily shown in fig. 1E or fig. 1K on the user interface 14, so that the application 1 can implement the binding of the bank card based on the short message verification code.

The window 200 is used for displaying a page corresponding to the short message verification code input by the user in the application 1. The window 200 may include: a display area 201, an input box 202, and a page 203.

The display area 201 is used to display a prompt message such as a text "the mobile phone that the verification code has sent 13 × × 3" so as to prompt the user to send a short message related to the verification code, such as sent information, error information, and the like.

The input box 202 is used to fill in the short message authentication code entered by the user, and application 1 takes the input box 202 as a first responder.

The page 203 is used to display a page corresponding to the keyboard application. Among other things, page 203 may include: a display area 2031 and pages 2032. The display area 2031 is used for displaying the short message verification code sent by the server, such as the words "from" message "and" 675670 ". Page 2032 is used to display the relevant content of the keyboard, such as the numbers 0 to 9 and controls for deletion.

After the application 1 receives the operation that the user performs the short message verification code "675670" in the window 200 shown in fig. 1E by clicking the display area 2031, since the application 1 uses the input box 202 as the first responder, the application 1 may display the number "675670" in the input box 202 as exemplarily shown in fig. 1F, so that the short message verification code "675670" input by the user can be automatically filled in the input box 202.

After the application 1 receives the short message verification code '675670' input by the user in the input box 202, the application 1 may send the short message verification code '675670' input by the user to the server, so that the server may determine whether the short message verification code '675670' input by the user is expired and whether the short message verification code '675670' input by the user is consistent with the short message verification code '675670' sent by the server.

When the server determines that the short message verification code '675670' input by the user is not expired and the short message verification code '675670' input by the user is consistent with the short message verification code '675670' sent by the server, the server may send a notification to the application 1 to indicate that the two are consistent. Upon receiving the aforementioned notification, since it takes some time for the application 1 to close the software components required for the user interface 14, the application 1 may display an icon 204, as exemplarily shown in fig. 1G, in the window 200 so as to wait for the application 1 to close the software components required for the user interface 14. The icon 204 is used to indicate that the application 1 is loading a page after the short message verification code is successfully verified.

After the application 1 closes the software components required by the user interface 14, the application 1 may display the user interface 15 exemplarily shown in fig. 1H on the mobile phone, thereby completing the process of binding the bank card by the application 1. The user interface 15 is used for displaying a page corresponding to the payment password of the bank card set in the application 1.

In summary, when the application 1 provides the page needing to be filled with the short message verification code for the user, the application 1 can use the input box as the first response object without considering the complexity of interaction, the user does not need to execute the operation of focusing the input box, and after the user inputs the short message verification code into the input box, the short message verification code can be automatically filled into the input box, so that the operation of filling the short message verification code is simplified, the user is prevented from executing unnecessary operations, and the experience of the user in using the application program is improved.

When the server determines that the user-entered short message verification code '675670' is expired, the server may transmit a notification indicating that the user-entered short message verification code '675670' is expired to the application 1. After receiving the notification, the application 1 may display a display area 201 and a control 205, as exemplarily shown in fig. 1I, in the window 200, so as to notify the user that the short message verification code input by the user has expired and needs to be retrieved. In the display area 201, the text "validation code timeout" is displayed. The control 205 is used for re-acquiring the short message verification code from the server.

After the application 1 receives an operation that the user performs, for example, clicking the control 205 on the window 200 shown in fig. 1I, the application 1 may send a request for obtaining the short message verification code to the server, and display the window 200 exemplarily shown in fig. 1J on the user interface 14, so that the application 1 can implement the binding of the bank card based on the short message verification code. In the window 200, a display area 201 displays the text "mobile phone with verification code already sent your 13 x 3" to indicate that the server has sent the short message verification code to the application 1 again, and a display area 2031 displays the short message verification code "394518" sent again by the server.

After the application 1 receives an operation that the user performs, for example, clicking on the short message verification code "394518" in the display area 2031 in the window 200 shown in fig. 1J, since the application 1 uses the input box 202 as a first responder, the application 1 may display the number "394518" in the input box 202, so that the short message verification code "394518" input by the user can be automatically filled in the input box 202.

Further, the app 1 may receive the short message authentication code "394518" input by the user in the input box 202. The subsequent operation of the application 1 receiving the short message verification code "394518" input by the user in the input box 202 is similar to the subsequent operation of receiving the short message verification code "675670" input by the user in the input box 202, which may be referred to the above-mentioned contents specifically, and is not described herein again.

In summary, when the short message verification code 2 expires, the application 1 may prompt the user in the page 1 that the short message verification code needs to be reacquired, and when the user requests to acquire the short message verification code again in the page 1, the page 1 may display corresponding prompt information on the page of the keyboard application, so that the user has requested to acquire the short message verification code again in the page 1. And after the server resends the short message verification code to the system component (native), the page 1 can still pick up the verification code sent by the server through the system component (native), display the page of the keyboard application carrying the short message verification code, and ensure that an input frame of the short message verification code is used as a first response object, so that the short message verification code can be automatically filled into the input frame. Therefore, the real-time interaction of the module interface (bridge) in the application 1 is ensured, the state of the module interface (bridge) is updated in time, and the application 1 can realize the function of automatically filling the input box with the short message verification code in a scene with complex interaction.

In addition, in addition to the user performing an operation of clicking the short message authentication code "675670" in the display area 2031 in the window 200 shown in fig. 1E, the user can automatically fill the short message authentication code in the input box 202 by performing an operation of clicking numbers in sequence in the page 2032 without performing an operation of focusing on the input box 202.

After the application 1 receives that the user performs the operation of sequentially clicking the number "645670" on the page 2032 exemplarily shown in fig. 1K, since the application 1 uses the input box 202 as the first responder, the application 1 may display the number "645670" exemplarily shown in fig. 1L in the input box 202, so that the short message verification code "645670" inputted by the user can be automatically filled in the input box 202.

In addition, the window 200 exemplarily shown in fig. 1L may further include: and a display area 206, wherein the display area 206 is used for displaying the countdown that the application 1 can reacquire the short message verification code from the server.

After the application 1 receives the short message verification code "645670" input by the user in the input box 202, the application 1 may send the short message verification code "645670" input by the user to the server, so that the server may determine whether the short message verification code "645670" input by the user is expired, and whether the short message verification code "645670" input by the user is consistent with the short message verification code "675670" sent by the server.

When the server determines that the short message verification code '645670' input by the user is not expired and the short message verification code '645670' input by the user is inconsistent with the short message verification code '675670' sent by the server, the server may send a notification to the application 1 to indicate that the two are inconsistent. After receiving the foregoing notification, the application 1 may display the text "verification code error" exemplarily shown in fig. 1M in the display area 201, please retry after checking "so as to notify the user of the input short message verification code error and notify the user to re-input the short message verification code.

In summary, after the electronic device fails to send the short message verification code input by the user to the server, or the electronic device receives a message verification code from the server indicating that the short message verification code input by the user is inconsistent with the short message verification code sent by the server, the page 1 may display a prompt message on the page of the keyboard application, so that the user can re-input the short message verification code, and still ensure that the input box of the short message verification code is used as the first responder, so that the user can re-input the short message verification code, and the short message verification code can be automatically filled in the input box. Therefore, the real-time interaction of the module interface (bridge) in the application 1 is ensured, the state of the module interface (bridge) is updated in time, and the application 1 can realize the function of automatically filling the input box with the short message verification code in a scene with complex interaction.

Based on the descriptions of the embodiments of fig. 1A to 1M, in the electronic device, the H5 page in the application 1 may communicate with a system component (native) and invoke a function, so that the H5 page in the application 1 can implement a function of automatically filling the short message verification code.

Next, with reference to fig. 2, a specific implementation process of the application 1 and the system component (native) in the electronic device to implement mutual communication and function invocation will be described.

Referring to fig. 2, fig. 2 is a schematic diagram of a partial software architecture of an electronic device according to an embodiment of the present disclosure. As shown in fig. 2, a part of the software architecture of the electronic device includes: application 1 and system components (native).

Application 1 may include: the short message verification code module comprises a page 1 component, a short message verification code module interface (CJVerify), a notification module interface (receiveNotification) and an updated short message verification code module interface (CJVerifyNotification).

The short message verification code module interface (CJVerify), the notification module interface (receiveNotification), and the updated short message verification code module interface (CJVerify) may be understood as Application Programming Interface (API).

And the page 1 component is used for setting the page 1 related to bank card binding as an H5 page, and the

user interfaces

11, 12, 13, 14 and 15 in the figures 1A-1M are all H5 pages.

The short message verification code module interface (CJVerify) is used for realizing communication and interaction between the page 1 component and the system component (native), so that the page 1 component automatically focuses on an input frame of the short message verification code through the system component (native), calls a keyboard application in the system component (native), automatically picks up the short message verification code sent by the server, and displays the picked short message verification code in a display page of the keyboard application.

The present disclosure does not limit the specific implementation manner of the short message verification code module interface (CJVerify). For example, the following codes are used to describe the setting of short message verification code module interface (CJVerify).

Window.CaijingStockJSBridge.call('CJVerify'，{

Id: "// Mark Current CJVerify, closeWebview method can be used for shutdown

title: "// title

mobil: "// Mobile phone number sending short message verification code

qa _ url: "// Upper Right Help button click on the page URL to load

qa _ title: "// Upper Right Help button click to load title of page

back_button_icon：″，//arrow|close

number_of_inputs：6，//4|6

animation _ direction: left',// left: sliding in from right to left and sliding out from left to right; up: from bottom to top, from top to bottom

A timer: 60,// how many seconds to count down, default 60

}，(data)＝>{

The callback function needs to be triggered when the following events are triggered in/CJVerify:

})；

and the notification module interface (receiveNotification) is used for realizing communication and interaction between the page 1 component and the system component (native), so that the page 1 component acquires the short message verification code input by the user from the notification sent by the system component (native).

The present disclosure does not limit the specific implementation manner of the notification module interface (receiveNotification). For example, using table 1, the setting of parameters in the notification module interface (receiveNotification) is described in detail.

Table 1 notification module interface (receiveNotification) of parameters and their meanings

Updating short message verification code module interface (CJVerifyNotify) for realizing communication and interaction between the page 1 component and the system component (native) so that the page 1 component calls the system component (native) to display corresponding prompt information and provide a control for reacquiring the short message verification code when the short message verification code input by the user is expired, calls the system component (native) to close the CJVerify module interface (CJVerify) and close the page 1 or close the CJVerify module interface (CJVerify) and open the H5 page of the message when the short message verification code input by the user is not expired and the short message verification code input by the user is inconsistent with the verification code sent by the server to display corresponding prompt information, so that the user can know that the short message verification code needs to be input again.

The present disclosure does not limit the specific implementation manner of updating the short message verification code module interface (CJVerifyNotify). For example, the following code is used to describe the setting of the update short message verification code module interface (CJVerifyNotify) in detail.

Window.CaijingStockJSBridge.call('CJVerifyNotify'，{

type：″，

data：‘’，

action：{}

}，(data)＝>{

})；

Wherein, the specific meanings of the above parameters type, data and action can be seen in table 2.

TABLE 2 meanings of type, data and action

In table 2, whether the short message authentication code is successfully transmitted can be distinguished by the type value. The short message verification code updating module interface (CJVerifyNotify) can actively send a notice to the page 1 component, and the page 1 component can display the countdown of the short message verification code or the error of the short message verification code.

And when the verification is finished, the short message verification code module interface (CJVerifyNotify) is updated and can be closed through verify-close.

Because the closing of the short message verification code module interface (CJVerify) requires about 250ms of animation, there is a case that the animation effect is inconsistent whether a new H5 page (webview) is opened or the current page 1 is closed after the short message verification code module interface (CJVerify) is closed. Therefore, in order to solve the above problem, the action parameter is updated in the short message verification code module interface (CJVerifyNotify).

When the close _ type value in action is close _ source, it indicates that the short message verification code module interface (CJVerify) needs to be closed synchronously with the current page 1 after verification is completed, and after the page 1 component can recognize the notification, the short message verification code module interface (CJVerify) and the current page 1 can be closed simultaneously.

When the close _ type value in the action is delay _ close, the short message verification code module interface (CJVerify) is delayed to be removed, and a new page is opened after the short check is completed, so that the page called by the short message verification code module interface (CJVerify) and the page called by the short check can be simultaneously pushed out, and the consistency of the effect of pushing out the transition animation is ensured.

It should be noted that the three module interfaces (bridges) can be implemented by using computer languages such as JavaScript (JS for short), for example, the module interface (bridge) can be regarded as JSbridge.

After a user requests to acquire the short message verification code in the page 1 and the server sends the short message verification code to the electronic equipment, the page 1 can call a system component (native) through the three module interfaces (bridge), so that the problem that the short message verification code cannot be automatically filled into an input box due to the fact that the input box of the short message verification code cannot be used as a first response object is solved.

And when the countdown is finished and the user requests to acquire the short message verification code again in the page 1, the page 1 can display prompt information on the page of the keyboard application, so that the user can request to acquire the short message verification code again in the page 1. After the server resends the short message verification code to the system component (native), the page 1 can still pick up the verification code sent by the server through the system component (native), display the page of the keyboard application carrying the short message verification code, and ensure that an input frame of the short message verification code is used as a first response object, so that the short message verification code can be automatically filled into the input frame.

And after the electronic equipment fails to send the short message verification code input by the user to the server or the electronic equipment receives the short message verification code input by the user from the server and is inconsistent with the short message verification code sent by the server, the page 1 can display prompt information on the page of the keyboard application so that the user can input the short message verification code again, and can still ensure that the input box of the short message verification code is used as a first response object so that the user can input the short message verification code again, and the short message verification code can be automatically filled into the input box.

In conclusion, the real-time interaction of the module interface (bridge) in the application 1 is ensured, and the state of the module interface (bridge) is facilitated to be updated in time, so that the application 1 can realize the function of automatically filling the input box with the short message verification code in a scene with complex interaction.

Based on the descriptions of the embodiments of fig. 1A to fig. 1M and fig. 2, a specific implementation process of the short message verification code filling method provided by the present disclosure is explained in detail with reference to fig. 3.

Referring to fig. 3, fig. 3 is an interaction diagram of a short message verification code filling method according to an embodiment of the present disclosure. As shown in fig. 3, the method for filling a short message verification code of the present disclosure may include:

s0, the system component (native) receives the operation of the user on the page 1 for obtaining the short message verification code, and responds to the operation for obtaining the short message verification code, and sends a notice 0 to the page 1 component.

Wherein, the page 1 is an H5 page requiring the short message verification code to be verified in the application 1. The present disclosure does not limit the specific representation manner of the page 1. For example, page 1 is the user interface 14 illustratively shown in FIG. 1D.

The operation of the user on the page 1 for acquiring the short message verification code may include, but is not limited to, clicking, double-clicking, long-pressing, dragging, and the like. For example, the operation of the user on the page 1 to obtain the short message verification code may be an operation performed by the user in the user interface 14 exemplarily shown in fig. 1D, such as clicking the control 106.

Wherein, the notification 0 is used to notify the page 1 component that the page 1 needs to verify the short message authentication code. The present disclosure does not limit the specific implementation of notification 0. For example, the notification 0 may carry the content such as the identifier of the page 1 and the mobile phone number.

S1, the page 1 component sends a request 1 to the server in response to receiving the operation of the user on the page 1 for acquiring the short message verification code.

The request 1 is used for requesting a short message verification code from the server.

S2, the server sends the short message verification code 1 to a system component (native).

The short message verification code 1 may adopt representation modes such as numbers, letters, coincidence and the like, and the short message verification code 1 may be carried in a response, for example, a response is sent to a system component (native) in a short message form, which is not limited in the disclosure. Additionally, a response may be included in the response, the response informing a system component (native) that the server has received request 1.

S3, the system component (native) sends notice 1 to the page 1 component through the short message verification code module interface (CJVerify).

Wherein, the notification 1 is used for notifying the page 1 component that the short message verification code 1 sent by the server is received. The present disclosure does not limit the specific implementation of notification 1.

S4, calling a short message verification code module interface (CJVerify) by a page 1 component, focusing an input box of the short message verification code through a system component (native), starting a keyboard application, picking up the short message verification code 1, and displaying the input box and a page 2 corresponding to the keyboard application containing the short message verification code 1 on the page 1.

The input box of the focused short message verification code can be understood as follows: the user does not need to execute operations such as clicking at the input box of the short message verification code, and after the user executes operations such as clicking keyboard numbers or the short message verification code in the page 2, the clicked contents can be automatically filled into the input box of the short message verification code.

The input box of the short message verification code may be already displayed on the page 1 before the step S4 is executed, or may be displayed on the page 1 when the step S4 is executed, which is not limited in this disclosure. The specific representation mode of the input box of the short message verification code is not limited, and the input box of the short message verification code is matched with the format of the short message verification code input by the user. For example, the input box of the short message verification code may be the input box 202 in the window 200 exemplarily shown in fig. 1E or fig. 1K.

Wherein, starting the keyboard application can be understood as: and starting the keyboard application in a system component (native) so as to realize the related functions of the keyboard application.

The page 2 is a page of the keyboard application, and the page 2 contains a short message verification code 1. The specific implementation of page 2 is not limited by this disclosure. For example, page 2 is page 203 in window 200 exemplarily shown in fig. 1E or fig. 1K.

It should be noted that the present disclosure may use a pop-up window to display the input box of the short message verification code and the page 2 on the page 1, for example, the window 200 exemplarily shown in fig. 1E or fig. 1K, or may separately display the input box of the short message verification code and the page 2, which is not limited in this disclosure.

And S5, after receiving the operation of the short message verification code 2 input on the page 2 by the user, the system component (native) sends a notification 2 to the page 1 component through a notification module interface (receiveNotification).

The operation of the short message verification code 2 input by the user on the page 2 may include, but is not limited to, clicking, double-clicking, long-pressing, dragging and other types of operations. For example, the user's operation of entering short message verification code 2 on page 2 may be the user performing an operation such as clicking short message verification code "675670" in display area 2031 in window 200 exemplarily shown in fig. 1E.

The notification 2 is used for notifying the page 1 component that the user has completed inputting the short message verification code 2, and the notification 2 carries the short message verification code 2. The present disclosure does not limit the specific implementation of notification 2. For example, notice 2 may be named with the notice name CJVerifyRes.

S6, the page 1 component responds to the received notice 2, and calls a notice module interface (receiveNotification) to acquire the short message verification code 2 carried in the notice 2 through a system component (native).

S71, the page 1 component calls a short message verification code module interface (receiveNotification) to display a short message verification code 2 in an input box of the short message verification code through a system component (native).

The page 1 component takes the input frame of the short message verification code as a first response object, so the page 1 component can fill the short message verification code 2 into the input frame of the short message verification code and display the short message verification code in the input frame of the short message verification code through a system component (native).

The specific implementation process of step S71 can refer to the description of filling the short message verification code "675670" into the input box 202 exemplarily shown in fig. 1F, which is not described herein again.

S72, the Page 1 component sends request 2 to the server.

The request 2 carries a short message verification code 2, and the request 2 is used for requesting the server to verify the short message verification code 2. The present disclosure does not limit the specific implementation of request 2.

It should be noted that, the execution sequence of step S71 and step S72 is not sequential, step S71 may be executed first and then step S72 is executed, step S72 may be executed first and then step S71 is executed, or step S71 and step S72 may be executed simultaneously.

S8, the server responds to the received request 2 and judges whether the short message verification code 2 is expired.

Because the short message verification code has timeliness, if the server receives the short message verification code 2 within the effective duration of the short message verification code 1, the server can determine that the short message verification code 2 is not expired. Within the effective duration of the short message verification code 1, if the server does not receive the short message verification code 2, the server can determine that the short message verification code 2 is overdue.

Thus, when the short message verification code 2 is not expired, the server may perform step S9; when the short message verification code 2 expires, the server may perform step S121.

S9, the server judges whether the short message verification code 1 is consistent with the short message verification code 2.

When the short message verification code 1 is consistent with the short message verification code 2, the server can execute the step S101; when the short message verification code 1 is not consistent with the short message verification code 2, the server may execute step S111.

S101, the server sends a notice 3 to the page 1 component.

The notification 3 is used for notifying the page 1 component that the short message verification code 2 is not expired and the short message verification code 1 is consistent with the short message verification code 2. The present disclosure does not limit the specific implementation of notification 3. For example, the notification 3 carries an identifier for identifying that the short message verification code 1 is consistent with the short message verification code 2.

S102, the page 1 component responds to the received notice 3 and sends a notice 4 to a system component (native) through updating a short message verification code module interface (CJVerifyNotify).

The notification 4 is used for notifying a system component (native) that the short message verification code is verified successfully and performing subsequent operations. The present disclosure does not limit the specific implementation of notification 4.

S103, in response to receiving the notice 4, the system component (native) simultaneously closes the short message verification code component (CJVerify) and opens a new page 3, or simultaneously closes the verification code component (CJVerify) and closes a page 1.

It takes a long time for the system component (native) to close the short message verification code component (CJverify). Therefore, the system component (native) can set the closing duration of the short message verification code component (CJVerify) to be less than or equal to the opening duration of the page 3, so that the closing of the short message verification code component (CJVerify) and the opening of the page 3 can be simultaneously pushed out, and the consistency of the effect of pushing out the transition animation is ensured. Or the system component (native) can set the closing duration of the short message verification code component (CJVerify) to be less than or equal to the closing duration of the page 1, so that the short message verification code component (CJVerify) is closed and the closed page 1 can be pushed out simultaneously, and consistency of the effect of pushing out the transition animation is guaranteed.

Here, page 3 is H5 page in application 1, and page 3 is different from page 1. The specific implementation of the page 3 is not limited in this disclosure. For example, page 3 may be the user interface 15 exemplarily shown in FIG. 1H.

S111, the server sends a notice 5 to the page 1 component.

The notification 5 is used for notifying the page 1 component that the short message verification code 2 is not expired and the short message verification code 1 is inconsistent with the short message verification code 2. The present disclosure does not limit the specific implementation of the notification 5. For example, the notification 5 carries an identifier for identifying that the short message verification code 1 is inconsistent with the short message verification code 2.

And S112, the page 1 component responds to the received notice 5 and sends a notice 6 to a system component (native) through updating a short message verification code module interface (CJVerifyNotify).

The notification 6 is used for notifying a system component (native) that the short message verification code is verified incorrectly and executing subsequent operations. The present disclosure does not limit the specific implementation of the notification 6.

And S113, the system component (native) responds to the received notice 6 and displays the prompt message of the error of the short message verification code 2.

The specific implementation manner of the error prompt message of the short message verification code 2 is not limited in the present disclosure. For example, the error prompt message of the short message verification code 2 may be the text "verification code error, retry after verification" exemplarily shown in fig. 1M.

S114, receiving the operation of the short message verification code 2 re-input on the page 2 by the user by a system component (native), and executing the step S5.

The operation of the short message verification code 2 re-input on the page 2 by the user in step S114 may be the same as the operation of the short message verification code 2 re-input on the page 2 by the user in step S5. For example, click on SMS verification code 2 on page 2 or sequentially click on keyboard numbers on page 2.

Alternatively, the operation of the sms verification code 2 re-input on the page 2 by the user in step S114 may be different from the operation of the sms verification code 2 re-input on the page 2 by the user in step S5. For example, one operation is to sequentially click the keyboard numbers on the page 2, and the other operation is to execute the click of the short message verification code 2 on the page 2.

S121, the server sends a notice 7 to the page 1 component.

Wherein, the notification 7 is used for notifying the page 1 component that the short message verification code 2 is expired. The present disclosure does not limit the specific implementation of the notification 7. For example, the notification 7 carries an identifier for identifying the expiration of the short message authentication code 2.

And S122, the page 1 component responds to the received notice 7 and sends a notice 8 to a system component (native) through updating a short message verification code module interface (CJVerifyNotify).

The notification 8 is used for notifying a system component (native) that the short message verification code is expired and performing subsequent operations. The present disclosure does not limit the specific implementation of the notification 8.

And S123, responding to the received notice 8 by a system component (native), and displaying prompt information for reacquiring the short message verification code on the page 1.

The specific implementation manner of reacquiring the prompt message of the short message verification code is not limited in the present disclosure. For example, the prompt message for retrieving the short message verification code may be the text "verification code timeout" in the display area 201 exemplarily shown in fig. 1I.

In addition, the system component (native) can also be used for acquiring a control of the short message verification code on the page 1. The specific implementation manner of the control for acquiring the short message verification code on the page 1 is not limited in the present disclosure. For example, the control may be the control 205 exemplarily shown in fig. 1I.

And S124, receiving the operation of the user on the page 1 for acquiring the short message verification code by the system component (native), and executing the step S0.

The operation of the user on the page 1 in step S124 for acquiring the short message verification code and the operation of the user on the page 1 in step S0 for acquiring the short message verification code may act on the same or different controls, and may also perform the same or different operations, which is not limited in this disclosure.

Based on the foregoing embodiments, the short message verification code filling method provided by the present disclosure is described below.

Illustratively, the present disclosure provides a short message verification code filling method. Referring to fig. 4, fig. 4 is an interaction diagram of a short message verification code filling method according to an embodiment of the present disclosure.

The execution main body of the short message verification code filling method is the electronic equipment. The electronic device includes: a first application and a system component. For the first application, the description contents of application 1 in fig. 1A to 1M and fig. 2 to 3 may be referred to, and for the system components, the description contents of system components (native) in fig. 1A to 1M and fig. 2 to 3 may be referred to, which is not described herein again.

As shown in fig. 4, the method for filling a short message verification code of the present disclosure may include: steps S101-S109;

s101, receiving an operation executed by a user on a first page of a first application and used for acquiring a short message verification code by a system component.

The specific implementation manner of step S101 may refer to the description content of step S0 in fig. 3, and the first page may refer to the description content of page 1 exemplarily shown in fig. 3, which is not described herein again. S102, the system component responds to the operation for obtaining the short message verification code and sends a first notice to the first application, wherein the first notice is used for informing the first application that the short message verification code needs to be obtained.

The specific implementation manner of step S102 may refer to the description content of step S0 in fig. 3, the operation performed by the user on the first page for acquiring the short message verification code may refer to the description content of the operation performed by the user on the page 1 shown in fig. 3 as an example, and the first notification may refer to the description content of the notification 0 shown in fig. 3 as an example, which is not described again here.

S103, the first application responds to the operation of receiving the short message verification code and sends a first request to the server, wherein the first request is used for requesting to obtain the short message verification code.

The specific implementation manner of step S103 may refer to the description content of step S1 in fig. 3, and the first request may refer to the description content of request 1 exemplarily shown in fig. 3, which is not described herein again.

S104, the server sends a first response to the system component, and the first response carries the first verification code.

The specific implementation manner of step S104 may refer to the description content of step S2 in fig. 3, the first response may refer to the description content of a response carrying the short message verification code 1 in fig. 3, and the first verification code may refer to the description content of the short message verification code 1 exemplarily shown in fig. 3, which is not described herein again.

S105, the system component sends a second notice to the first application.

The specific implementation manner of step S105 may refer to the description content of step S3 in fig. 3, and the second notification may refer to the description content of notification 1 exemplarily shown in fig. 3, which is not described herein again.

S106, the first application responds to the second notification, focuses on the input frame of the short message verification code through the system component to obtain the first verification code, starts the keyboard application in the system component, and displays a second page corresponding to the input frame and the keyboard application, wherein the second page carries the first verification code.

The specific implementation manner of step S106 may refer to the description content of step S4 in fig. 3, and the second page may refer to the description content of page 2 exemplarily shown in fig. 3, which is not described herein again.

And S107, after receiving the operation of the second verification code input by the user on the second page, the system component sends a third notice to the first application.

The specific implementation manner of step S107 may refer to the description content of step S5 in fig. 3, the second verification code may refer to the description content of the short message verification code 2 exemplarily shown in fig. 3, and the third notification may refer to the description content of the notification 2 exemplarily shown in fig. 3, which is not repeated here.

And S108, the first application responds to the third notice and acquires the second verification code from the third notice through the system component.

The specific implementation manner of step S108 can refer to the description content of step S6 in fig. 3, which is not described herein again.

S109, the first application displays the second verification code in the input box.

The specific implementation manner of step S109 can refer to the description content of step S71 in fig. 3, which is not described herein again.

In some embodiments, on the basis of the embodiments of steps S101 to S109, the method for filling short message verification codes of the present disclosure may further include: steps S110-S118;

s110, the first application sends a second request to the server, the second request is used for requesting the server to verify the second verification code, and the second request carries the second verification code.

The specific implementation manner of step S110 may refer to the description content of step S72 in fig. 3, and the second request may refer to the description content of request 2 exemplarily shown in fig. 3, which is not described herein again.

And S111, after receiving a fourth notice from the server, wherein the fourth notice is used for indicating that the second verification code is not expired and the first verification code is consistent with the second verification code, the first application sends a fifth notice to the system component.

The specific implementation manner of step S111 may refer to the description contents of steps S8, S9, S101, and S102 in fig. 3, the description contents of notification 3 exemplarily shown in fig. 3 may be referred to for the fourth notification, and the description contents of notification 4 exemplarily shown in fig. 3 may be referred to for the fifth notification, which is not repeated here.

And S112, in response to the fifth notification, the system component closes the first page and the second page, or opens a third page, wherein the third page is different from the first page and the second page, and the third page is an H5 page in the first application.

The specific implementation manner of step S112 may refer to the description content of step S103 in fig. 3, and the third page may refer to the description content of page 3 exemplarily shown in fig. 3, which is not described herein again.

S113, after receiving the sixth notification from the server indicating that the second verification code is not expired and the first verification code is inconsistent with the second verification code, the first application sends a seventh notification to the system component.

The specific implementation manner of step S113 may refer to the description contents of steps S8, S9, S111, and S112 in fig. 3, the description content of notification 5 exemplarily shown in fig. 3 may be referred to for the sixth notification, and the description content of notification 6 exemplarily shown in fig. 3 may be referred to for the seventh notification, which is not repeated here.

And S114, the system component responds to the seventh notice and displays first prompt information, and the first prompt information is used for prompting the second verification code error.

The specific implementation manner of step S114 may refer to the description content of step S113 in fig. 3, and the first prompt information may refer to the description content of the prompt information with the error short message verification code 2 exemplarily shown in fig. 3, which is not described herein again.

And S115, the system component receives the second verification code re-input by the user on the second page, and repeatedly executes the operation after receiving the operation of the second verification code input by the user on the second page.

The specific implementation manner of step S115 may refer to the description content of step S114 in fig. 3, which is not described herein again.

And S116, after receiving the eighth notification for indicating that the second verification code is expired from the server, the first application sends a ninth notification to the system component.

The specific implementation manner of step S116 may refer to the description contents of steps S8, S9, S121, and S122 in fig. 3, the eighth notification may refer to the description content of notification 6 exemplarily shown in fig. 3, and the ninth notification may refer to the description content of notification 7 exemplarily shown in fig. 3, which is not repeated here.

And S117, the system component responds to the ninth notification and displays second prompt information, and the second prompt information is used for prompting to obtain the short message verification code from the server again.

The specific implementation manner of step S117 may refer to the description content of step S123 in fig. 3, and the second prompt information may refer to the description content of the prompt information for reacquiring the short message verification code exemplarily shown in fig. 3, which is not described herein again.

S118, the system component receives the operation of the user on the first page for reacquiring the first verification code, and repeatedly executes the operation after receiving the operation of the user on the first page for acquiring the short message verification code.

The specific implementation manner of step S118 can refer to the description content of step S124 in fig. 3, which is not described herein again.

In step S118, while the system component displays the second prompt message, a first control may also be displayed, where the first control is used to obtain the first verification code from the server; the system component determines an operation performed by the user on the first control as an operation performed by the user on the first page to retrieve the first verification code.

The first control may refer to the description content of the control for acquiring the short message verification code on the page 1 exemplarily shown in fig. 3, which is not described herein again.

In some embodiments, the first application comprises: the device comprises a page component, a first module interface, a second module interface and a third module interface.

The page component may refer to the description content of the page 1 component exemplarily shown in fig. 2, the first module interface may refer to the description content of the short message verification code module interface (CJVerify) exemplarily shown in fig. 2, the second module interface may refer to the description content of the notification module interface (receiveNotification) exemplarily shown in fig. 2, and the third module interface may refer to the description content of the updated short message verification code module interface (CJVerify) exemplarily shown in fig. 2, which is not described herein again.

The method for filling the short message verification code specifically comprises the following steps: steps S201-S209;

s201, receiving an operation executed by a user on a first page of a first application and used for acquiring a short message verification code by a system component.

S202, the system component responds to the operation for obtaining the short message verification code and sends a first notice to the page component.

The specific implementation manner of steps S201 and S202 can refer to the description content of step S0 in fig. 3, which is not described herein again.

S203, the page component responds to the operation of receiving the short message verification code and sends a first request to the server.

The specific implementation manner of step S203 may refer to the description content of step S1 in fig. 3, which is not described herein again.

S204, the system component receives the first response from the server.

The specific implementation manner of step S204 may refer to the description content of step S2 in fig. 3, which is not described herein again.

And S205, the system component sends a second notice to the page component through the first module interface.

The specific implementation manner of step S205 may refer to the description content of step S3 in fig. 3, which is not described herein again.

S206, the page component calls the first module interface to pass through the system component in response to the second notification, focuses on the input frame, obtains the first verification code, starts the keyboard application, and displays the input frame and the second page.

The specific implementation manner of step S206 may refer to the description content of step S4 in fig. 3, which is not described herein again.

And S207, after receiving the operation of the second verification code input by the user on the second page, the system component sends a third notice to the page component through the second module interface.

The specific implementation manner of step S207 can refer to the description content of step S5 in fig. 3, which is not described herein again.

S208, the page component calls the second module interface to obtain the second verification code from the third notice through the system component in response to the third notice.

The specific implementation manner of step S208 can refer to the description content of step S6 in fig. 3, which is not described herein again.

S209, the page component calls the first module interface and displays the second verification code in the input box.

The specific implementation manner of step S209 may refer to the description content of step S71 in fig. 3, which is not described herein again.

In some embodiments, on the basis of the embodiments of steps S201 to S209, the method for filling a short message verification code of the present disclosure may specifically include: steps S210-S218;

s210, the page component sends a second request to the server.

The specific implementation manner of step S210 may refer to the description content of step S72 in fig. 3, which is not described herein again.

And S211, after receiving the fourth notification from the server, the page component sends a fifth notification to the system component through the third module interface.

The specific implementation manner of step S211 can refer to the description contents of steps S8, S9, S101, and S102 in fig. 3, which are not described herein again.

S212, the system component responds to the fifth notification, and closes the first module interface and closes the first page and the second page, or closes the first module interface and opens the third page.

The specific implementation manner of step S212 may refer to the description content of step S103 in fig. 3, which is not repeated herein.

And S213, after receiving the sixth notification from the server, the page component sends a seventh notification to the system component through the third module interface.

The specific implementation manner of step S213 can refer to the description contents of steps S8, S9, S111, and S112 in fig. 3, which is not described herein again.

And S214, the system component responds to the seventh notice and displays the first prompt message.

The specific implementation manner of step S214 may refer to the description content of step S113 in fig. 3, which is not described herein again.

S215, the system component receives the second verification code re-input by the user on the second page, and repeatedly executes the operation after the operation of receiving the second verification code input by the user on the second page is received.

The specific implementation manner of step S215 can refer to the description content of step S114 in fig. 3, which is not described herein again.

And S216, after receiving the eighth notification from the server, the page component sends a ninth notification to the system component through the third module interface.

The specific implementation manner of step S216 can refer to the description contents of steps S8, S9, S121, and S122 in fig. 3, which are not described herein again.

S217, the system component responds to the ninth notification and displays second prompt information.

The specific implementation manner of step S217 may refer to the description content of step S123 in fig. 3, which is not described herein again.

S218, the system component receives the operation of the user on the first page for re-acquiring the first verification code, and repeatedly executes the operation after receiving the operation of the user on the first page for acquiring the short message verification code.

The specific implementation manner of step S218 can refer to the description content of step S124 in fig. 3, which is not described herein again.

Illustratively, the present application provides an electronic device comprising: a memory and a processor; the memory is used for storing program instructions; the processor is configured to call the program instructions in the memory, so that the electronic device executes the application module starting method of the foregoing embodiment.

The application provides a chip system, which is applied to an electronic device comprising a memory, a display screen and a sensor; the chip system includes: a processor; when the processor executes the application module starting method of the previous embodiment.

Illustratively, the present application provides a computer-readable storage medium having stored thereon a computer program, which, when executed by a processor, causes an electronic device to implement the application module launching method of the foregoing embodiments.

The present application provides, for example, a computer program product which, when run on a computer, causes the computer to perform the application module launching method of the preceding embodiments.

In the above-described embodiments, all or part of the functions may be implemented by software, hardware, or a combination of software and hardware. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions according to the embodiments of the present application are all or partially generated when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.

It is noted that, in this document, relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

The previous description is only for the purpose of describing particular embodiments of the present disclosure, so as to enable those skilled in the art to understand or implement the present disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A short message verification code filling method is applied to electronic equipment, and the electronic equipment comprises the following steps: first application and system components; the method comprises the following steps:

the system component receives an operation executed by a user on a first page of the first application and used for acquiring a short message verification code;

the system component responds to the operation for acquiring the short message verification code and sends a first notice to the first application, wherein the first notice is used for notifying the first application that the short message verification code needs to be acquired;

the first application responds to the operation for acquiring the short message verification code and sends a first request to a server, wherein the first request is used for requesting to acquire the short message verification code;

the system component receives a first response from the server, wherein the first response carries a first verification code;

the system component sending a second notification to the first application;

the first application focuses on an input box of a short message verification code through the system component in response to receiving the second notification, obtains the first verification code, starts a keyboard application in the system component, and displays a second page corresponding to the input box and the keyboard application, wherein the second page carries the first verification code;

the system component sends a third notice to the first application after receiving the operation of a second verification code input by a user on the second page;

the first application, in response to receiving the third notification, obtaining, by the system component, the second passcode from the third notification;

the first application displays the second verification code in the input box.

2. The method of claim 1, further comprising:

the first application sends a second request to the server, wherein the second request is used for requesting the server to verify the second verification code, and the second request carries the second verification code;

the first application sends a fifth notification to the system component after receiving a fourth notification from the server indicating that the second verification code is not expired and the first verification code is consistent with the second verification code;

the system component closes the first page and the second page or opens a third page in response to the fifth notification, the third page being different from the first page and the second page.

3. The method of claim 2, further comprising:

the first application sends a seventh notification to the system component after receiving a sixth notification from the server indicating that the second verification code is not expired and that the first verification code is inconsistent with the second verification code;

the system component responds to the seventh notice and displays first prompt information, and the first prompt information is used for prompting the second verification code error;

the system component receives the second verification code re-input by the user on the second page, and repeatedly executes the operation after receiving the operation of the second verification code input by the user on the second page.

4. The method of claim 2, further comprising:

the first application sends a ninth notification to the system component after receiving an eighth notification from the server indicating that the second verification code is expired;

the system component responds to the ninth notification and displays second prompt information, and the second prompt information is used for prompting to obtain the short message verification code from the server again;

and the system component receives the operation of the user on the first page for reacquiring the short message verification code, and repeatedly executes the operation after receiving the operation of the user on the first page for acquiring the short message verification code.

5. The method of claim 4, further comprising:

the system component displays a first control, and the first control is used for acquiring the first verification code from the server;

the system component determines an operation performed by a user on the first control as an operation performed by the user on the first page to retrieve the first verification code.

6. The method according to any of claims 1-5, wherein the first application comprises: the system comprises a page component, a first module interface, a second module interface and a third module interface;

the method specifically comprises the following steps:

the system component responds to the operation for acquiring the short message verification code and sends the first notice to the page component;

the page component responds to the operation for acquiring the short message verification code and sends the first request to the server;

the system component receiving the first response from the server;

the system component sends the second notification to the page component through the first module interface;

the page component calls the first module interface to focus on the input frame through the system component in response to receiving the second notification, obtains the first verification code, starts the keyboard application, and displays the input frame and the second page;

after receiving the operation of the second verification code input by the user on the second page, the system component sends the third notification to the page component through the second module interface;

the page component calls the second module interface to acquire the second verification code from the third notice through the system component in response to receiving the third notice;

and the page component calls the first module interface and displays the second verification code in the input box.

7. The method according to claim 6, characterized in that the method further comprises:

the page component sends a second request to the server;

after receiving a fourth notification from the server, the page component sends a fifth notification to the system component through the third module interface;

the system component closes the first module interface and closes the first page and the second page, or closes the first module interface and opens a third page, in response to the fifth notification.

8. The method according to claim 6, characterized in that the method further comprises:

after receiving a sixth notification from the server, the page component sends a seventh notification to the system component through the third module interface;

the system component displays a first prompt in response to the seventh notification;

9. The method of claim 6, further comprising:

after receiving the eighth notification from the server, the page component sends a ninth notification to the system component through the third module interface;

the system component displays a second prompt in response to the ninth notification;

and the system component receives the operation of the user on the first page for reacquiring the first verification code, and repeatedly executes the operation after receiving the operation of the user on the first page for acquiring the short message verification code.

10. An electronic device, comprising: a memory and a processor;

the memory is to store program instructions;

the processor is configured to call the program instructions in the memory, so that the electronic device executes the short message verification code filling method according to any one of claims 1 to 9.

11. A chip system, wherein the chip system is applied to an electronic device comprising a memory, a display screen, and a sensor; the chip system includes: a processor; the electronic device performs the short message verification code population method of any one of claims 1-9 when the processor executes the computer instructions stored in the memory.

12. A computer-readable storage medium, on which a computer program is stored, wherein the computer program is configured to be executed by a processor to enable the electronic device to implement the short message verification code filling method according to any one of claims 1-9.