Application starting method, system and related device

Abstract

The invention discloses a method, a system and a related device for starting an application, which are used for improving the starting speed of the application under the condition of limited resources and meeting the requirement of a payment task. The method comprises the steps of determining a starting trigger event of an application; a pre-configured configuration file is obtained according to the start trigger event, the configuration file comprises a target frequency corresponding to the start trigger event, and the target frequency is greater than a default operation frequency; and starting the application according to the target frequency response to the starting trigger event.

Description

Technical Field

[0001] The present application relates to the field of data processing, and in particular to a method, system and related device for starting an application. Background Art

[0002] In modern payment systems, POS terminals (Point of Sale) are important tools for merchants to settle transactions. However, compared with smartphones, POS terminals usually have lower CPU resources, which to some extent affects the hot start speed of their applications. Especially in high-frequency payment scenarios, this startup delay may have a negative impact on transaction speed.

[0003] In the prior art, when dealing with CPU frequency management of POS terminals, a dynamic frequency adjustment strategy is usually adopted to balance performance and power consumption. When the system load is low, a lower CPU frequency is used to run to reduce power consumption; when an increase in tasks is detected, the CPU frequency is gradually increased to meet performance requirements. However, such a dynamic frequency adjustment strategy is insufficient in terms of quickly responding to user operations and handling high-load tasks. It cannot accurately predict and quickly respond to user operations, resulting in a long waiting time for merchants and users when starting applications, which seriously affects the payment experience in a commercial environment that requires instant payment confirmation. Summary of the invention

[0004] The present application provides a method, system and related device for starting an application, which are used to increase the speed of starting an application under limited resources and meet the requirements of payment tasks.

[0005] The first aspect of the present application provides a method for starting an application, comprising:

[0006] Determine the application launch trigger event;

[0007] Acquire a pre-configured configuration file according to the startup trigger event, wherein the configuration file includes a target frequency corresponding to the startup trigger event, and the target frequency is greater than a default operating frequency;

[0008] The application is started in response to the start trigger event at the target frequency.

[0009] Optionally, responding to the start trigger event at the target frequency includes:

[0010] Calling a pre-registered frequency boost function to generate a frequency boost instruction at the application layer according to the configuration file, wherein the frequency boost instruction includes a target frequency, a target CPU node, and a frequency boost duration;

[0011] Sending the frequency increase instruction to the hardware layer through the application layer, and sending the frequency increase instruction to the kernel layer through the hardware layer;

[0012] When the kernel layer receives the frequency increase instruction, it controls the frequency of the target CPU node to increase to the target frequency, and maintains the target frequency within the frequency increase duration.

[0013] Optionally, the acquiring a pre-configured configuration file according to the startup triggering event includes:

[0014] Determine the type of the application according to the start trigger event, the type of the application being a payment type or a non-payment type;

[0015] Obtaining a pre-configured configuration file according to the type of the application;

[0016] When the type of the application is the payment type, the configuration file includes a first target frequency;

[0017] When the type of the application is the non-payment type, the configuration file includes a second target frequency, and the first target frequency is greater than the second target frequency.

[0018] Optionally, before acquiring a pre-configured configuration file according to the startup trigger event, the method further includes:

[0019] The current geographic location information is obtained, and based on the geographic location information, it is determined that the current location is a target payment location.

[0020] Optionally, the target frequency has a positive correlation with the usage frequency of the application.

[0021] Optionally, after responding to the start trigger event at the target frequency and starting the application, the method further includes:

[0022] Dynamically adjust the operating frequency according to the actual load conditions.

[0023] Optionally, the start trigger event includes a click event, a voice start event, a card swiping event and a code scanning event.

[0024] A second aspect of the present application provides a system for starting an application, including:

[0025] A determination unit, used to determine a startup triggering event of an application;

[0026] an acquisition unit, configured to acquire a pre-configured configuration file according to the startup trigger event, wherein the configuration file includes a target frequency corresponding to the startup trigger event, and the target frequency is greater than a default operating frequency;

[0027] A starting unit is used to respond to the start trigger event at the target frequency to start the application.

[0028] Optionally, the startup unit is specifically used for:

[0029] Calling a pre-registered frequency boost function to generate a frequency boost instruction at the application layer according to the configuration file, wherein the frequency boost instruction includes a target frequency, a target CPU node, and a frequency boost duration;

[0030] Sending the frequency increase instruction to the hardware layer through the application layer, and sending the frequency increase instruction to the kernel layer through the hardware layer;

[0031] When the kernel layer receives the frequency increase instruction, it controls the frequency of the target CPU node to increase to the target frequency, and maintains the target frequency within the frequency increase duration.

[0032] Optionally, the acquiring unit is specifically used for:

[0033] Determine the type of the application according to the start trigger event, the type of the application being a payment type or a non-payment type;

[0034] Obtaining a pre-configured configuration file according to the type of the application;

[0035] When the type of the application is the payment type, the configuration file includes a first target frequency;

[0036] When the type of the application is the non-payment type, the configuration file includes a second target frequency, and the first target frequency is greater than the second target frequency.

[0037] Optionally, the system further includes:

[0038] The positioning unit is used to obtain the current geographical location information and determine the current target payment location based on the geographical location information.

[0039] Optionally, the target frequency has a positive correlation with the usage frequency of the application.

[0040] Optionally, the system further includes:

[0041] The adjustment unit is used to dynamically adjust the operating frequency according to the actual load conditions.

[0042] Optionally, the start trigger event includes a click event, a voice start event, a card swiping event and a code scanning event.

[0043] A third aspect of the present application provides a device for starting an application, the device comprising:

[0044] Processor, memory, input-output unit, and bus;

[0045] The processor is connected to the memory, the input and output unit, and the bus;

[0046] The memory stores a program, and the processor calls the program to execute the first aspect and any optional application startup method in the first aspect.

[0047] A fourth aspect of the present application provides a computer-readable storage medium, on which a program is stored. When the program is executed on a computer, the method for starting an application in the first aspect and any optional application in the first aspect is executed.

[0048] It can be seen from the above technical solutions that this application has the following advantages:

[0049] By capturing the startup trigger event of the application, and obtaining the corresponding configuration file based on the identified startup trigger event, the configuration file contains the target frequency corresponding to the startup trigger event, which is higher than the default operating frequency of the device, ensuring that sufficient CPU performance can be provided at critical moments. Finally, the CPU operating frequency is dynamically adjusted according to the target frequency in the configuration file, and the corresponding application is started in response to the startup trigger event, thereby significantly reducing the startup time of the application, achieving fast startup of the application, and improving merchant and user experience. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0051] Figure 1 A flowchart of an embodiment of the method for starting an application provided by the present application;

[0052] Figure 2 A flowchart of another embodiment of the method for starting an application provided by the present application;

[0053] Figure 3 A flowchart of an embodiment of obtaining a pre-configured configuration file according to the type of application in the method for starting an application provided by the present application;

[0054] Figure 4 A schematic flow chart of an embodiment of responding to the startup trigger event with the target frequency in the method for starting an application provided by the present application;

[0055] Figure 5 A schematic diagram of an embodiment of the system structure for application startup provided by the present application;

[0056] Figure 6 A schematic diagram of the structure of an embodiment of the device for launching an application provided in this application. DETAILED DESCRIPTION

[0057] The present application provides a method, system and related device for starting an application, which are used to increase the speed of starting an application under limited resources and meet the requirements of payment tasks.

[0058] It should be noted that the method for application startup provided in this application is applied to payment devices with limited performance, such as POS terminals. The design of POS terminals usually prioritizes low power consumption and stability. The CPU performance of POS terminals is usually lower than that of smartphones, and the application startup speed is slow. Especially in payment scenarios, this delay may cause dissatisfaction among merchants and customers and affect the payment experience. For the convenience of explanation, this application uses POS terminals as the execution subject for example.

[0059] See also Figure 1 , Figure 1 An embodiment of a method for starting an application provided by the present application includes:

[0060] S101, determining a startup trigger event of an application;

[0061] When a user performs an operation on a POS terminal, such as touching a certain location, sliding the screen, clicking an application icon, swiping a card, scanning a code, etc., these operations will generate corresponding input events in the POS terminal system. The system needs to effectively capture and identify these input events in order to correctly trigger the corresponding operations. These input events will be distributed to the corresponding application or system service through the system's input event distributor. The event distributor is responsible for identifying the event type and sending the event to the appropriate recipient based on the event type. When the event is correctly distributed, the corresponding application or system service will respond to the event.

[0062] A startup trigger event refers to a specific input event that can cause an application to start when a user interacts with a POS terminal. When the system detects a startup trigger event, it will start the corresponding application according to the pre-configured logic. The startup trigger event can be generated by various user operations, which are not limited here.

[0063] Specifically, in the Android system, the startup trigger event is usually captured by InputDispatcher or a similar event processing module. InputDispatcher is responsible for distributing user input events (such as touch, click, etc.) to the corresponding application or system service. For each event captured by the terminal, InputDispatcher will classify it to determine whether it is a startup trigger event or other types of events. If the current event is determined to be a startup trigger event, the subsequent step S102 is executed to trigger the subsequent startup optimization process.

[0064] S102, acquiring a pre-configured configuration file according to a startup trigger event, where the configuration file includes a target frequency corresponding to the startup trigger event, where the target frequency is greater than a default operating frequency;

[0065] When the system detects a startup trigger event, it reads the corresponding configuration file from the preset storage location. The configuration file contains the key parameters required for startup optimization to start the application. The target frequency is the core parameter in the configuration file, which determines the CPU performance of the POS terminal when starting the application. Since the CPU performance of POS terminals is usually lower than that of mobile phones and other devices, in order to ensure that the application can start quickly, the system needs to increase the CPU frequency to a higher level. Therefore, the target frequency in the configuration file needs to be higher than the default operating frequency of the device, which means that once the system recognizes a startup trigger event, the POS terminal will temporarily increase the CPU frequency to speed up the application startup.

[0066] Furthermore, the configuration file can also include the frequency boost duration and the scheduled CPU nodes. The frequency boost duration specifies the duration of the CPU after it is boosted to the target frequency. The frequency boost duration can be set according to the needs of application startup to ensure that the application has enough time to load and initialize. The CPU is usually composed of multiple CPU nodes, each of which can independently schedule and run tasks, so the configuration file can also specify which CPU nodes should be activated during the frequency boost operation, as well as the operating frequencies of these CPU nodes.

[0067] S103: Respond to the start trigger event at the target frequency to start the application.

[0068] By responding to the startup trigger event with the target frequency during the startup process of the application, and setting the system's operating environment according to the previously obtained target frequency, it is ensured that the POS terminal can achieve a better performance state when the application is started, and that the application can run at a higher performance level during the startup process, thereby shortening the application startup time and reducing the user's waiting time.

[0069] In this embodiment, by capturing the startup trigger event of the application, and obtaining the corresponding configuration file according to the identified startup trigger event, the configuration file contains the target frequency corresponding to the startup trigger event, and the target frequency is higher than the default operating frequency of the device, ensuring that sufficient CPU performance can be provided at critical moments. Finally, the CPU operating frequency is dynamically adjusted according to the target frequency in the configuration file, and the corresponding application is started in response to the startup trigger event, thereby significantly reducing the startup time of the application, achieving fast startup of the application, and improving merchant and user experience.

[0070] See also Figure 2 , Figure 2 An embodiment of a method for starting an application provided by the present application includes:

[0071] S201, determining a startup triggering event of an application;

[0072] In this embodiment, step S201 is similar to step S101 in the above embodiment and will not be described again here.

[0073] In some specific embodiments, the startup trigger event specifically includes a click event, a voice startup event, a card swiping event, and a code scanning event. A click event refers to a user starting an application by touching the touch screen or physical button of a POS terminal, a voice startup event refers to a user starting an application by voice command, a card swiping event refers to a user starting an application by swiping a card on a POS terminal through a magnetic stripe card, a chip card, or NFC, etc., and a code scanning event refers to a user starting an application by scanning a barcode or a QR code. Regardless of the startup trigger event, the system can quickly identify and obtain a configuration file to adjust the CPU frequency to achieve fast startup.

[0074] S202, obtaining current geographical location information, and determining that the current location is a target payment location according to the geographical location information;

[0075] Before executing the optimization process of starting step S203, the system first obtains the current geographical location information of the POS terminal, that is, determines the location of the POS terminal through GPS or other positioning technology, and determines whether the POS terminal is currently in the target payment location based on the geographical location information. The target payment location specifically refers to a specific geographical location or environment where payment transactions may be required, and the target payment location usually includes stores, supermarkets, restaurants, gas stations, parking lots and other places where transactions and payments are frequently required.

[0076] The target payment location is used to distinguish between ordinary locations and payment-intensive locations. When the system confirms that the POS terminal is currently in these specific target payment locations, the system will be more inclined to optimize resource allocation, and then continue to execute step S203 to increase the CPU frequency to ensure that the payment application can start quickly and respond in time, thereby providing a smooth payment experience. If the system confirms that the POS terminal is currently in a non-target payment location, it can continue to run with the default system settings to avoid unnecessary resource consumption.

[0077] In actual applications, the system can specifically compare the acquired geographic location information with the pre-set payment location database to determine whether the POS terminal is currently in the target payment location. The payment location database contains the geographic location data of all target locations that are identified as requiring optimized payment experience. Merchants or users can add, modify or delete payment locations in the payment location database on their own, so that the system can more accurately optimize the application startup speed, improve the efficiency of payment operations and user experience. The system can also provide prompts and notifications to users, such as reminding users that the application startup optimization settings take effect when they enter a payment location.

[0078] S203, acquiring a pre-configured configuration file according to the startup trigger event, the configuration file including a target frequency corresponding to the startup trigger event, the target frequency being greater than a default operating frequency, and the target frequency having a positive correlation with a usage frequency of the application;

[0079] In actual applications, different startup trigger events can correspond to different target frequencies, allowing the system to flexibly adjust the CPU frequency according to the user's specific operating scenario and application type. The system can dynamically select the corresponding configuration according to the event type or application characteristics corresponding to the startup trigger event, thereby flexibly determining the CPU frequency increase strategy. That is, a series of mapping rules can be defined in the configuration file to associate specific startup trigger events with corresponding target frequencies, and store them in the form of key-value pairs or similar structures, where each event type or startup trigger event of each application characteristic corresponds to a preset target frequency.

[0080] For example, the event types of the start trigger event can be specifically divided into the start trigger event generated by user interaction (such as clicking a button, touching the screen, selecting a menu item, etc.) and the start trigger event generated by the input of an external device or service (such as swiping a card, scanning a QR code, NFC payment, etc.). Since the start trigger event generated by the input of an external device or service usually involves a payment transaction, a higher target frequency can be set for the start trigger event generated by the input of an external device or service than for the start trigger event generated by user interaction to meet the demand for fast payment.

[0081] In some specific embodiments, the target frequency can also be positively correlated with the frequency of use of the application. The system records the startup frequency and usage of each application to determine the frequency of use of each application. The frequency of use depends on data such as the startup time, usage duration, and operation frequency of the application. Based on these data, the system can identify and classify the usage patterns of the application, such as high-frequency use (for example, payment applications) and low-frequency use (for example, inventory management applications). At this time, the target frequency that matches the application can be flexibly set according to the identified usage pattern. For example, a high-frequency application A can set a higher target frequency to increase the response speed, while a low-frequency application B can set a relatively low target frequency to reduce power consumption. By positively correlating the target frequency with the frequency of use of the application, the system can intelligently adjust resource allocation, improve the performance of high-frequency applications, and optimize the energy efficiency of low-frequency applications, thereby improving the overall system performance and user experience.

[0082] S204, responding to the trigger event with a target frequency to start the application;

[0083] In this embodiment, step S204 is similar to step S103 in the above embodiment and will not be described again here.

[0084] S205. Dynamically adjust the operating frequency according to actual load conditions.

[0085] After the application is successfully launched, the system can dynamically adjust the CPU frequency according to the actual task load to balance performance and power consumption. If the application load is high, the system can maintain the current increased CPU frequency to ensure smooth operation of the application. For long periods of low-load operation, the system can restore the CPU frequency to the default value or other appropriate frequency to reduce power consumption, ensuring that the adjusted frequency can balance performance and energy efficiency without causing slow application response or other performance issues, thereby optimizing the overall energy efficiency and user experience of the device.

[0086] In the above step S102 or step S203, a higher target frequency may be set for payment type applications to further enhance the user's payment experience. Figure 3 , Figure 3 In one embodiment of obtaining a pre-configured configuration file according to the type of application, the method includes:

[0087] S301, determining the type of application according to the start trigger event, the type of application being a payment type or a non-payment type;

[0088] In POS terminals, payment applications require higher priority and performance optimization to ensure that they can respond quickly to user operations when processing payment transactions. Moreover, payment applications usually require instant transaction processing. The speed and response time of payment application startup directly affect the user's satisfaction with the payment process. Moreover, payment applications usually involve sensitive user data and fund transactions. High-performance startup speed and processing capabilities can ensure that encryption operations and security verification are completed quickly in the background, thereby enhancing the security of transactions.

[0089] Therefore, in this embodiment, the system needs to determine the type of application being launched based on the captured launch trigger event. The type of application is specifically a payment type (such as a payment application, a wallet application, etc.) or a non-payment type (such as an inventory management application, a browser, etc.). The system can specifically query the category information of the application through system services or management tools, and can also directly use the package name, application ID or other unique identifier of the application to determine the type of application. For example, the package name of a payment application usually contains keywords such as "bank", "payment", "pay" or "wallet", while the package name of a non-payment application has nothing to do with payment.

[0090] S302. Obtain a pre-configured configuration file according to the type of application; when the type of application is a payment type, the configuration file includes a first target frequency; when the type of application is a non-payment type, the configuration file includes a second target frequency, and the first target frequency is greater than the second target frequency.

[0091] The system obtains the corresponding startup optimization parameters from the pre-configured configuration file according to the determined type of application. If it is identified that the application corresponding to the current startup trigger event is of the payment type, the system will load the configuration file containing the first target frequency. The first target frequency can be set to a maximum or higher frequency to ensure that the payment application can start quickly and run in high-performance mode to meet the high response requirements in the payment scenario. For non-payment type applications, such as ordinary management tools or other non-mission-critical applications, the system will load a configuration file containing the second target frequency. The second target frequency is lower than the first target frequency, and can save system resources and power consumption while meeting the basic operating requirements of the application. It should be noted that both the first target frequency and the second target frequency are higher than the default operating frequency to ensure that when the application is started, the system can provide higher performance support than the normal state.

[0092] In this embodiment, through this differentiated management, the POS terminal can flexibly provide appropriate performance support for different types of applications, which can not only ensure the quick startup and smooth operation of payment applications, but also optimize the startup experience of non-payment applications, while taking into account energy saving effects, effectively balancing system performance and resource usage, and improving the overall user experience.

[0093] In the above step S103 or S204, the frequency increase operation can be implemented by a pre-registered frequency increase function, which is described in detail below. Figure 4 , Figure 4 To initiate an embodiment of a trigger event at a target frequency response, the method includes:

[0094] S401, calling a pre-registered frequency boost function to generate a frequency boost instruction at the application layer according to a configuration file, the frequency boost instruction including a target frequency, a target CPU node, and a frequency boost duration;

[0095] A function specifically used to increase the CPU frequency is pre-registered in the application layer. This frequency increase function can be dynamically integrated into the system through the reflection mechanism so that it can be quickly called when needed. After obtaining the configuration file, the system first reads the parameters corresponding to the current startup trigger event from the configuration file, including the target frequency, target CPU node, and frequency increase duration, and then calls the registered frequency increase function through the reflection mechanism to generate a frequency increase instruction. The reflection mechanism allows the system to flexibly call the corresponding function without directly hard-coding the call to the frequency increase function, so that the system can dynamically select the execution function according to different configurations or conditions.

[0096] S402, sending the frequency increase instruction to the hardware layer through the application layer, and sending the frequency increase instruction to the kernel layer through the hardware layer;

[0097] The application layer sends the generated frequency increase instruction to the system's hardware layer, which is then further passed to the kernel layer to perform the actual frequency increase operation.

[0098] S403: After receiving the frequency increase instruction, the kernel layer controls the frequency of the target CPU node to increase to the target frequency, and maintains the target frequency within the duration of the frequency increase.

[0099] After receiving the frequency increase instruction, the CPU control module of the kernel layer will increase the frequency of the target CPU node to the corresponding target frequency according to the target frequency in the instruction. Ensure that the system can provide sufficient computing resources for the application at the critical moment of application startup to achieve fast startup. After the target frequency is increased in place, the CPU control module will maintain the target frequency within the frequency increase duration specified in the frequency increase instruction, ensuring that the application can continue to guarantee high-performance support during the critical time period after startup, avoiding performance degradation during the startup process. After the frequency increase duration ends, the CPU frequency can be safely restored to normal or energy-saving state to avoid unnecessary energy consumption.

[0100] The following is a detailed description of the application startup system provided by this application. Figure 5 , Figure 5Another embodiment of the system for launching the application provided by the present application includes:

[0101] A determination unit 501 is used to determine a startup triggering event of an application;

[0102] An acquisition unit 502 is used to acquire a pre-configured configuration file according to a startup trigger event, wherein the configuration file includes a target frequency corresponding to the startup trigger event, and the target frequency is greater than a default operating frequency;

[0103] The starting unit 503 is used to respond to the start trigger event at a target frequency to start the application.

[0104] Optionally, the starting unit 503 is specifically used for:

[0105] Calling a pre-registered frequency boost function to generate a frequency boost instruction at the application layer according to a configuration file, the frequency boost instruction including a target frequency, a target CPU node, and a frequency boost duration;

[0106] Sending a frequency increase instruction to the hardware layer through the application layer, and sending the frequency increase instruction to the kernel layer through the hardware layer;

[0107] When the kernel layer receives the frequency increase instruction, it controls the frequency of the target CPU node to increase to the target frequency and maintains the target frequency during the frequency increase duration.

[0108] Optionally, the acquiring unit 502 is specifically configured to:

[0109] Determine the type of application according to the start trigger event, and the type of application is payment type or non-payment type;

[0110] Get pre-configured configuration files based on the type of application;

[0111] When the type of application is a payment type, the configuration file includes a first target frequency;

[0112] When the type of the application is a non-payment type, the configuration file includes a second target frequency, and the first target frequency is greater than the second target frequency.

[0113] Optionally, the system further includes:

[0114] The positioning unit 504 is used to obtain the current geographical location information and determine the current target payment location based on the geographical location information.

[0115] Optionally, the target frequency has a positive correlation with the usage frequency of the application.

[0116] Optionally, the system further includes:

[0117] The adjustment unit 505 is used to dynamically adjust the operating frequency according to the actual load conditions.

[0118] Optionally, the start trigger event includes a click event, a voice start event, a card swiping event, and a code scanning event.

[0119] In this embodiment, the functions of each unit are the same as those described above. Figures 1 to 4 The steps in the method embodiment shown correspond to each other and will not be repeated here.

[0120] This application also provides a device for starting an application, see Figure 6 , Figure 6 An embodiment of a device for starting an application provided by the present application includes:

[0121] Processor 601, memory 602, input and output unit 603, bus 604;

[0122] The processor 601 is connected to the memory 602, the input and output unit 603 and the bus 604;

[0123] The memory 602 stores a program, and the processor 601 calls the program to execute any of the above application startup methods.

[0124] The present application also relates to a computer-readable storage medium, on which a program is stored. When the program is run on a computer, the computer executes any of the above-mentioned methods for starting an application.

[0125] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0126] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0127] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0128] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0129] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), disk or optical disk and other media that can store program code.

Claims

1. A method for starting an application, characterized in that: The method comprises: Determine the application launch trigger event; Acquire a pre-configured configuration file according to the startup trigger event, wherein the configuration file includes a target frequency corresponding to the startup trigger event, and the target frequency is greater than a default operating frequency; The application is started in response to the start trigger event at the target frequency.

2. The method according to claim 1, characterized in that The step of responding to the start trigger event at the target frequency includes: Calling a pre-registered frequency boost function to generate a frequency boost instruction at the application layer according to the configuration file, wherein the frequency boost instruction includes a target frequency, a target CPU node, and a frequency boost duration; Sending the frequency increase instruction to the hardware layer through the application layer, and sending the frequency increase instruction to the kernel layer through the hardware layer; When the kernel layer receives the frequency increase instruction, it controls the frequency of the target CPU node to increase to the target frequency, and maintains the target frequency within the frequency increase duration.

3. The method according to claim 1, characterized in that The obtaining of a pre-configured configuration file according to the startup triggering event includes: Determine the type of the application according to the start trigger event, the type of the application being a payment type or a non-payment type; Obtaining a pre-configured configuration file according to the type of the application; When the type of the application is the payment type, the configuration file includes a first target frequency; When the type of the application is the non-payment type, the configuration file includes a second target frequency, and the first target frequency is greater than the second target frequency.

4. The method according to claim 1, characterized in that: Before acquiring the pre-configured configuration file according to the startup trigger event, the method includes: The current geographic location information is obtained, and based on the geographic location information, it is determined that the current location is a target payment location.

5. The method according to claim 1, characterized in that The target frequency has a positive correlation with the usage frequency of the application.

6. The method according to any one of claims 1 to 5, characterized in that After responding to the start trigger event at the target frequency and starting the application, the method further includes: Dynamically adjust the operating frequency according to the actual load conditions.

7. The method according to any one of claims 1 to 5, characterized in that The start trigger event includes a click event, a voice start event, a card swiping event and a code scanning event.

8. A system for launching an application, characterized in that: The system comprises: A determination unit, used to determine a startup triggering event of an application; an acquisition unit, configured to acquire a pre-configured configuration file according to the startup trigger event, wherein the configuration file includes a target frequency corresponding to the startup trigger event, and the target frequency is greater than a default operating frequency; A starting unit is used to respond to the start trigger event at the target frequency to start the application.

9. A device for starting an application, characterized in that: The device comprises: Processor, memory, input-output unit, and bus; The processor is connected to the memory, the input and output unit, and the bus; The memory stores a program, and the processor calls the program to execute the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a program stored thereon, wherein the program, when executed on a computer, performs the method according to any one of claims 1 to 7.

Images