Channel allocation method, apparatus and system applied to fttr

Abstract

Embodiments of the present application disclose a channel allocation method, apparatus and system applied to FTTR. Each sub-device sends a first message to a main device to request the main device to allocate a working channel for the sub-device, that is, the working channels of all sub-devices in an FTTR network are centrally allocated by the main device. In this way, by comprehensively considering the requests from the sub-devices, the main device can more reasonably allocate working channels for all the sub-devices, thereby avoiding working channel conflicts among the sub-devices, effectively preventing mutual interference, and thus facilitating improvement of the overall network throughput efficiency.

Description

A channel allocation method, apparatus, and system for FTTR

[0001] This application claims priority to Chinese Patent Application No. 202510039041.X, filed on January 9, 2025, entitled "A Channel Allocation Method, Apparatus and System for FTTR", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to a channel allocation method, apparatus and system for FTTR. Background Technology

[0003] With the development of communication technology, optical fiber transmission is increasingly being used in communication systems, among which fiber to the room (FTTR) is a crucial component of optical networks. An FTTR network consists of a main FTTR unit (MFU) and sub-FTTR units (SFU), connected by optical fiber. The main unit, acting as an optical network terminal (ONT) or optical network unit (ONU) in a passive optical network (PON), connects to the optical line terminal (OLT) at the operator's central office via optical fiber.

[0004] In FTTR scenarios, due to the limited Wi-Fi channel resources, if there are many Wi-Fi users, multiple devices may transmit and receive signals on the same channel, leading to mutual interference. Taking a sub-device in an FTTR network as an example, the sub-device will switch channels to cope with interference. However, the working channel of the sub-device after channel switching may still conflict with the working channels of other devices in the FTTR network (including the master device and other sub-devices), failing to solve the interference problem and resulting in a decrease in the overall network throughput efficiency. Summary of the Invention

[0005] This application provides a channel allocation method, apparatus, and system for FTTR. The master device can allocate working channels to all sub-devices more reasonably by comprehensively considering the requests of each sub-device, which can avoid working channel conflicts between sub-devices and effectively avoid mutual interference, thereby improving the overall network throughput efficiency.

[0006] Firstly, embodiments of this application provide a channel allocation method for FTTR. In an FTTR network, the master device is also referred to as the main FTTR unit (MFU), and the sub-device is also referred to as the sub-FTTR unit (SFU). This channel selection method is applied to the master device. Specifically, the master device receives a first message sent by the sub-device, which requests the master device to allocate a working channel for the sub-device. The master device then sends a second message to the sub-device, which indicates the working channel allocated by the master device for the sub-device.

[0007] In this implementation, the sub-device sends a first message to the master device to request the master device to allocate a working channel for the sub-device. In other words, the working channels for the sub-devices are centrally allocated by the master device. This allows the master device to comprehensively consider the requests from each sub-device and allocate working channels more rationally, avoiding working channel conflicts between sub-devices and effectively preventing mutual interference, thereby improving the overall network throughput efficiency.

[0008] In some possible implementations, the first message is further used to request the master device to allocate bandwidth for the working channel to the sub-device, and the second message is further used to indicate the bandwidth of the working channel allocated by the master device to the sub-device. Considering that the master device has more information about the working channels and bandwidth of the devices than the sub-devices, it is equivalent to the master device having more reference information to allocate working channels to the sub-devices. The allocation scheme of working channels and bandwidth is more reasonable and can effectively avoid mutual interference caused by working channel conflicts between devices.

[0009] In some possible implementations, the master device assigns a different working channel to the sub-device than the working channel of at least one other device, thereby helping to avoid mutual interference with other devices.

[0010] In some possible implementations, the other devices include at least one of the following: a master device in the same FTTR network as the sub-device, other sub-devices in the same FTTR network as the sub-device, and devices in different networks than the sub-device. Various types of other devices are provided here, allowing the sub-device to avoid interference with devices in the same FTTR network as well as with devices in other networks.

[0011] In some possible implementations, the first message is also used to indicate that the request is urgent, and the method further includes: the master device prioritizing the allocation of a working channel to the sub-device based on the first message. The first message indicating an urgent request signifies that allocating a working channel to the sub-device is a priority matter, and the master device should immediately prioritize the allocation of a working channel to the sub-device, enabling the sub-device to begin normal operation as quickly as possible and improving the timeliness of data transmission.

[0012] In some possible implementations, the first message is also used to indicate that the request is not urgent. The method further includes: if preset conditions are met, the master device allocates a working channel to the sub-device according to the first message. The preset conditions include at least one of the following: being in a nighttime environment; the master device receiving messages from multiple sub-devices requesting the master device to allocate a working channel. In other words, the request in the first message is a non-urgent request, indicating that the allocation of a working channel to the sub-device can be postponed. For example, allocating a working channel to the sub-device only when certain preset conditions are met allows the master device to prioritize allocating working channels to other sub-devices that have sent urgent requests, which helps reduce the processing burden on the master device and improves allocation efficiency.

[0013] In some possible implementations, the first message is also used to indicate at least one of the sub-device's preferred operating channel and the bandwidth of the preferred operating channel. The method further includes: the master device allocating an operating channel and / or bandwidth to the sub-device based on at least one of the sub-device's preferred operating channel and the bandwidth of the preferred operating channel. The master device may prioritize satisfying the sub-device's preferences, thereby allocating a more suitable operating channel and / or bandwidth to the sub-device.

[0014] In some possible implementations, the first message includes the following fields: channel number, bandwidth, and priority value. This allows the sub-device to quickly understand its requests and preferences based on the content carried in the first message.

[0015] In some possible implementations, the first message includes a channel priority report from the sub-device, which includes the following fields: number of radio frequencies, radio frequency identifier, number of operation sets, operation set, number of channels, channel number, and priority value. The method further includes: the master device allocating a working channel to the sub-device based on the sub-device's channel priority report. This first message can reuse the format of the channel priority report, resulting in lower implementation costs.

[0016] In some possible implementations, after the master device sends the second message to the slave device, the method further includes: the master device receiving a third message sent by the slave device, the third message indicating whether the slave device accepts the working channel allocated to it by the master device. The master device can promptly ascertain whether the slave device accepts the allocated working channel through the third message sent by the slave device, enhancing the completeness of the solution.

[0017] Secondly, embodiments of this application provide a channel allocation method applied to FTTR. In an FTTR network, the master device is also referred to as MFU, and the slave device is also referred to as SFU. This channel selection method is applied to the slave device. Specifically, the slave device sends a first message to the master device, which requests the master device to allocate a working channel for the slave device. The slave device receives a second message sent by the master device, which indicates the working channel allocated by the master device for the slave device.

[0018] In some possible implementations, the first message is further used to request the master device to allocate bandwidth of the working channel to the sub-device, and the second message is further used to indicate the bandwidth of the working channel allocated by the master device to the sub-device.

[0019] In some possible implementations, the working channel assigned by the master device to the sub-device is different from the working channel of at least one other device.

[0020] In some possible implementations, other devices include at least one of the following: a master device that is in the same FTTR network as the sub-device, other sub-devices that are in the same FTTR network as the sub-device, and devices that are in different networks from the sub-device.

[0021] In some possible implementations, the first message is also used to indicate whether the request is urgent.

[0022] In some possible implementations, the first message is also used to indicate at least one of the sub-device's preferred operating channel and the bandwidth of the preferred operating channel.

[0023] In some possible implementations, the first message includes the following fields: channel number, bandwidth, and priority value.

[0024] In some possible implementations, the first message includes a channel priority report from the sub-device, which includes the following fields: number of radio frequencies, radio frequency identifier, number of operation sets, operation set, number of channels, channel number, and priority value.

[0025] In some possible implementations, after the sub-device receives the second message sent by the master device, the method further includes: the sub-device sending a third message to the master device, the third message indicating whether the sub-device accepts the working channel allocated to the sub-device by the master device.

[0026] Thirdly, embodiments of this application provide a master device, which includes a transceiver unit. The transceiver unit is configured to: receive a first message sent by a sub-device, the first message being a request from the master device to allocate a working channel for the sub-device; and send a second message to the sub-device, the second message being an indication from the master device to allocate a working channel for the sub-device.

[0027] In some possible implementations, the first message is further used to request the master device to allocate bandwidth of the working channel to the sub-device, and the second message is further used to indicate the bandwidth of the working channel allocated by the master device to the sub-device.

[0028] In some possible implementations, the master device assigns a different working channel to the sub-device than the working channel of at least one other device, thereby helping to avoid mutual interference with other devices.

[0029] In some possible implementations, other devices include at least one of the following: a master device that is in the same FTTR network as the sub-device, other sub-devices that are in the same FTTR network as the sub-device, and devices that are in different networks from the sub-device.

[0030] In some possible implementations, the first message is also used to indicate that the request is an urgent request. The master device also includes a processing unit, which is used to: preferentially allocate working channels to the sub-devices based on the first message.

[0031] In some possible implementations, the first message is also used to indicate that the request is not urgent. The master device further includes a processing unit, which is used to: allocate a working channel to the sub-devices according to the first message if preset conditions are met. The preset conditions include at least one of the following: being in a nighttime environment, or the master device receiving messages from multiple sub-devices requesting the master device to allocate a working channel.

[0032] In some possible implementations, the first message is also used to indicate at least one of the sub-device's preferred operating channel and the bandwidth of the preferred operating channel. The master device further includes a processing unit configured to: allocate an operating channel and / or bandwidth to the sub-device according to at least one of the sub-device's preferred operating channel and the bandwidth of the preferred operating channel.

[0033] In some possible implementations, the first message includes the following fields: channel number, bandwidth, and priority value.

[0034] In some possible implementations, the first message includes a channel priority report from the sub-device, which includes the following fields: number of radio frequencies, radio frequency identifier, number of operation sets, operation set, number of channels, channel number, and priority value. The master device also includes a processing unit for allocating working channels to the sub-device based on the sub-device's channel priority report.

[0035] In some possible implementations, after the transceiver unit sends the second message to the sub-device, the transceiver unit is further configured to: receive a third message sent by the sub-device, the third message being used to indicate whether the sub-device accepts the working channel allocated to the sub-device by the master device.

[0036] Fourthly, embodiments of this application provide a sub-device, which includes a transceiver unit. The transceiver unit is configured to: send a first message to a master device, the first message being a request for the master device to allocate a working channel for the sub-device; and receive a second message sent by the master device, the second message being an indication of the working channel allocated by the master device for the sub-device.

[0037] In some possible implementations, the first message is further used to request the master device to allocate bandwidth of the working channel to the sub-device, and the second message is further used to indicate the bandwidth of the working channel allocated by the master device to the sub-device.

[0038] In some possible implementations, the working channel assigned by the master device to the sub-device is different from the working channel of at least one other device.

[0039] In some possible implementations, other devices include at least one of the following: a master device that is in the same FTTR network as the sub-device, other sub-devices that are in the same FTTR network as the sub-device, and devices that are in different networks from the sub-device.

[0040] In some possible implementations, the first message is also used to indicate whether the request is urgent.

[0041] In some possible implementations, the first message is also used to indicate at least one of the sub-device's preferred operating channel and the bandwidth of the preferred operating channel.

[0042] In some possible implementations, the first message includes the following fields: channel number, bandwidth, and priority value.

[0043] In some possible implementations, the first message includes a channel priority report from the sub-device, which includes the following fields: number of radio frequencies, radio frequency identifier, number of operation sets, operation set, number of channels, channel number, and priority value.

[0044] In some possible implementations, after receiving the second message sent by the master device, the transceiver unit is further configured to: send a third message to the master device, the third message being used to indicate whether the sub-device accepts the working channel allocated to the sub-device by the master device.

[0045] Fifthly, embodiments of this application provide a master device that includes instructions that, when executed by the master device, cause the master device to perform the method described in any embodiment of the first aspect.

[0046] In a sixth aspect, embodiments of this application provide a sub-device that includes instructions that, when executed by the sub-device, cause the sub-device to perform the method described in any embodiment of the second aspect.

[0047] In a seventh aspect, embodiments of this application provide a master device, which includes a processor and an interface. The interface is used to transmit and receive signals, and the processor is used to execute the method described in any embodiment of the first aspect.

[0048] Eighthly, embodiments of this application provide a sub-device, which includes a processor and an interface. The interface is used to transmit and receive signals, and the processor is used to perform the method described in any embodiment of the second aspect.

[0049] In a ninth aspect, embodiments of this application provide a communication system comprising a master device as described in any embodiment of the third aspect, the fifth aspect, or the seventh aspect, and at least one sub-device as described in any embodiment of the fourth aspect, the sixth aspect, or the eighth aspect, wherein the master device communicates with at least one sub-device.

[0050] In a tenth aspect, embodiments of this application provide a chip for performing the methods described in any of the first or second aspects.

[0051] In one aspect, this application provides a computer-readable storage medium storing instructions that, when executed by a computer, cause the method described in any of the embodiments of the first or second aspect to be implemented.

[0052] In a twelfth aspect, this application provides a computer program product including program instructions that, when executed, implement the method described in any of the embodiments of the first or second aspect above. Attached Figure Description

[0053] Figure 1 is a schematic diagram of a possible WLAN network architecture in an embodiment of this application;

[0054] Figure 2 is a schematic diagram of the FTTH / O system architecture;

[0055] Figure 3 is a schematic diagram of the FTTR system architecture;

[0056] Figure 4 is a schematic diagram of a scenario where a sub-device switches channels in an FTTR network.

[0057] Figure 5 is a flowchart of a channel allocation method provided in an embodiment of this application;

[0058] Figure 6 is another flowchart of the channel allocation method provided in the embodiments of this application;

[0059] Figure 7 is a schematic diagram of an implementation scenario in which the master device allocates a working channel to the sub-device in an embodiment of this application;

[0060] Figure 8 is a schematic diagram of a main device in an embodiment of this application;

[0061] Figure 9 is a schematic diagram of another structure of the main device in an embodiment of this application;

[0062] Figure 10 is a schematic diagram of a sub-device in an embodiment of this application;

[0063] Figure 11 is a schematic diagram of another structure of the sub-device in an embodiment of this application. Detailed Implementation

[0064] This application provides a channel allocation method, apparatus, and system for FTTR. The master device can allocate working channels to all sub-devices more reasonably by comprehensively considering the requests of each sub-device, which can avoid working channel conflicts between sub-devices and effectively avoid mutual interference, thereby improving the overall network throughput efficiency.

[0065] It should be understood that the terms "an embodiment," "an implementation," "an embodiment," or "an example" used throughout the specification mean that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, the phrases "in an embodiment," "an implementation," "an embodiment," or "an example" appearing throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above processes do not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0066] Furthermore, the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship. It should be understood that in the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information. And, unless otherwise stated, the ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the order, sequence, priority, or importance of multiple objects. Furthermore, the terms "comprising" and "having" in the embodiments, claims, and drawings of this application are not exclusive. For example, a process, method, system, product, or device that includes a series of steps or modules is not limited to the listed steps or modules and may also include steps or modules not listed.

[0067] Referring to Figure 1, a possible WLAN network architecture is illustrated. The wireless local area network (WLAN) architecture includes a wireless controller (also referred to as a "control node" in this embodiment), wireless access points (also referred to as "network nodes" in this embodiment), and terminal devices. The wireless controller is used to configure services and radio frequency for the access points. The wireless access point (AP) is used to provide service access to associated STAs. Terminal devices, acting as STAs, can be associated with the access point.

[0068] Terminal devices can include mobile phones (or "cellular" phones), computers with mobile terminal devices, portable, pocket-sized, handheld, and computer-embedded mobile devices, etc. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), and other devices. Terminal devices can also be computers, tablets, e-readers, and smart home devices such as smart TVs and smart speakers. As an example and not a limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices or smart wearable devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices; they achieve powerful functions through software support, data interaction, and cloud interaction. Wearable smart devices in a broad sense include those that are feature-rich, large in size, and can perform all or part of their functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets, smart helmets, and smart jewelry for vital sign monitoring.

[0069] With the development of communication technology, fiber optic transmission is increasingly being used in communication systems, among which fiber to the room (FTTR) is a crucial component of optical networks. An FTTR system consists of a main device and sub-devices, connected via optical fiber. The main device, acting as an optical network terminal (ONT) or optical network unit (ONU) in a passive optical network (PON), is connected to the optical line terminal (OLT) at the operator's central office via optical fiber.

[0070] Figure 2 illustrates the system architecture of Fiber to the Home / Office (FTTH / O). It connects upstream network-side equipment (such as switches and routers) and downstream ONTs via an optical distribution network (ODN). The ODN includes passive optical splitters for optical power distribution, a trunk fiber connecting the passive splitters and the OLT, and branch fibers connecting the passive splitters and ONTs. When transmitting downlink signals, the downlink signal sent by the OLT is transmitted to each ONT through the splitter, and the ONT selectively receives downlink data belonging to itself from the downlink signal. When transmitting uplink signals, the uplink signals sent by N ONTs are combined into a single optical signal by the splitter and transmitted to the OLT.

[0071] Building upon FTTH / O, to address signal coverage issues (such as wireless LAN (WLAN) signals) in home or office networks, fiber optic cables can be extended further into the room. Optical terminal equipment providing WLAN signals is installed inside the room, thus reducing the distance between the user terminal and the wireless access point (AP) and improving signal quality. This technology is called Fiber to the Room (FTTR).

[0072] Figure 3 illustrates the system architecture of FTTR. In FTTH / O, the OLT is deployed in the central equipment room, while the ONT is deployed in homes or offices. The master device in the FTTR network acts as both the ONT in the FTTH network and the upstream device for the FTTR sub-devices, managing them. The sub-devices in FTTR can be deployed in various rooms of homes or offices to provide signal to user terminals. These sub-devices possess ONT functionality and can also function as wireless access points (APs).

[0073] Multiple sub-devices can be deployed in an FTTR system, each connected to the main device via an optical splitter. The main device can manage and configure all sub-devices centrally. The main device can also be called a "main gateway," "main optical modem," or "main FTTR unit (MFU)," while sub-devices can be called "slave gateways," "slave optical modems," or "slave FTTR units (SFU)," etc.

[0074] It should be noted that this application can be applied to point-to-multipoint (P2MP) communication systems, which specifically include a master device and multiple sub-devices. The master device can collaboratively manage multiple sub-devices. For example, in the FTTH / O scenario shown in Figure 2, the master device can be an OLT, and the sub-devices can be ONUs. As another example, in the FTTR scenario shown in Figure 3, the master device can be an MFU, and the sub-devices can be MFUs.

[0075] It's important to note that a frequency band refers to a specific range of radio waves allocated for wireless communication. The most common Wi-Fi frequency bands are 2.4 GHz and 5 GHz. The 2.4 GHz band offers wider coverage and stronger penetration, making it suitable for home and office environments, but it is susceptible to interference, and channels tend to overlap. The 5 GHz band provides faster data transmission speeds and less interference, but its coverage is relatively smaller, and its wall-penetrating ability is weaker. A channel is a further subdivision within a given frequency band. A channel is like a "lane" on the "highway" of the frequency band, used to send and receive wireless signals at specific frequencies. Each channel has its own corresponding numerical designation, also known as the channel number. The 2.4 GHz band typically contains 13 (or 14, depending on the region) channels. Channels numbered 1, 6, and 11 are non-overlapping, ideal for avoiding interference. Other channel numbers, such as 2, 3, 4, 5, 7, 8, 9, 10, 12, and 13, may interfere with each other. The 5GHz band offers more channel options, typically with more non-overlapping channels, reducing the possibility of channel overlap and interference. Common recommended channels include 149, 48, and 36.

[0076] In FTTR scenarios, due to the limited Wi-Fi channel resources, if there are many Wi-Fi users, multiple devices may transmit and receive signals on the same channel, leading to mutual interference. Taking a sub-device in an FTTR network as an example, the sub-device will switch channels to cope with interference. However, the working channel of the sub-device after channel switching may still conflict with the working channels of other devices in the FTTR network (including the master device and other sub-devices), failing to solve the interference problem and resulting in a decrease in the overall network throughput efficiency.

[0077] Figure 4 illustrates a scenario of sub-device channel switching in an FTTR network. In the FTTR network shown in Figure 4, the master device is connected to sub-devices 1 and 2 via optical fibers. All three devices (master, sub-device 1, and sub-device 2) can provide WLAN signals to the STA. Each device communicates with the STA on its own operating channel. For example, the master device's operating channel number is 149 (Ch149), sub-device 1's is 36 (Ch36), and sub-device 2's is 136 (Ch136). If sub-device 1 detects interference or poor communication quality, it indicates that its operating channel may overlap with the operating channels of other devices in the FTTR network. Sub-device 1 then switches its operating channel to Ch149. However, since sub-device 1 is unaware of the operating channels of other devices, its operating channel overlaps with the master device's after switching to Ch149, resulting in mutual interference between sub-device 1 and the master device.

[0078] To address the aforementioned issues, this application provides a channel allocation method for FTTR. A sub-device sends a first message to the master device, requesting the master device to allocate a working channel for the sub-device. In other words, the working channels for all sub-devices in the FTTR network are centrally allocated by the master device. This allows the master device to comprehensively consider the requests from each sub-device and allocate working channels more rationally, avoiding working channel conflicts between sub-devices and effectively preventing mutual interference, thereby improving the overall network throughput efficiency.

[0079] The channel allocation method for FTTR provided in this application is described in detail below with reference to the accompanying drawings. This application does not limit the number of sub-devices communicating with the master device. The following embodiments only illustrate the interaction between the master device and one or two sub-devices, denoted as sub-device 1 and sub-device 2. The interaction methods between more sub-devices and the master device are similar.

[0080] Figure 5 is a flowchart of a channel allocation method provided in an embodiment of this application. The specific flow of the channel allocation method shown in Figure 5 will be described in detail below.

[0081] 101. Sub-device 1 sends message 1 to master device.

[0082] Specifically, message 1 sent by sub-device 1 to master device requests master device to allocate a working channel for sub-device 1. Optionally, message 1 may also request master device to allocate bandwidth for the working channel for sub-device 1. It should be understood that, considering that master device has more information about the working channel and bandwidth of other devices than sub-device 1, master device has more reference information to allocate a working channel for sub-device 1, resulting in a more reasonable working channel allocation scheme and effectively avoiding mutual interference caused by working channel conflicts between devices.

[0083] It should be noted that the embodiments of this application do not limit the specific scenarios or conditions under which sub-device 1 sends message 1 to the master device. Example 1: When sub-device 1 does not have sufficient information to select a working channel, sub-device 1 sends message 1 to the master device. Example 2: When sub-device 1 selects a working channel and finds no significant performance improvement, sub-device 1 sends message 1 to the master device. Example 3: When global channel selection is enabled in the FTTR network, meaning each sub-device needs to select a working channel, sub-device 1 sends message 1 to the master device. Example 4: After the sub-device powers on or goes online, sub-device 1 sends message 1 to the master device. Example 5: After detecting interference, sub-device 1 sends message 1 to the master device.

[0084] In some possible scenarios, message 1 sent by sub-device 1 to master device can also indicate whether the request in message 1 is urgent, so that master device can allocate working channels to sub-devices in a targeted manner. For example, if message 1 is an urgent request, it means that allocating a working channel to sub-device 1 is a priority, and master device should immediately allocate a working channel to sub-device 1 with priority, so that sub-device 1 can start normal operation as soon as possible, improving the timeliness of data transmission. Alternatively, if message 1 is a non-urgent request, it means that allocating a working channel to sub-device 1 can be postponed, such as allocating a working channel to sub-device 1 when certain preset conditions are met, so that master device can prioritize allocating working channels to other sub-devices that send urgent requests, which helps reduce the processing burden on master device and improve allocation efficiency.

[0085] It should be noted that whether the request in message 1 is an urgent request can depend on the latency requirements of the current business. Some possible examples are provided below.

[0086] For example, a low-latency service, such as gaming or live streaming, or a high-throughput service, such as downloading or uploading, is currently in operation. If the air interface interference duty cycle exceeds a certain threshold, significantly impacting either the low-latency or high-throughput service, sub-device 1 wishes to quickly change its operating channel and bandwidth to avoid interference, thereby improving service transmission performance and user experience. In this scenario, message 1's request is an urgent request.

[0087] For example, if heavy interference is detected on the current working channel over a period of time (such as one day) (the interference duty cycle exceeds a certain threshold for a long time or repeatedly), but no users are performing low-latency or high-throughput services, or the user services have not been affected yet, then there is no need to immediately switch the working channel and the working channel bandwidth. In this scenario, the request in message 1 is a non-urgent request, and the master device will reallocate the working channel and the working channel bandwidth for the sub-device at night.

[0088] The following example, using Message 1 as an indicator of whether the request in Message 1 is urgent, provides a specific format for Message 1. Table 1 below provides the fields that Message 1 may include, the length of each field, its values, and definitions. As shown in Table 1, Message 1 includes the following fields: field type, field length, number of radios, radio identifier, request allocation information, and urgency level identifier.

[0089] The fieldType field is used to indicate that message 1 is a message from a sub-device requesting the master device to allocate a working channel.

[0090] The fieldLength field is used to indicate the field length of a subsequent field or the number of bytes a subsequent field includes.

[0091] The Number of Radios field is used to indicate the number of radio frequencies. For example, if the 2.4 GHz band and the 5 GHz band are supported, the number of radio frequencies is 2. Field 7 indicates that Fields 4-5 are repeated r-1 times, depending on the field value r of the Number of Radios field.

[0092] The Radio Identifier field is used to uniquely identify the radio frequency, for example, it can indicate whether the radio frequency is in the 2.4 GHz band or the 5 GHz band.

[0093] The urgency level identifier field is used to indicate whether the request in message 1 is an urgent request, which is equivalent to indicating whether a working channel needs to be allocated to sub-device 1 immediately. A field value of 0x00 indicates an urgent request (requesting immediate allocation), and a field value of 0x01 indicates a non-urgent request.

[0094] Table 1

[0095] This application does not limit the length of each field in message 1, nor does it limit the indication content corresponding to the value of each field in message 1. Similarly, it also applies to the format of other messages transmitted between the master device and the slave device. In other words, each table provided in the embodiments of this application is only a few possible examples, and those skilled in the art can make flexible changes based on it. For example, the byte length of each field in the table can be changed. For another example, the indication content corresponding to the value of each field can also be changed. Taking the fields in Table 1 as examples, the length of each field can be flexibly set; or, the length of each field can also be measured in bits. Taking the "urgency indicator" field in Table 1 as an example, the indication content corresponding to the field value of 0x00 and 0x01 of the "urgency indicator" can be swapped; or, other arbitrary values ​​can be used to indicate the above content; or, the length of the "urgency indicator" field can also be multiple bytes; or, the length of the "urgency indicator" field can also be measured in bits.

[0096] Based on Table 1 above, Table 2 below provides the fields that may be further included in Message 1, the length of each field, its value, and its definition. As shown in Table 2, Message 1 may also include a request allocation information field. The request allocation information field indicates what the sub-device is requesting the master device to allocate. For example, a field value of 0x00 indicates a request for the master device to allocate a working channel and its bandwidth; a field value of 0x01 indicates a request for the master device to allocate a working channel; and a field value of 0x02 indicates a request for the master device to allocate the bandwidth of the working channel. This request allocation information field is optional. If this field is not present, Message 1 may default to requesting the master device to allocate a working channel and / or its bandwidth.

[0097] Table 2

[0098] In some possible scenarios, message 1 sent by sub-device 1 to master device is also used to indicate at least one of the preferred operating channel and the bandwidth of the preferred operating channel. Master device can know the preferred operating channel and / or bandwidth of operating channel by sub-device 1 based on message 1. Master device can give priority to satisfying the preferences of sub-device 1, thereby allocating a more suitable operating channel and / or bandwidth of operating channel to sub-device 1. For example, sub-device 1 has performed channel scanning and identified some channels with less interference, and hopes that master device will allocate the channel with less interference as the operating channel as much as possible.

[0099] The following example illustrates the specific format of message 1, which also indicates at least one of the preferred operating channel and the bandwidth of the preferred operating channel for sub-device 1. Table 3 below provides the fields that may be included in message 1, the length of each field, its value, and its definition. As shown in Table 2, message 1 includes the following fields: field type (fieldType), field length (fieldLength), number of channels (Number of Channels), channel number, and priority value.

[0100] The fieldType field is used to indicate that message 1 is a message from a sub-device requesting the master device to allocate a working channel.

[0101] The fieldLength field is used to indicate the field length of a subsequent field or the number of bytes a subsequent field includes.

[0102] The Number of Channels field is used to indicate the preferred number of operating channels of sub-device 1 and / or the preferred bandwidth of the operating channels of sub-device 1. Field 6 indicates that fields 4-5 are repeated m-1 times depending on the field value m of the Number of Channels field.

[0103] The Channel Number field is used to indicate the preferred or preferred operating channel for sub-device 1.

[0104] The priority value field is used to indicate the specific priority preference ranking of sub-device 1. For example, the field value of the priority value field 0000-1110 is used for the table priority score 0-14, where the score 0 indicates the lowest priority preference ranking (least popular).

[0105] Table 3

[0106] Based on Table 3 above, Table 4 below provides further possible fields that may be included in message 1, the length of each field, its value, and its definition. As shown in Table 4, message 1 may also include the following fields: Number of Radios, Radio Identifier, Bandwidth, and Reason Code.

[0107] The Number of Radios field indicates the number of radio frequencies. For example, if the 2.4 GHz band and the 5 GHz band are supported, the number of radio frequencies is 2. Field 11 indicates that fields 4-10 are repeated r-1 times, depending on the field value r of the Number of Radios field. The Number of Radios field is optional.

[0108] The Radio Identifier field is used to uniquely identify the radio frequency, for example, it can indicate whether the radio frequency is in the 2.4 GHz band or the 5 GHz band. The Radio Identifier field is optional.

[0109] The bandwidth field is used to indicate the bandwidth of the preferred or preferred operating channel of sub-device 1.

[0110] The reason code field is used to indicate the reason for the preferred or preferred operation of sub-device 1. The reason code field is optional.

[0111] Table 4

[0112] The following example, using Message 1 as an example, indicates at least one of the preferred operating channel and the bandwidth of the preferred operating channel for Sub-device 1, to provide another specific format for Message 1. Message 1 carries a channel priority report from Sub-device 1; in other words, Message 1 can use the same message format as the channel priority report. Message 1 includes all the fields from the channel priority report, differing only in the description of some fields. Table 5 below provides the fields that Message 1 may include, the length of each field, its value, and its definition. As shown in Table 5, Message 1 includes the following fields: fieldType, fieldLength, channel selection type identifier, number of radios, radio identifier, number of operation sets, operation set, number of channels, channel number, priority value, and reason code.

[0113] The fieldType field is used to indicate that message 1 is a message related to channel selection.

[0114] The fieldLength field is used to indicate the field length of a subsequent field or the number of bytes a subsequent field includes.

[0115] The Channel Selection Type Identifier field is used to indicate whether message 1 is a Channel Selection Request message or a Channel Priority Report message.

[0116] The Number of Radios field is used to indicate the number of radio frequencies. For example, if the 2.4 GHz band and the 5 GHz band are supported, the number of radio frequencies is 2. Field 14 indicates that fields 5-13 are repeated r-1 times, depending on the field value r of the Number of Radios field.

[0117] The Radio Identifier field is used to uniquely identify the radio frequency, for example, it can indicate whether the radio frequency is in the 2.4 GHz band or the 5 GHz band.

[0118] The number field for the number of operations is used to indicate the number of operations. Field 13 indicates that fields 7-12 are repeated m-1 times, depending on the field value m of the number field for the number of operations.

[0119] The operation set field is used to indicate an enumerated value of the operation set, and the values ​​are shown in Table E-4 of IEEE 802.11-2020. The content of one operation set includes frequency band, bandwidth and several working channels.

[0120] The Channel Number field indicates the number of channels specified in the channel list. An empty channel list field (k=0) indicates that the specified channel takes precedence over all channels in the operation class. Field 12 indicates that fields 9-11 are repeated k-1 times depending on the field value k of the Channel Number field.

[0121] The Channel Number field is used to indicate the digital number of the channel, which is the digital number of a certain working channel in the operation set.

[0122] The priority value field is used to indicate the specific priority preference ranking of sub-device 1 in the channel list. For example, the field value 0000 of the priority value field identifies a non-operational channel, and the field values ​​0001-1110 of the priority value field are used to represent priority scores 1-14, where score 1 indicates the lowest priority preference ranking (least popular).

[0123] The reason code field is used to indicate the reason for the preferred or preferred operation of sub-device 1. The reason code field is optional.

[0124] Table 5

[0125] It should be noted that message 1 can indicate whether the request is urgent, or it can indicate at least one of the following: the preferred operating channel and the bandwidth of the preferred operating channel for sub-device 1. That is, message 1 can include the content from Table 1, Table 2, or Table 3. For example, the specific format of message 1 can include fields from Tables 1 and 2. As another example, the specific format of message 1 can include fields from Tables 1 and 3.

[0126] 102. The master device allocates a working channel to the sub-device 1.

[0127] Specifically, after receiving message 1 from sub-device 1, the master device allocates a working channel to sub-device 1 according to sub-device 1's request. Optionally, the master device may also allocate bandwidth for the working channel to sub-device 1 according to sub-device 1's request.

[0128] In some possible scenarios, message 1 sent by sub-device 1 to master device is also used to indicate whether the request in message 1 is an urgent request. In this embodiment, taking the request in message 1 as an urgent request as an example, the master device immediately allocates a working channel to sub-device 1 with priority and sends the allocated working channel to sub-device 1.

[0129] In some possible scenarios, message 1 sent by sub-device 1 to master device is also used to indicate at least one of sub-device 1's preferred working channel and preferred working channel bandwidth. Then, master device allocates working signal and / or working channel bandwidth to sub-device 1 according to at least one of sub-device 1's preferred working channel and preferred working channel bandwidth.

[0130] It should be noted that the master device can allocate the working channel and the bandwidth of the working channel to the sub-device 1 by taking into account multiple factors. Some possible examples are provided below.

[0131] For example, the master device can allocate a working channel to sub-device 1 to avoid overlap of working channels among devices. For instance, the working channel allocated to sub-device 1 by the master device may be different from the working channels of the master device and other sub-devices in the FTTR network, thereby helping to avoid mutual interference. Optionally, the working channel allocated to sub-device 1 by the master device may also be different from the working channels of devices in other networks, such as the working channels of master devices and / or other sub-devices in other FTTR networks, or the working channels of devices in other WLAN networks. It should be understood that if multiple working channels allocated to sub-device 1 can achieve the effect of avoiding interference, the working channel with the highest preference ranking (most popular) can be allocated to sub-device 1 based on its preference ranking.

[0132] For example, on the one hand, if the working channel allocated by the master device to the sub-device 1 is sufficiently staggered from the working channels of other devices to avoid interference, then the bandwidth of the working channel allocated by the master device to the sub-device 1 can be larger, for example, an 80MHz bandwidth, which is beneficial for improving transmission efficiency. On the other hand, if the bandwidth of the working channel allocated by the master device to the sub-device 1 is too large, it may still partially overlap with the working channels of other devices. In this case, the bandwidth of the working channel allocated by the master device to the sub-device 1 should be smaller, for example, a 40MHz bandwidth, to minimize interference. It should be understood that if the bandwidth of multiple working channels can satisfy either of the above aspects, then the bandwidth of the working channel with the highest preference ranking (most popular) can be allocated to the sub-device 1 according to its preference ranking.

[0133] For example, the master device can also allocate a working channel to sub-device 1 based on the distance between sub-device 1 and the master device or other sub-devices, and / or the received signal strength indicator (RSSI) between sub-device 1 and the master device or other sub-devices. For instance, if sub-device 1 and sub-device 2 are close together, or if the RSSI between sub-device 1 and sub-device 2 is high, it indicates a higher probability of mutual interference between sub-device 1 and sub-device 2. In this case, the master device allocates different working channels to sub-device 1 and sub-device 2 to minimize interference. Conversely, if sub-device 1 and sub-device 2 are far apart, or if the RSSI between sub-device 1 and sub-device 2 is low, or if sub-device 1 and sub-device 2 cannot receive signals from each other, it indicates a lower probability of mutual interference between sub-device 1 and sub-device 2. In this case, the master device can allocate the same working channel to sub-device 1 and sub-device 2, reducing channel occupancy and providing more channel options for other devices.

[0134] 103. The master device sends message 2 to the sub-device 1.

[0135] Specifically, after the master device allocates a working channel to the sub-device 1 according to message 1, the master device sends message 2 to the sub-device 1. Message 2 is used to indicate the working channel allocated by the master device to the sub-device 1. Optionally, message 2 is used to indicate the bandwidth of the working channel allocated by the master device to the sub-device 1.

[0136] It should be noted that the specific format of message 2 is not limited in the embodiments of this application. In one possible implementation, message 2 may reuse the format of message 1, and message 2 may include some or all of the fields in message 1. The descriptions of some of the same fields in message 2 and message 1 may differ.

[0137] For example, referring to Table 2 above, message 2 includes the fields in Table 2. For instance, the fieldType field can be used to indicate that message 2 is a response message to message 1; the description of the fieldLength field remains unchanged; the channel number field is used to indicate the working channel allocated by the master device to the sub-device 1; and the bandwidth field is used to indicate the bandwidth of the working channel allocated by the master device to the sub-device 1. The Number of Radios field, Radio Identifier field, Number of Channels field, Priority value field, and Reason Code field are optional and can be carried or omitted in message 2.

[0138] For example, referring to Table 3 above, message 2 includes the fields in Table 3. For instance, the fieldType field can be used to indicate that message 2 is a response message to message 1; the description of the fieldLength field remains unchanged; the channel number field is used to indicate the working channel allocated by the master device to the sub-device 1; the operation set field is used to indicate the bandwidth of the working channel allocated by the master device to the sub-device 1. The Number of Radios field, Radio Identifier field, Operation Set Number field, Channel Number field, Priority Value field, and Reason Code field are optional and can be carried or not carried in message 2.

[0139] 104. Sub-device 1 sends message 3 to master device.

[0140] Specifically, after receiving message 2 from the master device, sub-device 1 sends message 3 to the master device. Message 3 indicates whether sub-device 1 accepts the working channel allocated to it by the master device. Optionally, message 3 may also indicate whether sub-device 1 accepts the bandwidth of the working channel allocated to it by the master device. For example, if the working channel allocated to it by the master device is a preferred channel for sub-device 1, sub-device 1 accepts the allocated channel; or, if sub-device 1 has not recently performed a channel scan, it can directly accept the allocated channel. Yet another example is that sub-device 1 considers the air interface quality of the working channel allocated to it by the master device to be poor, and therefore does not accept the allocated channel.

[0141] It should be noted that this application does not limit the specific format of message 3. Table 6 below provides the fields that may be included in message 3, the length of each field, the value, and the definition. As shown in Table 6, message 3 includes the following fields: field type (fieldType), field length (fieldLength), number of radios (Number of Radios), radio (Radio) identifier, and response result.

[0142] The fieldType field is used to indicate that message 3 is a response message to message 2.

[0143] The fieldLength field is used to indicate the field length of a subsequent field or the number of bytes a subsequent field includes.

[0144] The Number of Radios field is used to indicate the number of radio frequencies. For example, if the 2.4 GHz band and the 5 GHz band are supported, the number of radio frequencies is 2. Field 6 indicates that fields 4-5 are repeated r-1 times, depending on the field value r of the Number of Radios field.

[0145] The Radio Identifier field is used to uniquely identify the radio frequency, for example, it can indicate whether the radio frequency is in the 2.4 GHz band or the 5 GHz band.

[0146] The response result field is used to indicate whether sub-device 1 accepts the working channel and / or bandwidth allocated to sub-device 1 in message 2. For example, a field value of 0x00 indicates acceptance, a field value of 0x01 indicates rejection, and a field value of 0x02-0xFF indicates reservation.

[0147] Table 6

[0148] It should be noted that, in scenarios where the request sent by the sub-device to the master device is a non-urgent request, the master device does not need to immediately allocate a working channel and its bandwidth to the sub-device. Allocation is performed only when certain preset conditions are met. A specific embodiment for this scenario is provided below. Figure 6 is another flowchart of the channel allocation method provided in this application embodiment. The specific flow of the channel allocation method shown in Figure 6 will be described in detail below.

[0149] 201. Sub-device 1 sends message 1-1 to master device.

[0150] Specifically, message 1-1 sent by sub-device 1 to master device is used to request master device to allocate a working channel for sub-device 1. Optionally, message 1-1 is also used to request master device to allocate bandwidth for the working channel for sub-device 1. Furthermore, the request in message 1-1 is a non-urgent request. For example, message 1-1 adopts the format provided in Table 1 above, and the field value of the urgency level identifier field is 0x01, indicating that it is a non-urgent request.

[0151] 202. Sub-device 2 sends message 2-1 to master device.

[0152] Specifically, message 2-1 sent by sub-device 2 to master device requests master device to allocate a working channel for sub-device 2. Optionally, message 2-1 may also request master device to allocate bandwidth for the working channel for sub-device 2. Furthermore, the request in message 2-1 is a non-urgent request; for example, message 2-1 may use the format provided in Table 1 above, with the urgency level identifier field having a value of 0x01, indicating a non-urgent request.

[0153] It should be noted that there is no explicit temporal relationship between steps 201 and 202. For example, step 201 can be executed first, or step 202 can be executed first, or steps 201 and 202 can be executed simultaneously.

[0154] 203. The master device allocates working channels for sub-device 1 and sub-device 2.

[0155] Specifically, after receiving message 1-1 from sub-device 1, the master device recognizes that the request in message 1-1 is a non-urgent request, and the master device will not immediately allocate a working channel to sub-device 1. Similarly, after receiving message 2-1 from sub-device 2, the master device recognizes that the request in message 2-1 is a non-urgent request, and the master device will not immediately allocate a working channel to sub-device 2. The master device can allocate corresponding working channels to sub-device 1 and sub-device 2 according to pre-configured allocation conditions, if the allocation conditions are met. This application embodiment does not limit the specific allocation conditions; some possible examples of allocation conditions are provided below.

[0156] For example, the master device is configured with a preset time or preset time period. If the current time is within the preset time or preset time period, the master device allocates a working channel to sub-device 1 according to message 1-1 sent by sub-device 1, and allocates a working channel to sub-device 2 according to message 2-1 sent by sub-device 2. It should be noted that the embodiments of this application do not limit the specific preset time period. For example, the preset time or preset time period is a certain time or time period in a nighttime environment. In a nighttime environment, users usually do not use the network frequently. This is equivalent to allocating corresponding working channels to sub-device 1 and sub-device 2 when the burden on the master device is reduced, which is beneficial to improving the allocation efficiency of working channels.

[0157] For example, if the master device has received messages from multiple sub-devices requesting the allocation of working channels, the master device can centrally allocate the corresponding working channels to the multiple sub-devices. Centralized allocation at a concentrated time is beneficial to improving the allocation efficiency of working channels. The specific number of multiple sub-devices depends on the actual scenario and is not limited here. For example, if sub-device 1 first sends message 1-1 to the master device, the master device will not immediately allocate a working channel to sub-device 1; later, sub-device 2 sends message 2-1 to the master device, which is equivalent to two sub-devices requesting the master device to allocate working channels; then, the master device centrally allocates the corresponding working channels to sub-device 1 and sub-device 2.

[0158] 204. The master device sends message 1-2 to the sub-device 1.

[0159] Specifically, after the master device allocates a working channel to the sub-device 1 according to message 1-1, the master device sends message 1-2 to the sub-device 1. Message 1-2 is used to indicate the working channel allocated by the master device to the sub-device 1. Optionally, message 1-2 is used to indicate the bandwidth of the working channel allocated by the master device to the sub-device 1.

[0160] It should be noted that messages 1-2 have a similar format to message 2 above. For details, please refer to the description of message 2 format in step 103 above. It will not be repeated here.

[0161] 205. Sub-device 1 sends messages 1-3 to the master device.

[0162] Specifically, after receiving message 1-2 from the master device, the sub-device 1 sends message 1-3 to the master device. Message 1-3 indicates whether the sub-device 1 accepts the working channel allocated to it by the master device. Optionally, message 1-3 may also indicate whether the sub-device 1 accepts the bandwidth of the working channel allocated to it by the master device.

[0163] It should be noted that messages 1-3 have a similar format to message 3 above. For details, please refer to the description of message 3 format in step 104 above. It will not be repeated here.

[0164] 206. The master device sends message 2-2 to the sub-device 2.

[0165] Specifically, after the master device allocates a working channel to the sub-device 2 according to message 2-1, the master device sends message 2-2 to the sub-device 2. Message 2-2 is used to indicate the working channel allocated by the master device to the sub-device 2. Optionally, message 2-2 is used to indicate the bandwidth of the working channel allocated by the master device to the sub-device 2.

[0166] It should be noted that message 2-2 has a similar format to message 2 above. For details, please refer to the introduction of message 2 format in step 103 above. It will not be repeated here.

[0167] 207. Sub-device 2 sends message 2-3 to master device.

[0168] Specifically, after receiving message 2-2 from the master device, the sub-device 2 sends message 2-3 to the master device. Message 2-3 indicates whether the sub-device 2 accepts the working channel allocated to it by the master device. Optionally, message 2-3 may also indicate whether the sub-device 2 accepts the bandwidth of the working channel allocated to it by the master device.

[0169] It should be noted that messages 2-3 have a similar format to message 3 above. For details, please refer to the description of message 3 format in step 104 above. It will not be repeated here.

[0170] The following describes a possible implementation scenario for a master device to allocate a working channel and the bandwidth of the working channel to a slave device, based on the embodiments described above.

[0171] Figure 7 is a schematic diagram of an implementation scenario in which the master device allocates a working channel to the sub-devices according to an embodiment of this application. As shown in Figure 7, the master device is connected to sub-device 1 and sub-device 2 via optical fibers. The master device, sub-device 1, and sub-device 2 can all provide WLAN signals to the STA. The working channel number of the master device is 36 (Ch36 for short), and the bandwidth of the working channel is 80MHz; the working channel number of sub-device 1 is 136 (Ch136 for short), and the bandwidth of the working channel of sub-device 1 is 80MHz; the working channel number of sub-device 2 is 56 (Ch56 for short), and the bandwidth of the working channel of sub-device 2 is 40MHz. Subsequently, sub-device 1 detects interference and requests the master device to allocate a new working channel and bandwidth for it. The master device allocates a working channel number of 149 (Ch149 for short) and a bandwidth of 40MHz to sub-device 1, thus avoiding mutual interference with the master device and sub-device 2. Subsequently, sub-device 2 detected interference and requested the master device to allocate a new working channel and bandwidth for it. The master device allocated working channel number 136 (Ch136 for short) to sub-device 2 and bandwidth of 40MHz to the working channel, thus avoiding mutual interference with the master device and sub-device 1.

[0172] Figure 8 is a schematic diagram of a master device in an embodiment of this application. As shown in Figure 8, the master device includes a processing unit 301 and a transceiver unit 302. Specifically, the transceiver unit 302 is used to perform message sending and receiving operations of the master device in the embodiment shown in Figure 5 or Figure 6. The processing unit 301 is used to perform other operations of the master device besides message sending and receiving in the embodiment shown in Figure 5 or Figure 6. For example, the processing unit 301 can perform the operation of allocating working channels for sub-devices.

[0173] Figure 9 is a schematic diagram of another structure of the main device in an embodiment of this application. As shown in Figure 9, the main device includes a processor 401 and an interface 402, which are interconnected via a line. It should be noted that the interface 402 is used to perform message sending and receiving operations of the main device in the embodiments shown in Figure 5 or Figure 6. The processor 401 is used to perform other operations of the main device in the embodiments shown in Figure 5 or Figure 6 besides message sending and receiving; for example, the processor 401 can perform the operation of allocating working channels for the sub-device. In some possible implementations, the processor 401 includes the aforementioned processing unit 301, and the interface 402 includes the aforementioned transceiver unit 302. Optionally, the main device may also include a memory 403, wherein the memory 403 is used to store program instructions and data.

[0174] Figure 10 is a schematic diagram of a sub-device in an embodiment of this application. As shown in Figure 10, the main device includes a processing unit 501 and a transceiver unit 502. Specifically, the transceiver unit 502 is used to perform message sending and receiving operations of the sub-device in the embodiment shown in Figure 5 or Figure 6. The processing unit 501 is used to perform other operations of the sub-device in the embodiment shown in Figure 5 or Figure 6 besides message sending and receiving. For example, the processing unit 501 can perform the operation of whether to accept the working channel allocated by the main device.

[0175] Figure 11 is a schematic diagram of another structure of the sub-device in an embodiment of this application. As shown in Figure 11, the sub-device includes a processor 601 and an interface 602, which are interconnected via a line. It should be noted that the interface 602 is used to perform message sending and receiving operations of the sub-device in the embodiments shown in Figure 5 or Figure 6. The processor 601 is used to perform other operations of the sub-device in the embodiments shown in Figure 5 or Figure 6 besides message sending and receiving; for example, the processor 601 can perform the operation of whether to accept the working channel allocated by the master device. In some possible implementations, the processor 601 includes the aforementioned processing unit 501, and the interface 602 includes the aforementioned transceiver unit 502. Optionally, the sub-device may also include a memory 603, wherein the memory 603 is used to store program instructions and data.

[0176] This application also provides a chip. The chip integrates circuitry for implementing the functions of the processor 401 or 601 described above, and one or more interfaces. As an example, the chip integrates a memory. As another example, when the chip does not integrate a memory, it can be connected to an external memory via an interface. The chip can perform the method steps of any one or more of the foregoing embodiments. Alternatively, the chip can implement the actions performed by the processing and transmission device in the foregoing embodiments based on program code stored in the memory.

[0177] As an example, the chip in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor, any conventional processor, or a processing circuit that implements a specific function.

[0178] This application also provides a computer-readable storage medium including a program or instructions that, when run on a computer, cause the method performed as described in the above method embodiments to be implemented.

[0179] It should be understood that the processor mentioned in the embodiments of this application can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. The memory can exist independently and be connected to the processor, or the memory can be integrated with the processor.

[0180] As an example, the processor in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor, any conventional processor, or a processing circuit that implements a specific function.

[0181] In embodiments of this application, the memory may be random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and storage medium may reside in an ASIC. Additionally, the ASIC may reside in a network device or a terminal device. Alternatively, the processor and storage medium may exist as discrete components in the network device or terminal device.

[0182] In the above embodiments, it can be implemented entirely or partially by software, hardware, firmware, or any combination thereof.

[0183] When implemented in hardware, the methods provided in this application embodiment may be implemented without reading software code or instructions. For example, they may be implemented using a CPU, DSP, ASIC, FPGA, other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.

[0184] When implemented using software, it can be implemented entirely or partially in the form of a computer program product. A computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, all or part of the processes or functions of the embodiments of this application are performed. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a terminal device, or other programmable device. The computer program or instructions can be stored in or transmitted through a computer-readable storage medium. The computer-readable storage medium can be any available medium that a computer can access, or a data storage device such as a server that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a Digital Versatile Disc (DVD); or it can be a semiconductor medium, such as a solid-state disk (SSD).

[0185] Finally, it should be noted that the above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A channel allocation method applied to fiber-to-the-room (FTTR), characterized in that, include: The master device receives a first message sent by the sub-device, the first message being used to request the master device to allocate a working channel for the sub-device; The master device sends a second message to the sub-device, the second message being used to instruct the master device to allocate a working channel to the sub-device.

2. The method according to claim 1, characterized in that, The first message is further used to request the master device to allocate bandwidth of the working channel to the sub-device, and the second message is further used to indicate the bandwidth of the working channel allocated by the master device to the sub-device.

3. The method according to claim 1 or 2, characterized in that, The working channel assigned to the sub-device by the master device is different from the working channel of at least one other device.

4. The method according to claim 3, characterized in that, The other devices include at least one of the following: the master device that is in the same FTTR network as the sub-device, other sub-devices that are in the same FTTR network as the sub-device, and devices that are in different networks from the sub-device.

5. The method according to any one of claims 1 to 4, characterized in that, The first message is also used to indicate that the request is an urgent request, and the method further includes: The master device allocates a working channel to the sub-device based on the first message.

6. The method according to any one of claims 1 to 4, characterized in that, The first message is also used to indicate that the request is a non-urgent request, and the method further includes: If the preset conditions are met, the master device allocates a working channel to the sub-device according to the first message; The preset conditions include at least one of the following: being in a nighttime environment, or the master device receiving messages from multiple sub-devices requesting the master device to allocate a working channel.

7. The method according to any one of claims 1 to 6, characterized in that, The first message is further used to indicate at least one of the sub-device's preferred operating channel and the bandwidth of the preferred operating channel, and the method further includes: The master device allocates a working channel and / or bandwidth to the sub-device based on at least one of the sub-device's preferred working channel and the bandwidth of the preferred working channel.

8. The method according to any one of claims 1 to 7, characterized in that, The first message includes the following fields: channel number, bandwidth, and priority value.

9. The method according to any one of claims 1 to 8, characterized in that, The first message includes the channel priority report of the sub-device, which includes the following fields: number of radio frequencies, radio frequency identifier, number of operation sets, operation set, number of channels, channel number, and priority value; The method further includes: the master device allocating a working channel to the sub-device based on the sub-device's channel priority report.

10. The method according to any one of claims 1 to 9, characterized in that, After the master device sends the second message to the slave device, the method further includes: The master device receives a third message sent by the sub-device, the third message being used to indicate whether the sub-device accepts the working channel allocated to the sub-device by the master device.

11. A channel allocation method applied to fiber-to-the-room (FTTR), characterized in that, include: The sub-device sends a first message to the master device, the first message being used to request the master device to allocate a working channel for the sub-device; The sub-device receives a second message sent by the master device, the second message being used to indicate the working channel allocated by the master device to the sub-device.

12. The method according to claim 11, characterized in that, The first message is further used to request the master device to allocate bandwidth of the working channel to the sub-device, and the second message is further used to indicate the bandwidth of the working channel allocated by the master device to the sub-device.

13. The method according to claim 11 or 12, characterized in that, The working channel assigned to the sub-device by the master device is different from the working channel of at least one other device.

14. The method according to claim 13, characterized in that, The other devices include at least one of the following: the master device that is in the same FTTR network as the sub-device, other sub-devices that are in the same FTTR network as the sub-device, and devices that are in different networks from the sub-device.

15. The method according to any one of claims 11 to 14, characterized in that, The first message is also used to indicate whether the request is an urgent request.

16. The method according to any one of claims 11 to 15, characterized in that, The first message is also used to indicate at least one of the sub-device's preferred operating channel and the bandwidth of the preferred operating channel.

17. The method according to any one of claims 11 to 16, characterized in that, The first message includes the following fields: channel number, bandwidth, and priority value.

18. The method according to any one of claims 11 to 17, characterized in that, The first message includes the channel priority report of the sub-device, which includes the following fields: number of radio frequencies, radio frequency identifier, number of operation sets, operation set, number of channels, channel number, and priority value.

19. The method according to any one of claims 11 to 17, characterized in that, After the sub-device receives the second message sent by the master device, the method further includes: The sub-device sends a third message to the master device, the third message indicating whether the sub-device accepts the working channel allocated to it by the master device.

20. A main device, characterized in that, The main equipment includes a transceiver unit; The transceiver unit is configured to: receive a first message sent by the sub-device, wherein the first message is used to request the master device to allocate a working channel for the sub-device; A second message is sent to the sub-device, the second message being used to instruct the master device to allocate a working channel to the sub-device.

21. A sub-device, characterized in that, The sub-device includes a transceiver unit; The transceiver unit is used to: send a first message to the master device, the first message being used to request the master device to allocate a working channel for the sub-device; The master device receives a second message, which indicates the working channel allocated by the master device to the sub-device.

22. A main device, characterized in that, The master device includes instructions that, when executed by the master device, cause the master device to perform the method as described in any one of claims 1 to 10.

23. A sub-device, characterized in that, The sub-device includes instructions that, when executed by the sub-device, cause the sub-device to perform the method as described in any one of claims 11 to 19.

24. A communication system, characterized in that, It includes a master device as described in claim 20 or 22 and at least one sub-device as described in claim 21 or 23, wherein the master device communicates with the at least one sub-device.

25. A chip, characterized in that, The chip is used to perform the method as described in any one of claims 1 to 19.

Images