阅读说明：本技术 云手机应用启动控制方法、相关装置及计算机程序产品 (Cloud mobile phone application starting control method, related device and computer program product ) 是由 周立群 黄坚 李全斌 陈娇 马伟翔 崔巍崧 唐顺辉 于 2021-07-23 设计创作，主要内容包括：本公开提供了一种云手机应用启动控制方法、装置、电子设备、计算机可读存储介质及计算机程序产品,涉及云计算技术领域,尤其涉及云服务、云平台技术领域。该方法包括：接收由当前的第一界面所属的第一云手机应用发起的启动请求；根据启动请求确定待启动的第二界面所属的第二云手机应用；响应于第二云手机应用属于不允许被启动的云手机应用,生成表征启动失败的目标返回值,并将目标返回值反馈给第一云手机应用。该方法在确定通过第一云手机应用发起启动请求的第二云手机应用属于不允许启动的云手机应用时,自行生成表征启动失败的返回值给第一云手机应用,使得第一云手机应用不至于因未收到回复而持续等待造成资源占用。(The disclosure provides a cloud mobile phone application starting control method and device, electronic equipment, a computer readable storage medium and a computer program product, and relates to the technical field of cloud computing, in particular to the technical field of cloud service and cloud platform. The method comprises the following steps: receiving a starting request initiated by a first cloud mobile phone application to which a current first interface belongs; determining a second cloud mobile phone application to which a second interface to be started belongs according to the starting request; and generating a target return value representing starting failure in response to the fact that the second cloud mobile phone application belongs to the cloud mobile phone application which is not allowed to be started, and feeding back the target return value to the first cloud mobile phone application. According to the method, when the fact that the second cloud mobile phone application which initiates the starting request through the first cloud mobile phone application belongs to the cloud mobile phone application which is not allowed to be started is determined, the return value representing the starting failure is automatically generated to the first cloud mobile phone application, and therefore the first cloud mobile phone application cannot be subjected to continuous waiting to cause resource occupation due to the fact that no reply is received.)

1. A cloud mobile phone application starting control method comprises the following steps:

receiving a starting request initiated by a first cloud mobile phone application to which a current first interface belongs;

determining a second cloud mobile phone application to which a second interface to be started belongs according to the starting request;

and in response to the fact that the second cloud mobile phone application belongs to the cloud mobile phone application which is not allowed to be started, generating a target return value representing starting failure, and feeding back the target return value to the first cloud mobile phone application.

2. The method of claim 1, wherein the determining, according to the launch request, a second cloud mobile phone application to which a second interface to be launched belongs comprises:

extracting an interface name and/or an application name in the starting request;

taking the interface corresponding to the interface name as the second interface;

determining the cloud mobile phone application to which the second interface belongs and the cloud mobile phone application corresponding to the application name as the second cloud mobile phone application; when only the application name is extracted, the second interface is a default interface or a representative interface of the second cloud mobile phone application corresponding to the application name.

3. The method of claim 1, further comprising:

responding to the second cloud mobile phone application as the first cloud mobile phone application, and jumping to the second interface;

and responding to the fact that the second cloud mobile phone application is not the first cloud mobile phone application and belongs to a white list application preset for the first cloud mobile phone application, and starting the second cloud mobile phone application.

4. The method of claim 1, further comprising:

and controlling the first cloud mobile phone application to terminate the waiting state of the starting request according to the target return value.

5. The method of claim 1, further comprising:

carrying out malicious application detection on the second cloud mobile phone application which is not allowed to be started;

and in response to the detection result that the malicious application belongs to the detection result, returning notification information for trying to start the malicious application through a preset path, and recording the cloud resource account initiating the starting request.

6. The method of any of claims 1-5, further comprising:

counting the interception times of each second cloud mobile phone application which is not allowed to be started within a preset time period;

marking the second cloud mobile phone application with the interception times exceeding the preset times as a target cloud mobile phone application;

according to the functional characteristics of the target cloud mobile phone application, adjusting to obtain a customized cloud mobile phone application meeting the current cloud mobile phone environment requirement;

and responding to the fact that the customized plate cloud mobile phone application is successfully installed in the current cloud mobile phone environment, and providing the customized plate cloud mobile phone application as a starting-allowed version of a target cloud mobile phone application which is not allowed to be started originally to a user attempting to start.

7. A cloud cell-phone application starts controlling means includes:

the starting request receiving unit is configured to receive a starting request initiated by a first cloud mobile phone application to which a current first interface belongs;

the second cloud mobile phone application determining unit is configured to determine a second cloud mobile phone application to which a second interface to be started belongs according to the starting request;

and the starting disallowance return value feedback unit is configured to generate a target return value representing starting failure in response to the second cloud mobile phone application belonging to the cloud mobile phone application which is not allowed to be started, and feed the target return value back to the first cloud mobile phone application.

8. The apparatus of claim 7, wherein the second cloud handset application determination unit is further configured to:

extracting an interface name and/or an application name in the starting request;

taking the interface corresponding to the interface name as the second interface;

determining the cloud mobile phone application to which the second interface belongs and the cloud mobile phone application corresponding to the application name as the second cloud mobile phone application; when only the application name is extracted, the second interface is a default interface or a representative interface of the second cloud mobile phone application corresponding to the application name.

9. The apparatus of claim 7, further comprising:

an in-app skip unit configured to skip to the second interface in response to the second cloud phone application being the first cloud phone application;

a white list application starting unit configured to start the second cloud mobile phone application in response to the second cloud mobile phone application not being the first cloud mobile phone application and belonging to a white list application set for the first cloud mobile phone application in advance.

10. The apparatus of claim 7, further comprising:

a waiting state terminating unit configured to control the first cloud mobile phone application to terminate a waiting state of the start request according to the target return value.

11. The apparatus of claim 7, further comprising:

the malicious application detection unit is configured to detect malicious applications of the second cloud mobile phone application which is not allowed to be started;

and the malicious application attempted starting processing unit is configured to respond to the detection result that the malicious application belongs to the malicious application, return notification information of the attempted starting of the malicious application through a preset path, and record the cloud resource account initiating the starting request.

12. The apparatus of any of claims 7-11, further comprising:

the intercepting times counting unit is configured to count the intercepting times of each second cloud mobile phone application which is not allowed to be started within a preset time period;

the target cloud mobile phone application determining unit is configured to mark the second cloud mobile phone application with the interception times exceeding the preset times as a target cloud mobile phone application;

the application customizing unit is configured to adjust and obtain a customized version of the cloud mobile phone application meeting the current cloud mobile phone environment requirement according to the functional characteristics of the target cloud mobile phone application;

an alternate version providing unit configured to provide the customized cloud phone application as a start-up-allowed version of a target cloud phone application that was not originally allowed to be started up to a user attempting to start up in response to the customized cloud phone application being successfully installed in a current cloud phone environment.

13. An electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the cloud handset application launch control method of any of claims 1-6.

14. A non-transitory computer readable storage medium storing computer instructions for causing a computer to perform the cloud handset application launch control method of any one of claims 1-6.

15. A computer program product comprising a computer program which, when executed by a processor, implements the cloud handset application launch control method according to any one of claims 1 to 6.

Technical Field

The present disclosure relates to the field of cloud computing technologies, and in particular, to the field of cloud services and cloud platforms, and in particular, to a method and an apparatus for controlling starting of a cloud mobile phone application, an electronic device, a computer-readable storage medium, and a computer program product.

Background

In the background of cloud game mode, the scene of trying to play for the user can only be allowed to operate in a game interface, and other non-game applications are not allowed to operate.

And a malicious user may perform some destructive operations on the cloud game system, for example, restore the cloud mobile phone to factory settings, or even set the screen locking software to execute lasso, and download the mining software to occupy system resources, such as occupying disk space, consuming cpu resources, memory, and network resources.

Disclosure of Invention

The embodiment of the disclosure provides a cloud mobile phone application starting control method and device, electronic equipment, a computer readable storage medium and a computer program product.

In a first aspect, an embodiment of the present disclosure provides a cloud mobile phone application start control method, including: receiving a starting request initiated by a first cloud mobile phone application to which a current first interface belongs; determining a second cloud mobile phone application to which a second interface to be started belongs according to the starting request; and generating a target return value representing starting failure in response to the fact that the second cloud mobile phone application belongs to the cloud mobile phone application which is not allowed to be started, and feeding back the target return value to the first cloud mobile phone application.

In a second aspect, an embodiment of the present disclosure provides a cloud mobile phone application start control apparatus, including: the starting request receiving unit is configured to receive a starting request initiated by a first cloud mobile phone application to which a current first interface belongs; the second cloud mobile phone application determining unit is configured to determine a second cloud mobile phone application to which a second interface to be started belongs according to the starting request; and the starting disallowance return value feedback unit is configured to generate a target return value representing the starting failure in response to the second cloud mobile phone application belonging to the cloud mobile phone application which is not allowed to be started, and feed the target return value back to the first cloud mobile phone application.

In a third aspect, an embodiment of the present disclosure provides an electronic device, including: at least one processor; and a memory communicatively coupled to the at least one processor; the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can implement the cloud mobile phone application start control method as described in any implementation manner of the first aspect.

In a fourth aspect, the present disclosure provides a non-transitory computer-readable storage medium storing computer instructions for enabling a computer to implement the cloud mobile phone application start control method as described in any implementation manner of the first aspect when executed.

In a fifth aspect, the present disclosure provides a computer program product including a computer program, where the computer program is capable of implementing the cloud mobile phone application start control method as described in any implementation manner of the first aspect when executed by a processor.

The cloud mobile phone application starting control method provided by the embodiment of the disclosure comprises the following steps: firstly, receiving a starting request initiated by a first cloud mobile phone application to which a current first interface belongs; then, determining a second cloud mobile phone application to which a second interface to be started belongs according to the starting request; and finally, generating a target return value representing starting failure in response to the fact that the second cloud mobile phone application belongs to the cloud mobile phone application which is not allowed to be started, and feeding back the target return value to the first cloud mobile phone application.

According to the method, the cloud mobile phone applications which are not allowed to be started are configured for each cloud mobile phone in advance, and when the fact that the second cloud mobile phone application which initiates the starting request through the first cloud mobile phone application belongs to the cloud mobile phone applications which are not allowed to be started is determined, the return value which represents the starting failure is automatically generated to the first cloud mobile phone application, so that the first cloud mobile phone application can judge that the sent starting request is replied according to the received return value, the starting request is not in an on-hook state and a reply waiting state during the period that the starting request does not receive the response, the occupation of the suspended invalid request on cloud mobile phone resources is reduced, and the performance of the cloud mobile phone is improved.

It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

Other features, objects and advantages of the disclosure will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:

FIG. 1 is an exemplary system architecture to which the present disclosure may be applied;

fig. 2 is a flowchart of a cloud mobile phone application start control method according to an embodiment of the present disclosure;

fig. 3 is a flowchart of another cloud mobile phone application start control method according to an embodiment of the present disclosure;

fig. 4 is a flowchart of a malicious application detection method in the cloud mobile phone application start control method according to the embodiment of the present disclosure;

fig. 5 is a flowchart of a method for customizing an application according to a start-up heat in a cloud mobile phone application start-up control method according to an embodiment of the present disclosure;

fig. 6 is a block diagram of a structure of a cloud mobile phone application start control apparatus according to an embodiment of the present disclosure;

fig. 7 is a schematic structural diagram of an electronic device adapted to execute a cloud mobile phone application start control method according to an embodiment of the present disclosure.

Detailed Description

Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness. It should be noted that, in the present disclosure, the embodiments and features of the embodiments may be combined with each other without conflict.

In the technical scheme of the disclosure, the acquisition, storage, application and the like of the personal information of the related user all accord with the regulations of related laws and regulations, necessary security measures are taken, and the customs of the public order is not violated.

Fig. 1 illustrates an exemplary system architecture 100 to which embodiments of the cloud handset application launch control method, apparatus, electronic device, and computer-readable storage medium of the present disclosure may be applied.

As shown in fig. 1, the system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

The user may use the terminal devices 101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. Various applications for realizing information communication between the terminal devices 101, 102, 103 and the server 105, such as a cloud mobile phone control application, a cloud game application, an instant messaging application, etc., may be installed on the terminal devices 101, 102, 103 and the server 105.

The terminal apparatuses 101, 102, 103 and the server 105 may be hardware or software. When the terminal devices 101, 102, 103 are hardware, they may be various electronic devices with display screens, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like; when the terminal devices 101, 102, and 103 are software, they may be installed in the electronic devices listed above, and they may be implemented as multiple software or software modules, or may be implemented as a single software or software module, and are not limited in this respect. When the server 105 is hardware, it may be implemented as a distributed server cluster composed of multiple servers, or may be implemented as a single server; when the server is software, the server may be implemented as a plurality of software or software modules, or may be implemented as a single software or software module, which is not limited herein.

The server 105 may provide various services through various built-in applications, and taking a cloud mobile phone control application that may provide a cloud mobile phone application service for a local user as an example, the server 105 may implement the following effects when running the cloud mobile phone control application: firstly, receiving a use request of a user for a cloud mobile phone from terminal equipment 101, 102 and 103 through a network 104; then, on the basis that a user can control the cloud mobile phone on the server 105 through the terminal devices 101, 102 and 103, receiving a starting request initiated by a first cloud mobile phone application to which the current first interface belongs; next, determining a second cloud mobile phone application to which a second interface to be started belongs according to the starting request; and finally, generating a target return value representing starting failure in response to the fact that the second cloud mobile phone application belongs to the cloud mobile phone application which is not allowed to be started, and feeding back the target return value to the first cloud mobile phone application. The user can project the screen of the terminal device 101, 102, 103 through the cloud mobile phone running condition on the server 105, and know that the second cloud mobile phone application which the user wants to start is refused to start.

The cloud mobile phone application start control method provided in the subsequent embodiments of the present disclosure is generally executed by the server 105 bearing cloud mobile phone resources, and accordingly, the cloud mobile phone application start control device is also generally disposed in the server 105. Of course, a smart terminal with a strong capability may also serve as the server 105 in the embodiment, that is, the smart phone of another person may serve as a cloud phone used for the request of the smart phone of the smart terminal.

It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Referring to fig. 2, fig. 2 is a flowchart of a cloud mobile phone application start control method according to an embodiment of the present disclosure, where the process 200 includes the following steps:

step 201: receiving a starting request initiated by a first cloud mobile phone application to which a current first interface belongs;

in this step, an execution main body of the cloud mobile phone application start control method (for example, the server 105 shown in fig. 1 and bearing cloud mobile phone resources, or a function responsible for managing interface creation on each cloud mobile phone, for example, a service activity manager service function startActivity related heavy-load function under an Android system) receives a start request initiated by a first cloud mobile phone application to which a current first interface belongs.

The starting request is initiated by a user on a first interface of a first cloud mobile phone application, the starting request may be triggered after a certain virtual function button displayed on the first interface is clicked, a clicking instruction of a virtual function key is actually transmitted from a clicking instruction issued by the user to a corresponding position on a local terminal device (for example, terminal devices 101, 102, 103 shown in fig. 1), and the clicking instruction is converted into a clicking instruction of the virtual function key at the corresponding position on the first interface after being transmitted to the execution main body. In addition to the virtual function key being clicked, the start request may be generated due to a shortcut gesture or a shortcut instruction being triggered, in this case, the first interface is not the current interface but an interface corresponding to the shortcut gesture, and the corresponding first cloud mobile application should also be a configuration and execution application of the shortcut gesture, and in this case, the cloud mobile phone is required to allow the execution of the shortcut instruction to be invoked on the current interface.

Step 202: determining a second cloud mobile phone application to which a second interface to be started belongs according to the starting request;

on the basis of step 201, in this step, the execution subject determines, according to the information included in the start request, a second cloud mobile phone application to which the second interface to be started belongs. For example, if the second interface is a web page link, then a default browser application is typically invoked to open the web page link. Specifically, if the start request is to start a service without an interface, since the current high-version android system does not allow such a service without an interface to be called and started by itself, it can be considered that the objects to be started by the start request for which the present disclosure is directed all have corresponding interfaces.

Specifically, there are various ways of determining the second interface and the second cloud mobile phone application according to the start request, for example, according to application interface information, a URL, a preset function, an interface name, an application package name, and the like in the start request, which are not listed here.

Step 203: and generating a target return value representing starting failure in response to the fact that the second cloud mobile phone application belongs to the cloud mobile phone application which is not allowed to be started, and feeding back the target return value to the first cloud mobile phone application.

On the basis of step 202, in this step, it is determined by the execution main body that the second cloud mobile phone does not belong to the cloud mobile phone application that is allowed to be started on the basis of the first cloud mobile phone application, so on the basis of intercepting or shielding the start request in general, the present disclosure also generates a target return value for representing a start failure or rejecting a start, and makes the first cloud mobile phone application know a reply of the start request initiated by the first cloud mobile phone application by feeding back the target return value to the first cloud mobile phone application, thereby facilitating the first cloud mobile phone application to terminate the start request.

It should be noted that the present disclosure is directed to a request type in which the start request needs to wait for a return value to be deleted or terminated, that is, a request type in a synchronous processing manner. Because the target return value is generated by the execution main body, some simulation processing is required to be performed when the target return value is generated so as to simulate the return value generation rule of the original return value generator, so that the start request can determine that the normal start cannot be performed due to any reason according to the target return value. In addition, the return operation of the return value may be delayed appropriately after generation in order to adapt the internal processing logic.

The method includes the steps that a starting control list of cloud mobile phone applications which are allowed to be started or not allowed to be started is configured for each cloud mobile phone in advance, so that whether the second cloud mobile phone applications are allowed to be started or not is judged according to the starting control list, and the starting control list can be embodied as a black list and/or a white list. Meanwhile, in order to prevent the start control function of the start control list from being illegally bypassed, the start control list can be set as a link which must be executed after the start request is triggered, and the priority of the start control list kept in the memory can be increased, so that the false phenomenon that the content of the start control list is empty is prevented from being produced by emptying the memory.

Further, the execution main body may control the first cloud mobile phone application to terminate the waiting state of the start request according to the target return value, so that the start request in the waiting reply state is indeed terminated or deleted, and further resources occupied by the thread initiating the start request are released.

According to the cloud mobile phone application starting control method provided by the embodiment of the disclosure, the cloud mobile phone application which is not allowed to be started is configured for each cloud mobile phone in advance, and when the second cloud mobile phone application which initiates the starting request through the first cloud mobile phone application is determined to belong to the cloud mobile phone application which is not allowed to be started, the return value which represents the starting failure is automatically generated to the first cloud mobile phone application, so that the first cloud mobile phone application can judge that the sent starting request is replied according to the received return value, the starting request is not in an on-hook state and a reply waiting state during a period when the response is not received, the occupation of the suspended invalid request on cloud mobile phone resources is further reduced, and the performance of the cloud mobile phone is improved.

Referring to fig. 3, fig. 3 is a flowchart of another cloud mobile phone application start control method according to an embodiment of the present disclosure, where the process 300 includes the following steps:

step 301: receiving a starting request initiated by a first cloud mobile phone application to which a current first interface belongs;

step 302: extracting an interface name and/or an application name in the starting request;

in this step, the execution subject extracts the interface name and/or application name (or application package name) included in the start request, that is, the interface name indicates what interface the interface to be started is specifically, and the application name indicates which interface the interface to be started is.

In general, when a plurality of applications can present the same interface (that is, the target interface to be started does not define the start application) and the interface for starting the interface is not designated, the default start application can be directly used to start the target interface, and if the default start application is not set, an option can be provided on the alternative application selection interface.

When only the application name exists, the target interface to be started is a default interface, a start interface or a homepage of the application corresponding to the application name, and if a plurality of versions of the application corresponding to the application name are installed on the cloud mobile phone on the execution subject and the application name does not specify a version, the application with the latest version can be selected by default to start or provide the interface selected by the user, and similarly, in order to avoid the risk of bypassing some versions of the application, the plurality of versions on the selection interface should also be the remaining applications allowed to be started after being screened by the start control list.

Step 303: taking the interface corresponding to the interface name as a second interface;

on the basis of step 302, this step is intended to make the interface corresponding to the interface name as the second interface to be started by the execution subject according to the corresponding relationship between the interface name and the interface.

Step 304: determining the cloud mobile phone application to which the second interface belongs and the cloud mobile phone application corresponding to the application name as a second cloud mobile phone application;

on the basis of step 303, in this step, the execution subject determines, as the second cloud mobile phone application, both the cloud mobile phone application to which the second interface belongs and the cloud mobile phone application corresponding to the existing application name. Similarly, there is a correspondence between application names and applications.

In the present disclosure, a specific implementation manner for determining the second interface and the second cloud mobile phone application according to the start request is provided through steps 302 to 304, so as to determine the second interface and the second cloud mobile phone application as accurately and comprehensively as possible.

Step 305: judging whether the second cloud mobile phone application is the first cloud mobile phone application, if so, executing step 306, otherwise, executing step 307;

on the basis of step 304, this step is intended to determine whether the second cloud mobile phone application is the first cloud mobile phone application by the execution subject, and select a different processing branch according to the determination result.

Step 306: jumping to a second interface;

this step is based on the determination result of step 305 being that the second cloud mobile phone application is the first cloud mobile phone application, and is intended to execute an operation of jumping to the second interface when the execution subject determines that the intra-application jump is involved.

Step 307: judging whether the second cloud mobile phone application is a white list application of the first cloud mobile phone application, if so, executing a step 309, otherwise, executing a step 308;

this step is established on the basis that the judgment result of the step 305 is that the second cloud mobile phone application is not the first cloud mobile phone application, and aims to continuously judge whether the second cloud mobile phone application is the white list application of the first cloud mobile phone application by the execution main body, and continuously select different processing branches according to the judgment result.

Step 308: generating a target return value representing starting failure, and feeding back the target return value to the first cloud mobile phone application;

in this step, based on the determination result in step 307 that the second cloud mobile phone application does not belong to the white list application of the first cloud mobile phone application, the execution subject generates a target return value representing the failed start, and feeds back the target return value to the first cloud mobile phone application.

Step 309: and starting the second cloud mobile phone application.

This step is established on the basis that the judgment result of the step 307 is that the second cloud mobile phone application belongs to the white list application of the first cloud mobile phone application, so the second cloud mobile phone application is started.

Different from the embodiment shown in the process 200, the embodiment not only provides a specific implementation manner for determining the second interface and the second cloud mobile phone application according to the extracted interface name and/or application name through steps 302 to 304, but also provides a complete judgment and processing scheme sequentially passing through two times of discrimination and three processing branches in total through steps 305 to 309, and embodies the comprehensiveness of consideration and the completeness of the scheme for various situations.

It should be understood that there is no cause or dependency relationship between the specific implementation provided in steps 302-304 and the specific implementation provided in steps 305-309, and even if the schemes in steps 302-304 are not adopted to determine the second interface and the second cloud mobile phone application, steps 305-309 may also be executed to accomplish similar technical effects, and similarly, even if the schemes in steps 305-309 are not adopted to determine, the second interface and the second cloud mobile phone application may also be determined through steps 302-304. This embodiment exists only as a preferred embodiment that includes both of the above two detailed implementations.

On the basis of any of the above embodiments, although the control over the start request can be realized through the preset start control list, in order to better prevent the malicious request from continuing to appear from the source, now, malicious application detection can also be performed on the second cloud mobile phone application which is not allowed to be started, because under the mode that the second cloud mobile phone application which is allowed to be started is controlled through the white list, the reason why the second cloud mobile phone application which is not allowed to be started is probably many, and therefore, in order to determine whether the second cloud mobile phone application which is allowed to be started is not due to belonging to the malicious application, the malicious application detection can be realized.

One implementation, including and not limited to, may be seen in flow 400 as shown in FIG. 4:

step 401: carrying out malicious application detection on the second cloud mobile phone application which is not allowed to be started;

step 402: and in response to the detection result that the application belongs to the malicious application, returning notification information for trying to start the malicious application through a preset path, and recording the cloud resource account initiating the starting request.

When the second cloud mobile phone application is determined to belong to the malicious application through the detection result, the notification information that the user tries to start the malicious application is returned through the preset path, so that the provider of the cloud mobile phone resource can timely know that the malicious intention exists, meanwhile, the cloud resource account initiating the starting request is recorded, the user can be conveniently and better warned, the account is forbidden under the condition of necessity and compliance, and the malicious intention is prevented from happening again.

Meanwhile, in order to avoid that the white list application is tampered privately to actually start a tampering application capable of executing malicious operation, the change of the application program data can be monitored in real time, so that an alarm can be sent out in real time.

On the basis of any of the above embodiments, it is considered that the reason why some special applications are not allowed to be started is because some more sensitive functional components exist, but if it is found that more general users really want to try to start the application and the more sensitive functional components are rarely used, the starting and using requirements of the users can be met by customizing the application to remove the sensitive functional components.

One implementation, including and not limited to, may be seen in flow 500 as shown in FIG. 5:

step 501: counting the interception times of each second cloud mobile phone application which is not allowed to be started within a preset time period;

step 502: marking the second cloud mobile phone application with the interception times exceeding the preset times as a target cloud mobile phone application;

steps 501-502 are intended to mark the second cloud mobile phone application with a large interception number as a target cloud mobile phone application with strong starting and using requirements of a user by the execution main body through counting the interception number within a period of time.

Step 503: according to the functional characteristics of the target cloud mobile phone application, the customized cloud mobile phone application meeting the current cloud mobile phone environment requirement is obtained through adjustment;

the execution main body adjusts the customized cloud mobile phone application meeting the current cloud mobile phone environment requirement according to the functional characteristics of the target cloud mobile phone application.

Specifically, the method comprises the steps of removing or adjusting some functional components which do not meet the current cloud mobile phone environment requirement, or adjusting parameters of some functional components which cannot be removed, so as to obtain the customized plate cloud mobile phone application.

Step 504: and in response to the customized cloud mobile phone application being successfully installed in the current cloud mobile phone environment, providing the customized cloud mobile phone application as a start-up-allowed version of the target cloud mobile phone application which is not originally allowed to be started to the user attempting to start up.

The step aims to provide the customized cloud mobile phone application as a starting-allowed version of a target cloud mobile phone application which is not allowed to be started originally to a user attempting to start by the execution subject.

With further reference to fig. 6, as an implementation of the method shown in the above diagrams, the present disclosure provides an embodiment of a cloud mobile phone application start control apparatus, where the apparatus embodiment corresponds to the method embodiment shown in fig. 2, and the apparatus may be specifically applied to various electronic devices.

As shown in fig. 6, the cloud mobile phone application start control apparatus 600 of the present embodiment may include: a starting request receiving unit 601, a second cloud mobile phone application determining unit 602, and a starting disallowance return value feedback unit 603. The starting request receiving unit 601 is configured to receive a starting request initiated by a first cloud mobile phone application to which a current first interface belongs; a second cloud mobile phone application determining unit 602 configured to determine, according to the start request, a second cloud mobile phone application to which a second interface to be started belongs; a start disallowance return value feedback unit 603 configured to generate a target return value representing a start failure in response to the second cloud mobile phone application belonging to the cloud mobile phone application that is not allowed to be started, and feed back the target return value to the first cloud mobile phone application.

In this embodiment, in the cloud mobile phone application start control apparatus 600: the specific processing of the start request receiving unit 601, the second cloud mobile phone application determining unit 602, and the disallowed start return value feedback unit 603 and the technical effects thereof may refer to the related descriptions of step 201 and step 203 in the corresponding embodiment of fig. 2, which are not described herein again.

In some optional implementations of this embodiment, the second cloud mobile phone application determining unit 602 may be further configured to:

extracting an interface name and/or an application name in the starting request;

taking the interface corresponding to the interface name as a second interface;

determining the cloud mobile phone application to which the second interface belongs and the cloud mobile phone application corresponding to the application name as a second cloud mobile phone application; when only the application name is extracted, the second interface is a default interface or a representative interface of the second cloud mobile phone application corresponding to the application name.

In some optional implementation manners of this embodiment, the cloud mobile phone application start control apparatus 600 may further include:

the same-application internal jumping unit is configured to jump to a second interface in response to the second cloud mobile phone application being the first cloud mobile phone application;

the white list application starting unit is configured to start the second cloud mobile phone application in response to the second cloud mobile phone application not being the first cloud mobile phone application and belonging to a white list application which is set for the first cloud mobile phone application in advance.

In some optional implementation manners of this embodiment, the cloud mobile phone application start control apparatus 600 may further include:

and the waiting state termination unit is configured to control the first cloud mobile phone application to terminate the waiting state of the starting request according to the target return value.

In some optional implementation manners of this embodiment, the cloud mobile phone application start control apparatus 600 may further include:

the malicious application detection unit is configured to detect malicious applications of the second cloud mobile phone application which is not allowed to be started;

and the malicious application attempted starting processing unit is configured to respond to the detection result that the malicious application belongs to the malicious application, return notification information of the attempted starting of the malicious application through a preset path, and record the cloud resource account initiating the starting request.

In some optional implementation manners of this embodiment, the cloud mobile phone application start control apparatus 600 may further include:

the intercepting times counting unit is configured to count the intercepting times of each second cloud mobile phone application which is not allowed to be started within a preset time period;

the target cloud mobile phone application determining unit is configured to mark the second cloud mobile phone application with the interception times exceeding the preset times as a target cloud mobile phone application;

the application customizing unit is configured to adjust and obtain a customized version of the cloud mobile phone application meeting the current cloud mobile phone environment requirement according to the functional characteristics of the target cloud mobile phone application;

and the substitute version providing unit is configured to respond to the fact that the customized cloud mobile phone application is successfully installed in the current cloud mobile phone environment, and provide the customized cloud mobile phone application to the user attempting to start as the starting-allowed version of the target cloud mobile phone application which is not allowed to start originally.

The cloud mobile phone application start control device provided in this embodiment is configured to configure, in advance, a cloud mobile phone application that is not allowed to be started for each cloud mobile phone, and when it is determined that a second cloud mobile phone application that initiates a start request through a first cloud mobile phone application belongs to the cloud mobile phone application that is not allowed to be started, generate a return value representing a start failure to the first cloud mobile phone application by itself, so that the first cloud mobile phone application can determine that the sent start request has been replied according to the received return value, and the start request is not in an on-hook and reply-waiting state for a period of time when a response is not received, thereby reducing occupation of cloud mobile phone resources by an invalid request that is on-hook, and improving performance of the cloud mobile phone.

According to an embodiment of the present disclosure, the present disclosure also provides an electronic device including: at least one processor; and a memory communicatively coupled to the at least one processor; the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can implement the cloud mobile phone application starting control method described in any of the above embodiments when executing the instructions.

According to an embodiment of the present disclosure, a readable storage medium is further provided, where the readable storage medium stores computer instructions, and the computer instructions are configured to enable a computer to implement the cloud mobile phone application start control method described in any of the above embodiments when executed.

The embodiment of the disclosure provides a computer program product, and when the computer program is executed by a processor, the method for controlling the start of the cloud mobile phone application described in any of the above embodiments can be implemented.

FIG. 7 illustrates a schematic block diagram of an example electronic device 700 that can be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 7, the device 700 comprises a computing unit 701, which may perform various suitable actions and processes according to a computer program stored in a Read Only Memory (ROM)702 or a computer program loaded from a storage unit 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data required for the operation of the device 700 can also be stored. The computing unit 701, the ROM 702, and the RAM 703 are connected to each other by a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.

Various components in the device 700 are connected to the I/O interface 705, including: an input unit 706 such as a keyboard, a mouse, or the like; an output unit 707 such as various types of displays, speakers, and the like; a storage unit 708 such as a magnetic disk, optical disk, or the like; and a communication unit 709 such as a network card, modem, wireless communication transceiver, etc. The communication unit 709 allows the device 700 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.

Computing unit 701 may be a variety of general purpose and/or special purpose processing components with processing and computing capabilities. Some examples of the computing unit 701 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The computing unit 701 executes the respective methods and processes described above, such as the cloud mobile phone application start control method. For example, in some embodiments, the cloud handset application launch control method may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 708. In some embodiments, part or all of a computer program may be loaded onto and/or installed onto device 700 via ROM 702 and/or communications unit 709. When the computer program is loaded into the RAM 703 and executed by the computing unit 701, one or more steps of the cloud handset application launch control method described above may be performed. Alternatively, in other embodiments, the computing unit 701 may be configured to perform the cloud handset application launch control method by any other suitable means (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.

The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The Server may be a cloud Server, which is also called a cloud computing Server or a cloud host, and is a host product in a cloud computing service system, so as to solve the defects of high management difficulty and weak service extensibility in the conventional physical host and Virtual Private Server (VPS) service.

According to the technical scheme of the embodiment of the disclosure, the cloud mobile phone applications which are not allowed to be started are configured for each cloud mobile phone in advance, and when the second cloud mobile phone application which initiates the starting request through the first cloud mobile phone application is determined to belong to the cloud mobile phone applications which are not allowed to be started, the return value which represents the starting failure is automatically generated to the first cloud mobile phone application, so that the first cloud mobile phone application can judge that the sent starting request is replied according to the received return value, the starting request is not in an on-hook state and a reply waiting state during the period that the starting request is not received, the occupation of the suspended invalid request on the cloud mobile phone resources is reduced, and the performance of the cloud mobile phone is improved.

It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present disclosure may be executed in parallel, sequentially, or in different orders, as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved, and the present disclosure is not limited herein.

The above detailed description should not be construed as limiting the scope of the disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present disclosure should be included in the scope of protection of the present disclosure.