Intelligent service push methods, devices, electronic equipment and storage media

Abstract

This application provides a method, apparatus, electronic device, and storage medium for intelligent service push, relating to the field of Internet of Things (IoT) technology. The method includes: based on status data reported by the device, searching a set of device conditions for a trigger condition matching the status indicated by the status data; obtaining a target device and a target action associated with the found trigger condition from a set of device actions; matching a target intelligent service among intelligent services of different service types based on service rules configured for the target device and / or the target action, and pushing the target intelligent service. This application solves the problem of high automation configuration pressure in intelligent services in related technologies.

Description

Technical Field

[0001] This application relates to the field of Internet of Things (IoT) technology, and more specifically, to a smart service push method, apparatus, electronic device, and storage medium. Background Technology

[0002] Smart home systems utilize advanced network, communication, and automatic control technologies to make modern home life safer, more convenient, efficient, faster, smarter, and more personalized, greatly improving the quality of life for modern people.

[0003] However, current smart home systems mainly use automated configuration as a means of realizing smart services. Automated configuration not only requires configuring trigger conditions, but also configuring the controlled actions of smart devices, thereby configuring corresponding automation according to various devices. Moreover, the more smart devices there are, the more complex the automation configuration becomes, which puts a lot of pressure on users. Summary of the Invention

[0004] This application provides a method, apparatus, electronic device, and storage medium for intelligent service push, which can solve the problem of high automation configuration pressure in intelligent services in related technologies. The technical solution is as follows:

[0005] According to one aspect of this application, a smart service push method is provided, the method comprising: searching a set of device conditions for a trigger condition that matches the state indicated by the status data based on status data reported by the device; obtaining a target device and a target action associated with the found trigger condition from a set of device actions; matching a target smart service among smart services of different service types based on service rules configured for the target device and / or the target action, and pushing the target smart service.

[0006] According to one aspect of this application, a smart service push method is provided, the method comprising: receiving at least one target smart service pushed by a server; the target smart service being obtained by the server from smart services of different service types based on service rules configured for a target device and / or a target action; the target device and the target action being obtained by the server from a set of device actions based on status data reported by each device; and displaying at least one of the target smart services.

[0007] According to one aspect of this application, an intelligent service push device includes: a condition lookup module, configured to look up a trigger condition matching the state indicated by the state data in a set of device conditions based on the state data reported by the device; a target acquisition module, configured to acquire a target device and a target action associated with the found trigger condition from a set of device actions; and a service push module, configured to match a target intelligent service among intelligent services of different service types based on service rules configured for the target device and / or the target action, and push the target intelligent service.

[0008] In an exemplary embodiment, the service push module includes: a verification unit, configured to verify the existence of the target device and obtain a verification result of the target device; the verification result is used to indicate whether the target device exists; a risk determination unit, configured to determine the risk level of the target action; and a matching unit, configured to match the target smart service among smart services of different service types based on the risk level of the target action and / or the verification result of the target device; wherein the service types include control types and reminder types; the control types include a first control type and a second control type; the smart service of the first control type is used to prompt whether to confirm that the target device performs the target action, and the smart service of the second control type is used to prompt whether to enable the linkage between the target device and the target action marker device.

[0009] In an exemplary embodiment, the matching unit includes a target determination subunit, configured to, if the verification result of the target device indicates that the target device exists, use a control-type smart service as the target smart service; or if the verification result of the target device indicates that the target device does not exist, use a reminder-type smart service as the target smart service.

[0010] In one exemplary embodiment, the matching unit includes:

[0011] The intelligent service matching subunit is used to match the target intelligent service in the first control type and the reminder type intelligent service according to the verification result of the target device if the risk level of the target action is detected as high risk level; or to match the target intelligent service in the control type and the reminder type intelligent service according to the verification result of the target device if the risk level of the target action is low risk level.

[0012] In an exemplary embodiment, the target intelligent service is an intelligent service of a first control type. The device further includes: a first message receiving module, configured to receive a first feedback message based on the push of the intelligent service of the first control type; the first feedback message is used to indicate whether the intelligent service of the first control type is rejected or accepted; a service replacement module, configured to, when a matching intelligent service of the first control type is obtained, replace the intelligent service of the first control type with an intelligent service of the second control type as the target intelligent service for push if the number of times the intelligent service of the first control type is accepted exceeds a first preset threshold; or, a service stop module, configured to stop pushing the intelligent service of the first control type if the number of times the intelligent service of the first control type is rejected exceeds a second preset threshold; or, a direct control module, configured to, if the number of times the intelligent service of the first control type is accepted exceeds a third preset threshold, stop pushing the intelligent service of the first control type and send a device control command to the target device, causing the target device to execute the target action in response to the device control command.

[0013] In one exemplary embodiment, the target intelligent service is a second type of intelligent service, and the device further includes: a second message receiving module, configured to receive a second feedback message based on the push of the second control type of intelligent service; the second feedback message is used to indicate whether the second control type of intelligent service is rejected or accepted; a rule adjustment module, configured to adjust the service rules for the target action if the number of rejections of the second control type of intelligent service exceeds a fourth preset threshold, so that the target intelligent service can be matched among intelligent services of different service types based on the adjusted service rules; or, a linkage configuration module, configured to perform device linkage configuration for the target device and the target action if the second control type of intelligent service is accepted.

[0014] According to one aspect of this application, an intelligent service push system is provided, the system comprising: a client and a server; wherein, the server is configured to push at least one target intelligent service to the client; the target intelligent service is obtained by the server from intelligent services of different service types based on service rules configured for target devices and / or target actions; the target device and the target action are obtained by the server from a set of device actions based on status data reported by each device; the client is configured to receive at least one target intelligent service pushed by the server and display it.

[0015] In an exemplary embodiment, the client is further configured to cancel the display of the current target intelligent service and display another target intelligent service that is different from the current target intelligent service.

[0016] According to one aspect of this application, the client is further configured to initiate a request to the server related to the triggered target intelligent service in response to a triggering operation for the displayed target intelligent service.

[0017] In one exemplary embodiment, the triggering operation includes at least one of the following: a confirmation operation, used to indicate that the target smart service has been accepted; a denial operation, used to indicate that the target smart service has been rejected; and a closing operation, used to request the server to mark the target smart service push as closed.

[0018] According to one aspect of this application, an electronic device includes: at least one processor and at least one memory, wherein program instructions or code are stored on the memory; the program instructions or code are loaded and executed by the processor, causing the electronic device to implement the intelligent service push method as described above.

[0019] According to one aspect of this application, a storage medium storing program instructions or code thereon is characterized in that the program instructions or code are loaded and executed by a processor to implement the intelligent service push method as described above.

[0020] According to one aspect of this application, a computer program product includes a computer program stored in a storage medium, a processor of a computer device reads the computer program from the storage medium, and the processor executes the computer program, causing the computer device to implement the intelligent service push method as described above when executed.

[0021] The beneficial effects of the technical solution provided in this application are:

[0022] In the above technical solution, based on the status data reported by each device, trigger conditions matching the status indicated by the status data are searched in the device condition set. Then, the target device and target action associated with the found trigger conditions are obtained from the device action set. Next, based on the service rules configured for the target device and / or target action, the target intelligent service is matched among intelligent services of different service types and pushed to the system. In other words, after determining the target device and target action, different types of target intelligent services can be automatically pushed through pre-configured service rules related to the target device and target action. This reduces the burden of users actively configuring automation, effectively solving the problem of high user pressure in automatically configuring intelligent services in related technologies. Attached Figure Description

[0023] To more clearly illustrate the technical solutions provided in this application, the accompanying drawings used in the description of the various embodiments of this application will be briefly introduced below.

[0024] Figure 1 This is a schematic diagram of the implementation environment according to the embodiments of this application;

[0025] Figure 2 This is a flowchart illustrating an intelligent service push method according to an exemplary embodiment;

[0026] Figure 3 yes Figure 2 A flowchart of step 250 in one embodiment corresponds to the following example;

[0027] Figure 4 for Figure 3 A flowchart of the intelligent service matching process involved in one embodiment of the corresponding implementation;

[0028] Figure 5 for Figure 3 A flowchart of the intelligent service matching process involved in one embodiment of the corresponding implementation;

[0029] Figure 6 This is a flowchart illustrating another intelligent service push method according to an exemplary embodiment;

[0030] Figure 7 This is a flowchart illustrating another intelligent service push method according to an exemplary embodiment;

[0031] Figure 8 This is a flowchart illustrating another intelligent service push method according to an exemplary embodiment;

[0032] Figure 9 This is a flowchart illustrating another intelligent service push method according to an exemplary embodiment;

[0033] Figure 9a yes Figure 9 A schematic diagram illustrating the target intelligent service involved in the corresponding embodiment;

[0034] Figure 10 This is a flowchart illustrating the specific implementation of an intelligent service push method in an application scenario.

[0035] Figure 11 This is a structural block diagram of an intelligent service device according to an exemplary embodiment;

[0036] Figure 12 This is a structural block diagram of an intelligent service system according to an exemplary embodiment;

[0037] Figure 13 This is a hardware structure diagram of an electronic device according to an exemplary embodiment;

[0038] Figure 14This is a structural block diagram of an electronic device according to an exemplary embodiment. Detailed Implementation

[0039] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain this application, and should not be construed as limiting this application.

[0040] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the term “comprising” as used in this application means the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. It should be understood that when we say an element is “connected” or “coupled” to another element, it can be directly connected or coupled to the other element, or there may be intermediate elements. Furthermore, “connected” or “coupled” as used herein can include wireless connections or wireless coupling. The term “and / or” as used herein includes all or any units and all combinations of one or more associated listed items.

[0041] As mentioned earlier, current smart home systems primarily rely on automated configuration as a means of providing smart services. This automated configuration requires not only configuring triggering conditions but also configuring the controlled actions of smart devices.

[0042] For example, in a smart home scenario, if a human-triggered condition is configured for the living room and the controlled action of the smart device is configured to turn on the living room light, then for a living room equipped with a human body sensor, if the human body sensor detects someone in the living room, the living room light can be turned on automatically, thereby achieving automated control of the living room light.

[0043] It is evident that, in terms of automated configuration, users need to understand not only the smart devices deployed in the living room that meet the trigger conditions, but also the smart devices that perform controlled actions. After understanding the smart devices, users need to configure the trigger conditions based on the device status or the environmental status detected by the smart devices, as well as configure the controlled actions of the smart devices. This results in all the underlying logic related to automated configuration being exposed to the user, which not only poses risks, but also makes automated configuration increasingly complex as the number of smart devices increases, placing a significant burden on users and ultimately affecting the user experience.

[0044] Therefore, the intelligent service push method provided in this application can effectively reduce the pressure of automated configuration in intelligent services.

[0045] Accordingly, the intelligent service push method is applicable to intelligent service push devices, which can be deployed on electronic devices. These electronic devices can be computer devices configured with the von Neumann architecture, such as desktop computers, laptops, servers, etc., or electronic devices with central control, gateway, and other functions, such as gateways.

[0046] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0047] Figure 1 This is a schematic diagram of the implementation environment involved in an intelligent service push method. The implementation environment includes a user terminal 110, an intelligent device 130, a gateway 150, a server 170, and a router 190.

[0048] Specifically, user terminal 110, which can also be considered as user terminal or terminal, can deploy (or install) the client associated with smart device 130. This user terminal 110 can be an electronic device such as a smartphone, tablet, laptop, desktop computer, smart control panel, or other device with display and control functions, without limitation here.

[0049] The client, associated with the smart device 130, is essentially where the user registers an account and configures the smart device 130. For example, the configuration includes adding a device identifier to the smart device 130, so that when the client runs on the user terminal 110, it can provide the user with functions such as device display and smart service push for the smart device 130. This client can be in the form of an application or a web page. Correspondingly, the interface for displaying the device on the client can be in the form of a program window or a web page, and there is no limitation here.

[0050] Smart device 130 is deployed in gateway 150 and communicates with gateway 150 through its own configured communication module, thereby being controlled by gateway 150. It should be understood that smart device 130 generally refers to one of multiple smart devices 130. This application embodiment only uses smart device 130 as an example; that is, this application embodiment does not limit the number or type of smart devices deployed in gateway 150. In one application scenario, smart device 130 is deployed in gateway 150 by accessing it through a local area network. The process of smart device 130 accessing gateway 150 through a local area network includes: gateway 150 first establishes a local area network, and smart device 130 joins the local area network established by gateway 150 by connecting to it. This local area network includes, but is not limited to, WIFI, ZIGBEE, or Bluetooth. Among them, the smart device 130 can be a smart printer, smart fax machine, smart camera, smart air conditioner, smart door lock, smart light, or electronic devices such as human body sensor, door and window sensor, temperature and humidity sensor, water immersion sensor, natural gas alarm, smoke alarm, wall switch, wall socket, wireless switch, wireless wall sticker switch, cube controller, curtain motor, etc., equipped with a communication module.

[0051] The interaction between user terminal 110 and smart device 130 can be achieved through a local area network (LAN) or a wide area network (WAN). In one application scenario, user terminal 110 establishes a wired or wireless communication connection with gateway 150 via router 190, such as Wi-Fi, allowing user terminal 110 and gateway 150 to be deployed on the same LAN, thus enabling user terminal 110 to interact with smart device 130 via the LAN path. In another application scenario, user terminal 110 establishes a wired or wireless communication connection with gateway 150 via server 170, such as 2G, 3G, 4G, 5G, or Wi-Fi, allowing user terminal 110 and gateway 150 to be deployed on the same WAN, thus enabling user terminal 110 to interact with smart device 130 via the WAN path.

[0052] The server-side 170 can also be considered as the cloud, cloud platform, platform side, server side, etc. This server-side 170 can be a single server, a server cluster consisting of multiple servers, or a cloud computing center consisting of multiple servers, in order to better provide backend services to a massive number of user terminals 110. For example, backend services include intelligent service push services.

[0053] In one application scenario, as the smart device 130 interacts with the server 170, the smart device 130 forwards its status data to the server 170 through the gateway 150, so that the server 170 can push smart services to the user based on the status data.

[0054] Accordingly, the server 170 can receive the status data reported by the smart device 130, and then search for the triggering condition that matches the status indicated by the status data in the device condition set according to the status data reported by the smart device 130. Then, it can obtain the target device and target action associated with the found triggering condition from the device action set. After determining the target device and target action, it can match the target smart service in the smart services of different service types based on the service rules configured for the target device and / or target action, and push the target smart service to the user terminal 110 for display.

[0055] In another application scenario, intelligent service push can also be implemented by the gateway based on the status data reported by the intelligent device, which is not a specific limitation.

[0056] Please see Figure 2 This application provides an intelligent service push method, which is applicable to electronic devices, specifically electronic devices that can be... Figure 1 The implementation environment shown is either server 170 or gateway 150.

[0057] In the following method embodiments, for ease of description, the execution subject of each step of the method is an electronic device, but this does not constitute a specific limitation.

[0058] like Figure 2 As shown, the method may include the following steps:

[0059] Step 210: Based on the status data reported by the device, search the device condition set for trigger conditions that match the status indicated by the status data.

[0060] First, it should be noted that the status data indicates the device's status and / or the environmental status in which the device exists. Status data may include at least one of the following: basic device information, device function information, and device operating status. Basic device information uniquely identifies the device and may include device type, device name, etc. Device function information indicates the device's purpose or function; it can also be considered as reflecting the environmental attributes that the device can regulate. For example, if an air conditioner can regulate temperature, then the air conditioner's device function information indicates that its purpose or function is to regulate temperature. Device operating status indicates the device's connection status, operating mode, etc. For example, connection status includes online, offline, fault, etc.; taking an air conditioner as an example, operating modes include dehumidification, cooling, heating, and ventilation, etc.

[0061] The reported status data can be the status data of one device or the status data of multiple devices.

[0062] Regarding the acquisition of status data, it can be that the device reports it to the gateway for storage, so that the gateway can provide users with subsequent intelligent service pushes; or the device forwards it to the server through the gateway for storage, so that the server can provide users with subsequent intelligent service pushes.

[0063] Secondly, the device condition set is used to store multiple trigger conditions.

[0064] Based on this, after obtaining the device's status data, it is possible to search for multiple trigger conditions stored in the device's condition database to see if there is a trigger condition that matches the status indicated by the status data. If a matching trigger condition is found, step 230 is executed; otherwise, if no matching trigger condition is found, the process returns to step 210 to continue searching for a matching trigger condition.

[0065] Step 230: From the set of device actions, obtain the target device and target action associated with the found trigger condition.

[0066] The device action set is used to store the target device and target action associated with multiple trigger conditions.

[0067] Based on this, after acquiring the status data, it is possible to search for multiple target devices and multiple target actions stored in the device action central repository to see if there are any target devices and target actions associated with the triggering condition. If an associated target device and target action are found, step 250 is executed; otherwise, if no associated target device and target action are found, the process returns to step 230 to continue searching for associated target devices and target actions.

[0068] Using the previous example, in a living room equipped with a human body sensor, if the sensor detects someone in the living room, the living room light can be automatically turned on, thus achieving automated control of the living room light. Here, "someone in the living room" is the trigger condition found in the device condition set, and the target device associated with this trigger condition found in the device action set is the "living room light," and the associated target action is "turn on the living room light."

[0069] It's worth noting that in actual use, the purpose of setting device condition sets and device action sets is to allow different users with different types of devices for the same purpose to enjoy the same service. For example, the device condition set stores the trigger condition "someone in the living room and the temperature is above 32°C," and the device action set stores the target device "air conditioner" and the target action "turn on the air conditioner" associated with this trigger condition. Suppose user A has an air conditioner, while user B has a fan of a different type but the same purpose. In this case, the electronic device can add the target device "fan" and the target action "turn on the fan" associated with this trigger condition to the device action set. Then, for user A, if it detects that someone is in the living room and the temperature is above 32°C, it can push the smart service related to "automatically turn on the air conditioner," while for user B, it can push the smart service related to "automatically turn on the fan." This achieves the goal of allowing different users with different types of devices for the same purpose to enjoy automatic cooling services.

[0070] In this approach, by setting up device action sets and device condition sets, regardless of whether the user's devices are of the same type, as long as their uses are the same, automated control can be provided to the user quickly and accurately, ensuring the stability of the automated control process and laying the foundation for subsequent intelligent service recommendations.

[0071] Step 250: Based on the service rules configured for the target device and / or target action, match the target intelligent service among intelligent services of different service types, and push the target intelligent service.

[0072] Among them, the service types of intelligent services include control type and reminder type.

[0073] In one possible implementation, the control type includes a first control type and a second control type. The intelligent service of the first control type is used to prompt whether to confirm that the target device performs the target action; this can be considered as an operation confirmation service. The intelligent service of the second control type is used to prompt whether to enable the linkage between the target device and the target action marker device; this can be considered as an automation configuration service.

[0074] It should be noted that target intelligence services refer to intelligent services related to target devices and target actions. This can be understood as intelligent services of different service types being transformed into target intelligence services only after being combined with target devices and target actions.

[0075] For example, if the room temperature of 32.3℃ is detected as a bit high, the target intelligent service of the reminder type could be "The temperature is a bit high, we suggest turning on the air conditioner." The target intelligent service of the first control type could be "The temperature is a bit high, shall we turn on the air conditioner for you?", and the target intelligent service of the second control type could be "Configure an automatic configuration to turn on the air conditioner when the temperature is a bit high."

[0076] Secondly, service rules are configured for target devices and / or target actions, and serve as the basis for determining the intelligent service push for different service types.

[0077] In one possible implementation, service rules can push different types of smart services based on whether the target device exists. For example, if the target device exists, a first-type control-type smart service can be pushed.

[0078] In one possible implementation, service rules can push different types of intelligent services based on the risk level of the target action. For example, if the risk level of the target action is high, an alert-type intelligent service can be pushed.

[0079] In one possible implementation, service rules can push different types of intelligent services based on whether the target device exists and the risk level of the target action. For example, if the target device exists and the risk level of the target action is low, a second type of intelligent service can be pushed.

[0080] Through the above process, after determining the target device and target action, different types of target intelligent services can be automatically pushed through pre-configured service rules related to the target device and target action. This avoids exposing all the underlying logic related to automated configuration to users or service personnel, thereby reducing the risks in the automated configuration process. At the same time, users do not need to actively perform complex configuration operations on various devices, which can effectively solve the problem of high user pressure in automated configuration of intelligent services in related technologies.

[0081] Please see Figure 3 In one exemplary embodiment, step 250 may include the following steps:

[0082] Step 310: Verify the existence of the target device and obtain the verification result of the target device.

[0083] The verification result indicates whether the target device exists. The verification of the target device's existence can be based on whether status data reported by the target device is received within a preset time period, or it can be based on the list of devices bound to the current account.

[0084] Step 330: Determine the risk level of the target action.

[0085] The risk level is related to the probability of the target device making a mistake when performing the target action.

[0086] In one possible implementation, risk levels include, but are not limited to, high-risk and low-risk levels. It should be understood that the higher the probability of misoperation or the greater the wasted energy, the higher the risk level.

[0087] The risk level of a target action can be pre-configured. For example, turning on the air conditioner might result in significant energy waste if accidentally performed by the smart home system or user; therefore, this target action can be pre-configured as high-risk. Similarly, turning off the air conditioner poses no risk to the smart home system or user, so this target action can be pre-configured as low-risk.

[0088] Step 350: Among the intelligent services of different service types, match the target intelligent service according to the risk level of the target action and / or the verification result of the target device.

[0089] In one possible implementation, such as Figure 4 As shown, the matching process for the target intelligent service based on the verification result of the target device may include the following steps:

[0090] Step 410: If the verification result of the target device indicates that the target device exists, then the control type intelligent service is taken as the target intelligent service.

[0091] Step 430: If the verification result of the target device indicates that the target device does not exist, then the reminder type smart service is used as the target smart service.

[0092] For example, suppose the trigger condition is "someone is in the living room and the temperature is above 32℃". The associated target device and target action is "turn on the living room air conditioner". Based on the verification result of the target device, if it indicates that the target device does not exist, a smart service of the type "The living room temperature is too high, it is recommended to turn on the air conditioner" will be pushed to the user. Otherwise, if it indicates that the target device exists, a smart service of the first control type "The living room temperature is too high, should I turn on the air conditioner for you?" will be pushed to the user, or a smart service of the second control type "The living room temperature is too high, you can configure the automatic configuration to turn on the air conditioner" will be pushed to the user.

[0093] In one possible implementation, such as Figure 5 As shown, the matching process for target intelligent services based on the risk level of the target action and the verification results of the target device may include the following steps:

[0094] Step 510: If the risk level of the target action is detected to be high risk, then match the target intelligent service in the first control type and the reminder type intelligent service according to the verification result of the target device.

[0095] Step 530: If the risk level of the target action is low risk, then the target intelligent service is matched in the intelligent services of the second control type and the reminder type according to the verification result of the target device.

[0096] For example, in a smart home scenario, assuming the trigger condition "someone is in the living room and the temperature is above 32℃" is met, then based on the verification result of the target device being an air conditioner and the risk level of the target action "turn on the air conditioner," corresponding smart services will be pushed. For instance, if "turn on the air conditioner" is a high-risk level and the air conditioner is present, a first-type smart service will be pushed to remind the user whether to confirm turning on the air conditioner; or, if "turn on the air conditioner" is a low-risk level and the air conditioner is present, a second-type smart service can be pushed to prompt the user whether related automation configuration is needed; or, if "turn on the air conditioner" is a low-risk level and the air conditioner is not present, a reminder-type smart service can be pushed to remind the user to cool down the room through other means.

[0097] For example, in a smart home scenario, if the triggering condition "the living room air conditioner is on and the window is not closed" is met, the corresponding target device is the window closing device, and the corresponding target action is "close the window". If the verification result of the window closing device is that it does not exist, a reminder-type smart service is pushed; if the verification result of the window closing device is that it exists, and the risk level of closing the window is low, a second control-type smart service is pushed.

[0098] The above embodiments enable the matching of target intelligent services based on the risk level of the target action. Before executing a target intelligent service, a risk level confirmation and verification is required, which effectively prevents losses to users caused by device misoperation, reduces the risk of intelligent service push, and helps improve the intelligence of device control services. Furthermore, it can consider the relevant characteristics of different services to provide users with personalized services.

[0099] Please see Figure 6 In an exemplary embodiment, after step 350, the method may further include the following steps:

[0100] Step 610: Based on the push of intelligent services of the first control type, receive the first feedback message.

[0101] The first feedback message is used to indicate whether the intelligent service of the first control type is rejected or accepted.

[0102] It is worth mentioning that for a home gateway, the first feedback message received is not limited to the same user terminal. It can also be any user terminal in the home that interacts with the gateway through the local area network, such as family member A's smartphone, family member B's tablet, family member C's smart control panel, etc. By sharing the push of smart services through different user terminals, the push of smart services can also be avoided too frequently, thereby effectively reducing the risk of interference.

[0103] For the server, the first feedback message received is not limited to users in the same household, but can also be from users in different households. Based on this, the first feedback message is essentially a combination of user feedback on the first type of intelligent service through different user terminals in different households. This is conducive to providing differentiated and personalized intelligent services to users, realizing a personalized intelligent service for each individual.

[0104] Step 630: If a smart service of the first control type is matched and the number of times the smart service of the first control type is accepted exceeds a first set threshold, then a smart service of the second control type is replaced as the target smart service for push.

[0105] As mentioned earlier, the first type of intelligent service can be considered an operation confirmation service, meaning that after the user confirms the operation, the target device will execute the target action. The second type of intelligent service can be considered an automation configuration service, meaning that it configures the automation settings related to the target device and the target action. Therefore, if the number of times the first type of intelligent service is accepted exceeds a first set threshold, it indicates that the user has a certain preference for the target device to execute the target action when the triggering condition is met. At this point, instead of recommending whether the user confirms the target device's execution of the target action, it can be recommended that the user configure the automation settings related to the target device and the target action. In this approach, the conversion between different service types is achieved based on user feedback. After completing the automation configuration related to the target device and the target action, subsequent automated control of the target device can be directly implemented for the user.

[0106] Step 650: If the number of times the first control type of smart service is rejected exceeds the second set threshold, then stop pushing the first control type of smart service.

[0107] If the number of rejections of the first type of smart service exceeds a second preset threshold, it indicates that the user does not fully approve of the target device performing the target action even when the triggering condition is met. In this case, the first type of smart service enters a cooling-off period, during which no further pushes of the first type of smart service to the user will be made. The cooling-off period can be flexibly set according to the actual needs of the application scenario and is not limited here. For example, if the cooling-off period is 3 days, then no pushes of the first type of smart service will be made during these 3 days, and pushes of the first type of smart service can resume after 3 days.

[0108] Step 670: If the number of times the first control type of smart service is accepted exceeds the third set threshold, then stop pushing the first control type of smart service and send a device control command to the target device so that the target device performs the target action in response to the device control command.

[0109] If the number of times the intelligent service of the first control type is accepted exceeds the third set threshold, it indicates that the user has a certain preference for the target device to perform the target action when the triggering condition is met. At this time, it is no longer necessary to recommend whether the user confirms the target device to perform the target action, but to directly control the target device to perform the target action.

[0110] It should be noted that the above-mentioned threshold values ​​can be flexibly adjusted according to the actual needs of the application scenario, and no restrictions are imposed here.

[0111] Under the above embodiments, it is possible to obtain the user's acceptance of intelligent services based on information interaction with the user, so as to adjust the intelligent service push strategy in a timely manner according to the user's preferences. This makes the push strategy have dynamic closed-loop growth capability, and when the intelligent service push strategy is adjusted to a certain extent, no further confirmation from the user is required, avoiding frequent pushes that may interfere with the user, meeting the user's personalized needs, and further improving the intelligence level of intelligent services.

[0112] Please see Figure 7 In one exemplary embodiment, after intelligent service matching, the method may further include the following steps:

[0113] Step 710: Based on the push of intelligent services of the second control type, receive the second feedback message.

[0114] The second feedback message is used to indicate whether the smart service of the second control type is rejected or accepted.

[0115] Similarly, the second feedback message is essentially a combination of user feedback on the second type of smart service from different families and different user terminals. This is conducive to providing users with differentiated and personalized smart services, realizing a personalized smart service for each individual.

[0116] Step 730: If the number of times the intelligent service of the second control type is rejected exceeds the fourth set threshold, then the service rules for the target action are adjusted so that the target intelligent service is matched among intelligent services of different service types based on the adjusted service rules.

[0117] As mentioned earlier, the intelligent service of the second control type can be considered as an automated configuration service. If the number of times the intelligent service of the second control type is rejected exceeds the fourth set threshold, it indicates that the user does not agree to configure the automated configuration related to the target device and the target action, which also reflects the user's preference. Therefore, it is necessary to adjust the risk level of the target action. For example, the risk level of the target action is adjusted from a low risk level to a high risk level, so that the operation confirmation service is pushed to the user instead of the automated configuration service.

[0118] Step 750: If the intelligent service of the second control type is accepted, then device linkage configuration is performed for the target device and the target action.

[0119] When the intelligent service of the second control type is accepted, it indicates that the user agrees to configure the automation configuration related to the target device and target action. Then, for the gateway / server side, an automation scheme can be generated based on the triggering conditions and the associated target device and target action, and stored in the device condition set and device action set respectively, which is conducive to the subsequent realization of automated control of the target device.

[0120] It should be noted that the above-mentioned threshold values ​​can be flexibly adjusted according to the actual needs of the application scenario, and are not limited here. Under the above embodiments, based on the continuous adjustment of risk levels, dynamic learning of the risk level of the target action is achieved. This enables the differentiated push of intelligent services of different service types according to risk and closed-loop characteristics. This not only considers the relevant characteristics of intelligent services of different service types but also helps to avoid risks and improve the stability of the user experience.

[0121] Please see Figure 8 This application provides an intelligent service push method, which is applicable to electronic devices, specifically electronic devices that can be... Figure 1 User terminal 110 in the implementation environment shown.

[0122] In the following method embodiments, for ease of description, the execution subject of each step of the method is an electronic device, but this does not constitute a specific limitation.

[0123] like Figure 8 As shown, the method may include the following steps:

[0124] Step 810: Receive at least one target intelligent service pushed by the server.

[0125] Specifically, the target intelligent service is obtained by the server from intelligent services of different service types based on service rules configured for the target device and / or target action; the target device and target action are obtained by the server from the device action set based on the status data reported by each device. It should be noted that the server can be... Figure 1 The server 170 or gateway 150 in the implementation environment are shown.

[0126] Step 830: Display at least one target intelligent service.

[0127] Specifically, the display process includes canceling the display of the currently displayed target intelligent service and displaying another target intelligent service that is different from the currently displayed target intelligent service. That is, when the server pushes multiple target intelligent services, these services can be displayed on the client side by swiping left or right. Of course, in other embodiments, multiple target intelligent services can also be displayed on the client side through lists, vertical scrolling, etc., which is not a specific limitation.

[0128] In this approach, the demonstration process takes place on the client side. By displaying multiple target intelligent services on the client and receiving user feedback on these services, the intelligent service interaction process can be completed efficiently.

[0129] Through the above process, the target intelligent service is proactively displayed to the user, allowing the user to intuitively understand the target intelligent service being pushed, improving the initiative and reach of the intelligent service, and helping to reduce the pressure on the user regarding the automated configuration of the intelligent service.

[0130] Please see Figure 9 In an exemplary embodiment, after step 830, the method may further include the following steps:

[0131] Step 910: In response to the triggered operation for the target intelligent service being displayed, initiate a request to the server related to the triggered target intelligent service.

[0132] The triggering operations include, but are not limited to: confirmation operations for reporting that the target intelligent service has been accepted, denial operations for reporting that the target intelligent service has been rejected, and closing operations for requesting the server to mark the target intelligent service push as closed.

[0133] exist Figure 9aIn the client, a service homepage is displayed to showcase the target smart services pushed by the server. This service homepage displays a service display window that allows multiple target smart services to be displayed by swiping left and right. In addition, the service homepage also displays a confirmation entry "OK", a denial entry "No need", and a close entry "Don't remind me again".

[0134] like Figure 9a As shown, if the user clicks the "OK" confirmation button, it indicates that the user accepts the target intelligent service pushed by the server. The user then sends feedback information to the server to confirm that the target intelligent service has been accepted. The click action is considered a confirmation operation used to confirm the acceptance of the target intelligent service.

[0135] like Figure 9a As shown, if a user clicks the "No More" option, it indicates that the user does not accept the target smart service pushed by the server. A feedback message is then sent to the server to indicate that the target smart service has been rejected. The click action is considered a rejection operation used to indicate that the target smart service has been rejected.

[0136] like Figure 9a As shown, if a user clicks the "Don't remind me again" option, it means the user has turned off the target smart service pushed by the server. A feedback message is then sent to the server to indicate that the target smart service has been turned off, thus preventing further push notifications. The click action is considered as a confirmation that the user has accepted the decision to turn off the target smart service.

[0137] Through the above process, user interaction with the intelligent service process is realized. Users can participate in adjusting the intelligent service until it meets their expectations or reaches a reasonable application level. This improves the stability and accuracy of the intelligent service process and satisfies users' personalized needs.

[0138] Figure 10 This is a schematic diagram illustrating the specific implementation of an intelligent service push method in an application scenario.

[0139] This application scenario is applicable to Figure 1 The implementation environment shown demonstrates how the interaction between various hardware devices within the environment enables proactive delivery of intelligent services to users.

[0140] When the intelligent service push function is detected to be enabled, steps (1) to (5) will be followed to proactively push different types of target intelligent services to the same / different user terminals under different triggering conditions. The intelligent service push function can be pre-configured on the user terminal. Here, "backend" can refer to... Figure 1The diagram shows the gateway or server in the implementation environment.

[0141] Step (1) involves pre-constructing an intelligent service library. This library includes a device condition set and a device action set. The device condition set stores multiple trigger conditions, and the device action set stores the target devices and target actions associated with the trigger conditions. The library also includes intelligent services of different service types, service rules, risk levels of target actions, various set thresholds, cooldown periods, etc.

[0142] In step (2), the device reports status data. Specifically, after the device is deployed on the gateway, it can report status data to the gateway, or the gateway can forward the status data to the server, so that the gateway / server can determine whether the triggering condition is met based on the device's status data. When it is detected that the status data of a device meets the triggering condition, the associated target device and target action are further obtained. For example, in an application scenario, the human body sensor, temperature sensor, and air conditioner report their respective status data to the gateway / server, so that the gateway / server can determine the current status as: there are people in the living room and the temperature is higher than 32°C, and the air conditioner is off. Based on the current status, it can determine whether there is a matching triggering condition in the device condition set. If there is a matching triggering condition, the target device associated with the triggering condition is the air conditioner, and the target action is "turn on the air conditioner".

[0143] In step (3), the target intelligent service is matched. The server or gateway matches the target intelligent service among intelligent services of different service types according to service rules and pushes it to the client running on the same / different user terminals. If, in the aforementioned application scenario, it is determined based on service rules that the target device air conditioner exists and the risk level of the target action "turn on the air conditioner" is high risk, then the target intelligent service is matched among intelligent services of different service types as the first control type intelligent service, that is, the operation confirmation service, and the target intelligent service is pushed to the user's client.

[0144] Step (4) displays the target intelligent service. The client will then receive the target intelligent service pushed from the background and display it in the service display window. See also... Figure 9a ,exist Figure 9a In the process, multiple target intelligent services can be displayed in the service display window by sliding left and right, so that users can perform different trigger operations on the target intelligent services.

[0145] Step (5) is executed based on user feedback. See also... Figure 9aUsers can accept the push notification of the target smart service by confirming the confirmation action. The backend will then control the target device to perform the target action based on the user's feedback, or perform related automated configurations for the target device and the target action. Users can also reject the push notification of the target smart service by denying the confirmation action. In this case, the backend will put the target smart service into a cooling-off period based on the user's feedback, so that the target smart service will no longer be pushed to the user during the cooling-off period. Alternatively, users can instruct the backend to permanently disable the push notification of the target smart service by closing the confirmation action.

[0146] As users continuously provide feedback on the push notifications for targeted intelligent services, it will be possible to intelligently adjust the risk level of the service type and action type of the intelligent service, thereby avoiding interference with some users and meeting their personalized needs.

[0147] The following are embodiments of the apparatus described in this application, which can be used to execute the intelligent service push method involved in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the method embodiments of the intelligent service push method involved in this application.

[0148] Please see Figure 11 This application provides an intelligent service push device 1100, including but not limited to:

[0149] The condition lookup module 1110 is used to search for trigger conditions that match the state indicated by the state data in the device condition set based on the state data reported by the device.

[0150] The target acquisition module 1130 is used to acquire the target device and target action associated with the found trigger condition from the device action set;

[0151] The service push module 1150 is used to match the target intelligent service among intelligent services of different service types based on the service rules configured for the target device and / or the target action, and push the target intelligent service.

[0152] In an exemplary embodiment, the service push module includes: a verification unit, configured to verify the existence of the target device and obtain a verification result of the target device; the verification result is used to indicate whether the target device exists; a risk determination unit, configured to determine the risk level of the target action; and a matching unit, configured to match the target smart service among smart services of different service types based on the risk level of the target action and / or the verification result of the target device; wherein the service types include control types and reminder types; the control types include a first control type and a second control type; the smart service of the first control type is used to prompt whether to confirm that the target device performs the target action, and the smart service of the second control type is used to prompt whether to enable the linkage between the target device and the target action marker device.

[0153] In an exemplary embodiment, the matching unit includes a target determination subunit, configured to, if the verification result of the target device indicates that the target device exists, use a control-type smart service as the target smart service; or if the verification result of the target device indicates that the target device does not exist, use a reminder-type smart service as the target smart service.

[0154] In an exemplary embodiment, the matching unit includes: an intelligent service matching subunit, configured to, if the risk level of the target action is detected to be high risk level, match the target intelligent service in intelligent services of a first control type and an alert type based on the verification result of the target device; or, if the risk level of the target action is low risk level, match the target intelligent service in intelligent services of a control type and an alert type based on the verification result of the target device.

[0155] In an exemplary embodiment, the target intelligent service is an intelligent service of a first control type. The device further includes: a first message receiving module, configured to receive a first feedback message based on the push of the intelligent service of the first control type; the first feedback message is used to indicate whether the intelligent service of the first control type is rejected or accepted; a service replacement module, configured to, when a matching intelligent service of the first control type is obtained, replace the intelligent service of the first control type with an intelligent service of the second control type as the target intelligent service for push if the number of times the intelligent service of the first control type is accepted exceeds a first preset threshold; or, a service stop module, configured to stop pushing the intelligent service of the first control type if the number of times the intelligent service of the first control type is rejected exceeds a second preset threshold; or, a direct control module, configured to, if the number of times the intelligent service of the first control type is accepted exceeds a third preset threshold, stop pushing the intelligent service of the first control type and send a device control command to the target device, causing the target device to execute the target action in response to the device control command.

[0156] In one exemplary embodiment, the target intelligent service is a second type of intelligent service, and the device further includes: a second message receiving module, configured to receive a second feedback message based on the push of the second control type of intelligent service; the second feedback message is used to indicate whether the second control type of intelligent service is rejected or accepted; a rule adjustment module, configured to adjust the service rules for the target action if the number of rejections of the second control type of intelligent service exceeds a fourth preset threshold, so that the target intelligent service can be matched among intelligent services of different service types based on the adjusted service rules; or, a linkage configuration module, configured to perform device linkage configuration for the target device and the target action if the second control type of intelligent service is accepted.

[0157] Please see Figure 12 This application provides an intelligent service push system 1200, including but not limited to: server 1210 and client 1230.

[0158] Among them, server 1210 is used to push at least one target intelligent service to the client; the target intelligent service is obtained by the server from intelligent services of different service types based on the service rules configured for the target device and / or target action; the target device and the target action are obtained by the server from the device action set based on the status data reported by each device.

[0159] Client 1230 is used to receive and display at least one of the target intelligent services pushed by the server.

[0160] In an exemplary embodiment, the client 1230 is further configured to cancel the display of the current target intelligent service and display another target intelligent service that is different from the current target intelligent service.

[0161] According to one aspect of this application, the client 1230 is further configured to initiate a request to the server related to the triggered target intelligent service in response to a triggering operation for the displayed target intelligent service.

[0162] In one exemplary embodiment, the triggering operation includes at least one of the following: a confirmation operation, used to indicate that the target smart service has been accepted; a denial operation, used to indicate that the target smart service has been rejected; and a closing operation, used to request the server to mark the target smart service push as closed.

[0163] It should be noted that the intelligent service push device provided in the above embodiments is only illustrated by the division of the above functional modules when performing intelligent service push. In actual applications, the above functions can be assigned to different functional modules as needed. That is, the internal structure of the intelligent service push device will be divided into different functional modules to complete all or part of the functions described above.

[0164] Furthermore, the embodiments of the intelligent service push device and the intelligent service push method provided in the above embodiments belong to the same concept, and the specific way in which each module performs operations has been described in detail in the method embodiments, and will not be repeated here.

[0165] Figure 13 A schematic diagram of the structure of an electronic device is shown according to an exemplary embodiment. This electronic device is suitable for... Figure 1 The gateway 150 or server 170 of the implementation environment is shown.

[0166] It should be noted that this electronic device is merely an example adapted to this application and should not be construed as providing any limitation on the scope of use of this application. Furthermore, this electronic device should not be interpreted as requiring or depending on any specific feature. Figure 13 One or more components of the exemplary electronic device 2000 shown.

[0167] The hardware structure of electronic devices 2000 can vary significantly due to differences in configuration or performance, such as... Figure 13 As shown, the electronic device 2000 includes: a power supply 210, an interface 230, at least one memory 250, and at least one central processing unit (CPU) 270.

[0168] Specifically, power supply 210 is used to provide operating voltage for various hardware devices on electronic device 2000.

[0169] Interface 230 includes at least one wired or wireless network interface 231 for interacting with external devices. For example, to perform... Figure 1 The diagram illustrates the interaction between terminal 100 and electronic device 200 in the implementation environment.

[0170] Of course, in other examples adapted in this application, interface 230 may further include at least one serial-to-parallel conversion interface 233, at least one input / output interface 235, and at least one USB interface 237, etc. Figure 13 As shown, this does not constitute a specific limitation.

[0171] The memory 250 serves as a carrier for resource storage and can be a read-only memory, random access memory, disk, or optical disk, etc. The resources stored on it include the operating system 251, application programs 253, and data 255, etc., and the storage method can be temporary storage or permanent storage.

[0172] The operating system 251 is used to manage and control the various hardware devices and application programs 253 on the electronic device 2000, so as to enable the central processing unit 270 to perform calculations and processing on the massive data 255 in the memory 250. It can be Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, etc.

[0173] Application 253 is a program instruction or code based on operating system 251 that performs at least one specific task, and may include at least one module. Figure 13 (Not shown), each module can contain program instructions or code for the electronic device 2000. For example, the smart service push device can be considered as an application 253 deployed on the electronic device 2000.

[0174] Data 255 can be photos, pictures, etc. stored on a disk, or status data reported by the device, and is stored in memory 250.

[0175] The central processing unit 270 may include one or more processors and is configured to communicate with the memory 250 via at least one communication bus to read program instructions or code stored in the memory 250, thereby enabling the computation and processing of massive amounts of data 255 in the memory 250. For example, an intelligent service push method can be implemented by the central processing unit 270 reading a series of program instructions or code stored in the memory 250.

[0176] Furthermore, this application can also be implemented through hardware circuits or a combination of hardware circuits and software. Therefore, the implementation of this application is not limited to any specific hardware circuit, software, or combination thereof.

[0177] Please see Figure 14 This application provides an electronic device 4000, which may include a gateway, a desktop computer, a laptop computer, a server, etc.

[0178] exist Figure 14 The electronic device 4000 includes at least one processor 4001, at least one communication bus 4002, and at least one memory 4003.

[0179] The processor 4001 and memory 4003 are connected, for example, via a communication bus 4002. Optionally, the electronic device 4000 may also include a transceiver 4004, which can be used for data interaction between the electronic device and other electronic devices, such as sending and / or receiving data. It should be noted that in practical applications, the transceiver 4004 is not limited to one, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of this application.

[0180] Processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 4001 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0181] The communication bus 4002 may include a path for transmitting information between the aforementioned components. The communication bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. The communication bus 4002 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 14 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0182] The memory 4003 may be ROM (Read Only Memory) or other types of static storage devices capable of storing static information and instructions, RAM (Random Access Memory) or other types of dynamic storage devices capable of storing information and instructions, or EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact Disc Read Only Memory) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto.

[0183] The memory 4003 stores program instructions or code, and the processor 4001 can read the program instructions or code stored in the memory 4003 through the communication bus 4002.

[0184] When the program instructions or code are executed by the processor 4001, the intelligent service push method in the above embodiments is implemented.

[0185] Furthermore, this application provides a storage medium storing program instructions or code, which is loaded and executed by a processor to implement the intelligent service push method as described above.

[0186] This application provides an application product, which includes program instructions or code stored in a storage medium. The processor of an electronic device reads the program instructions or code from the storage medium, loads and executes the program instructions or code, enabling the electronic device to implement the intelligent service push method described above.

[0187] Compared with related technologies, this application improves the intelligence level of intelligent services, enabling automatic push of target intelligent services of different service types, thereby reducing the risks in the automated configuration process; based on the proactive push and display of target intelligent services, it enhances the initiative and reach of intelligent services, which helps reduce the configuration pressure on users; it achieves differentiated push of intelligent services of different service types based on risk and closed-loop nature, not only considering the relevant characteristics of intelligent services of different service types, but also helping to avoid risks and improve the stability of user experience; through feedback from different households and users, it meets the personalized needs of users, making intelligent services fully matched to different users; the intelligent service push strategy has a dynamic closed-loop growth capability, realizing targeted matching of the intelligent service process, which helps to further avoid risks, avoid frequent pushes that may interfere with users, and further improve user experience; in addition, through the setting of device action sets and device condition sets, regardless of whether the user's devices are of the same type, as long as the purpose is the same, it can quickly and accurately provide users with automated control, ensuring the stability of the automated control process.

[0188] It should be understood that although the steps in the flowcharts of the accompanying figures are shown sequentially as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the accompanying figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0189] The above description is only a partial embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for intelligent service push, characterized in that, The method includes: Based on the status data reported by the device, a trigger condition matching the status indicated by the status data is searched in the device condition set; From the set of device actions, obtain the target device and target action associated with the found trigger condition; Based on the presence or absence of the target device and / or the risk level of the target action, a target intelligent service is matched among intelligent services of different service types, and the target intelligent service is pushed; the matching of the target intelligent service includes: if the risk level of the target action is high-risk, then matching the target intelligent service among intelligent services of the first control type and intelligent services of the reminder type based on the presence or absence of the target device; or, if the risk level of the target action is low-risk, then matching the target intelligent service among intelligent services of the second control type and intelligent services of the reminder type based on the presence or absence of the target device. The target intelligent service is any one of the following: a first control type intelligent service, a second control type intelligent service, and a reminder type intelligent service; the first control type intelligent service is an operation confirmation service, the second control type intelligent service is an automated configuration service, and the reminder type intelligent service is an operation reminder service.

2. The method as described in claim 1, characterized in that, Before matching the target intelligent service among intelligent services of different service types based on the existence of the target device and / or the risk level of the target action, the method further includes: The existence of the target device is verified to obtain a verification result, which indicates whether the target device exists; and / or The risk level of the target action is determined based on the risk level configured for the target action.

3. The method as described in claim 1, characterized in that, The matching of the target intelligent service also includes: If the verification result of the target device indicates that the target device exists, then if the risk level of the target action is high risk, the intelligent service of the first control type shall be used as the target intelligent service. If the verification result of the target device indicates that the target device exists, then if the risk level of the target action is low risk, the intelligent service of the second control type shall be used as the target intelligent service. If the verification result of the target device indicates that the target device does not exist, then the smart service of the reminder type will be used as the target smart service.

4. The method according to any one of claims 1 to 3, characterized in that, The target intelligent service is an intelligent service of the first control type, and the method further includes: Based on the push of intelligent services of the first control type, a first feedback message is received; the first feedback message is used to indicate whether the intelligent service of the first control type is rejected or accepted. If a smart service of the first control type is matched as the target smart service, and the number of times the smart service of the first control type is accepted exceeds a first preset threshold, then a smart service of the second control type is replaced as the target smart service for push notification; or If the number of times a smart service of the first control type is rejected exceeds the second preset threshold, then the push of smart services of the first control type will be stopped; or If the number of times the first control type of smart service is accepted exceeds a third preset threshold, then the push of the first control type of smart service will stop, and a device control command will be sent to the target device, so that the target device will execute the target action in response to the device control command.

5. The method according to any one of claims 1 to 3, characterized in that, The target intelligent service is a second type of intelligent service, and the method further includes: Based on the push of intelligent services of the second control type, a second feedback message is received; the second feedback message is used to indicate whether the intelligent service of the second control type is rejected or accepted. If the number of rejections of the second type of intelligent service exceeds the fourth preset threshold, then the service rules for the target action are adjusted, so that the target intelligent service is matched among intelligent services of different service types based on the adjusted service rules; or If the intelligent service of the second control type is accepted, then device linkage configuration is performed for the target device and the target action.

6. A method for intelligent service push, characterized in that, The method includes: The system receives at least one target intelligent service pushed by the server. The target intelligent service is obtained by the server through matching intelligent services of different service types based on the existence of a target device and / or the risk level of a target action. The target device and the target action are obtained by the server from a set of device actions based on the status data reported by the device. The matching of the target intelligent service includes: if the risk level of the target action is high-risk, then matching the target intelligent service in a first control type intelligent service and an alert type intelligent service based on the existence of the target device; or, if the risk level of the target action is low-risk, then matching the target intelligent service in a second control type intelligent service and an alert type intelligent service based on the existence of the target device. The target intelligent service is any one of the first control type intelligent service, the second control type intelligent service, and the alert type intelligent service. The first control type intelligent service is an operation confirmation service, the second control type intelligent service is an automated configuration service, and the alert type intelligent service is an operation alert service. Demonstrate at least one of the target intelligent services.

7. The method as described in claim 6, characterized in that, The demonstration of at least one of the target intelligent services includes: Cancel the display of the current target intelligent service and display another target intelligent service that is different from the current target intelligent service.

8. The method as described in claim 6 or 7, characterized in that, After displaying at least one of the target intelligent services, the method further includes: In response to a trigger operation on the displayed target intelligent service, a request related to the triggered target intelligent service is sent to the server.

9. The method as described in claim 8, characterized in that, The triggering operation includes at least one of the following: The confirmation operation is used to indicate that the target intelligent service has been accepted. A denial operation is used to indicate that the target intelligent service has been rejected. The close operation is used to request the server to mark the target smart service push as closed.

10. An intelligent service push device, characterized in that, The device includes: The condition lookup module is used to search for trigger conditions that match the state indicated by the status data reported by the device in the device condition set. The target acquisition module is used to acquire the target devices and target actions associated with the found trigger conditions from the set of device actions; The service push module is used to match a target intelligent service among intelligent services of different service types based on whether the target device exists and / or the risk level of the target action, and to push the target intelligent service. The matching of the target intelligent service includes: if the risk level of the target action is high-risk, then matching the target intelligent service among intelligent services of a first control type and intelligent services of an alert type based on whether the target device exists; or, if the risk level of the target action is low-risk, then matching the target intelligent service among intelligent services of a second control type and intelligent services of an alert type based on whether the target device exists. The target intelligent service is any one of the intelligent services of the first control type, the second control type, and the alert type; the intelligent service of the first control type refers to an operation confirmation service, the intelligent service of the second control type refers to an automated configuration service, and the intelligent service of the alert type refers to an operation alert service.

11. An intelligent service push system, characterized in that, The system includes: a client and a server; wherein... The server is configured to push at least one target intelligent service to the client. The target intelligent service is obtained by the server through matching intelligent services of different service types based on the presence of a target device and / or the risk level of a target action. The target device and the target action are obtained by the server from a set of device actions based on the status data reported by the device. The matching of the target intelligent service includes: if the risk level of the target action is high-risk, then matching the target intelligent service between a first control type intelligent service and a reminder type intelligent service based on the presence of the target device; or, if the risk level of the target action is low-risk, then matching the target intelligent service between a second control type intelligent service and a reminder type intelligent service based on the presence of the target device. The target intelligent service is any one of the first control type intelligent service, the second control type intelligent service, and the reminder type intelligent service. The first control type intelligent service is an operation confirmation service, the second control type intelligent service is an automated configuration service, and the reminder type intelligent service is an operation reminder service. The client is used to receive and display at least one of the target intelligent services pushed by the server.

12. An electronic device, characterized in that, include: At least one processor and at least one memory, wherein, The memory stores program instructions or code; The program instructions or code are loaded and executed by the processor, causing the electronic device to implement the intelligent service push method as described in any one of claims 1 to 9.

13. A storage medium storing program instructions or code thereon, characterized in that, The program instructions or code are loaded and executed by the processor to implement the intelligent service push method as described in any one of claims 1 to 9.

Images