Verification method, device, equipment, medium and program product for short message login function

Abstract

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

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of Internet, and particularly relates to a short message login function verification method and device, equipment, medium and program product. BACKGROUND

[0002] The short message login function availability perception of the current business application is realized by a set of simulation devices composed of entity special hardware devices, entity commercial mobile phones and subscriber identity modules (SIM) cards in a 1:1:1 resource ratio.

[0003] Among them, the special hardware is connected with the entity commercial mobile phone inserted with the SIM card through a data line, and sends control instructions to the mobile phone through a wired mode, controls the mobile phone to send a short message verification code and performs a short message login operation according to the verification code, so as to realize the monitoring of the short message login verification availability.

[0004] The monitoring system of the short message login function of the above business application needs to occupy more hardware resources, and the resource utilization rate is low. SUMMARY

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

[0006] To solve the above technical problems, the present application is implemented as follows:

[0007] In a first aspect, the embodiments of the present application provide a short message login function verification method, which is executed by a control device, and the method comprises the following steps:

[0008] sending a first login control instruction and first script information of an application program to a first virtual device;

[0009] receiving a message of the application program sent by a terminal device, wherein the message of the application program comprises a verification code;

[0010] 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 the verification code;

[0011] obtaining a login result of the first virtual device based on the second script information and the verification code.

[0012] Optionally, the step of sending the first login control instruction and the first script information of the application program to the first virtual device comprises:

[0013] obtaining a service application device list, the service application device list comprising information of at least one virtual device and information of an application installed in the at least one virtual device, the at least one virtual device comprising the first virtual device;

[0014] releasing a first token to the at least one virtual device;

[0015] in a case where the first virtual device obtains the first token, sending a first login control instruction and first script information of the application to the first virtual device.

[0016] Optionally, before the obtaining the service application device list, the method further comprises:

[0017] receiving service application information sent by the at least one virtual device, the service application information comprising information of an application and information of a virtual device;

[0018] generating the service application device list based on the service application information and a pre-configured service application list;

[0019] in a case where receiving indication information of adding first service application information sent by a second virtual device, not updating the service application device list;

[0020] after the obtaining the service application device list, the method further comprises:

[0021] in a case where receiving indication information of deleting second service application information sent by a second virtual device, deleting the second service application information from the service application device list.

[0022] Optionally, after the obtaining a login result of the first virtual device logging in based on the second script information and the verification code, the method further comprises:

[0023] according to the login result, adding a mark to service information corresponding to the first virtual device in the service application device list, the mark being used to indicate a verification state of the service information of the first virtual device.

[0024] Optionally, the obtaining a login result of the first virtual device logging in based on the second script information and the verification code comprises:

[0025] sending query information of an interface of the application to the first virtual device;

[0026] obtaining a login result sent by the first virtual device in response to the query information, the login result being a result of the first virtual device logging in based on the second script information and the verification code.

[0027] Optionally, after the login result of the first virtual device logging in based on the second script information and the verification code is acquired, the method further includes:

[0028] In a case where it is determined according to the login result that the number of login failures of the application program on the first virtual device reaches a preset number of times, alarm information is output.

[0029] Optionally, after the login result of the first virtual device logging in based on the second script information and the verification code is acquired, the method further includes:

[0030] In a case where it is determined according to the login result that the number of login failures of the application program on the first virtual device reaches a preset number of times, and the interval between the sending time of the verification code reaches a preset time length, a second token is released, the second token being used for acquisition by a virtual device other than the first virtual device among the at least one virtual device.

[0031] In a second aspect, an embodiment of the present application provides a verification method of a short message login function, executed by a terminal device, and the method includes:

[0032] Receiving a message of an application program sent by at least one virtual device, the at least one virtual device including a first virtual device, the message including a verification code;

[0033] Sending the message of the application program to a control device.

[0034] In a third aspect, an embodiment of the present application provides a verification method of a short message login function, executed by a first virtual device, and the method includes:

[0035] Receiving a first login control instruction and first script information sent by a control device;

[0036] Displaying a login interface of an application program based on the first login control instruction and the first script information, and sending a verification code to a terminal device based on a SIM number of the terminal device;

[0037] Receiving a second login control instruction and second script information sent by the control device, the second login control instruction including the verification code;

[0038] Performing a login operation on an interface of the application program based on the login interface and the verification code.

[0039] Optionally, after the login operation on the interface of the application program is performed, the method further includes:

[0040] Receiving query information of the interface of the application program sent by the control device;

[0041] In response to the query information, a login result is sent to the control device.

[0042] In a fourth aspect, an embodiment of the present application provides a verification apparatus of an SMS login function, applied to a control device, and comprising:

[0043] A first sending module is configured to send a first login control instruction and first script information of an application to a first virtual device;

[0044] A first receiving module is configured to receive a message of the application sent by a terminal device, wherein the message of the application comprises a verification code;

[0045] A second sending module is configured to send a second login control instruction and second script information of the application to the first virtual device, wherein the second login control instruction comprises the verification code;

[0046] A obtaining module is configured to obtain a login result of the first virtual device based on the second script information and the verification code.

[0047] In a fifth aspect, an embodiment of the present application provides a verification apparatus of an SMS login function, applied to a terminal device, and comprising:

[0048] A receiving module is configured to receive a message of an application sent by at least one virtual device, wherein the at least one virtual device comprises a first virtual device, and the message comprises a verification code;

[0049] A sending module is configured to send the message of the application to a control device.

[0050] In a sixth aspect, an embodiment of the present application provides a verification apparatus of an SMS login function, applied to a first virtual device, and comprising:

[0051] A first receiving module is configured to receive a first login control instruction and first script information sent by a control device;

[0052] A first sending module is 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 a terminal device based on a SIM number of the terminal device;

[0053] A second receiving module is configured to receive a second login control instruction and second script information sent by the control device, wherein the second login control instruction comprises the verification code;

[0054] An executing module is configured to perform a login operation in an interface of the application based on the login interface and the verification code.

[0055] In a seventh aspect, an electronic device is provided, which includes a processor, a memory, and a program stored in the memory and executable on the processor, and when the program is executed by the processor, the steps of the verification method of the short message login function are implemented.

[0056] In an eighth aspect, a computer readable storage medium is provided, which stores a computer program, and when the computer program is executed by a processor, the steps of the verification method of the short message login function are implemented.

[0057] In a ninth aspect, a computer program product is provided, which includes computer instructions, and when the computer instructions are executed by a processor, the steps of the verification method of the short message login function are implemented.

[0058] In the embodiments of the present application, the control device obtains the information of the application program by interacting with the terminal device, and controls the virtual device to log in the application program by interacting with the virtual device. The monitoring of the short message login function is realized through the interaction among the control device, the terminal device and the virtual device, the occupation of hardware resources is reduced, and the resource utilization rate is improved. BRIEF DESCRIPTION OF DRAWINGS

[0059] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed in the description of the embodiments of the present application will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0060] Figure 1 is a structural diagram of a short message login function verification system provided by the embodiments of the present application;

[0061] Figure 2 is one of the flowcharts of the short message login function verification method provided by the embodiments of the present application;

[0062] Figure 3 is an architecture diagram of a short message login function verification system provided by the embodiments of the present application;

[0063] Figure 4 is the second flowchart of the short message login function verification method provided by the embodiments of the present application;

[0064] Figure 5 is a processing method flowchart for adding business application information provided by the embodiments of the present application;

[0065] Figure 6 is a processing method flowchart for deleting business application information provided by the embodiments of the present application;

[0066] Figure 7 Figure 3 is a flowchart of a third method for verifying a short message login function according to an embodiment of the present application;

[0067] Figure 8 Figure 4 is a flowchart of a fourth method for verifying a short message login function according to an embodiment of the present application;

[0068] Figure 9 Figure 5 is a structural schematic diagram of a verification device for a short message login function according to an embodiment of the present application;

[0069] Figure 10 Figure 6 is a structural schematic diagram of a verification device for a short message login function according to an embodiment of the present application;

[0070] Figure 11 Figure 7 is a structural schematic diagram of a verification device for a short message login function according to an embodiment of the present application;

[0071] Figure 12 Figure 8 is a structural schematic diagram of an electronic device according to an embodiment of the present application;

[0072] Figure 13 Figure 9 is a structural schematic diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0073] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of the present application.

[0074] Short message login verification is a prerequisite for various mobile phone application programs (Application, APP) or personal computer (Personal Computer, PC) client business applications to provide services to users, and is a very frequently used business function. Once the short message login function of a business application is unavailable, it will directly result in the user's inability to use the business, greatly affecting the user's perception. Therefore, the perception monitoring of business application quality, to quickly and timely find problems, solve problems, and improve user perception, is a problem that needs to be solved urgently.

[0075] The currently commonly used way is to connect and control an Android system entity commercial mobile phone with a SIM card by a data line through a special hardware device, as shown in FIG. 1. Figure 1 The above-mentioned way has the following problems:

[0076] First, the operation is unstable, the repair operation is complex, and the recovery time is long. The availability monitoring of the short message login function of the business application needs to be continuously performed. When running for a long time, the connection operation control interaction between the special hardware and the commercial mobile phone is prone to failure, and the mobile phone software may also be stuck, and the repair operation is complex.

[0077] Second, the utilization efficiency is low. A special hardware and a real mobile phone can only be deployed at one location point to perceive the short message login capability state of the local business application. When there are N provinces, at least N special hardware, N real mobile phones and N SIM cards are needed. When the business covers many provinces, the demand for physical devices is large, and the utilization rate of SIM cards is low.

[0078] Third, the perception range of the application business is limited. When monitoring the short message login function of the PC client application, the PC client is installed on a notebook computer, and the notebook computer does not have a SIM card and cannot receive a short message, so it does not have the function of monitoring the short message login function of the PC client business application.

[0079] Embodiments of the present application provide a short message login function verification method, device, equipment, medium and program product to solve the problem of low resource utilization of the monitoring system.

[0080] Referring to Figure 2 , Figure 2 is a flowchart of a short message login function verification method provided by the embodiments of the present application, executed by a control device, as shown in Figure 2 , the method comprises the following steps:

[0081] Step 201, sending a first login control instruction and first script information of an application program to a first virtual device;

[0082] Step 202, receiving a message of the application program sent by a terminal device, the terminal device being provided with a Subscriber Identification Module (SIM), the message of the application program being sent by the first virtual device in response to the first login control instruction and the first script information, and the message of the application program comprising a verification code;

[0083] Step 203, sending a second login control instruction and second script information of the application program to the first virtual device, the second login control instruction comprising the verification code;

[0084] Step 204, obtaining a login result of the first virtual device based on the second script information and the verification code.

[0085] The verification method of the short message login function is executed by a system including: 1 entity user terminal (also referred to as user equipment) provided with a SIM card, 1 set of control equipment (also referred to as a cloud service control end), and 1 group of virtual equipment (also referred to as a cloud service simulation end), which includes one or more virtual equipment, and the first virtual equipment is one of the virtual equipment.

[0086] Since the virtual equipment (for example, a cloud phone or a cloud PC) installed with the APP application does not have a communication module with a SIM card inserted, it cannot receive the short message verification code sent by the short message login verification application platform. Therefore, an entity phone with a SIM card inserted is required to receive the business application.

[0087] Meanwhile, a short message code collection service needs to be installed on the user terminal (such as a mobile phone), which reads the updated short message in the user terminal in real time and pushes the short message information to the short message verification code of the control equipment in a message queue mode through the wireless network (wifi / wireless network) connected by the user terminal. The short message code collection service pushes the short message information to the control equipment (i.e., the cloud service control end), and the content of the short message information includes: the short message receiving mobile phone number, the short message receiving time, the short message sending platform number, and the short message content text.

[0088] Based on the above system, the control equipment sends a first login control instruction of an application program and first script information for executing the login control instruction to the first virtual equipment. The first virtual equipment can enter the login interface of the application program based on the first login control instruction and the first script information, and send a message of the application program to the entity terminal equipment with the SIM card, which can include the identification of the application program and the verification code for logging into the account of the application program.

[0089] The entity terminal equipment sends the obtained message of the application program (including the verification code and the identification of the application program) to the control equipment, and the control equipment sends a second login control instruction of the application program and second script information to the first virtual equipment again based on the identification of the application program.

[0090] The first virtual equipment enters the login interface of the application program based on the second script information and inputs the verification code carried by the second login control instruction. If the login is successful, a prompt information of login success is displayed, and if the login fails, a related prompt information of login failure is displayed.

[0091] The control equipment can obtain the login result of the first virtual equipment by sending a query message to the first virtual equipment, or the first virtual equipment can actively feed back the login result to the control equipment.

[0092] The embodiment of the application adopts one set of cloud service control end to access control N1 (an integer greater than 0) cloud PC clients and N2 (an integer greater than 0) cloud mobile APPs through the Internet to simulate the SMS verification code login availability of multi-type business applications and monitor the results. The above method can achieve the following beneficial effects:

[0093] I. A special hardware wired connection entity mobile phone is used, N1+N2 special hardware, N1+N2 mobile phones, and N1+N2 SIM card resources are used to develop business application SMS verification code login function monitoring means. Using the method of the application, N1+N2-1 hardware resource requirements can be reduced. One mobile phone and one SIM card can replace the need for N1+N2 mobile phones and SIM card resources, greatly improving resource utilization and reducing costs.

[0094] For example, the wired connection method requires an investment of 52,000 yuan* (N1+N2), and the present application can reduce the cost to 22,000 yuan* (N1+N2), a 60% reduction in cost. According to the current network minimum configuration N1+N2=62, 1.86 million yuan can be saved. The larger the deployment point requirement, the more cost savings. And reduce the resources of the monitoring system deployment, improve the resource utilization and stability.

[0095] II. Through the special hardware wired connection entity mobile phone method, when there is a fault, personnel need to go to the deployment room site to check and troubleshoot, and the problem solving effectiveness is low. Since the cloud deployment method is used, one set of cloud service control end interacts with the cloud PC and the cloud mobile phone through the Internet, and hardware and software problems can be solved through remote access, improving the effectiveness of problem solving.

[0096] III. It is convenient to quickly expand the cloud service simulation end and increase the simulation point. The coverage is large, and it is easier to reflect the real perception of business applications.

[0097] Optionally, the sending of the first login control instruction and the first script information of the application program to the first virtual device comprises:

[0098] Obtaining a business application device list, the business application device list comprising information of at least one virtual device and information of an application program installed in the at least one virtual device, the at least one virtual device comprising the first virtual device;

[0099] Releasing a first token to the at least one virtual device;

[0100] In the case where the first virtual device obtains the first token, sending the first login control instruction and the first script information of the application program to the first virtual device.

[0101] Among them, the virtual device (i.e. cloud service simulation end) exists in two modes of cloud PC and cloud mobile phone. The cloud PC supports the installation of PC version application client business application software, and the cloud mobile phone supports the installation of mobile phone APP business application software. The business application installed on each virtual device may be different. Each mode of virtual device is installed with cloud service simulation end information management service (hereinafter referred to as A1 service) and business execution service (hereinafter referred to as A2 service).

[0102] Among them, A1 service performs business application support query matching according to the built-in business application configuration table at the initial installation completion and every preset time thereafter, forms and updates its own business application device list (also referred to as business application configuration table). The list can include information of the application program, such as business application number (appid) and business application name (appname), and can also include information of the virtual device corresponding to the application program. These business applications interact with the cloud service control end through the Internet at the initial installation completion or when the business application is changed, and notify the cloud service control end of the application support state. The initial registration / increase / deletion information of the virtual device (i.e. virtual device information) includes: appid, appname, cloudid (virtual device number), cloudtype (virtual device type: including cloud PC and cloud mobile phone). When initially registered, the full-amount appid row of the business application configuration table information supported by itself is sent, and only the added / deleted appid row information is sent for the increase / deletion operation.

[0103] A2 service is used to compete for business application tokens, receive and execute business execution commands and stress test scripts sent by the cloud service control end. The virtual device only competes for the appid in the application configuration table supported by itself once, and does not compete for the appid business token after all the appids supported by it are simulated.

[0104] Among them, the control device (i.e. cloud service control end) includes a short message verification code processing service (referred to as C1 service), a cloud service simulation end information pool management (referred to as C2 service), a business application short message verification code simulation allocation service (referred to as C3 service), and a business application simulation end control service (referred to as C4 service).

[0105] The C1 service realizes the receiving, storage, identification, matching, and generation of a short message verification code query table for entity mobile phone push short messages. The C1 service receives and stores the short message information pushed by the mobile short message code collection service in real time, and identifies the verification code field in the short message using existing AI technology. The pre-configured business application information list (i.e., the business application list) is matched with the short message content, the appname is identified, and if it can be matched with the appname in the pre-configured business application information, the short message appname is recorded. If it cannot be identified, the short message is marked as "invalid". The short message verification code query table is generated for the short message with the matched appname, including: appid, appname, short message receiving time, and short message verification code.

[0106] The C2 service receives the initial registration / increase / deletion / information sent by the A1 service in real time, and the information includes: appid, appname, cloudid (cloud service simulation terminal number), cloudtype (virtual device type: cloud PC, cloud mobile phone), and the pre-configured business application information list of the control device is matched, and the business application device list is stored and updated in real time, as shown in Table 1 below:

[0107] Table 1

[0108] 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

[0109] C3 service. To avoid network attacks, the business application does not allow a mobile phone to repeatedly send short message verification codes within a certain period of time when designing short message verification code login. Therefore, the same application (whether PC client or mobile phone APP) can only be executed on one virtual device within a certain period of time when using a mobile phone to log in with a short message verification code. Different applications can simultaneously use the same mobile phone to log in with a short message verification code. To ensure accuracy, the same virtual device can only execute the short message verification code login of one business application within the same period of time. The short message verification code login simulation scheme is designed to fully reflect and simulate user perception, and the above principles are followed to design the business simulation allocation service strategy.

[0110] To fully utilize the resources of the virtual device, the control device controls different virtual devices to simulate the short message verification code login process of different business applications in parallel, and at the same time, the virtual device installed with a business application performs short message verification code login simulation for the business application. The C3 service forms an initial global simulation list including appid, cloudid, and cloudtype based on the business application device list in the C2 service in the initial state. Each round of simulation is completed when all the tasks in each row of the global simulation list are completed. The latest business application device list in the C2 service is used to generate an initial global simulation list before the next round of simulation, and the simulation is started again.

[0111] Since each appid can only be simulated on one virtual device at the same time, the C3 service generates and issues a token for each appid, which can only be assigned to one virtual device at the same time. When the C3 service sends a notification to start simulation execution to all virtual devices, the token of each appid is released. The A2 service of all virtual devices initiates a token contention operation to the C3 service according to the appids supported by the application configuration table. After the A2 service of the first virtual device (any virtual device in the virtual device) contends for the token of the appid, the C3 service initiates a business simulation start command (i.e., the first login control instruction) of the appid to the first virtual device that contends for the token.

[0112] The C4 service interacts with the A2 service to perform simulation startup, sends a simulation script (i.e., the first script information) to the first virtual device, queries the state of the A2 service simulation every interval of a preset time, and queries the appid short message verification code from the C1 service. After the simulation is completed, the C3 service is notified that the simulation is completed, the appid&cloudid business state is marked as completed in the global simulation list, and the success / failure result is recorded.

[0113] In the above manner, the control device releases the token according to the business application list, which can enable each business application in the business application list to perform simulation operation, reduce omission of business applications, and achieve simulation allocation of multiple cloud service simulation ends and applications in the form of appid tokens, thereby maximizing the use of service resources.

[0114] Optionally, before the business application device list is obtained, the method further includes:

[0115] receiving business application information sent by the at least one virtual device, the business application information including information of an application program and information of a virtual device;

[0116] generating the business application device list based on the business application information and a preconfigured business application list;

[0117] After the business application device list is obtained, the method further includes:

[0118] In a case where indication information of adding first business application information sent by a second virtual device is received, the business application device list is not updated;

[0119] In a case where indication information of deleting second business application information sent by a second virtual device is received, the second business application information is deleted from the business application device list.

[0120] The control device preconfigures a list of service application information that needs to be perceived (i.e., a service application list), including a service application number (appid) and a service application name (appname), for example, appid=0001, appname=application A, appid=0002, appname=application B, appid=02, and the like, as shown in Table 2.

[0121] Table 2

[0122] appid appname 0001 Application A 0002 Application B 0003 Application C …… ……

[0123] The virtual device sends the information of the service application and the corresponding virtual device to the cloud service control end through interaction with the control device (i.e., the cloud service control end) when the service application is initially installed or changed. The control device matches the information sent by at least one virtual device with the preconfigured service application information to generate a service application device list. Based on the list, the control device sends tokens to each virtual device in a predetermined order and sends a login script and a login control instruction to the token obtaining device.

[0124] In the case of receiving the indication information of adding the first service application information, the service application device list is not updated in this round, i.e., 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 in the next round.

[0125] In the case of receiving the indication information of deleting the second service application information, the second service application information is deleted from the service application device list. If the short message login service corresponding to the second service application information has been marked as completed, the login result is not changed; if the short message 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, which can reduce the interference of adding or deleting services on the current simulation and reduce omissions.

[0126] The C3 service and the C2 service form a service application device list information resource pool, and an initial global simulation list is formed according to the resource pool information, and the task list is updated to form a simulation task list.

[0127] In the above manner, the control device releases tokens according to the service application list, which can enable each service application in the service application list to perform a simulation operation and reduce omissions.

[0128] Optionally, after the first virtual device logs in based on the second script information and the verification code, the method further includes:

[0129] According to the login result, a mark is added to the business information corresponding to the first virtual device in the business application device list, and the mark is used to indicate the verification state of the business information of the first virtual device.

[0130] After each application corresponding business application completes login, the business information is marked, for example, the verification state of the business information is completed, and the result of successful login or failed login is recorded. Based on the mark, the completion state of the application corresponding business application can be determined.

[0131] In this way, the login simulation of the business application that has not logged in is facilitated, and the problems existing in the business application that has failed to log in are investigated.

[0132] Optionally, the login result of the first virtual device based on the second script information and the verification code includes:

[0133] The control device sends the query information of the interface of the application program to the first virtual device.

[0134] The control device sends the query information of the interface of the application program to the first virtual device.

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

[0136] The first virtual device can send the interface information to the control device, for example, the C4 service of the control device queries every preset time whether the application interface contains the "SMS verification code has been sent" element, and the first virtual device sends the queried application interface element to the control device. In the case of querying that the application interface element contains the "SMS verification code has been sent" element, the verification code sending time is recorded. The C4 service queries every preset period whether the application interface contains the "login success homepage interface" element, and whether the application interface contains the "login failure" element.

[0137] If the "login success homepage interface" element is queried, the SMS verification result of this time is recorded as success, and the first virtual device is sent an exit login control command. The C4 service queries every preset period whether the application interface contains the "exit login" element, and after the exit login, the C4 service informs the C3 service that the simulation result of this time is success.

[0138] In this way, the business application that has successfully logged in is facilitated to be managed, and the problems existing in the business application that has failed to log in are investigated.

[0139] Optionally, after the login result of the first virtual device logging in based on the second script information and the verification code is obtained, the method further comprises:

[0140] In a case where it is determined according to the login result that the number of login failures of the application program on the first virtual device reaches a preset number of times, alarm information is output.

[0141] In a case where it is determined according to the login result that the number of login failures of the application program on the first virtual device reaches a preset number of times, alarm information is output.

[0142] For example, in the above example, if the C4 service queries the "login failure" element on the first virtual device, records the short message verification result of this time as a failure, initiates a "short message login" control request again, and if the C4 service queries the application of the first virtual device and finds that the short message login has failed for a plurality of times, stops testing on the device, issues an alarm, and informs the C3 service of the simulation result.

[0143] In this way, problems of the business application that fails to log in can be investigated.

[0144] Optionally, after the login result of the first virtual device logging in based on the second script information and the verification code is obtained, the method further comprises:

[0145] In a case where it is determined according to the login result that the number of login failures of the application program on the first virtual device reaches a preset number of times and the time interval between sending the verification codes reaches a preset time length, a second token is released, and the second token is used by other virtual devices except the first virtual device in the at least one virtual device.

[0146] In a case where the first virtual device fails to log in to the application program for a preset number of times (for example, three consecutive login failures), the C3 service of the control device configures a time for releasing the token again according to the application short message login verification code reissue time interval. After the time interval between sending the verification codes reaches a preset time length (that is, the countdown of the reissue time interval ends), the token is released again to be contended for by virtual devices supporting the business, and the first virtual device no longer contends for the token.

[0147] The virtual device contends for the appid in the configuration table of the application supported by the virtual device only once, and does not contend for the appid business token any more after all the supported appids are simulated.

[0148] In the above manner, in a case where the login fails for a plurality of times, the token is no longer contended for, interference caused by the application program that fails to log in or the problem of the virtual device itself is reduced, and the efficiency of the short message login function verification can be improved.

[0149] In order to facilitate the understanding of the above-mentioned mode, the following is illustrated by specific examples.

[0150] The verification system of the short message login function includes: a terminal device (i.e. 1 SIM card inserted into the entity mobile phone), a control device (i.e. a set of cloud service control end), a virtual device (i.e. a group of cloud service simulation end (including: N1 cloud PC, N2 cloud mobile phone)), the system architecture is as shown in Figure 3

[0151] As shown in Figure 4 The control device (also known as cloud service control end, abbreviated as C module) is pre-configured with the business application information to be perceived, including: business application number (appid), business application name (appname), short message verification code retransmission interval (apptime), for example: appid=0001, appname=A, apptime=65s; appid=0002, appname=B, apptime=180s……, as shown in Table 3:

[0152] Table 3

[0153] 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

[0154] The C2 service receives the initial registration / increase / deletion / information sent by the A1 service of the virtual device (also known as cloud service simulation end, abbreviated as A module), and the information includes: appid, appname, cloudid (cloud service simulation end number), cloudtype (virtual device type: cloud PC, cloud mobile phone), which is matched with the business application information pre-configured by the control device, and is stored and updated to generate a business application device list, as shown in Table 1.

[0155] The C3 service forms an initialization global simulation list according to the business application device list in the C2 service in the initial state, including appid, cloudid, and cloudtype. Each round of simulation takes each row of tasks in the global simulation list as a round of simulation completion; before the next round of simulation, the latest business application device list in the C2 service is used to generate an initialization global simulation list to start a round of simulation again.

[0156] The C3 service sends a notification to start simulation execution to all virtual devices, and releases the tokens of each appid. The A2 service of all virtual devices initiates a token contention operation to the C3 service according to the appid supported by the application configuration table.

[0157] ​After the C3 service inquires the A2 service of the virtual device with Cloud ID = 10002 and cloudtype = cloud phone to contend for the APPID = 1 (application A) token, the C3 service initiates the APPID = 1 business simulation start command and the short message verification code login simulation script to the Cloud ID = 10002 device that contends for the token. The short message verification code login simulation scripts of different cloudtype = cloud phone / cloud PC are different for the same application business. The short message verification code login simulation scripts need to be selected and sent according to the contended Cloud ID and cloudtype.

[0158] The C4 service interacts with the A2 service to perform simulation start, and sends the cloud phone type simulation script of the application A business to the A2 service of the virtual device with Cloud ID = 10002. The virtual device with Cloud ID = 10002 and the A2 service with APPID = 1 execute the simulation command and the script to enter the short message verification code login interface, input the mobile phone number, and click to send the verification code. The entity phone with the SIM card receives the short message verification code, and sends the verification code to the control device. The C4 service inquires every 200 ms whether the application interface contains the “short message verification code has been sent” element, and records the verification code sending time if the application interface element contains the “short message verification code has been sent” element.

[0159] The C4 service records the time when the device with Cloud ID = 10002 and the application with APPID = 1 sends the short message verification code, inquires the short message verification code closest to the short message verification code sending time from the C1 service, and sends the input short message verification code and the login control command and script to the application with Cloud ID = 10002 and APPID = 1 after inquiring. The device with Cloud ID = 10002 executes the simulation short message verification code login process of the application with APPID = 1, and the C4 service inquires every 200 ms whether the application interface contains the “home page interface after login success” element and whether the application interface contains the “login failure” element.

[0160] The C4 service records the short message verification result as success if the “home page interface after login success” element is inquired, and sends the logout control command to the device with Cloud ID = 10002 and the application with APPID = 1. The C4 service inquires every 200 ms whether the application interface contains the “logout” element, and notifies the C3 service that the simulation result is success after logout.

[0161] The C3 service configures the time when the token is released again according to the apptime short message verification code resend interval in the control device, and releases the token of the application with APPID = 1 again after the resend time interval countdown ends, so that the A module supporting the business contends for the simulation task again, and the device with Cloud ID = 10002 does not contend for the token again.

[0162] When all the appid&cloudid simulation items in the global simulation task list are marked, this round of simulation is completed. The C3 service queries the C2 service to generate the latest initialization global simulation task list, and starts the next round of simulation.

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

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

[0165] When all the appid&cloudid simulation items in the global simulation task list are marked, this round of simulation is completed. The C3 service queries the C2 service to generate the latest initialization global simulation task list, and starts the next round of simulation.

[0166] Referring to Figure 7 , Figure 7 The verification method for the short message login function provided by the application is executed by a terminal device provided with a SIM, and the method comprises the following steps:

[0167] Step 701: receiving a message of an application program 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 comprises a first virtual device, and the message comprises a verification code;

[0168] Step 702: sending the message of the application program to the control device.

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

[0170] The terminal device is provided with a SIM and can receive a login verification code of an application program sent by a virtual device. The terminal device sends the message of the application program (including the verification code and the identification of the application program) sent by the at least one virtual device to the control device. The control device interacts with the virtual device to perform a simulated short message login operation.

[0171] ​​The specific implementation process can refer to the description in the corresponding embodiment of the control device side, which will not be repeated here.

[0172] Referring to Figure 8 , Figure 8 The method is executed by a first virtual device, and the method comprises the following steps:

[0173] Step 801, receiving a first login control instruction and first script information sent by a control device;

[0174] Step 802, displaying a login interface of an application program based on the first login control instruction and the first script information, and sending a verification code to a terminal device based on a SIM number of the terminal device;

[0175] Step 803, receiving a second login control instruction and second script information sent by the control device, wherein the second login control instruction comprises the verification code;

[0176] Step 804, performing a login operation in an interface of the application program based on the login interface and the verification code.

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

[0178] In the case of obtaining a login verification code sent by the control device, the verification code is input into the login interface according to the second script information, and a login operation is performed, that is, an account of the application program is logged in.

[0179] Optionally, after the login operation in the interface of the application program is performed, the method further comprises the following steps:

[0180] Receiving query information of the interface of the application program sent by the control device;

[0181] In response to the query information, sending a login result to the control device.

[0182] After receiving the query information sent by the control device, the first virtual device can send a login result to the control device, and the login result can comprise login success, login failure, and in the case of login failure, the reason for login failure.

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

[0184] The embodiment of the application utilizes a cloud service control end to connect N1 cloud PC machines and N2 cloud mobile phones in an Internet mode, and a special hardware is connected to an entity mobile phone through a wired data line. Since the cloud service runs stably and is easy to maintain, the problem of instability of the special hardware and the real mobile phone after long time running can be solved.

[0185] A real mobile phone with a SIM card is used to obtain a short message login verification code sent by a cloud PC service application client and a cloud mobile phone APP client, and the short message login verification code is sent to a cloud service control end. A short message verification code processing service of the cloud service control end identifies, matches and stores the short message content according to the business name. A business application simulation end control service queries a corresponding application verification code, initiates a short message verification code login control to the cloud PC service application client and the cloud mobile phone APP client by carrying the verification code, and monitors the login operation of the cloud PC service application client and the cloud mobile phone APP client. The device occupation is reduced, and the resource utilization rate is improved.

[0186] The cloud service control end is used to collect and analyze the short message verification code, match the cloud service simulation end and the application, send a verification code login control command with the short message verification code to the cloud PC, and solve the defect that the PC client cannot develop the short message verification code login of the business application.

[0187] Referring to Figure 9 , Figure 9 is a structural schematic diagram of a short message login function verification device provided by the embodiment of the application, and is applied to a control device, such as a cloud service control end. Figure 9 As shown in the figure, the short message login function verification device 900 includes:

[0188] A first sending module 901 is configured to send a first login control instruction and first script information of an application program to a first virtual device.

[0189] A first receiving module 902 is configured to receive a message of the application program sent by a terminal device, and the message of the application program includes a verification code.

[0190] A second sending module 903 is configured to send a second login control instruction and second script information of the application program to the first virtual device, and the second login control instruction includes the verification code.

[0191] An obtaining module 904 is configured to obtain a login result of the first virtual device based on the second script information and the verification code.

[0192] Optionally, the first sending module includes:

[0193] The first obtaining sub-module is configured to obtain a service application device list, wherein the service application device list comprises information of at least one virtual device and information of an application installed on the at least one virtual device, and the at least one virtual device comprises the first virtual device;

[0194] The releasing sub-module is configured to release a first token to the at least one virtual device;

[0195] The first sending sub-module is configured to send a first login control instruction and first script information of the application to the first virtual device in a case where the first virtual device obtains the first token.

[0196] Optionally, the apparatus further comprises:

[0197] The second receiving module is configured to receive service application information sent by the at least one virtual device, wherein the service application information comprises information of an application and information of a virtual device;

[0198] The generating module is configured to generate the service application device list based on the service application information and a preconfigured service application list;

[0199] The apparatus further comprises:

[0200] The processing module is configured to not update the service application device list in a case where second virtual device sends indication information of adding first service application information;

[0201] The deleting module is configured to delete second service application information from the service application device list in a case where second virtual device sends indication information of deleting the second service application information.

[0202] Optionally, the apparatus further comprises:

[0203] The adding module is configured to add a mark to service information corresponding to the first virtual device in the service application device list according to the login result, wherein the mark is used to indicate a verification state of the service information of the first virtual device.

[0204] Optionally, the obtaining module comprises:

[0205] The second sending sub-module is configured to send query information of an interface of the application to the first virtual device;

[0206] The second obtaining sub-module is configured to obtain a login result sent by the first virtual device in response to the query information, wherein the login result is a result of login of the first virtual device based on the second script information and the verification code.

[0207] Optionally, the apparatus further comprises:

[0208] an output module configured to output an alarm information in a case where it is determined according to the login result that the number of login failures of the application program on the first virtual device reaches a preset number.

[0209] Optionally, the apparatus further comprises:

[0210] a release module configured to release a second token in a case where it is determined according to the login result that the number of login failures of the application program on the first virtual device reaches a preset number, and an interval between sending time instants of the verification codes reaches a preset time length, the second token being used by other virtual devices except the first virtual device in the at least one virtual device to acquire.

[0211] The verification apparatus of the short message login function can implement each process in the method embodiment and achieve the same technical effects. To avoid repetition, details are not repeated here. Figure 2 The verification apparatus of the short message login function can implement each process in the method embodiment and achieve the same technical effects. To avoid repetition, details are not repeated here.

[0212] Referring to Figure 10 , Figure 10 is a structural schematic diagram of a verification apparatus of a short message login function provided by an embodiment of the present application, applied to a terminal device, such as Figure 10 As shown in the figure, the verification apparatus 1000 of the short message login function comprises:

[0213] a receiving module 1001 configured to receive a message of an application program sent by at least one virtual device, the at least one virtual device comprising a first virtual device, and the message comprising a verification code;

[0214] a sending module 1002 configured to send the message of the application program to a control device.

[0215] The verification apparatus of the short message login function can implement each process in the method embodiment and achieve the same technical effects. To avoid repetition, details are not repeated here. Figure 7 The verification apparatus of the short message login function can implement each process in the method embodiment and achieve the same technical effects. To avoid repetition, details are not repeated here.

[0216] Referring to Figure 11 , Figure 11 is a structural schematic diagram of a verification apparatus of a short message login function provided by an embodiment of the present application, applied to a first virtual device, such as Figure 11 As shown in the figure, the verification apparatus 1100 of the short message login function comprises:

[0217] a first receiving module 1101 configured to receive a first login control instruction and first script information sent by a control device;

[0218] The 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 send a verification code to a terminal device based on a SIM number of the terminal device.

[0219] The second receiving module 1103 is configured to receive a second login control instruction and second script information sent by the control device, wherein the second login control instruction comprises the verification code.

[0220] The execution module 1104 is configured to perform a login operation on an interface of the application based on the login interface and the verification code.

[0221] Optionally, the apparatus further comprises:

[0222] The third receiving module is configured to receive query information of the interface of the application sent by the control device.

[0223] The second sending module is configured to send a login result to the control device in response to the query information.

[0224] The verification apparatus of the short message login function can implement Figure 8 each process in the method embodiment and achieve the same technical effects. To avoid repetition, no further description is given here.

[0225] It should be noted that the electronic device provided in the embodiments of the present application is the verification apparatus capable of performing the short message login function, and all implementation manners in the short message login function verification method embodiments are applicable to the electronic device, and can achieve the same or similar beneficial effects. To avoid repeated description, no further description is given in the embodiments.

[0226] The embodiments of the present application also provide an electronic device. Since the principle of solving the problem by the electronic device is similar to the short message login function verification method of the control device side in the embodiments of the present application, the implementation of the electronic device can be referred to the implementation of the method, and no further description is given for the repeated parts.

[0227] As shown in Figure 12 the electronic device of the embodiments of the present application is a control device, the electronic device comprises a processor 1200 configured to read a program in a memory 1220 and perform the following processes:

[0228] sending, by a transceiver 1210, a first login control instruction and first script information of an application to a first virtual device;

[0229] receiving a message of the application sent by a terminal device, wherein the message of the application comprises a verification code;

[0230] send, under control of the processor 1200, a second login control instruction and second script information of the application program to the first virtual device, the second login control instruction comprising the verification code;

[0231] obtain a login result of the first virtual device logging in based on the second script information and the verification code.

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

[0233] The processor 1200 is configured to obtain a first virtual device list comprising information of at least one virtual device and information of an application program installed in the at least one virtual device, and send, under control of the processor 1200, a first login control instruction and first script information of the application program to the first virtual device, the first login control instruction comprising the verification code. Figure 12 The bus architecture can comprise any number of interconnecting buses and bridges, and the various circuitry representative of the processor 1200 and the memory 1220, which are linked together by the bus architecture, are presented as being linked together via the bus 1201. The bus architecture can also link various other circuitry, such as peripheral devices, voltage regulators, and power management circuitry, which are well known in the art and therefore, not further described herein. The bus interface provides an interface to the bus architecture. The transceiver 1210 can be a plurality of elements, i.e., comprising a transmitter and a receiver, which provide means for communicating with various other apparatuses over a transmission medium. The processor 1200 is responsible for managing the bus architecture and general processing, and the memory 1220 can store data used by the processor 1200 in executing operations.

[0234] Optionally, the processor 1200 is configured to read a program in the memory 1220 and execute the sending, to the first virtual device, of the first login control instruction and the first script information of the application program, comprising:

[0235] obtain a business application device list comprising information of at least one virtual device and information of an application program installed in the at least one virtual device, the at least one virtual device comprising the first virtual device;

[0236] release a first token to the at least one virtual device;

[0237] in a case where the first virtual device obtains the first token, send, to the first virtual device, a first login control instruction and first script information of the application program.

[0238] Optionally, the processor 1200 is configured to read a program in the memory 1220 and further execute the following steps:

[0239] receive business application information sent by the at least one virtual device, the business application information comprising information of an application program and information of a virtual device;

[0240] generate the business application device list based on the business application information and a pre-configured business application list;

[0241] In a case where the indication information of adding the first service application information is received by the second virtual device, the service application device list is not updated.

[0242] In a case where the indication information of deleting the second service application information is received by the second virtual device, the second service application information is deleted from the service application device list.

[0243] Optionally, the processor 1200 is configured to read a program in the memory 1220, and perform the following steps:

[0244] 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, and the mark is used to indicate a verification state of the service information of the first virtual device.

[0245] Optionally, the processor 1200 is configured to read a program in the memory 1220, and perform the following steps:

[0246] The query information of the interface of the application program is sent to the first virtual device.

[0247] The login result sent by the first virtual device in response to the query information is obtained, and the login result is a result of login of the first virtual device based on the second script information and the verification code.

[0248] Optionally, the processor 1200 is configured to read a program in the memory 1220, and perform the following steps:

[0249] In a case where it is determined according to the login result that the number of login failures of the application program on the first virtual device reaches a preset number of times, alarm information is output.

[0250] Optionally, the processor 1200 is configured to read a program in the memory 1220, and perform the following steps:

[0251] In a case where it is determined according to the login result that the number of login failures of the application program on the first virtual device reaches a preset number of times, and an interval between sending time instants of the verification codes reaches a preset time length, a second token is released, and the second token is used for obtaining by other virtual devices except the first virtual device in the at least one virtual device.

[0252] The electronic device provided by the embodiment of the application can execute the method embodiment corresponding to the control device, and the implementation principle and technical effects are similar, and the embodiment will not be described here.

[0253] When the electronic device of the embodiment of the present application is a first virtual device, the electronic device comprises: a processor 1200 configured to read a program in a memory 1220 and perform the following processes:

[0254] receive, through a transceiver 1210, a first login control instruction and first script information sent by a control device;

[0255] 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 a SIM number of the terminal device;

[0256] receive a second login control instruction and second script information sent by the control device, the second login control instruction comprising the verification code;

[0257] perform a login operation in an interface of the application based on the login interface and the verification code.

[0258] Optionally, the processor 1200 is configured to read the program in the memory 1220 and further perform the following steps:

[0259] receive query information of the interface of the application sent by the control device;

[0260] send a login result to the control device in response to the query information.

[0261] The electronic device provided by the embodiment of the present application can perform the method embodiment corresponding to the first virtual device side as described above, and the implementation principle and technical effects are similar, and the embodiment will not be repeated here.

[0262] The embodiment of the present application further provides an electronic device. Since the principle of solving the problem of the electronic device is similar to the verification method of the short message login function of the terminal device side in the embodiment of the present application, the implementation of the electronic device can be referred to the implementation of the method, and the repeated parts will not be repeated. As shown in Figure 13 The electronic device comprises: a processor 1300 configured to read a program in a memory 1320 and perform the following processes:

[0263] receive, through a transceiver 1310, a message of an application sent by at least one virtual device, the at least one virtual device comprising a first virtual device, the message comprising a verification code;

[0264] send the message of the application to the control device.

[0265] The transceiver 1310 is configured to receive and send data under the control of the processor 1300;

[0266] A user interface 1330 is configured to interact with a user.

[0267] wherein, in Figure 13 The bus architecture can include any number of interconnected buses and bridges, specifically, various circuitry linking the processor(s) 1300 and the memory represented by the memory 1320. The bus architecture can also link various other circuitry, such as peripheral devices, voltage regulators, and power management circuitry, all of which are well known in the art and thus, not further described herein. The bus interface provides an interface. The transceiver 1310 can be a plurality of elements, i.e., including a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 1300 is responsible for managing the bus architecture and general processing, with the memory 1320 storing data used by the processor 1300 in its execution of operations.

[0268] The electronic device provided by the embodiment of the present application can execute the method embodiment corresponding to the terminal device side, and the implementation principle and technical effects are similar, and thus will not be described here again.

[0269] The embodiment of the present application further provides a computer readable storage medium, and the computer readable storage medium stores a computer program. The computer program is executed by a processor to implement each process of the method embodiment of the short message login function verification method and achieve the same technical effects. To avoid repetition, details will not be described here. The computer readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0270] The embodiment of the present application further provides a computer program product, which includes computer instructions. The computer instructions are executed by a processor to implement each process of the method embodiment and achieve the same technical effects. To avoid repetition, details will not be described here.

[0271] It should be noted that, in this document, the term "comprising" or "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that processes, methods, articles, or devices including a series of elements not only include those elements, but also include other elements not explicitly listed, or inherent to such processes, methods, articles, or devices. Without more limitations, the element defined by the statement "including a" does not exclude the presence of another identical element in the process, method, article, or device including the element.

[0272] Through the above description of the embodiments, those skilled in the art can clearly understand that the above-mentioned example methods can be realized by means of software and a necessary general hardware platform, and of course, can also be realized by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product in essence or in the form of a part that contributes to the prior art. The computer software product is stored in a storage medium (such as a ROM / RAM, a magnetic disk, or an optical disk) and includes a plurality of instructions for causing a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in the various embodiments of the present application.

[0273] The embodiments of the present application are described above in combination with the drawings, but the present application is not limited to the above-mentioned specific embodiments, and the above-mentioned specific embodiments are only illustrative and not restrictive. Those skilled in the art can make many forms without departing from the scope of the present application under the inspiration of the present application, and all of them belong to the protection of the present application.

Claims

1. A method for verifying a short message login function, characterized by, The method is executed by a control device, and comprises: sending, to a first virtual device, first login control instructions and first script information of an application program, the first virtual device entering a login interface of the application program based on the first login control instructions and the first script information; receiving a message of the application program sent by a terminal device, the message of the application program comprising a verification code; sending, to the first virtual device, second login control instructions and second script information of the application program, the second login control instructions comprising the verification code; obtaining a login result of the first virtual device based on the second script information and the verification code, and adding a mark to service information corresponding to the first virtual device in a service application device list according to the login result, the mark being used to indicate a verification state of the service information of the first virtual device.

2. The method of claim 1, wherein, The method further comprises: obtaining a service application device list, the service application device list comprising information of at least one virtual device and information of an application program installed in the at least one virtual device, the at least one virtual device comprising the first virtual device; releasing a first token to the at least one virtual device; in a case where the first virtual device obtains the first token, sending, to the first virtual device, the first login control instructions and the first script information of the application program.

3. The method of claim 2, wherein, Before the obtaining of the service application device list, the method further comprises: receiving service application information sent by the at least one virtual device, the service application information comprising information of an application program and information of a virtual device; generating the service application device list based on the service application information and a preconfigured service application list; After the obtaining of the service application device list, the method further comprises: in a case where indication information of adding first service application information is received from a second virtual device, not updating the service application device list; in a case where indication information of deleting second service application information is received from a second virtual device, deleting the second service application information from the service application device list.

4. The method of claim 1, wherein, The method further comprises: sending, to the first virtual device, query information of an interface of the application program; obtaining a login result sent by the first virtual device in response to the query information, the login result being a result of the first virtual device logging in based on the second script information and the verification code.

5. The method according to claim 1 or 4, characterized in that, After the obtaining of the login result of the first virtual device based on the second script information and the verification code, the method further comprises: in a case where it is determined according to the login result that a number of login failures of the application program on the first virtual device reaches a preset number, outputting alarm information.

6. The method of claim 1, wherein, After the obtaining of the login result of the first virtual device based on the second script information and the verification code, the method further comprises: In a case where it is determined according to the login result that the number of login failures of the application program at the first virtual device reaches a preset number and an interval between sending moments of the verification code reaches a preset time length, a second token is released, the second token being used for at least one virtual device other than the first virtual device to acquire.

7. A method of verifying a short message login function, characterized by, The method is performed by a terminal device provided with a SIM, and the method comprises: receiving a message of an application program sent by at least one virtual device, the at least one virtual device comprising a first virtual device, the message comprising a verification code; sending the message of the application program to a control device, so that the control device sends second login control instructions of the application program and second script information to the first virtual device, the second login control instructions comprising the verification code, and the control device acquiring a login result of the first virtual device based on the second script information and the verification code.

8. A method of verifying a short message login function, characterized by, The method is performed by a first virtual device, and the method comprises: receiving first login control instructions and first script information sent by a control device; displaying a login interface of an application program based on the first login control instructions and the first script information, and sending a verification code to a terminal device based on a SIM number of the terminal device; receiving second login control instructions and second script information sent by the control device, the second login control instructions comprising the verification code; performing a login operation in an interface of the application program based on the login interface and the verification code.

9. The method of claim 8, wherein, After the login operation in the interface of the application program, the method further comprises: receiving query information of the interface of the application program sent by the control device; sending a login result to the control device in response to the query information.

10. An apparatus for verifying a short message login function, characterized by comprising: The control device comprises: a first sending module configured to send first login control instructions of an application program and first script information to a first virtual device; a first receiving module configured to receive a message of the application program sent by a terminal device, the message of the application program comprising a verification code; a second sending module configured to send second login control instructions of the application program and second script information to the first virtual device, the second login control instructions comprising the verification code; an acquiring module configured to acquire a login result of the first virtual device based on the second script information and the verification code.

11. An apparatus for verifying a short message login function, characterized by comprising: The terminal device comprises: a receiving module configured to receive a message of an application program sent by at least one virtual device, the at least one virtual device comprising a first virtual device, the message comprising a verification code; a sending module configured to send the message of the application program to a control device, so that the control device sends second login control instructions of the application program and second script information to the first virtual device, the second login control instructions comprising the verification code, and the control device acquiring a login result of the first virtual device based on the second script information and the verification code. The first virtual device comprises: a first receiving module configured to receive first login control instructions and first script information sent by a control device; 12. An apparatus for verifying a short message login function, characterized by comprising: ​ ​ The first sending module is 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 a SIM number of the terminal device; The second receiving module is configured to receive a second login control instruction and second script information sent by the control device, the second login control instruction comprising the verification code; The executing module is configured to perform a login operation on an interface of the application based on the login interface and the verification code.

13. An electronic device, comprising: The processor, the memory, and a program stored in the memory and executable on the processor, the program being executed by the processor to implement the steps of the verification method of the SMS login function according to any one of claims 1 to 6; or implement the steps of the verification method of the SMS login function according to claim 7; The steps of the verification method of the SMS login function according to any one of claims 8 to 9 are implemented. The computer program is stored in the computer readable storage medium, and the computer program is executed by the processor to implement the steps of the verification method of the SMS login function according to any one of claims 1 to 6; or implement the steps of the verification method of the SMS login function according to claim 7; 14. A computer-readable storage medium, characterized in that, The steps of the verification method of the SMS login function according to any one of claims 8 to 9 are implemented. The computer program is stored in the computer readable storage medium, and the computer program is executed by the processor to implement the steps of the verification method of the SMS login function according to any one of claims 1 to 6; or implement the steps of the verification method of the SMS login function according to claim 7; 15. A computer program product, characterised in that, The steps of the verification method of the SMS login function according to any one of claims 8 to 9 are implemented. ​

Images