Method, apparatus and electronic device for optimizing running of application program

Abstract

This disclosure relates to a method, apparatus, and electronic device for optimizing the operation of an application, belonging to the field of computer technology. The method for optimizing the operation of the application includes: displaying a first display interface of the application at a first process node; in response to a process change event, obtaining a node identifier of a second process node associated with the process change event; and, based on the node identifier, canceling the display of the first display interface and displaying a second display interface of the application at the second process node. This invention can effectively improve the operating efficiency of the application.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and more specifically, to a method, apparatus, and electronic device for optimizing the operation of an application. Background Technology

[0002] With the rapid development of applications, the types and number of applications available on user terminals are growing exponentially. Before an application can run on a user terminal, it needs to interface with the user terminal's Software Development Kit (SDK).

[0003] Currently, to ensure correct access methods, user terminals typically need to follow the platform's access documentation and complete processes such as application initialization and user account login in a specific order. This process of verifying the access documentation with the user terminal impacts application performance. Summary of the Invention

[0004] One objective of this disclosure is to provide a new technical solution for optimizing the operation of applications.

[0005] According to a first aspect of this disclosure, an application runtime optimization method is provided, the method comprising:

[0006] The application displays its first interface at the first process node;

[0007] In response to a process change event, obtain the node identifier of the second process node associated with the process change event;

[0008] Based on the node identifier, the first display interface is de-displayed, and the second display interface of the application in the second process node is displayed.

[0009] Optionally, the node identifier is associated with at least one process change event, including a process change event triggered by a user or a process change event triggered by the application.

[0010] The first display interface includes a first option triggered by a process change event by the user, or a second option triggered by the application, wherein the first option or the second option corresponds to at least one interactive interface of the first display interface.

[0011] Optionally, different process nodes correspond to different permission levels, and each permission level corresponds to at least one process node. The permission level is set based on the interactive interface of the display interface corresponding to that permission level.

[0012] The first permission level corresponding to the first process node is different from the second permission level corresponding to the second process node.

[0013] Optionally, the permission levels include device level, user account level, and user role level;

[0014] The interactive interface of the display interface corresponding to the device level includes a first interactive interface; wherein the first interactive interface provides the application's initialization information and program update information;

[0015] The interactive interface of the display interface corresponding to the user account level includes a first interactive interface and a second interactive interface; wherein, the second interactive interface provides preview information about the user's account information and the role held by the user;

[0016] The interactive interfaces of the display interface corresponding to the user role level include a first interactive interface, a second interactive interface, and a third interactive interface; wherein, the third interactive interface provides detailed information about the role held by the user.

[0017] Optionally, the process nodes corresponding to the device level include device login nodes and account logout nodes;

[0018] The process nodes corresponding to the user account level include the account login node and the role logout node;

[0019] The process nodes corresponding to the user role level include the role login node.

[0020] Optionally, when the first permission level is lower than the second permission level, the step of canceling the display of the first display interface and displaying the second display interface of the application at the second process node according to the node identifier includes:

[0021] Based on the node identifier, the first display interface is canceled, the first part of the interactive interface is kept in the ready state, and the second part of the interactive interface is set to the ready state; wherein, the first part of the interactive interface corresponds to the first permission level, and the first part of the interactive interface and the second part of the interactive interface correspond to the second permission level.

[0022] The application is displayed in the second presentation interface at the second process node.

[0023] Optionally, the first permission level is the next level below the second permission level.

[0024] Optionally, when the first permission level is higher than the second permission level, the step of canceling the display of the first display interface and displaying the second display interface of the application at the second process node according to the node identifier includes:

[0025] Based on the node identifier, the first display interface is canceled, the third part of the interaction interface is put into a ready state, and the fourth part of the interaction interface is kept in a ready state; wherein, the third part of the interaction interface corresponds to the first permission level, and the fourth part of the interaction interface corresponds to the first permission level and the second permission level.

[0026] The application is displayed in the second presentation interface at the second process node.

[0027] Optionally, the second permission level is any lower level of the first permission level.

[0028] According to a second aspect of this disclosure, an application runtime optimization apparatus is also provided, the apparatus comprising:

[0029] The display module is used to display the first display interface of the application at the first process node;

[0030] A response module is used to respond to a process change event and obtain the node identifier of the second process node associated with the process change event;

[0031] The switching module is used to cancel the display of the first display interface and display the second display interface of the application in the second process node according to the node identifier.

[0032] According to a third aspect of this disclosure, an electronic device is also provided, including a memory and a processor, the memory being used to store a computer program; the processor being used to execute the computer program to implement the method according to a first aspect of this disclosure.

[0033] According to a fourth aspect of this disclosure, a computer-readable storage medium is also provided, on which a computer program is stored, which, when executed by a processor, implements the method described according to a first aspect of this disclosure.

[0034] One beneficial effect of this disclosure is that the application operation optimization method provided by the present invention can obtain the node identifier of the second process node when a process change event is triggered, and determine the second display interface displayed on the user terminal based on the node identifier, so as to display different display interfaces at different process nodes, thereby improving the operating efficiency of the user terminal.

[0035] Other features and advantages of the embodiments of this disclosure will become clear from the following detailed description of exemplary embodiments with reference to the accompanying drawings. Attached Figure Description

[0036] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments of the present disclosure and, together with their description, serve to explain the principles of the embodiments of the present disclosure.

[0037] Figure 1 This is a schematic diagram of the hardware structure of an application runtime optimization system capable of applying an application runtime optimization method according to an embodiment;

[0038] Figure 2 This is a flowchart illustrating an application operation optimization method according to one embodiment;

[0039] Figure 3 This is a schematic diagram of the lifecycle of game A according to one embodiment;

[0040] Figure 4 This is a schematic diagram illustrating the operation of game A according to one embodiment;

[0041] Figure 5 This is a schematic diagram of the lifecycle of game B according to one embodiment;

[0042] Figure 6 This is a block diagram of an application runtime optimization apparatus according to one embodiment;

[0043] Figure 7 This is a schematic diagram of the hardware structure of an electronic device according to one embodiment. Detailed Implementation

[0044] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of the invention.

[0045] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit the invention or its application or use.

[0046] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.

[0047] In all the examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.

[0048] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0049] This disclosure provides a new technical solution for optimizing the operation of an application. When a process change event is triggered during the operation of the application, the node identifier of the second process node associated with the process change event can be obtained. The second display interface displayed on the user terminal is determined based on the node identifier, so that different display interfaces are displayed at different process nodes, thereby improving the operating efficiency of the user terminal.

[0050] Figure 1 A schematic diagram of the hardware structure of an application runtime optimization system is shown, which can be used to implement an application runtime optimization method according to embodiments of the present disclosure.

[0051] The application's optimization system includes an electronic device 1000 and a server 2000, which can communicate and interact with the server 2000 via a network.

[0052] The electronic device 1000 is a device capable of running applications. These applications can be local applications installed on the electronic device, or web applications, lightweight applications, or mini-programs, etc. The application can be media player software, office software, or games, etc., without limitation. The electronic device 1000 can be a mobile phone, tablet computer, PC, etc., without limitation.

[0053] like Figure 1 As shown, the electronic device 1000 may include a processor 1101, a memory 1102, an interface device 1103, a communication device 1104, an output device 1105, an input device 1106, etc. Figure 1 The hardware configuration shown is illustrative only and is not intended to limit this disclosure, its application, or its use.

[0054] The processor 1101 executes computer programs, which can be written using instruction sets of architectures such as x86, Arm, RISC, MIPS, and SSE. The memory 1102 includes, for example, ROM (Read-Only Memory), RAM (Random Access Memory), and non-volatile memory such as a hard disk. The interface device 1103 includes, for example, a USB interface, a network cable interface, and a headphone jack. The communication device 1104 is capable of wired or wireless communication. The communication device 1104 may include at least one short-range communication module, such as any module for short-range wireless communication based on short-range wireless communication protocols such as Hilink, WiFi (IEEE 802.11), Mesh, Bluetooth, ZigBee, Thread, Z-Wave, NFC, UWB, and LiFi. The communication device 1104 may also include a long-range communication module, such as any module for WLAN, GPRS, or 2G / 3G / 4G / 5G long-range communication. The output device 1105 may include, for example, an LCD screen or touch screen, and a speaker. Input device 1106 may include, for example, a touch screen, a keyboard, a microphone, various sensors, etc.

[0055] like Figure 1 As shown, the server 2000 may include a processor 2101, a memory 2102, an interface device 2103, a communication device 2104, an output device 2105, an input device 2106, etc. Figure 1 The hardware configuration shown is illustrative only and is not intended to limit this disclosure, its application, or its use.

[0056] The processor 2101 executes computer programs, which can be written using instruction sets of architectures such as x86, Arm, RISC, MIPS, and SSE. The memory 2102 includes, for example, ROM (Read-Only Memory), RAM (Random Access Memory), and non-volatile memory such as a hard disk. The interface device 2103 includes, for example, a USB interface, a network cable interface, and a headphone jack. The communication device 2104 is capable of wired or wireless communication. The communication device 2104 may include at least one short-range communication module, such as any module for short-range wireless communication based on short-range wireless communication protocols such as Hilink, WiFi (IEEE 802.11), Mesh, Bluetooth, ZigBee, Thread, Z-Wave, NFC, UWB, and LiFi. The communication device 2104 may also include a long-range communication module, such as any module for WLAN, GPRS, or 2G / 3G / 4G / 5G long-range communication. The output device 2105 may include, for example, an LCD screen or touch screen, and a speaker. Input device 2106 may include, for example, a touch screen, a keyboard, a microphone, various sensors, etc.

[0057] In this embodiment, the memory 1102 of the electronic device 1000 is used to store a computer program that controls the processor 1101 to perform a display method for moving a virtual character according to any embodiment of the present disclosure.

[0058] Next, as Figure 1 Taking an electronic device 1000 as an example, various embodiments of the application operation optimization method are explained.

[0059] <First Embodiment>

[0060] Figure 2 This is a flowchart illustrating an application runtime optimization method according to one embodiment. The implementing entity is, for example, a... Figure 1 1000 Chinese electronic devices.

[0061] like Figure 2 As shown, the application optimization method of this embodiment may include the following steps S210 to S230:

[0062] Step S210: Display the first display interface of the application at the first process node.

[0063] In some examples, the application can run in a certain process sequence, which may correspond to one or more process nodes, without limitation here.

[0064] In some examples, the application may have one process sequence or multiple process sequences, which is not limited here.

[0065] For example, an application can sequentially go through the following process nodes: device initialization node - user account login node - user role login node - user role logout node - user account logout node.

[0066] In some examples, the order in which the application runs can be set by the application or triggered by the user; this is not limited here.

[0067] In some examples, the transition from one process node to another can be triggered by the application. For instance, if a user has already logged into their account, when the application is restarted, it can transition to the user role login node after a set time has elapsed since the user account login node was last logged in.

[0068] In some examples, a change from one process node to another can be triggered by the user. When the application starts, it can display the corresponding username and password input boxes in the user account login node's display interface. After the user enters the corresponding username and password in the input boxes, the application flows to the user role login node.

[0069] In some examples, the display interface can show data information such as transition videos, illustrations, and audio; it can show controls to control volume, brightness, or characters; and it can also show windows for payment links, application information, or other promotional information, without limitation.

[0070] In this embodiment, the first process node can be any of the above-mentioned process nodes, and the display interface shown by the application at the first process node is the first display interface.

[0071] Step S220: In response to the process change event, obtain the node identifier of the second process node associated with the process change event.

[0072] In this embodiment, each process node corresponds to a node identifier, which may be a string, text, or image, and is not limited to any particular type.

[0073] In some examples, each process node corresponds to a unique node identifier, such as Figure 2 As shown, the node identifier corresponding to the device initialization node is on_init, and the node identifier corresponding to the user account login node is on_user_in.

[0074] In some examples, multiple process nodes can correspond to the same node identifier. For example, the node identifier corresponding to the device initialization node is init, the user account login node and the user role logout node are corresponding to user, and the user role login node is corresponding to player.

[0075] In some embodiments, since some applications can be configured to actively trigger process changes, in order to accommodate applications with different configurations, a node identifier is associated with at least one process change event, including a process change event triggered by a user or a process change event triggered by an application.

[0076] In some examples, the node identifier is associated with a process change event that is triggered by a user. For example... Figure 3 As shown, for example, when a user enters their account and password on the device initialization node's display screen, the application flows to the user account login node. As another example, after a user selects a user role on the user account login node, the application flows to the user role login node.

[0077] In some examples, a node identifier is associated with multiple process change events, which can be triggered separately by a user or an application. For example... Figure 3 As shown, for example, when a user clicks the "Logout" control in the user role login node's display interface, the user is redirected to the user role logout node. Another example is when a user places an application in the background at the user role login node; after the application has been in the background for a period of time, the account expires, and the application actively redirects to the user role logout node.

[0078] In some examples, such as Figure 3 As shown, the first process node is the user role login node, and the process change events are role logout and account expiration. The second process node is the user role logout node, and its node identifier is on_player_out. Role logout can be triggered by the user clicking the "Exit" control in the first display interface. Account expiration can be triggered by the application after the user has placed the application in the background for a period of time, or by the application receiving a notification of an account error for the user. The specific methods of account expiration are varied and not limited here.

[0079] In other words, by setting process change events that can be triggered by users or applications, it can be applied to different applications.

[0080] The first display interface includes a first option for a process change event triggered by a user, or a second option for a process change event triggered by an application, wherein the first option or the second option corresponds to at least one interactive interface of the first display interface.

[0081] In this embodiment, the option is used to provide the user or application with a way to trigger process events. An option can be an input box, a control, a progress bar, etc., and is not limited here.

[0082] In some examples, the first and second options can be the same or different. For example, the first and second options are the same, the process change event is role logout, and role logout can be triggered by the user clicking the "Logout" control in the first display interface, or by the application selecting the "Logout" control to log out the role after the user has left the application in the background for a period of time.

[0083] In some examples, the first option and the second option can be different options but correspond to the same process change event. For example, the first option might be the user's username and password input box on the device initialization node's display interface, while the second option might be the application directly logging into the user's account based on the stored username and password. The first option and the second option can also be different options and correspond to different process change events; this is not limited here.

[0084] In this embodiment, the interactive interface can provide data information such as transition videos, illustrations, and audio. It can change the volume, brightness, or character actions based on the output of controls that control volume, brightness, or characters. It can also provide payment links, application information, or other promotional information, etc., without limitation.

[0085] In some examples, when the first option and the second option are different options, the first option and the second option can correspond to the same interaction interface or different interaction interfaces, which is not limited here.

[0086] Step S230: Based on the node identifier, cancel the display of the first display interface and display the second display interface of the application in the second process node.

[0087] In some examples, such as Figure 3 As shown, the first process node is the user account login node, and the second process node is the user role login node. The user's electronic device interface can flow from the interface selected by the user role to the game interface of game A.

[0088] In some examples, such as Figure 4 As shown, the user's electronic device displays an icon for game A on its interface. The application is game A. When the user clicks the game A icon, the electronic device requests access parameters from the server. Based on these parameters, the device initializes the SDK and displays the device initialization node interface. According to... Figure 3 The lifecycle of Game A, as shown, determines the application's current process node and corresponding interaction interface after a user or application triggers a process change event, and obtains the user's account ticket or character ticket. Based on the user's account ticket or character ticket, corresponding SDK functions are provided to the user, such as payment functionality and viewing information. Here, account tickets are the ticket information required by account-related interface services, and character tickets are the ticket information required by character-related interface services.

[0089] In other words, a user's electronic device can determine the next step in an application's process based on its lifecycle, without needing to verify access documentation, thus improving application efficiency. Furthermore, by leveraging the application's lifecycle, the efficiency of obtaining account or role tickets can be effectively improved, thereby enhancing application management efficiency.

[0090] In some embodiments, different process nodes correspond to different permission levels, and each permission level corresponds to at least one process node. The permission level is set based on the interactive interface of the display interface corresponding to the permission level. The first permission level corresponding to the first process node is different from the second permission level corresponding to the second process node.

[0091] In some examples, permission levels can be pre-defined, and there can be one, two, or multiple permission levels. For example, the permission level could include device level. Or, the permission level could include both device level and user account level. For yet another example... Figure 3 As shown, the permission levels can include device level, user account level, and user role level. Device level corresponds to device initialization node and user account logout node, user account level corresponds to user account login node and user role logout node, and user role level corresponds to user role login node.

[0092] In other words, by dividing different process nodes into different permission levels through the interaction interfaces that each process node needs to provide, the management efficiency of the application's interaction interfaces can be effectively improved.

[0093] In some embodiments, the permission levels include device level, user account level, and user role level; wherein, the interactive interface of the display interface corresponding to the device level includes a first interactive interface; wherein, the first interactive interface provides application initialization information and program update information; wherein, the interactive interface of the display interface corresponding to the user account level includes a first interactive interface and a second interactive interface; wherein, the second interactive interface provides preview information about the user's account information and the user's held roles; wherein, the interactive interface of the display interface corresponding to the user role level includes a first interactive interface, a second interactive interface, and a third interactive interface; wherein, the third interactive interface provides detailed information about the user's held roles.

[0094] In some examples, such as Figure 3 As shown, each process node corresponds to a display interface, which is configured with corresponding interactive interfaces. For example, when the application is in the device initialization node and the user account logout node, the first interactive interface corresponding to the device initialization node can provide the application's initialization information and program update information, so that the user can obtain the basic information of the electronic device or open the webview, etc.

[0095] For example, when an application logs out of a user account or user role, the interaction interface corresponding to the user account login node may include a first interaction interface and a second interaction interface. Given the application's initialization and update information, the second interaction interface provides the user's account information and a preview of the user's held role, allowing the user to view user information, open the user center, etc. Taking a game as an example, the user's held role is a virtual game character, which can be one or more, without limitation.

[0096] For example, when an application is at a user role login node, the interaction interface corresponding to that user role login node may include a first interaction interface, a second interaction interface, and a third interaction interface. Under the premise of the user application's initialization information, program update information, account information, and preview information, it provides information related to the user role, such as adding other user roles as friends or chatting with other user roles.

[0097] In other words, setting permission levels to device level, user account level, and user role level allows users to have greater and more extensive permissions to use the application at different process nodes, thereby improving the user experience.

[0098] In some embodiments, to make the interaction interfaces provided by different process nodes more reasonable, the process nodes corresponding to the device level include device login nodes and account logout nodes; the process nodes corresponding to the user account level include account login nodes and role logout nodes; and the process nodes corresponding to the user role level include role login nodes.

[0099] In some examples, when an application logs out an account, users cannot view user information or open the user center. When an application logs out a role, users cannot add other user roles as friends or chat with other user roles. Therefore, when a user logs out of a user account or user role, permissions are appropriately reduced to improve the application's security.

[0100] <Second Embodiment>

[0101] In this embodiment, in order to improve the utilization efficiency of the interaction interface, the interaction interface shared by the first process node and the second process node can be kept in the ready state, and other interaction interfaces of the second process node can be set to the ready state, so that the application can apply more SDK functions when the process node has a higher permission level.

[0102] In these embodiments, relative to the first embodiment described above, when the first permission level is lower than the second permission level, step S230 may include the following steps S310 and S320:

[0103] Step S310: Based on the node identifier, cancel the display of the first display interface, maintain the first part of the interactive interface in the ready state, and set the second part of the interactive interface to the ready state; wherein, the first part of the interactive interface corresponds to the first permission level, and the first part of the interactive interface and the second part of the interactive interface correspond to the second permission level.

[0104] In this embodiment, the interactive interface may have a ready state, and the interactive interface in the ready state may have corresponding information or controls.

[0105] In some examples, the interactive interface may also have a disabled or enabled state. For instance, if the application is in the user account login node, then the disabled interactive interface is the one corresponding to the user role login node. As another example, if a user opens the user center in the user account login node, then the enabled interactive interface is the one corresponding to the user account login node.

[0106] Step S320: Display the second display interface of the application at the second process node.

[0107] In some examples, when the first process node is a user account login node, the second process node can be a user role login node, and the user's electronic device can display the interface of the user role login node.

[0108] In other words, by setting the additional second part of the interaction interface of the second process node to the ready state, the utilization rate of the first part of the interaction interface can be effectively improved.

[0109] In some embodiments, to further enhance the security of user accounts, the first permission level is the next level below the second permission level.

[0110] In some examples, such as Figure 3 As shown, when a user enters their username and password at the device initialization node, the process redirects to the user account login node to provide the user with account information. In other words, by restricting the user's sequential access to both the user account and user role, the security of the user account and user role can be further enhanced.

[0111] <Second Embodiment>

[0112] In this embodiment, in order to further improve the utilization efficiency of the interaction interface, the interaction interface shared by the first process node and the second process node can be kept in a ready state, so that the application can maintain basic SDK functions when the process node has a lower permission level.

[0113] In these embodiments, relative to the first embodiment described above, when the first permission level is higher than the second permission level, step S230 may include the following steps S410 and S420:

[0114] Step S410: Based on the node identifier, cancel the display of the first display interface, end the preparation state of the third part of the interaction interface, and maintain the preparation state of the fourth part of the interaction interface; wherein, the third part of the interaction interface corresponds to the first permission level, and the fourth part of the interaction interface corresponds to the first permission level and the second permission level.

[0115] In this embodiment, the interactive interface may have a ready state, and the interactive interface in the ready state may have corresponding information or controls.

[0116] In some examples, the interactive interface may also have a disabled or enabled state. For instance, if the application is in the user account login node, then the disabled interactive interface is the one corresponding to the user role login node. As another example, if a user opens the user center in the user account login node, then the enabled interactive interface is the one corresponding to the user account login node.

[0117] Step S420: Display the second display interface of the application at the second process node.

[0118] In some examples, when the first process node is a user role login node, the second process node can be a user role logout node, and the user's electronic device can display the user role logout node's interface. The second process node can also be a user account logout node, and the user's electronic device can display the user account logout node's interface.

[0119] In other words, by disabling the interaction interfaces that are not shared by the first and second process nodes, the security of user accounts and user roles can be effectively improved.

[0120] In some embodiments, in order to accommodate applications with different settings, the second permission level is any lower level of the first permission level.

[0121] In some examples, such as Figure 3 As shown, the first process node is the user role login node, and the process change event is the role logout or account expiration. Therefore, the second process node can be the user role logout node.

[0122] In some examples, such as Figure 5As shown, the first process node is the user role login node, and the process change event is the role logout. Therefore, the second process node can be the user role logout node; the process change event is the account expiration, so the second process node can be the user account logout node.

[0123] In other words, by setting the second permission level to any lower level of the first permission level, it can be effectively applied to applications with different settings.

[0124] <Equipment Example 1>

[0125] Figure 6 This is a schematic block diagram of an application runtime optimization apparatus according to one embodiment. Figure 6 As shown, the application's operation optimization device 500 may include a display module 510, a response module 520, and a switching module 530.

[0126] The display module 510 is used to display the first display interface of the application at the first process node;

[0127] The response module 520 is used to respond to a process change event and obtain the node identifier of the second process node associated with the process change event;

[0128] The switching module 530 is used to cancel the display of the first display interface and display the second display interface of the application at the second process node according to the node identifier.

[0129] Optionally, the switching module 530 is also used to cancel the display of the first display interface according to the node identifier, maintain the first part of the interactive interface in the ready state, and set the second part of the interactive interface to the ready state; wherein, the first part of the interactive interface corresponds to the first permission level, and the first part of the interactive interface and the second part of the interactive interface correspond to the second permission level; and display the second display interface of the application at the second process node.

[0130] Optionally, the switching module 530 is also used to, based on the node identifier, cancel the display of the first display interface, end the preparation state of the third part of the interaction interface, and maintain the preparation state of the fourth part of the interaction interface; wherein, the third part of the interaction interface corresponds to the first permission level, and the fourth part of the interaction interface corresponds to the first permission level and the second permission level; and display the second display interface of the application at the second process node.

[0131] The application's performance optimization device 500 can be Figure 1 1000 electronic devices in the system.

[0132] <Equipment Example 2>

[0133] Figure 7 This is a schematic diagram of the hardware structure of an electronic device according to another embodiment.

[0134] like Figure 7 As shown, the electronic device 600 includes a processor 610 and a memory 620, the memory 620 for storing an executable computer program, and the processor 610 for executing methods as described in any of the above method embodiments under the control of the computer program.

[0135] The electronic device 600 can be Figure 1 1000 electronic devices in the system.

[0136] Each module of the above application running optimization device 500 can be implemented by the processor 610 in this embodiment executing the computer program stored in the memory 620, or it can be implemented by other structures, which are not limited here.

[0137] This invention can be a system, method, and / or computer program product. A computer program product may include a computer-readable storage medium having computer-readable program instructions loaded thereon for causing a processor to implement various aspects of the invention.

[0138] Computer-readable storage media can be tangible devices capable of holding and storing instructions for use by an instruction execution device. Computer-readable storage media can be, for example—but not limited to—electrical storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital multifunction disc (DVD), memory sticks, floppy disks, mechanical encoding devices, such as punch cards or recessed protrusions storing instructions thereon, and any suitable combination thereof. The computer-readable storage media used herein are not to be construed as transient signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses through fiber optic cables), or electrical signals transmitted through wires.

[0139] The computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to the computer-readable storage media in the respective computing / processing device.

[0140] The computer program instructions used to perform the operations of this invention may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, etc., and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The computer-readable program instructions may be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuitry, such as programmable logic circuitry, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), is personalized by utilizing state information from the computer-readable program instructions. This electronic circuitry can execute the computer-readable program instructions to implement various aspects of the invention.

[0141] Various aspects of the present invention are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0142] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0143] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0144] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions. It will be known to those skilled in the art that implementation in hardware, implementation in software, and implementation using a combination of software and hardware are equivalent.

[0145] The various embodiments of the present invention have been described above. These descriptions are exemplary and not exhaustive, and are not limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles, practical application, or technical improvements to the embodiments in the market, or to enable others skilled in the art to understand the embodiments disclosed herein. The scope of the invention is defined by the appended claims.

Claims

1. A method for optimizing the execution of an application program, characterized in that, The method includes: The application displays its first interface at the first process node; In response to a process change event, obtain the node identifier of the second process node associated with the process change event; Based on the node identifier, the first display interface is canceled and the second display interface of the application is displayed at the second process node. The first process node and the second process node are process nodes in the process sequence of the application. The application is a game program. The second process node is after the first process node. The determination of the second process node is based on the life cycle of the application.

2. The method according to claim 1, characterized in that, The node identifier is associated with at least one process change event, including a process change event triggered by a user or a process change event triggered by the application. The first display interface includes a first option triggered by a process change event by the user, or a second option triggered by the application, wherein the first option or the second option corresponds to at least one interactive interface of the first display interface.

3. The method according to claim 1, characterized in that, Different process nodes correspond to different permission levels, and each permission level corresponds to at least one process node. The permission level is set based on the interactive interface of the display interface corresponding to that permission level. The first permission level corresponding to the first process node is different from the second permission level corresponding to the second process node.

4. The method according to claim 3, characterized in that, The permission levels include device level, user account level, and user role level; The interactive interface of the display interface corresponding to the device level includes a first interactive interface; wherein the first interactive interface provides the application's initialization information and program update information; The interactive interface of the display interface corresponding to the user account level includes a first interactive interface and a second interactive interface; wherein, the second interactive interface provides preview information about the user's account information and the role held by the user; The interactive interfaces of the display interface corresponding to the user role level include a first interactive interface, a second interactive interface, and a third interactive interface; wherein, the third interactive interface provides detailed information about the role held by the user.

5. The method according to claim 4, characterized in that, The process nodes corresponding to the device level include the device login node and the account logout node; The process nodes corresponding to the user account level include the account login node and the role logout node; The process nodes corresponding to the user role level include the role login node.

6. The method according to claim 3, characterized in that, When the first permission level is lower than the second permission level, the step of canceling the display of the first display interface and displaying the second display interface of the application at the second process node according to the node identifier includes: Based on the node identifier, the first display interface is canceled, the first part of the interactive interface is kept in the ready state, and the second part of the interactive interface is set to the ready state; wherein, the first part of the interactive interface corresponds to the first permission level, and the first part of the interactive interface and the second part of the interactive interface correspond to the second permission level. The application is displayed in the second presentation interface at the second process node.

7. The method according to claim 6, characterized in that, The first permission level is the next level below the second permission level.

8. The method according to claim 3, characterized in that, When the first permission level is higher than the second permission level, the step of canceling the display of the first display interface and displaying the second display interface of the application at the second process node according to the node identifier includes: Based on the node identifier, the first display interface is canceled, the third part of the interaction interface is put into a ready state, and the fourth part of the interaction interface is kept in a ready state; wherein, the third part of the interaction interface corresponds to the first permission level, and the fourth part of the interaction interface corresponds to the first permission level and the second permission level. The application is displayed in the second presentation interface at the second process node.

9. The method according to claim 8, characterized in that, The second permission level is any lower level of the first permission level.

10. An application runtime optimization device, characterized in that, The device includes: The display module is used to display the first display interface of the application at the first process node; A response module is used to respond to a process change event and obtain the node identifier of the second process node associated with the process change event; The switching module is used to cancel the display of the first display interface and display the second display interface of the application at the second process node according to the node identifier. The first process node and the second process node are process nodes in the process sequence of the application. The application is a game program. The second process node is after the first process node. The determination of the second process node is based on the life cycle of the application.

11. An electronic device, characterized in that, The system includes a memory and a processor, the memory being used to store a computer program; the processor being used to execute the computer program to implement the method according to any one of claims 1 to 9.

Images