WO2024017351A1

WO2024017351A1 - Method and apparatus for calling system service

Info

Publication number: WO2024017351A1
Application number: PCT/CN2023/108459
Authority: WO
Inventors: 陈康; 贾灿; 李加润
Original assignee: 华为技术有限公司
Priority date: 2022-07-22
Filing date: 2023-07-20
Publication date: 2024-01-25
Also published as: CN117472606A

Abstract

Provided in the embodiments of the present application are a method and apparatus for calling a system service. The method comprises: a first device sending first notification information to a second device, wherein the first notification information comprises information of a target service, that is, information of a system service needing to be called by the first device, and the first notification information is used for instructing the second device to load the target service; and after loading the target service, the second device sending first response information to the first device, wherein the first response information comprises a service handle of the target service, and the service handle is used for the first device to call the target service on the second device. By means of the method provided in the embodiments of the present application, a called device does not need to load a target service during startup, but loads the target service as required, such that the occupation of startup resources can be reduced, and the consumption of system resources is avoided.

Description

Methods and devices for calling system services

This application claims the priority of the Chinese patent application submitted to the State Intellectual Property Office of China with application number 202210871045.0 on July 22, 2022, and the priority of the Chinese patent application titled "Method and Device for Calling System Services", which The entire contents are incorporated herein by reference.

Technical field

The embodiments of the present application relate to the field of computer technology, and specifically, to a method and device for calling system services.

Background technique

A distributed system service is a system composed of multiple processors interconnected through communication lines. Normally, distributed system services only start to work in a cross-device scenario. In a single-machine scenario, distributed system services have no practical application, but occupy boot resources, resulting in unnecessary consumption of system resources to a certain extent. Therefore, it is necessary to provide a method and device for calling distributed system services to reduce the consumption of system resources.

Contents of the invention

Embodiments of the present application provide a method and device for calling system services, which can load or unload distributed system services on demand and reduce the consumption of system resources.

In a first aspect, a method for calling a system service is provided. The method includes: a first device sending first notification information to a second device. The first notification information includes information about a target service, and the information about the target service is the third device. Information about the system service that a device needs to call, the first notification information is used to instruct the second device to load the target service; the first device receives the first response information from the second device, the first response information includes the target service A service handle of the service, which is used by the first device to call the target service on the second device.

In a possible implementation manner, the first response information received by the first device includes a service handle of the target service. In this solution, the loading result of the target service by the second device is successful, and the second device can send the service handle to the first device to facilitate the first device to call the target service on the second device.

In another possible implementation, the first device receives first response information from the second device, where the first response information is used to indicate that the target service failed to load on the second device. In this solution, the second device sends the result of the loading failure to the first device, and the first device determines whether the target service still needs to be called on the second device based on actual needs. If it still needs to be called, it continues to call the target service. The second device sends notification information to instruct the second device to reload the target service.

In the embodiments provided by this application, in a networking scenario, or when a target service needs to be loaded across devices, the first device can send notification information to the second device. After receiving the notification information from the first device, the second device Load the target service that the first device needs to call. The first device is the calling device, and the second device is the called device. Based on this solution, the called device, that is, the second device, does not need to load the target service when it is powered on, but loads the target service according to usage requirements, thereby avoiding resource occupation problems in unnecessary scenarios and reducing the consumption of system resources.

With reference to the first aspect, in some implementations of the first aspect, before the first device sends the first notification information to the second device, the method further includes: the first device determines the target device and the target service, the The target device is a device that needs to load the target service, wherein the second device is the target device.

In the embodiments provided by this application, the first device can determine the system service that needs to be called and the device that needs to call the system service based on actual needs, and then provide the determined device, which is the target device, or the second device. Send notification information to instruct the second device to load the target service. Based on this solution, the called device does not need to load the target service when it is powered on, but loads the target service according to usage requirements, thereby avoiding resource occupation problems in unnecessary scenarios and reducing the consumption of system resources.

With reference to the first aspect, in some implementations of the first aspect, the first device determines the target device and the target service, including: the first device determines the target device and the target service according to task flow requirements.

In one possible scenario, the target service serves a distributed scheduling system, and the first device can determine the target service and target device that need to be called based on task flow requirements. The task flow requirement can be that the target service is loaded on the current device or the first device and needs to be transferred to other devices such as the second device for loading; or it can also be that the application corresponding to the target service is loaded on the current device. The use on the previous device or the first device needs to be transferred to other devices such as the second device for use. This transfer may also be called switching or the like. Based on this solution, the first device can instruct the second device to load the target service according to the usage scenario or actual usage requirements. The second device does not need to load the target service when it is turned on, but loads the target service according to the usage requirements, thereby avoiding unnecessary errors. Solve the problem of resource occupation in necessary scenarios and reduce the consumption of system resources.

In another possible scenario, for example, when the target service is a distributed hardware service, the first device may determine the target service and the target device based on hardware coordination requirements. For example, the hardware collaboration requirement can be a split-screen display of the upper-layer application corresponding to the target service. That is to say, the first device calls the second device so that the application interface corresponding to the target service can be partially displayed on the first device. , and the other part is displayed on the target device.

With reference to the first aspect, in some implementations of the first aspect, the method further includes: the first device sending second notification information to the second device, the second notification information being used to instruct the first device to The call to the target service ends.

In the embodiment provided by this application, after the first device determines that there is no application or service on the device that needs to continue to call the target service on the second device, it can send notification information to the second device to instruct the first device to call the target service. The call of the service has ended. Furthermore, the second device can determine whether it is necessary to uninstall the target service according to the actual call situation, so as to reduce the occupation of system resources.

With reference to the first aspect, in some implementations of the first aspect, before the first device sends the second notification information to the second device, the method further includes: the first device determines that the transfer of the target service ends.

In a possible scenario, the target service serves a distributed scheduling system, and the first device determines whether the transfer of the target service has ended. When it is determined that the transfer of the target service has ended, it sends the second notification information to the second device. , indicating that the call to the target service has ended, so that the second device can uninstall the target service and reduce unnecessary occupation of system resources.

The transfer of the target service ends, or the transfer of the upper-layer application corresponding to the target service ends.

In another possible scenario, the target service is a distributed hardware service. The first device determines that the hardware collaboration task is completed, and then sends the second notification information to the second device to indicate that the call to the target service is completed. .

In the embodiment provided by this application, the first device determines that the call to the target service has ended based on actual needs, and notifies the second device so that the second device determines whether the target service needs to be uninstalled to reduce unnecessary occupation of system resources.

In a second aspect, a method for calling system services is provided. The method includes: a second device receiving first notification information from a first device, where the first notification information includes information about a target service, and the information about the target service is: Information about the system service that the first device needs to call, the first notification information is used to instruct the second device to load the target service; the second device loads the target service; the second device sends a first response to the first device information, the first response information includes a service handle of the target service, and the service handle is used by the first device to call the target service on the second device.

In the embodiments provided by this application, in a networking scenario, or when a target service needs to be loaded across devices, the first device can send notification information to the second device. After receiving the notification information from the first device, the second device Load the target service that the first device needs to call. The first device is the calling device, and the second device is the called device. Based on this solution, the second device does not need to load the target service when it is powered on, but loads the target service according to usage requirements, thereby avoiding resource occupation problems in unnecessary scenarios and reducing the consumption of system resources.

Combined with the second aspect, in some implementations of the second aspect, the second device loads the target service, including: the second device pulls up a process corresponding to the target service; the second device initializes the target service; The second device registers with the target service.

In the embodiment provided by this application, after receiving the call notification from the first device, the second device loads the target service so that the first device calls the target service on the second device. Based on this solution, the second device does not need to load the target service when it is powered on. Instead, it loads the target service after receiving the call request from other devices, thereby reducing the occupation of boot resources and avoiding unnecessary waste of resources.

With reference to the second aspect, in some implementations of the second aspect, the method further includes: the second device receiving second notification information from the first device, the second notification information being used to instruct the first device to The call to the target service ends.

Combined with the second aspect, in some implementations of the second aspect, the method further includes: the second device checks the reference count of the target service and determines whether to uninstall the target service.

In the embodiment provided by this application, the second device checks the reference count of the target service, that is, checks whether the target service is still called. When the reference count of the target service is 0, that is, when the target service is not called, the second device can uninstall the target service. target service to reduce the occupation of system resources; when the reference count of the target service is not 0, that is, when there are still devices or other services calling the target service, the second device does not need to uninstall the target service to facilitate other devices. Or the service calls the target service directly.

In a third aspect, a device for calling system services is provided, which is applied to a first device. The device includes: a sending module, configured to send first notification information to a second device, where the first notification information includes information about the target service, The information of the target service is the information of the system service that the first device needs to call. The first notification information is used to instruct the second device to load the target service; the receiving module is used to receive the first response from the second device. information, the first response information includes a service handle of the target service, and the service handle is used by the first device to call the target service on the second device.

In conjunction with the third aspect, in some implementations of the third aspect, the device further includes: a processing module, configured to determine a target device and the target service, and the target device is a device that needs to load the target service, wherein the first The second device is the target device.

Combined with the third aspect, in some implementations of the third aspect, the processing module is specifically configured to determine the target device and the target service according to task flow requirements.

In conjunction with the third aspect, in some implementations of the third aspect, the sending module is further configured to send second notification information to the second device, where the second notification information is used to instruct the first device to serve the target. The call ends.

Combined with the third aspect, in some implementations of the third aspect, the processing module is also used to determine the end of the transfer of the target service.

In a fourth aspect, a device for calling system services is provided, which is applied to a second device. The device includes: a receiving module, configured to receive first notification information from the first device, where the first notification information includes information about the target service. , the information of the target service is the information of the system service that the first device needs to call, the first notification information is used to instruct the second device to load the target service; the processing module is used to load the target service; the sending module is used For sending first response information to the first device, the first response information includes a service handle of the target service, and the service handle is used by the first device to call the target service on the second device.

Combined with the fourth aspect, in some implementations of the fourth aspect, the processing module is specifically used to launch a process corresponding to the target service, initialize the target service, and register the target service.

In conjunction with the fourth aspect, in some implementations of the fourth aspect, the receiving module is further configured to receive second notification information from the first device, where the second notification information is used to instruct the first device to respond to the target. The service call ends.

Combined with the fourth aspect, in some implementations of the fourth aspect, the processing module is also used to check the reference count of the target service and determine whether to uninstall the target service.

In a fifth aspect, an electronic device is provided. The electronic device includes: a processor for calling and running a computer program from a memory, so that the electronic device executes the first aspect or any of the possible methods in the first aspect. Implementation method; or perform the first aspect or any possible implementation method of the first aspect.

In conjunction with the fifth aspect, in some implementations of the fifth aspect, the electronic device further includes: the memory and/or a communication interface, the memory is used to store the computer program; the communication interface is used to send and receive data/signaling.

In a sixth aspect, an electronic device is provided. The electronic device includes a device as in the third aspect or any one of the implementations of the third aspect, or as in the fourth aspect or any one of the implementations of the fourth aspect. device.

In a seventh aspect, a computer program storage medium is provided. The computer-readable medium stores program code. When the computer program code is run on a computer, it causes the computer to execute the implementation of the first aspect or any one of the first aspects. The method in the method, or the method in the second aspect or any of the implementation methods of the second aspect.

In an eighth aspect, a chip system is provided. The chip system includes at least one processor. When the program instructions are executed in the at least one processor, as in the first aspect or any one of the implementations of the first aspect, The method, or the method in the second aspect or any one of the implementation manners of the second aspect is implemented.

Description of drawings

Figure 1 is a system architecture diagram provided by an embodiment of the present application.

FIG. 2 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.

Figure 3 is a software structure block diagram of an electronic device provided by an embodiment of the present application.

Figure 4 is an interactive schematic diagram of a method for loading system services provided by an embodiment of the present application.

Figure 5 is a schematic diagram of a scenario for calling system services provided by an embodiment of the present application.

Figure 6 is a schematic diagram of a scenario for calling system services provided by an embodiment of the present application.

Figure 7 is an interactive schematic diagram of a method for uninstalling system services provided by an embodiment of the present application.

Figure 8 is an interactive schematic diagram of a method for calling system services provided by an embodiment of the present application.

Figure 9 is a structural block diagram of a device for calling system services provided by an embodiment of the present application.

Figure 10 is a structural block diagram of a device for calling system services provided by an embodiment of the present application.

Detailed ways

The terminology used in the following examples is for the purpose of describing specific embodiments only and is not intended to limit the application. As used in the specification and appended claims of this application, the singular expressions "a", "an", "said", "above", "the" and "the" are intended to also Expressions such as "one or more" are included unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of this application, "at least one" and "one or more" refer to one, two or more than two. The term "and/or" is used to describe the relationship between associated objects, indicating that there can be three relationships; for example, A and/or B can mean: A exists alone, A and B exist simultaneously, and B exists alone, Where A and B can be singular or plural. The character "/" generally indicates that the related objects are in an "or" relationship.

Reference in this specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Therefore, the phrases "in one embodiment", "in some embodiments", "in other embodiments", "in other embodiments", etc. appearing in different places in this specification are not necessarily References are made to the same embodiment, but rather to "one or more but not all embodiments" unless specifically stated otherwise. The terms “including,” “includes,” “having,” and variations thereof all mean “including but not limited to,” unless otherwise specifically emphasized.

Figure 1 is a schematic diagram of a system architecture applicable to embodiments of the present application. Two or more electronic devices form a networking scenario, such as device A and device B shown in the figure. Device A can call system services from device B. Device B can also call system services from device A. The device A and device B can be electronic devices that support the operation of distributed system services, such as mobile phones, computers, tablets, smart watches, large-screen devices, etc., and are not limited to the devices shown in Figure 1.

For example, FIG. 2 shows a schematic structural diagram of the electronic device 100. The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2 , mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone interface 170D, sensor module 180, compass 190, motor 191, indicator 192, camera 193, display screen 194, and Subscriber identification module (SIM) card interface 195, etc.

It can be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 100 . In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figures, or some components may be combined, some components may be separated, or some components may be arranged differently. The components illustrated may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (GPU), and an image signal processor. (image signal processor, ISP), controller, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU), etc. Among them, different processing units can be independent components or integrated in one or more processors. In some embodiments, electronic device 100 may also include one or more processors 110 . Among them, the controller can generate operation control signals based on the instruction operation code and timing signals to complete the control of fetching and executing instructions. In some other embodiments, the processor 110 may also be provided with a memory for storing instructions and data. By way of example, the memory in processor 110 may be a cache memory. This memory may hold instructions or data that have been recently used or recycled by processor 110 . If the processor 110 needs to use the instructions or data again, it can be called directly from the memory. This avoids repeated access and reduces the waiting time of the processor 110, thereby improving the efficiency of the electronic device 100 in processing data or executing instructions.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, and a universal asynchronous receiver and transmitter (universal asynchronous receiver/transmitter (UART) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, SIM card interface, and/or USB interface, etc. Among them, the USB interface 130 is an interface that complies with USB standard specifications, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the electronic device 100, and can also be used to transmit data between the electronic device 100 and peripheral devices. The USB interface The 130 can also be used to connect headphones to play audio through them.

It can be understood that the interface connection relationships between the modules illustrated in the embodiments of the present application are only schematic illustrations and do not constitute a structural limitation of the electronic device 100 . In other embodiments of the present application, the electronic device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

The charging management module 140 is used to receive charging input from the charger. Among them, the charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from the wired charger through the USB interface 130 . In some wireless charging embodiments, the charging management module 140 may receive wireless charging input through the wireless charging coil of the electronic device 100 . While the charging management module 140 charges the battery 142, it can also provide power to the electronic device through the power management module 141.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charging management module 140, and supplies power to the processor 110, internal memory 121, external memory, display screen 194, camera 193, wireless communication module 160, etc. The power management module 141 can also be used to monitor battery capacity, battery cycle times, battery health status (leakage, impedance) and other parameters. In some other embodiments, the power management module 141 may also be provided in the processor 110 . In other embodiments, the power management module 141 and the charging management module 140 may also be provided in the same device.

The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 may be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example: Antenna 1 can be reused as a diversity antenna for a wireless LAN. In other embodiments, antennas may be used in conjunction with tuning switches.

The mobile communication module 150 can provide solutions for wireless communication including 2G/3G/4G/5G applied on the electronic device 100 . The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves through the antenna 1, perform filtering, amplification and other processing on the received electromagnetic waves, and transmit them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves through the antenna 1 for radiation. In some embodiments, at least part of the functional modules of the mobile communication module 150 may be disposed in the processor 110 . In some embodiments, at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be provided in the same device.

The wireless communication module 160 can provide applications on the electronic device 100 including wireless local area networks (WLAN) (such as wireless fidelity (WiFi) network), Bluetooth (bluetooth, BT), global navigation satellite system ( Global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (infrared, IR) and other wireless communication solutions. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2 , frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 . The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.

The electronic device 100 implements display functions through a GPU, a display screen 194, an application processor, and the like. The GPU is an image processing microprocessor and is connected to the display screen 194 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, videos, etc. Display 194 includes a display panel. The display panel can use a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active matrix organic light emitting diode or an active matrix organic light emitting diode (active-matrix organic light emitting diode). emitting diode (AMOLED), flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, quantum dot light emitting diode (QLED), etc. In some embodiments, electronic device 100 may include one or more display screens 194.

In some embodiments of the present application, when the display panel uses materials such as OLED, AMOLED, FLED, etc., the display screen 194 in Figure 2 can be bent. Here, the above-mentioned display screen 194 can be bent means that the display screen 194 can be bent at any position to any angle and can be maintained at this angle. For example, the display screen 194 can be folded in half from the middle to the left and right. You can also fold it in half from the middle up and down.

The display screen 194 of the electronic device 100 may be a flexible screen. Currently, flexible screens have attracted much attention due to their unique characteristics and huge potential. Compared with traditional screens, flexible screens are more flexible and bendable. They can provide users with new interaction methods based on bendable characteristics and can meet more users' needs for electronic devices. For electronic devices equipped with a foldable display screen, the foldable display screen on the electronic device can be switched between a small screen in a folded form and a large screen in an unfolded form at any time. Therefore, users The split-screen function is used more and more frequently on electronic devices equipped with foldable displays.

The electronic device 100 can implement the shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, an application processor, and the like.

The ISP is used to process the data fed back by the camera 193. For example, when taking a photo, the shutter is opened, the light is transmitted to the camera sensor through the lens, the optical signal is converted into an electrical signal, and the camera sensor passes the electrical signal to the ISP for processing, and converts it into an image visible to the naked eye. ISP can also perform algorithm optimization on image noise, brightness, and skin color. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, the ISP may be provided in the camera 193.

Camera 193 is used to capture still images or video. The object passes through the lens to produce an optical image that is projected onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the ISP to convert it into a digital image signal. ISP outputs digital image signals to DSP for processing. DSP converts digital image signals into standard RGB, YUV and other format image signals. In some embodiments, electronic device 100 may include one or more cameras 193 .

Digital signal processors are used to process digital signals. In addition to digital image signals, they can also process other digital signals. For example, when the electronic device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. In this way, the electronic device 100 can play or record videos in multiple encoding formats, such as moving picture experts group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

NPU is a neural network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transmission mode between neurons in the human brain, it can quickly process input information and can continuously learn by itself. The NPU can realize intelligent cognitive applications of the electronic device 100, such as image recognition, face recognition, speech recognition, text understanding, etc.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement the data storage function. Such as saving music, videos, etc. files in external memory card.

Internal memory 121 may be used to store one or more computer programs including instructions. The processor 110 can execute the above instructions stored in the internal memory 121 to cause the electronic device 100 to execute the methods provided in some embodiments of the present application, as well as various applications and data processing. The internal memory 121 may include a program storage area and a data storage area. Among them, the stored program area can store the operating system; the stored program area can also store one or more applications (such as photo galleries, contacts, etc.). The storage data area may store data created during use of the electronic device 100 (such as photos, contacts, etc.). In addition, the internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as one or more disk storage components, flash memory components, universal flash storage (UFS), etc. In some embodiments, the processor 110 can cause the electronic device 100 to execute the instructions provided in the embodiments of the present application by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor 110 . methods, and other applications and data processing. The electronic device 100 can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor. For example, music playback, recording, etc.

The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, and an ambient light sensor. 180L, bone conduction sensor 180M, etc.

Among them, the pressure sensor 180A is used to sense the pressure signal and convert the pressure signal into an electrical signal. In some embodiments, pressure sensor 180A may be disposed on display screen 194 . There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. A capacitive pressure sensor may include at least two parallel plates of conductive material. When a force is applied to pressure sensor 180A, the capacitance between the electrodes changes. The electronic device 100 determines the intensity of the pressure based on the change in capacitance. When a touch operation is performed on the display screen 194, the electronic device 100 detects the intensity of the touch operation according to the pressure sensor 180A. The electronic device 100 may also calculate the touched position based on the detection signal of the pressure sensor 180A. In some embodiments, touch operations acting on the same touch location but with different touch operation intensities may correspond to different operation instructions. For example: when a touch operation with a touch operation intensity less than the first pressure threshold is applied to the short message application icon, an instruction to view the short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold is applied to the short message application icon, an instruction to create a new short message is executed.

The gyro sensor 180B may be used to determine the motion posture of the electronic device 100 . In some embodiments, the gyroscope can Sensor 180B determines the angular velocity of electronic device 100 about three axes (ie, X, Y, and Z axes). The gyro sensor 180B can be used for image stabilization. For example, when the shutter is pressed, the gyro sensor 180B detects the angle at which the electronic device 100 shakes, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to offset the shake of the electronic device 100 through reverse movement to achieve anti-shake. The gyro sensor 180B can also be used for navigation and somatosensory game scenes.

The acceleration sensor 180E can detect the acceleration of the electronic device 100 in various directions (generally three axes). When the electronic device 100 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of electronic devices and be used in horizontal and vertical screen switching, pedometer and other applications.

The ambient light sensor 180L is used to sense ambient light brightness. The electronic device 100 can adaptively adjust the brightness of the display screen 194 according to the perceived ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also cooperate with the proximity light sensor 180G to detect whether the electronic device 100 is in the pocket to prevent accidental touching.

Fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can use the collected fingerprint characteristics to achieve fingerprint unlocking, access to application locks, fingerprint photography, fingerprint answering of incoming calls, etc.

Temperature sensor 180J is used to detect temperature. In some embodiments, the electronic device 100 utilizes the temperature detected by the temperature sensor 180J to execute the temperature processing strategy. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the electronic device 100 reduces the performance of a processor located near the temperature sensor 180J in order to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, the electronic device 100 heats the battery 142 to prevent the low temperature from causing the electronic device 100 to shut down abnormally. In some other embodiments, when the temperature is lower than another threshold, the electronic device 100 performs boosting on the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperature.

Touch sensor 180K, also called "touch panel". The touch sensor 180K can be disposed on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is used to detect a touch operation on or near the touch sensor 180K. The touch sensor can pass the detected touch operation to the application processor to determine the touch event type. Visual output related to the touch operation may be provided through display screen 194 . In other embodiments, the touch sensor 180K may also be disposed on the surface of the electronic device 100 at a location different from that of the display screen 194 .

FIG. 3 is a software structure block diagram of the electronic device 100 according to the embodiment of the present application. The layered architecture divides the software into several layers, and each layer has clear roles and division of labor. The layers communicate through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: application layer, application framework layer, Android runtime and system libraries, and kernel layer. The application layer can include a series of application packages.

As shown in Figure 3, the application package can include camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message, etc.

The first application is located in the application layer, that is to say, any application in the application layer can trigger the call to the remote system service.

The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions.

As shown in Figure 3, the application framework layer can include a window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

The window manager is used to manage window programs. The window manager can obtain the display size, determine whether there is a status bar, lock the screen, capture the screen, etc.

Content providers are used to store and retrieve data and make this data accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The view system includes visual controls, such as controls that display text, controls that display pictures, etc. A view system can be used to build applications. The display interface can be composed of one or more views. For example, a display interface including a text message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide communication functions of the electronic device 100 . For example, call status management (including connected, hung up, etc.).

The resource manager provides various resources to applications, such as localized strings, icons, pictures, layout files, video files, etc.

The notification manager allows applications to display notification information in the status bar, which can be used to convey notification-type messages and can automatically disappear after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be notifications that appear in the status bar at the top of the system in the form of charts or scroll bar text, such as notifications for applications running in the background, or notifications that appear on the screen in the form of conversation windows. For example, prompting text messages in the status bar, making beeps, electronic devices Vibration, indicator light flashing, etc.

System libraries can include multiple functional modules. For example: surface manager (surface manager), media libraries (media libraries), 3D graphics processing libraries (for example: OpenGL ES), 2D graphics engines (for example: SGL), etc.

The surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications.

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG and PNG, etc.

The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, composition and layer processing.

2D Graphics Engine is a drawing engine for 2D drawing.

The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, camera driver, audio driver, and sensor driver.

In order to facilitate understanding of this application, the professional terms involved in this application are first explained.

(1) Distributed system: A distributed system is a loosely coupled system composed of multiple processors interconnected through communication lines. It can realize long-distance communication between nodes and usually has distribution, autonomy, parallelism and globality. Characteristics.

(2) Remote procedure call (RPC): RPC refers to a process on computer A that calls a process on another computer B. The calling process on A is suspended, and the called process on B Execution begins, and when the value is returned to A, the A process continues execution. The caller can pass information to the callee through the use of parameters, and then obtain the information through the returned results.

(3) Handle: The handle is a reference identifier managed by the system. It can be relocated to a memory address by the system. It is equivalent to a special pointer. When an application wants to reference other systems, such as databases and operations, When accessing memory blocks or objects managed by the system, etc., handles must be used.

(4) Reference counting: Reference counting is a memory management technology in computer programming languages. It refers to saving the number of references to resources (such as objects, memory or disk space, etc.). When the number of references becomes 0, it will be In its release process, the purpose of automatic resource management can be achieved using reference count technology.

(5) Semaphore: Also called a semaphore, it is a facility used in a multi-threaded environment and can be used to ensure that two or more key code segments are not called concurrently. Before entering a code segment, the thread must obtain a semaphore. After the code segment is completed, the thread releases the semaphore. Other threads that want to enter the code segment must wait until other threads release the semaphore before they can enter.

Normally, distributed system services are loaded when the electronic device is turned on. For example, if startup is configured in the configuration file of the process corresponding to the system service, when the electronic device is turned on, the process corresponding to the system service is pulled up. Start and register the system service. However, distributed system services only start to work in a cross-device scenario. They have no practical effect in a single-machine scenario, but occupy boot resources, causing unnecessary consumption of system resources to a certain extent. Therefore, this application proposes a method of loading and unloading system services on demand. When device A/device B needs to call system services from device B/device A, device B/device A loads the system service. The following describes the method of calling system services provided by the embodiment of the present application with reference to Figures 4 to 8.

Figure 4 is an interactive schematic diagram of a method for calling system services provided by an embodiment of the present application. The called device can load target system services on demand. The method includes steps S401 to S406.

S401. The first device determines the target device and target service.

The target service may be a system service that the first device requires the second device to load on demand, or in other words, the target service may be a system service that the first device needs to call. The target device is a device that needs to load the target service, or in other words, the target device is a device that the first device needs to call the target service. In this application, the target device may be a second device.

The target service may serve a distributed system, such as a distributed scheduling system service used to schedule distributed circulation components, or a distributed hardware service used to process hardware collaboration, etc.

In a possible implementation, the first device may determine the target device and the target service according to task flow requirements. The task flow requirement can be that the target service is loaded on the current device or the first device and needs to be transferred to other devices such as the second device for loading; or it can also be that the application corresponding to the target service is loaded on the current device or the first device. The use on one device needs to be transferred to other devices, or the target device, or the second device for use. This transfer may also be called switching or the like.

For example, as shown in Figure 5, the user can select an application that needs to be transferred on device A, such as application #1, and can select a device that is networked with the device, such as device B. After device A detects the user's operation, it determines the target device and target service. The device B is the second device, which is the target device, or the called device. The device A is the first device, which is the calling device. The target service is the system service corresponding to the application #1.

In another possible implementation, the first device may determine the target service and the target device according to hardware coordination requirements. Example Alternatively, the hardware collaboration requirement can be a split-screen display of the upper-layer application corresponding to the target service. That is to say, the first device calls the second device so that the application interface corresponding to the target service can be partially displayed on the first device. Part of it is displayed on the target device. As shown in Figure 6, for example, during a slide presentation, device A can call device B to cause the slides to be presented on device B, and comments corresponding to the slides to be presented on device A.

S402: The first device sends the first notification information to the second device, and accordingly, the second device receives the first notification information from the first device.

The first notification information includes information about the target service. The information about the target service is information about the system service that the first device needs to call. For example, the information about the target service can be the ID of the target service or the ID of the target service. Name, etc., this application does not limit this.

The first notification information may also be used to instruct the second device to load the target service.

In a possible implementation, the first device may send the first notification information to the second device through RPC.

After receiving the first notification information from the first device, the second device loads the target service. Loading the target service by the second device may include steps S403 to S405.

S403. The second device starts the process corresponding to the target service.

The second device can pull up the process corresponding to the target service or start the process corresponding to the target service for the second device.

S404, the second device initializes the target service.

The second device may initialize the target service so that the second device provides an application corresponding to the target service with the ability to run on the second device.

S405, the second device registers the target service.

The second device registers with the target service and manages and maintains the target service so that the target service can run on the second device.

S406: The second device sends the first response information to the first device, and accordingly, the first device receives the first response information from the second device.

In a possible implementation, the first response information includes a service handle, and the service handle is used by the first device to call the target service on the second device. The service handle is also the handle corresponding to the target service. The first device can determine the location and other information of the target service based on the service handle and call it.

The first response information may also be used to indicate that the loading result of the target service is successful.

In another possible implementation manner, the first response information is used to indicate that the loading result of the target service on the second device is a loading failure. In this solution, the first device can re-send notification information to the second device to instruct the second device to reload the target service, or the first device can give up calling the target service on the second device.

Based on the technical solutions provided by the embodiments of this application, in the distributed system service scenario, when the calling device needs to call the target service, the target device can load the target service. There is no need to load the system service in the boot or stand-alone scenario, thereby reducing boot resources. occupation to avoid unnecessary consumption of resources.

For the method of loading system services described above, after the target service call is completed, the target device can also uninstall the target service. The following describes a method for uninstalling system services provided by the embodiment of the present application, as shown in Figure 7. The method includes the following steps S701 to S705.

S701: The first device determines that the invocation of the target service is completed.

The end of the target service call can be specifically when the first device and the second device change from a networking scenario to a non-networking scenario, or a stand-alone scenario, that is, when the second device is not needed, the first device can independently meet the usage requirements. Scenes. The first device determines that the target service call is completed because the first device detects that the target service exits running on the first device, or the first device receives a user instruction indicating that the target service call is completed, etc.

In a possible implementation manner, the first device determines that the invocation of the target service has ended. The first device determines that the transfer of the target service has ended, or that the transfer of the upper-layer application corresponding to the target service has ended.

In another possible implementation manner, the first device determines that the invocation of the target service is completed by determining that the hardware collaboration task is completed, or that the cross-device display of the application corresponding to the target service is completed.

S702: The first device sends second notification information to the second device, and accordingly, the second device receives the second notification information from the first device.

The second notification information is used to indicate the end of the first device's call to the target service.

In a possible implementation, the second notification information can also be used to instruct the second device to uninstall the target service.

S703. The second device checks the reference count of the target service.

That is to say, the second device checks whether the target service is still called. When a device calls the target service, the reference count of the target service is not 0. When no device calls the target service, the reference count of the target service is is 0.

After the first device ends calling the target service on the second device, there may still be other devices calling the target service on the second device. Therefore, the second device needs to check the reference count of the target service to confirm whether The target service needs to be uninstalled.

In a possible implementation, the second device checks the reference count of the target service within the preset period. If the reference count of the target service is 0 within the preset period, the second device can start the reference count of the target service. Service uninstallation process.

S704, the second device releases resources.

In a possible implementation manner, the second device confirms that the reference count of the target service is 0, that is, when the target service is not called, the second device releases resources such as memory and semaphore.

S705, the second device uninstalls the target service.

After the second device releases the system resources, the process corresponding to the target service exits, and the second device uninstalls the target service.

In another possible implementation, the second device determines that the reference count of the target service is not 0, that is, after the first device completes the call to the target service, there are still other devices on the second device. If the target service is called on the second device, the second device may not uninstall the target service, so that other devices can call the target service on the second device.

Based on the technical solutions provided by the embodiments of this application, in a distributed scenario, after the calling device completes the call to the target service, the calling device sends notification information to the called device, and the called device determines that no other device calls the target service. , uninstall the target service and reduce the occupation of system resources. If it is determined that other devices still call the target service, retain the target service so that other devices can directly call the target service.

The above loading and unloading methods of system services can be combined and applied together in distributed scenarios. The calling device and the called device can trigger the loading and unloading of system services according to actual application requirements. The following takes the task flow scenario as an example, combined with the first The specific modules in the device and the second device introduce the loading and unloading method of system services, as shown in Figure 8. The method includes steps S801 to S816.

S801. The first application or first service determines the target device and target service.

The first service is a system service on the first device that needs to call the target service. The first application is an upper-layer application corresponding to the first service. The first service and the target service can be the same service or different services. service, and the first service can serve the system that has been loaded.

In a possible implementation, the first application or the first service can be determined according to task flow requirements. For example, when the first application or the first service detects a user operation and needs to flow the first application to the second device for running, or when the first service needs to flow to the second device for loading, the first application or the first service determines the first application or the first service. The second device is a target device, and the first service is a target service. In this implementation, the first service and the target service may be the same service.

The task can serve the target or the upper-layer application corresponding to the target. This task flow can be a cross-device call and load of the target service, or it can be a cross-device running or use of the application corresponding to the target service. As an example, this task flow can be that the user uses a music application on a mobile phone and now needs to continue to use the music application on a tablet, which can trigger the flow of the music application from the mobile phone to the tablet, and the music application can also be transferred back from the tablet. cell phone.

S802: The first application or first service of the first device specifies the target device and target service (load remote system capability) to the system service management module of the first device.

That is to say, the first application or the first service sends the information of the target device and the target service to the system service management module. The information of the target device may be the name of the target device, or the identification of the target device, and the target service The information can be the name of the target service, or the identification of the target service and other information.

S803. The system service management module of the first device sends the first notification information to the system service management module of the second device.

The second device is also the target device determined by the first device. Step S803 is similar to step S402. The only difference is that the first notification information can be sent by the system service management module of the first device and received by the system service management module of the second device. To avoid duplication, the content of this step will not be repeated. Again.

S804: The system service management module of the second device specifies the target service to the startup management module of the second device.

The system service management module of the second device can send the information of the target service to the startup management module, so that the startup management module can start the process corresponding to the target service.

In a possible implementation manner, the system service management module of the second device can also send instruction information to the startup management module, instructing the startup management module to pull up the process corresponding to the target service.

S805: The startup management module of the second device starts the process corresponding to the target service, or starts the process corresponding to the target service.

S806: The system service management module of the second device initializes the target service.

That is to say, the system service management module of the second device provides the application corresponding to the target service with the ability to run on the second device.

S807: The system service management module of the second device registers the target service.

The system service management module of the second device registers the target service, and manages and maintains the target service so that the target service can run on the second device.

S808: The system service management module of the second device sends the first response information to the system service management module of the first device.

Step S808 is similar to step S406. The only difference is that the first response information can be sent by the system service management module of the second device and received by the system service management module of the first device. To avoid duplication, the content of this step will not be repeated. Again.

S809, task transfer.

This task transfer can be that the target service is only loaded on the first device before the transfer, and now needs to be loaded on the second device as well; or the upper-layer application corresponding to the target service can be switched from running on the first device. To run on the second device, the upper-layer application corresponding to the target service can also be switched from running on the second device to running on the first device.

In this task flow scenario, the first service and the target service can serve the same system.

S810: The first application or first service of the first device notifies the system service management module of the first device that the invocation of the target service ends.

In a possible implementation, the first device determines that the task transfer is completed, that is to say, the first device determines that the transfer of the target service between the first device and the second device is completed, or that the scenario of the target service is determined by the group. Network scenarios have become non-network scenarios, or stand-alone scenarios, or scenarios that do not require task flow.

S811. The system service management module of the first device sends the second notification information to the system service management module of the second device.

The system service management module of the first device determines that the call of the first application or first service to the target service has ended, and checks whether there are other applications or services on the first device that call the target service. After determining that the first device has After no application or service calls the target service, the second notification information is sent to the system service management module of the second device.

In a possible implementation, the second notification information may also be used to instruct the second device to uninstall the target service.

S812: The system service management module of the second device notifies the first process of the second device that the invocation of the target service has ended.

In a possible implementation, the system service management module of the second device may also send instruction information to the first process to instruct the first process to exit running.

The first process is a process corresponding to the target service.

S813, the first process checks the reference count.

The first process checks whether the reference count of the target service is 0. That is to say, after the first device ends calling the target service, the first process checks whether there are still other devices calling the target service on the second device. target service.

S814, the first process releases resources.

In a possible implementation, the second device determines that the reference count of the target service is 0, that is to say, after the first device ends calling the target service on the second device, there is no other device on the second device. When the target service is called on the second device, the first process can release resources such as memory and semaphores.

When the second device determines that the reference count of the target service is not 0, the first process does not need to perform step S814. Alternatively, when the second device determines that the reference count of the target service is 0, it may choose not to release the resource. For example, when the system resources are sufficient, it is convenient for other subsequent devices to directly call the target service.

S815: The first process notifies the system service management module of the second device to uninstall or retain the target service.

In a possible implementation manner, if the first process determines that the reference count of the target service is 0, it may notify the system service management module of the second device to uninstall the target service.

In another possible implementation manner, if the first process determines that the reference count of the target service is not 0, it may notify the system service management module of the second device to retain the target service.

S816: The system service management module of the second device uninstalls or retains the target service.

In a possible implementation, the system service management module of the second device retains the target service when the reference count of the target service is not 0, so that other devices or other services can directly call the target service on the second device. target service.

In a possible implementation manner, the system service management module of the second device uninstalls the target service when the reference count of the target service is 0 to reduce the occupation of system resources.

In a possible implementation, the system service management module of the second device may not uninstall the target service when the reference count of the target service is 0, so that subsequent other devices can directly call the target service.

Through the embodiments provided by this application, for distributed scheduling services, it is not necessary to load the target service in a boot or stand-alone scenario. Instead, when multiple devices are networked and need to be transferred across devices, the called device loads the target. service, thereby reducing the boot memory usage and saving system resources; after the task transfer is completed, the called device will decide whether to uninstall the target service based on actual needs. Uninstalling the target service can save system resources, and retaining the target service will This can facilitate direct calling of the target service during the next task transfer.

In a possible implementation, after the first device calls the target service from the second device, when it needs to call the target service from the third device, for example, after the target service is transferred from the first device to the second device, When it needs to be transferred to a third device, the second device can call the target service on the third device. Specifically, in this method, the second device may perform the actions performed by the first device, and the third device may perform the actions performed by the second device.

The calling method of the system service provided by this application has been introduced above with reference to Figures 4 to 8. The device that can support the implementation of the above method will be introduced below with reference to Figures 9 and 10.

Figure 9 is a structural block diagram of a communication device provided according to a method embodiment of the present application. The communication device can have the functions of the first device or the second device in the above method embodiment, and is used to execute the first device in the above method embodiment. The steps performed by the device or a second device.

In a possible implementation, the communication device 900 shown in Figure 9 can serve as the first device involved in the above method embodiment, and perform the steps performed by the first device in the above method embodiment.

As shown in Figure 9, the communication device may include a receiving module 910 and a sending module 920.

The receiving module 910 may be used to support the communication device 900 in receiving information, for example, performing S406, S808 and other receiving actions performed by the first device in FIGS. 4 to 8 .

The sending module 920 may be used to support the communication device 900 in sending information, for example, performing S402, S702, S803, S811 and other sending actions performed by the first device in FIGS. 4 to 8 .

The receiving module 910 and the sending module 920 may also be used to perform receiving or sending actions performed between the system service management module of the first device and the first application or the first service, such as steps S802 and S810 in FIG. 8 .

Optionally, the communication device may also include a processing module 930, which is coupled to the sending module 920 and the receiving module 910, and may be used to support the communication device 900 in performing the processing actions in the above method embodiments, for example, executing the steps shown in FIG. 4 to FIG. S401, S701, S801 and S809 in 6 are processing actions performed by the first device.

Optionally, the communication device 900 may also include a storage module 940 for storing program codes and data of the communication device 900 .

In another possible implementation, the communication device 900 shown in Figure 9 can serve as the second device involved in the above method embodiment, and perform the steps performed by the second device in the above method embodiment.

As shown in FIG. 9 , the communication device 900 may include a sending module 920 and a receiving module 910 .

The receiving module 910 may be used to support the communication device 900 in receiving information, for example, performing S402, S702, S803 and S811 in FIGS. 4 to 8 and other receiving actions performed by the second device.

The sending module 920 may be used to support the communication device 900 in sending information, for example, performing sending actions performed by the second device such as S406 and S808 in FIGS. 4 to 8 .

The receiving module 910 and the sending module 920 can also be used to perform receiving and sending actions between the system service management module, startup management module and the first process of the second device, such as steps S804, S812 and S815 in Figure 8.

Optionally, the communication device may also include a processing module 930, which is coupled to the sending module 920 and the receiving module 910, and may be used to support the communication device 900 in performing the processing actions in the above method embodiments, for example, executing the steps shown in FIG. 4 to FIG. S403, S404, S405, S703, S704, S705, S705, S806, S807, S813, S814 and S816 in 8 are the processing actions performed by the second device.

Figure 10 is a schematic block diagram of a communication device 1000 provided by an embodiment of the present application. As shown in the figure, the communication device 1000 includes: at least one processor 1010 and a transceiver 1020. The processor 1010 is coupled to the memory 1030 and is used to execute instructions stored in the memory 1030 to control the transceiver 1020 to send signals and/or receive signals.

Optionally, the communication device 1000 further includes a memory 1030 for storing instructions.

In some embodiments, the above-mentioned processor 1010 and the memory 1030 can be combined into one processing device, and the processor 1010 is used to execute the program code stored in the memory 1030 to implement the above functions. During specific implementation, the memory 1030 can also be integrated into the processor 1010 in, or independently of processor 1010.

In some embodiments, transceiver 1020 may include a receiver and a transmitter.

The transceiver 1020 may further include an antenna, and the number of antennas may be one or more. The transceiver 1020 may be a communication interface or an interface circuit.

When the communication device 1000 is a chip, the chip includes a transceiver module and a processing module. The transceiver module may be an input-output circuit or a communication interface; the processing module may be a processor, microprocessor, or integrated circuit integrated on the chip.

When the above communication device is a chip applied to the first device/second device, the first device/second device chip implements the functions of the first device/second device in the above method embodiment. The first device/second device chip receives information from other modules (such as radio frequency modules or antennas) in the first device/second device, and the information is sent to the first device by the second device/first device or other devices. device/second device; or, the first device/second device chip outputs information to other modules (such as radio frequency modules or antennas) in the first device/second device, and the information is the first device/second device Sent to the second device/first device, or other devices.

Embodiments of the present application also provide a computer-readable storage medium. The computer-readable storage medium stores computer programs or instructions. The computer programs or instructions are executed by a computer (for example, a processor) to implement the steps in the embodiments of the present application. Some or all of the steps of any method performed by any device.

Embodiments of the present application also provide a computer program product containing instructions that, when run on a computer, cause some or all of the steps of any method executed by any device in the embodiments of the present application to be executed.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of modules is only a logical function division. In actual implementation, there may be other division methods. For example, multiple modules or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, indirect coupling or communication connection of devices or modules, and may be in electrical, mechanical or other forms.

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

In addition, each functional module in each embodiment of the present application can be integrated into one processing module, or each module can exist physically alone, or two or more modules can be integrated into one module.

If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code. .

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application. should be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A method of calling system services, characterized in that the method includes:

The first device sends first notification information to the second device. The first notification information includes information about a target service. The information about the target service is information about a system service that the first device needs to call. The first notification information The information is used to instruct the second device to load the target service;

The first device receives first response information from the second device. The first response information includes a service handle of the target service. The service handle is used by the first device to call on the second device. The target service.
The method according to claim 1, characterized in that, before the first device sends the first notification information to the second device, the method further includes:

The first device determines a target device and the target service, and the target device is a device that needs to load the target service,

Wherein, the second device is the target device.
The method of claim 2, wherein the first device determines the target device and the target service, including:

The first device determines the target device and the target service according to task flow requirements.
The method according to any one of claims 1 to 3, characterized in that the method further includes:

The first device sends second notification information to the second device, where the second notification information is used to indicate the end of the first device's call to the target service.
The method according to claim 4, characterized in that, before the first device sends the second notification information to the second device, the method further includes:

The first device determines that the transfer of the target service is completed.
A method of calling system services, characterized in that the method includes:

The second device receives first notification information from the first device. The first notification information includes information about a target service. The information about the target service is information about a system service that the first device needs to call. The first device The notification information is used to instruct the second device to load the target service;

The second device loads the target service;

The second device sends first response information to the first device. The first response information includes a service handle of the target service. The service handle is used by the first device on the second device. Call the target service.
The method of claim 6, wherein the second device loads the target service, including:

The second device pulls up the process corresponding to the target service;

The second device initializes the target service;

The second device registers with the target service.
The method according to claim 6 or 7, characterized in that, the method further includes:

The second device receives second notification information from the first device, and the second notification information is used to indicate that the first device's call to the target service has ended.
The method according to any one of claims 6 to 8, characterized in that the method further includes:

The second device checks the reference count of the target service and determines whether to uninstall the target service.
A device for calling system services, applied to a first device, characterized by including:

A sending module, configured to send first notification information to the second device, where the first notification information includes information about a target service, and the information about the target service is information about a system service that the first device needs to call. A notification message is used to instruct the second device to load the target service;

A receiving module, configured to receive first response information from a second device, where the first response information includes a service handle of the target service, and the service handle is used by the first device to call on the second device The target service.
The device according to claim 10, characterized in that the device further includes:

A processing module, configured to determine a target device and the target service, where the target device is a device that needs to load the target service.
The apparatus according to claim 11, wherein the processing module is specifically configured to determine the target device and the target service according to task flow requirements.
The device according to any one of claims 10 to 12, characterized in that the sending module is further configured to send a message to the second The device sends second notification information, where the second notification information is used to indicate the end of the first device's call to the target service.
The device according to any one of claims 10 to 13, wherein the processing module is further configured to determine the end of the transfer of the target service.
A device for calling system services, applied to a second device, characterized by including:

A receiving module configured to receive first notification information from the first device, where the first notification information includes information about a target service, and the information about the target service is information about a system service that the first device needs to call, and the The first notification information is used to instruct the second device to load the target service;

A processing module used to load the target service;

A sending module, configured to send first response information, where the first response information includes a service handle of the target service, and the service handle is used by the first device to call the target service on the second device.
The device according to claim 15, characterized in that the processing module is specifically used for:

Pull up the process corresponding to the target service;

Initialize the target service;

Register the target service.
The device according to claim 15 or 16, characterized in that the receiving module is further configured to receive second notification information, and the second notification information is used to indicate the end of calling the target service.
The device according to any one of claims 15 to 17, wherein the processing module is further configured to check the reference count of the target service and determine whether to uninstall the target service.
An electronic device, characterized in that the electronic device includes: a processor for calling and running a computer program from a memory, so that the electronic device executes the method according to any one of claims 1 to 5; Or perform a method as claimed in any one of claims 6 to 9.
The electronic device according to claim 19, characterized in that the electronic device further includes: the memory and/or a communication interface, the memory is used to store the computer program, and the communication interface is used to send and receive data/ signaling.
A computer program storage medium, characterized in that the computer-readable medium stores program code. When the computer program code is run on a computer, it causes the computer to execute the method described in any one of claims 1 to 5. Method, or the method according to any one of claims 6 to 9.
A chip system, characterized in that the chip system includes at least one processor, and when the program instructions are executed in the at least one processor, the method according to any one of claims 1 to 5 is performed, or , the method according to any one of claims 6 to 9 is implemented.