Communication method and apparatus

Abstract

A communication method and apparatus, capable of avoiding triggering abnormal behavior of a station, ensuring service transmission, and improving communication performance. If 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 acquires multicast / broadcast data to be sent, and sends the same scheduling information to each SFU, so as to schedule sending of the multicast / broadcast data, and multiple SFUs can send the multicast / broadcast data according to the scheduling of the MFU. In addition, the MFU may further send the multicast / broadcast data by using a configuration indicated by the scheduling information. That is, the MFU can perform unified scheduling of multiple SFUs to send multicast / broadcast data, thereby ensuring that each SFU and the MFU use the same configuration to send multicast / broadcast data. For example, the same content can be sent, sending times can be aligned, and the same parameters can be used, such that a station receives a superposition of signals sent by each SFU and the MFU, ensuring that the signal strength does not jump, thereby avoiding triggering abnormal behavior.

Description

Communication method and apparatus

[0001] The present application claims priority to the Chinese patent application No. 202411569925.8, filed on November 4, 2024, and entitled "Communication method and apparatus", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] Embodiments of the present application relate to the field of communication, in particular to a communication method and apparatus. BACKGROUND

[0003] Under the fiber to the room (FTTR) networking architecture, in order to realize seamless roaming, some manufacturers have proposed a same basic service set identifier (BSSID) networking scheme.

[0004] In the same BSSID networking scheme, a master fiber unit (MFU) and all sub fiber units (SFUs) use the same BSSID and work on the same channel. Based on this networking manner, the station (STA) can be switched to an AP with better signal without feeling in the case of poor service AP signal.

[0005] However, under this networking manner, the STA receives downlink multicast / broadcast data from different APs, which may cause the signal strength of the STA to jump, trigger abnormal behaviors such as channel probing or autonomous roaming, and affect the transmission of services. SUMMARY

[0006] The present application provides a communication method and apparatus, which can avoid triggering abnormal behaviors of the STA and will not affect the transmission of services of the STA.

[0007] In a first aspect, a communication method is provided. The method can be performed by an SFU, or by a component of the SFU, such as a processor, a chip, or a chip system of the SFU, or by a logic module or software that can realize all or part of the functions of the SFU. The method comprises: receiving first multicast / broadcast data from a master fiber unit (MFU); receiving scheduling information from the MFU, the scheduling information being used to schedule the first multicast / broadcast data; and transmitting second multicast / broadcast data according to the scheduling information, the second multicast / broadcast data being part or all of the first multicast / broadcast data.

[0008] Based on the scheme, the MFU can uniformly schedule the SFU to send the multicast / broadcast data, so that the SFU and the MFU send the multicast / broadcast data by using the same configuration, the station can receive the superposition of signals sent by the SFU and the MFU, the station can normally parse the data, the strength of the received signal does not jump, and the abnormal behavior of the station is avoided, the service transmission is ensured, and the communication performance is improved.

[0009] In a possible design, the transmission time, the transmission data length, the VAP identifier, the transmission power, the transmission bandwidth, the MCS, or the transmission protocol type.

[0010] Based on the possible design, the MFU can schedule the SFU and the MFU to send the multicast / broadcast data at the same time, send the same multicast / broadcast data, and use the same sending parameter, so that the station receives the superposition of signals sent by the SFU and the MFU, the station can normally parse the data, the strength of the received signal does not jump, and the abnormal behavior of the station is avoided, the service transmission is ensured, and the communication performance is improved.

[0011] In a possible design, the transmission time indicates the sending 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 send the second multicast / broadcast data; or the transmission power indicates the sending power of the second multicast / broadcast data; or the transmission bandwidth indicates the sending 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 the protocol used when the second multicast / broadcast data is sent.

[0012] In a possible design, the scheduling information is carried in a wireless local area network management and control interface (WMCI) message.

[0013] In a 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.

[0014] Based on the possible design, after receiving the multicast / broadcast data that is not from the MFU, the SFU can not immediately forward the multicast / broadcast data to the WLAN interface, but forward the multicast / broadcast data to the MFU, so that the MFU can uniformly schedule the transmission of the multicast / broadcast data, the strength of the received data of the station does not jump, the abnormal behavior of the station is avoided, the service transmission is ensured, and the communication performance improves.

[0015] 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; and transmitting the second multicast / broadcast data according to the scheduling information includes transmitting the second multicast / broadcast data at a third transmission time with a first power, the third transmission time being a time after the first transmission time by a preset time duration, and transmitting the second multicast / broadcast data at the second transmission time with a second power, the first power being a power after the second power is reduced by a preset power value.

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

[0017] In a second aspect, a communication method is provided. The method can be performed by an MFU, or by a component of the MFU, such as a processor, a chip, or a chip system of the MFU, or by a logic module or software that can implement all or part of the functions of the MFU. The method includes: transmitting first multicast / broadcast data to at least one sub-optical network unit (SFU); transmitting scheduling information to the at least one SFU, the scheduling information being used to schedule the first multicast / broadcast data; and transmitting 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 brought by the second aspect can be referred to the technical effects brought by the first aspect, which will not be repeated here.

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

[0019] In one possible design, the transmission time indicates a transmission time of the second multicast / broadcast data; the transmission data length indicates a length of the second multicast / broadcast data; or the VAP identifier is an identifier of a VAP used to transmit the second multicast / broadcast data; or the transmission power indicates a transmission power of the second multicast / broadcast data; or the transmission bandwidth indicates a transmission bandwidth of the second multicast / broadcast data; or the MCS indicates an MCS of the second multicast / broadcast data; or the transmission protocol type indicates a type of a protocol used to transmit the second multicast / broadcast data.

[0020] In one possible design, the scheduling information is carried in a wireless local area network management and control interface (WMCI) message.

[0021] In one possible design, the method further includes: obtaining the multicast / broadcast data, the first multicast / broadcast data being part or all of the multicast / broadcast data.

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

[0023] In a possible design, the obtaining the 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.

[0024] In a 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; and the sending the second multicast / broadcast data according to the scheduling information includes: sending the second multicast / broadcast data at the third power at the first transmission time; and sending the second multicast / broadcast data at a fourth power at a fourth transmission time, the fourth transmission time being a time after the second transmission time is delayed by a preset time length, and the fourth power being a power after the third power is reduced by a preset power value.

[0025] In a possible design, the preset time length is 20 microseconds, and / or the preset power value is 6 decibels (dB).

[0026] The technical effects brought by any possible design of the second aspect can refer to the technical effects brought by the corresponding design of the first aspect described above, which will not be repeated here.

[0027] In a third aspect, a communication apparatus is provided, which is configured to implement various methods. The communication apparatus includes modules, units, or means corresponding to the methods, and the modules, units, or means can be implemented by hardware, software, or by a combination of hardware and software. The hardware or software includes one or more modules or units corresponding to the functions.

[0028] In some possible designs, the communication apparatus can include a processing module and a transceiver module. The processing module can be configured to implement the processing functions in any of the aspects and any possible implementation of the aspects described above. The transceiver module can include a receiving module and a sending module, which are configured to implement the receiving functions and the sending functions in any of the aspects and any possible implementation of the aspects described above.

[0029] In some possible designs, the transceiver module can be composed of a transceiver circuit, a transceiver, a transceiver processor, or a communication interface.

[0030] In a fourth aspect, a communication apparatus is provided, which includes a processor and a memory. The memory is configured to store computer instructions, and when the processor executes the instructions, the communication apparatus is caused to perform the methods in any of the aspects and any possible design of the aspects described above.

[0031] In a fifth aspect, a communication apparatus is provided, which comprises: a processor and a communication interface; the communication interface is configured to communicate with a module outside the communication apparatus; the processor is configured to execute computer programs or instructions to enable the communication apparatus to perform the method described in any of the above aspects and any possible design thereof.

[0032] In a sixth aspect, a communication apparatus is provided, which comprises: at least one processor; the processor is configured to execute computer programs or instructions stored in a memory to enable the communication apparatus to perform the method described in any of the above aspects and any possible design thereof. The memory can be coupled with the processor, or can be independent of the processor.

[0033] In a seventh aspect, a communication apparatus (for example, the communication apparatus can be a chip or a chip system) is provided, which comprises a processor configured to implement the functions involved in any of the above aspects and any possible design thereof.

[0034] In some possible designs, the communication apparatus comprises a memory configured to store necessary program instructions and data.

[0035] In some possible designs, when the apparatus is a chip system, the apparatus can be composed of a chip, or can comprise a chip and other discrete devices.

[0036] The communication apparatus described in the third aspect to the seventh aspect can be the SFU in the first aspect, or an apparatus (for example, a chip or a chip system) included in the SFU; or the communication apparatus can be the MFU in the second aspect, or an apparatus (for example, a chip or a chip system) included in the MFU.

[0037] In an eighth aspect, a communication apparatus is provided, which can be the SFU, or a module or unit (for example, a chip, or a chip system, or a circuit) in the SFU performing the method / operation / step / action described in the first aspect one by one, or a module or unit that can be matched with the SFU; or the communication apparatus can be the MFU, or a module or unit (for example, a chip, or a chip system, or a circuit) in the MFU performing the method / operation / step / action described in the second aspect one by one, or a module or unit that can be matched with the MFU.

[0038] It can be understood that, when the communication apparatus provided in any of the third aspect to the eighth aspect is a chip, the transmission action / function of the communication apparatus can be understood as outputting information, and the reception action / function of the communication apparatus can be understood as inputting information.

[0039] In a ninth aspect, a computer-readable storage medium is provided, which stores a computer program or instructions, when executed on a communication device, causes the communication device to perform the method of any of the above aspects and any possible design thereof.

[0040] In a tenth aspect, a computer program product is provided, which contains instructions, when executed on a communication device, causes the communication device to perform the method of any of the above aspects and any possible design thereof.

[0041] In an eleventh aspect, a communication system is provided, which includes an SFU and an MFU. The SFU is configured to implement the method of the first aspect and any possible design thereof, and the MFU is configured to implement the method of the second aspect and any possible design thereof.

[0042] The technical effects brought by any of the designs of the third aspect to the eleventh aspect can be referred to the technical effects brought by different designs of the first aspect or the second aspect, which will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0043] FIG. 1 is a structural schematic diagram of a communication system provided by the present application;

[0044] FIG. 2 is a structural schematic diagram of another communication system provided by the present application;

[0045] FIG. 3 is a schematic diagram of a station side signal strength jump in a same BSSID networking scenario provided by the present application;

[0046] FIG. 4 is a flow schematic diagram of a communication method provided by the present application;

[0047] FIG. 5 is a forwarding schematic diagram of multicast / broadcast data provided by the present application;

[0048] FIG. 6 is another forwarding schematic diagram of multicast / broadcast data provided by the present application;

[0049] FIG. 7 is a format schematic diagram of a WMCI message provided by the present application;

[0050] FIG. 8 is a flow schematic diagram of another communication method provided by the present application;

[0051] FIG. 9 is a scenario schematic diagram of twice alignment transmission provided by the present application;

[0052] FIG. 10 is a timing relationship schematic diagram of strong and weak signals provided by the present application;

[0053] FIG. 11 is a structural schematic diagram of a communication device provided by the present application;

[0054] FIG. 12 is a structural schematic diagram of another communication device provided in the present application;

[0055] FIG. 13 is a structural schematic diagram of still another communication device provided in the present application. DETAILED DESCRIPTION

[0056] In order to make the objects, technical solutions and advantages of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the drawings.

[0057] The technical solution provided in the embodiments of the present application can be applied to a fiber to the room (FTTR) system networking scenario. In addition, the present application can also be applied to an FTTR-based evolved networking scenario, or a networking scenario similar to the FTTR networking scenario, without limitation.

[0058] As shown in FIG. 1, the FTTR system can include a master fiber unit (MFU) and at least one sub fiber unit (SFU). The MFU can be connected to one or more SFUs through an optical link (such as an optical fiber), and the SFU can be connected to a station (STA) through a wireless local area network (WLAN) technology. Optionally, the MFU can also communicate with the STA through the WLAN technology, and the MFU can also be connected to an optical line terminal (OLT) through the optical link.

[0059] As a possible implementation, in the embodiments of the present application, the SFU and the MFU communicate through a WLAN management and control interface (WMCI) / WMCI management channel. The WMCI management channel is a low-latency channel between the MFU and the SFU in the FTTR network, which realizes WLAN control and other functions, is used to carry WMCI messages, and is carried through an independent FEM port-ID.

[0060] As a possible implementation, in the embodiments of the present application, the basic service set identifier (BSSID) of the MFU and the SFU is the same, and / or the service set identifier (SSID) is the same.

[0061] As a possible implementation, the Chinese of MFU can also be FTTR master device, and the English of main FTTR unit, the Chinese of SFU can also be FTTR slave device or FTTR sub-device, and the English of sub FTTR unit, the MFU can also be called main gateway, and the SFU can also be called sub-gateway.

[0062] As a possible implementation, in a larger area or an area with higher requirements for network quality, multiple sets of FTTR systems can be centrally deployed, and the multiple sets of FTTR systems provide unified wireless network access services. In the FTTR centralized deployment scenario, multiple sets of FTTR systems can be deployed in the same subnet, and the multiple sets of FTTR systems are logically configured to belong to the same subnet when deployed online, and manual configuration or automatic configuration is adopted during configuration. For example, as shown in (a) of FIG. 2, FTTR system 1 and FTTR system 2 are deployed in the same subnet and are uniformly managed by OLT1, FTTR system 1 includes MFU1, SFU1.1 and SFU1.2, MFU1 is connected with SFU1.1 and SFU1.2 through optical fibers respectively, and MFU1 is connected with OLT1; FTTR system 2 includes MFU2, SFU2.1 and SFU2.2, MFU2 is connected with SFU2.1 and SFU2.2 through optical fibers respectively, and MFU2 is connected with OLT1.

[0063] As a possible implementation, the embodiments of the present application can be applied to the roaming scenario in the FTTR related networking.

[0064] As shown in (b) of FIG. 2, during the movement of the station in the FTTR networking, the channel quality of the currently associated SFU becomes poor, and the station needs to roam to an SFU with better channel quality to ensure the continuity of the service. Meanwhile, during the roaming process, the terminal needs to reestablish the connection on the new SFU, which will cause the interruption of the service. In order to ensure the timeliness and continuity of the roaming, the present application adopts WMCI to implement the cooperative roaming control scheme.

[0065] In the cooperative roaming scheme based on WMCI, four aspects of processing are mainly included, that is, roaming configuration information synchronization, networking information synchronization, terminal online processing, and terminal roaming processing.

[0066] When the SFU is online, the WMCI roaming and the network parameter configuration are started or stopped, the roaming network configuration is triggered.

[0067] When the SFU is online, the MFU checks whether the network's cooperative roaming function is enabled. If the network's cooperative roaming function is enabled, the SFU is checked according to the roaming capability information of the SFU to determine whether the SFU meets the enabling condition. If the SFU meets the enabling condition, the roaming configuration of the newly online SFU is enabled. If the SFU does not meet the enabling condition, the roaming configuration is not enabled. If the network's cooperative roaming function is not enabled, no cooperative roaming configuration is performed.

[0068] After the networking is completed, the cooperative roaming function in the network can be enabled or disabled. When the cooperative roaming function is enabled, the MFU should first determine whether the enabling condition is met. If the enabling condition is met, the enabling roaming configuration instruction is issued to all SFUs. If the enabling condition is not met, no roaming enabling configuration is performed. When the cooperative roaming function is disabled, the MFU should restore the normal configuration of the entire network and disable the roaming feature.

[0069] The cooperative roaming function enabling / disabling process includes the following steps:

[0070] (1) The MFU issues the roaming configuration information to the SFU through the roaming configuration message.

[0071] (2) The SFU completes the related parameter configuration after receiving the configuration message and feeds back the roaming configuration confirmation message.

[0072] (3) The MFU receives the roaming configuration confirmation message fed back by the SFU and issues the roaming enabling or disabling message to the SFU.

[0073] (4) After the SFU completes the enabling or disabling, the SFU feeds back the roaming enabling or disabling confirmation message to the MFU.

[0074] After the cooperative roaming function is enabled, the periodic synchronization of the networking information needs to be completed. The synchronization includes the synchronization transmission of the beacon frame. There are mainly two synchronization methods. One is that the MFU controls the synchronization time and issues the networking synchronization information to the SFUs in the networking at the synchronization time. The other is that all SFUs report the synchronization information, and then the MFU collects the information and issues the networking information synchronization.

[0075] When the station is online, the roaming function needs to be implemented, and the online association information and key information need to be synchronized in the entire network. When the station is offline, the associated SFU sends the terminal offline event to the MFU. After receiving the offline event, the MFU issues the instruction to delete the terminal information to the SFUs and the MFU in the entire network. After receiving the instruction to delete the terminal information issued by the MFU, the SFU deletes the terminal information. After the deletion is successful, the SFU reports the successful deletion instruction to the MFU. The MFU deletes the related terminal information.

[0076] As a possible implementation, the station in the embodiments of the present application can be a device supporting institute of electrical and electronics engineers (IEEE) related standards, and can implement a communication connection with the SFU based on WLAN technology, such as transmitting a physical frame to the SFU based on a radio frequency analog signal (or wireless signal, wireless radio frequency analog signal, wireless analog signal, etc.).

[0077] The IEEE related standards can include 802.11a / b / g standards, 802.11n standards, 802.11ac standards, 802.11ax standards, 802.11be standards, 802.11bn standards / ultra high reliability (UHR) standards / Wi-Fi8 standards, 802.11ad standards, 802.11ay standards, 802.11bf standards / sensing standards, ultra wide band (UWB) standards / 802.15 standards, etc., without limitation. In terms of bandwidth configuration, channel bonding is introduced from 802.11n, and multiple 20MHz channels can be bonded to achieve a larger bandwidth and provide a higher transmission rate. From 802.11ac, a maximum of 160MHz bandwidth can be provided. In the 802.11ax standard, the following bandwidth configurations can be supported: 20MHz, 40MHz, 80MHz, 160MHz, and 80+80MHz. In the 802.11be standard, 320MHz bandwidth configuration can also be supported.

[0078] For example, the station 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 example, the station can be a mobile phone supporting Wi-Fi communication function, a tablet computer supporting Wi-Fi communication function, a set-top box supporting Wi-Fi communication function, a smart home appliance supporting Wi-Fi communication function, a smart wearable device supporting Wi-Fi communication function, a vehicle-mounted communication device supporting Wi-Fi communication function, a computer supporting Wi-Fi communication function, a camera supporting Wi-Fi communication function, a robot supporting Wi-Fi communication function, an office equipment supporting Wi-Fi communication function, etc., without limitation.

[0079] As a possible implementation, the SFU in the embodiments of the present application can be a device supporting IEEE related standards, can realize communication connection with the station based on WLAN technology, and also realizes communication connection with the MFU through an optical link. That is, when the SFU and the MFU communicate, the digital signal can be converted into an optical signal for transmission. The optical signal can be understood as a signal transmission form of the digital signal between the SFU and the MFU. The transmission of the optical signal converted from the digital signal between the SFU and the MFU can also be understood as the digital signal transmission between the SFU and the MFU through the optical signal. For example, the SFU can send the optical signal converted from the uplink digital signal to the MFU through the uplink transmission channel of the optical link, and receive the optical signal converted from the downlink digital signal sent by the MFU through the downlink transmission channel of the optical link.

[0080] The SFU can include one or more antennas. The SFU can convert the digital signal of the one or more antennas into an optical signal, and send the optical signal to the MFU through the uplink transmission channel of the optical link, or receive the optical signal converted from the downlink digital signal sent by the MFU through the downlink transmission channel of the optical link through the one or more antennas. Taking the uplink transmission as an example, the SFU can collect the wireless signal sent by the station according to the uplink bandwidth indicated by the MFU to obtain the digital signal, and send the optical signal converted from the uplink digital signal to the MFU through the uplink transmission channel of the optical link according to the uplink bandwidth indicated by the MFU.

[0081] As a possible implementation, the MFU in the embodiments of the present application can be a device supporting IEEE related standards, and can realize communication connection with the SFU through an optical link. For example, the MFU can receive the optical signal converted from the uplink digital signal sent by the SFU through the uplink transmission channel of the optical link, and send the optical signal converted from the downlink digital signal to the SFU through the downlink transmission channel of the optical link. The MFU can also indicate the uplink bandwidth to the SFU, and instruct the SFU to perform uplink transmission according to the uplink bandwidth. The MFU can also determine the baseband signal according to the obtained uplink digital signal, perform physical layer demodulation on the baseband signal, and obtain the physical frame sent by the station.

[0082] For example, the MFU can be a terminal device, a network device, a communication server, a router, a switch, a bridge, a computer, etc. with a Wi-Fi chip. The MFU can also be an access point for mobile users to enter a wired network, and is mainly deployed in a home, a building, and a park, and has a typical coverage radius of tens of meters to hundreds of meters. Of course, the MFU can also be deployed outdoors. The MFU is equivalent to a bridge connecting the wired network and the wireless network, and mainly functions to connect various wireless network clients together, and then access the wireless network to the Ethernet.

[0083] In the FTTR networking architecture, in order to realize seamless roaming, some manufacturers have proposed a same basic service set identifier (BSSID) networking scheme. In the same BSSID networking scheme, the MFU and all the SFUs use the same BSSID and work on the same channel. Based on this networking manner, the station (STA) can be switched to an AP with better signal without feeling in the case of poor service AP signal. The AP can include the MFU or the SFU, etc.

[0084] However, in the same BSSID networking manner, the station cannot distinguish the MFU and the SFUs, and the station will receive the downlink multicast / broadcast data from different APs, causing the received signal strength indicator (RSSI) strength of the downlink data to fluctuate, which will cause the signal strength to jump at the station side. For example, as shown in FIG. 3, taking the APs in the same BSSID networking architecture including the MFU, SFU1 and SFU2 as an example, the signal strengths of the downlink multicast / broadcast data sent by the MFU, SFU1 and SFU2 at the station side are-30 dB, -70 dB and -90 dB respectively, that is, the signal strength jumps.

[0085] For the station, the signal strength jump can trigger business interruption, channel detection or abnormal behaviors such as autonomous roaming, thereby affecting the business transmission.

[0086] Based on this, the application provides a communication method. In the method, when the multicast / broadcast data received by each SFU is not from the MFU, the SFU only forwards the multicast / broadcast data to the MFU. The MFU obtains the multicast / broadcast data to be sent, sends the same scheduling information to each SFU to schedule the sending of the multicast / broadcast data, and the multiple SFUs can send the multicast / broadcast data according to the scheduling of the MFU. In addition, the MFU can also send the multicast / broadcast data according to the configuration indicated by the scheduling information.

[0087] Through the above scheme, the MFU can uniformly schedule the multiple SFUs to send the multicast / broadcast data, thereby ensuring that each SFU and the MFU send the multicast / broadcast data using the same configuration, for example, each SFU and the 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 the MFU, ensures that the strength of the signal received by the station will not jump, and further avoids triggering the abnormal behavior of the station, ensures the business transmission, and improves the communication performance.

[0088] The communication method provided by the embodiments of the present application is described below by taking the interaction between the SFU and the MFU as an example in the communication system shown in FIG. 1 or FIG. 2.

[0089] It should be noted that the names of messages, the names of parameters, or the names of information between the SFU and the MFU in the following embodiments of the present application are only examples, and other names can also be used in other embodiments, and the method provided by the present application does not make specific limitations.

[0090] It can be understood that in the embodiments of the present application, the SFU and the MFU can perform part or all of the steps in the embodiments of the present application, and these steps or operations are only examples, and the embodiments of the present application can also perform other operations or variations of various operations. In addition, each step can be performed in a different order as presented in the embodiments of the present application, and it is possible that not all operations in the embodiments of the present application are performed.

[0091] It can be understood that the SFU and the MFU are taken as the execution subject of the interaction in the present application, but the present application does not limit the execution subject of the interaction. For example, the method performed by the SFU in the present application can also be performed by a module (such as a chip, a chip system, or a processor) applied to the SFU, and can also be implemented by a logical node, a logical module, or software that can implement all or part of the SFU function; the method performed by the MFU in the present application can also be performed by a module (such as a chip, a chip system, or a processor) applied to the MFU, and can also be implemented by a logical node, a logical module, or software that can implement all or part of the MFU function.

[0092] The communication method provided by the embodiments of the present application is described below. As shown in FIG. 4, the communication method can include the following steps:

[0093] S400, the MFU acquires multicast / broadcast data.

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

[0095] As a possible implementation, for the SFU, if the multicast / broadcast data received by the SFU is not from the MFU, the SFU only forwards the multicast / broadcast data to the MFU.

[0096] For example, the multicast / broadcast data received by the SFU can be from a local area network (LAN) side or from a passive optical network (PON) side, such as from another SFU. For multicast / broadcast data from the LAN side or another SFU, the SFU does not directly forward to the air interface (or WLAN interface or Wi-Fi interface), but forwards to the MFU.

[0097] For example, as shown in FIG. 5, taking the MFU, the first SFU and the second SFU included in the same BSSID networking architecture as an example, the first SFU receives multicast / broadcast data a from a first device (the first device is not the MFU), and then forwards the multicast / broadcast data a to the MFU. The multicast / broadcast data a can also be referred to as third multicast / broadcast data.

[0098] As another possible implementation, for example, as shown in FIG. 6, the multicast / broadcast data obtained by the MFU can also include multicast / broadcast packets on the MFU side, for example, the MFU receives multicast / broadcast data b from an OLT. The multicast / broadcast data b can also be referred to as fourth multicast / broadcast data.

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

[0100] For example, the embodiments of the present application and FIG. 4 take the at least one SFU including the first SFU and the second SFU as an example for description. In actual application, the at least one SFU can refer to more or less SFUs than two SFUs. The implementation of other SFUs in the at least one SFU can refer to the related implementation of the first SFU and the second SFU in the embodiments of the present application, and will not be described herein.

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

[0102] For example, based on the example shown in FIG. 5 and FIG. 6, taking the first multicast / broadcast data as the whole multicast / broadcast data c, i.e., the first multicast / broadcast data and the multicast / broadcast data c are the same, as shown in FIG. 5, the MFU forwards the multicast / broadcast data a to the first SFU and the second SFU after receiving the multicast / broadcast data a from the first SFU. In addition, the MFU, the first SFU and the second SFU can also store the multicast / broadcast data a, for example, store it in the Wi-Fi cache.

[0103] In addition, as shown in FIG. 6, the MFU forwards the multicast / broadcast data b to the first SFU and the second SFU after receiving the multicast / broadcast data b. In addition, the MFU, the first SFU and the second SFU can also store the multicast / broadcast data b, for example, store it in the Wi-Fi cache.

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

[0105] The scheduling information is used to schedule the first multicast / broadcast data. It can be understood that the scheduling information sent by the MFU to different SFUs in the at least one SFU is the same.

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

[0107] As a possible implementation, the transmission time indicates a time of sending the multicast / broadcast data. For example, the transmission time can be an absolute time, such as coordinated universal time (UTC); or the transmission time can also be a relative time, such as a time represented by a WLAN frame number, without limitation.

[0108] 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, which are not limited in the present application.

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

[0110] 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.

[0111] 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.

[0112] 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.

[0113] 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.

[0114] 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.

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

[0116] 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.

[0117] 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.

[0118] 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.

[0119] Table 1

[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] 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.

[0123] 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.

[0124] 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.

[0125] 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.

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

[0127] 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 Message type ID field.

[0128] 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.

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

[0130] 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.

[0131] 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.

[0132] Table 2.2

[0133] 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.

[0134] 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.

[0135] 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.

[0136] 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.

[0137] Table 3

[0138] In other words, a possible format for a WMCI message or scheduling instruction message can be shown in Figure 7. The descriptions of the fields in Figure 7 can be found in the aforementioned descriptions of relevant information / parameters, and will not be repeated here.

[0139] 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.

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

[0141] 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.

[0142] 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.

[0143] 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.

[0144] 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.

[0145] 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.

[0146] 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:

[0147] 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.

[0148] For example, as shown in Figure 5 or Figure 6, 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 b (collectively referred to as multicast / broadcast data c), for example, in a Wi-Fi cache.

[0149] 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.

[0150] 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.

[0151] 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.

[0152] For example, as shown in Figure 8, 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.

[0153] 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.

[0154] 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.

[0155] 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.

[0156] 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.

[0157] 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.

[0158] This method is similar to the one shown in Figure 4 above. 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 given 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.

[0159] 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.

[0160] 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.

[0161] 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 from the second transmission time.

[0162] 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.

[0163] 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, and this application does not specifically limit them.

[0164] For example, taking multicast / broadcast data including data 1 and data 2 as an example, as shown in Figure 9, when transmitting data 1 for the first time, the MFU transmits at normal power, while the SFU transmits with a 20-microsecond delay and reduced transmission power; when transmitting data 1 for the second time, the SFU transmits at normal power, while the MFU transmits with a 20-microsecond delay and reduced transmission power. Similarly, when transmitting data 2 for the first time, the MFU transmits at normal power, while the SFU transmits with a 20-microsecond delay and reduced transmission power; when transmitting data 2 for the second time, the SFU transmits at normal power, while the MFU transmits with a 20-microsecond delay and reduced transmission power.

[0165] 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.

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

[0167] For example, based on the example shown in Figure 9, when the station is connected to the MFU, the third power and the second power can be understood as the normal power or initial power of the MFU and SFU, respectively, and the third power is usually 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, so the station receives the data with higher signal strength first (i.e., data 1 sent by the MFU); in the second transmission, although the MFU reduces the transmission power, the MFU reduces the power based on the third power, and the third power is tens of dB higher than the second power. Therefore, even if the third power is reduced by a preset power value (e.g., 6 dB), the reduced fourth power may still be greater than the second power, so the station receives the data with lower signal strength first (i.e., data 1 sent by the SFU). In other words, it is guaranteed that the station receives one data with a strong signal first and one data with a weak signal first.

[0168] 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.

[0169] 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.

[0170] 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.

[0171] 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.

[0172] 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.

[0173] 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.

[0174] Figure 11 shows a schematic diagram of a communication device 110. 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 in an SFU or MFU.

[0175] In some embodiments, the communication device 110 may further include a storage module (not shown in FIG11) for storing program instructions and data.

[0176] 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.

[0177] 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.

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

[0179] 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.

[0180] 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.

[0181] 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.

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

[0183] 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.

[0184] 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.

[0185] 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.

[0186] 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.

[0187] 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.

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

[0189] 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.

[0190] 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.

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

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

[0193] 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.

[0194] In this application, the communication device 110 can be presented in an integrated manner by dividing it 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.

[0195] In some embodiments, when the communication device 110 in FIG11 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.

[0196] In some embodiments, the transceiver module 1102 in FIG11 can be replaced by a transceiver that integrates the functions of the transceiver module 1102; the processing module 1101 can be replaced by a processor that integrates the functions of the processing module 1101. Furthermore, the communication device 110 shown in FIG11 may also include a memory.

[0197] 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 the communication device 120 shown in FIG. 12. The processor can be a logic circuit 1201, and the transceiver can be an interface circuit 1202. Furthermore, the communication device 120 shown in FIG. 12 can also include a memory 1203.

[0198] 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.

[0199] 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.

[0200] As another possible product form, the SFU or MFU in this application can adopt the composition structure shown in FIG13, or include the components shown in FIG13. FIG13 is a schematic diagram of the composition of a communication device 1300 provided in this application. The communication device 1300 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.

[0201] As shown in Figure 13, the communication device 1300 includes at least one processor 1301 and at least one communication interface (Figure 13 is merely an example illustrating the inclusion of a communication interface 1304 and a processor 1301). Optionally, the communication device 1300 may also include a communication bus 1302 and a memory 1303.

[0202] 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.

[0203] Communication bus 1302 is used to connect different components in communication device 1300, enabling communication between them. 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 illustration, only one thick line is used in Figure 13, but this does not indicate that there is only one bus or one type of bus.

[0204] 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.

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

[0206] 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.

[0207] 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.

[0208] 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.

[0209] 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.

[0210] In some embodiments, those skilled in the art will recognize that the communication device 110 shown in FIG11 can take the form of the communication device 1300 shown in FIG13 in terms of hardware implementation.

[0211] As an example, the function / implementation process of the processing module 1101 in Figure 11 can be implemented by the processor 1301 in the communication device 1300 shown in Figure 13 calling computer execution instructions stored in the memory 1303. The function / implementation process of the transceiver module 1102 in Figure 11 can be implemented by the communication interface 1304 in the communication device 1300 shown in Figure 13.

[0212] It should be noted that the structure shown in Figure 13 does 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 shown, or combine some components, or split some components, or have different component arrangements. The components shown can be implemented in hardware, software, or a combination of software and hardware.

[0213] 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.

[0214] 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.

[0215] 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.

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

[0217] 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.

[0218] 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.

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

[0220] 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.

[0221] 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.

[0222] 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.

[0223] 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.

[0224] 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.

[0225] 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.

[0226] 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.

[0227] 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.

[0228] 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.

[0229] 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.

[0230] 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.

[0231] 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