Optical network communication method and communication apparatus

Abstract

The present application provides an optical network communication method and a communication apparatus. The method is applied to an optical fiber network, the optical fiber network comprises a master device and at least one slave device, and the at least one slave device includes a first slave device. The master device sends a first message to the first slave device, wherein the first message is a wireless local area network (WLAN) management and control interface (WMCI) message, the first message is used for managing or controlling a WLAN function of the first slave device, the first message comprises first indication information, and the first indication information is used for indicating a delay requirement or a priority of the WLAN function corresponding to the first message. Since the first indication information in the first message can indicate the priority or the delay requirement of the first message, on the basis of the first indication information, the first slave device determines whether to prioritize processing of the first message, thereby reducing the bandwidth occupied by a low-priority message or a message having a normal-delay requirement, and improving communication real-time performance of a high-priority message or a message having a low-delay requirement.

Description

A method of optical network communication and a communication apparatus

[0001] The present application claims priority from the Chinese patent application No. 202411156795.5 filed on August 21, 2024, and entitled "A method of optical network communication and a communication 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 optical communication, and in particular to a method of optical network communication and a communication apparatus. BACKGROUND

[0003] Fiber to the room (FTTR) refers to a technology in which optical fibers are used to replace network cables to provide optical fiber medium access to rooms from optical network devices (e.g., optical network terminals (ONTs)). The optical fiber network in the FTTR scenario includes a master device and one or more slave devices (also referred to as sub-devices). A management channel can be established between the master device and the slave device, so that the master device can send messages related to management or control to the slave device through the management channel, to achieve the management or control of part of the functions of the slave device by the master device. For example, the master device and the slave device can establish a WLAN management control interface (WMCI) management channel based on the WMCI protocol, so that the master device and the slave device interact with WMCI messages through the WMCI management channel, thereby achieving the management or control of WLAN functions.

[0004] Currently, in the FTTR system management architecture, different management types or the same management type of WLAN functions of the same slave device can have different management requirements and characteristics, and the time delay requirements corresponding to different management requirements and characteristics are different. The unified message format (e.g., the current WMCI message format) cannot distinguish different time delay requirements, which is not conducive to efficient management or control of WLAN functions of the slave device by the master device. SUMMARY

[0005] The present application provides a method of optical network communication and a communication apparatus for identifying messages with different time delay requirements or priorities in the same management channel, to improve the efficiency of management or control of WLAN functions of the slave device by the master device.

[0006] In a first aspect, the present application provides a method for optical network communication, applied to an optical fiber network, the optical fiber network comprising a master device and at least one slave device, the at least one slave device comprising a first slave device. The method for optical network communication can be executed by the master device in the optical fiber network, or by a part of functional modules or chips in the master device. Taking the master device as an example, the master device sends a first message to the first slave device, the first message being a wireless local area network management control interface (WMCI) message, the first message being used for managing or controlling a wireless local area network (WLAN) function of the first slave device, the first message comprising first indication information, the first indication information being used for indicating a latency requirement or a priority of the WLAN function corresponding to the first message.

[0007] In the aspect, the first indication information in the first message sent by the master device to the first slave device can indicate the priority or the latency requirement of the first message, which is beneficial for the first slave device to decide whether to process the first message preferentially based on the first indication information, beneficial for reducing the bandwidth occupied by low-priority messages or ordinary latency requirement messages, and beneficial for improving the communication real-time performance of high-priority messages or low-latency requirement messages.

[0008] In a possible implementation, the first indication information comprises a first value or a second value. The first value is used for indicating a requirement of latency control, i.e., indicating that the message (e.g., the first message) carrying the first indication information is a low-latency control message. The second value is used for indicating a requirement of no latency control, i.e., indicating that the message (e.g., the first message) carrying the first indication information is an ordinary control message.

[0009] In the embodiment, the first indication information in the first message sent by the master device to the first slave device can indicate the latency requirement, i.e., indicating whether the first message is a low-latency control message or an ordinary control message, which is beneficial for the first slave device to decide whether to process the first message preferentially based on the first indication information, beneficial for reducing the bandwidth occupied by ordinary latency control messages, and beneficial for improving the communication real-time performance of low-latency control messages.

[0010] In a possible implementation, the first indication information comprises at least two values, and different values of the at least two values respectively indicate different priorities. For example, the first indication information comprises two values, respectively indicating a low priority and a high priority. For another example, the first indication information comprises three values, respectively indicating a low priority, a medium priority and a high priority.

[0011] In this embodiment, the first indication information in the first message sent by the master device to the first slave device can indicate the priority of the first message, i.e., indicate whether the first message has a lower priority or a higher priority relative to other WMCI messages, which is beneficial for the first slave device to decide whether to process the first message preferentially based on the first indication information, beneficial for reducing the bandwidth occupied by low-priority messages, and beneficial for improving the communication real-time performance of high-priority messages.

[0012] In a possible implementation, the first indication information is located in a message type identifier field of the first message, or the first indication information is located in a message length field of the first message.

[0013] Optionally, the first indication information is located in the highest bit of the message type identifier field, or the first indication information is located in the highest 2 bits of the first byte of the message length field.

[0014] In a possible implementation, the first message further includes second indication information, the second indication information is used to indicate a first management type of the WLAN function to which the first message is used to manage, and the first indication information is further used to indicate a latency requirement or a priority of the first management type of the WLAN function.

[0015] In this embodiment, the first message includes the second indication information indicating the management type, which can explicitly indicate which management type of the WLAN function the first message is used to manage, and can be beneficial for improving the management efficiency of the master device on the WLAN function of the slave device. In addition, in combination with the first indication information, a specific latency requirement or priority can be indicated for a specific management type, which is beneficial for performing priority management in the granularity of the management type, thereby improving the management accuracy and efficiency of the WLAN function.

[0016] In a possible implementation, the first management type of the WLAN function is any one of WLAN data sending scheduling management, WLAN roaming management, or WLAN power adjustment management.

[0017] In a possible implementation, the first message is encapsulated in a payload field of an FTTR encapsulation method (FEM) frame, and an FEM port identifier in a frame header of the FEM frame is used to indicate that the first message corresponds to the first slave device.

[0018] In this embodiment, the FEM port ID in the frame header of the FEM frame is allocated by the master device, which can not only indicate that the first message is a WMCI message, but also be used to indicate the transceiving object of the WMCI message (i.e., the first message), i.e., indicate that the WMCI message (i.e., the first message) corresponds to the first slave device instead of other slave devices. Therefore, the WMCI message can be distinguished from other management messages in the FTTR system through the FEM port ID, which is conducive to improving the management efficiency of the WLAN function.

[0019] In a possible implementation, the FEM frame is encapsulated in a payload field of a data link layer (DLL) frame.

[0020] In a possible implementation, the method further includes: the master device sends a second message to the first slave device, the second message being a WMCI message, the second message being used to manage or control the WLAN function of the first slave device, the second message including third indication information and fourth indication information, the third indication information being used to indicate the latency requirement or the priority of the WLAN function corresponding to the second message, the fourth indication information being used to indicate a second management type of the WLAN function to which the second message is used for management, the second management type being different from the first management type, the latency requirement indicated by the third indication information being different from the latency requirement indicated by the first indication information, or the priority indicated by the third indication information being different from the priority indicated by the first indication information.

[0021] In a possible implementation, the master device is a main FTTR unit (MFU), and the slave device is a sub FTTR unit (SFU).

[0022] In a second aspect, the present application provides an optical network communication method applied to an optical fiber network, the optical fiber network including a master device and at least one slave device, the at least one slave device including a first slave device. The optical network communication method provided in this aspect can be executed by the first slave device in the optical fiber network, or can be executed by part of the functional modules or chips in the first slave device. Taking the execution by the first slave device as an example, the first slave device receives a first message from the master device, the first message being a wireless local area network management control interface (WMCI) message, the first message being used to manage or control a wireless local area network (WLAN) function of the first slave device, the first message including first indication information, the first indication information being used to indicate the latency requirement or the priority of the WLAN function corresponding to the first message; then, the first slave device manages and controls the WLAN function corresponding to the first message based on the first indication information.

[0023] In the aspect, the first indication information in the first message received by the first slave device can indicate a priority or a latency requirement of the first message, so that the first slave device decides whether to process the first message preferentially based on the first indication information, which is beneficial to reduce bandwidth occupied by low-priority messages or messages with normal latency requirements, and is beneficial to improve communication real-time performance of high-priority messages or messages with low latency requirements.

[0024] In a possible implementation, the first indication information includes a first value or a second value, the first value is used to indicate a requirement of latency control, and the second value is used to indicate a requirement of no latency control.

[0025] In a possible implementation, the first indication information includes at least two values, and different values of the at least two values respectively indicate different priorities.

[0026] In a possible implementation, the first indication information is located in a message type identification field of the first message, or the first indication information is located in a message length field of the first message.

[0027] In a possible implementation, the first indication information is located in the highest bit of the message type identification field, or the first indication information is located in the highest 2 bits of the first byte of the message length field.

[0028] In a possible implementation, the first message further includes second indication information, the second indication information is used to indicate a first control type of the WLAN function to which the first message is used to control, and the first indication information is further used to indicate a latency requirement or a priority of the first control type of the WLAN function.

[0029] In a possible implementation, the first control type of the WLAN function is any one of WLAN data sending scheduling control, WLAN roaming control or WLAN power adjustment control.

[0030] In a possible implementation, the first message is encapsulated in a payload field of a FEM frame, and a FEM port identification in a frame header of the FEM frame is used to indicate that the first message corresponds to the first slave device.

[0031] In a possible implementation, the FEM frame is encapsulated in a payload field of a data link layer (DLL) frame.

[0032] In a possible implementation, the method further includes: receiving, by the first slave device, a second message from the master device, the second message being a WMCI message, the second message being used for managing or controlling the WLAN function of the first slave device, the second message including third indication information and fourth indication information, the third indication information being used for indicating a time delay requirement or a priority of the WLAN function corresponding to the second message, the fourth indication information being used for indicating a second management type of the WLAN function to which the second message is used for management and control, the second management type being different from the first management type, the time delay requirement indicated by the third indication information being different from the time delay requirement indicated by the first indication information, or the priority indicated by the third indication information being different from the priority indicated by the first indication information.

[0033] In a possible implementation, the method further includes: in a case where the first indication information indicates a requirement of time delay control and the third indication information indicates a requirement of no time delay control, or the priority indicated by the first indication information is higher than the priority indicated by the third indication information, the first slave device preferentially manages and controls the WLAN function corresponding to the first message.

[0034] In this embodiment, when the first slave device receives two or more messages carrying indication of time delay requirement or priority, the first slave device processes the message with low time delay requirement or the message with high priority first, which is beneficial to implement QoS management on the messages transmitted in the same management channel, improve resource utilization efficiency, and improve management and control efficiency.

[0035] In a possible implementation, the master device is a master FTTR unit (MFU), and the slave device is a slave FTTR unit (SFU).

[0036] It should be noted that the embodiments of the present application have various other specific implementations, and details can be referred to the specific implementations and advantages of the first aspect, which will not be described here.

[0037] In a third aspect, the present application provides an optical network communication method, applied to an optical fiber network, the optical fiber network including a master device and at least one slave device, the at least one slave device including a first slave device. The optical network communication method provided by the present application can be executed by the master device in the optical fiber network, or can be executed by part of the functional modules or chips in the master device. Taking the master device as an example, the master device sends a third message to the first slave device, the third message being a wireless local area network management control interface (WMCI) message, the third message being used for managing or controlling a wireless local area network (WLAN) function of the first slave device, the third message including fifth indication information, the fifth indication information being used for indicating a first management type of the WLAN function to which the third message is used for management and control, the first management type corresponding to a first time delay requirement or a first priority.

[0038] In the aspect, the fifth indication information in the third message sent by the master device to the first slave device can not only indicate the WLAN management type of the third message, but also correspond to the first latency requirement or the first priority, which is beneficial for the first slave device to decide whether to process the third message preferentially based on the fifth indication information, beneficial for reducing the bandwidth occupied by low-priority messages, and beneficial for improving the communication real-time performance of high-priority messages.

[0039] In a possible implementation, the first latency requirement corresponding to the first management type is different from the second latency requirement corresponding to the second management type, or the first priority corresponding to the first management type is different from the second priority corresponding to the second management type, and the second management type is another management type of the WLAN function managed by the master device to the first slave device.

[0040] In a possible implementation, the first management type of the WLAN function is any one of WLAN data sending scheduling management, WLAN roaming management, or WLAN power adjustment management.

[0041] In a possible implementation, the fifth indication information is located in a message type identifier field of the third message, and the fifth indication information occupies at least two bits in the message type identifier field of the third message.

[0042] In a possible implementation, the third message is encapsulated in a payload field of a FEM frame, and a FEM port identifier in a frame header of a fiber to the room encapsulation mode FEM frame is used to indicate that the third message corresponds to the first slave device.

[0043] In a possible implementation, the FEM frame is encapsulated in a payload field of a data link layer DLL frame.

[0044] In a possible implementation, the method further includes:

[0045] The master device sends a fourth message to the first slave device, the fourth message is a WMCI message, the fourth message is used to manage or control the WLAN function of the first slave device, and the fourth message includes sixth indication information, the sixth indication information is used to indicate that the fourth message is used to manage the WLAN function in the second management type, the second management type corresponds to the second latency requirement or the second priority, and the second latency requirement is different from the first latency requirement, or the second priority is different from the first priority.

[0046] In a possible implementation, the master device is a master fiber to the room FTTR unit MFU, and the slave device is a slave FTTR unit SFU.

[0047] In a fourth aspect, the present application provides an optical network communication method applied to an optical fiber network, the optical fiber network comprising a master device and at least one slave device, the at least one slave device comprising a first slave device. The optical network communication method provided by the present application can be executed by the first slave device in the optical fiber network, or can be executed by a part of functional modules or chips in the first slave device. Taking the first slave device as an example, the first slave device receives a third message from the master device, the third message being a wireless local area network management control interface (WMCI) message, the third message being used for managing or controlling a wireless local area network (WLAN) function of the first slave device, the third message comprising fifth indication information, the fifth indication information being used for indicating a first management and control type of the WLAN function to which the third message is used for, the first management and control type corresponding to a first latency requirement or a first priority; and then, the first slave device manages and controls the first management and control type of the WLAN function based on the third indication information.

[0048] In the embodiment, the fifth indication information in the third message received by the first slave device can not only indicate the WLAN management and control type of the third message, but also correspond to the first latency requirement or the first priority, which is beneficial for the first slave device to decide whether to process the third message preferentially based on the fifth indication information, beneficial for reducing the bandwidth occupied by low-priority messages, and beneficial for improving the communication real-time performance of high-priority messages.

[0049] In a possible implementation, the first latency requirement corresponding to the first management and control type is different from a second latency requirement corresponding to a second management and control type, or the first priority corresponding to the first management and control type is different from a second priority corresponding to the second management and control type, the second management and control type being another management and control type of the WLAN function of the first slave device managed by the master device.

[0050] In a possible implementation, the first management and control type of the WLAN function is any one of WLAN data sending scheduling management and control, WLAN roaming management and control, or WLAN power adjustment management and control.

[0051] In a possible implementation, the fifth indication information is located in a message type identifier field of the third message, and the fifth indication information occupies at least two bits in the message type identifier field of the third message.

[0052] In a possible implementation, the first message is encapsulated in a payload field of a FEM frame, and a FEM port identifier in a frame header of a fiber to the room encapsulation mode (FEM) frame is used to indicate that the first message corresponds to the first slave device.

[0053] In a possible implementation, the FEM frame is encapsulated in a payload field of a data link layer (DLL) frame.

[0054] In a possible implementation, the method further comprises:

[0055] The first slave device receives a fourth message from the master device, the fourth message being a WMCI message, the fourth message being used for managing or controlling a WLAN function of the first slave device, the fourth message comprising sixth indication information, the sixth indication information being used for indicating a second management or control type of the fourth message for managing or controlling the WLAN function, the second management or control type corresponding to a second latency requirement or a second priority, the second latency requirement being different from the first latency requirement, or the second priority being different from the first priority, and the first slave device preferentially managing or controlling a first management or control type of the WLAN function corresponding to the third message in a case that the first latency requirement is a low latency requirement, the second latency requirement is a normal latency requirement, or the first priority is higher than the second priority.

[0056] In a possible implementation, the master device is a master fiber-to-the-room (FTTR) unit (MFU), and the slave device is a slave FTTR unit (SFU).

[0057] It should be noted that the embodiments of the present application have a variety of other specific implementation manners, and specific implementation manners and advantages thereof can be referred to the specific implementation manners of the first aspect, which will not be described here.

[0058] In a fifth aspect, the present application provides a communication device applied to a fiber network, the fiber network comprising a master device and at least one slave device, the at least one slave device comprising a first slave device. The communication device can be the master device in the fiber network, or can be a part of a functional module or a chip in the master device. The communication device comprises a transceiver and a processor. The processor is configured to generate a first message, the first message being a wireless local area network management control interface (WMCI) message, the first message being used for managing or controlling a wireless local area network (WLAN) function of the first slave device, the first message comprising first indication information, the first indication information being used for indicating a latency requirement or a priority of the WLAN function corresponding to the first message. The transceiver is configured to send the first message to the first slave device.

[0059] In a possible implementation, the processor is further configured to generate a second message, the second message being a WMCI message, the second message being used for managing or controlling the WLAN function of the first slave device, the second message comprising third indication information and fourth indication information, the third indication information being used for indicating the latency requirement or the priority of the WLAN function corresponding to the second message, the fourth indication information being used for indicating a second management or control type of the second message for managing or controlling the WLAN function, the second management or control type being different from the first management or control type, the latency requirement indicated by the third indication information being different from the latency requirement indicated by the first indication information, or the priority indicated by the third indication information being different from the priority indicated by the first indication information. The transceiver is further configured to send the second message to the first slave device.

[0060] It should be noted that the embodiments of the present application have a plurality of other specific implementation manners, and the specific implementation manners and advantages thereof can be referred to the specific implementation manners of the first aspect, which will not be described here.

[0061] In a sixth aspect, the present application provides a communication device applied to an optical fiber network, the optical fiber network comprising a master device and at least one slave device, the at least one slave device comprising a first slave device. The communication device can be the first slave device in the optical fiber network, or a part of a functional module or a chip in the first slave device. The communication device comprises a transceiver and a processor. The transceiver is configured to receive a first message from the master device, the first message being a wireless local area network management control interface (WMCI) message, the first message being used for managing or controlling a wireless local area network (WLAN) function of the first slave device, and the first message comprising first indication information, the first indication information being used for indicating a time delay requirement or a priority of the WLAN function corresponding to the first message. The processor is configured to manage and control the WLAN function corresponding to the first message based on the first indication information.

[0062] In a possible implementation manner, the transceiver is further configured to receive a second message from the master device, the second message being a WMCI message, the second message being used for managing or controlling the WLAN function of the first slave device, the second message comprising third indication information and fourth indication information, the third indication information being used for indicating a time delay requirement or a priority of the WLAN function corresponding to the second message, and the fourth indication information being used for indicating a second management and control type of the WLAN function managed and controlled by the second message, the second management and control type being different from the first management and control type, the time delay requirement indicated by the third indication information being different from the time delay requirement indicated by the first indication information, or the priority indicated by the third indication information being different from the priority indicated by the first indication information. In addition, in a case where the first indication information indicates a requirement of time delay control and the third indication information indicates a requirement of no time delay control, or the priority indicated by the first indication information is higher than the priority indicated by the third indication information, the processor is further configured to preferentially manage and control the WLAN function corresponding to the first message.

[0063] It should be noted that the embodiments of the present application have a plurality of other specific implementation manners, and the specific implementation manners and advantages thereof can be referred to the specific implementation manners of the first aspect, which will not be described here.

[0064] In a seventh aspect, the present application provides a communication device applied to an optical fiber network, the optical fiber network comprising a master device and at least one slave device, the at least one slave device comprising a first slave device. The communication device can be the master device in the optical fiber network, or a functional module or a chip in the master device. The communication device comprises a transceiver and a processor. The processor is configured to generate a third message, the third message being a wireless local area network management control interface (WMCI) message, the third message being used for managing or controlling a wireless local area network (WLAN) function of the first slave device, the third message comprising fifth indication information, the fifth indication information being used for indicating a first management and control type of the third message for managing or controlling the WLAN function, the first management and control type corresponding to a first latency requirement or a first priority. The transceiver is configured to send the third message to the first slave device.

[0065] In a possible implementation, the processor is configured to generate a fourth message, the fourth message being a WMCI message, the fourth message being used for managing or controlling the WLAN function of the first slave device, the fourth message comprising sixth indication information, the sixth indication information being used for indicating a second management and control type of the fourth message for managing or controlling the WLAN function, the second management and control type corresponding to a second latency requirement or a second priority, the second latency requirement being different from the first latency requirement, or the second priority being different from the first priority. The transceiver is configured to send the fourth message to the first slave device.

[0066] It should be noted that the embodiments of the present application have various other specific implementations, which can be referred to the specific implementations and advantages of the third aspect, and will not be described here.

[0067] In an eighth aspect, the present application provides a communication device applied to an optical fiber network, the optical fiber network comprising a master device and at least one slave device, the at least one slave device comprising a first slave device. The communication device can be the first slave device in the optical fiber network, or a functional module or a chip in the first slave device. The communication device comprises a transceiver and a processor. The transceiver is configured to receive a third message from the master device, the third message being a wireless local area network management control interface (WMCI) message, the third message being used for managing or controlling a wireless local area network (WLAN) function of the first slave device, the third message comprising fifth indication information, the fifth indication information being used for indicating a first management and control type of the third message for managing or controlling the WLAN function, the first management and control type corresponding to a first latency requirement or a first priority. The processor is configured to manage or control the first management and control type of the WLAN function based on the third indication information.

[0068] In a possible implementation, the transceiver is configured to receive a fourth message from the master device, the fourth message being a WMCI message, the fourth message being used for managing or controlling the WLAN function of the first slave device, and the fourth message comprising sixth indication information, the sixth indication information being used for indicating a second management or control type of the fourth message for managing or controlling the WLAN function, the second management or control type corresponding to a second latency requirement or a second priority, the second latency requirement being different from the first latency requirement, or the second priority being different from the first priority; and the processor is configured to, in a case that the first latency requirement is a low latency requirement, the second latency requirement is a normal latency requirement, or the first priority is higher than the second priority, preferentially manage or control the first management or control type of the WLAN function corresponding to the third message.

[0069] It should be noted that the embodiments of the present application have various other specific implementations, which can be referred to the specific implementations and advantages of the fourth aspect, and will not be described here.

[0070] In a ninth aspect, the embodiments of the present application provide a communication apparatus, which can be the master device in the foregoing embodiments, or a chip in the master device. The communication apparatus can include a processing module and a transceiving module. When the communication apparatus is the master device, the processing module can be a processor, and the transceiving module can be a transceiver. The master device can further include a storage module, which can be a memory. The storage module is configured to store instructions, and the processing module executes the instructions stored in the storage module, so that the master device executes the method in the first aspect or any implementation of the first aspect, or executes the method in the third aspect or any implementation of the third aspect. When the communication apparatus is a chip in the master device, the processing module can be a processor, and the transceiving module can be an input / output interface, a pin, or a circuit, etc. The processing module executes the instructions stored in the storage module, so that the master device executes the method in the first aspect or any implementation of the first aspect, or executes the method in the third aspect or any implementation of the third aspect. The storage module can be a storage module (e.g., a register, a cache, etc.) in the chip, or a storage module (e.g., a read-only memory, a random access memory, etc.) in the master device and located outside the chip.

[0071] In a tenth aspect, an embodiment of the present application provides a communication apparatus, which can be the slave device (e.g., the first slave device) in the foregoing embodiments, or a chip in the slave device (e.g., the first slave device). The communication apparatus can include a processing module and a transceiver module. When the communication apparatus is the slave device (e.g., the first slave device), the processing module can be a processor, and the transceiver module can be a transceiver. Optionally, the slave device (e.g., the first slave device) can further include a storage module, which can be a memory. The storage module is configured to store instructions, and the processing module executes the instructions stored in the storage module, so that the slave device (e.g., the first slave device) performs the method in the second aspect or any of the implementation forms of the second aspect, or performs the method in the fourth aspect or any of the implementation forms of the fourth aspect. When the communication apparatus is a chip in the slave device (e.g., the first slave device), the processing module can be a processor, and the transceiver module can be an input / output interface, a pin, or a circuit, etc. The processing module executes the instructions stored in the storage module, so that the slave device (e.g., the first slave device) performs the method in the second aspect or any of the implementation forms of the second aspect, or performs the method in the fourth aspect or any of the implementation forms of the fourth aspect. The storage module can be a storage module (e.g., a register, a cache, etc.) in the chip, or a storage module (e.g., a read-only memory, a random access memory, etc.) in the slave device (e.g., the first slave device) and located outside the chip.

[0072] In an eleventh aspect, the present application provides a communication apparatus, which can be an integrated circuit chip. The integrated circuit chip includes a processor. The processor is coupled with a memory, and the memory is configured to store programs or instructions. When the programs or instructions are executed by the processor, the communication apparatus performs the method introduced in any of the implementation forms of the various aspects and the various aspects.

[0073] In a twelfth aspect, an embodiment of the present application provides a computer program product including instructions, which, when executed on a computer, cause the computer to perform the method introduced in any of the implementation forms of the various aspects.

[0074] In a thirteenth aspect, an embodiment of the present application provides a computer-readable storage medium including instructions, which, when executed on a computer, cause the computer to perform the method introduced in any of the implementation forms of the various aspects.

[0075] In a fourteenth aspect, an embodiment of the present application provides an optical fiber network, which includes the master device in the third aspect and any of the implementation forms of the third aspect, and the slave device (e.g., the first slave device) in the fourth aspect and any of the implementation forms of the fourth aspect.

[0076] In a fifteenth aspect, an optical fiber network is provided, which includes the master device in the fifth aspect and any implementation of the fifth aspect, and the slave device (e.g., the first slave device) in the sixth aspect and any implementation of the sixth aspect. BRIEF DESCRIPTION OF DRAWINGS

[0077] FIG. 1A is an example diagram of a network architecture of an optical fiber network;

[0078] FIG. 1B is another example diagram of a network architecture of an optical fiber network;

[0079] FIG. 1C is an example diagram of an FTTR system;

[0080] FIG. 1D is an example diagram of a transmission manner of a WMCI message in a conventional technology;

[0081] FIG. 2 is a flow diagram of an optical network communication method in the present application;

[0082] FIG. 3A is an example diagram of an FEM frame encapsulating a WMCI message;

[0083] FIG. 3B is an example diagram of an XFEM frame encapsulating a WMCI message;

[0084] FIG. 3C is an example diagram of a DLL frame encapsulating an FEM frame;

[0085] FIG. 3D is an example diagram of a DLL frame encapsulating an XFEM frame;

[0086] FIG. 4 is another flow diagram of an optical network communication method in the present application;

[0087] FIG. 5 is an example diagram of a communication device in the present application;

[0088] FIG. 6 is another example diagram of a communication device in the present application. DETAILED DESCRIPTION

[0089] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all of the embodiments of the present application.

[0090] In various embodiments of the present application, the terms and / or descriptions of different embodiments are consistent and can be mutually referenced if there is no special description and logical conflict. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0091] The terms "first", "second", "third", "fourth", and the like in the description and in the claims of the present application, and in the above-described drawings if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of proper

[0092] It is to be understood that the term "and / or", merely describes association between associated objects, it is to be understood that there are three types of relationships, for example, A and / or B, it can mean that A exists alone, A and B exist together, B exists alone. In addition, the character " / " in this paper generally represents that the front and rear associated objects are a "or" relationship.

[0093] The optical network communication method provided in the present application is applied to an optical fiber network. FIG. 1A is an example diagram of an architecture of an optical fiber network in the prior art. As shown in FIG. 1A, the optical fiber network includes an optical line terminal (OLT), an optical distribution network (ODN), and an optical network unit (ONU) (or an optical network terminal (ONT)). The OLT and the ONU are connected and communicate through optical fibers. The OLT is generally connected with the ONU (or the ONT) through the ODN. The ODN includes a network of one or more optical devices such as optical fibers, an optical distribution frame (ODF), an optical splitter (also referred to as a splitter), a combiner, and the like. In addition, the foregoing OLT can be connected with an operator network through a network-side interface, the OLT can be connected with the ODN through a dedicated interface, and the ODN can be connected with the ONU (or the ONT) through a dedicated interface. In the downstream direction, the OLT broadcasts a downstream optical signal, and the downstream optical signal is distributed to each ONU (or ONT) through the ODN. In the upstream direction, a time division multiple access (TDMA) mode is adopted, and each ONU (or ONT) transmits an upstream optical signal in a respective upstream time slot allocated by the OLT. It should be noted that the present application does not limit the specific type of optical fiber, and the optical fiber described in the present application can be a single optical fiber, a loose-tube optical fiber, an optical cable, or an optical and electrical composite cable, etc.

[0094] FIG. IB is a structural schematic diagram of an optical fiber network provided by the present application. As shown in FIG. IB, the optical fiber network provided by the present application includes a master device 01 and at least one slave device 02, and the master device 01 is connected with the at least one slave device 02 through optical fibers. For example, the master device 01 is connected with the at least one slave device 02 through an optical distribution network. The master device 01 can manage or control the specific functions of one or more slave devices 02 based on at least one protocol. For example, the master device 01 can manage or control the wireless local area network (WLAN) functions of one or more slave devices 02 based on the WMCI protocol. It can be understood that the master device 01 and / or the slave device 02 has WLAN function; it can also be understood that the master device 01 and / or the slave device 02 has wireless fidelity (WiFi) function. For example, in a fiber to the room (FTTR) scenario, the master device 01 can be referred to as a main FTTR unit (MFU), an FTTR master device or a master gateway, and the slave device 02 can be referred to as a sub FTTR unit (SFU), an FTTR slave device or a slave gateway.

[0095] FIG. 1C is an example diagram of a network location of FTTR. As shown in FIG. 1C, FTTR is a network that performs optical fiber coverage inside a broadband customer network (for example, a home or an office) on the basis of FTTH / 0. The FTTR master device is connected with the FTTR slave devices in each room through optical fibers, and the FTTR master device and the FTTR slave devices can be connected with user terminals through wireless or wired interfaces, or can be connected with user terminal devices through an adapter device such as a set-top box. The device north of the FTTR master device is connected with an access node (AN) device as an access network network terminal, and the FTTR transceiver unit of the device south of the FTTR master device is connected with the FTTR transceiver unit of the FTTR slave device through an indoor fiber distribution network (IFDN), and also provides a gateway function and other network functions. The FTTR transceiver unit of the FTTR slave device is connected with the TTTP transceiver unit of the FTTR master device through the indoor fiber distribution network, and provides terminal access through a wireless or wired interface. The indoor fiber distribution network is a point-to-multipoint optical fiber infrastructure, can be completely passive, and is usually composed of passive devices such as optical cables and optical splitters connected with each other, and can also provide remote power supply functions for the FTTR slave device by using optical-electric hybrid cables and optical-electric hybrid splitters.

[0096] For example, as shown in FIG. 1D, in the FTTR system management architecture, different management requirements and characteristics of the same WLAN function of the slave device or the same management type can have different latency requirements. For example, the messages of the management type 1 and the messages of the management type 2 between the master device and the slave device 1 in FIG. 1D are transmitted through the WMCI management channel, and the messages of the management type 1 and the messages of the management type 2 between the master device and the slave device 2 are also transmitted through the WMCI management channel. The same management type or different management types can have different latency requirements. The unified message format (for example, the current WMCI message format) cannot distinguish different latency requirements, which is not conducive to efficient management or control of the WLAN function of the slave device by the master device.

[0097] To this end, the present application provides an optical network communication method and a communication device for identifying messages with different latency requirements or priorities in the same management channel, and improving the efficiency of management or control of the WLAN function of the slave device by the master device.

[0098] The main flow of the optical network communication method provided by the present application will be introduced below in combination with FIG. 2:

[0099] As shown in FIG. 2, it is a flowchart of the optical network communication method provided by the present application. The optical network communication method is illustrated by taking the interaction between the master device and the first slave device as an example. Of course, the subject performing the action of the master device in the method can also be a device, a module or a chip in the master device; the subject performing the action of the first slave device in the method can also be a device, a module or a chip in the first slave device, which is not limited in the embodiment. For example, as shown in FIG. 2, the optical network communication method includes the following steps:

[0100] Step 201, the master device sends a first message to the first slave device; correspondingly, the first slave device receives the first message from the master device.

[0101] For example, the master device sends the first message to the first slave device through an optical fiber or a composite cable; correspondingly, the first slave device receives the first message from the master device through the optical fiber or the composite cable.

[0102] The first message is a WMCI message, which is used to manage or control (hereinafter referred to as management or control) the WLAN function of the first slave device. The first message includes first indication information, which is used to indicate the latency requirement or the priority of the first message. For example, the first indication information is used to indicate the latency requirement of the first message. For another example, the first indication information is used to indicate the priority of the first message. Since the first message is used to manage or control a certain WLAN function, the first indication information can also be understood as indicating the latency requirement or the priority of the WLAN function corresponding to the first message.

[0103] The latency requirement can include a transmission latency requirement and / or a processing latency requirement. For example, the requirement of low latency control or the requirement of real-time control means that the processing latency and / or the transmission latency should be controlled within a preset range; the non-requirement of low latency control or the non-requirement of real-time control, also referred to as normal control, means that the processing latency and / or the transmission latency can meet the system requirement. For ease of introduction, the message requiring low latency control (or requiring real-time control) is referred to as a low latency control message, and the message not requiring low latency control (or not requiring real-time control) is referred to as a normal control message. The latency of the low latency control message is lower than the latency of the normal control message. It can also be understood that the priority of the low latency control message is higher than the priority of the normal control message. For example, when the same device receives a low latency control message and a normal latency control message, the device processes the low latency control message first. This is beneficial to reduce the bandwidth occupied by the normal latency control message, and is beneficial to improve the communication real-time performance of the low latency control message, and thus is beneficial to improve the management and control efficiency of the master device on the WLAN function of the slave device.

[0104] The priority refers to a parameter for determining the priority level of each message to accept the internal resource when processing or transmitting multiple messages. In this embodiment, the priority refers to the level of each message being processed or transmitted preferentially when the slave device (for example, the first slave device) processes multiple messages for managing and controlling the WLAN function. For example, if the first device receives message 1 and message 2 from the master device, respectively, wherein the priority indicated by the indication information in the message 1 is higher than the priority indicated by the indication information in the message 2, the first device preferentially manages and controls the WLAN function of the first slave device based on the message 1. This is beneficial to reduce the bandwidth occupied by the low-priority message, and is beneficial to improve the communication real-time performance of the high-priority message, and thus is beneficial to improve the management and control efficiency of the master device on the WLAN function of the slave device.

[0105] Specifically, the first indication information can adopt any one of the following implementation manners:

[0106] In one possible implementation manner, the first indication information includes a first value or a second value. The first value is used to indicate the requirement of latency control, that is, to indicate that the message (for example, the first message) carrying the first indication information is a low latency control message; and the second value is used to indicate the non-requirement of latency control, that is, to indicate that the message (for example, the first message) carrying the first indication information is a normal control message.

[0107] Optionally, the first indication information is represented by at least one bit newly defined in the WMCI message. In an example, the first indication information is one bit newly defined in the WMCI message, i.e., the first value and the second value are two values of the newly defined one bit. The two values of the bit respectively indicate the low-latency control message and the normal control message. For example, the value of the bit is 1, indicating that the first message is the low-latency control message, and the value of the bit is 0, indicating that the first message is the normal control message; or the value of the bit is 0, indicating that the first message is the low-latency control message, and the value of the bit is 1, indicating that the first message is the normal control message. In another example, the first indication information is two bits newly defined in the WMCI message, i.e., the first value and the second value are two values of the newly defined two bits. The two values of the bit respectively indicate the low-latency control message and the normal control message. For example, the value of the two bits is 01, indicating that the first message is the low-latency control message, and the value of the two bits is 00, indicating that the first message is the normal control message; or the value of the two bits is 11, indicating that the first message is the low-latency control message, and the value of the two bits is 00, indicating that the first message is the normal control message. The embodiment does not limit the specific implementation of the first value and the second value, and only guarantees that the first value is different from the second value.

[0108] Optionally, the first indication information is located in a message type identifier field of the first message, or the first indication information is located in a message length field of the first message. The message type identifier field is used to indicate the type of the first message, and the message length field is used to indicate the length of the message content carried by the first message. For example, the first indication information is located in the highest bit or the highest two bits of the message type identifier field; or the first indication information is located in the highest bit or the highest two bits of the first byte of the message length field.

[0109] For example, Table 1 below is an example of the first message in the embodiment.

[0110] Table 1

[0111] As shown in Table 1, the first byte is a message type identification field (may also be referred to as a message type ID field), used to indicate the type of the message and define the semantics of the message content. The second byte is a sequence number field, containing a sequence number counter, used to ensure the robustness of the WMCI message passing channel. In the downlink direction, the sequence number field fills the value of the sequence number counter of the corresponding master device. The master device maintains a separate sequence number counter for each slave device unicast and broadcast WMCI message stream. Each sequence number counter rolls from 255 to 1, and the value 0 is not used in the downlink. The third and fourth bytes are a message content length field, used to indicate the number of bytes of the message content of the message. The fifth to Nth bytes are a message content field, used to carry the specific content of the message, related to the specific message. Among them, the fifth and sixth bytes are used to carry the parameter mask, and the seventh to Nth bytes are used to carry the parameter content of the parameter indicated by the parameter mask, which should be filled into the message content in the order indicated by the parameter mask. Wherein, N is an integer greater than 7. The (N+1)th to (N+4)th bytes are a message integrity check field, 4 bytes in size, used to verify the identity of the sender and prevent fake WMCI message attacks, and the field function follows the cyclic redundancy check (CRC) function.

[0112] In the example shown in Table 1, if the first indication information is carried in the message type identification field, and the first indication information is represented by 1 bit, the first indication information can be located in the highest bit X of the message type identification field, i.e. the 8th bit of the first byte of the first message. If the first indication information is carried in the message type identification field, and the first indication information is represented by 2 bits, the first indication information can be located in the highest 2 bits of the message type identification field, i.e. the 7th and 8th bits of the first byte of the first message. If the first indication information is carried in the message length field, and the first indication information is represented by 1 bit, the first indication information can be located in the highest bit Y of the message length field, i.e. the 8th bit of the third byte of the first message. If the first indication information is carried in the message length field, and the first indication information is represented by 2 bits, the first indication information can be located in the highest 2 bits of the message length field, i.e. the 7th and 8th bits of the third byte of the first message.

[0113] In this embodiment, the first indication information in the first message sent by the master device to the first slave device can indicate the delay requirement, i.e. indicate whether the first message is a low-latency control message or a normal control message, which is conducive to the first slave device deciding whether to prioritize processing the first message based on the first indication information, reducing the bandwidth occupied by normal latency control messages, and improving the communication real-time performance of low-latency control messages.

[0114] In another possible implementation, the first indication information includes at least two values, and different values of the at least two values respectively indicate different priorities. For example, the first indication information includes two values, and the two values respectively indicate a low priority and a high priority, i.e., indicate that the message (e.g., the first message) carrying the first indication information is a low priority message or a high priority message. For another example, the first indication information includes three values, and the three values respectively indicate a low priority, a medium priority and a high priority.

[0115] Optionally, the first indication information is represented by at least one newly defined bit in the WMCI message. In an example, the first indication information is one newly defined bit in the WMCI message, and two values of the bit respectively indicate a low priority and a high priority. For example, the bit has a value of 0, indicating that the first message is a low priority message, and the bit has a value of 1, indicating that the first message is a high priority message; or the bit has a value of 1, indicating that the first message is a low priority message, and the bit has a value of 0, indicating that the first message is a high priority message. In another example, the first indication information is two newly defined bits in the WMCI message, and the two bits can indicate at most four priorities. For example, the two bits have values including 00 and 11, where 00 indicates that the first message is a low priority message, and 11 indicates that the first message is a high priority message. For another example, the two bits have values including 00, 01 and 10, where 00 indicates that the first message is a low priority message, 01 indicates that the first message is a medium priority message, and 10 indicates that the first message is a high priority message. For yet another example, the two bits have values including 00, 01, 10 and 11, and the priorities increase in turn from 00, 01, 10 to 11. It should be noted that more bits can be newly defined in the WMCI message to indicate more kinds of priorities, which are not listed here.

[0116] Optionally, the first indication information is located in a message type identifier field of the first message, or the first indication information is located in a message length field of the first message. For example, the first indication information is located in the highest bit or the highest two bits of the message type identifier field, or the first indication information is located in the highest bit or the highest two bits of the first byte of the message length field.

[0117] For example, Table 2 below is an example of the first message in the embodiment.

[0118] Table 2

[0119] The meanings of the partial fields shown in Table 2 are the same as those of the example shown in Table 1, and please refer to the relevant description of Table 1 for details, which will not be repeated here.

[0120] In the example shown in Table 2, if the first indication information is carried in the message type identification field, and the first indication information is represented by 2 bits, the first indication information can be located in the highest 2 bits XX of the message type identification field, i.e., the 7th-8th bits of the 1st byte of the first message. If the first indication information is carried in the message length field, and the first indication information is represented by 2 bits, the first indication information can be located in the highest 2 bits YY of the message length field, i.e., the 7th-8th bits of the 3rd byte of the first message.

[0121] It should be noted that the names of the fields in the example shown in Table 1 or Table 2 are only examples, and in actual applications, the fields shown in Table 1 or Table 2 can also use other approximate names, and the application does not limit the names of the fields in the first message. In addition, the order between the fields in the message shown in Table 1 or Table 2 can be changed, and the application does not limit the arrangement order of the fields in the first message.

[0122] In this embodiment, the first indication information in the first message sent by the master device to the first slave device can indicate the priority of the first message, i.e., indicate whether the first message has a lower priority or a higher priority relative to other WMCI messages, which is beneficial to the first slave device to decide whether to process the first message preferentially based on the first indication information, reduce the bandwidth occupied by low-priority messages, and improve the communication real-time performance of high-priority messages. In addition, by indicating the priority through the first indication information, the first slave device can construct a message priority queue based on the same channel, implement QoS guarantee of the WMCI management channel for queues of different priorities, and improve the working efficiency of the WMCI.

[0123] The first indication information in this embodiment can be implemented by using any of the foregoing embodiments, which is limited here. In this embodiment, by adding a specific field to carry the first indication information in the WMCI managed message, the real-time requirement or priority of the message for transmission and processing is distinguished, and QoS management of the same message channel is implemented.

[0124] Optionally, the first message further includes second indication information, and the second indication information is used to indicate the management type of the first message. The first message is used to manage a WLAN function, and therefore, the second indication information can also be understood as being used to indicate the management type of the WLAN function managed by the first message. The management type is any one of WLAN data sending scheduling management, WLAN roaming management, or WLAN power adjustment management. If the second indication information indicates that the first message is used to manage a first management type of the WLAN function, the first indication information is further used to indicate the latency requirement or priority of the first management type of the WLAN function.

[0125] For example, the second indication information is carried in the message type identification field of the first message, as shown in Table 1 or Table 2. For example, the lower 6 bits Z in the message type identification field are used to carry the second indication information, i.e., the first 6 bits of the first byte of the first message. For example, the second indication information carried in the message type identification field has a value of 1, indicating WLAN data transmission scheduling control; the second indication information carried in the message type identification field has a value of 2, indicating WLAN roaming control; and the second indication information carried in the message type identification field has a value of 3, indicating WLAN power adjustment control. In actual applications, the message type identification field can also define other types of messages, which are not listed one by one here.

[0126] It should be noted that the master device sends the first message to the first slave device through the WMCI management channel; correspondingly, the first slave device receives the first message from the master device through the WMCI management channel. The management channel refers to a logical channel established between the master device and the slave device for transmitting messages. The WMCI management channel is a logical channel established between the master device and the first slave device for transmitting WMCI messages. Generally, different management channels correspond to different logical port identifications (port IDs). Different logical port identifications can correspond to the same physical transceiving port, or can correspond to different physical transceiving ports, which are not limited here. For example, the first management channel corresponds to Port ID1 of the master device and port ID1 of the first slave device, and other management channels correspond to Port ID2 of the master device and port ID2 of the first slave device. Port ID1 and Port ID2 can correspond to the same physical transceiving port, or can correspond to different physical transceiving ports.

[0127] Further, as shown in FIG. 3A, if the rate level of the master device is 2.5G, the first message is encapsulated in a payload field of an FTTR encapsulation method (FEM) frame, and a FEM port ID in a frame header of the FEM frame is assigned by the master device, which can not only indicate that the first message is a WMCI message, but also be used to indicate a transceiving object of the WMCI message (i.e., the first message), i.e., indicate that the WMCI message (i.e., the first message) corresponds to the first slave device instead of other slave devices. Therefore, the WMCI message can be distinguished from other management messages (e.g., FMCI messages or OMCI messages) in the FTTR system through the FEM port ID. It should be noted that, in the case that the rate level of the master device is 2.5G, the downlink rate of the master device is 2.48832 Gbit / s; the uplink rate of the master device can be 1.24416 Gbit / s, or 2.48832 Gbit / s, or simultaneously support 1.24416 Gbit / s and 2.48832 Gbit / s. The downlink rate of the slave device is 2.48832 Gbit / s, and the uplink rate of the slave device is 1.24416 Gbit / s or 2.48832 Gbit / s. It should be noted that the payload length L of the FEM frame is equal to the length L of the WMCI message, and L is an integer greater than 0.

[0128] In addition, as shown in FIG. 3B, if the rate level of the master device is 10G, the first message is encapsulated in the payload field of a 10G-FTTR encapsulation method (XFEM) frame, and an XFEM port ID in the frame header of the XFEM frame is assigned by the master device, which can not only indicate that the first message is a WMCI message, but also be used to indicate the transceiving object of the WMCI message (i.e., the first message), i.e., indicate that the WMCI message (i.e., the first message) corresponds to the first slave device instead of other slave devices. Therefore, the WMCI message can be distinguished from other management messages in the FTTR system through the XFEM port ID. It should be noted that, in the case where the rate level of the master device is 10G, the downlink rate of the master device is 9.95328 Gbit / s; the uplink rate of the master device can be 9.95328 Gbit / s, or 2.48832 Gbit / s, or both 9.95328 Gbit / s and 2.48832 Gbit / s. The downlink rate of the slave device is 9.95328 Gbit / s, and the uplink rate is 9.95328 Gbit / s or 2.48832 Gbit / s. It should be noted that the payload length P of the XFEM frame is an integer multiple of 4 bytes, but the length of the WMCI message can not be an integer multiple of 4 bytes, and therefore, the XFEM payload can need to add a padding field of 0-3 bytes when carrying the WMCI message.

[0129] In addition, as shown in FIG. 3C, the FEM frame is encapsulated in the payload field of a data link layer (DLL) frame. As shown in FIG. 3D, the XFEM frame is encapsulated in the payload field of a DLL frame. The DLL frame is composed of a DLL frame header and a DLL frame payload part. The DLL payload is formed at the sending side and is processed by a service adaptation sublayer at the receiving side. The DLL frame header is composed of 3 fixed-size partitions (i.e., PLOAMd, BIP, Plend) and a variable-size partition: a bandwidth mapping partition (BWmap), which is used to indicate the uplink transmission positions of different slave devices in the corresponding uplink physical frames (PHY frames).

[0130] It should be noted that, in the example shown in FIG. 3C, only the payload of the DLL frame contains 3 FEM frames as an example, and in actual applications, the payload of the DLL frame can contain other numbers of FEM frames, which are not limited here. In the example shown in FIG. 3D, only the payload of the DLL frame contains 3 XFEM frames as an example, and in actual applications, the payload of the DLL frame can contain other numbers of XFEM frames, which are not limited here.

[0131] At step 202, the first slave device controls the WLAN function corresponding to the first message based on the first indication information.

[0132] If the priority indicated by the first indication information in the first message is higher than the priority indicated by the indication information in the other message, or the first indication information in the first message indicates a time delay requirement, the first slave device processes the first message preferentially, i.e., the first slave device preferentially controls the WLAN function corresponding to the first message based on the first message.

[0133] It should be noted that the WMCI messages with different time delay requirements or priorities can indicate different control types of the WLAN. For example, the first slave device receives a first message and a second message from the master device, the first message is the WMCI message as described above, and the second message is a WMCI message for managing or controlling the WLAN function of the first slave device. The second message includes third indication information and fourth indication information, wherein the third indication information is used to indicate the time delay requirement or the priority of the WLAN function corresponding to the second message, and the fourth indication information is used to indicate a second control type of the WLAN function controlled by the second message. Optionally, the second control type is different from the first control type, the time delay requirement indicated by the third indication information is different from the time delay requirement indicated by the first indication information, or the priority indicated by the third indication information is different from the priority indicated by the first indication information. In the case that the first indication information indicates a time delay control requirement and the third indication information indicates no time delay control requirement, or the priority indicated by the first indication information is higher than the priority indicated by the third indication information, the first slave device preferentially controls the first control type of the WLAN function corresponding to the first message.

[0134] It should be further explained that the WMCI message with different latency requirement or priority can also indicate the same management type of the WLAN. For example, the first slave device receives the first message from the master device and the second message from the master device, the first message is described above, and the second message is a WMCI message for managing or controlling the WLAN function of the first slave device. The second message includes third indication information and fourth indication information, wherein the third indication information is used to indicate the latency requirement or the priority of the WLAN function corresponding to the second message, and the fourth indication information is used to indicate the second management type of the WLAN function corresponding to the second message. Optionally, the second management type is the same as the first management type, but the latency requirement indicated by the third indication information is different from the latency requirement indicated by the first indication information, or the priority indicated by the third indication information is different from the priority indicated by the first indication information. In the case that the first indication information indicates the latency control requirement and the third indication information indicates no latency control requirement, or the priority indicated by the first indication information is higher than the priority indicated by the third indication information, the first slave device preferentially manages the first management type of the WLAN function corresponding to the first message.

[0135] In this embodiment, the first indication information in the first message sent by the master device to the first slave device can indicate the priority or the latency requirement of the first message, which is beneficial to the first slave device to decide whether to preferentially process the first message based on the first indication information, reduce the bandwidth occupied by the low-priority message or the message with ordinary latency requirement, and improve the communication real-time performance of the high-priority message or the message with low latency requirement.

[0136] As shown in FIG. 4, a flowchart of the optical network communication method provided by the present application is shown. The optical network communication method is described by taking the interaction between the master device and the first slave device as an example. Of course, the subject performing the action of the master device in the method can also be a device, a module or a chip in the master device, and the subject performing the action of the first slave device in the method can also be a device, a module or a chip in the first slave device, which is not limited in the embodiment. For example, as shown in FIG. 4, the optical network communication method includes the following steps:

[0137] In step 401, the master device sends a third message to the first slave device; correspondingly, the first slave device receives the third message from the master device.

[0138] For example, the master device sends the third message to the first slave device through an optical fiber or a composite cable; correspondingly, the first slave device receives the third message from the master device through the optical fiber or the composite cable.

[0139] The third message is a WMCI message, and the third message is used to manage or control the WLAN function of the first slave device. The third message includes fifth indication information, and the fifth indication information is used to indicate a first management or control type of the third message for managing or controlling the WLAN function. The first management or control type corresponds to the first latency requirement or the first priority. That is, the first management or control type corresponds to a specific latency requirement or priority (i.e., the first latency requirement or the first priority), and the first management or control type has a binding relationship with the specific latency requirement or priority (i.e., the first latency requirement or the first priority). The third message does not need to carry indication information for indicating the latency requirement or the priority, and the first management or control type can indicate that the third message has the first latency requirement or has the first priority. For the explanation of the latency requirement and the priority, please refer to the related description in step 201 in the foregoing, which will not be repeated here.

[0140] Optionally, the management or control type of the WLAN function is any one of WLAN data sending scheduling management or control, WLAN roaming management or control, or WLAN power adjustment management or control. Optionally, different management or control types can correspond to different latency requirements or different priorities. For example, the first latency requirement corresponding to the first management or control type is different from the second latency requirement corresponding to the second management or control type, or the first priority corresponding to the first management or control type is different from the second priority corresponding to the second management or control type. The second management or control type is a management or control type indicated by another message received by the first slave device.

[0141] For example, the WLAN data sending scheduling management or control corresponds to a low latency requirement, the WLAN roaming management or control corresponds to a low latency requirement, and the WLAN power adjustment management or control corresponds to an ordinary latency requirement; or the WLAN power adjustment management or control corresponds to a low priority, the WLAN data sending scheduling management or control corresponds to a high priority, and the WLAN roaming management or control corresponds to a medium priority. For example, if the first management or control type is the WLAN data sending scheduling management or control, the first slave device can determine, based on the fifth indication information in the third message, that the third message is used to manage or control the WLAN data sending scheduling, and the WLAN data sending scheduling management or control corresponds to a low latency requirement or a high priority. For another example, if the first management or control type is the WLAN power adjustment management or control, the first slave device can determine, based on the fifth indication information in the third message, that the third message is used to manage or control the sending power of the WLAN, and the WLAN power adjustment management or control corresponds to an ordinary latency requirement or a low priority.

[0142] Optionally, the fifth indication information is located in a message type identifier field of the third message. Optionally, the fifth indication information occupies at least two bits in the message type identifier field of the third message.

[0143] For example, Table 3 in the following is an example of the third message in the embodiment.

[0144] Table 3

[0145] The meanings of the partial fields shown in Table 3 are the same as those in the example shown in Table 1, and please refer to the relevant description of Table 1 for details, which will not be repeated here. In the example shown in Table 3, the fifth indication information is carried in the message type identifier field of the third message. For example, the lower 6 bits Z in the message type identifier field are used to carry the fifth indication information, i.e., the first 1-6 bits of the first byte of the third message. For example, the fifth indication information carried by the message type identifier field has a value of 1, indicating WLAN data transmission scheduling control, corresponding to low latency demand or high priority; the value carried by the message type identifier field is 2, indicating WLAN roaming control, corresponding to low latency demand or medium priority; the value carried by the message type identifier field is 3, indicating WLAN power adjustment control, corresponding to ordinary latency demand or low priority. In actual applications, the message type identifier field can also define other control types, and the latency demand or priority of different control types can also be adjusted or defined as needed, which will not be listed one by one here.

[0146] In this embodiment, the master device sends the third message to the first slave device through the WMCI management channel; correspondingly, the first slave device receives the third message from the master device through the WMCI management channel. In addition, the third message is encapsulated in the payload field of the FEM frame, or the third message is encapsulated in the XFEM frame. As shown in FIG. 3A, the FEM port identifier (FEM port ID) in the frame header of the FEM frame is allocated by the master device, which can not only indicate that the third message is a WMCI message, but also be used to indicate the transceiving object of the WMCI message (i.e., the third message), i.e., to indicate that the WMCI message (i.e., the third message) corresponds to the first slave device rather than other slave devices. Therefore, the WMCI message can be distinguished from other control messages (e.g., FMCI messages or OMCI messages) in the FTTR system through the FEM port identifier. As shown in FIG. 3B, the XFEM port identifier (XFEM port ID) in the frame header of the XFEM frame is allocated by the master device, which can not only indicate that the third message is a WMCI message, but also be used to indicate the transceiving object of the WMCI message (i.e., the third message), i.e., to indicate that the WMCI message (i.e., the third message) corresponds to the first slave device rather than other slave devices. Therefore, the WMCI message can be distinguished from other control messages in the FTTR system through the XFEM port identifier.

[0147] Optionally, the FEM frame is encapsulated in a payload field of the DLL frame. For the encapsulation of the FEM frame in the DLL frame, refer to the related description of FIG. 3C, which will not be repeated here. For the encapsulation of the XFEM frame in the DLL frame, refer to the related description of FIG. 3D, which will not be repeated here.

[0148] At step 402, the first slave device controls the WLAN function corresponding to the third message based on the fifth indication information.

[0149] If the priority indicated by the fifth indication information in the third message is higher than the priority indicated by the control type of the other message, or the fifth indication information in the third message indicates that the third message has a latency requirement, the first slave device preferentially processes the third message, that is, the first slave device preferentially controls the first control type of the WLAN function corresponding to the third message based on the third message.

[0150] Optionally, the first latency requirement corresponding to the first control type is different from the second latency requirement corresponding to the second control type, or the first priority corresponding to the first control type is different from the second priority corresponding to the second control type.

[0151] For example, the first slave device receives the third message and the fourth message from the master device, the third message is described above, and the fourth message is a WMCI message, the fourth message is used to manage or control the WLAN function of the first slave device. The fourth message includes sixth indication information, the sixth indication information is used to indicate that the fourth message is used to control the second control type of the WLAN function, the second control type corresponds to the second latency requirement or the second priority, the second latency requirement is different from the first latency requirement, or the second priority is different from the first priority. In the case that the first latency requirement is a low latency requirement, the second latency requirement is a normal latency requirement, or the first priority is higher than the second priority, the first slave device preferentially controls the first control type of the WLAN function corresponding to the third message.

[0152] In this embodiment, the fifth indication information in the third message sent by the master device to the first slave device can not only indicate the WLAN control type of the third message, but also correspond to the first latency requirement or the first priority, which is beneficial to the first slave device to decide whether to preferentially process the third message based on the fifth indication information, beneficial to reduce the bandwidth occupied by the low-priority message, and beneficial to improve the communication real-time performance of the high-priority message.

[0153] Further, the embodiment of the present application further provides a communication device 50, as shown in Figure 5, which is a structural schematic diagram of the communication device 50 provided by the embodiment of the present application. The specific implementation of the master device and the slave device (for example, the first slave device) in the flowcharts shown in Figure 2 or Figure 4 can refer to the internal structure of the communication device 50 shown in Figure 5. When the communication device 50 is used to implement the function of the master device in the method shown in Figure 2 or Figure 4, the communication device 50 can be a master gateway or an MFU. When the communication device 50 is used to implement the function of the slave device in the method shown in Figure 2 or Figure 4, the communication device 50 can be a slave gateway or an SFU.

[0154] As shown in Figure 5, the communication device 50 can include a processor 501 and a transceiver 502, and the processor 501 is coupled with the transceiver 502. The aforementioned processor 501 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The aforementioned PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof. The processor 501 can refer to one processor, and can also include a plurality of processors, which is not limited specifically herein.

[0155] The aforementioned transceiver 502 can also be referred to as a transceiving unit, a transceiver, a transceiving device, etc. Optionally, the devices in the transceiving unit for implementing the receiving function can be regarded as a receiving unit, and the devices in the transceiving unit for implementing the sending function can be regarded as a sending unit, that is, the transceiving unit includes the receiving unit and the sending unit. The receiving unit can also be referred to as a receiver, an input port, a receiving circuit, etc., and the sending unit can be referred to as a transmitter, a transmitter or a transmitting circuit, etc.

[0156] Optionally, the communication apparatus 50 further comprises a memory 503. The processor 501 is coupled to the memory 503. The memory 503 is mainly used for storing software programs and data. The memory 503 can exist independently, and be connected to the processor 501. Alternatively, the memory 503 can be integrated with the processor 501, for example, integrated in one or more chips. The memory 503 can store program codes for implementing the technical solutions of the embodiments of the present application, and the execution is controlled by the processor 501. The executed computer programs of various types can also be regarded as the driver of the processor 501. The memory 503 can include volatile memory (volatile memory), such as random access memory (random-access memory, RAM); the memory can also include non-volatile memory (non-volatile memory), such as read-only memory (read-only memory, ROM), flash memory (flash memory), hard disk drive (hard disk drive, HDD) or solid-state drive (solid-state drive, SSD); the memory 503 can also include a combination of the above types of memory. The memory 503 can refer to one memory, or can include multiple memories. For example, the memory 503 is used to store various data.

[0157] In one implementation, the communication apparatus 50 is configured to implement the function of the master device in the method embodiment of FIG. 2. Specifically, the processor 501 is configured to generate a first message, the first message being a wireless local area network management control interface (WMCI) message, the first message being used for managing or controlling a wireless local area network (WLAN) function of a first slave device, the first message comprising first indication information, the first indication information being used for indicating a latency requirement or a priority of the WLAN function corresponding to the first message. The transceiver 502 is configured to transmit the first message to the first slave device.

[0158] In one possible implementation, the first indication information comprises a first value or a second value, the first value being used for indicating a requirement of latency control, and the second value being used for indicating a requirement of no latency control. Optionally, the first indication information is located in a message type identifier field of the first message; or the first indication information is located in a message length field of the first message.

[0159] In another possible implementation, the first indication information comprises at least two values, different values of the at least two values respectively indicating different priorities. Optionally, the first indication information is located in a message type identifier field of the first message; or the first indication information is located in a message length field of the first message.

[0160] In a possible implementation, the first message further comprises second indication information, the second indication information being used to indicate a first management type of the WLAN function to which the first message is used to manage or control, and the first indication information is further used to indicate a latency requirement or a priority of the first management type of the WLAN function. Optionally, the first management type of the WLAN function is any one of WLAN data transmission scheduling management, WLAN roaming management, or WLAN power adjustment management.

[0161] In a possible implementation, the first message is encapsulated in a payload field of a FEM frame, and a FEM port identifier in a frame header of the FEM frame is used to indicate that the first message corresponds to the first slave device. Optionally, the FEM frame is encapsulated in a payload field of a data link layer (DLL) frame.

[0162] In a possible implementation, the processor 501 is further configured to generate a second message, the second message being a WMCI message, the second message being used to manage or control the WLAN function of the first slave device, the second message comprising third indication information and fourth indication information, the third indication information being used to indicate a latency requirement or a priority of the WLAN function to which the second message corresponds, and the fourth indication information being used to indicate a second management type of the WLAN function to which the second message is used to manage or control, the second management type being different from the first management type, the latency requirement indicated by the third indication information being different from the latency requirement indicated by the first indication information, or the priority indicated by the third indication information being different from the priority indicated by the first indication information. The transceiver 502 is further configured to send the second message to the first slave device.

[0163] In another implementation, the communication apparatus 50 is configured to implement the function of a slave device (e.g., the first slave device) in the method embodiment of FIG. 2. Specifically, the transceiver 502 is configured to receive a first message from a master device, the first message being a wireless management control interface (WMCI) message, the first message being used to manage or control a WLAN function of the first slave device, and the first message comprising first indication information, the first indication information being used to indicate a latency requirement or a priority of the WLAN function to which the first message corresponds. The processor 501 is configured to manage or control the WLAN function to which the first message corresponds based on the first indication information.

[0164] In a possible implementation, the transceiver 502 is further configured to receive a second message from the master device, the second message being a WMCI message, the second message being used for managing or controlling the WLAN function of the first slave device, the second message comprising third indication information and fourth indication information, the third indication information being used for indicating a time delay requirement or a priority of the WLAN function corresponding to the second message, the fourth indication information being used for indicating a second management type of the WLAN function to which the second message is used for management or control, the second management type being different from the first management type, the third indication information indicating a time delay requirement different from the time delay requirement indicated by the first indication information, or the third indication information indicating a priority different from the priority indicated by the first indication information. The processor 501 is further configured to preferentially manage or control the WLAN function corresponding to the first message in a case that the first indication information indicates a requirement of time delay control and the third indication information indicates a requirement of no time delay control, or the priority indicated by the first indication information is higher than the priority indicated by the third indication information. For example, the communication apparatus 50 preferentially allocates a processing resource in the processor 501 to a queue used for processing the first message.

[0165] In an implementation, the communication apparatus 50 is configured to implement the function of the master device in the method embodiment corresponding to FIG. 4. Specifically, the processor 501 is configured to generate a third message, the third message being a WMCI message, the third message being used for managing or controlling a WLAN function of a first slave device, the third message comprising fifth indication information, the fifth indication information being used for indicating a first management type of the WLAN function to which the third message is used for management or control, the first management type corresponding to a first time delay requirement or a first priority. The transceiver 502 is configured to send the third message to the first slave device.

[0166] In a possible implementation, the first time delay requirement corresponding to the first management type is different from a second time delay requirement corresponding to a second management type, or the first priority corresponding to the first management type is different from a second priority corresponding to the second management type, the second management type being another management type of the WLAN function of the first slave device managed by the master device. Optionally, the first management type of the WLAN function is any one of WLAN data sending scheduling management, WLAN roaming management, or WLAN power adjustment management.

[0167] In a possible implementation, the fifth indication information is located in a message type identifier field of the third message, and the fifth indication information occupies at least two bits in the message type identifier field of the third message.

[0168] In a possible implementation, the third message is encapsulated in a payload field of the FEM frame, and the FEM port identification in the frame header of the fiber-to-the-room encapsulation mode FEM frame is used to indicate that the third message corresponds to the first slave device. Optionally, the FEM frame is encapsulated in a payload field of a data link layer (DLL) frame.

[0169] In a possible implementation, the processor 501 is further configured to generate a fourth message, the fourth message being a WMCI message, the fourth message being used for management or control of a WLAN function of the first slave device, the fourth message comprising sixth indication information, the sixth indication information being used to indicate a second management or control type of the WLAN function to which the fourth message is used for management or control, the second management or control type corresponding to a second latency requirement or a second priority, the second latency requirement being different from the first latency requirement, or the second priority being different from the first priority. The transceiver 502 is further configured to send the fourth message to the first slave device.

[0170] In another implementation, the communication apparatus 50 is configured to implement the function of a slave device (e.g., the first slave device) in the method embodiment of FIG. 4. Specifically, the transceiver 502 is configured to receive a third message from a master device, the third message being a wireless management control interface (WMCI) message, the third message being used for management or control of a WLAN function of the first slave device, the third message comprising fifth indication information, the fifth indication information being used to indicate a first management or control type of the WLAN function to which the third message is used for management or control, the first management or control type corresponding to a first latency requirement or a first priority; and the processor 501 is configured to manage or control the first management or control type of the WLAN function based on the third indication information.

[0171] In a possible implementation, the transceiver 502 is further configured to receive a fourth message from a master device, the fourth message being a WMCI message, the fourth message being used for management or control of a WLAN function of the first slave device, the fourth message comprising sixth indication information, the sixth indication information being used to indicate a second management or control type of the WLAN function to which the fourth message is used for management or control, the second management or control type corresponding to a second latency requirement or a second priority, the second latency requirement being different from the first latency requirement, or the second priority being different from the first priority. The processor 501 is further configured to, in a case where the first latency requirement is a low latency requirement and the second latency requirement is a normal latency requirement, or in a case where the first priority is higher than the second priority, preferentially manage or control the first management or control type of the WLAN function corresponding to the third message.

[0172] For details, refer to the related description in the embodiments of FIG. 2 or FIG. 4.

[0173] As shown in FIG. 6, the present application further provides a communication apparatus 60. The communication apparatus 60 can be a slave device (e.g., the first slave device) or a master device, or a component (e.g., an integrated circuit, a chip, etc.) of a slave device (e.g., the first slave device) or a master device. The communication apparatus 60 can also be a communication module for implementing the method in the method embodiments of the present application.

[0174] The communication apparatus 60 can include a processing module 601 (or a processing unit). Optionally, it can also include an interface module 602 (or a transceiving unit or a transceiving module) and a storage module 603 (or a storage unit). The interface module 602 is configured to implement communication with other devices. The interface module 602 can be a transceiving module or an input / output module, for example.

[0175] In a possible design, one or more of the modules in FIG. 6 can be implemented by one or more processors, or by one or more processors and memories; or by one or more processors and transceivers; or by one or more processors, memories and transceivers, and the embodiments of the present application are not limited in this regard. The processor, the memory, the transceiver can be separately provided, or integrated together.

[0176] The communication apparatus 60 has the function of implementing the slave device (e.g., the first slave device) described in the embodiments of the present application. For example, the communication apparatus 60 includes the modules or units or means corresponding to the steps involved in the slave device (e.g., the first slave device) described in the embodiments of the present application, and the function or unit or means can be implemented by software, or by hardware, or by hardware executing corresponding software, or by a combination of software and hardware. For details, further reference can be made to the corresponding description in the foregoing method embodiments. For details, further reference can be made to the communication apparatus 50 in the corresponding embodiments in FIG. 5.

[0177] Alternatively, the communication apparatus 60 has the function of implementing the master device described in the embodiments of the present application. For example, the communication apparatus 60 includes the modules or units or means corresponding to the steps involved in the master device described in the embodiments of the present application, and the function or unit or means can be implemented by software, or by hardware, or by hardware executing corresponding software, or by a combination of software and hardware. For details, further reference can be made to the corresponding description in the foregoing method embodiments. For details, further reference can be made to the communication apparatus 50 in the corresponding embodiments in FIG. 5.

[0178] Further, the present application provides a computer program product including one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are wholly or partially generated. For example, the method related to the slave device (e.g., the first slave device) in the foregoing FIG. 2 or FIG. 4 is implemented. For another example, the method related to the master device in the foregoing FIG. 2 or FIG. 4 is implemented. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable devices. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) manner. The computer readable storage medium can be any available medium that can be used to store computer readable data or can be integrated into a server, data center or other data storage device including one or more available media sets. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital versatile disc (DVD)) or a semiconductor medium (e.g., solid state disk (SSD)) and the like.

[0179] Further, the present application also provides a computer readable storage medium storing a computer program, which is executed by a processor to implement the method related to the slave device (e.g., the first slave device) in the foregoing FIG. 2 or FIG. 4.

[0180] Further, the present application also provides a computer readable storage medium storing a computer program, which is executed by a processor to implement the method related to the master device in the foregoing FIG. 2 or FIG. 4.

[0181] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described systems, devices and units can refer to the corresponding processes in the foregoing method embodiments, which will not be described here.

[0182] The above embodiments are only used to illustrate the technical solutions of the present application, but not limit the present application; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: it can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacement for part of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A method of optical network communication, applied to an optical fiber network comprising a master device and at least one slave device, the at least one slave device comprising a first slave device, characterized in that, The master device sends a first message to the first slave device, the first message being a wireless local area network management control interface (WMCI) message, the first message being used for managing or controlling a wireless local area network (WLAN) function of the first slave device, the first message comprising first indication information, the first indication information being used for indicating a time delay requirement or a priority of the first message. The first indication information comprises a first value or a second value, the first value being used for indicating a requirement of time delay control, and the second value being used for indicating a requirement of no time delay control.

2. The method of claim 1, wherein, The first indication information comprises at least two values, different values of the at least two values respectively indicating different priorities.

3. The method of claim 1, wherein, The first indication information is located in a message type identification field of the first message, or the first indication information is located in a message length field of the first message.

4. The method according to any one of claims 1 to 3, characterized in that, The first indication information is located in the highest bit of the message type identification field, or the first indication information is located in the highest 2 bits of a first byte of the message length field.

5. The method of claim 4, wherein, The first message further comprises second indication information, the second indication information being used for indicating a management and control type of the first message.

6. The method according to any one of claims 1 to 5, characterized in that, The management and control type comprises any one of a WLAN data sending scheduling management and control, a WLAN roaming management and control, or a WLAN power adjustment management and control.

7. The method of claim 6, wherein, The second indication information is located in the message type identification field of the first message.

8. The method according to claim 6 or 7, characterized in that, The first message is encapsulated in a payload field of a fiber to the room (FTR) encapsulation mode (FEM) frame, and a FEM port identification in a frame header of the FEM frame is used for indicating that the first message corresponds to the first slave device.

9. The method according to any one of claims 1 to 8, characterized in that, The FEM frame is encapsulated in a payload field of a data link layer (DLL) frame.

10. The method of claim 9, wherein, The method further comprises:

11. The method according to any one of claims 1 to 10, characterized in that, The master device sends a second message to the first slave device, the second message being a WMCI message, the second message being used for managing or controlling a WLAN function of the first slave device, the second message comprising third indication information and fourth indication information, the third indication information being used for indicating a time delay requirement or a priority of the second message, and the fourth indication information being used for indicating a management and control type of the second message, the management and control type of the second message being different from the management and control type of the first message, the time delay requirement indicated by the third indication information being different from the time delay requirement indicated by the first indication information, or the priority indicated by the third indication information being different from the priority indicated by the first indication information. The master device is a master FTR unit (MFU), and the slave device is a slave FTR unit (SFU).

12. The method according to any one of claims 1 to 11, characterized in that, The first slave device receives a first message from the master device, the first message being a WMCI message, the first message being used for managing or controlling a WLAN function of the first slave device, the first message comprising first indication information, the first indication information being used for indicating a time delay requirement or a priority of the first message.

13. A method of optical network communication, applied to an optical fiber network comprising a master device and at least one slave device, the at least one slave device comprising a first slave device, characterized in that, ​ ​ The first slave device controls the WLAN function corresponding to the first message based on the first indication information.

14. The method of claim 13, wherein, The first indication information includes a first value or a second value, the first value is used to indicate a requirement of time delay control, and the second value is used to indicate a requirement of no time delay control.

15. The method of claim 13, wherein, The first indication information includes at least two values, and different values in the at least two values respectively indicate different priorities.

16. The method according to any one of claims 13 to 15, characterized in that, The first indication information is located in a message type identifier field of the first message, or the first indication information is located in a message length field of the first message.

17. The method of claim 16, wherein, The first indication information is located in the highest bit of the message type identifier field, or the first indication information is located in the highest 2 bits of the first byte of the message length field.

18. The method according to any one of claims 13 to 17, characterized in that, The first message further includes second indication information, and the second indication information is used to indicate a control type of the first message.

19. The method of claim 18, wherein, The control type includes any one of WLAN data sending scheduling control, WLAN roaming control or WLAN power adjustment control.

20. The method of claim 18 or 19, wherein, The second indication information is located in the message type identifier field of the first message.

21. The method of any one of claims 13 to 20, wherein, The first message is encapsulated in a payload field of a FEM frame, and a FEM port identifier in a frame header of the FEM frame is used to indicate that the first message corresponds to the first slave device.

22. The method of claim 21, wherein, The FEM frame is encapsulated in a payload field of a data link layer (DLL) frame.

23. The method of any one of claims 13 to 22, wherein, The method further includes: The first slave device receives a second message from the master device, the second message is a WMCI message, the second message is used to manage or control a WLAN function of the first slave device, the second message includes third indication information and fourth indication information, the third indication information is used to indicate a time delay requirement or a priority of the second message, and the fourth indication information is used to indicate a control type of the second message, the control type of the second message is different from the control type of the first message, the time delay requirement indicated by the third indication information is different from the time delay requirement indicated by the first indication information, or the priority indicated by the third indication information is different from the priority indicated by the first indication information.

24. The method of claim 23, wherein, The method further includes: In a case where the first indication information indicates a requirement of time delay control and the third indication information indicates a requirement of no time delay control, or the priority indicated by the first indication information is higher than the priority indicated by the third indication information, the first slave device preferentially controls the WLAN function corresponding to the first message.

25. The method of any one of claims 13 to 24, wherein, The master device is a master FTTR unit (MFU), and the slave device is a slave FTTR unit (SFU).

26. A communications device, characterized by The method includes: A processor and a transceiver, the processor is connected with the transceiver, and the processor is used to implement the method in any one of claims 1 to 12.

27. A communications device, characterized by The method includes: A processor and a transceiver, the processor is connected with the transceiver, and the processor is used to implement the method in any one of claims 13 to 25.

Images