Communication method and device

Abstract

The invention discloses a communication method and device, which can avoid an abnormal behavior of triggering a site, ensure service transmission and improve communication performance. In the method, under the condition that multicast / broadcast data received by each SFU is not from an MFU, the SFU only forwards the multicast / broadcast data to the MFU. The MFU obtains the multicast / broadcast data needing to be sent, the same scheduling information is sent to each SFU to schedule the sending of the multicast / broadcast data, and the plurality of SFUs can send the multicast / broadcast data according to the scheduling of the MFU. In addition, the MFU may also send multicast / broadcast data using a configuration indicated by the scheduling information. Namely, the MFU can uniformly schedule the plurality of SFUs to send the multicast / broadcast data, thereby ensuring that each SFU and the MFU adopt the same configuration to send the multicast / broadcast data, for example, the same content can be sent, the sending time can be aligned, and the same parameter can be adopted, so that the station receives the superposition of the signals sent by each SFU and the MFU, and the signal strength is ensured not to jump. And thus, abnormal behaviors are prevented from being triggered.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to communication methods and apparatus. Background Technology

[0002] In order to achieve seamless roaming under the fiber-to-the-room (FTTR) networking architecture, some vendors have launched networking solutions with basic service set identifier (BSSID).

[0003] In the BSSID-based networking scheme, the master fiber unit (MFU) and all sub-fiber units (SFUs) use the same BSSID and operate on the same channel. Based on this networking method, stations (STAs) can be seamlessly switched to APs with better signals when the service access point (AP) signal is weak.

[0004] However, in this networking configuration, the site will receive downlink multicast / broadcast data from different APs, which may cause signal strength fluctuations on the site side, triggering interruptions to perform abnormal behaviors such as channel probing or autonomous roaming, thus affecting service transmission. Summary of the Invention

[0005] This application provides a communication method and apparatus that can avoid triggering abnormal behavior of the site and will not affect the site's business transmission.

[0006] Firstly, a communication method is provided. This method can be executed by an SFU (Small Optical Network Unit), a component of the SFU (such as its processor, chip, or chip system), or a logic module or software capable of implementing all or part of the SFU's functions. The method includes: receiving first multicast / broadcast data from a Main Optical Network Unit (MFU); receiving scheduling information from the MFU, which is used to schedule the first multicast / broadcast data; and sending second multicast / broadcast data according to the scheduling information, wherein the second multicast / broadcast data is part or all of the data in the first multicast / broadcast data.

[0007] Based on this scheme, the MFU can uniformly schedule the SFU to send multicast / broadcast data, thereby ensuring that the SFU and MFU use the same configuration to send multicast / broadcast data. This allows the station to receive the superposition of signals sent by each SFU and MFU, ensuring that the station can parse the data normally and that the strength of the received signal will not change abruptly. This avoids triggering abnormal behavior of the station, ensures service transmission, and improves communication performance.

[0008] In one possible design: transmission time, transmission data length, virtual access point (VAP) identifier, transmission power, transmission bandwidth, modulation and coding scheme (MCS), or transmission protocol type.

[0009] Based on this possible design, the MFU can schedule the SFU and MFU to align their transmission times, send the same multicast / broadcast data, and use the same transmission parameters. This ensures that the station receives the superposition of signals sent by each SFU and MFU, guaranteeing that the station can parse the data normally and that the strength of the received signal will not change abruptly. This avoids triggering abnormal behavior of the station, ensures service transmission, and improves communication performance.

[0010] In one possible design, the transmission time indicates the time of transmission of the second multicast / broadcast data; the transmission data length indicates the length of the second multicast / broadcast data; or, the VAP is identified as the identifier of the VAP used to transmit the second multicast / broadcast data; or, the transmission power indicates the transmission power of the second multicast / broadcast data; or, the transmission bandwidth indicates the transmission bandwidth of the second multicast / broadcast data; or, the MCS indicates the MCS of the second multicast / broadcast data; or, the transport protocol type indicates the type of protocol used when transmitting the second multicast / broadcast data.

[0011] In one possible design, scheduling information is carried in the Wireless LAN Management and Control Interface (WMCI) message.

[0012] In one possible design, the method further includes: receiving third multicast / broadcast data from a first device, the first device being a device other than the MFU; and sending the third multicast / broadcast data to the MFU, the first multicast / broadcast data including the third multicast / broadcast data.

[0013] Based on this possible design, after receiving multicast / broadcast data that is not from the MFU, the SFU may not immediately forward it to the WLAN port, but instead forward it to the MFU. This allows the MFU to uniformly schedule the transmission of multicast / broadcast data, thereby avoiding signal strength fluctuations in the data received by the site, thus preventing abnormal behavior of the site, ensuring service transmission, and improving communication performance.

[0014] In one possible design, the scheduling information indicates a first transmission time and a second transmission time, the first transmission time being earlier than the second transmission time; sending second multicast / broadcast data according to the scheduling information includes: sending the second multicast / broadcast data at a first power at a third transmission time, the third transmission time being a time after a preset delay of the first transmission time; and sending the second multicast / broadcast data at a second power at the second transmission time, the first power being the power after the second power is reduced by a preset power value.

[0015] In one possible design, the preset duration is 20 microseconds, and / or the preset power value is 6dB.

[0016] Secondly, a communication method is provided. This method can be executed by an MFU (Multi-Functional Optical Network Unit), or by components of the MFU, such as the MFU's processor, chip, or chip system, or by a logic module or software capable of implementing all or part of the MFU's functions. The method includes: sending first multicast / broadcast data to at least one Sub-Optical Network Unit (SFU); sending scheduling information to at least one SFU, the scheduling information being used to schedule the first multicast / broadcast data; and sending second multicast / broadcast data according to the scheduling information, the second multicast / broadcast data being part or all of the multicast / broadcast data. The technical effects of this second aspect are similar to those of the first aspect described above, and will not be repeated here.

[0017] In one possible design, the scheduling information indicates at least one of the following: transmission time, transmission data length, virtual access point (VAP) identifier, transmission power, transmission bandwidth, modulation and coding scheme (MCS), or transmission protocol type.

[0018] In one possible design, the transmission time indicates the time of transmission of the second multicast / broadcast data; the transmission data length indicates the length of the second multicast / broadcast data; or, the VAP is identified as the identifier of the VAP used to transmit the second multicast / broadcast data; or, the transmission power indicates the transmission power of the second multicast / broadcast data; or, the transmission bandwidth indicates the transmission bandwidth of the second multicast / broadcast data; or, the MCS indicates the MCS of the second multicast / broadcast data; or, the transport protocol type indicates the type of protocol used when transmitting the second multicast / broadcast data.

[0019] In one possible design, scheduling information is carried in the Wireless LAN Management and Control Interface (WMCI) message.

[0020] In one possible design, the method further includes: acquiring multicast / broadcast data, wherein the first multicast / broadcast data is part or all of the multicast / broadcast data.

[0021] In one possible design, acquiring multicast / broadcast data includes: receiving third multicast / broadcast data from a first SFU, the multicast / broadcast data including the third multicast / broadcast data.

[0022] In one possible design, acquiring multicast / broadcast data includes: receiving fourth multicast / broadcast data from an optical line terminal (OLT), the multicast / broadcast data including the fourth multicast / broadcast data.

[0023] In one possible design, the scheduling information indicates a first transmission time and a second transmission time, with the first transmission time being earlier than the second transmission time; sending second multicast / broadcast data according to the scheduling information includes: sending the second multicast / broadcast data at a third power at the first transmission time; and sending the second multicast / broadcast data at a fourth power at a fourth transmission time, where the fourth transmission time is the time after a preset delay of the second transmission time, and the fourth power is the power after the third power is reduced by a preset power value.

[0024] In one possible design, the preset duration is 20 microseconds, and / or the preset power value is 6dB.

[0025] The technical effects of any possible design in the second aspect can be referred to the technical effects of the corresponding design in the first aspect above, and will not be repeated here.

[0026] Thirdly, a communication device is provided for implementing various methods. The communication device includes modules, units, or means corresponding to the implementation of the methods, wherein the modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions.

[0027] In some possible designs, the communication device may include a processing module and a transceiver module. The processing module can be used to implement the processing functions in any of the above aspects and any possible implementations thereof. The transceiver module may include a receiving module and a transmitting module, respectively used to implement the receiving function and the transmitting function in any of the above aspects and any possible implementations thereof.

[0028] In some possible designs, the transceiver module can consist of transceiver circuits, transceivers, transceivers, or communication interfaces.

[0029] Fourthly, a communication device is provided, comprising: a processor and a memory; the memory being used to store computer instructions that, when executed by the processor, cause the communication device to perform the method described in any of the above aspects and any possible design thereof.

[0030] Fifthly, a communication device is provided, comprising: a processor and a communication interface; the communication interface being used to communicate with a module outside the communication device; the processor being used to execute computer programs or instructions to cause the communication device to perform the methods described in any of the above aspects and any possible designs thereof.

[0031] A sixth aspect provides a communication device comprising: at least one processor; said processor being configured to execute a computer program or instructions stored in a memory to cause the communication device to perform the methods described in any of the foregoing aspects and any possible designs thereof. The memory may be coupled to the processor, or may be independent of the processor.

[0032] In a seventh aspect, a communication device (e.g., a chip or chip system) is provided, the communication device including a processor for implementing the functions involved in any of the above aspects and any possible designs thereof.

[0033] In some possible designs, the communication device includes a memory for storing necessary program instructions and data.

[0034] In some possible designs, when the device is a chip system, it can be composed of chips or contain chips and other discrete components.

[0035] The communication device described in the third to seventh aspects may be the SFU in the first aspect, or a device contained in the SFU, such as a chip or chip system; or the communication device may be the MFU in the second aspect, or a device contained in the MFU, such as a chip or chip system.

[0036] Eighthly, a communication device is provided, which may be an SFU, or a module or unit (e.g., a chip, a chip system, or a circuit) in the SFU that performs the methods / operations / steps / actions described in the first aspect, or a module or unit that can be used in conjunction with the SFU; or, the communication device may be an MFU, or a module or unit (e.g., a chip, a chip system, or a circuit) in the MFU that performs the methods / operations / steps / actions described in the second aspect, or a module or unit that can be used in conjunction with the MFU.

[0037] It is understandable that when the communication device provided by any of the third to eighth aspects is a chip, the sending action / function of the communication device can be understood as outputting information, and the receiving action / function of the communication device can be understood as inputting information.

[0038] Ninthly, a computer-readable storage medium is provided that stores a computer program or instructions that, when executed on a communication device, enable the communication device to perform the methods described in any of the preceding aspects and any possible designs thereof.

[0039] In a tenth aspect, a computer program product containing instructions is provided, which, when run on a communication device, enables the communication device to perform the methods described in any of the foregoing aspects and any possible design thereof.

[0040] Eleventhly, a communication system is provided, comprising an SFU and an MFU. The SFU is used to implement the method described in the first aspect and any possible design thereof, and the MFU is used to implement the method described in the second aspect and any possible design thereof.

[0041] The technical effects of any of the design methods in aspects three through eleven can be found in the technical effects of different design methods in aspects one or two, and will not be repeated here. Attached Figure Description

[0042] Figure 1 A schematic diagram of the structure of a communication system provided in this application;

[0043] Figure 2 A schematic diagram of another communication system provided in this application;

[0044] Figure 3 A schematic diagram illustrating a signal strength jump at a site in a BSSID networking scenario provided in this application;

[0045] Figure 4 A flowchart illustrating a communication method provided in this application;

[0046] Figure 5 This application provides a schematic diagram of the forwarding of multicast / broadcast data;

[0047] Figure 6 Another schematic diagram of multicast / broadcast data forwarding provided in this application;

[0048] Figure 7 A schematic diagram of a WMCI message format provided in this application;

[0049] Figure 8 A flowchart illustrating another communication method provided in this application;

[0050] Figure 9 A schematic diagram illustrating a scenario of two-stage aligned transmission provided in this application;

[0051] Figure 10 A schematic diagram illustrating the timing relationship between strong and weak signals provided in this application;

[0052] Figure 11 A schematic diagram of the structure of a communication device provided in this application;

[0053] Figure 12 A schematic diagram of another communication device provided in this application;

[0054] Figure 13 A schematic diagram of another communication device provided in this application. Detailed Implementation

[0055] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0056] The technical solutions provided in this application can be applied to fiber-to-the-room (FTTR) system networking scenarios. Furthermore, this application can also be applied to FTTR-based evolution networking scenarios, or networking scenarios similar to FTTR networking scenarios, without limitation.

[0057] like Figure 1 As shown, an FTTR system may include a master fiber unit (MFU) and at least one sub-fiber unit (SFU). The MFU can connect to one or more SFUs via an optical link (such as optical fiber), and the SFU can communicate with a station (STA) via wireless local area network (WLAN) technology. Optionally, the MFU can also communicate with the STA via WLAN technology, and the MFU can also connect to an optical line terminal (OLT) via an optical link.

[0058] As one possible implementation, in this embodiment, the SFU and MFU communicate via the WLAN management and control interface (WMCI) / WMCI management channel. The WMCI management channel is a low-latency channel in the FTTR network that enables WLAN control and other functions between the MFU and SFU. It is used to carry WMCI messages and is carried through an independent FEM port-ID.

[0059] As one possible implementation, in the embodiments of this application, the basic service set identifier (BSSID) of the MFU and the SFU are the same, and / or the service set identifier (SSID) is the same.

[0060] As one possible implementation, MFU can also be called FTTR master device in Chinese and main FTTR unit in English. SFU can also be called FTTR slave device or FTTR sub-device in Chinese and sub FTTR unit in English. MFU can also be called master gateway and SFU can also be called sub-gateway.

[0061] As one possible implementation, in large areas or areas with high network quality requirements, multiple FTTR systems can be centrally deployed, providing a unified wireless network access service. In a centralized FTTR deployment scenario, multiple FTTR systems may be deployed within the same subnet. When these multiple FTTR systems are deployed and put into operation, they are logically configured in the OLT to belong to the same subnet, and the configuration can be manual or automatic. For example, ... Figure 2 As shown in (a), FTTR system 1 and FTTR system 2 are deployed in the same subnet and are managed by OLT1. FTTR system 1 includes MFU1, SFU1.1 and SFU1.2. MFU1 is connected to SFU1.1 and SFU1.2 via optical fibers and is connected to OLT1. FTTR system 2 includes MFU2, SFU2.1 and SFU2.2. MFU2 is connected to SFU2.1 and SFU2.2 via optical fibers and is connected to OLT1.

[0062] As one possible implementation, the embodiments of this application can be applied to roaming scenarios in FTTR-related networks.

[0063] like Figure 2 As shown in (b), during a site's movement within an FTTR network, the channel quality with its currently associated SFU deteriorates, necessitating roaming to an SFU with better channel quality to ensure service continuity. Simultaneously, during roaming, the terminal needs to re-establish a connection on the new SFU, leading to service interruption. To ensure the timeliness and continuity of roaming, this application employs a WMCI-based cooperative roaming control scheme.

[0064] The WMCI-based collaborative roaming solution mainly includes four aspects of processing: roaming configuration information synchronization, network information synchronization, terminal online processing, and terminal roaming processing.

[0065] Roaming network configuration is triggered when SFU goes online, WMCI roaming is enabled or disabled, and network parameters are configured.

[0066] When an SFU is launched and initialized, the MFU will check whether the network's cooperative roaming function is enabled. If the network's cooperative roaming function is enabled, the MFU will check whether the SFU meets the enabling conditions based on the SFU's roaming capability information. If it does, the roaming configuration of the newly launched SFU will be enabled. If the SFU does not meet the enabling conditions, the roaming configuration will not be enabled. If the network's cooperative roaming function is not enabled, no cooperative roaming configuration will be performed.

[0067] After network deployment is complete, the cooperative roaming function can be enabled or disabled. When enabling cooperative roaming, the MFU should first determine if the enabling conditions are met. If they are met, a roaming configuration command should be issued to all SFUs. If the conditions are not met, no roaming configuration should be performed. When disabling cooperative roaming, the MFU should restore the network's normal configuration and disable the roaming feature.

[0068] The process of enabling / disabling the collaborative roaming feature includes the following steps:

[0069] (1) The MFU sends roaming configuration information to the SFU via roaming configuration messages;

[0070] (2) After receiving the configuration message, the SFU completes the relevant parameter configuration and sends back a roaming configuration confirmation message;

[0071] (3) After receiving the roaming configuration confirmation message from the SFU, the MFU sends a roaming enable or disable message to the SFU.

[0072] (4) After the SFU is turned on or off, a confirmation message is sent to the MFU to confirm whether the roaming is turned on or off.

[0073] After cooperative roaming is enabled, periodic synchronization of network information is required. This includes the synchronized transmission of beacon frames. There are two main synchronization methods: one is that the MFU controls the synchronization time and sends network synchronization information to the SFUs within the network at the specified synchronization time; the other is that all SFUs report synchronization information, and then the MFU summarizes the information and sends out the network information for synchronization.

[0074] When a site goes online, in order to enable roaming functionality, the associated information and key information need to be synchronized across the entire network. When a site goes offline, the associated SFU sends the terminal offline event to the MFU. After receiving the offline event, the MFU sends an instruction to all SFUs and MFUs across the network to delete the terminal information. After receiving the terminal deletion instruction from the MFU, the SFU deletes the terminal information and reports a successful deletion instruction to the MFU. The MFU then deletes the terminal-related information.

[0075] As one possible implementation, the site in this application embodiment can be a device that supports relevant standards of the Institute of Electrical and Electronics Engineers (IEEE), and can achieve communication connection with the SFU based on WLAN technology, such as sending physical frames to the SFU based on radio frequency analog signals (or wireless signals, wireless radio frequency analog signals, wireless analog signals, etc.).

[0076] The relevant IEEE standards can include: 802.11a / b / g, 802.11n, 802.11ac, 802.11ax, 802.11be, 802.11bn (Ultra High Reliability, UHR) / Wi-Fi 8, 802.11ad, 802.11ay, 802.11bf (sensing), Ultra Wide Bandwidth (UWB), and 802.15, etc., without restriction. Regarding bandwidth configuration, channel bundling was introduced starting with 802.11n, allowing multiple 20MHz channels to be bundled together to achieve greater bandwidth and higher transmission rates. Starting with 802.11ac, a maximum bandwidth of 160MHz can be provided. The 802.11ax standard supports the following bandwidth configurations: 20MHz, 40MHz, 80MHz, 160MHz, and 80+80MHz. The 802.11be standard also supports a 320MHz bandwidth configuration.

[0077] For example, a site can be a wireless communication chip, a wireless sensor (such as a temperature and humidity sensor), a wireless communication terminal, a communication server, a router, a switch, a bridge, a computer, etc. For instance, a site can be a mobile phone supporting Wi-Fi communication, a tablet computer supporting Wi-Fi communication, a set-top box supporting Wi-Fi communication, a smart home appliance supporting Wi-Fi communication, a smart wearable device supporting Wi-Fi communication, an in-vehicle communication device supporting Wi-Fi communication, a computer supporting Wi-Fi communication, a camera supporting Wi-Fi communication, a robot supporting Wi-Fi communication, office equipment supporting Wi-Fi communication, etc., without limitation.

[0078] As one possible implementation, the SFU in this application embodiment can be a device supporting relevant IEEE standards. It can achieve communication connection with the site based on WLAN technology and also achieve communication connection with the MFU through an optical link. That is, when the SFU and MFU communicate, digital signals can be converted into optical signals for transmission. This optical signal can be understood as a signal transmission form of digital signals between the SFU and MFU. The transmission of optical signals converted from digital signals between the SFU and MFU can also be understood as digital signal transmission between the SFU and MFU through optical signals. For example, the SFU can send optical signals converted from uplink digital signals to the MFU through the uplink transmission channel of the optical link, and receive optical signals converted from downlink digital signals sent by the MFU through the downlink transmission channel of the optical link.

[0079] The SFU (System-Level Unit) may include one or more antennas. The SFU can convert the digital signals from the antennas into optical signals and transmit them to the MFU (Medium-Level Unit) via the uplink transmission channel of the optical link. Alternatively, the SFU can receive optical signals converted from downlink digital signals transmitted by the MFU via the downlink transmission channel of the optical link, using one or more antennas. Taking uplink transmission as an example, the SFU can collect the wireless signals transmitted by the site according to the uplink bandwidth indicated by the MFU, obtain digital signals, and transmit the optical signals converted from the uplink digital signals to the MFU via the uplink transmission channel of the optical link, according to the uplink bandwidth indicated by the MFU.

[0080] As one possible implementation, the MFU in this embodiment can be a device supporting relevant IEEE standards, and can establish a communication connection with the SFU via an optical link. For example, the MFU can receive optical signals converted from uplink digital signals sent by the SFU through the uplink transmission channel of the optical link, and send optical signals converted from downlink digital signals to the SFU through the downlink transmission channel of the optical link. The MFU can also indicate the uplink bandwidth to the SFU, instructing the SFU to perform uplink transmission according to the uplink bandwidth. The MFU can also determine the baseband signal based on the acquired uplink digital signal, perform physical layer demodulation on the baseband signal, and obtain the physical frame sent by the station.

[0081] For example, an MFU can be a terminal device with a Wi-Fi chip, network device, communication server, router, switch, bridge, computer, etc. An MFU can also serve as an access point for mobile users to access a wired network, primarily deployed in homes, buildings, and campuses, with a typical coverage radius of tens to hundreds of meters. Of course, it can also be deployed outdoors. An MFU acts as a bridge connecting wired and wireless networks, its main function being to connect various wireless network clients together and then connect the wireless network to the Ethernet.

[0082] In FTTR networking architecture, to achieve seamless roaming, some vendors have introduced networking schemes using the same Basic Service Set Identifier (BSSID). In this BSSID-based scheme, the MFU and all SFUs use the same BSSID and operate on the same channel. Based on this networking method, stations (STAs) can be seamlessly switched to APs with better signals even when the service access point (AP) signal is weak. The AP can include MFUs or SFUs, etc.

[0083] However, in a network configuration with the same BSSID, sites cannot distinguish between MFUs and individual SFUs. Sites will receive downlink multicast / broadcast data from different APs, causing fluctuations in the received signal strength indicator (RSSI). This will result in signal strength jumps at the site side. For example, as shown... Figure 3 As shown, taking the APs in the same BSSID network architecture, including MFU, SFU1, and SFU2, as an example, the signal strength of the downlink multicast / broadcast data sent by MFU, SFU1, and SFU2 at the site side is -30dB, -70dB, and -90dB, respectively, that is, the signal strength jumps.

[0084] For a site, a sudden change in signal strength may trigger service interruption, abnormal behavior such as channel probing or autonomous roaming, thereby affecting service transmission.

[0085] Based on this, this application provides a communication method in which, when the multicast / broadcast data received by each SFU does not originate from the MFU, the SFUs all forward the multicast / broadcast data only to the MFU. The MFU obtains the multicast / broadcast data to be sent and sends the same scheduling information to each SFU to schedule the transmission of the multicast / broadcast data. Multiple SFUs can send multicast / broadcast data according to the scheduling of the MFU. Alternatively, the MFU can also send multicast / broadcast data using the configuration indicated by the scheduling information.

[0086] Through the above scheme, the MFU can uniformly schedule multiple SFUs to send multicast / broadcast data, thereby ensuring that each SFU and MFU uses the same configuration to send multicast / broadcast data. For example, each SFU and MFU can send the same content and align the sending time, so that the station receives the superposition of the signals sent by each SFU and MFU, ensuring that the signal strength received by the station will not change abruptly, thereby avoiding triggering abnormal behavior of the station, ensuring service transmission, and improving communication performance.

[0087] The following is in conjunction with the above. Figure 1 or Figure 2 The communication system shown takes the interaction between SFU and MFU as an example to describe the communication method provided in the embodiments of this application.

[0088] It should be noted that in the following embodiments of this application, the message names between SFU and MFU, the names of each parameter, or the names of each piece of information are just examples. Other names may also be used in other embodiments, and the method provided in this application does not specifically limit them.

[0089] It is understood that in the embodiments of this application, the SFU and MFU can perform some or all of the steps in the embodiments of this application. These steps or operations are merely examples, and the embodiments of this application can also perform other operations or variations of various operations. Furthermore, the steps can be performed in different orders as presented in the embodiments of this application, and it is not necessary to perform all the operations in the embodiments of this application.

[0090] It is understood that this application uses SFU and MFU as examples of the execution entities in the interactive illustration, but this application does not limit the execution entities in the interactive illustration. For example, the method executed by SFU in this application can also be executed by a module applied to the SFU (e.g., a chip, chip system, or processor), or by a logic node, logic module, or software that can implement all or part of the SFU's functions; similarly, the method executed by MFU in this application can also be executed by a module applied to the MFU (e.g., a chip, chip system, or processor), or by a logic node, logic module, or software that can implement all or part of the MFU's functions.

[0091] The communication method provided in the embodiments of this application will be described below. For example... Figure 4 As shown, the communication method may include the following steps:

[0092] S400 and MFU acquire multicast / broadcast data.

[0093] In one possible implementation, the MFU can receive multicast / broadcast data from either the SFU side or the OLT side.

[0094] As one possible implementation, in this embodiment of the application, for the SFU, if the multicast / broadcast data received by the SFU is not from the MFU, then the SFU only forwards the multicast / broadcast data to the MFU.

[0095] For example, the multicast / broadcast data received by the SFU can originate from the local area network (LAN) side or from the passive optical network (PON) side, such as from other SFUs. For multicast / broadcast data from the LAN side or other SFUs, the SFU will not forward it directly to the air interface (also known as the WLAN port or Wi-Fi port), but will forward it to the MFU.

[0096] For example, such as Figure 5 As shown, taking a network architecture with the same BSSID, including an MFU, a first SFU, and a second SFU, as an example, if the first SFU receives multicast / broadcast data 'a' from a first device (which is not an MFU), then the first SFU forwards the multicast / broadcast data 'a' to the MFU. Here, multicast / broadcast data 'a' can also be referred to as third multicast / broadcast data.

[0097] As another possible implementation, exemplified by, Figure 6 As shown, the multicast / broadcast data acquired by the MFU can also include multicast / broadcast packets from the MFU side. For example, the MFU receives multicast / broadcast data b from the OLT. Multicast / broadcast data b can also be referred to as fourth multicast / broadcast data.

[0098] S401, the MFU sends the first multicast / broadcast data to at least one SFU. Correspondingly, at least one SFU receives the first multicast / broadcast data from the MFU.

[0099] Exemplary examples of this application and Figure 4 This example illustrates at least one SFU, including a first SFU and a second SFU. In practical applications, the at least one SFU may refer to more or fewer SFUs than two SFUs. The implementation of the other SFUs in the at least one SFU can be found in the relevant implementations of the first and second SFUs in the embodiments of this application, and will not be described in detail here.

[0100] The first multicast / broadcast data is part or all of the multicast / broadcast data acquired by the MFU in step S400. For example, based on... Figure 5 and Figure 6 The example shown, taking the multicast / broadcast data acquired by the MFU in step S400 as including multicast / broadcast data a and multicast / broadcast data b (collectively referred to as multicast / broadcast data c), is that the first multicast / broadcast data is part or all of the data in multicast / broadcast data c.

[0101] For example, based on Figure 5 and Figure 6The example shown uses the first multicast / broadcast data as all the data in multicast / broadcast data c, i.e., the first multicast / broadcast data and multicast / broadcast data c are the same. Figure 5 As shown, after receiving multicast / broadcast data 'a' from the first SFU, the MFU forwards the multicast / broadcast data 'a' to both the first and second SFUs. Furthermore, the MFU, the first SFU, and the second SFU can also store the multicast / broadcast data 'a', for example, in a Wi-Fi cache.

[0102] And, as Figure 6 As shown, after receiving multicast / broadcast data b, the MFU forwards the multicast / broadcast data b to the first SFU and the second SFU. Furthermore, the MFU, the first SFU, and the second SFU can also store the multicast / broadcast data b, for example, in a Wi-Fi cache.

[0103] S402, the MFU sends scheduling information to at least one SFU. Correspondingly, at least one SFU receives the scheduling information from the MFU.

[0104] This scheduling information is used to schedule the first multicast / broadcast data. It is understood that the MFU sends the same scheduling information to different SFUs within the at least one SFU.

[0105] In one possible implementation, the scheduling information indicates at least one of the following: transmission time, transmission data length, virtual access point (VAP) identifier, transmission power, transmission bandwidth, modulation and coding scheme (MCS), or transmission protocol type.

[0106] As one possible implementation, the transmission time indicates the time when multicast / broadcast data is sent. For example, the transmission time can be an absolute time, such as Coordinated Universal Time (UTC); or it can be a relative time, such as the time represented by the WLAN frame number, etc., without limitation.

[0107] For example, the transmission time can be carried by 4 bytes. Of course, the number of bytes carrying the transmission time can also be other values, and this application does not specifically limit this.

[0108] As one possible implementation, the transmission data length indicates the length of the multicast / broadcast data (or multicast / broadcast data to be sent) scheduled for this time.

[0109] For example, the length of the transmitted data can be less than or equal to the length of the first multicast / broadcast data. If the length of the transmitted data is less than the length of the first multicast / broadcast data, it indicates that a portion of the data in the first multicast / broadcast data is being scheduled in this operation; if the length of the transmitted data is equal to the length of the first multicast / broadcast data, it indicates that all the data in the first multicast / broadcast data is being scheduled in this operation.

[0110] For example, the length of transmitted data can be carried by 2 bytes. Of course, the number of bytes carrying the length of transmitted data can also be other values, and this application does not specifically limit this.

[0111] As one possible implementation, the VAP identifier is the identifier of the VAP used to send multicast / broadcast data, that is, it indicates which VAP ID is used to send multicast / broadcast data.

[0112] As one possible implementation, the transmission power indicator is the power used to send multicast / broadcast data, or in other words, the power used to send multicast / broadcast data.

[0113] As one possible implementation, the transmission bandwidth indicates the bandwidth for sending multicast / broadcast data, or in other words, the bandwidth for transmitting multicast / broadcast data. For example, the transmission bandwidth can be 20M, 40M, 80M, etc., without limitation.

[0114] As one possible implementation, the MCS indicates the MCS used for multicast / broadcast data, for example, the MCS used when sending multicast / broadcast data.

[0115] As one possible implementation, the transport protocol type indicates the type of protocol used to send multicast / broadcast data. For example, the transport protocol type can also be referred to as the transport mode.

[0116] For example, the VAP identifier, transmission power, transmission bandwidth, modulation and coding scheme (MCS), or transmission protocol type can be carried by 1 byte. Of course, the number of bytes carrying this information can also be other values, and this application does not specifically limit this.

[0117] As described above, for example, the fields or information included in the scheduling information may include at least one of the items in Table 1.

[0118] Table 1

[0119]

[0120] In one possible implementation, the scheduling information is carried in a WLAN management and control interface (WMCI) message. For example, the format of a WMCI message is shown in Table 2.1.

[0121] Table 2.1

[0122]

[0123] As one possible implementation, the Message Type ID is an 8-bit field used to indicate the type of message and define the semantics of the message content. When the MFU receives an uplink message with an unsupported message type ID, it should ignore the message. Similarly, when the SFU receives a message with a reserved or unsupported message type ID, it should ignore the message.

[0124] As one possible implementation, SeqNo is an 8-bit field containing a sequence number counter to ensure the robustness of the WMCI message channel. In the downlink direction, the SeqNo field is filled with the corresponding MFU sequence number counter value. The MFU maintains a separate sequence number counter for each SFU unicast and broadcast WMCI message stream. Each sequence number counter rolls from 255 to 1. A value of 0 is not used in the downlink direction. In the uplink direction, when an uplink WMCI message is a response to a downlink message, the value of the SeqNo field is equal to the value of the SeqNo field in the downlink message. If the WMCI message is initiated by the SFU, then SeqNo = 0 is used.

[0125] As one possible implementation, the message length and processing requirements are a 2-byte field consisting of three fields: message priority, operation type, and message content length.

[0126] X (the most significant bit of the third byte): Indicates the priority of processing this message. When X=1, it indicates that the message has a high priority; when X=0, it indicates that the message has a low priority.

[0127] C: Used to indicate the operation type of the current message.

[0128] In the downlink direction, when C=1, it indicates that the operation type of the message is a parameter request type, requesting the SFU to send the output indicated by the Message type ID field; when C=0, it indicates that the message is a parameter configuration type message, and the parameter type configured in the message is indicated by the Messagetype ID field.

[0129] In the uplink direction, when C=1, the operation type of the message is a scheduling request, requesting the MFU to send the scheduling configuration indicated by the Message type ID field; when C=0, the message is a parameter reporting message or an alarm message, and the parameter, alarm type or response reported by the message is indicated by the Message type ID field.

[0130] LL LLLL LLLL: This field indicates the length of the message content. The value range is 0 to 1023.

[0131] As one possible implementation, the format of the message content field is related to the specific message, and the message content includes two parts: the message mask and the parameter content.

[0132] The message mask consists of a 16-bit mask, as shown in Table 2.2. For example, when a bit in the message mask is set to a specific value (such as 1 or 0), it indicates that the content parameters carry (or contain) the parameter corresponding to that mask; when set to a non-specific value, it indicates that the content parameters do not carry (or do not contain) the parameter corresponding to that mask.

[0133] Table 2.2

[0134]

[0135] Each message type can carry a maximum of 16 parameters. The message content should be filled in the order indicated by the parameter mask. For downlink request messages, the parameter mask represents the parameters the MFU wants to obtain. For uplink messages, the parameter mask represents the parameters being reported and replied to.

[0136] As one possible implementation, the integrity check field can also be replaced with a message check field to verify whether the message has been corrupted during transmission. For example, the value of this field is generated by a cyclic redundancy check (CRC) algorithm.

[0137] As one possible implementation, WMCI messages are encapsulated in FEM frames for managing and controlling the WLAN functions of the SFU. The FTTR transceiver can identify the destination of the WMCI message using the FEM port ID in the FEM frame.

[0138] As one possible implementation, scheduling information can be carried in the message content field of a WMCI message. For example, scheduling information can be carried in the content parameter field of the message content of a WMCI message. For instance, the parameter numbers of the parameters in the content field within the scheduling information can be shown in Table 3.

[0139] Table 3

[0140]

[0141] In other words, a possible format for a WMCI message or scheduling instruction message could be as follows: Figure 7 As shown. Figure 7 For explanations of each field, please refer to the descriptions of the relevant information / parameters mentioned above, which will not be repeated here.

[0142] It should be noted that the parameter order in the content of the scheduling information shown in Table 3 above is only an illustrative example. In actual applications, this order may not be used. For example, the VAP ID can be the first parameter in the content, i.e., parameter number 1; the transmission time parameter number can be 2; the transmission data length parameter number can be 2; and the parameter numbers of other parameters can remain unchanged. Of course, other orders are also possible, and this application does not impose specific limitations on them.

[0143] S403, at least one SFU, and MFU send second multicast / broadcast data according to the scheduling information.

[0144] The second multicast / broadcast data is part or all of the data in the first multicast / broadcast data. For example, the transmission data length in the scheduling information indicates the length of the second multicast / broadcast data.

[0145] In addition, the transmission time in the scheduling information indicates the transmission time of the second multicast / broadcast data, the VAP identifier indicates the VAP identifier used to transmit the second multicast / broadcast data, the transmission power indicates the transmission power of the second multicast / broadcast data, the transmission bandwidth indicates the transmission bandwidth of the second multicast / broadcast data, the MCS indicates the MCS of the second multicast / broadcast data, and the transmission protocol type indicates the type of protocol used when transmitting the second multicast / broadcast data.

[0146] For example, at least one SFU and MFU transmitting second multicast / broadcast data according to scheduling information may include at least one of the following: determining the second multicast / broadcast data to be transmitted based on the transmission data length, and transmitting the second multicast / broadcast data at the transmission time indicated by the scheduling information. The second multicast / broadcast data is modulated and encoded using the MCS indicated by the scheduling information, and transmitted using the protocol indicated by the transmission protocol type indicated by the scheduling information, and using the AVP ID, transmission power, or transmission bandwidth indicated by the scheduling information, etc.

[0147] Understandably, at least one SFU and MFU send second multicast / broadcast data on the air interface (or WLAN interface or Wi-Fi interface) according to scheduling information, and the site receives the second multicast / broadcast data.

[0148] In the above-mentioned scheme of this application, the multicast / broadcast data packets received by the SFU from the LAN side and PON side are first forwarded to the MFU. The MFU then performs unified scheduling on the multicast / broadcast data packets forwarded by the SFU and / or the multicast / broadcast data packets received by the MFU from the OLT. This ensures that each SFU and MFU sends multicast / broadcast data with the same configuration. For example, each SFU and MFU can send the same content, align the sending time, and use the same sending parameters. This ensures that the site receives the superposition of signals sent by each SFU and MFU, guaranteeing that the site can normally receive and parse multicast / broadcast signals, and that the strength of the received signal will not change abruptly. This avoids triggering abnormal behavior of the site, ensures service transmission, and improves communication performance.

[0149] In the above scheme, the MFU can send the multicast / broadcast data it has acquired to at least one OFU in the following two ways:

[0150] Method 1: After receiving multicast / broadcast data forwarded by the SFU or from the OLT, the MFU sends the multicast / broadcast data to at least one SFU. Furthermore, the MFU and at least one SFU store the multicast / broadcast data, awaiting scheduling by the MFU.

[0151] For example, such as Figure 5 or Figure 6 As shown, after receiving multicast / broadcast data 'a' from the first SFU, the MFU forwards the multicast / broadcast data 'a' to both the first and second SFUs. After receiving multicast / broadcast data 'b', the MFU forwards the multicast / broadcast data 'b' to both the first and second SFUs. Furthermore, the MFU, the first SFU, and the second SFU can also store the multicast / broadcast data 'a' and multicast / broadcast data 'b' (collectively referred to as multicast / broadcast data 'c'), for example, in a Wi-Fi cache.

[0152] Subsequently, the MFU can send scheduling information to schedule multicast / broadcast data c. For example, if the scheduling information carries the data length to indicate the data length to be scheduled, then the MFU, the first SFU, and the second SFU will read the corresponding length of data from the multicast / broadcast data c according to the data length to be transmitted and send it.

[0153] In other words, in Method 1, before the MFU performs scheduling, at least one SFU can obtain all multicast / broadcast data to be scheduled by the MFU.

[0154] Method 2: After receiving multicast / broadcast data forwarded by the SFU or from the OLT, the MFU buffers the multicast / broadcast data. It then sends the multicast / broadcast data scheduled for transmission to at least one SFU.

[0155] For example, such as Figure 8 As shown, after receiving multicast / broadcast data d from the first SFU and multicast / broadcast data e from the OLT, the MFU buffers multicast / broadcast data d and multicast / broadcast data e (collectively referred to as multicast / broadcast data f). Subsequently, the MFU sends scheduling information and the multicast / broadcast data to be transmitted in this scheduling to at least one SFU. The multicast / broadcast data to be transmitted in this scheduling can be part or all of the data in multicast / broadcast data f.

[0156] Optionally, in this scenario, since the MFU sends the multicast / broadcast data that needs to be transmitted in this scheduling to at least one SFU, the scheduling information may not include the transmission data length. This is because the SFU does not need to determine the multicast / broadcast data to be transmitted based on the transmission data length. That is, in this second method, the SFU sends all the multicast / broadcast data sent by the MFU to the SFU. In other words, under this second method, the second multicast / broadcast data can be considered to be the same as the first multicast / broadcast data, or the second multicast / broadcast data is all the data in the first multicast / broadcast data.

[0157] Optionally, in this second method, the scheduling information and the first multicast / broadcast data can be carried in the same message, or they can be carried in different messages. This application does not make any specific restrictions on this.

[0158] In other words, in method two, the MFU does not need to send all the multicast / broadcast data it has acquired to the SFU in advance. Instead, it can send the multicast / broadcast data that needs to be transmitted in this scheduling session.

[0159] Based on this second method, since it is not necessary to send all the multicast / broadcast data obtained by the MFU to the SFU, the SFU does not need to use a large cache to store the multicast / broadcast data, which can reduce the storage space occupied by the SFU.

[0160] The above scheme is illustrated using the example of complete time synchronization between the MFU and each SFU. Furthermore, this application also provides a communication method applicable to scenarios where the time synchronization accuracy between the MFU and SFU is low, and data cannot be transmitted in perfect alignment.

[0161] This method is the same as the above Figure 4The method shown is similar: after receiving multicast / broadcast data that is not from the MFU, the SFU forwards the multicast / broadcast data to the MFU. The MFU can acquire multicast / broadcast data, including data forwarded by the SFU and / or data from the OLT, and send scheduling information to the SFU to schedule the multicast / broadcast data. The difference is that the MFU or SFU may not send multicast / broadcast data exactly according to the transmission time indicated by the scheduling information; for a certain multicast / broadcast data, it can be transmitted twice. In the first transmission, the SFU delays transmission and reduces its transmission power, while the MFU transmits normally; in the second transmission, the MFU delays transmission and reduces its transmission power, while the SFU transmits normally.

[0162] As one possible implementation, taking the scheduling of second multicast / broadcast data transmission as an example, the MFU can indicate a first transmission time and a second transmission time through scheduling information, wherein the first transmission time is earlier than the second transmission time.

[0163] In the first transmission, the MFU transmits the second multicast / broadcast data at a third power during the first transmission time; the SFU transmits the second multicast / broadcast data at a first power during the third transmission time, which is the time after a preset delay from the first transmission time. The third transmission time can be earlier than the second transmission time.

[0164] In the second transmission, the SFU transmits the second multicast / broadcast data at the second power during the second transmission time; the MFU transmits the second multicast / broadcast data at the fourth power during the fourth transmission time, which is the time after a preset delay of the second transmission time.

[0165] The first power is the power obtained by reducing the second power by a preset power value. The fourth power is the power obtained by reducing the third power by a preset power value. The second power and the third power can be the same or different. The second power can be indicated by the MFU to the SFU.

[0166] For example, the preset duration can be 20 microseconds, and the preset power value can be 6dB. The preset duration and / or preset power value can be indicated by the MFU to the SFU or pre-configured, or can be predefined by the protocol; this application does not specifically limit this.

[0167] For example, taking multicast / broadcast data including data 1 and data 2 as an example, such as Figure 9As shown, during the first transmission of data 1, the MFU transmits at normal power, while the SFU delays transmission by 20 microseconds and reduces its transmission power. During the second transmission of data 1, the SFU transmits at normal power, while the MFU delays transmission by 20 microseconds and reduces its transmission power. Similarly, during the first transmission of data 2, the MFU transmits at normal power, while the SFU delays transmission by 20 microseconds and reduces its transmission power; during the second transmission of data 2, the SFU transmits at normal power, while the MFU delays transmission by 20 microseconds and reduces its transmission power.

[0168] Optionally, for two transmissions of the same multicast / broadcast data, the MFU can send one scheduling message to schedule both transmissions. In this case, the first transmission time and the second transmission time can be carried in the same scheduling message. Alternatively, it can send two scheduling messages to schedule the two transmissions separately. In this case, the first transmission time can be carried in the scheduling message of the first transmission, and the second transmission time can be carried in the scheduling message of the second transmission.

[0169] When the data sent by the two APs are not perfectly aligned, such as Figure 10 As shown in (a), if the weak signal is sent first, the station cannot resolve it correctly; as Figure 10 As shown in (b), if the strong signal is transmitted first, the station can correctly parse it. Based on the above method of alternating reduction of transmission power by the MFU and SFU, it can be guaranteed that the station receives data with a strong signal first once, thus correctly parsing the data; if the weak signal comes first, it cannot be parsed.

[0170] For example, based on Figure 9 In the example shown, when the station is connected to the MFU, the third power and the second power can be understood as the normal or initial power of the MFU and SFU, respectively, with the third power typically being tens of dB higher than the second power. In the first transmission, the first power is lower than the second power; therefore, the third power is still greater than the first power, resulting in the station receiving data with higher signal strength first (i.e., data 1 sent by the MFU). In the second transmission, although the MFU reduces its transmission power, it does so based on the third power, which is tens of dB higher than the second power. Therefore, even if the third power is reduced by a preset value (e.g., 6 dB), the reduced fourth power may still be greater than the second power, resulting in the station receiving data with lower signal strength first (i.e., data 1 sent by the SFU). In other words, the station is guaranteed to receive one strong signal-first data transmission and one weak signal-first data transmission.

[0171] Furthermore, when a site is connected to an SFU, because the site is close to the SFU, in the first transmission, the site may receive data with a weaker signal strength sent by the MFU first, i.e., the weaker signal comes first. In the second transmission, the site may receive data with a stronger signal strength sent by the SFU first, i.e., the stronger signal comes first.

[0172] In other words, the above scheme can ensure that the site always receives data with a strong signal, so as to prevent the signal strength from fluctuating, thereby avoiding triggering abnormal behavior of the site, ensuring service transmission, and improving communication performance.

[0173] It should be noted that the various embodiments of this application can be implemented independently or in combination, without limitation. Unless otherwise specified or in conflict, the terminology and / or descriptions between the different embodiments provided in this application are consistent and can be referenced mutually. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0174] The method provided in this application has been described above. In addition, this application also provides a communication device for implementing the functions described in the above method embodiments.

[0175] It is understood that, in order to achieve the aforementioned functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0176] This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0177] Figure 11A schematic diagram of a communication device 110 is shown. The communication device 110 includes a processing module 1101 and a transceiver module 1102. The communication device 110 can be used to implement the functions of an SFU or MFU. The communication device 110 can be an SFU or MFU, or it can be a chip or other combined device or component with the aforementioned SFU or MFU functions applied within an SFU or MFU.

[0178] In some embodiments, the communication device 110 may further include a storage module. Figure 11 (Not shown in the image) is used to store program instructions and data.

[0179] In some embodiments, the transceiver module 1102, also referred to as a transceiver unit, is used to implement sending and / or receiving functions. The transceiver module 1102 may consist of a transceiver circuit, a transceiver unit, a transceiver interface, a communication interface, and an input / output interface.

[0180] In some embodiments, the transceiver module 1102 may include a receiving module and a sending module, respectively used to execute the receiving and sending steps performed by the SFU or MFU network element in the above method embodiments, and / or other processes used to support the technology described herein; the processing module 1101 may be used to execute the processing steps performed by the SFU or MFU in the above method embodiments, and / or other processes used to support the technology described herein.

[0181] When the communication device 110 is used to implement the SFU function:

[0182] The transceiver module 1102 is used to receive first multicast / broadcast data from the main optical network unit (MFU); the transceiver module 1102 is also used to receive scheduling information from the MFU, the scheduling information being used to schedule the first multicast / broadcast data; the transceiver module 1102 is also used to send second multicast / broadcast data according to the scheduling information, the second multicast / broadcast data being part or all of the data in the first multicast / broadcast data.

[0183] Optionally, the transceiver module 1102 is further configured to receive third multicast / broadcast data from a first device, wherein the first device is a device other than the MFU; the transceiver module 1102 is further configured to send third multicast / broadcast data to the MFU, wherein the first multicast / broadcast data includes the third multicast / broadcast data.

[0184] Optionally, the scheduling information indicates a first transmission time and a second transmission time, wherein the first transmission time is earlier than the second transmission time; the transceiver module 1102 is further configured to send second multicast / broadcast data according to the scheduling information, including: the transceiver module 1102 is further configured to send the second multicast / broadcast data at a first power at a third transmission time, wherein the third transmission time is the time after a preset delay of the first transmission time; and the transceiver module 1102 is further configured to send the second multicast / broadcast data at a second power at a second transmission time, wherein the first power is the power after the second power is reduced by a preset power value.

[0185] When the communication device 110 is used to implement the function of MFU:

[0186] The transceiver module 1102 is used to send first multicast / broadcast data to at least one sub-optical network unit (SFU); the transceiver module 1102 is also used to send scheduling information to at least one SFU, the scheduling information being used to schedule the first multicast / broadcast data; the transceiver module 1102 is also used to send second multicast / broadcast data according to the scheduling information, the second multicast / broadcast data being part or all of the multicast / broadcast data.

[0187] Optionally, the transceiver module 1102 is also used to acquire multicast / broadcast data, wherein the first multicast / broadcast data is part or all of the multicast / broadcast data.

[0188] Optionally, the transceiver module 1102 is also used to acquire multicast / broadcast data, including: the transceiver module 1102 is also used to receive third multicast / broadcast data from the first SFU, the multicast / broadcast data including third multicast / broadcast data.

[0189] Optionally, the transceiver module 1102 is also used to acquire multicast / broadcast data, including: receiving fourth multicast / broadcast data from the optical line terminal (OLT), wherein the multicast / broadcast data includes the fourth multicast / broadcast data.

[0190] Optionally, the scheduling information indicates a first transmission time and a second transmission time, wherein the first transmission time is earlier than the second transmission time; the transceiver module 1102 is further configured to send second multicast / broadcast data according to the scheduling information, including: the transceiver module 1102 is further configured to send the second multicast / broadcast data at a third power at the first transmission time; the transceiver module 1102 is further configured to send the second multicast / broadcast data at a fourth power at a fourth transmission time, wherein the fourth transmission time is the time after a preset delay of the second transmission time, and the fourth power is the power after the third power is reduced by a preset power value.

[0191] When the communication device 110 is used to implement the functions of an SFU or MFU:

[0192] Optionally, the scheduling information indicates at least one of the following: transmission time, transmission data length, virtual access point (VAP) identifier, transmission power, transmission bandwidth, modulation and coding scheme (MCS), or transmission protocol type.

[0193] Optionally, the transmission time indicates the transmission time of the second multicast / broadcast data; the transmission data length indicates the length of the second multicast / broadcast data; or, the VAP identifier is the identifier of the VAP used to transmit the second multicast / broadcast data; or, the transmission power indicates the transmission power of the second multicast / broadcast data; or, the transmission bandwidth indicates the transmission bandwidth of the second multicast / broadcast data; or, the MCS indicates the MCS of the second multicast / broadcast data; or, the transmission protocol type indicates the type of protocol used when transmitting the second multicast / broadcast data.

[0194] Optionally, scheduling information can be carried in the Wireless LAN Management and Control Interface (WMCI) message.

[0195] Optionally, the preset duration is 20 microseconds, and / or the preset power value is 6dB.

[0196] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0197] In this application, the communication device 110 can be presented in an integrated manner, divided into various functional modules. Here, "module" can refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the above functions.

[0198] In some embodiments, when Figure 11 When the communication device 110 is a chip or chip system, the function / implementation process of the transceiver module 1102 can be implemented through the input / output interface (or communication interface) of the chip or chip system, and the function / implementation process of the processing module 1101 can be implemented through the processor (or processing circuit) of the chip or chip system.

[0199] In some embodiments, Figure 11 The transceiver module 1102 can be replaced by a transceiver unit, which can integrate the functions of the transceiver module 1102; the processing module 1101 can be replaced by a processor, which can integrate the functions of the processing module 1101. Furthermore, Figure 11 The communication device 110 shown may also include a memory.

[0200] Alternatively, when the processing module 1101 is replaced by a processor and the transceiver module 1102 is replaced by a transceiver, the communication device 110 involved in the embodiments of this application can also be... Figure 12 The communication device 120 shown. The processor can be logic circuit 1201, and the transceiver can be interface circuit 1202. Further, Figure 12 The communication device 120 shown may also include a memory 1203.

[0201] Since the communication device 110 or communication device 120 provided in this embodiment can execute the above method, the technical effects it can obtain can be referred to the above method embodiment, and will not be repeated here.

[0202] As a possible product form, the SFU or MFU described in the embodiments of this application can be implemented using the following: one or more field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various functions described throughout this application.

[0203] As another possible product form, the SFU or MFU in this application can be adopted. Figure 13 The shown composition structure, or including Figure 13 The components shown. Figure 13 The present application provides a schematic diagram of the composition of a communication device 1300, which can be an SFU or a chip or system-on-a-chip in an SFU; or, it can be an MFU or a chip or system-on-a-chip in an MFU.

[0204] like Figure 13 As shown, the communication device 1300 includes at least one processor 1301 and at least one communication interface. Figure 13 (This is merely an example illustration, using a communication interface 1304 and a processor 1301 as examples.) Optionally, the communication device 1300 may also include a communication bus 1302 and a memory 1303.

[0205] Processor 1301 can be a general-purpose central processing unit (CPU), a general-purpose processor, a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a PLD, or any combination thereof. Processor 1301 can also be other devices with processing functions, such as circuits, devices, or software modules, without limitation.

[0206] The communication bus 1302 is used to connect different components in the communication device 1300, enabling communication between them. The communication bus 1302 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 13 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0207] Communication interface 1304 is used for communicating with other devices or communication networks. Exemplarily, communication interface 1304 can be a module, circuit, transceiver, or any device capable of communication. Optionally, the communication interface 1304 can also be an input / output interface located within processor 1301, used to implement signal input and signal output for the processor.

[0208] The memory 1303 may be a device with storage function, used to store instructions and / or data. The instructions may be computer programs.

[0209] For example, the memory 1303 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and / or instructions; it may also be a random access memory (RAM) or other type of dynamic storage device capable of storing information and / or instructions; it may also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, etc., without limitation.

[0210] It should be noted that the memory 1303 can exist independently of the processor 1301, or it can be integrated with the processor 1301. The memory 1303 can be located inside or outside the communication device 1300, without limitation. The processor 1301 can be used to execute the instructions stored in the memory 1303 to implement the methods provided in the following embodiments of this application.

[0211] Optionally, the processor 1301 and / or memory 1303 may include an artificial intelligence (AI) module, which is used to implement AI-related functions. The AI ​​module can be implemented through software, hardware, or a combination of both. For example, the AI ​​module may include a radio network intelligent controller (RIC) module. For example, the AI ​​module can be a near real-time RIC or a non-real-time RIC.

[0212] As an optional implementation, the communication device 1300 may also include an output device 1305 and an input device 1306. The output device 1305 communicates with the processor 1301 and can display information in various ways. For example, the output device 1305 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 1306 communicates with the processor 1301 and can receive user input in various ways. For example, the input device 1306 may be a mouse, keyboard, touchscreen device, or sensing device, etc.

[0213] In some embodiments, the hardware implementation will be apparent to those skilled in the art as described above. Figure 11 The communication device 110 shown can be adopted Figure 13 The communication device shown is in the form of 1300.

[0214] As an example, Figure 11 The function / implementation process of the processing module 1101 can be achieved through... Figure 13 The processor 1301 in the communication device 1300 shown calls computer execution instructions stored in memory 1303 to implement the function. Figure 11 The function / implementation process of the transceiver module 1102 can be obtained through Figure 13 This is achieved through the communication interface 1304 in the communication device 1300 shown.

[0215] It should be noted that, Figure 13The structures shown do not constitute a specific limitation on the SFU or MFU. For example, in other embodiments of this application, the SFU or MFU may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The components illustrated may be implemented in hardware, software, or a combination of software and hardware.

[0216] In some embodiments, this application also provides a communication device, which includes a processor for implementing the methods in any of the above method embodiments.

[0217] As one possible implementation, the communication device also includes a memory. This memory stores necessary computer programs and data. The computer program may include instructions, which a processor can invoke to instruct the communication device to execute the methods described in any of the above method embodiments. Alternatively, the memory may not be present in the communication device.

[0218] As another possible implementation, the communication device also includes an interface circuit, which is a code / data read / write interface circuit, used to receive computer execution instructions (which are stored in memory and may be read directly from memory or may be transmitted through other devices) and transmit them to the processor.

[0219] As another possible implementation, the communication device also includes a communication interface for communicating with modules outside the communication device.

[0220] It is understood that the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips or may include chips and other discrete devices. This application does not specifically limit this.

[0221] This application also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a computer, implements the functions of any of the above-described method embodiments.

[0222] This application also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0223] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0224] It is understood that the systems, apparatuses, and methods described in this application can also be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the couplings or direct couplings or communication connections shown or discussed may be through some interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

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

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

[0227] It should be noted that the terms "first" and "second," etc., in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. "First" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined with "first" and "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "a plurality of" means two or more.

[0228] Furthermore, the terms “comprising” and “having”, and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0229] It should be understood that in this application, "at least one (item)" means one or more. "More than one" means two or more. "At least two (items)" means two or three or more. "And / or" is used to describe the relationship between related objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple. Both "...when" and "if" indicate that a corresponding action will be taken under certain objective circumstances. They are not time limits, nor do they require a judgment action to be taken when the action is taken, nor do they imply any other limitations.

[0230] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0231] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0232] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive (SSD)). In this embodiment, the computer may include the aforementioned apparatus.

[0233] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0234] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the scope of this application. Accordingly, this specification and drawings are merely illustrative descriptions of the application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from its scope. Thus, if such modifications and modifications fall within the scope of the claims and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A communication method, characterized in that, The method, applied to a sub-optical network unit (SFU), includes: Receive the first multicast / broadcast data from the main optical network unit (MFU); Receive scheduling information from the MFU, the scheduling information being used to schedule the first multicast / broadcast data; The second multicast / broadcast data is sent according to the scheduling information, and the second multicast / broadcast data is part or all of the data in the first multicast / broadcast data.

2. The method according to claim 1, characterized in that, The scheduling information indicates at least one of the following: transmission time, transmission data length, virtual access point (VAP) identifier, transmission power, transmission bandwidth, modulation and coding scheme (MCS), or transmission protocol type.

3. The method according to claim 2, characterized in that, The transmission time indicates the time when the second multicast / broadcast data was sent; The transmitted data length indicates the length of the second multicast / broadcast data; or... The VAP identifier is the identifier of the VAP used to send the second multicast / broadcast data; or, The transmission power indicates the transmission power of the second multicast / broadcast data; or... The transmission bandwidth indicates the transmission bandwidth of the second multicast / broadcast data; or, The MCS indicates the MCS of the second multicast / broadcast data; or, The transport protocol type indicates the type of protocol used when sending the second multicast / broadcast data.

4. The method according to claim 1 or 2, characterized in that, The scheduling information is carried in the Wireless LAN Management and Control Interface (WMCI) message.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: Receive third multicast / broadcast data from a first device, which is a device other than an MFU; The third multicast / broadcast data is sent to the MFU, wherein the first multicast / broadcast data includes the third multicast / broadcast data.

6. The method according to any one of claims 1-5, characterized in that, The scheduling information indicates a first transmission time and a second transmission time, wherein the first transmission time is earlier than the second transmission time; Sending second multicast / broadcast data according to the scheduling information includes: The second multicast / broadcast data is transmitted at the first power during the third transmission time, wherein the third transmission time is the time after a preset delay from the first transmission time. as well as, The second multicast / broadcast data is transmitted at the second power during the second transmission time, where the first power is the power after the second power is reduced by a preset power value.

7. The method according to claim 6, characterized in that, The preset duration is 20 microseconds, and / or the preset power value is 6dB.

8. A communication method, characterized in that, Applied to a main optical network unit (MFU), the method includes: Send the first multicast / broadcast data to at least one sub-optical network unit (SFU); Send scheduling information to the at least one SFU, the scheduling information being used to schedule the first multicast / broadcast data; The second multicast / broadcast data is sent according to the scheduling information, and the second multicast / broadcast data is part or all of the data in the multicast / broadcast data.

9. The method according to claim 8, characterized in that, The scheduling information indicates at least one of the following: transmission time, transmission data length, virtual access point (VAP) identifier, transmission power, transmission bandwidth, modulation and coding scheme (MCS), or transmission protocol type.

10. The method according to claim 9, characterized in that, The transmission time indicates the time when the second multicast / broadcast data was sent; The transmitted data length indicates the length of the second multicast / broadcast data; or... The VAP identifier is the identifier of the VAP used to send the second multicast / broadcast data; or, The transmission power indicates the transmission power of the second multicast / broadcast data; or... The transmission bandwidth indicates the transmission bandwidth of the second multicast / broadcast data; or, The MCS indicates the MCS of the second multicast / broadcast data; or, The transport protocol type indicates the type of protocol used when sending the second multicast / broadcast data.

11. The method according to any one of claims 8-10, characterized in that, The scheduling information is carried in the Wireless LAN Management and Control Interface (WMCI) message.

12. The method according to any one of claims 8-11, characterized in that, The method further includes: acquiring multicast / broadcast data, wherein the first multicast / broadcast data is part or all of the multicast / broadcast data.

13. The method according to claim 12, characterized in that, The acquisition of multicast / broadcast data includes: receiving third multicast / broadcast data from the first SFU, wherein the multicast / broadcast data includes the third multicast / broadcast data.

14. The method according to claim 12 or 13, characterized in that, The acquisition of multicast / broadcast data includes: Receive fourth multicast / broadcast data from the optical line terminal (OLT), the multicast / broadcast data including the fourth multicast / broadcast data.

15. The method according to any one of claims 8-14, characterized in that, The scheduling information indicates a first transmission time and a second transmission time, wherein the first transmission time is earlier than the second transmission time; Sending second multicast / broadcast data according to the scheduling information includes: The second multicast / broadcast data is transmitted at a third power during the first transmission time; The second multicast / broadcast data is transmitted at a fourth power during the fourth transmission time, where the fourth transmission time is the time after a preset delay of the second transmission time, and the fourth power is the power after the third power is reduced by a preset power value.

16. The method according to claim 15, characterized in that, The preset duration is 20 microseconds, and / or the preset power value is 6dB.

17. A communication device, characterized in that, The communication device includes a processor; the processor is configured to run a computer program or instructions to cause the communication device to perform the method as described in any one of claims 1-7, or to cause the communication device to perform the method as described in any one of claims 8-16.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions or programs that, when executed on a computer, cause the method described in any one of claims 1-7 to be performed, or cause the method described in any one of claims 8-16 to be performed.

19. A computer program product, characterized in that, The computer program product includes computer instructions; when some or all of the computer instructions are run on a computer, they cause the method as described in any one of claims 1-7 to be performed, or cause the method as described in any one of claims 8-16 to be performed.

Images