Optical network communication method and communication device

Abstract

The invention provides an optical network communication method and a communication device, 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 comprises a first slave device. Wherein the master device sends a first message to the first slave device, the first message is a wireless local area network management and control interface (WMCI) message, the first message is used for managing or controlling a wireless local area network (WLAN) function of the first slave device, and the first message comprises first indication information; the first indication information is used for indicating the time delay demand or 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 time delay demand of the first message, the first slave device decides whether to process the first message preferentially based on the first indication information, which is beneficial for reducing the bandwidth occupied by the low-priority message or the message with the common time delay demand, and the bandwidth occupied by the message with the common time delay demand is reduced. And the communication real-time performance of high-priority messages or messages with low time delay requirements can be improved.

Description

Technical Field

[0001] This application relates to the field of optical communication, and more particularly to an optical network communication method and communication device. Background Technology

[0002] Fiber to the room (FTTR) refers to a technology that uses optical fiber instead of network cables to provide fiber optic media access to a room via optical network equipment (e.g., an optical network terminal, ONT). In this FTTR scenario, the fiber optic network includes a master device and one or more slave devices (also called sub-devices). A management channel can be established between the master and slave devices, allowing the master device to send management or control-related messages to the slave devices, thereby enabling the master device to manage or control some functions of the slave devices. For example, the master and slave devices can establish a WMCI management channel based on the Wireless Local Area Network Management and Control Interface (WMCI) protocol, allowing the master and slave devices to exchange WMCI messages, thus enabling the management or control of the wireless local area network (WLAN) functions.

[0003] Currently, in the FTTR system management architecture, even different management types or the same management type of the WLAN function of the same slave device may have different management requirements and characteristics, and the latency requirements corresponding to different management requirements and characteristics are different. A unified message format (e.g., the current WMCI message format) cannot distinguish between different latency requirements, which is not conducive to the master device's efficient management of the slave device's WLAN function. Summary of the Invention

[0004] This application provides an optical network communication method and communication device for identifying messages with different latency requirements or priorities in the same management channel, thereby improving the efficiency of the master device in managing or controlling the WLAN function of the slave device.

[0005] Firstly, this application provides an optical network communication method applied to an optical fiber network, which includes 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 master device in the optical fiber network, or by a portion of a functional module or chip within the master device. Taking execution by the master device as an example, the master device sends a first message to the first slave device. The first message is a Wireless Local Area Network Management and Control Interface (WMCI) message, used to manage or control the WLAN function of the first slave device. The first message includes first indication information, used to indicate the latency requirements or priority of the WLAN function corresponding to the first message.

[0006] In this aspect, the first indication information in the first message sent by the master device to the first slave device can indicate the priority or latency requirement of the first message, which is beneficial for the first slave device to decide whether to prioritize processing the first message based on the first indication information, which is beneficial to reduce the bandwidth occupied by low-priority messages or messages with ordinary latency requirements, and also beneficial to improve the real-time communication performance of high-priority messages or messages with low latency requirements.

[0007] In one possible implementation, the first indication information includes a first value or a second value. The first value indicates a need for delay control, meaning the message carrying the first indication information (e.g., the first message) is a low-latency control message; the second value indicates a need for no delay control, meaning the message carrying the first indication information (e.g., the first message) is a normal control message.

[0008] In this embodiment, the first indication information in the first message sent by the master device to the first slave device can indicate the latency requirement, that is, indicate whether the first message is a low latency control message or a normal control message. This is beneficial for the first slave device to decide whether to prioritize processing the first message based on the first indication information, which helps to reduce the bandwidth occupied by normal latency control messages, and also helps to improve the real-time communication performance of low latency control messages.

[0009] In one possible implementation, the first indication information includes at least two values, with different values ​​indicating different priorities. For example, the first indication information includes two values, indicating low priority and high priority respectively. Another example is that the first indication information includes three values, indicating low priority, medium priority, and high priority respectively.

[0010] 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, that is, whether the first message has a lower or higher priority than other WMCI messages. This is beneficial for the first slave device to decide whether to prioritize processing the first message based on the first indication information, which helps to reduce the bandwidth occupied by low-priority messages and improve the real-time communication performance of high-priority messages.

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

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

[0013] In one possible implementation, the first message further includes second indication information, which indicates a first control type for the first message to manage WLAN functions, and the first indication information also indicates the latency requirement or priority of the first control type of WLAN functions.

[0014] In this embodiment, the first message includes second indication information indicating the control type, which clarifies which control type the first message is used to control the WLAN function, thus improving the efficiency of the master device in controlling the WLAN function of the slave device. Furthermore, combined with the first indication information, specific latency requirements or priorities can be indicated for a specific control type, facilitating priority management at the granularity of control type, thereby improving the accuracy and efficiency of WLAN function control.

[0015] In one possible implementation, the first control type of the WLAN function is any one of WLAN data transmission scheduling control, WLAN roaming control, or WLAN power regulation control.

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

[0017] In this embodiment, the FEM port ID in the FEM frame header is assigned by the master device. This FEM port ID not only indicates that the first message is a WMCI message, but also indicates the sender and receiver of the WMCI message (i.e., the first message), that is, it indicates that the WMCI message (i.e., the first message) corresponds to the first slave device and not other slave devices. Therefore, the FEM port ID can be used to distinguish WMCI messages from other control messages in the FTTR system, which is beneficial to improving the control efficiency of WLAN functions.

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

[0019] In one possible implementation, the method further includes: the master device sending 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 priority of the WLAN function corresponding to the second message, the fourth indication information being used to indicate a second control type for the second message to manage the WLAN function, the second control type being different from the first 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.

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

[0021] Secondly, this application provides an optical network communication method applied to an optical fiber network, which includes 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 by a portion of a functional module or chip within the first slave device. Taking execution by the first slave device as an example, the first slave device receives a first message from the master device. The first message is a Wireless Local Area Network Management and Control Interface (WMCI) message, used to manage or control the WLAN function of the first slave device. The first message includes first indication information, used to indicate the latency requirements or 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.

[0022] In this aspect, the first indication information in the first message received by the first slave device can indicate the priority or latency requirement of the first message, so that the first slave device can decide whether to prioritize processing the first message based on the first indication information. This is beneficial to reducing the bandwidth occupied by low-priority messages or messages with ordinary latency requirements, and also beneficial to improving the real-time communication performance of high-priority messages or messages with low latency requirements.

[0023] In one possible implementation, the first indication information includes a first value or a second value, wherein the first value is used to indicate a need with delay control and the second value is used to indicate a need without delay control.

[0024] In one possible implementation, the first indication information includes at least two values, and different values ​​of the at least two values ​​indicate different priorities.

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

[0026] In one possible implementation, 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.

[0027] In one possible implementation, the first message further includes second indication information, which indicates a first control type for the first message to manage WLAN functions, and the first indication information also indicates the latency requirement or priority of the first control type of WLAN functions.

[0028] In one possible implementation, the first control type of the WLAN function is any one of WLAN data transmission scheduling control, WLAN roaming control, or WLAN power regulation control.

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

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

[0031] In one possible implementation, the method further includes: a first slave device receiving a second message from a master 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 priority of the WLAN function corresponding to the second message, the fourth indication information being used to indicate a second control type for the second message to manage the WLAN function, the second control type being different from the first 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.

[0032] In one possible implementation, the method further includes: when the first indication information indicates a need for latency control and the third indication information indicates no need for latency control, or when the priority of the first indication information is higher than the priority of the third indication information, the first slave device prioritizes the management and control of the WLAN function corresponding to the first message.

[0033] In this embodiment, when the first slave device receives two or more messages carrying indications of latency requirements or priorities, the first slave device processes the message with low latency requirements or the message with high priority first. This is beneficial for achieving QoS management of messages transmitted in the same management channel, improving resource utilization efficiency and control efficiency.

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

[0035] It should be noted that there are many other specific implementation methods in this application, and you can refer to the specific implementation methods and their beneficial effects in the first aspect, which will not be repeated here.

[0036] Thirdly, this application provides an optical network communication method applied to an optical fiber network, which includes 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 master device in the optical fiber network, or by a portion of a functional module or chip within the master device. Taking execution by the master device as an example, the master device sends a third message to the first slave device. The third message is a Wireless Local Area Network Management and Control Interface (WMCI) message, used to manage or control the WLAN function of the first slave device. The third message includes fifth indication information, which indicates a first control type for managing the WLAN function, the first control type corresponding to a first latency requirement or a first priority.

[0037] In this 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 the WLAN management type corresponds to the first latency requirement or the first priority. This is beneficial for the first slave device to decide whether to prioritize the processing of the third message based on the fifth indication information, which is beneficial to reduce the bandwidth occupied by low-priority messages and improve the real-time communication performance of high-priority messages.

[0038] In one possible implementation, 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, and the second control type is another control type for the WLAN function managed by the master device for the first slave device.

[0039] In one possible implementation, the first control type of the WLAN function is any one of WLAN data transmission scheduling control, WLAN roaming control, or WLAN power regulation control.

[0040] In one possible implementation, the fifth indication information is located in the 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.

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

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

[0043] In one possible implementation, the method further includes:

[0044] 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. The fourth message includes a sixth indication information. The sixth indication information is used to indicate the second control type for the fourth message to manage the WLAN function. The second control type corresponds to a second latency requirement or a second priority. The second latency requirement is different from the first latency requirement, or the second priority is different from the first priority.

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

[0046] Fourthly, this 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 by some 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 third message from the master device, the third message being a Wireless Local Area Network Management and Control Interface (WMCI) message, the third message being used to manage or control the wireless local area network (WLAN) function of the first slave device, the third message including fifth indication information, the fifth indication information being used to indicate a first control type for the third message to manage the WLAN function, the first control type corresponding to a first latency requirement or a first priority; then, the first slave device manages the first control type of the WLAN function based on the third indication information.

[0047] In this embodiment, the fifth indication information in the third message received by the first slave device can not only indicate the WLAN management type of the third message, but the WLAN management type also corresponds to the first latency requirement or the first priority. This is beneficial for the first slave device to decide whether to prioritize the processing of the third message based on the fifth indication information, which is beneficial to reduce the bandwidth occupied by low-priority messages and improve the real-time communication performance of high-priority messages.

[0048] In one possible implementation, 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, and the second control type is another control type for the WLAN function managed by the master device for the first slave device.

[0049] In one possible implementation, the first control type of the WLAN function is any one of WLAN data transmission scheduling control, WLAN roaming control, or WLAN power regulation control.

[0050] In one possible implementation, the fifth indication information is located in the 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.

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

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

[0053] In one possible implementation, the method further includes:

[0054] The first slave device receives a fourth message from the master device. The fourth message is a WMCI message and is used to manage or control the WLAN function of the first slave device. The fourth message includes a sixth indication information, which indicates the second control type for managing the WLAN function. The second control type corresponds to a second latency requirement or a second priority. The second latency requirement is different from the first latency requirement, or the second priority is different from the first priority. If the first latency requirement is a low latency requirement and the second latency requirement is a normal latency requirement, or the first priority is higher than the second priority, the first slave device prioritizes managing the first control type of the WLAN function corresponding to the third message.

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

[0056] It should be noted that there are many other specific implementation methods in this application, and you can refer to the specific implementation methods and their beneficial effects in the first aspect, which will not be repeated here.

[0057] Fifthly, this application provides a communication device 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 communication device can be the master device in the optical fiber network, or a functional module or chip within the master device. The communication device includes a transceiver and a processor. The processor is used to generate a first message, the first message being a Wireless Local Area Network Management and Control Interface (WMCI) message, the first message being used to manage or control the WLAN function of the first slave device, the first message including first indication information, the first indication information being used to indicate the latency requirements or priority of the WLAN function corresponding to the first message. The transceiver is used to send the first message to the first slave device.

[0058] In one possible implementation, the processor is further configured to generate a second message, which is a WMCI message, used to manage or control the WLAN function of the first slave device. The second message includes third and fourth indication information. The third indication information indicates the latency requirements or priority of the WLAN function corresponding to the second message. The fourth indication information indicates a second control type for managing the WLAN function, which is different from the first control type. The latency requirements indicated by the third indication information are different from those indicated by the first indication information, or the priority indicated by the third indication information is different from that indicated by the first indication information. The transceiver is further configured to send the second message to the first slave device.

[0059] It should be noted that there are many other specific implementation methods in this application, and you can refer to the specific implementation methods and their beneficial effects in the first aspect, which will not be repeated here.

[0060] Sixthly, this application provides a communication device 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 communication device can be the first slave device in the optical fiber network, or it can be a functional module or chip within the first slave device. The communication device includes a transceiver and a processor. The transceiver is used to receive a first message from the master device, the first message being a Wireless Local Area Network Management and Control Interface (WMCI) message, the first message being used to manage or control the WLAN function of the first slave device, the first message including first indication information, the first indication information being used to indicate the latency requirements or priority of the WLAN function corresponding to the first message; the processor is used to manage and control the WLAN function corresponding to the first message based on the first indication information.

[0061] In one possible implementation, the transceiver is further configured to receive a second message from the master device. The second message is a WMCI message used to manage or control the WLAN function of the first slave device. The second message includes third and fourth indication information. The third indication information indicates the latency requirement or priority of the WLAN function corresponding to the second message. The fourth indication information indicates a second control type for managing the WLAN function, which is different from the first control type. 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. Furthermore, if the first indication information indicates a latency control requirement and the third indication information indicates no latency control requirement, or if the priority of the first indication information is higher than the priority of the third indication information, the processor is further configured to prioritize the management of the WLAN function corresponding to the first message.

[0062] It should be noted that there are many other specific implementation methods in this application, and you can refer to the specific implementation methods and their beneficial effects in the second aspect, which will not be repeated here.

[0063] In a seventh aspect, this application provides a communication device 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 communication device can be the master device in the optical fiber network, or a functional module or chip within the master device. The communication device includes a transceiver and a processor. The processor is used to generate a third message, the third message being a Wireless Local Area Network Management and Control Interface (WMCI) message, the third message being used to manage or control the WLAN function of the first slave device, the third message including fifth indication information, the fifth indication information being used to indicate a first control type for managing the WLAN function, the first control type corresponding to a first latency requirement or a first priority. The transceiver is used to send the third message to the first slave device.

[0064] In one possible implementation, the processor generates a fourth message, which is a WMCI message, used to manage or control the WLAN function of the first slave device. The fourth message includes sixth indication information, indicating a second control type for managing the WLAN function. This second control type corresponds to a second latency requirement or a second priority, which differs from a first latency requirement or a first priority. The transceiver sends the fourth message to the first slave device.

[0065] It should be noted that there are many other specific implementation methods in this application, and you can refer to the specific implementation methods and their beneficial effects in the third aspect, which will not be repeated here.

[0066] Eighthly, this application provides a communication device 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 communication device may be the first slave device in the optical fiber network, or it may be a functional module or chip within the first slave device. The communication device includes a transceiver and a processor. The transceiver is used to receive a third message from the master device, the third message being a Wireless Local Area Network Management and Control Interface (WMCI) message, the third message being used to manage or control the WLAN function of the first slave device, the third message including fifth indication information, the fifth indication information being used to indicate a first control type for managing the WLAN function, the first control type corresponding to a first latency requirement or a first priority; the processor is used to manage the first control type of the WLAN function based on the third indication information.

[0067] In one possible implementation, a transceiver is configured to receive a fourth message from a master device, the fourth message being a WMCI message, which is used to manage or control the WLAN function of a first slave device. The fourth message includes sixth indication information, which indicates a second control type for managing the WLAN function. The second control type corresponds to a second latency requirement or a second priority, where the second latency requirement is different from the first latency requirement, or the second priority is different from the first priority. A processor is configured to prioritize managing the first control type of the WLAN function corresponding to the third message when 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.

[0068] It should be noted that there are many other specific implementation methods in this application, and you can refer to the specific implementation methods and their beneficial effects in the fourth aspect, which will not be repeated here.

[0069] Ninthly, embodiments of this application provide a communication device, which may be a main device as described in the foregoing embodiments, or a chip within the main device. The communication device may include a processing module and a transceiver module. When the communication device is a main device, the processing module may be a processor, and the transceiver module may be a transceiver. The main device may further include a storage module, which may be a memory. The storage module stores instructions, and the processing module executes the instructions stored in the storage module to cause the main device to perform the method of the first aspect or any embodiment of the first aspect; or, to perform the method of the third aspect or any embodiment of the third aspect. When the communication device is a chip within the main device, the processing module may be a processor, and the transceiver module may be an input / output interface, pin, or circuit, etc. The processing module executes the instructions stored in the storage module to cause the main device to perform the method of the first aspect or any embodiment of the first aspect; or, to perform the method of the third aspect or any embodiment of the third aspect. The storage module may be a storage module within the chip (e.g., a register, cache, etc.), or a storage module located outside the chip within the main device (e.g., a read-only memory, random access memory, etc.).

[0070] In a tenth aspect, embodiments of this application provide a communication device, which may be a slave device (e.g., a first slave device) as described in the foregoing embodiments, or a chip within the slave device (e.g., the first slave device). The communication device may include a processing module and a transceiver module. When the communication device is a slave device (e.g., the first slave device), the processing module may be a processor, and the transceiver module may be a transceiver. Optionally, the slave device (e.g., the first slave device) may further include a storage module, which may be a memory; the storage module stores instructions, and the processing module executes the instructions stored in the storage module to cause the slave device (e.g., the first slave device) to perform the method of the second aspect or any embodiment of the second aspect; or, to perform the method of the fourth aspect or any embodiment of the fourth aspect. When the communication device is a chip within a slave device (e.g., a first slave device), the processing module can be a processor, and the transceiver module can be an input / output interface, pin, or circuit, etc. The processing module executes instructions stored in the storage module to cause the slave device (e.g., the first slave device) to perform the method of the second aspect or any embodiment of the second aspect; or, to perform the method of the fourth aspect or any embodiment of the fourth aspect. The storage module can be a storage module within the chip (e.g., a register, cache, etc.), or it can be a storage module located outside the chip within the slave device (e.g., the first slave device) (e.g., a read-only memory, random access memory, etc.).

[0071] Eleventhly, this application provides a communication device, which may be an integrated circuit chip. The integrated circuit chip includes a processor. The processor is coupled to a memory for storing programs or instructions that, when executed by the processor, cause the communication device to perform the methods described in any of the various embodiments of the foregoing aspects, as well as the foregoing aspects.

[0072] In a twelfth aspect, embodiments of this application provide a computer program product containing instructions that, when executed on a computer, cause the computer to perform the methods described in any of the various embodiments of the foregoing aspects.

[0073] In a thirteenth aspect, embodiments of this application provide a computer-readable storage medium including instructions that, when executed on a computer, cause the computer to perform the methods described in any of the various embodiments of the foregoing aspects.

[0074] In a fourteenth aspect, embodiments of this application provide an optical fiber network including a master device in the third aspect and any embodiment of the third aspect, and a slave device (e.g., a first slave device) in the fourth aspect and any embodiment of the fourth aspect.

[0075] In a fifteenth aspect, embodiments of this application provide an optical fiber network including a master device in the fifth aspect and any embodiment thereof, and a slave device (e.g., a first slave device) in the sixth aspect and any embodiment thereof. Attached Figure Description

[0076] Figure 1A An example diagram of the network architecture of a fiber optic network;

[0077] Figure 1B Another example diagram of the network architecture of a fiber optic network;

[0078] Figure 1C Here is an example diagram of an FTTR system;

[0079] Figure 1D This is an example diagram illustrating the transmission method of WMCI messages in traditional technologies.

[0080] Figure 2 This is a flowchart illustrating the optical network communication method in this application;

[0081] Figure 3A An example diagram of an FEM frame encapsulating WMCI messages;

[0082] Figure 3B An example diagram of an XFEM frame encapsulating a WMCI message;

[0083] Figure 3C An example diagram of a DLL frame that encapsulates an FEM frame;

[0084] Figure 3D An example diagram of a DLL frame that encapsulates an XFEM frame;

[0085] Figure 4 This is another flowchart illustrating the optical network communication method in this application;

[0086] Figure 5 This is a schematic diagram of one embodiment of the communication device in this application;

[0087] Figure 6 This is a schematic diagram of another embodiment of the communication device in this application. Detailed Implementation

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

[0089] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0090] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such terms are interchangeable where appropriate so that the embodiments described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0091] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0092] The optical network communication method provided in this application is applied to optical fiber networks. Figure 1A This is an example diagram of the architecture of a fiber optic network in traditional technology. (Example:) Figure 1AAs shown, this fiber optic network includes an optical line terminal (OLT), an optical distribution network (ODN), and optical network units (ONUs) (or optical network terminals (ONTs)). The OLT and ONUs are connected and communicate via optical fibers. The OLT is typically connected to the ONU (or ONT) through the ODN. The ODN comprises a network of one or more optical devices, such as optical fibers, optical distribution frames (ODFs), optical splitters (also known as splitters), and combiners. Furthermore, the aforementioned OLT can connect to the operator's network through a network-side interface, and it can also connect to the ODN through a dedicated interface. The ODN, in turn, connects to the ONUs (or ONTs) through a dedicated interface. In the downlink direction, the OLT broadcasts downlink optical signals, which are then distributed to each ONU (or ONT) via the ODN. In the uplink direction, a time division multiple access (TDMA) method is used, with each ONU (or ONT) transmitting uplink optical signals in its assigned uplink time slot by the OLT. It should be noted that this application does not limit the specific type of optical fiber. The optical fiber described in this application can be a single optical fiber, loose-tube optical fiber, optical cable, or optoelectronic composite cable, etc.

[0093] Figure 1B A schematic diagram of the optical fiber network provided in this application. Figure 1BAs shown, the fiber optic network provided in this application includes a master device 01 and at least one slave device 02, with the master device 01 connected to the at least one slave device 02 via optical fiber. For example, the master device 01 is connected to the at least one slave device 02 via an optical distribution network. The master device 01 is capable of managing or controlling specific functions of one or more slave devices 02 based on at least one protocol. For example, the master device 01 is capable of managing or controlling the wireless local area network (WLAN) function 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 have WLAN functionality; it can also be understood that the master device 01 and / or the slave device 02 have wireless fidelity (WiFi) functionality. Exemplarily, in a fiber to the room (FTTR) scenario, the master device 01 can be referred to as a main FTTR unit (MFU), FTTR master device, or main gateway, and the slave device 02 can be referred to as a sub FTTR unit (SFU), FTTR slave device, or slave gateway.

[0094] Figure 1C This is an example diagram showing the network locations for FTTR. Figure 1C As shown, FTTR is a fiber optic network built on top of FTTH / O, providing fiber optic coverage within broadband customer networks (e.g., homes or offices). Fiber optic connections are used between the FTTR master device and the FTTR slave devices in each room. Both the FTTR master and slave devices can connect to user terminals via wireless or wired interfaces, or via adapters such as set-top boxes. Specifically, the northbound connection of the FTTR master device acts as an access network terminal, connecting to the access node (AN). The southbound connection of the FTTR master device's FTTR transceiver unit connects to the FTTR transceiver units of the slave devices via an indoor fiber distribution network (IFDN), also providing gateway and other network functions. The FTTR transceiver units of the slave devices connect to the TTTP transceiver unit of the FTTR master device via the indoor fiber distribution network, providing terminal access via wireless or wired interfaces. Indoor optical distribution networks are point-to-multipoint fiber optic infrastructures that can be completely passive, typically consisting of interconnected optical cables and passive devices such as optical splitters. They can also provide remote power supply functionality for FTTR slave devices by using hybrid optical-electrical cables and hybrid optical-electrical splitters.

[0095] For example, such as Figure 1DAs shown, in the FTTR system management architecture, even different management types or the same management type of the WLAN function of the same slave device may have different management requirements and characteristics, and the latency requirements corresponding to different management requirements and characteristics are different. For example, Figure 1D Both control type 1 and control type 2 messages between the master device and slave device 1 are transmitted through the WMCI management channel, as are control type 1 and control type 2 messages between the master device and slave device 2. The same control type or different control classes may have different latency requirements. A unified message format (e.g., the current WMCI message format) cannot distinguish between these different latency requirements, thus hindering the master device's efficient management of the slave device's WLAN functions.

[0096] In response, this 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, thereby improving the efficiency of the master device in managing or controlling the WLAN functions of the slave device.

[0097] The following will combine Figure 2 The main process of the optical network communication method provided in this application is described below:

[0098] like Figure 2 The diagram shown is a flowchart of an optical network communication method provided in this application. This optical network communication method is illustrated using the interaction between a master device and a first slave device as an example. Of course, the entity executing the master device's actions in this method can also be a device, module, or chip within the master device; similarly, the entity executing the first slave device's actions in this method can also be a device, module, or chip within the first slave device. This embodiment does not specifically limit this. For example, as shown... Figure 2 As shown, the optical network communication method includes the following steps:

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

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

[0101] The first message is a WMCI message, used to manage or control the WLAN function of the first slave device (hereinafter referred to as management). The first message includes first indication information, which is used to indicate the latency requirements or priority of the WLAN function corresponding to the first message.

[0102] This refers to whether the latency requirement necessitates low-latency control, or whether real-time control is required. Optionally, this latency requirement needs to include transmission latency and / or processing latency. For example, requiring low-latency control or real-time control means that processing latency and / or transmission latency should be controlled within a preset range; not requiring low-latency control or real-time control, also known as normal control, means that processing latency and / or transmission latency only need to meet system requirements. For ease of explanation, messages requiring low-latency control (or requiring real-time control) are called low-latency control messages, and messages not requiring low-latency control (or not requiring real-time control) are called normal control messages. The latency of low-latency control messages is lower than that of normal control messages. This can also be understood as low-latency control messages having a higher priority than normal control messages. For example, when the same device receives both low-latency control messages and normal-latency control messages, the device will prioritize processing the low-latency control messages. It helps reduce the bandwidth occupied by ordinary latency control messages and improves the real-time communication performance of low latency control messages, thereby improving the management efficiency of the master device over the WLAN function of the slave device.

[0103] In this context, "priority" refers to a parameter that determines the priority level of resources within the receiving device when processing or transmitting multiple messages. In this embodiment, the priority refers to the level at which each message is processed or transmitted preferentially when a slave device (e.g., a first slave device) processes multiple messages for controlling WLAN functions. For example, if the first device receives messages 1 and 2 from the master device, where the priority indicated by the indication information in message 1 is higher than the priority indicated by the indication information in message 2, then the first device prioritizes controlling the WLAN function of the first slave device based on message 1. This helps reduce the bandwidth occupied by low-priority messages and improves the real-time communication performance of high-priority messages, thereby improving the efficiency of the master device in controlling the WLAN function of the slave device.

[0104] Specifically, the first instruction information can be implemented in any of the following ways:

[0105] In one possible implementation, the first indication information includes a first value or a second value. The first value indicates a need for delay control, meaning the message carrying the first indication information (e.g., the first message) is a low-latency control message; the second value indicates a need for no delay control, meaning the message carrying the first indication information (e.g., the first message) is a normal control message.

[0106] Optionally, the first indication information is represented by at least one newly defined bit in the WMCI message. In one example, the first indication information is a newly defined bit in the WMCI message, i.e., a first value and a second value are two possible values ​​for this newly defined bit. The two values ​​of this bit indicate low-latency control messages and normal control messages, respectively. For example, a value of 1 indicates that the first message is a low-latency control message, and a value of 0 indicates that the first message is a normal control message; or, a value of 0 indicates that the first message is a low-latency control message, and a value of 1 indicates that the first message is a normal control message. In another example, the first indication information is two newly defined bits in the WMCI message, i.e., a first value and a second value are two possible values ​​for this newly defined 2 bits. The two values ​​of this bit indicate low-latency control messages and normal control messages, respectively. For example, a value of 01 for the two bits indicates that the first message is a low-latency control message, and a value of 00 indicates that the first message is a normal control message; or, a value of 11 for the two bits indicates that the first message is a low-latency control message, and a value of 00 indicates that the first message is a normal control message. This embodiment does not limit the specific implementation of the first and second values, only ensuring that the first and second values ​​are different.

[0107] Optionally, the first indication information is located in the message type identifier field of the first message; or, the first indication information is located in the message length field of the first message. The message type identifier field indicates the type of the first message, and the message length field indicates the length of the message content carried by the first message. For example, the first indication information is located in the most significant bit or the most significant 2 bits of the message type identifier field; or, the first indication information is located in the most significant bit or the most significant 2 bits of the first byte of the message length field.

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

[0109] Table 1

[0110]

[0111] As shown in Table 1, the first byte is the message type identifier field (also called the message type ID field), used to indicate the message type and define the semantics of the message content. The second byte is the sequence number field, containing a sequence number counter, used to ensure the robustness of the WMCI message delivery channel. In the downlink direction, the sequence number field is filled with the value of the corresponding master device's sequence number counter. The master device maintains a separate sequence number counter for each slave device's 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. Bytes 3 and 4 are the message content length field, used to indicate the number of bytes in the message content. Bytes 5 to N are the message content field, used to carry the specific content of the message, which is related to the specific message. Among them, bytes 5 and 6 are used to carry the parameter mask, and bytes 7 to N are used to carry the parameter content of the parameters indicated by the parameter mask. The parameter content should be filled into the message content in the order indicated by the parameter mask. Here, N is an integer greater than 7. Bytes (N+1) to (N+4) are message integrity verification fields, each 4 bytes in size. They are used to verify the sender's identity and prevent forged WMCI message attacks. This field follows the cyclic redundancy check (CRC) function.

[0112] In the examples shown in Table 1, if the first indication information is carried in the message type identifier field and is represented by 1 bit, then the first indication information can be located in the highest bit X of the message type identifier field, that is, the 8th bit of the first byte of the first message. If the first indication information is carried in the message type identifier field and is represented by 2 bits, then the first indication information can be located in the highest bit 2 of the message type identifier field, that is, the 7th to 8th bits of the first byte of the first message. If the first indication information is carried in the message length field and is represented by 1 bit, then the first indication information can be located in the highest bit Y of the message length field, that is, the 8th bit of the third byte of the first message. If the first indication information is carried in the message length field and is represented by 2 bits, then the first indication information can be located in the highest bit 2 of the message length field, that is, the 7th to 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 latency requirement, that is, indicate whether the first message is a low latency control message or a normal control message. This is beneficial for the first slave device to decide whether to prioritize processing the first message based on the first indication information, which helps to reduce the bandwidth occupied by normal latency control messages, and also helps to improve the real-time communication performance of low latency control messages.

[0114] In another possible implementation, the first indication information includes at least two values, with different values ​​indicating different priorities. For example, the first indication information includes two values, indicating low priority and high priority respectively. As another example, the first indication information includes three values, indicating low priority, medium priority, and high priority respectively.

[0115] Optionally, the first indication information is represented by at least one newly defined bit in the WMCI message. In one example, the first indication information is a newly defined bit in the WMCI message, where the two values ​​of this bit indicate low priority and high priority, respectively. For example, a value of 0 indicates that the first message is a low-priority message, and a value of 1 indicates that the first message is a high-priority message; or, a value of 1 indicates that the first message is a low-priority message, and a value of 0 indicates 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, which can indicate up to four priority levels. For example, the values ​​of these two bits include 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. As another example, the values ​​of these two bits include 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 example, the 2-bit value can be 00, 01, 10, or 11, with priority increasing sequentially from 00, 01, 10 to 11. It should be noted that more bits can be defined in the WMCI message to indicate more types of priorities, which will not be listed here.

[0116] Optionally, the first indication information is located in the message type identifier field of the first message; or, the first indication information is located in the message length field of the first message. For example, the first indication information is located in the most significant bit or the most significant 2 bits of the message type identifier field; or, the first indication information is located in the most significant bit or the most significant 2 bits of the first byte of the message length field.

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

[0118] Table 2

[0119]

[0120] The meanings of some fields shown in Table 2 are the same as those in the example shown in Table 1. Please refer to the relevant introduction in Table 1 above for details, which will not be repeated here.

[0121] In the examples shown in Table 2, if the first indication information is carried in the message type identifier field and is represented by 2 bits, then the first indication information can be located in the highest 2 bits XX of the message type identifier field, that is, the 7th to 8th bits of the first byte of the first message. If the first indication information is carried in the message length field and is represented by 2 bits, then the first indication information can be located in the highest 2 bits YY of the message length field, that is, the 7th to 8th bits of the third byte of the first message.

[0122] It should be noted that the names of the fields in the examples shown in Table 1 or Table 2 are merely illustrative. In practical applications, other approximate names may be used for the fields shown in Table 1 or Table 2. This application does not restrict the names of the fields in the first message. Furthermore, the order of the fields in the messages shown in Table 1 or Table 2 may be changed. This application does not restrict the order of the fields in the first message.

[0123] In this embodiment, the first indication information in the first message sent by the master device to the first slave device indicates the priority of the first message, that is, whether the first message has a lower or higher priority than other WMCI messages. This helps the first slave device decide whether to prioritize processing the first message based on the first indication information, reduces the bandwidth occupied by low-priority messages, and improves the real-time communication performance of high-priority messages. Furthermore, indicating priority through the first indication information allows the first slave device to build message priority queues based on the same channel, enabling QoS guarantees for the WMCI management channel for queues of different priorities, thus improving the efficiency of WMCI operations.

[0124] The first indication information in this embodiment can be implemented using any of the aforementioned implementation methods, and is therefore limited here. In this embodiment, by adding a specific field to the WMCI control message to carry the first indication information, the real-time requirements or priorities of the message for transmission and processing are distinguished, thereby achieving QoS management of the same message channel.

[0125] Optionally, the first message may also include second indication information, which indicates the control type for managing WLAN functions. If the second indication information indicates that the first message is used for a first control type to manage WLAN functions, the first indication information may also indicate the latency requirements or priority of the control type for WLAN functions. The first control type for WLAN functions may be any one of WLAN data transmission scheduling control, WLAN roaming control, or WLAN power adjustment control.

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

[0127] It should be noted that the master device sends a 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. Here, the management channel refers to the logical channel established between the master device and the slave device for transmitting messages. The WMCI management channel is the 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 identifiers (port IDs). Different logical port identifiers may correspond to the same physical transceiver port, or they may correspond to different physical transceiver ports; this is not limited here. For example, the first management channel corresponds to the master device's Port ID1 and the first slave device's Port ID1, while other management channels correspond to the master device's Port ID2 and the first slave device's Port ID2. Port ID1 and Port ID2 may correspond to the same physical transceiver port, or they may correspond to different physical transceiver ports.

[0128] In addition, such as Figure 3AAs shown, if the master device's rate level is 2.5G, the first message is encapsulated in the payload field of an FTTR Encapsulation Method (FEM) frame. The FEM port ID in the FEM frame header is assigned by the master device. This FEM port ID not only indicates that the first message is a WMCI message, but also indicates the sender and receiver of the WMCI message (i.e., the first message), that is, it indicates that the WMCI message (i.e., the first message) corresponds to the first slave device and not other slave devices. Therefore, the FEM port ID can be used to distinguish WMCI messages from other control messages in the FTTR system (e.g., FMCI messages or OMCI messages). It should be noted that when the master device's rate class 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, and can support both simultaneously. The slave device's downlink rate is 2.48832 Gbit / s, and its uplink rate is 1.24416 Gbit / s or 2.48832 Gbit / s. It should also be noted that the payload length L of the FEM frame is equal to the length L of the WMCI message, where L is a positive integer.

[0129] In addition, such as Figure 3BAs shown, if the master device's rate class is 10G, the first message is encapsulated in the payload field of a 10G-FTTR Encapsulation Method (XFEM) frame. The XFEM port ID in the XFEM frame header is assigned by the master device. This XFEM port ID not only indicates that the first message is a WMCI message, but also indicates the sender and receiver of the WMCI message (i.e., the first message), that is, it indicates that the WMCI message (i.e., the first message) corresponds to the first slave device and not other slave devices. Therefore, the XFEM port ID can be used to distinguish WMCI messages from other control messages in the FTTR system. It should be noted that when the master device's rate class 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, 2.48832 Gbit / s, or both simultaneously. The slave device's downlink rate is 9.95328 Gbit / s, and its uplink rate is either 9.95328 Gbit / s or 2.48832 Gbit / s. It should also 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 may not be an integer multiple of 4 bytes. Therefore, the XFEM payload may need to include 0 to 3 bytes of padding fields while carrying the WMCI message.

[0130] In addition, such as Figure 3C As shown, the FEM frame is encapsulated in the payload field of the data link layer (DLL) frame. For example... Figure 3D As shown, XFEM frames are encapsulated in the payload field of DLL frames. A DLL frame consists of a DLL frame header and a DLL frame payload. The DLL payload is formed on the transmitting side and processed by the service adaptation sublayer on the receiving side. The DLL frame header consists of three fixed-size partitions (PLOAMd, BIP, Plend) and one variable-size partition: a bandwidth mapping partition (BWmap). The bandwidth mapping (BWmap) indicates the uplink transmission position in the corresponding uplink physical frame (PHY frame) for different slave devices.

[0131] It should be noted that, in Figure 3C The example shown only illustrates that the payload of the DLL frame contains three FEM frames. In practical applications, the payload of the DLL frame can contain other numbers of FEM frames; this is not limited here. Figure 3D In the example shown, the payload of the DLL frame contains 3 XFEM frames. In actual applications, the payload of the DLL frame can contain other numbers of XFEM frames, which is not limited here.

[0132] Step 202: The first slave device manages the WLAN function corresponding to the first message based on the first instruction information.

[0133] If the priority of the first indication information in the first message is higher than the priority of the indication information in other messages, or if the first indication information in the first message indicates that there is a time delay requirement, then the first slave device will process the first message first, that is, the first slave device will prioritize the management and control of the WLAN function corresponding to the first message based on the first message.

[0134] It should be noted that WMCI messages with different latency requirements or priorities may indicate different management types for WLAN. For example, a first slave device receives a first message and a second message from a master device. The first message is described above; the second message is a WMCI message used to manage or control the WLAN function of the first slave device. The second message includes third and fourth indication information. The third indication information indicates the latency requirement or priority of the WLAN function corresponding to the second message, and the fourth indication information indicates the second management type used by the second message to manage the WLAN function. Optionally, the second management type may differ from the first management type, the latency requirement indicated by the third indication information may differ from the latency requirement indicated by the first indication information, or the priority indicated by the third indication information may differ from the priority indicated by the first indication information. If the first indication information indicates a latency control requirement and the third indication information indicates no latency control requirement, or if the priority indicated by the first indication information is higher than the priority indicated by the third indication information, the first slave device prioritizes managing the first management type of the WLAN function corresponding to the first message.

[0135] It should also be noted that WMCI messages with different latency requirements or priorities may indicate the same control type for WLAN management. For example, a first slave device receives a first message and a second message from a master device. As described above, the first message is a WMCI message used to manage or control the WLAN function of the first slave device. The second message includes third and fourth indication information. The third indication information indicates the latency requirement or priority of the WLAN function corresponding to the second message, and the fourth indication information indicates the second control type used by the second message to manage the WLAN function. Optionally, the second control type may be the same as the first control type, but the latency requirement indicated by the third indication information may differ from that indicated by the first indication information, or the priority indicated by the third indication information may differ from that indicated by the first indication information. If the first indication information indicates a latency control requirement and the third indication information indicates no latency control requirement, or if the priority indicated by the first indication information is higher than that indicated by the third indication information, the first slave device prioritizes managing the first control type of the WLAN function corresponding to the first message.

[0136] 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 latency requirement of the first message. This is beneficial for the first slave device to decide whether to prioritize processing the first message based on the first indication information, which helps to reduce the bandwidth occupied by low-priority messages or messages with ordinary latency requirements, and also helps to improve the real-time communication performance of high-priority messages or messages with low latency requirements.

[0137] like Figure 4 The diagram shown is a flowchart of an optical network communication method provided in this application. This optical network communication method is illustrated using the interaction between a master device and a first slave device as an example. Of course, the entity executing the master device's actions in this method can also be a device, module, or chip within the master device; similarly, the entity executing the first slave device's actions in this method can also be a device, module, or chip within the first slave device. This embodiment does not specifically limit this. For example, as shown... Figure 4 As shown, the optical network communication method includes the following steps:

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

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

[0140] The third message is a WMCI message, used to manage or control the WLAN function of the first slave device. The third message includes a fifth indication, which indicates the first control type used by the third message to manage the WLAN function. This first control type corresponds to a first latency requirement or a first priority. In other words, the first control type corresponds to a specific latency requirement or priority (i.e., the first latency requirement or the first priority), meaning there is a binding relationship between the first control type and the specific latency requirement or priority. The third message does not need to carry indication information to indicate the latency requirement or priority; it can indicate to the first slave device that the third message has a first latency requirement or a first priority through the first control type. For an explanation of latency requirements and priorities, please refer to the relevant introduction in step 201 above; it will not be repeated here.

[0141] Optionally, the WLAN function's control type can be any one of WLAN data transmission scheduling control, WLAN roaming control, or WLAN power adjustment control. Optionally, different control types may correspond to different latency requirements or different priorities. For example, the first latency requirement corresponding to the first control type may differ from the second latency requirement corresponding to the second control type; or, the first priority corresponding to the first control type may differ from the second priority corresponding to the second control type, where the second control type is the control type indicated by another message received from the device.

[0142] For example, WLAN data transmission scheduling and control corresponds to low latency requirements, WLAN roaming control corresponds to low latency requirements, and WLAN power adjustment and control corresponds to normal latency requirements; or, WLAN power adjustment and control corresponds to low priority, WLAN data transmission scheduling and control corresponds to high priority, and WLAN roaming control corresponds to medium priority. For instance, if the first control type is WLAN data transmission scheduling and control, the first slave device can determine, based on the fifth indication information in the third message, that the third message is used to control WLAN data transmission scheduling, and this WLAN data transmission scheduling and control corresponds to low latency requirements or high priority. As another example, if the first control type is WLAN power adjustment and control, the first slave device can determine, based on the fifth indication information in the third message, that the third message is used to control the WLAN transmission power, and this WLAN power adjustment and control corresponds to normal latency requirements or low priority.

[0143] Optionally, the fifth indication information is located in the 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.

[0144] For example, Table 3 below is an example of a third message in this embodiment.

[0145] Table 3

[0146]

[0147] The meanings of some fields shown in Table 3 are the same as those in the example shown in Table 1. Please refer to the relevant introduction in Table 1 above 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, that is, the first to sixth bits of the first byte of the third message. For example, a value of 1 for the fifth indication information carried in the message type identifier field indicates WLAN data transmission scheduling and control, corresponding to low latency requirements or high priority; a value of 2 indicates WLAN roaming control, corresponding to low latency requirements or medium priority; a value of 3 indicates WLAN power adjustment and control, corresponding to normal latency requirements or low priority. In practical applications, the message type identifier field can also define other control types, and the latency requirements or priorities of different control types can be adjusted or defined as needed, which will not be listed here.

[0148] In this embodiment, the master device sends a 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. Furthermore, the third message is encapsulated in the payload field of an FEM frame, or, the third message is encapsulated in an XFEM frame. Figure 3A As shown, the FEM port ID in the FEM frame header is assigned by the master device. This FEM port ID not only indicates that the third message is a WMCI message, but also indicates the sender and receiver of the WMCI message (i.e., the third message), specifically indicating that the WMCI message (i.e., the third message) corresponds to the first slave device and not other slave devices. Therefore, the FEM port ID can be used to distinguish WMCI messages from other control messages in the FTTR system (e.g., FMCI messages or OMCI messages). Figure 3B As shown, the XFEM port ID in the XFEM frame header is assigned by the master device. This XFEM port ID not only indicates that the third message is a WMCI message, but also indicates the sender and receiver of the WMCI message (i.e., the third message), specifically indicating that the WMCI message (i.e., the third message) corresponds to the first slave device and not other slave devices. Therefore, the XFEM port ID can be used to distinguish WMCI messages from other control messages in the FTTR system.

[0149] Optionally, the FEM frame is encapsulated in the payload field of the DLL frame. Please refer to the previous text for details on how FEM frames are encapsulated within DLL frames. Figure 3C The relevant details are not elaborated here. For information on the encapsulation method of XFEM frames within DLL frames, please refer to the previous text. Figure 3D The relevant details will not be elaborated here.

[0150] Step 402: The first slave device manages the WLAN function corresponding to the third message based on the fifth instruction information.

[0151] If the priority of the fifth indication information in the third message is higher than the priority of the control type indication in other messages, or if the fifth indication information in the third message indicates that there is a time delay requirement, then the first slave device will process the third message first, that is, the first slave device will prioritize the control of the first control type of the WLAN function corresponding to the third message based on the third message.

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

[0153] For example, the first slave device receives a third message and a fourth message from the master device. As described above, the third message is a WMCI message used to manage or control the WLAN function of the first slave device. The fourth message includes sixth indication information, which indicates a second control type for managing the WLAN function. This second control type corresponds to a second latency requirement or a second priority. The second latency requirement is different from the first latency requirement, or the second priority is different from the first priority. If 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 prioritizes managing the WLAN function corresponding to the third message using the first control type.

[0154] 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 management type of the third message, but also correspond to the first latency requirement or the first priority. This is beneficial for the first slave device to decide whether to prioritize the processing of the third message based on the fifth indication information, which helps to reduce the bandwidth occupied by low-priority messages and improve the real-time communication performance of high-priority messages.

[0155] Furthermore, embodiments of this application also provide a communication device 50, such as... Figure 5 As shown, Figure 5 This is a schematic diagram of the structure of a communication device 50 provided in an embodiment of this application. Figure 2 or Figure 4 The specific implementation of the master device and slave device (e.g., the first slave device) in the flowchart shown can be found in [reference]. Figure 5 The internal structure of the communication device 50 is shown. When the communication device 50 is used to implement… Figure 2 or Figure 4 When the communication device 50 is used to implement the function of the master device in the method shown, it can be a master gateway or an MFU. Figure 2 or Figure 4 When the device in the method shown functions as a slave device, the communication device 50 can be a slave gateway or an SFU.

[0156] like Figure 5 As shown, the communication device 50 may include a processor 501 and a transceiver 502, with the processor 501 coupled to the transceiver 502. The processor 501 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD may 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 may refer to a single processor or may include multiple processors; no specific limitation is made here.

[0157] The aforementioned transceiver 502 can also be referred to as a transceiver unit, transceiver, transceiver device, etc. Optionally, the device in the transceiver unit that performs the receiving function can be regarded as a receiving unit, and the device in the transceiver unit that performs the transmitting function can be regarded as a transmitting unit. That is, the transceiver unit includes a receiving unit and a transmitting unit. The receiving unit can also be referred to as a receiver, input port, receiving circuit, etc., and the transmitting unit can be referred to as a transmitter, transmitter, or transmitting circuit, etc.

[0158] Optionally, the communication device 50 further includes a memory 503. The processor 501 is coupled to the memory 503. The memory 503 is primarily used to store software programs and data. The memory 503 can exist independently, connected to the processor 501. Optionally, the memory 503 can be integrated with the processor 501, for example, integrated within one or more chips. The memory 503 can store program code that executes the technical solutions of the embodiments of this application, and its execution is controlled by the processor 501. The various types of computer program code being executed can also be considered as drivers for the processor 501. The memory 503 can include volatile memory, such as random-access memory (RAM); the memory can also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid-state drive (SSD); the memory 503 can also include combinations of the above types of memory. Memory 503 can refer to a single memory or may include multiple memories. For example, memory 503 is used to store various types of data.

[0159] In one implementation, the communication device 50 is used to implement Figure 2 The corresponding method embodiment describes the function of the master device. Specifically, the processor 501 is used to generate a first message, which is a Wireless LAN Management and Control Interface (WMCI) message. The first message is used to manage or control the WLAN function of the first slave device. The first message includes first indication information, which indicates the latency requirements or priority of the WLAN function corresponding to the first message. The transceiver 502 is used to send the first message to the first slave device.

[0160] In one possible implementation, the first indication information includes a first value or a second value, wherein the first value indicates a requirement with delay control, and the second value indicates a requirement without delay control. Optionally, the first indication information is located in the message type identifier field of the first message; or, the first indication information is located in the message length field of the first message.

[0161] In another possible implementation, the first indication information includes at least two values, with different values ​​indicating different priorities. Optionally, the first indication information is located in the message type identifier field of the first message; or, the first indication information is located in the message length field of the first message.

[0162] In one possible implementation, the first message further includes second indication information, which indicates a first control type for managing the WLAN function. The first indication information also indicates the latency requirements or priority of the first control type for the WLAN function. Optionally, the first control type for the WLAN function is any one of WLAN data transmission scheduling control, WLAN roaming control, or WLAN power regulation control.

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

[0164] In one possible implementation, the processor 501 is further configured to generate a second message, which is a WMCI message. The second message is used to manage or control the WLAN function of the first slave device. The second message includes third and fourth indication information. The third indication information indicates the latency requirement or priority of the WLAN function corresponding to the second message. The fourth indication information indicates a second control type for managing the WLAN function, which is different from the first control type. 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. The transceiver 502 is further configured to send the second message to the first slave device.

[0165] In another implementation, the communication device 50 is used to implement Figure 2 This corresponds to the function of the slave device (e.g., the first slave device) in the method embodiment. Specifically, transceiver 502 is used to receive a first message from the master device. The first message is a Wireless LAN Management and Control Interface (WMCI) message, which is used to manage or control the WLAN function of the first slave device. The first message includes first indication information, which indicates the latency requirements or priority of the WLAN function corresponding to the first message. Processor 501 is used to manage and control the WLAN function corresponding to the first message based on the first indication information.

[0166] In one possible implementation, transceiver 502 is further configured to receive a second message from the master device. The second message is a WMCI message, used to manage or control the WLAN function of the first slave device. The second message includes third and fourth indication information. The third indication information indicates the latency requirement or priority of the WLAN function corresponding to the second message. The fourth indication information indicates a second control type for managing the WLAN function, which is different from the first control type. 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. Processor 501 is further configured to prioritize managing the WLAN function corresponding to the first message when the first indication information indicates a latency control requirement and the third indication information indicates no latency control requirement, or when the priority indicated by the first indication information is higher than the priority indicated by the third indication information. For example, communication device 50 prioritizes allocating processing resources in processor 501 to the queue used for processing the first message.

[0167] In one implementation, the communication device 50 is used to implement Figure 4 The corresponding method embodiment describes the function of the master device. Specifically, processor 501 is used to generate a third message, which is a Wireless LAN Management and Control Interface (WMCI) message. This third message is used to manage or control the WLAN function of the first slave device. The third message includes fifth indication information, which indicates a first control type for managing the WLAN function. The first control type corresponds to a first latency requirement or a first priority. Transceiver 502 is used to send the third message to the first slave device.

[0168] In one possible implementation, 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, and the second control type is another control type for the WLAN function managed by the master device for the first slave device. Optionally, the first control type of the WLAN function is any one of WLAN data transmission scheduling control, WLAN roaming control, or WLAN power adjustment control.

[0169] In one possible implementation, the fifth indication information is located in the 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.

[0170] In one possible implementation, the third message is encapsulated in the payload field of the FEM frame, and the FEM port identifier in the frame header of the fiber-to-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 the payload field of a data link layer DLL frame.

[0171] In one possible implementation, processor 501 is further configured to generate a fourth message, which is a WMCI message, used to manage or control the WLAN function of the first slave device. The fourth message includes sixth indication information, which indicates a second control type for managing the WLAN function. This second control type corresponds to a second latency requirement or a second priority, which may differ from a first latency requirement or a first priority. Transceiver 502 is further configured to send the fourth message to the first slave device.

[0172] In another implementation, the communication device 50 is used to implement Figure 4 This corresponds to the function of the slave device (e.g., the first slave device) in the corresponding method embodiment. Specifically, the transceiver 502 is used to receive a third message from the master device. The third message is a Wireless LAN Management and Control Interface (WMCI) message. The third message is used to manage or control the WLAN function of the first slave device. The third message includes fifth indication information, which indicates a first control type for managing the WLAN function. The first control type corresponds to a first latency requirement or a first priority. The processor 501 is used to manage the first control type of the WLAN function based on the third indication information.

[0173] In one possible implementation, transceiver 502 is further configured to receive a fourth message from the master device, the fourth message being a WMCI message, used to manage or control the WLAN function of the first slave device. The fourth message includes sixth indication information, which indicates a second control type for managing the WLAN function. The second control type corresponds to a second latency requirement or a second priority, where the second latency requirement is different from the first latency requirement, or the second priority is different from the first priority. Processor 501 is further configured to prioritize managing the first control type of the WLAN function corresponding to the third message when 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.

[0174] Please refer to the preceding text for details. Figure 2 or Figure 4 The relevant descriptions in the corresponding embodiments will not be repeated here.

[0175] like Figure 6As shown, this application also provides a communication device 60. The communication device 60 can be a slave device (e.g., a first slave device) or a master device, or a component (e.g., an integrated circuit, a chip, etc.) of a slave device (e.g., a first slave device) or a master device. The communication device 60 can also be other communication modules used to implement the methods in the method embodiments of this application.

[0176] The communication device 60 may include a processing module 601 (or processing unit). Optionally, it may also include an interface module 602 (or transceiver unit or transceiver module) and a storage module 603 (or storage unit). The interface module 602 is used to enable communication with other devices. The interface module 602 may be, for example, a transceiver module or an input / output module.

[0177] In one possible design, such as Figure 6 One or more modules may be implemented by one or more processors, or by one or more processors and memory; or by one or more processors and transceivers; or by one or more processors, memory, and transceivers. This application does not limit the implementation in this way. The processors, memory, and transceivers can be configured individually or integrated into one unit.

[0178] The communication device 60 is equipped to implement the functions of a slave device (e.g., a first slave device) as described in the embodiments of this application. For example, the communication device 60 includes modules, units, or means corresponding to the steps described in the embodiments of this application for executing the steps of the slave device (e.g., the first slave device). These functions, units, or means can be implemented in software, hardware, or a combination of both. Further details can be found in the corresponding descriptions in the foregoing method embodiments. Please refer to the preceding text for specific details. Figure 5 The communication device 50 in the corresponding embodiment.

[0179] Alternatively, the communication device 60 may have the functions of the main device described in the embodiments of this application. For example, the communication device 60 includes modules, units, or means corresponding to the steps involved in the main device described in the embodiments of this application. These functions, units, or means can be implemented in software, hardware, or hardware executing corresponding software, or a combination of software and hardware. Further details can be found in the corresponding descriptions in the foregoing method embodiments. Please refer to the preceding text for specific details. Figure 5 The communication device 50 in the corresponding embodiment.

[0180] Furthermore, this application provides a computer program product comprising one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. For example, implementing the aforementioned... Figure 2 or Figure 4 Methods related to the slave device (e.g., the first slave device). For example, implementing the methods described above. Figure 2 or Figure 4 The method relates to the main device in the process. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. The available medium can be magnetic media (e.g., floppy disk, hard disk, magnetic tape), optical media (e.g., digital versatile disc (DVD)), or semiconductor media (e.g., solid-state disk (SSD)).

[0181] Furthermore, this application also provides a computer-readable storage medium storing a computer program that is executed by a processor to perform the aforementioned functions. Figure 2 or Figure 4 Methods related to slave devices (e.g., the first slave device).

[0182] Furthermore, this application also provides a computer-readable storage medium storing a computer program that is executed by a processor to perform the aforementioned functions. Figure 2 or Figure 4 Methods related to the master device in the process.

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

[0184] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. 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, characterized in that, include: The master device sends a first message to the first slave device. The first message is a Wireless LAN Management and Control Interface (WMCI) message. The first message is used to manage or control the wireless LAN (WLAN) function of the first slave device. The first message includes first indication information, which is used to indicate the latency requirements or priority of the WLAN function corresponding to the first message.

2. The method according to claim 1, characterized in that, The first indication information includes a first value or a second value, wherein the first value is used to indicate a need for time delay control, and the second value is used to indicate a need for no time delay control.

3. The method according to claim 1, characterized in that, The first indication information includes at least two values, and different values ​​of the at least two values ​​indicate different priorities.

4. The method according to any one of claims 1 to 3, characterized in that, The first indication information is located in the message type identifier field of the first message; or, the first indication information is located in the message length field of the first message.

5. The method according to claim 4, characterized in that, 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.

6. The method according to any one of claims 1 to 5, characterized in that, The first message also includes second indication information, which indicates a first control type for the first message to manage the WLAN function, and the first indication information further indicates the latency requirement or priority of the first control type of the WLAN function.

7. The method according to claim 6, characterized in that, The first control type of the WLAN function is any one of WLAN data transmission scheduling control, WLAN roaming control, or WLAN power adjustment control.

8. The method according to any one of claims 1 to 7, characterized in that, The first message is encapsulated in the payload field of a fiber-to-room encapsulation mode (FEM) frame, and the FEM port identifier in the frame header of the FEM frame is used to indicate that the first message corresponds to the first slave device.

9. The method according to claim 8, characterized in that, The FEM frame is encapsulated in the payload field of the data link layer DLL frame.

10. The method according to claim 6, characterized in that, The method further includes: The master device sends a second message to the first slave device. The second message is a WMCI message. The second message is used to manage or control the WLAN function of the first slave device. The second message includes a third indication information and a fourth indication information. The third indication information is used to indicate the latency requirement or priority of the WLAN function corresponding to the second message. The fourth indication information is used to indicate a second control type for the second message to manage the WLAN function. The second control type is different from the first control type. 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.

11. The method according to any one of claims 1 to 10, characterized in that, The master device is the main fiber-to-room FTTR unit (MFU), and the slave device is the slave FTTR unit (SFU).

12. 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, characterized in that, include: The first slave device receives a first message from the master device. The first message is a Wireless Local Area Network Management and Control Interface (WMCI) message. The first message is used to manage or control the wireless local area network (WLAN) function of the first slave device. The first message includes first indication information, which is used to indicate the latency requirements or priority of the WLAN function corresponding to the first message. The first slave device manages and controls the WLAN function corresponding to the first message based on the first indication information.

13. The method according to claim 12, characterized in that, The first indication information includes a first value or a second value, wherein the first value is used to indicate a need for time delay control, and the second value is used to indicate a need for no time delay control.

14. The method according to claim 12, characterized in that, The first indication information includes at least two values, and different values ​​of the at least two values ​​indicate different priorities.

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

16. The method according to claim 15, characterized in that, 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.

17. The method according to any one of claims 12 to 16, characterized in that, The first message also includes second indication information, which indicates a first control type for the first message to manage the WLAN function, and the first indication information further indicates the latency requirement or priority of the first control type of the WLAN function.

18. The method according to claim 17, characterized in that, The first control type of the WLAN function is any one of WLAN data transmission scheduling control, WLAN roaming control, or WLAN power adjustment control.

19. The method according to any one of claims 12 to 18, characterized in that, The first message is encapsulated in the payload field of an FEM frame, and the FEM port identifier in the frame header of the FEM frame is used to indicate that the first message corresponds to the first slave device.

20. The method according to claim 19, characterized in that, The FEM frame is encapsulated in the payload field of the data link layer DLL frame.

21. The method according to claim 17, characterized in that, 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 the 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 the latency requirement or priority of the WLAN function corresponding to the second message. The fourth indication information is used to indicate a second control type for the second message to manage the WLAN function. The second control type is different from the first control type. 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.

22. The method according to claim 21, characterized in that, The method further includes: When the first indication information indicates a need for latency control and the third indication information indicates no need for latency control, or when the priority of the first indication information is higher than the priority of the third indication information, the first slave device prioritizes the management and control of the WLAN function corresponding to the first message.

23. The method according to any one of claims 12 to 22, characterized in that, The master device is the master FTTR unit (MFU), and the slave device is the slave FTTR unit (SFU).

24. A communication device, characterized in that, include: A processor and a transceiver, the processor being connected to the transceiver, the processor being configured to implement the method as described in any one of claims 1 to 11.

25. A communication device, characterized in that, include: A processor and a transceiver, the processor being connected to the transceiver, the processor being configured to implement the method as described in any one of claims 12 to 23.

Images