Object Management Method, Device, Electronic Device, and Computer Readable Storage Medium

Abstract

An embodiment of the present disclosure discloses an object management method, apparatus, electronic device, and computer-readable storage medium. The method includes: in response to receiving a first object startup request, obtaining first object startup data; starting a first object according to the first object startup data; in response to receiving a second object jump request, saving the running data of the first object before the jump, and jumping to the second object, where the first object and the second object are generated based on the same generation tool. This technical solution can establish a management link between different objects, enabling developers to manage and schedule multiple objects without having to be familiar with the underlying system logic of different terminal devices, nor having to perform adaptation runs or repeated development on terminal devices of different systems, thus bringing great convenience to developers and effectively improving the work efficiency of developers.

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the field of data processing technology, and in particular to an object management method, device, electronic device, and computer-readable storage medium. Background Art

[0002] With the development of network science and technology and data processing technology, the use of applications and other programs is becoming more and more widespread. The same user often needs to operate multiple applications at the same time, especially for the Internet of Things that is connected to multiple terminal devices or smart terminal devices, and needs to frequently jump between different devices or different applications. However, many devices are currently directly based on Linux or RTOS (Real-Time Operating System) when developing applications, using development languages ​​such as C++. This requires developers in multiple application fields such as the Internet of Things to be familiar with the underlying system logic of different terminal devices, and also needs to adapt and run or repeat development on terminal devices of different systems, which brings inconvenience to developers and is not conducive to improving the work efficiency of developers. Summary of the invention

[0003] Embodiments of the present disclosure provide an object management method, an apparatus, an electronic device, and a computer-readable storage medium.

[0004] In a first aspect, an object management method is provided in an embodiment of the present disclosure.

[0005] Specifically, the object management method includes:

[0006] In response to receiving the first object startup request, acquiring first object startup data;

[0007] Starting the first object according to the first object starting data;

[0008] In response to receiving a second object jump request, saving the running data of the first object before the jump, and jumping to the second object, wherein the first object and the second object are generated based on the same generation tool.

[0009] In combination with the first aspect, in a first implementation of the first aspect of the embodiment of the present disclosure, in response to receiving the first object startup request, obtaining the first object startup data includes:

[0010] In response to receiving the first object startup request, confirming whether the first object startup data is stored in the cache;

[0011] When it is confirmed that the first object startup data is stored in the cache, reading the first object startup data from the cache;

[0012] When it is confirmed that the first object startup data is not stored in the cache, a first object startup data acquisition request is sent to a data server to acquire the first object startup data.

[0013] In combination with the first aspect and the first implementation of the first aspect, in a second implementation of the first aspect of the embodiment of the present disclosure, when it is confirmed that the first object startup data is stored in the cache, after reading the first object startup data from the cache, the method further includes:

[0014] A first object start-update data query request is sent to the data server, and when the data server confirms that the first object start-update data exists, the first object start-update data sent by the data server is received.

[0015] In combination with the first aspect, the first implementation of the first aspect, and the second implementation of the first aspect, in a third implementation of the first aspect of the present disclosure, in response to receiving a second object jump request, jumping to the second object includes:

[0016] In response to receiving the second object jump request, acquiring second object startup data;

[0017] The second object is started according to the second object start data.

[0018] In combination with the first aspect, the first implementation manner of the first aspect, the second implementation manner of the first aspect, and the third implementation manner of the first aspect, in a fourth implementation manner of the first aspect of the present disclosure, in response to receiving a second object jump request, obtaining second object startup data includes:

[0019] In response to receiving the second object jump request, confirming whether the second object startup data is stored in the cache;

[0020] When it is confirmed that the second object startup data is stored in the cache, reading the second object startup data from the cache;

[0021] When it is confirmed that the second object startup data is not stored in the cache, a second object startup data acquisition request is sent to the data server to acquire the second object startup data.

[0022] In combination with the first aspect, the first implementation of the first aspect, the second implementation of the first aspect, the third implementation of the first aspect, and the fourth implementation of the first aspect, the fifth implementation of the first aspect of the present disclosure further includes:

[0023] In response to receiving the first object recovery request, the first object is recovered according to the running data of the first object before the jump.

[0024] In combination with the first aspect, the first implementation of the first aspect, the second implementation of the first aspect, the third implementation of the first aspect, the fourth implementation of the first aspect, and the fifth implementation of the first aspect, the sixth implementation of the first aspect of the present disclosure further includes:

[0025] The objects are arranged according to the time when they were last operated.

[0026] In combination with the first aspect, the first implementation of the first aspect, the second implementation of the first aspect, the third implementation of the first aspect, the fourth implementation of the first aspect, the fifth implementation of the first aspect, and the sixth implementation of the first aspect, the seventh implementation of the first aspect of the present disclosure further includes:

[0027] In response to receiving the object execution termination request, the object execution is terminated in sequence according to the last operation time of the object.

[0028] In combination with the first aspect, the first implementation of the first aspect, the second implementation of the first aspect, the third implementation of the first aspect, the fourth implementation of the first aspect, the fifth implementation of the first aspect, the sixth implementation of the first aspect, and the seventh implementation of the first aspect, the eighth implementation of the first aspect of the present disclosure further includes:

[0029] Preset management is performed for the object, wherein the preset management includes one or more of the following managements: object page management, object resource management, object visual component management, object functional module component management, and object message management.

[0030] In a second aspect, an object management device is provided in an embodiment of the present disclosure.

[0031] Specifically, the object management device includes:

[0032] an acquisition module, configured to acquire first object startup data in response to receiving a first object startup request;

[0033] A startup module, configured to start the first object according to the first object startup data;

[0034] The jump module is configured to save the running data of the first object before the jump in response to receiving a jump request for the second object, and jump to the second object, wherein the first object and the second object are generated based on the same generation tool.

[0035] In combination with the second aspect, in a first implementation of the second aspect of the embodiment of the present disclosure, the acquisition module is configured as follows:

[0036] In response to receiving the first object startup request, confirming whether the first object startup data is stored in the cache;

[0037] When it is confirmed that the first object startup data is stored in the cache, reading the first object startup data from the cache;

[0038] When it is confirmed that the first object startup data is not stored in the cache, a first object startup data acquisition request is sent to a data server to acquire the first object startup data.

[0039] In combination with the second aspect and the first implementation of the second aspect, in the second implementation of the second aspect of the embodiment of the present disclosure, when it is confirmed that the first object startup data is stored in the cache, after reading the first object startup data from the cache, the acquisition module is further configured to:

[0040] A first object start-update data query request is sent to the data server, and when the data server confirms that the first object start-update data exists, the first object start-update data sent by the data server is received.

[0041] In combination with the second aspect, the first implementation of the second aspect, and the second implementation of the second aspect, in a third implementation of the second aspect of the present disclosure, the jump module is configured as follows:

[0042] In response to receiving the second object jump request, acquiring second object startup data;

[0043] The second object is started according to the second object start data.

[0044] In combination with the second aspect, the first implementation manner of the second aspect, the second implementation manner of the second aspect, and the third implementation manner of the second aspect, in a fourth implementation manner of the second aspect of the present disclosure, the part of acquiring the second object startup data in response to receiving the second object jump request is configured as follows:

[0045] In response to receiving the second object jump request, confirming whether the second object startup data is stored in the cache;

[0046] When it is confirmed that the second object startup data is stored in the cache, reading the second object startup data from the cache;

[0047] When it is confirmed that the second object startup data is not stored in the cache, a second object startup data acquisition request is sent to the data server to acquire the second object startup data.

[0048] In combination with the second aspect, the first implementation manner of the second aspect, the second implementation manner of the second aspect, the third implementation manner of the second aspect, and the fourth implementation manner of the second aspect, the present disclosure, in a fifth implementation manner of the second aspect, further includes:

[0049] The recovery module is configured to, in response to receiving a recovery request for the first object, recover the first object according to the running data before the first object jumps.

[0050] In combination with the second aspect, the first implementation manner of the second aspect, the second implementation manner of the second aspect, the third implementation manner of the second aspect, the fourth implementation manner of the second aspect, and the fifth implementation manner of the second aspect, the present disclosure, in a sixth implementation manner of the second aspect, further includes:

[0051] The arrangement module is configured to arrange the objects according to the last operation time of the objects.

[0052] In combination with the second aspect, the first implementation manner of the second aspect, the second implementation manner of the second aspect, the third implementation manner of the second aspect, the fourth implementation manner of the second aspect, the fifth implementation manner of the second aspect, and the sixth implementation manner of the second aspect, the seventh implementation manner of the second aspect of the present disclosure further includes:

[0053] The ending module is configured to, in response to receiving a request to end the operation of the object, end the operation of the objects in sequence according to the last operation time of the object.

[0054] In combination with the second aspect, the first implementation manner of the second aspect, the second implementation manner of the second aspect, the third implementation manner of the second aspect, the fourth implementation manner of the second aspect, the fifth implementation manner of the second aspect, the sixth implementation manner of the second aspect, and the seventh implementation manner of the second aspect, the eighth implementation manner of the second aspect of the present disclosure further includes:

[0055] The management module is configured to perform preset management on the object, wherein the preset management includes one or more of the following managements: object page management, object resource management, object visual component management, object functional module component management and object message management.

[0056] In a third aspect, an embodiment of the present disclosure provides an electronic device, including a memory and a processor, wherein the memory is used to store one or more computer instructions that support an object management device to execute the above-mentioned object management method, and the processor is configured to execute the computer instructions stored in the memory. The object management device may also include a communication interface for the object management device to communicate with other devices or a communication network.

[0057] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium for storing computer instructions used by an object management device, which includes computer instructions involved in the object management device for executing the above-mentioned object management method.

[0058] The technical solution provided by the embodiments of the present disclosure may have the following beneficial effects:

[0059] The above technical solution realizes time-sharing startup and mutual jump of different objects by establishing management mechanisms and strategies for different objects generated based on the same generation tool. The technical solution can establish management links between different objects, so that developers do not need to be familiar with the underlying system logic of different terminal devices, nor do they need to adapt and run or repeat development on terminal devices of different systems, and can realize the management and scheduling of multiple objects, which brings great convenience to developers and effectively improves their work efficiency.

[0060] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0061] Other features, purposes and advantages of the embodiments of the present disclosure will become more apparent through the following detailed description of non-limiting embodiments in conjunction with the accompanying drawings. In the accompanying drawings:

[0062] Figure 1 A flowchart showing an object management method according to an embodiment of the present disclosure is shown;

[0063] Figure 2 A schematic diagram showing an application scenario of an object management method according to an embodiment of the present disclosure;

[0064] Figure 3 A structural block diagram of an object management device according to an embodiment of the present disclosure is shown;

[0065] Figure 4 It is a structural diagram of a computer system suitable for implementing an object management method according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0066] Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily implement them. In addition, for the sake of clarity, parts not related to the description of the exemplary embodiments are omitted in the accompanying drawings.

[0067] In the embodiments of the present disclosure, it should be understood that terms such as "including" or "having" are intended to indicate the existence of features, numbers, steps, behaviors, components, parts, or a combination thereof disclosed in this specification, and are not intended to exclude the possibility of one or more other features, numbers, steps, behaviors, components, parts, or a combination thereof existing or being added.

[0068] It should also be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present disclosure may be combined with each other. The embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0069] The technical solution provided by the embodiment of the present disclosure realizes time-sharing startup and mutual jump of different objects by establishing a management mechanism and strategy for different objects generated based on the same generation tool. The technical solution can establish a management link between different objects, so that developers do not need to be familiar with the underlying system logic of different terminal devices, nor do they need to adapt and run or repeat development on terminal devices of different systems, and can realize the management and scheduling of multiple objects, thereby bringing great convenience to developers and effectively improving the work efficiency of developers.

[0070] Figure 1 A flowchart of an object management method according to an embodiment of the present disclosure is shown as follows: Figure 1 As shown, the object management method includes the following steps S101-S103:

[0071] In step S101, in response to receiving a first object startup request, first object startup data is acquired;

[0072] In step S102, the first object is started according to the first object start data;

[0073] In step S103, in response to receiving a second object jump request, the running data of the first object before the jump is saved, and the jump is to the second object, wherein the first object and the second object are generated based on the same generation tool.

[0074] As mentioned above, with the development of network science and technology and data processing technology, the use of applications and other programs is becoming more and more widespread. The same user often needs to operate multiple applications at the same time, especially for the Internet of Things that is connected to multiple terminal devices or smart terminal devices, and needs to frequently jump between different devices or different applications. However, many devices are currently directly based on Linux or RTOS when developing applications, using development languages ​​such as C++. This requires developers in multiple application fields such as the Internet of Things to be familiar with the underlying system logic of different terminal devices, and also need to adapt and run or repeat development on terminal devices of different systems, which brings inconvenience to developers and is not conducive to improving the work efficiency of developers.

[0075] In view of the above problems, in this embodiment, an object management method is proposed, which realizes the time-sharing startup and mutual jump of different objects by establishing a management mechanism and strategy for different objects generated based on the same generation tool. This technical solution can establish a management link between different objects, so that developers do not need to be familiar with the underlying system logic of different terminal devices, nor do they need to adapt and run or repeat development on terminal devices of different systems, and can realize the management and scheduling of multiple objects, thereby bringing great convenience to developers and effectively improving the work efficiency of developers.

[0076] In one embodiment of the present disclosure, the object management method may be applicable to computers, computing devices, electronic devices, servers, service clusters, etc. that manage objects.

[0077] In one embodiment of the present disclosure, the object refers to an object such as an application program or a process that can be started, can be run, can generate running results, and can generate corresponding running data during the running process.

[0078] In one embodiment of the present disclosure, the first object start request refers to a request to start the first object and make it begin running, wherein the first object start request can be issued by the user of the first object, such as a user, can be issued by other objects, or can be issued by a system or other management party. The present invention does not specifically limit the issuer of the first object start request.

[0079] In one embodiment of the present disclosure, the first object startup data refers to data that can start the first object to run, wherein the first object startup data may be stored in a remote server or in a local cache.

[0080] In one embodiment of the present disclosure, the second object jump request refers to a request to jump to the second object so that the second object starts to run while other objects are running. Similar to the first object start request, the second object jump request can be issued by the user of the second object, such as a user, or by other objects, or by a system or other management party. The present invention does not specifically limit the issuer of the second object jump request.

[0081] In order to ensure that the user of the first object can see the data of the first object before the jump when he wants to jump back to the first object from another object, so as to save the operation time of the user of the first object and avoid the need to reload all the data of the first object, therefore, in one embodiment of the present disclosure, before receiving a second object jump request to jump to the second object, it is necessary to first save the current running data of the first object, that is, the running data before jumping to the second object, wherein the current running data of the first object can enable the first object to quickly and completely restore to the running state before the running data of the first object was saved.

[0082] In one embodiment of the present disclosure, in order to facilitate the management and scheduling of objects and the transmission of object-related data, the first object and the second object are generated based on the same generation tool, wherein the generation tool may be, for example, javascript (JS, a lightweight interpreted programming language with function priority) and other tools.

[0083] In an embodiment of the present disclosure, the step S101, i.e., the step of acquiring the first object startup data in response to receiving the first object startup request, includes the following steps:

[0084] In response to receiving the first object startup request, confirming whether the first object startup data is stored in the cache;

[0085] When it is confirmed that the first object startup data is stored in the cache, reading the first object startup data from the cache;

[0086] When it is confirmed that the first object startup data is not stored in the cache, a first object startup data acquisition request is sent to a data server to acquire the first object startup data.

[0087] In order to obtain the first object startup data as quickly as possible and improve the startup speed of the first object as much as possible, in this embodiment, it is first checked whether the first object startup data is stored in the local cache. If not, a request is made to obtain it from the data server. Specifically, when the first object startup request is received, it is first confirmed whether the first object startup data for starting the first object is pre-stored in the local cache. If so, the first object startup data is directly taken out from the cache to start the first object. If not, a first object startup data acquisition request is sent to the data server to obtain the first object startup data from the data server to start the first object, wherein the data server refers to a server for storing object-related data, which can be either a remote server or a local server, and the above-mentioned data pre-stored in the cache can be requested to be downloaded from the data server.

[0088] In an embodiment of the present disclosure, when it is confirmed that the first object startup data is stored in the cache, after reading the first object startup data from the cache, the following steps are further included:

[0089] A first object start-update data query request is sent to the data server, and when the data server confirms that the first object start-update data exists, the first object start-update data sent by the data server is received.

[0090] As mentioned above, in order to start the first object as soon as possible and save the waiting time of the first object user, when the first object startup data for starting the first object is pre-stored in the local cache, the first object startup data is directly taken out from the cache to start the first object. However, considering that the original data stored in the data server may be updated, in this embodiment, in order to provide the first object user with the latest and most complete data, after the first object startup data is taken out from the cache to start the first object, a first object startup update data query request is also sent to the data server. If the data server confirms that there is the first object startup update data, the first object startup update data can be received from the data server and stored in the local cache, so that the latest first object startup data can be used to start the first object when the first object startup request is received next time.

[0091] In an embodiment of the present disclosure, the step S103, i.e., the step of jumping to the second object in response to receiving the second object jump request, may include the following steps:

[0092] In response to receiving the second object jump request, acquiring second object startup data;

[0093] The second object is started according to the second object start data.

[0094] In this embodiment, although the second object is jumped in response to the second object jump request, its startup mechanism is similar to the startup mechanism of the first object, that is, after receiving the second object jump request, it is necessary to first obtain the second object startup data, and then perform the startup operation on the second object according to the second object startup data.

[0095] In an embodiment of the present disclosure, the step of acquiring the second object startup data in response to receiving the second object jump request includes the following steps:

[0096] In response to receiving the second object jump request, confirming whether the second object startup data is stored in the cache;

[0097] When it is confirmed that the second object startup data is stored in the cache, reading the second object startup data from the cache;

[0098] When it is confirmed that the second object startup data is not stored in the cache, a second object startup data acquisition request is sent to the data server to acquire the second object startup data.

[0099] Similar to the step of obtaining the first object startup data described above, in this embodiment, when the second object startup data needs to be obtained, first confirm whether the second object startup data for starting the second object is pre-stored in the local cache, if yes, directly fetch the second object startup data from the cache to start the second object, if no, send a second object startup data acquisition request to the data server to obtain the second object startup data from the data server to start the second object. By analogy, the jump of multiple objects can be realized.

[0100] As mentioned above, in order to ensure that the user of the first object can see the data of the first object before the jump when he wants to jump back to the first object from another object, so as to save the operation time of the user of the first object and avoid the situation where all the data of the first object need to be reloaded, in one embodiment of the present disclosure, before jumping to the second object, it is necessary to save the current running data of the first object, that is, the running data before jumping to the second object, wherein the current running data of the first object can enable the first object to quickly and completely restore to the running state before the running data of the first object was saved. In this embodiment, the method also includes the following steps:

[0101] In response to receiving the first object recovery request, the first object is recovered according to the running data of the first object before the jump.

[0102] In one embodiment of the present disclosure, the first object recovery request refers to a request for restoring the operation of the first object, wherein, similar to the first object start request and the second object jump request, the first object recovery request can be issued by the user of the first object, such as a user, can be issued by other objects, or can be issued by a system or other management party. The present invention does not specifically limit the issuer of the first object recovery request.

[0103] In one embodiment of the present disclosure, the method further comprises the following steps:

[0104] The objects are arranged according to the time when they were last operated.

[0105] In order to determine the heat order of different objects so as to determine the order of object exit when the objects are exited later, in this embodiment, the objects are also arranged according to the last operation time of the objects, so that when a request to end the operation of the objects is received later, the operation of the objects can be terminated in sequence according to the last operation time of the objects, for example, the object whose last operation time is closest to the current time is terminated first, and so on. That is, in this embodiment, the method further includes the following steps:

[0106] In response to receiving the object execution termination request, the execution of corresponding objects is terminated in sequence according to the last operation time of the object to be terminated specified in the object execution termination request.

[0107] In one embodiment of the present disclosure, the object end operation request refers to a request for ending the operation of the object, wherein the object may be one or more. Similar to the first object start request, the second object jump request and the first object recovery request, the object end operation request may be issued by the user of the object, such as a user, or may be issued by other objects, or may be issued by a system or other management party. The present invention does not specifically limit the issuer of the object end operation request. In one embodiment of the present disclosure, the object end operation request may be a first object recovery request, in which case it may be considered that all objects except the first object are designated to end operation, and the first object recovery request may also be a request carrying designated end operation object identification information, so as to perform an end operation operation on the corresponding object according to the designated end operation object identification information.

[0108] In one embodiment of the present disclosure, the method further comprises the following steps:

[0109] Preset management is performed for the object, wherein the preset management includes one or more of the following managements: object page management, object resource management, object visual component management, object functional module component management, object message management, and the like.

[0110] In addition to the above-mentioned scheduling management of objects, the present disclosure can also manage the objects in various aspects, such as object page management, object resource management, object visual component management, object functional module component management, object message management, etc., wherein the object page management refers to the scheduling of the object display page and the management of the display page data; the object resource management refers to the management of the pictures, sounds and other resource data involved in the object; the object visual component management refers to the management of the components related to the object and vision; the object functional module component management refers to the management of the functional components related to the object; the object message management refers to the management of object-related messages, such as messages between components within the object and messages between objects. In this way, an object management framework can be formed to coordinate the management and scheduling of multiple objects generated based on the same generation tool to meet the management needs of the object users and eliminate the management obstacles of objects generated by different generation tools.

[0111] Figure 2 A schematic diagram showing an application scenario of an object management method according to an embodiment of the present disclosure is shown as follows: Figure 2As shown, in this scenario, the object user is the user, the object manager is the management server, and the object is the application. The user sends a first application startup request to the management server through voice or screen operation. After receiving the first application startup request, the management server first confirms whether the first application startup data is stored in the local cache. If so, the first application startup data is read from the cache to start and display the application, and at the same time requests the first application startup update data from the data server for use when the first application is started next time; if not, a first application startup data acquisition request is sent to the data server to obtain the first application startup data from the data server to start and display the application. If the user wants to jump from the first application to the second application, the second application jump request is sent to the management server with the help of the user's operation. After receiving the second application jump request, the management server obtains the second application startup data from the cache or data server to realize the jump of the second application, similar to the startup process of the first application. The difference is that before the jump operation takes effect, the running status data of the first application needs to be saved first, so as to be used when the first application is restored later. By analogy, if the user wants to jump from the second application to the third application, similarly, with the help of the user's operation, a third application jump request is sent to the management server. After receiving the third application jump request, the management server obtains the third application startup data from the cache or data server to realize the jump of the third application, and saves the running status data of the second application before the jump operation takes effect, so as to be used when the second application is restored later. The jump of the user to start more applications is similar to the above, which not only realizes the free jump of multiple applications, but also can use the previously saved running status data to quickly restore the corresponding application when the user determines to jump back to which application was started before at any time. Assuming that the user wants to return to the second application after launching the third application, a second application recovery request can be sent to the management server. The management server ends the operation of the third application in the order of the last operation time according to the second application recovery request, and quickly restores the operation of the second application by using the previously saved second application operation data; assuming that the user wants to return to the first application after launching the second application and the third application in sequence, a first application recovery request can be sent to the management server. The management server ends the operation of the third application and the second application in the order of the last operation time according to the first application recovery request, and quickly restores the operation of the first application by using the previously saved first application operation data.

[0112] The following are embodiments of the apparatus of the present disclosure, which can be used to execute embodiments of the method of the present disclosure.

[0113] Figure 3FIG. 1 is a block diagram showing a structure of an object management device according to an embodiment of the present disclosure. The device can be implemented as part or all of an electronic device through software, hardware, or a combination of both. Figure 3 As shown, the object management device includes:

[0114] The acquisition module 301 is configured to acquire first object startup data in response to receiving a first object startup request;

[0115] A startup module 302 is configured to start the first object according to the first object startup data;

[0116] The jump module 303 is configured to save the running data of the first object before the jump in response to receiving the jump request of the second object, and jump to the second object, wherein the first object and the second object are generated based on the same generation tool.

[0117] As mentioned above, with the development of network science and technology and data processing technology, the use of applications and other programs is becoming more and more widespread. The same user often needs to operate multiple applications at the same time, especially for the Internet of Things that is connected to multiple terminal devices or smart terminal devices, and needs to frequently jump between different devices or different applications. However, many devices are currently directly based on Linux or RTOS when developing applications, using development languages ​​such as C++. This requires developers in multiple application fields such as the Internet of Things to be familiar with the underlying system logic of different terminal devices, and also need to adapt and run or repeat development on terminal devices of different systems, which brings inconvenience to developers and is not conducive to improving the work efficiency of developers.

[0118] In view of the above problems, in this embodiment, an object management device is proposed, which realizes time-sharing startup and mutual jump of different objects by establishing a management mechanism and strategy for different objects generated based on the same generation tool. This technical solution can establish a management link between different objects, so that developers do not need to be familiar with the underlying system logic of different terminal devices, nor do they need to adapt and run or repeat development on terminal devices of different systems, and can realize the management and scheduling of multiple objects, thereby bringing great convenience to developers and effectively improving the work efficiency of developers.

[0119] In one embodiment of the present disclosure, the object management device may be implemented as a computer, a computing device, an electronic device, a server, a service cluster, etc. that manages objects.

[0120] In one embodiment of the present disclosure, the object refers to an object such as an application program or a process that can be started, can be run, can generate running results, and can generate corresponding running data during the running process.

[0121] In one embodiment of the present disclosure, the first object start request refers to a request to start the first object and make it begin running, wherein the first object start request can be issued by the user of the first object, such as a user, can be issued by other objects, or can be issued by a system or other management party. The present invention does not specifically limit the issuer of the first object start request.

[0122] In one embodiment of the present disclosure, the first object startup data refers to data that can start the first object to run, wherein the first object startup data may be stored in a remote server or in a local cache.

[0123] In one embodiment of the present disclosure, the second object jump request refers to a request to jump to the second object so that the second object starts to run while other objects are running. Similar to the first object start request, the second object jump request can be issued by the user of the second object, such as a user, or by other objects, or by a system or other management party. The present invention does not specifically limit the issuer of the second object jump request.

[0124] In order to ensure that the user of the first object can see the data of the first object before the jump when he wants to jump back to the first object from another object, so as to save the operation time of the user of the first object and avoid the need to reload all the data of the first object, therefore, in one embodiment of the present disclosure, before receiving a second object jump request to jump to the second object, it is necessary to first save the current running data of the first object, that is, the running data before jumping to the second object, wherein the current running data of the first object can enable the first object to quickly and completely restore to the running state before the running data of the first object was saved.

[0125] In one embodiment of the present disclosure, in order to facilitate the management and scheduling of objects and the transmission of object-related data, the first object and the second object are generated based on the same generation tool, wherein the generation tool may be, for example, javascript (JS, a lightweight interpreted programming language with function priority) and other tools.

[0126] In one embodiment of the present disclosure, the acquisition module 301 may be configured as follows:

[0127] In response to receiving the first object startup request, confirming whether the first object startup data is stored in the cache;

[0128] When it is confirmed that the first object startup data is stored in the cache, reading the first object startup data from the cache;

[0129] When it is confirmed that the first object startup data is not stored in the cache, a first object startup data acquisition request is sent to a data server to acquire the first object startup data.

[0130] In order to obtain the first object startup data as quickly as possible and improve the startup speed of the first object as much as possible, in this embodiment, it is first checked whether the first object startup data is stored in the local cache. If not, a request is made to obtain it from the data server. Specifically, when the first object startup request is received, it is first confirmed whether the first object startup data for starting the first object is pre-stored in the local cache. If so, the first object startup data is directly taken out from the cache to start the first object. If not, a first object startup data acquisition request is sent to the data server to obtain the first object startup data from the data server to start the first object, wherein the data server refers to a server for storing object-related data, which can be either a remote server or a local server, and the above-mentioned data pre-stored in the cache can be requested to be downloaded from the data server.

[0131] In an embodiment of the present disclosure, when it is confirmed that the first object startup data is stored in the cache, after reading the first object startup data from the cache, the acquisition module 301 is further configured to:

[0132] A first object start-update data query request is sent to the data server, and when the data server confirms that the first object start-update data exists, the first object start-update data sent by the data server is received.

[0133] As mentioned above, in order to start the first object as soon as possible and save the waiting time of the first object user, when the first object startup data for starting the first object is pre-stored in the local cache, the first object startup data is directly taken out from the cache to start the first object. However, considering that the original data stored in the data server may be updated, in this embodiment, in order to provide the first object user with the latest and most complete data, after the first object startup data is taken out from the cache to start the first object, a first object startup update data query request is also sent to the data server. If the data server confirms that there is the first object startup update data, the first object startup update data can be received from the data server and stored in the local cache, so that the latest first object startup data can be used to start the first object when the first object startup request is received next time.

[0134] In one embodiment of the present disclosure, the jump module 303 may be configured as follows:

[0135] In response to receiving the second object jump request, acquiring second object startup data;

[0136] The second object is started according to the second object start data.

[0137] In this embodiment, although the second object is jumped in response to the second object jump request, its startup mechanism is similar to the startup mechanism of the first object, that is, after receiving the second object jump request, it is necessary to first obtain the second object startup data, and then perform the startup operation on the second object according to the second object startup data.

[0138] In an embodiment of the present disclosure, the part of acquiring the second object startup data in response to receiving the second object jump request may be configured as follows:

[0139] In response to receiving the second object jump request, confirming whether the second object startup data is stored in the cache;

[0140] When it is confirmed that the second object startup data is stored in the cache, reading the second object startup data from the cache;

[0141] When it is confirmed that the second object startup data is not stored in the cache, a second object startup data acquisition request is sent to the data server to acquire the second object startup data.

[0142] Similar to the step of obtaining the first object startup data described above, in this embodiment, when the second object startup data needs to be obtained, first confirm whether the second object startup data for starting the second object is pre-stored in the local cache, if yes, directly fetch the second object startup data from the cache to start the second object, if no, send a second object startup data acquisition request to the data server to obtain the second object startup data from the data server to start the second object. By analogy, the jump of multiple objects can be realized.

[0143] As mentioned above, in order to ensure that the user of the first object can see the data of the first object before the jump when he wants to jump back to the first object from another object, so as to save the operation time of the user of the first object and avoid the situation where all the data of the first object need to be reloaded, in one embodiment of the present disclosure, before jumping to the second object, it is necessary to save the current running data of the first object, that is, the running data before jumping to the second object, wherein the current running data of the first object can enable the first object to quickly and completely restore to the running state before the running data of the first object was saved. In this embodiment, the device also includes:

[0144] The recovery module is configured to, in response to receiving a recovery request for the first object, recover the first object according to the running data before the first object jumps.

[0145] In one embodiment of the present disclosure, the first object recovery request refers to a request for restoring the operation of the first object, wherein, similar to the first object start request and the second object jump request, the first object recovery request can be issued by the user of the first object, such as a user, can be issued by other objects, or can be issued by a system or other management party. The present invention does not specifically limit the issuer of the first object recovery request.

[0146] In one embodiment of the present disclosure, the device further comprises:

[0147] The arrangement module is configured to arrange the objects according to the last operation time of the objects.

[0148] In order to determine the heat order of different objects so as to determine the order of object exit when the objects are exited later, in this embodiment, the objects are also arranged according to the last operation time of the objects, so that when a request to end the operation of the objects is received later, the operation of the objects can be terminated in sequence according to the last operation time of the objects, for example, the object whose last operation time is closest to the current time is terminated first, and so on. That is, in this embodiment, the device also includes:

[0149] The ending module is configured to, in response to receiving an object ending operation request, sequentially end the operation of corresponding objects according to the last operation time of the object to be ended specified in the object ending operation request.

[0150] In one embodiment of the present disclosure, the object end operation request refers to a request for ending the operation of the object, wherein the object may be one or more. Similar to the first object start request, the second object jump request and the first object recovery request, the object end operation request may be issued by the user of the object, such as a user, or may be issued by other objects, or may be issued by a system or other management party. The present invention does not specifically limit the issuer of the object end operation request. In one embodiment of the present disclosure, the object end operation request may be a first object recovery request, in which case it may be considered that all objects except the first object are designated to end operation, and the first object recovery request may also be a request carrying designated end operation object identification information, so as to perform an end operation operation on the corresponding object according to the designated end operation object identification information.

[0151] In one embodiment of the present disclosure, the device further comprises:

[0152] The management module is configured to perform preset management on the object, wherein the preset management includes one or more of the following managements: object page management, object resource management, object visual component management, object functional module component management and object message management.

[0153] In addition to the above-mentioned scheduling management of objects, the present disclosure can also manage the objects in various aspects, such as object page management, object resource management, object visual component management, object functional module component management, object message management, etc., wherein the object page management refers to the scheduling of the object display page and the management of the display page data; the object resource management refers to the management of the pictures, sounds and other resource data involved in the object; the object visual component management refers to the management of the components related to the object and vision; the object functional module component management refers to the management of the functional components related to the object; the object message management refers to the management of object-related messages, such as messages between components within the object and messages between objects. In this way, an object management framework can be formed to coordinate the management and scheduling of multiple objects generated based on the same generation tool to meet the management needs of the object users and eliminate the management obstacles of objects generated by different generation tools.

[0154] The present disclosure also discloses an electronic device, which includes a memory and a processor; wherein:

[0155] The memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement any of the above method steps.

[0156] Figure 4 It is a structural diagram of a computer system suitable for implementing an object management method according to an embodiment of the present disclosure.

[0157] like Figure 4 As shown, the computer system 400 includes a processing unit 401, which can perform various processes in the above-mentioned embodiments according to a program stored in a read-only memory (ROM) 402 or a program loaded from a storage part 408 into a random access memory (RAM) 403. In the RAM 403, various programs and data required for the operation of the system 400 are also stored. The processing unit 401, the ROM 402, and the RAM 403 are connected to each other via a bus 404. An input / output (I / O) interface 405 is also connected to the bus 404.

[0158] The following components are connected to the I / O interface 405: an input section 406 including a keyboard, a mouse, etc.; an output section 407 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage section 408 including a hard disk, etc.; and a communication section 409 including a network interface card such as a LAN card, a modem, etc. The communication section 409 performs communication processing via a network such as the Internet. The drive 410 is also connected to the I / O interface 405 as needed. Removable media 411, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., are installed on the drive 410 as needed, so that the computer program read therefrom is installed into the storage section 408 as needed. Among them, the processing unit 401 can be implemented as a processing unit such as a CPU, a GPU, a TPU, an FPGA, an NPU, etc.

[0159] In particular, according to an embodiment of the present disclosure, the method described above can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program tangibly contained on a readable medium thereof, and the computer program includes a program code for executing the object management method. In such an embodiment, the computer program can be downloaded and installed from a network through the communication part 409, and / or installed from a removable medium 411.

[0160] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the road map or block diagram can represent a part of a module, program segment or code, and the part of the module, program segment or code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a different order from the order marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0161] The units or modules involved in the embodiments described in the present disclosure may be implemented by software or hardware. The units or modules described may also be set in a processor, and the names of these units or modules do not constitute limitations on the units or modules themselves in some cases.

[0162] As another aspect, the embodiments of the present disclosure further provide a computer-readable storage medium, which may be a computer-readable storage medium included in the device described in the above-mentioned embodiment; or a computer-readable storage medium that exists independently and is not assembled into the device. The computer-readable storage medium stores one or more programs, and the programs are used by one or more processors to execute the methods described in the embodiments of the present disclosure.

[0163] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the embodiments of the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the inventive concept. For example, the above features are replaced with (but not limited to) technical features with similar functions disclosed in the embodiments of the present disclosure.

Claims

1. An object management method, including: In response to receiving a first object startup request, obtaining first object startup data; Starting the first object according to the first object startup data; In response to receiving a second object jump request, saving the running data of the first object before the jump, and jumping to the second object, where the second object jump request is used to indicate jumping to the second object, so that the second object starts to start during the running of other objects, and where the first object and the second object are generated based on the same generation tool; The obtaining of the first object startup data includes: In response to receiving a first object startup request, confirming whether the first object startup data is stored in the cache; when it is confirmed that the first object startup data is stored in the cache, reading the first object startup data from the cache; when it is confirmed that the first object startup data is not stored in the cache, sending a first object startup data acquisition request to the data server to obtain the first object startup data; The saving of the running data of the first object before the jump includes: confirming whether the second object startup data is stored in the cache; When it is confirmed that the second object startup data is stored in the cache, reading the second object startup data from the cache; when it is confirmed that the second object startup data is not stored in the cache, sending a second object startup data acquisition request to the data server to obtain the second object startup data.

2. The method according to claim 1, after reading the first object startup data from the cache when it is confirmed that the first object startup data is stored in the cache, further including: Sending a first object startup update data query request to the data server, and when the data server confirms the existence of first object startup update data, receiving the first object startup update data sent by the data server.

3. The method according to claim 2, in response to receiving a second object jump request, jumping to the second object, including: In response to receiving a second object jump request, obtaining second object startup data; Starting the second object according to the second object startup data.

4. The method according to any one of claims 1-3, further including: In response to receiving a first object resume request, resuming the running of the first object according to the running data of the first object before the jump.

5. The method according to any one of claims 1-3, further including: Arranging the objects according to the last operation time of the objects.

6. The method according to claim 5, further including: In response to receiving an object end running request, ending the running of the corresponding objects in sequence according to the last operation time of the object specified to end the running in the object end running request.

7. The method according to any one of claims 1-3, 6, further including: Performing preset management on the objects, where the preset management includes one or more of the following managements: object page management, object resource management, object visual component management, object function module component management, and object message management.

8. An object management device, including: An acquisition module, configured to acquire first object startup data in response to receiving a first object startup request; The acquiring the first object startup data includes: In response to receiving a first object startup request, confirming whether the first object startup data is stored in a cache; when it is confirmed that the first object startup data is stored in the cache, reading the first object startup data from the cache; when it is confirmed that the first object startup data is not stored in the cache, sending a first object startup data acquisition request to a data server to acquire the first object startup data; A startup module, configured to start a first object according to the first object startup data; A jump module, configured to, in response to receiving a second object jump request, save the running data of the first object before the jump, and jump to the second object, where the second object jump request is used to indicate a jump to the second object, so that the second object starts to start during the running of other objects, and the first object and the second object are generated based on the same generation tool; The saving the running data of the first object before the jump includes: confirming whether the second object startup data is stored in the cache; When it is confirmed that the second object startup data is stored in the cache, reading the second object startup data from the cache; when it is confirmed that the second object startup data is not stored in the cache, sending a second object startup data acquisition request to the data server to acquire the second object startup data.

9. The apparatus according to claim 8, after reading the first object startup data from the cache when it is confirmed that the first object startup data is stored in the cache, the acquisition module is further configured to: Send a first object startup update data query request to the data server, and when the data server confirms the existence of first object startup update data, receive the first object startup update data sent by the data server.

10. The apparatus according to claim 9, the jump module is configured to: In response to receiving a second object jump request, acquire second object startup data; Start the second object according to the second object startup data.

11. The apparatus according to claim 8, further comprises: A recovery module, configured to, in response to receiving a first object recovery request, resume running the first object according to the running data of the first object before the jump.

12. The apparatus according to any one of claims 8-11, further comprises: An arrangement module, configured to arrange the objects according to the last operation time of the objects.

13. The apparatus according to claim 12, further comprises: An end module, configured to, in response to receiving an object end operation request, end the running of the corresponding objects in sequence according to the last operation time of the object specified to end the running in the object end operation request.

14. The apparatus according to any one of claims 8-11, 13, further comprises: A management module, configured to perform preset management on the object, where the preset management includes one or more of the following managements: object page management, object resource management, object visual component management, object function module component management, and object message management.

15. An electronic device, characterized in that, it includes a memory and a processor; wherein, the memory is used to store one or more computer instructions, and the one or more computer instructions are executed by the processor to implement the method steps described in any one of claims 1-7.

16. A computer-readable storage medium, on which computer instructions are stored, characterized in that, when the computer instructions are executed by a processor, the method steps described in any one of claims 1-7 are implemented.

Images