CN113656105B - Keep-alive processing method for enterprise application, mobile terminal and storage medium - Google Patents
Keep-alive processing method for enterprise application, mobile terminal and storage medium Download PDFInfo
- Publication number
- CN113656105B CN113656105B CN202110956834.XA CN202110956834A CN113656105B CN 113656105 B CN113656105 B CN 113656105B CN 202110956834 A CN202110956834 A CN 202110956834A CN 113656105 B CN113656105 B CN 113656105B
- Authority
- CN
- China
- Prior art keywords
- keep
- alive
- application
- enterprise
- configuration information
- 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
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 26
- 238000000034 method Methods 0.000 claims abstract description 19
- 238000012545 processing Methods 0.000 claims abstract description 15
- 239000008186 active pharmaceutical agent Substances 0.000 description 21
- 238000012550 audit Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 10
- 238000004891 communication Methods 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 5
- 230000002093 peripheral effect Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000011161 development Methods 0.000 description 3
- 238000004590 computer program Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000033001 locomotion Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 101100055496 Arabidopsis thaliana APP2 gene Proteins 0.000 description 1
- 101100264195 Caenorhabditis elegans app-1 gene Proteins 0.000 description 1
- 101100016250 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) GYL1 gene Proteins 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000005286 illumination Methods 0.000 description 1
- 229910044991 metal oxide Inorganic materials 0.000 description 1
- 150000004706 metal oxides Chemical class 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000010076 replication Effects 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000010897 surface acoustic wave method Methods 0.000 description 1
- 239000000725 suspension Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/44—Program or device authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Mobile Radio Communication Systems (AREA)
- Stored Programmes (AREA)
- Telephone Function (AREA)
Abstract
The invention discloses a keep-alive processing method for enterprise applications, a mobile terminal and a storage medium. The keep-alive treatment method comprises the following steps: sending signature data of the keep-alive application to an authentication server for authentication to obtain authentication data of the keep-alive application; starting the authority of the keep-alive application to call the system API of the mobile terminal based on the authentication data; the keep-alive application obtains configuration information from the configuration server, wherein the configuration information comprises authority configuration information of the enterprise application, and the authority configuration information comprises keep-alive authority information; and calling a system API by the keep-alive application according to keep-alive authority information of the enterprise application, and carrying out keep-alive processing on the enterprise application.
Description
Technical Field
The present invention relates to the field of mobile internet, and in particular, to a keep-alive processing method for enterprise applications, a mobile terminal, and a storage medium.
Background
In the development of mobile applications facing enterprises, more and more scenarios need to ensure that enterprise applications are always in a surviving state and are not killed by an operating system (abbreviated as a system), such as instant messaging, real-time monitoring, timing task applications, and the like. But is limited by the power management and memory reclamation mechanism of the operating system of the mobile terminal, the enterprise application cannot survive for a long time in the background, and once the enterprise application is killed by the operating system, the enterprise application cannot wake up again through system broadcasting.
One solution is to modify the operating system source code of the mobile terminal by customizing the ROM to let the operating system keep-alive the enterprise applications. However, the customized ROM is complex in technical implementation, and related to system stability, compatibility, updating of the mobile terminal, and the like, and a complete solution is required, so that the workload is huge.
Disclosure of Invention
The present invention has been made in view of the above problems, and it is an object of the present invention to provide a keep-alive processing scheme for enterprise applications that overcomes or at least partially solves the above problems.
According to an aspect of the present invention, there is provided a keep-alive processing method of an enterprise application, executed in a mobile terminal in which the keep-alive application and a plurality of enterprise applications reside and which is communicatively connected with a configuration server and an authentication server, the method comprising:
sending the signature data of the keep-alive application to an authentication server for authentication to obtain the authentication data of the keep-alive application;
starting the authority of the keep-alive application to call the system API of the mobile terminal based on the authentication data;
the keep-alive application obtains configuration information from the configuration server, wherein the configuration information comprises authority configuration information of the enterprise application, and the authority configuration information comprises keep-alive authority information;
and calling a system API by the keep-alive application according to keep-alive authority information of the enterprise application, and carrying out keep-alive processing on the enterprise application.
Optionally, in the keep-alive processing method according to the present invention, the sending signature data of the keep-alive application to an authentication server for authentication includes: and after the keep-alive application is installed for the first time or version updating is carried out, the signature data of the keep-alive application is sent to an authentication server for authentication.
Optionally, in the keep-alive processing method according to the present invention, the keep-alive application obtains configuration information from the configuration server, including: and the keep-alive application acquires configuration information from the configuration server after receiving a start-up broadcast or a screen-off broadcast of the mobile terminal and when a preset condition is met.
Optionally, in the keep-alive processing method according to the invention, the predetermined condition is: the difference between the current time and the last time the configuration information was acquired is greater than a predetermined time interval.
Optionally, in the keep-alive processing method according to the present invention, the configuration information further includes a latest version number of the keep-alive application, and after the configuration information is acquired, the method further includes: and judging whether the version number of the keep-alive application is smaller than the latest version number or not, and if so, upgrading the keep-alive application to the latest version number.
Optionally, in the keep-alive processing method according to the present invention, the configuration information further includes a latest version number of the enterprise application, and after the configuration information is acquired, the method further includes: and the keep-alive application judges whether the version number of the enterprise application is smaller than the latest version number, and if so, the enterprise application is upgraded to the latest version number.
Optionally, in the keep-alive processing method according to the invention, the authority configuration information further includes other authority information of the enterprise application, and the method further includes: and calling a system API by the keep-alive application according to other authority information of the enterprise application, and setting the authority of the enterprise application.
Optionally, in the keep-alive processing method according to the present invention, the other authority information includes: the self-starting permission zone bit, the default zone bit, the anti-unloading zone bit and/or the run-time permission grant zone bit.
According to another aspect of the present invention, there is provided a mobile terminal including:
one or more processors;
a memory; and
one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for performing any of the keep-alive processing methods of an enterprise application in accordance with the invention.
According to another aspect of the present invention, there is provided a computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by a mobile terminal, cause the mobile terminal to perform any of the keep-alive processing methods of an enterprise application according to the present invention.
According to the keep-alive processing scheme of the enterprise application, the independent keep-alive APP is used as the proxy application, only a system manufacturer is required to check and sign the application, the enterprise application needing to keep-alive is obtained from the configuration server through the network, the keep-alive APP calls the system API to achieve the purpose of keeping the enterprise application alive, and the realization complexity of keeping the enterprise application alive is reduced.
The foregoing description is only an overview of the present invention, and is intended to be implemented in accordance with the teachings of the present invention in order that the same may be more clearly understood and to make the same and other objects, features and advantages of the present invention more readily apparent.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to designate like parts throughout the figures. In the drawings:
FIG. 1 illustrates a schematic diagram of a keep-alive processing system 100 for an enterprise application in accordance with one embodiment of the invention;
fig. 2 shows a schematic configuration diagram of a mobile terminal 200 according to an embodiment of the present invention;
FIG. 3 illustrates a flow chart of a keep-alive processing method 300 for an enterprise application in accordance with one embodiment of the invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
As described above, in order to keep-alive enterprise applications in mobile terminals, implementation schemes using custom ROMs are complex and introduce problems of system stability and compatibility.
Based on the problem, an operating system (e.g. Android system) manufacturer of the mobile terminal provides authentication service for enterprise applications, namely, the system manufacturer authenticates signature data of the enterprise applications, authentication data (e.g. audit signature of manufacturer) is returned after authentication is passed, after the enterprise applications acquire the manufacturer signature, the mobile terminal for installing the enterprise applications can open authority of the enterprise applications for calling system APIs of the mobile terminal based on the front of the manufacturer, and the enterprise applications can realize the keep-alive of the enterprise applications in the mobile terminal by calling the system APIs.
However, since the enterprise applications need to be authenticated again through the system manufacturer each time, the audit signature is obtained, and is influenced by the audit efficiency of the system manufacturer, so that the update time of the enterprise applications is uncontrollable.
Therefore, the scheme of the embodiment of the invention enables the keep-alive application to manage all other enterprise applications by specially setting one enterprise application, namely the keep-alive application, and taking the keep-alive application as a proxy of an operating system of the mobile terminal and other enterprise applications running in the mobile terminal, thereby realizing the keep-alive processing of the other enterprise applications.
FIG. 1 illustrates a schematic diagram of a keep-alive processing system 100 for an enterprise application in accordance with one embodiment of the invention. As shown in fig. 1, the system 100 includes a configuration server 110, an authentication server 120, and a mobile terminal 200.
The mobile terminal 200, i.e. a terminal device used by a user, may be, but not limited to, a mobile phone, a tablet computer, a multimedia device, an intelligent wearable device, etc. The mobile terminal 200 is communicatively connected to the configuration server 110 and the authentication server 120, respectively. The mobile terminal 200 has resident therein a keep-alive application (keep-alive APP) and a plurality of enterprise applications (APP 1, APP2, …, APPn), the enterprise applications (enterprise applicaton), i.e. enterprise-oriented mobile applications, n being the number of enterprise applications installed in the mobile terminal 200.
The authentication server 120 is a server set by a manufacturer of an operating system of the mobile terminal, and the authentication server 120 can perform authentication processing on various mobile applications, for example, in the embodiment of the invention, the authentication server 120 can perform authentication on the keep-alive APP, that is, audit is performed on signature data of the keep-alive APP, after the audit is passed, authentication data, that is, an audit signature of the manufacturer is generated, and after the keep-alive APP acquires the audit signature, in the mobile terminal, authority of a system API for calling the operating system can be acquired. After the keep-alive APP has the authority to call the system API, the APP can keep itself and other enterprise applications alive by calling the system API, and can set various authority settings for the other enterprise applications.
The configuration server 110 is a server of enterprise setting, the enterprise provides various enterprise applications, the user of the enterprise can install the enterprise applications in his mobile terminal, relevant personnel (such as application developer or manager) of the enterprise only need to perform keep-alive configuration or other authority configuration in the configuration server 110, the mobile terminal 200 can timely obtain the latest configuration information of the enterprise applications from the configuration server, keep-alive and authority setting of the enterprise applications can be simply and quickly realized, and the enterprise applications needing to be kept alive can be timely added and deleted.
The mobile terminal 200 is resident with the keep-alive APP and a plurality of enterprise applications, and the keep-alive APP is operated by communicating keep-alive, upgrade and authority settings of the enterprise applications to the keep-alive APP, so that developers of the enterprise applications do not need to consider the functions, and a large number of development tasks are omitted. Further, when the enterprise application has a version update, only the configuration information of the configuration server 110 needs to be modified, and the update is directly downloaded by the keep-alive APP without the need for the system manufacturer to review the signature again.
Fig. 2 is a schematic configuration diagram of a mobile terminal 200 according to an embodiment of the present invention. Referring to fig. 2, the mobile terminal 200 includes: a memory interface 202, one or more data processors, an image processor and/or a central processing unit 204, and a peripheral interface 206. The memory interface 202, the one or more processors 204 and/or the peripheral interface 206 may be discrete components or integrated in one or more integrated circuits. In the mobile terminal 200, the various elements may be coupled by one or more communication buses or signal lines. Sensors, devices, and subsystems may be coupled to peripheral interface 206 to facilitate various functions. For example, motion sensor 210, light sensor 212, and distance sensor 214 may be coupled to peripheral interface 206 to facilitate orientation, illumination, and ranging functions. Other sensors 216 may also be coupled to the peripheral interface 206, such as a positioning system (e.g., a GPS receiver), a temperature sensor, a biometric sensor, or other sensing device, to facilitate relevant functions.
The camera subsystem 220 and the optical sensor 222 may be used to facilitate implementation of camera functions such as recording photographs and video clips, where the camera subsystem 220 and the optical sensor 222 may be, for example, charge Coupled Devices (CCDs) or Complementary Metal Oxide Semiconductor (CMOS) optical sensors. Communication functions may be facilitated by one or more wireless communication subsystems 224, which may include radio frequency receivers and transmitters and/or optical (e.g., infrared) receivers and transmitters. The particular design and implementation of the wireless communication subsystem 224 may depend on the one or more communication networks supported by the mobile terminal 200. For example, mobile terminal 200 may include a network designed to support a GSM network, a GPRS network, an EDGE network, a 3G network, a 4G network, a 5G network, a Wi-Fi or WiMax network, and Bluetooth TM A communication subsystem 224 of the network. The audio subsystem 226 may be coupled with a speaker 228 and a microphone 230 to facilitate voice-enabled functions, such as voice recognition, voice replication, digital recording, and telephony functions.
The I/O subsystem 240 may include a touch screen controller 242 and/or one or more other input controllers 244. The touch screen controller 242 may be coupled to a touch screen 246. For example, the touch screen 246 and touch screen controller 242 can detect contact and movement or suspension therewith using any of a variety of touch sensing technologies including, but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies. One or more other input controllers 244 may be coupled to other input/control devices 248, such as one or more buttons, rocker switches, thumbwheels, infrared ports, USB ports, and/or pointing devices such as a stylus. The one or more buttons (not shown) may include up/down buttons for controlling the volume of speaker 228 and/or microphone 230.
The memory interface 202 may be coupled to a memory 250. The memory 250 may include system memory and storage devices. The system memory is, for example, high-speed random access memory, while the storage device is, for example, non-volatile memory, such as one or more magnetic disk storage devices, one or more optical storage devices, and/or flash memory (e.g., NAND, NOR), etc. The memory 250 may store an operating system 252, such as an operating system like Android, IOS, or Windows Phone. The operating system 252 may include instructions for handling basic system services and performing hardware dependent tasks. The memory 250 may also store one or more programs 254 (i.e., application programs, hereinafter referred to as applications). Programs 254, when executed, are loaded from memory 250 onto processor 204 and run on top of operating system 252, which has been executed by processor 204, and utilize the interface provided by operating system 252 and the underlying hardware to perform various user-desired functions, such as instant messaging, web browsing, picture management, and the like. The program 254 may be provided independently of the operating system or may be self-contained with the operating system.
In some embodiments, mobile terminal 200 is configured to perform keep-alive processing method 300 for an enterprise application in accordance with the invention. Wherein one or more programs 254 of mobile terminal 200 include instructions for executing keep-alive processing method 300 for an enterprise application in accordance with the invention.
FIG. 3 illustrates a flow chart of a keep-alive processing method 300 for an enterprise application in accordance with one embodiment of the invention. Referring to fig. 3, the method 300 begins at step S310, where signature data of a keep-alive application is sent to an authentication server for authentication to obtain authentication data of the keep-alive application in step S310. Specifically, the keep-alive application may be installed in the mobile terminal for the first time, and after version update of the keep-alive application, signature data of the keep-alive application may be sent to the authentication server for authentication. When the keep-alive APP is developed or the version is updated, signature data is uploaded to an authentication server of an operating system manufacturer of the mobile terminal to conduct audit signature, after authentication is successful, the authentication server sends the authentication data, namely the audit signature of the manufacturer, to the mobile terminal, and when the mobile terminal starts the keep-alive application, the mobile terminal prompts to start an enterprise mode. If the authentication server fails to authenticate the keep-alive application, signature data of a manufacturer cannot be returned, the mobile terminal cannot enable an enterprise mode, and the keep-alive application cannot have permission to call a system API.
After the enterprise mode is enabled, the method 300 proceeds to step S320. In step S320, the operating system of the mobile terminal opens the right for the keep-alive application to call the system API of the mobile terminal based on the authentication data. In the embodiment of the invention, the keep-alive application belongs to a system-level application, has high authority and needs to ensure the safety of the keep-alive application, so that the keep-alive application needs to check a signature every time the keep-alive application sends a edition update. When developing an operating system, a manufacturer can reserve signature data of the manufacturer in the operating system, and when receiving an instruction of an application installed on the operating system for requesting to start and call the system API, the operating system can verify whether authentication data carried by the request is consistent with the reserved audit signature of the manufacturer, and if so, the operating system starts the authority of the application for starting and calling the system API.
In step S330, the keep-alive application acquires (updates) the configuration information from the configuration server. In one implementation, the keep-alive application listens to the power-on broadcast and the off-screen broadcast of the mobile terminal, and when listening to the power-on broadcast of the mobile terminal or listening to the off-screen broadcast of the mobile terminal, the keep-alive application requests configuration information from the configuration server.
In another implementation manner, when the keep-alive application monitors the start-up broadcast of the mobile terminal or monitors the screen-off broadcast of the mobile terminal, whether the current time meets the preset condition is further judged. The predetermined condition may be that the difference between the current time and the last time the configuration information was acquired is greater than a predetermined time interval, for example 3600 seconds. In this way, the keep-alive application can be prevented from frequently acquiring configuration information from the configuration server.
For example, the keep-alive APP receives a start-up broadcast and a screen-off broadcast of the mobile terminal, checks a difference between a current timestamp mCurrentTime and a last acquisition configuration time mLastRequestConfigTime, and if the difference is smaller than a specified interval time requestInterval, no operation is performed, and the flow ends. If the request interval is greater than the specified interval time, the configuration information is acquired from the configuration server.
In the embodiment of the invention, the configuration information at least comprises keep-alive authority information of each enterprise application, namely whether a certain enterprise application has keep-alive authority, when the enterprise application has the keep-alive authority, the keep-alive application can perform keep-alive processing on the enterprise application, and when the enterprise application does not have the keep-alive authority, the keep-alive application does not perform keep-alive processing on the enterprise application. In one implementation, the configuration information includes a list of all enterprise applications, and each enterprise application in the list is associated with a flag bit that has keep-alive rights. In another implementation, the configuration information includes a white list of enterprise applications, i.e., enterprise applications that are in the white list have keep-alive rights, and enterprise applications that are not in the white list do not have keep-alive rights.
In some embodiments, the configuration information further includes rights configuration information for the enterprise application, including keep-alive rights information, and other rights information including, for example, a self-priming rights flag, a default flag, an anti-reload flag, and/or a runtime rights grant flag, etc. Thus, various rights configurations can be made for each enterprise application based on the configuration information.
In some embodiments, the configuration information may also include version information for each application and a download (update) address for the new version, including, for example, the latest version number of the keep-alive application, and including the latest version number of each enterprise application. Thus, the keep-alive application and the enterprise applications can be updated in version based on the configuration information.
The configuration information may be stored and transmitted in a Json structure. The Json structure of the configuration information is exemplified as follows:
after acquiring the configuration information, the method 300 proceeds to step S340. In step S340, the keep-alive application calls a system API according to keep-alive authority information of the enterprise application, and performs keep-alive processing on the enterprise application.
It should be noted that if the configuration information includes version information of each application. Then the keep-alive application and/or the enterprise applications are updated with versions based on the version information prior to the keep-alive process. Specifically, after the keep-alive application acquires the latest configuration information through the network request, the mLastRequestConfigTime is updated to the current time. And then, comparing the version number version code of the current keep-alive APP with the latest version number of the keep-alive APP in the configuration information, and detecting whether the update is needed. If the current version number is smaller than the latest version number, the update is needed, an update box is popped up to remind the user to update the keep-alive APP, and the latest version of the keep-alive APP can be downloaded for updating specifically through the address of the new version package in the configuration information.
Further, whether the version number of each enterprise application is smaller than the latest version number of the enterprise application in the configuration information is detected, and if yes, the need of upgrading is determined. The enterprise application may be installed or updated by silent download according to the download address of the enterprise application in the configuration information.
After version updating is performed on the keep-alive application and the enterprise application, the keep-alive application performs keep-alive processing on the enterprise application. Since the keep-alive application has the right to call the system API of the operating system, the responsive enterprise application can be kept alive by calling the system API. Of course, if the configuration information also includes other authority information of the enterprise application, the keep-alive application can also call the system API to perform various authority settings on the enterprise application.
For example, according to the Json structure of the configuration information above, the keep-alive APP calls the system API (system enterprise mode API) of the operating system, and the whitelisted enterprise application is kept alive and has the corresponding rights (other rights settings) by the package name packageName and the rights flag bits per. In enterprise mode, the operating system may have associated APIs that are open to enterprise applications. The following is an example of a system API called by a keep-alive application:
ApplicationManager.setApplicationSettings(java.lang.String packageName,int flags)
parameter description:
package name for a packageName application
flag permission zone bit
flag enumeration type:
corresponding to the above permassiontags: 00110, a flag_all_autostart flag bit is 0, which indicates that the enterprise application corresponding to the packagenname does not have self-starting authority, that is, the enterprise application is not automatically started when the mobile terminal is started; the flag_default FLAG bit is 0, which indicates that the enterprise application corresponding to the packageName does not have DEFAULT rights, and when the enterprise application has DEFAULT rights, other rights are cleared; the flag_keep_alive FLAG bit is 1, which indicates that the enterprise application corresponding to the packageName has KEEP-ALIVE authority, and the mobile terminal KEEPs ALIVE the enterprise application; the flag_previous_unique FLAG bit is 1, which indicates that the enterprise application corresponding to the packageName has anti-unloading PERMISSION, that is, cannot be unloaded, and the flag_grant_all_runtime_per_present FLAG bit is 1, which indicates that the enterprise application corresponding to the packageName has RUNTIME PERMISSION GRANT PERMISSION, that is, the enterprise application can call address book, camera, geographic location information, and the like without confirmation by a user during running.
In summary, according to the keep-alive processing scheme of the enterprise application in the embodiment of the invention, by setting the configuration server, only keep-alive configuration or other authority configuration needs to be performed in the configuration server, the mobile terminal can timely obtain the latest configuration information of the enterprise application from the configuration server, so that the keep-alive and authority setting of the enterprise application can be simply and quickly realized, and the enterprise application needing to be kept alive can be timely added and deleted. The configuration information can also comprise version information of the keep-alive application and other enterprise applications, so that the version upgrading of the keep-alive APP and the enterprise applications can be conveniently realized.
The scheme of the embodiment of the invention ensures that keep-alive, upgrading and authority setting of the enterprise application are all exchanged with the keep-alive APP for operation, so that developers of the enterprise application do not need to consider the functions, and a large number of development tasks are omitted. When the enterprise application has version update, only configuration information of the server side needs to be modified, and the update is directly downloaded by the keep-alive APP without checking signature again by a system manufacturer.
In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that some or all of the functionality of some or all of the components in the keep-alive process of an enterprise application in accordance with embodiments of the invention may be implemented in practice using a microprocessor or Digital Signal Processor (DSP). The present invention can also be implemented as an apparatus or device program (e.g., a computer program and a computer program product) for performing a portion or all of the methods described herein. Such a program embodying the present invention may be stored on a computer readable medium, or may have the form of one or more signals. Such signals may be downloaded from an internet website, provided on a carrier signal, or provided in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the words first, second, third, etc. do not denote any order. These words may be interpreted as names.
Claims (10)
1. A keep-alive processing method of an enterprise application, executed in a mobile terminal in which the keep-alive application and a plurality of enterprise applications reside, and which is communicatively connected with a configuration server and an authentication server, the method comprising:
sending the signature data of the keep-alive application to an authentication server for authentication to obtain the authentication data of the keep-alive application;
starting the authority of the keep-alive application to call the system API of the mobile terminal based on the authentication data;
the keep-alive application obtains configuration information from the configuration server, wherein the configuration information comprises authority configuration information of the enterprise application, and the authority configuration information comprises keep-alive authority information; and
and calling a system API by the keep-alive application according to keep-alive authority information of the enterprise application, and carrying out keep-alive processing on the enterprise application.
2. The keep-alive processing method of claim 1, wherein the sending the signature data of the keep-alive application to an authentication server for authentication comprises:
and after the keep-alive application is installed for the first time or version updating is carried out, the signature data of the keep-alive application is sent to an authentication server for authentication.
3. The keep-alive processing method of claim 1, wherein the keep-alive application obtaining configuration information from the configuration server, comprising:
and the keep-alive application acquires configuration information from the configuration server after receiving a start-up broadcast or a screen-off broadcast of the mobile terminal and when a preset condition is met.
4. The keep-alive processing method according to claim 3, wherein the predetermined condition is: the difference between the current time and the last time the configuration information was acquired is greater than a predetermined time interval.
5. The keep-alive processing method of claim 4, wherein the configuration information further comprises a latest version number of the keep-alive application, the method further comprising, after the configuration information is obtained:
and judging whether the version number of the keep-alive application is smaller than the latest version number or not, and if so, upgrading the keep-alive application to the latest version number.
6. The keep-alive processing method of claim 5, wherein the configuration information further comprises a latest version number of an enterprise application, the method further comprising, after the configuration information is obtained:
and the keep-alive application judges whether the version number of the enterprise application is smaller than the latest version number, and if so, the enterprise application is upgraded to the latest version number.
7. The keep-alive processing method of claim 1, wherein the rights configuration information further comprises other rights information of an enterprise application, the method further comprising:
and calling a system API by the keep-alive application according to other authority information of the enterprise application, and setting the authority of the enterprise application.
8. The keep-alive processing method of claim 7, wherein the other rights information comprises: the self-starting permission zone bit, the default zone bit, the anti-unloading zone bit and/or the run-time permission grant zone bit.
9. A mobile terminal, comprising:
one or more processors;
a memory;
one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for performing any of the methods of claims 1-8.
10. A computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by a mobile terminal, cause the mobile terminal to perform any of the methods of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110956834.XA CN113656105B (en) | 2021-08-19 | 2021-08-19 | Keep-alive processing method for enterprise application, mobile terminal and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110956834.XA CN113656105B (en) | 2021-08-19 | 2021-08-19 | Keep-alive processing method for enterprise application, mobile terminal and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113656105A CN113656105A (en) | 2021-11-16 |
| CN113656105B true CN113656105B (en) | 2024-02-23 |
Family
ID=78492438
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110956834.XA Active CN113656105B (en) | 2021-08-19 | 2021-08-19 | Keep-alive processing method for enterprise application, mobile terminal and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113656105B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109669730A (en) * | 2018-12-26 | 2019-04-23 | 北京达佳互联信息技术有限公司 | A kind of process keepalive method, device, electronic equipment and medium |
| CN112286652A (en) * | 2020-09-17 | 2021-01-29 | 福州云联畅想软件科技有限公司 | Android APP background keep-alive method |
-
2021
- 2021-08-19 CN CN202110956834.XA patent/CN113656105B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109669730A (en) * | 2018-12-26 | 2019-04-23 | 北京达佳互联信息技术有限公司 | A kind of process keepalive method, device, electronic equipment and medium |
| CN112286652A (en) * | 2020-09-17 | 2021-01-29 | 福州云联畅想软件科技有限公司 | Android APP background keep-alive method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113656105A (en) | 2021-11-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11256496B2 (en) | Apparatus and method for managing application | |
| JP4468380B2 (en) | Automated air plug-in device recognition and software driver download | |
| CN105045643B (en) | Launcher startup method and device in Android system | |
| CN102945182B (en) | Application program update method and apparatus | |
| JP2017505966A (en) | Firmware upgrade method, apparatus, program, and recording medium | |
| CN104951336A (en) | Application program installation method and device | |
| CN106406956B (en) | Application program installation method and device | |
| CN107291481B (en) | Component updating method, device and system | |
| CN109558042A (en) | Show topics the method, apparatus and computer readable storage medium of skin | |
| CN111459523A (en) | Image quality chip software upgrading method and device, electronic equipment and storage medium | |
| CN102981880A (en) | Method and device for realizing application program updating | |
| CN105530130A (en) | Method and device for upgrading Over-The-Air downloading technology | |
| CN105740027A (en) | Application program updating method and device | |
| CN110998525A (en) | Method and device for processing broadcast events | |
| US11604656B2 (en) | Method and apparatus for managing application | |
| CN107704259A (en) | Application upgrade method, apparatus and storage medium | |
| CN112181406B (en) | Sharing method and device of rendering engine | |
| KR20190098516A (en) | Method for managing data related to application and electronic device thereof | |
| KR20190109979A (en) | Electronic device and method for controling update thereof | |
| CN113656105B (en) | Keep-alive processing method for enterprise application, mobile terminal and storage medium | |
| US20180316818A1 (en) | System and method for installing application and recording medium | |
| CN118484211A (en) | Operating system upgrading method and electronic equipment | |
| CN108762981B (en) | Black screen processing method and related device | |
| CN115562732B (en) | A startup method, electronic equipment and computer storage medium | |
| CN107220082B (en) | Application program installation method, device and equipment |
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 |