Access method, optical fiber network system, and related device

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

[0001] This application claims priority to 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”, the entire contents of which are incorporated by reference into this application. Technical Field

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

[0003] Fiber to the room (FTTR) refers to a technology that uses optical fiber instead of network cables, providing fiber media access to rooms via the optical network terminal (ONT). The fiber optic network system in this FTTR scenario consists of a master device and one or more slave devices. The master device triggers the activation process of a slave device after it comes online.

[0004] In the traditional activation process, the master device broadcasts a sequence number request allocation structure, prompting the sub-device that receives this allocation structure to report its serial number by sending an uplink optical signal, thereby triggering the subsequent activation process. However, the fiber optic network system may contain sub-devices that support different uplink rates. These sub-devices, which support different uplink rates, transmit light at their respective supported uplink rates in the allocated time slots indicated by the allocation structure. As a result, the uplink optical signals received by the master device in these allocated time slots have different uplink rates. This means that the master device needs to receive bursts of uplink optical signals at different uplink rates in a relatively short period of time, increasing the complexity of implementing uplink burst reception.

[0005] Summary of the Invention

[0006] The present application provides an access method, an optical fiber network system, and related equipment for reducing the implementation complexity of uplink burst reception.

[0007] 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 an unactivated sub-device that supports a first uplink rate to respond 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.

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

[0009] 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 first sub-device's serial number in the first allocated time slot only if the first sub-device determines that it supports the first uplink rate. In other words, 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 allocated time slot, and will not trigger sub-devices of other uplink rates (at uplink rates other than the first uplink rate) to report the serial number in the first allocated time slot. This helps avoid the first sub-device and sub-devices supporting other uplink rates sharing the allocated time slot to report the serial number, that is, helps avoid the main device receiving optical signals of two uplink rates in a relatively short period of time, thereby helping to reduce the implementation complexity of uplink burst reception.

[0010] In one possible implementation, the first sub-device supports a second uplink rate, which is different from the first uplink rate. In this case, the access method further includes:

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

[0012] In a possible implementation, the multiple sub-devices further include an unactivated second sub-device, the second sub-device supports the 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 the serial number of the second sub-device.

[0013] In this implementation, the master device can use different allocation identifiers to distinguish the allocation information corresponding to sub-devices supporting different uplink rates, and thus distinguish the allocated time slots for reporting sequence numbers corresponding to the different allocation information. Sub-devices supporting different uplink rates use different allocated time slots when reporting sequence numbers. Compared to traditional technologies that use different time slots within the same allocated time slot, this increases the time interval between the master network device receiving uplink optical signals of different uplink rates, helping to reduce the complexity of the receiver for uplink burst reception.

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

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

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

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

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

[0019] In this implementation, for sub-devices supporting 2.48832 Gbit / s, Alloc-ID = 254 is redefined as a reserved allocation identifier, meaning Alloc-ID = 254 is not included in the allocation structure. Furthermore, Alloc-ID = 255 is redefined as a broadcast allocation identifier. Sub-devices supporting an uplink rate of 1.24416 Gbit / s use Alloc-ID = 254 during the activation process. Therefore, during the activation process, 2.5G sub-devices use the allocation structure and allocated timeslots corresponding to Alloc-ID = 255, while 1.25G sub-devices use the allocation structure and allocated timeslots corresponding to Alloc-ID = 254. Therefore, sub-devices supporting different uplink rates use different allocated timeslots when reporting sequence numbers, enabling independent windowing for multiple rates and reducing the complexity of uplink burst reception.

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

[0021] In this implementation, for sub-devices supporting 2.48832 Gbit / s, Alloc-ID = 254 is redefined as a reserved allocation identifier, meaning Alloc-ID = 254 is not included in the allocation structure. Furthermore, Alloc-ID = 253 is redefined as a broadcast allocation identifier. Sub-devices supporting an uplink rate of 1.24416 Gbit / s use Alloc-ID = 254 during the activation process. Therefore, during the activation process, 2.5G sub-devices use the allocation structure and allocated timeslots corresponding to Alloc-ID = 253, while 1.25G sub-devices use the allocation structure and allocated timeslots corresponding to Alloc-ID = 254. Therefore, sub-devices supporting different uplink rates use different allocated timeslots when reporting sequence numbers, enabling independent windowing for multiple rates and reducing the complexity of uplink burst reception.

[0022] 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, and 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 an unactivated sub-device that supports 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. 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.

[0023] In this application, the master device can send first allocation information carrying a first allocation identifier and first time information to instruct only inactive sub-devices that support the first uplink rate to trigger the transmission of the sub-device's sequence number in the first allocated time slot indicated by the first time information, while not triggering sub-devices that do not support the first uplink rate to report their sub-device's sequence number in the first allocated time slot. Therefore, this helps prevent sub-devices supporting different uplink rates from sharing the same allocated time slot to report sequence numbers, thus preventing the master device from receiving optical signals at two uplink rates in a relatively short period of time, thereby reducing the implementation complexity of uplink burst reception.

[0024] In one possible implementation, the first sub-device supports a second uplink rate, which is different from the first uplink rate. The access method further includes: the master device sends 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 instruct an unactivated sub-device that supports the 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 by 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.

[0025] In a possible implementation, the multiple sub-devices further include an unactivated second sub-device, the second sub-device supports the 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 the serial number of the second sub-device.

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

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

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

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

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

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

[0032] In a third aspect, the present application provides an access method applied to a fiber optic network system, wherein the fiber optic network system includes a master device and multiple sub-devices, and the access method includes:

[0033] 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;

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

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

[0036] 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, thereby managing the resources and communication process of the first sub-device.

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

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

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

[0040] Through the above-mentioned second capability acquisition setting message, the main device can set the capability of the first sub-device, for example, set 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 enhance communication security.

[0041] 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 for the first sub-device, and the method further includes:

[0042] The first sub-device applies the FEC code to the uplink data stream according to the timestamp, that is, when the time corresponding to the timestamp arrives, the first sub-device uses the new FEC codeword to encode the uplink data stream, thereby updating the codeword encoded by the uplink data stream of the first sub-device.

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

[0044] In a possible implementation manner, 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.

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

[0046] In one possible implementation, the above-mentioned 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.

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

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

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

[0050] In one possible implementation, the capability setting message further carries a response code, where the response code is used to identify a reason why the first sub-device did not schedule 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 being busy.

[0051] In one possible implementation, the response code is used to identify the reason why the first sub-device did not complete the capability setting. For example, the reason includes at least one of insufficient resources of the first sub-device, other errors, or the first sub-device being unable to obtain downlink synchronization (DSYNC) after setting the capability.

[0052] In a fourth 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 master device and multiple sub-devices, and the access method includes:

[0053] 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;

[0054] The master 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.

[0055] In a possible implementation, the master 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 (feature or function) to be set;

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

[0057] 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 in the capability reporting message.

[0058] In a possible implementation, 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 (IK) between the main device and the first sub-device.

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

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

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

[0062] In the access method provided in this embodiment, the capability reporting message and capability setting message can be unified into an ONU capability (ONU_Capabilities) message. The ONU_Capabilities message can be distinguished as a capability reporting message or a capability setting message by the "no pass" operation code carried in the message. The ONU_Capabilities message can respond to a Get_Set_Capability PLOAM message carrying a query operation code to report the ONU capabilities. The ONU_Capabilities message can also respond to a Get_Set_Capability PLOAM message carrying a set operation code to indicate whether the capability setting is desired or not, along with a response code. Furthermore, the ONU_Capabilities message can also provide an indication of the success or failure of the capability setting, as well as a response code.

[0063] In a fifth aspect, the present application provides a communication device, which is applied to a fiber optic network system. 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 can be the first sub-device in the fiber optic network system, or it can be a functional module or chip in the first sub-device. The communication device includes a transceiver and a processor.

[0064] The transceiver is configured to receive first allocation information from the master device, the first allocation information including a first allocation identifier and first time information, the first time information being used to indicate a first allocated time slot, and the first allocation identifier being used to instruct an unactivated sub-device supporting a first uplink rate to respond to the first allocation information;

[0065] 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, where the first response information includes a serial number of the first sub-device.

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

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

[0068] The transceiver is further configured to receive second allocation information from the master device, the second allocation information including a second allocation identifier and second time information, the second time information being used to indicate a second allocated time slot, the second allocation identifier being used to instruct an inactivated sub-device supporting the second uplink rate to respond to the second allocation information, the second allocation identifier being different from the first allocation identifier, and the second time information being different from the first time information. The processor is further configured to, upon determining that the first sub-device supports the second uplink rate, control the transceiver to send first response information in the second allocated time slot, the first response information including the serial number of the first sub-device.

[0069] In a possible implementation, the multiple sub-devices further include an unactivated second sub-device, the second sub-device supports the 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 the serial number of the second sub-device.

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

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

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

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

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

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

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

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

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

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

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

[0081] In a possible implementation, the multiple sub-devices further include an unactivated second sub-device, the second sub-device supports the 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 the serial number of the second sub-device.

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

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

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

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

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

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

[0088] In a seventh aspect, an embodiment of the present application provides a communication device, which may be a sub-device (e.g., a first sub-device) in the aforementioned embodiment, or a chip within the sub-device (e.g., the first sub-device). The communication device may include a processing module and a transceiver module. When the communication device is a sub-device (e.g., the first sub-device), the processing module may be a processor, and the transceiver module may be a transceiver. Optionally, the sub-device (e.g., the first sub-device) may further 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 (e.g., the first sub-device) performs the method in the first aspect or any one of the embodiments of the first aspect. When the communication device is a chip within a sub-device (e.g., the 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 (e.g., the first sub-device) performs the method in any one of the embodiments of the first aspect or the third aspect. The storage module can be a storage module within the chip (for example, a register, a cache, etc.), or a storage module within the sub-device (for example, the first sub-device) located outside the chip (for example, a read-only memory, a random access memory, etc.).

[0089] In an eighth aspect, an embodiment of the present application provides a communication device, which may be a main device in the aforementioned embodiment or a chip within the main device. The communication device may include a processing module and a transceiver module. When the communication device is a main device, the processing module may be a processor and the transceiver module may be a transceiver; the main device may 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 to cause the main device to perform the method in the second aspect or any one of the embodiments of the second aspect. When the communication device is a chip within the main device, the processing module may be a processor and the transceiver module may be an input / output interface, pin, or circuit; the processing module executes the instructions stored in the storage module to cause the main device to perform the method in the second aspect or any one of the embodiments of the fourth aspect. The storage module may be a storage module within the chip (e.g., a register, cache, etc.) or a storage module within the main device located outside the chip (e.g., a read-only memory, a random access memory, etc.).

[0090] 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, which stores programs or instructions. When the processor executes the programs or instructions, the communication device performs the methods described in any of the various embodiments of the first to fourth aspects, as well as the various aspects described above.

[0091] In the tenth aspect, an embodiment of the present application provides a computer program product comprising instructions, which, when the aforementioned instructions are run 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 each of the aforementioned aspects.

[0092] 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 aforementioned first to fourth aspects and the various aspects.

[0093] In the 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

[0094] FIG1A is an example diagram of a network architecture of a conventional optical fiber network system;

[0095] FIG1B is an example diagram of an optical fiber network system in this application;

[0096] FIG2 is a flow chart of the access method in this application;

[0097] FIG3 is an example diagram of a downlink frame carrying a first allocation structure involved in this application;

[0098] FIG4 is another flow chart of the access method in this application;

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

[0100] FIG6 is a schematic diagram of an embodiment of a communication device in the present application. DETAILED DESCRIPTION

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

[0102] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0103] The terms "first," "second," "third," "fourth," and the like (if any) in the specification and claims of this application and in the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or sequential sequence. It should be understood that the terms used in this manner 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, e.g., a process, method, system, product, or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such process, method, product, or apparatus.

[0104] It should be understood that the term "and / or" in this document simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0105] The access method provided in this application is applied to a fiber optic network system. To facilitate understanding of the access method proposed in this application, the basic architecture of a fiber optic network system in conventional technology is first introduced below:

[0106] As shown in Figure 1A, it is a basic architecture diagram of a fiber optic network system in traditional technology. The fiber optic network system includes an optical line terminal (OLT), an optical distribution network (ODN) and an optical network unit (ONU) (or 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 components such as optical fiber, optical distribution frame (ODF), optical splitter (also known as splitter), and combiner. In addition, the aforementioned OLT can be connected to the operator network through a network side interface, and the OLT can be connected to the ODN through a dedicated interface, and the ODN is connected to the ONU (or ONT) through a dedicated interface. In the downstream direction, the OLT broadcasts the downstream optical signal, and the downstream optical signal is distributed to each ONU (or ONT) through the ODN. In the upstream direction, a time division multiple access (TDMA) method is adopted, and each ONU (or ONT) sends an upstream optical signal in its respective upstream time slot allocated by the OLT.

[0107] As shown in Figure 1B, a structural diagram of the optical fiber network system provided by the present application is shown. 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, all of the multiple sub-devices 02 may 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 include 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.

[0108] 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. For example, 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 in the user's home. The terminal device 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 is another network (such as Ethernet, etc.) between the sub-device and the terminal device in the user's home. The sub-device is an optical modem provided by the operator, and the optical modem is then connected to devices such as indoor routers. This application is introduced by taking the main device and the slave device as an example.

[0109] The following describes the main process of the access method provided by this application in conjunction with Figure 2:

[0110] As shown in Figure 2, a flow chart of the access method provided by this application is shown. In this figure, the master device and the first sub-device will perform the following steps:

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

[0112] 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, 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 allocated time slot.

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

[0114] Among them, an unactivated sub-device can be a sub-device that has not entered the activation process, 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 master 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 the activation procedure. Optionally, the unactivated sub-device can be a sub-device in the serial number acquisition state (Serial_Number state) (i.e., O3 state).

[0115] In addition, the allocation information can be an allocation structure that specifies an allocation interval for a specific bandwidth allocation to the receiving sub-device. The specific bandwidth allocation refers to the upstream bandwidth allocation used by the sub-device in a specific state. The upstream bandwidth allocation is an uplink transmission opportunity granted by the master device to a specified traffic bearer entity (e.g., a transmission container (T-CONT) entity or an uplink management control channel) within the sub-device within a specified time interval (i.e., an allocation interval).

[0116] 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 carrying 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 (that is, the allocation structure containing the allocation identifier) ​​is used when an unactivated sub-device is found, that is, the allocation structure is used for the sub-device to use in the activation process. For example, the allocation structure is assigned by the master device to the sub-device to respond to and report information (for example, a serial number) in the activation process.

[0117] The first allocation information in this 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).

[0118] 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, as a serial number request allocation structure, is used to trigger a sub-device that supports the first uplink rate and executes an activation procedure (for example, a sub-device that supports the first uplink rate and is in a serial number acquisition 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.

[0119] Alternatively, the first allocation information may be included in a broadcast serial number request message, which requests the allocation of broadcast bandwidth to all inactive sub-devices in the serial number acquisition state (Serial_Number state). For example, a master device broadcasts a serial number request message including 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.

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

[0121] As shown in Figure 3, it is an example diagram of a downlink frame carrying the first allocation structure involved in this application. Figure 3 takes the downlink G-PON transmission convergence (GTC) frame (Downstream GTC frame) as an example. 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., 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 physical layer operations administration and maintenance downstream (PLOAMd) field (13 bytes), a bit interleaved parity (BIP) field (1 byte), a payload length (Plend) field (4 bytes) and an upstream bandwidth map (USBWmap) field (N*8 bytes). The BWmap field includes multiple allocation structures. The aforementioned first allocation structure can 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 of which includes an allocation identifier, and a first allocation structure includes a first allocation identifier.

[0122] In this step, after receiving 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 it supports the specific uplink rate corresponding to the first allocation identifier (i.e., the first uplink rate), 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.

[0123] 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 master device receives the first response message.

[0124] In this embodiment, step 202a is an optional step.

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

[0126] The first sub-device supports the first uplink rate, which means that the first sub-device can send uplink optical signals using the first uplink rate, and the uplink optical signals from the first sub-device received by the main device use the first uplink rate.

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

[0128] Exemplarily, after receiving 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 (e.g., the pre-allocated delay indicated in the upstream frame header (Upstream_Overhead)) to the start time in the first time information, and sends a sequence number response message, where the sequence number response message includes the sequence number of the first sub-device.

[0129] 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 the serial number collection state and performs the activation process at the first uplink rate can use the first allocation 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.

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

[0131] In this embodiment, step 202b is an optional step.

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

[0133] 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. If the first sub-device does not support the first uplink rate, the first sub-device does not respond.

[0134] 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 first sub-device's serial number in the first allocated time slot only if the first sub-device determines that it supports the first uplink rate. In other words, 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 allocated time slot, and will not trigger sub-devices of other uplink rates (at uplink rates other than the first uplink rate) to report the serial number in the first allocated time slot. This helps avoid the first sub-device and sub-devices supporting other uplink rates sharing the allocated time slot to report the serial number, that is, helps avoid the main device receiving optical signals of two uplink rates in a relatively short period of time, thereby helping to reduce the implementation complexity of uplink burst reception.

[0135] Furthermore, as shown in FIG4 , when there are sub-devices supporting different uplink 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:

[0136] Step 401: The master device sends first allocation information; accordingly, the first slave device receives the first allocation information; and the second device receives the first allocation information.

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

[0138] In addition, both the first sub-device and the second sub-device are inactive 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 description, the following description uses the example where the first sub-device supports the second uplink rate and the second sub-device supports the first uplink rate. The first uplink rate is different from the second uplink rate.

[0139] For example, the master device broadcasts the first allocation information, and both the first and second sub-devices receive the first allocation information. After the first sub-device receives the first allocation information, it executes step 402; after the second sub-device receives the first allocation information, it executes step 403. It should be understood that there is no time sequence restriction between steps 402 and 403; step 402 can be executed after step 401, and step 403 can be executed after step 401.

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

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

[0142] Step 403: The second sub-device sends a second response message in the first allocated time slot; accordingly, the master device receives the second response message.

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

[0144] Step 404 and step 405 are optional steps.

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

[0146] The second allocation information includes a second allocation identifier and second time information, wherein the second time information is used to indicate a second allocated 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 allocated time slot.

[0147] The second identification information is used to indicate that an unactivated sub-device supporting the second uplink rate responds 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 supporting 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 allocated time slot indicated by the first time information is different from the second allocated time slot indicated by the second time information. The first allocation information and the second allocation information are issued through different bandwidth mappings (BWmaps).

[0148] It can be understood that the second allocation information provided in this application is used to discover inactivated sub-devices that support another specific uplink rate (e.g., the second uplink rate), and is not only used to discover inactivated sub-devices, nor is it used to discover inactivated sub-devices that support other uplink rates. For example, when multiple sub-devices receive the second allocation information, only the inactivated sub-devices that support the second uplink rate can respond to the second allocation information.

[0149] 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, as a serial number request allocation structure, is used to trigger a sub-device that supports the second uplink rate and executes an activation procedure (for example, a sub-device that supports the second uplink rate and is in a serial number acquisition state (Serial_Number state) (i.e., O3 state)) to report the serial number of the sub-device in response to the second allocation information.

[0150] Alternatively, the second allocation information may be included in a broadcast serial number request message, which requests the allocation of broadcast bandwidth to all inactive sub-devices in the serial number acquisition state (Serial_Number state). For example, a master device broadcasts a serial number request message including the second allocation structure. One or more inactive sub-devices connected to the master device can receive the serial number request message and obtain the second allocation information. However, only sub-devices that support the second uplink rate can respond to the first allocation information.

[0151] 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 an introduction to the frame header of the downstream GTC frame, please refer to the corresponding introduction in Figure 3 above, which will not be repeated here. The first allocation information and the second allocation information are carried and issued in different bandwidth map (BWmap) fields.

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

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

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

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

[0156] In this embodiment, the master device can distinguish the allocation structures corresponding to sub-devices supporting different uplink rates through different allocation identifiers, and further distinguish the allocation time slots corresponding to different allocation structures for reporting serial numbers. That is, the first allocation identifier indicates that the first allocation structure is used to discover inactivated sub-devices 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 inactivated sub-devices supporting the second uplink rate, and the second allocation structure corresponds to the second allocation time slot. Therefore, sub-devices supporting different uplink rates use different allocation time slots when reporting serial numbers. Compared with the use of different time slots in the same allocation time slot in traditional technologies, the time interval between the uplink optical signals of different uplink rates received by the master network device is lengthened, which helps to reduce the complexity of the receiver for uplink burst reception.

[0157] Furthermore, it should be noted that, of the aforementioned first and second allocation identifiers, one of the allocation identifiers can retain the value of the allocation identifier used in the activation process in conventional technology, while the other allocation identifier can be a newly defined allocation identifier. For ease of explanation, the following example uses the case where the first allocation identifier retains the value of the allocation identifier used in the activation process in conventional technology, and the second allocation identifier is a newly defined allocation identifier.

[0158] In one 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.24416Gbit / 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.48832Gbit / 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-device in the system responds to the first allocation structure by sending the serial number of the 1.25G sub-device, and the 2.5G sub-device in the system does not respond to the first 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:

[0159] 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 inactivated sub-device supporting an uplink rate of 2.48832 Gbit / s (ie, a 2.5G sub-device).

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

[0161] Table 1-1

[0162] As shown in Table 1-1, Alloc-IDs 0 to 253 are the default allocation identifiers (i.e., the default Alloc-IDs). These default allocation identifiers are implicitly assigned using the slave device's identifier (i.e., the SFU-ID, used in PLOAM messages) and do not require an explicit Assign_Alloc-ID PLOAM message. The default Alloc-ID is used to carry PLOAM and FMCC traffic for uplink frames, and may also carry user data traffic. Furthermore, the Assign_Alloc-ID PLOAM message cannot be used to cancel or change the default Alloc-ID. If a slave device requires more Alloc-ID values, the master device allocates them from Alloc-IDs above 255.

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

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

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

[0166] In this implementation, for sub-devices supporting 2.48832 Gbit / s, Alloc-ID=254 is redefined as a reserved allocation identifier, meaning Alloc-ID=254 is not included in the allocation structure. Furthermore, Alloc-ID=255 is redefined as a broadcast allocation identifier. Sub-devices supporting an uplink rate of 1.24416 Gbit / s use Alloc-ID=254 during the activation process. Therefore, during the activation process, 2.5G sub-devices use the allocation structure and allocation timeslots corresponding to Alloc-ID=255, while 1.25G sub-devices use the allocation structure and allocation timeslots corresponding to Alloc-ID=254. Therefore, sub-devices supporting different uplink rates use different allocation timeslots when reporting sequence numbers, enabling multi-rate independent windowing and reducing the implementation complexity of uplink burst reception.

[0167] 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 inactivated sub-device supporting an uplink rate of 2.48832 Gbit / s (ie, a 2.5G sub-device).

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

[0169] Table 1-2

[0170] As shown in Table 1-2, Alloc-IDs from 0 to 252 are the default allocation identifiers (i.e., the default Alloc-IDs). These default allocation identifiers are implicitly assigned using the slave device's identifier (i.e., the SFU-ID, used in PLOAM messages) and do not require an explicit Assign_Alloc-ID PLOAM message. The default Alloc-ID is used to carry PLOAM and FMCC traffic for uplink frames, and may also carry user data traffic. Furthermore, the Assign_Alloc-ID PLOAM message cannot be used to cancel or change the default Alloc-ID. If a slave device requires more Alloc-ID values, the master device allocates them from Alloc-IDs above 255.

[0171] In addition, Alloc-ID=253 is a newly defined broadcast allocation identifier. It can be understood that Alloc-ID=253 is the Alloc-ID used by sub-devices supporting 2.48832 Gbit / s in the activation process to discover unknown (or unactivated) sub-devices. For example, Alloc-ID=253 is used in a serial number request allocation structure, that is, the allocation structure corresponding to Alloc-ID=253 is a serial number request allocation structure. The allocation structure corresponding to 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.48832 Gbit / 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 Alloc-ID=253 to report the serial number of the sub-device.

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

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

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

[0175] In this implementation, for sub-devices supporting 2.48832 Gbit / s, Alloc-ID=254 is redefined as a reserved allocation identifier, meaning Alloc-ID=254 is not included in the allocation structure. Furthermore, Alloc-ID=253 is redefined as a broadcast allocation identifier. Sub-devices supporting an uplink rate of 1.24416 Gbit / s use Alloc-ID=254 during the activation process. Therefore, during the activation process, 2.5G sub-devices use the allocation structure and allocation timeslots corresponding to Alloc-ID=253, while 1.25G sub-devices use the allocation structure and allocation timeslots corresponding to Alloc-ID=254. Therefore, sub-devices supporting different uplink rates use different allocation timeslots when reporting sequence numbers, enabling multi-rate independent windowing and reducing the implementation complexity of uplink burst reception.

[0176] 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 capabilities of the ONU, for example, the OLT sets the FEC code used by the ONU upstream. For example, the OLT can send a capability acquisition (setting) message to the ONU, which is used to query the capabilities supported by the ONU or set a specific capability for the ONU. A separate capability acquisition (setting) message can set a capability supported by the ONU. The capabilities supported by the ONU (also referred to as characteristics or functions) can be carried by specific fields. For example, the characteristics supported by the ONU are carried by the "Set Characteristics Identifier" field.

[0177] The Get_Set_Capabilities message provided in the embodiment of the present application may carry multiple pieces of information. The Get_Set_Capabilities message may be specifically as shown in Table 1 below:

[0178] Table 1 - Get_Set_Capabilities message

[0179] Table 1 - Get_Set_Capabilities message

[0180] 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 coding), the FEC coding 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).

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

[0182] Correspondingly, after the OLT sends the Get_Set_Capabilities message, the ONU can respond with a capability message to the OLT, 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:

[0183] Table 2 – ONU_Capabilities message

[0184] Table 2 – ONU_Capabilities message

[0185] Table 2 – ONU_Capabilities message

[0186] 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 it supports in the eighth byte.

[0187] In the access method provided in this embodiment, the ONU capabilities (ONU_Capabilities) message includes the following functions:

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

[0189] 2) The ONU_Capabilities message can also respond to a Get_Set_Capability PLOAM message carrying a set operation code, indicating whether the ONU wishes to set the capability or cannot set the capability, and a response code. The operation code and response code carry the reason why the ONU wishes to set the capability or cannot set the capability. For specific values, refer to the table above.

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

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

[0192] The above function 3 is implemented when the ONU completes an attempt to execute the setting command transmitted by the Get_Set_Capability PLOAM message.

[0193] In addition, an embodiment of the present application further provides a communication device 50, as shown in Figure 5, which is a structural diagram 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 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 SFU.

[0194] 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 be a single processor or may include multiple processors, which is not specifically limited here.

[0195] 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 transmitting function in the transceiver unit may be regarded as a transmitting unit, that is, the transceiver unit includes a receiving unit and a transmitting unit. The receiving unit may also be referred to as a receiver, an input port, a receiving circuit, etc., and the transmitting 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 Figure 2 or Figure 3, the transceiver 502 may be used to receive uplink burst optical signals. Optionally, the transceiver 502 supports reception of burst optical signals of one or more uplink rates. For example, the transceiver 502 supports reception of uplink burst optical signals of 2.48832Gbit / s. For another example, the transceiver 502 supports reception of uplink burst optical signals of 1.24416Gbit / s.

[0196] 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 may exist independently and be connected to the processor 501. Optionally, the memory 503 may be integrated with the processor 501, for example, integrated into one or more chips. The memory 503 can store program codes for executing the technical solutions of the embodiments of the present application, and is controlled by the processor 501 for execution. The various types of computer program codes executed can also be regarded as drivers for the processor 501. The memory 503 may include volatile memory, such as random-access memory (RAM); the memory may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD) or solid-state drive (SSD); the memory 503 may also include a combination of the above types of memory. The memory 503 may refer to a single memory or may include multiple memories. Exemplarily, the memory 503 is used to store various data.

[0197] In one implementation, the communication device 50 is configured to implement the functionality of a first sub-device in a fiber optic network system. Specifically, a transceiver 502 is configured to receive first allocation information from a master device, the first allocation information including a first allocation identifier and first time information, the first time information indicating a first allocated timeslot, and the first allocation identifier indicating an inactive sub-device supporting a first uplink rate to respond to the first allocation information. Upon determining that the first uplink rate is supported, the processor 501 is configured to control the transceiver 502 to send a first response information in the first allocated timeslot, the first response information including the serial number of the first sub-device.

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

[0199] In one possible implementation, the first sub-device supports a second uplink rate, which is different from the first uplink rate. The transceiver 502 is further configured to receive second allocation information from the master device, the second allocation information including a second allocation identifier and second time information, the second time information being used to indicate a second allocated time slot, the second allocation identifier being used to indicate that an inactivated sub-device supporting the second uplink rate responds to the second allocation information, the second allocation identifier being different from the first allocation identifier, and the second time information being different from the first time information. The processor 501 is further configured to, upon determining that the first sub-device supports the second uplink rate, control the transceiver 502 to send a first response message in the second allocated time slot, the first response message including the serial number of the first sub-device.

[0200] In a possible implementation, the multiple sub-devices further include an unactivated second sub-device, the second sub-device supports the 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 the serial number of the second sub-device.

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

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

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

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

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

[0206] In another implementation, the communication device 50 is configured to implement the functions of a master device in a fiber optic network system. Specifically, the processor 501 is configured to generate first allocation information; the transceiver 502 is configured to send the first allocation information, which includes a first allocation identifier and first time information. The first time information indicates a first allocated time slot, and the first allocation identifier indicates that an inactive sub-device supporting a first uplink rate should respond to the first allocation information. If the first sub-device supports the first uplink rate, the first allocation information is used by the first sub-device to send a first response message in the first allocated time slot. The first response message includes the serial number of the first sub-device.

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

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

[0209] The transceiver 502 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 by 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.

[0210] In a possible implementation, the multiple sub-devices further include an unactivated second sub-device, the second sub-device supports the 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 the serial number of the second sub-device.

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

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

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

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

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

[0216] For details, please refer to the relevant descriptions in the corresponding embodiments of Figures 2 and 4 above, which will not be repeated here.

[0217] 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 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 another communication module for implementing the method in the method embodiment of the present application.

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

[0219] In one possible design, one or more modules in FIG6 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 this embodiment of the present application. The processors, memories, and transceivers may be provided separately or integrated.

[0220] The communication device 60 has the function of implementing the sub-device (for example, the first sub-device) described in the embodiment of the present application. For example, the communication device 60 includes a sub-device (for example, the first sub-device) that performs the module or unit or means corresponding to the steps involved in the sub-device (for example, the first sub-device) described in the embodiment of the present application. 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.

[0221] 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 (means) corresponding to the main device step described in the embodiment of the present application for the main device to execute. The function or unit or means (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.

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

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

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

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

[0226] 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, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. An access method, applied to an optical fiber network system, wherein the optical fiber network system comprises a main device and a plurality of sub-devices, characterized in that: include: 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.

2. The method according to claim 1, characterized in that Also includes: 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.

3. The method according to claim 2, characterized in that 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 performs FEC encoding on the uplink data stream according to the timestamp.

4. The method according to claim 3, characterized in that The second capability acquisition setting information also includes an FEC code identifier.

5. The method according to claim 3, characterized in that The uplink FEC code of the first sub-device includes one or more of a default FEC code, a high margin code, and a high throughput code.

6. The method according to claim 5, characterized in that 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 shortened columns of the LDPC code.

7. The method according to claim 2, 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.

8. The method according to claim 7, characterized in that The capability setting message also carries a response code, where the response code is used to identify the reason why the first sub-device did not arrange the capability setting.

9. The method according to any one of claims 1 to 8, characterized in that: The capability information of the first sub-device includes FEC codewords supported by the first sub-device.

10. An access method, applied to an optical fiber network system, the optical fiber network system comprising a main device and a plurality of sub-devices, characterized in that: include: 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.

11. The method according to claim 10, characterized in that Also includes: 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.

12. The method according to claim 10, characterized in that Also includes: The main device stores the capability information of the first sub-device.

13. The method according to claim 10 or 11, 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 according to the integrity key between the main device and the first sub-device.

14. The method according to any one of claims 10 to 13, characterized in that The second capability acquisition setting information also includes an FEC code identifier.

15. The method according to any one of claims 10 to 14, 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.

16. A communication device, characterized in that: include: 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 any one of claims 10 to 15.

Images