WO2025056060A1 - Access method, optical fiber network system, and related device - Google Patents

Abstract

The present application provides an access method, an optical fiber network system, and a related device. After receiving first allocation information carrying a first allocation identifier and first time information, a first sub-device sends a serial number of the first sub-device in a first allocation time slot in response to the first allocation information only after determining that the first sub-device supports a first uplink rate. That is to say, the first allocation information received by the first sub-device is used for instructing a non-activated sub-device supporting the first uplink rate to report its serial number in the first allocation time slot, and does not trigger sub-devices supporting other uplink rates (uplink rates other than the first uplink rate) to report their serial numbers in the first allocation time slot, to prevent the first sub-device and the sub-devices supporting other uplink rates from sharing the allocation time slot to report their serial numbers, i.e., to prevent a main device from receiving optical signals of two uplink rates in a short time, thereby reducing the implementation complexity of uplink burst reception.

Description

Access method, optical fiber network system and related equipment

This application claims the priority of the Chinese patent application filed with the State Intellectual Property Office on September 15, 2023, with application number 202311199896.6 and invention name “An access method, optical fiber network system and related equipment”, all contents of which are incorporated by reference in this application.

Technical Field

The embodiments of the present application relate to the field of optical communications, and in particular to an access method, an optical fiber network system, and related equipment.

Background Art

Fiber to the room (FTTR) refers to the technology of using optical fiber instead of network cable to provide optical fiber media access to the room in the downstream of the optical network terminal (ONT). The optical fiber network system in the FTTR scenario includes a main device and one or more sub-devices. The main device can trigger the activation process of the sub-device after the sub-device goes online.

In the traditional activation process, the master device broadcasts a sequence number request allocation structure, so that the sub-device that receives the allocation structure reports the sequence number of the sub-device by sending an uplink optical signal, thereby triggering the subsequent activation process. However, there may be sub-devices that support different uplink rates in the optical fiber network system. The sub-devices that support different uplink rates use their respective supported uplink rates to emit light in the allocated time slot indicated by the allocation structure, resulting in the uplink optical signal received by the master device in the allocated time slot having different uplink rates, that is, the master device needs to receive burst uplink optical signals of different uplink rates in a shorter time, which increases the implementation complexity of uplink burst reception.

Summary of the invention

The present application provides an access method, an optical fiber network system and related equipment, which are used to reduce the implementation complexity of uplink burst reception.

In a first aspect, the present application provides an access method, which is applied to a fiber optic network system, wherein the fiber optic network system includes a main device and multiple sub-devices, wherein the multiple sub-devices include an unactivated first sub-device. The access method provided in this aspect can be executed by the first sub-device in the fiber optic network system, or it can be executed by some functional modules or chips in the first sub-device. Taking the execution of the first sub-device as an example, the first sub-device receives first allocation information from the main device, the first allocation information includes a first allocation identifier and first time information, the first time information is used to indicate a first allocation time slot, and the first allocation identifier is used to indicate that an unactivated sub-device supporting a first uplink rate responds to the first allocation information; if the first sub-device supports the first uplink rate, the first sub-device sends a first response information in the first allocation time slot, and the first response information includes the serial number of the first sub-device.

Optionally, if the first sub-device does not support the first uplink rate, the first sub-device does not respond to the first allocation information.

In the present application, after the first sub-device receives the first allocation information carrying the first allocation identifier and the first time information, the first sub-device will respond to the first allocation information and send the serial number of the first sub-device in the first allocation time slot only when the first sub-device determines that it supports the first uplink rate. That is to say, the first allocation information received by the first sub-device is used to instruct the sub-device supporting the first uplink rate to report the serial number in the first allocation time slot, and will not trigger the sub-devices of other uplink rates (uplink rates other than the first uplink rate) to report the serial number in the first allocation time slot, which is conducive to avoiding the first sub-device and the sub-devices supporting other uplink rates from sharing the allocation time slot to report the serial number, that is, it is conducive to avoiding the main device from receiving optical signals of two uplink rates in a short time, and further conducive to reducing the implementation complexity of uplink burst reception.

In a possible implementation manner, the first sub-device supports a second uplink rate, and the second uplink rate is different from the first uplink rate. In this case, the access method further includes:

The first sub-device receives second allocation information from the main device, the second allocation information includes a second allocation identifier and second time information, the second time information is used to indicate a second allocated time slot, the second allocation identifier is used to indicate an unactivated sub-device supporting a second uplink rate to respond to the second allocation information, the second allocation identifier is different from the first allocation identifier, and the second time information is different from the first time information; the first sub-device sends a first response information in the second allocated time slot, and the first response information includes the serial number of the first sub-device.

In a possible implementation, the multiple sub-devices further include an unactivated second sub-device, the second sub-device supports a first uplink rate, the first allocation information is used by the second sub-device to send second response information in the first allocated time slot, and the second response information includes a serial number of the second sub-device.

In this implementation, the master device can distinguish the allocation information corresponding to the sub-devices supporting different uplink rates through different allocation identifiers, and further distinguish the allocation time slots for reporting the sequence numbers corresponding to the different allocation information. Different allocated time slots are used respectively, compared with the traditional technology of using different time slots in the same allocated time slot, which lengthens the time interval between the main network device receiving the uplink optical signals of different uplink rates, which is beneficial to reducing the complexity of the receiver for uplink burst reception.

In a possible implementation manner, the first allocation identifier is a broadcast allocation identifier, and the first allocation information is a sequence number request allocation structure.

In a possible implementation manner, the first allocation information is carried in a bandwidth mapping field in a downlink physical control block.

In a possible implementation manner, the first allocation identifier is 254, and the first uplink rate is 1.25G; or, the first allocation identifier is 255 or 253, and the first uplink rate is 2.5G.

In a possible implementation manner, the first allocation identifier is 254, the second allocation identifier does not include 254, the first uplink rate is 1.25G, and the second uplink rate is 2.5G.

In a possible implementation manner, the second allocation identifier is 255.

In this implementation, for the sub-device supporting 2.48832Gbit/s, Alloc-ID=254 is redefined as a reserved allocation identifier, that is, Alloc-ID=254 is not carried in the allocation structure, and Alloc-ID=255 is redefined as a broadcast allocation identifier. The sub-device supporting the uplink rate of 1.24416Gbit/s uses Alloc-ID=254 in the activation process. Therefore, in the activation process, the 2.5G sub-device uses the allocation structure and allocation time slot corresponding to Alloc-ID=255, and the 1.25G sub-device uses the allocation structure and allocation time slot corresponding to Alloc-ID=254. Therefore, the sub-devices supporting different uplink rates use different allocation time slots when reporting sequence numbers, which can realize multi-rate separate windowing, which is conducive to reducing the implementation complexity of uplink burst reception.

In a possible implementation manner, the second allocation identifier is 253.

In this implementation, for the sub-device supporting 2.48832Gbit/s, Alloc-ID=254 is redefined as a reserved allocation identifier, that is, Alloc-ID=254 is not carried in the allocation structure, and Alloc-ID=253 is redefined as a broadcast allocation identifier. The sub-device supporting the uplink rate of 1.24416Gbit/s uses Alloc-ID=254 in the activation process. Therefore, in the activation process, the 2.5G sub-device uses the allocation structure and allocation time slot corresponding to Alloc-ID=253, and the 1.25G sub-device uses the allocation structure and allocation time slot corresponding to Alloc-ID=254. Therefore, the sub-devices supporting different uplink rates use different allocation time slots when reporting sequence numbers, which can realize multi-rate separate windowing, which is conducive to reducing the implementation complexity of uplink burst reception.

In a second aspect, the present application provides an access method, which is applied to a fiber optic network system, wherein the fiber optic network system includes a main device and multiple sub-devices, wherein the multiple sub-devices include an unactivated first sub-device. The access method provided in this aspect can be executed by the main device in the fiber optic network system, or it can be executed by some functional modules or chips in the main device. Taking the execution of the main device as an example, the main device sends a first allocation information, the first allocation information includes a first allocation identifier and a first time information, the first time information is used to indicate a first allocation time slot, and the first allocation identifier is used to indicate that an unactivated sub-device supporting a first uplink rate responds to the first allocation information; wherein, if the first sub-device supports the first uplink rate, the first allocation information is used for the first sub-device to send a first response information in the first allocation time slot, and the first response information includes the serial number of the first sub-device. Optionally, if the first sub-device does not support the first uplink rate, the first allocation information is used for the first sub-device not to respond to the first allocation information.

In the present application, the master device can send the first allocation information carrying the first allocation identifier and the first time information to indicate that only the unactivated sub-device supporting the first uplink rate triggers the transmission of the sub-device's sequence number in the first allocation time slot indicated by the first time information, and does not trigger the sub-device that does not support the first uplink rate to report the sub-device's sequence number in the first allocation time slot. Therefore, it is helpful to avoid sub-devices supporting different uplink rates from sharing the allocation time slot to report the sequence number, that is, it is helpful to avoid the master device receiving optical signals of two uplink rates in a short time, and further helps to reduce the implementation complexity of uplink burst reception.

In a possible implementation, the first sub-device supports a second uplink rate, and the second uplink rate is different from the first uplink rate. The access method also includes: the master device sends a second allocation information, the second allocation information includes a second allocation identifier and second time information, the second time information is used to indicate a second allocated time slot, the second allocation identifier is used to indicate that an unactivated sub-device supporting the second uplink rate responds to the second allocation information, the second allocation identifier is different from the first allocation identifier, the second time information is different from the first time information, the second allocation information is used for the first sub-device to send a first response information in the second allocated time slot, and the first response information includes the serial number of the first sub-device.

In a possible implementation, the multiple sub-devices further include an unactivated second sub-device, the second sub-device supports a first uplink rate, the first allocation information is used by the second sub-device to send second response information in the first allocated time slot, and the second response information includes a serial number of the second sub-device.

In a possible implementation manner, the first allocation identifier is a broadcast allocation identifier, and the first allocation information is a sequence number request allocation structure.

In a possible implementation manner, the first allocation information is carried in a bandwidth mapping field in a downlink physical control block.

In a possible implementation manner, the first allocation identifier is 254, and the first uplink rate is 1.25G; or, the first allocation identifier is 255 or 253, and the first uplink rate is 2.5G.

In a possible implementation manner, the first allocation identifier is 254, the second allocation identifier does not include 254, the first uplink rate is 1.25G, and the second uplink rate is 2.5G.

In a possible implementation manner, the second allocation identifier is 255 or 253.

It should be noted that there are many other specific implementations of the embodiments of the present application. Please refer to the specific implementations of the first aspect and their beneficial effects for details, which will not be repeated here.

In a third aspect, the present application provides an access method, which is applied to an optical fiber network system, wherein the optical fiber network system includes a main device and multiple sub-devices, and the access method includes:

The first sub-device receives first capability acquisition setting information from the main device, where the first capability acquisition setting information includes an identifier of the first sub-device and a query operation code;

In response to the first capability acquisition setting information, the first sub-device acquires its own capability information;

The first sub-device sends a capability reporting message to the main device, where the capability reporting message carries capability information of the first sub-device.

Through the above access method, the main device can obtain the capability (characteristic or function) information of the first sub-device after the first sub-device is activated, so as to manage the resources and communication process of the first sub-device.

In a possible implementation manner, the first sub-device further receives second capability acquisition setting information from the main device, where the second capability acquisition setting information includes an identifier of the first sub-device, a setting operation code, and a capability to be set;

The first sub-device sets (or operates) itself according to the capability to be set;

The first sub-device sends a capability setting message to the main device, where the capability setting message carries a result of the first sub-device setting itself.

By obtaining the setting message through the above-mentioned second capability, the main device can set the capability of the first sub-device, for example, setting to change the forward error correction coding FEC codeword (FEC code) of the uplink data stream of the first sub-device to improve communication efficiency or improve communication security.

In a possible implementation manner, the capability to be set in the second capability acquisition setting information includes setting an uplink FEC code and a timestamp of the first sub-device, and the method further includes:

The first sub-device applies the FEC code to the uplink data stream according to the timestamp, that is, when the moment corresponding to the timestamp arrives, the first sub-device uses the new FEC codeword to encode the uplink data stream, thereby updating the codeword for encoding the uplink data stream of the first sub-device.

In a possible implementation manner, the second capability acquisition setting information further includes an FEC code identifier, which is used to identify an FEC codeword.

In a possible implementation, the uplink FEC code of the first sub-device includes one of a default FEC code, a high margin code, and a high throughput code.

In a possible implementation, when the uplink FEC code of the first sub-device is a high-margin code, the second capability acquisition setting information further includes the number of columns in which the LDPC code is shortened. The uplink FEC code of the first sub-device and the number of columns in which the LDPC code is shortened are carried in different fields.

In a possible implementation, the timestamp is a planned superframe counter (SFC). After the planned superframe counter expires, the first sub-device performs FEC encoding on the uplink data stream according to the FEC codeword carried in the second capability acquisition setting message.

In a possible implementation manner, the capability setting message carries an operation code, where the operation code is used to identify whether the first sub-device arranges capability setting.

In a possible implementation manner, the capability setting message carries an operation code, where the operation code is used to identify whether the first sub-device completes the capability setting.

In a possible implementation manner, the capability information of the first sub-device includes one or more FEC codewords supported by the first sub-device.

In a possible implementation, the capability setting message also carries a response code, and the response code is used to identify the reason why the first sub-device does not arrange the capability setting. For example, the reason includes at least one of switching the superframe counter value too early, not supporting the capability to be set, or the first sub-device is busy.

In a possible implementation manner, the response code is used to identify the reason why the first sub-device did not complete the capability setting. For example, the reasons include insufficient resources of the first sub-device, other errors occurring, or the first sub-device being unable to obtain at least one of the downlink synchronization DSYNC after setting the capability.

In a fourth aspect, the present application provides an access method, which is applied to an optical fiber network system, wherein the optical fiber network system includes a main device and multiple sub-devices, and the access method includes:

The master device sends first capability acquisition setting information to the first sub-device, where the first capability acquisition setting information includes an identifier of the first sub-device and a query operation code;

The main device receives a capability reporting message sent by the first sub-device, where the capability reporting message carries capability information of the first sub-device.

In a possible implementation manner, the main device further sends second capability acquisition setting information to the first sub-device, where the second capability acquisition setting information includes an identifier of the first sub-device, a setting operation code, and a capability (characteristic or function) to be set;

The main device receives a capability setting message sent by the first sub-device, where the capability setting message carries a result of the first sub-device setting (or operating) itself.

In a possible implementation manner, after receiving the capability reporting message sent by the first sub-device, the main device saves the capability information of the first sub-device carried therein.

In a possible implementation manner, the first capability acquisition setting information or the second capability acquisition setting information carries the message integrity check value, and the message integrity check value is calculated based on an integrity key (IK) between the main device and the first sub-device.

In a possible implementation manner, the second capability acquisition setting information further includes an FEC code identifier, which is used to identify an FEC codeword.

In a possible implementation manner, the capability information of the first sub-device includes one or more FEC codewords supported by the first sub-device.

In a possible implementation, the first capability acquisition setting information and the second capability acquisition setting information are downlink physical layer operations administration and maintenance (PLOAM) messages, and the capability reporting message and the capability setting message sent by the first sub-device are uplink PLOAM messages.

In the access method provided in this embodiment, the capability reporting message and the capability setting message can be unified into an ONU capability (ONU_Capabilities) message, and the capability reporting message and the capability setting message can be distinguished by the non-passing operation code carried in the message. The ONU_Capabilities message can respond to the Get_Set_Capability PLOAM message carrying the query operation code to report the ONU capability. The ONU_Capabilities message can also respond to the Get_Set_Capability PLOAM message carrying the setting operation code, indicating the desire or inability to perform the capability setting, as well as the response code. In addition, the ONU_Capabilities message can also provide an indication of the success or failure of the capability setting execution and a response code.

In a fifth aspect, the present application provides a communication device, which is applied to a fiber optic network system, wherein the fiber optic network system includes a main device and multiple sub-devices, wherein the multiple sub-devices include an unactivated first sub-device. The communication device may be the first sub-device in the fiber optic network system, or may be a partial functional module or chip in the first sub-device. The communication device includes a transceiver and a processor.

The transceiver is used to receive first allocation information from the master device, the first allocation information includes a first allocation identifier and first time information, the first time information is used to indicate a first allocated time slot, and the first allocation identifier is used to indicate that an unactivated sub-device supporting a first uplink rate responds to the first allocation information;

The processor is configured to control the transceiver to send first response information in a first allocated time slot when determining that the first uplink rate is supported, wherein the first response information includes a serial number of the first sub-device.

In a possible implementation, the processor is configured to, when determining that the first uplink rate is not supported, not trigger a response to the first allocation information.

In a possible implementation manner, the first sub-device supports a second uplink rate, and the second uplink rate is different from the first uplink rate.

The transceiver is further used to receive second allocation information from the master device, the second allocation information includes a second allocation identifier and a second time information, the second time information is used to indicate a second allocation time slot, the second allocation identifier is used to indicate that an unactivated sub-device supporting the second uplink rate responds to the second allocation information, the second allocation identifier is different from the first allocation identifier, and the second time information is different from the first time information. The processor is further used to control the transceiver to send a first response information in the second allocation time slot when it is determined that the first sub-device supports the second uplink rate, and the first response information includes a serial number of the first sub-device.

In a possible implementation, the multiple sub-devices further include an unactivated second sub-device, the second sub-device supports a first uplink rate, the first allocation information is used by the second sub-device to send second response information in the first allocated time slot, and the second response information includes a serial number of the second sub-device.

In a possible implementation manner, the first allocation identifier is a broadcast allocation identifier, and the first allocation information is a sequence number request allocation structure.

In a possible implementation manner, the first allocation information is carried in a bandwidth mapping field in a downlink physical control block.

In a possible implementation manner, the first allocation identifier is 254, and the first uplink rate is 1.25G; or, the first allocation identifier is 255 or 253, and the first uplink rate is 2.5G.

In a possible implementation manner, the first allocation identifier is 254, the second allocation identifier does not include 254, the first uplink rate is 1.25G, and the second uplink rate is 2.5G.

In a possible implementation manner, the second allocation identifier is 255 or 253.

It should be noted that there are many other specific implementations of the embodiments of the present application. Please refer to the specific implementations of the first aspect and their beneficial effects for details, which will not be repeated here.

In a sixth aspect, the present application provides a communication device, which is applied to a fiber optic network system, wherein the fiber optic network system includes a main device and multiple sub-devices, wherein the multiple sub-devices include an unactivated first sub-device. The communication device may be a main device in the fiber optic network system, or may be a partial functional module or chip in the main device. The communication device includes a transceiver and a processor.

Wherein, the processor is used to generate first allocation information; the transceiver is used to send the first allocation information, the first allocation information includes a first allocation identifier and first time information, the first time information is used to indicate a first allocation time slot, and the first allocation identifier is used to indicate an unactivated sub-device supporting a first uplink rate to respond to the first allocation information; wherein, if the first sub-device supports the first uplink rate, the first allocation information is used for the first sub-device to send a first response information in the first allocation time slot, and the first response information includes the serial number of the first sub-device.

In a possible implementation manner, if the first sub-device does not support the first uplink rate, the first allocation information is used for the first sub-device not to respond to the first allocation information.

In a possible implementation manner, the first sub-device supports a second uplink rate, and the second uplink rate is different from the first uplink rate.

The transceiver is also used to send second allocation information, the second allocation information includes a second allocation identifier and second time information, the second time information is used to indicate a second allocated time slot, the second allocation identifier is used to indicate an unactivated sub-device supporting a second uplink rate to respond to the second allocation information, the second allocation identifier is different from the first allocation identifier, the second time information is different from the first time information, the second allocation information is used for the first sub-device to send a first response information in the second allocated time slot, and the first response information includes the serial number of the first sub-device.

In a possible implementation, the multiple sub-devices further include an unactivated second sub-device, the second sub-device supports a first uplink rate, the first allocation information is used by the second sub-device to send second response information in the first allocated time slot, and the second response information includes a serial number of the second sub-device.

In a possible implementation manner, the first allocation identifier is a broadcast allocation identifier, and the first allocation information is a sequence number request allocation structure.

In a possible implementation manner, the first allocation information is carried in a bandwidth mapping field in a downlink physical control block.

In a possible implementation manner, the first allocation identifier is 254, and the first uplink rate is 1.25G; or, the first allocation identifier is 255 or 253, and the first uplink rate is 2.5G.

In a possible implementation manner, the first allocation identifier is 254, the second allocation identifier does not include 254, the first uplink rate is 1.25G, and the second uplink rate is 2.5G.

In a possible implementation manner, the second allocation identifier is 255 or 253.

It should be noted that there are many other specific implementations of the embodiments of the present application. Please refer to the specific implementations of the first aspect or the third aspect and their beneficial effects, which will not be repeated here.

In the seventh aspect, an embodiment of the present application provides a communication device, which may be a sub-device (for example, a first sub-device) in the aforementioned implementation, or may be a chip in the sub-device (for example, the first sub-device). The communication device may include a processing module and a transceiver module. When the communication device is a sub-device (for example, a first sub-device), the processing module may be a processor, and the transceiver module may be a transceiver. Optionally, the sub-device (for example, the first sub-device) may also include a storage module, which 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 sub-device (for example, the first sub-device) executes the method in the first aspect or any one of the implementations of the first aspect. When the communication device is a chip in a sub-device (for example, a first sub-device), the processing module may be a processor, and the transceiver module may be an input/output interface, a pin or a circuit, etc.; the processing module executes the instructions stored in the storage module so that the sub-device (for example, the first sub-device) executes any one of the first aspect or the third aspect. The storage module may be a storage module in the chip (e.g., a register, a cache, etc.), or a storage module in the sub-device (e.g., the first sub-device) located outside the chip (e.g., a read-only memory, a random access memory, etc.).

In the eighth aspect, an embodiment of the present application provides a communication device, which may be a main device in the aforementioned implementation mode, or a chip in the main device. The communication device may include a processing module and a transceiver module. When the communication device is a main device, the processing module may be a processor, and the transceiver module may be a transceiver; the main device may also 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 main device executes the method in the second aspect or any one of the implementation modes of the second aspect. When the communication device is a chip in the main device, the processing module may be a processor, and the transceiver module may be an input/output interface, a pin or a circuit, etc.; the processing module executes the instructions stored in the storage module so that the main device executes the method in any one of the implementation modes of the second aspect or the fourth aspect. The storage module may be a storage module in the chip (for example, a register, a cache, etc.), or a storage module in the main device located outside the chip (for example, a read-only memory, a random access memory, etc.).

In a ninth aspect, the present application provides a communication device, which may be an integrated circuit chip. The integrated circuit chip includes a processor. The processor is coupled to a memory, and the memory is used to store a program or instruction. When the program or instruction is executed by the processor, the communication device executes the method described in any one of the first to fourth aspects and various embodiments of the aforementioned various aspects, and the aforementioned various aspects.

In the tenth aspect, an embodiment of the present application provides a computer program product comprising instructions, which, when the aforementioned instructions are executed on a computer, enables the computer to execute the method described in any one of the various embodiments of the aforementioned first to fourth aspects and various aspects.

In the eleventh aspect, an embodiment of the present application provides a computer-readable storage medium, comprising instructions, which, when executed on a computer, enable the computer to execute the method described in any one of the various embodiments of the first to fourth aspects and the various aspects.

In a twelfth aspect, an embodiment of the present application provides a fiber optic network system, which includes the first sub-device in the above-mentioned second aspect and any one of the embodiments of the second aspect, and the main device in the above-mentioned fourth aspect and any one of the embodiments of the fourth aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is an example diagram of a network architecture of a fiber optic network system in conventional technology;

FIG1B is an example diagram of an optical fiber network system in the present application;

FIG2 is a schematic diagram of a flow chart of the access method in the present application;

FIG3 is an example diagram of a downlink frame carrying a first allocation structure involved in the present application;

FIG4 is another schematic diagram of the access method in the present application;

FIG5 is a schematic diagram of an embodiment of a communication device in the present application;

FIG. 6 is a schematic diagram of an embodiment of a communication device in the present application.

DETAILED DESCRIPTION

The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments.

In the various embodiments of the present application, unless otherwise specified or provided in a logical conflict, the terms and/or descriptions between the different embodiments are consistent and may be referenced to each other, and the technical features in the different embodiments may be combined to form new embodiments according to their inherent logical relationships.

The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

It should be understood that the term "and/or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character "/" in this article generally indicates that the associated objects before and after are in an "or" relationship.

The access method provided by this application is applied to an optical fiber network system. To facilitate understanding of the access method proposed by this application, the basic architecture of the optical fiber network system in the traditional technology is first introduced below:

As shown in FIG. 1A , it is a basic architecture diagram of a fiber optic network system in conventional technology. The fiber optic network system 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 is generally connected to the ONU (or ONT) through the ODN. The ODN includes a network composed of optical devices such as optical fibers, optical distribution frames (ODF), optical splitters (also known as splitters), and combiners. In addition, the aforementioned 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 a downstream optical signal, and distributes the downstream optical signal to each ONU (or ONT) through the ODN. In the upstream direction, time division multiple access (TDMA) is adopted, and each ONU (or ONT) sends the upstream optical signal in its own upstream time slot allocated by the OLT.

As shown in FIG. 1B , it is a schematic diagram of the structure of the optical fiber network system provided by the present application. The optical fiber network system provided by the present application includes a main device 01 and multiple sub-devices 02, and the main device 01 is connected to the multiple sub-devices 02. The multiple sub-devices 02 include sub-devices with at least one upstream rate, that is, the multiple sub-devices 02 may all support a certain upstream rate. For example, the multiple sub-devices 02 include multiple first sub-devices 021 (for example, first sub-device #1 and first sub-device #2, etc.), and the first sub-device 021 is a sub-device that supports a certain upstream rate (for example, upstream rate 1). In addition, the multiple sub-devices 02 may also have multiple sub-devices that support different upstream rates. For example, multiple sub-devices 02 include at least one first sub-device 021 (for example, first sub-device #1 and first sub-device #2, etc.) and at least one second sub-device 022 (for example, second sub-device #1 and second sub-device #2, etc.), the second sub-device 022 is a sub-device that supports another uplink rate (for example, uplink rate 2), and the uplink rate supported by the first sub-device 021 is different from the uplink rate supported by the second sub-device 022.

It should be understood that the main device can be an OLT, the sub-device can be an ONU (or ONT), and the main device is connected to multiple sub-devices through an optical distribution network. Exemplarily, in a fiber to the room (FTTR) scenario, the main device can be called a main FTTR unit (MFU) or a main gateway, and the sub-device can be called a sub-FTTR unit (SFU) or a slave gateway. In one example, the sub-device can be directly connected to a terminal device at the user's home, which can be a mobile phone or tablet computer connected to the aforementioned router via wireless fidelity (Wi-Fi), or an Internet of Things device (for example, an indoor temperature control device, an indoor monitoring device, and other artificial intelligence devices). In another example, there are other networks (such as Ethernet, etc.) between the sub-device and the terminal device at the user's home, and the sub-device is an optical modem provided by the operator, which is then connected to indoor routers and other devices. This application is introduced by taking the main device and the slave device as an example.

The main process of the access method provided by this application will be introduced below in conjunction with Figure 2:

As shown in FIG2 , it is a flow chart of the access method provided by the present application. In which, the main device and the first sub-device will perform the following steps:

Step 201: The master device sends first allocation information; correspondingly, the first slave device receives the first allocation information.

The first allocation information includes a first allocation identifier and first time information. The first time information is used to indicate a first allocation time slot, which is an uplink bandwidth resource associated with the first allocation identifier and is used for a specific sub-device to send response information in the first allocation time slot.

Among them, the first allocation identifier is used to indicate that an unactivated sub-device supporting the first uplink rate responds to the first allocation information. It can also be understood that the first allocation identifier indicates that the first allocation information is used to discover unactivated sub-devices supporting the first uplink rate. It can be understood that the first allocation information provided in the present application is used to discover unactivated sub-devices that support a specific uplink rate (for example, the first uplink rate), and is not only used to discover unactivated sub-devices. For example, when multiple sub-devices receive the first allocation information, only unactivated sub-devices with a specific uplink rate (for example, the first uplink rate) can respond to the first allocation information.

Among them, the unactivated sub-device can be a sub-device that has not entered the activation process, or a sub-device that is at a certain stage in the activation process, or a sub-device that is unknown (or not discovered) by the main device. In this application, the term "unactivated sub-device" is mainly used for introduction. Optionally, the unactivated sub-device can be a sub-device that executes an activation procedure. Optionally, the unactivated sub-device can be a sub-device in a serial number collection state (Serial_Number state) (i.e., O3 state).

In addition, the allocation information may be an allocation structure, which is used to specify an allocation interval of a specific bandwidth allocation to the sub-device as the receiving party. The specific bandwidth allocation refers to the upstream bandwidth allocation used by the sub-device in a specific state, and the upstream bandwidth allocation is the allocation time slot (i.e., the allocation interval) of the master device at a specified time interval (i.e., the allocation interval) of the master device. An uplink transmission opportunity is given to a designated traffic bearing entity (eg, a transmission container (T-CONT) entity or an uplink management control channel) in a sub-device within an allocated time slot.

The allocation structure includes an allocation identifier (Alloc-ID) (also called an allocation identifier), which is a number assigned by the master device to the sub-device, and is used to identify a traffic bearing entity of a sub-device that receives upstream bandwidth allocation within the sub-device. In addition, the allocation identifier in the allocation structure can reflect the purpose of the allocation structure to a certain extent. For example, when the allocation identifier is a broadcast allocation identifier, the allocation structure corresponding to the allocation identifier (i.e., the allocation structure containing the allocation identifier) is used when an unactivated sub-device is found, that is, the allocation structure is used by the sub-device in the activation process. For example, the allocation structure is assigned by the master device to the sub-device to respond and report information (e.g., serial number) in the activation process.

The first allocation information in the present application may be an allocation structure including a first allocation identifier and first time information, which may be referred to as a first allocation structure. The first time information includes a start time (start time) and a stop time (stop time).

Optionally, the first allocation identifier is a broadcast allocation identifier, and the first allocation identifier is used in a serial number request allocation structure, that is, the first allocation information is a serial number request allocation structure. The first allocation information is used as a serial number request allocation structure to trigger a sub-device that supports the first uplink rate to execute an activation procedure (for example, a sub-device that supports the first uplink rate and is in a serial number collection state (Serial_Number state) (i.e., O3 state)) to respond to the first allocation information and report the serial number of the sub-device in the first allocation time slot.

It can also be understood that the first allocation information is carried in the broadcasted serial number request message, and the serial number request message is a request to allocate broadcast bandwidth to all inactive sub-devices in the serial number acquisition state (Serial_Number state). For example, the master device broadcasts a serial number request message, and the serial number request message includes the first allocation information. One or more inactive sub-devices connected to the master device can receive the serial number request message and obtain the first allocation information. However, only sub-devices that support the first uplink rate can respond to the first allocation information.

Optionally, taking the first allocation information as a first allocation structure as an example, the first allocation structure is carried in a bandwidth map (BWmap) field in a physical control block downstream (PCBd). For example, the first allocation structure is an 8-byte field in the bandwidth map (BWmap) field.

As shown in FIG3 , it is an example diagram of a downlink frame carrying a first allocation structure involved in the present application. FIG3 takes a downlink G-PON transmission convergence (gigabit PON transmission convergence, GTC) frame (Downstream GTC frame) as an example, and the downlink physical control block PCBd is located in the frame header of the downlink GTC frame. The downlink GTC frame includes a GTC frame header (i.e., a PCBd field) and a GTC payload. Among them, the PCBd field includes a physical synchronization (Psync) field (4 bytes), an IDENT field (4 bytes), a downlink physical layer operations administration and maintenance (physical layer operations administration and maintenance downstream, PLOAMd) field (13 bytes), a bit interleaved parity (bit interleaved parity, BIP) field (1 byte), a payload length (payload length, Plend) field (4 bytes) and an uplink bandwidth map (upstream bandwidth map, USBWmap) field (N*8 bytes). The BWmap field includes multiple allocation structures. The aforementioned first allocation structure may be located in the BWmap field, for example, the multiple allocation structures include the aforementioned first allocation structure. For example, the BWmap field may be a vector array of 8-byte allocation structures. Each allocation structure includes an allocation identifier. The first allocation structure includes a first allocation identifier.

In this step, after the first sub-device receives the first allocation information, the first sub-device needs to determine whether it supports the first uplink rate, that is, the first sub-device needs to determine whether the first sub-device supports the specific uplink rate (that is, the first uplink rate) corresponding to the first allocation identifier, and then the first device determines whether to respond to the first allocation information. If the first sub-device supports the first uplink rate, the first sub-device executes step 202a; if the first sub-device does not support the first uplink rate, the first sub-device executes step 202b.

Step 202a: If the first sub-device supports the first uplink rate, the first sub-device sends a first response message in the first allocated time slot; correspondingly, the main device receives the first response message.

In this embodiment, step 202a is an optional step.

The first response information includes the serial number of the first sub-device.

The first sub-device supports the first uplink rate, which means that the first sub-device can use the first uplink rate to send an uplink optical signal, and then the uplink optical signal from the first sub-device received by the main device uses the first uplink rate.

In addition, the first time information in the first allocation information indicates a first allocation time slot associated with the first allocation identifier, and the first allocation time slot is used for an unactivated sub-device supporting the first uplink rate to report the serial number of the sub-device through the first allocation time slot. In response to the first allocation information, the sub-device sends a first response information including the serial number of the first sub-device in the first allocated time slot.

Exemplarily, after the first sub-device receives the first allocation information, the first sub-device sends the sequence number of the first sub-device based on the first time information and a combined delay. For example, the first sub-device adds a random delay and a pre-allocated delay (for example, the pre-allocated delay indicated in the upstream frame header (Upstream_Overhead)) based on the start time in the first time information to send a sequence number response message, and the sequence number response message includes the sequence number of the first sub-device.

Optionally, if the main device is connected to multiple sub-devices that support the first uplink rate, the first allocation information broadcast by the main device indicates that any sub-device among the multiple sub-devices connected to the main device that is in a serial number collection state and executes an activation process at the first uplink rate can use the first allocated time slot indicated by the first time information in the first allocation information to transmit response information such as the serial number of the sub-device.

Step 202b: If the first sub-device does not support the first uplink rate, the first sub-device does not respond to the first allocation information.

In this embodiment, step 202b is an optional step.

The fact that the first sub-device does not support the first uplink rate means that the first sub-device cannot use the first uplink rate to send an uplink optical signal.

When the first sub-device receives the first allocation information, it determines based on the first allocation identifier in the first allocation information that the first allocated time slot is allocated to a sub-device supporting the first uplink rate, and the first sub-device does not support the first uplink rate, so the first sub-device does not respond.

In the present application, after the first sub-device receives the first allocation information carrying the first allocation identifier and the first time information, the first sub-device will respond to the first allocation information and send the serial number of the first sub-device in the first allocation time slot only when the first sub-device determines that it supports the first uplink rate. That is to say, the first allocation information received by the first sub-device is used to instruct the sub-device supporting the first uplink rate to report the serial number in the first allocation time slot, and will not trigger the sub-devices of other uplink rates (uplink rates other than the first uplink rate) to report the serial number in the first allocation time slot, which is conducive to avoiding the first sub-device and the sub-devices supporting other uplink rates from sharing the allocation time slot to report the serial number, that is, it is conducive to avoiding the main device from receiving optical signals of two uplink rates in a short time, and further conducive to reducing the implementation complexity of uplink burst reception.

Further, as shown in FIG4 , when there are sub-devices supporting different upstream rates in the optical fiber network system provided by the present application, each device in the optical fiber network system will perform the following steps:

Step 401: The main device sends first allocation information; accordingly, the first sub-device receives the first allocation information; and the second device receives the first allocation information.

The first allocation information includes a first allocation identifier and first time information. For explanations of the first allocation information, the first allocation identifier and the first time information, please refer to the relevant introduction in the above step 201, which will not be repeated here.

In addition, both the first sub-device and the second sub-device are inactivated sub-devices. The uplink rate supported by the first sub-device is different from the uplink rate supported by the second sub-device. For ease of introduction, the following text takes the case where the first sub-device supports the second uplink rate and the second sub-device supports the first uplink rate as an example. The first uplink rate is different from the second uplink rate.

Exemplarily, the master device broadcasts the first allocation information, and both the first sub-device and the second sub-device can receive the first allocation information. After the first sub-device receives the first allocation information, the first sub-device executes step 402; after the second sub-device receives the first allocation information, the second sub-device executes step 403. It should be understood that there is no time sequence limitation between step 402 and step 403, and step 402 can be executed after step 401, and step 403 can be executed after step 401.

Step 402: The first sub-device does not respond to the first allocation information.

Since the first sub-device does not support the first uplink rate, the first sub-device does not respond to the first allocation information.

Step 403: The second sub-device sends a second response message in the first allocated time slot; correspondingly, the main device receives the second response message.

Since the second sub-device supports the first uplink rate, the second sub-device uses the first allocated time slot to send second response information after receiving the first allocation information. The second response information includes the serial number of the second sub-device.

Step 404 and step 405 are optional steps.

Step 404: the master device sends second allocation information; correspondingly, the first slave device receives the second allocation information.

The second allocation information includes a second allocation identifier and second time information. The second time information is used to indicate a second allocation time slot, which is an uplink bandwidth resource associated with the second allocation identifier and is used for a specific sub-device to send response information in the second allocation time slot.

The second identification information is used to instruct the unactivated sub-device supporting the second uplink rate to respond to the second allocation information. It can also be understood that, The second allocation identifier indicates that the second allocation information is used to discover an unactivated sub-device that supports the second uplink rate. The second allocation identifier is different from the first allocation identifier, that is, the value of the second allocation identifier is different from the value of the first allocation identifier. The second time information is different from the first time information, that is, the first allocation time slot indicated by the first time information is different from the second allocation time slot indicated by the second time information. The first allocation information and the second allocation information are sent down through different bandwidth mappings (BWmap).

It can be understood that the second allocation information provided in the present application is used to discover an unactivated sub-device that supports another specific uplink rate (e.g., the second uplink rate), and is not only used to discover an unactivated sub-device, nor is it used to discover an unactivated sub-device that supports other uplink rates. For example, when multiple sub-devices receive the second allocation information, only the unactivated sub-device that supports the second uplink rate can respond to the second allocation information.

Optionally, the second allocation identifier is a broadcast allocation identifier, and the second allocation identifier is used in a serial number request allocation structure, that is, the second allocation information is a serial number request allocation structure. The second allocation information is used as a serial number request allocation structure to trigger a sub-device that supports the second uplink rate to execute an activation procedure (for example, a sub-device that supports the second uplink rate and is in a serial number collection state (Serial_Number state) (i.e., O3 state)) to respond to the second allocation information to report the serial number of the sub-device.

It can also be understood that the second allocation information is carried in the broadcasted serial number request message, which is a request to allocate broadcast bandwidth to all inactive sub-devices in the serial number acquisition state (Serial_Number state). For example, the master device broadcasts a serial number request message, which includes the second allocation structure, and one or more inactive sub-devices connected to the master device can receive the serial number request message to obtain the second allocation information. However, only sub-devices that support the second uplink rate can respond to the first allocation information.

Optionally, the second allocation information is carried in the bandwidth map (BWmap) field in the physical control block downstream (PCBd). For example, the second allocation structure is an 8-byte field in the bandwidth map (BWmap) field. Optionally, the downstream physical control block PCBd is located in the frame header of the downstream GTC frame. For the introduction to the frame header of the downstream GTC frame, please refer to the corresponding introduction of Figure 3 above, which will not be repeated here. The first allocation information and the second allocation information are carried and sent down in different bandwidth mapping (BWmap) fields.

Step 405: The first device sends first response information in the second allocated time slot.

The first response information includes the serial number of the first sub-device.

Since the first sub-device supports the second uplink rate, the first sub-device sends the first response information including the serial number of the first sub-device in the second allocated time slot in response to the second allocation information.

It should be noted that there is no time sequence limitation between step 401 to step 403 and step 404 to step 405. That is, the master device may broadcast the first allocation information first, or may broadcast the second allocation information first, and this application does not limit it.

In this embodiment, the main device can distinguish the allocation structures corresponding to the sub-devices supporting different uplink rates through different allocation identifiers, and further distinguish the allocation time slots for reporting the sequence numbers corresponding to the different allocation structures. That is, the first allocation identifier indicates that the first allocation structure is used to discover the unactivated sub-device supporting the first uplink rate, and the first allocation structure corresponds to the first allocation time slot; the second allocation identifier indicates that the second allocation structure is used to discover the unactivated sub-device supporting the second uplink rate, and the second allocation structure corresponds to the second allocation time slot. Therefore, the sub-devices supporting different uplink rates use different allocation time slots when reporting the sequence numbers. Compared with the use of different time slots in the same allocation time slot in the traditional technology, the time interval between the uplink optical signals of different uplink rates received by the main network device is lengthened, which is beneficial to reduce the complexity of the receiver for uplink burst reception.

In addition, it should be noted that, among the aforementioned first allocation identifier and the second allocation identifier, one of the allocation identifiers may continue to use the value of the allocation identifier used in the activation process in the traditional technology, and the other allocation identifier may be a newly defined allocation identifier. For ease of introduction, the following text takes the case where the first allocation identifier continues to use the value of the allocation identifier used in the activation process in the traditional technology, and the second allocation identifier is a newly defined allocation identifier as an example.

In a possible implementation, the first allocation identifier is equal to 254, and the first allocation identifier indicates that the first allocation structure is used to discover unactivated sub-devices that support an uplink rate of 1.24416 Gbit/s (hereinafter referred to as 1.25G sub-devices); the second allocation identifier is not equal to 254, and the second allocation identifier indicates that the second allocation structure is used to discover unactivated sub-devices that support an uplink rate of 2.48832 Gbit/s (hereinafter referred to as 2.5G sub-devices). When the master device broadcasts the first allocation structure (i.e., the allocation structure carrying Alloc-ID=254), the 1.25G sub-devices in the system respond to the first allocation structure by sending the serial number of the 1.25G sub-device, and the 2.5G sub-devices in the system do not respond to the first allocation structure. 1. Allocation structure. In this implementation, it is necessary to redefine the allocation identifier used by the 2.5G sub-device in the activation process. This can be implemented in a variety of ways, which are introduced below:

Furthermore, in one implementation, the second allocation identifier is equal to 255, and the second allocation identifier indicates that the second allocation structure is used to discover an unactivated sub-device supporting an uplink rate of 2.48832 Gbit/s (ie, a 2.5G sub-device).

For example, when 255 is defined as the allocation identifier used in the activation process, the functions of other allocation identifiers are shown in the following Table 1-1:

Table 1-1

As shown in Table 1-1, Alloc-ID = 0 to 253 is the default allocation identifier (i.e., the default Alloc-ID), which is implicitly allocated through the identifier of the sub-device (i.e., SFU-ID, which is used in the PLOAM message) and does not require an explicit Assign_Alloc-ID PLOAM message for allocation. The default Alloc-ID is used to carry PLOAM and FMCC traffic for uplink frames, and may also carry user data traffic. In addition, the Assign_Alloc-ID PLOAM message cannot be used to cancel or change the default Alloc-ID. If the sub-device requires more Alloc-ID values, the master device will allocate from Alloc-ID values above 255.

In addition, Alloc-ID=254 is a newly defined reserved allocation identifier.

In addition, Alloc-ID=255 is a newly defined broadcast allocation identifier, which can be understood as Alloc-ID=255 is the Alloc-ID used by the sub-device supporting 2.48832Gbit/s in the activation process, and is used to discover unknown (or unactivated) sub-devices. For example, the Alloc-ID=255 is used in the serial number request allocation structure, that is, the allocation structure corresponding to the Alloc-ID=255 is the serial number request allocation structure. The allocation structure corresponding to the Alloc-ID=255 is used as a serial number request allocation structure to trigger the execution of the activation procedure. The sub-device supporting 2.48832Gbit/s (for example, a sub-device in the serial number acquisition state (Serial_Number state) (i.e., O3 state)) responds to the allocation structure corresponding to the Alloc-ID=255 to report the serial number of the sub-device.

In addition, Alloc-ID = 256 ~ 4095 is an assignable allocation identifier. When a sub-device requires multiple Alloc-IDs, the master device can allocate an additional Alloc-ID (i.e., additional Alloc-ID) to the sub-device by selecting a unique number from this range (i.e., 256 ~ 4095) and passing it to the sub-device using an Assign_Alloc-ID PLOAM message. In addition, the additional Alloc-ID is explicitly assigned to the sub-device through an Assign_Alloc-ID PLOAM message with an Alloc-ID type of 1, and can also be explicitly revoked through an Assign_Alloc-ID PLOAM message with an Alloc-ID type of 255. All Alloc-ID allocations, including the default Alloc-ID allocation, will become invalid when the sub-device is deactivated.

In this implementation, for the sub-device supporting 2.48832Gbit/s, Alloc-ID=254 is redefined as a reserved allocation identifier, that is, Alloc-ID=254 is not carried in the allocation structure, and Alloc-ID=255 is redefined as a broadcast allocation identifier. The sub-device supporting the uplink rate of 1.24416Gbit/s uses Alloc-ID=254 in the activation process. Therefore, in the activation process, the 2.5G sub-device uses the allocation structure and allocation time slot corresponding to Alloc-ID=255, and the 1.25G sub-device uses the allocation structure and allocation time slot corresponding to Alloc-ID=254. Therefore, the sub-devices supporting different uplink rates use different allocation time slots when reporting sequence numbers, which can realize multi-rate separate windowing, which is conducive to reducing the implementation complexity of uplink burst reception.

Furthermore, in another implementation, the second allocation identifier is equal to 253, and the second allocation identifier indicates that the second allocation structure is used to discover an unactivated sub-device supporting an uplink rate of 2.48832 Gbit/s (ie, a 2.5G sub-device).

For example, when 253 is defined as the allocation identifier used in the activation process, the functions of other allocation identifiers are shown in the following Table 1-2:

Table 1-2

As shown in Table 1-2, Alloc-ID = 0 to 252 is the default allocation identifier (i.e., the default Alloc-ID), which is implicitly allocated through the identifier of the sub-device (i.e., SFU-ID, which is used in the PLOAM message) and does not require an explicit Assign_Alloc-ID PLOAM message for allocation. The default Alloc-ID is used to carry PLOAM and FMCC traffic for uplink frames, and may also carry user data traffic. In addition, the Assign_Alloc-ID PLOAM message cannot be used to cancel or change the default Alloc-ID. If the sub-device requires more Alloc-ID values, the master device will allocate from Alloc-ID values above 255.

In addition, Alloc-ID=253 is a newly defined broadcast allocation identifier, which can be understood as Alloc-ID=253 is the Alloc-ID used by the sub-device supporting 2.48832Gbit/s in the activation process, and is used to discover unknown (or unactivated) sub-devices. For example, the Alloc-ID=253 is used in the serial number request allocation structure, that is, the allocation structure corresponding to the Alloc-ID=253 is the serial number request allocation structure. The allocation structure corresponding to the Alloc-ID=253 is used as a serial number request allocation structure to trigger the execution of the activation procedure. The sub-device supporting 2.48832Gbit/s (for example, a sub-device in the serial number acquisition state (Serial_Number state) (i.e., O3 state)) responds to the allocation structure corresponding to the Alloc-ID=253 to report the serial number of the sub-device.

In addition, Alloc-ID=254 is a newly defined reserved allocation identifier.

In addition, Alloc-ID=255 is a newly defined unassigned allocation identifier. This Alloc-ID=255 can be used by the master device, indicating that no sub-device should use a specific allocation structure, that is, no sub-device should use the allocation structure corresponding to Alloc-ID=255.

In addition, Alloc-ID = 256 ~ 4095 is an assignable allocation identifier. When a sub-device requires multiple Alloc-IDs, the master device can allocate an additional Alloc-ID (i.e., additional Alloc-ID) to the sub-device by selecting a unique number from this range (i.e., 256 ~ 4095) and passing it to the sub-device using an Assign_Alloc-ID PLOAM message. In addition, the additional Alloc-ID is explicitly assigned to the sub-device through an Assign_Alloc-ID PLOAM message with an Alloc-ID type of 1, and can also be explicitly revoked through an Assign_Alloc-ID PLOAM message with an Alloc-ID type of 255. All Alloc-ID allocations, including the default Alloc-ID allocation, will become invalid when the sub-device is deactivated.

In this implementation, for the sub-device supporting 2.48832Gbit/s, Alloc-ID=254 is redefined as a reserved allocation identifier, that is, Alloc-ID=254 is not carried in the allocation structure, and Alloc-ID=253 is redefined as a broadcast allocation identifier. The sub-device supporting the uplink rate of 1.24416Gbit/s uses Alloc-ID=254 in the activation process. Therefore, in the activation process, the 2.5G sub-device uses the allocation structure and allocation time slot corresponding to Alloc-ID=253, and the 1.25G sub-device uses the allocation structure and allocation time slot corresponding to Alloc-ID=254. Therefore, the sub-devices supporting different uplink rates use different allocation time slots when reporting sequence numbers, which can realize multi-rate separate windowing, which is conducive to reducing the implementation complexity of uplink burst reception.

In the access method provided in the embodiment of the present application, after the ONU is activated, the OLT can obtain the capabilities supported by the ONU or set the ONU's Capabilities, such as the FEC code used by the ONU upstream when the OLT sets it. For example, the OLT may send a capability acquisition (setting) message to the ONU, which is used to query the capabilities supported by the ONU or to set a specific capability for the ONU. A single capability acquisition (setting) message may set a capability supported by the ONU, and the capabilities (also referred to as features or functions) supported by the ONU may be carried through specific fields. For example, the features supported by the ONU are carried through the "Set Feature Identifier" field.

The Get_Set_Capabilities message provided in the embodiment of the present application may carry multiple information, and the Get_Set_Capabilities message may be specifically as shown in the following Table 1:

Table 1 - Get_Set_Capabilities message

Table 1 - Get_Set_Capabilities message

In the above-mentioned Get_Set_Capabilities message, when the "Set feature identifier" in the 6th byte has a value of 0x01 (set uplink FEC encoding), the FEC encoding identifier is indicated in the 9th byte (set feature parameters), and the timestamp for setting this feature is indicated in bytes 7-8 (planned superframe counter).

Furthermore, when the "Set Feature Identifier" in the 6th byte has a value of 0x01 and the "Set Feature Parameter" in the 9th byte has a value of 0x02, the "Number of Shortened Columns" in the 10th byte contains the number of columns of the LDPC code that need to be shortened.

Correspondingly, after the OLT sends the Get_Set_Capabilities message, the ONU can respond to the OLT with a capability message, which carries the features supported by the ONU. The ONU capability message ONU_Capabilities message provided in the embodiment of the present application can carry multiple pieces of information, and the ONU_Capabilities message can be specifically shown in Table 2 below:

Table 2 – ONU_Capabilities message

Table 2 – ONU_Capabilities message

Table 2 – ONU_Capabilities message

In this embodiment, the capability information reported by the ONU may include the FEC codewords supported by the ONU. For example, the ONU carries the FEC codewords supported by it in the eighth byte.

In the access method provided in this embodiment, the ONU capability (ONU_Capabilities) message includes the following functions:

1) Respond to the Get_Set_Capability PLOAM message carrying the query operation code and report the ONU capabilities.

2) The ONU_Capabilities message can also respond to the Get_Set_Capability PLOAM message carrying the setting operation code, indicating the desire or inability to perform the capability setting, and the response code. The operation code and response code carry the reason why the ONU desires or cannot perform the capability setting. For specific values, refer to the table above.

3) Provide an indication of the success or failure of the capability setting execution and a response code.

The above functions 1 and 2 are implemented by the ONU when it receives the downstream Get_Set_Capability PLOAM message.

Function 3 above is implemented when the ONU completes its attempt to execute the set command transmitted by the Get_Set_Capability PLOAM message.

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

As shown in FIG5 , the communication device 50 may include a processor 501 and a transceiver 502, wherein the processor 501 is coupled to the transceiver 502. The processor 501 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof. The processor 501 may refer to one processor or may include multiple processors, which is not specifically limited here.

Among them, the aforementioned transceiver 502 may also be referred to as a transceiver unit, a transceiver, a transceiver device, etc. Optionally, the device used to implement the receiving function in the transceiver unit may be regarded as a receiving unit, and the device used to implement 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, and 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. Optionally, when the communication device 50 is used to implement the function of the master device in the method shown in FIG. 2 or FIG. 3, the transceiver 502 may be used for receiving an uplink burst optical signal. Optionally, the transceiver 502 supports receiving burst optical signals of one or more uplink rates. For example, the transceiver 502 supports receiving an uplink burst optical signal of 2.48832 Gbit/s. For another example, the transceiver 502 supports receiving an uplink burst optical signal of 1.24416 Gbit/s.

Optionally, the communication device 50 further includes a memory 503. The processor 501 is coupled to the memory 503. The memory 503 is mainly used to store software programs and data. The memory 503 can exist independently and be connected to the processor 501. Optionally, the memory 503 can be integrated with the processor 501, for example, integrated into one or more chips. Among them, the memory 503 can store program codes for executing the technical solutions of the embodiments of the present application, and the execution is controlled by the processor 501. The various types of computer program codes executed can also be regarded as drivers of the processor 501. The memory 503 may include volatile memory (volatile memory), such as random-access memory (random-access memory, RAM); the memory may also include non-volatile memory (non-volatile memory), such as read-only memory (read-only memory, ROM), flash memory (flash memory), hard disk drive (hard disk drive, HDD) or solid-state drive (solid-state drive, SSD); the memory 503 may also include a combination of the above-mentioned types of memory. The memory 503 may refer to one memory or may include multiple memories. Exemplarily, the memory 503 is used to store various data.

In one implementation, the communication device 50 is used to implement the function of the first sub-device in the optical fiber network system. Specifically, the transceiver 502 is used to receive the first allocation information from the main device, the first allocation information includes a first allocation identifier and a first time information, the first time information is used to indicate the first allocation time slot, and the first allocation identifier is used to indicate that the unactivated sub-device supporting the first uplink rate responds to the first allocation information; the processor 501 is used to control the transceiver 502 to send the first response information in the first allocation time slot when it is determined that the first uplink rate is supported, and the first response information includes the serial number of the first sub-device.

In a possible implementation, the processor 501 is configured to, when determining that the first uplink rate is not supported, not trigger a response to the first allocation information.

In a possible implementation, the first sub-device supports a second uplink rate, and the second uplink rate is different from the first uplink rate. The transceiver 502 is also used to receive second allocation information from the main device, the second allocation information includes a second allocation identifier and second time information, the second time information is used to indicate a second allocated time slot, the second allocation identifier is used to indicate that an unactivated sub-device supporting the second uplink rate responds to the second allocation information, the second allocation identifier is different from the first allocation identifier, and the second time information is different from the first time information. The processor 501 is also used to control the transceiver 502 to send a first response information in the second allocated time slot when it is determined that the first sub-device supports the second uplink rate, and the first response information includes the serial number of the first sub-device.

In a possible implementation, the multiple sub-devices further include an unactivated second sub-device, the second sub-device supports a first uplink rate, the first allocation information is used by the second sub-device to send second response information in the first allocated time slot, and the second response information includes a serial number of the second sub-device.

In a possible implementation manner, the first allocation identifier is a broadcast allocation identifier, and the first allocation information is a sequence number request allocation structure.

In a possible implementation manner, the first allocation information is carried in a bandwidth mapping field in a downlink physical control block.

In a possible implementation manner, the first allocation identifier is 254, and the first uplink rate is 1.25G; or, the first allocation identifier is 255 or 253, and the first uplink rate is 2.5G.

In a possible implementation manner, the first allocation identifier is 254, the second allocation identifier does not include 254, the first uplink rate is 1.25G, and the second uplink rate is 2.5G.

In a possible implementation manner, the second allocation identifier is 255 or 253.

In another implementation, the communication device 50 is used to implement the function of a master device in a fiber optic network system. Specifically, the processor 501 is used to generate first allocation information; the transceiver 502 is used to send the first allocation information, the first allocation information includes a first allocation identifier and first time information, the first time information is used to indicate a first allocation time slot, and the first allocation identifier is used to indicate that an unactivated sub-device supporting a first uplink rate responds to the first allocation information; wherein, if the first sub-device supports the first uplink rate, the first allocation information is used for the first sub-device to send a first response information in the first allocation time slot, and the first response information includes a serial number of the first sub-device.

In a possible implementation manner, if the first sub-device does not support the first uplink rate, the first allocation information is used for the first sub-device not to respond to the first allocation information.

In a possible implementation manner, the first sub-device supports a second uplink rate, and the second uplink rate is different from the first uplink rate.

The transceiver 502 is also used to send second allocation information, the second allocation information includes a second allocation identifier and a second time information, the second time information is used to indicate a second allocated time slot, the second allocation identifier is used to indicate that an unactivated sub-device supporting a second uplink rate responds to the second allocation information, the second allocation identifier is different from the first allocation identifier, the second time information is different from the first time information, the second allocation information is used for the first sub-device to send a first response information in the second allocated time slot, and the first response information includes the serial number of the first sub-device.

In a possible implementation manner, the plurality of sub-devices further include an unactivated second sub-device, the second sub-device supports the first uplink rate, the first allocation information is used for the second sub-device to send the second response information in the first allocated time slot, and the second response information includes the sequence number of the second sub-device Number.

In a possible implementation manner, the first allocation identifier is a broadcast allocation identifier, and the first allocation information is a sequence number request allocation structure.

In a possible implementation manner, the first allocation information is carried in a bandwidth mapping field in a downlink physical control block.

In a possible implementation manner, the first allocation identifier is 254, and the first uplink rate is 1.25G; or, the first allocation identifier is 255 or 253, and the first uplink rate is 2.5G.

In a possible implementation manner, the first allocation identifier is 254, the second allocation identifier does not include 254, the first uplink rate is 1.25G, and the second uplink rate is 2.5G.

In a possible implementation manner, the second allocation identifier is 255 or 253.

For details, please refer to the relevant descriptions in the embodiments corresponding to FIG. 2 and FIG. 4 above, which will not be repeated here.

As shown in FIG6 , the present application further provides a communication device 60. The communication device 60 may be a sub-device (e.g., a first sub-device) or a main device, or may be a component (e.g., an integrated circuit, a chip, etc.) of a sub-device (e.g., a first sub-device) or a main device. The communication device 60 may also be other communication modules for implementing the method in the method embodiment of the present application.

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

In a possible design, one or more modules in FIG. 6 may be implemented by one or more processors, or by one or more processors and memories; or by one or more processors and transceivers; or by one or more processors, memories, and transceivers, which are not limited in the embodiments of the present application. The processor, memory, and transceiver may be provided separately or integrated into one.

The communication device 60 has the function of implementing the sub-device (e.g., the first sub-device) described in the embodiment of the present application. For example, the communication device 60 includes a sub-device (e.g., the first sub-device) executing the module or unit or means corresponding to the steps involved in the sub-device (e.g., the first sub-device) described in the embodiment of the present application, and the function or unit or means can be implemented by software, or by hardware, or by hardware executing the corresponding software implementation, or by a combination of software and hardware. For details, please refer to the corresponding description in the aforementioned corresponding method embodiment. Please refer to the communication device 50 in the corresponding embodiment of Figure 5 above.

Alternatively, the communication device 60 has the function of implementing the main device described in the embodiment of the present application. For example, the communication device 60 includes a module or unit or means corresponding to the main device steps described in the embodiment of the present application, and the function or unit or means can be implemented by software, or by hardware, or by hardware executing the corresponding software implementation, or by a combination of software and hardware. For details, please refer to the corresponding description in the aforementioned corresponding method embodiment. Please refer to the communication device 50 in the corresponding embodiment of Figure 5 above.

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 process or function according to the embodiment of the present application is generated in whole or in part. For example, a method related to a sub-device (e.g., a first sub-device) as shown in Figure 2 or Figure 3 is implemented. For another example, a method related to a main device as shown in Figure 2 or Figure 3 is implemented. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital versatile disc (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.

In addition, the present application also provides a computer-readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement a method related to a sub-device (for example, the first sub-device) as shown in Figure 2 or Figure 3 above.

In addition, the present application also provides a computer-readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement a method related to the main device as shown in Figure 2 or Figure 3 above.

It will be clear to those skilled in the art that for the convenience and brevity of description, the specific embodiments of the systems, devices and units described above are For the whole working process, reference can be made to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims (16)

An access method is applied to an optical fiber network system, wherein the optical fiber network system includes a main device and a plurality of sub-devices, and is characterized by comprising: The first sub-device receives first capability acquisition setting information from the main device, where the first capability acquisition setting information includes an identifier of the first sub-device and a query operation code; The first sub-device obtains its own capability information, and sends a capability reporting message to the main device, where the capability reporting message carries the capability information of the first sub-device. The method according to claim 1, further comprising: The first sub-device receives second capability acquisition setting information from the main device, where the second capability acquisition setting information includes an identifier of the first sub-device, a setting operation code, and a capability to be set; The first sub-device configures itself according to the capability to be configured; The first sub-device sends a capability setting message to the main device, where the capability setting message carries a result of the first sub-device setting itself. The method according to claim 2 is characterized in that the capability to be set in the second capability acquisition setting information includes setting an FEC code and a timestamp on the uplink of the first sub-device, and the method further comprises: The first sub-device performs FEC encoding on the uplink data stream according to the timestamp. The method according to claim 3 is characterized in that the second capability acquisition setting information also includes an FEC code identifier. The method according to claim 3 is characterized in that the FEC code on the uplink of the first sub-device includes one or more of a default FEC code, a high margin code, and a high throughput code. The method according to claim 5 is characterized in that when the uplink FEC code of the first sub-device is a high margin code, the second capability acquisition setting information also includes the number of columns of the LDPC code that are shortened. The method according to claim 2 is characterized in that the capability setting message carries an operation code, and the operation code is used to identify whether the first sub-device arranges capability setting. The method according to claim 7 is characterized in that the capability setting message also carries a response code, and the response code is used to identify the reason why the first sub-device did not arrange the capability setting. The method according to any one of claims 1 to 8 is characterized in that the capability information of the first sub-device includes FEC codewords supported by the first sub-device. An access method is applied to an optical fiber network system, wherein the optical fiber network system includes a main device and a plurality of sub-devices, and is characterized by comprising: The master device sends first capability acquisition setting information to the first sub-device, where the first capability acquisition setting information includes an identifier of the first sub-device and a query operation code; The main device receives a capability reporting message sent by the first sub-device, where the capability reporting message carries capability information of the first sub-device. The method according to claim 10, further comprising: The master device sends second capability acquisition setting information to the first sub-device, where the second capability acquisition setting information includes an identifier of the first sub-device, a setting operation code, and a capability to be set; The main device receives a capability setting message sent by the first sub-device, where the capability setting message carries a result of the first sub-device setting itself. The method according to claim 10, further comprising: The main device stores capability information of the first sub-device. The method according to claim 10 or 11 is characterized in that the first capability acquisition setting information or the second capability acquisition setting information carries the message integrity check value, and the message integrity check value is calculated based on the integrity key between the main device and the first sub-device. The method according to any one of claims 10 to 13 is characterized in that the second capability acquisition setting information also includes an FEC code identifier. The method according to any one of claims 10 to 14 is characterized in that the first capability acquisition setting information and the second capability acquisition setting information are downlink PLOAM messages, and the capability reporting message and the capability setting message are uplink PLOAM messages. A communication device, comprising: A processor and a transceiver, wherein the processor is connected to the transceiver, and the processor is used to implement the method according to any one of claims 1 to 9 or the method according to any one of claims 10 to 15.