[go: up one dir, main page]

CN113703793B - Application installation method, device, equipment and medium for cloud mobile phone - Google Patents

Application installation method, device, equipment and medium for cloud mobile phone Download PDF

Info

Publication number
CN113703793B
CN113703793B CN202110974766.XA CN202110974766A CN113703793B CN 113703793 B CN113703793 B CN 113703793B CN 202110974766 A CN202110974766 A CN 202110974766A CN 113703793 B CN113703793 B CN 113703793B
Authority
CN
China
Prior art keywords
dictionary file
identification
target application
application
mobile phone
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202110974766.XA
Other languages
Chinese (zh)
Other versions
CN113703793A (en
Inventor
杨杰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Baidu Netcom Science and Technology Co Ltd
Original Assignee
Beijing Baidu Netcom Science and Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Baidu Netcom Science and Technology Co Ltd filed Critical Beijing Baidu Netcom Science and Technology Co Ltd
Priority to CN202110974766.XA priority Critical patent/CN113703793B/en
Publication of CN113703793A publication Critical patent/CN113703793A/en
Application granted granted Critical
Publication of CN113703793B publication Critical patent/CN113703793B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/61Installation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/16File or folder operations, e.g. details of user interfaces specifically adapted to file systems

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Telephone Function (AREA)

Abstract

The disclosure provides an application installation method, device, equipment and medium for a cloud mobile phone, relates to the technical field of cloud computing, and particularly relates to the technical field of cloud mobile phones. The specific implementation scheme is as follows: responding to an installation request of a current cloud mobile phone to a target application, locking a pre-configured dictionary file, and checking whether the dictionary file contains the identification of the target application or not, wherein the dictionary file is used for recording the identification of the application being installed; writing the identification of the target application into the dictionary file and unlocking the dictionary file in response to the fact that the identification of the target application does not exist in the dictionary file; and starting the installation flow of the target application for the current cloud mobile phone, and deleting the identification of the target application from the dictionary file after the installation is completed. The method and the device can realize that the application can be successfully installed under the condition that a plurality of cloud mobile phones managed under the same cloud server simultaneously request to install the same application.

Description

Application installation method, device, equipment and medium for cloud mobile phone
Technical Field
The disclosure relates to the technical field of cloud computing, in particular to the technical field of cloud mobile phones, and specifically relates to an application installation method, device, equipment and medium for a cloud mobile phone.
Background
A cloud mobile phone (Cloudphone) is a mobile phone which applies cloud computing technology to network terminal services and realizes cloud services through a cloud server. Such a mobile phone can realize a plurality of functions through a network by means of a self-contained system and a network terminal erected by a manufacturer.
For example, a cloud desktop on the cloud mobile phone provides a function of installing an application, the cloud mobile phone downloads an application installation package, and a system installer of the cloud server is called up to install the installation package.
Disclosure of Invention
The disclosure provides an application installation method, device, equipment and medium for a cloud mobile phone.
According to an aspect of the present disclosure, there is provided an application installation method for a cloud mobile phone, including:
responding to an installation request of a current cloud mobile phone to a target application, locking a pre-configured dictionary file, and checking whether the dictionary file contains the identification of the target application or not, wherein the dictionary file is used for recording the identification of the application being installed;
writing the identification of the target application into the dictionary file and unlocking the dictionary file in response to the fact that the identification of the target application does not exist in the dictionary file;
and starting the installation flow of the target application for the current cloud mobile phone, and deleting the identification of the target application from the dictionary file after the installation is completed.
According to another aspect of the present disclosure, there is provided an application installation apparatus for a cloud mobile phone, including:
the dictionary file checking module is used for responding to the installation request of the current cloud mobile phone to the target application, locking a pre-configured dictionary file and checking whether the dictionary file has the identification of the target application or not, wherein the dictionary file is used for recording the identification of the application being installed;
the dictionary file writing module is used for writing the identification of the target application into the dictionary file and unlocking the dictionary file in response to the fact that the identification of the target application does not exist in the dictionary file;
and the installation starting module is used for starting the installation flow of the target application for the current cloud mobile phone, and deleting the identification of the target application from the dictionary file after the installation is completed.
According to another aspect of the present disclosure, there is provided an electronic device including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the application installation method for a cloud handset of any embodiment of the disclosure.
According to another aspect of the present disclosure, there is provided a non-transitory computer-readable storage medium storing computer instructions for causing a computer to execute the application installation method for a cloud mobile phone according to any embodiment of the present disclosure.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.
Drawings
The drawings are for a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:
fig. 1 is a schematic diagram of an application installation method for a cloud handset according to an embodiment of the disclosure;
FIG. 2 is a schematic diagram of an application installation method for a cloud handset, according to an embodiment of the disclosure;
FIG. 3 is a schematic diagram of an application installation method for a cloud handset according to an embodiment of the disclosure;
fig. 4 is a schematic structural view of an application installation apparatus for a cloud mobile phone according to an embodiment of the present disclosure;
fig. 5 is a block diagram of an electronic device used to implement an application installation method for a cloud handset according to an embodiment of the disclosure.
Description of the embodiments
Exemplary embodiments of the present disclosure are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present disclosure to facilitate understanding, and should be considered as merely exemplary. Accordingly, one 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.
In the prior art, when two or more cloud mobile phones simultaneously install the same application, only one cloud mobile phone can be successfully installed, and other cloud mobile phones can fail to be installed, so that the success rate of application installation of the cloud mobile phones is affected. According to the technical scheme, the problem can be solved, the success rate of application installation in the cloud mobile phone scene is improved, and the cloud mobile phone user experience is improved.
Fig. 1 is a flow chart of an application installation method for a cloud mobile phone according to an embodiment of the present disclosure, where the embodiment may be applicable to a case how to install an application for a cloud mobile phone user after the cloud mobile phone user initiates an installation request for any target application through a cloud desktop, especially a case where multiple cloud mobile phone users initiate an installation request for the same application at the same time, and relates to the technical field of cloud computing, especially to the technical field of cloud mobile phones. The method may be performed by an application installation apparatus for a cloud handset, which is implemented in software and/or hardware, preferably configured in an electronic device, such as a server or computer device. As shown in fig. 1, the method specifically includes the following steps:
s101, responding to an installation request of a current cloud mobile phone for a target application, locking a pre-configured dictionary file, and checking whether the dictionary file stores the identification of the target application or not, wherein the dictionary file is used for recording the identification of the application being installed.
Generally, the cloud server is responsible for managing cloud desktops of a plurality of cloud mobile phones, and a cloud mobile phone user logs in the cloud desktop on a terminal of the cloud mobile phone user by using a pre-registered account, so that an installation request for any application can be initiated through the cloud desktop. Thus, there may be a case where a plurality of cloud mobile phone users initiate installation requests to the same application at the same time. The term "simultaneously" as used herein means that when the first user has not yet installed, a second user initiates an installation request for the same application, and in the prior art, the second user fails to install.
To avoid the above-described problem, in the embodiment of the present disclosure, a dictionary file for recording the identification of the application being installed is configured in advance, for example, may be implemented by means of a dictionary lock or the like. The cloud server receives an installation request of any current cloud mobile phone for any target application, responds to the request, locks the dictionary file first, and then checks whether the dictionary file stores the identification of the target application or not. And if the target application is stored, the target application is installed for other cloud mobile phones, and if the target application is not stored, the target application is not installed for other cloud mobile phones currently.
S102, in response to the fact that the dictionary file does not store the identification of the target application, the identification of the target application is written into the dictionary file, and the dictionary file is unlocked.
And when the dictionary file does not store the identification of the target application, the target application can be installed for the current cloud mobile phone. Thus, the identification of the target application is written into the dictionary file first for recording and indicating that the target application is being installed, and then the dictionary file is unlocked, so that when other cloud mobile phones initiate an installation request for a certain application, the cloud server can lock and check the dictionary file again.
S103, starting an installation flow of the target application for the current cloud mobile phone, and deleting the identification of the target application from the dictionary file after the installation is completed.
And the cloud server starts an installation flow, namely, a system installer is called up to install the downloaded installation package. After the cloud mobile phone is installed, the icon of the target application can be displayed on the cloud desktop of the current cloud mobile phone user, and the user can use the target application through the cloud desktop.
When the installation of the target application is completed, the cloud server also needs to delete the identification of the target application from the dictionary file, which indicates that the application has been installed. Specifically, the dictionary file is locked, then the identifier of the installed target application is deleted, and the dictionary file is unlocked after the deletion.
According to the technical scheme, the dictionary file is pre-configured to record the identification of the application being installed, in response to the installation request of any application, the cloud server needs to lock and check whether the dictionary file stores the identification of the application, if not, the current application is not requested to be installed by other cloud mobile phones, and then the application can be installed for the current cloud mobile phones. Therefore, a plurality of cloud mobile phones managed under the same cloud server can successfully install the application under the condition of simultaneously requesting to install the same application, the success rate of application installation in a cloud mobile phone scene is improved, and the user experience of the cloud mobile phone is also improved.
Fig. 2 is a flowchart of an application installation method for a cloud mobile phone according to an embodiment of the present disclosure, where the embodiment is further optimized based on the above embodiment. As shown in fig. 2, the method specifically includes the following steps:
s201, responding to an installation request of the current cloud mobile phone to the target application, and locking a pre-configured dictionary file.
The dictionary file can be locked in a file locking mode.
S202, checking whether the dictionary file has the identification of the target application, if so, executing S203, returning to execute S201, if not, executing S204,
wherein the dictionary file is used for recording the identification of the application being installed.
S203, unlocking the dictionary file.
Specifically, when the dictionary file stores the identifier of the target application, it indicates that the target application is currently being installed for other cloud mobile phones, so that it is necessary to wait for retry. First, unlocking the dictionary file, then waiting for a first preset time, attempting to lock the dictionary file again, and checking the dictionary file. That is, every first preset time, the operations of locking the dictionary file and checking whether the dictionary file has the identification of the target application are re-executed until the dictionary file does not have the identification of the target application. At this time, it indicates that the target application has been installed for the previous cloud mobile phone user, and the installation may be performed for the current cloud mobile phone user, and then S204 is performed.
S204, writing the identification of the target application into the dictionary file, and unlocking the dictionary file.
The object of writing the identification of the target application into the dictionary file is that if other cloud mobile phones initiate an installation request for the target application in the process of installing the target file for the current cloud mobile phone, the target application can be determined to be installed by checking the dictionary file, and then the installation of the target application for other cloud mobile phones needs to be tried again after waiting.
S205, starting an installation flow of the target application for the current cloud mobile phone, and deleting the identification of the target application from the dictionary file after the installation is completed.
After the target application is installed, the target application can be installed for other cloud mobile phones, so that the identification of the target application needs to be deleted from the dictionary file.
In addition, in the process of locking the dictionary file, there may be a case that the locking is unsuccessful, so the locking the dictionary file configured in advance may further include:
if the dictionary file is successfully locked, executing the operation of checking whether the dictionary file stores the identification of the target application or not;
and if the dictionary file is not successfully locked, re-executing the operation of locking the dictionary file every second preset time until the locking is successful.
That is, if locking the dictionary file is unsuccessful, it is possible to wait for a later retry, and thus, the success rate of locking the dictionary file can be improved.
Further, in order to avoid falling into a dead loop, if the locking of the dictionary file is unsuccessful and the total duration of the re-execution of the locking operation exceeds a third preset time, the dictionary file may be forcibly unlocked. For example, the last time the dictionary file is locked, the corresponding cloud desktop crashes, or is forced to crash out of process, at which time the dictionary file becomes a deadlock. Therefore, in order to avoid the situation, when the conditions are met, forced breakthrough is carried out to read the dictionary file, and the success rate of locking the dictionary file is further improved.
According to the technical scheme, the dictionary file is pre-configured to record the identification of the application being installed, in addition, in response to the installation request of any application, the cloud server needs to lock and check whether the dictionary file stores the identification of the application or not, if the dictionary file does not store the identification, the current application is not requested to be installed by other cloud mobile phones, then the application can be installed for the current cloud mobile phones, if the dictionary file does not store the identification of the application, and if the dictionary file does store the identification of the application for other cloud mobile phones, locking and checking the dictionary file again after waiting for a preset time can be performed until the dictionary file is checked to have no identification of the application, and then the application can be installed for the current cloud mobile phones. Therefore, the application can be successfully installed under the condition that a plurality of cloud mobile phones managed under the same cloud server simultaneously request to install the same application, the success rate of application installation in a cloud mobile phone scene is improved, and the user experience of the cloud mobile phones is also improved.
Fig. 3 is a flowchart of an application installation method for a cloud mobile phone according to an embodiment of the present disclosure, where the embodiment is further optimized based on the above embodiment. As shown in fig. 3, the method specifically includes the following steps:
s301, unlocking the dictionary file in response to the starting operation of the cloud desktop of any target cloud mobile phone.
Wherein the dictionary file is used for recording the identification of the application being installed.
S302, locking the dictionary file again, deleting the user identification corresponding to the target cloud mobile phone and the application identification corresponding to the user identification from the dictionary file, and unlocking the dictionary file.
S303, responding to an installation request of the current cloud mobile phone to the target application, and locking a pre-configured dictionary file.
S304, checking whether the dictionary file has the identification of the target application, executing S305 if the dictionary file has the identification of the target application, returning to execute S303, and executing S306 if the dictionary file has no identification of the target application.
S305, unlocking the dictionary file.
S306, writing the identification of the target application and the user identification corresponding to the current cloud mobile phone into the dictionary file, and unlocking the dictionary file.
S307, starting an installation flow of the target application for the current cloud mobile phone, and deleting the identification of the target application and the user identification corresponding to the current cloud mobile phone from the dictionary file after the installation is completed.
In the embodiment of the present disclosure, the content written into the dictionary file includes, in addition to the application identifier described in the foregoing embodiment, a user identifier corresponding to the current cloud mobile phone, that is, a user identifier of each cloud mobile phone managed by the cloud server at the cloud server side. Correspondingly, after the application is installed, the application identifier and the user identifier are deleted from the dictionary file.
Correspondingly, when the cloud server starts the cloud desktop of any target cloud mobile phone for the first time, the cloud server firstly unlocks the dictionary file, then retries locking, deletes related items such as the application unique identifier and the user identifier corresponding to the target cloud mobile phone after locking is successful, and unlocks after deleting. The method aims at avoiding the problem that the file lock of the dictionary file becomes deadlock due to special conditions such as abnormal closing of the cloud desktop of the target cloud mobile phone, so that the follow-up use is affected.
According to the technical scheme, for the first starting of the cloud desktop, the dictionary file unlocking operation is executed, then the locking, deleting and unlocking operations are executed, and then the dictionary file can be normally used. The problem that the subsequent use is affected due to the fact that the file lock of the dictionary file becomes a deadlock caused by special conditions such as abnormal closing of the cloud desktop can be avoided. The success rate of application installation in the cloud mobile phone scene is further improved, and the cloud mobile phone user experience is also improved.
Fig. 4 is a schematic structural diagram of an application installation device for a cloud mobile phone according to an embodiment of the present disclosure, where the embodiment may be applicable to a case how to install an application for a cloud mobile phone user after the cloud mobile phone user initiates an installation request for any target application through a cloud desktop, especially a case where multiple cloud mobile phone users initiate an installation request for the same application at the same time, and relates to the technical field of cloud computing, especially to the technical field of cloud mobile phones. The device can realize the application installation method for the cloud mobile phone according to any embodiment of the disclosure. As shown in fig. 4, the apparatus 400 specifically includes:
a dictionary file checking module 401, configured to respond to an installation request of a current cloud mobile phone for a target application, lock a pre-configured dictionary file, and check whether an identifier of the target application exists in the dictionary file, where the dictionary file is used to record an identifier of the application being installed;
a dictionary file writing module 402, configured to write the identifier of the target application into the dictionary file and unlock the dictionary file in response to the identifier of the target application not being stored in the dictionary file;
and the installation starting module 403 is configured to start an installation process of the target application for the current cloud mobile phone, and delete the identifier of the target application from the dictionary file after the installation is completed.
Optionally, the apparatus further includes:
the dictionary file unlocking module is used for responding to the dictionary file in which the identification of the target application is stored and unlocking the dictionary file;
and the loop execution module is used for re-executing the operations of locking the dictionary file and checking whether the dictionary file contains the identification of the target application or not every first preset time until the dictionary file does not contain the identification of the target application.
Optionally, the dictionary file checking module 401 is specifically configured to:
if the dictionary file is successfully locked, executing the operation of checking whether the dictionary file contains the identification of the target application or not;
and if the dictionary file is not successfully locked, re-executing the operation of locking the dictionary file every second preset time until the locking is successful.
Optionally, the dictionary file checking module 401 is specifically further configured to:
and if the dictionary file is not successfully locked, and the total time length for re-executing the locking operation exceeds a third preset time, the dictionary file is forcedly unlocked.
Optionally, the dictionary file writing module 402 is specifically configured to:
writing the identification of the target application and the user identification corresponding to the current cloud mobile phone into the dictionary file;
accordingly, the installation initiation module 403 is specifically configured to:
and deleting the identification of the target application and the user identification corresponding to the current cloud mobile phone from the dictionary file.
Optionally, the device further comprises a start processing module, specifically configured to:
unlocking the dictionary file in response to the starting operation of the cloud desktop of any target cloud mobile phone;
and locking the dictionary file again, deleting the user identification corresponding to the target cloud mobile phone and the application identification corresponding to the user identification from the dictionary file, and unlocking the dictionary file.
Optionally, the dictionary file is implemented by means of a dictionary lock.
The product can execute the method provided by any embodiment of the disclosure, and has the corresponding functional modules and beneficial effects of executing the method.
It should be noted that, in the technical solution of the present disclosure, the related processes of collecting, storing, using, processing, transmitting, providing, disclosing, etc. of the personal information of the user all conform to the rules of the related laws and regulations, and do not violate the popular regulations.
According to embodiments of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.
Fig. 5 illustrates a schematic block diagram of an example electronic device 500 that may 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 telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the disclosure described and/or claimed herein.
As shown in fig. 5, the apparatus 500 includes a computing unit 501 that can perform various suitable actions and processes according to a computer program stored in a Read Only Memory (ROM) 502 or a computer program loaded from a storage unit 508 into a Random Access Memory (RAM) 503. In the RAM 503, various programs and data required for the operation of the device 500 can also be stored. The computing unit 501, ROM 502, and RAM 503 are connected to each other by a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.
Various components in the device 500 are connected to the I/O interface 505, including: an input unit 506 such as a keyboard, a mouse, etc.; an output unit 507 such as various types of displays, speakers, and the like; a storage unit 508 such as a magnetic disk, an optical disk, or the like; and a communication unit 509 such as a network card, modem, wireless communication transceiver, etc. The communication unit 509 allows the device 500 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.
The computing unit 501 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 501 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, etc. The computing unit 501 performs the respective methods and processes described above, for example, an application installation method for a cloud cellular phone. For example, in some embodiments, the application installation method for a cloud handset may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as storage unit 508. In some embodiments, part or all of the computer program may be loaded and/or installed onto the device 500 via the ROM 502 and/or the communication unit 509. When the computer program is loaded into RAM 503 and executed by computing unit 501, one or more steps of the application installation method for a cloud handset described above may be performed. Alternatively, in other embodiments, the computing unit 501 may be configured to perform the application installation method for a cloud handset 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 circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On 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, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program code 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 code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. 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. The 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 pointing device (e.g., a mouse or 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 may 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 input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background 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 background, 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), blockchain networks, and the internet.
The computer system may include a client and a server. The client and server are typically 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 can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome. The server may also be a server of a distributed system or a server that incorporates a blockchain.
Artificial intelligence is the discipline of studying the process of making a computer mimic certain mental processes and intelligent behaviors (e.g., learning, reasoning, thinking, planning, etc.) of a person, both hardware-level and software-level techniques. Artificial intelligence hardware technologies generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing, and the like; the artificial intelligent software technology mainly comprises a computer vision technology, a voice recognition technology, a natural language processing technology, a machine learning/deep learning technology, a big data processing technology, a knowledge graph technology and the like.
Cloud computing (cloud computing) refers to a technical system that a shared physical or virtual resource pool which is elastically extensible is accessed through a network, resources can comprise servers, operating systems, networks, software, applications, storage devices and the like, and resources can be deployed and managed in an on-demand and self-service mode. Through cloud computing technology, high-efficiency and powerful data processing capability can be provided for technical application such as artificial intelligence and blockchain, and model training.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps recited in the present disclosure may be performed in parallel, sequentially, or in a different order, provided that the desired results of the technical solutions provided by the present disclosure are achieved, and are not limited herein.
The above detailed description should not be taken as limiting the scope of the present disclosure. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present disclosure are intended to be included within the scope of the present disclosure.

Claims (14)

1. An application installation method for a cloud mobile phone, comprising:
responding to an installation request of a current cloud mobile phone to a target application, locking a pre-configured dictionary file, and checking whether the dictionary file contains the identification of the target application or not, wherein the dictionary file is used for recording the identification of the application being installed;
writing the identification of the target application into the dictionary file and unlocking the dictionary file in response to the fact that the identification of the target application does not exist in the dictionary file;
starting an installation flow of the target application for the current cloud mobile phone, and deleting the identification of the target application from the dictionary file after the installation is completed;
unlocking the dictionary file in response to the dictionary file storing the identification of the target application;
and re-executing the operations of locking the dictionary file and checking whether the identification of the target application exists in the dictionary file or not every first preset time until the identification of the target application does not exist in the dictionary file.
2. The method of claim 1, wherein the locking the pre-configured dictionary file comprises:
if the dictionary file is successfully locked, executing the operation of checking whether the dictionary file contains the identification of the target application or not;
and if the dictionary file is not successfully locked, re-executing the operation of locking the dictionary file every second preset time until the locking is successful.
3. The method of claim 2, wherein the locking the pre-configured dictionary file further comprises:
and if the dictionary file is not successfully locked, and the total time length for re-executing the locking operation exceeds a third preset time, the dictionary file is forcedly unlocked.
4. The method of claim 1, wherein the writing the identification of the target application to the dictionary file comprises:
writing the identification of the target application and the user identification corresponding to the current cloud mobile phone into the dictionary file;
correspondingly, the deleting the identification of the target application from the dictionary file comprises the following steps:
and deleting the identification of the target application and the user identification corresponding to the current cloud mobile phone from the dictionary file.
5. The method of claim 4, further comprising:
unlocking the dictionary file in response to the starting operation of the cloud desktop of any target cloud mobile phone;
and locking the dictionary file again, deleting the user identification corresponding to the target cloud mobile phone and the application identification corresponding to the user identification from the dictionary file, and unlocking the dictionary file.
6. The method of claim 1, wherein the dictionary file is implemented by way of a dictionary lock.
7. An application installation apparatus for a cloud mobile phone, comprising:
the dictionary file checking module is used for responding to the installation request of the current cloud mobile phone to the target application, locking a pre-configured dictionary file and checking whether the dictionary file has the identification of the target application or not, wherein the dictionary file is used for recording the identification of the application being installed;
the dictionary file writing module is used for writing the identification of the target application into the dictionary file and unlocking the dictionary file in response to the fact that the identification of the target application does not exist in the dictionary file;
the installation starting module is used for starting the installation flow of the target application for the current cloud mobile phone, and deleting the identification of the target application from the dictionary file after the installation is completed;
the dictionary file unlocking module is used for responding to the dictionary file in which the identification of the target application is stored and unlocking the dictionary file;
and the loop execution module is used for re-executing the operations of locking the dictionary file and checking whether the dictionary file contains the identification of the target application or not every first preset time until the dictionary file does not contain the identification of the target application.
8. The apparatus of claim 7, wherein the dictionary file checking module is specifically configured to:
if the dictionary file is successfully locked, executing the operation of checking whether the dictionary file contains the identification of the target application or not;
and if the dictionary file is not successfully locked, re-executing the operation of locking the dictionary file every second preset time until the locking is successful.
9. The apparatus of claim 8, wherein the dictionary file checking module is further specifically configured to:
and if the dictionary file is not successfully locked, and the total time length for re-executing the locking operation exceeds a third preset time, the dictionary file is forcedly unlocked.
10. The apparatus of claim 7, wherein the dictionary file writing module is specifically configured to:
writing the identification of the target application and the user identification corresponding to the current cloud mobile phone into the dictionary file;
correspondingly, the installation starting module is specifically used for:
and deleting the identification of the target application and the user identification corresponding to the current cloud mobile phone from the dictionary file.
11. The apparatus of claim 10, further comprising a start-up processing module, in particular for:
unlocking the dictionary file in response to the starting operation of the cloud desktop of any target cloud mobile phone;
and locking the dictionary file again, deleting the user identification corresponding to the target cloud mobile phone and the application identification corresponding to the user identification from the dictionary file, and unlocking the dictionary file.
12. The apparatus of claim 7, wherein the dictionary file is implemented by way of a dictionary lock.
13. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the application installation method for a cloud handset of any one of claims 1-6.
14. A non-transitory computer-readable storage medium storing computer instructions for causing a computer to execute the application installation method for a cloud cellular phone according to any one of claims 1 to 6.
CN202110974766.XA 2021-08-24 2021-08-24 Application installation method, device, equipment and medium for cloud mobile phone Active CN113703793B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110974766.XA CN113703793B (en) 2021-08-24 2021-08-24 Application installation method, device, equipment and medium for cloud mobile phone

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110974766.XA CN113703793B (en) 2021-08-24 2021-08-24 Application installation method, device, equipment and medium for cloud mobile phone

Publications (2)

Publication Number Publication Date
CN113703793A CN113703793A (en) 2021-11-26
CN113703793B true CN113703793B (en) 2024-01-16

Family

ID=78654468

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110974766.XA Active CN113703793B (en) 2021-08-24 2021-08-24 Application installation method, device, equipment and medium for cloud mobile phone

Country Status (1)

Country Link
CN (1) CN113703793B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114281398A (en) * 2021-12-10 2022-04-05 西安万像电子科技有限公司 Cloud mobile phone application management method, electronic device and storage medium

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111177776A (en) * 2019-12-20 2020-05-19 平安资产管理有限责任公司 Multi-tenant data isolation method and system
CN112084021A (en) * 2020-08-14 2020-12-15 刘俊锋 Interface configuration method, device and equipment of education system and readable storage medium

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9710821B2 (en) * 2011-09-15 2017-07-18 Stephan HEATH Systems and methods for mobile and online payment systems for purchases related to mobile and online promotions or offers provided using impressions tracking and analysis, location information, 2D and 3D mapping, mobile mapping, social media, and user behavior and

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111177776A (en) * 2019-12-20 2020-05-19 平安资产管理有限责任公司 Multi-tenant data isolation method and system
CN112084021A (en) * 2020-08-14 2020-12-15 刘俊锋 Interface configuration method, device and equipment of education system and readable storage medium

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
已开发的MIS软件数据字典的应用管理;王继德,郑广海;中国金融电脑(第04期);全文 *

Also Published As

Publication number Publication date
CN113703793A (en) 2021-11-26

Similar Documents

Publication Publication Date Title
CN113766487B (en) Cloud mobile phone information acquisition method, device, equipment and medium
CN113703793B (en) Application installation method, device, equipment and medium for cloud mobile phone
CN106528333A (en) A data backup method and device
US20230144949A1 (en) Virtual-machine cold migration method and apparatus, electronic device and storage medium
CN112965799B (en) Task state prompting method and device, electronic equipment and medium
CN114401121A (en) Application program login method and device, electronic equipment and readable storage medium
CN107657155B (en) Method and device for authenticating user operation authority
CN115328621B (en) Transaction processing method, device, equipment and storage medium based on block chain
CN113051055A (en) Task processing method and device
CN116755725A (en) Configuration rollback method, device and apparatus based on configuration file, and storage medium
CN115798469A (en) Voice control method and device, electronic equipment and computer readable storage medium
CN114091909A (en) A method, system, device and electronic device for collaborative development
CN115390992A (en) Virtual machine creating method, device, equipment and storage medium
CN114228745A (en) Driving system module control method, device, equipment, medium, product and vehicle
CN114237755A (en) Application operating method, apparatus, electronic device, and storage medium
CN113660635A (en) Connection method, connection device, electronic apparatus, storage medium, and program product
CN112596925B (en) Transaction data transmission method and device
CN113139891A (en) Image processing method, image processing device, electronic equipment and storage medium
CN115499420B (en) Data transmission method, device, electronic device and storage medium
CN114006902B (en) Cloud mobile phone restarting method, device, equipment and storage medium
CN114422638B (en) Cloud mobile phone control method, device, equipment, medium and program product
CN114428646B (en) Data processing method and device, electronic equipment and storage medium
CN115756768B (en) Distributed transaction processing method, device, equipment and medium based on saga
CN111352732B (en) Voice recognition process control method and device
CN113949767B (en) Method, device, electronic equipment and medium for realizing vehicle-mounted interaction

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant