A smart home scene sharing method, device and electronic equipment

Abstract

Embodiments of the present application provide a smart home scene sharing method, device and electronic equipment. The method comprises: obtaining a shared smart scene rule; abstracting the shared smart scene rule to generate an abstract smart scene rule; concretizing the abstract smart scene rule to generate a concrete smart scene rule; and sharing the concrete smart scene rule with the scene application user. According to the method of the embodiments of the present application, the difficulty of technical personnel configuring a smart scene rule is greatly reduced, the difficulty of the user sharing a smart scene rule is reduced, and the difficulty of the scene application user applying a shared smart scene rule is reduced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of intelligent terminals, in particular to a smart home scene sharing method and device and electronic equipment. BACKGROUND

[0002] Smart home is a platform based on residence, which uses integrated wiring technology, network communication technology, security and protection technology, automatic control technology, audio and video technology to integrate facilities related to home life, build an efficient management system of residential facilities and family affairs, and improve the safety, convenience, comfort, artistry and environmentally friendly energy-saving living environment of home.

[0003] Smart scene rules are a kind of intelligent rules formed by combining the state of devices, time conditions and device executable actions relying on a smart home platform. According to whether the rules contain conditions, the smart scene rules can be divided into automatic scene rules and manual scene rules. Manual scene rules: a person combines device actions to display a button on the smart home platform to realize one-key control of multiple devices. Automatic scene rules: conditions (such as time, weather state, location information, device state, device event) and device actions are combined to form a rule of "when *** do ***", and when the server detects that the condition is met, it automatically controls the device to execute the corresponding action.

[0004] In the prior art, smart scene rules are usually manually created by users according to the actual situation of the smart home purchased by the users. However, since the process of manually creating smart scene rules is very complex, the willingness of users to manually create smart scene rules is not high. Even if the users create smart scene rules, they are usually created based on some simple control rules, and in addition, the users lack understanding of the smart home purchased by the users, so the smart scene rules manually created by the users cannot well meet the needs of the users, and the user experience of smart scene rules is not ideal. SUMMARY

[0005] In view of the problem that the user experience of smart scene rules in the prior art is not ideal, the present application provides a smart home scene sharing method, device and electronic equipment, and further provides a computer readable storage medium.

[0006] The embodiments of the present application adopt the following technical solutions:

[0007] In a first aspect, the present application provides a smart home scene sharing method, comprising:

[0008] obtaining a shared smart scene rule;

[0009] abstracting the shared smart scene rule to generate an abstract smart scene rule, including: obtaining a device type description and / or a device function description of a smart home device in the shared smart scene rule and a corresponding device action description; saving the device type description and / or the device function description and the corresponding device action description to generate the abstract smart scene rule;

[0010] concretizing the abstract smart scene rule to generate a concrete smart scene rule, including: matching a smart home device currently owned by a scene application user according to the device type description and / or the device function description in the abstract smart scene rule to generate the concrete smart scene rule containing the smart home device currently owned by the scene application user;

[0011] sharing the concrete smart scene rule with the scene application user.

[0012] According to the method flow of the first aspect, a technical person only needs to create a smart scene rule according to a conventional operation and then share it on a sharing platform, without considering the specific model of a smart home device owned by a user, without providing a complete scene rule for different smart home device models, and greatly reducing the difficulty of a technical person in configuring a smart scene rule.

[0013] Further, before a scene sharing user uploads a shared smart scene rule, the scene sharing user does not need to make any adjustment to the shared smart scene rule created by the scene sharing user, greatly reducing the difficulty of the user in sharing a smart scene rule.

[0014] Further, before a scene application user applies an abstract smart scene rule, the scene application user only needs to know the final effect of the abstract smart scene rule and the required device type, without needing to know the specific device model applying the abstract smart scene rule, so as to achieve the purpose of the same effect of different devices, and greatly reducing the difficulty of the scene application user in applying a shared smart scene rule.

[0015] In a feasible implementation manner of the first aspect, the method further includes: creating the shared smart scene rule, including:

[0016] calling a device condition parameter from a device configuration file library;

[0017] setting a device condition value for the device condition parameter;

[0018] calling a device action parameter from the device configuration file library;

[0019] setting a device action value for the device action parameter;

[0020] generate the shared smart scene rule based on the device condition value and the device action value.

[0021] In a possible implementation of the first aspect, the configuration file of the smart home device stores a device function code, a device type code, and / or a device action code, wherein the device function code, the device type code, and the device action code are unified codes for different manufacturers.

[0022] According to the implementation of the first aspect, the unified mapping of the device function, the device type, and the device action on devices of different manufacturers can be realized by reading the configuration file of the smart home device, which greatly reduces the difficulty of creating, abstracting, and concretizing the smart scene rule.

[0023] In a possible implementation of the first aspect, the shared smart scene rule includes a device location limit.

[0024] The abstracting the shared smart scene rule to generate an abstract smart scene rule includes: obtaining the device type description and / or the device function description, the corresponding device action description, and the corresponding device location limit of the smart home device in the shared smart scene rule; and saving the device type description and / or the device function description, the corresponding device action description, and the corresponding device location limit to generate the abstract smart scene rule.

[0025] The concretizing the abstract smart scene rule to generate a concrete smart scene rule includes: matching the smart home device currently owned by the scene application user according to the device type description and / or the device function description and the corresponding device location limit in the abstract smart scene rule to generate the concrete smart scene rule.

[0026] According to the implementation of the first aspect, since the abstract smart scene rule includes the device location limit, the determination of the smart home device in the concrete smart scene rule refers to the device location limit included in the abstract smart scene rule, which can effectively ensure the consistency of the application effect of the concrete smart scene rule and the application effect of the shared smart scene rule, thereby greatly improving the user experience.

[0027] In a possible implementation of the first aspect, the method further includes obtaining a house type corresponding to the shared smart scene rule.

[0028] The abstract smart scene rule is abstracted to generate an abstract smart scene rule, including: according to the device type description and / or the device function description, the corresponding device location definition and the house type in the abstract smart scene rule, and in combination with the house type of the scene application user, matching the smart home device currently owned by the scene application user to generate the abstract smart scene rule.

[0029] According to the implementation manner of the first aspect, since the determination of the smart home device in the concrete smart scene rule refers to the house type of the scene sharing user, the consistency of the application effect of the concrete smart scene rule and the application effect of the shared smart scene rule can be effectively ensured, thereby greatly improving the user experience.

[0030] In a feasible implementation manner of the first aspect, the house type is recorded in an encoding manner.

[0031] In a feasible implementation manner of the first aspect, the method further includes: obtaining a general condition description of the smart home device in the smart home scene corresponding to the shared smart scene rule;

[0032] The abstract smart scene rule is abstracted to generate an abstract smart scene rule, including:

[0033] According to the general condition description and the smart home device in the shared smart scene rule, a smart home device supplementary description is generated;

[0034] The device type description and / or the device function description of the smart home device in the shared smart scene rule and the corresponding device action description are obtained;

[0035] The device type description and / or the device function description, the corresponding device action description and the smart home device supplementary description are saved to generate the abstract smart scene rule.

[0036] According to the implementation manner of the first aspect, since the abstract smart scene rule contains the smart home device supplementary description referring to the general condition description of the smart home device, after the abstract smart scene rule is concretized, the consistency of the application effect of the concrete smart scene rule and the application effect of the shared smart scene rule can be effectively ensured, thereby greatly improving the user experience.

[0037] In a second aspect, the present application provides a smart home scene sharing device, including:

[0038] A rule obtaining module is configured to obtain a shared smart scene rule.

[0039] an abstracting module configured to abstract the shared smart scene rule to generate an abstract smart scene rule, including: obtaining a device type description and / or a device function description of a smart home device in the shared smart scene rule and a corresponding device action description; and saving the device type description and / or the device function description and the corresponding device action description to generate the abstract smart scene rule;

[0040] a concretizing module configured to concretize the abstract smart scene rule to generate a concrete smart scene rule, including: matching a smart home device currently owned by a scene application user according to the device type description and / or the device function description in the abstract smart scene rule to generate the concrete smart scene rule containing the smart home device currently owned by the scene application user;

[0041] a sharing module configured to share the concrete smart scene rule to the scene application user.

[0042] In a third aspect, the present application provides an electronic device, including a memory for storing computer program instructions and a processor for executing the program instructions, wherein when the computer program instructions are executed by the processor, the electronic device is triggered to execute the method steps of the first aspect.

[0043] In a fourth aspect, the present application provides a computer readable storage medium, which stores a computer program, and when the computer program is run on a computer, the computer is caused to execute the method of the first aspect. BRIEF DESCRIPTION OF DRAWINGS

[0044] Figure 1 Fig. 1 shows a flow chart of a smart home scene sharing method according to an embodiment of the present application;

[0045] Figure 2 Fig. 2 shows a smart home scene sharing application scenario according to an embodiment of the present application;

[0046] Figure 3 Fig. 3 shows a smart home scene sharing application scenario according to an embodiment of the present application;

[0047] Figure 4 Fig. 4 shows a smart scene rule creation flow chart according to an embodiment of the present application;

[0048] Figure 5 Fig. 5 shows a smart home scene sharing system structure schematic diagram according to an embodiment of the present application;

[0049] Figure 6 Fig. 6 shows a smart home scene sharing application scenario according to an embodiment of the present application;

[0050] Figure 7 Fig. 1 shows a schematic diagram of an application scenario of sharing a smart home scene according to an embodiment of the present application. DETAILED DESCRIPTION

[0051] In order to make the objects, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be described clearly and completely below with reference to the embodiments of the present application and corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of protection of the present application.

[0052] The terms used in the embodiment part of the present application are only used to explain the specific embodiments of the present application, but not to limit the present application.

[0053] In view of the problem that the user experience of the smart scene rule in the prior art is not ideal, one of the feasible solutions is to provide the user with the created smart scene rule in a sharing manner. For example, a technical personnel creates a smart scene rule, and a smart home platform shares the smart scene rule created by the technical personnel with a user. Since the technical personnel has a deep understanding of the smart home, the technical personnel can create a smart scene rule containing a relatively complex control rule, thereby enriching the application experience of the smart scene rule. The user directly uses the smart scene rule created by the technical personnel, which saves the user from the tedious operation of manually creating a smart scene rule, and greatly improves the user experience of the smart scene rule.

[0054] For example, in an application scenario, a technical personnel creates a shared smart scene rule Z11 (automatic scene rule) for a sleep scene according to the sleep monitoring function of the Honor Band 4, the remote control function of the Sanside lamp, and the remote control function of the Hegel smart screen: when the Honor Band 4 monitors that the user falls asleep, the user's Sanside lamp is automatically turned off, and the user's Hegel smart screen is also automatically turned off. Then, when the technical personnel creates the above shared smart scene rule Z11, a user A11 who has the Honor Band 4, the Sanside lamp, and the Hegel smart screen can directly use the above shared smart scene rule Z11 created by the technical personnel, without the need to create a smart scene rule for the sleep scene by himself / herself.

[0055] However, in actual application scenarios, due to the variety of types and models of smart home devices, the combination of smart home devices that a user can have is also various. The number of smart scene rules created by technical personnel is limited, and technical personnel cannot completely predict which type and model of smart home device a user will purchase, so the smart scene rules created by technical personnel often do not match the smart home devices of the user. For example, the smart scene rules created by technical personnel do not include the type and model of the smart home device owned by the user; or one or more of the smart home devices included in the smart scene rules created by technical personnel is not the type and model owned by the user. This results in the need to modify the smart scene rules created by technical personnel before the user uses the smart scene rules created by technical personnel, which undoubtedly increases the difficulty of using smart scene rules and reduces the practicality of smart scene rules.

[0056] For example, in an application scenario, taking the above shared smart scene rule Z11 as an example, if the user A21 has the Honor Band 4, the OPO lamp, and the Hegel smart screen. Although the OPO lamp can realize remote switching of the lamp, since the controlled lamp in the shared smart scene rule Z11 is the Sansheng lamp, without modifying the shared smart scene rule Z11, the shared smart scene rule Z11 cannot be applied to the smart home scene of the user A21. Or, if the user A22 has the Honor Band 4, the Sansheng lamp, the OPO lamp, and the Hegel smart screen. Since the controlled lamp in the shared smart scene rule Z11 is the Sansheng lamp, when the user A22 uses the shared smart scene rule Z11, the OPO lamp of the user A22 cannot be controlled.

[0057] Further, to solve the problem of limited number of smart scene rules created by technical personnel, one of the feasible solutions is to share smart scene rules among users. That is, when a user creates a smart scene rule, he or she can share the smart scene rule created by himself or herself with other users for use. In this way, the user can obtain a smart scene rule that matches the type and model of the smart home device owned by himself or herself from the shared smart scene rule, so as to directly use the shared smart scene rule without modifying the smart scene rule, greatly reducing the difficulty of using smart scene rules and enhancing the practicality of smart scene rules.

[0058] However, one of the prerequisites for directly using the shared smart scene rule is that the model of the smart home device of the other user sharing the smart scene rule is consistent with the current user. In actual application scenarios, due to the large number of types of smart home devices, it is possible that the model of the smart home device of the current user is inconsistent with the model of the smart home device of all other users participating in sharing the smart scene rule (for example, the current user uses the latest model of the smart home device, and the other users sharing the smart scene rule have not purchased the smart home device of this model). Then, the current user cannot obtain the shared smart scene rule matching the model of the smart home device.

[0059] In summary, the sharing manner provides the user with the created smart scene rule, which can enable the user to obtain the smart scene rule that can be directly used, thereby saving the user from the cumbersome operation of creating the smart scene rule. However, since the created smart scene rule does not completely match the model of the smart home device of the user, the sharing manner for providing the user with the created smart scene rule cannot achieve the expected effect in practical effect.

[0060] To solve the above problems, in an embodiment of the present application, a new smart home scene sharing manner is provided. When the user and / or the technician share the smart scene rule created by the user and / or the technician, instead of directly saving the shared smart scene rule created by the user and / or the technician as the smart scene rule to be shared with the user later, the smart scene rule created by the user and / or the technician is abstracted to generate an abstract smart scene rule. In the abstract smart scene rule, the model of each scene triggering device and each controlled device is not saved, but the device type description and / or the device function description of each controlled device is saved. When the smart scene rule is shared with the user, instead of directly pushing the abstract smart scene rule to the user, the device type description and / or the device function description of the controlled device in the abstract smart scene rule is matched to the smart home device currently owned by the user to generate a concrete smart scene rule containing the smart home device currently owned by the user, so that the user can directly use the concrete smart scene rule to control the smart home device in the smart home scene. In this way, even if the smart scene rule created by the technician does not match the model of the smart home device of the user, the user can directly use the smart scene rule created by the technician, and the sharing of the smart scene rule can be realized among users with different models of smart home devices.

[0061] The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0062] Figure 1Fig. 1 shows a flowchart of a method for sharing a smart home scene according to an embodiment of the present application. In an embodiment of the present application, as shown in Fig. 1, the following procedure is performed to realize sharing of a smart scene rule: Figure 1

[0063] In step 100, a shared smart scene rule is obtained, wherein the shared smart scene rule is created by a scene sharing user according to his / her own smart home scene, or is created by a technician according to a user's smart home scene that is expected;

[0064] In step 110, the shared smart scene rule is abstracted to generate an abstract smart scene rule, including obtaining a device type description and / or a device function description of a smart home device in the shared smart scene rule, and a corresponding device action description; and saving the device type description and / or the device function description, and the corresponding device action description to generate the abstract smart scene rule;

[0065] In step 120, the abstract smart scene rule is concretized to generate a concrete smart scene rule, wherein the device type description and / or the device function description in the abstract smart scene rule are matched with a smart home device currently owned by a scene application user (so that the device action description in the abstract smart scene rule is matched to the smart home device currently owned by the scene application user) to generate the concrete smart scene rule containing the smart home device currently owned by the scene application user;

[0066] In step 130, the concrete smart scene rule is shared with the scene application user.

[0067] Specifically, in an application scenario, the execution of step 120 can be triggered by the scene application user. For example, when the scene application user needs to apply the abstract smart scene rule generated in step 110 to his / her own smart home scene, the execution of step 120 is triggered, and in step 130, the concrete smart scene rule is sent to a control device of the scene application user to apply the concrete smart scene rule to the smart home scene of the scene application user.

[0068] In an application scenario, the execution of step 120 can be automatically triggered. For example, after step 110 is executed and a new abstract smart scene rule is obtained, step 120 is automatically executed for a specific scene application user (for example, a user with a VIP account, or a user who meets a smart home device possession condition), and in step 130, the generated concrete smart scene rule is actively pushed to the corresponding scene application user.

[0069] ​For example, in an application scenario, taking the above shared smart scene rule Z11 as an example, a technical person creates a shared smart scene rule Z11 for a sleep scene according to the sleep monitoring function of the Honor Band 4, the remote control function of the Sanside lamp, and the remote control function of the Hegel smart screen: after the Honor Band 4 monitors that a user has fallen asleep, the user's Sanside lamp is automatically turned off, and the user's Hegel smart screen is also automatically turned off. Scene abstraction is performed on the shared smart scene rule Z11 to generate an abstract smart scene rule S21: after it is monitored that a user has fallen asleep, the user's lighting device is automatically turned off, and the user's display device is also automatically turned off.

[0070] The user A31 has the Honor Band 4, the Sanside lamp, and the smart television. When the user A31 hopes to apply the abstract smart scene rule S21, the type / function description of the controlled device in the abstract smart scene rule S21 is matched to the smart home devices currently owned by the user A31 to generate a concrete smart scene rule X31: after the Honor Band 4 monitors that a user has fallen asleep, the Sanside lamp is automatically turned off, and the user's smart television is also automatically turned off.

[0071] The user A32 has the Honor Band 4, the Oupu lamp, the Sanside lamp, the Hegel smart screen, and the smart television. When the user A32 hopes to apply the abstract smart scene rule S21, the type / function description of the controlled device in the abstract smart scene rule S21 is matched to the smart home devices currently owned by the user A32 to generate a concrete smart scene rule X32: after the Honor Band 4 monitors that a user has fallen asleep, the user's Sanside lamp is automatically turned off, the Oupu lamp is automatically turned off, the Hegel smart screen is automatically turned off, and the user's smart television is also automatically turned off.

[0072] For another example, in an application scenario, a scene sharing user creates a shared smart scene rule Z12 (a manual scene rule) for a sleep scene: after a sleep scene entering button on a mobile phone is pressed, the user's Sanside lamp is automatically turned off, and the user's Hegel smart screen is also automatically turned off. Scene abstraction is performed on the shared smart scene rule Z12 to generate an abstract smart scene rule S22: after the sleep scene entering button on the mobile phone is pressed, the user's lighting device is automatically turned off, and the user's display device is also automatically turned off.

[0073] The user A33 has a normal lamp connected with a smart switch and a smart television. When the user A33 hopes to apply the abstract smart scene rule S22, the type / function description of the controlled device in the abstract smart scene rule S22 is matched to the smart home devices currently owned by the user A33 to generate a concrete smart scene rule X33: after the sleep scene entering button on the mobile phone of the user A33 is pressed, the smart switch connected with the normal lamp is automatically turned off, and the smart television of the user is also automatically turned off.

[0074] User A 34 owns a normal lamp connected with a smart switch, a ThinkPad lamp, a Hegel smart screen and a smart TV. When user A 34 wants to apply the abstract smart scene rule S22, the type / function description of the controlled device in the abstract smart scene rule S22 is matched to the smart home devices currently owned by user A 34, and the concrete smart scene rule X34 is generated: when the sleep scene button on the mobile phone of user A 34 is pressed, the ThinkPad lamp of the user is automatically turned off, the smart switch connected with the normal lamp is automatically turned off, the Hegel smart screen is automatically turned off, and the smart TV of the user is also automatically turned off.

[0075] From the perspective of a technical staff, the technical staff only needs to create a smart scene rule according to a conventional operation and then share it on a sharing platform, without considering the specific models of the smart home devices owned by a user, without providing complete scene rules for different smart home device models, and thus greatly reducing the difficulty of the technical staff in configuring a smart scene rule.

[0076] From the perspective of a scene sharing user, before the scene sharing user uploads a shared smart scene rule, the scene sharing user does not need to make any adjustment to the shared smart scene rule created by the scene sharing user, and thus greatly reducing the difficulty of the user in sharing a smart scene rule.

[0077] From the perspective of a scene application user, before the scene application user applies an abstract smart scene rule, the scene application user only needs to know the final effect of the abstract smart scene rule and the required device type, without needing to know the specific device model applying the abstract smart scene rule, so as to achieve the purpose of the same effect of different devices, and thus greatly reducing the difficulty of the scene application user in applying a shared smart scene rule.

[0078] Further, in an actual application scenario, the scene abstraction operation of step 110 can be completed by a local device of the scene sharing user or the technical staff when the scene sharing user or the technical staff shares a shared smart scene rule; the scene abstraction operation of step 110 can also be completed by a cloud server when the scene sharing user or the technical staff uploads a shared smart scene rule to the cloud server. Moreover, in an actual application scenario, the scene concretization operation of step 120 can be completed by a local device of the scene application user when the scene application user obtains an abstract smart scene rule; the scene concretization operation of step 120 can also be completed by a cloud server when the scene application user requests the cloud server to apply an abstract smart scene rule.

[0079] Specifically, Figure 2 Fig. 1 shows a smart home scene sharing application scenario according to an embodiment of the present application. As shown in Fig. 1, the smart home scene sharing application scenario includes a scene sharing user, a scene application user and a technical staff. Figure 2As shown, the technician 201 creates a shared smart scene rule Z41 on the computer terminal device 211 and uploads the shared smart scene rule to the scene sharing cloud server 200; the scene sharing cloud server 200 abstracts the shared smart scene rule Z41 into an abstract smart scene rule S41 after receiving the shared smart scene rule Z41 and saves it. The user 202 creates a smart scene rule Z42 on the mobile phone 212, the mobile phone 212 controls the smart home device of the user 202 through the smart scene rule Z42, and the user 202 can also upload the smart scene rule Z42 as a shared smart scene rule Z42 to the scene sharing cloud server 200 through the mobile phone 212; the scene sharing cloud server 200 abstracts the shared smart scene rule Z42 into an abstract smart scene rule S42 after receiving the shared smart scene rule Z42 and saves it.

[0080] The users 203-205 can browse the abstract smart scene rules (for example, the shared smart scene rules S41, S42) saved in the scene sharing cloud server 200 through their own mobile phones 213-215. When one or several of the users 203-205 want to apply the shared smart scene rules saved in the scene sharing cloud server 200, the scene sharing cloud server 200 generates an embodied smart scene rule for the user according to the smart home device of the user who makes the request, embodies the abstract smart scene rule selected by the user, and sends the generated embodied smart scene rule to the user.

[0081] Alternatively, when one or several of the users 203-205 want to apply the shared smart scene rules saved in the scene sharing cloud server 200, the scene sharing cloud server 200 sends the abstract smart scene rule selected by the user to the mobile phone (213-215) of the user (203-205). The mobile phone (213-215) of the user generates a corresponding embodied smart scene rule according to the smart home device model of the user (203-205) himself / herself.

[0082] Specifically, Figure 3 As shown in the application scenario diagram of the smart home scene sharing according to an embodiment of the present application. The user A51 creates a shared smart scene rule Z51 for the honor band 4, the Sansheng lamp and the smart large screen owned by himself / herself. The mobile phone display interface after creation is as shown in Figure 3 As shown in 301, the shared smart scene rule Z51 is:

[0083] If: device (honor band 4), condition (fall asleep);

[0084] Then: device (Sansheng lamp), action (turn off the light);

[0085] Device (Huawei smart TV), action (turn off).

[0086] User A 51 clicks the sharing button 310 in the interface shown in 301, and the shared smart scene rule Z51 is uploaded to the scene sharing cloud server 300. The scene sharing cloud server 300 abstracts the shared smart scene rule Z51 to generate an abstract smart scene rule S51.

[0087] User A 52 can browse the abstract smart scene rule S51 saved on the scene sharing cloud server through his own mobile phone. The mobile phone browsing interface is shown in 302, and the abstract smart scene rule S51 is as follows: Figure 3

[0088] If: device (smart bracelet), condition (fall asleep);

[0089] Then: device (smart lamp), action (turn off the light);

[0090] Device (smart screen), action (turn off).

[0091] When user A 52 wants to use the abstract smart scene rule S51, he clicks the apply button 320 in the interface shown in 302. The scene sharing cloud server 300 obtains the device information of the smart home devices owned by user A 52, instantiates the abstract smart scene rule S51, generates an instantiated smart scene rule X51, and sends the instantiated smart scene rule X51 to the mobile phone of user A 52.

[0092] The mobile phone browsing interface of user A 52 is shown in 303, and the instantiated smart scene rule X51 is as follows: Figure 3

[0093] If: device (smart bracelet XXX), condition (fall asleep);

[0094] Then: device (Oppo lamp), action (turn off the light);

[0095] Device (Hegel smart screen), action (turn off).

[0096] When user A 52 confirms to use the instantiated smart scene rule X51, he clicks the save button 330 in the interface shown in 303. The instantiated smart scene rule X51 is saved to the mobile phone of user A 52.

[0097] Alternatively, in another application scenario, when user A 52 wants to use the abstract smart scene rule S51, he clicks the apply button 320 in the interface shown in 302. The mobile phone of user A 52 generates the instantiated smart scene rule X51 according to the device information of the smart home devices owned by user A 52 and the abstract smart scene rule S51.

[0098] Specifically, Figure 4 ​​Fig. 1 shows a flowchart of creating a smart scene rule according to an embodiment of the present application. A device profile library is used to save device information of smart home devices owned by a user. As shown in Fig. 1, a user creates a smart scene rule by inputting device condition parameters and device action parameters of smart home devices owned by the user. Figure 4 Fig. 1 shows a flowchart of creating a smart scene rule according to an embodiment of the present application. A device profile library is used to save device information of smart home devices owned by a user. As shown in Fig. 1, a user creates a smart scene rule by inputting device condition parameters and device action parameters of smart home devices owned by the user.

[0099] Step 410, device condition parameters are called from the device profile library, for example, sleep monitoring parameters of the Honor Band 4 are called;

[0100] Step 420, device condition values are set for the device condition parameters, for example, for the sleep monitoring parameters of the Honor Band 4, the device condition values are set to be the parameter values corresponding to the user falling asleep;

[0101] Step 430, device action parameters are called from the device profile library, for example, control parameters of the Sansi lamp are called;

[0102] Step 440, device action values are set for the device action parameters, for example, for the control parameters of the Sansi lamp, the device action values are set to be the parameter values corresponding to turning off the lamp;

[0103] Step 450, a smart scene rule is generated based on the device condition values and the device action values.

[0104] Figure 5 Fig. 2 shows a structure diagram of a smart home scene sharing system according to an embodiment of the present application. As shown in Fig. 2, a device profile library 400 is used to save device information of smart home devices owned by a user. A rule creation module 410 is used to create a smart scene rule based on input data of the user (performing steps 410-450 as shown in Fig. 1). Figure 5 As shown in Fig. 2, a device profile library 400 is used to save device information of smart home devices owned by a user. A rule creation module 410 is used to create a smart scene rule based on input data of the user (performing steps 410-450 as shown in Fig. 1). Figure 4 As shown in Fig. 2, a device profile library 400 is used to save device information of smart home devices owned by a user. A rule creation module 410 is used to create a smart scene rule based on input data of the user (performing steps 410-450 as shown in Fig. 1).

[0105] When the smart scene rule is applied, a scene condition detection module 403 detects whether the current scene environment meets the device condition values of the smart scene rule in the scene rule database 402. If yes, an action execution module 404 executes corresponding device actions according to the device action values of the smart scene rule. For example, the scene condition detection module 403 detects whether the sleep monitoring parameters of the Honor Band 4 are the parameter values corresponding to the user falling asleep. If yes, the action execution module 404 calls the parameter values corresponding to turning off the lamp to control the Sansi lamp, thereby turning off the lamp.

[0106] When a user shares a smart scene rule, the scene sharing module 405 sends the smart scene rule selected by the user in the scene rule database 402 to the rule abstraction module 406 as a shared smart scene rule. The rule abstraction module 406 abstracts the shared smart scene rule to generate an abstract smart scene rule, and saves the abstract smart scene rule to the abstract rule database 407 of the scene sharing cloud server.

[0107] When a user wants to use a shared smart scene rule shared by another user, the rule instantiation module 408 obtains the abstract smart scene rule selected by the user from the abstract rule database 407. The rule instantiation module 408 instantiates the abstract smart scene rule based on the device information of the smart home devices owned by the user in the device profile library 400 to generate an instantiated smart scene rule. The instantiated smart scene rule generated by the rule instantiation module 408 is saved to the scene rule database 402, and the scene condition detection module 403 and the action execution module 404 can implement smart control of the smart home device scene based on the instantiated smart scene rule in the scene rule database 402.

[0108] Further, in actual application scenarios, the abstract rule database 407 of the scene sharing cloud server will save multiple abstract smart scene rules that can be selected by a user. The user can confirm the abstract smart scene rule required by the user from the abstract rule database 407 based on multiple different ways.

[0109] Specifically, in an embodiment, when a scene sharing user uploads a shared smart scene rule to the scene sharing cloud server, the scene sharing cloud server generates a two-dimensional code corresponding to the abstract smart scene rule after abstracting the shared smart scene rule to generate an abstract smart scene rule, and sends the two-dimensional code to the scene sharing user. The scene application user can obtain the smart scene rule shared by the scene sharing user from the scene sharing cloud server by scanning the two-dimensional code of the scene sharing user.

[0110] Specifically, in an embodiment, when a scene sharing user uploads a shared smart scene rule to the scene sharing cloud server, the scene sharing user can specify the sharing object (for example, specify a specific user identifier) of the shared smart scene rule. After abstracting the shared smart scene rule to generate an abstract smart scene rule, the scene sharing cloud server directly pushes the abstract smart scene rule to the scene application user specified by the scene sharing user.

[0111] Specifically, in an embodiment, the scene sharing cloud server opens a browsing interface of the abstract smart scene rule, and the scene application user can browse the abstract smart scene rules saved in the scene sharing cloud server through the browsing platform provided by the scene sharing cloud server, so as to select the abstract smart scene rule required by the user.

[0112] Figure 6 Fig. 1 shows a schematic diagram of an application scenario of sharing a smart home scene according to an embodiment of the present application. For example, in the application scenario shown in Fig. 1, when user A 51 clicks the sharing button 310 in the interface shown in 301, the phone display interface is as shown in 302. Figure 3 Figure 6

[0113] For example, when the user A 51 clicks the QR code sharing button 601, the phone of the user A 51 uploads the shared smart scene rule Z51 to the scene sharing cloud server, the scene sharing cloud server abstracts the shared smart scene rule Z51 to generate an abstract smart scene rule S51 and a QR code corresponding to the abstract smart scene rule S51, the QR code corresponding to the abstract smart scene rule S51 is sent to the phone of the user A 51, and the phone of the user A 51 displays the QR code corresponding to the abstract smart scene rule S51. When the user A 52 scans the QR code displayed by the phone of the user A 51 with the phone, the phone of the user A 52 displays the interface shown in 302. Figure 3

[0114] For example, when the user A 51 clicks the account sharing button 602, the phone of the user A 51 displays an account confirmation interface, and confirms the sharing target user A 52 according to the input of the user A 51. The phone of the user A 51 uploads the shared smart scene rule Z51 and the user account identifier of the user A 52 to the scene sharing cloud server, the scene sharing cloud server abstracts the shared smart scene rule Z51 to generate an abstract smart scene rule S51, and pushes a prompt message corresponding to the abstract smart scene rule S51 to the user A 52. The user A 52 clicks the link of the prompt message to enter the interface shown in 302. Figure 3

[0115] For example, when the user A 51 clicks the platform sharing button 603, the phone of the user A 51 uploads the shared smart scene rule Z51 to the scene sharing cloud server, the scene sharing cloud server abstracts the shared smart scene rule Z51 to generate an abstract smart scene rule S51, and saves the abstract smart scene rule S51 to a database for browsing by other users. When the user A 52 uses the phone to select to browse the abstract smart scene rule S51 saved in the database, the phone of the user A 52 displays the interface shown in 302. Figure 3

[0116] ​​​​​Further, in actual application scenarios, for the same type / model of smart home devices, the devices placed in different positions in the house often have different effects, especially for special positions such as bedrooms and balconies. If the positions of the smart home devices are not distinguished in the process of creating the shared smart scene rule, the abstract smart scene rule may not be consistent with the smart scene control effect of the initial shared smart scene rule after the abstract smart scene rule is abstracted from the shared smart scene rule and the abstract smart scene rule is concretized into a concrete smart scene rule.

[0117] For example, in an application scenario, user A 61 creates a shared smart scene rule Z 61 for the honor band 4, Sansi lamp and Oppo lamp owned by user A 61. The Sansi lamp of user A 61 is installed in the bathroom, and the Oppo lamp is installed in the living room. User A 61 hopes that after falling asleep, the Oppo lamp installed in the living room will automatically turn off, and the Sansi lamp installed in the bathroom does not need to be automatically controlled. The created smart scene rule Z 61 is:

[0118] If: device (honor band 4), condition (fall asleep);

[0119] Then: device (Oppo lamp), action (turn off).

[0120] User A 61 shares the smart scene rule Z 61 as a shared smart scene rule to the scene sharing cloud server, and the scene sharing cloud server abstracts the shared smart scene rule Z 61 to generate an abstract smart scene rule S 61. The abstract smart scene rule S 61 is:

[0121] If: device (honor band 4), condition (fall asleep);

[0122] Then: device (smart lamp), action (turn off).

[0123] User A 62 owns the honor band 4, Sansi lamp and Oppo lamp. The Oppo lamp of user A 62 is installed in the bathroom, and the Sansi lamp is installed in the living room. When user A 62 wants to use the abstract smart scene rule S 61, the scene sharing cloud server obtains the device information of the smart home devices owned by user A 62, concretizes the abstract smart scene rule S 61, and generates a concrete smart scene rule X 61. Since in the abstract smart scene rule S 61, the device performing the action is abstracted as a smart lamp, when the abstract smart scene rule S 61 is concretized for the smart home devices owned by user A 62, all smart lamps owned by user A 62 are added to the concrete smart scene rule X 61. The concrete smart scene rule X 61 is:

[0124] If: device (honor band 4), condition (fall asleep);

[0125] For: device (OLED lamp), action (turn off the light);

[0126] For: device (OLED lamp), action (turn off the light);

[0127] That is, for user A61, the final effect of the smart scene rule is that after user A61 goes to sleep, the OLED lamp in the living room is automatically turned off; the Sansi lamp in the bathroom is unchanged. For user A62, the final effect of the smart scene rule is that after user A62 goes to sleep, the Sansi lamp in the living room and the OLED lamp in the bathroom are automatically turned off. User A62 does not achieve the same scene control effect as user A61.

[0128] To solve the above problem, in an embodiment of the present application, a device position limit is added to the smart scene rule, that is, when creating a smart scene rule, not only the device condition and the device action are set, but also the device position of the device participating in the smart scene rule is described, for example, the room name of the room where the device is located is marked in the smart scene rule, for example, living room, bedroom, bathroom, balcony, etc.

[0129] Specifically, the shared smart scene rule uploaded by the user creating and sharing contains a device position limit. In one implementation of step 110, the device type description and / or device function description of the smart home device in the shared smart scene rule, the corresponding device action description, and the corresponding device position limit are obtained; the device type description and / or device function description, the corresponding device action description, and the corresponding device position limit are saved to generate an abstract smart scene rule.

[0130] In one implementation of step 120, in the process of matching the device type description and / or device function description in the abstract smart scene rule to the smart home devices currently owned by the scene application user, the device position limit corresponding to the device type description and / or device function description is also included in the matching reference, that is, according to the device type description and / or device function description and the corresponding device position limit in the abstract smart scene rule, the smart home devices currently owned by the scene application user are matched, so that the device action description in the abstract smart scene rule is matched to the smart home devices currently owned by the scene application user, to generate a concrete smart scene rule.

[0131] Since the abstract smart scene rule contains a device position limit, the determination of the smart home device in the concrete smart scene rule refers to the device position limit contained in the abstract smart scene rule, so that the consistency of the application effect of the concrete smart scene rule and the application effect of the shared smart scene rule can be effectively ensured, thereby greatly improving the user experience.

[0132] For example, in an application scenario, a user A 71 creates a shared smart scene rule Z 71 for a HONOR BAND 4, a Sansi lamp and an OPO lamp owned by the user A 71. The Sansi lamp of the user A 71 is installed in a bathroom, and the OPO lamp is installed in a living room. The created smart scene rule Z 71 is:

[0133] If: device (HONOR BAND 4), condition (sleeping in);

[0134] Then: device (OPO lamp) (living room), action (turn off the light).

[0135] The user A 71 shares the smart scene rule Z 71 as a shared smart scene rule to a scene sharing cloud server. The scene sharing cloud server abstracts the shared smart scene rule Z 71 to generate an abstract smart scene rule S 71. The abstract smart scene rule S 71 is:

[0136] If: device (HONOR BAND 4), condition (sleeping in);

[0137] Then: device (OPO lamp) (living room), action (turn off the light).

[0138] A user A 72 owns a HONOR BAND 4, a Sansi lamp and an OPO lamp. The OPO lamp of the user A 72 is installed in a bathroom, and the Sansi lamp is installed in a living room. When the user A 72 wants to use the abstract smart scene rule S 71, the scene sharing cloud server obtains device information of smart home devices owned by the user A 72 and room information of each device, and concretizes the abstract smart scene rule S 71 to generate a concrete smart scene rule X 71. The concrete smart scene rule X 71 is:

[0139] If: device (HONOR BAND 4), condition (sleeping in);

[0140] Then: device (Sansi lamp) (living room), action (turn off the light).

[0141] That is, for the user A 71, the final effect of the smart scene rule is that after the user A 71 sleeps, the OPO lamp in the living room is automatically turned off, and the Sansi lamp in the bathroom has no change. For the user A 72, the final effect of the smart scene rule is that after the user A 72 sleeps, the Sansi lamp in the living room is automatically turned off, and the OPO lamp in the bathroom has no change. The scene control effect of the user A 72 is consistent with that of the user A 71.

[0142] Further, in actual application scenarios, due to the difference of residential house types, positions with the same function may be given different names. This may cause room matching errors when concretizing the abstract smart scene rule.

[0143] For example, in an application scenario, a user A 81 creates a shared smart scene rule Z 81 for a glory bracelet 4, a Sansi lamp and an Oupu lamp owned by the user A 81. The user A 81 has a two-room-one-living-room house, and the Sansi lamp is installed in the secondary bedroom and the Oupu lamp is installed in the master bedroom. The created smart scene rule Z 81 is:

[0144] If: device (glory bracelet 4), condition (sleeping in);

[0145] Then: device (Oupu lamp) (master bedroom), action (turn off the light);

[0146] Device (Sansi lamp) (secondary bedroom), action (turn off the light).

[0147] The user A 81 shares the smart scene rule Z 81 as a shared smart scene rule to a scene sharing cloud server, and the scene sharing cloud server abstracts the shared smart scene rule Z 81 to generate an abstract smart scene rule S 81. The abstract smart scene rule S 81 is:

[0148] If: device (glory bracelet 4), condition (sleeping in);

[0149] Then: device (Oupu lamp) (master bedroom), action (turn off the light);

[0150] Device (Sansi lamp) (secondary bedroom), action (turn off the light).

[0151] The user A 82 owns the glory bracelet 4, the Sansi lamp and the Oupu lamp. The user A 82 has a one-room-one-living-room house, and the Oupu lamp of the user A 82 is installed in the bedroom and the Sansi lamp is installed in the living room. Since the room names (master bedroom, secondary bedroom and living room) of the user A 81 do not include the room name (bedroom) of the user A 82, if the user A 82 wants to use the abstract smart scene rule S 81, a room matching error will occur in the process of instantiating the abstract smart scene rule S 81.

[0152] Therefore, in order to avoid the position matching error in the instantiation of the abstract smart scene rule, in an embodiment of the present application, the house type (house type of the scene sharing user) corresponding to the shared smart scene rule is recorded when the shared smart scene rule is abstracted, and the device position matching is performed according to the house type of the scene sharing user and the device position limitation in combination with the house type of the scene application user when the abstract smart scene rule is instantiated. That is, according to the device type description and / or device function description in the abstract smart scene rule, the corresponding device position limitation and the house type, the smart home devices currently owned by the scene application user are matched in combination with the house type of the scene application user, so that the device action description in the abstract smart scene rule is matched to the smart home devices currently owned by the scene application user, to generate an instantiated smart scene rule.

[0153] Since the determined reference of the smart home device in the concrete smart scene rule refers to the house type of the scene sharing user, the consistency of the application effect of the concrete smart scene rule and the application effect of the shared smart scene rule can be effectively ensured, thereby greatly improving the user experience.

[0154] For example, the following mapping relationship is established:

[0155]

[0156]

[0157] Table 1

[0158] Taking the above abstract smart scene rule S81 as an example, in an application scene, when user A82 hopes to use the abstract smart scene rule S81, the scene sharing cloud server obtains the device information of the smart home device owned by user A82 and the room information of each device, and generates a concrete smart scene rule X81 by concretizing the abstract smart scene rule S81. In the process of concretizing the abstract smart scene rule S81, based on Table 1, the "bedroom" in the one-room-one-living-room house type corresponds to the "master bedroom" and "secondary bedroom" in the two-room-one-living-room house type, therefore, the concrete smart scene rule X81 is:

[0159] If: device (Honor Band 4), condition (sleep in);

[0160] Then: device (Oppo lamp) (bedroom), action (turn off the light).

[0161] For another example, in an application scene, user A91 creates a shared smart scene rule Z91 for the Honor Band 4, Sisilai 1, Sisilai 2 and Oppo lamp owned by user A91. The house type of user A91 is two-room-one-living-room, Sisilai 1 is installed in the secondary bedroom, Sisilai 2 is installed in the secondary bedroom, and Oppo lamp is installed in the living room. The created smart scene rule Z91 is:

[0162] If: device (Honor Band 4), condition (sleep in);

[0163] Then: device (Oppo lamp) (living room), action (turn off the light).

[0164] User A91 shares the smart scene rule Z91 as a shared smart scene rule to the scene sharing cloud server, and the scene sharing cloud server abstracts the shared smart scene rule Z91 to generate an abstract smart scene rule S91, and the abstract smart scene rule S91 is:

[0165] If: device (Honor Band 4), condition (sleep in);

[0166] Then: device (Oppo lamp) (living room), action (turn off the light).

[0167] User A 92 owns the honor band 4 and Sansheng lamp. The user A 92's house type is a single room, and the user A 92's Oupu lamp is installed in the bedroom. When the user A 92 wants to use the abstract intelligent scene rule S91, the scene sharing cloud server obtains the device information of the smart home device owned by the user A 92 and the room information of each device, and materializes the abstract intelligent scene rule S91 to generate the materialized intelligent scene rule X91. In the process of materializing the abstract intelligent scene rule S91, based on table 1, the "living room" in the two-room-one-hall house type corresponds to the "bedroom" in the single-room house type, therefore, the materialized intelligent scene rule X91 is:

[0168] If: device (honor band 4), condition (sleep in);

[0169] Then: device (Oupu lamp) (bedroom), action (turn off the light).

[0170] Further, in actual application scenarios, when establishing the mapping between different rooms of different house types, a room of a house type may correspond to multiple rooms of another house type, for example, the bedroom in a one-room-one-hall house type corresponds to the master bedroom and the secondary bedroom in a two-room-one-hall house type. However, in some intelligent scene rules, one-to-one correspondence of rooms must be ensured in the materialization process. Therefore, in an embodiment of the present application, the rooms are prioritized, and the matching of the rooms is performed according to the priority order.

[0171] For example, the following mapping relationship is established:

[0172]

[0173]

[0174] Table 2

[0175] For example, in an application scenario, the user A 101 creates a shared intelligent scene rule Z101 for the honor band 4, Sansheng lamp and Oupu lamp owned by himself. The user A 91's house type is a one-room-one-hall, and the Sansheng lamp is installed in the bedroom and the Oupu lamp is installed in the living room. The created intelligent scene rule Z101 is:

[0176] If: device (honor band 4), condition (sleep in);

[0177] Then: device (Oupu lamp) (living room), action (turn off the light).

[0178] The user A 101 shares the intelligent scene rule Z101 as a shared intelligent scene rule to the scene sharing cloud server, and the scene sharing cloud server abstracts the shared intelligent scene rule Z101 to generate the abstract intelligent scene rule S101, and the abstract intelligent scene rule S101 is:

[0179] If: device (bracelet), condition (sleep in);

[0180] Just: device (smart light) (master bedroom), behavior (turn off the light).

[0181] User A102 owns the honor bracelet 4, Sansi light 1, Sansi light 2 and Opl light. The user A102's house type is two rooms and one living room, Sansi light 1 is installed in the master bedroom, Sansi light 2 is installed in the secondary bedroom, and Opl light is installed in the living room. When user A102 wants to use abstract smart scene rule S101, the scene sharing cloud server obtains the device information of the smart home devices owned by user A102 and the room information of each device, and concretizes the abstract smart scene rule S101 to generate the concrete smart scene rule X101. In the process of concretizing the abstract smart scene rule S101, based on table 2, "bedroom" in one room and one living room corresponds to "master bedroom" and "secondary bedroom" in two rooms and one living room, but because "master bedroom" has higher priority than "secondary bedroom", therefore, the concrete smart scene rule X101 is:

[0182] If: device (bracelet), condition (sleep in);

[0183] Just: device (smart light) (master bedroom), behavior (turn off the light).

[0184] User A103 owns the honor bracelet 4, Sansi light and Opl light User A103's house type is two rooms and one living room, Sansi light is installed in the secondary bedroom, and Opl light is installed in the living room. When user A103 wants to use abstract smart scene rule S101, the scene sharing cloud server obtains the device information of the smart home devices owned by user A103 and the room information of each device, and concretizes the abstract smart scene rule S101 to generate the concrete smart scene rule X102. In the process of concretizing the abstract smart scene rule S101, based on table 2, "bedroom" in one room and one living room corresponds to "master bedroom" and "secondary bedroom" in two rooms and one living room, "master bedroom" has higher priority than "secondary bedroom", first match "master bedroom", but because the "master bedroom" of user A103 does not install smart light, match "secondary bedroom", the concrete smart scene rule X102 is:

[0185] If: device (bracelet), condition (sleep in);

[0186] Just: device (smart light) (secondary bedroom), behavior (turn off the light).

[0187] Take a specific application scenario as an example, Figure 7 The application scenario of the smart home scene sharing according to an embodiment of the application is shown. User A111 creates a manual scene rule Z111. As Figure 7The name of the manual scene rule Z111 is "Optimize sleep environment" as shown in the interface 701 of the mobile phone. In the manual scene rule Z111, when the "Enter Optimize sleep environment" button on the mobile phone is pressed, the following devices are controlled:

[0188] Device (smart light) (living room), action (turn off the light);

[0189] Device (sleep aid light A) (bedroom), action (turn off);

[0190] Device (air purifier EP400) (bedroom), action (start sleep mode);

[0191] Device (fan A) (living room), action (turn off);

[0192] Device (air conditioner companion A) (bedroom), action (start sleep mode).

[0193] The user A111 clicks the share button 710 in the interface shown in 701, and the mobile phone enters the interface shown in 702.

[0194] The user A111 clicks the account sharing in the interface shown in 701 and inputs the user account of the user A112. The manual scene rule Z111 is uploaded to the scene sharing cloud server as a shared smart scene rule Z111. The scene sharing cloud server abstracts the shared smart scene rule Z111 to generate an abstract smart scene rule S111. At the same time, the scene sharing cloud server pushes a message to the mobile phone of the user A112. After the user A112 clicks the message link on the mobile phone, the mobile phone of the user A112 displays the interface shown in 702. The interface shown in 702 displays the abstract smart scene rule S111, wherein the scene name of the abstract smart scene rule S111 is "Optimize sleep environment", and the abstract smart scene rule S111 is that when the "Enter Optimize sleep environment" button on the mobile phone is pressed, the following devices are controlled:

[0195] Device (smart light) (living room), action (turn off the light);

[0196] Device (sleep aid light) (bedroom), action (turn off);

[0197] Device (air purifier) (bedroom), action (start sleep mode);

[0198] Device (fan) (living room), action (turn off);

[0199] Device (air conditioner companion) (bedroom), action (start sleep mode).

[0200] When user A112 wants to use the abstract intelligent scene rule S111, he clicks the application button 720 in the interface shown in 703, the scene sharing cloud server acquires the device information of the smart home device owned by user A112, materializes the abstract intelligent scene rule S111, generates the materialized intelligent scene rule X111, and the scene sharing cloud server sends the materialized intelligent scene rule X111 to the mobile phone of user A112.

[0201] The browsing interface of the mobile phone of user A112 is shown in 704, the scene name of the materialized intelligent scene rule X111 is optimized sleep environment, and the materialized intelligent scene rule X111 is that when the enter optimized sleep environment button on the mobile phone is pressed, the following devices are controlled:

[0202] Device (Oppo lamp) (living room), action (turn off the light);

[0203] Device (sleep aid lamp B) (bedroom), action (turn off);

[0204] Device (air purifier 720) (bedroom), action (start sleep mode);

[0205] Device (fan B) (living room), action (turn off);

[0206] Device (air conditioner companion B) (bedroom), action (start sleep mode).

[0207] When user A112 confirms to use the materialized intelligent scene rule X111, he clicks the save button 730 in the interface shown in 704. The materialized intelligent scene rule X111 is saved to the mobile phone of user A112, as shown in 705.

[0208] Further, in order to facilitate data recording, in an embodiment of the present application, the user's house type and room name are recorded in an encoding manner. Specifically, all house types and room names are enumerated and coded.

[0209] For example, the following mapping relationship is established:

[0210]

[0211]

[0212] Table 3

[0213] Further, in some application scenarios, when a user creates a smart scene rule, the user does not only set a control condition for a controlled smart home device, but also considers all controllable smart home devices in a room, and the user considers which part of the devices needs to be controlled and which part of the devices does not need to be controlled. However, when the user creates the smart scene rule, the smart scene rule usually only describes the part of the devices that need to be controlled, and does not describe the devices that do not need to be controlled. This results in that, when the user uploads and shares the smart scene rule, a part of devices in a certain type of devices in the smart home scene that are controlled is abstracted as all devices in the type of devices being controlled. Finally, the control effect achieved by the instantiated smart scene rule generated after the abstract smart scene rule is instantiated is completely different from the control effect achieved by the original shared smart scene rule.

[0214] For example, assume that there are four lamps, lamp 1, lamp 2, lamp 3, and lamp 4, in the bedroom of user A121. If user A121 wants at least half of the lamps in the bedroom to be turned off when the user goes to sleep, the user can create a smart scene rule Z121 as follows:

[0215] If: device (honor band 4), condition (go to sleep);

[0216] Then: device (lamp 1) (bedroom), action (turn off);

[0217] Device (lamp 2) (bedroom), action (turn off).

[0218] According to the smart scene rule Z121, when the honor band 4 of user A121 detects that the user goes to sleep, the lamp 1 and the lamp 2 in the bedroom are automatically turned off, so that at least half of the lamps in the bedroom are turned off, thereby achieving the user's intended purpose.

[0219] However, if the smart scene rule Z121 is abstracted to an abstract smart scene rule S121, because the operation behavior of the smart scene rule Z121 only describes the turn-off behavior, the abstract smart scene rule S121 generated after abstraction is as follows:

[0220] If: device (honor band 4), condition (go to sleep);

[0221] Then: device (smart lamp) (bedroom), action (turn off).

[0222] Assume that there are four lamps, lamp 1, lamp 2, lamp 3, and lamp 4, in the bedroom of user A121. If user A121 wants at least half of the lamps in the bedroom to be turned off when the user goes to sleep, the user can create a smart scene rule Z121 as follows:

[0223] If: device (honor band 4), condition (go to sleep);

[0224] Device (Oplamp 1) (Bedroom), Action (Turn off the light);

[0225] Device (Oplamp 2) (Bedroom), Action (Turn off the light);

[0226] Device (Oplamp 3) (Bedroom), Action (Turn off the light);

[0227] Device (Oplamp 4) (Bedroom), Action (Turn off the light).

[0228] According to the concrete smart scene rule X121, when the Honor Band 4 of the user A122 detects that the user falls asleep, the Oplamp 1, the Oplamp 2, the Oplamp 3 and the Oplamp 4 in the bedroom are automatically turned off, so that all the lights in the bedroom are turned off. The control effect achieved by the concrete smart scene rule X121 is completely different from the control effect achieved by the smart scene rule Z121.

[0229] To solve the above problem, in an embodiment of the present application, when a user uploads a shared smart scene rule, the scene sharing cloud server further obtains a general condition description of the smart home devices in the smart home scene of the user. For example, it is obtained that which smart home devices are included in the smart home scene of the user. In this way, the scene sharing cloud server can combine the general condition description of the smart home devices to perform the abstraction in the process of abstracting the shared smart scene rule into an abstract smart scene rule, so as to avoid the obvious difference between the shared smart scene rule and the concrete smart scene rule.

[0230] Specifically, in an implementation of the step 110:

[0231] Obtain a general condition description of the smart home devices in the smart home scene corresponding to the shared smart scene rule;

[0232] Generate a supplementary description of the smart home devices according to the general condition description of the smart home devices in the smart home scene and the smart home devices in the shared smart scene rule;

[0233] Obtain a device type description and / or a device function description of the smart home devices in the shared smart scene rule and a corresponding device action description;

[0234] Save the device type description and / or the device function description, the corresponding device action description and the supplementary description of the smart home devices to generate an abstract smart scene rule.

[0235] In one implementation of step 130, the smart home devices currently owned by the user of the scene application are matched according to the device type description and / or the device function description in the abstract smart scene rule and the smart home device supplementary description, so as to generate a concrete smart scene rule containing the smart home devices currently owned by the user of the scene application (so as to match the device action description in the abstract smart scene rule to the smart home devices currently owned by the user of the scene application).

[0236] Since the abstract smart scene rule contains the smart home device supplementary description referring to the overall condition description of the smart home device, after the abstract smart scene rule is concretized, the application effect of the concrete smart scene rule can be effectively ensured to be consistent with the application effect of the shared smart scene rule, thereby greatly improving the user experience.

[0237] Further, in order to protect the user privacy, when obtaining the overall condition description of the smart home device in the smart home scene of the user, only the type and the number of the smart home device in the smart home scene of the user are obtained, and the device model is not obtained.

[0238] For example, it is assumed that there are four lamps, i.e., lamp 1, lamp 2, lamp 3 and lamp 4, in the bedroom of user A131. If user A131 wants at least half of the lamps in the bedroom to be turned off when the user falls asleep. Then, the user can create a smart scene rule Z131 as follows:

[0239] If: device (honor band 4), condition (fall asleep);

[0240] Then: device (lamp 1) (bedroom), action (turn off the light);

[0241] Device (lamp 2) (bedroom), action (turn off the light).

[0242] According to the smart scene rule Z131, when the honor band 4 of user A131 detects that the user falls asleep, the lamp 1 and the lamp 2 in the bedroom will be automatically turned off, so that at least half of the lamps in the bedroom are turned off, thereby achieving the user's intended purpose.

[0243] User A131 uploads the smart scene rule Z131 as a shared smart scene rule to the scene sharing cloud server. The scene sharing cloud server obtains the overall condition description of the smart home device in the smart home scene of user A131: there are four smart lamps in the bedroom.

[0244] In combination with “there are four smart lamps in the bedroom”, the abstract smart scene rule S131 generated by the scene sharing cloud server after abstracting the smart scene rule Z131 is as follows:

[0245] If: device (honor band 4), condition (fall asleep);

[0246] If: device (total number of smart lights (smart home device supplement description) 1 / 2) (bedroom), action (turn off the light).

[0247] Suppose user A132 has four lamps, lamp 1, lamp 2, lamp 3, and lamp 4, in his bedroom. User A132 applies abstract smart scene rule S131 to his bedroom, and then generates concrete smart scene rule X131:

[0248] If: device (Honor Band 4), condition (fall asleep);

[0249] Just: device (lamp 1) (bedroom), action (turn off the light);

[0250] Device (lamp 2) (bedroom), action (turn off the light).

[0251] According to concrete smart scene rule X131, when user A122's Honor Band 4 detects that the user has fallen asleep, lamp 1 and lamp 2 in the bedroom will automatically turn off, so that at least half of the lights in the bedroom are turned off. The control effect achieved by concrete smart scene rule X131 is consistent with the control effect achieved by smart scene rule Z131. Further, in actual application scenarios, in order to achieve control of smart home devices, the configuration related to the action of the smart home device needs to be stored in the device configuration file. For example, in an application scenario, lamp A supports two actions: on and off. In the control parameters (deviceCmd) set by the manufacturer for lamp A, the parameters corresponding to the on and off actions are "switch", and the "switch" parameter value 1 corresponds to "on" and the "switch" parameter value 0 corresponds to "off".

[0252] Therefore, if lamp A needs to be controlled, the following code needs to be saved in the device configuration file:

[0253] "devName": "lamp A",

[0254] "devType": "001",

[0255] "prodID": "0001",

[0256] "actionInfo": [

[0257] {

[0258] "name": "on",

[0259] "deviceCmd": {

[0260] "value": 1,

[0261] "sid": "switch"

[0262] }

[0263] }

[0264] {

[0265] "name": "off",

[0266] "deviceCmd": {

[0267] "value": 0,

[0268] "sid": "switch"

[0269] }

[0270] }

[0272] In the above code, it includes the name of the lamp devName, the type of the lamp devType, the unique code of the lamp prodId, and the actions supported by the lamp actionInfo.

[0273] However, in actual application scenarios, due to different manufacturers, for different smart home devices with similar or identical functions and control methods, their control parameter settings are usually different. For example, Lamp B supports two actions: on and off. In the control parameters (deviceCmd) set by the manufacturer for Lamp B, the parameter corresponding to the switch action is "on", the parameter value 0 of "on" corresponds to "on", and the parameter value 1 of "on" corresponds to "off".

[0274] This results in the need to match different device control parameters when abstracting, concretizing, and controlling smart home devices according to the concrete smart scene rules.

[0275] To uniformly map the same functions, types, and actions of devices from different manufacturers, in an embodiment of the present application, the device functions, device types, and / or device actions are uniformly encoded, and the unified encoding is stored in the configuration file of the device. That is, in the application scenario of smart home scene sharing, the configuration file of the smart home device stores the device function encoding, and / or the device type encoding, and / or the device action encoding, and the device function encoding, device type encoding, and device action encoding are unified encodings for different manufacturers.

[0276] In this way, it is possible to directly implement the unified mapping of device functions, device types, and device actions on devices from different manufacturers by reading the configuration file of the smart home device, greatly reducing the difficulty of creating, abstracting, and concretizing smart scene rules.

[0277] ​For example, in one embodiment, the code for turning on a light is X0001 and the code for turning off a light is X0002.

[0278] For light A, the following configuration code is saved:

[0279] "devName": "light A",

[0280] "devType": "001",

[0281] "prodID": "0001",

[0282] "actionInfo": [

[0283] {

[0284] "name": "on",

[0285] "deviceCmd": {

[0286] "value": 1,

[0287] "sid": "switch"

[0288] },

[0289] "actionCode": ["X0001"]

[0290] },

[0291] {

[0292] "name": "off",

[0293] "deviceCmd": {

[0294] "value": 0,

[0295] "sid": "switch"

[0296] },

[0297] "actionCode": ["X0002"]

[0298] } ]

[0300] For light B, the following configuration code is saved:

[0301] "devName": "light B",

[0302] "devType": "001",

[0303] "prodID": "0002",

[0304] "actionInfo":

[0305] {

[0306] "name": "on", ​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​

[0327]

[0328]

[0329] In the embodiment of the abstract intelligent scene rule, first, according to the roomId, combined with the actual house type of the user, the final selected room is obtained to perform a screening on the device. Then it is checked whether the configuration file of the device contains the corresponding actionCode. If yes, the corresponding action parameter configuration is automatically obtained.

[0330] It can be understood that part or all of the steps or operations in the above embodiments are only examples, and the embodiments of the present application can also perform other operations or various modifications of the operations. In addition, each step can be executed in a different order from the above embodiments, and it is possible that not all the operations in the above embodiments are executed.

[0331] Further, with the development of technology, many method process improvements today can be considered as direct improvements of hardware circuit structures. Designers almost all get the corresponding hardware circuit structure by programming the improved method process into the hardware circuit. Therefore, it cannot be said that the improvement of a method process cannot be implemented by a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is an integrated circuit whose logic function is determined by the programmer accessing the device. A digital device is "integrated" on a PLD by the designer programming it himself, without having to ask a chip manufacturer to design and manufacture a special integrated circuit chip. Moreover, instead of manually manufacturing integrated circuit chips, such programming is now mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing programs, and the original code before compilation also needs to be written in a specific programming language, which is called hardware description language (HDL). Those skilled in the art should also be clear that only the method process needs to be logically programmed and programmed into an integrated circuit using the above-mentioned several hardware description languages, and the hardware circuit that implements the logical method process can be easily obtained.

[0332] Specifically, the method flow proposed in the embodiments of the present application can be integrated into a physical entity in whole or in part, or can be physically separated. These modules can be implemented in the form of software invoked by a processing element in whole, or in the form of hardware, or some modules are implemented in the form of software invoked by a processing element and some modules are implemented in the form of hardware. For example, the detection module can be a separately established processing element, or can be implemented in a certain chip of the electronic device. The implementation of other modules is similar. In addition, all or part of these modules can be integrated together, or can be independently implemented. In the implementation process, each step of the above method or each of the above modules can be completed by the integrated logic circuit of hardware in the processor element or the instruction in the form of software.

[0333] Specifically, according to the method flow proposed in the embodiments of the present application, the embodiments of the present application further propose an intelligent home scene sharing device, which can be constructed in a scene sharing cloud server.

[0334] Specifically, the device comprises:

[0335] a rule acquisition module configured to acquire a shared intelligent scene rule;

[0336] an abstraction module configured to abstract the shared intelligent scene rule to generate an abstract intelligent scene rule, including: acquiring a device type description and / or a device function description of an intelligent home device in the shared intelligent scene rule and a corresponding device action description; and saving the device type description and / or the device function description and the corresponding device action description to generate the abstract intelligent scene rule;

[0337] a concretization module configured to concretize the abstract intelligent scene rule to generate a concrete intelligent scene rule, including: matching the device type description and / or the device function description in the abstract intelligent scene rule with an intelligent home device currently owned by a scene application user to generate the concrete intelligent scene rule containing the intelligent home device currently owned by the scene application user;

[0338] a sharing module configured to share the concrete intelligent scene rule to the scene application user.

[0339] An embodiment of the present application further proposes an electronic device, which comprises a memory for storing computer program instructions and a processor for executing the program instructions, wherein when the computer program instructions are executed by the processor, the electronic device is triggered to execute the method steps as described in the embodiments of the present application.

[0340] Specifically, in an embodiment of the present application, the one or more computer programs are stored in the memory, and the one or more computer programs include instructions that, when executed by the device, cause the device to perform the method steps described in the embodiments of the present application.

[0341] Specifically, in an embodiment of the present application, the processor of the electronic device can be a system on a chip (SOC), and the processor can include a central processing unit (CPU) and can further include other types of processors. Specifically, in an embodiment of the present application, the processor of the electronic device can be a PWM control chip.

[0342] Specifically, in an embodiment of the present application, the processor can include, for example, a CPU, a DSP, a microcontroller, or a digital signal processor, and can further include a GPU, a neural-network process unit (NPU), and an image signal processor (ISP), and can further include necessary hardware accelerators or logic processing hardware circuits, such as an ASIC, or one or more integrated circuits for controlling the execution of the programs of the technical solutions of the present application. In addition, the processor can have the function of operating one or more software programs, and the software programs can be stored in a storage medium.

[0343] Specifically, in an embodiment of the present application, the memory of the electronic device can be a read-only memory (ROM), other types of static storage devices that can store static information and instructions, a random access memory (RAM), or other types of dynamic storage devices that can store information and instructions, and can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can also be any computer-readable medium capable of carrying or storing desired program codes in the form of instructions or data structures and capable of being accessed by a computer.

[0344] Specifically, in an embodiment of the present application, the processor and the memory can be combined into one processing device, and more commonly, they are independent components from each other. The processor is configured to execute program codes stored in the memory to implement the method according to the embodiments of the present application. In a specific implementation, the memory can be integrated in the processor, or independent of the processor.

[0345] Further, the method or device according to the embodiments of the present application can be implemented by a computer chip or an entity, or by a product with certain functions.

[0346] Those skilled in the art should understand that the embodiments of the present application can be provided as a method or a computer program product. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including a magnetic disk, an optical disk, or a CD-ROM) containing computer-usable program codes.

[0347] In several embodiments provided by the present application, any function if realized in the form of a software function unit and sold or used as an independent product, can be stored in a computer-readable storage medium. Based on such understanding, the technical solutions of the present application essentially, or the parts of the technical solutions that make contributions to the prior art, or the parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods according to the embodiments of the present application.

[0348] Specifically, the embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program runs on a computer, the computer is caused to execute the method according to the embodiments of the present application.

[0349] The embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program runs on a computer, the computer is caused to execute the method according to the embodiments of the present application.

[0350] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, devices and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of the flows and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing devices to produce a machine, so that the instructions executed by the computer or other programmable data processing devices generate a means for implementing the functions described in the flowcharts and / or block diagrams.Figure 1 one or more processes and / or blocks Figure 1 means for performing the function specified by the block or blocks.

[0351] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the Figure 1 one or more processes and / or blocks Figure 1 means for performing the function specified by the block or blocks.

[0352] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the Figure 1 one or more processes and / or blocks Figure 1 Figure 1 means for performing the function specified by the block or blocks.

[0353] It should also be noted that, in the embodiments of the present application, "at least one" means one or more, and "multiple" means two or more. The "and / or" describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B, which can represent the cases of A alone, A and B together, and B alone. Wherein A and B can be singular or plural. The character " / " generally represents an "or" relationship between the front and rear associated objects. "At least one of the following" and the like means any combination of these items, including any combination of single or multiple items. For example, at least one of a, b and c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0354] In the embodiments of the present application, the terms "comprise", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, product or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or includes elements inherent to such process, method, product or device. Without more limitations, the element defined by the sentence "comprising a" does not exclude the presence of another identical element in the process, method, product or device including the element.

[0355] The application can be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote computer storage media including memory storage devices.

[0356] The various embodiments in this application are described in progressive manner, and the same or similar parts between various embodiments can be referred to each other. Each embodiment focuses on the difference from other embodiments. Especially, the device embodiments are described simply because they are basically similar to the method embodiments, and the relevant parts can be referred to the part of the method embodiments.

[0357] Those skilled in the art can understand that each unit and algorithm steps described in the embodiments of the application can be implemented by electronic hardware, computer software or combination of the two. Whether the function is implemented in hardware or software depends on the specific application and design constraints of the technical solution. A person skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the application.

[0358] Those skilled in the art can clearly understand that, for the convenience and brevity, the specific working process of the device, apparatus and unit described above can refer to the corresponding process in the foregoing method embodiments, which will not be described here.

[0359] The above is only a specific implementation of the application. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the application, which should be covered within the protection scope of the application. The protection scope of the application should be subject to the protection scope of the claims.

Claims

1. A method for sharing smart home scenes, characterized in that, include: Establish room mapping relationships between different apartment types; Obtain the shared smart scene rules and the corresponding apartment types, wherein the shared smart scene rules include device location restrictions; Abstracting the shared smart scene rules to generate abstract smart scene rules includes: obtaining device type descriptions and / or device function descriptions, corresponding device action descriptions, and corresponding device location constraints of smart home devices in the shared smart scene rules; and saving the device type descriptions and / or device function descriptions, corresponding device action descriptions, and corresponding device location constraints to generate the abstract smart scene rules. The abstract intelligent scene rules are concretized to generate concrete intelligent scene rules, including: obtaining the apartment type of the scene application user; based on the room mapping relationship, determining the room correspondence between the apartment type of the scene application user and the apartment type of the shared intelligent scene rule according to the apartment type corresponding to the shared intelligent scene rule and the apartment type of the scene application user; based on the room correspondence, matching the smart home devices currently owned by the scene application user according to the device type description and / or device function description in the abstract intelligent scene rule and the corresponding device location limitation, to generate the concrete intelligent scene rules containing the smart home devices currently owned by the scene application user; The concrete intelligent scene rules are shared with the scene application users.

2. The method according to claim 1, characterized in that, The method further includes creating the shared intelligent scene rules, including: Retrieve device condition parameters from the device configuration file library; Set the equipment condition values ​​for the aforementioned equipment condition parameters; Retrieve device action parameters from the device configuration file library; Set the device action values ​​for the device action parameters; The shared intelligent scene rules are generated based on the device condition values ​​and the device action values.

3. The method according to claim 1, characterized in that, The configuration file of the smart home device stores device function codes, and / or device type codes, and / or device action codes, wherein the device function codes, device type codes, and device action codes are unified codes for different manufacturers.

4. The method according to claim 1, characterized in that, The apartment type is recorded using a coding method.

5. The method according to any one of claims 1-3, characterized in that, The method also includes obtaining an overall description of the status of smart home devices in the smart home scene corresponding to the shared smart scene rule; The abstraction of the shared intelligent scene rules to generate abstract intelligent scene rules further includes: Based on the overall situation description and the smart home devices in the shared smart scene rules, generate a supplementary description of the smart home devices; Obtain the device type description and / or device function description of the smart home devices in the shared smart scene rules, as well as the corresponding device action description; Save the device type description and / or device function description, the corresponding device action description, and the supplementary description of the smart home device to generate the abstract smart scene rules.

6. A smart home scene sharing device, characterized in that, include: The rule acquisition module is used to: establish room mapping relationships between different apartment types; Obtain the shared smart scene rules and the corresponding apartment types, wherein the shared smart scene rules include device location restrictions; An abstract module is used to abstract the shared smart scene rules to generate abstract smart scene rules. This includes obtaining device type descriptions and / or device function descriptions, corresponding device action descriptions, and corresponding device location constraints of smart home devices in the shared smart scene rules; and saving the device type descriptions and / or device function descriptions, corresponding device action descriptions, and corresponding device location constraints to generate the abstract smart scene rules. The concrete module, used to concretize the abstract smart scene rules to generate concrete smart scene rules, includes: obtaining the apartment type of the scene application user; based on the room mapping relationship, determining the room correspondence between the apartment type of the scene application user and the apartment type of the shared smart scene rule according to the apartment type corresponding to the shared smart scene rule and the apartment type of the scene application user; based on the room correspondence, matching the smart home devices currently owned by the scene application user according to the device type description and / or device function description in the abstract smart scene rule and the corresponding device location limitation, to generate the concrete smart scene rules containing the smart home devices currently owned by the scene application user; The sharing module is used to share the concrete intelligent scene rules with the scene application users.

7. An electronic device, characterized in that, The electronic device includes a memory for storing computer program instructions and a processor for executing the program instructions, wherein when the computer program instructions are executed by the processor, the electronic device is triggered to perform the method steps as described in any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1-5.

Images