An uplink overhead configuration method, a fiber network system, and related devices
By introducing a dedicated uplink overhead configuration method in the fiber optic network system, and using reserved fields to carry indication information, uplink burst overhead parameters are configured separately for sub-devices with specific uplink rates. This solves the problem of low efficiency caused by configuring the same parameters for sub-devices with different uplink rates in the traditional method, and achieves efficient uplink burst configuration and system compatibility.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- HUAWEI TECH CO LTD
- Filing Date
- 2023-10-10
- Publication Date
- 2026-05-08
AI Technical Summary
In traditional fiber optic network systems, sub-devices supporting different uplink speeds are inefficient when configuring uplink burst overhead parameters, resulting in sub-devices with different uplink speeds using the same parameters, which affects uplink burst efficiency.
By introducing a dedicated uplink overhead configuration method in the fiber optic network system, and using reserved fields to carry indication information, uplink burst overhead parameters can be configured separately for sub-devices that support specific uplink rates, thus avoiding configuring the same parameters for other sub-devices with different uplink rates.
It improves uplink burst efficiency, saves signaling overhead, enhances system compatibility, and ensures efficient configuration of sub-devices with different uplink rates.
Smart Images

Figure CN120498994B_ABST
Abstract
Description
[0001] This application is a divisional application. The original application has the application number 202311319468.2 and the original application date is October 10, 2023. The entire contents of the original application are incorporated herein by reference. Technical Field
[0002] This application relates to the field of optical communication, and more particularly to an uplink overhead configuration method, an optical fiber network system, and related equipment. Background Technology
[0003] Fiber to the room (FTTR) refers to the technology of using optical fiber instead of network cables to provide fiber optic media access to a room via an optical network terminal (ONT). In this FTTR scenario, the fiber optic network system includes a master device and one or more sub-devices. The master device can trigger the activation process of the sub-devices after they come online and configure the upstream overhead parameters for each sub-device.
[0004] In the traditional configuration process, the master device broadcasts an Upstream_Overhead message. Each sub-device in the fiber optic network system that receives the Upstream_Overhead message configures its Upstream_Overhead parameters based on the content carried in the message.
[0005] However, this fiber optic network system may contain sub-devices supporting different uplink rates, and these sub-devices may have different uplink overhead requirements. Therefore, the traditional configuration process leads to all sub-devices supporting different uplink rates using the same uplink burst overhead parameters, which may affect the efficiency of uplink bursts. Summary of the Invention
[0006] This application provides an uplink overhead configuration method, an optical fiber network system, and related equipment, which are used to configure uplink overhead individually for sub-devices that support specific uplink rates, thereby improving the efficiency of uplink bursts.
[0007] Firstly, this application provides an uplink overhead configuration method applied to an optical fiber network system, which includes a master device and multiple sub-devices, including a first sub-device. The uplink overhead configuration method provided in this aspect can be executed by the first sub-device in the optical fiber network system, or by a portion of a functional module or chip within the first sub-device. Taking execution by the first sub-device as an example, the first sub-device receives a first message, which includes first indication information. The first indication information indicates that the first message is applicable to configuring uplink burst overhead parameters for sub-devices supporting a first uplink rate. If the first sub-device supports the first uplink rate, then the first sub-device configures its own uplink burst overhead parameters based on the first message.
[0008] Optionally, if the first sub-device does not support the first uplink rate, then the first sub-device does not perform a configuration operation based on the first message.
[0009] In this application, the first message received by the first sub-device includes first indication information, which indicates that the first message is applicable to configuring uplink burst overhead parameters for sub-devices supporting the first uplink rate. The first sub-device only triggers the configuration of its uplink burst overhead parameters based on the first message if it determines that it supports the first uplink rate. In other words, the first configuration message received by the first sub-device only triggers sub-devices supporting the first uplink rate to configure uplink burst overhead parameters based on the first message; it does not trigger sub-devices with other uplink rates (i.e., uplink rates other than the first uplink rate) to configure uplink burst overhead parameters based on the first message. This facilitates the individual configuration of uplink overhead for sub-devices with specific uplink rates, thereby improving the efficiency of uplink bursts.
[0010] In one possible implementation, the first sub-device supports a second uplink rate, which is different from the first uplink rate. The method further includes: the first sub-device receiving a second message, the second message including second indication information, the second indication information indicating that the second message is applicable to configuring uplink burst overhead parameters for sub-devices supporting the second uplink rate; and the first sub-device configuring its uplink burst overhead parameters based on the second message.
[0011] In this embodiment, if the first sub-device does not complete the uplink burst overhead parameter configuration based on the first message, it may also receive a second message. This second message is applicable to sub-devices supporting the second uplink rate configuring uplink burst overhead parameters. If the first sub-device supports the second uplink rate, it can trigger the configuration of uplink burst overhead parameters based on the second message.
[0012] In one possible implementation, the plurality of sub-devices further includes a second sub-device that supports a first uplink rate, and a first message is used for the second sub-device to configure uplink burst overhead parameters of the second sub-device.
[0013] In one possible implementation, the first indication information is carried in a reserved field of the uplink burst overhead message.
[0014] Optionally, the reserved field is located in the 10th byte of the uplink burst overhead message. For example, the first indication information is represented by one reserved bit in the 10th byte; or, the first indication information is represented by two reserved bits in the 10th byte.
[0015] In one example, the first indication information is represented by a single reserved bit. For instance, one value (e.g., the aforementioned 1 bit being "1") indicates that the first uplink rate is 2.5G, meaning the first indication information indicates that the first message is applicable to configuring uplink burst overhead parameters for sub-devices supporting 2.5G uplink rates. Another value (e.g., the aforementioned 1 bit being "0") indicates that the first uplink rate is any uplink rate, meaning the first indication information indicates that the first message is applicable to configuring uplink burst overhead parameters for sub-devices with any uplink rate. In this example, the first indication information is implemented using 1 bit, which can represent either a 2.5G uplink rate or any uplink rate. This not only enables separate configuration of uplink burst overhead parameters for sub-devices supporting 2.5G uplink rates to improve the burst efficiency of these sub-devices, but also allows configuration of sub-devices with any uplink rate through a single message, thus saving signaling overhead for configuring uplink burst overhead parameters. In addition, setting a value to indicate that the first uplink rate is arbitrary is beneficial to improving system compatibility and avoiding the impact on the configuration of the sub-device when the system introduces sub-devices that support other uplink rates (e.g., sub-devices that support 2.5G and 1.25G).
[0016] In another example, the first indication information is represented by a reserved bit. For example, one value (e.g., the aforementioned bit being "1") indicates that the first uplink rate is 2.5G, meaning the first indication information indicates that the first message is applicable to configuring uplink burst overhead parameters for sub-devices supporting 2.5G uplink rates; another value (e.g., the aforementioned bit being "0") indicates that the first uplink rate is both 1.25G and 2.5G, meaning the first indication information indicates that the first message is applicable to configuring uplink burst overhead parameters for sub-devices supporting both 1.25G and 2.5G uplink rates. In this example, not only is it possible to configure uplink burst overhead parameters separately for sub-devices supporting 2.5G uplink rates to improve the burst efficiency of sub-devices supporting 2.5G uplink rates, but it is also possible to configure both 1.25G and 2.5G uplink rate sub-devices simultaneously with a single message, thereby saving signaling overhead for configuring uplink burst overhead parameters.
[0017] In another example, the first indication information is represented by a single reserved bit. One value (e.g., the aforementioned 1 bit being "1") indicates that the first uplink rate is 2.5G, meaning the first indication information indicates that the first message is applicable to configuring uplink burst overhead parameters for sub-devices supporting 2.5G uplink rates. Another value (e.g., the aforementioned 1 bit being "0") indicates that the first uplink rate is 1.25G, meaning the first indication information indicates that the first message is applicable to configuring uplink burst overhead parameters for sub-devices supporting 1.25G uplink rates. In this example, the first indication information is implemented using 1 bit, which allows for configuring uplink burst overhead parameters for both 2.5G and 1.25G uplink rate sub-devices, thus improving the burst efficiency of sub-devices at various rates in the system.
[0018] In another example, the first indication information is represented by two reserved bits. For example, one value (e.g., the aforementioned two bits being "00") indicates that the first uplink rate is any uplink rate, that is, the first indication information indicates that the first message is applicable to sub-devices configuring uplink burst overhead parameters for any uplink rate; another value (e.g., the aforementioned two bits being "01") indicates that the first uplink rate is 2.5G, that is, the first indication information indicates that the first message is applicable to sub-devices configuring uplink burst overhead parameters for supporting 2.5G uplink rates; another value (e.g., the aforementioned two bits being "10") indicates that the first uplink rate is 1.25G, that is, the first indication information indicates that the first message is applicable to sub-devices configuring uplink burst overhead parameters for supporting 1.25G uplink rates. In this example, the first indication information is implemented using 2 bits. This not only allows for the configuration of uplink burst overhead parameters for sub-devices with 2.5G uplink speeds and those with 1.25G uplink speeds, respectively, thereby improving the burst efficiency of sub-devices at various speeds in the system, but also enables the configuration of sub-devices with any uplink speed through a single message, saving signaling overhead for configuring uplink burst overhead parameters. Furthermore, setting a value to indicate that the first uplink speed is arbitrary improves system compatibility and prevents the introduction of sub-devices supporting other uplink speeds (e.g., sub-devices supporting speeds other than 2.5G and 1.25G) from affecting the configuration of those sub-devices.
[0019] In one possible implementation, the first message includes a message type field, which carries first indication information. Alternatively, the first indication information can be understood as being carried in the message type field of the uplink burst overhead message.
[0020] Optionally, the message type field is located in the second byte of the uplink burst overhead message.
[0021] In this embodiment, a new message type is added, specifically for configuring uplink burst overhead parameters for sub-devices supporting the first uplink rate. This enables individual configuration of uplink burst overhead parameters for sub-devices supporting the first uplink rate, thereby improving the burst efficiency of these sub-devices. Furthermore, the traditional uplink burst overhead message is retained, allowing configuration of sub-devices with any uplink rate (i.e., 2.5G uplink rate and 1.25G uplink rate sub-devices) using a single message, which helps save on signaling overhead for configuring uplink burst overhead parameters.
[0022] In one possible implementation, the method further includes: a first sub-device receiving a third message, the third message including third indication information, the third indication information being used to indicate that the third message is applicable to sub-devices supporting a first uplink rate to configure extended burst overhead parameters; if the first sub-device supports the first uplink rate, the first sub-device configures extended burst overhead parameters of the first sub-device based on the third message.
[0023] Optionally, if the first sub-device does not support the first uplink rate, then the first sub-device does not perform configuration operations based on the third message.
[0024] In one possible implementation, the third indication information is carried in a reserved field of the burst overhead length message.
[0025] Optionally, the reserved field can be located in any one of the 5th to 12th bytes of the burst overhead length message. For example, the third indication information can be represented by one reserved bit in the 5th byte; or, the third indication information can be represented by two reserved bits in the 5th byte.
[0026] In one example, the third indication information is represented by a single reserved bit. For instance, one value (e.g., the aforementioned 1 bit being "1") indicates that the first uplink rate is 2.5G, meaning the third indication information indicates that the third message is applicable to configuring extended burst overhead parameters for sub-devices supporting 2.5G uplink rates. Another value (e.g., the aforementioned 1 bit being "0") indicates that the first uplink rate is any uplink rate, meaning the third indication information indicates that the third message is applicable to configuring extended burst overhead parameters for sub-devices with any uplink rate. In this example, the third indication information is implemented using 1 bit, which can represent either a 2.5G uplink rate or any uplink rate. This not only enables separate configuration of extended burst overhead parameters for sub-devices supporting 2.5G uplink rates to improve the burst efficiency of these sub-devices, but also allows configuration of sub-devices with any uplink rate through a single message, thus saving signaling overhead for configuring extended burst overhead parameters. In addition, setting a value to indicate that the first uplink rate is arbitrary is beneficial to improving system compatibility and avoiding the impact on the configuration of the sub-device when the system introduces sub-devices that support other uplink rates (e.g., sub-devices that support 2.5G and 1.25G).
[0027] In another example, the third indication information is represented by a reserved bit. For example, one value (e.g., the aforementioned bit "1") indicates that the first uplink rate is 2.5G, meaning the third indication information indicates that the third message is applicable to configuring extended burst overhead parameters for sub-devices supporting 2.5G uplink rates; another value (e.g., the aforementioned bit "0") indicates that the first uplink rate is 1.25G and 2.5G, meaning the third indication information indicates that the third message is applicable to configuring extended burst overhead parameters for sub-devices supporting both 1.25G and 2.5G uplink rates. In this example, not only is the extended burst overhead parameter configuration implemented separately for sub-devices supporting 2.5G uplink rates to improve the burst efficiency of sub-devices supporting 2.5G uplink rates, but it also enables simultaneous configuration of sub-devices supporting 1.25G and 2.5G uplink rates with a single message, thereby saving signaling overhead for configuring extended burst overhead parameters.
[0028] In another example, the third indication information is represented by a single reserved bit. One value (e.g., the aforementioned 1 bit being "1") indicates that the first uplink rate is 2.5G, meaning the third indication information indicates that the third message is applicable to configuring extended burst overhead parameters for sub-devices supporting 2.5G uplink rates. Another value (e.g., the aforementioned 1 bit being "0") indicates that the first uplink rate is 1.25G, meaning the third indication information indicates that the third message is applicable to configuring extended burst overhead parameters for sub-devices supporting 1.25G uplink rates. In this example, the third indication information is implemented using 1 bit, which allows for configuring extended burst overhead parameters for both 2.5G and 1.25G uplink rate sub-devices, thus improving the burst efficiency of sub-devices at various rates in the system.
[0029] In another example, the third indication information is represented by two reserved bits. For example, one value (e.g., the aforementioned two bits being "00") indicates that the first uplink rate is any uplink rate, meaning the third indication information indicates that the third message is applicable to the burst overhead parameters of the sub-device configuration extension for any uplink rate; another value (e.g., the aforementioned two bits being "01") indicates that the first uplink rate is 2.5G, meaning the third indication information indicates that the third message is applicable to the burst overhead parameters of the sub-device configuration extension supporting 2.5G uplink rate; yet another value (e.g., the aforementioned two bits being "10") indicates that the first uplink rate is 1.25G, meaning the third indication information indicates that the third message is applicable to the burst overhead parameters of the sub-device configuration extension supporting 1.25G uplink rate. In this example, the third indication information is implemented using 2 bits. This not only allows for the configuration of extended burst overhead parameters for sub-devices with 2.5G uplink speeds and those with 1.25G uplink speeds, respectively, thereby improving the burst efficiency of sub-devices at various speeds in the system, but also enables the configuration of sub-devices with any uplink speed through a single message, saving signaling overhead for configuring extended burst overhead parameters. Furthermore, setting a value to indicate that the first uplink speed is arbitrary improves system compatibility and prevents the introduction of sub-devices supporting other uplink speeds (e.g., sub-devices supporting speeds other than 2.5G and 1.25G) from affecting the configuration of those sub-devices.
[0030] In one possible implementation, the third message includes a message type field, which is used to carry third indication information.
[0031] Optionally, the message type field is located in the second byte of the extended burst length message.
[0032] In this embodiment, an extended burst length message is added as a new message type. This message is specifically used to configure extended burst overhead parameters for sub-devices supporting the first uplink rate. This allows for individual configuration of extended burst overhead parameters for sub-devices supporting the first uplink rate, thereby improving the burst efficiency of these sub-devices. Furthermore, the traditional extended burst length message is retained, allowing configuration of sub-devices with any uplink rate (i.e., 2.5G uplink rate sub-devices and 1.25G uplink rate sub-devices) using a single traditional extended burst overhead message. This helps save on signaling overhead associated with configuring extended burst overhead parameters.
[0033] In one possible implementation, the first uplink rate includes 2.5G and / or 1.25G.
[0034] In one possible implementation, the uplink burst overhead parameters include at least one of the following: guard time overhead, preamble overhead, separator overhead, pre-allocation delay, and transmitted optical power.
[0035] In one possible implementation, the extended burst overhead parameter is used to indicate the number of type 3 preamble bytes used in the uplink direction.
[0036] Secondly, this application provides an uplink overhead configuration method applied to an optical fiber network system, which includes a master device and multiple sub-devices, including a first sub-device. The uplink overhead configuration method provided in this aspect can be executed by the master device in the optical fiber network system, or by a portion of a functional module or chip within the master device. Taking execution by the master device as an example, the master device sends a first message, which includes first indication information. The first indication information is used to indicate that the first message is applicable to configuring uplink burst overhead parameters for a sub-device supporting a first uplink rate; wherein, if the first sub-device supports the first uplink rate, the first message is used to configure the uplink burst overhead parameters for the first sub-device.
[0037] Optionally, if the first sub-device does not support the first uplink rate, the first message is used for the first sub-device not to perform configuration operations based on the first message.
[0038] In this application, the first message sent by the master device includes first indication information, which instructs the first message to be applicable to configuring uplink burst overhead parameters for sub-devices supporting the first uplink rate. Only sub-devices supporting the first uplink rate will trigger the configuration of uplink burst overhead parameters based on the first message; other sub-devices supporting uplink rates (i.e., uplink rates other than the first uplink rate) will not be triggered to configure uplink burst overhead parameters based on the first message. Therefore, this facilitates the individual configuration of uplink overhead for sub-devices with specific uplink rates, thereby improving the efficiency of uplink bursts.
[0039] In one possible implementation, the first sub-device supports a second uplink rate, which is different from the first uplink rate. The method further includes: the master device sending a second message, the second message including second indication information, the second indication information being used to indicate that the second message is applicable to configuring uplink burst overhead parameters for a sub-device supporting the second uplink rate, and the second message being used by the first sub-device to configure the uplink burst overhead parameters of the first sub-device.
[0040] In one possible implementation, the plurality of sub-devices further includes a second sub-device that supports a first uplink rate, and a first message is used for the second sub-device to configure uplink burst overhead parameters of the second sub-device.
[0041] In one possible implementation, the first indication information is carried in a reserved field of the uplink burst overhead message.
[0042] In one possible implementation, the first message includes a message type field, which is used to carry first indication information.
[0043] In one possible implementation, the method further includes: the master device sending a third message, the third message including third indication information, the third indication information being used to indicate that the third message is applicable to configuring extended burst overhead parameters for a sub-device supporting the first uplink rate; wherein, if the first sub-device supports the first uplink rate, the third message is used for the first sub-device to configure extended burst overhead parameters for the first sub-device.
[0044] In one possible implementation, if the first sub-device does not support the first uplink rate, the third message is used for the first sub-device not to perform configuration operations based on the third message.
[0045] In one possible implementation, the third indication information is carried in a reserved field of the burst overhead length message.
[0046] In one possible implementation, the third message includes a message type field, which is used to carry third indication information.
[0047] In one possible implementation, the first uplink rate includes 2.5G and / or 1.25G.
[0048] In one possible implementation, the uplink burst overhead parameters include at least one of the following:
[0049] Protection time overhead, preamble overhead, separator overhead, pre-allocated delay, and transmitted optical power.
[0050] In one possible implementation, the extended burst overhead parameter is used to indicate the number of type 3 preamble bytes used in the uplink direction.
[0051] It should be noted that there are many other specific implementation methods in this application, and the specific implementation methods and their beneficial effects in the first aspect can be found therein, which will not be repeated here.
[0052] Thirdly, this application provides a communication device applied to an optical fiber network system, the optical fiber network system including a main device and multiple sub-devices, the multiple sub-devices including a first sub-device. The communication device can be the first sub-device in the optical fiber network system, or it can be a functional module or chip within the first sub-device. The communication device includes a transceiver and a processor.
[0053] The transceiver is used to receive a first message, which includes first indication information. The first indication information is used to indicate that the first message is applicable to configuring uplink burst overhead parameters for a sub-device that supports the first uplink rate. The processor is used to configure the uplink burst overhead parameters of the first sub-device based on the first message when it is determined that the first uplink rate is supported.
[0054] Alternatively, the processor may perform a configuration operation without based on the first message if it determines that the first uplink rate is not supported.
[0055] In one possible implementation, the first sub-device supports a second uplink rate, which is different from the first uplink rate.
[0056] The transceiver is also configured to receive a second message, the second message including second indication information, the second indication information being used to indicate that the second message is applicable to configuring uplink burst overhead parameters for a sub-device supporting the second uplink rate; the processor is also configured to configure uplink burst overhead parameters for the first sub-device based on the second message, if it is determined that the second uplink rate is supported.
[0057] In one possible implementation, the plurality of sub-devices further includes a second sub-device that supports a first uplink rate, and a first message is used for the second sub-device to configure uplink burst overhead parameters of the second sub-device.
[0058] In one possible implementation, the first indication information is carried in a reserved field of the uplink burst overhead message.
[0059] In one possible implementation, the first message includes a message type field, which is used to carry first indication information.
[0060] In one possible implementation, the transceiver is further configured to receive a third message, the third message including third indication information, the third indication information being used to indicate that the third message is applicable to the configuration of extended burst overhead parameters for a sub-device supporting the first uplink rate; the processor is further configured to configure extended burst overhead parameters for the first sub-device based on the third message, if it is determined that the first uplink rate is supported.
[0061] Alternatively, the processor may also be configured not to perform configuration operations based on a third message if it is determined that the first uplink rate is not supported.
[0062] In one possible implementation, the third indication information is carried in a reserved field of the burst overhead length message.
[0063] In one possible implementation, the third message includes a message type field, which is used to carry third indication information.
[0064] In one possible implementation, the first uplink rate includes 2.5G and / or 1.25G.
[0065] In one possible implementation, the uplink burst overhead parameters include at least one of the following: guard time overhead, preamble overhead, separator overhead, pre-allocation delay, and transmitted optical power.
[0066] In one possible implementation, the extended burst overhead parameter is used to indicate the number of type 3 preamble bytes used in the uplink direction.
[0067] It should be noted that there are many other specific implementation methods in this application, and the specific implementation methods and their beneficial effects in the first aspect can be found therein, which will not be repeated here.
[0068] Fourthly, this application provides a communication device applied to an optical fiber network system, the optical fiber network system including a main device and multiple sub-devices, the multiple sub-devices including a first sub-device. The communication device can be the main device in the optical fiber network system, or it can be a functional module or chip within the main device. The communication device includes a transceiver and a processor.
[0069] The processor is configured to generate a first message, which includes first indication information indicating that the first message is applicable to configuring uplink burst overhead parameters for a sub-device supporting a first uplink rate. The transceiver is configured to send the first message. If the first sub-device supports the first uplink rate, the first message is used to configure the uplink burst overhead parameters for the first sub-device.
[0070] In one possible implementation, if the first sub-device does not support the first uplink rate, the first message is used for the first sub-device not to perform configuration operations based on the first message.
[0071] In one possible implementation, the first sub-device supports a second uplink rate, which is different from the first uplink rate.
[0072] The processor is also configured to generate a second message, the second message including second indication information, the second indication information being used to indicate that the second message is applicable to configuring uplink burst overhead parameters for a sub-device supporting a second uplink rate; the transceiver is also configured to send a second message, the second message being used for configuring uplink burst overhead parameters for a first sub-device.
[0073] In one possible implementation, the plurality of sub-devices further includes a second sub-device that supports a first uplink rate, and a first message is used for the second sub-device to configure uplink burst overhead parameters of the second sub-device.
[0074] In one possible implementation, the first indication information is carried in a reserved field of the uplink burst overhead message.
[0075] In one possible implementation, the first message includes a message type field, which is used to carry first indication information.
[0076] In one possible implementation, the processor is further configured to generate a third message, the third message including third indication information, the third indication information being used to indicate that the third message is applicable to the configuration of extended burst overhead parameters for a sub-device supporting the first uplink rate. The transceiver is further configured to transmit the third message. Wherein, if the first sub-device supports the first uplink rate, the third message is used for the first sub-device to configure extended burst overhead parameters for the first sub-device; or, if the first sub-device does not support the first uplink rate, the third message is used for the first sub-device not to perform a configuration operation based on the third message.
[0077] In one possible implementation, the third indication information is carried in a reserved field of the burst overhead length message.
[0078] In one possible implementation, the third message includes a message type field, which is used to carry third indication information.
[0079] In one possible implementation, the first uplink rate includes 2.5G and / or 1.25G.
[0080] In one possible implementation, the uplink burst overhead parameters include at least one of the following: guard time overhead, preamble overhead, separator overhead, pre-allocation delay, and transmitted optical power.
[0081] In one possible implementation, the extended burst overhead parameter is used to indicate the number of type 3 preamble bytes used in the uplink direction.
[0082] It should be noted that there are many other specific implementation methods in this application, and you can refer to the specific implementation methods and their beneficial effects in the first or third aspects, which will not be repeated here.
[0083] Fifthly, embodiments of this application provide a communication device, which may be a sub-device (e.g., a first sub-device) as described in the foregoing embodiments, 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 stores instructions, and the processing module executes the instructions stored in the storage module to cause the sub-device (e.g., the first sub-device) to perform the method of the first aspect or any embodiment 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, pin, or circuit, etc.; the processing module executes the instructions stored in the storage module to cause the sub-device (e.g., the first sub-device) to perform the method of the first aspect or any embodiment of the first aspect. The storage module can be an internal storage module of the chip (e.g., registers, caches, etc.) or an external storage module of the sub-device (e.g., read-only memory, random access memory, etc.).
[0084] Sixthly, embodiments of this application provide a communication device, which may be a main device as described in the foregoing embodiments, or a chip within the main device. The communication device may include a processing module and a transceiver module. When the communication device is a main device, the processing module may be a processor, and the transceiver module may be a transceiver; the main device may 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 of the second aspect or any embodiment 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, etc.; the processing module executes the instructions stored in the storage module to cause the main device to perform the method of the second aspect or any embodiment of the second aspect. The storage module may be a storage module within the chip (e.g., a register, cache, etc.), or a storage module located outside the chip within the main device (e.g., a read-only memory, random access memory, etc.).
[0085] In a seventh aspect, this application provides a communication device, which may be an integrated circuit chip. The integrated circuit chip includes a processor. The processor is coupled to a memory for storing programs or instructions that, when executed by the processor, cause the communication device to perform the methods described in any of the various embodiments of the first aspect or the second aspect, as well as the foregoing aspects.
[0086] Eighthly, embodiments of this application provide a computer program product containing instructions that, when executed on a computer, cause the computer to perform the methods described in any of the various embodiments of the first or second aspect and the various aspects described above.
[0087] Ninthly, embodiments of this application provide a computer-readable storage medium including instructions that, when executed on a computer, cause the computer to perform the methods described in any of the various embodiments of the foregoing first or second aspects and the various aspects thereof.
[0088] In a tenth aspect, embodiments of this application provide an optical fiber network system, which includes a first sub-device in the third aspect and any embodiment of the third aspect, and a main device in the fourth aspect and any embodiment of the fourth aspect. Attached Figure Description
[0089] Figure 1A An example diagram of the network architecture of a fiber optic network system in traditional technology;
[0090] Figure 1B This is an example diagram of the fiber optic network system in this application;
[0091] Figure 2 This is a flowchart illustrating the uplink overhead configuration method in this application;
[0092] Figure 3 This is another flowchart illustrating the uplink overhead configuration method in this application;
[0093] Figure 4 This is a schematic diagram of one embodiment of the communication device in this application;
[0094] Figure 5 This is a schematic diagram of another embodiment of the communication device in this application. Detailed Implementation
[0095] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.
[0096] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.
[0097] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such terms are interchangeable where appropriate so that the embodiments described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0098] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.
[0099] The uplink overhead configuration method provided in this application is applied to fiber optic network systems. To facilitate understanding of the uplink overhead configuration method proposed in this application, the basic architecture of fiber optic network systems in conventional technology is first introduced below:
[0100] like Figure 1AThe diagram shows the basic architecture of a traditional fiber optic network system. This system includes an optical line terminal (OLT), an optical distribution network (ODN), and optical network units (ONUs) (or optical network terminals (ONTs)). The OLT typically connects to the ONU (or ONT) through the ODN. The ODN is a network of optical devices including optical fibers, optical distribution frames (ODFs), optical splitters (also known as splitters), and combiners. Furthermore, the aforementioned OLT can connect to the operator's network via a network-side interface, and it can also connect to the ODN via a dedicated interface. The ODN, in turn, connects to the ONUs (or ONTs) via a dedicated interface. In the downlink direction, the OLT broadcasts the downlink optical signal, which is then distributed to each ONU (or ONT) via the ODN. In the uplink direction, a time-division multiple access (TDMA) method is used, with each ONU (or ONT) transmitting the uplink optical signal in its assigned uplink time slot by the OLT. This uplink optical signal is also called an uplink burst.
[0101] like Figure 1B The diagram shown is a structural schematic of the fiber optic network system provided in this application. The fiber optic network system provided in this application includes a main device 01 and multiple sub-devices 02, with the main device 01 connected to the multiple sub-devices 02. Each of the multiple sub-devices 02 includes a sub-device supporting at least one uplink rate; that is, all of the multiple sub-devices 02 may support a specific uplink rate. For example, the multiple sub-devices 02 may include multiple first sub-devices 021 (e.g., first sub-device #1 and first sub-device #2, etc.), where each first sub-device 021 supports a specific uplink rate (e.g., uplink rate 1). Furthermore, the multiple sub-devices 02 may also include multiple sub-devices supporting different uplink rates. For example, the plurality of sub-devices 02 include at least one first sub-device 021 (e.g., first sub-device #1 and first sub-device #2, etc.) and at least one second sub-device 022 (e.g., second sub-device #1 and second sub-device #2, etc.), the second sub-device 022 being a sub-device that supports another uplink rate (e.g., uplink rate 2), the uplink rate supported by the first sub-device 021 being different from the uplink rate supported by the second sub-device 022.
[0102] It should be understood that the master device can be an OLT, and the sub-devices can be ONUs (or ONTs). The master device connects to multiple sub-devices through an optical distribution network. For example, in a fiber-to-the-room (FTTR) scenario, the master device can be called a main FTTR unit (MFU) or a main gateway, and the sub-devices can be called subFTTR units (SFUs) or slave gateways. In one example, the sub-device can directly connect to a user's home terminal device, which can be a mobile phone or tablet connected to the aforementioned router via wireless fidelity (Wi-Fi), or an IoT device (e.g., indoor thermostat, indoor monitoring device, and other AI devices). In another example, the sub-device may have other networks (e.g., Ethernet) connected to the user's home terminal device. This sub-device may be an optical modem provided by the operator, which then connects to an indoor router or other devices. This application uses master and sub-devices as examples for illustration.
[0103] The following will combine Figure 2 The main process of the uplink overhead configuration method provided in this application is described below:
[0104] like Figure 2 The diagram shown is a flowchart of the uplink overhead configuration method provided in this application. The master device and the first sub-device will perform the following steps:
[0105] Step 201: The master device sends a first message; correspondingly, the first sub-device receives the first message.
[0106] The first message includes first indication information, which indicates that the first message is applicable to configuring uplink burst overhead parameters for a sub-device supporting a first uplink rate. Alternatively, the first indication information can be understood as indicating the adaptability of the first message to a specific uplink rate (e.g., the first uplink rate). The first message carrying the first indication information is a message used to configure uplink burst overhead parameters for a specific sub-device that supports the first uplink rate indicated by the first indication information.
[0107] It should be understood that the upstream rates involved in this application can also be referred to as upstream line rates. For example, the first upstream rate described above can also be referred to as the first upstream line rate. In this embodiment and subsequent embodiments, the term "upstream rate" will only be used as an example. For example, the first upstream rate can be 2.48832 Gbit / s (hereinafter referred to as 2.5G), 1.24416 Gbit / s (hereinafter referred to as 1.25G), or other upstream rates. Specific examples will be used to illustrate this later, and it will not be elaborated here.
[0108] Optionally, the first message is an upstream overhead message. The parameters configured through this upstream overhead message mainly include upstream overhead parameters. In some application scenarios, these parameters may also be referred to as transmit parameters, global network parameters, operating parameters, etc. In this embodiment and subsequent embodiments, only the term "upstream overhead parameters" will be used as an example.
[0109] For example, the upstream overhead parameters include at least one of the following: guard time overhead, preamble overhead, delimiter overhead, pre-assigned delay, and transmit power.
[0110] Specifically, the first instruction information can be carried in the first message in any of the following ways:
[0111] In one possible implementation, the first indication information is carried in a reserved field of the Upstream_Overhead message. For ease of explanation, the reserved field of the Upstream_Overhead message is referred to as the first reserved field, and the first reserved field is located in the 10th byte of the Upstream_Overhead message, that is, the first indication information is carried in the 10th byte of the first message.
[0112] For example, the content and meaning of each field in the first message are described in Table 1-0 below:
[0113] Table 1-0
[0114]
[0115] As shown in the example in Table 1-0, the 10th byte of the uplink burst overhead message includes two reserved bits, "xx", which can be used to carry the first indication information. Specifically, the first indication information can be represented using one of the reserved bits, that is, one bit of "xx" is reserved and the other bit is used to represent the first indication information; the first indication information can also be represented using two reserved bits, that is, two bits of "xx" represent the first indication information. The following will introduce these examples in detail:
[0116] In one implementation of this embodiment, the first indication information is represented by one bit in the first reserved field. Since one bit can represent two values (i.e., "0" or "1"), the first indication information has two selectable values, that is, the first uplink rate has two selectable values.
[0117] In Example 1.1, one value (e.g., the aforementioned 1 bit being "1") indicates that the first uplink rate is 2.5G, meaning the first indication information indicates that the first message is applicable to configuring uplink burst overhead parameters for sub-devices supporting 2.5G uplink rates; another value (e.g., the aforementioned 1 bit being "0") indicates that the first uplink rate is any uplink rate, meaning the first indication information indicates that the first message is applicable to configuring uplink burst overhead parameters for sub-devices with any uplink rate. Similarly, in other examples, a value of "1" can be used to represent an arbitrary uplink rate, and a value of "0" can be used to represent a first uplink rate of 2.5G. This will not be elaborated upon here; the former will be used as an example in the following text.
[0118] For example, taking the first bit (i.e., the most significant bit (MSB)) in "xx" as a reserved bit, and the second bit in "xx" representing the first indication information, the bytes carrying the first indication information in the first message are shown in Table 1-1 below:
[0119] Table 1-1
[0120]
[0121] In the example shown in Table 1-1, the first bit of the 10th byte (i.e., "x") is reserved, and the second bit of the 10th byte (i.e., "B") represents the first indication information, indicating the code pattern for the applicability of the uplink burst overhead message to a specific uplink rate (i.e., the uplink rate indicated by "B"). If B=0, it means that the uplink burst overhead message is applicable to sub-devices with any uplink rate, that is, sub-devices with any uplink rate can configure uplink burst overhead parameters based on this uplink burst overhead message; if B=1, it means that the uplink burst overhead message is applicable to sub-devices with a 2.5G uplink rate, that is, sub-devices with only a 2.5G uplink rate can configure uplink burst overhead parameters based on this uplink burst overhead message.
[0122] This example can be applied to a fiber optic network system that includes sub-devices with at least two uplink rates, wherein one of the sub-devices supports a 2.5G uplink rate in the fiber optic network system.
[0123] In this example, the first indication information is implemented using 1 bit, which can represent a 2.5G uplink rate or any uplink rate. This not only enables individual configuration of uplink burst overhead parameters for sub-devices supporting 2.5G uplink rates, thereby improving the burst efficiency of these sub-devices, but also allows configuration of sub-devices supporting any uplink rate through a single message, saving signaling overhead for configuring uplink burst overhead parameters. Furthermore, setting a value to represent the first uplink rate as arbitrary improves system compatibility and prevents the introduction of sub-devices supporting other uplink rates (e.g., sub-devices supporting rates other than 2.5G and 1.25G) from affecting the configuration of those sub-devices.
[0124] In another example 1.2, one value (e.g., the aforementioned 1 bit being "1") indicates that the first uplink rate is 2.5G, meaning the first indication information indicates that the first message is applicable to configuring uplink burst overhead parameters for sub-devices supporting 2.5G uplink rates; another value (e.g., the aforementioned 1 bit being "0") indicates that the first uplink rate is 1.25G and 2.5G, meaning the first indication information indicates that the first message is applicable to configuring uplink burst overhead parameters for sub-devices supporting both 1.25G and 2.5G uplink rates. Similarly, in other examples, a value of "1" can be used to represent the first uplink rate as 1.25G and 2.5G, and a value of "0" can be used to represent the first uplink rate as 2.5G. This will not be elaborated upon here; the former will be used as an example later.
[0125] For example, taking the first bit (i.e., MSB) in "xx" as a reserved bit, and the second bit in "xx" as the first indication information, the bytes carrying the first indication information in the first message are shown in Table 1-2 below:
[0126] Table 1-2
[0127]
[0128] In the example shown in Table 1-2, the first bit of the 10th byte (i.e., "x") is reserved, and the second bit of the 10th byte (i.e., "B") represents the first indication information, indicating the code pattern for the applicability of the uplink burst overhead message to a specific uplink rate (i.e., the uplink rate indicated by "B"). If B=0, it means that the uplink burst overhead message is applicable to both 2.5G uplink rate sub-devices and 1.25G uplink rate sub-devices, that is, both 2.5G uplink rate sub-devices and 1.25G uplink rate sub-devices can configure uplink burst overhead parameters based on this uplink burst overhead message; if B=1, it means that the uplink burst overhead message is applicable to 2.5G uplink rate sub-devices, that is, only 2.5G uplink rate sub-devices can configure uplink burst overhead parameters based on this uplink burst overhead message.
[0129] This example can be applied to fiber optic network systems that only contain sub-devices with uplink speeds of 1.25G and 2.5G.
[0130] In this example, not only can uplink burst overhead parameters be configured separately for sub-devices supporting 2.5G uplink speeds to improve the burst efficiency of sub-devices supporting 2.5G uplink speeds, but it can also configure sub-devices supporting 1.25G uplink speeds and 2.5G uplink speeds simultaneously with a single message to save signaling overhead for configuring uplink burst overhead parameters.
[0131] In another example 1.3, one value (e.g., the aforementioned 1 bit being "1") indicates that the first uplink rate is 2.5G, meaning the first indication information indicates that the first message is applicable to configuring uplink burst overhead parameters for sub-devices supporting 2.5G uplink rates; another value (e.g., the aforementioned 1 bit being "0") indicates that the first uplink rate is 1.25G, meaning the first indication information indicates that the first message is applicable to configuring uplink burst overhead parameters for sub-devices supporting 1.25G uplink rates. Similarly, in other examples, a value of "1" can be used to represent the first uplink rate of 1.25G, and a value of "0" can be used to represent the first uplink rate of 2.5G. This will not be elaborated upon here; the former will be used as an example later.
[0132] For example, taking the first bit (i.e., MSB) in "xx" as a reserved bit, and the second bit in "xx" as the first indication information, the bytes carrying the first indication information in the first message are shown in Table 1-3 below:
[0133] Table 1-3
[0134]
[0135] In the example shown in Table 1-3, the first bit of the 10th byte (i.e., "x") is reserved, and the second bit of the 10th byte (i.e., "B") represents the first indication information, indicating the code pattern for the applicability of the uplink burst overhead message to a specific uplink rate (i.e., the uplink rate indicated by "B"). If B=0, it means that the uplink burst overhead message is applicable to sub-devices with a 1.25G uplink rate, that is, only sub-devices with a 1.25G uplink rate can configure uplink burst overhead parameters based on this uplink burst overhead message; if B=1, it means that the uplink burst overhead message is applicable to sub-devices with a 2.5G uplink rate, that is, only sub-devices with a 2.5G uplink rate can configure uplink burst overhead parameters based on this uplink burst overhead message.
[0136] This example can be applied to fiber optic network systems that only contain sub-devices with uplink speeds of 1.25G and 2.5G.
[0137] In this example, the first indication information is implemented using 1 bit, which can configure uplink burst overhead parameters for sub-devices with uplink speeds of 2.5G and 1.25G respectively, which is beneficial to improving the burst efficiency of sub-devices with different speeds in the system.
[0138] It should be understood that the reserved bits in Tables 1-1, 1-2, and 1-3 can also be filled with either "0" or "1", meaning the first indication information uses two bits in the first reserved field to represent two possible values. Taking MSB filled with "0" as an example, Tables 1-1, 1-2, and 1-3 can be modified to Tables 2-1, 2-2, and 2-3 as shown below:
[0139] Table 2-1
[0140]
[0141] In the example shown in Table 2-1, the 2 bits of the 10th byte (i.e., "BB") represent the first indication information, indicating the code pattern for the applicability of the uplink burst overhead message to a specific uplink rate (i.e., the uplink rate indicated by "BB"). If BB=00, it means that the uplink burst overhead message is applicable to sub-devices with any uplink rate, that is, sub-devices with any uplink rate can configure uplink burst overhead parameters based on this uplink burst overhead message; if BB=01, it means that the uplink burst overhead message is applicable to sub-devices with a 2.5G uplink rate, that is, sub-devices with only a 2.5G uplink rate can configure uplink burst overhead parameters based on this uplink burst overhead message.
[0142] Table 2-2
[0143]
[0144] In the example shown in Table 2-2, the 2 bits of the 10th byte (i.e., "BB") represent the first indication information, indicating the code pattern for the applicability of the uplink burst overhead message to a specific uplink rate (i.e., the uplink rate indicated by "BB"). If BB=00, it means that the uplink burst overhead message is applicable to both 2.5G uplink rate sub-devices and 1.25G uplink rate sub-devices, that is, both 2.5G uplink rate sub-devices and 1.25G uplink rate sub-devices can configure uplink burst overhead parameters based on this uplink burst overhead message; if BB=01, it means that the uplink burst overhead message is applicable to 2.5G uplink rate sub-devices, that is, only 2.5G uplink rate sub-devices can configure uplink burst overhead parameters based on this uplink burst overhead message.
[0145] Table 2-3
[0146]
[0147] In the example shown in Table 2-3, the 2 bits of the 10th byte (i.e., "BB") represent the first indication information, indicating the code pattern for the applicability of the uplink burst overhead message to a specific uplink rate (i.e., the uplink rate indicated by "BB"). If BB=00, it means that the uplink burst overhead message is applicable to sub-devices with a 1.25G uplink rate, that is, only sub-devices with a 1.25G uplink rate can configure uplink burst overhead parameters based on this uplink burst overhead message; if BB=01, it means that the uplink burst overhead message is applicable to sub-devices with a 2.5G uplink rate, that is, only sub-devices with a 2.5G uplink rate can configure uplink burst overhead parameters based on this uplink burst overhead message.
[0148] It should be understood that the examples shown in Tables 2-1, 2-2, and 2-3 have similar beneficial effects to those shown in Tables 1-1, 1-2, and 1-3 above. For details, please refer to the descriptions of Tables 1-1, 1-2, and 1-3 above, which will not be repeated here.
[0149] In another implementation of this embodiment, the first indication information is represented by 2 bits in the first reserved field. Since 2 bits can represent 4 values (i.e., "00", "01", "10" and "11"), the first indication information has at most 4 selectable values, that is, the first uplink rate has at most 4 selectable values.
[0150] In Example 1.4, taking an optical network system containing at least two uplink rates as an example, the first indication information has at least three selectable values, meaning the first uplink rate has at least three selectable values. Three of the aforementioned four values can be assigned meaning, while one value is reserved. For example, one value (e.g., the aforementioned two bits set to "00") indicates that the first uplink rate is any uplink rate, meaning the first indication information indicates that the first message is applicable to configuring uplink burst overhead parameters for sub-devices with any uplink rate; another value (e.g., the aforementioned two bits set to "01") indicates that the first uplink rate is 2.5G, meaning the first indication information indicates that the first message is applicable to configuring uplink burst overhead parameters for sub-devices supporting a 2.5G uplink rate; yet another value (e.g., the aforementioned two bits set to "10") indicates that the first uplink rate is 1.25G, meaning the first indication information indicates that the first message is applicable to configuring uplink burst overhead parameters for sub-devices supporting a 1.25G uplink rate. It should be understood that in some other examples, the meanings of the three values mentioned above can be interchanged, which will not be elaborated here. Furthermore, in other examples, other values can be reserved, with the other three values representing the three meanings mentioned above respectively. For example, "00" is reserved, while "01", "10", and "11" respectively represent a first uplink rate of any uplink rate, a first uplink rate of 2.5G, and a first uplink rate of 1.25G, which will not be elaborated here. Subsequent embodiments will only use the former as an example.
[0151] For example, the bytes carrying the first indication information in the first message are shown in Table 3-1 or Table 3-2 below:
[0152] Table 3-1
[0153]
[0154] In the example shown in Table 3-1, the first two bits of the 10th byte (i.e., "BB") represent the first indication information, indicating the code pattern for the applicability of the uplink burst overhead message to a specific uplink rate (i.e., the uplink rate indicated by "BB"). If BB=00, it means that the uplink burst overhead message is applicable to sub-devices with any uplink rate, that is, sub-devices with any uplink rate can configure uplink burst overhead parameters based on this uplink burst overhead message; if BB=01, it means that the uplink burst overhead message is applicable to sub-devices with a 2.5G uplink rate, that is, sub-devices with only a 2.5G uplink rate can configure uplink burst overhead parameters based on this uplink burst overhead message; if BB=10, it means that the uplink burst overhead message is applicable to sub-devices with a 1.25G uplink rate, that is, sub-devices with only a 1.25G uplink rate can configure uplink burst overhead parameters based on this uplink burst overhead message. BB=11 is a reserved value.
[0155] This example can be applied to fiber optic network systems that include sub-devices with uplink speeds of at least 1.25G and 2.5G.
[0156] In this example, the first indication information is implemented using 2 bits. This not only allows for the configuration of uplink burst overhead parameters for sub-devices with 2.5G uplink speeds and those with 1.25G uplink speeds, respectively, thereby improving the burst efficiency of sub-devices at various speeds in the system, but also enables the configuration of sub-devices with any uplink speed through a single message, saving signaling overhead for configuring uplink burst overhead parameters. Furthermore, setting a value to indicate that the first uplink speed is arbitrary improves system compatibility and prevents the introduction of sub-devices supporting other uplink speeds (e.g., sub-devices supporting speeds other than 2.5G and 1.25G) from affecting the configuration of those sub-devices.
[0157] Table 3-2
[0158]
[0159] In the example shown in Table 3-2, the first two bits of the 10th byte (i.e., "BB") represent the first indication information, indicating the code pattern for the applicability of the uplink burst overhead message to a specific uplink rate (i.e., the uplink rate indicated by "BB"). The difference from the example shown in Table 3-1 is that BB=00, indicating that the uplink burst overhead message applies to both 2.5G uplink rate sub-devices and 1.25G uplink rate sub-devices; that is, both 2.5G and 1.25G uplink rate sub-devices can configure uplink burst overhead parameters based on this message. The meanings of the other values are described in the relevant descriptions of the example shown in Table 3-1 above, and will not be repeated here.
[0160] This example can be applied to fiber optic network systems containing sub-devices with uplink speeds of at least 1.25G and 2.5G. When sub-devices supporting other uplink speeds are introduced into the fiber optic network system, the value "11" can be assigned to these sub-devices, thereby improving system compatibility.
[0161] In this example, the first indication information is implemented using 2 bits, which not only enables the configuration of uplink burst overhead parameters for sub-devices with uplink speeds of 2.5G and 1.25G respectively, thereby improving the burst efficiency of sub-devices with different speeds in the system; but also enables the configuration of sub-devices with uplink speeds of 1.25G and 2.5G simultaneously through a single message, thereby saving the signaling overhead used for configuring uplink burst overhead parameters.
[0162] In another possible implementation, the first indication information is carried in the message type field of the first message. Optionally, the first message is an Upstream_Overhead message, and the type field is located in the second byte of the Upstream_Overhead message, that is, the first indication information is carried in the second byte of the first message. It can be understood that this implementation defines a new message type, which is used to configure upstream_overhead parameters for sub-devices with a specific upstream rate.
[0163] In Example 1.5, a new message type is defined as an uplink burst overhead message applicable to sub-devices supporting 2.5G uplink rates. For example, the content and meaning of the various fields included in this first message are described in Table 4-1 below:
[0164] Table 4-1
[0165]
[0166] In the example shown in Table 4-1, the first indication information is "00010101", meaning the newly added value "00010101" indicates "uplink burst for 2.5G uplink rate", i.e., the first uplink rate is 2.5G. This can be understood as a newly defined uplink burst overhead message of type "00010101" used to configure uplink burst overhead parameters for sub-devices supporting 2.5G uplink rates.
[0167] In addition, the system retains the use of uplink burst overhead messages with the traditional value (i.e., "00000001") and continues to use the functionality of message types indicated by the traditional value. This uplink burst overhead message with the traditional value is used to configure sub-devices with 1.25G uplink speeds and sub-devices with 2.5G uplink speeds. It can also be understood that this uplink burst overhead message with the traditional value is used to configure sub-devices with any uplink speed.
[0168] In this example, the master device supports sending values including "00010101" and "00000001". For example, the master device broadcasts an uplink burst overhead message with the value "00010101" to configure uplink burst overhead parameters for sub-devices supporting 2.5G uplink rates; the master device also broadcasts an uplink burst overhead message with the value "00000001" to configure uplink burst overhead parameters for both sub-devices supporting 2.5G uplink rates and sub-devices supporting 1.25G uplink rates.
[0169] In this example, a new message type has been added specifically for configuring uplink burst overhead parameters for sub-devices supporting 2.5G uplink rates. This allows for individual configuration of uplink burst overhead parameters for sub-devices supporting 2.5G uplink rates, thereby improving the burst efficiency of these sub-devices. Furthermore, the traditional value ("00000001") is retained for configuring sub-devices with any uplink rate (i.e., 2.5G and 1.25G uplink rates) with a single message, which helps save on signaling overhead for configuring uplink burst overhead parameters.
[0170] In another example, 1.6, in addition to defining the uplink burst overhead message as shown in Table 4-1 above, the function of the message type indicated by the traditional value (i.e., "00000001") can also be modified. For example, as shown in Table 4-2, the definition (or function) of the traditional value (i.e., "00000001") is modified to indicate "uplink burst for 1.25G uplink rate", that is, the first uplink rate is 1.25G. This can be understood as a newly defined uplink burst overhead message with message type "00000001" is used to configure uplink burst overhead parameters for sub-devices that support 1.25G uplink rates.
[0171] Table 4-2
[0172]
[0173] It should be understood that the example shown in Table 4-2 only shows a portion of the bytes of the uplink burst overhead message. For the remaining bytes in the example shown in Table 4-2, please refer to the example shown in Table 4-1 above, which will not be repeated here.
[0174] In this example, the master device supports sending values including "00010101" and "00000001". For example, the master device broadcasts an uplink burst overhead message with the value "00010101" to configure uplink burst overhead parameters for sub-devices supporting 2.5G uplink speeds; the master device broadcasts an uplink burst overhead message with the value "00000001" to configure uplink burst overhead parameters for sub-devices supporting 1.25G uplink speeds.
[0175] In this example, a new message type has been added specifically for configuring uplink burst overhead parameters for sub-devices supporting 2.5G uplink speeds. This allows for separate configuration of uplink burst overhead parameters for sub-devices supporting 2.5G uplink speeds, thereby improving the burst efficiency of these sub-devices. Furthermore, the definition of the traditional value ("00000001") has been modified. A new value of "00000001" is defined specifically for configuring uplink burst overhead parameters for sub-devices supporting 1.25G uplink speeds, thus enabling separate configuration of uplink burst overhead parameters for sub-devices supporting 1.25G uplink speeds and improving their burst efficiency.
[0176] In another example, 1.7, in addition to defining the uplink burst overhead message shown in Table 4-1 above, a new value (e.g., "000000011") can be defined to indicate "uplink burst for 1.25G uplink rate". For example, as shown in Table 4-3, a new uplink burst overhead message with message type "000000011" is defined to configure uplink burst overhead parameters for sub-devices supporting 1.25G uplink rates. Furthermore, the system retains the use of the traditional value (i.e., "00000001") for uplink burst overhead messages and retains the functionality of the message type indicated by the traditional value. This traditional value uplink burst overhead message is used to configure sub-devices with 1.25G uplink rates and sub-devices with 2.5G uplink rates. It can also be understood that this traditional value uplink burst overhead message is used to configure sub-devices with any uplink rate.
[0177] Table 4-3
[0178]
[0179] It should be understood that the example shown in Table 4-3 only shows a portion of the bytes of the uplink burst overhead message. For the remaining bytes in the example shown in Table 4-3, please refer to the example shown in Table 4-1 above, which will not be repeated here.
[0180] In this example, the master device supports sending values including "00010101", "000000011", and "00000001". For example, the master device broadcasts an uplink burst overhead message with the value "00010101" to configure uplink burst overhead parameters for sub-devices supporting 2.5G uplink rates; the master device broadcasts an uplink burst overhead message with the value "00000011" to configure uplink burst overhead parameters for sub-devices supporting 1.25G uplink rates; and the master device broadcasts an uplink burst overhead message with the value "00000001" to configure uplink burst overhead parameters for both sub-devices supporting 1.25G uplink rates and sub-devices supporting 2.5G uplink rates simultaneously.
[0181] In this example, a new message type has been added specifically for configuring uplink burst overhead parameters for sub-devices supporting 2.5G uplink speeds. This allows for separate configuration of uplink burst overhead parameters for sub-devices supporting 2.5G uplink speeds, thereby improving the burst efficiency of these sub-devices. Furthermore, the definition of the traditional value ("00000001") has been modified. A new value of "00000001" is defined specifically for configuring uplink burst overhead parameters for sub-devices supporting 1.25G uplink speeds, thus enabling separate configuration of uplink burst overhead parameters for sub-devices supporting 1.25G uplink speeds and improving their burst efficiency.
[0182] It should be understood that the main device in this application can implement the first message and the first instruction information using any of the foregoing implementation methods or examples, and this application is not limited thereto.
[0183] It should also be understood that the first sub-device in this embodiment can be either an inactive or an activated sub-device. In one example, the first sub-device may be a sub-device performing an activation procedure. For example, before receiving the first message from the master device, the first sub-device may be in a standby state (i.e., O2 state). In another example, the first sub-device may be a sub-device that has completed the activation procedure. For example, if the first sub-device is activated but some of its uplink burst overhead parameters need to be modified, the master device may also send an uplink burst overhead message applicable to the uplink rate of the first sub-device.
[0184] In this step, after receiving the first message, 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 (i.e., the first uplink rate) corresponding to the first message, and then the first sub-device determines whether to trigger the configuration process. 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.
[0185] Step 202a: If the first sub-device supports the first uplink rate, the first sub-device configures the uplink burst overhead parameters of the first sub-device based on the first message.
[0186] In this embodiment, step 202a is an optional step.
[0187] In one example, taking Table 2-1 as an example, if the first indication information is "00" as shown in Table 2-1, it means that the uplink burst overhead message is applicable to any normal uplink rate, that is, the first uplink rate is any uplink rate. If the first sub-device supports a 2.5G uplink rate, then the first sub-device supports the first uplink rate; if the first sub-device supports a 1.25G uplink rate, then the first sub-device also supports the first uplink rate. At this time, regardless of whether the first sub-device supports a 2.5G uplink rate or a 1.25G uplink rate, the first sub-device can configure the uplink burst overhead parameters of the first sub-device based on the first message.
[0188] In another example, taking Table 2-1 above as an example, if the first indication information is "01" as shown in Table 2-1, it means that the uplink burst overhead message is applicable to the 2.5G uplink rate, that is, the first uplink rate is 2.5G. In this case, the first sub-device can only configure the uplink burst overhead parameters of the first sub-device based on the first message if the first sub-device supports the 2.5G uplink rate.
[0189] In another example, taking Table 2-3 above as an example, if the first indication information is "00" as shown in Table 2-3, it means that the uplink burst overhead message is applicable to the 1.25G uplink rate, that is, the first uplink rate is 1.25G. In this case, the first sub-device can only configure the uplink burst overhead parameters of the first sub-device based on the first message if the first sub-device supports the 1.25G uplink rate.
[0190] In another example, taking Table 4-1 above as an example, if the first indication information is "00010101" as shown in Table 4-1, it means that the uplink burst overhead message is applicable to the 2.5G uplink rate, that is, the first uplink rate is 2.5G. In this case, the first sub-device can only configure the uplink burst overhead parameters of the first sub-device based on the first message if the first sub-device supports the 2.5G uplink rate.
[0191] For other examples in this step, please refer to the relevant description in step 201 above, which will not be repeated here.
[0192] In addition, the first sub-device configures protection time overhead based on the protection time value in the first message, preamble overhead based on the preamble value (e.g., type 1 preamble, type 2 preamble, and type 3 preamble) in the first message, separator overhead based on the separator value in the first message, pre-allocated delay overhead based on the pre-allocated delay value in the first message, and transmit power based on the sub-device transmit power level mode, etc. Details are omitted here. Optionally, after configuring the uplink burst overhead parameters, the first sub-device enters the serial number acquisition state (Serial_Numberstate) (i.e., state O3). Optionally, the first sub-device starts timer TO1, i.e., the serial number acquisition and ranging timer.
[0193] Step 202b: If the first sub-device does not support the first uplink rate, then the first sub-device does not perform a configuration operation based on the first message.
[0194] In this embodiment, step 202b is an optional step.
[0195] This can also be understood as follows: when the first sub-device receives the first message and does not support the first uplink rate, the first sub-device directly ignores the first message and does not configure uplink burst overhead parameters based on the first message.
[0196] In one example, taking Table 2-1 as an example, if the first indication information is "01" as shown in Table 2-1, it means that the uplink burst overhead message is applicable to a 2.5G uplink rate, that is, the first uplink rate is 2.5G. At this time, if the first sub-device supports a 1.25G uplink rate, then the first sub-device does not trigger configuration based on the first message.
[0197] In another example, taking Table 2-3 above as an example, if the first indication information is "00" as shown in Table 2-3, it means that the uplink burst overhead message is applicable to a 1.25G uplink rate, that is, the first uplink rate is 1.25G. In this case, if the first sub-device supports a 2.5G uplink rate, then the first sub-device does not trigger configuration based on the first message.
[0198] In another example, taking Table 4-1 above as an example, if the first indication information is "00010101" as shown in Table 4-1, it means that the uplink burst overhead message is applicable to a 2.5G uplink rate, that is, the first uplink rate is 2.5G. In this case, if the first sub-device supports a 1.25G uplink rate, then the first sub-device does not trigger the configuration based on the first message.
[0199] For other examples in this step, please refer to the relevant description in step 201 above, which will not be repeated here.
[0200] Therefore, it is evident that the uplink burst overhead message in the conventional technology does not include the first indication information. Thus, the uplink burst overhead message in the conventional technology can configure uplink burst overhead parameters for sub-devices supporting any uplink rate; that is, all sub-devices in the fiber optic network system that receive the uplink burst overhead message can configure uplink burst overhead parameters based on it. In this embodiment, however, the first message includes the first indication information, making the first message only applicable to sub-devices supporting the first uplink rate. That is, only sub-devices in the fiber optic network system that receive the first message and support the first uplink rate can configure uplink burst overhead parameters based on it. Therefore, this facilitates the individual configuration of uplink overhead for sub-devices supporting different uplink rates, thereby improving the efficiency of uplink bursts.
[0201] It should be noted that after the master device configures the uplink burst overhead parameters for the sub-device supporting the first uplink rate via the first message, the master device can also configure extended burst overhead parameters for the sub-device supporting the first uplink rate via the third message. At this time, the master device and the first sub-device can execute steps 203 and 204a, or steps 203 and 204b.
[0202] Step 203: The master device sends a third message; correspondingly, the first sub-device receives the third message.
[0203] The third message includes third indication information, which indicates that the third message is applicable to configuring extended overhead parameters for a sub-device supporting the first uplink rate. Alternatively, the third indication information can be understood as indicating the adaptability of the third message to a specific uplink rate (e.g., the first uplink rate). The third message carrying the third indication information is a message used to configure extended overhead parameters for a specific sub-device that supports the first uplink rate indicated by the third indication information.
[0204] Optionally, the third message is the Extended_Burst_Length message, where the extended burst overhead parameter indicates the number of type 3 preamble bytes used in the uplink direction.
[0205] Specifically, the third instruction information can be carried in the third message in any of the following ways:
[0206] In one possible implementation, the third indication information is carried in a reserved field of the Extended_Burst_Length message. For ease of explanation, the reserved field of the Extended_Burst_Length message is referred to as the second reserved field. The second reserved field is located in any one of the 5th to 12th bytes of the Extended_Burst_Length message, meaning the third indication information is carried in one of the 5th to 12th bytes of the Extended_Burst_Length message. The following description uses the example of the third indication information being carried in the 5th byte of the Extended_Burst_Length message.
[0207] For example, the content and meaning of each field in the third message are described in Table 5-0 below:
[0208] Table 5-0
[0209]
[0210] As shown in the example in Table 5-0, the second reserved field is located in the 5th byte of the extended burst length message. This 5th byte includes 8 reserved bits that can be used to carry the third indication information. Specifically, the third indication information can be represented using 1 reserved bit, with the remaining 7 bits reserved; alternatively, the third indication information can be represented using 2 reserved bits, with the remaining 6 bits reserved. The following examples illustrate these points:
[0211] In one implementation of this embodiment, the third indication information is represented by one bit in the second reserved field. Since one bit can represent two values (i.e., "0" or "1"), the third indication information has two selectable values, which means the first uplink rate has two selectable values.
[0212] In Example 2.1, one value (e.g., the aforementioned 1 bit being "1") indicates that the first uplink rate is 2.5G, meaning the third indication information indicates that the third message is applicable to the burst overhead parameters of the sub-device configuration extension supporting the 2.5G uplink rate; another value (e.g., the aforementioned 1 bit being "0") indicates that the first uplink rate is any uplink rate, meaning the third indication information indicates that the third message is applicable to the burst overhead parameters of the sub-device configuration extension for any uplink rate. Similarly, in other examples, a value of "1" can be used to indicate that the first uplink rate is any uplink rate, and a value of "0" can be used to indicate that the first uplink rate is 2.5G. This will not be elaborated upon here; the former will be used as an example later.
[0213] For example, taking the last bit (i.e., the least significant bit (LSB)) in the 5th byte to represent the third indication information, and the remaining bits as reserved bits, the bytes carrying the third indication information in the third message are shown in Table 5-1 below:
[0214] Table 5-1
[0215]
[0216] In the example shown in Table 5-1, the first 7 bits of the 5th byte (i.e., "xxxxxxx") are reserved, and the 8th bit of the 5th byte (i.e., "R") represents the third indication information, indicating the code pattern for the applicability of the extended burst overhead length message to a specific uplink rate (i.e., the uplink rate indicated by "R"). If R=0, it means that the extended burst overhead length message is applicable to sub-devices with any uplink rate, that is, sub-devices with any uplink rate can configure extended burst overhead parameters based on this extended burst overhead length message; if R=1, it means that the extended burst overhead length message is applicable to sub-devices with a 2.5G uplink rate, that is, sub-devices with only a 2.5G uplink rate can configure extended burst overhead parameters based on this extended burst overhead length message.
[0217] This example can be applied to a fiber optic network system that includes sub-devices with at least two uplink rates, wherein one of the sub-devices supports a 2.5G uplink rate in the fiber optic network system.
[0218] In this example, the third indication information is implemented using 1 bit, which can represent a 2.5G uplink rate or any uplink rate. This not only enables separate configuration of extended burst overhead parameters for sub-devices supporting 2.5G uplink rates to improve their burst efficiency, but also allows configuration of sub-devices supporting any uplink rate through a single message, saving signaling overhead for configuring extended burst overhead parameters. Furthermore, setting a value to indicate that the first uplink rate is arbitrary improves system compatibility and prevents the introduction of sub-devices supporting other uplink rates (e.g., sub-devices supporting rates other than 2.5G and 1.25G) from affecting the configuration of those sub-devices.
[0219] In another example, 2.2, one value (e.g., the aforementioned 1 bit being "1") indicates that the first uplink rate is 2.5G, meaning the third indication information indicates that the third message is applicable to the burst overhead parameters of the sub-device configuration extension supporting 2.5G uplink rates; another value (e.g., the aforementioned 1 bit being "0") indicates that the first uplink rate is 1.25G and 2.5G, meaning the third indication information indicates that the third message is applicable to the burst overhead parameters of the sub-device configuration extension supporting both 1.25G and 2.5G uplink rates. Similarly, in other examples, a value of "1" can be used to represent the first uplink rate as 1.25G and 2.5G, and a value of "0" can be used to represent the first uplink rate as 2.5G. This will not be elaborated upon here; the former will be used as an example later.
[0220] For example, the first 7 bits of the 5th byte (i.e., "xxxxxxx") are reserved, and the 8th bit of the 5th byte (i.e., "R") represents the third indication information. The bytes carrying the third indication information in the third message are shown in Table 5-2 below:
[0221] Table 5-2
[0222]
[0223] In the example shown in Table 5-2, the first 7 bits of the 5th byte (i.e., "xxxxxxx") are reserved, and the 8th bit of the 5th byte (i.e., "R") represents the third indication information, indicating the code pattern for the applicability of the extended burst length message to a specific uplink rate (i.e., the uplink rate indicated by "R"). If R=0, it means that the extended burst length message is applicable to both 2.5G uplink rate sub-devices and 1.25G uplink rate sub-devices, that is, both 2.5G uplink rate sub-devices and 1.25G uplink rate sub-devices can configure extended burst overhead parameters based on this extended burst length message; if R=1, it means that the extended burst length message is applicable to 2.5G uplink rate sub-devices, that is, only 2.5G uplink rate sub-devices can configure extended burst overhead parameters based on this extended burst length message.
[0224] This example can be applied to fiber optic network systems that only contain sub-devices with uplink speeds of 1.25G and 2.5G.
[0225] In this example, not only are extended burst overhead parameters configured separately for sub-devices supporting 2.5G uplink speeds to improve the burst efficiency of sub-devices supporting 2.5G uplink speeds, but it is also possible to configure both 1.25G uplink speed sub-devices and 2.5G uplink speed sub-devices simultaneously with a single message, thereby saving signaling overhead for configuring extended burst overhead parameters.
[0226] In another example, 2.3, one value (e.g., the aforementioned 1 bit being "1") indicates that the first uplink rate is 2.5G, meaning the third indication information indicates that the third message is applicable to the burst overhead parameters of the sub-device configuration extension supporting the 2.5G uplink rate; another value (e.g., the aforementioned 1 bit being "0") indicates that the first uplink rate is 1.25G, meaning the third indication information indicates that the third message is applicable to the burst overhead parameters of the sub-device configuration extension supporting the 1.25G uplink rate. Similarly, in other examples, a value of "1" can be used to represent the first uplink rate of 1.25G, and a value of "0" can be used to represent the first uplink rate of 2.5G. This will not be elaborated upon here; the former will be used as an example later.
[0227] For example, taking the first 7 bits of the 5th byte (i.e., "xxxxxxx") as reserved and the 8th bit of the 5th byte (i.e., "R") as representing the third indication information, the bytes carrying the third indication information in the third message are shown in Table 5-3 below:
[0228] Table 5-3
[0229]
[0230] In the example shown in Table 5-3, the first 7 bits of the 5th byte (i.e., "xxxxxxx") are reserved, and the 8th bit of the 5th byte (i.e., "R") represents the third indication information, indicating the code pattern for the applicability of the extended burst length message to a specific uplink rate (i.e., the uplink rate indicated by "R"). If R=0, it means that the extended burst length message is applicable to sub-devices with a 1.25G uplink rate, that is, only sub-devices with a 1.25G uplink rate can configure extended burst overhead parameters based on this extended burst length message; if R=1, it means that the extended burst length message is applicable to sub-devices with a 2.5G uplink rate, that is, only sub-devices with a 2.5G uplink rate can configure extended burst overhead parameters based on this extended burst length message.
[0231] This example can be applied to fiber optic network systems that only contain sub-devices with uplink speeds of 1.25G and 2.5G.
[0232] In this example, the third indication information is implemented using 1 bit, which can configure extended burst overhead parameters for sub-devices with uplink speeds of 2.5G and 1.25G respectively, which is beneficial to improving the burst efficiency of sub-devices at various speeds in the system.
[0233] It should be understood that the least significant reserved bit (i.e., the 7th bit) in Tables 5-1, 5-2, and 5-3 can also be filled with either "0" or "1". That is, the third indication information uses the least significant two bits of the 5th byte to represent the two possible values. Taking filling the least significant bit with "0" as an example, Tables 5-1, 5-2, and 5-3 can be modified as shown in Tables 6-1, 6-2, and 6-3 below:
[0234] Table 6-1
[0235]
[0236] In the example shown in Table 6-1, the lowest two bits of the fifth byte (i.e., "RR") represent the third indication information, indicating the code pattern for the applicability of the extended overhead length message to a specific uplink rate (i.e., the uplink rate indicated by "RR"). If RR=00, it means that the extended overhead length message is applicable to sub-devices with any uplink rate, that is, sub-devices with any uplink rate can configure extended burst overhead parameters based on this extended overhead length message; if RR=01, it means that the extended overhead length message is applicable to sub-devices with a 2.5G uplink rate, that is, sub-devices with only a 2.5G uplink rate can configure extended burst overhead parameters based on this extended overhead length message.
[0237] Table 6-2
[0238]
[0239] In the example shown in Table 6-2, the lowest two bits of the fifth byte (i.e., “RR”) represent the third indication information, indicating the code pattern for the applicability of the extended overhead length message to a specific uplink rate (i.e., the uplink rate indicated by “RR”). If RR=00, it means that the extended overhead length message is applicable to both 2.5G uplink rate sub-devices and 1.25G uplink rate sub-devices, that is, both 2.5G uplink rate sub-devices and 1.25G uplink rate sub-devices can configure extended burst overhead parameters based on this extended overhead length message; if RR=01, it means that the extended overhead length message is applicable to 2.5G uplink rate sub-devices, that is, only 2.5G uplink rate sub-devices can configure extended burst overhead parameters based on this extended overhead length message.
[0240] Table 6-3
[0241]
[0242] In the example shown in Table 6-3, the last two bits of the fifth byte (i.e., "RR") represent the third indication information, which indicates the code pattern for the applicability of the extended overhead length message to a specific uplink rate (i.e., the uplink rate indicated by "RR"). If RR=00, it means that the extended overhead length message is applicable to sub-devices with a 1.25G uplink rate, that is, only sub-devices with a 1.25G uplink rate can configure extended burst overhead parameters based on this extended overhead length message; if RR=01, it means that the extended overhead length message is applicable to sub-devices with a 2.5G uplink rate, that is, only sub-devices with a 2.5G uplink rate can configure extended burst overhead parameters based on this extended overhead length message.
[0243] It should be understood that the examples shown in Tables 6-1, 6-2, and 6-3 have similar beneficial effects to those shown in Tables 5-1, 5-2, and 5-3 above. For details, please refer to the descriptions of Tables 5-1, 5-2, and 5-3 above, which will not be repeated here.
[0244] In another implementation of this embodiment, the third indication information is represented by the lowest two bits of the second reserved field. Since two bits can represent four values (i.e., "00", "01", "10" and "11"), the third indication information has at most four selectable values, that is, the first uplink rate has at most four selectable values.
[0245] In Example 2.4, taking an optical network system containing at least two uplink rates as an example, the third indication information has at least three selectable values, meaning the first uplink rate has at least three selectable values. Three of the aforementioned four values can be assigned meaning, while one value is reserved. For example, one value (e.g., the aforementioned 2 bits set to "00") indicates that the first uplink rate is any uplink rate, meaning the third indication information indicates that the third message applies to the burst overhead parameters for configuring extended uplink rates for sub-devices with arbitrary uplink rates; another value (e.g., the aforementioned 2 bits set to "01") indicates that the first uplink rate is 2.5G, meaning the third indication information indicates that the third message applies to the burst overhead parameters for configuring extended uplink rates for sub-devices supporting 2.5G uplink rates; yet another value (e.g., the aforementioned 2 bits set to "10") indicates that the first uplink rate is 1.25G, meaning the third indication information indicates that the third message applies to the burst overhead parameters for configuring extended uplink rates for sub-devices supporting 1.25G uplink rates. It should be understood that in some other examples, the meanings of the three values mentioned above can be interchanged, which will not be elaborated here. Furthermore, in other examples, other values can be reserved, with the other three values representing the three meanings mentioned above respectively. For example, "00" is reserved, while "01", "10", and "11" respectively represent a first uplink rate of any uplink rate, a first uplink rate of 2.5G, and a first uplink rate of 1.25G, which will not be elaborated here. Subsequent embodiments will only use the former as an example.
[0246] For example, the bytes carrying third indication information in the third message are shown in Table 7-1 or Table 7-2 below:
[0247] Table 7-1
[0248]
[0249] In the example shown in Table 7-1, the lowest two bits of the fifth byte (i.e., "RR") represent the third indication information, indicating the code pattern for the applicability of the extended burst length message to a specific uplink rate (i.e., the uplink rate indicated by "RR"). If RR=00, it means that the extended burst length message is applicable to sub-devices with any uplink rate, that is, sub-devices with any uplink rate can configure extended burst overhead parameters based on this extended burst length message; if RR=01, it means that the extended burst length message is applicable to sub-devices with a 2.5G uplink rate, that is, sub-devices with only a 2.5G uplink rate can configure extended burst overhead parameters based on this extended burst length message; if RR=10, it means that the extended burst length message is applicable to sub-devices with a 1.25G uplink rate, that is, sub-devices with only a 1.25G uplink rate can configure extended burst overhead parameters based on this extended burst length message. RR=11 is a reserved value.
[0250] This example can be applied to fiber optic network systems that include sub-devices with uplink speeds of at least 1.25G and 2.5G.
[0251] In this example, the third indication information is implemented using 2 bits. This not only allows for the configuration of extended burst overhead parameters for sub-devices with 2.5G uplink speeds and those with 1.25G uplink speeds, respectively, thereby improving the burst efficiency of sub-devices at various speeds in the system, but also enables the configuration of sub-devices with any uplink speed through a single message, saving signaling overhead for configuring extended burst overhead parameters. Furthermore, setting a value to indicate that the first uplink speed is arbitrary improves system compatibility and prevents the introduction of sub-devices supporting other uplink speeds (e.g., sub-devices supporting speeds other than 2.5G and 1.25G) from affecting the configuration of those sub-devices.
[0252] Table 7-2
[0253]
[0254] In the example shown in Table 7-2, the lowest two bits of the fifth byte (i.e., "RR") represent the third indication information, indicating the code pattern for the applicability of the extended burst length message to a specific uplink rate (i.e., the uplink rate indicated by "RR"). The difference from the example shown in Table 7-1 is that RR=00, indicating that the extended burst length message applies to both 2.5G uplink rate sub-devices and 1.25G uplink rate sub-devices. That is, both 2.5G and 1.25G uplink rate sub-devices can configure extended burst overhead parameters based on this extended burst length message. The meanings of the other values are described in the relevant descriptions of the example shown in Table 7-1 above, and will not be repeated here.
[0255] This example can be applied to fiber optic network systems containing sub-devices with uplink speeds of at least 1.25G and 2.5G. When sub-devices supporting other uplink speeds are introduced into the fiber optic network system, the value "11" can be assigned to these sub-devices, thereby improving system compatibility.
[0256] In this example, the third indication information is implemented using 2 bits. This not only allows for the configuration of extended burst overhead parameters for sub-devices with uplink speeds of 2.5G and 1.25G respectively, thereby improving the burst efficiency of sub-devices at various speeds in the system, but also allows for the simultaneous configuration of sub-devices with uplink speeds of 1.25G and 2.5G simultaneously through a single message, thus saving signaling overhead for configuring extended burst overhead parameters.
[0257] In another possible implementation, the third indication information is carried in the message type field of the third message. Optionally, the third message is an extended_Burst_Length message, and the type field is located in the second byte of the extended_Burst_Length message, that is, the third indication information is carried in the second byte of the third message. It can be understood that this implementation defines a new message type, which is used to configure extended burst overhead parameters for sub-devices with a specific uplink rate.
[0258] In Example 2.5, a new message type is defined as an extended burst length message suitable for sub-devices supporting 2.5G uplink rates. For example, the content and meaning of the various fields included in this third message are described in Table 8-1 below:
[0259] Table 8-1
[0260]
[0261] In the example shown in Table 8-1, the third indication information is "00010110", meaning the newly added value "00010110" indicates "uplink burst for 2.5G uplink rate", i.e., the first uplink rate is 2.5G. This can be understood as a newly defined extended burst length message of type "00010110" used to configure extended burst overhead parameters for sub-devices supporting 2.5G uplink rates.
[0262] In addition, the system retains the extended burst length message using the traditional value (i.e., "00010100") and continues to use the message type indicated by the traditional value. This extended burst length message with the traditional value is used to configure sub-devices with 1.25G uplink speeds and sub-devices with 2.5G uplink speeds. It can also be understood that this extended burst length message with the traditional value is used to configure sub-devices with arbitrary uplink speeds.
[0263] In this example, the master device supports sending values including "00010110" and "00010100". For instance, the master device broadcasts an extended burst length message with the value "00010110" to configure extended burst overhead parameters for sub-devices supporting 2.5G uplink rates; the master device also broadcasts an extended burst length message with the value "00010100" to configure extended burst overhead parameters for both sub-devices supporting 2.5G uplink rates and sub-devices supporting 1.25G uplink rates.
[0264] In this example, an extended burst length message is added as a new message type, specifically for configuring extended burst overhead parameters for sub-devices supporting 2.5G uplink speeds. This allows for individual configuration of extended burst overhead parameters for sub-devices supporting 2.5G uplink speeds, thereby improving the burst efficiency of these sub-devices. Furthermore, the traditional value ("00010100") is retained for configuring sub-devices with any uplink speed (i.e., 2.5G and 1.25G uplink speeds) with a single message, which helps save signaling overhead for configuring extended burst overhead parameters.
[0265] In another example, 2.6, in addition to defining the extended burst length message as shown in Table 8-1 above, the function of the message type indicated by the traditional value (i.e., "00010100") can also be modified. For example, as shown in Table 8-2, the definition (or function) of the traditional value (i.e., "00010100") is modified to indicate "uplink burst for 1.25G uplink rate", that is, the first uplink rate is 1.25G. This can be understood as a newly defined extended burst length message with message type "00010100" used to configure extended burst overhead parameters for sub-devices supporting 1.25G uplink rates.
[0266] Table 8-2
[0267]
[0268] It should be understood that the example shown in Table 8-2 only shows a portion of the bytes of the extended burst length message. For the remaining bytes in the example shown in Table 8-2, please refer to the example shown in Table 8-1 above, which will not be repeated here.
[0269] In this example, the master device supports sending values including "00010110" and "00010100". For example, the master device broadcasts an extended burst length message with the value "00010110" to configure extended burst overhead parameters for sub-devices supporting 2.5G uplink rates; the master device broadcasts an extended burst length message with the value "00010100" to configure extended burst overhead parameters for sub-devices supporting 1.25G uplink rates.
[0270] In this example, a new message type, the Extended Burst Length message, is added specifically for configuring extended burst overhead parameters for sub-devices supporting 2.5G uplink speeds. This allows for separate configuration of extended burst overhead parameters for sub-devices supporting 2.5G uplink speeds, thereby improving the burst efficiency of these sub-devices. Furthermore, the definition of the traditional value ("00010100") has been modified. A new value of "00010100" is defined specifically for configuring extended burst overhead parameters for sub-devices supporting 1.25G uplink speeds, thus enabling separate configuration of extended burst overhead parameters for sub-devices supporting 1.25G uplink speeds and improving their burst efficiency.
[0271] In another example, 2.7, in addition to defining the extended burst length message shown in Table 8-1 above, a new value (e.g., "00010111") can be defined to indicate "uplink burst for 1.25G uplink rate". For example, as shown in Table 8-3, a new extended burst length message with message type "00010111" is defined to configure extended burst overhead parameters for sub-devices supporting 1.25G uplink rate. Furthermore, the system retains the use of the traditional value (i.e., "00010100") for extended burst length messages and retains the functionality of the message type indicated by the traditional value. This traditional value extended burst length message is used to configure sub-devices with 1.25G uplink rate and sub-devices with 2.5G uplink rate. It can also be understood that this traditional value extended burst length message is used to configure sub-devices with any uplink rate.
[0272] Table 8-3
[0273]
[0274] It should be understood that the example shown in Table 8-3 only shows a portion of the bytes of the extended burst length message. For the remaining bytes in the example shown in Table 8-3, please refer to the example shown in Table 8-1 above, which will not be repeated here.
[0275] In this example, the master device supports sending values including "00010110", "00010111", and "00010100". For example, the master device broadcasts an extended burst length message with the value "00010110" to configure extended burst overhead parameters for sub-devices supporting 2.5G uplink rates; the master device broadcasts an extended burst length message with the value "00010111" to configure extended burst overhead parameters for sub-devices supporting 1.25G uplink rates; and the master device broadcasts an extended burst length message with the value "00010100" to configure extended burst overhead parameters for both sub-devices supporting 1.25G uplink rates and sub-devices supporting 2.5G uplink rates simultaneously.
[0276] In this example, a new message type, the Extended Burst Length message, is added specifically for configuring extended burst overhead parameters for sub-devices supporting 2.5G uplink speeds. This allows for separate configuration of extended burst overhead parameters for sub-devices supporting 2.5G uplink speeds, thereby improving the burst efficiency of these sub-devices. Furthermore, the definition of the traditional value ("00010100") has been modified. A new value of "00010100" is defined specifically for configuring extended burst overhead parameters for sub-devices supporting 1.25G uplink speeds, thus enabling separate configuration of extended burst overhead parameters for sub-devices supporting 1.25G uplink speeds and improving their burst efficiency.
[0277] It should be understood that the main device in this application can implement the third message and the third instruction information using any of the foregoing implementation methods or examples, and this application is not limited thereto.
[0278] In this step, after receiving the third message, 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 (i.e., the first uplink rate) corresponding to the third message, and then the first sub-device determines whether to trigger the configuration process. If the first sub-device supports the first uplink rate, the first sub-device executes step 204a; if the first sub-device does not support the first uplink rate, the first sub-device executes step 204b.
[0279] Step 204a: If the first sub-device supports the first uplink rate, the first sub-device configures the extended burst overhead parameters of the first sub-device based on the third message.
[0280] In this embodiment, step 204a is an optional step.
[0281] In one example, taking Table 6-1 as an example, if the third indication information is "00" as shown in Table 6-1, it means that the extended burst length message is applicable to any normal uplink rate, that is, the first uplink rate is any uplink rate. If the first sub-device supports a 2.5G uplink rate, then the first sub-device supports the first uplink rate; if the first sub-device supports a 1.25G uplink rate, then the first sub-device also supports the first uplink rate. At this time, regardless of whether the first sub-device supports a 2.5G uplink rate or a 1.25G uplink rate, the first sub-device can configure the extended burst overhead parameters of the first sub-device based on the third message.
[0282] In another example, taking Table 6-1 as an example, if the third indication information is "01" as shown in Table 6-1, it means that the extended burst length message is applicable to the 2.5G uplink rate, that is, the first uplink rate is 2.5G. In this case, the first sub-device can only configure the extended burst overhead parameters of the first sub-device based on the third message if the first sub-device supports the 2.5G uplink rate.
[0283] In another example, taking Table 6-3 as an example, if the third indication information is "00" as shown in Table 6-3, it means that the extended burst length message is applicable to the 1.25G uplink rate, that is, the first uplink rate is 1.25G. In this case, the first sub-device can only configure the extended burst overhead parameters of the first sub-device based on the third message if the first sub-device supports the 1.25G uplink rate.
[0284] In another example, taking Table 8-1 as an example, if the third indication information is "00010110" as shown in Table 8-1, it means that the extended burst length message is applicable to the 2.5G uplink rate, that is, the first uplink rate is 2.5G. In this case, the first sub-device can only configure the extended burst overhead parameters of the first sub-device based on the third message if the first sub-device supports the 2.5G uplink rate.
[0285] For other examples in this step, please refer to the relevant description in step 203 above, which will not be repeated here.
[0286] Specifically, the first sub-device configures the type 3 preamble overhead based on the number of bytes in the type 3 preamble in the third message. For example, if the first sub-device is in the sequence number state (i.e., state O3) or the ranging state (i.e., state O4), then the first sub-device configures the type 3 preamble overhead based on the value in the third byte of the third message. As another example, if the first sub-device is in the operation state (i.e., state O5), then the first sub-device configures the type 3 preamble overhead based on the value in the fourth byte of the third message.
[0287] Step 204b: If the first sub-device does not support the first uplink rate, then the first sub-device does not perform a configuration operation based on the third message.
[0288] In this embodiment, step 204b is an optional step.
[0289] This can also be understood as follows: when the first sub-device receives the third message and does not support the first uplink rate, the first sub-device directly ignores the third message and does not configure the extended burst overhead parameters based on the third message.
[0290] In this embodiment, the third message received by the first sub-device includes third indication information. This third indication information indicates that the first message is applicable to configuring extended burst overhead parameters for sub-devices supporting the first uplink rate. The first sub-device only triggers the configuration of extended burst overhead parameters based on the third message if it determines that it supports the first uplink rate. In other words, the third message received by the first sub-device only triggers the configuration of extended burst overhead parameters for sub-devices supporting the first uplink rate, and will not trigger the configuration of extended burst overhead parameters for sub-devices supporting other uplink rates (i.e., uplink rates other than the first uplink rate). This facilitates the separate configuration of extended uplink overhead for sub-devices supporting different uplink rates, thereby improving the efficiency of uplink bursts.
[0291] Furthermore, such as Figure 3 As shown, when there are sub-devices supporting different uplink rates in the optical fiber network system provided in this application, each device in the optical fiber network system will perform the following steps:
[0292] Step 301: The master device sends a first message; correspondingly, the first sub-device receives the first message; the second sub-device receives the first message.
[0293] The first message includes the first instruction information. For an explanation of the first message and the first instruction information, please refer to the relevant introduction in step 201 above, which will not be repeated here.
[0294] Furthermore, the uplink rates supported by the first sub-device differ from those supported by the second sub-device. For ease of explanation, the following description will use an example where the first sub-device supports the second uplink rate and the second sub-device supports the first uplink rate. Note that the first uplink rate differs from the second uplink rate.
[0295] For example, the master device broadcasts a first message, which is received by both the first and second sub-devices. After receiving the first message, the first sub-device executes step 302; after receiving the first message, the second sub-device executes step 303. It should be understood that there is no specific time order between steps 302 and 303; step 302 can be executed after step 301, and step 303 can be executed after step 301.
[0296] Step 302: The first sub-device does not perform configuration operations based on the first message.
[0297] Since the first sub-device does not support the first uplink rate, the first sub-device does not perform configuration operations based on the first message.
[0298] Step 303: The second sub-device configures the uplink burst overhead parameters of the second sub-device based on the first message.
[0299] Since the second sub-device supports the first uplink rate, after receiving the first message, the second sub-device configures the uplink burst overhead parameters of the second sub-device based on the first message.
[0300] Steps 304 and 305 are optional.
[0301] Step 304: The master device sends a second message; correspondingly, the first sub-device receives the second message.
[0302] The second message includes second indication information, which indicates that the second message applies to configuring uplink burst overhead parameters for sub-devices supporting the second uplink rate. The difference between the second message and the first message is that the second indication information carried in the second message indicates the second uplink rate. The way the second indication information is carried in the second message is similar to the way the first indication information is carried in the first message; please refer to the previous introduction regarding the first indication information for details, which will not be repeated here.
[0303] Step 305: The first sub-device configures the uplink burst overhead parameters of the first sub-device based on the second message.
[0304] Since the first sub-device supports the second uplink rate, the first sub-device configures the uplink burst overhead parameters of the first sub-device based on the second message.
[0305] It should be noted that there is no time order requirement between steps 301 to 303 and steps 303 to 305. That is, the master device may broadcast the first message first or the second message first; this application does not impose any restrictions.
[0306] To facilitate understanding, the following example uses the scenario where the first sub-device supports an uplink speed of 1.25G and the second sub-device supports an uplink speed of 2.5G, combined with the example of the first indication information introduced earlier:
[0307] For example, taking the example shown in Table 2-1, if the first indication information carried by the first message is "01", then the first sub-device does not trigger configuration based on the first message, and the second sub-device configures the uplink burst overhead message based on the first message; if the second indication information carried by the second message is "00", then the first sub-device configures the uplink burst overhead message in the second message.
[0308] For example, taking the example shown in Table 3-1, if the first indication information carried by the first message is "01", then the first sub-device does not trigger configuration based on the first message, and the second sub-device configures the uplink burst overhead message based on the first message; if the second indication information carried by the second message is "00" or "10", then the first sub-device configures the uplink burst overhead message in the second message.
[0309] For example, taking the example shown in Table 4-1, if the first indication information carried by the first message is "00010101", then the first sub-device does not trigger configuration based on the first message, and the second sub-device configures the uplink burst overhead message based on the first message; if the second indication information carried by the second message is "00000001", then the first sub-device configures the uplink burst overhead message in the second message.
[0310] In practical applications, there are many other examples, which will not be listed one by one in this embodiment.
[0311] In this embodiment, the master device can send uplink burst overhead messages applicable to different uplink rates to sub-devices with different uplink rates, thereby enabling the configuration of uplink burst overhead parameters for sub-devices with different uplink rates. This facilitates the individual configuration of uplink overhead for sub-devices supporting different uplink rates, thus improving the efficiency of uplink bursts.
[0312] Furthermore, embodiments of this application also provide a communication device 40, such as... Figure 4 As shown, Figure 4 This is a schematic diagram of the structure of a communication device 40 provided in an embodiment of this application. Figure 2 and Figure 3 The specific implementations of the master device and sub-devices (e.g., the first sub-device or the second sub-device) in the flowchart shown can be found in [reference]. Figure 4 The internal structure of the communication device 40 is shown. When the communication device 40 is used to implement... Figure 2 or Figure 3 When the communication device 40 is used to implement the function of the master device in the method shown, it can be a master gateway or an MFU. Figure 2 or Figure 3 When the sub-device in the method shown functions, the communication device 40 can be a gateway or an SFU.
[0313] like Figure 4As shown, the communication device 40 may include a processor 401 and a transceiver 402, with the processor 401 coupled to the transceiver 402. The processor 401 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 401 may refer to a single processor or may include multiple processors; no specific limitation is made here.
[0314] The aforementioned transceiver 402 can also be referred to as a transceiver unit, transceiver, or transceiver device. Optionally, the device in the transceiver unit that performs the receiving function can be considered as a receiving unit, and the device in the transceiver unit that performs the transmitting function can be considered as a transmitting unit. That is, the transceiver unit includes a receiving unit and a transmitting unit. The receiving unit can also be referred to as a receiver, input port, or receiving circuit, and the transmitting unit can be referred to as a transmitter, transmitter, or transmitting circuit, etc. Optionally, when the communication device 40 is used to implement... Figure 2 or Figure 3 When the master device in the illustrated method functions, the transceiver 402 can be used for uplink burst optical signal reception. Optionally, the transceiver 402 supports the reception of one or more uplink burst optical signals. For example, the transceiver 402 supports uplink burst optical signal reception of 2.48832 Gbit / s. Another example is that the transceiver 402 supports uplink burst optical signal reception of 1.24416 Gbit / s.
[0315] Optionally, the communication device 40 further includes a memory 403. The processor 401 is coupled to the memory 403. The memory 403 is primarily used to store software programs and data. The memory 403 can exist independently, connected to the processor 401. Optionally, the memory 403 can be integrated with the processor 401, for example, integrated within one or more chips. The memory 403 can store program code executing the technical solutions of the embodiments of this application, and its execution is controlled by the processor 401. The various types of computer program code being executed can also be considered as drivers for the processor 401. The memory 403 can include volatile memory, such as random-access memory (RAM); the memory can also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid-state drive (SSD); the memory 403 can also include combinations of the above types of memory. The memory 403 can refer to a single memory or can include multiple memories. For example, memory 403 is used to store various types of data.
[0316] In one implementation, the communication device 40 is used to implement the function of a first sub-device in an optical fiber network system. Specifically, the transceiver 402 is used to receive a first message, the first message including first indication information, the first indication information being used to indicate that the first message is applicable to configuring uplink burst overhead parameters for a sub-device supporting a first uplink rate; the processor 401 is used to configure the uplink burst overhead parameters of the first sub-device based on the first message, if it is determined that the first uplink rate is supported.
[0317] Alternatively, processor 401 is configured not to perform configuration operations based on the first message if it is determined that the first uplink rate is not supported.
[0318] In one possible implementation, the first sub-device supports a second uplink rate, which is different from the first uplink rate.
[0319] The transceiver 402 is also configured to receive a second message, the second message including second indication information, the second indication information being used to indicate that the second message is applicable to configuring uplink burst overhead parameters for a sub-device supporting the second uplink rate; the processor 401 is also configured to configure uplink burst overhead parameters for a first sub-device based on the second message, if it is determined that the second uplink rate is supported.
[0320] In one possible implementation, the plurality of sub-devices further includes a second sub-device that supports a first uplink rate, and a first message is used for the second sub-device to configure uplink burst overhead parameters of the second sub-device.
[0321] In one possible implementation, the first indication information is carried in a reserved field of the uplink burst overhead message.
[0322] In one possible implementation, the first message includes a message type field, which is used to carry first indication information.
[0323] In one possible implementation, the transceiver 402 is further configured to receive a third message, the third message including third indication information, the third indication information being used to indicate that the third message is applicable to the sub-device configuration of extended burst overhead parameters supporting the first uplink rate; the processor 401 is further configured to configure the extended burst overhead parameters of the first sub-device based on the third message if it is determined that the first uplink rate is supported.
[0324] Alternatively, processor 401 is also configured to not perform configuration operations based on a third message if it is determined that the first uplink rate is not supported.
[0325] In one possible implementation, the third indication information is carried in a reserved field of the burst overhead length message.
[0326] In one possible implementation, the third message includes a message type field, which is used to carry third indication information.
[0327] In another implementation, the communication device 40 is used to implement the functions of a master device in a fiber optic network system. Specifically, the processor 401 is used to generate first allocation information; the transceiver 402 is used to generate a first message, the first message including first indication information, the first indication information being used to indicate that the first message is applicable to configuring uplink burst overhead parameters for a sub-device supporting a first uplink rate; the transceiver 402 is used to send the first message. Wherein, if the first sub-device supports the first uplink rate, the first message is used for the first sub-device to configure its uplink burst overhead parameters.
[0328] In one possible implementation, if the first sub-device does not support the first uplink rate, the first message is used for the first sub-device not to perform configuration operations based on the first message.
[0329] In one possible implementation, the first sub-device supports a second uplink rate, which is different from the first uplink rate.
[0330] The processor 401 is further configured to generate a second message, the second message including second indication information, the second indication information being used to indicate that the second message is applicable to configuring uplink burst overhead parameters for a sub-device supporting a second uplink rate; the transceiver 402 is further configured to send a second message, the second message being used for configuring uplink burst overhead parameters for a first sub-device.
[0331] In one possible implementation, the plurality of sub-devices further includes a second sub-device that supports a first uplink rate, and a first message is used for the second sub-device to configure uplink burst overhead parameters of the second sub-device.
[0332] In one possible implementation, the first indication information is carried in a reserved field of the uplink burst overhead message.
[0333] In one possible implementation, the first message includes a message type field, which is used to carry first indication information.
[0334] In one possible implementation, processor 401 is further configured to generate a third message, the third message including third indication information, the third indication information being used to indicate that the third message is applicable to the configuration of extended burst overhead parameters for a sub-device supporting the first uplink rate. Transceiver 402 is further configured to send the third message. Wherein, if the first sub-device supports the first uplink rate, the third message is used for the first sub-device to configure extended burst overhead parameters for the first sub-device; or, if the first sub-device does not support the first uplink rate, the third message is used for the first sub-device not to perform a configuration operation based on the third message.
[0335] In one possible implementation, the third indication information is carried in a reserved field of the burst overhead length message.
[0336] In one possible implementation, the third message includes a message type field, which is used to carry third indication information.
[0337] Please refer to the preceding text for details. Figure 2 and Figure 3 The relevant descriptions in the corresponding embodiments will not be repeated here.
[0338] like Figure 5 As shown, this application also provides a communication device 50. The communication device 50 can be a sub-device (e.g., a first sub-device) or a main device, or it can be a component (e.g., an integrated circuit, a chip, etc.) of a sub-device (e.g., a first sub-device) or a main device. The communication device 50 can also be other communication modules used to implement the methods in the method embodiments of this application.
[0339] The communication device 50 may include a processing module 501 (or processing unit). Optionally, it may also include an interface module 502 (or transceiver unit or transceiver module) and a storage module 503 (or storage unit). The interface module 502 is used to enable communication with other devices. The interface module 502 may be, for example, a transceiver module or an input / output module.
[0340] In one possible design, such as Figure 5 One or more modules may be implemented by one or more processors, or by one or more processors and memory; or by one or more processors and transceivers; or by one or more processors, memory, and transceivers. This application does not limit the implementation in this way. The processors, memory, and transceivers can be configured individually or integrated into one unit.
[0341] The communication device 50 has the functionality to implement the sub-device (e.g., the first sub-device) described in the embodiments of this application. For example, the communication device 50 includes modules, units, or means corresponding to the steps involved in the sub-device (e.g., the first sub-device) described in the embodiments of this application. These functions, units, or means can be implemented by software, hardware, or hardware executing corresponding software implementations, or a combination of software and hardware. Further details can be found in the corresponding descriptions in the foregoing method embodiments. Please refer to the preceding text for specific details. Figure 4 The corresponding embodiment is the communication device 40.
[0342] Alternatively, the communication device 50 may have the functions of the main device described in the embodiments of this application. For example, the communication device 50 includes modules, units, or means corresponding to the steps involved in the main device described in the embodiments of this application. These functions, units, or means can be implemented by software, hardware, or hardware executing corresponding software, or a combination of software and hardware. Further details can be found in the corresponding descriptions in the foregoing method embodiments. Please refer to the preceding text for specific details. Figure 4 The corresponding embodiment is the communication device 40.
[0343] Furthermore, this application provides a computer program product comprising one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. For example, implementing the aforementioned... Figure 2 or Figure 3 Methods related to the sub-device (e.g., the first sub-device) in the process. For example, implementing methods as described above. Figure 2 or Figure 3The method relates to the main device in the process. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital versatile disc (DVD)), or a semiconductor medium (e.g., solid-state disk (SSD)).
[0344] Furthermore, this application also provides a computer-readable storage medium storing a computer program that is executed by a processor to perform the aforementioned functions. Figure 2 or Figure 3 Methods related to sub-devices (e.g., the first sub-device) in the process.
[0345] Furthermore, this application also provides a computer-readable storage medium storing a computer program that is executed by a processor to perform the aforementioned functions. Figure 2 or Figure 3 Methods related to the master device in the process.
[0346] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0347] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.
Claims
1. An uplink overhead configuration method applied to an optical fiber network, the optical fiber network comprising a master device and at least one sub-device, the at least one sub-device comprising a first sub-device, characterized in that, include: The first sub-device receives a first message, the first message including first indication information, the first indication information being used to indicate that the sub-device to which the first message applies is a sub-device with any uplink rate, and the first message is an Upstream_Overhead message; The first sub-device configures the uplink burst overhead parameters of the first sub-device based on the first message.
2. The method according to claim 1, characterized in that, The uplink burst overhead parameter includes at least one of the following: Protection time overhead, preamble overhead, separator overhead, pre-allocated delay, and transmitted optical power.
3. The method according to claim 1, characterized in that, The method further includes: The first sub-device receives a third message, the third message including third indication information, the third indication information being used to indicate that the sub-device to which the third message applies is a sub-device with any uplink rate; The first sub-device configures the extended burst overhead parameters of the first sub-device based on the third message.
4. The method according to claim 3, characterized in that, The third message is the Extended_Burst_Length message.
5. The method according to claim 3 or 4, characterized in that, The extended burst overhead parameter is used to indicate the number of type 3 preamble bytes used in the uplink direction.
6. The method according to claim 1, characterized in that, The at least one sub-device further includes a second sub-device, the second sub-device supporting an uplink rate different from the uplink rate supported by the first sub-device, and the sub-devices to which the first indication information applies to the first message include the first sub-device and the second sub-device.
7. The method according to any one of claims 1 to 4, characterized in that, The arbitrary uplink rate includes 2.48832 Gbit / s and / or 1.24416 Gbit / s.
8. A communication device, characterized in that, include: A processor and a transceiver, the processor being connected to the transceiver, the processor being configured to implement the method as described in any one of claims 1 to 7.
9. The communication device according to claim 8, characterized in that, The communication device is a chip.
10. A communication system, characterized in that, include: The main device and the communication apparatus as described in claim 8.
11. A computer-readable storage medium, characterized in that, The computer program is stored thereon and can be executed by a processor to cause the computer to perform the method as described in any one of claims 1 to 7.
12. A computer program product, characterized in that, It includes computer program instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1 to 7.
Citation Information
Patent Citations
System and Method for Passive Optical Network Communication
US20140126910A1