Equipment binding prompting method, equipment and medium

Abstract

The invention discloses an equipment binding prompting method, equipment and a medium, and relates to the technical field of smart home / smart home, and the method comprises the steps: obtaining the order information of a target channel indicated by a channel collection offline date configuration table, and the channel collection offline date configuration table comprises the target channel of which the order information needs to be collected; according to the order information and a device binding record, calculating a binding parameter of the device recorded in the order information; determining target order information based on the binding parameters of the equipment and a binding promotion equipment category management and control configuration table; and determining a to-be-pushed user list based on the target order information, and pushing information to a terminal corresponding to a user according to the user list so as to prompt the user in the user list to bind equipment. According to the method, accurate equipment binding prompt is realized by integrating order information of channels such as sales, logistics, installation and the like, so that the user experience can be effectively improved, and prompt information is ensured to be timely and accurately pushed to the user.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of smart home technology, in particular to a device binding prompting method, device and medium. BACKGROUND

[0002] Nowadays, the functions of smart home appliances are no longer limited to providing basic user experience, but through networking and remote control, etc., they bring users a more convenient and intelligent life. Smart home appliances have become the choice of many families. They can provide real-time data monitoring, remote operation, automation services and other functions, greatly improving people's quality of life and efficiency.

[0003] However, although the functions of smart home appliances are becoming more and more rich, the actual experience of many users has not reached the expected. Users may not bind the device after purchasing the smart home appliance, which makes the user unable to use part of the Internet of Things functions of the device, affects the user's efficiency of using the device, and reduces the user experience. SUMMARY

[0004] In view of the above problems, the present application provides a device binding prompting method, device and medium.

[0005] In a first aspect, the present application provides a device binding prompting method, comprising:

[0006] Obtaining order information corresponding to a target channel indicated by a channel collection date configuration table, the channel collection date configuration table comprising a target channel requiring collection of order information, the target channel comprising one or more combinations of a sales channel, a logistics channel and an installation channel, and the order information comprising a mapping relationship between a user corresponding to each order and a purchased device;

[0007] According to the order information and the device binding record, determining the binding parameter of the device recorded in the order information, the binding parameter being used to indicate whether the device has been bound to a user;

[0008] Based on the binding parameter of the device and a promotion binding device category control configuration table, determining target order information, the promotion binding device category control configuration table comprising a target device type requiring collection of order information and a target channel corresponding to the target device type requiring collection;

[0009] Based on the target order information, determining a user list to be pushed, and according to the user list, pushing information to a terminal corresponding to a user to prompt the user in the user list to bind the device.

[0010] In a possible implementation, the channel collection date configuration table further includes a preset delay duration corresponding to each target channel, and the order information of the target channel indicated by the channel collection date configuration table includes:

[0011] The original order information of the target channel before the current time is obtained, and the original order information includes the establishment time of each order.

[0012] For each target channel, a difference value between the current time and the preset delay duration corresponding to the target channel indicated by the channel collection date configuration table is obtained, and the difference value is a target time corresponding to each target channel, and the preset delay duration represents a duration from when a user books a device through the corresponding target channel to when the device can be used.

[0013] According to the original order information, the original order information of each target channel in which the establishment time is before the corresponding target time is obtained as the order information of the target channel.

[0014] In a possible implementation, the target order information is determined based on the binding parameter of the device and the promotion binding device category control configuration table, and the target order information includes:

[0015] According to the binding parameter of the device, a bound device in the order information is determined, and the bound device is removed from the order information to obtain first order information.

[0016] From the first order information, a target device type indicated by the promotion binding device category control configuration table and order information corresponding to the target device type are screened out to generate second order information.

[0017] The historical target order information processed within a first preset duration before the current time is obtained.

[0018] According to the historical target order information, information same as the historical target order information is removed from the second order information to obtain third order information.

[0019] The target order information is determined based on the third order information.

[0020] In a possible implementation, the channel collection date configuration table further includes a first priority corresponding to each target channel, and the target order information is determined based on the third order information, and the target order information includes:

[0021] It is determined whether there are at least two target orders of different target channels but with same mapping relationship between a user and a device in the third order information.

[0022] If yes, the same at least two orders are de-duplicated according to the first priority corresponding to each target channel in the channel collection date configuration table, and the order with the highest first priority of the target channel in the same target order is retained.

[0023] After the same orders in the third order information are de-duplicated, fourth order information is obtained.

[0024] The target order information is determined based on the fourth order.

[0025] In a possible implementation, the promotion-bundling device category management configuration table further includes a preset second priority corresponding to each device model under each target device type, and the target order information is determined based on the fourth order, including:

[0026] It is determined whether there are at least two orders with the same target device type and the same user based on the fourth order.

[0027] If yes, the same at least two orders with the same target device type and the same user are de-duplicated according to the preset second priority corresponding to each device model under each target device type in the promotion-bundling device category management configuration table, and the order with the highest second priority of the device model in the same target device type is retained.

[0028] After the fourth order is de-duplicated, the target order information is obtained.

[0029] In a possible implementation, the target order information is determined based on the target order information, and the user list to be pushed is determined, including:

[0030] The historical push times corresponding to each user terminal corresponding to each user in the target order information within a second preset time period before the current time are obtained.

[0031] Orders corresponding to users with a historical push time reaching a preset number of times are removed from the target order information, and a user list to be pushed is obtained.

[0032] In a possible implementation, the information is pushed to the terminal corresponding to the user according to the user list, including:

[0033] The application program login record of the terminal corresponding to the user in the user list to be pushed is obtained.

[0034] The terminal corresponding to the user who has not logged in the application program within a third preset time period is pushed information in a first manner according to the application program login record, and the first manner is used to indicate a non-application prompt manner.

[0035] Information is pushed to the terminals of users who have logged into the application within a third preset time period in a second manner, wherein the second manner is used to indicate the application prompts.

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

[0037] Based on the user list, the corresponding terminal and smart device of the user are bound.

[0038] Secondly, this application provides a device binding prompting device, the device comprising:

[0039] The acquisition module is used to acquire order information of the target channel indicated by the channel acquisition date configuration table. The channel acquisition date configuration table includes the target channels for which order information needs to be collected. The target channels include at least one of the sales channel, logistics channel and installation channel. The order information includes the mapping relationship between the user and the device corresponding to each order.

[0040] The calculation module is used to calculate the binding parameters of the device recorded in the order information based on the order information and the device binding record. The binding parameters are used to indicate whether the device has been bound to a user.

[0041] The first processing module is used to determine the target order information based on the binding parameters of the device and the binding device category management configuration table. The binding device category management configuration table includes the target device type for which order information needs to be collected and the target channel for which the information needs to be collected corresponding to the target device type.

[0042] The second processing module is used to determine a list of users to be pushed to based on the target order information, and push information to the terminals corresponding to the users according to the user list to prompt the users in the user list to bind their devices.

[0043] Thirdly, this application provides a computer-readable storage medium comprising a stored program, wherein the program, when executed, performs the method described in any one of the first aspects.

[0044] Fourthly, this application provides an electronic device including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to perform the method described in any one of the first aspects through the computer program.

[0045] This invention provides a device binding prompt method, device, and medium. By acquiring order information from target channels involving user-device relationships, and calculating the binding parameters of the devices recorded in the order information based on the order information and device binding records, unbound devices in the order information are identified. Further, target order information is determined based on a pre-configured device binding prompt category control configuration table. Based on the target order information, a user list to be pushed is determined, and information is pushed to the corresponding terminals of the users to prompt users on the user list to bind their devices. This method integrates order information from sales, logistics, and installation channels to achieve accurate device binding prompts, thereby effectively improving user experience and ensuring that prompts are pushed to users in a timely and accurate manner, prompting them to bind unbound devices. Simultaneously, the configuration table allows for flexible adjustment of target channels and device types, achieving automated management of device binding prompts. Attached Figure Description

[0046] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0047] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0048] Figure 1 This is a schematic diagram illustrating an application scenario provided in the embodiments of this application;

[0049] Figure 2 This is a flowchart of a device binding prompting method according to an embodiment of this application. Figure 1 ;

[0050] Figure 3 This is a flowchart of a device binding prompting method according to an embodiment of this application. Figure 2 ;

[0051] Figure 4 This is a schematic diagram of a device binding prompting device according to an embodiment of this application;

[0052] Figure 5 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0053] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0054] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0055] To address the aforementioned issues, this application provides a device binding prompt method. By acquiring order information from target channels involving user-device relationships, and calculating the binding parameters of the devices recorded in the order information based on the order information and device binding records, the method identifies unbound devices within the order information. Further, based on a pre-configured device binding category control configuration table, target order information is determined. Based on the target order information, a user list to be pushed to is determined, and information is pushed to the corresponding terminals of the users to prompt the users on the user list to bind their devices. This method integrates order information from sales, logistics, and installation channels to achieve accurate device binding prompts. This effectively improves user experience, ensuring that prompts are pushed to users in a timely and accurate manner, prompting them to bind unbound devices. Simultaneously, by flexibly adjusting the target channels and device types using the configuration table, automated management of device binding prompts is achieved.

[0056] Meanwhile, the method provided in this application can be widely applied to whole-house intelligent digital control application scenarios such as smart home, smart home appliances ecosystem, and intelligence house ecosystem.

[0057] Figure 1 This is a schematic diagram illustrating an application scenario provided in an embodiment of this application. For example... Figure 1As shown, firstly, order data can be obtained from designated sales, logistics, and installation channels. This is because order information from these channels contains the correspondence between users and devices, providing a valid basis for subsequent device binding promotion. The obtained order data can be aggregated into a unified database, becoming a database providing user-device mapping relationships. Furthermore, existing device binding records contain the binding status of all current devices. Based on this record, it can be confirmed which devices in the order information have not yet been bound to users, and these devices have been marked. Then, according to the pre-configured device category control settings for device binding promotion, target order information requiring binding prompts is filtered out. The device category control configuration table lists the device types that require key attention and their corresponding channel requirements. It allows for flexible configuration of which device types need binding prompts and from which channels to obtain order data for these device types. A user list to be pushed to is generated from the target order information. During the generation of this list, deduplication operations can be performed to ensure that each user receives a push only once, avoiding duplicate pushes. Based on the generated user list, binding prompt information is pushed to the user's terminal device. The user receives the prompt information on their terminal device, prompting them to complete the device binding operation.

[0058] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Where there is no conflict between the embodiments, the following embodiments and features can be combined with each other. Furthermore, the timing of the steps in the following method embodiments is merely an example and not a strict limitation.

[0059] Figure 2 This is a flowchart of a device binding prompting method according to an embodiment of this application. Figure 1 .like Figure 2 As shown, the method includes:

[0060] S201. Obtain the order information corresponding to the target channel indicated by the channel collection date configuration table.

[0061] The channel collection date configuration table includes target channels for which order information needs to be collected. The target channels include one or more combinations of sales channels, logistics channels, and installation channels. The order information includes the mapping relationship between the user corresponding to each order and the purchased device.

[0062] In this step, the channel collection date configuration table records the target channels for which order information needs to be collected, including sales channels, logistics channels, and installation channels. The purpose of this configuration table is to help the system acquire order information from highly relevant channels at appropriate times, thereby ensuring the timeliness and accuracy of device binding prompts. The system acquires the original order information from the target channels, including the order creation time and the mapping relationship between the user and the device. Furthermore, the specific data collection scope for the target channels can be determined based on the actual business scenario. In this embodiment, in a typical shopping scenario, when a user places an order for a device, a sales order is first generated in the sales channel; after the device is delivered according to the sales order, a corresponding logistics order is generated in the logistics channel; when the device arrives at the delivery location and requires installation, a corresponding installation order is generated in the installation channel, providing the user with the corresponding installation service. Therefore, each channel's order for a device requires a certain period until the user can use it. At this time, a preset time range can be used to collect order data that meets the requirements, excluding devices that are in transit or being installed after purchase.

[0063] For example, the channel collection date configuration table also includes a preset delay duration for each target channel, and obtaining the order information of the target channel indicated by the channel collection date configuration table includes:

[0064] Obtain the original order information of the target channel up to the present, including the creation time of each order;

[0065] For each target channel, based on the preset delay duration indicated by the channel collection date configuration table, the difference between the current time and the corresponding preset delay duration is obtained. The difference is the target time corresponding to each target channel, and the preset delay duration represents the time from when a user reserves a device through the corresponding target channel until it becomes usable.

[0066] Based on the original order information, obtain the original order information of each target channel whose establishment time is before the corresponding target time, and use it as the order information of the target channel.

[0067] It's important to note that the preset delay duration for each channel represents the time interval between a user ordering a device through that channel and being able to use the device. For example, a sales channel might represent the time from purchase to receipt or installation completion, a logistics channel from shipment to receipt, and an installation channel from receipt to installation completion. Based on the preset delay duration, the difference between the current time and the preset delay duration is calculated. The current time is a point in time, and subtracting the corresponding preset delay duration yields another point in time. This calculated point in time is the deadline for collecting orders from the corresponding channel. Orders created before the target time are used as the final target order information. The above example ensures that only orders where the device may already be ready for binding are selected, avoiding premature or meaningless binding prompts.

[0068] For example, suppose a user purchases a smart home device through an e-commerce platform. The device is expected to take 3 days from order placement to delivery, 2 days from delivery to receipt, and 1 day from receipt to installation completion. These correspond to the preset delay times for each target channel: 6 days for the sales channel, 3 days for the logistics channel, and 1 day for the installation channel.

[0069] S202. Based on the order information and the device binding record, determine the binding parameters of the device recorded in the order information. The binding parameters are used to indicate whether the device has been bound to a user.

[0070] In this step, information for each device is extracted from the order information and compared with existing device binding records. The binding parameter is a flag indicating whether a device is bound to a user. If a device is bound, the binding parameter is marked as "bound"; if not, it is marked as "not bound." Once a device is bound to a user, it is added to the device binding record, which contains all bound devices. It's important to note that device-user binding can mean that a user associates with a device through a client application, enabling the user to control the device. For example, through the device's corresponding application, the user binds the device to achieve intelligent, remote control via the application.

[0071] S203. Based on the binding parameters of the device and the binding device category control configuration table, determine the target order information.

[0072] The device category management configuration table includes the target device types for which order information needs to be collected, as well as the target channels for which the information needs to be collected for the corresponding target device types.

[0073] In this step, the Device Category Control Configuration Table lists the device types that need attention and their corresponding channels. These devices have binding functionality and related smart functions after binding, therefore binding prompts are required. Combining the device binding parameters with this configuration table, the devices that truly require binding prompts are filtered out. That is, only those device types that are "unbound" and listed in the configuration table will be included in the target order information.

[0074] S204. Based on the target order information, determine the list of users to be pushed to, and push information to the terminals corresponding to the users according to the user list to prompt the users in the user list to bind their devices.

[0075] In this step, a list of users to be pushed to will be generated from the filtered order information. The list contains all users who need to receive binding prompts and their device information. Since the target order information may contain the same device and corresponding user information appearing on different channels, or the historical analysis may have already prompted a device and corresponding user to bind but the filtering operation was repeated, such duplicate data can be deduplicated when determining the list of users to be pushed to, thereby avoiding data duplication and causing users to receive redundant information, which will affect the user experience.

[0076] For example, determining the list of users to be pushed to based on the target order information includes:

[0077] Get the historical push count for each user terminal in the target order information within a second preset time period before the current time;

[0078] Orders corresponding to users whose historical push notifications have reached a preset number are removed from the target order information to obtain a list of users to be pushed to.

[0079] It's important to note that some users may have received device binding prompts multiple times but failed to complete the binding for various reasons. Continuing to push the same prompts to these users might be considered disruptive, thus degrading the user experience. Therefore, the system can aggregate each user's push notification history within a specified time period and compare these counts to a preset maximum number of pushes. By limiting the number of pushes, the system avoids excessively bothering users and also helps filter out users who are more likely to want or need the binding prompts. This improves the effectiveness of push notifications and user satisfaction. For example, user A has received 5 device binding prompts but has not yet bound the device. If the system presets a maximum of 5 pushes, user A will not be included in the next list generation, thus avoiding duplicate push interference.

[0080] For example, the step of pushing information to the terminal corresponding to the user based on the user list includes:

[0081] Obtain the application login records of the terminals corresponding to the users in the list of users to be pushed to;

[0082] Based on the application login record, information is pushed to the terminal of the user who has not logged into the application within a third preset time period in a first manner, wherein the first manner is used to indicate a non-application prompt method.

[0083] Information is pushed to the terminals of users who have logged into the application within a third preset time period in a second manner, wherein the second manner is used to indicate the application prompts.

[0084] It's important to note that understanding user activity levels helps in choosing the appropriate push notification method. If a user hasn't recently logged into the application, a push notification directly within the application might not be seen, so a more attention-grabbing approach is needed. For example, you can access the application's login logs to obtain each user's login history within a specified time period. For users who haven't logged into the application within a third preset time period, a non-application push notification method (such as SMS, email, or phone notification) can be chosen, as this is more likely to attract their attention. For users who have logged into the application within the third preset time period, the system will choose to push notifications within the application (such as in-app notifications or pop-ups), which is less intrusive and suitable for already active users. For instance, if user B hasn't recently logged into the application, a device binding reminder could be sent via SMS to ensure the user doesn't miss important information. Conversely, if user C frequently logs into the application, an in-app push notification could remind the user to complete device binding.

[0085] For example, the method further includes binding the user's corresponding terminal and smart device according to the user list.

[0086] In some scenarios, the user's terminal can also authorize the binding of smart devices in advance. That is, after purchasing the device, the user's terminal can also automatically bind the terminal according to the usage status of the device, providing users with a seamless binding operation, which can further improve the user experience.

[0087] The device binding prompt method provided in this application obtains order information from target channels involving user-device relationships. Based on the order information and device binding records, it calculates the binding parameters of the devices recorded in the order information to identify unbound devices in the order information. Further, based on a pre-configured device binding category control configuration table, it determines target order information. Based on the target order information, it determines a list of users to be pushed to and pushes information to the corresponding terminals of the users to prompt users on the user list to bind their devices. This method integrates order information from sales, logistics, installation, and other channels to achieve accurate device binding prompts. This effectively improves user experience, ensuring that prompts are pushed to users in a timely and accurate manner, prompting them to bind unbound devices. Simultaneously, by flexibly adjusting the target channels and device types using the configuration table, it achieves automated management of device binding prompts.

[0088] Figure 3 This is a flowchart of a device binding prompting method according to an embodiment of this application. Figure 2 .like Figure 3 As shown, the method includes:

[0089] S301. Based on the order information and the device binding record, calculate the binding parameters of the device recorded in the order information. The binding parameters are used to indicate whether the device has been bound to a user.

[0090] S302. Based on the binding parameters of the device, determine the devices already bound in the order information, and remove the bound devices from the order information to obtain the first order information.

[0091] It's important to note that in a multi-channel environment, multiple orders may involve the same device. Therefore, it's necessary to clearly define the binding status of each device to avoid duplicate binding operations or prompts. For example, this can be achieved by querying the device binding record database to obtain the binding status of each device, comparing it with the current order information, and generating corresponding binding parameters (such as "bound" or "not bound"). Based on the binding parameters generated in the previous step, order information for unbound devices is filtered out and stored in the first order information, avoiding duplicate prompts or operations for bound devices, improving efficiency and reducing unnecessary user actions.

[0092] S303. From the first order information, filter out the target equipment type indicated by the bundled equipment category control configuration table and the order information corresponding to the target equipment type, and generate the second order information.

[0093] In this step, the device type for analysis and processing can be specified through the device category management configuration table. The device type specified in the configuration table indicates the type of device that meets the binding conditions. For example, the device has network connectivity or also has user-end intelligent control functionality.

[0094] S304. Obtain historical target order information that has been processed within the first preset time period before the current time.

[0095] S305. Based on the historical target order information, remove information that is the same as the historical target order information from the second order information to obtain the third order information.

[0096] Historical target orders represent the target order information processed in the last time. By comparing historical order information with current order information, it ensures that only new or unprocessed orders are processed, preventing the duplicate processing of the same order information, which would lead to redundant operations or repeated prompts. For example, duplicate order information can be identified and removed by comparing the unique identifier of the order (such as order number, device ID, etc.).

[0097] S306. Confirm whether there are at least two target orders in the third order information that have different target channels but the same mapping relationship between the indicated user and device.

[0098] S307. If so, then according to the first priority corresponding to each target channel in the channel collection date configuration table, deduplication is performed on at least two identical orders, and the order with the highest first priority of the target channel among the identical target orders is retained.

[0099] S308. If not, then the third order will be treated as the fourth order.

[0100] It's important to note that the same device may be recorded through different channels (such as sales and logistics channels). Therefore, it's necessary to check for duplicate mappings to avoid redundant processing. If the same user-device mapping is found across different channels, these orders are deduplicated based on their priority in the channel collection date configuration table, retaining only the highest-priority orders. This ensures that processed order information originates from the highest-priority channel, improving data reliability and consistency. For example, the priority of different channels can be determined based on their ability to more accurately determine whether the device has been used by the user. For instance, installation orders are closer to the time the user used the device, thus they can be considered the highest-priority channel. Logistics orders, on the other hand, are further removed from the time the user used the device compared to installation orders, so logistics can be prioritized after installation.

[0101] S309. After deduplicating identical orders in the third order information, the fourth order information is obtained, and the target order information is determined based on the fourth order.

[0102] For example, the bundled device category control configuration table also includes a preset second priority for each device model under each target device type, and the determination of the target order information based on the fourth order includes:

[0103] Based on the fourth order, confirm whether there are at least two orders with the same target device type and the same user;

[0104] If so, according to the preset second priority corresponding to each device model under each target device type in the device category control configuration table, at least two orders with the same target device type and the same user are deduplicated, and the order with the highest second priority of device model in the same target device type is retained;

[0105] After deduplication of the fourth order is completed, the target order information is obtained.

[0106] It's important to note that in real-world scenarios, a single user may purchase multiple devices of the same category through different channels or at different times. In such cases, it's necessary to determine whether these devices require repeated binding or processing. Different device models may have different priorities. For example, some device models may be the latest or higher-end models, thus requiring priority processing or binding notifications. Priority management ensures these devices receive processing, while also alerting users to the need for the same operation on other related devices, thus avoiding excessive disruption from similar notifications. For instance, if user A purchases two smart door locks, one a high-end model and the other a basic model, the order for the high-end model can be retained and the order for the basic model can be discarded based on the priority in the configuration table.

[0107] The device binding prompting method provided in this application reduces redundant operations and avoids repeated prompts for already bound devices by removing orders for already bound devices, thus improving processing speed. Secondly, it accurately filters order information for target device types, making push notifications more targeted and effectively avoiding binding prompts irrelevant to users. By removing historical order information, it further prevents duplicate processing and ensures data accuracy. The priority mechanism ensures that in complex scenarios involving multiple channels and devices, orders for key devices and high-priority channels are processed first, ultimately achieving reasonable resource allocation and priority execution of important tasks, improving overall stability and user satisfaction.

[0108] The devices that can be bound in this embodiment of the application may not be limited to smart air conditioners, smart range hoods, smart refrigerators, smart ovens, smart stoves, smart washing machines, smart water heaters, smart washing equipment, smart dishwashers, smart projectors, smart TVs, smart clothes racks, smart curtains, smart audio-visual systems, smart sockets, smart speakers, smart speakers, smart fresh air systems, smart kitchen and bathroom equipment, smart bathroom equipment, smart robot vacuum cleaners, smart window cleaning robots, smart mopping robots, smart air purifiers, smart steam ovens, smart microwave ovens, smart water heaters, smart air purifiers, smart water dispensers, smart door locks, etc. The corresponding user terminal may not be limited to PCs, mobile phones, tablets, etc.

[0109] Corresponding to the above method, this application also provides a device binding prompting device. Figure 4 This is a schematic diagram of a device binding prompting device according to an embodiment of this application; as shown below. Figure 4 As shown, the device includes:

[0110] The acquisition module 401 is used to acquire order information of the target channel indicated by the channel acquisition date configuration table. The channel acquisition date configuration table includes the target channels for which order information needs to be collected. The target channels include at least one of the sales channel, logistics channel and installation channel. The order information includes the mapping relationship between the user and the device corresponding to each order.

[0111] The calculation module 402 is used to calculate the binding parameters of the device recorded in the order information based on the order information and the device binding record. The binding parameters are used to indicate whether the device has been bound to a user.

[0112] The first processing module 403 is used to determine the target order information based on the binding parameters of the device and the binding device category management configuration table. The binding device category management configuration table includes the target device type for which order information needs to be collected and the target channel for which the order information needs to be collected corresponding to the target device type.

[0113] The second processing module 404 is used to determine a list of users to be pushed to based on the target order information, and push information to the terminals corresponding to the users according to the user list to prompt the users in the user list to bind their devices.

[0114] Figure 5 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Figure 5 As shown, the electronic device 50 provided in this embodiment includes at least one processor 501 and a memory 502. The device 50 also includes a communication component 503. The processor 501, memory 502, and communication component 503 are connected via a bus 504.

[0115] In a specific implementation, at least one processor 501 executes computer execution instructions stored in the memory 502, causing at least one processor 501 to perform the above method.

[0116] The specific implementation process of processor 501 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0117] In the above Figure 5 In the illustrated embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0118] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0119] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0120] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the method described above.

[0121] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0122] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0123] The division of units described herein is merely a logical functional division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0124] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0125] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0126] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0127] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0128] The technical solutions of this application have been described above with reference to the preferred embodiments shown in the accompanying drawings. However, it is readily understood by those skilled in the art that the scope of protection of this application is obviously not limited to these specific embodiments. The above embodiments are only used to illustrate the technical solutions of this application and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. These modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A device binding prompt method, characterized in that, The method comprises: obtaining order information corresponding to a target channel indicated by a channel collection date configuration table, the channel collection date configuration table comprising a target channel for which order information needs to be collected, the target channel comprising one or more combinations of a sales channel, a logistics channel and an installation channel, and the order information comprising a mapping relationship between a user corresponding to each order and a purchased device; determining a binding parameter of a device recorded in the order information according to the order information and a device binding record, the binding parameter being used to indicate whether the device has been bound to a user; determining target order information based on the binding parameter of the device and a promotion binding device category control configuration table, the promotion binding device category control configuration table comprising a target device type for which order information needs to be collected and a target channel corresponding to the target device type for which order information needs to be collected; determining a user list to be pushed based on the target order information, and performing information pushing to a terminal corresponding to a user according to the user list to prompt the user in the user list to bind a device.

2. The method of claim 1, wherein, The channel collection date configuration table further comprises a preset delay time length corresponding to each target channel, and the order information of the target channel indicated by the channel collection date configuration table comprises: obtaining original order information of the target channel before the current time, the original order information comprising a creation time of each order; for each target channel, obtaining a difference between the current time and the preset delay time length corresponding to the target channel according to the preset delay time length corresponding to the target channel indicated by the channel collection date configuration table, the difference being a target time corresponding to each target channel, and the preset delay time length representing a time length from when a user places an order for a device through the corresponding target channel to when the device can be used; obtaining original order information of each target channel in which the creation time is before the corresponding target time as the order information of the target channel according to the original order information.

3. The method of claim 1, wherein, The determination of the target order information based on the binding parameter of the device and the promotion binding device category control configuration table comprises: determining a bound device in the order information according to the binding parameter of the device, and excluding the bound device in the order information to obtain first order information; selecting a target device type indicated by the promotion binding device category control configuration table and order information corresponding to the target device type from the first order information to generate second order information; obtaining historical target order information processed within a first preset time length before the current time; excluding information same as the historical target order information in the second order information according to the historical target order information to obtain third order information; determining the target order information based on the third order information.

4. The method of claim 3, wherein, The channel collection date configuration table further comprises a first priority corresponding to each target channel, and the determination of the target order information based on the third order information comprises: determining whether there are at least two target orders of different target channels but with the same mapping relationship between a user and a device in the third order information. If yes, the same at least two orders are de-duplicated according to a first priority corresponding to each target channel in a channel collection date configuration table, and an order with the highest first priority of the target channel in the same target order is retained. After de-duplicating the same orders in the third order information, fourth order information is obtained. The target order information is determined based on the fourth order.

5. The method of claim 4, wherein, The promotion binding device category management configuration table further includes a preset second priority corresponding to each device model under each target device type, and the determination of the target order information based on the fourth order includes: According to the fourth order, it is determined whether there are at least two orders with the same target device type and the same user; If yes, the same at least two orders are de-duplicated according to a first priority corresponding to each target channel in a channel collection date configuration table, and an order with the highest first priority of the target channel in the same target order is retained. After de-duplicating the same orders in the third order information, fourth order information is obtained.

6. The method of claim 5, wherein, The target order information is determined based on the fourth order. The target order information is determined based on the fourth order. The target order information is determined based on the fourth order.

7. The method of claim 6, wherein, The target order information is determined based on the fourth order. The target order information is determined based on the fourth order. The method further includes: According to the user list, the terminal and the smart device corresponding to the user are bound.

8. The method of claim 1, wherein, The computer-readable storage medium includes a stored program, wherein the program executes the method of any one of claims 1-8 when running. The memory stores a computer program, and the processor is configured to execute the method of any one of claims 1-8 through the computer program.

9. A computer readable storage medium, characterized in that, ​ 10. An electronic device comprising a memory and a processor, characterized in that, ​

Images