Optical network communication method and communication device

Abstract

The invention provides an optical network communication method and device, and the method comprises the steps: a first slave device can receive a rate amplification factor from a main device, and the rate amplification factor is an adjustment coefficient of a first rate (i.e., the attribute value of a CIR attribute / PIR attribute); the first slave device determines a second rate (i.e., a valid CIR / PIR of the first slave device) by means of the rate amplification factor and the first rate. Therefore, even if 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, on the basis of not changing the existing attributes, the value of the CIR / PIR used by the first slave device during working is expanded. And the CIR / PIR configuration problem of a 50G PON and a future higher-rate PON is solved.

Description

[0001] This application is a divisional application. The application number of the original application is 202410638484.6, and the original application date is May 21, 2024. The entire content of the original application is incorporated herein by reference. Technical Field

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

[0003] Broadband access technology has developed rapidly in recent years, and passive optical networks (PONs) have been widely popularized and rapidly expanded. With the continuous sharp increase in the demand for user data, 10-Gigabit-capable Passive Optical Networks (XG-PONs) have entered the stage of large-scale deployment, and the standards for the next-generation PON systems (e.g., 50-Gigabit-capable Passive Optical Networks (50GPONs)) are also being gradually developed and improved.

[0004] In the current standard, the optical line terminal (OLT) in the PON network manages the optical network unit (ONU) 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 management messages and waits for the response from the ONU. When the OLT receives a response or times out, the OLT continues to send the next message. The OLT manages and configures the managed entity (ME) of the ONU through OMCI messages.

[0005] In the current standard, the OMCI protocol defines the committed information rate (CIR) attribute and the peak information rate (PIR) attribute of the traffic descriptor managed entity, which are used to manage the CIR attribute and the PIR attribute of the ONU. The OLT realizes the configuration of the CIR attribute or the PIR attribute by sending OMCI messages related to the traffic descriptor managed entity to the ONU, or obtains the values of the CIR attribute or the PIR attribute. Since the lengths of the CIR attribute field and the PIR attribute field defined in the current standard are both 4 bytes, and the units of the CIR attribute and the PIR attribute are both bytes per second, the maximum values of the CIR attribute and the PIR attribute are 4,294,967,295 respectively. That is, the maximum CIR or PIR that can be configured through these two attributes is 4,294,967,295 bytes / s, which is approximately equal to 34 G bit / s. It can be seen that the field lengths of the CIR attribute and the PIR attribute in the current traffic descriptor managed entity are not sufficient to support the configuration of 50G PON and future higher-rate PONs. Summary of the Invention

[0006] This application provides an optical network communication method and a communication device, which are used to solve the CIR / PIR configuration problems of 50G PON and future higher-rate PONs.

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

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

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

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

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

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

[0013] In a possible implementation, the first message further includes 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 the rate amplification factor and the first rate simultaneously through the first message, which is beneficial to improving the configuration efficiency.

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

[0015] Optionally, when the message type of the first message is a setup request, the message content field of the first message further includes a first attribute mask, and the bit corresponding to the rate amplification factor attribute in the first attribute mask is 1. In addition, 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 message type of the first message is a setup 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 the first slave device receives the first message from the master device, the first slave device receives a seventh message from the master device, and the seventh message includes the identification information of the traffic descriptor managed entity and the first rate. Since the first rate and the rate amplification factor can be indicated to the first slave device through different messages respectively, it is beneficial to improve the flexibility of configuring the rate amplification factor.

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

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

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

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

[0021] In a second aspect, the present application provides an optical network communication method, which is applied to an optical fiber network. The optical fiber network includes a master device and at least one slave device, and the at least one slave device includes a first slave device. The optical network communication method provided in this aspect can be executed by the master device in the optical fiber network, or can be executed by a partial functional module or chip in the master device. Taking 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, and the rate amplification factor is an adjustment coefficient of a first rate. The first rate is a committed information rate (CIR) and / or a peak information rate (PIR). The rate amplification factor and the first rate are used to determine a second rate of the first slave device, and the second rate is the effective CIR and / or PIR of the first slave device.

[0022] In a possible implementation manner, the default value of the rate amplification factor is 1.

[0023] In a possible implementation manner, the value of the rate amplification factor is an integer greater than 0.

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

[0025] In a possible implementation manner, the first message further includes identification information of a traffic descriptor managed entity.

[0026] In a possible implementation manner, the first message further includes the first rate. For example, when the message type of the first message is a set request or a create request, the master device can configure the rate amplification factor and the first rate simultaneously through the first message, which is beneficial to improving the configuration efficiency.

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

[0028] Optionally, when the message type of the first message is a set request, the message content field of the first message further includes a first attribute mask, and the bit corresponding to the rate amplification factor attribute in the first attribute mask is 1. In addition, 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 message type of the first message is a setup 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 the first slave device receives the first message from the master device, the first slave device receives a seventh message from the master device, and the seventh message includes the identification information of the traffic descriptor managed entity and the first rate. Since the first rate and the rate amplification factor can be indicated to the first slave device through different messages respectively, it is beneficial to improve the flexibility of configuring the rate amplification factor.

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

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

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

[0033] In a 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 also many other specific implementation manners in this aspect. For specific details, reference can be made to the specific implementation manners and their beneficial effects of the first aspect, which will not be elaborated here.

[0035] In a third aspect, the present application provides an optical network communication method applied to an optical fiber network. The optical fiber network includes a master device and at least one slave device, and the at least one slave device includes a first slave device. The optical network communication method provided in this aspect can be executed by the first slave device in the optical fiber network, or can be executed by a partial functional module or chip in the first slave device. Taking the execution by the first slave device as an example, the first slave device receives a second message from the master device. The second message includes a first indication information for indicating the first slave device to report a rate amplification factor. The rate amplification factor is an adjustment coefficient of the first rate, and the first rate is a committed information rate CIR and / or a peak information rate PIR. Then, the first slave device sends a third message to the master device, and the third message includes the rate amplification factor of the first slave device.

[0036] In this aspect, the first slave device can receive first indication information from the master device to indicate that the first slave device reports a rate amplification factor, which is an adjustment coefficient of a first rate (i.e., the attribute value of the CIR attribute / PIR attribute). After receiving the first indication information, the first slave device reports the rate amplification factor of the first slave device, and the master device can combine the rate amplification factor and the first rate to determine the effective CIR / PIR of the first slave device, thereby providing the effective CIR / PIR of the first slave device to the master device. That is to say, on the basis of not changing the existing attributes, the value range of the CIR / PIR used by the first slave device during operation is extended, and the problem of CIR / PIR reporting for 50G PON and future higher-rate PONs is solved.

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

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

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

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

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

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

[0043] In this implementation, only the attribute value of the rate amplification factor attribute is indicated by the first attribute mask, rather than necessarily reporting it together with the attribute value of the CIR attribute or the attribute value of the PIR attribute, which is beneficial to improving the flexibility of the slave device to report attribute values.

[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, in addition to including the rate amplification factor, the third message further includes the first rate. 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, and the bit corresponding to the rate amplification factor attribute in the first attribute mask is 1. In addition, 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 implementation, by using the first attribute mask to indicate the attribute value of the reported rate amplification factor, as well as the attribute value of the CIR attribute and / or the attribute value of the PIR attribute, the first slave device can feedback 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, which is beneficial to improving the efficiency of the master device to obtain the attribute value and avoiding wasting signaling overhead due to multiple reports.

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

[0047] In a possible implementation, the message type of the third message is a get response, the identification information field of the managed entity of the third message includes the identification information of the traffic descriptor managed entity, and the message content field of the third message includes the first attribute mask and the attribute value of the rate amplification factor attribute. Optionally, the message content field of the third message further includes the attribute value of the CIR attribute and / or the attribute value of the PIR attribute.

[0048] In a 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 a 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 also many other specific implementation manners in this aspect. For specific details, reference can be made to the specific implementation manners and their beneficial effects of the first aspect, which will not be elaborated here.

[0051] Fourthly, the present application provides an optical network communication method, which is applied to an optical fiber network. The optical fiber network includes a master device and at least one slave device, and the at least one slave device includes a first slave device. The optical network communication method provided in this aspect can be executed by the master device in the optical fiber network, or can be executed by some functional modules or chips in the master device. Taking the execution by the master device as an example, the master device sends a second message to the first slave device. The second message includes first indication information, and the first indication information is used to instruct the first slave device to report a first rate and a rate amplification factor. The rate amplification factor is an adjustment coefficient of the first rate, and the first rate is a committed 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 includes the rate amplification factor and the first rate of the first slave device.

[0052] In a possible implementation manner, the default value of the rate amplification factor is 1.

[0053] In a possible implementation manner, the value of the rate amplification factor is an integer greater than 0.

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

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

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

[0057] In a possible implementation manner, when the first indication information is only used to instruct the first slave device to report the rate amplification factor, the first indication information is a first attribute mask. The bit corresponding to the rate amplification factor attribute in the first attribute mask is 1, indicating a request for the attribute value of the rate amplification factor attribute of the first slave device. 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 instruct the first slave device to report a first rate, that is, the first indication information is used to instruct the first slave device to report a rate amplification factor and a first rate. In this case, in addition to including the rate amplification factor, the third message further includes the first rate. When the first indication information is used to instruct the first slave device to report the rate amplification factor and the first rate, the first indication information is a first attribute mask, and the bit corresponding to the rate amplification factor attribute in the first attribute mask is 1. In addition, 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 a possible implementation, the message type of the second message is a get request, the identification information field of the managed entity of the second message includes the identification information of the traffic descriptor managed entity, and the message content field of the second message includes the first attribute mask.

[0060] In a possible implementation, the message type of the third message is a get response, the identification information field of the managed entity of the third message includes the identification information of the traffic descriptor managed entity, and the message content field of the third message includes the first attribute mask and the attribute value of the rate amplification factor attribute. Optionally, the message content field of the third message further includes the attribute value of the CIR attribute and / or the attribute value of the PIR attribute.

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

[0062] In a 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 also various other specific implementation manners in this aspect. For specific details, reference can be made to the specific implementation manners and their beneficial effects of the third aspect, which will not be elaborated here.

[0064] Fifth aspect, the present application provides an optical network communication method, which is applied to an optical fiber network. The optical fiber network includes a master device and at least one slave device, and the at least one slave device includes a first slave device. The optical network communication method provided in this aspect can be executed by the first slave device in the optical fiber network, or can be executed by some functional modules or chips in the first slave device. Taking the execution by the first slave device as an example, the first slave device receives a fourth message from the master device. The fourth message includes a third rate, and the third rate is the committed 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; 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 the preset threshold, and the first slave device can determine the unit of the third rate based on the line rate of the first slave device and the preset threshold. Therefore, even when the value range of the third rate is limited, the first slave device can determine the unit of the third rate based on the line rate of the first slave device and the preset threshold, and further determine the effective CIR / PIR of the first slave device. This solves the problem of CIR / PIR configuration for 50GPON and future higher-rate PONs.

[0066] In a possible implementation manner, 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 an integer greater than 0.

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

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

[0069] In a possible implementation manner, the fourth message further includes the identification information of the traffic descriptor managed entity.

[0070] In a possible implementation manner, the message type of the fourth message is a set request or a create request. The identification information field of the managed entity of the fourth message includes the identification information of the traffic descriptor managed entity, 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 a 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 unit of the effective CIR of the first slave device is bytes per second; when the line rate of the first slave device is greater than a 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 unit of the effective PIR of the first slave device is bytes per second.

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

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

[0074] In a sixth aspect, the present application provides an optical network communication method, which is applied to an optical fiber network. The optical fiber network includes a master device and at least one slave device, and the at least one slave device includes a first slave device. The optical network communication method provided in this aspect can be executed by the master device in the optical fiber network, or can be executed by some functional modules or chips in the master device. Taking the master device as an example, the master device sends a fourth message to the first slave device. The fourth message includes a third rate, and the third rate is the committed 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 the preset threshold, and the line rate and the preset threshold of the first slave device are used to determine the unit of the third rate.

[0075] In a possible implementation, 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 an integer greater than 0.

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

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

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

[0079] In a possible implementation, the message type of the fourth message is a set request or a create request. The identification information field of the managed entity of the fourth message includes the identification information of the traffic descriptor managed entity, 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 a 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 unit of the effective CIR of the first slave device is bytes per second; when the line rate of the first slave device is greater than a 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 unit of the effective PIR of the first slave device is bytes per second.

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

[0082] In a 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 also many other specific implementation manners in this aspect. For specific details, reference can be made to the specific implementation manners and their beneficial effects of the fifth aspect, which will not be elaborated here.

[0084] In a seventh aspect, the present application provides an optical network communication method applied to an optical fiber network. The optical fiber network includes a master device and at least one slave device, and the at least one slave device includes a first slave device. The optical network communication method provided in this aspect can be executed by the first slave device in the optical fiber network, or can be executed by a partial functional module or chip in the first slave device. Taking the execution by the first slave device as an example, the first slave device receives a fifth message from the master device. The fifth message includes second indication information for instructing the first slave device to report a third rate. The third rate is a committed information rate CIR and / or a peak information rate PIR, and the unit of the third rate is 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, and the sixth message includes the third rate of the first slave device.

[0085] In this aspect, the first slave device can receive the second indication information from the master device to instruct the first slave device to report the third rate (i.e., the attribute value of the CIR attribute / PIR attribute). Since the unit of the third rate is related to the line rate of the first slave device and a preset threshold, after receiving the second indication information, the first slave device reports the attribute value of the CIR attribute / PIR attribute, and the master device itself determines the effective CIR / PIR of the first slave device, thereby indirectly providing the effective CIR / PIR of the first slave device to the master device. That is to say, on the basis of not changing the existing attributes, the value range of the CIR / PIR used by the first slave device during operation is extended, and the problem of CIR / PIR reporting for 50G PON and future higher-rate PONs is solved.

[0086] In a 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 a possible implementation, the default value of N is 1.

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

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

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

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

[0092] In a possible implementation, the message type of the sixth message is a get response, the identification information field of the managed entity of the sixth message includes the identification information of the traffic descriptor managed entity, 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 a possible implementation, when the line rate of the first slave device is greater than the 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 unit of the effective CIR of the first slave device is 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 unit of the effective PIR of the first slave device is bytes per second.

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

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

[0096] In an eighth aspect, the present application provides an optical network communication method, which is applied to an optical fiber network. The optical fiber network includes a master device and at least one slave device, and the at least one slave device includes a first slave device. The optical network communication method provided in this aspect can be executed by the master device in the optical fiber network, or can be executed by a partial functional module or chip in the master device. Taking the execution by the master device as an example, the master device sends a fifth message to the first slave device. The fifth message includes second indication information, and the second indication information is used to instruct the first slave device to report a third rate. The third rate is a committed information rate (CIR) and / or a peak information rate (PIR), and the unit of the third rate is 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, and the sixth message includes 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 attribute / PIR attribute) through the second indication information. Since the unit of the third rate is related to the line rate of the first slave device and the preset threshold, after receiving the second indication information, the first slave device reports the attribute value of the CIR attribute / PIR attribute, and the master device itself determines the effective CIR / PIR of the first slave device, thereby indirectly providing the effective CIR / PIR of the first slave device to the master device. That is to say, on the basis of not changing the existing attributes, the value range of the CIR / PIR used by the first slave device during operation is expanded, and the problem of CIR / PIR reporting for 50G PON and future higher-rate PONs is solved.

[0098] In a possible implementation manner, 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 an integer greater than 0.

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

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

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

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

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

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

[0105] In a 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 unit of the effective CIR of the first slave device is bytes per second; when the line rate of the first slave device is greater than a 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 unit of the effective PIR of the first slave device is bytes per second.

[0106] In a possible implementation, the fifth message is encapsulated in the payload field of a downstream XGEM frame, and the XGEM port identification in the frame header of the downstream XGEM frame is the same as the identification information of the first slave device; the sixth message is encapsulated in the payload field of an upstream XGEM frame, and the XGEM port identification in the frame header of the upstream XGEM frame is the same as the identification information of the first slave device.

[0107] In a 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 also various other specific implementation manners in this aspect. For specific details, reference can be made to the specific implementation manners and their beneficial effects in the seventh aspect, which will not be elaborated here.

[0109] In a ninth aspect, an embodiment of the present application provides a communication device, which may be the master device in the foregoing embodiments, or a chip within the master device. The communication device may include a processing module and a transceiver module. When the communication device is the master device, the processing module may be a processor, and the transceiver module may be a transceiver; the master device may further include a storage module, and the storage module may be a memory; the storage module is used to store instructions, and the processing module executes the instructions stored in the storage module so that the master device executes the methods in the second aspect, the fourth aspect, the sixth aspect, the eighth aspect, and any implementation manner of the foregoing aspects. When the communication device is a chip within the master device, the processing module may be a processor, and the transceiver module may be an input / output interface, a pin, a circuit, etc.; the processing module executes the instructions stored in the storage module so that the master device executes the methods in the second aspect, the fourth aspect, the sixth aspect, the eighth aspect, and any implementation manner of the foregoing aspects. The storage module may be a storage module within the chip (such as a register, a cache, etc.), or a storage module outside the chip within the master device (such as a read-only memory, a random access memory, etc.).

[0110] In a tenth aspect, an embodiment of the present application provides a communication device, which may be the slave device (such as the first slave device) in the foregoing embodiments, or a chip within the slave device (such as the first slave device). The communication device may include a processing module and a transceiver module. When the communication device is the slave device (such as the first slave device), the processing module may be a processor, and the transceiver module may be a transceiver. Optionally, the slave device (such as the first slave device) may further include a storage module, and the storage module may be a memory; the storage module is used to store instructions, and the processing module executes the instructions stored in the storage module so that the slave device (such as the first slave device) executes the methods in the first aspect, the third aspect, the fifth aspect, the seventh aspect, and any implementation manner of the foregoing aspects. When the communication device is a chip within the slave device (such as the first slave device), the processing module may be a processor, and the transceiver module may be an input / output interface, a pin, a circuit, etc.; the processing module executes the instructions stored in the storage module so that the slave device (such as the first slave device) executes the methods in the first aspect, the third aspect, the fifth aspect, the seventh aspect, and any implementation manner of the foregoing aspects. The storage module may be a storage module within the chip (such as a register, a cache, etc.), or a storage module outside the chip within the slave device (such as the first slave device) (such as a read-only memory, a random access memory, etc.).

[0111] Eleventh aspect, the present application provides a communication device, which may be an integrated circuit chip. The integrated circuit chip includes a processor. The processor is coupled to a memory for storing programs or instructions, and when the programs or instructions are executed by the processor, the communication device is caused to execute the methods described in any one of the various embodiments of the foregoing aspects.

[0112] Twelfth aspect, an embodiment of the present application provides a computer program product containing instructions, which when run on a computer, causes the computer to execute the methods described in any one of the various embodiments of the foregoing aspects.

[0113] Thirteenth aspect, an embodiment of the present application provides a computer-readable storage medium including instructions, which when run on a computer, causes the computer to execute the methods described in any one of the various embodiments of the foregoing aspects.

[0114] Fourteenth aspect, an embodiment of the present application provides an optical fiber network, which includes the master device described in the second aspect and any one of the embodiments of the second aspect, and the slave device (e.g., the first slave device) described in the first aspect and any one of the embodiments of the first aspect; or, the optical fiber network includes the master device described in the fourth aspect and any one of the embodiments of the fourth aspect, and the slave device (e.g., the first slave device) described in the third aspect and any one of the embodiments of the third aspect; the optical fiber network includes the master device described in the sixth aspect and any one of the embodiments of the sixth aspect, and the slave device (e.g., the first slave device) described in the fifth aspect and any one of the embodiments of the fifth aspect; the optical fiber network includes the master device described in the eighth aspect and any one of the embodiments of the eighth aspect, and the slave device (e.g., the first slave device) described in the seventh aspect and any one of the embodiments of the seventh aspect. Description of the Drawings

[0115] Figure 1A FIG. is an example diagram of the network architecture of an optical fiber network;

[0116] Figure 1B FIG. is another example diagram of the network architecture of an optical fiber network;

[0117] Figure 2 FIG. is a schematic flowchart of an optical network communication method in the present application;

[0118] Figure 3A FIG. is an example diagram of the message format of a traditional create request message;

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

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

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

[0122] Figure 4 Another process schematic diagram of the optical network communication method in this application;

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

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

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

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

[0127] Figure 6 Another process schematic diagram of the optical network communication method in this application;

[0128] Figure 7 Another process schematic diagram of the optical network communication method in this application;

[0129] Figure 8 An example diagram of an embodiment of the communication device in this application;

[0130] Figure 9 Another example diagram of an embodiment of the communication device in this application. Detailed implementation manners

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

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

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

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

[0135] The optical network communication method provided by this application is applied to an optical fiber network. Figure 1A It is an example diagram of the architecture of an optical fiber network in the traditional technology. As Figure 1AAs shown in the figure, the optical fiber network includes an optical line terminal (OLT), an optical distribution network (ODN), and an optical network unit (ONU) (or an optical network terminal (ONT)). The OLT and the ONU are connected and communicate through optical fibers. The OLT is generally 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 beam splitters), combiners, etc. In addition, the aforementioned OLT can be connected to the operator network through a network-side interface, the OLT can be connected to the ODN through a dedicated interface, the ODN is connected to the ONU (or ONT) through a dedicated interface, and the ONU (or ONT) is connected to the user-side network through a user-side interface or a dedicated interface. In the downstream direction, the OLT broadcasts a downstream optical signal, and distributes the downstream optical signal to each ONU (or ONT) through the ODN. In the upstream direction, in a time division multiple access (TDMA) manner, each ONU (or ONT) sends an upstream optical signal in its respective upstream time slot allocated by the OLT.

[0136] As Figure 1B shown, it is a schematic structural diagram of the optical fiber network provided by this application. The optical fiber network provided by this application includes a master device 01 and at least one slave device 02. The master device 01 is connected to the at least one slave device 02 through an 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 the at least one slave device through an optical distribution network. In one example, the slave device can be directly connected to the user's terminal device, and the terminal device can be a mobile phone or a tablet computer connected to the aforementioned router through WiFi, or can also be an Internet of Things device (for example, an indoor temperature control device, an indoor monitoring device, and other artificial intelligence devices, etc.). In another example, there is another network (such as Ethernet, etc.) between the slave device and the user's terminal device. The slave device is an optical modem provided by the operator, and the optical modem is connected to devices such as an indoor router. This application is introduced by taking the master device and the slave device as examples.

[0137] It should be understood that this application does not limit the specific type of the optical fiber. The optical fiber described in this application can be a single optical fiber, a loose tube optical fiber, an optical cable, an optical and electrical composite cable, etc.

[0138] It should also be understood that the optical network communication method provided by this application can be applied to a PON network. 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 higher data rates, etc. This application does not impose any restrictions.

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

[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 foregoing commands and then reply with a response. In the OMCI protocol, 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 management information base is the managed entity (also known as the management entity) (ME). The managed entity is an abstract representation of the resources and / or services of the slave device and is a management object abstracted from numerous resources and / or services to be managed. When the foregoing managed entity is concretized to a specific slave device or a specific service, it becomes an instance. The master device realizes the configuration management function of each managed entity ME by configuring instances for the slave device.

[0141] This application mainly relates to a managed entity of a traffic descriptor (hereinafter referred to as the traffic descriptor ME). This traffic descriptor ME is used to manage the traffic of a slave device. For example, a slave device that supports priority control can configure a data managed entity of a media access control (MAC) bridge port to point to the traffic descriptor managed entity to implement traffic management such as marking traffic and policing traffic. Another example is that a slave device that supports rate control can configure a data managed entity of a MAC bridge port or a GEM port network connection termination point (CTP) managed entity to point to the traffic descriptor managed entity to implement traffic management such as marking traffic and traffic shaping.

[0142] In the current standard, this traffic descriptor ME includes various attributes as shown in Table 1 below:

[0143] Table 1

[0144] Order of attributes Attribute Read / write Optional Attribute size 1 Managed entity identifier Readable Required 2 bytes 2 Committed information rate CIR Readable, writable, set at creation Optional 4 bytes 3 Peak information rate PIR Readable, writable, set at creation Optional 4 bytes 4 Committed burst size Readable, writable, set at creation Optional 4 bytes 5 Peak burst size Readable, writable, set at creation Optional 4 bytes 6 Color mode Readable, writable, set at creation Optional 1 byte 7 Ingress color label Readable, writable, set at creation Optional 1 byte 8 Egress color label Readable, writable, set at creation Optional 1 byte 9 Algorithm type Readable, set at creation Optional 1 byte

[0145] As shown in Table 1, the first column represents the order of multiple attributes included in the traffic descriptor ME. When the master device configures multiple attributes of the traffic descriptor ME for the slave device, or when the master device obtains multiple attributes of the traffic descriptor ME from the slave device, the attribute values or attribute masks are filled in according to the order of the foregoing attributes. The second column is the names of multiple attributes included in the traffic descriptor ME. The third column indicates whether the master device can perform read (Read) and write (Write) operations on this attribute, and when to set it. Among them, the 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 of this attribute; the 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 of this attribute. "Set-by-create" means that the master device sets the attribute value of this attribute when creating the first instance of this ME. The fourth column indicates which attributes among the multiple attributes of the traffic descriptor ME are mandatory attributes and which are optional attributes. The fifth column indicates the byte size occupied by the attribute value of each attribute.

[0146] This application mainly relates to the first three attributes of the traffic descriptor ME. As shown in Table 1, the first row is the first attribute of the traffic descriptor ME, that is, the Managed entity ID (ME ID) attribute, which uniquely identifies an instance of the traffic descriptor ME. The ME ID attribute is a readable and writable attribute, and it is a mandatory attribute with a size of 2 bytes. The second row is the second attribute of the traffic descriptor ME, that is, 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 creating an instance, is a readable and writable attribute, and is an optional attribute with a size of 4 bytes. The third row is the third attribute of the traffic descriptor ME, that is, 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 creating an instance, is a readable and writable attribute, and is an optional attribute with a size of 4 bytes.

[0147] Since the lengths of both the CIR attribute field and the PIR attribute field are 4 bytes, and the units of both the CIR attribute and the PIR attribute are bytes per second (byte / s), the maximum values of the CIR attribute and the PIR attribute are respectively 4,294,967,295 (i.e., 2 32 ^32 - 1), that is, the maximum CIR or PIR that can be configured through these two attributes is 4,294,967,295 bytes / s, approximately equal to 34 G bit / s. That is to say, according to the current standard, the master device can only configure a CIR or PIR of 34 G bit / s for the slave device. However, the PON system has developed to 50G PON and even higher-speed PONs in the future, that is, the working line rate of the slave device can reach 50 G bit / s or even higher line rates, and it is necessary for the master device to configure a CIR or PIR of 50 G bit / s or even higher line rates for the slave device. Obviously, the field lengths of the CIR attribute and the PIR attribute in the current traffic descriptor ME are not sufficient to support the configuration of 50G PON and future higher-speed PONs.

[0148] In response to this, this application provides a variety of solutions to solve the CIR / PIR configuration problems of 50G PON and future higher-speed PONs.

[0149] In one solution, a new attribute of the traffic descriptor ME is defined, namely the rate amplification factor attribute introduced later. This rate amplification factor attribute and the predefined CIR attribute in the standard jointly determine the effective CIR of the slave device, and this rate amplification factor attribute and the predefined PIR attribute in the standard jointly determine the effective PIR of the slave device. For specific details, please refer to the relevant descriptions in the following text. Figure 2 and Figure 4 the relevant descriptions in the corresponding embodiments.

[0150] In another solution, it is proposed to modify the definitions of CIR and PIR in the current standard, that is, to define that the units of CIR and PIR are related to the line rate and the preset threshold of the slave device, rather than necessarily being bytes per second. For specific details, please refer to the relevant descriptions in the following text. Figure 6 and Figure 7 the relevant descriptions in the corresponding embodiments.

[0151] First, in combination with Figure 2 and Figure 4 the main process of the first solution of the optical network communication method provided by this application is introduced:

[0152] As Figure 2 shown, it is a schematic diagram of an embodiment of the optical network communication method provided by this application. In this embodiment, the master device configures attributes for the first slave device through a create message or a set message. The first slave device is one of the multiple slave devices connected to the master device. This embodiment takes the interaction between the master device and the first slave device as an example for illustration. Of course, the entity executing the actions of the master device in this method can also be a device, module, or chip in the master device; the entity executing the actions of the first slave device in this method can also be a device, module, or chip in the first slave device. This embodiment does not make specific limitations in this regard. Exemplarily, as Figure 2 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 the first message to the first slave device through an optical fiber; correspondingly, the first slave device receives the first message from the master device through an optical fiber. Among them, the first message includes a rate amplification factor. Optionally, the first message further includes a first rate. The rate amplification factor is an adjustment coefficient of the first rate.

[0155] Among them, the first rate is the CIR and / or PIR. For example, the first rate is the CIR; or, the first rate is the PIR; or, the first rate is the CIR and PIR. In one implementation, the first rate may be the CIR value and / or PIR value indicated by the master device to the first slave device through the CIR field and / or PIR field in the current standard. For example, before the master device sends the first message to the first slave device, the master device sends a seventh message to the first slave device, and the seventh message includes the first rate. In another implementation, the first rate may be the CIR value and / or PIR value indicated by the master device to the first slave device through the CIR field and / or PIR field in the first message. For example, the first message includes not only the rate amplification factor but also the first rate. In 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 CIR value and / or PIR value that the first slave device uses by default when the master device does not configure the CIR and / or PIR for the first slave device. For the convenience of introduction, the following takes the first rate carried in the first message as an example for introduction. It should be understood that the "CIR carried in the first message" in the following text can be replaced by the "CIR carried in the seventh message", or replaced by the "default CIR", and the "PIR carried in the first message" in the following text can be replaced by the "PIR carried in the seventh message", or replaced by the "default PIR".

[0156] Among them, the rate amplification factor is an adjustment coefficient of the first rate, that is, the rate amplification factor is an adjustment coefficient of the CIR carried in the first message and / or the PIR carried in the first message. It can be understood that the rate amplification factor and the first rate are used to determine the second rate, and the second rate is the valid CIR (valid CIR) and / or valid PIR (valid PIR) of the first slave device. Among them, the valid CIR (valid CIR) of the first slave device can be understood as the effective CIR (effective CIR) of the first slave device, or can be understood as the CIR used when the first slave device works; the valid PIR (valid PIR) of the first slave device can be understood as the effective PIR (effective PIR) of the first slave device, or can be understood as the PIR used when the first slave device works.

[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 valid CIR of the first slave device (that is, the CIR used when the first slave device works). Another example is that the product of the rate amplification factor and the PIR carried in the first message is equal to the valid PIR of the first slave device (that is, the PIR used when the first slave device works).

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

[0159] It should be noted that, in the current standards and the future standard development trend, the master device manages and maintains the CIR and PIR of the slave device through the CIR attribute and PIR attribute of the traffic descriptor ME. Therefore, the first message includes the first rate, which can be understood as that the first message carries the attribute value of the CIR attribute and / or the attribute value of the PIR attribute. In addition, the rate amplification factor is a newly defined attribute of a traffic descriptor ME in this application, that is, the rate amplification factor attribute. The first message includes the rate amplification factor, which can be understood as that the first message carries 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 attribute value of the rate amplification factor attribute is 2 4 (i.e., 16), indicating that the maximum value of the CIR (or PIR) used when the first slave device operates can be 16 times the attribute value of the CIR attribute (or PIR attribute) carried by the first message. Another example, if the rate amplification factor attribute occupies 2 bytes, the maximum value of the attribute value of the rate amplification factor attribute is 2 8 (i.e., 256), indicating that the maximum value of the CIR (or PIR) used when the first slave device operates can be 256 times the attribute value of the CIR attribute (or PIR attribute) carried by the first message.

[0161] Exemplarily, the attributes included in the traffic descriptor ME provided in this application are shown in Table 2 below:

[0162] Table 2

[0163] Order of attributes Attribute Read / write Optional Attribute size 1 Managed entity identifier Readable Required 2 bytes 2 Committed information rate CIR Readable, writable, set at creation Optional 4 bytes 3 Peak information rate PIR Readable, writable, set at creation Optional 4 bytes 4 Committed burst size Readable, writable, set at creation Optional 4 bytes 5 Peak burst size Readable, writable, set at creation Optional 4 bytes 6 Color mode Readable, writable, set at creation Optional 1 byte 7 Ingress color label Readable, writable, set at creation Optional 1 byte 8 Egress color label Readable, writable, set at creation Optional 1 byte 9 Algorithm type Readable, set at creation Optional 1 byte 10 Rate amplification factor Readable, writable, set at creation Optional 2 bytes

[0164] In the example shown in Table 2, the present application newly defines the 10th attribute of the traffic descriptor ME, namely the rate amplification factor attribute. Since this rate amplification factor attribute is related to the CIR attribute or the PIR attribute, this rate amplification factor can also be referred to as the CIR / PIR scale factor. The rate amplification factor attribute can be defined as a readable attribute, that is, the master device can read the attribute value of the rate amplification factor attribute from the slave device (for example, the first slave device) through the get process. The rate amplification factor attribute can be defined as a writable attribute, that is, the master device can configure the attribute value of the rate amplification factor attribute for the slave device (for example, the first slave device) through the create process or the set process. In addition, the rate amplification factor attribute is an attribute set-by-create, that is, the master device can set the attribute value of the rate amplification factor attribute used by the first slave device when creating an instance of the traffic descriptor ME of the first slave device. Optionally, the rate amplification factor attribute is an optionally configurable attribute. The default value of the rate amplification factor is 1. Optionally, the size of the rate amplification factor attribute is 2 bytes. Other attributes shown in Table 2 are the same as the current standard definitions and will not be elaborated here.

[0165] It should be understood that the definitions of the rate amplification factor attribute shown in Table 2 are only an example, not a strict limitation. For example, if other new attributes of the traffic descriptor ME are introduced in the standard, the rate amplification factor attribute can also be the 11th attribute of the traffic descriptor ME. Another example is that the rate amplification factor may also be defined as other byte sizes, such as 1 byte, 3 bytes, or 4 bytes, etc. For ease of understanding, only the example shown in Table 2 will be used for introduction hereinafter.

[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, and the master device and the first slave device can communicate through OMCI messages. Therefore, the first message can be an OMCI message. Generally, OMCI messages include messages related to the create process (for example, the create request message, also referred to as the create message), messages related to the set process (for example, the set request message, also referred to as the set message), and messages related to the get process (for example, the get request message, also referred to as the get message). In this embodiment, the first message is a create request message or a set request message.

[0167] The first message will be introduced below in combination with a specific message format:

[0168] In a possible implementation, the first message is a creation request message, that is, the message type of the first message is a creation request, which is the message sent by the master device to the first slave device when first creating an instance of the traffic descriptor ME of the first slave device. The identification information field of the managed entity of the first message includes the identification information of the traffic descriptor managed entity, 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 further includes the attribute value of the CIR attribute and / or the attribute value of the PIR attribute.

[0169] Exemplarily, as Figure 3A shown, it is an example diagram of the creation request message provided by this application. Among them, the 1st to 2nd bytes are the transaction correlation identifier (TCI) field, which is used to identify the same set of request messages and response messages. For example, it is used to match the request message (or command) from the master device to the slave device and the response message from the slave device to the master device. Generally, the values of the transaction correlation identifier fields in a set of corresponding request and response messages are the same. The 3rd byte is the message type (MT) field, which is used to indicate the purpose or action of the message. It can also be understood as indicating the message type of the message. Among them, the 1st to 5th bits of the 3rd byte are the message type (MT) bits, which are used to indicate the message type, such as message types like create, delete, set, get, etc.; the 6th bit of the 3rd byte is the acknowledge request (AR) bit, which is used to indicate whether the message requires a response from the peer end; the 7th bit of the 3rd byte is the acknowledge (AK) bit, which is used to indicate whether to respond to the message; the 8th bit of the 3rd byte is a reserved bit, fixed to 0. Figure 3A The message type of the shown example is the create request type. The 4th byte is the device identifier field. For Figure 3A the shown baseline OMCI message format, this field is a fixed value of 0x0A. The 5th to 8th bytes are the message entity identifier, which includes the entity class and the entity instance corresponding to it. In Figure 3AIn the example shown, the values of the 5th to 6th bytes are 280, indicating the managed entity of the traffic descriptor, that is, the ME ID of the managed entity of the traffic descriptor. The 9th to 40th bytes are the message contents field, which is used to carry the message content, that is, to encapsulate the packet payload. The last 4 bytes are the message integrity check (MIC) field, which is used for message integrity verification.

[0170] Since the first byte of the message contents field in the create message starts with the attribute value of the first set-by-create attribute, and space is allocated for each set-by-create attribute in the create message in sequence and according to the size of the attribute. Therefore, combining the aforementioned Table 2, it can be seen that the first attribute value in the message contents field is the attribute value of the 4-byte CIR attribute, occupying the 9th to 12th bytes; the second attribute value in the message contents field is the attribute value of the 4-byte PIR attribute, occupying the 13th to 16th bytes, and so on. The ninth attribute value in the message contents field is the attribute value of the 2-byte rate amplification factor attribute, occupying the 29th to 30th bytes. The remaining bytes in the message contents field (i.e., the 31st to 40th bytes) are filled with zero values. Compared with Figure 3B the create request message for configuring CIR / PIR in the traditional technology shown, in the traditional technology, the 29th to 40th bytes of the message contents field are all filled with zero values.

[0171] In another possible implementation, the first message is a set request message, that is, the message type of the first message is a set request. For example, when the master device needs to reconfigure the instance of the traffic descriptor ME of the first slave device, it sends a set request message to the first slave device. The identification information field of the managed entity of the first message includes the identification information of the managed entity of the traffic descriptor, and the message contents field of the first message includes the attribute value of the rate amplification factor attribute. Optionally, the message contents field of the first message further 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 further includes an Attribute mask, which is used to indicate which attribute values are carried in the message content field. The size of the Attribute mask is 2 bytes (i.e., 16 bits). Therefore, the Attribute mask can indicate at most 16 attributes. The Attribute mask can be a bit map used in get messages (i.e., get request messages), get response messages, create response messages, and set messages (i.e., set request messages), which indicates which attributes are requested or provided. The Attribute mask corresponds to the order of the attributes after the ME ID in the attributes of the traffic descriptor ME from the high-order bit to the low-order bit (i.e., from the 8th bit to the 1st bit) (i.e., the order of the attributes after the ME ID shown in Table 2). Since the CIR attribute is the 2nd attribute of the traffic descriptor entity (i.e., the 1st attribute after the MEID attribute), the CIR attribute corresponds to the 1st bit in the Attribute mask, and the PIR attribute is the 3rd attribute of the traffic descriptor entity (i.e., the 2nd attribute after the ME ID attribute), so the PIR attribute corresponds to the 2nd bit in the Attribute mask. If the message content field carries the attribute value of the CIR attribute, the 1st bit corresponding to the CIR attribute in the Attribute mask is 1; if the message content field does not carry the attribute value of the CIR attribute, the 1st bit corresponding to the CIR attribute in the Attribute mask is 0. The same applies to the remaining attributes, which will not be elaborated here.

[0173] In this application, the Attribute mask that indicates 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 traffic descriptor entity, i.e., the 9th attribute after the ME ID attribute, the rate amplification factor attribute corresponds to the 9th bit in the first Attribute mask.

[0174] Exemplarily, as Figure 3C shown, it is an example diagram of the set request message provided by this application. Figure 3C The set request message shown Figure 3A compared with the create request message shown, only the message type field and the message content field are different. For the explanations of the remaining fields, please refer to the relevant descriptions of the example shown Figure 3A above, which will not be elaborated here. As Figure 3CAs shown, the message type indicated by the third byte in the message type (MT) field is the set request type. The 9th to 40th bytes are the message contents field. Among them, the 9th to 10th bytes are the Attribute mask. The 9th to 10th bytes of this Attribute mask correspond to the order of the attributes after the ME ID in the attributes of the traffic descriptor ME from the high-order bit to the low-order bit (i.e., from the 8th bit to the 1st bit) (i.e., the order of the 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. The 8th bit of the 10th byte corresponds to the rate amplification factor attribute. In one example, Figure 3C As shown, if the first message carries the attribute value of the CIR attribute, the attribute value of the PIR attribute, and the attribute value of the rate amplification factor attribute, then the 8th bit of the 9th byte is 1, indicating that the message contents field carries the attribute value of the CIR attribute, the 7th bit of the 9th byte is 1, indicating that it carries the attribute value of the PIR attribute, and the 8th bit of the 10th byte is 1, indicating that it carries the attribute value of the rate amplification factor attribute. In another example, if the first message carries the attribute value of the rate amplification factor attribute, then the 8th bit of the 9th byte is 0, indicating that the message contents field does not carry the attribute value of the CIR attribute, the 7th bit of the 9th byte is 0, indicating that it does not carry the attribute value of the PIR attribute, and the 8th bit of the 10th byte is 1, indicating that it carries the attribute value of the rate amplification factor attribute. It should be understood that according to the different types of attribute values carried in the message contents field, there can be other examples of the Attribute mask, which will not be elaborated here.

[0175] In addition, the remaining bytes of the message contents field are used to carry the attribute values of the attributes indicated by the Attribute mask. It should be noted that the message contents field of the set request message is different from that of the create request message. The first byte of the message contents field of the create request message starts with the attribute value of the first set-by-create attribute, and in order and according to the size of this attribute, space is allocated for each set-by-create attribute in the create message. However, the message contents field of the set request message only carries the attribute values of the attributes indicated by the Attribute mask, and does not necessarily carry the attribute values of all set-by-create attributes. Optionally, the attribute value of the rate amplification factor attribute can be carried in the nth to (n + 2)th bytes of the message contents 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 sets the attribute values of all attributes of the configured traffic descriptor ME, referring to Table 2 above, bytes 11 to 14 are the attribute values of the 4-byte CIR attribute, bytes 15 to 18 are the attribute values of the 4-byte PIR attribute, and so on. Bytes 31 to 32 are the attribute values of the 2-byte rate amplification factor attribute, and the remaining bytes in the message content field (i.e., bytes 33 to 40) are filled with zero values. In another example, if the request message sets the CIR attribute, PIR attribute, and rate amplification factor attribute, referring to Table 2 above, bytes 11 to 14 are the attribute values of the 4-byte CIR attribute, bytes 15 to 18 are the attribute values of the 4-byte PIR attribute, bytes 19 to 20 are the attribute values of the 2-byte rate amplification factor attribute, and the remaining bytes in the message content field (i.e., bytes 21 to 40) are filled with zero values. In another example, if the request message sets the CIR attribute (or PIR attribute) and rate amplification factor attribute, referring to Table 2 above, bytes 11 to 14 are the attribute values of the 4-byte CIR attribute (or PIR attribute), bytes 15 to 16 are the attribute values of the 2-byte rate amplification factor attribute, and the remaining bytes in the message content field (i.e., bytes 17 to 40) are filled with zero values. In another example, if the request message only sets the rate amplification factor attribute, bytes 11 to 12 are the attribute values of the 2-byte rate amplification factor attribute, and the remaining bytes in the message content field (i.e., bytes 13 to 40) are filled with zero values. In practical applications, there may be other examples, which will not be listed one by one here.

[0177] It should be noted that Figure 3D compared with the setup request message for configuring CIR / PIR in the traditional technology shown, in the traditional technology, since the attribute value of the rate amplification factor attribute is not carried, the 8th bit of byte 10 in the message content field is 0, and the message content field does not contain the attribute value of the rate amplification factor attribute.

[0178] It should be understood that in this embodiment Figure 3A 、 Figure 3B 、 Figure 3C and Figure 3D are all introduced by taking the Baseline OMCI message format as an example. In practical applications, the various types of messages described above Figure 3A 、 Figure 3B 、 Figure 3C and Figure 3D can also adopt the Extended OMCI message format with variable length, which will not be elaborated here.

[0179] Optionally, the first message is encapsulated in the payload field of the downstream XG-PON encapsulation mode (10-Gigabit passive optical network encapsulation method, XGEM frame). The header (XGEM Header) of the downstream XGEM frame contains information for differentiating different OMCI XGEM Ports (hereinafter referred to as XGEM Ports for short). The XGEM Port is a logical port on the slave device and is used to carry the data from the downstream PON port of the master device. The identifiers of the XGEM Ports of different slave devices are different. Therefore, different slave devices can be differentiated according to the identifiers of the XGEM Ports. In this embodiment, the XGEM port identifier (XGEM port ID) in the header (XGEM Header) of the downstream XGEM frame is the same as the identifier information of the first slave device (for example, 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] Wherein, the second rate is the effective CIR and / or PIR of the first slave device. For the introduction of the second rate, please refer to step 201 above, which will not be elaborated here.

[0182] In a possible implementation manner, 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. Exemplarily, the attribute value of the CIR attribute obtained by the first slave device from the first message is 4,294,967,295 bytes / s (about 34.36 Gbit / s), and the attribute value of the rate amplification factor attribute is 2. Then, the effective CIR of the first slave device is the product of the attribute value of the CIR attribute and the attribute value of the rate amplification factor attribute, that is, 8,589,934,590 bytes / s (about 68.72 Gbit / s). Thus, the master device can solve the CIR / PIR configuration problem of 50G PON and future higher-rate PONs through the newly defined rate amplification factor.

[0183] In this embodiment, the first slave device can receive a rate amplification factor from the master device. The rate amplification factor is an adjustment coefficient of the first rate (i.e., the attribute value of the CIR attribute / PIR attribute). The first slave device determines a second rate (i.e., the effective CIR / PIR of the first slave device) based on 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. That is to say, without changing the existing attributes, the value range of the CIR / PIR used by the first slave device during operation is extended. This solves the CIR / PIR configuration problem of 50G PON and future higher-rate PONs.

[0184] As Figure 4 shown, it is a schematic diagram of another embodiment of the optical network communication method provided by this application. In this embodiment, the master device reads attributes from the first slave device through get messages and get response messages. The first slave device is one of multiple slave devices connected to the master device. This embodiment takes the interaction between the master device and the first slave device as an example for illustration. Of course, the entity executing the actions of the master device in this method can also be a device, module, or chip in the master device; the entity executing the actions of the first slave device in this method can also be a device, module, or chip in the first slave device. This embodiment does not make specific limitations on this. Exemplarily, as Figure 4 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 through an optical fiber; correspondingly, the first slave device receives the second message from the master device through the optical fiber. Among them, the second message includes first indication information, and the first indication information is used to instruct the first slave device to report a rate amplification factor. The rate amplification factor is an adjustment coefficient of the first rate. Optionally, the first indication information is further used to instruct the first slave device to report the first rate, and the first rate is CIR and / or PIR. The rate amplification factor and the first rate are used to determine a second rate, and the second rate is the effective rate of the CIR and / or PIR of the first slave device. For the explanations of the first rate, the rate amplification factor, and the second rate, please refer to the relevant descriptions in step 201 above, and will not be elaborated here.

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

[0188] In a possible implementation, the first indication information is a first attribute mask, and the first attribute mask is used to indicate the attribute value of the second message requesting the first slave device to report the rate amplification factor attribute. For example, the bit corresponding to the rate amplification factor attribute in the first attribute mask being 1 indicates a request for the first slave device to report the attribute value of the rate amplification factor attribute. Optionally, if the rate amplification factor attribute is the 10th attribute of the traffic descriptor entity, that is, 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 further used to indicate the attribute value of the first slave device reporting the CIR attribute and / or the attribute value of the PIR attribute. In an example, the first attribute mask indicates the attribute value of the reported rate amplification factor attribute, the attribute value of the CIR attribute, and the attribute value of the PIR attribute. Then, the first attribute in the first attribute mask is the CIR attribute, and the bit corresponding to the CIR attribute in the first attribute mask being 1 indicates a request for the first slave device to report the attribute value of the CIR attribute; the second attribute in the first attribute mask is the PIR attribute, and the bit corresponding to the PIR attribute in the first attribute mask being 1 indicates a request for the first slave device to report the attribute value of the PIR attribute; the 9th attribute in the first attribute mask is the rate amplification factor attribute, and the bit corresponding to the rate amplification factor attribute in the first attribute mask being 1 indicates a request for the first slave device to report the attribute value of the rate amplification factor attribute. It should be understood that according to the different attributes indicated by the first attribute mask of the message, there may 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, and the master device and the first slave device can communicate through OMCI messages. Therefore, the second message can be an OMCI message. Generally, OMCI messages include messages related to the create process (such as create request messages), messages related to the set process (such as set request messages), and messages related to the get process (such as get request messages). In this embodiment, the second message is a get message (i.e., a get request message). The identification information field of the managed entity of the second message includes the identification information of the traffic descriptor managed entity, and the message content field of the second message includes the foregoing first indication information, that is, the message content field of the second message includes the foregoing first attribute mask.

[0191] Exemplarily, as Figure 5A shown, it is an example diagram of the get message (i.e., the get request message) provided by this application. Figure 5A The shown get request message compared to Figure 3AThe creation request messages shown only differ in the message type field and the message content field. For the explanations of the remaining fields, please refer to the previous text. Figure 3A For the relevant descriptions of the examples shown, they will not be elaborated here. Such as Figure 5A As shown, the message type indicated by the 3rd byte (message type, MT) field is the get request type. The 9th to 40th bytes are the message contents field. Among them, the 9th to 10th bytes are the attribute mask, which is used to indicate which attributes are requested. The mapping rule of this attribute mask is the same as that of the attribute mask in the set request message shown in the previous text Figure 3C and will not be elaborated 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. The 8th bit of the 10th byte corresponds to the rate amplification factor attribute. In one example, Figure 5A as shown, if the second message requests to report the attribute values of the CIR attribute, the PIR attribute, and the rate amplification factor attribute, then the 8th bit of the 9th byte is 1, indicating that the slave device is requested to report the attribute value of the CIR attribute, the 7th bit of the 9th byte is 1, indicating that the slave device is requested to report the attribute value of the PIR attribute, and the 8th bit of the 10th byte is 1, indicating that the slave device is requested to report the attribute value of the rate amplification factor attribute. In another example, if the second message only requests to report the attribute values of the CIR attribute and the rate amplification factor attribute, then the 8th bit of the 9th byte is 1, indicating that the slave device is requested to report the attribute value of the CIR attribute, 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 that the slave device is requested to report the attribute value of the rate amplification factor attribute. It should be understood that according to the different types of attribute values requested by the second message, there can be other examples of the attribute mask, which will not be elaborated here. In addition, the remaining bytes of the message content field are filled with zero values.

[0192] It should be noted that compared with Figure 5B the get request message for configuring CIR / PIR in the traditional technology shown, in the traditional technology, since the master device does not indicate the slave device to report the rate amplification factor attribute, therefore, 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 downstream XGEM frame. The header of the downstream XGEM frame (XGEMHeader) contains information for differentiating different OMCI XGEM Ports (hereinafter referred to as XGEM Ports for short). The XGEM Port is a logical port on the slave device and is used to carry data from the downstream PON port of the master device. The identifiers of the XGEM Ports of different slave devices are different. Therefore, different slave devices can be differentiated according to the identifier of the XGEM Port. In this embodiment, the XGEM port identifier (XGEM port ID) in the header (XGEM Header) of the downstream XGEM frame is the same as the identifier information of the first slave device (for example, 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 the third message to the master device through an optical fiber; correspondingly, the master device receives the third message from the first slave device through an optical fiber. The third message includes the rate amplification factor and the first rate of the first slave device. For the explanations of the rate amplification factor and the first rate, please refer to the relevant descriptions in step 201 above, which will not be elaborated here.

[0196] In addition, the third message is a response message to the second message. Since the second message is a get request message, the third message is a get response message, that is, the message type of the third message is get response. In addition, the identifier information field of the managed entity of the third message includes the identifier information of the traffic descriptor managed entity, and the message content field of the third message includes the first attribute mask and the attribute value of the rate amplification factor attribute. 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 further includes the attribute value of the CIR attribute and / or the attribute value of the 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 the explanation of the first attribute mask, please refer to the relevant descriptions in step 401 above, which will not be elaborated here.

[0197] Exemplarily, as Figure 5C shown, it is an example diagram of the get response message provided by this application. Figure 5C The shown get response message compared with Figure 3A the shown create request message, only the message type field and the message content field are different. For the explanations of the remaining fields, please refer to the relevant descriptions in the example shown in Figure 3A above, which will not be elaborated here. As Figure 5CAs shown, the message type indicated by the third byte, i.e., the message type (MT) field, is the getresponse type. Bytes 9 to 40 are the message contents field. Among them, the ninth byte is used to indicate the processing result of the get operation. The first four bits of the ninth byte are fixed as "0000", that is, bits 8 to 5 are fixed as "0000"; the last four bits of the ninth byte are used to indicate the reason for the processing result. Figure 5C The "0000" of bits 4 to 1 shown indicates that the command processing is successful, that is, the attribute values that need to be reported as indicated by the attribute mask (for example, the first attribute mask) in the request message (for example, the second message) are successfully obtained. Bytes 10 to 11 are the attribute mask, which is used to indicate which attributes are provided. The mapping rule of this attribute mask is the same as that of the attribute mask in the setup request message shown above, which will not be elaborated here. It should be noted that when the attributes requested by the get request message are the same as the attributes reported by the get response message, the attribute mask in the second message is the same as the attribute mask in the third message. This embodiment takes the second message and the third message both carrying the first attribute mask as an example for introduction. Specifically, the eighth bit of the tenth byte corresponds to the CIR attribute, the seventh bit of the tenth byte corresponds to the PIR attribute, and so on. The eighth bit of the eleventh byte corresponds to the rate amplification factor attribute. In one example, as Figure 3C shown, if the third message carries the attribute values of the CIR attribute, the PIR attribute, and the rate amplification factor attribute, then the eighth bit of the tenth byte is 1, indicating that the message contents field carries the attribute value of the CIR attribute, the seventh bit of the tenth byte is 1, indicating that the message contents field carries the attribute value of the PIR attribute, and the eighth bit of the eleventh byte is 1, indicating that the message contents field carries the attribute value of the rate amplification factor attribute. In another example, if the third message carries the attribute values of the CIR attribute and the rate amplification factor attribute, then the eighth bit of the ninth byte is 1, indicating that the message contents field carries the attribute value of the CIR attribute, the seventh bit of the ninth byte is 0, indicating that the message contents field does not carry the attribute value of the PIR attribute, and the eighth bit of the tenth byte is 1, indicating that the message contents field carries the attribute value of the rate amplification factor attribute. It should be understood that according to the different types of attribute values 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 to 38 carry an optional attribute mask, and bytes 39 to 40 carry an attribute execution mask. In addition, the remaining bytes of the message contents field are used to carry the attribute values of the attributes indicated by the attribute mask. Figure 5C In addition, bytes 37 to 38 carry an optional attribute mask, and bytes 39 to 40 carry an attribute execution mask. In addition, the remaining bytes of the message contents 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 for obtaining the response message is different from the message content field for creating the request message. The first byte of the message content field for creating the request message starts with the attribute value of the first set-by-create attribute, and in sequence and according to the size of this attribute, space is allocated in the create message for each set-by-create attribute. However, the message content field for obtaining the response message only carries the attribute values of the attributes indicated by the attribute mask, and does not necessarily carry the attribute values of all set-by-create attributes. Optionally, the attribute value of the rate amplification factor attribute can be carried in the m-(m + 2)th bytes 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 obtained response message carries the attribute values of all attributes of the traffic descriptor ME, then referring to the aforementioned Table 2, the 12th-15th bytes are the attribute values of the 4-byte CIR attribute, the 16th-19th bytes are the attribute values of the 4-byte PIR attribute, and so on. The 32nd-33rd bytes are the attribute values of the 2-byte rate amplification factor attribute, and the remaining bytes in the message content field (i.e., the 34th-36th bytes) are filled with zero values. In another example, if the obtained response message provides the CIR attribute, PIR attribute, and rate amplification factor attribute to the master device, then referring to the aforementioned Table 2, the 12th-15th bytes are the attribute values of the 4-byte CIR attribute, the 16th-19th bytes are the attribute values of the 4-byte PIR attribute, the 20th-21st bytes are the attribute values of the 2-byte rate amplification factor attribute, and the remaining bytes in the message content field (i.e., the 22nd-36th bytes) are filled with zero values. In another example, if the obtained response message provides the CIR attribute (or PIR attribute) and rate amplification factor attribute to the master device, then referring to the aforementioned Table 2, the 12th-15th bytes are the attribute values of the 4-byte CIR attribute (or PIR attribute), the 16th-17th bytes are the attribute values of the 2-byte rate amplification factor attribute, and the remaining bytes in the message content field (i.e., the 18th-36th bytes) are filled with zero values. In another example, if the obtained response message only provides the rate amplification factor attribute to the master device, then the 12th-13th bytes are the attribute values of the 2-byte rate amplification factor attribute, and the remaining bytes in the message content field (i.e., the 14th-36th bytes) are filled with zero values. In practical applications, there can be other examples, which are not listed one by one here.

[0200] It should be noted that compared with Figure 5D the obtained response message for configuring CIR / PIR in the traditional technology shown, in the traditional technology, since the attribute value of the rate amplification factor attribute is not carried, 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 attribute.

[0201] It should be understood that in this embodimentFigure 5A , Figure 5B , Figure 5C and Figure 5D are all introduced by taking the Baseline OMCI message format as an example. In actual applications, the various types of messages described above Figure 5A , Figure 5B , Figure 5C and Figure 5D can also adopt the Extended OMCI message format with variable lengths, which will not be elaborated here.

[0202] Optionally, the third message is encapsulated in the payload field of the upstream XGEM frame. The XGEM port ID in the XGEM header of the upstream 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 can receive the first indication information from the master device to instruct the first slave device to report the rate amplification factor and the first rate. The rate amplification factor is an adjustment coefficient of the first rate (i.e., the attribute value of the CIR attribute / PIR attribute). After receiving the first indication information, the first slave device reports the rate amplification factor and the first rate of the first slave device, thereby providing the effective CIR / PIR of the first slave device to the master device. That is to say, on the basis of not changing the existing attributes, the value range of the CIR / PIR used by the first slave device during operation is extended, and the problem of CIR / PIR reporting for 50G PON and future higher-rate PONs is solved.

[0204] Next, in combination with Figure 6 and Figure 7 , the main process of the second solution of the optical network communication method provided by this application will be introduced:

[0205] As Figure 6 shown, it is a schematic diagram of another embodiment of the optical network communication method provided by this application. In this embodiment, the master device configures attributes for the first slave device through a create message or a set message. The first slave device is one of the multiple slave devices connected to the master device. This embodiment is described by taking the interaction between the master device and the first slave device as an example. Of course, the entity performing the actions of the master device in this method can also be a device, module, or chip in the master device; the entity performing the actions of the first slave device in this method can also be a device, module, or chip in the first slave device, and this embodiment does not make specific limitations in this regard. Exemplarily, as Figure 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 the fourth message to the first slave device through an optical fiber; correspondingly, the first slave device receives the fourth message from the master device through the optical fiber.

[0208] Among them, the fourth message includes a third rate, and the third rate is the CIR and / or PIR. Since the master device manages and maintains the CIR and PIR of the slave device through the CIR attribute and PIR attribute of the traffic descriptor ME, therefore, the fourth message includes the third rate, which can be understood as that the fourth message carries the attribute value of the CIR attribute and / or the attribute value of the PIR attribute.

[0209] In addition, the unit of the third rate is related to the line rate and the preset threshold of the first slave device. Among them, 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 an integer greater than 0. Among them, the line rate of the first slave device can be the line rate used when the first slave device is working. It should be noted that before the first slave device receives the fourth message, the first slave device registers and goes online with the master device, and the master device and the first slave device establish an OMCI management channel. During this process, the master device can learn the line rate used when the first slave device is working.

[0210] That is to say, compared with the CIR attribute and PIR attribute in the traditional technology, the CIR attribute and PIR attribute provided in this embodiment have different definitions. In the traditional technology, the unit of the attribute value of the CIR attribute is bytes per second, and the unit of the attribute value of the PIR attribute is bytes per second. In this application, the units of the CIR attribute and the PIR attribute are related to the line rate and the preset threshold of the slave device to be configured by the master device, and are not necessarily bytes per second. For example, for the CIR attribute, when the line rate of the slave device to be configured by the master device is less than or equal to the preset threshold, the unit of the attribute value of the CIR attribute is bytes per second; when the line rate of the slave device to be configured by the master device is greater than the preset threshold, the unit of the attribute value of the CIR attribute is N bytes per second, where N is an integer greater than 0. Another example is that for the PIR attribute, when the line rate of the slave device to be configured by the master device is less than or equal to the preset threshold, the unit of the attribute value of the PIR attribute is bytes per second; when the line rate of the slave device to be configured by the master device is greater than the preset threshold, the unit of the attribute value of the PIR attribute is N bytes per second, where N is an integer greater than 0.

[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, which is not limited in this application.

[0212] Optionally, the preset threshold is 9.95328 Gbit / s. In some scenarios, the preset threshold can also be abbreviated as 10 Gbit / s. Optionally, the preset threshold is less than 4,294,967,295 bytes / s (about 34.36 Gbit / s). Since the byte size of the attribute value carrying the CIR attribute and the byte size of the attribute value carrying the PIR attribute are not modified in this embodiment, the maximum value of the attribute value of the CIR attribute remains 4,294,967,295 bytes / s (about 34.36 Gbit / s), and the maximum value of the attribute value of the PIR attribute remains 4,294,967,295 bytes / s (about 34.36 Gbit / s). Therefore, the value of the preset threshold is less than 4,294,967,295 bytes / s (about 34.36 Gbit / s).

[0213] In addition, the fourth message in this embodiment can be a create request message or a set request message.

[0214] In a possible implementation manner, the fourth message is a create request message, that is, the message type of the fourth message is a create request, that is, the message sent by the master device to the first slave device when first creating an instance of the traffic descriptor ME of the first slave device. In this case, the identification information field of the managed entity of the fourth message includes the identification information of the traffic descriptor managed entity, 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. The message format of the fourth message is the same as the message format of the create message for configuring CIR / PIR in the prior art. For specific examples, please refer to the examples shown above and will not be elaborated here. Figure 3B shown example, which will not be elaborated here.

[0215] In another possible implementation manner, the fourth message is a set request message, that is, the message type of the fourth message is a set request. For example, that is, the message sent by the master device to the first slave device when it is necessary to reconfigure the instance of the traffic descriptor ME of the first slave device. In this case, the identification information field of the managed entity 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 value of the CIR attribute and / or the attribute value of the PIR attribute, but also a second attribute mask. Among them, the second attribute mask is used to indicate that the message content field carries the attribute value of the CIR attribute and the attribute value of the PIR attribute. The 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; the 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 downstream XGEM frame. The header (XGEMHeader) of the downstream XGEM frame contains information for differentiating different XGEM Ports. The XGEM Port is a logical port on the slave device and is used to carry data from the downstream PON port of the master device. The identifiers of the XGEM Ports of different slave devices are different. Therefore, different slave devices can be differentiated based on the identifier of the XGEM Port. In this embodiment, the XGEM port identifier (XGEM port ID) in the header (XGEM Header) of the downstream XGEM frame is the same as the identification information of the first slave device (for example, 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] It can also be understood that the first slave device determines the valid CIR and / or PIR of the first slave device based on the line rate of the first slave device and a preset threshold. For the explanation of the preset threshold, please refer to Step 601 above and will not be elaborated 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 when the first slave device is working; 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 working.

[0219] In a possible implementation, if the line rate of the first slave device is less than or equal to the preset threshold, the first slave device determines that the value of the third rate (i.e., the attribute value of the CIR attribute and / or the attribute value of the PIR attribute) is the valid CIR / PIR of the first slave device, and the unit is bytes per second. Exemplarily, 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 unit of the attribute value of the CIR attribute is bytes per second, and the valid 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 unit of the attribute value of the PIR attribute is bytes per second, and the valid PIR of the first slave device is B bytes per second. Wherein, both A and B are integers greater than 0.

[0220] In another possible implementation, 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, with the unit of bytes per second. Exemplarily, 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 unit of the attribute value of the CIR attribute is 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 unit of the attribute value of the PIR attribute is 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. Wherein, 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 the preset threshold. The first slave device can determine the unit of the third rate based on the line rate of the first slave device and the preset threshold, that is, determine the effective CIR / PIR of the first slave device. Therefore, even when the value of the third rate is limited, the first slave device can determine the unit of the third rate based on the line rate of the first slave device and the preset threshold, and then determine the effective CIR / PIR of the first slave device. This solves the problem of CIR / PIR configuration for 50G PON and future higher-rate PONs.

[0222] As Figure 7 shown, it is a schematic diagram of another embodiment of the optical network communication method provided by this application. In this embodiment, the master device reads attributes from the first slave device through get messages and get response messages. The first slave device is one of multiple slave devices connected to the master device. This embodiment is described by taking the interaction between the master device and the first slave device as an example. Of course, the entity that executes the actions of the master device in this method can also be a device, module, or chip in the master device; the entity that executes the actions of the first slave device in this method can also be a device, module, or chip in the first slave device. This embodiment does not make specific limitations in this regard. Exemplarily, as Figure 7 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 an optical fiber; correspondingly, the first slave device receives the fifth message from the master device via the optical fiber. The fifth message includes second indication information for instructing the first slave device to report a third rate, where the third rate is the CIR and / or PIR, and the unit of the third rate is related to the line rate and the preset threshold of the first slave device. For the explanation of the third rate, please refer to the relevant description in step 601 above, which will not be elaborated here.

[0225] In a possible implementation, the second indication information is a second attribute mask, which is used to indicate that the fifth message requests the first slave device to report the attribute value of the CIR attribute and / or the attribute value of the PIR attribute. Optionally, the second attribute mask is a 2-byte bit map, and the second attribute mask corresponds to the order of the attributes after the ME ID in the attributes of the traffic descriptor ME from the high-order bit to the low-order bit (i.e., from the 8th bit to the 1st bit) (i.e., the order of the attributes after the ME ID shown in Table 2). For example, 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, indicating that the first slave device is requested to report the attribute value of the CIR attribute; 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, indicating that the first slave device is requested to report the attribute value of the PIR attribute.

[0226] In addition, the fifth message in this embodiment may be a get request message, that is, the message type of the fifth message is a get request. In this case, the fifth message further includes the identification information of the traffic descriptor managed entity, and the message content field of the fifth message includes the foregoing second indication information (for example, the foregoing second attribute mask). The message format of the fifth message is the same as the message format of the get request message for configuring CIR / PIR in the prior art. For specific examples, please refer to the Figure 5B examples shown above, which will not be elaborated here.

[0227] Optionally, the fifth message is encapsulated in the payload field of the downstream XGEM frame. The frame header (XGEMHeader) of the downstream XGEM frame contains information for distinguishing different XGEM Ports. The XGEM Port is a logical port on the slave device and is used to carry the data of the downstream PON port from the master device. The identifiers of the XGEM Ports of different slave devices are different. Therefore, different slave devices can be distinguished according to the identifier of the XGEM Port. In this embodiment, the XGEM port identifier (XGEM port ID) in the frame header (XGEM Header) of the downstream XGEM frame is the same as the identification information of the first slave device (for example, ONU ID), that is, XGEM portID is the same as 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 the sixth message to the master device through an optical fiber; correspondingly, the master device receives the sixth message from the first slave device through the 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 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 an integer greater than 0. For the explanation of the third rate, please refer to the relevant description in step 601 above, which will not be elaborated here.

[0230] In addition, the sixth message is a response message to the fifth message. Since the fifth message is a retrieval request message, the sixth message is a retrieval response message, that is, the message type of the sixth message is retrieval response. In addition, the identification information field of the managed entity of the sixth message includes the identification information of the traffic descriptor managed entity, and the message content field of the sixth message includes the second indication information (for example, 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 retrieval response message for configuring CIR / PIR in the prior art. For the specific example, please refer to the example shown above, which will not be elaborated here. Figure 5D Shown in the example, it will not be elaborated here.

[0231] It should be understood that before the first slave device receives 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. In this process, the first slave device can determine the line rate used during operation, and the master device can also learn 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 effective CIR and / or PIR of the first slave device based on the attribute value of the CIR attribute and / or the attribute value of the PIR attribute carried in the sixth message, the line rate of the first slave device, and the preset threshold.

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

[0233] In this embodiment, the first slave device can receive the second indication information from the master device to instruct the first slave device to report the third rate (i.e., the attribute value of the CIR attribute / PIR attribute). Since the unit of the third rate is related to the line rate and the preset threshold of the first slave device, after receiving the second indication information, the first slave device reports the attribute value of the CIR attribute / PIR attribute, and the master device itself determines the effective CIR / PIR of the first slave device, thereby indirectly providing the effective CIR / PIR of the first slave device to the master device. That is to say, on the basis of not changing the existing attributes, the value range of the CIR / PIR used by the first slave device during operation is extended, and the problem of CIR / PIR reporting for 50G PON and future higher-rate PONs is solved.

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

[0235] As Figure 8As shown, the communication device 80 may include a processor 801 and a transceiver 802, and the processor 801 is coupled to the transceiver 802. Among them, the aforementioned 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 aforementioned 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, and specific details are not limited herein.

[0236] Among them, the aforementioned transceiver 802 may also be referred to as a transceiver unit, a transceiver, a transceiver device, etc. Optionally, the devices used to implement the receiving function in the transceiver unit may be regarded as the receiving unit, and the devices used to implement the sending function in the transceiver unit may be regarded as the sending unit, that is, the transceiver unit includes a receiving unit and a sending unit. The receiving unit may also be referred to as a receiver, an input port, a receiving circuit, etc., and the sending unit may be referred to as a transmitter, a transmitter, or a transmitting circuit, etc. Optionally, when the communication device 80 is used to implement Figure 2 , Figure 4 , Figure 6 or Figure 7 the function of the master device in the method shown, the transceiver 802 may be used for receiving an upstream burst optical signal. Optionally, the transceiver 802 supports receiving burst optical signals at one or more upstream 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 mainly used to store software programs and data. The memory 803 can exist independently and be 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 the program code for implementing the technical solution of the embodiment of the present application and be controlled by the processor 801 for execution. The various computer program codes to be executed can also be regarded as the driver programs of 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 a combination of the above types of memory. The memory 803 can refer to a single memory or can include multiple memories. Exemplarily, the memory 803 is used to store various data.

[0238] In one implementation, the communication device 80 is used to implement Figure 2 the functions of the master device in the corresponding method embodiment. Specifically, the processor 801 is used to generate a first message, the first message includes a rate amplification factor, the rate amplification factor is an adjustment coefficient of a first rate, the first rate is a guaranteed information rate CIR and / or a peak information rate PIR, and the rate amplification factor and the first rate are used to determine a second rate of a first slave device, and the second rate is an 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 further includes the first rate.

[0239] In another implementation, the communication device 80 is used to implement Figure 2 the functions of the first slave device in the corresponding method embodiment. Specifically, the transceiver 802 is used to receive a first message from the master device, the first message includes a rate amplification factor, the rate amplification factor is an adjustment coefficient of a first rate, the first rate is a guaranteed information rate CIR and / or a peak information rate PIR. The processor 801 is used to determine a second rate of the first slave device based on the rate amplification factor and the first rate, and the second rate is an effective CIR and / or PIR of the first slave device. Optionally, the first message further includes the first rate.

[0240] In another implementation, the communication device 80 is used to implement Figure 4 the functions of the master device in the corresponding method embodiment. Specifically, the processor 801 is used to generate a second message, the second message includes first indication information, the first indication information is used to instruct the first slave device to report a rate amplification factor, the rate amplification factor is an adjustment coefficient of a first rate, and the first rate is a guaranteed information rate CIR and / or a peak information rate PIR. The transceiver 802 is used to send the second message to the first slave device. In addition, the transceiver 802 is further used to receive a third message from the first slave device, and the third message includes the rate amplification factor of the first slave device. Optionally, the first indication information is further used to instruct the first slave device to report the first rate. At this time, the third message further includes the first rate.

[0241] In another implementation, the communication device 80 is used to implement Figure 4 the functions of the first slave device in the corresponding method embodiment. Specifically, the transceiver 802 is used to receive a second message from the master device, the second message includes first indication information, the first indication information is used to instruct the first slave device to report a rate amplification factor, the rate amplification factor is an adjustment coefficient of a first rate, and the first rate is a guaranteed information rate CIR and / or a peak information rate PIR. The processor 801 is used to generate a third message, and the third message includes the rate amplification factor of the first slave device. In addition, the transceiver 802 is further used to send the third message to the master device. Optionally, the first indication information is further used to instruct the first slave device to report the first rate. At this time, the third message further includes the first rate.

[0242] In another implementation, the communication device 80 is used to implement Figure 6 the functions of the master device in the corresponding method embodiment. Specifically, the processor 801 is used to generate a fourth message, the fourth message includes a third rate, the third rate is a guaranteed information rate CIR and / or a peak information rate PIR, and the unit of the third rate is related to the line rate of the first slave device and a preset threshold, and the line rate of the first slave device and the preset threshold 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 functions of the first slave device in the corresponding method embodiment. Specifically, the transceiver 802 is used to receive a fourth message from the master device, the fourth message includes a third rate, the third rate is a guaranteed information rate CIR and / or a peak information rate PIR, and the unit of the third rate is related to the line rate of the first slave device and a preset threshold. The 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 implementFigure 7 Corresponding to the functions of the master device in the method embodiments. Specifically, the processor 801 is configured to generate a fifth message, where the fifth message includes second indication information for indicating that the first slave device reports a third rate, and the third rate is the committed 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 configured to send the fifth message to the first slave device. In addition, the transceiver 802 is further configured to receive a sixth message from the first slave device, where the sixth message includes the third rate of the first slave device.

[0245] In another implementation, the communication device 80 is used to implement Figure 7 Corresponding to the functions of the first slave device in the method embodiments. Specifically, the transceiver 802 is configured to receive a fifth message from the master device, where the fifth message includes second indication information for indicating that the first slave device reports a third rate, and the third rate is the committed 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 processor 801 is configured to generate a sixth message, where the sixth message includes the third rate of the first slave device. The transceiver 802 is further configured to send the sixth message to the master device.

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

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

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

[0249] In a possible design, as Figure 9One or more of the modules in [the device] may be implemented by one or more processors, or by one or more processors and a memory; or by one or more processors and a transceiver; or by one or more processors, a memory, and a transceiver. The embodiments of the present application do not limit this. The processor, the memory, and the transceiver may be provided separately or integrated into one body.

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

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

[0252] In addition, the present application provides a computer program product, which includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are fully or partially generated. For example, it implements the methods related to the slave device (e.g., the first slave device) as described in the foregoing Figure 2 , Figure 4 , Figure 6 or Figure 7 . Also, for example, it implements the methods related to the master device as described in the foregoing Figure 2 , Figure 4 , Figure 6 or Figure 7Methods related to the master device in it. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. 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 a website, computer, server, or data center to another website, computer, server, or data center in a wired manner (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or a wireless manner (such as infrared, wireless, microwave, etc.). 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 includes one or more integrated available media. The available medium can be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a digital versatile disc (DVD)), or a semiconductor medium (such as a solid-state disk (SSD)), etc.

[0253] In addition, the present application also provides a computer-readable storage medium storing a computer program, which is executed by a processor to implement the method related to the slave device (such as the first slave device) as described above Figure 2 , Figure 4 , Figure 6 or Figure 7 in it.

[0254] In addition, the present application also provides a computer-readable storage medium storing a computer program, which is executed by a processor to implement the method related to the master device as described above Figure 2 , Figure 4 , Figure 6 or Figure 7 in it.

[0255] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the above-described systems, devices, and units can refer 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 the present application and are not intended to limit them. Although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments or perform equivalent replacements for some of the technical features. And these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A optical network communication method, applied to an optical fiber network, the optical fiber network including a master device and a slave device, characterized in that, The method includes: The slave device receives a first message from the master device, the first message includes a rate amplification factor, the rate amplification factor is an adjustment coefficient of a first rate, and the first rate is a first guaranteed information rate CIR and / or a first peak information rate PIR; The slave device determines an effective CIR and / or an effective PIR based on the rate amplification factor and the first rate.

2. The method according to claim 1, characterized in that, The default value of the rate amplification factor is 1.

3. The method according to claim 1, wherein The value of the rate amplification factor is an integer greater than 0.

4. The method according to claim 1, wherein 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.

5. The method according to claim 1, wherein The first message further includes identification information of a traffic descriptor managed entity.

6. The method according to claim 1, characterized in that, The first message further includes the first rate.

7. The method according to any one of claims 1 to 6, characterized in that The message type of the first message is a set request or a create request.

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

9. The method according to any one of claims 1 to 6, characterized in that The first message is encapsulated in the payload field of a downstream 10G-bit symmetric passive optical network encapsulation mode XGEM frame.

10. The method according to any one of claims 1 to 6, characterized in that, The XGEM port identifier in the frame header of the XGEM frame encapsulating the first message is the same as the identification information of the slave device.

11. The method according to any one of claims 1 to 6, characterized in that, The master device is an optical line terminal OLT, and the slave device is an optical network unit ONU.

12. A optical network communication method, applied to an optical fiber network, the optical fiber network including a master device and a slave device, characterized in that, The method includes: The master device sends a first message to the slave device, the first message includes a rate amplification factor, the rate amplification factor is an adjustment coefficient of a first rate, the first rate is a first guaranteed information rate CIR and / or a first peak information rate PIR, and the rate amplification factor and the first rate are used to determine an effective CIR and / or an effective PIR.

13. The method according to claim 12, wherein The default value of the rate amplification factor is 1.

14. The method according to claim 12, wherein The value of the rate amplification factor is an integer greater than 0.

15. The method according to claim 12, wherein 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.

16. The method according to claim 12, wherein The first message further includes identification information of a traffic descriptor managed entity.

17. The method according to claim 12, wherein The first message further includes the first rate.

18. The method according to any one of claims 12 to 17, characterized in that, The message type of the first message is a set request or a create request.

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

20. The method according to any one of claims 12 to 17, characterized in that The master device is an optical line terminal OLT, and the slave device is an optical network unit ONU.

21. A optical network communication method, applied to an optical fiber network, the optical fiber network including a master device and a slave device, characterized in that, Includes: The slave device receives a second message from the master device, the second message includes first indication information for instructing the slave device to report the rate amplification factor, the rate amplification factor is an adjustment coefficient of a first rate, and the first rate is a first guaranteed information rate CIR and / or a first peak information rate PIR; The slave device sends a third message to the master device, and the third message includes the rate amplification factor of the slave device.

22. The method according to claim 21, wherein The default value of the rate amplification factor is 1.

23. The method according to claim 21, wherein The value of the rate amplification factor is an integer greater than 0.

24. The method according to claim 21, wherein The rate amplification factor and the first rate are used to determine an effective CIR and / or an effective PIR.

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

26. The method according to any one of claims 21 to 25, characterized in that 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.

27. The method according to any one of claims 21 to 25, characterized in that, The first indication information includes a first attribute mask, and the bit corresponding to the rate amplification factor attribute in the first attribute mask is 1.

28. The method according to any one of claims 21 to 25, 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.

29. The method according to any one of claims 21 to 25, characterized in that, The first indication information is further used to instruct the slave device to report the first rate, and the third message further includes the first rate.

30. A optical network communication method is applied to an optical fiber network, and the optical fiber network includes a master device and a slave device, characterized in that, including: The master device sends a second message to the slave device, and the second message includes first indication information, which is used to instruct the slave device to report a rate amplification factor, where the rate amplification factor is an adjustment coefficient of the first rate, and the first rate is a first guaranteed information rate CIR and / or a first peak information rate PIR; The master device receives a third message from the slave device, and the third message includes the rate amplification factor of the slave device.

31. The method according to claim 30, characterized in that, The default value of the rate amplification factor is 1.

32. The method according to claim 30, wherein, The value of the rate amplification factor is an integer greater than 0.

33. The method according to claim 30, wherein The rate amplification factor and the first rate are used to determine the effective CIR and / or the effective PIR.

34. The method according to claim 33, wherein 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.

35. The method according to any one of claims 30 to 34, characterized in that, 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.

36. The method according to any one of claims 30 to 34, characterized in that, The first indication information includes a first attribute mask, and the bit corresponding to the rate amplification factor attribute in the first attribute mask is 1.

37. The method according to any one of claims 30 to 34, 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.

38. The method according to any one of claims 30 to 34, characterized in that, The first indication information is further used to instruct the slave device to report the first rate, and the third message further includes the first rate.

39. A communication device, characterized in that, The communication device is used to implement the method according to any one of claims 1 to 11; or, to implement the method according to any one of claims 21 to 29.

40. A communication device, characterized in that, The communication device is used to implement the method according to any one of claims 12 to 20; or, to implement the method according to any one of claims 30 to 38.

41. A communication system, characterized in that, including: The communication device according to claim 39, and the communication device according to claim 40.

42. A computer-readable storage medium, characterized in that, A computer program is stored, and the computer program can be executed by a processor to cause the computer to execute the method according to any one of claims 1 to 38.

43. A computer program product, characterized in that, including computer program instructions, when the computer program instructions run on a computer, causing the computer to execute the method according to any one of claims 1 to 38.

Images