Push message processing method and electronic equipment

Abstract

The embodiment of the invention provides a push message processing method and electronic equipment. The electronic equipment comprises a main processor and a coprocessor. In the method, the coprocessor receives a push message, the coprocessor processes the push message, or the coprocessor sends the push message to the main processor, so that the main processor processes the push message. According to the embodiment of the invention, the power consumption of the push service to the electronic equipment can be reduced, and the standby time of the electronic equipment is prolonged.

Description

Technical Field

[0001] This application relates to the technical field of data processing, and particularly to a method for processing push messages and an electronic device. Background Art

[0002] The push service is a service that notifies users of specified content. Taking cloud push as an example, the cloud server sends relevant content to the applications of the electronic device in the form of push messages. For example, it sends instant messages (IM) to the instant messaging application of the electronic device and shopping advertisement data to the shopping application of the electronic device.

[0003] With the continuous development of push services in electronic devices, there are more and more applications providing push services. As a result, the electronic device receives more and more push messages, leading to an increasing power consumption of the push service for the electronic device and affecting the standby time of the electronic device. Summary of the Invention

[0004] Embodiments of this application provide a method for processing push messages and an electronic device, which can reduce the power consumption of the push service for the electronic device and extend the standby time of the electronic device.

[0005] In a first aspect, this application provides a method for processing push messages, which is applied to an electronic device. The electronic device includes a main processor and a coprocessor. The method includes: the coprocessor receives a push message; the coprocessor processes the push message, or the coprocessor sends the push message to the main processor for the main processor to process the push message. This method allows the coprocessor to receive the push message and the coprocessor or the main processor to process the push message, thus eliminating the need to wake up the main processor every time a push message is received, reducing the number of times the main processor is woken up, reducing the power consumption of the electronic device, and extending the standby time of the electronic device.

[0006] In some embodiments, the method may further include: the coprocessor determines a target processor from the main processor and the coprocessor according to the push message. The target processor may be only the main processor, or only the coprocessor, or both the main processor and the coprocessor. In some embodiments, there may be multiple coprocessors. When there are multiple coprocessors, the coprocessor that receives the push message and the coprocessor that processes the push message may be the same or different. For example, when the coprocessors include a first coprocessor and a second coprocessor, the first coprocessor may receive the push message and send the push message to the second coprocessor for the second coprocessor to process the push message. In some embodiments, when determining the target processor, the priority of the coprocessor may be higher than that of the main processor. In other words, when both the coprocessor and the main processor are capable of processing the push message, the target processor is determined to be the coprocessor, thus eliminating the need to wake up the main processor and reducing the power consumption of the electronic device.

[0007] In some embodiments, the push message may include a first identifier. The coprocessor determines the target processor from the main processor and the coprocessor according to the push message, including: the coprocessor determines the target processor according to the first identifier. By setting the first identifier in the push message, the coprocessor can quickly and accurately determine the target processor, improving the processing efficiency of the coprocessor.

[0008] Optionally, the above-mentioned first identifier may be used to indicate the capabilities related to the push message. The capabilities may be hardware capabilities or software running capabilities. The coprocessor may determine the target processor according to the capabilities supported by the coprocessor and the main processor. Specifically, the coprocessor may determine the capabilities related to the push message according to the first identifier, and determine the target processor according to the capabilities related to the push.

[0009] Alternatively, the above-mentioned first identifier may be used to indicate the target processor. For example, it may be the identifier of the target processor, and the coprocessor may directly determine the target processor according to the first identifier.

[0010] In some embodiments, the coprocessor determines the target processor from the main processor and the coprocessor according to the push message, including: the coprocessor parses the push message to determine the capabilities related to the push message, and determines the target processor according to the capabilities related to the push.

[0011] Optionally, the capabilities related to the push message may be hardware capabilities. Then, when the coprocessor parses the push message to determine the capabilities related to the push message, it may include: the coprocessor parses the push message to determine the hardware related to the push message. Correspondingly, the coprocessor may specifically determine the target processor according to the hardware related to the push message.

[0012] In some embodiments, determining the target processor according to the hardware related to the push message may include: determining the target processor according to whether the hardware connected to the target processor includes the hardware related to the push message. In this embodiment, the determination of the target processor is associated with the hardware connected to the processor, so as to ensure that the target processor can process the push message and prevent the problem that the determined target processor cannot process the push message. Optionally, when the hardware connected to both the coprocessor and the main processor includes the hardware related to the push message, the coprocessor may be preferentially determined as the target processor, thereby reducing the number of times the main processor is awakened, reducing the power consumption of the electronic device, and prolonging the standby time of the electronic device.

[0013] In some embodiments, the coprocessor parses the push message and determines the capabilities related to the push message, which may include: the coprocessor determines the capabilities related to the push message according to the keywords included in the push message. Through this process, the coprocessor can obtain the capabilities related to the push message more accurately, and then determine the appropriate target processor to process the push message.

[0014] In some embodiments, the mapping relationship between capabilities and processors can be stored on the coprocessor. Correspondingly, the coprocessor can search for keywords from the push message and determine the capabilities corresponding to the found keywords according to the mapping relationship as the capabilities related to the push message. By storing the above mapping relationship on the coprocessor, the coprocessor can more quickly determine the capabilities related to the push message according to the keywords.

[0015] In some embodiments, the above main processor can be an AP, and / or, the coprocessor can be an MCU. Since the MCU has lower power consumption than the AP, processing the push message by the MCU has relatively lower power consumption than processing the push message by the AP, thereby reducing the power consumption of the electronic device and extending the standby time of the electronic device.

[0016] In a second aspect, an embodiment of the present application provides a push message processing method applied to an electronic device, where the electronic device includes a main processor and a coprocessor; the method includes: receiving a push message; sending the push message to the coprocessor for the coprocessor to process the push message; or sending the push message to the main processor for the main processor to process the push message. In this method, after receiving the push message, the push message is preferentially sent to the coprocessor or the main processor for processing, so that it is not necessary to wake up the main processor every time a push message is received, reducing the number of times the main processor is woken up, reducing the power consumption of the electronic device, and extending the standby time of the electronic device.

[0017] In some embodiments, the method may further include: determining a target processor from the main processor and the coprocessor according to the push message.

[0018] In some embodiments, the push message may include a first identifier. Determining a target processor from the main processor and the coprocessor according to the push message may include: determining the target processor according to the first identifier. By setting the first identifier in the push message, the coprocessor can quickly and accurately determine the target processor, improving the processing efficiency of the coprocessor.

[0019] Optionally, the above first identifier can be used to indicate the capabilities related to the push message, and the capabilities can be hardware capabilities or software running capabilities. Then, determining the target processor according to the first identifier may include: determining the capabilities related to the push message according to the first identifier; determining the target processor according to the capabilities related to the push.

[0020] Alternatively, the above first identifier may be used to indicate a target processor. For example, it may be an identifier of the target processor, and thus the target processor can be directly determined according to the first identifier.

[0021] In some embodiments, if the first identifier is used to indicate the hardware related to the push message, then according to the first identifier, determining the capabilities related to the push message may include: determining the hardware related to the push message according to the first identifier.

[0022] In some embodiments, determining the target processor according to the capabilities related to the push may include: determining the target processor according to whether the hardware connected to the target processor includes the hardware related to the push message.

[0023] In some embodiments, the above main processor may be an AP, and / or, the co-processor may be an MCU. Since the MCU has lower power consumption than the AP, processing the push message by the MCU has relatively lower power consumption than processing the push message by the AP, thereby reducing the power consumption of the electronic device and prolonging the standby time of the electronic device.

[0024] In a third aspect, an embodiment of the present application provides an electronic device, including: a main processor, a co-processor, and a memory; one or more computer programs are stored in the memory, and one or more computer programs include instructions, when the instructions are executed by the co-processor, the electronic device is caused to execute the method according to any one of the first aspect.

[0025] In a fourth aspect, an embodiment of the present application provides an electronic device, including: a main processor, a co-processor, a routing processor, and a memory; one or more computer programs are stored in the memory, and one or more computer programs include instructions, when the instructions are executed by the routing processor, the electronic device is caused to execute the method according to any one of the second aspect.

[0026] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored, and when it runs on a computer, the computer is caused to execute the method according to any one of the first aspect or the second aspect.

[0027] In a sixth aspect, an embodiment of the present application provides a chip system, including a processor, the processor is coupled to a memory, and the processor executes a computer program stored in the memory to implement the method according to any one of the first aspect or the second aspect. Wherein, the chip system may be a single chip or a chip module composed of multiple chips. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 It is a schematic structural diagram of an electronic device provided by an embodiment of the present application;

[0029] Figure 2 A structural schematic diagram of the HarmonyOS provided by an embodiment of this application;

[0030] Figure 3 A schematic diagram of the push service processing flow provided by an embodiment of this application;

[0031] Figure 4 A schematic flow diagram of a push message processing method provided by an embodiment of this application;

[0032] Figure 5 Another schematic flow diagram of the push message processing method provided by an embodiment of this application;

[0033] Figure 6 A third schematic flow diagram of the push message processing method provided by an embodiment of this application;

[0034] Figure 7 A fourth schematic flow diagram of the push message processing method provided by an embodiment of this application;

[0035] Figure 8 A fifth schematic flow diagram of the push message processing method provided by an embodiment of this application;

[0036] Figure 9 A sixth schematic flow diagram of the push message processing method provided by an embodiment of this application;

[0037] Figure 10 A seventh schematic flow diagram of the push message processing method provided by an embodiment of this application;

[0038] Figure 11 An eighth schematic flow diagram of the push message processing method provided by an embodiment of this application;

[0039] Figure 12 A ninth schematic flow diagram of the push message processing method provided by an embodiment of this application. Detailed implementation manners

[0040] The terms used in the implementation manners part of this application are only for explaining the specific embodiments of this application, rather than aiming to limit this application.

[0041] An embodiment of this application provides a push message processing method and an electronic device, which can reduce the power consumption of the push service on the electronic device and extend the standby time of the electronic device.

[0042] An embodiment of this application can be applied to electronic devices, such as mobile phones, tablet computers (PADs), personal computers (PCs), wearable intelligent devices such as smart watches, etc.

[0043] Figure 1 A schematic structural diagram of the electronic device 100 is shown. The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, a display screen 194, etc.

[0044] Optionally, the electronic device 100 may further include: 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, a mobile communication module 150, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, and a subscriber identification module (SIM) card interface 195, etc.

[0045] It can be understood that the structure schematically shown in the embodiments of the present invention 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 those shown in the figure, or combine certain components, or split certain components, or have different component arrangements. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0046] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units may be independent devices or integrated in one or more processors.

[0047] The controller may generate operation control signals according to the instruction operation code and timing signals to complete the control of fetching and executing instructions.

[0048] A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory may store instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to use the instruction or data again, it can be directly called from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0049] In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0050] The wireless communication function of the electronic device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modulation and demodulation processor, and the baseband processor, etc.

[0051] The antenna 1 and the antenna 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization rate of the antennas. For example, the antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0052] The mobile communication module 150 may provide a solution for wireless communication including 2G / 3G / 4G / 5G, etc., which is applied to 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 may receive electromagnetic waves through the antenna 1, filter and amplify the received electromagnetic waves, and then transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modulation and demodulation processor and convert it into electromagnetic waves through the antenna 1 for radiation. In some embodiments, at least some functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be disposed in the same device.

[0053] The modulation and demodulation processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. Subsequently, the demodulator transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After being processed by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, receiver 170B, etc.), or displays an image or video through the display screen 194. In some embodiments, the modulation and demodulation processor may be an independent device. In other embodiments, the modulation and demodulation processor may be independent of the processor 110 and disposed in the same device as the mobile communication module 150 or other functional modules.

[0054] The wireless communication module 160 may provide solutions for wireless communications applied to the electronic device 100, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite systems (GNSSs), frequency modulation (FM), near field communication (NFC), infrared (IR), and the like. 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 may also receive signals to be sent from the processor 110, frequency-modulate them, amplify them, and convert them into electromagnetic waves through the antenna 2 for radiation.

[0055] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling electronic device 100 to communicate with a network and other devices via wireless communication technologies. The wireless communication technologies may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology, etc. The GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), beidou navigation satellite system (BDS), quasi-zenith satellite system (QZSS), and / or satellite based augmentation systems (SBAS).

[0056] Electronic device 100 implements a display function through a GPU, display screen 194, and an application processor, etc. The GPU is a microprocessor for image processing, connected to display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or change display information.

[0057] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Miniled, a MicroLed, a Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include one or N display screens 194, where N is a positive integer greater than 1.

[0058] The internal memory 121 can be used to store computer-executable program code, and the executable program code includes instructions. The internal memory 121 can include a program storage area and a data storage area. Among them, the program storage area can store an operating system, application programs required for at least one function (such as a sound playback function, an image playback function, etc.). The data storage area can store data created during the use of the electronic device 100 (such as audio data, a phone book, etc.). In addition, the internal memory 121 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121 and / or the instructions stored in the memory provided in the processor.

[0059] Figure 2 The following is a software structure block diagram of an electronic device provided by an embodiment of the present application. The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. The layers communicate with each other through software interfaces. In this embodiment of the present application, taking the HarmonyOS as an example, the software structure of the electronic device of the HarmonyOS is described. In some embodiments, the HarmonyOS is divided into four layers, from top to bottom are the application layer, the application framework layer, the basic services and the kernel layer.

[0060] The application layer may include several applications (hereinafter simply referred to as applications), such as a camera application, a gallery application, a video application, an instant messaging application, etc. The application layer of the electronic device in the embodiments of the present application includes Application A that supports push services, which may be, for example, an instant messaging application, a shopping application, a browser application, a video application, a short video application, etc.

[0061] The application framework layer provides application programming interfaces (APIs) and programming frameworks for the applications in the application layer, including various components and capabilities to support developers' HarmonyOS development. An ability represents an atomic basic ability in the HarmonyOS system and can correspond to (Android)'s Service or ContentProvider, the service uniform resource identifier (URI) exposed externally, such as ringtone playback, Bluetooth, Wi-Fi, battery management, etc. Whether it is Android, iOS, or HarmonyOS, when an application is packaged, it will declare the set of abilities it uses to facilitate the system to initialize the corresponding resources.

[0062] The basic services are the core set of capabilities of the HarmonyOS system, providing services to applications through the framework layer.

[0063] The kernel layer is the layer between the hardware and the software. The kernel layer may include: display drivers, camera drivers, audio drivers, sensor drivers, etc.

[0064] In the following embodiments, the push message processing method of the embodiments of the present application will be described in detail in combination with the structure of the above-mentioned electronic device.

[0065] First, an exemplary description will be given of the processing flow of the push service applicable to the push message processing method of the embodiments of the present application.

[0066] See Figure 3 As shown, the user installs Application A in the electronic device. The electronic device sends the user account of Application A to the push server through Application A to register the push service; after the push server completes the registration according to the user account, it assigns a device token to the user and sends the device token to Application A of the electronic device; Application A of the electronic device sends the user account and the device token to the application processing server corresponding to Application A, and the application processing server stores the user account and the corresponding device token; when there is data to be pushed to the user, the application processing server sends the data to be pushed and the device token to the push server, and the push server sends the data to be pushed to Application A of the electronic device through a push message according to the device token.

[0067] In some embodiments, the application processing server may implement service processing and push message distribution through a service processing server and a push message distribution server respectively. At this time, when the push message distribution server has a push message to distribute, it may send the user account and the data to be pushed to the service processing server. The service processing server finds the corresponding device token according to the user account and sends the device token and the data to be pushed to the push server. The above push message is also called push notification in some related technologies.

[0068] In some embodiments, when the communication chip in the electronic device receives a push message, it sends the push message to the message receiving module in the AP. The message receiving module in the AP sends the push message to the application corresponding to the push message for processing. For example Figure 4 As shown in, assuming that the push message belongs to Application A, the message receiving module sends the push message to Application A in the AP. Application A in the AP performs processing such as push message parsing, push content acquisition, and related UI drawing on the push message.

[0069] In some embodiments, referring to Figure 4 As shown in, the AP in the electronic device may serve as the main processor, and a coprocessor may be provided outside the main processor. In the embodiments of the present application, taking the coprocessor as a microcontroller unit (MCU) as an example, Application A may be respectively provided in the AP and the MCU. Communication and cooperation within the application can be carried out between the Application A in the two processors to implement the function of Application A. Referring to Figure 4 As shown in, the message receiving module in the AP can only communicate with Application A set in the AP and cannot communicate with Application A in the MCU.

[0070] To save power consumption, when there is no task running, the AP of the electronic device will enter the sleep state. For example, when the screen of the electronic device is turned off and there is no active interrupt source, the AP will automatically enter the sleep state. If the communication chip of the mobile phone receives a push message, it will wake up the AP of the electronic device. The AP of the electronic device is powered on, and the communication chip sends the push message to the message receiving module in the AP. The message receiving module in the AP and the corresponding application process the push message. When there are many push messages, the AP of the mobile phone will be frequently woken up, resulting in a relatively large power consumption for the electronic device to process push messages. Taking a wearable electronic device such as a smart watch as an example, the power consumption of the smart watch for processing push messages accounts for more than 40% of the overall standby power consumption of the machine.

[0071] To solve the power consumption of the electronic device for processing push messages, the embodiments of the present application provide a solution for processing push messages on multiple processors of a mobile phone.

[0072] An electronic device according to an embodiment of the present application may include a main processor and at least one coprocessor. Optionally, the main processor may be a processor that can provide relatively more resources and computing power but has relatively high power consumption, such as an AP, and the coprocessor may be a processor that provides relatively fewer resources and computing power but has relatively low power consumption, such as an MCU. For example, in Figure 5 the electronic device shown, the electronic device includes a main processor and one coprocessor, and taking the main processor as an AP and the coprocessor as an MCU as an example.

[0073] In the push message processing method provided by the embodiment of the present application, when the communication chip in the electronic device receives a push message, the push message is sent to the coprocessor. After the coprocessor receives the push message, the coprocessor processes the push message, or sends it to the main processor for the main processor to process the push message. Therefore, in the embodiment of the present application, some of the received push messages are processed by the coprocessor and some are processed by the main processor. Thus, compared with directly waking up the main processor to process the push message in the above embodiment, the number of times the main processor is woken up is reduced, thereby reducing the power consumption of the electronic device for processing push messages and prolonging the standby time of the electronic device.

[0074] In some embodiments, after the coprocessor receives a push message, it may first determine a target processor for processing the push message from the coprocessor and the main processor. When the target processor is the coprocessor, the coprocessor processes the push message. When the target processor is the main processor, the coprocessor sends the push message to the main processor for processing.

[0075] To improve the rationality and accuracy of the coprocessor in determining the target processor, in the embodiment of the present application, when the coprocessor determines the target processor, it may be determined based on the matching between the capabilities related to the push message and the capabilities of the processor (main processor or coprocessor). The following is an exemplary description.

[0076] In the embodiment of the present application, a certain number of capabilities may be respectively arranged in the main processor and the coprocessor.

[0077] In some embodiments, the capabilities of the processor (main processor or coprocessor) may be the hardware mounted on the processor. For the convenience of description, it is also simply referred to as hardware capabilities hereinafter. Assuming that a piece of hardware is mounted on the processor, the processor has the capabilities corresponding to the hardware, or it can be said that the processor supports the capabilities corresponding to the hardware. The above hardware may be the hardware on the electronic device other than the processor, such as Figure 1Enumerated cameras, speakers, displays, and / or various sensors, etc. For example, if a camera is mounted on the AP, then the AP has the "camera" capability. Similarly, if a camera is mounted on the MCU, then the MCU has the "camera" capability. In some embodiments, the above-mentioned processor-mounted hardware can also be referred to as the processor connecting to the hardware.

[0078] Optionally, a processor mounting a piece of hardware generally means that the processor is connected to the hardware and the driver of the hardware is installed so that the processor can drive the hardware to work properly. Taking the AP mounting a camera as an example, the AP is connected to the camera and the camera driver is installed to drive the camera to work properly.

[0079] In some other embodiments, the capabilities of the processor can be software running capabilities related to the hardware mounted on the processor. For the convenience of description, it is also simply referred to as software running capabilities hereinafter. Suppose a piece of hardware is mounted on the processor, then the processor has at least one software running capability related to the hardware. For example, if a camera is mounted on the AP, then the AP can have video shooting capabilities related to the camera; if a display is mounted on the AP, then the AP can have text display capabilities, corner mark display capabilities, etc. related to the display.

[0080] In the embodiments of the present application, there are no restrictions on which hardware is respectively mounted on the main processor and the coprocessor and the number of the respectively mounted hardware, and they can be set independently in actual applications. In some embodiments, the hardware mounted on each processor can be arranged based on the different resources, computing powers, etc. corresponding to different processors. For example, for capabilities with relatively high requirements for resources and computing power, they can be mounted on the main processor, and for capabilities with relatively low requirements for resources and computing power, they can be mounted on the coprocessor, or mounted on the main processor and the coprocessor at the same time. For example, for the capability of the camera, which has relatively high requirements for resources and computing power, it can be mounted on the AP, and for capabilities such as displays, speakers, and various sensors, which have relatively low requirements for resources and computing power, they can be mounted only on the MCU, or mounted on the AP and the MCU at the same time. Through the above layout of the processor-mounted hardware, the resources and computing powers of the main processor and the coprocessor can be better utilized, and the processing efficiency of the electronic device for push messages can be improved.

[0081] In the embodiments of the present application, the set of capabilities of the main processor is called capability set 1, and the set of capabilities of the coprocessor is called capability set 2. Optionally, there can be an intersection or no intersection between capability set 1 and capability set 2. In some embodiments, capability set 2 is a subset of capability set 1.

[0082] In an embodiment of the push message processing method provided in this application, the main processor and the coprocessor do not cooperate in processing push messages. Specifically: If the coprocessor has all the capabilities declared for use in the push message, regardless of whether the main processor has all the capabilities declared for use in the push message, the coprocessor is preferentially called to use the capabilities declared for use in the push message to process the push message. If the coprocessor does not have all the capabilities declared for use in the push message, the main processor is called to use the capabilities declared for use in the push message to process the push message.

[0083] Combined with Figure 5 , taking the main processor as the AP and the coprocessor as the MCU as an example, if the push message declares the use of "display screen" and "camera" capabilities, and the MCU has the "display screen" and "camera" capabilities, the MCU uses the "display screen" and "camera" capabilities to process the push message. Otherwise, if the MCU only has the "display screen" capability or only has the "camera" capability or does not have either capability, the AP uses the "display screen" and "camera" capabilities to process the push message.

[0084] Optionally, in some embodiments, in order to ensure that when the coprocessor does not have all the capabilities declared for use in a certain push message, the main processor can have all the capabilities declared for use in the push message, so that the electronic device can normally process the push message, the capability set 1 of the main processor can be the set of all capabilities that the push message in the electronic device can declare for use, and the capability set 2 of the coprocessor can be a subset of the capability set 1 of the main processor.

[0085] In the embodiments of this application, the coprocessor is preferentially used to process the push message, and only when the coprocessor does not have all the capabilities declared for use in the push message, the main processor is used to process the push message, thereby reducing the number of times the main processor is awakened and reducing the power consumption of the electronic device.

[0086] In some embodiments, the routing of the above push message can be specifically executed by the coprocessor. After the communication chip of the electronic device receives the push message, it can send a wake-up signal to the coprocessor (such as the MCU). The coprocessor is awakened from the sleep state by the wake-up signal, and the communication chip sends the push message to the coprocessor, and the coprocessor routes the push message to the coprocessor or the main processor for processing.

[0087] Next, through Figure 5 and Figure 6 an exemplary description of the implementation of the push message processing method in the embodiments of this application is given.

[0088] See Figure 5 As shown, the electronic device may include: a communication chip, a main processor (such as an AP) and a coprocessor (such as an MCU); where

[0089] The communication chip can be a communication chip supporting any wireless communication method. The communication chip includes a communication chip controller for performing wireless communication with other devices based on the communication protocol supported by the communication chip. In the embodiments of the present application, the communication chip can be connected to a network to receive push messages sent by a push server to the electronic device.

[0090] When installing Application A that supports push services (such as an instant messaging application) in the electronic device, Application A can be installed in the main processor and the coprocessor respectively. The Application A in the main processor and the Application A in the coprocessor both have the function of processing push messages. In other words, both can process the push messages of Application A.

[0091] It can be understood that the Application A in the main processor and the Application A in the coprocessor can also have other functions besides the push message processing function, and the embodiments of the present application do not make specific limitations. Taking Application A as a shopping application as an example, in addition to the push message processing function, the Application A in the main processor and the Application A in the coprocessor can also have functions such as product search function, product display function, and product purchase function.

[0092] Among them, the functions of the Application A in the main processor and the Application A in the coprocessor can be the same or different. In some embodiments, the functions of the Application A in the coprocessor can be a subset of the functions of Hardware A in the main processor. For example, the Application A in the main processor can have all the functions that Application A can provide, such as push message processing function, product search function, product display function, and product purchase function. The Application A in the coprocessor can have all or part of the above functions, as long as it includes the push message processing function.

[0093] To support the routing of push messages, a message processing module can be set in the coprocessor. The above message processing module can be a module provided by the operating system. In some embodiments, the message processing module can specifically be an application provided by the operating system, and this application can be an application different from Application A.

[0094] Among them, the message processing module is used to parse the received push message, identify the capabilities declared by the push message, and route the push message to the Application A in the coprocessor or the Application A in the main processor according to the capabilities declared by the push message.

[0095] Figure 6 is based on Figure 5 A schematic flowchart of a method for processing push messages according to an embodiment of the present application provided based on the structure of the electronic device shown. As Figure 6 shown, the method can include:

[0096] Step 601: The communication chip controller receives a push message.

[0097] Step 602: The communication chip controller sends a push message to the message processing module of the coprocessor.

[0098] Optionally, before the communication chip controller sends a push message to the message processing module of the coprocessor, the communication chip may send a wake-up signal to the coprocessor. If the coprocessor is in a sleep state, the coprocessor is woken up. After that, the message processing module of the coprocessor can receive the push message sent by the communication chip controller.

[0099] Step 603: The message processing module identifies the abilities declared in the push message to obtain the ability list of the push message.

[0100] For the specific implementation of this step, please refer to the corresponding description in the subsequent embodiments and will not be elaborated here.

[0101] Step 604: The message processing module determines the target processor for processing the push message based on the ability list of the push message and the distribution routing table. When the target processor is the coprocessor, step 605 is executed; otherwise, step 607 is executed.

[0102] Optionally, the message processing module may find the processor corresponding to each ability in the ability list from the distribution routing table. When each processor corresponding to the ability includes the coprocessor, it is determined that the target processor is the coprocessor; otherwise, it is determined that the target processor is the main processor. For the specific implementation of this step, please refer to the corresponding description in the subsequent embodiments and will not be elaborated here.

[0103] Step 605: The message processing module sends the push message to Application A in the coprocessor and executes step 606.

[0104] Step 606: Application A in the coprocessor processes the push message using the ability declared in the push message, and this branch process ends.

[0105] Step 607: The message processing module sends the push message to Application A in the coprocessor and executes step 608.

[0106] Optionally, in order to prevent the main processor from being in a sleep state and unable to receive the push message, before this step is executed, the coprocessor may send a wake-up signal to the main processor. If the main processor is in a sleep state, the main processor is woken up by the wake-up signal. After that, Application A in the main processor can receive the push message sent by the message processing module in the coprocessor.

[0107] Step 608: Application A in the main processor processes the push message using the ability declared in the push message, and this branch process ends.

[0108] In this method, after the communication chip receives the push message, the message processing module of the coprocessor parses and routes the push message. When the coprocessor has all the capabilities declared for use by the push message, Application A in the coprocessor can directly use the capabilities in the coprocessor to process the push message. In the whole process, only the coprocessor needs to be woken up, and there is no need to wake up the main processor to implement the processing of the push message, thus avoiding the frequent wake-up of the main processor and reducing the power consumption of the electronic device.

[0109] Hereinafter, an exemplary description will be given of a possible implementation of the message processing module in the above embodiment for identifying the capabilities declared for use by the push message.

[0110] The code of the push message declares the processing that the push message requires the application to execute, and these processes are identified using relatively fixed strings. For example, the code of the push message is as follows:

[0111] {

[0112] "aps":{

[0113] "alert":"message" / / Message

[0114] "badge":9 / / Display 9 badges

[0115] "sound":"default" / / Vibration prompt tone. Default is default

[0116] },

[0117] "parm1″:"bar" / / Extended parameter 1

[0118] "parm2″:2 / / Extended parameter 2

[0119] }

[0120] Alternatively, the push message of the voice call in the instant messaging application is as follows, for example:

[0121] {

[0122] "aps":{

[0123] "alert":"message", / / Message (text display)

[0124] "badge":9, / / Display 9 badges

[0125] "sound":"default" / / Vibration prompt tone. Default is default (audio playback)

[0126] },

[0127] "voicecall":"123456789" (Incoming voice call from 123456789)

[0128] }

[0129] Among them, there are strings such as "alert", "badge", "sound", etc., which are respectively used to indicate the processing that the application A needs to execute for the push message. In the embodiments of the present application, the capabilities declared by the push message can be identified based on the above keywords.

[0130] In some embodiments, keywords corresponding to each capability can be preset, and whether there are keywords corresponding to the capabilities can be searched for in the push message, so as to identify the capabilities declared by the push message. Specifically, the keywords corresponding to each capability can be searched for in the push message in turn. When there are keywords corresponding to a certain capability, it is recognized that the push message declares the use of that capability.

[0131] In some embodiments, if the capability declared by the push message is the hardware mounted on the processor, the message processing module may pre-store the mapping relationship between each capability and the keyword. The above mapping relationship is shown in Table 1 below:

[0132] Capability Keyword Speaker Sound Display screen Alert, Badge Camera Camera … …

[0133] Table 1

[0134] Then, the message processing module can search for keywords such as sound, alert, badge, camera, etc. in the above push message in turn. Since the keywords sound, alert, and badge can be found in the above push message, it can be recognized that the capabilities declared by the push message include: the speaker and the display screen. Then, the capability list of the push message can be obtained as including: the speaker and the display screen.

[0135] In some embodiments, if the capability declared by the push message is the software running capability related to the hardware mounted on the processor, the mapping relationship between each capability and the keyword pre-stored in the message processing module is shown in Table 2 below:

[0136]

[0137]

[0138] Table 2

[0139] Then, the message processing module can sequentially search for keywords such as sound, alert, and badge in the above push messages. Since the keywords sound, alert, and badge can be found in the above push messages, it can be recognized that the capabilities declared by the push messages include: sound playback capability, text display capability, and badge display capability. Then, the capability list of the push messages can be obtained, including: sound playback capability, text display capability, and badge display capability.

[0140] Next, an exemplary description will be given of the implementation of the message processing module in the above embodiment for determining the target processor for processing the push message based on the distribution routing table.

[0141] Optionally, the message processing module can generate a distribution routing table for the push message based on the capabilities of the main processor and the coprocessor. Specifically, for each capability, the information of the processor with that capability can be recorded in the distribution routing table. Optionally, the distribution routing table can include a capability field and a processor field, and in the processor field corresponding to each capability field, the processors with that capability are recorded.

[0142] In some embodiments, when the processors (including the main processor and the coprocessor) in the electronic device are started, the processors can obtain the hardware mounted by the processors, so as to obtain the capabilities of the processors. The message processor module can obtain the capabilities of each processor from each processor and generate the above distribution routing table based on the capabilities of each processor.

[0143] Optionally, if the message processing module recognizes that the capabilities declared by the push message and the capabilities recorded in the distribution routing table are of the same type, for example, both are hardware capabilities or both are software running capabilities, then when the message processing module determines the target processor for processing the push message based on the distribution routing table, it can, based on the capability list of the push message, search in the distribution routing table for the processors corresponding to each capability in the capability list (that is, each capability declared by the push message). When all the processors corresponding to each capability in the capability list include the coprocessor, it is determined that the target processor of the push message is the coprocessor; otherwise, it is determined that the target processor is the main processor.

[0144] The following is an example.

[0145] In some embodiments, if the capabilities of the processor are the hardware mounted by the processor, the distribution routing table is as shown in Table 3 below.

[0146] Capability Processor Display screen AP, MCU Speaker AP, MCU Touch screen AP, MCU Barometer MCU Camera AP Acceleration sensor MCU

[0147] Table 3

[0148] Table 3 includes a capability field and a processor field. In the processor field corresponding to each capability field, the processors with that capability are recorded. For example, in Table 3, taking the main processor as AP and the coprocessor as MCU, the processors with the capabilities of "display screen", "speaker", and "touch screen" are AP and MCU respectively, the processors with the capabilities of "barometer" and "acceleration sensor" are MCU, and the processor with the capability of "camera" is AP.

[0149] In this embodiment, when the message processing module determines the target processor for processing the push message based on the distribution routing table:

[0150] If the capability list of the push message includes: speaker and display screen, it can be found from Table 3 that the processors corresponding to the "speaker" capability are AP and MCU, and the processors corresponding to the "display screen" capability are also AP and MCU. Since the processors corresponding to both capabilities include MCU, it is determined that the target processor for the push message is MCU.

[0151] If the capability list of the push message includes: display screen and camera, it can be found from Table 3 that the processors corresponding to the "display screen" capability are AP and MCU, and the processor corresponding to the "camera" capability is AP. Since only one of the capabilities has a processor including MCU, it is determined that the target processor for the push message is AP.

[0152] Other possible implementations of the embodiments of the present application will not be listed one by one.

[0153] In other embodiments, if the capability of the processor is the software running capability related to the hardware mounted on the processor, the distribution routing table is as shown in Table 4 below.

[0154]

[0155]

[0156] Table 4

[0157] Table 4 includes a capability field and a processor field. In the processor field corresponding to each capability field, the processors with that capability are recorded. For example, in Table 4, taking the main processor as AP and the coprocessor as MCU, the processors with the capabilities of text display, audio playback, and corner mark display are AP and MCU respectively, and the processor with the capability of video playback is AP.

[0158] In this embodiment, when the message processing module determines the target processor for processing the push message based on the distribution routing table:

[0159] If the list of capabilities for pushing messages includes: text display capability and audio playback capability, it can be found from Table 4 that the processors corresponding to the text display capability and the audio playback capability are both the AP and the MCU. Therefore, since the processors corresponding to both capabilities include the MCU, it is determined that the target processor for pushing messages is the MCU.

[0160] If the list of capabilities for pushing messages includes: text display capability and video playback capability, it can be found from Table 4 that the processor corresponding to the text display capability is the AP and the MCU, and the processor corresponding to the video playback capability is the AP. Since only one of the capabilities has a processor that includes the MCU, it is determined that the target processor for pushing messages is the AP.

[0161] Other possible implementations of the embodiments of the present application will not be listed one by one.

[0162] Optionally, if the message processing module identifies that the capability declared for use in the pushed message is a software running capability, and the capability recorded in the distribution routing table is a hardware capability, in other words, the types of the two capabilities do not match, then before the message processing module determines the target processor for processing the pushed message based on the distribution routing table, it can first convert the software running capability declared for use in the pushed message into a hardware capability, and then based on the converted hardware capability, look up in the distribution routing table the processors corresponding to each capability in the capability list (i.e., each capability declared for use in the pushed message). When the processors corresponding to each capability in the capability list all include the coprocessor, it is determined that the target processor for the pushed message is the coprocessor; otherwise, it is determined that the target processor is the main processor.

[0163] The following is an example for illustration.

[0164] A capability type conversion table can be preset in the message processing module. For example, as shown in Table 5 below, it includes a hardware capability field and a software running capability field, and the hardware capability corresponding to the software running capability is recorded in the hardware capability field corresponding to the software running capability field.

[0165] Software running capability Hardware capability Text capability Display screen Corner mark display capability Display screen Audio playback capability Speaker Video playback capability Camera … …

[0166] Table 5

[0167] If the message processing module, through a preset relationship such as shown in Table 2, identifies that the capability declared for use in the pushed message is a software running capability, while the capability recorded in the preset distribution routing table in the message processing module is a hardware capability, such as shown in Table 3, then before the message processing module determines the target processor for processing the pushed message based on the distribution routing table such as shown in Table 3, it can first convert the capability declared for use in the pushed message from a software running capability into a hardware capability based on the capability type conversion table shown in Table 5.

[0168] For example, if the capabilities declared for a push message include: text display capability and audio playback capability, the message processing module may convert the text display capability to the "display screen" capability and the audio playback capability to the "speaker" capability based on Table 5. This will not be listed one by one hereinafter.

[0169] Combined with Figure 5 the structure of the electronic device shown, in another embodiment of the push message processing method provided in this application, the main processor and the coprocessor may cooperate to process push messages. Specifically:

[0170] If the coprocessor has all the capabilities declared for the push message, the coprocessor is given priority to call the capabilities declared for the push message to process the push message; if the coprocessor only has some of the capabilities declared for the push message, the coprocessor calls the above-mentioned partial capabilities to process the push message, and the main processor calls the other capabilities declared for the push message to process the push message; if the coprocessor does not have any of the capabilities declared for the push message, the main processor calls the capabilities declared for the push message to process the push message.

[0171] Still taking the main processor as the AP and the coprocessor as the MCU as an example, if the push message declares the use of text display capability and audio playback capability, and the MCU has text display capability and audio playback capability, then the MCU calls the text display capability and audio playback capability to process the push message. If the MCU only has text display capability, then the MCU calls the text display capability to process the push message, and the AP calls the audio playback capability to process the push message. If the MCU does not have text display capability and audio playback capability, then the AP calls the text display capability and audio playback capability to process the push message.

[0172] Optionally, in some embodiments, to ensure that the main processor and the coprocessor can cooperate to process all push messages, the union of the capability set 1 of the main processor and the capability set 2 of the coprocessor may be the set of all capabilities that push messages in the electronic device can declare for use. There may be an intersection or no intersection between the capability set 2 of the coprocessor and the capability set 1 of the main processor.

[0173] In this embodiment, the coprocessor is given priority to process the push message. When the coprocessor does not have all the capabilities declared for the push message, the main processor and the coprocessor cooperate to process the push message or the main processor processes the push message alone, thereby reducing the number of times the main processor is awakened and reducing the power consumption of the electronic device.

[0174] Hereinafter, through Figure 5 and Figure 7 an exemplary description will be given of the implementation of the push message processing method in the embodiments of this application.

[0175] The difference between the message processing module in this embodiment and that in the previous embodiment mainly lies in that: in the previous embodiment, the message processing module routes the push message to Application A of the main processor or Application A of the coprocessor for processing, while in this embodiment, the message processing module routes the push message to Application A of the main processor and / or Application A of the coprocessor for processing.

[0176] Figure 7 is based on Figure 5 A schematic flowchart of a method for processing push messages according to an embodiment of the present application provided by the shown electronic device structure. As Figure 7 shown, the main difference between this method and Figure 6 the method shown is that steps 604 to 608 are replaced with the following steps 701 to step 707.

[0177] Step 701: The message processing module determines the target processor for processing the push message based on the distribution routing table according to the capability list of the push message. When the target processor is the coprocessor, step 702 is executed; when the target processor is the main processor, step 704 is executed; when the target processor is the main processor and the coprocessor, step 706 is executed.

[0178] Optionally, the message processing module can find the processor corresponding to each capability in the capability list from the distribution routing table. When each processor corresponding to the capability includes the coprocessor, it is determined that the target processor is the coprocessor; when each processor corresponding to the capability does not include the coprocessor, it is determined that the target processor is the main processor; when some processors corresponding to the capability include the coprocessor, it is determined that the target processor is the main processor and the coprocessor.

[0179] Step 702: The message processing module sends the push message to Application A in the coprocessor and executes step 703.

[0180] Step 703: Application A in the coprocessor processes the push message using the capabilities declared in the push message, and this branch process ends.

[0181] Step 704: The message processing module sends the push message to Application A in the main processor and executes step 705.

[0182] Optionally, in order to prevent the main processor from being in a sleep state and unable to receive the push message, before this step is executed, the coprocessor can send a wake-up signal to the main processor. If the main processor is in a sleep state, the main processor is woken up by this wake-up signal. After that, Application A in the main processor can receive the push message sent by the message processing module in the coprocessor.

[0183] Step 705: Application A in the main processor processes the push message using the capabilities declared in the push message, and this branch process ends.

[0184] Step 706: The message processing module sends the push message to Application A of the main processor and Application A of the coprocessor respectively, and executes Step 707.

[0185] Step 707: Application A of the coprocessor processes the push message using the capabilities supported by the coprocessor among the capabilities declared to be used by the push message, and Application A of the main processor processes the push message using the capabilities not supported by the coprocessor among the capabilities declared to be used by the push message, and this branch process ends.

[0186] Optionally, in this step, Application A of the coprocessor can use a method similar to that of the message processing module to determine the capabilities declared to be used by the push message and the capabilities supported by the coprocessor among them, so as to process the push message using the corresponding capabilities; Application A of the main processor can use a method similar to that of the message processing module to determine the capabilities declared to be used by the push message and the capabilities supported by the coprocessor among them, and then obtain the capabilities not supported by the coprocessor among the capabilities declared to be used by the push message, so as to process the push message using the corresponding capabilities.

[0187] In some other embodiments provided by the present application, in order to save processing resources and improve processing efficiency, when determining that the target processors are the main processor and the coprocessor, the message processing module in the above embodiments can divide the capability list of the push message into capability sub-list 1 and capability sub-list 2 based on the processors corresponding to each capability found in the distribution routing table. Capability sub-list 1 records the capabilities supported by the coprocessor among the capabilities declared to be used by the push message, and capability sub-list 2 records the capabilities not supported by the coprocessor among the capabilities declared to be used by the push message. For example, if the push message declares the use of text display capability and video playback capability, while the MCU only has text display capability and does not have video playback capability, and the AP has video playback capability, then capability sub-list 1 can include text display capability, and capability sub-list 2 can include video playback capability. In Step 706, when the message processing module sends the push message to Application A of the main processor, it can send the above capability sub-list 2 at the same time, and when sending the push message to Application A of the coprocessor, it can send the above capability sub-list 1 at the same time; thus, in Step 707, Application A of the main processor and Application A of the coprocessor do not need to determine the capabilities they need to use from the push message, improving the processing efficiency of the two Application As for the push message.

[0188] It can be understood that the union of the above capability sub-list 1 and capability sub-list 2 is the capability list, and the above capability sub-list 2 is the part of the capability list except capability sub-list 1.

[0189] In some other embodiments provided by the present application, when the message processing module determines that the target processor is the main processor and the coprocessor, it may also not send the above-mentioned capability sub-list 1 and capability sub-list 2. Instead, the push message is split into push message 1 and push message 2 according to the capabilities respectively used by the main processor and the coprocessor to process the push message. Push message 1 is the partial message content corresponding to the capabilities supported by the coprocessor in the push message, and push message 2 is the partial message content corresponding to the capabilities not supported by the coprocessor but supported by the main processor in the push message. Thus, in step 706, the message processing module may send push message 1 to application A of the coprocessor and send push message 2 to application A of the main processor. Correspondingly, in step 707, application A of the coprocessor processes push message 1, and application B of the main processor processes push message 2.

[0190] Taking the following push message as an example:

[0191] {

[0192] "aps":{

[0193] "alert":"message"

[0194] "badge":9

[0195] "sound":"default"

[0196] },

[0197] "parm1":"bar"

[0198] "parm2":2

[0199] }

[0200] Assume that the coprocessor only supports the "speaker" capability and the main processor supports the "display screen" capability. Then, this push message can be split into the following push message 1 and push message 2.

[0201] Push message 1 is:

[0202] {

[0203] "aps":{

[0204] "sound":"default"

[0205] },

[0206] "parm1":"bar"

[0207] "parm2":2

[0208] Push message 2 is:

[0209] {

[0210] "aps":{

[0211] "alert":"message"

[0212] "badge":9

[0213] },

[0214] "parm1":"bar"

[0215] "parm2":2

[0216] In some other embodiments provided in the present application, when the message processing module determines that the target processors are the main processor and the coprocessor, it may also not split the push message or the capability list. Instead, before sending the push message to the main processor and the coprocessor in step 706, it marks the push message according to the capabilities respectively used by the main processor and the coprocessor to process the push message. Thus, in step 707, the main processor and the coprocessor can determine the capabilities they need to use in the push message based on the marks, and then process the push message.

[0217] In one example, the message processing module may use different marks in the same push message to indicate the parts of the message content that the main processor and the coprocessor need to process respectively.

[0218] Taking the following push message as an example:

[0219] {

[0220] "aps":{

[0221] "alert":"message"

[0222] "badge":9

[0223] "sound":"default"

[0224] },

[0225] "parm1":"bar"

[0226] "parm2":2

[0227] }

[0228] Assume that the coprocessor only supports the "speaker" capability and the main processor supports the "display screen" capability. Then, the part of the message content corresponding to the "speaker" capability in the push message can be indicated by mark 1, and the part of the message content corresponding to the "display screen" capability in the push message can be indicated by mark 2. The marked push message is shown as follows:

[0229] {

[0230] "aps":{

[0231] "alert":"message" / / Δ

[0232] "badge":9 / / Δ

[0233] "sound":"default" / / √

[0234] },

[0235] "parm1":"bar"

[0236] "parm2":2

[0237] }

[0238] Among them, √ indicates flag 1, Δ indicates flag 2, and the unmarked part can indicate that both processors perform processing.

[0239] It should be noted that the above flags Δ and √ are only examples, and the specific implementation of flag 1 and flag 2 is not limited in the embodiments of the present application.

[0240] In another example, the message processing module can use flag a in the push message sent to the main processor to indicate the part of the message content that the main processor needs to process, and use flag b in the push message sent to the coprocessor to indicate the part of the message content that the coprocessor needs to process. Flag a and flag b can be the same or different flags, which are not limited in the embodiments of the present application.

[0241] Continuing with the above example of the push message, the push message sent to the main processor is as follows:

[0242] {

[0243] "aps":{ / / Δ

[0244] "alert":"message" / / Δ

[0245] "badge":9 / / Δ

[0246] "sound":"default"

[0247] }

[0248] "parm1":"bar" / / Δ

[0249] "parm2":2 / / Δ

[0250] }

[0251] Among them, Δ represents tag a. The tagged part of the message content in the push message indicates that the main processor needs to process it, and the untagged part of the message content in the push message indicates that the main processor does not need to process it.

[0252] The push message sent to the coprocessor is as follows:

[0253] {

[0254] "aps":{ / / Δ

[0255] "alert":"message"

[0256] "badge":9

[0257] "sound":"default" / / Δ

[0258] }

[0259] "parm1":"bar" / / Δ

[0260] "parm2":2 / / Δ

[0261] }

[0262] Among them, Δ represents tag b. The tagged part of the message content in the push message indicates that the coprocessor needs to process it, and the untagged part of the message content in the push message indicates that the coprocessor does not need to process it.

[0263] In the above embodiment of the present application, after the communication chip receives the push message, the coprocessor parses and routes the push message. When the coprocessor has all the capabilities declared for use in the push message, Application A in the coprocessor can directly call the capabilities in the coprocessor to process the push message. In the whole process, only the coprocessor needs to be awakened, and there is no need to awaken the main processor to implement the processing of the push message, thereby reducing the number of times the main processor is awakened, reducing the power consumption of the electronic device, and extending the standby time of the electronic device.

[0264] Combined with Figure 5 the structure of the electronic device shown, in another embodiment of the push message processing method provided by the present application, the main processor and the coprocessor can cooperate to process the push message. The difference from the previous embodiment is:

[0265] In the previous embodiment, if the coprocessor only has some of the capabilities declared for use in the push message, the coprocessor calls the above-mentioned partial capabilities to process the push message, and the main processor calls the other capabilities declared for use in the push message to process the push message;

[0266] In this embodiment, if the coprocessor only has some of the capabilities declared for push message usage, but the main processor has all the capabilities declared for push message usage, the main processor is called to handle the push message using the capabilities declared for push message usage;

[0267] If both the main processor and the coprocessor only have some of the capabilities declared for push message usage, the coprocessor is called to handle the push message using the part of the capabilities it has declared for push message usage, and the main processor is called to handle the push message using the other capabilities declared for push message usage; or, if both the coprocessor and the main processor only have some of the capabilities declared for push message usage, the main processor is called to handle the push message using the part of the capabilities it has declared for push message usage, and the coprocessor is called to handle the push message using the other capabilities declared for push message usage.

[0268] For example, assume that the capabilities declared for push message usage include text display capability, audio playback capability, and badge display capability. Then: If the MCU has the above three capabilities, regardless of whether the AP has the above three capabilities, the MCU is preferentially called to handle the push message using the above three capabilities; if the MCU does not have the above three capabilities, the AP is called to handle the push message using the above three capabilities. If the MCU has the text display capability but the AP has the above three capabilities, the AP is called to handle the push message using the above three capabilities; if the MCU has the text display capability and the audio playback capability, and the AP has the audio playback capability and the badge display capability, then the MCU can be called to handle the push message using the text display capability and the audio playback capability, and the AP can be called to handle the push message using the badge display capability, or the MCU can be called to handle the push message using the text display capability, and the AP can be called to handle the push message using the audio playback capability and the badge display capability.

[0269] Optionally, to ensure that the main processor and the coprocessor can cooperate to handle all push messages, the union of the capability set 1 of the main processor and the capability set 2 of the coprocessor can be the set of all capabilities that can be declared for push message usage in the electronic device. There can be an intersection or no intersection between the capability set 2 of the coprocessor and the capability set 1 of the main processor.

[0270] The specific implementation of the embodiments of this application can still refer to Figure 7 the process shown, with the main difference being:

[0271] Step 701 in the embodiments of this application can specifically include:

[0272] The message processing module can find the processors corresponding to each capability in the capability list from the distribution routing table; when each processor corresponding to a capability includes a coprocessor, it is determined that the target processor is the coprocessor; when each processor corresponding to a capability does not include a coprocessor, it is determined that the target processor is the main processor; when some processors corresponding to capabilities include coprocessors, but each processor corresponding to a capability includes a main processor, it is determined that the target processor is the main processor; when some processors corresponding to capabilities include coprocessors and some processors corresponding to capabilities include main processors, it is determined that the target processor is the main processor and the coprocessor.

[0273] In this embodiment, the coprocessor is given priority to process the push message. When the coprocessor does not have all the capabilities declared for using the push message, the main processor processes the push message alone or cooperates with the coprocessor to process the push message, so that the number of times the main processor is woken up can be reduced, the power consumption of the electronic device can be reduced, and the standby time of the electronic device can be extended.

[0274] In the foregoing embodiment, taking the electronic device with a main processor and one coprocessor set to process the push message as an example, in other embodiments provided in this application, two or more coprocessors can be set in the electronic device to process the push message, and the specific number of coprocessors is not specifically limited in the embodiments of this application. At this time, Application A can be set in the main processor and multiple coprocessors, and a message processing module can be set in one of the coprocessors (hereinafter referred to as the main coprocessor), and the push message is routed to Application A of the target processor through this message processing module for processing. It can be understood that the target processor here can be one or more processors, which is not limited in the embodiments of this application. When the message processing module determines the target processor, the priority relationship between the processors can be: main coprocessor (the coprocessor including the message processing module) > other coprocessors > main processor.

[0275] For example Figure 8 In, taking the electronic device with a main processor (such as an AP), coprocessor 1 (such as MCU1) and coprocessor 2 (such as MCU2) in total of 3 processors set to process the push message as an example, coprocessor 1 among them can correspond to Figure 5 the coprocessor in. Different from Figure 5 the structure of the electronic device shown, in the embodiments of this application, the message processing module in coprocessor 1 can route the push message to Application A of coprocessor 1, Application A of coprocessor 2 and / or Application A of the main processor. Optionally, in this embodiment, the priority of the processors to process the push message can be coprocessor 1 > coprocessor 2 > main processor.

[0276] In an embodiment of the push message processing method provided in this application, if the main processor and the coprocessor do not cooperate in processing push messages, the message processing module in coprocessor 1 can preferentially route the push message to application A in coprocessor 1 for processing based on the above priorities, so that only coprocessor 1 needs to be woken up, reducing power consumption. When coprocessor 1 cannot process the push message, it is then routed to coprocessor 2 or the main processor for processing. When both coprocessor 2 and the main processor can process the push message, it is preferentially routed to coprocessor 2 for processing, so as to preferentially use coprocessor 2 with relatively lower power consumption to process push messages, thereby reducing the processing power consumption of push messages.

[0277] Figure 9 is based on Figure 8 A schematic flowchart of the push message processing method according to an embodiment of this application provided based on the electronic device structure shown, as Figure 9 shown, the main difference between this method and Figure 6 the method shown is mainly that: due to the addition of coprocessor 2, compared with Figure 6 step 604 in, step 901 in this embodiment adds a branch where the target processor is coprocessor 2, so that steps 604 to 608 are replaced by the following steps 901 to step 907.

[0278] Step 901: The message processing module determines the target processor for processing the push message based on the distribution routing table according to the ability list of the push message. When the target processor is coprocessor 1, step 902 is executed. When the target processor is coprocessor 2, step 904 is executed. When the target processor is the main processor, step 906 is executed.

[0279] Optionally, the message processing module can find the processor corresponding to each ability in the ability list from the distribution routing table. When coprocessor 1 is included in the processors corresponding to each ability, it is determined that the target processor is coprocessor 1. When coprocessor 1 is not included in at least one of the processors corresponding to the abilities, and coprocessor 2 is included in the processors corresponding to each ability, it is determined that the target processor is coprocessor 2. When coprocessor 1 and coprocessor 2 are not included in the processors corresponding to some of the abilities, it is determined that the target processor is the main processor.

[0280] Steps 902 - 903: The message processing module sends the push message to application A in coprocessor 1, and application A in coprocessor 1 processes the push message using the abilities declared in the push message, and this branch process ends.

[0281] Steps 904 - 905: The message processing module sends the push message to application A in coprocessor 2, and application A in coprocessor 2 processes the push message using the abilities declared in the push message, and this branch process ends.

[0282] Optionally, in order to prevent the coprocessor 2 from entering the sleep state and being unable to receive push messages, before sending a push message, the coprocessor 1 can send a wake-up signal to the coprocessor 2. If the coprocessor 2 is in the sleep state, the coprocessor 2 is woken up by the wake-up signal. After that, Application A in the coprocessor 2 can receive the push message sent by the message processing module in the coprocessor 1.

[0283] Steps 906 - 907: The message processing module sends the push message to Application A of the main processor. Application A of the main processor processes the push message using the capabilities declared in the push message, and this branch of the process ends.

[0284] In this method, after the communication chip receives a push message, the message processing module of the coprocessor 1 parses and routes the push message. When the coprocessor 1 has all the capabilities declared in the push message, Application A in the coprocessor 1 can directly process the push message using the capabilities in the coprocessor. When the coprocessor 1 does not have all the capabilities declared in the push message but the coprocessor 2 has all the capabilities declared in the push message, the push message is routed to Application A of the coprocessor 2 for processing. In the whole process, only the coprocessor needs to be woken up, and there is no need to wake up the main processor to implement the processing of the push message, thereby reducing the number of times the main processor is woken up, reducing the power consumption of the electronic device, and extending the standby time of the electronic device.

[0285] In another embodiment of the push message processing method provided in this application, if the main processor and the coprocessor cooperate to process the push message, based on the above priorities, the message processing module in the coprocessor 1 can preferentially route the push message to Application A of the coprocessor 1 and / or Application A of the coprocessor 2 for processing; when the coprocessor is unable to process the push message, it is then routed to the main processor for processing.

[0286] Figure 10 is based on Figure 8 A schematic flowchart of a push message processing method according to an embodiment of this application provided based on the structure of the electronic device shown, the difference from the embodiment shown in Figure 7 is mainly that: due to the addition of the coprocessor 2, compared with step 701 in Figure 7 , step 1001 in this embodiment adds branches where the target processor is the coprocessor 2 and the coprocessors that cooperate to process the push message include the coprocessor 2, thereby replacing steps 701 - 707 with the following steps 1001 - step 1015.

[0287] Specifically, in step 1001, when the message processing module of coprocessor 1 determines the target processor for processing the push message based on the distribution routing table according to the capability list of the push message, the determined target processor can be: coprocessor 1, coprocessor 2, main processor, coprocessor 1 and coprocessor 2, coprocessor 2 and main processor, coprocessor 1 and main processor, coprocessor 1, coprocessor 2 and main processor, etc. Thus, in subsequent steps, the message processing module of coprocessor 1 can route the push message to application A of the target processor, and application A of the target processor processes the push message.

[0288] For the specific implementation of this embodiment, reference can be made to the related embodiments in which the electronic device includes a main processor and a coprocessor, and the main processor and the coprocessor can cooperate to process push messages, which will not be elaborated here.

[0289] In other embodiments provided by this application, the message processing module in the above embodiment can also be disposed in the communication chip controller of the communication chip. For example Figure 11 as shown, taking Figure 5 the message processing module in the shown electronic device structure being disposed in the communication chip controller of the communication chip as an example. At this time, for the implementation of the push message processing method in the embodiments of this application, reference can be made to the foregoing embodiments, which will not be elaborated here.

[0290] In other embodiments provided by this application, a routing processor can be connected between the communication chip and each processor in the above embodiment, and the message processing module can be disposed in the routing processor. For example Figure 12 as shown, taking Figure 5 the message processing module in the shown electronic device structure being disposed in the routing processor as an example. At this time, for the implementation of the push message processing method in the embodiments of this application, reference can be made to the foregoing embodiments, which will not be elaborated here. Optionally, the above routing processor can be implemented by a low-power processor such as an MCU.

[0291] In another embodiment of the push message processing method provided by this application, the push message sent by the push server to the electronic device can carry identification information, and the identification information can be a capability identifier for indicating the capabilities required for the push message, or an identifier for indicating the target processor for processing the push message, hereinafter simply referred to as the target processor identifier.

[0292] The following are exemplary descriptions respectively.

[0293] In some embodiments, the push message sent by the push server to the electronic device may carry an ability identifier, and the ability identifier is used to indicate the ability required for the push message. At this time, the message processing module in the above embodiments does not need to identify the ability declared by the push message through the keywords in the push message, and can directly obtain the ability declared by the push message by obtaining the ability identifier from the push message.

[0294] The ability required for the push message may correspond to the hardware ability or software running ability of the above-mentioned processor, which will not be elaborated here.

[0295] In some embodiments, the push server may also use the above methods such as searching for keywords to identify the ability declared by the push message of life, and set the identifier of the above ability in the push message. The specific implementation can refer to the corresponding description above and will not be elaborated here.

[0296] The present application embodiments do not limit the setting position of the ability identifier in the push message, as long as it is predefined between the push server and the electronic device, so that the electronic device can obtain the ability identifier from the push message.

[0297] In some embodiments, the ability identifier can be set in the push message as a parameter of the push message. For example, taking the following push message as an example:

[0298] {

[0299] "aps":{

[0300] "alert":"message"

[0301] "badge":9

[0302] "sound":"default"

[0303] "abilityID":"1,3"

[0304] },

[0305] "parm1″:"bar"

[0306] "parm2″:2

[0307] }

[0308] The 1, 3 corresponding to abilityID therein is the ability identifier, for example, it can respectively identify the "display screen" ability and the "speaker" ability.

[0309] In some embodiments, the push message sent by the push server to the electronic device may carry a target processor identifier. At this time, the message processing module in the above embodiments does not need to identify the capabilities declared in the push message, nor does it need to determine the target server based on the distribution routing table. It only needs to obtain the target processor identifier from the push message and determine the target processor according to the target processor identifier. The position where the target processor identifier is set in the push message is not limited in the embodiments of the present application, as long as it is predefined between the push server and the electronic device, so that the electronic device can obtain the capability identifier from the push message.

[0310] In some embodiments, the target processor identifier may be set as a parameter in the push message. For example, taking the following push message as an example:

[0311] {

[0312] "aps":{

[0313] "alert":"message"

[0314] "badge":9

[0315] "sound":"default"

[0316] "CPUID":"1"

[0317] },

[0318] "parm1″:"bar"

[0319] "parm2″:2

[0320] }

[0321] The "1" corresponding to the CPUID here is the target processor identifier. For example, when the electronic device is implemented through the Figure 5 shown structure, "1" can identify Figure 5 the coprocessor in it as the target processor.

[0322] In some embodiments, if the target processor identifier carried in the push message sent by the push server to the electronic device indicates at least two target processors, the push server may perform processing such as partitioning and / or identifying the message content in the push message, so that the electronic device can know the message content required to be processed by each target processor.

[0323] In one example, the push message can divide the push message content according to the push messages that each target processor needs to process, and respectively identify the target servers corresponding to each part of the message content. Correspondingly, the message processing module in the electronic device can split the push message into sub-messages and send them to the corresponding target processors for processing respectively; alternatively, after the message processing module in the electronic device sends the push message to Application A of the target processor, Application A of each target processor can obtain the message content it needs to process from the push message and process it.

[0324] Take the following push message as an example:

[0325] {

[0326] "aps":{

[0327] "alert":"message"

[0328] "badge":9

[0329] "sound":"default"

[0330] },

[0331] "parm1":"bar"

[0332] "parm2":2

[0333] }

[0334] Assume that the coprocessor only supports the "speaker" capability and the main processor supports the "display screen" capability. Then, the push message content can be split and represented to obtain the following push message.

[0335] {

[0336] "aps":{

[0337] "sound":"default"

[0338] "CPUID":"1"

[0339] },

[0340] "parm1":"bar"

[0341] "parm2":2

[0342] { / / / / Boundary between the two parts of the message content

[0343] "aps":{

[0344] "alert":"message"

[0345] "badge": 9

[0346] "CPUID": "2"

[0347] },

[0348] "parm1": "bar"

[0349] "parm2": 2

[0350] Among them, the first part of the message content has the ID "1" of the coprocessor and is executed by the coprocessor. The second part of the message content has the ID "2" of the main processor and is executed by the main processor.

[0351] In another example, the push message can be marked correspondingly according to the content of the push message that each target processor needs to process. Accordingly, the message processing module in the electronic device can split the push message into sub-messages according to different marks and send them to the corresponding target processors for processing respectively; or, after the message processing module in the electronic device sends the push message to Application A of the target processor, Application A of each target processor can obtain the message content it needs to process from the push message according to its corresponding mark and process it.

[0352] Continuing the example of the foregoing push message, the marked push message is as follows:

[0353] {

[0354] "aps": {

[0355] "alert": "message" / / Δ

[0356] "badge": 9 / / Δ

[0357] "sound": "default" / / √

[0358] },

[0359] "parm1": "bar"

[0360] "parm2": 2

[0361] }

[0362] Among them, √ represents Mark 1, which is used to mark the content of the push message that the coprocessor needs to process. Δ represents Mark 2, which is used to mark the content of the push message that the main processor needs to process. The unmarked part can indicate that both processors need to process.

[0363] In some embodiments, in order for the push server to obtain information about the processor set in the electronic device and information about the capabilities of the processor, so that it can accurately indicate the target processor for the electronic device, the electronic device may send the above information to the push server. Specifically, for example, it may be sent during Figure 3 the registration process shown above.

[0364] Since information such as the brand and model of the electronic device can also be associated with the information about the processor set in the electronic device and the information about the capabilities of the processor, in some embodiments, the electronic device may not send the above information about the processor and its capabilities to the push server, but send device information such as the brand and model of the electronic device, which is related to the above information, to the push server for the push server to determine the information about the processor set in the electronic device and the information about the capabilities of the processor based on the above device information.

[0365] In some embodiments, the method for the push server to determine the target server of the push message according to the information about the processor set in the electronic device and the information about the capabilities of the processor can be specifically implemented by using the method for determining the target server of the push message in the aforementioned electronic device.

[0366] The embodiments of the present application also provide a computer-readable storage medium, in which a computer program is stored. When it runs on a computer, it causes the computer to execute the method provided by the embodiments of the present application.

[0367] The embodiments of the present application also provide a computer program product, which includes a computer program. When it runs on a computer, it causes the computer to execute the method provided by the embodiments of the present application.

[0368] In the embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent the situation where A exists alone, A and B exist simultaneously, and B exists alone. Where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the front and back associated objects. "At least one of the following" and its similar expressions refer to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, and c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0369] Those of ordinary skill in the art can realize that the units and algorithm steps described in the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of electronic hardware. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled professionals can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

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

[0371] In several embodiments provided in this application, if any function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can 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 foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memories (hereinafter referred to as ROM), random access memories (hereinafter referred to as RAM), magnetic disks, or optical discs that can store program codes.

[0372] The above is only the specific implementation manner of this application. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application and should be covered by the protection scope of this application. The protection scope of this application shall be subject to the protection scope of the claims.

Claims

1. A method for processing push messages, characterized in that, Applied to an electronic device, the electronic device includes a main processor and a coprocessor; the method includes: The coprocessor receives a push message; The coprocessor processes the push message, or the coprocessor sends the push message to the main processor for the main processor to process the push message.

2. The method according to claim 1, wherein Further includes: The coprocessor determines a target processor from the main processor and the coprocessor according to the push message.

3. The method according to claim 2, characterized in that The push message includes a first identifier, and the coprocessor determines a target processor from the main processor and the coprocessor according to the push message, including: The coprocessor determines the target processor according to the first identifier.

4. The method according to claim 3, wherein The coprocessor determines the target processor according to the first identifier, including: The coprocessor determines the capabilities related to the push message according to the first identifier; Determine the target processor according to the capabilities related to the push.

5. The method according to claim 2, wherein The coprocessor determines a target processor from the main processor and the coprocessor according to the push message, including: The coprocessor parses the push message to determine the capabilities related to the push message; Determine the target processor according to the capabilities related to the push.

6. The method according to claim 5, wherein The coprocessor parses the push message to determine the capabilities related to the push message, including: The coprocessor parses the push message to determine the hardware related to the push message; The determining the target processor according to the capabilities related to the push, including: Determine the target processor according to the hardware related to the push message.

7. The method according to claim 6, wherein The determining the target processor according to the hardware related to the push message, including: Determine the target processor according to whether the hardware connected to the target processor includes the hardware related to the push message.

8. The method according to claim 5, characterized in that, The coprocessor parses the push message to determine the capabilities related to the push message, including: The coprocessor determines the capabilities related to the push message according to the keywords included in the push message.

9. The method according to any one of claims 5 to 8, characterized in that Further includes: Store the mapping relationship between the capabilities and the processors on the coprocessor.

10. The method according to any one of claims 1 to 9, characterized in that, The main processor is an AP, and / or the coprocessor is an MCU.

11. A push message processing method, characterized in that: Applied to an electronic device, the electronic device includes a main processor and a coprocessor; the method includes: Receive a push message; Send the push message to the coprocessor for the coprocessor to process the push message; or send the push message to the main processor for the main processor to process the push message.

12. The method according to claim 11, wherein Further includes: Determine a target processor from the main processor and the coprocessor according to the push message.

13. The method according to claim 12, characterized in that The push message includes a first identifier, and the determining a target processor from the main processor and the coprocessor according to the push message, including: Determine the target processor according to the first identifier.

14. The method according to claim 13, wherein The determining the target processor according to the first identifier, including: Determine the capabilities related to the push message according to the first identifier; Determine the target processor according to the capabilities related to the push.

15. The method according to claim 14, characterized in that The determining the capabilities related to the push message according to the first identifier, including: Determine the hardware related to the push message according to the first identifier.

16. The method according to claim 15, characterized in that Determining the target processor according to the capabilities related to the push includes: Determine the target processor according to whether the hardware connected to the target processor includes the hardware related to the push message.

17. The method according to any one of claims 11 to 16, characterized in that, The main processor is an AP, and / or the coprocessor is an MCU.

18. An electronic device, characterized in that, It includes: A main processor, a coprocessor, and a memory; One or more computer programs are stored in the memory, and the one or more computer programs include instructions that, when executed by the coprocessor, cause the electronic device to execute the method according to any one of claims 1 to 10.

19. An electronic device, characterized in that, It includes: A main processor, a coprocessor, a routing processor, and a memory; One or more computer programs are stored in the memory, and the one or more computer programs include instructions that, when executed by the routing processor, cause the electronic device to execute the method according to any one of claims 11 to 17.

20. A computer-readable storage medium, characterized in that, A computer program is stored in the computer-readable storage medium, and when it runs on a computer, it causes the computer to execute the method according to any one of claims 1 to 17.

21. A chip system, characterized in that, The chip system includes a processor, the processor is coupled to a memory, and the processor executes a computer program stored in the memory to implement the method according to any one of claims 1 to 17.

Images