A method and apparatus for determining a channel

Abstract

The application relates to a channel determination method and device, and relates to the technical field of intelligent household appliances. The method comprises the following steps: a broadcast type channel application request message is sent in a first channel; the channel application request message carries a channel occupation table, and the channel occupation table comprises a corresponding relationship between a channel identifier and a device identifier; after a waiting duration of the first channel reaches a preset channel waiting duration, switching to a second channel, receiving a channel application response message sent by a first slave in the second channel, the channel application response message carrying a device identifier corresponding to the first slave, and updating the channel occupation table according to a channel identifier of the second channel and the device identifier of the first slave; the channel identifier of the second channel is equal to the channel identifier of the first channel plus 1; after a waiting duration of the second channel reaches the channel waiting duration, switching to a third channel, and the process is continued until the last channel is ended. The application can avoid communication failure caused by same frequency interference.

Description

Technical Field ,

[0010] ,

[0009]

[0001] This application relates to the technical field of smart home appliances, and particularly to a method and device for determining a channel. Background Art

[0002] Currently, in a kitchen appliance linkage system, kitchen appliances can be networked through wireless communication to perform information interaction and achieve a linkage function. The wireless communication methods can be RF (Radio Frequency), Bluetooth, Wi-Fi, etc. Among them, when a kitchen appliance performs wireless communication, it needs to determine a certain communication frequency point as the network channel. For example, when using the RF method, a certain communication frequency point can be selected within the domestic license-free ISM (Industrial Scientific Medical) open frequency band of 433.05 - 434.79 MHZ as the network channel.

[0003] However, if two or more devices send information using the same communication frequency point simultaneously, a co-channel interference problem will occur, resulting in the information sent not being received normally and causing communication failure. Summary of the Invention

[0004] Based on this, in view of the above technical problems, it is necessary to provide a method and device for determining a channel.

[0005] In a first aspect, a method for determining a channel is provided. The method is applied to a host, and the method includes:

[0006] Sending a broadcast-type channel application request message in a first channel; the channel application request message carries a channel occupancy table, and the channel occupancy table includes the correspondence between channel identifiers and device identifiers;

[0007] After the waiting duration of the first channel reaches a preset channel waiting duration, switching to a second channel, receiving, in the second channel, a channel application response message sent by a first slave device and carrying the device identifier corresponding to the first slave device, and updating the channel occupancy table according to the channel identifier of the second channel and the device identifier of the first slave device; the channel identifier of the second channel is equal to the channel identifier of the first channel plus 1; <00000!7>

[0008] After the waiting duration of the second channel reaches the channel waiting duration, switching to a third channel until the last channel ends,

[0009] As an optionally implemented manner, the updating the channel occupancy table according to the channel identifier of the second channel and the device identifier of the first slave device includes:

[0010] Based on the channel identifier of the second channel, query the target device identifier corresponding to the channel identifier of the second channel in the channel occupancy table;

[0011] If the target device identifier is not found, then the correspondence between the channel identifier of the second channel and the device identifier of the first slave device is added to the channel occupancy table;

[0012] If the target device identifier is found, it is determined whether the target device identifier is consistent with the device identifier of the first slave device;

[0013] If the target device identifier is inconsistent with the device identifier of the first slave device, the correspondence between the channel identifier of the second channel and the target device identifier is kept unchanged in the channel occupancy table.

[0014] As an optional implementation, the method further includes:

[0015] If a channel request response message sent by the second slave device to which the target device identifier belongs is not received in the second channel, then the number of disconnections corresponding to the target device identifier is incremented by 1;

[0016] If the number of lost connections exceeds a preset threshold, the correspondence between the channel identifier of the second channel and the target device identifier is deleted from the channel occupancy table.

[0017] As an optional implementation, the method further includes:

[0018] If the target device identifier is the same as the device identifier of the first slave device, then the number of disconnections corresponding to the target device identifier is reset to zero.

[0019] Secondly, a method for determining a channel is provided, the method being applied to a slave device, the method comprising:

[0020] In the first channel, a broadcast-type channel request message sent by a host is received; the channel request message carries a channel occupancy table, which includes the correspondence between channel identifiers and device identifiers;

[0021] In the channel occupancy table, query the channel identifier of the target channel corresponding to the local device identifier;

[0022] If the channel identifier of the target channel corresponding to the local device identifier is not found, then an idle channel is randomly selected from the idle channels as the target channel; the idle channel is a channel in the channel occupancy table that does not have a correspondence between the channel identifier and the device identifier.

[0023] The delayed transmission duration is determined based on the channel identifier of the target channel and the preset channel waiting time.

[0024] After waiting for the specified delay duration, a unicast channel request response message is sent to the host in the target channel; the channel request response message carries the local device identifier, which is used by the host to update the channel occupancy table.

[0025] As an optional implementation, the method further includes:

[0026] If the channel identifier of the target channel corresponding to the local device identifier is found, then the step of determining the delayed transmission duration based on the channel identifier of the target channel and the preset channel waiting duration is executed.

[0027] As an optional implementation, the formula for determining the delayed transmission duration based on the channel identifier of the target channel and the preset channel waiting time is as follows:

[0028] T = k * t

[0029] Where T represents the delay transmission duration, k represents the channel identifier of the target channel, and t represents the preset channel waiting time.

[0030] Thirdly, a channel determination device is provided, the device being applied to a host, the device comprising:

[0031] The broadcast module is used to send a broadcast-type channel request message in the first channel; the channel request message carries a channel occupancy table, which includes the correspondence between channel identifiers and device identifiers;

[0032] The update module is used to switch to the second channel after the waiting time of the first channel reaches a preset channel waiting time. In the second channel, it receives a channel request response message sent by the first slave device carrying the device identifier corresponding to the first slave device, and updates the channel occupancy table according to the channel identifier of the second channel and the device identifier of the first slave device. The channel identifier of the second channel is equal to the channel identifier of the first channel plus 1.

[0033] The switching module is used to switch to the third channel after the waiting time of the second channel reaches the channel waiting time, until the last channel ends.

[0034] As an optional implementation, the update module is specifically used for:

[0035] Based on the channel identifier of the second channel, query the target device identifier corresponding to the channel identifier of the second channel in the channel occupancy table;

[0036] If the target device identifier is not found, then the correspondence between the channel identifier of the second channel and the device identifier of the first slave device is added to the channel occupancy table;

[0037] If the target device identifier is found, it is determined whether the target device identifier is consistent with the device identifier of the first slave device;

[0038] If the target device identifier is inconsistent with the device identifier of the first slave device, the correspondence between the channel identifier of the second channel and the target device identifier is kept unchanged in the channel occupancy table.

[0039] As an optional implementation, the apparatus further includes:

[0040] The judgment module is used to increment the number of disconnections corresponding to the target device identifier by 1 if a channel request response message sent by the second slave to which the target device identifier belongs is not received in the second channel;

[0041] The deletion module is used to delete the correspondence between the channel identifier of the second channel and the target device identifier in the channel occupancy table if the number of lost connections is greater than a preset threshold for the number of lost connections.

[0042] As an optional implementation, the apparatus further includes:

[0043] The reset module is used to reset the number of disconnections corresponding to the target device identifier to zero if the target device identifier is consistent with the device identifier of the first slave device.

[0044] Fourthly, a channel determination device is provided, the device being applied to a slave device, the device comprising:

[0045] The receiving module is used to receive a broadcast-type channel request message sent by a host in the first channel; the channel request message carries a channel occupancy table, which includes the correspondence between channel identifiers and device identifiers;

[0046] The query module is used to query the channel identifier of the target channel corresponding to the local device identifier in the channel occupancy table;

[0047] The first determining module is used to randomly select an idle channel from the idle channels as the target channel if no channel identifier corresponding to the local device identifier is found; the idle channel is a channel in the channel occupancy table that does not have a correspondence between the channel identifier and the device identifier.

[0048] The second determining module is used to determine the delayed transmission duration based on the channel identifier of the target channel and the preset channel waiting duration;

[0049] The sending module is configured to send a unicast channel request response message to the host in the target channel after waiting for the specified delay duration; the channel request response message carries the local device identifier, which is used by the host to update the channel occupancy table.

[0050] As an optional implementation, the apparatus further includes:

[0051] The third determining module is used to execute the second determining module if the channel identifier of the target channel corresponding to the local device identifier is found.

[0052] Fifthly, a kitchen appliance linkage system is provided, the kitchen appliance linkage system including a host and at least one slave, the host applying the channel determination method as described in the first aspect, and the slave applying the channel determination method as described in the second aspect.

[0053] In a sixth aspect, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program executable on the processor, and the processor executes the computer program to implement the steps of the method described in the first aspect.

[0054] In a seventh aspect, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program executable on the processor, and the processor executes the computer program to perform the steps of the method described in the second aspect.

[0055] Eighthly, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in the first aspect.

[0056] In a ninth aspect, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in the second aspect.

[0057] This application provides a channel determination method and apparatus. The technical solution provided by the embodiments of this application brings at least the following beneficial effects: First, the host sends a broadcast-type channel request message in a first channel. The channel request message carries a channel occupancy table, which includes a correspondence between channel identifiers and device identifiers. After receiving the broadcast-type channel request message from the host in the first channel, the slave device queries the channel occupancy table for the channel identifier of the target channel corresponding to its local device identifier. If no channel identifier corresponding to the local device identifier is found, an idle channel is randomly selected as the target channel, and a delay transmission duration is determined based on the channel identifier of the target channel. After waiting for the delay transmission duration, the slave device sends a unicast-type channel request response message to the host in the target channel. The channel request response message carries the local device identifier. After the host waits on the first channel for the preset channel waiting time, it switches to the second channel with the channel identifier incremented by 1. On the second channel, it receives the channel request response message from the first slave device, carrying the device identifier corresponding to the first slave device, and updates the channel occupancy table based on the channel identifier of the second channel and the device identifier of the first slave device. After the host waits on the second channel for the preset channel waiting time, it switches to the third channel with the channel identifier incremented by 1, receives the channel request response message, and updates the channel occupancy table, and so on, until the last channel is used. Through this method, after receiving the channel request request message from the host, each slave device can select the corresponding target channel according to the channel occupancy table and send a channel request response message to the host in a time-division multiplexing manner. In this way, the host switches channels in ascending order of channel identifier, allowing it to sequentially receive the channel request response messages from the slave devices and update the channel occupancy table based on the channel identifier and the device identifier of the slave device, thereby avoiding communication failures caused by co-channel interference.

[0058] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

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

[0060] Figure 1 This is a schematic diagram of the structure of a kitchen appliance linkage system provided in an embodiment of this application;

[0061] Figure 2 A schematic diagram of a multi-channel allocation timing provided in an embodiment of this application;

[0062] Figure 3 A flowchart illustrating a channel determination method provided in an embodiment of this application;

[0063] Figure 4 A flowchart illustrating another method for determining a channel provided in an embodiment of this application;

[0064] Figure 5 A flowchart illustrating an example of a channel determination method provided in an embodiment of this application;

[0065] Figure 6 A flowchart illustrating an example of another channel determination method provided in an embodiment of this application;

[0066] Figure 7 An interaction diagram illustrating an example of a host and slave unit in a kitchen appliance linkage system provided in this application embodiment;

[0067] Figure 8 A schematic diagram of a channel determination device provided in an embodiment of this application;

[0068] Figure 9 A schematic diagram of another channel determination device provided in an embodiment of this application;

[0069] Figure 10 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0070] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0071] The channel determination method provided in this application embodiment can be applied to a kitchen appliance linkage system, which includes one host and at least one slave device. The host and slave devices can be networked through wireless communication. Figure 1 This is a schematic diagram of the structure of a kitchen appliance linkage system provided in an embodiment of this application, as shown below. Figure 1 As shown, the kitchen appliance linkage system includes a main unit 110, slave units 121, 122, and 123. Preferably, both the main unit and the slave units are kitchen appliances. For example, the main unit can be a range hood, and the slave units can be kitchen appliances that generate oil fumes during use, such as cooktops, steam ovens, rice cookers, electric frying pans, and induction cookers. The main unit 110 and slave units 121, and slave units 122 and 123 in the kitchen appliance linkage system can communicate with each other via a wireless communication network. The wireless communication network can typically be divided into multiple channels according to frequency bands. Figure 2This is a schematic diagram of a multi-channel allocation timing provided in an embodiment of this application, as shown below. Figure 2 As shown, the wireless communication network of the kitchen appliance linkage system is divided into N+1 channels (i.e., channels 0 to N). In existing technology, after a slave device comes online, it randomly selects one of the above N+1 channels to communicate with the master device. When multiple slave devices randomly select the same channel, channel collisions will occur between the slave devices, thus affecting the communication between the slave and the master device.

[0072] The following will describe in detail a channel determination method provided by the embodiments of this application, with reference to specific implementation methods. First, the channel determination method applied to the host will be introduced. Figure 3 A flowchart illustrating a channel determination method provided in an embodiment of this application is shown below. Figure 3 As shown, the specific steps are as follows:

[0073] Step 301: Send a broadcast-type channel request message in the first channel. The channel request message carries a channel occupancy table, which includes the correspondence between channel identifiers and device identifiers.

[0074] In implementation, to prevent channel collisions with other slave devices caused by the slave device randomly selecting one of the N+1 channels after coming online, as in existing technologies, this application addresses the issue where the slave device waits for the host to initiate channel selection on the first of the N+1 channels after coming online. This first channel can be channel 0. When the host needs to initiate channel selection, it can send a broadcast-type channel request message on the first channel. This message carries a channel occupancy table, which includes the correspondence between channel identifiers and device identifiers. The device identifier is a locally stored device identifier on the slave device, used to uniquely identify a slave device within a kitchen appliance linkage system. After receiving the broadcast-type channel request message from the host, each slave device in the communication network can determine the delay duration for sending a channel request response message and the target channel to be occupied based on the channel occupancy table. The delay duration ensures that when the slave device sends its channel request response message on the target channel, the host also polls the target channel, thus ensuring that the host can receive the slave device's channel request response message on the target channel. The specific processing steps for the slave device to determine the delay duration for sending the channel request response message and the target channel to be occupied based on the channel occupancy table will be described in detail later and will not be repeated here.

[0075] Table 1 is an example of a channel occupancy table provided in an embodiment of this application. As shown in Table 1, since the first channel (i.e., the channel with channel identifier 0) is the channel occupied by the host sending broadcast type messages, it is not shown in the channel occupancy table. Among them, the slave device identifier corresponding to the channel with channel identifier 1 is 22; the slave device identifier corresponding to the channel with channel identifier 4 is 44; the slave device identifier corresponding to the channel with channel identifier 6 is 33; the channels with channel identifiers 2, 3, 5 and 7 do not have corresponding slave device identifiers, that is, they have not yet been occupied by slaves.

[0076] Channel identifier 1 2 3 4 5 6 7 Equipment identification 22 - - 44 - 33 -

[0077] Preferably, in order to enhance the anti-interference capability of the communication network, the host sends three consecutive broadcast-type channel request messages in the first channel to ensure that each slave can receive the message.

[0078] Step 302: After the waiting time on the first channel reaches the preset channel waiting time, switch to the second channel. In the second channel, receive the channel request response message sent by the first slave device, which carries the device identifier corresponding to the first slave device. Update the channel occupancy table according to the channel identifier of the second channel and the device identifier of the first slave device. The channel identifier of the second channel is equal to the channel identifier of the first channel plus 1.

[0079] In implementation, the host waits for a preset channel waiting time (denoted as t) on each of the aforementioned N+1 channels before switching to the next channel, i.e., as follows: Figure 2 As shown, the host is in channel 0 from time 0 to t, in channel 1 from time t to 2t, in channel 2 from time 2t to 3t, and so on. Therefore, after the host's waiting time in the first channel (channel identifier 0) reaches the preset channel waiting time, it switches to the second channel (channel identifier 1). In the second channel, it receives the channel request response message sent by the first slave device, which carries the device identifier corresponding to the first slave device, and updates the channel occupancy table according to the channel identifier of the second channel and the device identifier of the first slave device. The operation of updating the channel occupancy table can include adding a mapping between the channel identifier of the second channel and the device identifier of the first slave device, deleting a mapping between the channel identifier of the second channel and the device identifier of the first slave device, and modifying a mapping between the channel identifier of the second channel and the device identifier of the first slave device.

[0080] Furthermore, the process by which the host updates the channel occupancy table based on the channel identifier of the second channel and the device identifier of the first slave is as follows:

[0081] Step 1: Based on the channel identifier of the second channel, look up the target device identifier corresponding to the channel identifier of the second channel in the channel occupancy table.

[0082] In implementation, the host queries the channel occupancy table for the target device identifier corresponding to the channel identifier of the second channel. If a correspondence exists between the channel identifier and device identifier of the second channel in the channel occupancy table, the host can find the target device identifier corresponding to the channel identifier of the second channel in the channel occupancy table; otherwise, the target device identifier cannot be found. For example, in the channel occupancy table shown in Table 1, the host can find that the target device identifier corresponding to channel identifier 1 of the second channel is 22.

[0083] Step 2: If the target device identifier is not found, add the correspondence between the channel identifier of the second channel and the device identifier of the first slave device to the channel occupancy table.

[0084] In practice, if the target device identifier corresponding to the channel identifier of the second channel is not found, it means that the second channel has not yet been occupied by any slave device in the channel occupancy table, and has been selected by the first slave device as the target channel for sending the channel request response message. At this time, the host adds the correspondence between the channel identifier of the second channel and the device identifier of the first slave device to the channel occupancy table, indicating that the second channel has been occupied by the first slave device.

[0085] Step 3: If the target device identifier is found, determine whether the target device identifier is consistent with the device identifier of the first slave device.

[0086] In implementation, if the number of slave devices not occupying a channel in the channel occupancy table exceeds two, different slave devices may select the same idle channel as the target channel. In this case, the host will update the channel occupancy table based on the device identifier carried in the channel request response message sent by the first slave device received. See step two for the specific process. Since the channel occupancy table has now added the correspondence between the channel identifier and device identifier of the second channel, channel request response messages sent by other slave devices that have selected the second channel as the target channel need to be discarded. Therefore, if the host finds the target device identifier, it needs to determine whether the target device identifier matches the device identifier of the first slave device. If the target device identifier matches the device identifier of the first slave device, it means that the first slave device is occupying the second channel. The host can process the channel request response message sent by the first slave device, and the correspondence between the channel identifier and the target device identifier of the second channel remains unchanged in the channel occupancy table.

[0087] Step 4: If the target device identifier is inconsistent with the device identifier of the first slave device, then the correspondence between the channel identifier of the second channel and the target device identifier remains unchanged in the channel occupancy table.

[0088] In practice, if the target device identifier does not match the device identifier of the first slave device, it means that the first slave device is not the device occupying the second channel. In this case, the host will keep the correspondence between the channel identifier of the second channel and the target device identifier unchanged in the channel occupancy table and discard the channel request response message sent by the first slave device.

[0089] As an optional implementation, to avoid resource waste caused by slave devices that have been unused for a long time or have been removed occupying channels in the channel occupancy table, the host's processing also includes:

[0090] Step 1: If no channel request response message is received from the second slave device to which the target device identifier belongs in the second channel, then increment the number of disconnections corresponding to the target device identifier by 1.

[0091] In practice, the host can update the number of disconnections for each device identifier in the channel occupancy table. If the host does not receive a channel request response message from the second slave device to which the target device identifier belongs in the second channel, it means that the second slave device corresponding to the target device identifier has lost connection in this communication cycle. In this case, the host will increment the number of disconnections corresponding to the target device identifier by 1.

[0092] Furthermore, the number of disconnections corresponding to the target device identifier is the number of consecutive disconnections of the slave device corresponding to the target device identifier. The master's processing also includes: if the target device identifier is consistent with the device identifier of the first slave device, then the number of disconnections corresponding to the target device identifier is cleared to zero.

[0093] Step 2: If the number of lost connections exceeds the preset threshold, delete the correspondence between the channel identifier of the second channel and the target device identifier in the channel occupancy table.

[0094] In implementation, if the host determines that the number of disconnections corresponding to the target device identifier exceeds a preset disconnection threshold, it indicates that the slave device corresponding to the target device identifier has experienced a large number of consecutive disconnections, suggesting it may have been unused for a long time or has been moved. In this case, the host deletes the correspondence between the channel identifier of the second channel and the target device identifier from the channel occupancy table, allowing the second channel to be occupied by other slave devices. The disconnection threshold can be set by engineers based on experience and pre-stored in the computer. Preferably, the disconnection threshold is 5.

[0095] Step 303: After the waiting time of the second channel reaches the channel waiting time limit, switch to the third channel until the last channel ends.

[0096] In implementation, after the waiting time on the second channel (channel identifier 1) reaches its designated waiting time, the host switches to the third channel (channel identifier 2) to receive channel request response messages from the slave devices and update the channel occupancy table. This process continues until the last channel is used. In this way, each slave device (device identifiers 22, 33, and 44) ​​occupies a channel according to the channel occupancy table. Based on the channel identifier of the occupied channel, each slave device sends a channel request response message to the host in a time-sharing manner. The host switches channels in ascending order of channel identifier, sequentially receiving channel request response messages from each slave device and updating the channel occupancy table. This eliminates co-channel interference in the communication network, avoids channel congestion, and improves the anti-interference performance of the kitchen appliance linkage system.

[0097] The following describes the method for determining the channel applied to the slave device. Figure 4 A flowchart of another channel determination method provided in an embodiment of this application is shown below. Figure 4 As shown, the specific steps are as follows:

[0098] Step 401: Receive a broadcast-type channel request message from the host in the first channel. The channel request message carries a channel occupancy table, which includes the correspondence between channel identifiers and device identifiers.

[0099] In implementation, after the slave device connects to the communication network, it defaults to switching to the first channel to receive broadcast messages sent by the host. When the host sends a broadcast channel request message on the first channel, the slave device can receive the broadcast channel request message sent by the host on the first channel. The channel request message carries a channel occupancy table, which includes the correspondence between channel identifiers and device identifiers. A description of the channel occupancy table is provided in step 201 and will not be repeated here.

[0100] Step 402: In the channel occupancy table, query the channel identifier of the target channel corresponding to the local device identifier.

[0101] In implementation, after the slave device receives a broadcast-type channel request message from the master device on the first channel, it needs to send a channel request response message to the master device. To determine the time to send the channel request response message and the target channel to be occupied, the slave device first queries the channel occupancy table for the channel identifier of the target channel corresponding to the local device identifier.

[0102] Step 403: If no channel identifier for the target channel corresponding to the local device identifier is found, then a random idle channel is selected from the idle channels as the target channel. Here, an idle channel is a channel for which there is no correspondence between the channel identifier and the device identifier in the channel occupancy table.

[0103] In implementation, if the slave device cannot find the channel identifier of the target channel corresponding to its local device identifier, it means that the slave device does not have an occupied target channel in the channel occupancy table. Therefore, the slave device randomly selects an idle channel from the available channels as the target channel for sending the channel request response message. An idle channel is a channel in the channel occupancy table where there is no corresponding relationship between the channel identifier and the device identifier. For example, in the channel occupancy table shown in Table 1, channels with channel identifiers 2, 3, 5, and 7 do not have corresponding slave device identifiers; therefore, channels 2, 3, 5, and 7 are idle channels. For a slave device with local device identifier 55, if the channel identifier of the target channel corresponding to device identifier 55 is not found in the channel occupancy table shown in Table 1, then the idle channel 2 (i.e., channels 2, 3, 5, and 7) is randomly selected as the target channel for sending the channel request response message.

[0104] As an optional implementation, the slave device's processing further includes: if the channel identifier of the target channel corresponding to the local device identifier is found, then step 404 is executed.

[0105] In implementation, if the slave device finds the channel identifier of the target channel corresponding to the local device identifier in the channel occupancy table, it means that the slave device has an already occupied target channel in the channel occupancy table, and step 404 can be executed directly. For example, if the local device identifier of the slave device is 22, and the channel identifier of the target channel corresponding to device identifier 22 is found to be 1 in the channel occupancy table shown in Table 1, the slave device can directly execute step 404.

[0106] Step 404: Determine the delayed transmission duration based on the channel identifier of the target channel and the preset channel waiting time.

[0107] In implementation, the master can only successfully receive the response message sent by the slave when both the master and slave are on the same channel. Therefore, to ensure synchronization between the master and slave, the slave can determine the corresponding delayed transmission duration for the target channel based on the channel identifier and the preset channel waiting time. Preferably, the formula for determining the delayed transmission duration based on the channel identifier and the preset channel waiting time is as follows:

[0108] T = k * t

[0109] Where T represents the delay transmission duration, k represents the channel identifier of the target channel, and t represents the preset channel waiting duration. For example, if the target channel identifier of the slave device with local device identifier 55 is 2, then the delay transmission duration for this slave device is 2t; if the target channel identifier of the slave device with local device identifier 22 is 1, then the delay transmission duration for this slave device is t.

[0110] Step 405: After waiting for the specified transmission delay, a unicast channel request response message is sent to the host in the target channel. This message carries a local device identifier, which is used by the host to update the channel occupancy table.

[0111] In implementation, after waiting for the specified delay, the slave device sends a unicast channel request response message to the host on the target channel. This message carries a local device identifier, which is used by the host to update the channel occupancy table. In this embodiment, for slave A, which already occupies a channel in the channel occupancy table, other slave devices will not select the channel occupied by slave A as the target channel. For slaves B and C, which do not yet occupy a channel in the table, the probability of selecting the same idle channel as the target channel is low when there are many idle channels. Even if slaves B and C select the same idle channel, one slave device may successfully occupy it. The slave device that fails to occupy the channel can reselect the target channel based on the updated channel occupancy table after receiving a broadcast channel request message from the host. Ultimately, this embodiment achieves the ideal state where each slave device in the kitchen appliance linkage network occupies a channel in the channel occupancy table, thus avoiding co-channel interference caused by two or more slave devices simultaneously sending channel request response messages on the same channel.

[0112] It should be noted that existing kitchen appliance linkage systems typically select a fixed communication frequency as the network channel. However, in practical applications, external devices such as building wireless water meter systems and intercoms may use the same communication frequency as the communication network selected by the kitchen appliance linkage system. In this case, the wireless communication signals of the external devices will cause co-channel interference with the wireless communication of the kitchen appliance linkage system. The multi-channel coexistence design in this application embodiment allows the slave device to randomly select an idle channel as the target channel, thereby greatly reducing the possibility of interference from external devices during communication of the kitchen appliance linkage system.

[0113] Figure 5 A flowchart illustrating an example of a channel determination method provided in this application embodiment is shown below. Figure 5 As shown, the slave device's processing procedure is as follows:

[0114] Step 501: Power on.

[0115] Step 502: Switch to the first channel and receive a broadcast-type channel request message from the host. The channel request message carries a channel occupancy table, which includes the correspondence between channel identifiers and device identifiers.

[0116] Step 503: In the channel occupancy table, query whether the local machine has already occupied the target channel.

[0117] If yes, proceed to step 505; otherwise, proceed to step 504.

[0118] Step 504: Randomly select an idle channel from the idle channels as the target channel.

[0119] Step 505: Determine the waiting delay transmission duration based on the channel identifier of the target channel. After the waiting delay transmission duration, send a unicast channel request response message to the host in the target channel, and then execute step 502.

[0120] Figure 6 A flowchart illustrating another method for determining a channel provided in embodiments of this application is shown below. Figure 6 As shown, the host's processing procedure is as follows:

[0121] Step 601: Power on.

[0122] Step 602: Switch to the first channel (i.e., channel 0) and send three consecutive broadcast-type channel request messages. Each channel request message carries a channel occupancy table.

[0123] Step 603: Determine whether the waiting time has reached the preset channel waiting time.

[0124] If so, proceed to step 604; otherwise, continue with step 603.

[0125] Step 604: Switch to the channel with channel identifier incremented by 1.

[0126] Step 605: Receive the channel request response message sent by the first slave device, which carries the device identifier corresponding to the first slave device, and update the channel occupancy table according to the channel identifier of the second channel and the device identifier of the first slave device.

[0127] Step 606: Determine whether the waiting time has reached the preset channel waiting time.

[0128] If yes, proceed to step 607; otherwise, proceed to step 605.

[0129] Step 607: Determine whether the channel identifier of the current channel is N.

[0130] If yes, proceed to step 602; otherwise, proceed to step 604.

[0131] For ease of understanding, Figure 7 An interaction diagram illustrating an example of a master and slave unit in a kitchen appliance linkage system provided in this application embodiment, such as... Figure 7 As shown, the processing procedures for the master and slave devices are as follows:

[0132] Step 701a: Power on the host computer.

[0133] Step 701b: Power on slave device 1.

[0134] Step 701c: Power on slave device 2.

[0135] Step 701d: Power on slave device 3.

[0136] Step 702: The host switches to channel 0 and sends a broadcast channel request message. This channel request message carries a channel occupancy table.

[0137] Step 703a: Slave 1 (device identifier 22) receives a channel request message sent by the host on channel 0. In the channel occupancy table, it finds that the channel identifier of the target channel corresponding to device identifier 22 is 1.

[0138] Step 703b: Slave 2 (device identifier 44) receives a channel request message sent by the host on channel 0. In the channel occupancy table, it finds that the target channel corresponding to device identifier 44 has a channel identifier of 4.

[0139] Step 703c: Slave 3 (device ID 55) receives a channel request message sent by the host on channel 0. In the channel occupancy table, the channel ID corresponding to the target channel with device ID 55 is not found. So, idle channel 2 is randomly selected from the idle channels as the target channel.

[0140] Step 704a: Slave 1 determines the delayed transmission duration as t based on the channel identifier 1 of the target channel and the preset channel waiting time t.

[0141] Step 704b: Slave 2 determines the delayed transmission duration to be 4t based on the channel identifier 4 of the target channel and the preset channel waiting time t.

[0142] Step 704c: Slave 3 determines the delayed transmission duration to be 2t based on the channel identifier 2 of the target channel and the preset channel waiting time t.

[0143] Step 705a: After waiting for a transmission delay duration t, slave device 1 sends a unicast channel request response message to the host in channel 1. The channel request response message carries the local device identifier 22.

[0144] In step 705b, after waiting for a transmission delay of 2t, slave device 3 sends a unicast channel request response message to the master device in channel 2. The channel request response message carries the local device identifier 55.

[0145] In step 705c, after waiting for a transmission delay of 4t, slave device 2 sends a unicast channel request response message to the master device on channel 4. The channel request response message carries the local device identifier 44.

[0146] Step 706a: After the host waits for a preset channel waiting time t, it switches to the channel with the channel identifier incremented by 1 (i.e., channel 1) and receives a channel request response message from slave 1 carrying the device identifier corresponding to slave 1. Based on the channel identifier of channel 1 and the device identifier of slave 1, the host queries the channel occupancy table to find that the target device identifier of channel 1 is consistent with the device identifier of slave 1. The host keeps the correspondence between the channel identifier of channel 1 and the target device identifier unchanged in the channel occupancy table.

[0147] Step 706b: After the host waits for a preset channel waiting time t, it switches to the channel with the channel identifier incremented by 1 (i.e., channel 2) and receives a channel request response message from slave 3 carrying the device identifier corresponding to slave 3. Based on the channel identifier of channel 2 and the device identifier of slave 3, if the target device identifier of channel 2 is not found in the channel occupancy table, the host adds the correspondence between the channel identifier of channel 2 and the device identifier of slave 3 to the channel occupancy table.

[0148] In step 706c, after the host waits for a preset channel waiting time t, it switches to the channel with the channel identifier incremented by 1 (i.e., channel 3). It does not receive a channel request response message, and the host does not find the target device identifier of channel 3 in the channel occupancy table, so it does not need to update the channel occupancy table.

[0149] In step 706d, after the host waits for a preset channel waiting time t, it switches to the channel with the channel identifier incremented by 1 (i.e., channel 4) and receives a channel request response message from slave 2 carrying the device identifier corresponding to slave 2. Based on the channel identifier of channel 4 and the device identifier of slave 2, the host queries the channel occupancy table to find that the target device identifier of channel 4 is consistent with the device identifier of slave 2. The host keeps the correspondence between the channel identifier of channel 4 and the target device identifier unchanged in the channel occupancy table.

[0150] This application provides a method for determining a channel. First, a host sends a broadcast-type channel request message on a first channel. The channel request message carries a channel occupancy table, which includes a correspondence between channel identifiers and device identifiers. After receiving the broadcast-type channel request message from the host on the first channel, a slave device queries the channel occupancy table for the channel identifier of the target channel corresponding to its local device identifier. If no channel identifier is found, an idle channel is randomly selected as the target channel, and a delay transmission duration is determined based on the target channel's channel identifier. After waiting for the delay transmission duration, the slave device sends a unicast-type channel request response message to the host on the target channel. This channel request response message carries the local device identifier. After the waiting duration on the first channel reaches a preset channel waiting duration, the host switches to a second channel with its channel identifier incremented by 1. On the second channel, the host receives a channel request response message from the first slave device carrying the device identifier corresponding to the first slave device, and updates the channel occupancy table based on the channel identifier of the second channel and the device identifier of the first slave device. After the host's waiting time on the second channel reaches its designated duration, it switches to the third channel (channel identifier incremented by 1), accepts the channel request response message, and updates the channel occupancy table. This process continues until the last channel is used. Using this method, each slave device, upon receiving a channel request message from the host, can select the corresponding target channel according to the channel occupancy table and send a channel request response message to the host in a time-division multiplexing manner. In this way, the host switches channels in ascending order of channel identifiers, allowing it to sequentially receive the channel request response messages from the slave devices and update the channel occupancy table based on the channel identifier and the slave device's device identifier, thus avoiding communication failures caused by co-channel interference.

[0151] It should be understood that, although Figures 3 to 7 The steps in the flowchart are shown sequentially as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order in which these steps are executed, and they can be performed in other orders. Figures 3 to 7 At least some of the steps in the process may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but may be executed at different times. The execution order of these steps or stages is not necessarily sequential, but may be executed in turn or alternately with other steps or at least some of the steps or stages in other steps.

[0152] It is understood that the same / similar parts between the various embodiments of the methods described above in this specification can be referred to each other. Each embodiment focuses on the differences from other embodiments, and relevant parts can be referred to the description of other method embodiments.

[0153] This application also provides a channel determination device, such as... Figure 8 As shown, the device is used in a host computer and includes:

[0154] The broadcast module 810 is used to send a broadcast-type channel request message in the first channel; the channel request message carries a channel occupancy table, which includes the correspondence between channel identifiers and device identifiers;

[0155] The update module 820 is used to switch to the second channel after the waiting time of the first channel reaches the preset channel waiting time. In the second channel, it receives the channel request response message sent by the first slave device, which carries the device identifier of the first slave device. The update module 820 updates the channel occupancy table according to the channel identifier of the second channel and the device identifier of the first slave device. The channel identifier of the second channel is equal to the channel identifier of the first channel plus 1.

[0156] The switching module 830 is used to switch to the third channel after the waiting time of the second channel reaches the channel waiting time, until the last channel ends; the channel identifier of the third channel is equal to the channel identifier of the second channel plus 1.

[0157] As an optional implementation, the update module is specifically used for:

[0158] Based on the channel identifier of the second channel, look up the target device identifier corresponding to the channel identifier of the second channel in the channel occupancy table;

[0159] If the target device identifier is not found, the correspondence between the channel identifier of the second channel and the device identifier of the first slave device will be added to the channel occupancy table.

[0160] If the target device identifier is found, determine whether the target device identifier matches the device identifier of the first slave device;

[0161] If the target device identifier is inconsistent with the device identifier of the first slave device, the correspondence between the channel identifier of the second channel and the target device identifier remains unchanged in the channel occupancy table.

[0162] As an optional implementation, the device further includes:

[0163] The judgment module is used to increment the number of disconnections corresponding to the target device identifier by 1 if a channel request response message sent by the second slave to which the target device identifier belongs is not received in the second channel.

[0164] The deletion module is used to delete the correspondence between the channel identifier of the second channel and the target device identifier in the channel occupancy table if the number of lost connections exceeds a preset threshold.

[0165] As an optional implementation, the device further includes:

[0166] The reset module is used to reset the number of disconnections corresponding to the target device identifier to zero if the target device identifier is the same as the device identifier of the first slave device.

[0167] This application also provides another channel determination device, such as... Figure 9 As shown, the device is applied to a slave device, and the device includes:

[0168] The receiving module 910 is used to receive a broadcast-type channel request message sent by the host in the first channel; the channel request message carries a channel occupancy table, which includes the correspondence between channel identifiers and device identifiers;

[0169] The query module 920 is used to query the channel identifier of the target channel corresponding to the local device identifier in the channel occupancy table;

[0170] The first determining module 930 is used to randomly select an idle channel from the idle channels as the target channel if no channel identifier corresponding to the local device identifier is found; the idle channel is a channel in the channel occupancy table that does not have a correspondence between the channel identifier and the device identifier.

[0171] The second determining module 940 is used to determine the delayed transmission duration based on the channel identifier of the target channel and the preset channel waiting duration;

[0172] The sending module 950 is used to send a unicast channel request response message to the host in the target channel after waiting for a delay period. The channel request response message carries a local device identifier, which is used by the host to update the channel occupancy table.

[0173] As an optional implementation, the device further includes:

[0174] The third determination module is used to execute the second determination module if the channel identifier of the target channel corresponding to the local device identifier is found.

[0175] This application provides a channel determination apparatus. First, a host sends a broadcast-type channel request message in a first channel. The channel request message carries a channel occupancy table, which includes a correspondence between channel identifiers and device identifiers. After receiving the broadcast-type channel request message from the host in the first channel, a slave device queries the channel occupancy table for the channel identifier of the target channel corresponding to its local device identifier. If no channel identifier is found, an idle channel is randomly selected as the target channel, and a delay transmission duration is determined based on the channel identifier of the target channel. After waiting for the delay transmission duration, the slave device sends a unicast-type channel request response message to the host in the target channel. This channel request response message carries the local device identifier. After the waiting time in the first channel reaches a preset channel waiting time, the host switches to a second channel with its channel identifier incremented by 1. In the second channel, the host receives a channel request response message from the first slave device carrying the device identifier corresponding to the first slave device, and updates the channel occupancy table based on the channel identifier of the second channel and the device identifier of the first slave device. After the host's waiting time on the second channel reaches its designated duration, it switches to the third channel (channel identifier incremented by 1), accepts the channel request response message, and updates the channel occupancy table. This process continues until the last channel is used. Using this method, each slave device, upon receiving a channel request message from the host, can select the corresponding target channel according to the channel occupancy table and send a channel request response message to the host in a time-division multiplexing manner. In this way, the host switches channels in ascending order of channel identifiers, allowing it to sequentially receive the channel request response messages from the slave devices and update the channel occupancy table based on the channel identifier and the slave device's device identifier, thus avoiding communication failures caused by co-channel interference.

[0176] Specific limitations regarding the channel determination device can be found in the limitations of the channel determination method described above, and will not be repeated here. Each module in the aforementioned channel determination device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in hardware or independently of the processor in the computer device, or stored in software in the memory of the computer device, so that the processor can call and execute the corresponding operations of each module.

[0177] In one embodiment, a computer device is provided, such as Figure 10 As shown, it includes a memory and a processor. The memory stores a computer program that can run on the processor. When the processor executes the computer program, it implements the method steps for determining the aforementioned channel.

[0178] In one embodiment, a computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method for determining the channel described above.

[0179] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0180] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0181] It should also be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for display, data used for analysis, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0182] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0183] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0184] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A method of determining a channel, characterized by, The method is applied to a host, and the method comprises: sending a broadcast type channel application request message in a first channel; the channel application request message carries a channel occupation table, and the channel occupation table comprises a correspondence between a channel identifier and a device identifier; after a waiting duration of the first channel reaches a preset channel waiting duration, switching to a second channel, receiving a channel application response message sent by a first slave in the second channel, the channel application response message carrying a device identifier corresponding to the first slave, and updating the channel occupation table according to a channel identifier of the second channel and the device identifier of the first slave; the channel identifier of the second channel is equal to the channel identifier of the first channel plus 1; after a waiting duration of the second channel reaches the channel waiting duration, switching to a third channel until the last channel ends; the updating of the channel occupation table according to the channel identifier of the second channel and the device identifier of the first slave comprises: querying a target device identifier corresponding to the channel identifier of the second channel in the channel occupation table according to the channel identifier of the second channel; if the target device identifier is not queried, adding a correspondence between the channel identifier of the second channel and the device identifier of the first slave in the channel occupation table; and if the target device identifier is queried, keeping the correspondence between the channel identifier of the second channel and the target device identifier unchanged in the channel occupation table.

2. The method of claim 1, wherein, The method further comprises: if the channel application response message sent by a second slave to which the target device identifier belongs is not received in the second channel, determining that the target device identifier is in a disconnection state, and adding 1 to a disconnection number corresponding to the target device identifier; otherwise, clearing the disconnection number corresponding to the target device identifier.

3. The method of claim 2, wherein, The method further comprises: if the disconnection number is greater than a preset disconnection number threshold, deleting the correspondence between the channel identifier of the second channel and the target device identifier in the channel occupation table.

4. A method of determining a channel, characterized by, The method is applied to a slave, and the method comprises: receiving a broadcast type channel application request message sent by a host in a first channel; the channel application request message carries a channel occupation table, and the channel occupation table comprises a correspondence between a channel identifier and a device identifier; querying a target channel identifier corresponding to a local device identifier in the channel occupation table; if the target channel identifier corresponding to the local device identifier is not queried, randomly selecting an idle channel as the target channel in an idle channel; the idle channel is a channel in which the channel occupation table does not comprise a correspondence between a channel identifier and a device identifier; determining a delay sending duration according to the target channel identifier and a preset channel waiting duration; after waiting for the delay sending duration, sending a unicast type channel application response message to the host in the target channel; the channel application response message carries the local device identifier, and the local device identifier is used by the host to update the channel occupation table. If the channel identifier corresponding to the target channel of the local device identifier is queried, the step of determining the delay sending time length according to the channel identifier of the target channel and a preset channel waiting time length is executed. The formula for determining the delay sending time length according to the channel identifier of the target channel and the preset channel waiting time length is T=kxt, wherein T represents the delay sending time length, k represents the channel identifier of the target channel, and t represents the preset channel waiting time length.

5. A channel determining apparatus characterized by comprising: The device is applied to a host, and the device comprises: The broadcast module is configured to send a channel application request message of a broadcast type in a first channel; the channel application request message carries a channel occupation table, and the channel occupation table comprises a corresponding relationship between a channel identifier and a device identifier; The update module is configured to switch to a second channel after a waiting time length of the first channel reaches a preset channel waiting time length, receive a channel application response message carrying a device identifier corresponding to a first slave in the second channel, and update the channel occupation table according to a channel identifier of the second channel and the device identifier of the first slave; the channel identifier of the second channel is equal to the channel identifier of the first channel plus 1; the target device identifier corresponding to the channel identifier of the second channel is queried in the channel occupation table according to the channel identifier of the second channel; if the target device identifier is not queried, the corresponding relationship between the channel identifier of the second channel and the device identifier of the first slave is added in the channel occupation table; if the target device identifier is queried, the corresponding relationship between the channel identifier of the second channel and the target device identifier is kept unchanged in the channel occupation table; The switching module is configured to switch to a third channel after a waiting time length of the second channel reaches the channel waiting time length, and the switching is performed until a last channel ends.

6. A channel determining apparatus characterized by comprising: The device is applied to a slave, and the device comprises: The receiving module is configured to receive a channel application request message of a broadcast type sent by a host in a first channel; the channel application request message carries a channel occupation table, and the channel occupation table comprises a corresponding relationship between a channel identifier and a device identifier; The query module is configured to query a channel identifier of a target channel corresponding to a local device identifier in the channel occupation table; The first determination module is configured to select a free channel as the target channel in the free channel if the channel identifier corresponding to the target channel of the local device identifier is not queried; the free channel is a channel without a corresponding relationship between a channel identifier and a device identifier in the channel occupation table; The second determination module is configured to determine a delay sending time length according to the channel identifier of the target channel and a preset channel waiting time length. The sending module is configured to send a unicast type channel application response message to the host in the target channel after waiting for the delay sending duration; the channel application response message carries the local device identifier, and the local device identifier is used by the host to update the channel occupancy table; if the channel identifier of the target channel corresponding to the local device identifier is queried, the step of determining the delay sending duration according to the channel identifier of the target channel and the preset channel waiting duration is performed; the formula for determining the delay sending duration according to the channel identifier of the target channel and the preset channel waiting duration is T=kxt; wherein T represents the delay sending duration, k represents the channel identifier of the target channel, and t represents the preset channel waiting duration. 7.A kitchen electrical appliance linkage system, comprising a host and at least one slave, wherein the host applies the channel determination method according to any one of claims 1 to 3, and the slave applies the channel determination method according to claim 4.

Images