Method and system for implementing desktop services

Abstract

The embodiment of the application discloses a kind of implementation method and system of desktop service.The main technical scheme includes: in the process of operating system starting, starting desktop launcher;By the desktop launcher, the application program containing preset desktop service is started and the background service corresponding to the application program containing preset desktop service is kept alive;Wherein, the application program containing preset desktop service is non-rom built-in program.In the application, the application program of preset desktop service is decoupled from desktop launcher, and the application program of preset desktop service is as ordinary system-level application program, so that the application program of preset desktop service does not need to flush the ROM of operating system when updating, to realize more easily and efficiently.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer application, in particular to a desktop service implementation method and system. BACKGROUND

[0002] The continuous development of computer technology has led to the production of more and more intelligent devices, in addition to common computers and mobile phones, there are many medical instruments, geological equipment, household equipment, robots with specific functions, etc. Many of these intelligent devices have screens that can display running information, status information, etc. to users. However, with the diversification of intelligent device application scenarios, different intelligent devices have different service logic that needs to be started with the operating system and always run in the background, such as power display, volume control, audio and video call service logic in the inspection robot, which needs to be started with the operating system and always run in the background. The current method is to integrate these service logics in the desktop launcher, as shown in Figure 1 , but this will cause the code compilation of the service logic to be time-consuming, and the update of the service logic will cause the ROM (Read-Only Memory) of the operating system to be frequently updated, which is very inconvenient and time-consuming, thus causing service pain points. SUMMARY

[0003] Therefore, the present application provides a desktop service implementation method and system to solve the above-mentioned service pain points.

[0004] The present application provides the following solutions:

[0005] In a first aspect, a desktop service implementation method is provided, which comprises:

[0006] starting a desktop launcher during the startup of an operating system;

[0007] starting an application containing preset desktop services by the desktop launcher and keeping the application containing preset desktop services alive;

[0008] The application containing preset desktop services is a non-Read-Only Memory (ROM) built-in program.

[0009] According to an implementable manner in the embodiments of the present application, before starting the application containing preset desktop services, it further comprises:

[0010] The desktop launcher judges whether the application containing preset desktop services has been installed;

[0011] If installed, the starting the application containing preset desktop service is performed; otherwise, the user is prompted to install the application containing preset desktop service, and the starting the application containing preset desktop service is performed after the application containing preset desktop service is installed.

[0012] According to an implementable manner in the embodiments of the present application, the keeping alive of the application containing preset desktop service comprises:

[0013] The desktop launcher listens to the survival state of the application containing preset desktop service.

[0014] If the application containing preset desktop service is found to be deactivated, the application containing preset desktop service is restarted.

[0015] According to an implementable manner in the embodiments of the present application, the method further comprises:

[0016] When the application containing preset desktop service is started, a daemon process is started.

[0017] The daemon process listens to the running state of the background service corresponding to the application containing preset desktop service.

[0018] If the running state of the background service corresponding to the application containing preset desktop service is found to be abnormal, the background service corresponding to the application containing preset desktop service is restarted.

[0019] According to an implementable manner in the embodiments of the present application, the method further comprises:

[0020] When the application containing preset desktop service is started, the background service corresponding to the application containing preset desktop service and a data channel for loading preset desktop service data are started, and the operating system desktop, status bar and navigation bar are loaded.

[0021] According to an implementable manner in the embodiments of the present application, the method further comprises:

[0022] An installation package of the updated application containing preset desktop service is obtained.

[0023] The installation package is used to install the updated application containing preset desktop service.

[0024] According to an implementable manner in the embodiments of the present application, the method is applied to a patrol robot, and the preset desktop service comprises at least one of the following:

[0025] The volume of the patrol robot is displayed.

[0026] The power of the patrol robot is displayed.

[0027] Sensor data upload;

[0028] Establishing an audio call;

[0029] Establishing a video call;

[0030] Voice announcement;

[0031] Video playing;

[0032] Over-the-air technology (OTA) function.

[0033] In a second aspect, an implementation system of a desktop service is provided, and the system comprises a system service module, a desktop launcher and an application program containing preset desktop services;

[0034] The system service module is configured to start the desktop launcher in the process of starting an operating system;

[0035] The desktop launcher is configured to start the application program containing preset desktop services and keep the application program containing preset desktop services alive;

[0036] The application program containing preset desktop services is a non- ROM built-in program.

[0037] According to a third aspect, a computer readable storage medium is provided, and the medium stores a computer program, and the program is executed by a processor to implement the steps of the method according to any one of the first aspect.

[0038] According to a fourth aspect, an electronic device is provided, and the device comprises:

[0039] One or more processors; and

[0040] A memory associated with the one or more processors, the memory being configured to store program instructions, and the program instructions being configured to be executed by the one or more processors to implement the steps of the method according to any one of the first aspect.

[0041] According to the embodiments provided in the present application, the present application can have the following technical effects:

[0042] 1) In the present application, the application program containing preset desktop services is decoupled from the desktop launcher, and the application program containing preset desktop services is a non- ROM built-in program, so that the application program containing preset desktop services does not need to refresh the ROM of the operating system when being updated, and the updating is easier and more efficient.

[0043] 2) The desktop launcher listens to the survival state of the application containing the preset desktop service after starting the application containing the preset desktop service, and restarts the application containing the preset desktop service when it is found that the application containing the preset desktop service is deactivated, so as to realize the keep-alive of the application containing the preset desktop service and ensure the long-term effectiveness of the desktop service.

[0044] 3) The keep-alive mechanism is realized by starting a daemon process to listen to the running state of the background service corresponding to the application containing the preset desktop service, and restarting the background service corresponding to the application containing the preset desktop service when it is found that the running state of the background service corresponding to the application containing the preset desktop service is abnormal, so as to realize the keep-alive of the background service corresponding to the application containing the preset desktop service. The keep-alive mechanism is simple and can further ensure the long-term effectiveness of the desktop service.

[0045] 4) The application containing the preset desktop service is a non- ROM built-in program, so the compilation is faster. It can also be personalized according to the needs, without being limited and affected by the original desktop of the operating system.

[0046] Of course, implementing any product of the present application does not necessarily require all the advantages described above. BRIEF DESCRIPTION OF DRAWINGS

[0047] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed in the embodiments will be briefly introduced as follows. Obviously, the drawings in the following description only constitute some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor on the basis of these drawings.

[0048] Figure 1 is a schematic diagram of the main implementation architecture for realizing the desktop service in the prior art;

[0049] Figure 2 is a schematic diagram of the main implementation architecture for realizing the desktop service provided by the embodiments of the present application;

[0050] Figure 3 is a flowchart of the implementation method of the desktop service provided by the embodiments of the present application;

[0051] Figure 4 is a flowchart of a method for starting the desktop service provided by the embodiments of the present application;

[0052] Figure 5 is a flowchart of a method for keeping the Laucher APP alive provided by the embodiments of the present application;

[0053] Figure 6A schematic diagram of an implementation system of a desktop service provided by an embodiment of the present application is shown in FIG. 1.

[0054] Figure 7 An architecture diagram of an electronic device provided by an embodiment of the present application is shown in FIG. 2. DETAILED DESCRIPTION

[0055] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art belong to the scope of protection of the present application.

[0056] The terms used in the embodiments of the present application are merely for the purpose of describing the specific embodiments, and are not intended to limit the present application. The singular forms "a", "an" and "the" used in the embodiments of the present application and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise.

[0057] It should be understood that the term "and / or" used herein is merely to describe the association relationship of the associated objects, and means that there can be three relationships, for example, A and / or B can mean that A exists alone, A and B exist together, and B exists alone. In addition, the character " / " herein generally represents an "or" relationship between the front and rear associated objects.

[0058] Depending on the context, the word "if" as used herein can be interpreted as "when" or "upon" or "in response to determining" or "in response to detecting". Similarly, depending on the context, the phrase "if determined" or "if detecting (a stated condition or event)" can be interpreted as "when determined" or "in response to determining" or "when detecting (a stated condition or event)" or "in response to detecting (a stated condition or event)".

[0059] Figure 2 A main implementation architecture schematic diagram of implementing a desktop service in an embodiment of the present application is shown in FIG. 1. As shown in FIG. 1, in the architecture, an APP (Application) containing a preset desktop service is decoupled from a desktop launcher, and no longer integrated in the desktop launcher but exists as a non- ROM built-in APP, that is, as a common system-level APP. Figure 2

[0060] ​The desktop launcher is still a ROM built-in APP and is integrated in the operating system ROM and is an APP started with the operating system. In the embodiment of the application, the preset desktop service logic is decoupled from the desktop launcher, and the desktop launcher is responsible for starting and keeping alive the APP of the preset desktop service. Since the desktop service logic is no longer included, the desktop launcher logic is simple and does not need to be frequently updated, and can even be unchanged once the function is implemented.

[0061] It should be noted that the ROM built-in APP in the embodiment of the application refers to an APP integrated in the operating system ROM and cannot be installed and uninstalled by the user. The non- ROM built-in APP refers to an APP not integrated in the operating system ROM and installed in other storage spaces of the operating system ROM and can be installed and uninstalled by the user.

[0062] Figure 3 The implementation method of the desktop service provided in the embodiment of the application is based on Figure 2 The system architecture is shown in FIG. 1, and the method mainly includes the following steps, as shown in FIG. 2. Figure 3

[0063] Step 302: In the process of starting the operating system, the desktop launcher is started.

[0064] Taking the Android operating system as an example, in the process of starting the operating system, the SystemServer component starts the Launcher launcher through the ActivityManagerService.

[0065] The desktop launcher is a ROM built-in APP and is integrated in the operating system ROM and is started with the operating system. Since the desktop service logic is decoupled from the desktop launcher, the logic of the desktop launcher is simpler and will not cause frequent refreshing of the operating system ROM.

[0066] Step 304: The desktop launcher starts the APP containing the preset desktop service and keeps alive the APP containing the preset desktop service, wherein the APP containing the preset desktop service is a non- ROM built-in APP.

[0067] As can be seen from the above process, the APP of the preset desktop service is decoupled from the desktop launcher in the application, and the APP of the preset desktop service is a non- ROM built-in APP, so that the APP of the preset desktop service does not need to refresh the ROM of the operating system when it is updated, and the updating is more easy and efficient.

[0068] ​In the embodiment of the present application, the desktop launcher is responsible for starting and keeping alive the APP of the preset desktop service when the desktop launcher is started. The step 304 is described in detail below in combination with the embodiment.

[0069] In the embodiment of the present application, the preset desktop service refers to the service that needs to be started with the desktop and resident in the desktop, including the service for implementing the desktop UI, the service for reflecting the device state information such as the device power and volume, and the personalized service such as the audio and video communication service in the inspection robot. The code of these desktop services can be contained in a non- ROM built-in APP, which is called Laucher APP in the subsequent embodiment. The Laucher APP is a non- ROM built-in APP and can be installed or uninstalled by the user. The developer can contain the service logic that needs to be started with the desktop and resident in the desktop in the Laucher APP, which can be customized by the developer according to the device requirements and updated later.

[0070] In addition, the desktop service usually involves the calling of some system-level interfaces, so the APP containing the preset desktop service has certain system permissions and can call the system-level interfaces, such as the interface for obtaining the system time and the interface for connecting the remote host.

[0071] Figure 4 A flowchart of a method for starting the desktop service provided in the embodiment of the present application is shown in FIG. 4, which can include the following steps: Figure 4

[0072] Step 402: After the desktop launcher is started and initialized, it is determined whether the Laucher APP is installed. If yes, step 404 is performed; otherwise, step 408 is performed.

[0073] Taking the Android operating system as an example, the desktop launcher can use the PackageManager (package manager) to try to obtain the PackageInfo (package information) through the package name of the Laucher APP. If the obtained PackageInfo is not empty, it indicates that the Laucher APP is installed. If the obtained PackageInfo is empty, it indicates that the Laucher APP is not installed.

[0074] Step 404: Start the Laucher APP.

[0075] ​If the Laucher APP has been installed, the desktop launcher directly starts the Laucher APP. For example, in Android, the launcher can call the startActivity() function to inform the SystemServer component to create a process of the Laucher APP.

[0076] Step 406: The survival state of the Laucher APP is listened to. If the Laucher APP is alive, the listening continues; if the Laucher APP is not alive, the process returns to step 404 to restart the Laucher APP.

[0077] Taking Android as an example, the life cycle state of each APP is maintained by the ActivityManagerService process, and each APP corresponds to an activity. The desktop launcher can obtain the activities running in the system through the ActivityManagerService, thereby being able to timely know whether the Laucher APP is alive.

[0078] Step 408: The user is prompted to install the Laucher APP.

[0079] If the Laucher APP has not been installed, the system setting interface can be opened, and the user can install the Laucher APP through the component provided on the system setting interface.

[0080] Step 410: The installation state of the Laucher APP is listened to, and the process returns to step 402. That is, the Laucher APP is started after the Laucher APP is installed.

[0081] After the user is prompted to install the Laucher APP, the desktop launcher listens to the installation state of the Laucher APP, starts the Laucher APP after the Laucher APP is installed, and keeps the background service corresponding to the Laucher APP alive.

[0082] Since the Laucher APP is a non- ROM built-in APP, taking Android as an example, the Laucher APP is usually installed in the " / data / app / " directory.

[0083] The Laucher APP is separated from the desktop launcher. As a non- ROM built-in APP, the background service of the Laucher APP can be ended due to the operating system memory recycling mechanism, the cleaning of third-party software, the management system of background programs of various manufacturers, and the like, which will affect the normal service of the desktop service and can cause the desktop to be abnormal. In view of this, Figure 5The method flowchart for keeping the Laucher APP alive provided in the embodiments of the present application is shown in FIG. 5, which can include the following steps: Figure 5

[0084] Step 502: After the Laucher APP is started, a daemon process is started, and then steps 504 and 508 are executed.

[0085] Step 504: The daemon process listens to the running state of the background service corresponding to the Laucher APP.

[0086] After the Laucher APP is started, the launcher starts an independent process to listen to and restart the running state of the background service corresponding to the Laucher APP. This process is referred to as a daemon process in the embodiments of the present application.

[0087] When the daemon process listens to the running state of the background service corresponding to the Laucher APP, the Service component binding capability is used. The principle of the daemon process keep-alive mechanism is to bind two Services to each other, i.e., to bind the daemon process and the background service corresponding to the Laucher APP to each other, and to listen to each other. Once the binding relationship between the two is disconnected, for example, the background service corresponding to the Laucher APP crashes or is killed by the operating system, the Service of the daemon process will trigger the onServiceDisconnected callback, and in this callback, the other Service (i.e., the background service corresponding to the Laucher APP) will be restarted and bound again, thereby playing a keep-alive role.

[0088] Step 506: It is determined whether the background service corresponding to the Laucher APP is running abnormally. If yes, the background service of the Laucher APP is restarted, i.e., step 510 is performed; otherwise, step 504 is continued to listen to the running state of the background service corresponding to the Laucher APP.

[0089] Step 508: A data channel for loading the data required by the Laucher APP is started, i.e., the data channel is initialized, and then the service data is loaded.

[0090] In some desktop services, service data needs to be obtained from outside the device, for example, sensor data, media stream data, etc., and therefore a data channel needs to be established between the operating system and the data acquisition device to facilitate the use of the service data for desktop display.

[0091] Step 510: The background service of the Laucher APP is started, and the initialization of the background service corresponding to the Laucher APP is performed.​

[0092] Step 512: loading the desktop.

[0093] Loading the desktop mainly initializes the UI-related content, such as the icons, layout, main menu, widgets, and other content of the application, and provides an entry for the application.

[0094] Step 514: loading the system status bar.

[0095] The system status bar is loaded on the desktop, and the status bar is usually located at the top of the screen to display information related to the device status, such as device power, device volume, network speed, etc.

[0096] Step 516: loading the system navigation bar.

[0097] The navigation bar is a basic control on the desktop to help users return to the previous operation, return to the desktop, and other operations. The processes of loading the desktop, loading the system status bar, and loading the system navigation bar are existing technologies, and are not described in detail here.

[0098] The above step 508 is actually the entire process of starting the desktop service, including initializing the background service corresponding to the Laucher APP and the data channel for loading the preset desktop service data, loading the operating system desktop, status bar, and navigation bar, etc. According to the actual operating system and the content of the Laucher APP, the above process of starting the Laucher APP may have some differences. In addition, when restarting the Laucher APP, the established data channel is usually not affected, so the reinitialization of the data channel can be omitted.

[0099] As can be seen from the above process, after starting the Laucher APP, the desktop launcher starts the daemon process to listen to the running state of the background service corresponding to the Laucher APP, and when the running state of the background service of the Laucher APP is abnormal, the Laucher APP is restarted to realize the keep-alive of the Laucher APP. The keep-alive mechanism is simple to implement and can effectively ensure the long-term effectiveness of the desktop service.

[0100] At this point, the desktop service is started.

[0101] The Laucher APP is a non- ROM built-in APP, so the compilation is faster. The Laucher APP may need to be updated frequently, but the update of the Laucher APP does not require the flashing of the operating system ROM, and only needs to reinstall the updated installation package.

[0102] When the Laucher APP needs to be updated, the updated installation package of the Laucher APP can be imported manually, or the server side can actively push the updated installation package of the Laucher APP, or the server side can be requested to obtain the updated installation package of the Laucher APP after obtaining the message that the Laucher APP exists update. After obtaining the updated installation package of the Laucher APP, the updated Laucher APP can be directly installed by using the installation package. The desktop launcher starts the Laucher APP after listening to the installation of the Laucher APP, and performs keep-alive processing on the Laucher APP.

[0103] The Laucher APP is a non- ROM built-in APP, which can be conveniently personalized according to requirements, and is not limited and affected by the original desktop of the operating system.

[0104] An example is as follows:

[0105] Inspection work plays a very important role in production and life, and its purpose is to discover various hidden troubles and feedback in time. Based on this demand, a fixed-point inspection robot can be set in the inspection area to perform inspection according to a fixed route and feedback in time after discovering abnormalities. The inspection robot is a device that realizes the inspection task through navigation positioning, path planning, image analysis, and environment perception, and does not need manual intervention, and can provide discrimination and automatic alarm for abnormal objects, thereby realizing automatic management.

[0106] The inspection robot usually has a screen and realizes the desktop service based on Android. The display of various running state data of the inspection robot and specific UI interaction functions need to be displayed on the starting desktop. For example, the power, running state, and volume of the inspection robot need to be displayed on the system status bar. For another example, the sensor data upload, audio call establishment, video call establishment, voice broadcast, video playback, and OTA (over-the-air technology) function of the inspection robot need to be realized as a desktop service. This means that the desktop service needs to be customized, and the desktop service needs to include more service logic. If the traditional desktop service implementation method is used, the desktop service logic is integrated in the Laucher launcher, and then the update of any service logic will cause the ROM of Android to be refreshed, which is obviously very inconvenient and time-consuming.

[0107] In the method provided in the application, the service logic of the desktop is separated from the Launcher launcher, and the Launcher APP containing the desktop service logic is taken as a non- ROM built-in APP. The Launcher launcher is only responsible for starting the Launcher APP and keeping the Launcher APP alive. When the inspection robot is started, the Launcher launcher is started by the SystemServer component through the ActivityManagerService in the process of starting the Android operating system. The Launcher launcher judges whether the Launcher APP has been installed. If not, the system setting interface is displayed, and the user can install the Launcher APP through the component provided by the system setting interface. If the Launcher APP has been installed, the Launcher APP is started. In addition, the Launcher launcher listens to the survival state of the Launcher APP after starting the Launcher APP. Once it is found that the Launcher APP is inactivated, the Launcher APP is restarted.

[0108] After starting the Launcher APP, the daemon process is started to keep the background service of the Launcher APP alive. That is, the daemon process listens to the running state of the background service corresponding to the Launcher APP. Once it is found that the background service corresponding to the Launcher APP runs abnormally, the background service of the Launcher APP is restarted. In addition, after starting the Launcher APP, the data channel, the background service corresponding to the Launcher APP is initialized, and the desktop, the system status bar, the system navigation bar and the like are loaded to complete the start of the desktop service.

[0109] Since the Launcher APP is a non- ROM built-in APP, any service logic update in the Launcher APP will not cause the refresh of the Android operating system ROM. Only the installation package of the updated Launcher APP needs to be installed, which is obviously more convenient and efficient.

[0110] It should be noted that the above embodiments of the application are described by taking the Android operating system as an example. However, other types of operating systems are also applicable within the above spirit and principles of the embodiments of the application, but there may be differences in the names of components, processes and functions.

[0111] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0112] According to another embodiment, a system for implementing desktop services is provided. Figure 6 A schematic block diagram of an implementation system for a desktop service according to one embodiment is shown. Figure 6 As shown, the system 600 includes: a system service module 601, a desktop launcher 602, and an application 603 containing preset desktop services.

[0113] System service module 601 is configured to start desktop launcher 602 during the operating system startup process.

[0114] Desktop launcher 602 is configured to launch application 603 containing preset desktop services and keep application 603 containing preset desktop services active.

[0115] Among them, application 603, which includes preset desktop services, is a non-ROM built-in program.

[0116] As one possible implementation, the desktop launcher 602 is further configured to determine whether an application containing a preset desktop service has been installed; if it has been installed, to launch the application containing the preset desktop service; otherwise, to prompt the user to install the application containing the preset desktop service, and to launch the application containing the preset desktop service after the application containing the preset desktop service has been installed.

[0117] As one possible implementation, the desktop launcher 602 is specifically configured to: monitor the liveness status of an application containing a preset desktop service; if the application containing the preset desktop service is detected to be inactive, then restart the application containing the preset desktop service.

[0118] As one possible implementation method, the application 603 containing the preset desktop service is specifically configured to: start a daemon process upon startup; have the daemon process monitor the running status of the background service corresponding to the application containing the preset desktop service; and if the running status of the background service corresponding to the application containing the preset desktop service is detected to be abnormal, restart the background service corresponding to the application containing the preset desktop service.

[0119] As one of the implementable manners, the application program 603 containing the preset desktop service is configured to start the background service corresponding to the application program containing the preset desktop service and the data channel for loading the preset desktop service data when starting, load the operating system desktop, the status bar and the navigation bar.

[0120] Based on the above system, after obtaining the installation package of the updated application program containing the preset desktop service, only the installation of the updated application program containing the preset desktop service is needed, and the refreshing of the operating system ROM is not needed.

[0121] It should be noted that the present application embodiments can involve the use of user data. In actual application, user-specific personal data can be used in the schemes described herein in the range allowed by applicable laws and regulations, for example, with the explicit consent of the user, the actual notification to the user, etc.

[0122] In addition, the present application embodiment further provides a computer readable storage medium, which stores a computer program, and the program is executed by a processor to implement the steps of the method in any one of the preceding method embodiments.

[0123] And an electronic device, comprising:

[0124] one or more processors; and

[0125] a memory associated with the one or more processors, the memory configured to store program instructions that, when executed by the one or more processors, perform the steps of the method in any one of the preceding method embodiments.

[0126] wherein, Figure 7 An exemplary architecture of an electronic device is shown, which can specifically include a processor 710, a video display adapter 711, a disk drive 712, an input / output interface 713, a network interface 714, and a memory 720. The processor 710, the video display adapter 711, the disk drive 712, the input / output interface 713, the network interface 714, and the memory 720 can be communicatively connected through a communication bus 730.

[0127] The processor 710 can be implemented in the form of a general-purpose CPU, a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, etc., for executing related programs to implement the technical solutions provided by the present application.

[0128] The memory 720 can be implemented in the form of a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, etc. The memory 720 can store an operating system 721 for controlling the operation of the electronic device 700, a basic input / output system (BIOS) 722 for controlling the low-level operation of the electronic device 700. In addition, a web browser 723, a data storage management system 724, and an implementation system 725 of a desktop service, etc. can also be stored. The implementation system 725 of the desktop service described above can be an application program that specifically implements the operations of the steps described above in the embodiments of the present application. In summary, when the technical solutions provided in the present application are implemented by software or firmware, the relevant program codes are stored in the memory 720 and are executed by the processor 710.

[0129] The input / output interface 713 is configured to connect an input / output module to realize information input and output. The input / output module can be configured as a component in the device (not shown in the figure) or can be externally connected to the device to provide corresponding functions. The input device can include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device can include a display, a speaker, a vibrator, an indicator light, etc.

[0130] The network interface 714 is configured to connect a communication module (not shown in the figure) to realize the communication interaction between the device and other devices. The communication module can realize communication through a wired manner (such as USB, network cable, etc.) or through a wireless manner (such as mobile network, WIFI, Bluetooth, etc.).

[0131] The bus 730 includes a path for transmitting information between various components (such as the processor 710, the video display adapter 711, the disk drive 712, the input / output interface 713, the network interface 714, and the memory 720) of the device.

[0132] It should be noted that although the above device only shows the processor 710, the video display adapter 711, the disk drive 712, the input / output interface 713, the network interface 714, the memory 720, the bus 730, etc., in the specific implementation process, the device can also include other components necessary for normal operation. In addition, those skilled in the art can understand that the above device can also only contain the components necessary to implement the solutions of the present application, and does not necessarily contain all the components shown in the figure.

[0133] Those skilled in the art can clearly understand the application by the description of the above embodiments that the application can be implemented by means of software and the necessary universal hardware platforms. Based on such an understanding, the technical solutions of the application can be embodied in the form of a software product, and the computer software product can be stored in a storage medium, such as a ROM / RAM, a magnetic disk, an optical disk, and the like, and includes a number of instructions to make a computer device (which can be a personal computer, a server, or a network device, and the like) execute the methods described in various embodiments or some parts of the embodiments.

[0134] Each of the embodiments in the specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other. Each of the embodiments focuses on the difference from other embodiments. In particular, for the system or the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the related parts can be referred to the part of the method embodiment. The above-described system and system embodiment are merely illustrative, and the units described as separate components can be or can not be physically separated, and the components displayed as units can be or can not be physical units, that is, they can be located in one place, or can be distributed on multiple network units. According to the actual needs, some or all of the modules can be selected to achieve the purpose of the embodiment. Those skilled in the art can understand and implement without creative labor.

[0135] The above describes the technical solutions provided by the application in detail, and the principle and implementation manner of the application are described by applying specific examples. The above embodiment is only used to help understand the method of the application and its core idea; meanwhile, for those skilled in the art, according to the idea of the application, the specific implementation manner and application range can be changed. In conclusion, the content of the specification should not be understood as a limitation of the application.

Claims

1. A method of implementing a desktop service, characterized by, The method comprises: starting a desktop launcher during the process of starting an operating system; starting an application containing preset desktop services by the desktop launcher and keeping the application containing preset desktop services alive; wherein the application containing preset desktop services is a non-Read-Only Memory (ROM) built-in program.

2. The method of claim 1, wherein, Before starting the application containing preset desktop services, the method further comprises: the desktop launcher judging whether the application containing preset desktop services has been installed; if yes, executing the starting of the application containing preset desktop services; otherwise, prompting a user to install the application containing preset desktop services and executing the starting of the application containing preset desktop services after the application containing preset desktop services is installed.

3. The method of claim 1, wherein, keeping the application containing preset desktop services alive comprises: the desktop launcher listening to the alive state of the application containing preset desktop services; if the application containing preset desktop services is found to be inactivated, restarting the application containing preset desktop services.

4. The method of claim 1, wherein, The method further comprises: starting a daemon when the application containing preset desktop services is started; the daemon listening to the running state of a background service corresponding to the application containing preset desktop services; if the running state of the background service corresponding to the application containing preset desktop services is found to be abnormal, restarting the background service corresponding to the application containing preset desktop services.

5. The method according to claim 1 or 4, characterized in that, The method further comprises: starting the background service corresponding to the application containing preset desktop services and a data channel for loading preset desktop service data when the application containing preset desktop services is started, and loading an operating system desktop, a status bar and a navigation bar.

6. The method of claim 1, wherein, The method further comprises: obtaining an installation package of the updated application containing preset desktop services; installing the updated application containing preset desktop services by using the installation package.

7. The method of claim 1, 2, 4, or 6, wherein, The method is applied to a patrol robot, and the preset desktop services comprise at least one of the following: displaying the volume of the patrol robot; displaying the power of the patrol robot; uploading sensor data; establishing an audio call; establishing a video call; voice broadcasting; video playing; Over-the-Air (OTA) technology.

8. A system for implementing a desktop service, characterized by The system comprises a system service module, a desktop launcher and an application containing preset desktop services. The system service module is configured to start the desktop launcher during the process of starting an operating system. The desktop launcher is configured to start the application containing preset desktop services and keep the application containing preset desktop services alive. The application containing preset desktop services is a non-Read-Only Memory (ROM) built-in program.

9. A computer readable storage medium having stored thereon a computer program, characterized in that, The program is executed by a processor to implement the steps of the method in any one of claims 1 to 7.

10. An electronic device, comprising: comprise: one or more processors; and a memory associated with the one or more processors, the memory being configured to store program instructions, the program instructions being configured to be executed by the one or more processors to implement the steps of the method in any one of claims 1 to 7.

Images