Method and device for verifying short message login function, equipment, medium and program product

Abstract

The invention provides a verification method and device of a short message login function, equipment, a medium and a program product, and relates to the technical field of the Internet, and a method of a control equipment side comprises the following steps: sending a first login control instruction and first script information of an application program to first virtual equipment; receiving a message of the application program sent by the terminal equipment, wherein the message of the application program comprises the verification code; sending a second login control instruction and second script information of the application program to the first virtual device, wherein the second login control instruction comprises a verification code; and obtaining a login result of the first virtual device based on the second script information and the verification code. According to the embodiment of the invention, the control device interacts with the terminal device to obtain the information of the application program, and interacts with the virtual device to control the virtual device to log in the application program. Through interaction among the control equipment, the terminal equipment and the virtual equipment, monitoring of the short message login function is realized, occupation of hardware resources is reduced, and the resource utilization rate is improved.

Description

Technical Field

[0001] The present application relates to the field of Internet technology, and in particular to a verification method, device, equipment, medium and program product for a text message login function. Background Art

[0002] The availability of SMS login functionality in current business applications is achieved through a simulated device consisting of a dedicated physical hardware device, a commercial mobile phone, and a Subscriber Identity Module (SIM) card in a 1:1:1 resource ratio.

[0003] Among them, the dedicated hardware is connected to a physical commercial mobile phone with a SIM card inserted through a data cable, and sends control instructions to the mobile phone through a wired method to control the mobile phone to send SMS verification codes and perform SMS login operations based on the verification codes, thereby realizing the monitoring of the availability of SMS login verification.

[0004] The monitoring system of the SMS login function of the above business applications requires a lot of hardware resources and has low resource utilization. Summary of the Invention

[0005] The embodiments of the present application provide a verification method, apparatus, device, medium, and program product for a text message login function to solve the problem of low resource utilization in a monitoring system for the text message login function.

[0006] To solve the above technical problems, this application is implemented as follows: In a first aspect, an embodiment of the present application provides a method for verifying a text message login function, which is executed by a control device, and the method includes: Sending a first login control instruction and first script information of the application program to the first virtual device; Receiving a message of the application sent by a terminal device, wherein the message of the application includes a verification code; Sending a second login control instruction and second script information of the application to the first virtual device, where the second login control instruction includes the verification code; Obtain a login result of the first virtual device logging in based on the second script information and the verification code.

[0007] Optionally, the sending the first login control instruction and the first script information of the application to the first virtual device includes: Acquire a service application device list, the service application device list including information of at least one virtual device and information of an application installed on the at least one virtual device, the at least one virtual device including the first virtual device; releasing a first token to the at least one virtual device; When the first virtual device obtains the first token, a first login control instruction and first script information of the application are sent to the first virtual device.

[0008] Optionally, before obtaining the service application device list, the method further includes: Receiving business application information sent by the at least one virtual device, the business application information including application program information and virtual device information; generating the service application device list based on the service application information and a pre-configured service application list; When receiving the indication information of the newly added first service application information sent by the second virtual device, not updating the service application device list; After obtaining the service application device list, the method further includes: When instruction information for deleting the second service application information is received from the second virtual device, the second service application information is deleted from the service application device list.

[0009] Optionally, after obtaining a login result of the first virtual device logging in based on the second script information and the verification code, the method further includes: According to the login result, a mark is added to the service information corresponding to the first virtual device in the service application device list, where the mark is used to indicate a verification status of the service information of the first virtual device.

[0010] Optionally, obtaining a login result of the first virtual device logging in based on the second script information and the verification code includes: Sending query information of the application interface to the first virtual device; A login result sent by the first virtual device in response to the query information is obtained, where the login result is a result of the first virtual device logging in based on the second script information and the verification code.

[0011] Optionally, after obtaining a login result of the first virtual device logging in based on the second script information and the verification code, the method further includes: When it is determined according to the login result that the number of times that the application fails to log in to the first virtual device reaches a preset number, an alarm message is output.

[0012] Optionally, after obtaining a login result of the first virtual device logging in based on the second script information and the verification code, the method further includes: When it is determined based on the login result that the number of times the application has failed to log in to the first virtual device reaches a preset number, and the interval between sending the verification code reaches a preset time length, the second token is released, and the second token is obtained by other virtual devices in the at least one virtual device except the first virtual device.

[0013] In a second aspect, an embodiment of the present application provides a method for verifying a text message login function, which is executed by a terminal device, and the method includes: receiving a message of an application sent by at least one virtual device, wherein the at least one virtual device includes a first virtual device, and the message includes a verification code; A message of the application is sent to the control device.

[0014] In a third aspect, an embodiment of the present application provides a method for verifying a text message login function, which is executed by a first virtual device, and the method includes: Receiving a first login control instruction and first script information sent by a control device; Displaying a login interface of an application based on the first login control instruction and the first script information, and sending a verification code to the terminal device based on the SIM number of the terminal device; receiving a second login control instruction and second script information sent by the control device, where the second login control instruction includes the verification code; Based on the login interface and the verification code, a login operation is performed on the interface of the application.

[0015] Optionally, after performing a login operation on the interface of the application, the method further includes: receiving query information of the application interface sent by the control device; In response to the query information, a login result is sent to the control device.

[0016] In a fourth aspect, an embodiment of the present application provides a verification device for a SMS login function, which is applied to a control device, including: A first sending module, configured to send a first login control instruction and first script information of an application program to a first virtual device; A first receiving module is configured to receive a message from the application sent by a terminal device, wherein the message from the application includes a verification code; A second sending module, configured to send a second login control instruction and second script information of the application to the first virtual device, where the second login control instruction includes the verification code; An acquisition module is used to obtain a login result of the first virtual device based on the second script information and the verification code.

[0017] In a fifth aspect, an embodiment of the present application provides a verification device for a SMS login function, applied to a terminal device, comprising: A receiving module, configured to receive a message of an application sent by at least one virtual device, wherein the at least one virtual device includes a first virtual device, and the message includes a verification code; The sending module is used to send the message of the application to the control device.

[0018] In a sixth aspect, an embodiment of the present application provides a verification device for a SMS login function, applied to a first virtual device, comprising: A first receiving module, configured to receive a first login control instruction and first script information sent by a control device; A first sending module, configured to display a login interface of an application based on the first login control instruction and the first script information, and send a verification code to the terminal device based on the SIM number of the terminal device; A second receiving module is configured to receive a second login control instruction and a second script information sent by the control device, wherein the second login control instruction includes the verification code; An execution module is used to perform a login operation on the interface of the application based on the login interface and the verification code.

[0019] In the seventh aspect, an embodiment of the present application provides an electronic device, comprising: a processor, a memory, and a program stored on the memory and runnable on the processor, wherein when the program is executed by the processor, the steps of the verification method for the SMS login function described in the first aspect are implemented.

[0020] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the verification method for the SMS login function described in the first aspect are implemented.

[0021] In a ninth aspect, a computer program product is provided, comprising computer instructions, which, when executed by a processor, implement the steps of the verification method for the SMS login function as described in the first aspect.

[0022] In this embodiment of the application, the control device interacts with the terminal device to obtain application information and interacts with the virtual device to control the virtual device to log into the application. By enabling the interaction between the control device, the terminal device, and the virtual device, SMS login functionality can be monitored, reducing hardware resource usage and improving resource utilization. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments of the present application. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0024] Figure 1 This is a structural diagram of a verification system for SMS login function provided by an embodiment of the present application; Figure 2 This is one of the flow charts of a verification method for a SMS login function provided in an embodiment of the present application; Figure 3 This is an architecture diagram of a verification system for SMS login function provided by an embodiment of the present application; Figure 4 This is the second flowchart of a verification method for a SMS login function provided in an embodiment of the present application; Figure 5 This is a flow chart of a method for adding business application information provided by an embodiment of the present application; Figure 6 This is a flow chart of a method for deleting business application information provided by an embodiment of the present application; Figure 7 This is the third flowchart of a verification method for a SMS login function provided in an embodiment of the present application; Figure 8 This is the fourth flow chart of a verification method for a SMS login function provided in an embodiment of the present application; Figure 9 This is one of the structural diagrams of a verification device for SMS login function provided in an embodiment of the present application; Figure 10 This is the second structural diagram of a verification device for SMS login function provided in an embodiment of the present application; Figure 11 This is the third structural diagram of a verification device for SMS login function provided in an embodiment of the present application; Figure 12 This is one of the structural diagrams of an electronic device provided in an embodiment of the present application; Figure 13 This is the second structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0025] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0026] SMS login verification is a prerequisite for various mobile applications (APPs) or personal computer (PC) client business applications to provide services to users. It is a frequently used business function. If the SMS login function of a business application is unavailable, users will be unable to use the service, which will significantly affect user experience. Therefore, perceptual monitoring of business application quality is an urgent issue to quickly identify and resolve problems and improve user experience.

[0027] The commonly used method at present is to connect a physical dedicated hardware device to and control a physical commercial Android phone with a SIM card inserted through a data cable, such as Figure 1 The above method has the following problems: First, unstable operation, complex repair operations, and long recovery times. The availability of SMS login functions for business applications requires continuous monitoring. During extended operation, the connection and control interactions between the dedicated hardware and commercial mobile phones are prone to failure, and the mobile phone software may freeze, complicating repair operations.

[0028] Second, utilization is low. A dedicated piece of hardware and a real mobile phone can only be deployed at one location to detect the SMS login capabilities of local business applications. For N provinces, at least N dedicated pieces of hardware, N real mobile phones, and N SIM cards are required. When the service covers many provinces, the demand for physical devices is high, and SIM card utilization is low.

[0029] Third, the scope of application service perception is limited. When monitoring the SMS login function of PC client applications, because the PC client is installed on a laptop, which does not have a SIM card and cannot receive SMS messages, the SMS login function of PC client business applications cannot be monitored.

[0030] The embodiments of the present application provide a verification method, apparatus, device, medium and program product for a text message login function to solve the problem of low resource utilization in a monitoring system.

[0031] See also Figure 2 , Figure 2 This is a flow chart of a verification method for SMS login function provided by an embodiment of the present application, which is executed by a control device, such as Figure 2 As shown, the method includes the following steps: Step 201: Send a first login control instruction and first script information of an application to a first virtual device; Step 202: Receive a message from the application sent by a terminal device, where the terminal device is provided with a Subscriber Identification Module (SIM). The message from the application is sent by the first virtual device to the terminal device in response to the first login control instruction and the first script information, and the message from the application includes a verification code. Step 203: Send a second login control instruction and second script information of the application to the first virtual device, where the second login control instruction includes the verification code; Step 204: Obtain a login result of the first virtual device based on the second script information and the verification code.

[0032] Among them, the execution system of the verification method of the SMS login function includes: a physical user terminal equipped with a SIM card (also known as a user device), a set of control devices (also known as a cloud service control terminal), and a group of virtual devices (also known as a cloud service simulation terminal). A group of virtual devices includes one or more virtual devices, and the first virtual device is one of the virtual devices.

[0033] Because virtual devices with apps installed (e.g., cloud phones and cloud PCs) lack a communication module with a SIM card, they cannot receive SMS verification codes sent by the SMS login verification application platform. Therefore, a physical phone with a SIM card is required to receive the service app.

[0034] At the same time, a SMS code collection service must be installed on the user terminal (such as a mobile phone). This service reads updated SMS messages from the user terminal in real time and pushes SMS verification codes to the control device in real time via a message queue, using the user terminal's wireless network connection (Wi-Fi). Multiple applications installed on the virtual device can reuse a single user terminal number for SMS login simulation. For example, using a mobile phone number as an example, the SMS code collection service pushes SMS messages to the control device (i.e., the cloud service control terminal) containing the receiving phone number, the time the message was received, the platform number where the message was sent, and the text of the message.

[0035] Based on the above system, the control device sends a first login control instruction for the application and first script information for executing the login control instruction to the first virtual device. Based on the first login control instruction and the first script information, the first virtual device can access the application's login interface and send an application message to the physical terminal device equipped with the SIM card. The message may include the application's identifier and a verification code for logging into the application account.

[0036] The physical terminal device sends the obtained application message (including the verification code and the application identifier) to the control device. Based on the application identifier, the control device again sends the second login control instruction and second script information of the application to the first virtual device.

[0037] The first virtual device enters the login interface of the application based on the second script information and enters the verification code carried by the second login control instruction. If the login is successful, a prompt message indicating the login success is displayed; if the login fails, a prompt message indicating the login failure is displayed.

[0038] The control device may obtain the login result of the first virtual device by sending a query message to the first virtual device, or the first virtual device may actively feed back the login result to the control device.

[0039] This embodiment uses a cloud service controller to control N1 (an integer greater than 0) cloud PC clients and N2 (an integer greater than 0) cloud mobile phone apps using internet access to simulate and monitor the availability of SMS verification code logins for multiple business applications. This method achieves the following beneficial effects: 1. A method for monitoring the availability of SMS verification code login functionality for business applications using dedicated hardware connected to physical mobile phones, utilizing the resources of N1+N2 dedicated hardware, N1+N2 mobile phones, and N1+N2 SIM cards. This method can reduce the hardware resource requirements by N1+N2 units to 1. One mobile phone and one SIM card can replace the resources required for N1+N2 mobile phones and SIM cards, significantly improving resource utilization and reducing costs.

[0040] For example, using a wired connection would require an investment of 52,000 yuan * (N1 + N2). This solution can reduce this cost to 22,000 yuan * (N1 + N2), a 60% reduction. Based on the current minimum network configuration of N1 + N2 = 62, this translates to a savings of 1.86 million yuan. The greater the number of deployment points required, the greater the cost savings. This solution also reduces the resources required for monitoring system deployment, improving resource utilization and stability.

[0041] Second, using dedicated hardware to connect to physical phones requires personnel to visit the deployment room for on-site troubleshooting when a problem occurs, resulting in low problem-solving efficiency. Cloud deployment uses a cloud service control terminal that interacts with the cloud PC / cloud phone via the internet. Both hardware and software issues can be resolved remotely, improving problem-solving efficiency.

[0042] 3. It facilitates rapid expansion of the cloud service simulation end and increases the number of simulation points. The wide coverage area makes it easier to reflect the real perception of business applications.

[0043] Optionally, the sending the first login control instruction and the first script information of the application to the first virtual device includes: Acquire a service application device list, the service application device list including information of at least one virtual device and information of an application installed on the at least one virtual device, the at least one virtual device including the first virtual device; releasing a first token to the at least one virtual device; When the first virtual device obtains the first token, a first login control instruction and first script information of the application are sent to the first virtual device.

[0044] Virtual devices (i.e., cloud service simulation terminals) are available in two modes: cloud PC and cloud phone. Cloud PC supports the installation of PC-based application client business applications, while cloud phone supports the installation of mobile app business applications. The business applications required for SMS verification code login simulation may vary on each virtual device. Each virtual device mode includes the cloud service simulation terminal information management service (hereinafter referred to as A1 service) and business execution service (hereinafter referred to as A2 service).

[0045] The A1 service generates and updates its own business application device list (also known as the business application configuration table) based on the built-in business application configuration table during initial installation and at predetermined intervals thereafter. This list includes application information, such as the business application ID (appID) and business application name (appname), as well as information about the virtual devices corresponding to the applications. Upon initial installation or when business applications are modified, these business applications interact with the cloud service control terminal via the internet to notify the cloud service control terminal of their application support status. Initial registration / addition / deletion information for virtual devices (i.e., virtual device information) includes: appID, appname, cloudID (virtual device ID), and cloudtype (virtual device type: including cloud PC and cloud phone). During initial registration, the business application configuration table information for all supported appID rows is sent; addition / deletion operations only send information about added / deleted appID rows.

[0046] The A2 service is used to compete for business application tokens and receive and execute business execution commands and dial-test scripts sent by the cloud service control terminal. A virtual device only competes once for the AppID in its supported application configuration table. Once all supported AppIDs have been simulated, no further competition for AppID business tokens is performed.

[0047] Among them, the control device (i.e., cloud service control terminal) includes SMS verification code processing service (referred to as C1 service), cloud service simulation terminal information pool management (referred to as C2 service), business application SMS verification code simulation distribution service (referred to as C3 service), and business application simulation terminal control service (referred to as C4 service).

[0048] The C1 service receives, stores, identifies, matches, and generates a query table for SMS verification codes for SMS messages pushed to physical mobile phones. The C1 service receives and stores SMS messages pushed by the SMS code collection service in real time, and uses existing AI technology to identify the verification code field in the SMS. It matches the pre-configured business application information list (i.e., the business application list) with the SMS content, identifies the appname, and records the SMS appname if it matches the appname in the pre-configured business application information. If it cannot be identified, the SMS is marked as "invalid." A SMS verification code query table is generated for SMS messages with matching appnames, containing: appid, appname, SMS reception time, and SMS verification code.

[0049] The C2 service receives the initial registration / addition / deletion information sent by the A1 service in real time. The information includes: appid, appname, cloudid (cloud service simulation terminal number), cloudtype (virtual device type: cloud PC, cloud phone), and matches it with the pre-configured business application information list of the control device. It stores and updates the generated business application device list in real time, as shown in Table 1 below: Table 1 cloudid cloudtype appid appname 010001 Cloud PC 0001 Application A 010001 Cloud PC 0002 Application B 010001 Cloud PC 0003 Application C 010002 Cloud Phone 0001 Application A 010002 Cloud Phone 0002 Application B 010002 Cloud Phone 0003 Application C 010003 Cloud PC 0001 Application A 010003 Cloud PC 0002 Application B 010003 Cloud PC 0003 Application C C3 service. To protect against cyberattacks, when designing SMS verification code login for business applications, a single mobile phone number is prohibited from sending SMS verification codes repeatedly within a certain period of time. Therefore, SMS verification code login for the same application (whether a PC client or a mobile app) using a single mobile phone number can only be executed on one virtual device at a time. However, different applications can use the same mobile phone number for SMS verification code login simultaneously. To ensure accuracy, the same virtual device only executes SMS verification code login for one business application at a time. The SMS verification code login simulation solution follows the above principles to fully reflect and simulate user perception and design a business simulation distribution service strategy.

[0050] To fully utilize the resources of virtual devices, the control device controls different virtual devices to simulate the SMS verification code login process for different business applications in parallel. At the same time, all virtual devices installed with a business application simulate the SMS verification code login process for that business application. In its initial state, the C3 service initializes a global simulation list based on the business application device list in the C2 service, including appid, cloudid, and cloudtype. Each round of simulation is considered complete when all tasks in each row of the global simulation list are completed. Before the next round of simulation, the initial global simulation list is generated based on the latest business application device list in the C2 service to start another round of simulation.

[0051] Because each appID can only be simulated on one virtual device at a time, the C3 service generates and issues a token based on the appID. This token can only be assigned to one virtual device at a time. When the C3 service sends a notification to all virtual devices to initiate simulation execution, it releases the token for each appID. The A2 services of all virtual devices initiate a token grabbing operation with the C3 service based on the appIDs they support in the application configuration table. After the C3 service finds that the A2 service of the first virtual device (any virtual device) has grabbed the appID token, it initiates a business simulation startup command (i.e., the first login control instruction) for that appID to the first virtual device that has grabbed the token.

[0052] The C4 service interacts with the A2 service to initiate the simulation, sending a simulation script (i.e., the first script information) to the first virtual device. It then queries the A2 service for the simulation status at preset intervals and queries the C1 service for the AppID SMS verification code. Upon completion of the simulation, the C3 service is notified of the end of the simulation, the AppID & CloudID service status is marked as completed in the global simulation list, and the success / failure result is recorded.

[0053] Through the above method, the control device releases tokens according to the business application list, which enables each business application in the business application list to perform simulation operations, reduce the omission of business applications, and realize the simulation allocation of multiple cloud service simulation terminals and applications in the form of appid tokens, thereby maximizing the utilization of service resources.

[0054] Optionally, before obtaining the service application device list, the method further includes: Receiving business application information sent by the at least one virtual device, the business application information including application program information and virtual device information; generating the service application device list based on the service application information and a pre-configured service application list; After obtaining the service application device list, the method further includes: When receiving the indication information of the newly added first service application information sent by the second virtual device, not updating the service application device list; When instruction information for deleting the second service application information is received from the second virtual device, the second service application information is deleted from the service application device list.

[0055] The control device is pre-configured with a list of business application information that needs to be sensed (i.e., business application list), including: business application number (appid), business application name (appname), for example: appid=0001, appname=application A, appid=0002, appname=application B, appid=02, etc., as shown in Table 2 below: Table 2 appid appname 0001 Application A 0002 Application B 0003 Application C …… …… Upon initial installation or changes to a business application, the virtual device interacts with the control device (i.e., the cloud service control terminal) to send information about the business application and the corresponding virtual device. The control device matches the information sent by at least one virtual device with preconfigured business application information to generate a list of business application devices. Based on this list, the control device sends a token to each virtual device in a predetermined order and sends a login script and login control instructions to the device that received the token.

[0056] When the indication information of adding the first service application information is received, the service application device list is not updated in this round, that is, the first service application information is not added to the service application device list in this round, and the first service application information can be added to the service application device list of the next round.

[0057] Upon receiving an instruction to delete the second service application information, the second service application information is removed from the service application device list. If the SMS login service corresponding to the second service application information has been marked as completed, the login result is not changed. If the SMS login service corresponding to the second service application information is not completed, the information corresponding to the second service application information is directly deleted from the list. This can reduce the interference caused by the addition or deletion of services to the current simulation round and reduce omissions.

[0058] A business application device list information resource pool is formed through C3 service and C2 service, an initialized global simulation list is formed according to the resource pool information, and the task list is updated to form a simulation task list.

[0059] In the above manner, the control device releases the token according to the service application list, so that each service application in the service application list can perform the simulation operation, thereby reducing omissions.

[0060] Optionally, after obtaining a login result of the first virtual device logging in based on the second script information and the verification code, the method further includes: According to the login result, a mark is added to the service information corresponding to the first virtual device in the service application device list, where the mark is used to indicate a verification status of the service information of the first virtual device.

[0061] After each application program's corresponding business application completes login, a mark is added to the business information, such as the verification status of the business information is completed, and the result of login success or login failure is recorded. Based on the mark, the completion status of the business application corresponding to the application program can be determined.

[0062] This makes it easier to simulate login for business applications that have not logged in, and to troubleshoot problems with business applications that have failed to log in.

[0063] Optionally, obtaining a login result of the first virtual device logging in based on the second script information and the verification code includes: Sending query information of the application interface to the first virtual device; A login result sent by the first virtual device in response to the query information is obtained, where the login result is a result of the first virtual device logging in based on the second script information and the verification code.

[0064] After the control device sends the login control instruction including the verification code to the first virtual device, it may send query information of the application program interface information to the first virtual device.

[0065] The first virtual device can send interface information to the control device. For example, the control device's C4 service can query the first virtual device at preset intervals whether the application interface contains the "SMS verification code sent" element. The first virtual device then sends the query application interface element to the control device. If the query finds that the application interface element contains the "SMS verification code sent" element, the time the verification code was sent is recorded. The C4 service can query the application interface at preset intervals whether it contains the "Homepage interface after successful login" element and whether it contains the "Login failed" element.

[0066] If the "Homepage after successful login" element is found, the SMS verification result is recorded as successful and a logout control command is sent to the first virtual device. The application interface is checked every preset period to see if it contains the "Logout" element. After logging out, the C4 service notifies the C3 service that the simulation result was successful.

[0067] This makes it easier to manage business applications that have successfully logged in, and to troubleshoot problems with business applications that have failed to log in.

[0068] Optionally, after obtaining a login result of the first virtual device logging in based on the second script information and the verification code, the method further includes: When it is determined according to the login result that the number of times that the application fails to log in to the first virtual device reaches a preset number, an alarm message is output.

[0069] If the number of failed login attempts reaches the preset number, an alarm will be output.

[0070] For example, in the above example, if the C4 service finds the "login failure" element on the first virtual device, it records the SMS verification result as failure and initiates the "SMS login" control request again; if the C4 service finds that the application of the first virtual device fails to log in via SMS multiple times in a row, it stops testing on the device, issues an alarm, and informs the C3 service of the simulation results.

[0071] This makes it easier to troubleshoot problems with business applications that fail to log in.

[0072] Optionally, after obtaining a login result of the first virtual device logging in based on the second script information and the verification code, the method further includes: When it is determined based on the login result that the number of times the application has failed to log in to the first virtual device reaches a preset number, and the interval between sending the verification code reaches a preset time length, the second token is released, and the second token is obtained by other virtual devices in the at least one virtual device except the first virtual device.

[0073] If the first virtual device fails to log into the application a preset number of times (for example, three consecutive login failures), the control device's C3 service configures a token release time based on the SMS login verification code resend interval. After a preset time interval between verification code resends (i.e., the resend interval countdown expires), the token is released again for virtual devices supporting the service to contend for. The first virtual device no longer competes for the token.

[0074] The virtual device only competes for the appid in the application configuration table it supports once. When all supported appids are simulated, no more competition for the appid business token is performed.

[0075] Through the above method, in the case of multiple consecutive login failures, there is no need to compete for tokens, which reduces the interference caused by the application program that fails to log in or the virtual device itself, and can improve the efficiency of SMS login function verification.

[0076] In order to facilitate understanding of the above method, specific embodiments are given below as examples.

[0077] The SMS login verification system includes: terminal device (i.e., a physical mobile phone with a SIM card inserted), control device (i.e., a cloud service control terminal), virtual device (i.e., a set of cloud service simulation terminals (including: N1 cloud PCs and N2 cloud phones)). The system architecture is as follows: Figure 3 shown.

[0078] like Figure 4 As shown in Table 3, the control device (also called the cloud service control terminal, referred to as C module) is pre-configured with the business application information that needs to be perceived, including: business application number (appid), business application name (appname), SMS verification code retransmission interval (apptime), for example: appid = 0001, appname = A, apptime = 65s; appid = 0002, appname = B, apptime = 180s..., as shown in Table 3: Table 3 appid appname apptime 0001 Application A 65s 0002 Application B 180s 0003 Application C 120s 0004 Application D 120s 0005 Application E 120s 0006 Application F 180s The C2 service receives the initial registration / addition / deletion information sent by the A1 service of the virtual device (also called the cloud service simulation end, referred to as the A module) in real time. The information includes: appid, appname, cloudid (cloud service simulation end number), cloudtype (virtual device type: cloud PC, cloud phone), and matches it with the pre-configured business application information of the control device. It stores and updates the generated business application device list in real time, as shown in Table 1.

[0079] In its initial state, the C3 service generates an initial global simulation list based on the business application device list in the C2 service, including appID, cloudID, and cloudtype. Each simulation round is considered complete when all tasks in the global simulation list are completed. Before the next simulation round, the initial global simulation list is generated based on the latest business application device list in the C2 service and the simulation begins again.

[0080] The C3 service sends a notification to all virtual devices to start the simulation execution and releases the token of each appID. The A2 service of each virtual device initiates a token competition operation with the C3 service based on the appIDs supported by itself in the application configuration table.

[0081] After the C3 service obtains the token for APPID=1 (Application A) from the A2 service of the virtual device with Cloud ID=10002 and cloudtype=Cloud Phone, it sends a service simulation start command and SMS verification code login simulation script for APPID=1 to the device with Cloud ID=10002. The SMS verification code login simulation script for the same application service differs depending on the cloud type=Cloud Phone / Cloud PC. The script is selectively delivered based on the Cloud ID and cloud type.

[0082] The C4 service interacts with the A2 service to perform a simulated startup, sending a cloud phone type simulation script for Application A to the A2 service of the virtual device with Cloud ID 10002. The virtual device with Cloud ID 10002 and the A2 service with APP ID 1 execute the simulated command and script to access the SMS verification code login interface. The user enters their phone number and clicks "Send verification code." The physical phone with the SIM card receives the SMS verification code and sends it to the control device. The C4 service queries the application interface every 200ms to see if it contains a "SMS verification code sent" element. If so, it records the time the verification code was sent.

[0083] The C4 service records the time when the device with Cloud ID=10002 and the application with APPID=1 sends the SMS verification code, and queries the C1 service for the SMS verification code with APPID=1 and the closest time to the SMS verification code sending time. After finding the code, it sends the input SMS verification code and login control commands and scripts to the application with Cloud ID=10002 and APPID=1. The device with Cloud ID=10002 executes the simulated SMS verification code login process of the application with APPID=1. The C4 service queries the application interface every 200ms whether it contains the "home page interface after successful login" element, and queries the application interface every 200ms whether it contains the "login failure" element.

[0084] If the C4 service finds the "Homepage after successful login" element, it records the SMS verification result as successful and sends a logout control command to the device with Cloud ID = 10002 and the application with APP ID = 1. Every 200ms, the C4 service checks the application interface for the "Logout" element. After logging out, the C4 service notifies the C3 service of the successful simulation result.

[0085] The C3 service configures the token release time based on the apptime SMS verification code resend interval in the control device. After the resend interval countdown ends, the token of the application with APPID=1 is released again for module A supporting this service to compete for simulation tasks. The device with Cloud ID=10002 no longer competes for the token.

[0086] When all appID & cloudID simulation items in the global simulation task list are marked complete, the current round of simulation is completed. The C3 service queries the C2 service to generate the latest initialized global simulation task list and starts the next round of simulation.

[0087] If the virtual device adds business application information during the initialization global task list simulation execution process, the C2 service will not update the initialization global task list and will not simulate the business in this round. Figure 5 shown.

[0088] If the virtual device deletes the business application information during the simulation execution of the initialization global task list, the C2 service will update the information in real time to generate the business application device list and notify the C3 service to update the initialization global task list. It should be noted that if the appid&cloudid simulation item has been marked as completed, the simulation result will not be changed. If the simulation item is not marked as completed, the simulation item will be deleted. Figure 6 shown.

[0089] When all appID & cloudID simulation items in the global simulation task list are marked complete, the current round of simulation is completed. The C3 service queries the C2 service to generate the latest initialized global simulation task list and starts the next round of simulation.

[0090] See also Figure 7 , Figure 7 This application provides a verification method for SMS login function, which is executed by a terminal device provided with a SIM card. The method includes: Step 701: Receive an application message sent by at least one virtual device, wherein the message is sent by the at least one virtual device in response to a first login control instruction and first script information sent by a control device, the at least one virtual device including a first virtual device, and the message includes a verification code; Step 702: Send the application program's message to the control device.

[0091] The terminal device may be referred to as a user device, for example, a mobile phone.

[0092] The terminal device is equipped with a SIM card and is capable of receiving application login verification codes sent by virtual devices. The terminal device sends the received application message (including the verification code and application identifier) from at least one virtual device to the control device. The control device interacts with the virtual device to perform a simulated SMS login operation.

[0093] The specific implementation process can be found in the description of the corresponding embodiment on the control device side, which will not be repeated here.

[0094] See also Figure 8 , Figure 8 This application provides a verification method for SMS login function, which is executed by a first virtual device and includes: Step 801: Receive a first login control instruction and first script information sent by a control device; Step 802: Displaying a login interface of an application based on the first login control instruction and the first script information, and sending a verification code to the terminal device based on the SIM number of the terminal device; Step 803: Receive a second login control instruction and second script information sent by the control device, where the second login control instruction includes the verification code; Step 804: Based on the login interface and the verification code, perform a login operation on the interface of the application.

[0095] The first virtual device is any one of the at least one virtual device. The first virtual device receives a first login control instruction and a first script message sent by the control device, enters a login interface according to the first script message and the first login control instruction, enters a SIM number of the terminal device into the login interface, and sends a login verification code to the SIM number.

[0096] When the login verification code sent by the control device is obtained, the verification code is input into the login interface according to the second script information, and the login operation is performed, that is, the account of the application is logged in.

[0097] Optionally, after performing a login operation on the interface of the application, the method further includes: receiving query information of the application interface sent by the control device; In response to the query information, a login result is sent to the control device.

[0098] After receiving the query information sent by the control device, the first virtual device may send a login result to the control device. The login result may include a successful login or a failed login. In the case of a failed login, the reason for the failed login may also be included.

[0099] The specific implementation process can be found in the description of the corresponding embodiment on the control device side, which will not be repeated here.

[0100] In the embodiment of the present application, a cloud service control terminal is used to connect N1 cloud PCs and N2 cloud phones via the Internet, and proprietary hardware is connected to physical mobile phones via wired data cables. Since the cloud service runs stably and is easy to maintain, it can solve the problem of instability of dedicated hardware and real mobile phones after long-term operation.

[0101] Using a real mobile phone with a SIM card inserted, the SMS login verification code sent by the Cloud PC business application client and Cloud Mobile App client is captured and sent to the Cloud Service Control terminal. The SMS verification code processing service on the Cloud Service Control terminal then identifies, matches, and stores the service name within the SMS message. The Business Application Simulation Control Service then queries the corresponding application verification code and initiates SMS verification code login control with it to the Cloud PC business application client and Cloud Mobile App client. The Cloud PC business application client and Cloud Mobile App client execute the login operation, and the Business Application Simulation Control Service monitors the results. This reduces device usage and improves resource utilization.

[0102] The cloud service control terminal is used to centrally obtain and parse SMS verification codes to match the cloud service simulation terminal and application, and send a verification code login control command with the SMS verification code to the cloud PC, which solves the defect of being unable to carry out PC client business application SMS verification code login.

[0103] See also Figure 9 , Figure 9 This is a schematic diagram of a verification device for SMS login function provided by an embodiment of the present application, which is applied to control devices such as Figure 9 As shown, the verification device 900 of the SMS login function includes: A first sending module 901 is configured to send a first login control instruction and first script information of an application to a first virtual device; A first receiving module 902 is configured to receive a message from the application sent by a terminal device, where the message includes a verification code; A second sending module 903 is configured to send a second login control instruction and second script information of the application to the first virtual device, where the second login control instruction includes the verification code; The acquisition module 904 is configured to acquire a login result of the first virtual device based on the second script information and the verification code.

[0104] Optionally, the first sending module includes: A first acquisition submodule is configured to acquire a service application device list, wherein the service application device list includes information of at least one virtual device and information of an application installed on the at least one virtual device, wherein the at least one virtual device includes the first virtual device; a releasing submodule, configured to release a first token to the at least one virtual device; The first sending submodule is configured to send a first login control instruction and first script information of the application to the first virtual device when the first virtual device obtains the first token.

[0105] Optionally, the device further comprises: A second receiving module is configured to receive service application information sent by the at least one virtual device, wherein the service application information includes application program information and virtual device information; A generating module, configured to generate the service application device list based on the service application information and a pre-configured service application list; The device further comprises: a processing module, configured to not update the service application device list when receiving indication information of newly added first service application information sent by the second virtual device; The deleting module is configured to delete the second service application information from the service application device list upon receiving instruction information for deleting the second service application information sent by the second virtual device.

[0106] Optionally, the device further comprises: An adding module is used to add a mark to the business information corresponding to the first virtual device in the business application device list according to the login result, wherein the mark is used to indicate the verification status of the business information of the first virtual device.

[0107] Optionally, the acquisition module includes: A second sending submodule, configured to send query information of the application interface to the first virtual device; The second acquisition submodule is configured to acquire a login result sent by the first virtual device in response to the query information, where the login result is a result of the first virtual device logging in based on the second script information and the verification code.

[0108] Optionally, the device further comprises: The output module is configured to output an alarm message when it is determined, based on the login result, that the number of times the application fails to log in to the first virtual device reaches a preset number.

[0109] Optionally, the device further comprises: A release module is used to release a second token when it is determined based on the login result that the number of times the application has failed to log in to the first virtual device has reached a preset number and the interval between sending the verification code has reached a preset time length. The second token is obtained by other virtual devices in the at least one virtual device except the first virtual device.

[0110] The verification device of SMS login function can realize Figure 2 The various processes implemented in the method embodiment can achieve the same technical effect, and to avoid repetition, they will not be described here.

[0111] See also Figure 10 , Figure 10 This is a schematic diagram of a verification device for SMS login function provided by an embodiment of the present application, which is applied to a terminal device such as Figure 10 As shown, the verification device 1000 for the SMS login function includes: A receiving module 1001 is configured to receive a message from an application program sent by at least one virtual device, where the at least one virtual device includes a first virtual device, and the message includes a verification code; The sending module 1002 is configured to send a message of the application to a control device.

[0112] The verification device of SMS login function can realize Figure 7 The various processes implemented in the method embodiment can achieve the same technical effect, and to avoid repetition, they will not be described here.

[0113] See also Figure 11 , Figure 11 This is a schematic diagram of a structure of a verification device for SMS login function provided by an embodiment of the present application, which is applied to a first virtual device, such as Figure 11 As shown, the verification device 1100 of the SMS login function includes: A first receiving module 1101 is configured to receive a first login control instruction and first script information sent by a control device; A first sending module 1102 is configured to display a login interface of an application based on the first login control instruction and the first script information, and to send a verification code to the terminal device based on the SIM number of the terminal device; A second receiving module 1103 is configured to receive a second login control instruction and a second script information sent by the control device, where the second login control instruction includes the verification code; The execution module 1104 is configured to execute a login operation on the interface of the application program based on the login interface and the verification code.

[0114] Optionally, the device further comprises: a third receiving module, configured to receive query information of the application interface sent by the control device; The second sending module is configured to send a login result to the control device in response to the query information.

[0115] The verification device of SMS login function can realize Figure 8 The various processes implemented in the method embodiment can achieve the same technical effect, and to avoid repetition, they will not be described here.

[0116] It should be noted that the electronic device provided in the embodiment of this application is a verification device capable of performing the above-mentioned SMS login function. Therefore, all implementation methods in the embodiment of the verification method for the above-mentioned SMS login function are applicable to the electronic device and can achieve the same or similar beneficial effects. To avoid repetition, this embodiment will not be described in detail.

[0117] The present application also provides an electronic device. Since the principle of solving the problem by the electronic device is similar to the verification method of the SMS login function of the control device side in the present application embodiment, the implementation of the electronic device can refer to the implementation of the method, and the repeated parts are not repeated.

[0118] like Figure 12 As shown, when the electronic device of the embodiment of the present application is a control device, the electronic device includes: a processor 1200, which is used to read the program in the memory 1220 and execute the following process: Sending a first login control instruction and first script information of the application to the first virtual device via the transceiver 1210; Receiving a message of the application sent by a terminal device, wherein the message of the application includes a verification code; Sending a second login control instruction and second script information of the application to the first virtual device, where the second login control instruction includes the verification code; Obtain a login result of the first virtual device logging in based on the second script information and the verification code.

[0119] The transceiver 1210 is configured to receive and send data under the control of the processor 1200 .

[0120] Among them, Figure 12 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 1200 and memory represented by memory 1220. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are all well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 1210 may be a plurality of components, i.e., a transmitter and a transceiver, providing a unit for communicating with various other devices on a transmission medium. The processor 1200 is responsible for managing the bus architecture and general processing, and the memory 1220 may store data used by the processor 1200 when performing operations.

[0121] Optionally, the processor 1200 is configured to read a program in the memory 1220 and execute the sending of the first login control instruction and the first script information of the application to the first virtual device, including: Acquire a service application device list, the service application device list including information of at least one virtual device and information of an application installed on the at least one virtual device, the at least one virtual device including the first virtual device; releasing a first token to the at least one virtual device; When the first virtual device obtains the first token, a first login control instruction and first script information of the application are sent to the first virtual device.

[0122] Optionally, the processor 1200 is configured to read a program in the memory 1220 and further configured to perform the following steps: Receiving business application information sent by the at least one virtual device, the business application information including application program information and virtual device information; generating the service application device list based on the service application information and a pre-configured service application list; When receiving the indication information of the newly added first service application information sent by the second virtual device, not updating the service application device list; When instruction information for deleting the second service application information is received from the second virtual device, the second service application information is deleted from the service application device list.

[0123] Optionally, the processor 1200 is configured to read a program in the memory 1220 and further configured to perform the following steps: According to the login result, a mark is added to the service information corresponding to the first virtual device in the service application device list, where the mark is used to indicate a verification status of the service information of the first virtual device.

[0124] Optionally, the processor 1200 is configured to read a program in the memory 1220 and further configured to perform the following steps: Sending query information of the application interface to the first virtual device; A login result sent by the first virtual device in response to the query information is obtained, where the login result is a result of the first virtual device logging in based on the second script information and the verification code.

[0125] Optionally, the processor 1200 is configured to read a program in the memory 1220 and further configured to perform the following steps: When it is determined according to the login result that the number of times that the application fails to log in to the first virtual device reaches a preset number, an alarm message is output.

[0126] Optionally, the processor 1200 is configured to read a program in the memory 1220 and further configured to perform the following steps: When it is determined based on the login result that the number of times the application has failed to log in to the first virtual device reaches a preset number, and the interval between sending the verification code reaches a preset time length, the second token is released, and the second token is obtained by other virtual devices in the at least one virtual device except the first virtual device.

[0127] The electronic device provided in the embodiment of the present application can execute the method embodiment corresponding to the above-mentioned control device side. Its implementation principle and technical effects are similar, and this embodiment will not be repeated here.

[0128] When the electronic device in the embodiment of the present application is a first virtual device, the electronic device includes: a processor 1200 configured to read a program in a memory 1220 and execute the following process: Receiving, through the transceiver 1210, a first login control instruction and first script information sent by the control device; Displaying a login interface of an application based on the first login control instruction and the first script information, and sending a verification code to the terminal device based on the SIM number of the terminal device; receiving a second login control instruction and second script information sent by the control device, where the second login control instruction includes the verification code; Based on the login interface and the verification code, a login operation is performed on the interface of the application.

[0129] Optionally, the processor 1200 is configured to read a program in the memory 1220 and further configured to perform the following steps: receiving query information of the application interface sent by the control device; In response to the query information, a login result is sent to the control device.

[0130] The electronic device provided in the embodiment of the present application can execute the method embodiment corresponding to the above-mentioned first virtual device side. Its implementation principle and technical effects are similar, and this embodiment will not be repeated here.

[0131] The embodiment of the present application also provides an electronic device. Since the principle of solving the problem by the electronic device is similar to the verification method of the SMS login function on the terminal device side in the embodiment of the present application, the implementation of the electronic device can refer to the implementation of the method, and the repeated parts will not be repeated. Figure 13 As shown, the electronic device includes: a processor 1300, which is used to read the program in the memory 1320 and execute the following processes: receiving, through the transceiver 1310, a message of an application sent by at least one virtual device, wherein the at least one virtual device includes a first virtual device, and the message includes a verification code; Sending a message of the application to the control device.

[0132] The transceiver 1310 is configured to receive and send data under the control of the processor 1300; User interface 1330 is used for interacting with users.

[0133] Among them, Figure 13In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 1300 and memory represented by memory 1320. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are all well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 1310 may be a plurality of components, i.e., including a transmitter and a transceiver, providing a unit for communicating with various other devices on a transmission medium. The processor 1300 is responsible for managing the bus architecture and general processing, and the memory 1320 may store data used by the processor 1300 when performing operations.

[0134] The electronic device provided in the embodiment of the present application can execute the method embodiment corresponding to the above-mentioned terminal device side. Its implementation principle and technical effects are similar, and this embodiment will not be repeated here.

[0135] The present application also provides a computer-readable storage medium having a computer program stored thereon. When executed by a processor, the computer program implements the various steps of the embodiment of the verification method for SMS login function described above, achieving the same technical effect. To avoid repetition, the details are not described here. The computer-readable storage medium may be, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0136] An embodiment of the present application also provides a computer program product, including computer instructions. When the computer instructions are executed by a processor, the various processes of the above-mentioned method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, they will not be repeated here.

[0137] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0138] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a more preferred embodiment. Based on this understanding, the technical solution of this application, or the part that contributes to the existing technology, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of this application.

[0139] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms without departing from the purpose of this application and the scope of protection of the claims, all of which are within the protection of this application.

Claims

1. A verification method for SMS login function, characterized in that: Executed by a control device, the method includes: Sending a first login control instruction and first script information of the application program to the first virtual device; Receiving a message of the application sent by a terminal device, wherein the message of the application includes a verification code; Sending a second login control instruction and second script information of the application to the first virtual device, where the second login control instruction includes the verification code; Obtain a login result of the first virtual device logging in based on the second script information and the verification code.

2. The method according to claim 1, characterized in that The sending of the first login control instruction and the first script information of the application to the first virtual device includes: Acquire a service application device list, the service application device list including information of at least one virtual device and information of an application installed on the at least one virtual device, the at least one virtual device including the first virtual device; releasing a first token to the at least one virtual device; When the first virtual device obtains the first token, a first login control instruction and first script information of the application are sent to the first virtual device.

3. The method according to claim 2, characterized in that Before obtaining the service application device list, the method further includes: Receiving business application information sent by the at least one virtual device, the business application information including application program information and virtual device information; generating the service application device list based on the service application information and a pre-configured service application list; After obtaining the service application device list, the method further includes: When receiving the indication information of the newly added first service application information sent by the second virtual device, not updating the service application device list; When instruction information for deleting the second service application information is received from the second virtual device, the second service application information is deleted from the service application device list.

4. The method according to claim 2 or 3, characterized in that After obtaining the login result of the first virtual device based on the second script information and the verification code, the method further includes: According to the login result, a mark is added to the service information corresponding to the first virtual device in the service application device list, where the mark is used to indicate a verification status of the service information of the first virtual device.

5. The method according to claim 1, characterized in that The obtaining a login result of the first virtual device based on the second script information and the verification code includes: Sending query information of the application interface to the first virtual device; A login result sent by the first virtual device in response to the query information is obtained, where the login result is a result of the first virtual device logging in based on the second script information and the verification code.

6. The method according to claim 1 or 5, characterized in that After obtaining the login result of the first virtual device based on the second script information and the verification code, the method further includes: When it is determined according to the login result that the number of times that the application fails to log in to the first virtual device reaches a preset number, an alarm message is output.

7. The method according to claim 1, characterized in that After obtaining the login result of the first virtual device based on the second script information and the verification code, the method further includes: When it is determined based on the login result that the number of times the application has failed to log in to the first virtual device reaches a preset number, and the interval between sending the verification code reaches a preset time length, the second token is released, and the second token is obtained by other virtual devices in at least one virtual device except the first virtual device.

8. A verification method for SMS login function, characterized in that: The method is executed by a terminal device provided with a SIM card, and includes: receiving a message of an application sent by at least one virtual device, wherein the at least one virtual device includes a first virtual device, and the message includes a verification code; A message of the application is sent to the control device.

9. A verification method for SMS login function, characterized in that: Executed by a first virtual device, the method includes: Receiving a first login control instruction and first script information sent by a control device; Displaying a login interface of an application based on the first login control instruction and the first script information, and sending a verification code to the terminal device based on the SIM number of the terminal device; receiving a second login control instruction and second script information sent by the control device, where the second login control instruction includes the verification code; Based on the login interface and the verification code, a login operation is performed on the interface of the application.

10. The method according to claim 9, characterized in that After the login operation is performed on the interface of the application, the method further includes: receiving query information of the application interface sent by the control device; In response to the query information, a login result is sent to the control device.

11. A verification device for SMS login function, characterized in that: Applied to control equipment, including: A first sending module, configured to send a first login control instruction and first script information of an application program to a first virtual device; A first receiving module is configured to receive a message from the application sent by a terminal device, wherein the message from the application includes a verification code; A second sending module, configured to send a second login control instruction and second script information of the application to the first virtual device, where the second login control instruction includes the verification code; An acquisition module is used to obtain a login result of the first virtual device based on the second script information and the verification code.

12. A verification device for SMS login function, characterized in that: Applied to terminal equipment, including: A receiving module, configured to receive a message of an application sent by at least one virtual device, wherein the at least one virtual device includes a first virtual device, and the message includes a verification code; The sending module is used to send the message of the application to the control device.

13. A verification device for SMS login function, characterized in that: Applied to the first virtual device, including: A first receiving module, configured to receive a first login control instruction and first script information sent by a control device; A first sending module, configured to display a login interface of an application based on the first login control instruction and the first script information, and send a verification code to the terminal device based on the SIM number of the terminal device; A second receiving module is configured to receive a second login control instruction and a second script information sent by the control device, wherein the second login control instruction includes the verification code; An execution module is used to perform a login operation on the interface of the application based on the login interface and the verification code.

14. An electronic device, characterized in that: include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the program implements the steps of the SMS login function verification method according to any one of claims 1 to 7; or implements the steps of the SMS login function verification method according to claim 8; Implement the steps of the verification method of the SMS login function as described in any one of claims 9 to 10.

15. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by the processor, the computer program implements the steps of the verification method for the SMS login function according to any one of claims 1 to 7; or implements the steps of the verification method for the SMS login function according to claim 8; Implement the steps of the verification method of the SMS login function as described in any one of claims 9 to 10.

16. A computer program product, characterized in that The method comprises computer instructions, which, when executed by a processor, implement the steps of the verification method for the SMS login function according to any one of claims 1 to 7; or implement the steps of the verification method for the SMS login function according to claim 8; Implement the steps of the verification method of the SMS login function as described in any one of claims 9 to 10.

Images