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. In the method, a master device sends a third message to a first slave device, the third message is a wireless local area network management and control interface (WMCI) message, the third message is used for managing or controlling a wireless local area network (WLAN) function of the first slave device, the third message comprises fourth indication information and fifth indication information, the fourth indication information is used for indicating a first characteristic, and the fifth indication information is used for indicating a second characteristic. The fifth indication information is used for indicating whether the first characteristic of the first slave device is started or not. The master device can flexibly configure the first characteristic of the first slave device, so that the efficiency of controlling the first slave device by the master device is improved.

Description

[0001] This application is a divisional application. The application number of the original application is 202510183400.9, and the original application date is February 18, 2025. The entire content of the original application is incorporated herein by reference; and the original application claims the priority of a Chinese patent application with the application number 202411564842.X and the application title "An Optical Network Communication Method and a Communication Device" filed with the China National Intellectual Property Administration on November 4, 2024, and its entire content is incorporated herein by reference. Technical Field

[0002] Embodiments of the present application relate to the field of optical communication, and in particular, to an optical network communication method and a communication device. Background Art

[0003] Fiber to the room (FTTR) refers to a technology that uses optical fibers instead of network cables to provide optical fiber medium access to rooms in the downlink of an optical network device (for example, an optical network terminal (ONT)). The optical fiber network in this FTTR scenario includes a master device and one or more slave devices (also called sub-devices). A management channel can be established between the master device and the slave device, so that the master device can send messages related to management or control to the slave device through the management channel to implement the management or control of some functions of the slave device by the master device. For example, a WMCI management channel can be established between the master device and the slave device based on the Wireless Local Area Network Management and Control Interface (WMCI) protocol, so that WMCI messages can be exchanged between the master device and the slave device through the WMCI management channel, thereby implementing the management or control of the Wireless Local Area Network (WLAN) function.

[0004] In the current standard, the definition of the format of WMCI messages is not clear, which is not conducive to the master device to efficiently manage and control the slave device. Summary of the Invention

[0005] The present application provides an optical network communication method and a communication device. By defining indication information to indicate the operation type of WMCI messages, it is beneficial to improve the management and control efficiency between the master device and the slave device.

[0006] In a first aspect, the present application provides an optical network communication method, which is applied to an optical fiber network. The optical fiber network includes a master device and at least one slave device, and the at least one slave device includes 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 can be executed by a partial functional module or chip in the master device. Taking the 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, and the third message is used to manage or control the Wireless Local Area Network (WLAN) function of the first slave device. The third message includes a fourth indication information and a fifth indication information. The fourth indication information is used to indicate a first characteristic, and the fifth indication information is used to indicate whether to enable the first characteristic of the first slave device.

[0007] In this aspect, the third message sent by the master device to the first slave device includes a fourth indication information and a fifth indication information. By using the fourth indication information and the fifth indication information to indicate whether to enable or disable the first characteristic of the first slave device, it is beneficial for the master device to flexibly configure the first characteristic of the first slave device, thereby improving the efficiency of the master device in managing and controlling the first slave device.

[0008] In a possible implementation manner, the third message includes a message content field. The fourth indication information is located in the first two bytes of the message content field, and the fifth indication information is located in the remaining bytes of the message content field.

[0009] In a possible implementation manner, the first two bytes of the message content field are a parameter mask field, and the fourth indication information is a bit of the parameter mask field.

[0010] In a possible implementation manner, the fifth indication information includes a first value and a second value. The first value is used to indicate enabling the first characteristic, and the second value is used to indicate disabling the first characteristic.

[0011] In a possible implementation manner, the third message further includes a second indication information. The second indication information is used to indicate a parameter set of the third message, and the first characteristic is a characteristic indicated by a parameter in the parameter set.

[0012] In a possible implementation manner, the parameter set includes a WMCI characteristic parameter set, and the first characteristic is a characteristic related to WMCI.

[0013] In a possible implementation manner, the second indication information is located in the message type identification field of the third message.

[0014] In a possible implementation manner, the characteristics related to WMCI include at least one of the following:

[0015] Time domain scheduling characteristics; or, energy saving characteristics; or, enhanced distributed channel access (EDCA) characteristics; or, roaming characteristics; or, spatial division multiplexing characteristics; or, frequency domain scheduling characteristics; or, Wi-Fi time synchronization characteristics.

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

[0017] The master device receives a fourth message from the first slave device. The fourth message is a wireless local area network management control interface (WMCI) message, and is used to manage or control the wireless local area network (WLAN) function of the first slave device. The fourth message includes fourth indication information and sixth indication information. The fourth indication information is used to indicate a first characteristic, and the sixth indication information is used to indicate whether to enable the first characteristic of the first slave device.

[0018] In this implementation manner, the master device can receive the fourth message from the first slave device. The fourth message includes fourth indication information and sixth indication information, and indicates whether the first characteristic of the first slave device is successfully enabled or not through the fourth indication information and the sixth indication information. This is beneficial for the master device to accurately know the configuration result of the first characteristic, thereby improving the efficiency of the master device in controlling the first slave device.

[0019] In a possible implementation manner, the fourth message includes a message content field. The fourth indication information is located in the first two bytes of the message content field, and the sixth indication information is located in the remaining bytes of the message content field.

[0020] In a possible implementation manner, the sixth indication information includes a first value and a second value. The first value is used to indicate enabling the first characteristic, and the second value is used to indicate not enabling the first characteristic.

[0021] In a possible implementation manner, the fourth message further includes second indication information, and the second indication information is located in the message type identification field of the fourth message.

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

[0023] In this embodiment, the FEM port ID in the frame header of the FEM frame is assigned by the master device. This FEM port ID can not only indicate that the third message is a WMCI message, but also be used to indicate the transceiver object of this WMCI message (i.e., the third message), that is, to indicate that this WMCI message (i.e., the third message) corresponds to the first slave device rather than other slave devices. Therefore, the WMCI message can be distinguished from other control messages in the FTTR system through the FEM port ID, which is beneficial to improving the control efficiency of the WLAN function.

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

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

[0026] In a second aspect, the present application provides an optical network communication method, which is applied to an optical fiber network. The optical fiber network includes a master device and at least one slave device, and the at least one slave device includes a first slave device. The optical network communication method provided in this aspect can be executed by the first slave device in the optical fiber network, or can be executed by 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 is a wireless local area network management and control interface (WMCI) message, and the third message is used to manage or control the wireless local area network (WLAN) function of the first slave device. The third message includes fourth indication information and fifth indication information. The fourth indication information is used to indicate a first characteristic, and the fifth indication information is used to indicate whether to enable the first characteristic of the first slave device; then, the first slave device configures the first characteristic based on the third message.

[0027] In a possible implementation, the third message includes a message content field. The fourth indication information is located in the first two bytes of the message content field, and the fifth indication information is located in the remaining bytes of the message content field.

[0028] In a possible implementation, the first two bytes of the message content field are a parameter mask field, and the fourth indication information is a bit of the parameter mask field.

[0029] In a possible implementation, the fifth indication information includes a first value and a second value. The first value is used to indicate enabling the first characteristic, and the second value is used to indicate not enabling the first characteristic.

[0030] In a possible implementation, the third message further includes second indication information, where the second indication information is used to indicate a parameter set of the third message, and the first characteristic is a characteristic indicated by a parameter in the parameter set.

[0031] In a possible implementation, the parameter set includes a WMCI characteristic parameter set, and the first characteristic is a characteristic related to WMCI.

[0032] In a possible implementation, the second indication information is located in the message type identification field of the third message.

[0033] In a possible implementation, the characteristics related to WMCI include at least one of the following:

[0034] Time domain scheduling characteristic; or, energy saving characteristic; or, coordinated enhanced distributed channel access (EDCA) characteristic; or, roaming characteristic; or, spatial division multiplexing characteristic; or, frequency domain scheduling characteristic; or, Wi-Fi time synchronization characteristic.

[0035] In a possible implementation, the method further includes: a first slave device sending a fourth message to a master device, where the fourth message is a wireless local area network management and control interface (WMCI) message, and the fourth message is used to manage or control the wireless local area network (WLAN) function of the first slave device. The fourth message includes fourth indication information and sixth indication information, where the fourth indication information is used to indicate the first characteristic, and the sixth indication information is used to indicate whether to enable the first characteristic of the first slave device.

[0036] In a possible implementation, the fourth message includes a message content field, the fourth indication information is located in the first two bytes of the message content field, and the sixth indication information is located in the remaining bytes of the message content field.

[0037] In a possible implementation, the sixth indication information includes a first value and a second value, where the first value is used to indicate enabling the first characteristic, and the second value is used to indicate not enabling the first characteristic.

[0038] In a possible implementation, the fourth message further includes second indication information, where the second indication information is located in the message type identification field of the fourth message.

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

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

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

[0042] It should be noted that there are also various other specific implementation manners in the embodiments of the present application. For specific details, reference can be made to the specific implementation manners and their beneficial effects in the first aspect, which will not be elaborated here.

[0043] In a third aspect, the present application provides a communication device, which is applied to an optical fiber network. The optical fiber network includes a master device and at least one slave device, and the at least one slave device includes a first slave device. The communication device can be the master device in the optical fiber network, or a partial functional module or chip in the master device. The communication device includes a transceiver and a processor. Among them, the processor is used to generate a third message, and the transceiver is used to send the third message. Among them, the third message is a wireless local area network management control interface WMCI message, and the third message is used to manage or control the wireless local area network WLAN function of the first slave device. The third message includes fourth indication information and fifth indication information. The fourth indication information is used to indicate a first characteristic, and the fifth indication information is used to indicate whether to enable the first characteristic of the first slave device.

[0044] In a possible implementation, the transceiver is further configured to receive a fourth message from the first slave device. The fourth message is a wireless local area network management control interface WMCI message, and the fourth message is used to manage or control the wireless local area network WLAN function of the first slave device. The fourth message includes fourth indication information and sixth indication information. The fourth indication information is used to indicate a first characteristic, and the sixth indication information is used to indicate whether to enable the first characteristic of the first slave device.

[0045] It should be noted that there are also various other specific implementation manners in the embodiments of the present application. For specific details, reference can be made to the specific implementation manners and their beneficial effects in the first aspect, which will not be elaborated here.

[0046] In a fourth aspect, the present application provides a communication device, which is applied to an optical fiber network. The optical fiber network includes a master device and at least one slave device, and the at least one slave device includes a first slave device. The communication device can be the first slave device in the optical fiber network, or a partial functional module or chip in the first slave device. The communication device includes a transceiver and a processor. Among them, the transceiver is configured to receive a third message from the master device. The third message is a wireless local area network management control interface WMCI message, and the third message is used to manage or control the wireless local area network WLAN function of the first slave device. The third message includes fourth indication information and fifth indication information. The fourth indication information is used to indicate a first characteristic, and the fifth indication information is used to indicate whether to enable the first characteristic of the first slave device; then, the first slave device configures the first characteristic based on the third message.

[0047] In a possible implementation, a processor is configured to generate a fourth message, and a transceiver is configured to send the fourth message. The fourth message is a Wireless Local Area Network Management and Control Interface (WMCI) message, which is used to manage or control the Wireless Local Area Network (WLAN) function of a first slave device. The fourth message includes fourth indication information and sixth indication information. The fourth indication information is used to indicate a first characteristic, and the sixth indication information is used to indicate whether to enable the first characteristic of the first slave device.

[0048] It should be noted that there are also various other specific implementation manners in the embodiments of the present application. For specific details, reference may be made to the specific implementation manners and their beneficial effects in the second aspect, which will not be elaborated here.

[0049] In a fifth aspect, an embodiment of the present application provides a communication device, which may be the master device in the foregoing implementation manners, or a chip within the master device. The communication device may include a processing module and a transceiver module. When the communication device is the master device, the processing module may be a processor, and the transceiver module may be a transceiver; the master device may further include a storage module, and the storage module may be a memory; the storage module is configured to store instructions, and the processing module executes the instructions stored in the storage module, so that the master device executes the method in the first aspect or any one of the implementation manners of the first aspect. When the communication device is a chip within the master device, the processing module may be a processor, and the transceiver module may be an input / output interface, a pin, a circuit, etc.; the processing module executes the instructions stored in the storage module, so that the master device executes the method in the first aspect or any one of the implementation manners of the first aspect. The storage module may be a storage module within the chip (e.g., a register, a cache, etc.), or a storage module outside the chip within the master device (e.g., a read-only memory, a random access memory, etc.).

[0050] Sixth aspect, an embodiment of the present application provides a communication device. The communication device may be a slave device (e.g., the first slave device) 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, and the storage module may be a memory; the storage module is used to store instructions, and the processing module executes the instructions stored in the storage module so that the slave device (e.g., the first slave device) executes the method in the second aspect or any one of the embodiments of the second aspect. When the communication device is a chip within the slave device (e.g., the first slave device), the processing module may be a processor, and the transceiver module may be an input / output interface, a pin, a circuit, etc.; the processing module executes the instructions stored in the storage module so that the slave device (e.g., the first slave device) executes the method in the second aspect or any one of the embodiments of the second aspect. The storage module may be a storage module within the chip (e.g., a register, a cache, etc.), or a storage module outside the chip within the slave device (e.g., a read-only memory, a random access memory, etc.).

[0051] Seventh aspect, the present application provides a communication device, and the communication device may be an integrated circuit chip. The integrated circuit chip includes a processor. The processor is coupled to a memory, and the memory is used to store programs or instructions. When the programs or instructions are executed by the processor, the communication device is caused to execute the methods and the foregoing aspects introduced in any one of the various embodiments of the foregoing aspects.

[0052] Eighth aspect, an embodiment of the present application provides a computer program product containing instructions. When the foregoing instructions run on a computer, the computer is caused to execute the methods introduced in any one of the various embodiments of the foregoing aspects.

[0053] Ninth aspect, an embodiment of the present application provides a computer-readable storage medium, including instructions. When the instructions run on a computer, the computer is caused to execute the methods introduced in any one of the various embodiments of the foregoing aspects.

[0054] Tenth aspect, an embodiment of the present application provides an optical fiber network. The optical fiber network includes the master device in the foregoing third aspect and any one of the embodiments of the third aspect, and the slave device (e.g., the first slave device) in the foregoing fourth aspect and any one of the embodiments of the fourth aspect. Description of the Drawings

[0055] Figure 1AAn example diagram of the network architecture of an optical fiber network;

[0056] Figure 1B Another example diagram of the network architecture of an optical fiber network;

[0057] Figure 1C An example diagram of an FTTR system;

[0058] Figure 2 A flowchart of an optical network communication method in this application;

[0059] Figure 3 Another flowchart of an optical network communication method in this application;

[0060] Figure 4 Another flowchart of an optical network communication method in this application;

[0061] Figure 5A An example diagram of an FEM frame encapsulating a WMCI message;

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

[0063] Figure 5C An example diagram of a DLL frame encapsulating an FEM frame;

[0064] Figure 5D An example diagram of a DLL frame encapsulating an XFEM frame;

[0065] Figure 6 A schematic diagram of an embodiment of a communication device in this application;

[0066] Figure 7 Another schematic diagram of an embodiment of a communication device in this application. Detailed implementation manners

[0067] Next, the technical solutions in the embodiments of this application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of this application. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all the embodiments.

[0068] In each embodiment of this application, if there is no special description and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0069] The terms "first", "second", "third", "fourth", etc. (if any) in the description, claims and above-mentioned drawings of this application are used to distinguish similar objects and do not necessarily describe a specific order or sequence. It should be understood that such terms can be interchanged under appropriate circumstances so that the embodiments described herein can be implemented in an order different from that shown or described herein. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that comprises a series of steps or units does not necessarily limit to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0070] It should be understood that the term "and / or" herein is merely a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " herein generally represents an "or" relationship between the associated objects before and after.

[0071] The optical network communication method provided by this application is applied to an optical fiber network. Figure 1A An example diagram of the architecture of an optical fiber network in the prior art. As Figure 1AAs shown in the figure, the optical fiber network includes an optical line terminal (OLT), an optical distribution network (ODN), and an optical network unit (ONU) (or an optical network terminal (ONT)). The OLT and the ONU are connected and communicate with each other through optical fibers. The OLT is generally connected to the ONU (or ONT) through the ODN. The ODN includes a network composed of one or more optical devices such as optical fibers, optical distribution frames (ODFs), optical splitters (also known as beam splitters), combiners, etc. In addition, the foregoing OLT can be connected to the operator network through a network-side interface, the OLT can be connected to the ODN through a dedicated interface, and the ODN is connected to the ONU (or ONT) through a dedicated interface. In the downstream direction, the OLT broadcasts the downstream optical signal, and distributes the downstream optical signal to each ONU (or ONT) through the ODN. In the upstream direction, using the time division multiple access (TDMA) method, each ONU (or ONT) sends an upstream optical signal in its respective upstream time slot allocated by the OLT. It should be noted that the present application does not limit the specific type of the optical fiber. The optical fiber described in the present application can be a single optical fiber, a loose tube optical fiber, an optical cable, or an optical and electrical composite cable, etc.

[0072] Figure 1B This is a schematic structural diagram of the optical fiber network provided by the present application. As Figure 1BAs shown in the figure, the optical fiber network provided by this application includes a master device 01 and at least one slave device 02. The master device 01 is connected to at least one slave device 02 through an optical fiber. For example, the master device 01 is connected to at least one slave device 02 through an optical distribution network. The master device 01 can manage or control the specific functions of one or more slave devices 02 based on at least one protocol. For example, the master device 01 can manage or control the wireless local area network (WLAN) 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 has a WLAN function; it can also be understood that the master device 01 and / or the slave device 02 has a wireless fidelity (WiFi) function. Exemplarily, in the fiber to the room (FTTR) scenario, the master device 01 can be called a main FTTR unit (MFU), an FTTR master device, or a main gateway, and the slave device 02 can be called a sub FTTR unit (SFU), an FTTR slave device, or a slave gateway.

[0073] Figure 1C This is an example diagram of the network location of FTTR. As Figure 1C shown, FTTR is a network that provides fiber optic coverage inside the broadband customer network (such as a home or office) based on FTTH / 0. Optical fibers are used to connect the FTTR master device to the FTTR slave devices in each room. Both the FTTR master device and the FTTR slave device can be connected to user terminals through wireless or wired interfaces, or can be connected to user terminal devices through an adapter device such as a set-top box. Among them, the north side of the FTTR master device is connected to an access node (AN) device as an access network network terminal. The FTTR transceiver unit on the south side of the FTTR master device is connected to the FTTR transceiver unit of the FTTR slave device through an indoor fiber distribution network (IFDN), and also provides gateway functions and other network functions. The FTTR transceiver unit of the FTTR slave device is connected to the TTTP transceiver unit of the FTTR master device through the indoor fiber distribution network and provides terminal access through a wireless or wired interface. The indoor fiber distribution network is a point-to-multipoint fiber optic infrastructure, which can be completely passive and is usually composed of passive devices such as interconnected optical cables and optical splitters. It can also provide remote power feeding functions for FTTR slave devices by using hybrid fiber-coaxial cables and hybrid fiber-coaxial splitters.

[0074] Exemplarily, in the FTTR system management architecture, the master device manages or controls the WLAN function of the slave device by interacting with WMCI messages. Since the master device may have different management requirements and characteristics. However, in the current standard, the definition of the format of WMCI messages is not clear, which is not conducive to efficient communication between the master device and the slave device.

[0075] This application provides an optical network communication method and a communication device. By defining indication information to indicate the operation type of WMCI messages, it is beneficial to improve the management and control efficiency between the master device and the slave device.

[0076] The following will combine Figure 2 and Figure 3 to introduce the main processes of the optical network communication method provided by this application applied in the downlink communication scenario and the uplink communication scenario:

[0077] As Figure 2 shown, it is a flowchart of an embodiment of the optical network communication method provided by this application. In this embodiment, the scenario where the master device sends a message to the first slave device is taken as an example for illustration. Of course, the entity that executes the actions of the master device in this method can also be a device, module, or chip in the master device; the entity that executes the actions of the first slave device in this method can also be a device, module, or chip in the first slave device. This embodiment does not make specific limitations in this regard. Exemplarily, as Figure 2 shown, the optical network communication method includes the following steps:

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

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

[0080] Among them, the first message is a WMCI message for managing or controlling (hereinafter simply referred to as managing and controlling) the WLAN function of the first slave device. The first message includes first indication information, and the first indication information is used to indicate the operation type of the first message. It should be noted that the operation type in this embodiment and subsequent embodiments can also be referred to as operation code, control type, control code, action type, or action code, etc., and no limitation is made here. In this embodiment and subsequent embodiments, the term "operation type" is mainly used for introduction as an example.

[0081] In a possible implementation, the operation type of the first message includes a parameter request type, that is, the first indication information indicates that the operation type of the first message is a parameter request type. This parameter request type means that the master device requests the first slave device to send the parameters of the first slave device to the master device, that is, it requires the first slave device to send the parameters of the first slave device to the master device. It can be understood that a message of the parameter request type (for example, the first message) is used to request the receiving end (for example, the first slave device) to report one or more parameters. Therefore, the receiving end (for example, the first slave device) needs to send the parameters requested by the first message to the sending end (for example, the master device). Among them, the aforementioned parameters can be the inherent parameters of the first slave device or the parameters already configured by the master device for the first slave device, which is not limited here.

[0082] In another possible implementation, the operation type of the first message includes a parameter configuration type, that is, the first indication information indicates that the operation type of the first message is a parameter configuration type. This parameter configuration type means that the master device sends the configuration parameters of the first slave device to the first slave device. It can be understood that a message of the parameter configuration type (for example, the first message) is used to configure one or more parameters for the receiving end (for example, the first slave device).

[0083] It should also be noted that "parameter request type" and "parameter configuration type" are only names, and other names can also be used to describe the above two operation types. For example, the above two operation types can also be called "first operation type" and "second operation type", etc., and examples are not listed one by one here.

[0084] It should be noted that the parameters in the above two implementations can be determined by another indication information in the first message. Optionally, the first message further includes second indication information, and the second indication information is used to indicate the parameter set corresponding to the first message. For example, the parameter set configured by the first message, or the capability parameter set requested by the first message. The parameter set can be understood as a set with multiple parameters. Exemplarily, if the operation type of the first message is a parameter request type, the parameter set indicated by the second indication information means which parameter set the parameters requested by the first message belong to, that is, which parameter set the parameters requested by the master device from the first slave device through the first message belong to. If the operation type of the first message is a parameter configuration type, the parameter set indicated by the second indication information means which parameter set the parameters configured by the first message belong to, that is, which parameter set the parameters configured by the master device for the first slave device through the first message belong to.

[0085] It should also be noted that the parameters included in a parameter set are generally of the same type or have similar functions. Therefore, a parameter set can also be understood as a parameter type. The second indication information can also be understood as being used to indicate the parameter type corresponding to the first message. For example, the parameter type of the parameters configured by the first message, or the parameter type of the parameters requested by the first message. Exemplarily, if the operation type of the first message is a parameter request type, the parameter type indicated by the second indication information represents the parameter type of the parameters requested by the first message, that is, the type of parameters that the master device requests the first slave device to report through the first message. If the operation type of the first message is a parameter configuration type, the parameter type indicated by the second indication information represents the parameter type of the parameters configured by the first message, that is, the type of parameters that the master device configures for the first slave device through the first message.

[0086] It can be seen that in the case where the first message includes both the first indication information and the second indication information, if the first indication information indicates that the operation type of the first message is a parameter request type, then this parameter request type means that the master device requests the first slave device to send the parameters of the parameter set (or parameter type) indicated by the second indication information to the master device; if the first indication information indicates that the operation type of the first message is a parameter configuration type, then the parameter configuration type means that the master device sends the configuration parameters of the parameter set (or parameter type) indicated by the second indication information to the first slave device.

[0087] Optionally, the first indication information includes a first value or a second value. Among them, the first value is used to indicate that the operation type of the first message is a parameter request type; the second value is used to indicate that the operation type of the first message is a parameter configuration type.

[0088] Optionally, the first indication information is represented by at least one bit newly defined in the WMCI message. In one example, the first indication information is one bit newly defined in the WMCI message, that is, the first value and the second value are two values of the newly defined 1 bit. The two values of this bit respectively indicate the parameter request type and the parameter configuration type. For example, when the value of this bit is 1, it indicates that the operation type of the first message is the parameter request type; when the value of this bit is 0, it indicates that the operation type of the first message is the parameter configuration type. Another example, when the value of this bit is 0, it indicates that the operation type of the first message is the parameter request type; when the value of this bit is 1, it indicates that the operation type of the first message is the parameter configuration type. In another example, the first indication information is two bits newly defined in the WMCI message, that is, the first value and the second value are two values of the newly defined 2 bits. The two values of this bit respectively indicate the parameter request type and the parameter configuration type. For example, when the value of these 2 bits is 01, it indicates that the operation type of the first message is the parameter request type; when the value of these 2 bits is 00, it indicates that the operation type of the first message is the parameter configuration type. Another example, when the value of these 2 bits is 11, it indicates that the operation type of the first message is the parameter request type; when the value of these 2 bits is 00, it indicates that the operation type of the first message is the parameter configuration type. This embodiment does not limit the specific implementation manner of the first value and the second value, as long as the first value is different from the second value. In addition, the first indication information can also be implemented with three bits, or even four bits. Examples are not listed one by one here.

[0089] Specifically, the first indication information can be carried in the first message in any of the following ways:

[0090] In a possible implementation manner, the first indication information is located in the message length field of the first message, and the message length field is used to indicate the length of the message content carried by the first message. The first indication information is located in a certain bit or certain two bits of the first byte of the message length field. For example, the first indication information is located in bit 7 of the first byte of the message length field, that is, the 7th bit from low to high of the first byte. Another example, the first indication information is located in bit 7 and bit 6 of the first byte of the message length field, that is, the 6th bit and the 7th bit from low to high of the first byte.

[0091] Optionally, the message length field further includes processing requirement indication information for indicating the priority of the message. For example, the processing requirement indication information is located in bit 8 of the first byte of the message length field, i.e., the highest bit of the first byte. In this case, the message length field can also be referred to as the message length and processing requirement field. For example, the message length and processing requirement field of the first message includes processing requirement indication information and first indication information, where the processing requirement indication information is located in bit 8 of the first byte of the message length and processing requirement field, and the first indication information is located in bit 7 of the first byte of the message length and processing requirement field.

[0092] Exemplarily, Table 1-1 below is an example of the first message when the first indication information is implemented using one bit in the message length and processing requirement field.

[0093] Table 1-1

[0094]

[0095] As shown in Table 1-1, the first byte is the message type identification field (which can also be referred to as the message type ID (message type ID) field) for indicating the type of the message and defining the semantics of the message content. The second byte is the sequence number (sequence number, SeqNo) field containing a sequence number counter for ensuring the robustness of the WMCI message delivery channel. In the downlink direction, the sequence number field is filled with the value of the sequence number counter of the corresponding master device. The master device maintains a separate sequence number counter for each unicast and broadcast WMCI message stream to each slave device. Each sequence number counter rolls over from 255 to 1, and the value 0 is not used in the downlink. The 3rd - 4th bytes are the message length and processing requirement (message length and processing requirement) field, which consists of three fields: the priority of the message, the operation type, and the length of the message content. Among them, X (the most significant bit of the 3rd byte): is used to indicate the priority of processing this message. When X = 1, it indicates that the message has a high priority; when X = 0, it indicates that the message has a lower priority. C: is the first indication information introduced above for indicating the operation type of this message. In the downlink direction, when C = 1, it indicates that the operation type of the message is the parameter request type, indicating that the master device requests the first slave device to send the parameters of the first slave device to the master device, i.e., requiring the first slave device to send the parameters of the first slave device to the master device; when C = 0, it indicates that the operation type of the message is the parameter configuration type, indicating that the master device sends the configuration parameters of the first slave device to the first slave device. LL LLLL LLLL: represents the length of the message content, with a value range of 0 - 1023. The remaining 4 bits RRRR are reserved.

[0096] It should be noted that the second indication information may be carried in the message type identification field of the first message, and the second indication information indicates the parameter set or parameter type corresponding to the first message. For example, the lower n bits in the message type identification field are used to carry the second indication information, where n is an integer greater than 2. For example, n = 5, that is, the 1st to 5th bits of the 1st byte of the first message carry the second indication information. Another example, n = 6, that is, the 1st to 6th bits of the 1st byte of the first message carry the second indication information.

[0097] It should be noted that carrying the second indication information in the message type identification field can be understood as classifying WMCI messages according to different parameter sets (or parameter types) obtained or configured. When the first message contains both the first indication information and the second indication information, if the first indication information indicates that the operation type of the first message is a parameter request type, and the second indication information is carried in the message type identification field, then this parameter request type means that the master device requests the first slave device to send the parameters of the parameter set (or parameter type) indicated by the message type identification field to the master device; if the first indication information indicates that the operation type of the first message is a parameter configuration type, and the second indication information is carried in the message type identification field, then the parameter configuration type means that the master device sends the configuration parameters of the parameter set (or parameter type) indicated by the message type identification field to the first slave device. Taking Table 1-1 as an example, in the downlink direction, when C = 1, it indicates that the operation type of this message is a parameter request type, and it is required that the slave device (for example, the first slave device) send the output indicated by the message type ID field; when C = 0, it indicates that this message is a parameter configuration message, and the parameter type configured by this message is indicated by the message type ID field.

[0098] In addition, the 5th to Nth bytes are the message content field, which is used to carry the specific content of the message and is related to the specific message. Among them, the 5th to 6th bytes are used to carry the parameter mask (referred to as the parameter mask field), and the parameter mask field is used to indicate the parameters in the parameter set corresponding to the first message. For example, the parameter mask field is used to indicate which parameters in the request parameter set are needed, or which parameters in the configuration parameter set need to be configured. It should be noted that since the size of the parameter mask is 16 bits (i.e., 2 bytes), a parameter set can contain at most 16 parameters, and the message type of each parameter set can carry at most 16 parameters. In addition, the 7th to Nth bytes are used to carry the parameter content of the parameters indicated by the parameter mask, and the parameter content should be filled into the message content in the order indicated by the parameter mask. For a downlink request message, the parameter mask represents the parameters that the master device wants to obtain. For an uplink message, the parameter mask represents the reported and replied parameters. Here, N is an integer greater than 7. It should be noted that when C = 1, that is, when the operation type of the message is the parameter request type, the 7th to Nth bytes are invalid. After receiving this message, the receiving end (for example, the first slave device) should feedback the corresponding parameters according to the indication. The (N + 1)th to (N + 4)th bytes are the message integrity check field, with a size of 4 bytes, which is used to verify the identity of the sender and prevent forged WMCI message attacks. The function of this field follows the cyclic redundancy check (CRC) function.

[0099] Exemplarily, Table 1-2 below shows an example of the first message when the first indication information is represented by two bits in the message length and processing requirement fields.

[0100] Table 1-2

[0101]

[0102] As shown in Table 1-2, the example only differs from the example shown in Table 1-1 in terms of the message length and the processing requirement field. For the explanations of the remaining fields, please refer to the description shown in Table 1-1 above, which will not be elaborated here. The first indication information can be represented by the 6th to 7th bits of the first byte of the message length and the processing requirement field. For example, in the third byte, X: is used to indicate the priority of processing this message. When X = 1, it means the message has a high priority; when X = 0, it means the message has a lower priority. CC: is the first indication information introduced above and is used to indicate the operation type of this message. In the downlink direction, when CC = 11, it identifies that the operation type of this message is the parameter request type, indicating that the master device requests the first slave device to send the parameters of the first slave device to the master device, that is, it requires the first slave device to send the parameters of the first slave device to the master device; when CC = 00, it identifies that the operation type of this message is the parameter configuration type, indicating that the master device sends the configuration parameters of the first slave device to the first slave device. LL LLLL LLLL: represents the length of the message content, and the value range is 0 to 1023. The remaining 3 bits RRR are reserved.

[0103] For example, in the downlink direction, when CC = 11, it identifies that the operation type of this message is the parameter request type, and it requires the slave device (for example, the first slave device) to send the output indicated by the message type ID field; when CC = 00, it identifies that this message is a parameter configuration type message, and the parameter type configured by this message is indicated by the message type ID field.

[0104] It should be understood that the value of bit C in Table 1-1 and the value of bit CC in Table 1-2 are only examples. In actual applications, other values can also be used to represent similar functions, and examples will not be listed one by one here.

[0105] In another possible implementation, the first indication information is located in the message type identification field of the first message. The second indication information may be carried in the message type identification field of the first message, and the second indication information indicates the parameter set or parameter type corresponding to the first message. For example, the size of the message type identification field is 1 byte (8 bits). The lower n bits in this message type identification field can be used to carry the second indication information, and the higher m bits carry the first indication information, where n is an integer greater than 2, m is an integer greater than 0, and m + n ≤ 8. For example, n = 5, m = 1. The 1st to 5th bits from the lowest to the highest of the 1st byte of the first message carry the second indication information, and the highest bit of the 1st byte of the first message (i.e., the 8th bit from the lowest to the highest) carries the first indication information. Another example, n = 5, m = 2. The 1st to 5th bits from the lowest to the highest of the 1st byte of the first message carry the second indication information, and the 7th to 8th bits from the lowest to the highest of the 1st byte of the first message carry the first indication information. Another example, n = 6, m = 1. The 1st to 6th bits from the lowest to the highest of the 1st byte of the first message carry the second indication information, and the highest bit of the 1st byte of the first message (i.e., the 8th bit from the lowest to the highest) carries the first indication information. Another example, n = 6, m = 2. The 1st to 6th bits from the lowest to the highest of the 1st byte of the first message carry the second indication information, and the 7th to 8th bits from the lowest to the highest of the 1st byte of the first message carry the first indication information.

[0106] Exemplarily, Table 1-3 below is an example of the first message when the first indication information is implemented using one bit in the message type identification.

[0107] Table 1-3

[0108]

[0109] As shown in Table 1-3, the example shown in Table 1-1 differs only in the message length, processing requirement field and message type identification field. For the explanation of the remaining fields, please refer to the description shown in Table 1-1 above, which will not be repeated here. The 1st to 5th bits from low to high of the first byte of the first message carry the second indication information, and the highest bit of the first byte of the first message (i.e., the 8th bit from low to high) carries the first indication information. In the downlink direction, when C=1, the operation type of the message is identified as a parameter request type, indicating that the master device requests the first slave device to send the parameters of the first slave device to the master device, that is, requires the first slave device to send the parameters of the first slave device to the master device; when C=0, the operation type of the message is identified as a parameter configuration type, indicating that the master device sends the configuration parameters of the first slave device to the first slave device. In the downlink direction, when C=1, it indicates that the operation type of the message is a parameter request type, requiring the slave device (for example, the first slave device) to send the output indicated by the second indication information (i.e., bit ZZZZZ); when C=0, it indicates that the message is a parameter configuration message, and the parameter type configured by the message is indicated by the second indication information (i.e., bit ZZZZZ). In addition, in the third byte, X: is used to indicate the priority of processing this message. When X=1, it indicates that the message has a high priority; when X=0, it indicates that the message has a low priority. LLLLLL LLLL: indicates the length of the message content, ranging from 0 to 1023. The remaining 5 bits RRRRR are reserved.

[0110] Optionally, the parameter set indicated by the second indication information may be any one of the following:

[0111] (1) A device capability parameter set of the slave device WLAN, which includes parameters related to the WLAN capability of the slave device, such as Wi-Fi version number, number of Wi-Fi frequency bands, number of supported service set identifiers (SSIDs), supported transmit power levels, number of antennas, multiple-in-multiple-out (MIMO) capability, etc.

[0112] Exemplarily, the meanings of the parameters included in the device capability parameter set of the slave device WLAN are shown in the following Table 2-1:

[0113] Table 2-1

[0114]

[0115]

[0116] (2) Configuration parameter set for the working parameters of the slave device's WLAN. This parameter set includes parameters related to the configuration of the working parameters of the slave device's WLAN. For example, working mode, SSID, password, beacon type, encryption mode, authentication mode, Wi-Fi Protected Access (WPA) encryption mode, WPA authentication mode, IEEE11i encryption mode, IEEE11i authentication mode, frequency band selection, channel, channel width, transmit power level, etc.

[0117] Exemplarily, the meanings of the various parameters included in the device capability parameter set of the slave device's WLAN are shown in Table 2-2 below:

[0118] Table 2-2

[0119]

[0120]

[0121] (3) WMCI feature parameter set. This parameter set includes parameters related to WMCI features. For example, time domain scheduling, energy saving, enhanced distributed channel access (EDCA), roaming, spatial division multiplexing, frequency domain scheduling, Wi-Fi time synchronization, etc.

[0122] Exemplarily, the meanings of the various parameters included in the WMCI feature parameter set are shown in Table 2-3 below:

[0123] Table 2-3

[0124]

[0125] (4) Interference matrix parameter set. This parameter set includes parameters related to the interference sources of the interference matrix. For example, parameters of interference source 1, parameters of interference source 2, parameters of interference source 3, etc.

[0126] (5) Timer configuration parameter set. This parameter set includes parameters related to one or more timers. For example, parameters of timer 1, parameters of timer 2, parameters of timer 3, etc.

[0127] It should be noted that the above-listed 5 types of parameter sets are only examples. In actual applications, there may be other parameter sets and each parameter set may also have other parameters. This embodiment does not limit the specific types of parameter sets and the specific parameters included in the parameter sets. In addition, the order of the parameters in the same parameter set listed above is also only an example. This embodiment does not limit the order of different parameters in the same parameter set.

[0128] Step 202, the first slave device sends a response message to the master device; correspondingly, the master device receives the response message from the first slave device.

[0129] For example, if the operation type of the first message indicates that the first slave device needs to respond to the first message, after receiving the first message, the first slave device can generate a response message to the first message based on the indication in the first message and send the response message to the master device.

[0130] In this embodiment, step 202 is an optional step. For example, when the operation type of the first message is the parameter configuration type, after the first slave device configures the parameters based on the first message, it may not send a response message to the first message.

[0131] In this embodiment, the first message sent by the master device to the first slave device carries first indication information, which indicates the operation type of the first message. Therefore, it is beneficial for the first slave device to quickly decide whether to generate a response message to the first message based on the first indication information, which is beneficial to improving the communication efficiency between the master device and the slave device, and further beneficial to improving the control efficiency of the master device over the slave device.

[0132] As Figure 3 shown, it is a flowchart of another embodiment of the optical network communication method provided by this application. In this embodiment, the scenario where the first slave device sends a message to the master device is taken as an example for illustration. Of course, the entity that executes the actions of the master device in this method can also be a device, module, or chip in the master device; the entity that executes the actions of the first slave device in this method can also be a device, module, or chip in the first slave device, and this embodiment does not make specific limitations on this. Exemplarily, as Figure 3 shown, the optical network communication method includes the following steps:

[0133] Step 301, the first slave device sends a second message to the master device; correspondingly, the master device receives the second message from the first slave device.

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

[0135] Among them, the second message is a WMCI message, and the second message includes third indication information, which is used to indicate the operation type of the second message.

[0136] In a possible implementation, the operation type of the second message includes a scheduling request type, that is, the third indication information indicates that the operation type of the second message is a scheduling request type. This scheduling request type means that the first slave device requests the master device to send parameters for scheduling the first slave device to the first slave device, that is, requests the master device to send scheduling parameters for the first slave device to the first slave device. It can be understood that a message of the scheduling request type (for example, the second message) is used to request the receiving end (for example, the master device) to issue one or more scheduling parameters. Therefore, the receiving end (for example, the master device) needs to send the parameters requested by the second message to the sending end (for example, the first slave device).

[0137] In another possible implementation, the operation type of the first message includes a parameter reporting type or an alarm type (abbreviated as parameter reporting or alarm type), that is, the third indication information indicates that the operation type of the second message is a parameter reporting type or an alarm type. This parameter reporting type means that the first slave device sends parameters of the first slave device (for example, inherent parameters or configured parameters) to the master device, and this alarm type means that the first slave device reports alarm information to the master device. It can be understood that a message of the parameter reporting type (for example, the second message) is that the sending end (for example, the first slave device) actively reports one or more parameters to the receiving end (for example, the master device). A message of the alarm type (for example, the second message) is that the sending end (for example, the first slave device) actively reports alarm information to the receiving end (for example, the master device).

[0138] It should also be noted that "scheduling request type" and "parameter reporting or alarm type" are only names, and other names can also be used to describe the aforementioned two operation types. For example, the aforementioned two operation types can also be called "third operation type" and "fourth operation type", etc., and examples are not listed one by one here.

[0139] It should be noted that the parameters in the aforementioned two implementations can be determined by another indication information in the second message. Optionally, the second message further includes second indication information, and the second indication information is used to indicate the parameter set corresponding to the second message. For example, the set of capability parameters reported through the second message, or the alarm type reported through the second message. The parameter set can be understood as a set having multiple parameters. Exemplarily, if the operation type of the second message is a scheduling request type, the parameter set indicated by the second indication information means which parameter set the parameters requested by the second message belong to, that is, which parameter set the parameters that the first slave device requests the master device to issue through the second message belong to. If the operation type of the second message is a parameter reporting or alarm type, the parameter set indicated by the second indication information means which parameter set the parameters or alarm information reported by the second message belong to, that is, which parameter set the parameters or alarm information that the first slave device reports to the master device through the second message belong to.

[0140] It should also be noted that the parameters included in a parameter set are generally of the same type or have similar functions. Therefore, a parameter set can also be understood as a parameter type. The second indication information can also be understood as being used to indicate the parameter type of the second message. Exemplarily, if the operation type of the second message is a scheduling request type, the parameter type indicated by the second indication information represents the parameter type of the parameters requested by the second message, that is, what type of parameters the first slave device requests the master device to schedule through the second message. If the operation type of the second message is a parameter reporting or alarm type, the parameter type indicated by the second indication information represents the parameter type of the parameters reported by the second message or the alarm type reported by the second message, that is, what type of parameters the first slave device reports to the master device through the second message or what type of alarm information is reported.

[0141] It can be seen from this that in the case where the second message includes both the third indication information and the second indication information, if the third indication information indicates that the operation type of the second message is a scheduling request type, then this scheduling request type means that the first slave device requests the master device to send the parameters of the parameter set (or parameter type) indicated by the second indication information to the first slave device; if the third indication information indicates that the operation type of the second message is a parameter reporting or alarm type, then the parameter reporting or alarm type means that the first slave device sends the parameters of the parameter set (or parameter type) indicated by the second indication information or the alarm information to the master device.

[0142] Optionally, the third indication information includes a first value or a second value. Among them, the first value is used to indicate the scheduling request type; the second value is used to indicate the parameter reporting or alarm type.

[0143] Optionally, the third indication information is represented by at least one bit newly defined in the WMCI message. In one example, the third indication information is one bit newly defined in the WMCI message, that is, the first value and the second value are two values of the newly defined 1 bit. The two values of this bit respectively indicate the scheduling request type and the parameter reporting or alarm type. For example, when the value of this bit is 1, it indicates that the operation type of the second message is the scheduling request type; when the value of this bit is 0, it indicates that the operation type of the second message is the parameter reporting or alarm type. Another example, when the value of this bit is 0, it indicates that the operation type of the second message is the scheduling request type; when the value of this bit is 1, it indicates that the operation type of the second message is the parameter reporting or alarm type. In another example, the third indication information is two bits newly defined in the WMCI message, that is, the first value and the second value are two values of the newly defined 2 bits. The two values of these two bits respectively indicate the scheduling request type and the parameter reporting or alarm type. For example, when the value of these 2 bits is 01, it indicates that the operation type of the second message is the scheduling request type; when the value of these 2 bits is 00, it indicates that the operation type of the second message is the parameter reporting or alarm type. Another example, when the value of these 2 bits is 11, it indicates that the operation type of the second message is the scheduling request type; when the value of these 2 bits is 00, it indicates that the operation type of the second message is the parameter reporting or alarm type. This embodiment does not limit the specific implementation manners of the first value and the second value, as long as the first value is different from the second value. In addition, the third indication information can also be implemented with three bits or even four bits, and examples are not listed one by one here.

[0144] Optionally, the third indication information can be located in the message length field of the second message or in the message type identification field of the second message. The carrying position of the third indication information in the second message is the same as the carrying position of the first indication information in the first message. For details, please refer to the foregoing text. Figure 2 For the relevant introduction of the first indication information in the corresponding embodiment, it will not be elaborated here.

[0145] Exemplarily, Table 3-1 below is an example of the second message when the third indication information is implemented with one bit in the message length and processing requirement fields.

[0146] Table 3-1

[0147]

[0148] The meanings of the fields included in the second message shown in Table 3-1 are basically the same as those of the first message shown in Table 1-1 above. The difference is that the example shown in Table 1-1 is a downlink message, and bit 7 of the first byte of the message length and processing requirement fields is the first indication information; the example shown in Table 3-1 is an uplink message, and bit 7 of the first byte of the message length and processing requirement fields is the third indication information.

[0149] In the example shown in Table 3-1, C is the third indication information introduced above, which is used to indicate the operation type of this message. In the uplink direction, when C = 1, it indicates that the operation type of this message is a scheduling request type, meaning that the first slave device requests the master device to send parameters for scheduling the first slave device to the first slave device, that is, requests the master device to send scheduling parameters for the first slave device to the first slave device; when C = 0, it indicates that the operation type of this message is a parameter reporting or alarm type, meaning that the first slave device reports parameters of the first slave device or reports alarm information to the master device.

[0150] In addition, the second indication information can be carried in the message type identification field. The carrying position of the second indication information in the second message is the same as that in the first message. For specific details, please refer to the relevant introduction in the previous text Figure 2 For the relevant introduction in the corresponding embodiment, it will not be elaborated here. If the third indication information indicates that the operation type of the second message is a scheduling request type, and the second indication information is carried in the message type identification field, then this scheduling request type means that the first slave device requests the master device to send scheduling parameters for the parameter set indicated by this message type identification field (for example, scheduling configuration information, etc.); if the third indication information indicates that the operation type of the second message is a parameter reporting or alarm type, and the second indication information is carried in the message type identification field, then the parameter reporting or alarm type means that the first slave device reports parameters of the parameter set indicated by the message type identification field or the alarm type to the master device. Taking Table 3-1 as an example, in the uplink direction, when C = 1, it indicates that the operation type of this message is a scheduling request type, requesting the master device to send the scheduling configuration indicated by the message type ID field; when C = 0, it indicates that this message is a parameter reporting message or an alarm message, and the parameters or alarm type reported by this message are indicated through the message type ID field.

[0151] For the explanations of other fields in the example shown in Table 3-1, please refer to the relevant descriptions in the example shown in Table 1-1 above. It will not be elaborated here.

[0152] It should be noted that the second message also includes a parameter mask field. For example, the 5th to 6th bytes of the message content field carry a parameter mask (mask), and the parameter mask field is used to indicate the parameters in the parameter set corresponding to the second message. For example, the parameter mask field is used to indicate which parameters in the scheduling parameter set are required, or which parameters in the reporting parameter set are required, or what type of alarm type is reported. For other introductions about the parameter mask field and the explanation of the parameter set, please refer to the relevant descriptions in the example shown in Table 1-1 above. It will not be elaborated here.

[0153] Exemplarily, the following Table 3-2 is an example of a second message when the third indication information is implemented using one bit in the message type identifier.

[0154] Table 3-2

[0155]

[0156] The fields in the second message shown in Table 3-2 and the first message shown in Table 1-3 above have basically the same meaning. The difference is that the example shown in Table 1-3 is a downlink message, and the most significant bit of the message type identification field is the first indication information; the example shown in Table 3-2 is an uplink message, and the most significant bit of the message type identification field is the third indication information.

[0157] Step 302: The master device sends a response message of the second message to the first slave device; correspondingly, the first slave device receives the response message from the master device.

[0158] For example, if the operation type of the second message indicates that the master device needs to respond to the second message, after receiving the second message, the master device can generate a response message to the second message based on the indication in the second message and send the response message to the first slave device.

[0159] In this embodiment, step 302 is an optional step. For example, when the operation type of the second message sent by the first slave device to the master device is an alarm type, the master device may not return a response message.

[0160] In this embodiment, the second message sent by the first slave device to the master device carries third indication information, and the third indication information indicates the operation type of the second message. Therefore, it is beneficial for the master device to quickly decide whether to generate a response message to the second message based on the third indication information, thereby facilitating the improvement of the communication efficiency between the master device and the slave device, and further facilitating the improvement of the control efficiency of the master device over the slave device.

[0161] It should be noted that Figure 2 The corresponding embodiments and Figure 3 Corresponding embodiments may be combined.

[0162] In one implementation, the second message may be a response message to the first message. For example, during the initialization process, the master device needs to obtain basic capability information of the slave device and complete the configuration of basic working parameters of the slave device.

[0163] In one example, the master device sends a first message to the first slave device (as shown in Table 4-1 below). The first indication information included in the first message indicates that the operation type of the first message is a parameter request type (i.e., in Table 4-1, C = 1). The second indication information included in the first message indicates the device capability parameter set of the slave device WLAN (i.e., in Table 4-1, ZZZZZ = the device capability of SFU WLAN). The parameter mask field of the first message is used to indicate at least one parameter in the device capability parameter set of the slave device WLAN. For example, if the device capability parameter set of the slave device WLAN includes WiFi version number, number of Wi-Fi bands, Wi-Fi bands, number of supported SSIDs, supported transmit power levels, number of antennas, MIMO capability, etc., taking the request for 3 parameters, namely the WiFi version number, number of Wi-Fi bands, and Wi-Fi bands, in the first message as an example, then bits 8, 7, and 6 of the 5th byte in Table 4-1 are all 1, and the remaining bits are 0. After receiving the first message, the master device generates a second message (as shown in Table 4-2 below). The third indication information included in the second message indicates that the operation type of the second message is a parameter reporting type (i.e., in Table 4-2, C = 0). The second indication information included in the second message indicates the device capability parameter set of the slave device WLAN (i.e., in Table 4-2, ZZZZZ = the device capability of SFU WLAN). The parameter mask field of the second message is used to indicate which parameters in the device capability parameter set of the slave device WLAN are reported in the second message. The remaining fields (i.e., bytes 7 to N) of the message content of the second message are used to carry the specific content of the aforementioned parameters. For example, in the example shown in Table 4-2, bits 8, 7, and 6 of the 5th byte are all 1, and the remaining bits are 0, indicating that the second message reports three parameters, namely the WiFi version number, number of Wi-Fi bands, and Wi-Fi bands. In addition, the content of the WiFi version number (e.g., support for 802.11AX; support for 802.11BE;) is carried in the 7th byte of the second message, the value of the number of Wi-Fi bands (e.g., 2, i.e., support for 2 bands) is carried in the 8th byte, and the content of the Wi-Fi bands (i.e., support for 2.4G and 5G) is carried in the 9th byte.

[0164] In the examples shown in Table 4-1 and Table 4-2, the first message shown in Table 4-1 and the second message shown in Table 4-2 have the same sequence number.

[0165] Table 4-1

[0166]

[0167] Table 4-2

[0168]

[0169] It should be noted that after the master device and the slave device complete initialization using the aforementioned first message and / or second message, the master device can manage and control the relevant characteristics of the WMCI. The following combines Figure 4 to introduce this control process:

[0170] As Figure 4 shown, it is a flowchart of another embodiment of the optical network communication method provided by this application. In this embodiment, the signaling interaction between the master device and the first slave device is taken as an example for illustration. Of course, the entity executing the actions of the master device in this method can also be a device, module, or chip in the master device; the entity executing the actions of the first slave device in this method can also be a device, module, or chip in the first slave device, and this embodiment does not make specific limitations in this regard. Exemplarily, as Figure 4 shown, this optical network communication method includes the following steps:

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

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

[0173] Among them, the third message is a WMCI message, and the third message is used to manage or control the wireless local area network (WLAN) function of the first slave device. The third message includes a fourth indication information and a fifth indication information. The fourth indication information is used to indicate a first characteristic, and the fifth indication information is used to indicate whether to enable the first characteristic of the first slave device.

[0174] Among them, the first characteristic can be a characteristic of the WLAN function. Since WMCI is used to manage and control the WLAN function of the slave device, the first characteristic can also be understood as a characteristic related to WMCI. Exemplarily, the first characteristic can be any one of time domain scheduling, energy saving, coordinated EDCA, roaming, spatial division multiplexing, frequency domain scheduling, or Wi-Fi time synchronization characteristics. It should be noted that with the development of WMCI technology or the change of WLAN application scenarios, the first characteristic may also be other WLAN-related characteristics or other WMCI-related characteristics, and this embodiment does not limit.

[0175] Optionally, the third message further includes second indication information for indicating a parameter set of the third message. The parameter set can be understood as a set having multiple parameters. The fourth indication information indicates one parameter in the parameter set indicated by the second indication information, that is, the first characteristic is the characteristic indicated by one parameter in the parameter set indicated by the second indication information. Generally, the parameters included in a parameter set are of the same type or have similar functions. Therefore, the parameter set can also be understood as a parameter type. The fourth indication information indicates one parameter in the parameter type indicated by the second indication information, that is, the first characteristic is the characteristic indicated by one parameter in the parameter type indicated by the second indication information.

[0176] Optionally, the parameter set includes a WMCI characteristic parameter set. For example, the parameter set indicated by the second indication information is a WMCI characteristic parameter set, and the first characteristic is the characteristic indicated by one parameter in the WMCI characteristic parameter set, that is, the first characteristic is a characteristic related to WMCI.

[0177] Exemplarily, the parameters and the order of the parameters included in the WMCI characteristic parameter set can be as shown in Table 2-3 above.

[0178] In the example shown in Table 2-3, the time-domain scheduling parameter is used to indicate the time-domain scheduling characteristic, the energy-saving parameter is used to indicate the energy-saving characteristic, the coordinated EDCA parameter is used to indicate the coordinated EDCA characteristic, the roaming parameter is used to indicate the roaming characteristic, the spatial division multiplexing parameter is used to indicate the spatial division multiplexing characteristic, the frequency-domain scheduling parameter is used to indicate the frequency-domain scheduling characteristic, and the Wi-Fi time synchronization parameter is used to indicate the Wi-Fi time synchronization characteristic.

[0179] It should be noted that the various parameters (or characteristics) included in the foregoing WMCI characteristic parameter set are only examples. In actual applications, there may be other parameters (or characteristics). In addition, the order of the parameters (or characteristics) in the foregoing WMCI characteristic parameter set is also only an example. In actual applications, the parameters (or characteristics) in the WMCI characteristic parameter set may also be arranged in other orders. This embodiment does not limit the order of different parameters (or characteristics) in the WMCI characteristic parameter set.

[0180] Specifically, the foregoing second indication information, fourth indication information, and fifth indication information can be implemented in the following manner:

[0181] Optionally, the second indication information is carried in the message type identification field of the third message. For example, the lower n bits in the message type identification field are used to carry the second indication information, where n is an integer greater than 2. For example, n = 5, that is, the 1st to 5th bits of the 1st byte of the third message carry the second indication information. Another example, n = 6, that is, the 1st to 6th bits of the 1st byte of the third message carry the second indication information. Hereinafter, the case where the second indication information uses the 1st to 5th bits is taken as an example for introduction. For details, please refer to the example shown in Table 5-1 hereinafter.

[0182] Optionally, the third message includes a message content field. The fourth indication information is located in the first two bytes of the message content field, and the fifth indication information is located in the remaining bytes of the message content field. The first two bytes of the message content field are a parameter mask field, and the fourth indication information is one bit of the parameter mask field. For example, the parameter mask field is used to indicate which parameter's characteristic in the parameter set indicated by the second indication information the first characteristic is. For details, please refer to the example shown in Table 5-1 hereinafter.

[0183] Optionally, the fifth indication information includes a first value and a second value. The first value is used to indicate enabling the first characteristic, and the second value is used to indicate not enabling the first characteristic. In one implementation, the fifth indication information can be represented by a newly defined bit in the WMCI message, that is, the first value and the second value are two values of the newly defined 1 bit. The two values of this bit respectively indicate enabling the first characteristic and not enabling the first characteristic. For example, when the value of this bit is 1, it indicates enabling the first characteristic, and when the value of this bit is 0, it indicates not enabling the first characteristic. For details, please refer to the example shown in Table 5-2 hereinafter. In another implementation, the fifth indication information can be represented by m newly defined bits in the WMCI message, that is, the first value and the second value are two of the newly defined m bits, where m is an integer greater than 1. For example, the m bits can represent a total of 0 to 2 m values. The values 0 and 1 can be taken to respectively indicate enabling the first characteristic and not enabling the first characteristic, and the remaining values are reserved. For example, the fifth indication information can be represented by one byte (8 bits). When the value of this byte is 0, it indicates not enabling the first characteristic, and when the value is 1, it indicates enabling the first characteristic, and the remaining values (i.e., 2 to 255) are reserved. For details, please refer to the example shown in Table 5-3 hereinafter.

[0184] Exemplarily, Table 5-1 below is an example of the third message in this embodiment.

[0185] Table 5-1

[0186]

[0187] As shown in Table 5-1, the first byte is the message type identification field (which can also be called the message type ID (message type ID) field), used to indicate the type of the message and define the semantics of the message content. The second indication information is carried in the message type identification field of the third message, used to indicate the parameter set, that is, the parameter set to which the parameters of the first feature belong, that is, which parameter set's parameters determine the first feature. In the example shown in Table 5-1, the first to fifth bits are used to represent the second indication information, that is, the bits "ZZZZZ". The second byte is the sequence number (sequence number, SeqNo) field, which contains a sequence number counter, used to ensure the robustness of the WMCI message transfer channel. In the downlink direction, the sequence number field is filled with the value of the sequence number counter of the corresponding master device. The master device maintains a separate sequence number counter for each unicast and broadcast WMCI message stream to each slave device. Each sequence number counter rolls over from 255 to 1, and the value 0 is not used in the downlink. The third to fourth bytes are the message length and processing requirement field. If the third message also includes the first indication information and the processing requirement indication information introduced above, the message length and processing requirement field consists of three fields: the priority of the message, the operation type, and the length of the message content. For the explanation of this field, please refer to the relevant introduction in the examples shown in Table 1-1, Table 1-2, or Table 1-3 above, which will not be elaborated here. In addition, the fifth to N bytes are the message content field, used to carry the specific content of the message, which is related to the specific message. Among them, the fifth to sixth bytes are used to carry the parameter mask (referred to as the parameter mask field), and the parameter mask field is used to indicate the parameters in the parameter set indicated by the second indication information. Since the size of the parameter mask field is 16 bits (i.e., 2 bytes), therefore, a parameter set can contain at most 16 parameters, and each message type of each parameter set can carry at most 16 parameters. The number of parameters contained in the parameter set indicated by the second indication information is less than or equal to 16. The fourth indication information is a bit of the parameter mask field. For example, the fourth indication information is bit S1 to bit S 16A bit in it, and the value of this bit is 1. For example, if the first characteristic is the characteristic of the parameter indicated by bit S1, then the value of bit S1 is 1. In addition, the 7th to Nth bytes are used to carry the parameter content of the parameter indicated by the parameter mask, and the parameter content should be filled into the message content in the order indicated by the parameter mask. Where N is an integer greater than 7. The fifth indication information is located in the parameter content field, and the number of bytes occupied by the fifth indication information corresponds to the bit positions of the fourth indication information. For the specific correspondence relationship, please refer to the example shown in Table 5-2 later. In addition, the (N + 1)th to (N + 4)th bytes are the message integrity check field, with a size of 4 bytes, which is used to verify the identity of the sender and prevent forged WMCI message attacks, and the function of this field follows the cyclic redundancy check (CRC) function.

[0188] For ease of understanding, take the parameter set indicated by the second indication information as the WMCI characteristic parameter set, and the parameters included in this WMCI characteristic parameter set and the order of the parameters are as shown in Table 2-3 above as an example to introduce the third message.

[0189] Exemplarily, the following Table 5-2 is an example of the third message when the fifth indication information is implemented using a bit in the parameter content field.

[0190] Table 5-2

[0191]

[0192]

[0193] In the example shown in Table 5-2, the second indication information is located in bits 1 to 5 of the message type identification field, indicating the WMCI feature parameter set. In the example of the WMCI feature parameter set shown in Table 2-3, the WMCI feature parameter set contains 7 parameters, corresponding to 7 features respectively. The 7 parameters (or features) are respectively represented by the first 7 bits of the parameter mask field in the message content field, and the first 7 bits in the parameter mask field are mapped according to the parameter order shown in Table 2-3. That is to say, bit S1 of the 5th byte represents time domain scheduling, bit S2 of the 5th byte represents energy saving, bit S3 of the 5th byte represents coordinated EDCA, bit S4 of the 5th byte represents roaming, bit S5 of the 5th byte represents space division multiplexing, bit S6 of the 5th byte represents frequency domain scheduling, bit S7 of the 5th byte represents Wi-Fi time synchronization, and the remaining bits are reserved. If the parameter content of each parameter occupies one byte, the first 7 bytes in the parameter content field are mapped according to the parameter order shown in Table 2-3. That is to say, the 7th byte is the parameter content of the time domain scheduling parameter, the 8th byte is the parameter content of the energy saving parameter, the 9th byte is the parameter content of the coordinated EDCA parameter, the 10th byte is the parameter content of the roaming parameter, the 11th byte is the parameter content of the space division multiplexing parameter, the 12th byte is the parameter content of the frequency domain scheduling parameter, the 13th byte is the parameter content of the Wi-Fi time synchronization parameter, and the remaining bytes are reserved. The parameter content in this example includes the fifth indication information, which is used to indicate whether to enable the feature indicated by the parameter. If the value of the highest bit of the parameter content field is used to indicate whether to enable the corresponding feature, F i = 1 indicates enabling the feature indicated by bit Si, F i= 0 indicates that the feature indicated by bit Si is not enabled, where i = 1, 2, 3, 4, 5, 6, or 7. For example, in the 7th byte, bit F1 = 1 enables the time-domain scheduling feature, and bit F1 = 0 disables the time-domain scheduling feature; in the 8th byte, bit F2 = 1 enables the energy-saving feature, and bit F2 = 0 disables the energy-saving feature; in the 9th byte, bit F3 = 1 enables the coordinated EDCA feature, and bit F3 = 0 disables the coordinated EDCA feature; in the 10th byte, bit F4 = 1 enables the roaming feature, and bit F4 = 0 disables the roaming feature; in the 11th byte, bit F5 = 1 enables the spatial multiplexing feature, and bit F5 = 0 disables the spatial multiplexing feature; in the 12th byte, bit F6 = 1 enables the frequency-domain scheduling feature, and bit F6 = 0 disables the frequency-domain scheduling feature; in the 13th byte, bit F7 = 1 enables the Wi-Fi time synchronization feature, and bit F7 = 0 disables the Wi-Fi time synchronization feature. Exemplarily, if the first feature indicated by the fourth indication information is the energy-saving feature, and the fifth indication information indicates to enable the energy-saving feature, then bit S2 in the 5th byte in the example shown in Table 5-2 takes the value of 1, and the value of the highest bit F2 in the 8th byte is 1. If the first feature indicated by the fourth indication information is the coordinated EDCA feature, and the fifth indication information indicates not to enable the coordinated EDCA feature, then bit S3 in the 5th byte in the example shown in Table 5-2 takes the value of 1, and the value of the highest bit F3 in the 9th byte is 0.

[0194] Exemplarily, Table 5-3 below shows an example of the third message when the fifth indication information is implemented using one byte in the parameter content field.

[0195] Table 5-3

[0196]

[0197]

[0198] The example shown in Table 5-3 is only different from the example shown in Table 5-2 in the parameter content field, and the remaining fields are the same. For the explanations of the remaining fields, please refer to the corresponding description in Table 5-2 above, which will not be elaborated here. The difference between the example shown in Table 5-3 and the example shown in Table 5-2 is that in the example shown in Table 5-3, the values 0 and 1 of one byte are used to represent enabling and disabling the corresponding feature respectively, and the values 2 to 255 of this byte are reserved. For example, in the 7th byte, when byte F1 = 1, the time domain scheduling feature is enabled, and when byte F1 = 0, the time domain scheduling feature is disabled; in the 8th byte, when byte F2 = 1, the energy saving feature is enabled, and when byte F2 = 0, the energy saving feature is disabled; in the 9th byte, when byte F3 = 1, the coordinated EDCA feature is enabled, and when byte F3 = 0, the coordinated EDCA feature is disabled; in the 10th byte, when byte F4 = 1, the roaming feature is enabled, and when byte F4 = 0, the roaming feature is disabled; in the 11th byte, when byte F5 = 1, the spatial division multiplexing feature is enabled, and when byte F5 = 0, the spatial division multiplexing feature is disabled; in the 12th byte, when byte F6 = 1, the frequency domain scheduling feature is enabled, and when byte F6 = 0, the frequency domain scheduling feature is disabled; in the 13th byte, when byte F7 = 1, the Wi-Fi time synchronization feature is enabled, and when byte F7 = 0, the Wi-Fi time synchronization feature is disabled. Exemplarily, if the first feature indicated by the fourth indication information is the energy saving feature, and the fifth indication information indicates to enable the energy saving feature, then in the example shown in Table 5-2, the bit S2 of the 5th byte takes 1, and the value of the 8th byte is 1. If the first feature indicated by the fourth indication information is the coordinated EDCA feature, and the fifth indication information indicates not to enable the coordinated EDCA feature, then in the example shown in Table 5-2, the bit S3 of the 5th byte takes 1, and the value of the 9th byte is 0.

[0199] It should be noted that the third message may include multiple fourth indication information and multiple fifth indication information, and the fourth indication information and the fifth indication information correspond one by one. It can be understood that the master device can simultaneously indicate whether multiple features are enabled or not through the third message. For example, as shown in Table 5-2, both the bit S2 and the bit S3 of the parameter mask field of the third message take 1, the value of the 8th byte is 1, and the value of the 9th byte is 0, indicating that the energy saving feature is enabled and the coordinated EDCA feature is not enabled. Another example, as shown in Table 5-2, both the bit S2 and the bit S4 of the parameter mask field of the third message take 1, the value of the 8th byte is 1, and the value of the 10th byte is 1, indicating that the energy saving feature is enabled and the roaming feature is enabled. Another example, as shown in Table 5-2, both the bit S2 and the bit S3 of the parameter mask field of the third message take 1, the value of the 8th byte is 0, and the value of the 9th byte is 0, indicating that the energy saving feature is not enabled and the coordinated EDCA feature is not enabled.

[0200] Step 402, the first slave device configures the first feature based on the third message.

[0201] For example, after the first slave device receives the third message, the first slave device may enable or disable the first feature according to the instructions of the fourth indication information and the fifth indication information in the received third message. For example, before receiving the third message, the first feature of the first slave device is a disabled feature, and the third message instructs to enable the first feature, then the first slave device enables the first feature based on the instruction of the third message. Another example is that before receiving the third message, the first feature of the first slave device is an enabled feature, and the third message instructs to disable the first feature, then the first slave device disables the first feature based on the instruction of the third message. It can also be understood that the first feature is turned off based on the instruction of the third message.

[0202] After the first slave device performs an operation on the first feature (such as starting or not starting the first feature) based on the third message, the first slave device will also execute step 403.

[0203] Step 403, the first slave device sends a fourth message to the master device; correspondingly, the master device receives the fourth message from the first slave device.

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

[0205] Among them, the fourth message is a WMCI message, and the fourth message is used to manage or control the wireless local area network (WLAN) function of the first slave device. The fourth message includes fourth indication information and sixth indication information. The fourth indication information is used to indicate the first feature, and the sixth indication information is used to indicate whether to enable the first feature of the first slave device.

[0206] For the explanation of the fourth indication information and the first feature, please refer to the relevant introduction in step 401 above, which will not be elaborated here.

[0207] Optionally, the fourth message further includes second indication information, and the second indication information is located in the message type identification field of the fourth message. For the explanation of the second indication information, please refer to the relevant introduction in step 401 above, which will not be elaborated here.

[0208] Optionally, the fourth message includes a message content field. The fourth indication information is located in the first two bytes of the message content field, and the sixth indication information is located in the message content field. The sixth indication information includes a first value and a second value. The first value is used to indicate enabling the first feature, and the second value is used to indicate disabling the first feature. The sixth indication information in this step is similar to the fifth indication information introduced above. The function and the carrying position of the sixth indication information in the message can refer to the description of the fifth indication information above, which will not be elaborated here.

[0209] In a possible implementation, if the first slave device enables the first feature according to the indication of the fourth indication information and the fifth indication information in the received third message, the fourth indication information and the sixth indication information in the fourth message sent by the first slave device also indicate enabling the first feature. If the first slave device does not enable the first feature according to the indication of the fourth indication information and the fifth indication information in the received third message, the fourth indication information and the sixth indication information in the fourth message sent by the first slave device also indicate not enabling the first feature. In this case, the value of the sixth indication information is the same as the value of the fifth indication information. It can be understood that the configuration effect result of the first feature fed back by the first slave device through the fourth message is successful effect.

[0210] In another possible implementation, the first slave device may also not enable or disable the first feature according to the indication of the fourth indication information and the fifth indication information in the received third message. For example, the fourth indication information and the fifth indication information in the third message received by the first slave device indicate enabling the energy-saving feature. However, the first slave device may have service transmission and is not suitable for energy saving, so the first slave device does not enable the energy-saving feature according to the indication of the third message. In this case, the value of the sixth indication information is different from the value of the fifth indication information. It can be understood that the configuration effect result of the first feature fed back by the first slave device through the fourth message is failed effect.

[0211] Exemplarily, the third message sent by the master device to the first slave device (as shown in Table 6-1 below), the second indication information included in the third message indicates the WMCI feature parameter set. The third message includes two fourth indication information, respectively indicating the energy-saving feature (i.e., the 7th bit from low to high of the 5th byte) and the Wi-Fi time synchronization feature (i.e., the 2nd bit from low to high of the 5th byte). The third message includes two fifth indication information, respectively indicating enabling the energy-saving feature (i.e., the value of the 8th byte is 1) and enabling the Wi-Fi time synchronization feature (i.e., the value of the 13th byte is 1). The first slave device attempts to enable the energy-saving feature and the Wi-Fi time synchronization feature according to the indication of the third message. If the first slave device successfully enables the Wi-Fi time synchronization feature but fails to enable the energy-saving feature, the first slave device sends a fourth message to the master device (as shown in Table 6-2 below). The second indication information included in the fourth message indicates the WMCI feature parameter set. The fourth message includes two fourth indication information, respectively indicating the energy-saving feature (i.e., the 7th bit from low to high of the 5th byte) and the Wi-Fi time synchronization feature (i.e., the 2nd bit from low to high of the 5th byte). The fourth message includes two sixth indication information, that is, the values of the 8th byte and the 13th byte of the parameter content field. Among them, the value of the 8th byte is 1, indicating that the energy-saving feature is not successfully enabled; the value of the 13th byte is 1, indicating that the Wi-Fi time synchronization feature is successfully enabled.

[0212] Table 6-1

[0213]

[0214] Table 6-2

[0215]

[0216] In this embodiment, the first slave device is instructed to enable or disable the first characteristic of the first slave device through the fourth indication information and the fifth indication information in the third message, which is beneficial to the master device flexibly configuring the first characteristic of the first slave device, thereby improving the efficiency of the master device in controlling the first slave device.

[0217] The parameters in Table 2-1 above (such as Wi-Fi version number, number of Wi-Fi frequency bands, Wi-Fi frequency bands, number of supported SSIDs, supported transmit power levels, number of antennas, MIMO capabilities), the parameters in Table 2-2 (such as operating mode, SSID, Password, Beacon type, encryption mode, authentication mode, WPA encryption mode, WPA authentication mode, IEEE11i encryption mode, IEEE11i authentication mode, frequency band selection, channel, channel width, transmit power level), and the parameters in Table 2-3 (such as time domain scheduling, energy saving, coordinated EDCA, roaming, spatial multiplexing, frequency domain scheduling, Wi-Fi time synchronization) can be represented in other forms in addition to being represented in the message in the form of a mask shown by 5-N bytes in Table 1-1, Table 1-2, or Table 1-3. For example, one or more of the above parameters can be represented in the message in the form of type-length-value (TLV). Each TLV can carry one parameter or multiple parameters. If a TLV carries multiple parameters, these parameters can be used as the "value" of the TLV or multiple parameters can be carried in the form of sub-TLVs. For example, the "value" of a TLV can include two parameters, namely the Wi-Fi frequency band and the number of Wi-Fi frequency bands, or the TLV includes at least 2 sub-TLVs, the "value" of one sub-TLV includes the Wi-Fi frequency band parameter, and the "value" of another sub-TLV includes the number of Wi-Fi frequency bands parameter.

[0218] In addition, each parameter can be carried by one message or multiple messages. If a certain parameter is carried by multiple different messages, the parameter can be an optional parameter in one or some of the messages and a mandatory parameter in another or some other messages.

[0219] If the above parameters are represented in the form of TLV, the format of the WMCI message can be as shown in Table 7 below:

[0220] Table 7

[0221]

[0222] It should also be noted that the master device and the slave device interact with each other through the WMCI management channel for the messages introduced above (for example, the first message, the second message, the response message of the first message, the response message of the second message, the third message, the fourth message, etc.). Taking the first message as an example for illustration, the remaining messages are similar to the first message. The master device sends the first message to the first slave device through the WMCI management channel; correspondingly, the first slave device receives the first message from the master device through the WMCI management channel. Among them, 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 ID). Different logical port identifiers may correspond to the same physical transceiver port or may respectively correspond to different physical transceiver ports, which is not limited here. For example, the first management channel corresponds to PortID1 of the master device and port ID1 of the first slave device, while other management channels correspond to Port ID2 of the master device and port ID2 of the first slave device. Among them, Port ID1 and Port ID2 may correspond to the same physical transceiver port or may correspond to different physical transceiver ports.

[0223] In addition, as Figure 5AAs shown, if the rate level of the master device 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 frame header of the FEM frame is assigned by the master device. This FEM port ID can not only indicate that the first message is a WMCI message, but also be used to indicate the transceiver object of this WMCI message (i.e., the first message), that is, to indicate that this WMCI message (i.e., the first message) corresponds to the first slave device rather than other slave devices. Therefore, the WMCI message can be distinguished from other management and control messages in the FTTR system (e.g., FMCI messages or OMCI messages) through the FEM port ID. It should be noted that when the rate level of the master device is 2.5G, the downstream line rate of the master device is 2.48832 Gbit / s; the upstream line rate of the master device can be 1.24416 Gbit / s, or 2.48832 Gbit / s, or it can also support both 1.24416 Gbit / s and 2.48832 Gbit / s simultaneously. The downstream line speed of the slave device is 2.48832 Gbit / s, and the upstream line speed is 1.24416 Gbit / s or 2.48832 Gbit / s. It should be noted that the payload length L of the FEM frame is equal to the length L of the WMCI message, and L is an integer greater than 0.

[0224] In addition, as Figure 5BAs shown in the figure, if the rate level of the master device is 10G, the first message is encapsulated in the payload field of a frame in the 10G-FTTR Encapsulation Method (XFEM) format. The XFEM port ID in the frame header of the XFEM frame is assigned by the master device. This XFEM port ID can not only indicate that the first message is a WMCI message, but also be used to indicate the transceiver object of this WMCI message (i.e., the first message), that is, it indicates that this WMCI message (i.e., the first message) corresponds to the first slave device rather than other slave devices. Therefore, the WMCI message can be distinguished from other control messages in the FTTR system through the XFEM port ID. It should be noted that when the rate level of the master device is 10G, the downstream line rate of the master device is 9.95328 Gbit / s; the upstream line rate of the master device can be 9.95328 Gbit / s, or 2.48832 Gbit / s, or it can also support both 9.95328 Gbit / s and 2.48832 Gbit / s simultaneously. The downstream line speed of the slave device is 9.95328 Gbit / s, and the upstream line speed is 9.95328 Gbit / s or 2.48832 Gbit / s. It should be noted that the payload length P of the XFEM frame is an integer multiple of 4 bytes, but the length of the WMCI message may not be an integer multiple of 4 bytes. Therefore, when carrying the WMCI message, the XFEM payload may need to add a padding field of 0 to 3 bytes.

[0225] In addition, as Figure 5C shown, the FEM frame is encapsulated in the payload field of a data link layer (DLL) frame. As Figure 5D shown, the XFEM frame is encapsulated in the payload field of the DLL frame. The DLL frame consists of a DLL frame header and a DLL frame payload part. The DLL payload is formed on the sending side and processed by the service adaptation sublayer on the receiving side. The DLL frame header consists of three fixed-size partitions (i.e., PLOAMd, BIP, Plend) and a variable-size partition: the bandwidth mapping partition (BWmap). One bandwidth mapping (BWmap) is used to indicate the upstream transmission position in the corresponding upstream physical frame (PHY frame) of different slave devices.

[0226] It should be noted that in the Figure 5C shown example, only the case where the payload of the DLL frame contains 3 FEM frames is taken as an example. In actual applications, the payload of the DLL frame can contain other numbers of FEM frames, which is not limited here. In the Figure 5D shown example, only the case where the payload of the DLL frame contains 3 XFEM frames is taken as an example. In actual applications, the payload of the DLL frame can contain other numbers of XFEM frames, which is not limited here.

[0227] In addition, an embodiment of the present application further provides a communication device 60, as Figure 6 shown, Figure 6 is a schematic structural diagram of a communication device 60 provided by an embodiment of the present application. Figure 2 , Figure 3 or Figure 4 The specific implementation of the master device and the slave device (e.g., the first slave device) in the flowchart shown can refer to Figure 6 the internal structure of the communication device 60 shown. When the communication device 60 is used to implement Figure 2 , Figure 3 or Figure 4 the function of the master device in the method shown, the communication device 60 can be a master gateway or an MFU. When the communication device 60 is used to implement Figure 2 , Figure 3 or Figure 4 the function of the slave device in the method shown, the communication device 60 can be a slave gateway or an SFU.

[0228] As Figure 6 shown, the communication device 60 may include a processor 601 and a transceiver 602, and the processor 601 is coupled to the transceiver 602. Among them, the aforementioned processor 601 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The above 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 601 may refer to a single processor or may include multiple processors, and specific details are not limited herein.

[0229] Among them, the aforementioned transceiver 602 may also be referred to as a transceiver unit, a transceiver, a transceiver device, etc. Optionally, the device for implementing the receiving function in the transceiver unit may be regarded as a receiving unit, and the device for implementing the sending function in the transceiver unit may be regarded as a sending unit, that is, the transceiver unit includes a receiving unit and a sending unit. The receiving unit may also be referred to as a receiver, an input port, a receiving circuit, etc., and the sending unit may be referred to as a transmitter, a transmitter, or a transmitting circuit, etc.

[0230] Optionally, the communication device 60 further includes a memory 603. The processor 601 is coupled to the memory 603. The memory 603 is mainly used to store software programs and data. The memory 603 can exist independently and be connected to the processor 601. Optionally, the memory 603 can be integrated with the processor 601, for example, integrated within one or more chips. The memory 603 can store program codes for implementing the technical solutions of the embodiments of the present application and be controlled by the processor 601 for execution. Various computer program codes executed can also be regarded as driver programs of the processor 601. The memory 603 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 603 can also include a combination of the above types of memories. The memory 603 can refer to a single memory or include multiple memories. Exemplarily, the memory 603 is used to store various data.

[0231] In one implementation, the communication device 60 is used to implement Figure 2 the functions of the master device in the corresponding method embodiment. Specifically, the processor 601 is used to generate a first message; the transceiver 602 is used to send the first message to the first slave device. The first message is a wireless local area network management and control interface WMCI message, and 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, and the first indication information is used to indicate the operation type of the first message.

[0232] In a possible implementation manner, the operation type of the first message includes any one of the following: a parameter request type, which is used to indicate that the master device requests the first slave device to send the parameters of the first slave device to the master device; or, a parameter configuration type, which is used to indicate that the master device sends the configuration parameters of the first slave device to the first slave device.

[0233] In a possible implementation manner, the first indication information includes a first value or a second value. The first value is used to indicate that the operation type is a parameter request type, and the second value is used to indicate that the operation type is a parameter configuration type.

[0234] In another implementation, the communication device 60 is used to implement Figure 2The functions of the slave device (e.g., the first slave device) in the corresponding method embodiments. Specifically, the transceiver 602 is configured to receive a first message from the master device. The first message is a Wireless Local Area Network Management and Control Interface (WMCI) message, which 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 operation type of the first message.

[0235] For the remaining implementation manners, please refer to the relevant introduction on the master device side in the foregoing text, which will not be elaborated herein.

[0236] In one implementation, the communication device 60 is configured to implement Figure 3 The functions of the master device in the corresponding method embodiments. Specifically, the processor 601 is configured to generate a second message; the transceiver 602 is configured to send the second message to the master device. The second message is a Wireless Local Area Network Management and Control Interface (WMCI) message, which is used to request to manage or control the Wireless Local Area Network (WLAN) function of the first slave device. The second message includes third indication information, which is used to indicate the operation type of the second message.

[0237] In a possible implementation manner, the operation type of the second message includes any one of the following:

[0238] A scheduling request type, which is used to request the master device to send scheduling configuration information to the first slave device; or, a parameter reporting type or an alarm type, which is used for the first slave device to send parameters of the first slave device or alarm information of the first slave device to the master device.

[0239] In a possible implementation manner, the third indication information includes a first value or a second value. The first value is used to indicate that the operation type is a scheduling request type, and the second value is used to indicate that the operation type is a parameter reporting type or an alarm type.

[0240] In another implementation, the communication device 60 is configured to implement Figure 3 The functions of the slave device (e.g., the first slave device) in the corresponding method embodiments. Specifically, the transceiver 602 is configured to receive a second message from the first slave device. The second message is a Wireless Local Area Network Management and Control Interface (WMCI) message, which is used to request to manage or control the Wireless Local Area Network (WLAN) function of the first slave device. The second message includes third indication information, which is used to indicate the operation type of the second message.

[0241] For the remaining implementation manners, please refer to the relevant introduction on the master device side in the foregoing text, which will not be elaborated herein.

[0242] In one implementation, the communication device 60 is configured to implement Figure 4Corresponding to the functions of the master device in the method embodiments. Specifically, the processor 601 is configured to generate a third message; the transceiver 602 is configured to send the third message to the first slave device. The third message is a Wireless Local Area Network Management and Control Interface (WMCI) message, and the third message is used to manage or control the Wireless Local Area Network (WLAN) function of the first slave device. The third message includes a fourth indication information and a fifth indication information. The fourth indication information is used to indicate a first characteristic, and the fifth indication information is used to indicate whether to enable the first characteristic of the first slave device.

[0243] In a possible implementation, the transceiver 602 is further configured to receive a fourth message from the first slave device. The fourth message is a Wireless Local Area Network Management and Control Interface (WMCI) message, and the fourth message is used to manage or control the Wireless Local Area Network (WLAN) function of the first slave device. The fourth message includes a fourth indication information and a sixth indication information. The fourth indication information is used to indicate a first characteristic, and the sixth indication information is used to indicate whether to enable the first characteristic of the first slave device.

[0244] In another implementation, the communication device 60 is configured to implement Figure 4 Corresponding to the functions of the slave device (e.g., the first slave device) in the method embodiments. Specifically, the transceiver 602 is configured to receive a third message from the master device. The third message is a Wireless Local Area Network Management and Control Interface (WMCI) message, and the third message is used to manage or control the Wireless Local Area Network (WLAN) function of the first slave device. The third message includes a fourth indication information and a fifth indication information. The fourth indication information is used to indicate a first characteristic, and the fifth indication information is used to indicate whether to enable the first characteristic of the first slave device.

[0245] In a possible implementation, the processor 601 is configured to generate a fourth message, and the transceiver 602 is further configured to send the fourth message to the master device. The fourth message is a Wireless Local Area Network Management and Control Interface (WMCI) message, and the fourth message is used to manage or control the Wireless Local Area Network (WLAN) function of the first slave device. The fourth message includes a fourth indication information and a sixth indication information. The fourth indication information is used to indicate a first characteristic, and the sixth indication information is used to indicate whether to enable the first characteristic of the first slave device.

[0246] For details, please refer to Figure 2 、 Figure 3 or Figure 4 the relevant descriptions in the corresponding embodiments, which will not be elaborated here.

[0247] Such as Figure 7As shown in the figure, the present application also provides a communication device 70. The communication device 70 may be a slave device (e.g., the first slave device) or a master device, or may be a component (e.g., an integrated circuit, a chip, etc.) of a slave device (e.g., the first slave device) or a master device. The communication device 70 may also be other communication modules for implementing the methods in the method embodiments of the present application.

[0248] The communication device 70 may include a processing module 701 (or referred to as a processing unit). Optionally, it may further include an interface module 702 (or referred to as a transceiver unit or a transceiver module) and a storage module 703 (or referred to as a storage unit). The interface module 702 is used to communicate with other devices. The interface module 702 may be, for example, a transceiver module or an input / output module.

[0249] In a possible design, as Figure 7 one or more of the modules may be implemented by one or more processors, or by one or more processors and a memory; or by one or more processors and a transceiver; or by one or more processors, a memory, and a transceiver. The present application embodiments do not make limitations in this regard. The processor, the memory, and the transceiver may be provided separately or integrated together.

[0250] The communication device 70 is capable of implementing the functions of the slave device (e.g., the first slave device) described in the embodiments of the present application. For example, the communication device 70 includes the modules or units or means corresponding to the steps involved in the slave device (e.g., the first slave device) described in the embodiments of the present application. The functions or units or means may be implemented by software, or by hardware, or by hardware executing corresponding software, or by a combination of software and hardware. For details, further reference may be made to the corresponding descriptions in the foregoing corresponding method embodiments. Specifically, please refer to the Figure 6 communication device 60 in the corresponding embodiment above.

[0251] Alternatively, the communication device 70 is capable of implementing the functions of the master device described in the embodiments of the present application. For example, the communication device 70 includes the modules or units or means corresponding to the steps involved in the master device described in the embodiments of the present application. The functions or units or means may be implemented by software, or by hardware, or by hardware executing corresponding software, or by a combination of software and hardware. For details, further reference may be made to the corresponding descriptions in the foregoing corresponding method embodiments. Specifically, please refer to the Figure 6 communication device 60 in the corresponding embodiment above.

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

[0253] In addition, the present application further provides a computer-readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the methods related to the slave device (e.g., the first slave device) in the foregoing Figure 2 , Figure 3 or Figure 4 .

[0254] In addition, the present application further provides a computer-readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the methods related to the master device in the foregoing Figure 2 , Figure 3 or Figure 4 .

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

[0256] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements on some of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the various embodiments of the present application.

Claims

1. An optical network communication method, the optical network comprising a master device and at least one slave device, the at least one slave device including a first slave device, characterized in that, Comprising: The master device sends a first message to the first slave device, the first message being a Wireless Local Area Network Management and Control Interface (WMCI) message, the first message including first indication information for indicating the operation type of the first message.

2. A 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, Comprising: The first slave device receives the first message from the master device, the first message being a Wireless Local Area Network Management and Control Interface (WMCI) message, the first message including first indication information for indicating the operation type of the first message.

3. The method according to claim 1 or 2, characterized in that, The operation type of the first message includes any one of the following: A parameter request type, used to indicate that the master device requests the first slave device to send the parameters of the first slave device to the master device; or, A parameter configuration type, used to indicate that the master device sends the configuration parameters of the first slave device to the first slave device.

4. The method according to any one of claims 1 to 3, characterized in that, The first indication information includes a first value or a second value, the first value being used to indicate that the operation type is the parameter request type, and the second value being used to indicate that the operation type is the parameter configuration type.

5. The method according to any one of claims 1 to 4, characterized in that, The first indication information is located in the 3rd to 4th bytes of the first message.

6. The method according to claim 5, characterized in that The first indication information is located in the second highest bit position of the 3rd to 4th bytes.

7. The method according to any one of claims 1 to 6, characterized in that, The first message further includes a message type identifier, which is located in the first byte of the first message.

8. The method according to any one of claims 1 to 7, characterized in that The message content field of the first message further includes a parameter mask field, which is used to indicate the parameters in the parameter set corresponding to the first message.

9. The method according to claim 8, wherein, The parameter mask field is the first two bytes of the message content field, and the remaining bytes of the message content field are used to carry the content of the parameter.

10. The method according to claim 8 or 9, characterized in that, The parameter set includes any one of the following: The device capability parameter set of the slave device's WLAN; or, The working parameter configuration parameter set of the slave device's WLAN.

11. The method according to any one of claims 1 to 10, characterized in that, The first message is encapsulated in a FEM frame, and the FEM port identifier of the FEM frame is used to indicate that the first message corresponds to the first slave device.

12. The method according to any one of claims 1-11, characterized in that, The highest bit in the 3rd to 4th bytes of the first message is used to indicate the priority of the first message, where a value of 1 indicates high priority and a value of 0 indicates low priority.

13. The method according to any one of claims 1-12, characterized in that, The first message further includes an integrity check field, which is used to verify the identity of the sender and prevent spoofing attacks on WMCI messages.

14. The method according to any one of claims 1 to 13, characterized in that, The master device is an MFU, and the slave device is an SFU.

15. The method according to any one of claims 1-14, characterized in that, The optical network is a fiber optic network, and the master device is connected to the at least one slave device through optical fibers.

16. The method according to any one of claims 1-15, characterized in that, The first message is used to manage or control the Wireless Local Area Network (WLAN) function of the first slave device.

17. A communication device, characterized in that, Comprising: A processor and a transceiver, the processor being connected to the transceiver, and the processor being used to implement the method according to any one of claims 1-16.

18. A communication device, characterized in that, For implementing the method according to any one of claims 1-16.

19. A chip, characterized in that, For implementing the method according to any one of claims 1-16.

Images