Service pushing method, service pushing system and electronic device

Abstract

The application provides a service pushing method, a service pushing system and an electronic device. The method comprises: analyzing received to-be-pushed data to determine a trigger creation condition of the to-be-pushed data, wherein the trigger creation condition indicates that the to-be-pushed data meets a pushing demand of a user; when the trigger creation condition is met, creating a trigger of the to-be-pushed data, wherein the trigger is used to monitor whether a pre-trigger event of the to-be-pushed data is met; when the trigger is triggered, creating a pushing condition of the to-be-recommended data; and when the pushing condition is met, pushing the to-be-pushed data. The service pushing method of the application embodiment judges whether to push data at a terminal side, and the accuracy of service pushing can be improved by multiple judgment settings of a trigger creation condition, a trigger and a pushing condition, and pushing is performed according to user habits at the terminal locally, compared with service pushing according to user tags at a server.

Description

Technical Field

[0001] This application relates to the field of data push technology, specifically to service push methods, service push systems, and electronic devices. Background Technology

[0002] In related service push methods, user tags are created in the cloud, and the target audience for the content to be pushed is identified based on these tags. The content is then pushed to the corresponding user's terminal devices. Upon receiving the content, the terminal device displays it directly. However, pushing services solely based on user tags can lead to inaccurate service delivery; for example, a service might be pushed to a user when they do not need it. Summary of the Invention

[0003] In view of this, this application provides a service push method, a service push system, and an electronic device to improve the accuracy of service push.

[0004] In a first aspect of this application, a service push method is applied to a terminal, the method comprising:

[0005] The received data to be pushed is analyzed to determine the trigger creation conditions for the data to be pushed, wherein the trigger creation conditions indicate that the data to be pushed meets the user's push requirements;

[0006] When the trigger creation conditions are met, a trigger for the data to be pushed is created, wherein the trigger is used to monitor whether the pre-trigger event for the data to be pushed is met;

[0007] When the trigger is activated, the conditions for pushing the data to be recommended are created;

[0008] When the push conditions are met, the data to be pushed is pushed.

[0009] The service push method of this application determines whether to push data on the terminal side, and performs the push locally on the terminal according to user habits by setting multiple judgment conditions for trigger creation and trigger and push conditions. Compared with service push based on user tags on the server side, it can improve the accuracy of service push.

[0010] In one possible implementation, the data to be pushed includes a creation condition type and creation condition parameters; the step of analyzing the received data to be pushed to determine the trigger creation conditions for the data to be pushed includes:

[0011] The received data to be pushed is parsed to obtain the creation condition type and creation condition parameters of the data to be pushed;

[0012] Based on the creation condition type and creation condition parameters of the data to be pushed, generate the trigger creation conditions for the data to be pushed.

[0013] By utilizing the creation condition type and parameters of the data to be pushed, trigger creation conditions can be accurately generated, enabling the determination of trigger creation conditions locally on the terminal. Compared to service push based on user tags on the server side, this improves the accuracy of service push.

[0014] In one possible implementation, the data to be pushed includes a trigger type and trigger parameters; the step of creating a trigger for the data to be pushed when the trigger creation conditions are met includes: creating a trigger for the data to be pushed according to the trigger type and trigger parameters of the data to be pushed when the trigger creation conditions are met.

[0015] By utilizing the trigger type and trigger parameters of the data to be pushed, triggers can be accurately generated, enabling trigger determination locally on the terminal. This improves the accuracy of service push compared to pushing services based on user tags on the server side.

[0016] In one possible implementation, the data to be pushed includes a push condition type and push condition parameters; when the trigger is triggered, creating push conditions for the data to be recommended includes: when the trigger is triggered, creating push conditions for the data to be pushed according to the push condition type and push condition parameters of the data to be pushed.

[0017] By utilizing the push condition type and parameters of the data to be pushed, push conditions can be accurately determined, thus enabling the determination of push conditions locally on the terminal. Compared to pushing services based on user tags on the server side, this improves the accuracy of service push.

[0018] In one possible implementation, the data to be pushed includes an action type and action parameters; pushing the data to be pushed when the push condition is met includes:

[0019] When the push conditions are met, a push action is created based on the action type and action parameters of the data to be pushed.

[0020] When the trigger operation of the push action is detected, the push action is executed to push the data to be pushed.

[0021] By utilizing the action type and action parameters of the data to be pushed, the action can be pushed accurately, thus enabling the push of the data to be pushed locally on the terminal, which can meet various push action requirements.

[0022] In one possible implementation, the push action is a card dispensing action; the data to be pushed includes card type and card parameters;

[0023] The step of executing the push action to push the data to be pushed when the trigger operation of the push action is detected includes:

[0024] When a trigger operation for the push action is detected, a target card is generated based on the card type and card parameters of the data to be pushed.

[0025] The target card is rendered and displayed in the display area corresponding to the touch point.

[0026] By generating a target card using the card type and card parameters of the data to be pushed, and rendering and displaying the target card in the display area corresponding to the touch point, the system enables the data to be pushed in the form of a card, which can complete the push of the data in a simple and intuitive way.

[0027] In one possible implementation, the method further includes:

[0028] In response to changes in user push requests, determine whether the trigger creation conditions are met.

[0029] After the terminal receives the data to be pushed, even if the user does not have a push request at that time, the push request can still be monitored locally on the terminal. When the user's push request changes, it is determined whether the trigger creation conditions are met. If they are met, a trigger for the data to be pushed is created, realizing on-demand service push and improving the accuracy of service push.

[0030] Secondly, embodiments of this application provide a service push system, the system comprising: a server and a terminal;

[0031] The server sends the data to be pushed to the terminal;

[0032] The terminal is configured to analyze the received data to be pushed, determine the trigger creation conditions for the data to be pushed, wherein the trigger creation conditions indicate that the data to be pushed meets the user's push requirements; when the trigger creation conditions are met, a trigger for the data to be pushed is created, wherein the trigger is used to monitor whether the pre-triggered event of the data to be pushed is met; when the trigger is triggered, push conditions for the data to be recommended are created; when the push conditions are met, the data to be pushed is pushed.

[0033] The service push system of this application determines whether to push data on the terminal side, and performs push according to user habits on the terminal local through trigger creation conditions, trigger and push conditions multiple judgment settings. Compared with service push based on user tags on the server side, it can improve the accuracy of service push.

[0034] In one possible implementation, the terminal is further configured to send its identification information to the server after the IoT platform is started.

[0035] The server is specifically used to authenticate the terminal based on the terminal's identification information, and after successful authentication, to send the data to be pushed to the terminal.

[0036] In this embodiment of the application, data security can be improved by authenticating the terminal.

[0037] In one possible implementation, the server includes an operations cloud, a device cloud, and a push cloud;

[0038] The operation cloud is used to respond to the push configuration operation, generate corresponding push data, and send the push data to the device cloud;

[0039] The device cloud is used to authenticate the terminal based on the terminal's identification information, and after successful authentication, send the data to be pushed to the push cloud.

[0040] The push cloud is used to send data to be pushed to the terminal.

[0041] In this embodiment of the application, the division into operation cloud, device cloud and push cloud facilitates push management on the server side.

[0042] In one possible implementation, the data to be pushed includes a creation condition type and creation condition parameters; the terminal is specifically used to: parse the received data to be pushed to obtain the creation condition type and creation condition parameters of the data to be pushed; and generate trigger creation conditions for the data to be pushed based on the creation condition type and creation condition parameters of the data to be pushed.

[0043] By utilizing the creation condition type and parameters of the data to be pushed, trigger creation conditions can be accurately generated, enabling the determination of trigger creation conditions locally on the terminal. Compared to service push based on user tags on the server side, this improves the accuracy of service push.

[0044] In one possible implementation, the data to be pushed includes a trigger type and trigger parameters; the terminal is specifically used to: when the trigger creation conditions are met, create a trigger for the data to be pushed according to the trigger type and trigger parameters of the data to be pushed;

[0045] By utilizing the trigger type and trigger parameters of the data to be pushed, triggers can be accurately generated, enabling trigger determination locally on the terminal. This improves the accuracy of service push compared to pushing services based on user tags on the server side.

[0046] In one possible implementation, the data to be pushed includes a push condition type and push condition parameters; the terminal is specifically used to: when the trigger is triggered, create push conditions for the data to be pushed according to the push condition type and push condition parameters of the data to be pushed.

[0047] By utilizing the push condition type and parameters of the data to be pushed, push conditions can be accurately determined, thus enabling the determination of push conditions locally on the terminal. Compared to pushing services based on user tags on the server side, this improves the accuracy of service push.

[0048] In one possible implementation, the data to be pushed includes an action type and action parameters; the terminal is specifically used to: when the push condition is met, create a push action for the push condition based on the action type and action parameters of the data to be pushed; and when the triggering operation of the push action is detected, execute the push action to push the data to be pushed.

[0049] By utilizing the action type and action parameters of the data to be pushed, the action can be pushed accurately, thus enabling the push of the data to be pushed locally on the terminal, which can meet various push action requirements.

[0050] In one possible implementation, the push action is a card dispensing action; the data to be pushed includes card type and card parameters;

[0051] The terminal is specifically used to: when a trigger operation for the push action is detected, generate a target card according to the card type and card parameters of the data to be pushed; and render and display the target card in the display area corresponding to the touch point.

[0052] By generating a target card using the card type and card parameters of the data to be pushed, and rendering and displaying the target card in the display area corresponding to the touch point, the system enables the data to be pushed in the form of a card, which can complete the push of the data in a simple and intuitive way.

[0053] In one possible implementation, the terminal is further configured to determine whether the trigger creation conditions are met in response to a change in the user's push request.

[0054] After the terminal receives the data to be pushed, even if the user does not have a push request at that time, the push request can still be monitored locally on the terminal. When the user's push request changes, it is determined whether the trigger creation conditions are met. If they are met, a trigger for the data to be pushed is created, realizing on-demand service push and improving the accuracy of service push.

[0055] In a third aspect of this application, an electronic device is provided, comprising:

[0056] One or more processors and memory;

[0057] The memory is coupled to the one or more processors, and the memory is used to store computer program code, the computer program code including computer instructions, which the one or more processors call to cause the electronic device to perform the steps of the method described in the first aspect above.

[0058] The electronic device in this application determines whether to push data on the terminal side, and performs the push locally on the terminal according to user habits by setting multiple judgment conditions for trigger creation and trigger and push conditions. Compared with service push based on user tags on the server side, it can improve the accuracy of service push. Attached Figure Description

[0059] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0060] Figure 1 This is a schematic diagram of a service push method in related technologies;

[0061] Figure 2 This is a schematic diagram of an electronic device according to an embodiment of this application;

[0062] Figure 3 This is a schematic diagram of the software framework of an electronic device according to an embodiment of this application;

[0063] Figure 4 This is a schematic diagram of a service push method according to an embodiment of this application;

[0064] Figure 5 This is a first schematic diagram of a service push system according to an embodiment of this application;

[0065] Figure 6 This is a second schematic diagram of a service push system according to an embodiment of this application;

[0066] Figure 7 This is a third schematic diagram of the service push system according to an embodiment of this application;

[0067] Figure 8 This is a schematic diagram illustrating the process of creating trigger creation conditions in an embodiment of this application. Detailed Implementation

[0068] To better understand the technical solution of this application, the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0069] It should be understood that the described embodiments are merely some, not all, of the embodiments in this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.

[0070] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. The singular forms “a,” “the,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0071] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0072] Service push methods in related technologies, such as Figure 1 As shown, the cloud server configures the content to be pushed and selects the user tags that will benefit from it. Based on the user tags, it determines the target audience for the content and then pushes the content to the corresponding user's terminal devices. Upon receiving the content, the terminal device displays it directly. However, in most cases, relying solely on user tags to push services can lead to inaccurate service delivery.

[0073] On the one hand, user tags have a weak ability to identify users' actual needs and cannot accurately identify user requirements. For example, if a service provider wants to recommend smart air conditioning services or compatible air conditioning companion products to users who want to use air conditioning, the push service in related technologies can only select users with air conditioning and those without based on user tags, pushing the service to users with air conditioning. It cannot accurately push the service to users when they want to use air conditioning. Pushing the service to users when they do not need it will only bother them.

[0074] On the other hand, the system can only make judgments based on the user tags at the time of the push notification. When the user attributes change, the system can no longer push notifications to the user. For example, the cloud server recommends air conditioning services in September, but user A does not have an air conditioner in September. However, this does not mean that user A will never have an air conditioner. It is possible that after a period of time, such as in November, user A will purchase an air conditioner. However, because the cloud server has already passed the push notification period for air conditioning services, it will not be able to push the air conditioning service that user A might need.

[0075] To address at least one of the aforementioned problems, embodiments of this application provide a service push method, a service push system, and an electronic device. These are described in detail below:

[0076] In a first aspect, this application also provides an electronic device comprising:

[0077] One or more processors and memory;

[0078] The memory is coupled to the one or more processors, and the memory is used to store computer program code, the computer program code including computer instructions, which the one or more processors invoke to cause the electronic device to perform the service push method described in any one of the present applications.

[0079] In one example, the structural schematic diagram of the electronic device provided in this application embodiment can be as follows: Figure 2 As shown, the electronic device can be a mobile phone, a tablet computer, or other user terminals.

[0080] The electronic device includes a processor 110, a transceiver 120, and a display unit 170. The display unit 170 may include a display screen.

[0081] Optionally, the electronic device may also include a memory 130. The processor 110, transceiver 120 and memory 130 can communicate with each other through internal connection paths to transmit control and / or data signals. The memory 130 is used to store computer programs, and the processor 110 is used to call and run the computer programs from the memory 130.

[0082] Optionally, the electronic device may also include an antenna 140 for transmitting wireless signals output by the transceiver 120.

[0083] The processor 110 and memory 130 can be combined into a single processing device, but more commonly they are independent components. The processor 110 executes the program code stored in the memory 130 to achieve the aforementioned functions. In specific implementations, the memory 130 can be integrated into the processor 110, or it can be independent of the processor 110.

[0084] In addition, to further enhance the functionality of the electronic device, it may also include one or more of an input unit 160, an audio circuit 180, a camera 190, and a sensor 101. The audio circuit may also include a speaker 182, a microphone 184, etc.

[0085] Optionally, the above-mentioned electronic device may also include a power supply 150 for providing power to various devices or circuits in the electronic device.

[0086] Understandable, Figure 2 The operation and / or function of each module in the illustrated electronic device are respectively for implementing the corresponding processes in the following method embodiments. For details, please refer to the descriptions in the following method embodiments; detailed descriptions are omitted here to avoid repetition.

[0087] Understandable, Figure 2 The processor 110 in the illustrated electronic device may include one or more processing units, such as 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). Different processing units may be independent devices or integrated into one or more processors. The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or is reusing. If the processor 110 needs to reuse the instruction or data, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves system efficiency.

[0088] In some embodiments, the processor 110 may include one or more interfaces. 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.

[0089] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a limitation on the structure of the electronic device. In other embodiments of this application, the electronic device may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0090] Understandable, Figure 2 The power supply 150 shown provides power to the processor 110, memory 130, display unit 170, camera 190, input unit 160, and transceiver 120, etc. The antenna 140 is used to transmit and receive electromagnetic wave signals. Each antenna in the electronic device can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 140 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in conjunction with a tuning switch.

[0091] Transceiver 120 can provide solutions for wireless communication applications in electronic devices, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. Transceiver 120 can be one or more devices integrating at least one communication processing module. Transceiver 120 receives electromagnetic waves via antenna 140, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. Transceiver 120 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 140.

[0092] In some embodiments, the antenna 140 and transceiver 120 of the electronic device are coupled, enabling the electronic device 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 technologies. 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).

[0093] The electronic device implements display functions through a GPU, a display unit 170, and an application processor. The GPU is a microprocessor for image processing, connecting the display unit 170 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. The processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0094] Display unit 170 is used to display images, videos, etc. Display unit 170 includes a display panel. The display panel may 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 Mini LED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device may include one or N display units 170, where N is a positive integer greater than 1.

[0095] Electronic devices can achieve shooting functions through ISP, camera 190, video codec, GPU, display unit 170 and application processor.

[0096] The ISP (Image Signal Processor) processes data fed back from the camera. For example, when recording video, the camera is turned on, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, which is then transmitted to the ISP for processing, transforming it into a visible image. The ISP can also perform algorithmic optimizations on image noise, brightness, and skin tone.

[0097] The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments, the ISP can be set in the camera 190. The camera 190 is used to capture still images or videos. An object generates an optical image through the lens and projects it onto a photosensitive element. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, and then passes the electrical signal to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, and other formats. In some embodiments, the electronic device may include one or N cameras 190, where N is a positive integer greater than 1. The digital signal processor is used to process digital signals, and can process not only digital image signals but also other digital signals. For example, when the electronic device selects a frequency point, the digital signal processor is used to perform Fourier transforms on the frequency point energy, etc.

[0098] Video codecs are used to compress or decompress digital video. Electronic devices can support one or more video codecs. This allows the electronic device to play or record video in various encoded formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0099] An NPU (Neural Processing Unit) is a computational processor for neural networks (NNs). By borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it can rapidly process input information and continuously learn on its own. NPUs enable intelligent cognitive applications in electronic devices, such as image recognition, facial recognition, speech recognition, and text understanding.

[0100] The memory 130 can be used to store computer executable program code, which includes instructions. The memory 130 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of the electronic device (such as audio data, phonebook, etc.). Furthermore, the memory 130 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the electronic device by running instructions stored in the memory 130 and / or instructions stored in memory disposed within the processor.

[0101] Electronic devices can implement audio functions through audio circuitry 180, speakers 182, microphones 184, and application processors, such as music playback and recording.

[0102] The audio circuit 180 is used to convert digital audio information into analog audio signal output, and also to convert analog audio input into digital audio signal. The audio circuit 180 can also be used for encoding and decoding audio signals. In some embodiments, the audio circuit 180 may be located in the processor 110, or some functional modules of the audio circuit 180 may be located in the processor 110.

[0103] The speaker 182, also known as a "loudspeaker," is used to convert audio electrical signals into sound signals. Electronic devices can listen to music or make hands-free calls through the speaker 182.

[0104] Microphone 184, also known as a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can speak by bringing their voice close to microphone 184, inputting the sound signal into microphone 184. An electronic device may have at least one microphone 184. In some embodiments, the electronic device may have two microphones 184, which, in addition to collecting sound signals, can also perform noise reduction. In other embodiments, the electronic device may have three, four, or more microphones 184, enabling sound signal collection, noise reduction, sound source identification, and directional recording, among other functions.

[0105] like Figure 3 As shown, the software framework of the electronic device involved in this application may include an application layer, an application framework layer (FWK), a system layer, a hardware abstraction layer (HAL), and a kernel layer.

[0106] The application layer can include a series of application packages, such as an IoT (Internet of Things) platform, touchpoints, cameras, photo galleries, calendars, calling, maps, navigation, WLAN, Bluetooth, music, video, and SMS applications (also known as applications). The IoT platform application can interact with the server to obtain data to be pushed and configure the push strategy for that data. The touchpoint application can respond to user triggers to display the data to be pushed.

[0107] like Figure 3 As shown, an IoT middleware application may include an application initialization module, a message receiving module, a message parsing and distribution module, a precondition manager, a trigger manager, a condition manager, an action manager, a card issuance service module, a data management module, and a card management module.

[0108] The application initialization module is responsible for initializing the IoT platform. Upon initial startup of the IoT platform, the application initialization module obtains the user's account login status. If the user is logged in, the module sends the electronic device's ID (identity identifier) ​​and Token to the server to complete authentication negotiation, indicating that the electronic device can receive the data to be pushed. The message receiving module receives data messages sent by the server, which include the data to be pushed. The message parsing and distribution module parses the data messages to obtain the data to be pushed. The precondition manager parses the received data to be pushed to obtain the creation condition type and creation condition parameters. Based on the creation condition type and creation condition parameters, the precondition manager uses a precondition factory to determine the trigger creation conditions for the data to be pushed. When the trigger creation conditions are met, the trigger manager uses a trigger factory to create a trigger for the data to be pushed. After the trigger is triggered, the condition manager uses a condition working module to create push conditions for the data to be recommended, based on the push condition type and push condition parameters. When the push conditions are met, the Action Manager uses the Action Factory to create a push action corresponding to those conditions. For example, the push action could be a card dispensing action. The Action Manager encapsulates the relevant data and delegates the actual execution of the card dispensing action to the card dispensing service module. The card dispensing service module sends the encapsulated data to the data management module for storage. Because the actual card view is only displayed when the user swipes to the corresponding area, the corresponding data is only queried when a touchpoint is triggered, so the data needs to be stored at this time. The card dispensing service module sends a card dispensing message to each corresponding touchpoint based on which touchpoint the card needs to be displayed on. Each touchpoint decides whether to dispense the card based on the actual display situation and the user's triggering operation; for example, when the user swipes to the negative one screen, the negative one screen requests a card view from the IoT platform. The card management module retrieves the corresponding card data from the data management module based on the card identifier in the request, and assembles a formal card view by calling the corresponding resources based on the card type, card parameters, etc., in the card data, and sends the card view to the touchpoint for rendering and display.

[0109] The application framework layer provides an Application Programming Interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0110] like Figure 3As shown, the application framework layer can include the IoT Platform FWK and the Touchpoint FMK. The IoT Platform FWK can provide API interfaces for applications to call, thereby receiving data from applications (e.g., the Touchpoint application), while maintaining the business logic for the internal flow of requests. Similarly, the Touchpoint FWK can provide API interfaces for corresponding applications to call, thereby receiving data from applications (e.g., the IoT Platform), passing the data down the application, and then sending it back to the application.

[0111] It is understandable that the application framework layer may also include a window manager, content provider, view system, phone manager, resource manager, notification manager, etc. For their specific meanings, please refer to relevant technical documentation; they will not be elaborated upon here.

[0112] The runtime is responsible for system scheduling and management. The runtime includes the core libraries and the virtual machine. The core libraries consist of two parts: one part contains the functionalities that the programming language (e.g., Java) needs to call, and the other part contains the system's core libraries.

[0113] The application layer and application framework layer can run in a virtual machine. The virtual machine executes the programming files (e.g., Java files) of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0114] The system layer can include multiple functional modules. For example: Surface Manager, Media Libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), etc.

[0115] The Surface Manager is used to manage the display subsystem and provides the fusion of two-dimensional (2D) and three-dimensional (3D) layers for multiple applications.

[0116] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

[0117] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0118] A 2D graphics engine is a graphics engine for 2D drawing.

[0119] The Hardware Abstraction Layer (HAL) is an interface layer located between the operating system kernel and upper-level software, its purpose being to abstract hardware. The HAL is an abstract interface for device kernel drivers, providing application programming interfaces (APIs) for accessing the underlying device to higher-level Java API frameworks. The HAL contains multiple library modules, such as the Camera HAL, Vendor repository, Display HAL, Bluetooth HAL, and Audio HAL. Each library module implements an interface for a specific type of hardware component. For example, the Display HAL provides an interface for accessing the display hardware. The Camera HAL provides an interface for accessing hardware components such as cameras to the camera firmware. The Vendor repository provides an interface for accessing hardware components such as encoders to the media firmware. When the system framework layer API requires access to the portable device's hardware, the Android operating system loads the library module for that hardware component.

[0120] The kernel layer is the foundation of an electronic device's operating system; all the operating system's final functions are implemented through the kernel layer. The kernel layer can contain display drivers, camera drivers, audio drivers, sensor drivers, and virtual card drivers.

[0121] It should be noted that the application provided Figure 3 The software structure diagram of the electronic device shown is only an example and does not limit the specific module division in different layers of the operating system. For details, please refer to the introduction of the operating system software structure in conventional technology.

[0122] Secondly, this application provides a service push method, applicable to the aforementioned electronic devices, including but not limited to mobile phones, tablets, etc., the method as follows: Figure 4 As shown, it includes:

[0123] S201, Analyze the received data to be pushed and determine the trigger creation conditions for the data to be pushed, wherein the trigger creation conditions indicate that the data to be pushed meets the user's push requirements.

[0124] S202, when the trigger creation conditions are met, a trigger for the data to be pushed is created, wherein the trigger is used to monitor whether the pre-trigger event of the data to be pushed is met.

[0125] S203, when the trigger is triggered, the push conditions for the data to be recommended are created.

[0126] S204, when the push conditions are met, push the data to be pushed.

[0127] After receiving push data from the server, the electronic device analyzes the data to determine the user's push request corresponding to the data, thus determining the trigger creation conditions for the push data. For example, if the push data is air conditioning service data, the corresponding user push request could be that the user has air conditioning, meaning the trigger creation condition is that the user has air conditioning. When the user has air conditioning, the trigger creation condition is met, and a trigger for air conditioning service data is created.

[0128] In one possible implementation, the data to be pushed includes a creation condition type and creation condition parameters; the step of analyzing the received data to be pushed and determining the trigger creation conditions for the data to be pushed includes: parsing the received data to be pushed to obtain the creation condition type and creation condition parameters for the data to be pushed; and generating the trigger creation conditions for the data to be pushed based on the creation condition type and creation condition parameters for the data to be pushed.

[0129] The creation condition type indicates the type of conditions for trigger creation, which can be set according to actual needs. In one example, the creation condition type can include single-condition and multi-condition types. A single-condition type has only one condition, such as whether the user has a certain device. A multi-condition type has multiple conditions, such as whether the pet is a certain type and whether the pet is a certain age. The creation condition parameters are the configuration parameters for the trigger creation conditions and need to be set according to the actual service push requirements. For example, for the single-condition type "whether the user has a certain device," the configuration parameter could be "air condition," resulting in a trigger creation condition that the user has an air conditioner. For the multi-condition type "whether the pet is a certain type" and "whether the pet is a certain age," the configuration parameters could be "cat" and "3-6 months," resulting in a trigger creation condition that the pet is a cat and the cat's age is 3-6 months.

[0130] Even if the trigger creation conditions are not met at the time of judgment, the terminal can re-judge the trigger creation conditions locally later. The terminal can perform periodic judgments at preset time intervals, or it can monitor variables to trigger the trigger creation condition judgment upon detecting a change in a specified parameter. In one possible implementation, the method further includes: determining whether the trigger creation conditions are met in response to a change in user push requests.

[0131] After the terminal receives the data to be pushed, even if the user does not have a push request at that time, the push request can still be monitored locally on the terminal. When the user's push request changes, it is determined whether the trigger creation conditions are met. If they are met, a trigger for the data to be pushed is created, realizing on-demand service push and improving the accuracy of service push.

[0132] A trigger is used to monitor whether a pre-triggered event for the data to be pushed is met. For example, for an air conditioning service, the pre-triggered condition could be detecting that the terminal's location information is at the user's home, or that the terminal (electronic device) is connected to the home's Wi-Fi. The data to be pushed may also include a trigger type and trigger parameters. In one possible implementation, creating a trigger for the data to be pushed when the trigger creation condition is met includes: creating a trigger for the data to be pushed according to the trigger type and trigger parameters of the data to be pushed when the trigger creation condition is met.

[0133] Trigger types can be configured according to actual needs. In one example, trigger types can include event-triggered and time-triggered types. Event-triggered triggers are triggered by the occurrence of a specified event, while time-triggered triggers are triggered when a specified time arrives. Trigger parameters are configuration parameters for the trigger and need to be set according to actual service push requirements. Specifically, trigger parameters can specify a specific triggering event, such as triggering after an electronic device connects to Wi-Fi; trigger parameters can also specify a specific time, such as triggering at 8:00 AM every day.

[0134] When the trigger condition is met, the trigger is activated, and after activation, push conditions for the data to be recommended are created. The data to be recommended may further include a push condition type and push condition parameters. In one possible implementation, creating push conditions for the data to be recommended when the trigger is activated includes: creating push conditions for the data to be recommended based on the push condition type and push condition parameters when the trigger is activated.

[0135] Push conditions are the direct triggers for pushing recommended data. The type of push condition can be set according to the actual situation. In one example, push condition types can include single-condition and multi-condition types. A single-condition type has only one condition, such as whether the indoor temperature is XX. A multi-condition type has multiple conditions, such as whether the season is XX and whether the indoor temperature is higher than XX. Push condition parameters are the configuration parameters for the push conditions and need to be set according to the actual service push requirements. For example, for the single-condition type "indoor temperature is higher than XX", the configuration parameter can be 30 degrees, then the generated push condition will be "indoor temperature is higher than 30 degrees". For example, for the multi-condition type "whether the season is XX" and "indoor temperature is higher than XX", the configuration parameters can be "summer" and "30 degrees", then the generated push conditions will be "the season is summer" and "indoor temperature is higher than 30 degrees".

[0136] When the push conditions are met, the data to be pushed needs to be pushed. Specifically, a push action for the data to be pushed can be generated, and the data to be pushed can be pushed by executing the push action. The data to be pushed may also include an action type and action parameters. In one possible implementation, pushing the data to be pushed when the push conditions are met includes: creating a push action for the push conditions based on the action type and action parameters of the data to be pushed; and executing the push action to push the data to be pushed when the trigger operation of the push action is detected. The action type can be set according to the actual situation. In one example, the action type can be desktop push, notification push, capsule push, negative one screen push, or lock screen push, etc. The push parameters are the configuration parameters of the push action and need to be set according to the actual service push requirements. For example, they can be push display duration, push notification sound, etc.

[0137] The push action can be a card-dispensing action on the negative one screen or the desktop, or it can be a notification push or a pop-up action on the lock screen. In one possible implementation, the push action is a card-dispensing action; the data to be pushed includes card type and card parameters; the step of executing the push action to push the data to be pushed when a trigger operation for the push action is detected includes: generating a target card according to the card type and card parameters of the data to be pushed when a trigger operation for the touch point of the push action is detected; and rendering and displaying the target card in the display area corresponding to the touch point.

[0138] The service push method of this application determines whether to push data on the terminal side, and performs the push locally on the terminal according to user habits by setting multiple judgment conditions for trigger creation and trigger and push conditions. Compared with service push based on user tags on the server side, it can improve the accuracy of service push.

[0139] This application also provides a service push system, see [link to relevant documentation]. Figure 5 The system includes: server 01 and terminal 02;

[0140] The server 01 sends the data to be pushed to the terminal 02;

[0141] The terminal 02 is used to analyze the received data to be pushed, determine the trigger creation conditions for the data to be pushed, wherein the trigger creation conditions indicate that the data to be pushed meets the user's push requirements; when the trigger creation conditions are met, a trigger for the data to be pushed is created, wherein the trigger is used to monitor whether the pre-triggered event of the data to be pushed is met; when the trigger is triggered, push conditions for the data to be recommended are created; when the push conditions are met, the data to be pushed is pushed.

[0142] The service push system of this application determines whether to push data on the terminal side, and performs push according to user habits on the terminal local through trigger creation conditions, trigger and push conditions multiple judgment settings. Compared with service push based on user tags on the server side, it can improve the accuracy of service push.

[0143] In one possible implementation, see Figure 6 The server 01 includes an operations cloud, a device cloud, and a push cloud; the terminal 02 includes a push SDK (Software Development Kit), an IoT platform, a desktop, and a negative one screen. Specifically, the operations cloud is used to configure the corresponding services; the device cloud is responsible for encapsulating data; the push cloud is responsible for transmitting data; the push SDK is responsible for receiving and sending messages and launching the IoT platform; the IoT platform is responsible for judging user habits and current conditions, and finally issuing the card; the desktop and negative one screen are used to display the corresponding card.

[0144] See below. Figure 7 The working process of the service push system in the embodiments of this application will be described in detail. Figure 7 The terminal in the process can be an electronic device such as a smartphone, tablet, or smartwatch.

[0145] like Figure 7 As shown, the IoT platform in the terminal may include an application initialization module, a message receiving module, a message parsing and distribution module, a precondition manager, a precondition factory, a trigger manager, a trigger factory, a condition manager, a condition factory, an action manager, an action factory, a card issuance service module, a data management module, and a card management module.

[0146] S1. The application initialization module is responsible for the initialization of the IoT platform. When the IoT platform is started for the first time on the terminal, the application initialization module obtains the user's account login status. If the account is logged in, the module sends the terminal's (electronic device's) ID (identity identifier) ​​and Token (token) to the server's device cloud to complete the authentication negotiation with the server, indicating that the electronic device can receive the data to be pushed.

[0147] S2-S3: When the server wants to push services, it configures the relevant services on the backend of the operations cloud, i.e., configures the data to be pushed. After configuration, the data to be pushed is sent to the device cloud. After receiving the data to be pushed from the operations cloud, the device cloud encapsulates the original data to be pushed, finally packaging it into the format required for PUSH, and then sends the packaged data to the PUSH cloud. This process is similar to the traditional PUSH message sending process and will not be described in detail here. After receiving it, the PUSH cloud will pass the data to be pushed to the terminal side.

[0148] Taking air conditioning service push notifications as an example, the format of the data to be pushed can be:

[0149]

[0150]

[0151]

[0152] It is understood that the above are merely examples of the format of the data to be pushed and are not intended to limit the scope of protection of this application. The specific format and data content can be customized according to the actual situation.

[0153] After the PUSH SDK in the S4-S5 terminal receives the data message sent by the PUSH cloud (the data message includes the data to be pushed), the message receiving module of the IoT middleware is launched. The message receiving module obtains the data message and sends it to the message parsing and distribution module.

[0154] S6. The message parsing and distribution module is responsible for parsing and distributing messages. The message parsing and distribution module parses the data message, finds that it is a push service, obtains the data to be pushed, and sends it to the precondition manager.

[0155] S7-S8, the precondition manager parses the received data to be pushed, obtaining the creation condition type and creation condition parameters of the data to be pushed. The precondition factory determines the trigger creation conditions for the data to be pushed based on the creation condition type and creation condition parameters. The trigger creation conditions correspond to actual user needs; for example, for air conditioning services, the trigger creation condition could be that the user has an air conditioning unit.

[0156] Specifically, the process of creating trigger creation conditions can be as follows: Figure 8 As shown, it includes:

[0157] S301, the precondition manager sends a creation message for the trigger creation condition instance to the precondition factory.

[0158] In one example, the creation message may include the creation condition type and creation condition parameters.

[0159] S302, Precondition Factory creates triggers to create condition instances.

[0160] S303, the precondition manager determines whether the trigger creation condition is met by creating a condition instance of the trigger.

[0161] Otherwise, create a pre-triggered trigger corresponding to the trigger creation condition instance. If so, notify the trigger manager to create a trigger for the data to be recommended. The pre-triggered trigger corresponding to the trigger creation condition instance is used to trigger the creation of the trigger creation condition instance, and the trigger for the data to be recommended is used to trigger the creation of the push conditions.

[0162] S304, The Precondition Manager registers the precondition triggers corresponding to the trigger creation condition instance with the Trigger Manager.

[0163] S305, the Precondition Manager stores the correspondence between precondition triggers and trigger creation conditions in the database.

[0164] S306, user requirements change, triggering the pre-triggered trigger.

[0165] S307, the precondition manager queries the database for the corresponding relationship to determine the trigger creation conditions corresponding to the precondition trigger.

[0166] S308, the precondition manager sends a creation message for the trigger creation condition instance to the precondition factory.

[0167] If the conditions for trigger creation change, the trigger creation condition instance needs to be re-registered with the predecessor condition factory, or the already created trigger creation condition instance needs to be deregistered.

[0168] After the terminal receives the data to be pushed, even if the user does not have a push request at that time (the trigger creation conditions are not met), the push request can still be monitored locally on the terminal. When the user's push request changes, it is determined whether the trigger creation conditions are met. If they are met, a trigger for the data to be pushed is created, realizing on-demand service push and improving the accuracy of service push.

[0169] S9-S10: When the trigger creation conditions are met, the trigger manager registers the trigger for the data to be pushed using the trigger factory, based on the trigger type and trigger parameters. Taking the air conditioning service as an example, the trigger can be an "off-get off work trigger" or an "arrival at home trigger," etc.

[0170] S11-S12 After the trigger is triggered, the Condition Manager will use the Condition Working Module to create push conditions for the data to be recommended based on the push condition type and push condition parameters.

[0171] S13-S14 When the push conditions are met, the Action Manager uses the Action Factory to create a push action corresponding to the push conditions based on the action type and action parameters of the data to be pushed. For example, the push action can be a card dispensing action pushed to the desktop or a card dispensing action pushed to the negative one screen. The relevant data is encapsulated, and the specific execution of the card dispensing action is handed over to the card dispensing service module for processing.

[0172] S15. The card dispensing service module sends the encapsulated data to the data management module for storage. Since the actual card view is only displayed when the user slides to the corresponding area, the corresponding data will only be queried when the touch point is triggered. Therefore, the data needs to be stored at this time.

[0173] S16. The card dispensing service module will send the card dispensing message to the corresponding contact point according to which contact point the card needs to be displayed.

[0174] S17. Each touchpoint will decide whether to display a card based on the actual display status and the user's triggering action; for example, when the user swipes to the negative one screen, the negative one screen will request a card view from the IoT platform. Touchpoints can include one or more of the following: desktop, negative one screen, notifications, capsules, and lock screen.

[0175] S18-S20: The card management module retrieves the corresponding card data from the data management module based on the card identifier in the card request from the touchpoint. Then, the card factory uses the card type, card parameters, etc. in the card data to call the corresponding resources through the resource management service. The card factory uses the called resources to assemble a formal card view and sends the card view to the touchpoint for rendering and display.

[0176] The service push system of this application determines whether to push data on the terminal side, and performs push according to user habits on the terminal local through trigger creation conditions, trigger and push conditions multiple judgment settings. Compared with service push based on user tags on the server side, it can improve the accuracy of service push.

[0177] This application also provides a computer program product that, when run on a computer, causes the computer to execute any of the service push methods described in the above embodiments.

[0178] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a solid-state drive (SSD), etc.

[0179] This application also provides a GUI (Graphical User Interface), which includes the aforementioned first interface, second interface, first sharing interface, second sharing interface, third sharing interface, fourth sharing interface, conversion interface, application selection interface, and icon editing interface. How users interact with these interfaces and under what circumstances the electronic device displays which interface can be found in the foregoing descriptions of each interface, and will not be repeated here.

Claims

1. A service push method, characterized in that, Applied to a terminal, the method includes: The received data to be pushed is parsed to obtain the creation condition type and creation condition parameters of the data to be pushed; based on the creation condition type and creation condition parameters of the data to be pushed, a trigger creation condition for the data to be pushed is generated, wherein the trigger creation condition indicates that the data to be pushed meets the user's push requirements; the data to be pushed includes the creation condition type and creation condition parameters. When the trigger creation conditions are met, a trigger for the data to be pushed is created, wherein the trigger is used to monitor whether the pre-trigger event for the data to be pushed is met; When the trigger is activated, the push conditions for the data to be pushed are created; When the push conditions are met, the data to be pushed is pushed.

2. The method according to claim 1, characterized in that, The data to be pushed includes a trigger type and trigger parameters; the step of creating a trigger for the data to be pushed when the trigger creation conditions are met includes: creating a trigger for the data to be pushed according to the trigger type and trigger parameters of the data to be pushed when the trigger creation conditions are met; And / or, the data to be pushed includes a push condition type and push condition parameters; when the trigger is triggered, the push conditions for the data to be pushed are created, including: when the trigger is triggered, the push conditions for the data to be pushed are created according to the push condition type and push condition parameters of the data to be pushed.

3. The method according to claim 1, characterized in that, The data to be pushed includes an action type and action parameters; pushing the data to be pushed when the push conditions are met includes: When the push conditions are met, a push action is created based on the action type and action parameters of the data to be pushed. When the trigger operation of the push action is detected, the push action is executed to push the data to be pushed.

4. The method according to claim 3, characterized in that, The push action is a card dispensing action; the data to be pushed includes card type and card parameters; The step of executing the push action to push the data to be pushed when the trigger operation of the push action is detected includes: When a trigger operation for the push action is detected, a target card is generated based on the card type and card parameters of the data to be pushed. The target card is rendered and displayed in the display area corresponding to the touch point.

5. The method according to claim 1, characterized in that, The method further includes: In response to changes in user push requests, determine whether the trigger creation conditions are met.

6. A service push system, characterized in that, The system includes: a server and a terminal; The server sends the data to be pushed to the terminal; The terminal is configured to parse the received data to be pushed to obtain the creation condition type and creation condition parameters of the data to be pushed; generate trigger creation conditions for the data to be pushed based on the creation condition type and creation condition parameters, wherein the trigger creation conditions indicate that the data to be pushed meets the user's push requirements; the data to be pushed includes a creation condition type and creation condition parameters; when the trigger creation conditions are met, a trigger for the data to be pushed is created, wherein the trigger is used to monitor whether the pre-triggered event of the data to be pushed is met; when the trigger is triggered, push conditions for the data to be pushed are created; when the push conditions are met, the data to be pushed is pushed.

7. The system according to claim 6, characterized in that, The terminal is also used to send the terminal's identification information to the server after the IoT platform is started. The server is specifically used to authenticate the terminal based on the terminal's identification information, and after successful authentication, to send the data to be pushed to the terminal.

8. The system according to claim 7, characterized in that, The server-side includes an operations cloud, a device cloud, and a push cloud; The operation cloud is used to respond to the push configuration operation, generate corresponding push data, and send the push data to the device cloud; The device cloud is used to authenticate the terminal based on the terminal's identification information, and after successful authentication, send the data to be pushed to the push cloud. The push cloud is used to send data to be pushed to the terminal.

9. The system according to claim 6, characterized in that, The data to be pushed includes a trigger type and trigger parameters; the terminal is specifically used to: when the trigger creation conditions are met, create a trigger for the data to be pushed according to the trigger type and trigger parameters of the data to be pushed; And / or, the data to be pushed includes a push condition type and push condition parameters; the terminal is specifically used to: when the trigger is triggered, create push conditions for the data to be pushed according to the push condition type and push condition parameters of the data to be pushed.

10. The system according to claim 6, characterized in that, The terminal is also used to respond to changes in user push requests and determine whether the trigger creation conditions are met.

11. The system according to claim 6, characterized in that, The data to be pushed includes an action type and action parameters; the terminal is specifically used to: when the push conditions are met, create a push action for the push conditions according to the action type and action parameters of the data to be pushed; and when the triggering operation of the push action is detected, execute the push action to push the data to be pushed.

12. The system according to claim 11, characterized in that, The push action is a card dispensing action; the data to be pushed includes card type and card parameters; The terminal is specifically used to: when a trigger operation for the push action is detected, generate a target card according to the card type and card parameters of the data to be pushed; and render and display the target card in the display area corresponding to the touch point.

13. An electronic device, characterized in that, include: One or more processors and memory; The memory is coupled to the one or more processors, the memory being used to store computer program code, the computer program code including computer instructions, the one or more processors invoking the computer instructions to cause the electronic device to perform the method as described in any one of claims 1 to 5.

Images