Equipment data exchange method and system

Abstract

The invention discloses a device data exchange method and system. The method comprises the following steps that a controller obtains output data of a driving device, a driven device is determined based on a controller installation action, the controller calls the output data of the driving device, a driven device processing program is determined according to driven device information, and the driven device processing program is output to the driven device. The beneficial effects of the invention are that the dependence on an external network is reduced, the linkage between devices is improved, the use complexity of a user is reduced, and the user experience is improved.

Description

Technical Field

[0001] The present application relates to the technical field of household electrical appliances, and in particular to a method and system for exchanging device data. Background Art

[0002] In the networking of multiple home appliances, it is usually necessary to rely on external networks to realize information exchange between home appliances. However, the stability of the external network directly affects the effect of information exchange between home appliances, and in the environment of multiple home appliance networking, each device may generate a large amount of data, including status information, control instructions, etc. If they all rely on external networks for transmission, the network burden is large. At the same time, in traditional networking methods, control instructions or status information are often sent to all devices in the form of broadcast or multicast. Although this method is simple, it will cause non-target devices to receive unnecessary information, increasing the network burden and the processing pressure of the device.

[0003] Point-to-point precise push means that control instructions or status information are sent directly to the target device, and other devices will not receive the control instructions or status information. However, in the relevant technology, the realization of point-to-point precise push in the environment of multiple home appliances networking requires complex routing and distribution mechanisms, as well as accurate identification of device identity and status, which places high demands on the devices.

[0004] The Chinese patent "An integrated control method, terminal and application control system for household appliances", publication number: CN105259828A, publication date: January 20, 2016, specifically discloses: establishing a connection with one or more household appliances and integrating the functions of household appliances; receiving control instructions from users, and performing functional control operations on household appliances according to the control instructions. In this solution, the functions of all household appliances are integrated into a control terminal, the operation mode of the household appliances is set based on user needs, and control instructions are sent to the control terminal. However, in this process, there is only interaction between the user and the information of each device, and there is no interaction between the information of each device, so it depends on the subjective choice of the user. It is impossible to automatically generate recommended information of other device programs based on the user's choice of one device program, and the linkage between devices is poor.

[0005] The Chinese patent "A Smart Home Control System", publication number: CN112987583A, publication date: June 18, 2021, specifically discloses: user terminal, main control device, multiple home appliances; the user terminal is connected to the main control device via Internet communication; the main control device is connected to each home appliance via Bluetooth communication; each home appliance is connected point-to-point via Bluetooth communication to form a Bluetooth home network; wherein: the user terminal sends a command request to the main control device, and after receiving the command request, the main control device forwards the corresponding command request to the corresponding home appliance via Bluetooth broadcast, and the home appliance receiving the command request executes the corresponding instruction. Although the Bluetooth home network is formed through Bluetooth point-to-point connection in this scheme to reduce the dependence when the network fails, the main control device still uses Bluetooth broadcast when forwarding the command request to the corresponding home appliance, and the linkage performance between home appliances is poor, and it still causes non-target devices to receive unnecessary information. Summary of the invention

[0006] In order to solve the problem in the prior art that device data exchange depends on external network data, resulting in large transmission volume and poor linkage between devices, the present application provides a device data exchange method and system, wherein a slave device is determined through a controller installation action, and data exchange between an active device and a slave device is realized through the controller, and no additional communication is required between the active device and the slave device, which reduces both dependence on an external network and energy consumption for maintaining communication between the active device and the slave device. At the same time, the user can determine the slave device according to actual needs, which is suitable for the situation where there are multiple slave devices and the active device cannot determine the subsequent device to be used by itself. At this time, after selecting the active device to run the program, the user can install the controller that has obtained the output data of the active device on the slave device, so as to realize the output of the slave device processing program without selecting the subsequent running program on the slave device, thereby improving the linkage between devices, reducing the user's usage complexity, and improving the user experience.

[0007] To achieve the above technical objectives, a technical solution provided by the present application is a device data exchange method, comprising the following steps: a controller obtains output data of an active device, determines a slave device based on an installation action of the controller, the controller calls the output data of the active device, determines a slave device handler according to the slave device information, and outputs the slave device handler to the slave device.

[0008] Furthermore, the controller obtains the active device output data, and determines the slave device based on the controller installation action, including: obtaining the active device output data based on the installation action of the controller installed on the active device; determining the slave device based on the installation action of the controller installed on the slave device.

[0009] Furthermore, the controller obtains the output data of the active device, and determining the slave device based on the controller installation action also includes: obtaining the installation device information based on the controller installation action, judging whether the installation device is a slave device according to the installation device information and preset master-slave device information, and if so, determining the current installation device as a slave device, and if not, determining the current installation device as an active device, and obtaining the output data of the active device.

[0010] Furthermore, the controller obtains the output data of the active device, and determines the slave device based on the installation action of the controller, which also includes: when the controller triggers the installation action, it determines whether there is a historical installation action within a preset time sequence. If so, it is considered that the currently installed device is a slave device; if not, it is considered that the currently installed device is an active device, and the output data of the active device is obtained.

[0011] Furthermore, it also includes: matching the display interface of the controller according to the installation status of the controller.

[0012] Further, matching the display interface of the controller according to the installation status of the controller includes: the display interface of the controller matches the display interface of a currently installed device; and / or, the display interface of the controller matches the display interface of a historically installed device.

[0013] Furthermore, the outputting of the slave device processing program to the slave device also includes: outputting recommendation information through a user interaction interface of the slave device based on the slave device processing program; and / or updating a custom program of the slave device according to the slave device processing program.

[0014] Furthermore, the controller obtains the output data of the active device, and determines the slave device based on the installation action of the controller, which also includes: when the controller triggers the installation action and there is no historical installation action within the preset time sequence, judging whether the obtained output data is the first obtained data within the preset time sequence; if so, the current device is regarded as the active device and the obtained output data is regarded as the active output data; if not, the current device is regarded as the slave device and the obtained output data is regarded as the slave device information.

[0015] Furthermore, the controller obtains the output data of the active device, and determining the slave device based on the controller installation action also includes: if there are historical installation actions within a preset time sequence, outputting the slave device order and / or the number of slave devices based on the number of historical installation actions.

[0016] Furthermore, the controller calls the active device to output data, and determines the slave device processing program according to the slave device information, which also includes: the controller calls the active device to output data, and determines the slave device processing program of each slave device and the corresponding execution order according to the slave device order and slave device type.

[0017] Furthermore, the outputting of the slave device processing program to the slave device also includes: setting the slave device processing program output timing according to the execution order of each slave device processing program; and outputting the slave device processing program to the corresponding slave device at the slave device processing program output timing.

[0018] Furthermore, the method also includes: receiving a reset signal and deleting the installation device information obtained within the reset sequence in the controller.

[0019] Another technical solution provided by the present application is a device data exchange system for implementing the method as described above, comprising: a controller, which can be detachably installed on an active device and a slave device, for obtaining output data of the active device and obtaining information of the slave device according to the installation action, and executing data exchange between the slave device and the active device.

[0020] Furthermore, it also includes: a household appliance having a controller installation space, and when the controller is installed in the controller installation space, the household appliance transmits device information to the controller.

[0021] A technical solution provided by the present application is that the controller is a detachably mounted knob or user terminal.

[0022] Beneficial effects of this application: 1. The data exchange between the active device and the slave device is realized through the controller. There is no need to establish additional communication between the active device and the slave device, which not only reduces the dependence on the external network, but also improves the linkage between devices, reduces the user's usage complexity, and improves the user experience.

[0023] 2. The information transmission through physical actions further reduces the abnormal matching problem between the active device and the slave device, and improves the reliability and safety of the operation between the active device and the slave device.

[0024] 3. Not limited to the preset master-slave device relationship, users can freely select master and slave devices according to actual needs, improve the freedom of interaction, and enhance the user experience.

[0025] 4. Regardless of whether the user returns the controller to the active device, the active device and the slave device can still be automatically identified at the next action, and data exchange between the active device and the slave device can be realized.

[0026] 5. When there are multiple slave devices, users can install the controllers one by one to determine the operating order of the slave devices and output the operating programs of the slave devices, thereby improving user convenience and user experience. When multiple home appliances are operating in conjunction, it not only realizes point-to-point accurate information interaction between each home appliance, but also ensures the efficiency of the linkage between home appliances.

[0027] 6. Determine the number of slave devices of the same device type and the order of slave devices of different device types based on the number of historical installation actions, so as to output the slave device processing program according to the slave devices that need to be executed at the same time and the slave devices that are executed sequentially.

[0028] 7. Reduce the difficulty for users to check the information of linked devices and further improve the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 This is a flow chart of the device data exchange method of this application.

[0030] Figure 2 This is a flow chart of the equipment data exchange method in the washing and drying case of this application. DETAILED DESCRIPTION

[0031] In order to make the purpose, technical solutions and advantages of the present application more clear, the present application is further described in detail below in conjunction with the drawings and examples. It should be understood that the specific implementation method described here is only an optimal embodiment of the present application, which is only used to explain the present application and does not limit the scope of protection of the present application. All other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0032] like Figure 1 As shown, as the first embodiment of the present application, the device data exchange method includes the following steps: The controller obtains the output data of the active device, determines the slave device based on the controller installation action, calls the output data of the active device, determines the slave device processing program according to the slave device information, and outputs the slave device processing program to the slave device.

[0033] In this embodiment, the active device is the device used first, and the slave device is the device used later. The output data of the active device includes at least the type of the active device and the running program of the active device. The slave device is determined by the controller installation action, and the data exchange between the active device and the slave device is realized through the controller. There is no need to establish additional communication between the active device and the slave device, which not only reduces the dependence on the external network, but also reduces the energy consumption of maintaining communication between the active device and the slave device. At the same time, the user can determine the slave device according to actual needs. It is suitable for the situation where there are multiple slave devices and the active device cannot determine the device to be used later by itself. At this time, after selecting the running program of the active device, the user can install the controller that has obtained the output data of the active device on the slave device to realize the output of the slave device processing program without selecting the running program later on the slave device, thereby improving the linkage between devices, reducing the complexity of user use, and improving user experience.

[0034] The controller obtains the output data of the active device and determines the slave device based on the controller installation action, including: Obtaining active device output data based on an installation action of the controller installed on the active device; The driven device is determined based on an installation action of the controller on the driven device.

[0035] By installing the controller on the active device and the slave device respectively, the controller obtains the output data of the active device and determines the slave device respectively. At this time, the user only needs to install the controller on the active device and the slave device respectively to realize the information exchange between the active device and the slave device. Since there is no need to build an information transmission channel between the active device and the slave device, there is no need for communication matching between the active device and the slave device. Instead, information is exchanged through physical actions, which further reduces the abnormal matching problem between the active device and the slave device and improves the reliability and safety of the successive operation between the active device and the slave device.

[0036] In this embodiment, the controller obtains the output data of the active device, and determines the slave device based on the controller installation action, further comprising: Based on the controller installation action, the installation device information is obtained, and whether the installation device is a slave device is determined according to the installation device information and the preset master-slave device information. If so, the current installation device is determined as a slave device. If not, the current installation device is determined as an active device, and the output data of the active device is obtained.

[0037] The controller has pre-stored preset master-slave device information, which can be preset active device information and preset slave device information preset by the manufacturer at the time of leaving the factory. The preset active device information at least includes the active device identification code, and the preset slave device information at least includes the slave device identification code. The preset master-slave device information can also be obtained according to the preset master-slave device relationship, such as Figure 2 As shown, in washing machines and clothes dryers, washing machines are usually used as active devices, and clothes dryers are used as slave devices. The identification codes of the two can be pre-stored as active device identification codes and slave device identification codes respectively. In order to adapt to multiple types of the same device, the identification code can only identify the device type. When the controller is installed on a certain device, the device is the current installed device, and the installed device information is obtained. At this time, the installed device information at least includes the installed device identification code. The installed device identification code is matched with the active device identification code and the slave device identification code respectively. If the installed device identification code successfully matches any active device identification code, the current installed device is considered to be an active device. If the installed device identification code successfully matches any slave device identification code, the current installed device is considered to be a slave device.

[0038] In other embodiments, the preset master-slave device information may also be any information that can distinguish between an active device and a slave device. For example, it may be set such that when the active device recognizes that the controller is installed, the active device actively outputs the active device output data to the controller. At this time, the preset master-slave device information is "1" for the active device and "0" for the slave device. Whether the active output data is received is used as the distinction between the master and slave devices. At this time, the slave device is set to not actively output data when the controller is recognized to be installed, but if the controller does not receive the active output data within a preset time, the installation device is set as a slave device, and the controller outputs a data acquisition signal to the slave device, and the slave device outputs the slave device information to the controller. It is understandable that the preset master-slave device information here can also be set or changed by the user to be more suitable for the user's actual use.

[0039] In other cases, it may also be that the installation device information is obtained based on the controller installation action, and it is determined whether the installation device is a slave device based on the installation device information and the preset active device information. If so, the current installation device is determined as a slave device, if not, the current installation device is determined as an active device, and the active device output data is obtained; or, the installation device information is obtained based on the controller installation action, and it is determined whether the installation device is a slave device based on the installation device information and the preset slave device information. If so, the current installation device is determined as a slave device, if not, the current installation device is determined as an active device, and the active device output data is obtained.

[0040] At this time, the pre-stored device information can be any one of an active device and a slave device. When the pre-stored active device information is preset, if the installed device information does not match the preset active device information, the currently installed device is considered to be a slave device. When the pre-stored slave device information is preset, if the installed device information matches the preset slave device information, the currently installed device is considered to be a slave device.

[0041] As a second embodiment of the present application, the controller obtains the output data of the active device, and determines the slave device based on the controller installation action, further comprising: When the controller triggers the installation action, it is determined whether there is a historical installation action within the preset time sequence. If so, the currently installed device is considered to be a slave device. If not, the currently installed device is considered to be an active device, and the output data of the active device is obtained.

[0042] The difference from the first embodiment is that the present embodiment determines the master and slave devices through the front and back installation actions of the controller, that is, the device installed in front is used as the active device, and the device installed in the back is used as the slave device. If there is no historical installation action within the preset time sequence, the currently installed device is considered to be the first installed device and is used as the active device. If there is a historical installation action within the preset time sequence, the currently installed device is not the first installed device and is used as the slave device. Thus, it is not limited to the preset master-slave device relationship, and the user can freely select the master and slave devices according to actual needs, improve the freedom of interaction, and enhance the user experience. At this time, the preset time sequence can be the longest running time of the currently installed device, so that the remaining devices are not triggered within the longest running time of the currently installed device, and it is considered that the operation of the previous and subsequent devices is unrelated. Or considering the situation that the user controls the remaining devices after the previous device is completed, the preset time sequence can be the sum of the reserved time sequence and the running time of the previous device. The reserved time sequence can be set according to the actual use situation. For example, when the previous device is a washing machine, the reserved time sequence can be one day, and when the previous device is a rice washing machine, the reserved time sequence can be 6 hours.

[0043] In other cases, the controller obtains the output data of the active device, and determining the slave device based on the controller installation action further includes: When the controller triggers the installation action, it determines whether the currently installed device is the first triggered installation device within the preset timing. If so, the currently installed device is considered to be an active device, and the secondary output data of the active device is obtained and pre-stored. If not, the currently installed device is considered to be a slave device.

[0044] In this case, whether the first trigger installation device is used as the active device, when the controller installs the first trigger installation device back after the remaining slave devices are installed, the device will not be used as a slave device, but the current data of the device will be obtained and pre-stored as the active device output data.

[0045] At this time, considering that the user may have the next action, the device where the current controller is located is still used as the active device, or the controller is installed on other devices and other devices are used as active devices. Thus, the controller obtains the output data of the active device, and determining the slave device based on the controller installation action also includes: When the controller triggers an installation action and there is no historical installation action within the preset time sequence, it is determined whether the acquired output data is the first acquired data within the preset time sequence. If so, the current device is used as an active device and the acquired output data is used as active output data. If not, the current device is used as a slave device and the acquired output data is used as slave device information.

[0046] If the controller is returned to the active device after the previous action is completed, and the controller does not install the action on the active device in the next action, the active device will still output its own operating data to the controller when it starts. When the controller triggers the first installation action, it determines whether the output data currently obtained is the first data obtained within the preset time sequence, that is, the first acquisition data. If so, it is considered that the controller did not obtain the data of other devices before installation, and the current device is the first triggering device, as the active device, and the output data obtained is the output data of the active device. If not, the first acquisition data is used as the output data of the active device, the device that outputs the first acquisition data is used as the active device, the current installation device is used as the slave device, and the output data currently obtained is used as the slave device information. Therefore, regardless of whether the user returns the controller to the active device, the active device and the slave device can still be automatically identified in the next action, and the data interaction between the active device and the slave device can be realized.

[0047] Of course, this embodiment can also be combined with the first embodiment, such as the controller pre-stores preset active device information. At this time, the controller obtains the output data of the active device, and the determination of the slave device based on the controller installation action also includes: The active device and the active device output data are determined according to the output data obtained by the controller and the preset active device information; when the active device is determined, the slave device is determined according to the controller installation action.

[0048] In this case, first determine whether the current device is an active device based on the matching of the output data obtained by the controller with the preset active device information, that is, the output data includes at least the identification code of the device. At this time, determine whether the identification code of the device matches the identification code of any active device in the preset active device information. If the match is successful, the device is an active device. If the match is unsuccessful, the device is ignored. When the user starts the slave device to run alone and removes the controller on the slave device and installs it on the active device, determine whether the initially obtained output data comes from the slave device through the preset active device information, and then choose whether to ignore the device, so as to avoid misjudgment of the master and slave devices and improve the accuracy of data exchange.

[0049] In this embodiment, the controller obtains the output data of the active device, and determines the slave device based on the controller installation action, further comprising: If there are historical installation actions within the preset timing, the order of the slave devices is output based on the number of historical installation actions.

[0050] Through the user's installation actions, the slave devices are sequentially ordered. For example, when there are three devices A, B, and C, the controller is sequentially installed on the three devices A, B, and C, with A as the active device. At this time, when the controller is installed on the B device, the controller outputs the processing program of the B device to the B device according to the device information of A and B. When the controller is installed on the C device, based on the existence of two installation actions of A and B, the C device is determined to be the third running device, and the processing program of the C device is output to the C device according to the device information of A, B, and C, thereby avoiding being limited to the sequential operation relationship between the two devices. When there are multiple slave devices, the user can install the controller in sequence at one time to determine the running order of the slave devices and output the running program of the slave devices, thereby improving the convenience of use and the user experience. At the same time, in the case of multi-home appliance linkage operation, it not only realizes the point-to-point precise information interaction between each home appliance, but also ensures the efficiency of linkage between home appliances.

[0051] At this time, the controller calls the active device to output data, and determines the slave device processing program according to the slave device information, and further includes: The controller calls the active device to output data, and determines the slave device processing program of each slave device and the corresponding execution order according to the slave device sequence and the slave device type.

[0052] The slave device order is obtained according to the number of existing historical installation actions of the controller, and the slave device type is obtained according to the slave device information.

[0053] Outputting the slave device processing program to the slave device also includes: Setting the output timing of the slave device processing program according to the execution order of each slave device processing program; The slave device processing program is output to the corresponding slave device at the slave device processing program output timing.

[0054] In this process, there are two situations: if the controller communicates with the slave device only when it is installed on the slave device, the slave device processor output timing and the slave device processor will be output to the slave device when installed; if the controller establishes communication with the slave device when it is installed on the slave device, and can subsequently output data through the established communication channel, the slave device processor can be output to the corresponding slave device when the slave device processor outputs the timing, thereby realizing the integrated control of the slave device by the controller. When the operating time of any device changes, the controller can directly change the output timing of the slave device processor to achieve unified regulation, which is more flexible.

[0055] In other embodiments, the controller obtains the output data of the active device, and determines the slave device based on the controller installation action, further comprising: If there are historical installation actions within the preset time sequence, the number of slave devices is determined based on the number of historical installation actions.

[0056] At this time, the controller calls the active device to output data, and determines the slave device processing program according to the slave device information, and further includes: The controller calls the master device to output data, and determines the slave device processing program of each slave device according to the number of slave devices and the type of slave devices.

[0057] In this case, considering that one active device may correspond to multiple slave devices, the number of slave devices can be determined based on the user's historical installation actions, and a communication connection is established with each slave device based on the controller's installation actions. When the installation action is completed, the slave device processing program of each slave device is determined based on the number of slave devices corresponding to each device type. For example, if the clothes of a washing machine are dried by two dryers and only by one dryer, the processing program of the dryer will be different. The processing program of the slave device can be adaptively adjusted according to the number of slave devices selected by the user, so as to adapt to the different needs of users and improve the user experience.

[0058] In other cases, the number of slave devices and the order of slave devices can also be determined based on the number of historical installation actions. The number of slave devices is the number of slave devices of the same slave device type, and the order of slave devices is the order of slave devices of different slave device types, so that the slave device processing program is output according to the slave devices that need to be executed at the same time and the slave devices that are executed sequentially.

[0059] In this embodiment, the slave device information at least includes the slave device type. In some cases, the slave device information may also include the master-slave device relationship, that is, whether the master device and the slave device determined are incorrect according to the master-slave device relationship in the slave device information, and if so, a prompt is given to prevent the user from accidentally triggering a device that does not belong to the previous and next running relationship. When the slave device processing program is output to the slave device, the slave device runs according to the slave device processing program, and the slave device processing program at least includes the slave device running time and the slave device running action.

[0060] As a third embodiment of the present application, outputting the slave device processing program to the slave device further includes: Outputting recommendation information through a user interface of the slave device based on the slave device processing program; and / or, Update the slave device's custom program according to the slave device's handler.

[0061] In this embodiment, outputting the slave device processing program to the slave device does not directly control the operation of the slave device, but outputs recommendation information through the user interaction interface and / or updates the slave device processing program to the slave device custom program.

[0062] When the recommended information is output through the user interaction interface of the slave device based on the slave device processing program, the corresponding control button can be recommended in the form of flashing or highlighting on the user interaction interface; when the custom program of the slave device is updated according to the slave device processing program, the slave device processing program is pre-stored in the custom program of the slave device, so that the user can start the slave device with one click, and when the slave device processing program has multiple steps or multiple button linkage selections, the user's operation complexity can be reduced. Of course, the two can also be combined, and the recommended information, such as the program and time recommended by the slave device, can be output on the user interaction interface, and the custom program of the slave device can be updated according to the slave device processing program, so as to facilitate the user to know the slave device startup program and improve the convenience of user operation. Of course, in other cases, the controller can only output the active device output data to the slave device, and the slave device can obtain the slave device processing program according to the active device output data.

[0063] In this embodiment, the device data exchange method further includes: Match the controller's display interface according to the controller's installation status.

[0064] The display interface that matches the controller according to the controller installation status includes: The display interface of the controller matches the display interface of the currently installed device; and / or, The display interface of the controller matches the display interface of the historical installation device.

[0065] When the display interface of the controller matches the display interface of the currently installed device, the user can directly adjust the currently installed device and know the operation information of the currently installed device according to the display interface of the controller. The historically installed device is the device that the controller has installed in the preset sequence except the currently installed device, that is, the display interface of the controller does not match the display interface of the currently installed device at this time, but displays the display interface of the remaining installed devices, so that the user can get the operation information of all devices in the whole process within the scope of one device at the same time. For example, when the washing machine and the dryer are interacting with data, if there is a dryer placed above the washing machine, it is difficult for the user to view the display interface of the dryer. At this time, if the display interface of the washing machine itself displays its own operation information, the operation information of the dryer is reflected by the display interface of the controller installed on the washing machine, reducing the difficulty of users to check the information of the linked devices back and forth, and further improving the user experience. Of course, the display interface of the currently installed device and the historically installed device can also be displayed at the same time through the controller, and the user can freely switch the display interface of different devices according to their own needs.

[0066] In this embodiment, the communication between the active device and the controller, and the slave device and the controller can be carried out only when the controller is installed on the device, or a communication channel can be established during installation to realize data exchange requirements under different needs, while ensuring the security of data exchange and reducing the complexity of user operations, thereby improving the convenience of user linkage control of devices.

[0067] The device data exchange method also includes: Receive a reset signal and delete the installed device information obtained during the reset sequence in the controller.

[0068] The user can delete the installed device information in the controller through the reset button on the controller or the installation device, or other set reset actions. The reset signal includes at least a reset sequence. If the user finds that he has installed the controller incorrectly when installing it on a certain device and needs to delete the device, the corresponding reset sequence will be output. The controller will delete all the installed device information within the reset sequence, and can also synchronously delete the slave device handler output to the currently installed device, thereby improving the fault tolerance rate and facilitating users to make modifications according to actual needs. Of course, in other cases, the reset signal includes a reset sequence and a reset object, and the historical retained data of the reset object in the reset sequence is deleted, thereby achieving targeted deletion of historical pre-stored information and improving user freedom.

[0069] In the present application, Embodiment 1, Embodiment 2 and Embodiment 3 may be arbitrarily combined to adapt to different usage requirements.

[0070] Among them, the active device and the slave device are both household appliances, and the controller is a knob that can be detachably installed on the household appliance. It can be understood that although the present application adopts the description of active devices and slave devices, it does not limit the slave device to only act according to the operation of the active device. When there is no need for data exchange linkage, the slave device is a device that can be operated independently. In some special cases, some devices can also be used as active devices or slave devices in different situations. For example, in a washing machine and a dryer, if the dryer is to be set according to the operating program of the washing machine, then the dryer is used as a slave device, and in a dryer and a care cabinet, the care cabinet sets the clothing care program according to the operating program of the dryer, and then the dryer is used as an active device.

[0071] As a fourth embodiment of the present application, a device data exchange system includes: The controller is detachably mounted on the active device and the slave device, and is used to obtain the output data of the active device and obtain the information of the slave device according to the installation action, and execute the data exchange between the slave device and the active device.

[0072] In this embodiment, the active device and the slave device are home appliances, and the controller is a knob or user terminal that can be detachably mounted on the home appliance. The user terminal can be a user terminal including an operation screen, a user terminal including physical operation buttons, or a user terminal including both an operation screen and physical operation buttons. When the controller is a user terminal including an operation screen, the user obtains the home appliance information received by the user terminal through the operation screen, and can adjust the operation program of the home appliance through the touch buttons on the operation screen. When the controller is a user terminal including physical operation buttons, the information on the controller is displayed through the display screen of the installation device, and the user can adjust the operation program of the home appliance through the physical operation buttons on the controller. When the controller is a user terminal including both an operation screen and physical operation buttons, the user obtains the home appliance information received by the user terminal through the operation screen, and can adjust the operation program of the home appliance through the physical operation buttons and / or the touch buttons on the operation screen.

[0073] In some specific cases, the active device is a washing machine, and the passive device is a drying machine and / or a care cabinet.

[0074] At this time, the device data exchange system also includes: A home appliance is provided with a controller installation space. When the controller is installed in the controller installation space, the home appliance transmits device information to the controller.

[0075] When the home appliance is an active device, the device information transmitted by the home appliance to the controller is active device output data; when the home appliance is a slave device, the device information transmitted by the home appliance to the controller is slave device information.

[0076] The specific implementation methods described above are preferred implementation methods of the device data exchange method and system of the present application, and are not intended to limit the specific implementation scope of the present application. The scope of the present application includes but is not limited to the specific implementation methods. All equivalent changes made in accordance with the shape and structure of the present application are within the protection scope of the present application.

Claims

1. A device data exchange method, characterized in that: The steps include: The controller obtains the output data of the active device, determines the slave device based on the controller installation action, calls the output data of the active device, determines the slave device processing program according to the slave device information, and outputs the slave device processing program to the slave device.

2. The device data exchange method according to claim 1, characterized in that: The controller obtains the output data of the active device, and determines the slave device based on the controller installation action, including: Obtaining active device output data based on an installation action of the controller installed on the active device; The driven device is determined based on an installation action of the controller on the driven device.

3. The device data exchange method according to claim 1, characterized in that: The controller obtains the output data of the active device, and determines the slave device based on the controller installation action, and further includes: Based on the controller installation action, the installation device information is obtained, and whether the installation device is a slave device is determined according to the installation device information and the preset master-slave device information. If so, the current installation device is determined as a slave device. If not, the current installation device is determined as an active device, and the output data of the active device is obtained.

4. The device data exchange method according to claim 1, characterized in that: The controller obtains the output data of the active device, and determines the slave device based on the controller installation action, and further includes: When the controller triggers the installation action, it is determined whether there is a historical installation action within the preset time sequence. If so, the currently installed device is considered to be a slave device. If not, the currently installed device is considered to be an active device, and the output data of the active device is obtained.

5. The device data exchange method according to claim 1, characterized in that: Also includes: Match the controller's display interface according to the controller's installation status.

6. The device data exchange method according to claim 5, characterized in that: The display interface of the controller matching the controller according to the controller installation state includes: The display interface of the controller matches the display interface of the currently installed device; and / or, The display interface of the controller matches the display interface of the historical installation device.

7. The device data exchange method according to claim 1, characterized in that: The outputting of the slave device processing program to the slave device further comprises: Outputting recommendation information through a user interface of the slave device based on the slave device processing program; and / or, Update the slave device's custom program according to the slave device's handler.

8. The device data exchange method according to claim 4, characterized in that: The controller obtains the output data of the active device, and determines the slave device based on the controller installation action, and further includes: When the controller triggers an installation action and there is no historical installation action within the preset time sequence, it is determined whether the acquired output data is the first acquired data within the preset time sequence. If so, the current device is used as an active device and the acquired output data is used as active output data. If not, the current device is used as a slave device and the acquired output data is used as slave device information.

9. The device data exchange method according to claim 4, characterized in that: The controller obtains the output data of the active device, and determines the slave device based on the controller installation action, and further includes: If there are historical installation actions within the preset time sequence, the slave device order and / or the number of slave devices are output based on the number of historical installation actions.

10. The device data exchange method according to claim 9, characterized in that: The controller calls the active device to output data, and determines the slave device processing program according to the slave device information, and further includes: The controller calls the active device to output data, and determines the slave device processing program of each slave device and the corresponding execution order according to the slave device sequence and the slave device type.

11. The device data exchange method according to claim 10, characterized in that: The outputting of the slave device processing program to the slave device further comprises: Setting the output timing of the slave device processing program according to the execution order of each slave device processing program; The slave device processing program is output to the corresponding slave device at the slave device processing program output timing.

12. The device data exchange method according to claim 3, characterized in that: Also includes: Receive a reset signal and delete the installed device information obtained during the reset sequence in the controller.

13. A device data exchange system, used to implement the method according to any one of claims 1 to 12, characterized in that: include: The controller is detachably mounted on the active device and the slave device, and is used to obtain the output data of the active device and obtain the information of the slave device according to the installation action, and execute the data exchange between the slave device and the active device.

14. The device data exchange system according to claim 13, characterized in that: Also includes: A home appliance is provided with a controller installation space. When the controller is installed in the controller installation space, the home appliance transmits device information to the controller.

15. The device data exchange system according to claim 14, characterized in that: The controller is a detachably mounted knob or a user terminal.

Images