A method of optical network communication and a communication device

Abstract

The application provides an optical network communication method and a communication device. In the method, a first slave device can receive a rate amplification factor from a master device, the rate amplification factor being an adjustment factor of a first rate (i.e. an attribute value of a CIR attribute / PIR attribute). The first slave device determines a second rate (i.e. an effective CIR / PIR of the first slave device) by using the rate amplification factor and the first rate. Therefore, even if the first rate has a limited value, the effective CIR / PIR of the first slave device can be adjusted by using the rate amplification factor. That is, without changing the existing attribute, the value of the CIR / PIR used by the first slave device in operation is expanded. The CIR / PIR configuration problem of 50G PON and future higher-rate PONs is solved.

Description

[0001] This application is a divisional application. The original application has the application number 202410638484.6 and the original application date is May 21, 2024. 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 optical network communication method and communication device. Background Technology

[0003] Broadband access technology has developed rapidly in recent years, and passive optical networks (PONs) have achieved large-scale popularization and rapid expansion. With the continuous and rapid increase in user data demand, 10-Gigabit-capable passive optical networks (XG-PONs) have entered the stage of large-scale deployment, and the standards for next-generation PON systems (such as 50-Gigabit-capable passive optical networks (50GPONs)) are also being gradually formulated and improved.

[0004] In current standards, the optical line terminal (OLT) in a PON network manages the ONUs in the PON network through the ONU management and control interface (OMCI) protocol. The OMCI protocol is a master / slave, stop, and wait management protocol. Generally, the OLT is the master device, and the ONU is the slave device. The basic process is that the OLT sends a management message and waits for the ONU's response. When the OLT receives a response or a timeout occurs, it sends the next message. The OLT manages and configures the managed entities (MEs) of the ONUs through OMCI messages.

[0005] In the current standard, the OMCI protocol defines the committed information rate (CIR) and peak information rate (PIR) attributes for managed entities of traffic descriptors, used for managing the CIR and PIR attributes of ONUs. The OLT configures or retrieves the values ​​of CIR or PIR attributes by sending OMCI messages related to the managed entities of the traffic descriptors to the ONU. Since the length of both the CIR and PIR attribute fields defined in the current standard is 4 bytes, and the unit for both CIR and PIR attributes is bytes per second, the maximum values ​​for CIR and PIR attributes are 4,294,967,295, respectively. This means the maximum CIR or PIR that can be configured using these two attributes is 4,294,967,295 bytes / s, approximately equal to 34 Gbit / s. Therefore, it is evident that the field lengths of the CIR and PIR attributes in the current traffic descriptor managed entity are insufficient to support the configuration of 50G PON and future higher-speed PON. Summary of the Invention

[0006] This application provides an optical network communication method and communication device to solve the CIR / PIR configuration problem of 50G PON and future higher speed PON.

[0007] In a first aspect, this application provides an optical network communication method applied to an optical fiber network, the optical fiber network including a master device and at least one slave device, the at least one slave device including a first slave device. The optical network communication method provided in this aspect can be executed by the first slave device in the optical fiber network, or by a portion of a functional module or chip in the first slave device. Taking execution by the first slave device as an example, the first slave device receives a first message from the master device, the first message including a rate amplification factor, the rate amplification factor being an adjustment coefficient for a first rate, the first rate being a guaranteed information rate (CIR) and / or a peak information rate (PIR); then, the first slave device determines a second rate based on the rate amplification factor and the first rate, the second rate being the effective CIR and / or PIR of the first slave device.

[0008] In this aspect, the first slave device receives a rate amplification factor from the master device. This rate amplification factor is an adjustment coefficient for the first rate (i.e., the attribute value of the CIR / PIR attribute). The first slave device determines the second rate (i.e., the effective CIR / PIR of the first slave device) using the rate amplification factor and the first rate. Therefore, even when the value of the first rate is limited, the effective CIR / PIR of the first slave device can be adjusted through the rate amplification factor. In other words, without changing the existing attributes, the range of CIR / PIR values ​​used by the first slave device during operation is expanded. This solves the CIR / PIR configuration problem for 50G PON and future higher-speed PONs.

[0009] In one possible implementation, the default value for the rate amplification factor is 1.

[0010] In one possible implementation, the rate amplification factor is an integer greater than 0. For example, if the rate amplification factor is 1, the second rate is equal to the first rate, meaning the first slave device operates according to the CIR and / or PIR values ​​indicated by the first message. If the rate amplification factor is greater than 1, for example, if the rate amplification factor is a (a is an integer greater than 1), the second rate is a times the first rate, meaning the first slave device operates according to a times the CIR value indicated by the first message, and / or a times the PIR value. Therefore, when the first message carries the rate amplification factor, the master device can indicate integer multiples of the CIR value and / or PIR value to the first slave device, ensuring that the effective CIR and / or PIR of the first slave device is not limited to the maximum rate indicated by 4 bytes. Thus, the CIR / PIR configuration problem for 50G PON and future higher-speed PONs is solved.

[0011] In one possible implementation, the second rate is equal to the product of the first rate and the rate amplification factor.

[0012] In one possible implementation, the first message also includes identification information of the traffic descriptor managed entity. Since the CIR and PIR attributes are properties of the traffic descriptor managed entity, the first message carries the identification information of the traffic descriptor managed entity. That is, the rate amplification factor can be a newly defined attribute of the traffic descriptor managed entity, facilitating the master device to configure the rate amplification factor through the same message when configuring CIR / PIR for the slave device, thereby improving the efficiency of the master device configuring effective CIR / PIR for the slave device.

[0013] In one possible implementation, the first message may also include a first rate. For example, when the message type of the first message is a setup request or a creation request, the master device can configure both the rate amplification factor and the first rate simultaneously through the first message, which helps to improve configuration efficiency.

[0014] In this scenario, the managed entity identification information field of the first message includes the traffic descriptor and the managed entity's identification information. The message content field of the first message includes the attribute value of the rate amplification factor attribute, and also includes the attribute value of the CIR attribute and / or the attribute value of the PIR attribute.

[0015] Optionally, if the message type of the first message is a setting request, the message content field of the first message also includes a first attribute mask, in which the bit corresponding to the rate amplification factor attribute is 1. Furthermore, the bit corresponding to the CIR attribute in the first attribute mask is 1, and / or, the bit corresponding to the PIR attribute in the first attribute mask is 1.

[0016] In another possible implementation, the first message type is a setting request, and the first message may not carry the first rate. Optionally, the first rate is a default value, or the first slave device obtains the first rate through other messages. For example, before receiving the first message from the master device, the first slave device receives a seventh message from the master device, which includes the identification information of the managed entity of the traffic descriptor and the first rate. Since the first rate and the rate amplification factor can be indicated to the first slave device through different messages, it is beneficial to improve the flexibility of configuring the rate amplification factor.

[0017] In this case, the managed entity identification information field of the first message includes the traffic descriptor and the identification information of the managed entity. The message content field of the first message includes the attribute values ​​of the first attribute mask and the rate amplification factor attribute, wherein the bit corresponding to the rate amplification factor attribute in the first attribute mask is 1.

[0018] In one possible implementation, the rate amplification factor attribute is the 10th attribute of the managed entity in the flow descriptor, that is, the 9th attribute after the managed entity identification information attribute of the managed entity in the flow descriptor. The rate amplification factor attribute corresponds to the 9th bit in the first attribute mask.

[0019] In one possible implementation, the first message is encapsulated in the payload field of a downlink XGEM frame, and the XGEM port identifier in the frame header of the downlink XGEM frame is the same as the identifier information of the first slave device.

[0020] In one possible implementation, the master device is an optical line terminal (OLT), and the slave device is an optical network unit (ONU).

[0021] Secondly, this application provides an optical network communication method applied to an optical fiber network, the optical fiber network including a master device and at least one slave device, the at least one slave device including a first slave device. The optical network communication method provided in this aspect can be executed by the master device in the optical fiber network, or by a portion of a functional module or chip in the master device. Taking execution by the master device as an example, the master device sends a first message to the first slave device. The first message includes a rate amplification factor, which is an adjustment coefficient for a first rate. The first rate is the guaranteed information rate (CIR) and / or peak information rate (PIR). The rate amplification factor and the first rate are used to determine a second rate for the first slave device, the second rate being the effective CIR and / or PIR of the first slave device.

[0022] In one possible implementation, the default value for the rate amplification factor is 1.

[0023] In one possible implementation, the rate amplification factor is an integer greater than 0.

[0024] In one possible implementation, the second rate is equal to the product of the first rate and the rate amplification factor.

[0025] In one possible implementation, the first message also includes identification information of the traffic descriptor managed entity.

[0026] In one possible implementation, the first message may also include a first rate. For example, when the message type of the first message is a setup request or a creation request, the master device can configure both the rate amplification factor and the first rate simultaneously through the first message, which helps to improve configuration efficiency.

[0027] In this scenario, the managed entity identification information field of the first message includes the traffic descriptor and the managed entity's identification information. The message content field of the first message includes the attribute value of the rate amplification factor attribute, and also includes the attribute value of the CIR attribute and / or the attribute value of the PIR attribute.

[0028] Optionally, if the message type of the first message is a setting request, the message content field of the first message also includes a first attribute mask, in which the bit corresponding to the rate amplification factor attribute is 1. Furthermore, the bit corresponding to the CIR attribute in the first attribute mask is 1, and / or, the bit corresponding to the PIR attribute in the first attribute mask is 1.

[0029] In another possible implementation, the first message type is a setting request, and the first message may not carry the first rate. Optionally, the first rate is a default value, or the first slave device obtains the first rate through other messages. For example, before receiving the first message from the master device, the first slave device receives a seventh message from the master device, which includes the identification information of the managed entity of the traffic descriptor and the first rate. Since the first rate and the rate amplification factor can be indicated to the first slave device through different messages, it is beneficial to improve the flexibility of configuring the rate amplification factor.

[0030] In this case, the managed entity identification information field of the first message includes the traffic descriptor and the identification information of the managed entity. The message content field of the first message includes the attribute values ​​of the first attribute mask and the rate amplification factor attribute, wherein the bit corresponding to the rate amplification factor attribute in the first attribute mask is 1.

[0031] In one possible implementation, the rate amplification factor attribute is the 10th attribute of the managed entity in the flow descriptor, that is, the 9th attribute after the managed entity identification information attribute of the managed entity in the flow descriptor. The rate amplification factor attribute corresponds to the 9th bit in the first attribute mask.

[0032] In one possible implementation, the first message is encapsulated in the payload field of a downlink XGEM frame, and the XGEM port identifier in the frame header of the downlink XGEM frame is the same as the identifier information of the first slave device.

[0033] In one possible implementation, the master device is an optical line terminal (OLT), and the slave device is an optical network unit (ONU).

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

[0035] Thirdly, this application provides an optical network communication method applied to an optical fiber network, the optical fiber network including a master device and at least one slave device, the at least one slave device including a first slave device. The optical network communication method provided in this aspect can be executed by the first slave device in the optical fiber network, or by a portion of a functional module or chip in the first slave device. Taking execution by the first slave device as an example, the first slave device receives a second message from the master device, the second message including first indication information, the first indication information being used to instruct the first slave device to report a rate amplification factor, the rate amplification factor being an adjustment coefficient for a first rate, the first rate being a guaranteed information rate (CIR) and / or a peak information rate (PIR); then, the first slave device sends a third message to the master device, the third message including the rate amplification factor of the first slave device.

[0036] In this aspect, the first slave device receives a first indication message from the master device, instructing the first slave device to report a rate amplification factor, which is an adjustment coefficient for the first rate (i.e., the attribute value of the CIR / PIR attribute). After receiving the first indication message, the first slave device reports its rate amplification factor. The master device can then combine the rate amplification factor and the first rate to determine the effective CIR / PIR of the first slave device, thereby providing the master device with the effective CIR / PIR of the first slave device. In other words, without changing the existing attributes, the range of CIR / PIR values ​​used by the first slave device during operation is expanded, and the CIR / PIR reporting problem for 50G PON and future higher-speed PONs is solved.

[0037] In one possible implementation, the default value for the rate amplification factor is 1.

[0038] In one possible implementation, the rate amplification factor is an integer greater than 0.

[0039] In one possible implementation, the rate amplification factor and the first rate are used to determine the second rate of the first slave device, the second rate being the effective CIR and / or PIR of the first slave device.

[0040] In one possible implementation, the second rate is equal to the product of the first rate and the rate amplification factor.

[0041] In one possible implementation, the second message further includes identification information of the traffic descriptor managed entity, and the third message further includes identification information of the traffic descriptor managed entity.

[0042] In one possible implementation, where the first indication information is used only to indicate the rate amplification factor reported by the first slave device, the first indication information is a first attribute mask, where the bit corresponding to the rate amplification factor attribute in the first attribute mask is 1, indicating a request for the first slave device to report the attribute value of the rate amplification factor attribute. Optionally, the rate amplification factor attribute corresponds to the 9th bit in the first attribute mask.

[0043] In this embodiment, the first attribute mask only indicates the attribute value of the reported rate amplification factor attribute, and does not necessarily report it together with the attribute value of the CIR attribute or the attribute value of the PIR attribute, which helps to improve the flexibility of the attribute value reported by the device.

[0044] In another possible implementation, the first indication information is further used to indicate that the first slave device reports a first rate; that is, the first indication information is used to indicate that the first slave device reports a rate amplification factor and a first rate. In this case, the third message includes the first rate in addition to the rate amplification factor. When the first indication information is used to indicate that the first slave device reports a rate amplification factor and a first rate, the first indication information is a first attribute mask, in which the bit corresponding to the rate amplification factor attribute is 1. Furthermore, the bit corresponding to the CIR attribute in the first attribute mask is 1, and / or, the bit corresponding to the PIR attribute in the first attribute mask is 1. Optionally, the rate amplification factor attribute corresponds to the 9th bit in the first attribute mask.

[0045] In this embodiment, the attribute value of the reported rate amplification factor, the attribute value of the CIR attribute, and / or the attribute value of the PIR attribute are indicated by the first attribute mask. The first slave device can feed back the rate amplification factor (i.e., the attribute value of the rate amplification factor) and the first rate (i.e., the attribute value of the CIR attribute and / or the attribute value of the PIR attribute) through the third message. This helps to improve the efficiency of the master device in obtaining attribute values ​​and avoids wasting signaling overhead due to multiple reporting.

[0046] In one possible implementation, the message type of the second message is a retrieval request, the managed entity identification information field of the second message includes the traffic descriptor managed entity identification information, and the message content field of the second message includes a first attribute mask.

[0047] In one possible implementation, the message type of the third message is "Retrieve Response," the managed entity identification information field of the third message includes the traffic descriptor and the managed entity identification information, and the message content field of the third message includes the attribute values ​​of the first attribute mask and the rate amplification factor attribute. Optionally, the message content field of the third message may also include the attribute values ​​of the CIR attribute and / or the PIR attribute.

[0048] In one possible implementation, the second message is encapsulated in the payload field of the downlink XGEM frame, and the XGEM port identifier in the frame header of the downlink XGEM frame is the same as the identification information of the first slave device; the third message is encapsulated in the payload field of the uplink XGEM frame, and the XGEM port identifier in the frame header of the uplink XGEM frame is the same as the identification information of the first slave device.

[0049] In one possible implementation, the master device is an optical line terminal (OLT), and the slave device is an optical network unit (ONU).

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

[0051] Fourthly, this application provides an optical network communication method applied to an optical fiber network, the optical fiber network including a master device and at least one slave device, the at least one slave device including a first slave device. The optical network communication method provided in this aspect can be executed by the master device in the optical fiber network, or by a part of a functional module or chip in the master device. Taking execution by the master device as an example, the master device sends a second message to the first slave device, the second message including first indication information, the first indication information being used to instruct the first slave device to report a first rate and a rate amplification factor, the rate amplification factor being an adjustment coefficient for the first rate, the first rate being a guaranteed information rate (CIR) and / or a peak information rate (PIR); then, the master device receives a third message from the first slave device, the third message including the rate amplification factor and the first rate of the first slave device.

[0052] In one possible implementation, the default value for the rate amplification factor is 1.

[0053] In one possible implementation, the rate amplification factor is an integer greater than 0.

[0054] In one possible implementation, the rate amplification factor and the first rate are used to determine the second rate of the first slave device, the second rate being the effective CIR and / or PIR of the first slave device.

[0055] In one possible implementation, the second rate is equal to the product of the first rate and the rate amplification factor.

[0056] In one possible implementation, the second message further includes identification information of the traffic descriptor managed entity, and the third message further includes identification information of the traffic descriptor managed entity.

[0057] In one possible implementation, where the first indication information is used only to indicate the rate amplification factor reported by the first slave device, the first indication information is a first attribute mask, where the bit corresponding to the rate amplification factor attribute in the first attribute mask is 1, indicating a request for the first slave device to report the attribute value of the rate amplification factor attribute. Optionally, the rate amplification factor attribute corresponds to the 9th bit in the first attribute mask.

[0058] In another possible implementation, the first indication information is further used to indicate that the first slave device reports a first rate; that is, the first indication information is used to indicate that the first slave device reports a rate amplification factor and a first rate. In this case, the third message includes the first rate in addition to the rate amplification factor. When the first indication information is used to indicate that the first slave device reports a rate amplification factor and a first rate, the first indication information is a first attribute mask, in which the bit corresponding to the rate amplification factor attribute is 1. Furthermore, the bit corresponding to the CIR attribute in the first attribute mask is 1, and / or, the bit corresponding to the PIR attribute in the first attribute mask is 1. Optionally, the rate amplification factor attribute corresponds to the 9th bit in the first attribute mask.

[0059] In one possible implementation, the message type of the second message is a retrieval request, the managed entity identification information field of the second message includes the traffic descriptor managed entity identification information, and the message content field of the second message includes a first attribute mask.

[0060] In one possible implementation, the message type of the third message is "Retrieve Response," the managed entity identification information field of the third message includes the traffic descriptor and the managed entity identification information, and the message content field of the third message includes the attribute values ​​of the first attribute mask and the rate amplification factor attribute. Optionally, the message content field of the third message may also include the attribute values ​​of the CIR attribute and / or the PIR attribute.

[0061] In one possible implementation, the second message is encapsulated in the payload field of the downlink XGEM frame, and the XGEM port identifier in the frame header of the downlink XGEM frame is the same as the identification information of the first slave device; the third message is encapsulated in the payload field of the uplink XGEM frame, and the XGEM port identifier in the frame header of the uplink XGEM frame is the same as the identification information of the first slave device.

[0062] In one possible implementation, the master device is an optical line terminal (OLT), and the slave device is an optical network unit (ONU).

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

[0064] Fifthly, this application provides an optical network communication method applied to an optical fiber network, the optical fiber network including a master device and at least one slave device, the at least one slave device including a first slave device. The optical network communication method provided in this aspect can be executed by the first slave device in the optical fiber network, or by a portion of a functional module or chip in the first slave device. Taking execution by the first slave device as an example, the first slave device receives a fourth message from the master device, the fourth message including a third rate, the third rate being a guaranteed information rate (CIR) and / or a peak information rate (PIR), the unit of the third rate being related to the line rate of the first slave device and a preset threshold; then, the first slave device determines the unit of the third rate based on the line rate of the first slave device and the preset threshold.

[0065] In this aspect, the unit of the third rate received by the first slave device from the master device is related to the line rate of the first slave device and a preset threshold. The first slave device can determine the unit of the third rate based on its line rate and the preset threshold. Therefore, even when the possible values ​​of the third rate are limited, the first slave device can still determine the unit of the third rate based on its line rate and the preset threshold, thereby determining the effective CIR / PIR of the first slave device. This solves the CIR / PIR configuration problem for 50GPON and future higher-speed PONs.

[0066] In one possible implementation, when the line rate of the first slave device is less than or equal to a preset threshold, the unit of the third rate is bytes per second; when the line rate of the first slave device is greater than the preset threshold, the unit of the third rate is N bytes per second, where N is an integer greater than 0.

[0067] In one possible implementation, the default value of N is 1.

[0068] In one possible implementation, the preset threshold is 9.95328 Gbit / s.

[0069] In one possible implementation, the fourth message also includes identification information of the traffic descriptor managed entity.

[0070] In one possible implementation, the message type of the fourth message is a setup request or a creation request, the managed entity identification information field of the fourth message includes the traffic descriptor managed entity identification information, and the message content field of the fourth message includes the attribute value of the CIR attribute and / or the attribute value of the PIR attribute.

[0071] In one possible implementation, when the line rate of the first slave device is greater than a preset threshold, the effective CIR of the first slave device is equal to the product of the attribute value of the CIR attribute and N, and the effective CIR of the first slave device is in bytes per second; when the line rate of the first slave device is greater than the preset threshold, the effective PIR of the first slave device is equal to the product of the attribute value of the PIR attribute and N, and the effective PIR of the first slave device is in bytes per second.

[0072] In one possible implementation, the fourth message is encapsulated in the payload field of the downlink XGEM frame, and the XGEM port identifier in the frame header of the downlink XGEM frame is the same as the identifier information of the first slave device.

[0073] In one possible implementation, the master device is an optical line terminal (OLT), and the slave device is an optical network unit (ONU).

[0074] Sixthly, this application provides an optical network communication method applied to an optical fiber network, the optical fiber network including a master device and at least one slave device, the at least one slave device including a first slave device. The optical network communication method provided in this aspect can be executed by the master device in the optical fiber network, or by a portion of a functional module or chip in the master device. Taking execution by the master device as an example, the master device sends a fourth message to the first slave device, the fourth message including a third rate, the third rate being a guaranteed information rate (CIR) and / or a peak information rate (PIR), the unit of the third rate being related to the line rate of the first slave device and a preset threshold, the line rate of the first slave device and the preset threshold being used to determine the unit of the third rate.

[0075] In one possible implementation, when the line rate of the first slave device is less than or equal to a preset threshold, the unit of the third rate is bytes per second; when the line rate of the first slave device is greater than the preset threshold, the unit of the third rate is N bytes per second, where N is an integer greater than 0.

[0076] In one possible implementation, the default value of N is 1.

[0077] In one possible implementation, the preset threshold is 9.95328 Gbit / s.

[0078] In one possible implementation, the fourth message also includes identification information of the traffic descriptor managed entity.

[0079] In one possible implementation, the message type of the fourth message is a setup request or a creation request, the managed entity identification information field of the fourth message includes the traffic descriptor managed entity identification information, and the message content field of the fourth message includes the attribute value of the CIR attribute and / or the attribute value of the PIR attribute.

[0080] In one possible implementation, when the line rate of the first slave device is greater than a preset threshold, the effective CIR of the first slave device is equal to the product of the attribute value of the CIR attribute and N, and the effective CIR of the first slave device is in bytes per second; when the line rate of the first slave device is greater than the preset threshold, the effective PIR of the first slave device is equal to the product of the attribute value of the PIR attribute and N, and the effective PIR of the first slave device is in bytes per second.

[0081] In one possible implementation, the fourth message is encapsulated in the payload field of the downlink XGEM frame, and the XGEM port identifier in the frame header of the downlink XGEM frame is the same as the identifier information of the first slave device.

[0082] In one possible implementation, the master device is an optical line terminal (OLT), and the slave device is an optical network unit (ONU).

[0083] It should be noted that there are many other specific implementation methods in this aspect, and for details, please refer to the specific implementation methods and their beneficial effects in the fifth aspect, which will not be repeated here.

[0084] In a seventh aspect, this application provides an optical network communication method applied to an optical fiber network, the optical fiber network including a master device and at least one slave device, the at least one slave device including a first slave device. The optical network communication method provided in this aspect can be executed by the first slave device in the optical fiber network, or by a portion of a functional module or chip in the first slave device. Taking execution by the first slave device as an example, the first slave device receives a fifth message from the master device, the fifth message including second indication information, the second indication information being used to instruct the first slave device to report a third rate, the third rate being a guaranteed information rate (CIR) and / or a peak information rate (PIR), the unit of the third rate being related to the line rate of the first slave device and a preset threshold; then, the first slave device sends a sixth message to the master device, the sixth message including the third rate of the first slave device.

[0085] In this aspect, the first slave device can receive a second instruction from the master device, instructing the first slave device to report a third rate (i.e., the attribute value of the CIR / PIR attribute). Since the unit of the third rate is related to the line rate and preset threshold of the first slave device, after receiving the second instruction, the first slave device reports the attribute value of the CIR / PIR attribute. The master device determines the valid CIR / PIR of the first slave device, thereby indirectly providing the master device with the valid CIR / PIR of the first slave device. In other words, without changing the existing attributes, the range of CIR / PIR values ​​used by the first slave device during operation is expanded, and the CIR / PIR reporting problem for 50G PON and future higher-speed PONs is solved.

[0086] In one possible implementation, when the line rate of the first slave device is less than or equal to a preset threshold, the unit of the third rate is bytes per second; when the line rate of the first slave device is greater than the preset threshold, the unit of the third rate is N bytes per second, where N is an integer greater than 0.

[0087] In one possible implementation, the default value of N is 1.

[0088] In one possible implementation, the preset threshold is 9.95328 Gbit / s.

[0089] In one possible implementation, the fifth message also includes identification information of the traffic descriptor managed entity; the sixth message also includes identification information of the traffic descriptor managed entity.

[0090] In one possible implementation, the second indication information is a second attribute mask, in which the bit corresponding to the CIR attribute is 1 and the bit corresponding to the PIR attribute is 1.

[0091] In one possible implementation, the message type of the fifth message is a retrieval request, the managed entity identification information field of the fifth message includes the traffic descriptor managed entity identification information, and the message content field of the fifth message includes second indication information.

[0092] In one possible implementation, the message type of the sixth message is to obtain a response, the managed entity identification information field of the sixth message includes the traffic descriptor managed entity identification information, and the message content field of the sixth message includes the second indication information, the attribute value of the CIR attribute, and the attribute value of the PIR attribute.

[0093] In one possible implementation, when the line rate of the first slave device is greater than a preset threshold, the effective CIR of the first slave device is equal to the product of the attribute value of the CIR attribute and N, and the effective CIR of the first slave device is in bytes per second; when the line rate of the first slave device is greater than the preset threshold, the effective PIR of the first slave device is equal to the product of the attribute value of the PIR attribute and N, and the effective PIR of the first slave device is in bytes per second.

[0094] In one possible implementation, the fifth message is encapsulated in the payload field of the downlink XGEM frame, and the XGEM port identifier in the frame header of the downlink XGEM frame is the same as the identification information of the first slave device; the sixth message is encapsulated in the payload field of the uplink XGEM frame, and the XGEM port identifier in the frame header of the uplink XGEM frame is the same as the identification information of the first slave device.

[0095] In one possible implementation, the master device is an optical line terminal (OLT), and the slave device is an optical network unit (ONU).

[0096] Eighthly, this application provides an optical network communication method applied to an optical fiber network, the optical fiber network including a master device and at least one slave device, the at least one slave device including a first slave device. The optical network communication method provided in this aspect can be executed by the master device in the optical fiber network, or by a part of a functional module or chip in the master device. Taking execution by the master device as an example, the master device sends a fifth message to the first slave device, the fifth message including second indication information, the second indication information being used to instruct the first slave device to report a third rate, the third rate being a guaranteed information rate (CIR) and / or a peak information rate (PIR), the unit of the third rate being related to the line rate of the first slave device and a preset threshold; then, the master device receives a sixth message from the first slave device, the sixth message including the third rate of the first slave device.

[0097] In this aspect, the master device can instruct the first slave device to report the third rate (i.e., the attribute value of the CIR / PIR attribute) via the second indication information. Since the unit of the third rate is related to the line rate and preset threshold of the first slave device, after receiving the second indication information, the first slave device reports the attribute value of the CIR / PIR attribute. The master device then determines the valid CIR / PIR of the first slave device, thereby indirectly providing the master device with the valid CIR / PIR of the first slave device. In other words, without changing the existing attributes, the range of CIR / PIR values ​​used by the first slave device during operation is expanded, and the CIR / PIR reporting problem for 50G PON and future higher-speed PONs is solved.

[0098] In one possible implementation, when the line rate of the first slave device is less than or equal to a preset threshold, the unit of the third rate is bytes per second; when the line rate of the first slave device is greater than the preset threshold, the unit of the third rate is N bytes per second, where N is an integer greater than 0.

[0099] In one possible implementation, the default value of N is 1.

[0100] In one possible implementation, the preset threshold is 9.95328 Gbit / s.

[0101] In one possible implementation, the fifth message also includes identification information of the traffic descriptor managed entity; the sixth message also includes identification information of the traffic descriptor managed entity.

[0102] In one possible implementation, the second indication information is a second attribute mask, in which the bit corresponding to the CIR attribute is 1 and the bit corresponding to the PIR attribute is 1.

[0103] In one possible implementation, the message type of the fifth message is a retrieval request, the managed entity identification information field of the fifth message includes the traffic descriptor managed entity identification information, and the message content field of the fifth message includes second indication information.

[0104] In one possible implementation, the message type of the sixth message is to obtain a response, the managed entity identification information field of the sixth message includes the traffic descriptor managed entity identification information, and the message content field of the sixth message includes the second indication information, the attribute value of the CIR attribute, and the attribute value of the PIR attribute.

[0105] In one possible implementation, when the line rate of the first slave device is greater than a preset threshold, the effective CIR of the first slave device is equal to the product of the attribute value of the CIR attribute and N, and the effective CIR of the first slave device is in bytes per second; when the line rate of the first slave device is greater than the preset threshold, the effective PIR of the first slave device is equal to the product of the attribute value of the PIR attribute and N, and the effective PIR of the first slave device is in bytes per second.

[0106] In one possible implementation, the fifth message is encapsulated in the payload field of the downlink XGEM frame, and the XGEM port identifier in the frame header of the downlink XGEM frame is the same as the identification information of the first slave device; the sixth message is encapsulated in the payload field of the uplink XGEM frame, and the XGEM port identifier in the frame header of the uplink XGEM frame is the same as the identification information of the first slave device.

[0107] In one possible implementation, the master device is an optical line terminal (OLT), and the slave device is an optical network unit (ONU).

[0108] It should be noted that there are many other specific implementation methods in this aspect, and for details, please refer to the specific implementation methods and their beneficial effects in aspect seven, which will not be repeated here.

[0109] Ninthly, embodiments of this application provide a communication device, which can 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 stores instructions, and the processing module executes the instructions stored in the storage module to cause the main device to perform the methods of the second, fourth, sixth, and eighth aspects, and any of the foregoing embodiments. 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 methods of the second, fourth, sixth, and eighth aspects, and any of the foregoing embodiments. 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.).

[0110] In a tenth aspect, embodiments of this application provide a communication device, which may be a slave device (e.g., a first slave device) as described in the foregoing embodiments, or a chip within the slave device (e.g., the first slave device). The communication device may include a processing module and a transceiver module. When the communication device is a slave device (e.g., the first slave device), the processing module may be a processor, and the transceiver module may be a transceiver. Optionally, the slave device (e.g., the first slave device) may further include a storage module, which may be a memory; the storage module stores instructions, and the processing module executes the instructions stored in the storage module to cause the slave device (e.g., the first slave device) to perform the methods of the first aspect, the third aspect, the fifth aspect, the seventh aspect, and any of the embodiments of the foregoing aspects. When the communication device is a chip within the slave device (e.g., the first slave device), the processing module may be a processor, and the transceiver module may be an input / output interface, pin, or circuit, etc.; the processing module executes the instructions stored in the storage module to cause the slave device (e.g., the first slave device) to perform the methods of the first aspect, the third aspect, the fifth aspect, the seventh aspect, and any of the embodiments of the foregoing aspects. The storage module can be an internal storage module of the chip (e.g., registers, caches, etc.) or an external storage module of the slave device (e.g., first slave device) located outside the chip.

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

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

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

[0114] In a fourteenth aspect, embodiments of this application provide an optical fiber network comprising a master device as described in the second aspect and any embodiment thereof, and a slave device (e.g., a first slave device) as described in the first aspect and any embodiment thereof; or, the optical fiber network comprising a master device as described in the fourth aspect and any embodiment thereof, and a slave device (e.g., a first slave device) as described in the third aspect and any embodiment thereof; the optical fiber network comprising a master device as described in the sixth aspect and any embodiment thereof, and a slave device (e.g., a first slave device) as described in the fifth aspect and any embodiment thereof; the optical fiber network comprising a master device as described in the eighth aspect and any embodiment thereof, and a slave device (e.g., a first slave device) as described in the seventh aspect and any embodiment thereof. Attached Figure Description

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

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

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

[0118] Figure 3A An example diagram of the traditional message format for creating a request message;

[0119] Figure 3BAn example diagram of the message format for the creation request message provided in this application;

[0120] Figure 3C An example diagram illustrating the message format for a traditional setup request message;

[0121] Figure 3D An example diagram illustrating the message format of the setup request message provided in this application;

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

[0123] Figure 5A An example diagram of the traditional message format for retrieving request messages;

[0124] Figure 5B An example diagram of the message format for the acquisition request message provided in this application;

[0125] Figure 5C An example diagram of the traditional message format for obtaining response messages;

[0126] Figure 5D An example diagram of the message format for obtaining response messages provided in this application;

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

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

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

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

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

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

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

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

[0135] The optical network communication method provided in this application is applied to optical fiber networks. Figure 1A This is an example diagram of the architecture of a fiber optic network in traditional technology. (Example:) Figure 1AAs shown, this fiber optic network includes an optical line terminal (OLT), an optical distribution network (ODN), and optical network units (ONUs) (or optical network terminals (ONTs)). The OLT and ONUs are connected and communicate via optical fibers. The OLT is typically connected to the ONU (or ONT) through the ODN. The ODN is a network composed of one or more 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 through a network-side interface, and it can also connect to the ODN through a dedicated interface. The ODN connects to the ONU (or ONT) through a dedicated interface, and the ONU (or ONT) connects to the user-side network through a user-side interface or a dedicated interface. In the downlink direction, the OLT broadcasts the downlink optical signal, which is then distributed to each ONU (or ONT) through the ODN. In the uplink direction, time division multiple access (TDMA) is used, and each ONU (or ONT) transmits uplink optical signals in its respective uplink time slot allocated by the OLT.

[0136] like Figure 1B The diagram shown is a structural schematic of the optical fiber network provided in this application. The optical fiber network provided in this application includes a master device 01 and at least one slave device 02. The master device 01 is connected to at least one slave device 02 via optical fiber. The master device 01 can manage one or more slave devices 02 based on the OMCI protocol. It should be understood that the master device can be an OLT, and the slave device can be an ONU (or ONT). The master device is connected to at least one slave device through an optical distribution network. In one example, the slave device can be directly connected to a user's terminal device, which can be a mobile phone or tablet connected to the aforementioned router via WiFi, or an IoT device (e.g., indoor temperature control equipment, indoor monitoring equipment, and other artificial intelligence devices). In another example, there are other networks (e.g., Ethernet) between the slave device and the user's terminal device. The slave device can be an optical modem provided by an operator, which is then connected to an indoor router or other devices. This application uses a master device and a slave device as examples for description.

[0137] It should be understood that this application does not limit the specific type of optical fiber. The optical fiber described in this application may be a single optical fiber, loose-tube optical fiber, optical cable, or optoelectronic composite cable, etc.

[0138] It should also be understood that the optical network communication method provided in this application can be applied to PON networks. For example, Gigabit-capable Passive Optical Networks (GPON), 10-Gigabit-capable Passive Optical Networks (XG-PON), 10-Gigabit-capable Symmetric Passive Optical Networks (XGS-PON), 50-Gigabit-capable Passive Optical Networks (50GPON), and future PON systems with even higher speeds. This application is not limiting.

[0139] To facilitate understanding of the optical network communication method provided in this application, the OMCI protocol and the management model defined in the OMCI protocol will be introduced below:

[0140] The OMCI protocol is a master-slave management protocol. The master device (e.g., OLT) issues commands and waits for the slave device (e.g., ONU) to execute the commands and respond. In the OMCI protocol, the various resources and services of the slave devices managed by the master device are abstracted into a protocol-independent management information base (MIB). The basic information unit of this MIB is the managed entity (also called the managed entity, ME). This managed entity is an abstract representation of the resources and / or services of the slave device, an object of management abstracted from numerous resources and / or services to be managed. When the aforementioned managed entity is concretized to a specific slave device or a specific service, it becomes an instance. The master device implements the configuration management function of each managed entity (ME) by configuring instances on the slave devices.

[0141] This application primarily relates to a Traffic Descriptor (ME) managed entity. The ME is used for traffic management of slave devices. For example, a slave device supporting priority control can configure a data managed entity from a media access control (MAC) bridge port to point to a traffic descriptor managed entity to achieve traffic management such as traffic labeling and policing. As another example, a slave device supporting rate control can configure a data managed entity or a GEM port Connection Termination Point (CTP) managed entity from a MAC bridge port to point to a traffic descriptor managed entity to achieve traffic management such as traffic labeling and traffic shaping.

[0142] In the current standard, the flow descriptor ME includes several attributes as shown in Table 1 below:

[0143] Table 1

[0144] Attribute order property Is it readable and writable? Is it optional? Attribute size 1 Regulated Entity Identifier Readable Required 2 bytes 2 Information rate can be guaranteed (CIR) Readable, writable, set at creation time Optional 4 bytes 3 Peak Information Rate (PIR) Readable, writable, set at creation time Optional 4 bytes 4 It can guarantee the safety of sudden events of all sizes. Readable, writable, set at creation time Optional 4 bytes 5 Peak burst size Readable, writable, set at creation time Optional 4 bytes 6 Color mode Readable, writable, set at creation time Optional 1 byte 7 Entrance color marking Readable, writable, set at creation time Optional 1 byte 8 Export color marking Readable, writable, set at creation time Optional 1 byte 9 Algorithm type Readable, set at creation time Optional 1 byte

[0145] As shown in Table 1, the first column indicates the order of the multiple attributes contained in the flow descriptor ME. When the master device configures multiple attributes of the flow descriptor ME for the slave device, or when the master device obtains multiple attributes of the flow descriptor ME from the slave device, it fills in the attribute values ​​or attribute masks in the aforementioned order. The second column is the name of the multiple attributes contained in the flow descriptor ME. The third column indicates whether the attribute can be read or written by the master device, and when it is set. A read operation can be understood as the master device sending a get message to the slave device and receiving a get response message from the slave device to read the attribute value; a write operation can be understood as the master device sending a create message or a set message to the slave device to configure the attribute value. "Set-by-create" indicates that the master device sets the attribute value when the instance of the ME is first created. The fourth column indicates which attributes of the flow descriptor ME are mandatory and which are optional. The fifth column indicates the size of the attribute value in bytes for each attribute.

[0146] This application primarily concerns the first three attributes of the traffic descriptor ME. As shown in Table 1, the first row represents the first attribute of the traffic descriptor ME, namely the Managed Entity ID (ME ID) attribute, which uniquely identifies an instance of the traffic descriptor ME. The ME ID attribute is readable and writable, and is mandatory, with a size of 2 bytes. The second row represents the second attribute of the traffic descriptor ME, namely the committed information rate (CIR) attribute, which specifies the committed information rate in bytes per second (byte / s). The default value is 0. This CIR attribute is set when the instance is created, is readable and writable, and is optional, with a size of 4 bytes. The third row represents the third attribute of the traffic descriptor ME, namely the peak information rate (PIR) attribute, which specifies the peak information rate in bytes per second (byte / s). The default value is 0. This PIR attribute is set when the instance is created, is readable and writable, and is optional, with a size of 4 bytes.

[0147] Since both the CIR and PIR attribute fields are 4 bytes long, and the unit for both CIR and PIR attributes is bytes per second (byte / s), the maximum values ​​for the CIR and PIR attributes are 4,294,967,295 (i.e., 2...). 32 -1), meaning the maximum CIR or PIR that can be configured through these two attributes is 4,294,967,295 bytes / s, approximately 34 Gbit / s. In other words, according to the current standard, the master device can only configure a 34 Gbit / s CIR or PIR for the slave device. However, PON systems have evolved to 50G PON and even higher-speed PON in the future, meaning the slave device's operating line rate can reach 50 Gbit / s or even higher. This necessitates the master device configuring a 50 Gbit / s or even higher line rate CIR or PIR for the slave device. Clearly, the field length of the CIR and PIR attributes in the current traffic descriptor ME is insufficient to support the configuration of 50GPON and future higher-speed PON.

[0148] This application provides several solutions to address the CIR / PIR configuration issues of 50G PON and future higher-speed PON.

[0149] One solution proposes a newly defined attribute for the flow descriptor ME, namely the rate amplification factor attribute, which will be introduced later. This rate amplification factor attribute, together with the standard-defined CIR attribute, determines the effective CIR of the slave device. Furthermore, this rate amplification factor attribute, together with the standard-defined PIR attribute, determines the effective PIR of the slave device. Please refer to the following text for details. Figure 2 and Figure 4 The relevant descriptions in the corresponding embodiments.

[0150] Another solution proposes modifying the current standard's definitions of CIR and PIR, defining the units of CIR and PIR as related to the slave device's line rate and preset threshold, rather than necessarily in bytes per second. See below for details. Figure 6 and Figure 7 The relevant descriptions in the corresponding embodiments.

[0151] Let's combine the following... Figure 2 and Figure 4 The main process of the first solution of the optical network communication method provided in this application is described below:

[0152] like Figure 2 The diagram shown is a schematic representation of an embodiment of the optical network communication method provided in this application. In this embodiment, the master device configures attributes for a first slave device via a create message or a set message. The first slave device is one of multiple slave devices connected to the master device. This embodiment uses the interaction between the master device and the first slave device as an example for illustration. Of course, the entity executing the master device's actions in this method can also be a device, module, or chip in the master device; the entity executing the first slave device's actions in this method can also be a device, module, or chip in the first slave device. This embodiment does not specifically limit this. For example, as shown... Figure 2 As shown, the optical network communication method includes the following steps:

[0153] Step 201: The master device sends a first message to the first slave device; correspondingly, the first slave device receives the first message from the master device.

[0154] For example, the master device sends a first message to the first slave device via optical fiber; correspondingly, the first slave device receives the first message from the master device via optical fiber. The first message includes a rate amplification factor. Optionally, the first message also includes a first rate. The rate amplification factor is an adjustment coefficient for the first rate.

[0155] The first rate is CIR and / or PIR. For example, the first rate is CIR; or, the first rate is PIR; or, the first rate is both CIR and PIR. In one implementation, the first rate may be the CIR and / or PIR values ​​indicated by the master device to the first slave device via the CIR and / or PIR fields in the current standard. For example, the master device sends a seventh message to the first slave device before sending a first message, and this seventh message includes the first rate. In another implementation, the first rate may be the CIR and / or PIR values ​​indicated by the master device to the first slave device via the CIR and / or PIR fields in the first message. For example, the first message includes not only the rate amplification factor but also the first rate. In yet another implementation, the first rate is a pre-configured CIR and / or PIR, or a default CIR and / or PIR. For example, the standard defines the default CIR and / or PIR values ​​used by the first slave device when the master device has not configured CIR and / or PIR for the first slave device. For ease of explanation, the following text will use the first rate carried in the first message as an example. It should be understood that "CIR carried in the first message" can be replaced with "CIR carried in the seventh message" or "default CIR" in the following text, and "PIR carried in the first message" can be replaced with "PIR carried in the seventh message" or "default PIR" in the following text.

[0156] The rate amplification factor is an adjustment coefficient for the first rate, specifically the adjustment coefficient for the CIR and / or PIR carried by the first message. This can be understood as the rate amplification factor and the first rate being used to determine the second rate, which is the valid CIR and / or valid PIR of the first slave device. The valid CIR of the first slave device can be understood as the effective CIR of the first slave device, or the CIR used when the first slave device is operating; similarly, the valid PIR of the first slave device can be understood as the effective PIR of the first slave device, or the PIR used when the first slave device is operating.

[0157] Optionally, the product of the rate amplification factor and the first rate is equal to the second rate. For example, the product of the rate amplification factor and the CIR carried in the first message is equal to the effective CIR of the first slave device (i.e., the CIR used when the first slave device is operating). Another example is that the product of the rate amplification factor and the PIR carried in the first message is equal to the effective PIR of the first slave device (i.e., the PIR used when the first slave device is operating).

[0158] Optionally, the rate amplification factor can be an integer greater than 0. For example, if the rate amplification factor is 1, the second rate is equal to the first rate, meaning the first slave device operates according to the CIR and / or PIR values ​​indicated by the first message. If the rate amplification factor is greater than 1, for example, if the rate amplification factor is a (a is an integer greater than 1), the second rate is a times the first rate, meaning the first slave device operates according to a times the CIR value indicated by the first message, and / or a times the PIR value. Therefore, when the first message carries a rate amplification factor, the master device can indicate integer multiples of the CIR value and / or PIR value to the first slave device, ensuring that the effective CIR and / or PIR of the first slave device is not limited to the maximum rate indicated by 4 bytes. Thus, the CIR / PIR configuration problem for 50G PON and future higher-speed PONs is solved.

[0159] It should be noted that, in current and future standard development trends, the master device manages and maintains the CIR and PIR of the slave device through the CIR and PIR attributes of the flow descriptor ME. Therefore, the first message including the first rate can be understood as carrying the attribute values ​​of the CIR attribute and / or the PIR attribute. Furthermore, the rate amplification factor is a newly defined attribute of the flow descriptor ME in this application, namely the rate amplification factor attribute. The first message including the rate amplification factor can be understood as carrying the attribute value of the rate amplification factor attribute.

[0160] Optionally, the rate amplification factor attribute occupies at least one byte. The attribute value of the rate amplification factor attribute is an integer greater than 0. For example, if the rate amplification factor attribute occupies 1 byte, the maximum value of the rate amplification factor attribute is 2. 4 (i.e., 16), indicating that the maximum value of the CIR (or PIR) used by the first slave device when it is working can be 16 times the attribute value of the CIR attribute (or the attribute value of the PIR attribute) carried in the first message. For example, if the rate amplification factor attribute occupies 2 bytes, then the maximum value of the rate amplification factor attribute is 2. 8 (i.e., 256) indicates that the maximum value of the CIR (or PIR) used when the first slave device is working can be 256 times the attribute value of the CIR attribute (or the attribute value of the PIR attribute) carried in the first message.

[0161] For example, the traffic descriptor ME provided in this application includes the following attributes as shown in Table 2:

[0162] Table 2

[0163] Attribute order property Is it readable and writable? Is it optional? Attribute size 1 Regulated Entity Identifier Readable Required 2 bytes 2 Information rate can be guaranteed (CIR) Readable, writable, set at creation time Optional 4 bytes 3 Peak Information Rate (PIR) Readable, writable, set at creation time Optional 4 bytes 4 It can guarantee the safety of sudden events of all sizes. Readable, writable, set at creation time Optional 4 bytes 5 Peak burst size Readable, writable, set at creation time Optional 4 bytes 6 Color mode Readable, writable, set at creation time Optional 1 byte 7 Entrance color marking Readable, writable, set at creation time Optional 1 byte 8 Export color marking Readable, writable, set at creation time Optional 1 byte 9 Algorithm type Readable, set at creation time Optional 1 byte 10 Rate amplification factor Readable, writable, set at creation time Optional 2 bytes

[0164] In the example shown in Table 2, this application newly defines a 10th attribute for the flow descriptor ME, namely the rate amplification factor attribute. Since this rate amplification factor attribute is related to the CIR or PIR attribute, it can also be called the CIR / PIR scale factor. This rate amplification factor attribute can be defined as a readable attribute, meaning the master device can read its value from the slave device (e.g., the first slave device) through a get procedure. This rate amplification factor attribute can also be defined as a writable attribute, meaning the master device can configure its value for the slave device (e.g., the first slave device) through a create or set procedure. Furthermore, this rate amplification factor attribute is a set-by-create attribute, meaning the master device can set the value of the rate amplification factor attribute used by the first slave device when creating an instance of the flow descriptor ME of the first slave device. Optionally, this rate amplification factor attribute is an optional configuration attribute. The default value of this rate amplification factor is 1. Optionally, the size of the rate amplification factor attribute is 2 bytes. The other attributes shown in Table 2 are the same as those defined in the current standard and will not be repeated here.

[0165] It should be understood that the definitions of the rate amplification factor attributes shown in Table 2 are merely examples and not strict limitations. For instance, if other new attributes of the flow descriptor ME are introduced in the standard, the rate amplification factor attribute could also be the 11th attribute of the flow descriptor ME. Furthermore, the rate amplification factor could also be defined in other byte sizes, such as 1 byte, 3 bytes, or 4 bytes. For ease of understanding, the following descriptions will only use the examples shown in Table 2.

[0166] It should be noted that in this embodiment, the first slave device is a registered and online slave device, and an OMCI management channel has been established between the first slave device and the master device, enabling communication between them via OMCI messages. Therefore, the first message can be an OMCI message. Generally, OMCI messages include messages related to the create process (e.g., create request messages, also known as create messages), messages related to the set process (e.g., set request messages, also known as set messages), and messages related to the get process (e.g., get request messages, also known as get messages). In this embodiment, the first message is either a create request message or a set request message.

[0167] The first message will be explained below with reference to its specific message format:

[0168] In one possible implementation, the first message is a creation request message, meaning the message type of the first message is a creation request, which is a message sent by the master device to the first slave device when it first creates an instance of the flow descriptor ME of the first slave device. The managed entity identification information field of the first message includes the identification information of the managed entity of the flow descriptor, and the message content field of the first message includes the attribute value of the rate amplification factor attribute. The message content field of the first message also includes the attribute value of the CIR attribute and / or the attribute value of the PIR attribute.

[0169] For example, such as Figure 3A The diagram shown is an example of a creation request message provided in this application. The first two bytes are the transaction correlation identifier (TCI) field, used to identify the same set of request and response messages. For example, it is used to match a request message (or command) from the master device to the slave device and a response message from the slave device to the master device. Generally, the value of the transaction correlation identifier field is consistent in a set of corresponding request and response messages. The third byte is the message type (MT) field, used to indicate the purpose or action of the message; it can also be understood as indicating the message type. In this configuration, bits 1 to 5 of the third byte are message type (MT) bits, used to indicate the message type, such as create, delete, set, get, etc.; bit 6 of the third byte is the acknowledge request (AR) bit, used to indicate whether the message requires a response from the other end; bit 7 of the third byte is the acknowledge (AK) bit, used to indicate whether a response to the message is required; and bit 8 of the third byte is a reserved bit, which is fixed at 0. Figure 3A The example message type shown is a create request type. The 4th byte is the device identifier field, for... Figure 3A The baseline OMCI message format shown has this field set to 0x0A. Bytes 5 through 8 are the message entity identifier, containing the entity class and the corresponding entity instance. Figure 3AIn the example shown, the value of bytes 5 and 6 is 280, representing the managed entity of the traffic descriptor, i.e., the ME ID of the managed entity. Bytes 9 to 40 are the message contents field, used to carry the message content, i.e., used to encapsulate the message payload. The last 4 bytes are the message integrity check (MIC) field, used for message integrity verification.

[0170] Because the first byte of the message content field in the creation message begins with the value of the first set-by-create attribute, and space is allocated for each set-by-create attribute in the creation message according to its order and size, as shown in Table 2 above, the first attribute value in the message content field, the 4-byte CIR attribute value, occupies bytes 9-12; the second attribute value, the 4-byte PIR attribute value, occupies bytes 13-16, and so on, with the 9th attribute value, the 2-byte rate amplification factor attribute, occupying bytes 29-30. The remaining bytes in the message content field (bytes 31-40) are filled with zero values. Compared to... Figure 3B As can be seen from the creation request message for configuring CIR / PIR in the conventional technology, bytes 29 to 40 of the message content field are filled with zero values.

[0171] In another possible implementation, the first message is a setup request message, meaning the message type of the first message is a setup request. For example, the master device sends a setup request message to the first slave device when it needs to reconfigure an instance of the flow descriptor ME of the first slave device. The managed entity identification information field of the first message includes the identification information of the managed entity of the flow descriptor, and the message content field of the first message includes the attribute value of the rate amplification factor attribute. Optionally, the message content field of the first message also includes the attribute value of the CIR attribute and / or the attribute value of the PIR attribute.

[0172] In addition, the message content field of the first message also includes an attribute mask, which indicates which attribute values ​​the message content field carries. The attribute mask is 2 bytes (16 bits) in size, therefore, it can indicate a maximum of 16 attributes. This attribute mask can be a bitmap used in get messages (i.e., get request messages), get response messages, create response messages, and set messages (i.e., set request messages), indicating which attributes are requested or provided. The attribute mask, from the most significant bit to the least significant bit (i.e., from bit 8 to bit 1), corresponds to the order of attributes after the ME ID in the attributes of the flow descriptor ME (i.e., the order of attributes after the ME ID shown in Table 2). Since the CIR attribute is the second attribute of the flow descriptor entity (i.e., the first attribute after the MEID attribute), the CIR attribute corresponds to the first bit in the attribute mask. Similarly, the PIR attribute is the third attribute of the flow descriptor entity (i.e., the second attribute after the MEID attribute), and the PIR attribute corresponds to the second bit in the attribute mask. If the message content field carries a value for the CIR attribute, the first bit in the attribute mask corresponding to the CIR attribute is 1; if the message content field does not carry a value for the CIR attribute, the first bit in the attribute mask corresponding to the CIR attribute is 0. Other attributes are similar and will not be elaborated upon here.

[0173] In this application, the attribute mask indicating the attribute value carrying the rate amplification factor attribute is referred to as the first attribute mask. The bit corresponding to the rate amplification factor attribute in the first attribute mask is 1. Optionally, the bit corresponding to the CIR attribute in the first attribute mask is 1, and / or, the bit corresponding to the PIR attribute in the first attribute mask is 1. Optionally, if the rate amplification factor attribute is the 10th attribute of the flow descriptor entity, i.e., the 9th attribute after the ME ID attribute, then the rate amplification factor attribute corresponds to the 9th bit in the first attribute mask.

[0174] For example, such as Figure 3C The image shown is an example diagram of the setup request message provided in this application. Figure 3C The setup request message shown is compared to Figure 3A The creation request message shown differs only in the message type and message content fields. Please refer to the previous text for explanations of the remaining fields. Figure 3A The relevant descriptions of the examples shown are not repeated here. Figure 3CAs shown, the third byte is the message type (MT) field, indicating that the message type is a set request type. Bytes 9 to 40 are the message contents field. Among them, bytes 9 and 10 are the attribute mask. The 9th and 10th bytes of this attribute mask, from the most significant bit to the least significant bit (i.e., from bit 8 to bit 1), correspond to the order of attributes after the ME ID in the attributes of the flow descriptor ME (i.e., the order of attributes after the ME ID shown in Table 2). For example, the 8th bit of the 9th byte corresponds to the CIR attribute, the 7th bit of the 9th byte corresponds to the PIR attribute, and so on, with the 8th bit of the 10th byte corresponding to the rate amplification factor attribute. In one example, Figure 3C As shown, if the first message carries the attribute values ​​of the CIR attribute, PIR attribute, and rate amplification factor attribute, then the 8th bit of the 9th byte is 1, indicating that the message content field carries the CIR attribute value; the 7th bit of the 9th byte is 1, indicating that it carries the PIR attribute value; and the 8th bit of the 10th byte is 1, indicating that it carries the rate amplification factor attribute value. In another example, if the first message carries the rate amplification factor attribute value, then the 8th bit of the 9th byte is 0, indicating that the message content field does not carry the CIR attribute value; the 7th bit of the 9th byte is 0, indicating that it does not carry the PIR attribute value; and the 8th bit of the 10th byte is 1, indicating that it carries the rate amplification factor attribute value. It should be understood that, depending on the type of attribute values ​​carried in the message content field, there can be other examples of attribute masks, which will not be elaborated here.

[0175] In addition, the remaining bytes of the message content field are used to carry the attribute values ​​of the attributes indicated by the attribute mask. It should be noted that the message content field of a set request message differs from that of a creation request message. The first byte of the message content field of a creation request message begins with the attribute value of the first set-by-create attribute, and space is allocated in the creation message for each set-by-create attribute in sequence and according to its size. However, the message content field of a set request message only carries the attribute values ​​of the attributes indicated by the attribute mask, and not necessarily the attribute values ​​of all set-by-create attributes. Optionally, the attribute value of the rate amplification factor attribute can be carried in bytes n to (n+2) of the message content field, where n is an integer greater than or equal to 11 and less than or equal to 38.

[0176] In one example, if the request message requests the configuration of all attributes of the traffic descriptor ME, then referring to Table 2 above, bytes 11-14 are the 4-byte CIR attribute values, bytes 15-18 are the 4-byte PIR attribute values, and so on, bytes 31-32 are the 2-byte rate amplification factor attribute values, and the remaining bytes in the message content field (i.e., bytes 33-40) are filled with zero values. In another example, if the request message requests the configuration of CIR, PIR, and rate amplification factor attributes, then referring to Table 2 above, bytes 11-14 are the 4-byte CIR attribute values, bytes 15-18 are the 4-byte PIR attribute values, bytes 19-20 are the 2-byte rate amplification factor attribute values, and the remaining bytes in the message content field (i.e., bytes 21-40) are filled with zero values. In another example, if the request message requests configuration of the CIR (or PIR) attribute and the rate amplification factor attribute, then, referring to Table 2 above, bytes 11-14 contain the 4-byte CIR attribute value (or PIR attribute value), bytes 15-16 contain the 2-byte rate amplification factor attribute value, and the remaining bytes in the message content field (bytes 17-40) are filled with zero values. In another example, if the request message only requests configuration of the rate amplification factor attribute, then bytes 11-12 contain the 2-byte rate amplification factor attribute value, and the remaining bytes in the message content field (bytes 13-40) are filled with zero values. Other examples may exist in practical applications, which will be listed here.

[0177] It should be noted that, compared to Figure 3D As can be seen from the configuration request message for CIR / PIR in the conventional technology, since the conventional technology does not carry the attribute value of the rate amplification factor, the 8th bit of the 10th byte of the message content field is 0, and the message content field does not contain the attribute value of the rate amplification factor.

[0178] It should be understood that in this embodiment Figure 3A , Figure 3B , Figure 3C and Figure 3D The above descriptions all use the Baseline OMCI message format as an example. In practical applications, the aforementioned... Figure 3A , Figure 3B , Figure 3C and Figure 3D The various message types described can also be implemented using the extended OMCI message format, which will not be elaborated upon here.

[0179] Optionally, the first message is encapsulated in the payload field of a downlink XG-PON encapsulation method (10-Gigabit passive optical network encapsulation method, XGEM frame). The frame header (XGEMHeader) of the downlink XGEM frame contains information to distinguish different OMCI XGEM Ports (hereinafter referred to as XGEM Ports). These XGEM Ports are logical ports on the slave device, used to carry data from the downlink PON port of the master device. Different slave devices have different XGEM Port identifiers; therefore, different slave devices can be distinguished based on the XGEM Port identifier. In this embodiment, the XGEM port ID in the frame header (XGEM Header) of the downlink XGEM frame is the same as the identifier information of the first slave device (e.g., ONU ID), that is, the XGEM port ID is the same as the ONU ID.

[0180] Step 202: The first slave device determines the second rate of the first slave device based on the rate amplification factor and the first rate.

[0181] The second rate is the valid CIR and / or PIR of the first slave device. For an explanation of the second rate, please refer to step 201 above; it will not be repeated here.

[0182] In one possible implementation, the second rate is equal to the product of the first rate and the rate amplification factor. The first slave device determines the second rate based on the product of the first rate and the rate amplification factor. For example, if the first slave device obtains a CIR attribute value of 4,294,967,295 bytes / s (approximately 34.36 Gbit / s) from the first message, and the rate amplification factor attribute value is 2, then the effective CIR of the first slave device is the product of the CIR attribute value and the rate amplification factor attribute value, i.e., 8,589,934,590 bytes / s (approximately 68.72 Gbit / s). Therefore, the master device can solve the CIR / PIR configuration problem for 50G PON and future higher-speed PONs through the newly defined rate amplification factor.

[0183] In this embodiment, the first slave device receives a rate amplification factor from the master device. This rate amplification factor is an adjustment coefficient for the first rate (i.e., the attribute value of the CIR / PIR attribute). The first slave device determines the second rate (i.e., the effective CIR / PIR of the first slave device) using the rate amplification factor and the first rate. Therefore, even when the values ​​of the first rate are limited, the effective CIR / PIR of the first slave device can be adjusted using the rate amplification factor. In other words, without changing the existing attributes, the range of CIR / PIR values ​​used by the first slave device during operation is expanded. This solves the CIR / PIR configuration problem for 50GPON and future higher-speed PONs.

[0184] like Figure 4 The diagram shown illustrates another embodiment of the optical network communication method provided in this application. In this embodiment, the master device reads attributes from a first slave device by obtaining (get) messages and obtaining (get response) messages. The first slave device is one of a plurality of slave devices connected to the master device. This embodiment uses the interaction between the master device and the first slave device as an example for explanation. Of course, the entity executing the master device's actions in this method can also be a device, module, or chip in the master device; the entity executing the first slave device's actions in this method can also be a device, module, or chip in the first slave device. This embodiment does not specifically limit this. For example, as shown... Figure 4 As shown, the optical network communication method includes the following steps:

[0185] Step 401: The master device sends a second message to the first slave device; correspondingly, the first slave device receives the second message from the master device.

[0186] For example, the master device sends a second message to the first slave device via optical fiber; correspondingly, the first slave device receives the second message from the master device via optical fiber. The second message includes first indication information, which instructs the first slave device to report a rate amplification factor, which is an adjustment coefficient for the first rate. Optionally, the first indication information may also instruct the first slave device to report a first rate, which is CIR and / or PIR. The rate amplification factor and the first rate are used to determine a second rate, which is the effective rate of the first slave device's CIR and / or PIR. For an explanation of the first rate, rate amplification factor, and second rate, please refer to the relevant description in step 201 above; it will not be repeated here.

[0187] In this embodiment, the first indication information may be an attribute mask. For an introduction to the attribute mask, please refer to the relevant description in step 201 above, which will not be repeated here.

[0188] In one possible implementation, the first indication information is a first attribute mask, which indicates that the second message requests the first slave device to report the value of the rate amplification factor attribute. For example, if the bit corresponding to the rate amplification factor attribute in the first attribute mask is 1, it indicates that the first slave device is requesting the report of the rate amplification factor attribute value. Optionally, if the rate amplification factor attribute is the 10th attribute of the traffic descriptor entity, i.e., the 9th attribute after the ME ID attribute, then the rate amplification factor attribute corresponds to the 9th bit in the first attribute mask, and the 9th bit in the first attribute mask is 1.

[0189] Optionally, the first attribute mask is also used to indicate the attribute values ​​of the CIR attribute and / or PIR attribute reported by the first slave device. In one example, the first attribute mask indicates the attribute values ​​of the reported rate amplification factor attribute, CIR attribute, and PIR attribute. In this example, the first attribute in the first attribute mask is the CIR attribute, and the bit corresponding to the CIR attribute is 1, indicating a request for the first slave device to report the CIR attribute value; the second attribute in the first attribute mask is the PIR attribute, and the bit corresponding to the PIR attribute is 1, indicating a request for the first slave device to report the PIR attribute value; the ninth attribute in the first attribute mask is the rate amplification factor attribute, and the bit corresponding to the rate amplification factor attribute is 1, indicating a request for the first slave device to report the rate amplification factor attribute value. It should be understood that, depending on the attribute indicated by the first attribute mask in the message, there can be other examples of the first attribute mask, which will not be elaborated here.

[0190] It should be noted that in this embodiment, the first slave device is a registered and online slave device, and an OMCI management channel has been established between the first slave device and the master device, enabling communication between them via OMCI messages. Therefore, the second message can be an OMCI message. Generally, OMCI messages include messages related to the create process (e.g., create request message), messages related to the set process (e.g., set request message), and messages related to the get process (e.g., get request message). In this embodiment, the second message is a get message (i.e., a get request message). The managed entity identification information field of the second message includes the traffic descriptor and the managed entity identification information, and the message content field of the second message includes the aforementioned first indication information, that is, the message content field of the second message includes the aforementioned first attribute mask.

[0191] For example, such as Figure 5A The image shown is an example diagram of the GET message (i.e., GET request message) provided in this application. Figure 5A The retrieve request message shown is compared to Figure 3AThe creation request message shown differs only in the message type and message content fields. Please refer to the previous text for explanations of the remaining fields. Figure 3A The relevant descriptions of the examples shown are not repeated here. Figure 5A As shown, the third byte is the message type (MT) field, indicating that the message type is a GET request. Bytes 9 to 40 are the message contents field. Bytes 9 and 10 are attribute masks, used to indicate which attributes are requested. The mapping rules for this attribute mask are the same as described above. Figure 3C The mapping rules for the attribute masks in the setup request message are the same and will not be repeated here. Specifically, the 8th bit of the 9th byte corresponds to the CIR attribute, the 7th bit of the 9th byte corresponds to the PIR attribute, and so on, with the 8th bit of the 10th byte corresponding to the rate amplification factor attribute. In one example, Figure 5A As shown, if the second message requests the reporting of the CIR attribute value, PIR attribute value, and rate amplification factor attribute value, then the 8th bit of the 9th byte is 1, indicating a request for the device to report the CIR attribute value; the 7th bit of the 9th byte is 1, indicating a request for the device to report the PIR attribute value; and the 8th bit of the 10th byte is 1, indicating a request for the device to report the rate amplification factor attribute value. In another example, if the second message only requests the reporting of the CIR attribute value and the rate amplification factor attribute value, then the 8th bit of the 9th byte is 1, indicating a request for the device to report the CIR attribute value; the 7th bit of the 9th byte is 0, indicating that the PIR attribute value does not need to be reported; and the 8th bit of the 10th byte is 1, indicating a request for the device to report the rate amplification factor attribute value. It should be understood that, depending on the type of attribute value requested in the second message, there can be other examples of attribute masks, which will not be elaborated here. Furthermore, the remaining bytes of the message content field are filled with zero values.

[0192] It should be noted that, compared to Figure 5B As can be seen from the acquisition request message for configuring CIR / PIR in the conventional technology, since the master device does not indicate the slave device to report the rate amplification factor attribute, the 8th bit of the 10th byte of the message content field is 0.

[0193] Optionally, the second message is encapsulated in the payload field of the downlink XGEM frame. The frame header (XGEMHeader) of the downlink XGEM frame contains information to distinguish different OMCI XGEM Ports (hereinafter referred to as XGEM Ports). These XGEM Ports are logical ports on the slave device used to carry data from the downlink PON port of the master device. Different slave devices have different XGEM Port identifiers; therefore, different slave devices can be distinguished based on the XGEM Port identifier. In this embodiment, the XGEM port identifier (XGEM port ID) in the frame header (XGEM Header) of the downlink XGEM frame is the same as the identifier information of the first slave device (e.g., ONU ID), that is, the XGEM port ID is the same as the ONU ID.

[0194] Step 402: The first slave device sends a third message to the master device; correspondingly, the master device receives the third message from the first slave device.

[0195] For example, the first slave device sends a third message to the master device via optical fiber; correspondingly, the master device receives the third message from the first slave device via optical fiber. The third message includes the rate amplification factor and the first rate of the first slave device. For an explanation of the rate amplification factor and the first rate, please refer to the relevant description in step 201 above; it will not be repeated here.

[0196] Furthermore, the third message is a response message to the second message. Since the second message is a request message, the third message is a response message; that is, the message type of the third message is response. Additionally, the managed entity identification information field of the third message includes the identification information of the managed entity in the traffic descriptor field, and the message content field of the third message includes the attribute values ​​of a first attribute mask and a rate amplification factor attribute, where the bit corresponding to the rate amplification factor attribute in the first attribute mask is 1. Optionally, the message content field of the third message also includes the attribute values ​​of a CIR attribute and / or a PIR attribute. The bit corresponding to the CIR attribute in the first attribute mask is 1, and / or, the bit corresponding to the PIR attribute in the first attribute mask is 1. For an explanation of the first attribute mask, please refer to the relevant description in step 401 above; it will not be repeated here.

[0197] For example, such as Figure 5C The image shown is an example diagram of the get response message provided in this application. Figure 5C The response message shown is compared to Figure 3A The creation request message shown differs only in the message type and message content fields. Please refer to the previous text for explanations of the remaining fields. Figure 3A The relevant descriptions of the examples shown are not repeated here. Figure 5CAs shown, the third byte is the message type (MT) field, indicating that the message type is a getresponse. Bytes 9 to 40 are the message contents fields. Byte 9 indicates the processing result of the get operation. The first four bits of this ninth byte are fixed as "0000", meaning bits 8 to 5 are fixed as "0000"; the last four bits of this ninth byte indicate the reason for the processing result. Figure 5C The "0000" in bits 4-1 indicates successful command processing, meaning the attribute mask (e.g., the first attribute mask) in the request message (e.g., the second message) indicating the attribute values ​​that need to be reported was successfully retrieved. Bytes 10-11 are the attribute mask, used to indicate which attributes are provided. The mapping rule for this attribute mask is the same as described above. Figure 3C The mapping rules for the attribute masks in the setting request message are the same as those shown, and will not be repeated here. It should be noted that when the attribute requested in the get request message is the same as the attribute reported in the get response message, the attribute mask in the second message is the same as the attribute mask in the third message. This embodiment uses the example where both the second and third messages carry the first attribute mask. Specifically, the 8th bit of the 10th byte corresponds to the CIR attribute, the 7th bit of the 10th byte corresponds to the PIR attribute, and so on, with the 8th bit of the 11th byte corresponding to the rate amplification factor attribute. In one example, such as... Figure 5C As shown, if the third message carries the attribute values ​​of the CIR attribute, PIR attribute, and rate amplification factor attribute, then the 8th bit of the 10th byte is 1, indicating that the message content field carries the CIR attribute value; the 7th bit of the 10th byte is 1, indicating that the message content field carries the PIR attribute value; and the 8th bit of the 11th byte is 1, indicating that the message content field carries the rate amplification factor attribute value. In another example, if the third message carries the CIR attribute value and the rate amplification factor attribute value, then the 8th bit of the 9th byte is 1, indicating that the message content field carries the CIR attribute value; the 7th bit of the 9th byte is 0, indicating that the message content field does not carry the PIR attribute value; and the 8th bit of the 10th byte is 1, indicating that the message content field carries the rate amplification factor attribute value. It should be understood that, depending on the type of attribute value carried by the third message, there can be other examples of the first attribute mask, which will not be elaborated here. In addition, bytes 37-38 carry optional attribute masks, and bytes 39-40 carry attribute execution masks. In addition, the remaining bytes of the message content field are used to carry the attribute values ​​of the attributes indicated by the attribute mask.

[0198] It should be noted that the message content field of the retrieved response message differs from that of the creation request message. The first byte of the message content field in the creation request message begins with the value of the first set-by-create attribute, and space is allocated in the creation message for each set-by-create attribute in sequence and according to its size. However, the message content field of the retrieved response message only carries the values ​​of the attributes indicated by the attribute mask, and not necessarily the values ​​of all set-by-create attributes. Optionally, the value of the rate amplification factor attribute can be carried in bytes m to (m+2) of the message content field, where m is an integer greater than or equal to 12 and less than or equal to 34.

[0199] In one example, if the response message carries the attribute values ​​of all attributes of the flow descriptor ME, then referring to Table 2 above, bytes 12-15 are the 4-byte CIR attribute values, bytes 16-19 are the 4-byte PIR attribute values, and so on, bytes 32-33 are the 2-byte rate amplification factor attribute values, and the remaining bytes in the message content field (i.e., bytes 34-36) are filled with zero values. In another example, if the response message provides the master device with CIR, PIR, and rate amplification factor attributes, then referring to Table 2 above, bytes 12-15 are the 4-byte CIR attribute values, bytes 16-19 are the 4-byte PIR attribute values, bytes 20-21 are the 2-byte rate amplification factor attribute values, and the remaining bytes in the message content field (i.e., bytes 22-36) are filled with zero values. In another example, if the retrieval response message provides the master device with the CIR attribute (or PIR attribute) and rate amplification factor attribute, then, referring to Table 2 above, bytes 12-15 contain the 4-byte CIR attribute value (or PIR attribute value), bytes 16-17 contain the 2-byte rate amplification factor attribute value, and the remaining bytes in the message content field (i.e., bytes 18-36) are filled with zero values. In another example, if the retrieval response message only provides the rate amplification factor attribute to the master device, then bytes 12-13 contain the 2-byte rate amplification factor attribute value, and the remaining bytes in the message content field (i.e., bytes 14-36) are filled with zero values. Other examples may exist in practical applications, which will be listed here.

[0200] It should be noted that, compared to Figure 5D As can be seen from the acquisition response message of CIR / PIR configured in the conventional technology, since the conventional technology does not carry the attribute value of the rate amplification factor, the 8th bit of the 11th byte of the message content field is 0, and the message content field does not contain the attribute value of the rate amplification factor.

[0201] It should be understood that in this embodiment Figure 5A , Figure 5B , Figure 5C and Figure 5D The above descriptions all use the Baseline OMCI message format as an example. In practical applications, the aforementioned... Figure 5A , Figure 5B , Figure 5C and Figure 5D The various message types described can also be implemented using the extended OMCI message format, which will not be elaborated upon here.

[0202] Optionally, the third message is encapsulated in the payload field of the uplink XGEM frame. The XGEM port ID in the frame header (XGEMHeader) of the uplink XGEM frame is the same as the identification information of the first slave device (e.g., ONU ID), that is, the XGEM port ID is the same as the ONU ID.

[0203] In this embodiment, the first slave device receives a first indication message from the master device, instructing the first slave device to report a rate amplification factor and a first rate. The rate amplification factor is an adjustment coefficient for the first rate (i.e., the attribute value of the CIR / PIR attribute). After receiving the first indication message, the first slave device reports its rate amplification factor and first rate, thereby providing the master device with the effective CIR / PIR of the first slave device. In other words, without changing the existing attributes, the range of CIR / PIR values ​​used by the first slave device during operation is expanded, and the CIR / PIR reporting problem for 50G PON and future higher-speed PONs is solved.

[0204] The following is combined with Figure 6 and Figure 7 The main process of the second solution to the optical network communication method provided in this application is described below:

[0205] like Figure 6 The diagram shown illustrates another embodiment of the optical network communication method provided in this application. In this embodiment, the master device configures attributes for a first slave device via a create message or a set message. The first slave device is one of multiple slave devices connected to the master device. This embodiment uses the interaction between the master device and the first slave device as an example for explanation. Of course, the entity executing the master device's actions in this method can also be a device, module, or chip within the master device; similarly, the entity executing the first slave device's actions in this method can also be a device, module, or chip within the first slave device. This embodiment does not specifically limit this. For example, as shown... Figure 6As shown, the optical network communication method includes the following steps:

[0206] Step 601: The master device sends a fourth message to the first slave device; correspondingly, the first slave device receives the fourth message from the master device.

[0207] For example, the master device sends a fourth message to the first slave device via optical fiber; correspondingly, the first slave device receives the fourth message from the master device via optical fiber.

[0208] The fourth message includes a third rate, which is CIR and / or PIR. Since the master device manages and maintains the slave device's CIR and PIR through the CIR and PIR attributes of the flow descriptor ME, the inclusion of the third rate in the fourth message can be understood as the fourth message carrying the attribute values ​​of the CIR attribute and / or the PIR attribute.

[0209] Furthermore, the unit of the third rate is related to the line rate of the first slave device and a preset threshold. Specifically, when the line rate of the first slave device is less than or equal to the preset threshold, the unit of the third rate is bytes per second; when the line rate of the first slave device is greater than the preset threshold, the unit of the third rate is N bytes per second, where N is a positive integer. The line rate of the first slave device can be the line rate used by the first slave device during operation. It should be noted that before receiving the fourth message, the first slave device registers online with the master device, and the master device establishes an OMCI management channel with the first slave device. During this process, the master device can learn the line rate used by the first slave device during operation.

[0210] In other words, compared to the CIR and PIR attributes in traditional technologies, the CIR and PIR attributes provided in this embodiment have different definitions. In traditional technologies, the unit of the CIR attribute value is bytes per second, and the unit of the PIR attribute value is bytes per second. However, in this application, the unit of the CIR attribute and the PIR attribute is related to the line rate of the slave device to be configured on the master device and a preset threshold, and is not necessarily bytes per second. For example, for the CIR attribute, when the line rate of the slave device to be configured on the master device is less than or equal to the preset threshold, the unit of the CIR attribute value is bytes per second; when the line rate of the slave device to be configured on the master device is greater than the preset threshold, the unit of the CIR attribute value is N bytes per second, where N is a positive integer. Similarly, for the PIR attribute, when the line rate of the slave device to be configured on the master device is less than or equal to the preset threshold, the unit of the PIR attribute value is bytes per second; when the line rate of the slave device to be configured on the master device is greater than the preset threshold, the unit of the PIR attribute value is N bytes per second, where N is a positive integer.

[0211] Optionally, the default value of N is 1. The value of N can be pre-configured or determined through negotiation between the master device and the slave device; this application does not limit this.

[0212] Optionally, the preset threshold is 9.95328 Gbit / s. In some scenarios, the preset threshold can also be simply referred to as 10 Gbit / s. Optionally, the preset threshold is less than 4,294,967,295 bytes / s (approximately 34.36 Gbit / s). Since this embodiment does not modify the byte size of the attribute value carrying the CIR attribute, nor does it modify the byte size of the attribute value carrying the PIR attribute, the maximum value of the CIR attribute remains 4,294,967,295 bytes / s (approximately 34.36 Gbit / s), and the maximum value of the PIR attribute remains 4,294,967,295 bytes / s (approximately 34.36 Gbit / s). Therefore, the preset threshold value is less than 4,294,967,295 bytes / s (approximately 34.36 Gbit / s).

[0213] Furthermore, the fourth message in this embodiment can be a creation request message or a setting request message.

[0214] In one possible implementation, the fourth message is a creation request message, meaning the message type of the fourth message is a creation request, which is a message sent by the master device to the first slave device when it first creates an instance of the flow descriptor ME of the first slave device. In this case, the managed entity identification information field of the fourth message includes the identification information of the flow descriptor managed entity, and the message content field of the fourth message includes the attribute values ​​of the CIR attribute and / or the PIR attribute. The message format of this fourth message is the same as the message format of the creation message for configuring CIR / PIR in conventional technology; please refer to the preceding text for details. Figure 3B The example shown is not elaborated here.

[0215] In another possible implementation, the fourth message is a setup request message, meaning the message type of the fourth message is a setup request. For example, the master device sends a setup request message to the first slave device when it needs to reconfigure an instance of the traffic descriptor ME of the first slave device. In this case, the managed entity identification information field of the fourth message includes the identification information of the traffic descriptor managed entity, and the message content field of the fourth message includes not only the attribute values ​​of the CIR attribute and / or the PIR attribute, but also a second attribute mask. The second attribute mask is used to indicate that the message content field carries the attribute values ​​of the CIR attribute and the PIR attribute. A bit corresponding to the CIR attribute in the second attribute mask is 1, indicating that the message content field carries the attribute value of the CIR attribute; a bit corresponding to the PIR attribute in the second attribute mask is 1, indicating that the message content field carries the attribute value of the PIR attribute.

[0216] Optionally, the fourth message is encapsulated in the payload field of the downlink XGEM frame. The frame header (XGEM header) of the downlink XGEM frame contains information to distinguish different XGEM ports, which are logical ports on the slave device used to carry data from the downlink PON port of the master device. Different slave devices have different XGEM port identifiers; therefore, different slave devices can be distinguished based on the XGEM port identifier. In this embodiment, the XGEM port ID in the frame header (XGEM header) of the downlink XGEM frame is the same as the identification information of the first slave device (e.g., ONU ID), that is, the XGEM port ID is the same as the ONU ID.

[0217] Step 602: The first slave device determines the unit of the third rate based on the line rate of the first slave device and a preset threshold.

[0218] This can also be understood as the first slave device determining its valid CIR and / or PIR based on its line rate and a preset threshold. For an explanation of the preset threshold, please refer to step 601 above; it will not be repeated here. The valid CIR of the first slave device can be understood as the effective CIR of the first slave device, or the CIR used by the first slave device during operation; similarly, the valid PIR of the first slave device can be understood as the effective PIR of the first slave device, or the PIR used by the first slave device during operation.

[0219] In one possible implementation, if the line rate of the first slave device is less than or equal to a preset threshold, the first slave device determines the value of the third rate (i.e., the attribute value of the CIR attribute and / or the attribute value of the PIR attribute) as the effective CIR / PIR of the first slave device, in bytes per second. For example, if the line rate of the first slave device is less than or equal to the preset threshold, and the attribute value of the CIR attribute is A, then the attribute value of the CIR attribute is in bytes per second, and the effective CIR of the first slave device is A bytes per second; if the line rate of the first slave device is less than or equal to the preset threshold, and the attribute value of the PIR attribute is B, then the attribute value of the PIR attribute is in bytes per second, and the effective PIR of the first slave device is B bytes per second. Here, A and B are both integers greater than 0.

[0220] In another possible implementation, if the line rate of the first slave device is greater than a preset threshold, the first slave device determines that the product of the value of the third rate (i.e., the attribute value of the CIR attribute and / or the attribute value of the PIR attribute) and N is the effective CIR / PIR of the first slave device, in bytes per second. For example, if the line rate of the first slave device is greater than the preset threshold, and the attribute value of the CIR attribute is A, then the attribute value of the CIR attribute is in units of N bytes per second, and the first slave device determines that the effective CIR of the first slave device is A*N bytes per second; if the line rate of the first slave device is greater than the preset threshold, and the attribute value of the PIR attribute is B, then the attribute value of the PIR attribute is in units of N bytes per second, and the first slave device determines that the effective PIR of the first slave device is equal to B*N bytes per second. Here, A, B, and N are all integers greater than 0.

[0221] In this embodiment, the unit of the third rate received by the first slave device from the master device is related to the line rate of the first slave device and a preset threshold. The first slave device can determine the unit of the third rate based on its line rate and the preset threshold, thus determining its effective CIR / PIR. Therefore, even when the possible values ​​of the third rate are limited, the first slave device can still determine the unit of the third rate based on its line rate and the preset threshold, thereby determining its effective CIR / PIR. This solves the CIR / PIR configuration problem for 50G PON and future higher-speed PONs.

[0222] like Figure 7 The diagram shown illustrates another embodiment of the optical network communication method provided in this application. In this embodiment, the master device reads attributes from a first slave device by obtaining (get) messages and obtaining (get response) messages. The first slave device is one of a plurality of slave devices connected to the master device. This embodiment uses the interaction between the master device and the first slave device as an example for explanation. Of course, the entity executing the master device's actions in this method can also be a device, module, or chip in the master device; the entity executing the first slave device's actions in this method can also be a device, module, or chip in the first slave device. This embodiment does not specifically limit this. For example, as shown... Figure 7 As shown, the optical network communication method includes the following steps:

[0223] Step 701: The master device sends a fifth message to the first slave device; correspondingly, the first slave device receives the fifth message from the master device.

[0224] For example, the master device sends a fifth message to the first slave device via optical fiber; correspondingly, the first slave device receives the fifth message from the master device via optical fiber. The fifth message includes second indication information, which instructs the first slave device to report a third rate. The third rate is CIR and / or PIR, and the unit of the third rate is related to the line rate and a preset threshold of the first slave device. For an explanation of the third rate, please refer to the relevant description in step 601 above; it will not be repeated here.

[0225] In one possible implementation, the second indication information is a second attribute mask, which is used to indicate the attribute values ​​of the CIR attribute and / or PIR attribute requested by the fifth message from the first slave device. Optionally, the second attribute mask is a 2-byte bit mapping, and the second attribute mask from the high-order bits to the low-order bits (i.e., from the 8th bit to the 1st bit) corresponds to the order of attributes after the ME ID in the attributes of the flow descriptor ME (i.e., the order of attributes after the ME ID shown in Table 2). For example, if the first attribute in the second attribute mask is the CIR attribute, and the bit corresponding to the CIR attribute in the second attribute mask is 1, it indicates that the first slave device is requested to report the attribute value of the CIR attribute; if the second attribute in the second attribute mask is the PIR attribute, and the bit corresponding to the PIR attribute in the second attribute mask is 1, it indicates that the first slave device is requested to report the attribute value of the PIR attribute.

[0226] Furthermore, the fifth message in this embodiment can be a retrieval request message, meaning the message type of the fifth message is a retrieval request. In this case, the fifth message also includes the identification information of the traffic descriptor managed entity, and the message content field of the fifth message includes the aforementioned second indication information (e.g., the aforementioned second attribute mask). The message format of this fifth message is the same as the message format of the retrieval request message for configuring CIR / PIR in conventional technology; please refer to the preceding text for details. Figure 5B The example shown is not elaborated here.

[0227] Optionally, the fifth message is encapsulated in the payload field of the downlink XGEM frame. The frame header (XGEM header) of the downlink XGEM frame contains information to distinguish different XGEM ports, which are logical ports on the slave device used to carry data from the downlink PON port of the master device. Different slave devices have different XGEM port identifiers; therefore, different slave devices can be distinguished based on the XGEM port identifier. In this embodiment, the XGEM port ID in the frame header (XGEM header) of the downlink XGEM frame is the same as the identification information of the first slave device (e.g., ONU ID), that is, the XGEM port ID is the same as the ONU ID.

[0228] Step 702: The first slave device sends a sixth message to the master device; correspondingly, the master device receives the sixth message from the first slave device.

[0229] For example, the first slave device sends a sixth message to the master device via optical fiber; correspondingly, the master device receives the sixth message from the first slave device via optical fiber. The sixth message includes the third rate of the first slave device. When the line rate of the first slave device is less than or equal to a preset threshold, the unit of the third rate is bytes per second; when the line rate of the first slave device is greater than the preset threshold, the unit of the third rate is N bytes per second, where N is a positive integer. For an explanation of the third rate, please refer to the relevant description in step 601 above; it will not be repeated here.

[0230] Furthermore, the sixth message is a response message to the fifth message. Since the fifth message is a request message, the sixth message is a response message; that is, the message type of the sixth message is a response message. Additionally, the managed entity identification information field of the sixth message includes the traffic descriptor, and the message content field includes second indication information (e.g., the aforementioned second attribute mask), the attribute value of the CIR attribute, and the attribute value of the PIR attribute. The message format of this sixth message is the same as the message format of the response message for configuring CIR / PIR in conventional technology; please refer to the preceding text for details. Figure 5D The example shown is not elaborated here.

[0231] It should be understood that before receiving the fifth message, the first slave device registers and goes online with the master device, and the master device establishes an OMCI management channel with the first slave device. During this process, the first slave device can determine the line rate used during operation, and the master device can also learn about the line rate used by the first slave device during operation. Therefore, after the master device receives the sixth message, the master device can determine the valid CIR and / or PIR of the first slave device based on the attribute values ​​of the CIR and / or PIR attributes carried in the sixth message, the line rate of the first slave device, and a preset threshold.

[0232] Optionally, the sixth message is encapsulated in the payload field of the uplink XGEM frame. The XGEM port ID in the frame header (XGEMHeader) of the uplink XGEM frame is the same as the identification information of the first slave device (e.g., ONU ID), that is, the XGEM port ID is the same as the ONU ID.

[0233] In this embodiment, the first slave device receives a second indication message from the master device, instructing it to report a third rate (i.e., the attribute value of the CIR / PIR attribute). Since the unit of the third rate is related to the line rate and a preset threshold of the first slave device, after receiving the second indication message, the first slave device reports the attribute value of the CIR / PIR attribute. The master device then determines the valid CIR / PIR of the first slave device, thereby indirectly providing the master device with the valid CIR / PIR of the first slave device. In other words, without changing the existing attributes, the range of CIR / PIR values ​​used by the first slave device during operation is expanded, and the CIR / PIR reporting problem for 50G PON and future higher-speed PONs is solved.

[0234] like Figure 8 As shown in the figure, this application embodiment also provides a communication device 80. Figure 2 , Figure 4 , Figure 6 or Figure 7 The specific implementation of the master device and slave device (e.g., the first slave device) in the flowchart shown can be found in [reference]. Figure 8 The internal structure of the communication device 80 is shown. When the communication device 80 is used to implement... Figure 2 , Figure 4 , Figure 6 or Figure 7 When the communication device 80 is used to implement the function of the master device in the method shown, it can be an OLT. Figure 2 , Figure 4 , Figure 6 or Figure 7 When the slave device in the method shown is used, the communication device 80 can be an ONU or an ONT.

[0235] like Figure 8As shown, the communication device 80 may include a processor 801 and a transceiver 802, with the processor 801 coupled to the transceiver 802. The processor 801 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 801 may refer to a single processor or may include multiple processors; no specific limitation is made here.

[0236] The aforementioned transceiver 802 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 80 is used to implement... Figure 2 , Figure 4 , Figure 6 or Figure 7 When the master device in the method shown functions, the transceiver 802 can be used for uplink burst optical signal reception. Optionally, the transceiver 802 supports burst optical signal reception at one or more uplink rates.

[0237] Optionally, the communication device 80 further includes a memory 803. The processor 801 is coupled to the memory 803. The memory 803 is primarily used to store software programs and data. The memory 803 can exist independently, connected to the processor 801. Optionally, the memory 803 can be integrated with the processor 801, for example, integrated within one or more chips. The memory 803 can store program code that executes the technical solutions of the embodiments of this application, and its execution is controlled by the processor 801. The various types of computer program code being executed can also be considered as drivers for the processor 801. The memory 803 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 803 can also include combinations of the above types of memory. Memory 803 can refer to a single memory or may include multiple memories. For example, memory 803 is used to store various types of data.

[0238] In one implementation, the communication device 80 is used to implement Figure 2 The corresponding method embodiment describes the function of the master device. Specifically, the processor 801 is used to generate a first message, which includes a rate amplification factor, which is an adjustment coefficient for a first rate. The first rate is the Guaranteed Information Rate (CIR) and / or Peak Information Rate (PIR). The rate amplification factor and the first rate are used to determine a second rate for the first slave device, where the second rate is the effective CIR and / or PIR of the first slave device. The transceiver 802 is used to send the first message to the first slave device. Optionally, the first message may also include the first rate.

[0239] In another implementation, the communication device 80 is used to implement Figure 2 The function of the first slave device in the corresponding method embodiment is as follows. Specifically, transceiver 802 is used to receive a first message from the master device. The first message includes a rate amplification factor, which is an adjustment coefficient for a first rate. The first rate is the Guaranteed Information Rate (CIR) and / or the Peak Information Rate (PIR). Processor 801 is used to determine a second rate of the first slave device based on the rate amplification factor and the first rate. The second rate is the effective CIR and / or PIR of the first slave device. Optionally, the first message may also include the first rate.

[0240] In another implementation, the communication device 80 is used to implement Figure 4 The corresponding method embodiment describes the function of the master device. Specifically, the processor 801 is used to generate a second message, which includes first indication information. The first indication information is used to indicate a rate amplification factor for the first slave device, where the rate amplification factor is an adjustment coefficient for a first rate, and the first rate is the Guaranteed Information Rate (CIR) and / or the Peak Information Rate (PIR). The transceiver 802 is used to send the second message to the first slave device. Furthermore, the transceiver 802 is also used to receive a third message from the first slave device, which includes the rate amplification factor of the first slave device. Optionally, the first indication information may also be used to indicate that the first slave device reports a first rate; in this case, the third message may also include the first rate.

[0241] In another implementation, the communication device 80 is used to implement Figure 4 The function of the first slave device corresponds to that in the method embodiment. Specifically, transceiver 802 receives a second message from the master device. The second message includes first indication information, which indicates that the first slave device should report a rate amplification factor. The rate amplification factor is an adjustment coefficient for a first rate, where the first rate is the Guaranteed Information Rate (CIR) and / or the Peak Information Rate (PIR). Processor 801 generates a third message, which includes the rate amplification factor of the first slave device. Furthermore, transceiver 802 also sends the third message to the master device. Optionally, the first indication information may also indicate that the first slave device should report a first rate; in this case, the third message may also include the first rate.

[0242] In another implementation, the communication device 80 is used to implement Figure 6 The corresponding method embodiment describes the function of the master device. Specifically, the processor 801 is used to generate a fourth message, which includes a third rate. The third rate is the Guaranteed Information Rate (CIR) and / or the Peak Information Rate (PIR). The unit of the third rate is related to the line rate of the first slave device and a preset threshold, which are used to determine the unit of the third rate. The transceiver 802 is used to send the fourth message to the first slave device.

[0243] In another implementation, the communication device 80 is used to implement Figure 6 The function of the first slave device in the corresponding method embodiment is as follows. Specifically, transceiver 802 is used to receive a fourth message from the master device. The fourth message includes a third rate, which is a Guaranteed Information Rate (CIR) and / or a Peak Information Rate (PIR). The unit of the third rate is related to the line rate of the first slave device and a preset threshold. Processor 801 is used to determine the unit of the third rate based on the line rate of the first slave device and the preset threshold.

[0244] In another implementation, the communication device 80 is used to implement Figure 7 The corresponding method embodiment describes the function of the master device. Specifically, the processor 801 is used to generate a fifth message, which includes second indication information. The second indication information instructs the first slave device to report a third rate, where the third rate is the Guaranteed Information Rate (CIR) and / or the Peak Information Rate (PIR). The unit of the third rate is related to the line rate of the first slave device and a preset threshold. The transceiver 802 is used to send the fifth message to the first slave device. Furthermore, the transceiver 802 is also used to receive a sixth message from the first slave device, which includes the third rate of the first slave device.

[0245] In another implementation, the communication device 80 is used to implement Figure 7 The transceiver 802 corresponds to the function of the first slave device in the method embodiment. Specifically, the transceiver 802 is used to receive a fifth message from the master device. The fifth message includes second indication information, which instructs the first slave device to report a third rate. The third rate is the Guaranteed Information Rate (CIR) and / or the Peak Information Rate (PIR), and the unit of the third rate is related to the line rate and a preset threshold of the first slave device. The processor 801 is used to generate a sixth message, which includes the third rate of the first slave device. The transceiver 802 is also used to send the sixth message to the master device.

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

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

[0248] The communication device 90 may include a processing module 901 (or processing unit). Optionally, it may also include an interface module 902 (or transceiver unit or transceiver module) and a storage module 903 (or storage unit). The interface module 902 is used to enable communication with other devices. The interface module 902 may be, for example, a transceiver module or an input / output module.

[0249] In one possible design, such as Figure 9One 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.

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

[0251] Alternatively, the communication device 90 may have the functions of the main device described in the embodiments of this application. For example, the communication device 90 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 8 The corresponding embodiment is the communication device 80.

[0252] 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 , Figure 4 , Figure 6 or Figure 7 Methods related to the slave device (e.g., the first slave device). For example, implementing the methods described above. Figure 2 , Figure 4 , Figure 6 or Figure 7The 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)).

[0253] 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 , Figure 4 , Figure 6 or Figure 7 Methods related to slave devices (e.g., the first slave device).

[0254] 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 , Figure 4 , Figure 6 or Figure 7 Methods related to the master device in the process.

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

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

Claims

1. An optical network communication method applied to an optical fiber network, wherein the optical fiber network includes an optical line terminal (OLT) and an optical network unit (ONU), characterized in that, The method includes: The ONU receives a first optical network unit management and control interface (OMCI) message from the OLT. The first OMCI message includes a rate amplification factor and traffic descriptor identification information of the managed entity. The rate amplification factor is an adjustment coefficient for a first rate, and the first rate is a first guaranteed information rate (CIR) and / or a first peak information rate (PIR). The ONU determines the effective CIR and / or effective PIR based on the rate amplification factor and the first rate. The default value of the rate amplification factor is 1, and the value of the rate amplification factor is greater than or equal to 1.

2. The method according to claim 1, characterized in that, The effective CIR is equal to the product of the first CIR and the rate amplification factor, and / or the effective PIR is equal to the product of the first PIR and the rate amplification factor.

3. The method according to claim 1, characterized in that, The first OMCI message also includes the first rate.

4. The method according to any one of claims 1 to 3, characterized in that, The message type of the first OMCI message is either a setup request or a creation request.

5. The method according to any one of claims 1 to 3, characterized in that, The rate amplification factor occupies one byte in the first OMCI message.

6. The method according to any one of claims 1 to 3, characterized in that, The first OMCI message is encapsulated in the payload field of a downlink 10Gbit symmetric passive optical network encapsulation mode XGEM frame.

7. The method according to any one of claims 1 to 3, characterized in that, The XGEM port identifier in the frame header of the XGEM frame encapsulating the first OMCI message is the same as the identifier information of the ONU.

8. An optical network communication method applied to an optical fiber network, wherein the optical fiber network includes an optical line terminal (OLT) and an optical network unit (ONU), characterized in that, The method includes: The OLT sends a first Optical Network Unit Management and Control Interface (OMCI) message to the ONU. The first OMCI message includes a rate amplification factor and a traffic descriptor, which is the identifier information of the managed entity. The rate amplification factor is an adjustment coefficient for a first rate, which is a first guaranteed information rate (CIR) and / or a first peak information rate (PIR). The rate amplification factor and the first rate are used to determine a valid CIR and / or a valid PIR. The default value of the rate amplification factor is 1, and the value of the rate amplification factor is greater than or equal to 1.

9. The method according to claim 8, characterized in that, The effective CIR is equal to the product of the first CIR and the rate amplification factor, and / or the effective PIR is equal to the product of the first PIR and the rate amplification factor.

10. The method according to claim 8, characterized in that, The first OMCI message also includes the first rate.

11. The method according to any one of claims 8 to 10, characterized in that, The message type of the first OMCI message is either a setup request or a creation request.

12. The method according to any one of claims 8 to 10, characterized in that, The rate amplification factor occupies one byte in the first OMCI message.

13. An optical network communication method applied to an optical fiber network, wherein the optical fiber network includes an optical line terminal (OLT) and an optical network unit (ONU), characterized in that, include: The ONU receives a second optical network unit management and control interface (OMCI) message from the OLT. The second OMCI message includes first indication information and traffic descriptor identification information of the managed entity. The first indication information is used to instruct the ONU to report a rate amplification factor. The rate amplification factor is an adjustment coefficient for a first rate. The first rate is a first guaranteed information rate (CIR) and / or a first peak information rate (PIR). The ONU sends a third OMCI message to the OLT. The third OMCI message includes the ONU's rate amplification factor and the identifier information of the managed entity of the flow descriptor. The rate amplification factor has a value greater than or equal to 1.

14. The method according to claim 13, characterized in that, The default value for the rate amplification factor is 1.

15. The method according to claim 13, characterized in that, The rate amplification factor and the first rate are used to determine the effective CIR and / or effective PIR.

16. The method according to claim 15, characterized in that, The effective CIR is equal to the product of the first CIR and the rate amplification factor, and / or the effective PIR is equal to the product of the first PIR and the rate amplification factor.

17. The method according to any one of claims 13 to 16, characterized in that, The first indication information includes a first attribute mask, in which the bit corresponding to the rate amplification factor attribute is 1.

18. The method according to any one of claims 13 to 16, characterized in that, The first indication information includes a first attribute mask, and the rate amplification factor attribute corresponds to the 9th bit in the first attribute mask.

19. The method according to any one of claims 13 to 16, characterized in that, The first indication information is also used to instruct the ONU to report the first rate, and the third OMCI message also includes the first rate.

20. An optical network communication method applied to an optical fiber network, the optical fiber network including an optical line terminal (OLT) and an optical network unit (ONU), characterized in that, include: The OLT sends a second optical network unit management and control interface (OMCI) message to the ONU. The second OMCI message includes first indication information and traffic descriptor identification information of the managed entity. The first indication information is used to instruct the ONU to report a rate amplification factor. The rate amplification factor is an adjustment coefficient for a first rate. The first rate is a first guaranteed information rate (CIR) and / or a first peak information rate (PIR). The OLT receives a third OMCI message from the ONU. The third OMCI message includes the rate amplification factor and the identifier information of the managed entity of the ONU's flow descriptor. The rate amplification factor has a value greater than or equal to 1.

21. The method according to claim 20, characterized in that, The default value for the rate amplification factor is 1.

22. The method according to claim 20, characterized in that, The rate amplification factor and the first rate are used to determine the effective CIR and / or effective PIR.

23. The method according to claim 22, characterized in that, The effective CIR is equal to the product of the first CIR and the rate amplification factor, and / or the effective PIR is equal to the product of the first PIR and the rate amplification factor.

24. The method according to any one of claims 20 to 23, characterized in that, The first indication information includes a first attribute mask, in which the bit corresponding to the rate amplification factor attribute is 1.

25. The method according to any one of claims 20 to 23, characterized in that, The first indication information includes a first attribute mask, and the rate amplification factor attribute corresponds to the 9th bit in the first attribute mask.

26. The method according to any one of claims 20 to 23, characterized in that, The first indication information is also used to instruct the ONU to report the first rate, and the third OMCI message also includes the first rate.

27. A communication device, characterized in that, The communication device is used to implement the method as described in any one of claims 1 to 7; or to implement the method as described in any one of claims 13 to 19.

28. A communication device, characterized in that, The communication device is used to implement the method as described in any one of claims 8 to 12; or to implement the method as described in any one of claims 20 to 26.

29. A communication system, characterized in that, include: The communication device as claimed in claim 27, and the communication device as claimed in claim 28.

30. 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 26.

31. 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 26.

Images