Optical network communication method, and communication apparatus

Abstract

Provided in the present application are an optical network communication method, and a communication apparatus. In the method, a first slave device can receive a rate scale factor from a master device, the rate scale factor being an adjustment coefficient for a first rate (i.e., the attribute value of a CIR attribute / PIR attribute), and the first slave device determines a second rate (i.e., a valid CIR / PIR of the first slave device) by means of the rate scale factor and the first rate. Thus, even if the value range of a first rate is limited, a valid CIR / PIR of a first slave device can still be adjusted by means of a rate scale factor. That is, on the basis of not changing an existing attribute, the value range of the CIR / PIR used by the first slave device during operation is expanded, thereby solving the problem of CIR / PIR configuration in 50G PONs and future higher-rate PONs.

Description

Method and apparatus for optical network communication

[0001] The present application claims priority from the Chinese patent application No. 202410638484.6 filed on May 21, 2024, and entitled "Method and apparatus for optical network communication", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] Embodiments of the present application relate to the field of optical communication, and in particular to a method and apparatus for optical network communication. BACKGROUND

[0003] In recent years, broadband access technology has developed rapidly, and passive optical network (PON) has completed large-scale popularization and rapid expansion. With the continuous and rapid increase of user data demand, 10-Gigabit-capable Passive Optical Networks (X G-PON) has entered the stage of large-scale deployment, and the standards of the next-generation PON system (e.g., 50-Gigabit-capable Passive Optical Networks (50GPON)) are also being gradually developed and improved.

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

[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 for the management of the CIR attribute and the PIR attribute of the ONU. The OLT configures the CIR attribute or the PIR attribute by sending the OMCI message related to the traffic descriptor managed entity to the ONU, or obtains the value of the CIR attribute or the PIR attribute. Since the length of the CIR attribute field and the PIR attribute field defined in the current standard is 4 bytes, and the unit of the CIR attribute and the PIR attribute is byte per second, the maximum value of the CIR attribute and the PIR attribute is 4,294,967,295, that is, the maximum CIR or PIR that can be configured by the two attributes is 4,294,967,295 bytes / s, which is approximately equal to 34G bit / s. It can be seen that the field length of the CIR attribute and the PIR attribute in the current traffic descriptor managed entity is insufficient to support the configuration of 50G PON and future higher rate PONs. SUMMARY

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

[0007] In a first aspect, the present application provides an optical network communication method applied to an optical fiber network, the optical fiber network including a master device and at least one slave device, the at least one slave device including a first slave device. The optical network communication method provided by the present application can be executed by the first slave device in the optical fiber network, or can be executed by part of the 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 first message from the master device, the first message including a rate amplification factor, the rate amplification factor being an adjustment coefficient of a first rate, the first rate being a committed information rate (CIR) and / or a 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, the second rate being an effective CIR and / or PIR of the first slave device.

[0008] In the aspect, the first slave device can receive a rate amplification factor from the master device, the rate amplification factor being a scaling factor of the first rate (i.e. the attribute value of the CIR attribute / PIR attribute), and the first slave device determines the second rate (i.e. the effective CIR / PIR of the first slave device) by the rate amplification factor and the first rate. Therefore, even if the first rate has a limited value, the effective CIR / PIR of the first slave device can be adjusted by the rate amplification factor. That is, without changing the existing attributes, the value of the CIR / PIR used by the first slave device in operation is extended. The CIR / PIR configuration problem of 50G PON and future higher rate PONs is solved.

[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, i.e. 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, i.e. the first slave device operates according to a times the CIR value indicated by the first message and / or a times the PIR value. As can be seen, in the case where 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 not be limited to the maximum rate indicated by 4 bytes. Therefore, the CIR / PIR configuration problem of 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 comprises 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, the rate amplification factor can be a newly defined attribute of the traffic descriptor managed entity, which facilitates the master device to configure the rate amplification factor through the same message when configuring the CIR / PIR for the slave device, and improves the efficiency of the master device in configuring the effective CIR / PIR for the slave device.

[0013] In a possible implementation, the first message further comprises 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.

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

[0015] Optionally, in the case where the message type of the first message is a set request, the message content field of the first message further comprises a first attribute mask, and a bit corresponding to the rate amplification factor attribute in the first attribute mask is 1. In addition, a bit corresponding to the CIR attribute in the first attribute mask is 1, and / or a 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 set request, and the first message can 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 comprises 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 improving the flexibility of configuring the rate amplification factor.

[0017] In this case, the identification information field of the first message comprises the identification information of the traffic descriptor managed entity. The message content field of the first message comprises the first attribute mask and the attribute value of the rate amplification factor attribute, and a 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, i.e., 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 downlink XGEM frame, and the XGEM port identification in the frame header of the downlink 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 applied to an optical fiber network, the optical fiber network comprising a master device and at least one slave device, the at least one slave device comprising a first slave device. The optical network communication method provided by the present application can be executed by the master device in the optical fiber network, or by a part of functional modules or chips 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 comprising a rate amplification factor, the rate amplification factor being an adjustment coefficient of a first rate, the first rate being a CIR (Committed Information Rate) and / or a PIR (Peak Information Rate), the rate amplification factor and the first rate being used to determine a second rate of the first slave device, the second rate being an effective CIR and / or PIR of the first slave device.

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

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

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

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

[0026] In a possible implementation, the first message further comprises 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 conducive to improving the configuration efficiency.

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

[0028] Optionally, in the case where the message type of the first message is a set request, the message content field of the first message further comprises a first attribute mask, a bit corresponding to the rate amplification factor attribute in the first attribute mask being 1. In addition, a bit corresponding to the CIR attribute in the first attribute mask is 1, and / or a 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 set request, and the first message can not carry the first rate. Optionally, the first rate is a default value, or the first slave device obtains the first rate through another message. 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, the flexibility of configuring the rate amplification factor is improved.

[0030] In this case, the identification information field of the first message includes the identification information of the traffic descriptor managed entity. The message content field of the first message includes the 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 tenth attribute of the traffic descriptor managed entity, that is, the rate amplification factor attribute is the ninth attribute after the managed entity identification information attribute of the traffic descriptor managed entity. The rate amplification factor attribute corresponds to the ninth bit in the first attribute mask.

[0032] In a possible implementation, the first message is encapsulated in the payload field of a downlink XGEM frame, and the XGEM port identification in the frame header of the downlink 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 the present application also has a plurality of other specific implementations, and specific implementations and advantages thereof can be referred to the specific implementations of the first aspect, which will not be described 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 including a master device and at least one slave device, the at least one slave device including a first slave device. The optical network communication method provided by the present application can be executed by the first slave device in the optical fiber network, or can be executed by part of the 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 second message from the master device, the second message including first indication information, the first indication information being used to indicate that the first slave device reports a rate amplification factor, the rate amplification factor being an adjustment coefficient of a first rate, and the first rate being a guaranteed information rate (CIR) and / or a peak information rate (PIR); then, the first slave device sends a third message to the master device, the third message including the rate amplification factor of the first slave device.

[0036] In the 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 factor of the first rate (i.e., an 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 determine the effective CIR / PIR of the first slave device in combination with the rate amplification factor and the first rate, so as to realize providing the master device with the effective CIR / PIR of the first slave device. That is, without changing the existing attribute, the value range of the CIR / PIR used by the first slave device in operation is expanded, and the CIR / PIR reporting problem of the 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 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, in a case where 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, and a bit corresponding to the rate amplification factor attribute in the first attribute mask is 1, to indicate that the attribute value of the rate amplification factor attribute is requested to be reported by the first slave device. Optionally, the bit corresponding to the rate amplification factor attribute in the first attribute mask is the 9th bit.

[0043] In the embodiment, the first attribute mask is only used to indicate the attribute value of the rate amplification factor attribute, and does not necessarily report 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 in reporting the attribute value.

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

[0045] In this embodiment, the attribute value of the rate amplification factor reported by the first slave device is indicated by the first attribute mask, and the attribute value of the CIR attribute and / or the attribute value of the PIR attribute, so that the first slave device can feed back the rate amplification factor (that is, the attribute value of the rate amplification factor) and the first rate (that is, 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 in acquiring 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 request for acquisition, the identification information field of the managed entity of the second message includes 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 response for acquisition, the identification information field of the managed entity of the third message includes 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 a downlink XGEM frame, and the XGEM port identification in the frame header of the downlink XGEM frame is the same as the identification information of the first slave device; and the third message is encapsulated in the payload field of an uplink XGEM frame, and the XGEM port identification 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 the present aspect has a plurality of other specific implementations, and specific implementations and advantages thereof can be referred to the specific implementations and advantages of the first aspect, which will not be described herein.

[0051] In a fourth aspect, the present application provides an optical network communication method applied to an optical fiber network, the optical fiber network comprising a master device and at least one slave device, the at least one slave device comprising a first slave device. The optical network communication method can be executed by the master device in the optical fiber network, or by a part of functional modules or chips in the master device. Taking the master device as an example, the master device sends a second message to the first slave device, the second message comprising first indication information, the first indication information being used to instruct the first slave device to report a first rate and a rate amplification factor, the rate amplification factor being an adjustment factor of the first rate, the first rate being a CIR (Committed Information Rate) and / or a PIR (Peak Information Rate); then, the master device receives a third message from the first slave device, the third message comprising the rate amplification factor and the first rate of the first slave device.

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

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

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

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

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

[0057] In a possible implementation, in the case that 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, a bit corresponding to a rate amplification factor attribute in the first attribute mask being 1, indicating that the first slave device is requested to report the attribute value of the rate amplification factor attribute. Optionally, the bit corresponding to the rate amplification factor attribute in the first attribute mask is the 9th bit.

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

[0059] In a possible implementation, the message type of the second message is an acquisition 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 an acquisition 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 downlink XGEM frame, and the XGEM port identification in the frame header of the downlink XGEM frame is the same as the identification information of the first slave device; and the third message is encapsulated in the payload field of an uplink XGEM frame, and the XGEM port identification in the frame header of the uplink 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 the present aspect has a plurality of other specific implementations, and specific implementations and advantages thereof can be referred to the specific implementations and advantages of the third aspect, which will not be described here.

[0064] In a fifth aspect, the present application provides an optical network communication method applied to an optical fiber network, the optical fiber network comprising a master device and at least one slave device, the at least one slave device comprising a first slave device. The optical network communication method provided by the present application can be executed by the first slave device in the optical fiber network, or by a part of functional modules or chips in the first slave device. Taking the first slave device as an example, the first slave device receives a fourth message from the master device, the fourth message comprising a third rate, the third rate being a CIR (Committed Information Rate) and / or a PIR (Peak Information Rate), and the unit of the third rate being related to a 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 the present application, 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 if 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 further determine the effective CIR / PIR of the first slave device. The CIR / PIR configuration problem of 50G PON and future higher-rate PONs is solved.

[0066] 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 byte per second; and when the line rate of the first slave device is greater than the preset threshold, the unit of the third rate is N byte per second, N being an integer greater than 0.

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

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

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

[0070] 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 comprises the identification information of the traffic descriptor managed entity, and the message content field of the fourth message comprises an attribute value of a CIR attribute and / or an attribute value of a PIR attribute.

[0071] 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 byte 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 byte per second.

[0072] In a possible implementation, the fourth message is encapsulated in a payload field of a downstream XGEM frame, and an XGEM port identifier in a 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, applied to a fiber network, the fiber network including a master device and at least one slave device, the at least one slave device including a first slave device. The optical network communication method provided in this aspect can be executed by the master device in the fiber network, or can be executed by part of 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 including a third rate, the third rate being a guaranteed information rate (CIR) and / or a peak information rate (PIR), the unit of the third rate being related to a line rate of the first slave device and a preset threshold, the line rate of the first slave device and the preset threshold being used to determine the unit of the third rate.

[0075] In 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 byte per second; and when the line rate of the first slave device is greater than the preset threshold, the unit of the third rate is N byte per second, N being 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 identification information of a 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 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 byte 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 byte per second.

[0081] In a possible implementation, the fourth message is encapsulated in a payload field of a downlink XGEM frame, and an XGEM port identifier in a frame header of the downlink 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 the present aspect has a plurality of other specific implementations, and specific reference can be made to the specific implementations and advantages of the fifth aspect, which will not be described here again.

[0084] In a seventh aspect, the present application provides an optical network communication method applied to a fiber network, the fiber network including a master device and at least one slave device, the at least one slave device including a first slave device. The optical network communication method provided by the present aspect can be executed by the first slave device in the fiber network, or can be executed by part of a functional module or a 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 including second indication information, the second indication information being used to instruct the first slave device to report a third rate, the third rate being a guaranteed information rate (CIR) and / or a peak information rate (PIR), and the unit of the third rate being related to a line rate of the first slave device and a preset threshold; then, the first slave device sends a sixth message to the master device, the sixth message including the third rate of the first slave device.

[0085] In the present 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 the preset threshold, the first slave device reports the attribute value of the CIR attribute / PIR attribute after receiving the second indication information, and the effective CIR / PIR of the first slave device is determined by the master device itself, thereby indirectly realizing the provision of the effective CIR / PIR of the first slave device to the master device. That is, without changing the existing attribute, the value of the CIR / PIR used by the first slave device in operation is expanded, and the CIR / PIR reporting problem of 50G PON and future higher-rate PONs is solved.

[0086] In a possible implementation, the third rate is in units of bytes per second when the line rate of the first slave device is less than or equal to a preset threshold; and the third rate is in units of N bytes per second when the line rate of the first slave device is greater than the preset threshold, N being 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 comprises identification information of the traffic descriptor managed entity; and the sixth message further comprises the identification information of the traffic descriptor managed entity.

[0090] In a possible implementation, the second indication information is a second attribute mask, a bit corresponding to the CIR attribute in the second attribute mask is 1, and a 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 comprises the identification information of the traffic descriptor managed entity, and the message content field of the fifth message comprises 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 comprises the identification information of the traffic descriptor managed entity, and the message content field of the sixth message comprises 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; and 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 a payload field of a downstream XGEM frame, an XGEM port identifier in a frame header of the downstream XGEM frame is the same as the identification information of the first slave device; and the sixth message is encapsulated in a payload field of an upstream XGEM frame, an XGEM port identifier in a 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 applied to an optical fiber network, the optical fiber network comprising a master device and at least one slave device, the at least one slave device comprising a first slave device. The optical network communication method provided by the present application can be executed by the master device in the optical fiber network, or by a part of functional modules or chips in the master device. Taking the master device as an example, the master device sends a fifth message to the first slave device, the fifth message comprising second indication information, the second indication information being used to instruct the first slave device to report a third rate, the third rate being a CIR (Committed Information Rate) and / or a PIR (Peak Information Rate), the unit of the third rate being related to a line rate of the first slave device and a preset threshold; then, the master device receives a sixth message from the first slave device, the sixth message comprising the third rate of the first slave device.

[0097] In the present application, 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, the first slave device reports the attribute value of the CIR attribute / PIR attribute after receiving the second indication information, and the effective CIR / PIR of the first slave device is determined by the master device itself, thereby indirectly providing the effective CIR / PIR of the first slave device to the master device. That is, without changing the existing attribute, the value of the CIR / PIR used by the first slave device in operation is expanded, and the CIR / PIR reporting problem of the 50G PON and future higher-rate PONs is solved.

[0098] In a possible implementation, in the case that the line rate of the first slave device is less than or equal to the preset threshold, the unit of the third rate is byte per second; in the case that the line rate of the first slave device is greater than the preset threshold, the unit of the third rate is N byte per second, N being an integer greater than 0.

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

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

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

[0102] 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 being 1, and the bit corresponding to the PIR attribute in the second attribute mask being 1.

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

[0104] In a possible implementation, the message type of the sixth message is an acquisition response, the identification information field of the managed entity of the sixth message comprises the identification information of the traffic descriptor managed entity, and the message content field of the sixth message comprises the 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 byte 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 byte per second.

[0106] In a possible implementation, the fifth message is encapsulated in the payload field of a downlink XGEM frame, and the XGEM port identification in the frame header of the downlink XGEM frame is the same as the identification information of the first slave device; and the sixth message is encapsulated in the payload field of an uplink XGEM frame, and the XGEM port identification in the frame header of the uplink 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 the present aspect has a plurality of other specific implementations, and specific implementations and beneficial effects of the seventh aspect can be referred to for details, which will not be described here again.

[0109] In a ninth aspect, an embodiment of the present application provides a communication apparatus, which can be the master device in the foregoing embodiments, or a chip in the master device. The communication apparatus can include a processing module and a transceiver module. When the communication apparatus is the master device, the processing module can be a processor, and the transceiver module can be a transceiver. The master device can further include a storage module, which can be a memory. The storage module is configured to store instructions, and the processing module executes the instructions stored in the storage module, so that the master device performs the method in the second aspect, the fourth aspect, the sixth aspect, the eighth aspect, and any one of the embodiments of the foregoing aspects. When the communication apparatus is a chip in the master device, the processing module can be a processor, and the transceiver module can be an input / output interface, a pin, or a circuit, etc. The processing module executes the instructions stored in the storage module, so that the master device performs the method in the second aspect, the fourth aspect, the sixth aspect, the eighth aspect, and any one of the embodiments of the foregoing aspects. The storage module can be a storage module (for example, a register, a cache, etc.) in the chip, or a storage module (for example, a read-only memory, a random access memory, etc.) in the master device and located outside the chip.

[0110] In a tenth aspect, an embodiment of the present application provides a communication apparatus, which can be the slave device (for example, the first slave device) in the foregoing embodiments, or a chip in the slave device (for example, the first slave device). The communication apparatus can include a processing module and a transceiver module. When the communication apparatus is the slave device (for example, the first slave device), the processing module can be a processor, and the transceiver module can be a transceiver. Optionally, the slave device (for example, the first slave device) can further include a storage module, which can be a memory. The storage module is configured to store instructions, and the processing module executes the instructions stored in the storage module, so that the slave device (for example, the first slave device) performs the method in the first aspect, the third aspect, the fifth aspect, the seventh aspect, and any one of the embodiments of the foregoing aspects. When the communication apparatus is a chip in the slave device (for example, the first slave device), the processing module can be a processor, and the transceiver module can be an input / output interface, a pin, or a circuit, etc. The processing module executes the instructions stored in the storage module, so that the slave device (for example, the first slave device) performs the method in the first aspect, the third aspect, the fifth aspect, the seventh aspect, and any one of the embodiments of the foregoing aspects. The storage module can be a storage module (for example, a register, a cache, etc.) in the chip, or a storage module (for example, a read-only memory, a random access memory, etc.) in the slave device (for example, the first slave device) and located outside the chip.

[0111] In an eleventh aspect, the present application provides a communication apparatus, which can be an integrated circuit chip. The integrated circuit chip comprises a processor. The processor is coupled to a memory for storing a program or instructions, which when executed by the processor, cause the communication apparatus to perform the method introduced in any of the various embodiments of the preceding aspects.

[0112] In a twelfth aspect, the embodiments of the present application provide a computer program product comprising instructions which, when executed on a computer, cause the computer to perform the method introduced in any of the various embodiments of the preceding aspects.

[0113] In a thirteenth aspect, the embodiments of the present application provide a computer-readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform the method introduced in any of the various embodiments of the preceding aspects.

[0114] In a fourteenth aspect, the embodiments of the present application provide an optical fiber network, which comprises the master device introduced in the second aspect and any of the embodiments of the second aspect, and the slave device (e.g., the first slave device) introduced in the first aspect and any of the embodiments of the first aspect; or the optical fiber network comprises the master device introduced in the fourth aspect and any of the embodiments of the fourth aspect, and the slave device (e.g., the first slave device) introduced in the third aspect and any of the embodiments of the third aspect; the optical fiber network comprises the master device introduced in the sixth aspect and any of the embodiments of the sixth aspect, and the slave device (e.g., the first slave device) introduced in the fifth aspect and any of the embodiments of the fifth aspect; the optical fiber network comprises the master device introduced in the eighth aspect and any of the embodiments of the eighth aspect, and the slave device (e.g., the first slave device) introduced in the seventh aspect and any of the embodiments of the seventh aspect. BRIEF DESCRIPTION OF DRAWINGS

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

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

[0117] FIG. 2 is a flow diagram of an optical network communication method in the present application;

[0118] FIG. 3A is an example diagram of a message format of a create request message in the prior art;

[0119] FIG. 3B is an example diagram of a message format of a create request message provided in the present application;

[0120] FIG. 3C is an example diagram of a message format of a conventional set request message;

[0121] FIG. 3D is an example diagram of a message format of a set request message provided by the present application;

[0122] FIG. 4 is another flow diagram of an optical network communication method in the present application;

[0123] FIG. 5A is an example diagram of a message format of a conventional get request message;

[0124] FIG. 5B is an example diagram of a message format of a get request message provided by the present application;

[0125] FIG. 5C is an example diagram of a message format of a conventional get response message;

[0126] FIG. 5D is an example diagram of a message format of a get response message provided by the present application;

[0127] FIG. 6 is another flow diagram of an optical network communication method in the present application;

[0128] FIG. 7 is another flow diagram of an optical network communication method in the present application;

[0129] FIG. 8 is a diagram of an embodiment of a communication device in the present application;

[0130] FIG. 9 is a diagram of another embodiment of a communication device in the present application. DETAILED DESCRIPTION

[0131] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, not all the embodiments of the present application.

[0132] In the various embodiments of the present application, the terms and / or descriptions of different embodiments are consistent and can be referenced to each other if there is no special description and logical conflict. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0133] The terms "first", "second", "third", "fourth", and the like in the description and in the claims of the present application, and above-mentioned drawings (if there are) are used to distinguish similar objects, and do not have to be used to describe a particular order or sequence. It should be understood that the terms used in this way 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 "include" and "have" 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 have to be limited to those steps or units clearly listed, but can 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 only used to describe the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent the three cases of A alone, A and B together, and B alone. In addition, the character " / " herein generally represents an "or" relationship between the associated objects before and after it.

[0135] The optical network communication method provided by the present application is applied to a fiber network. FIG. 1A is an example diagram of the architecture of a fiber network in the prior art. As shown in FIG. 1A, the 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 with the ONU (or the ONT) through the ODN. The ODN is a network composed of one or more optical devices, including optical fibers, an optical distribution frame (ODF), an optical splitter (also known as a splitter), a combiner, etc. In addition, the foregoing OLT can be connected with an operator network through a network-side interface, the OLT can be connected with the ODN through a dedicated interface, the ODN is connected with the ONU (or the ONT) through a dedicated interface, and the ONU (or the ONT) is connected with a user-side network through a user-side interface or a dedicated interface. In the downstream direction, the OLT broadcasts a downstream optical signal, and the downstream optical signal is distributed to each ONU (or the ONT) through the ODN. In the upstream direction, a time division multiple access (TDMA) mode is adopted, and each ONU (or the ONT) transmits an upstream optical signal in a respective upstream time slot allocated by the OLT.

[0136] As shown in FIG. IB, a structure diagram of the optical fiber network provided by the present application is shown. The optical fiber network provided by the present application includes a master device 01 and at least one slave device 02, the master device 01 is connected with the at least one slave device 02 through 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 an ONT), and the master device is connected with the at least one slave device through an optical distribution network. In an example, the slave device can be directly connected with a terminal device of a user, and the terminal device can be a mobile phone, a tablet computer connected with the foregoing router through WiFi, and 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, the slave device is an optical modem provided by an operator, and the optical modem is connected with an indoor router and other devices. The present application takes the master device and the slave device as an example for introduction.

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

[0138] It should also be understood that the optical network communication method provided by the present application can be applied to a PON network. For example, a G-bit passive optical network (Gigabit-capable Passive Optical Networks, GPON), a 10G-bit passive optical network (10-Gigabit-capable Passive Optical Networks, XG-PON), a 10G-bit symmetric passive optical network (10-Gigabit-capable Symmetric Passive Optical Networks, XGS-PON), a 50G-bit passive optical network (50-Gigabit-capable Passive Optical Networks, 50GPON), and a future higher rate PON system, etc. The present application is not limited.

[0139] In order to facilitate understanding of the optical network communication method provided by the present application, the OMCI protocol and the management model defined in the OMCI protocol are introduced as follows:

[0140] The OMCI protocol is a master-slave management protocol, in which a master device (e.g., an OLT) issues commands and waits for a slave device (e.g., an ONU) to reply after executing the aforementioned commands. In the OMCI protocol, various resources and services of the slave device managed by the master device are abstracted into a protocol-independent management information base (MIB). The basic information unit of the management information base is a managed entity (also referred to as a management entity, ME). The managed entity is an abstract representation of a resource and / or service of the slave device, and is a management object abstracted from a plurality of resources and / or services to be managed. When the managed entity is embodied in a certain slave device or a certain service, it becomes an instance. The master device implements configuration management of each managed entity ME by configuring instances for the slave device.

[0141] The present application mainly relates to a traffic descriptor managed entity (hereinafter referred to as a traffic descriptor ME). The traffic descriptor ME is used for traffic management of a slave device. For example, a slave device supporting priority control can point from a media access control (MAC) bridge port configuration data managed entity to a traffic descriptor managed entity to implement traffic management such as marking traffic and policing traffic. For another example, a slave device supporting rate control can point from a MAC bridge port configuration data managed entity or a GEM port network connection termination point (CTP) managed entity to a traffic descriptor managed entity to implement traffic management such as marking traffic and traffic shaping.

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

[0143] Table 1

[0144] The first column in Table 1 shows the order of the multiple attributes included in the traffic descriptor ME. When the master device configures the multiple attributes of the traffic descriptor ME for the slave device, or when the master device acquires the multiple attributes of the traffic descriptor ME from the slave device, the master device fills in the attribute values or attribute masks in the order of the aforementioned attributes. The second column shows the names of the multiple attributes included in the traffic descriptor ME. The third column shows whether the attribute is readable, writable, and when it is set. The readable operation can be understood as the master device reading the attribute value by sending a get message to the slave device and receiving a get response message from the slave device. The writable operation can be understood as the master device configuring the attribute value by sending a create message or a set message to the slave device. Set-by-create means that the master device sets the attribute value when the instance of the ME is created for the first time. The fourth column shows which of the multiple attributes of the traffic descriptor ME are mandatory attributes and which are optional attributes. The fifth column shows the size of each attribute value in bytes.

[0145] The present 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, namely the managed entity ID (ME ID) attribute, which uniquely identifies the instance of the traffic descriptor ME. The ME ID attribute is a readable and writable attribute, and is a mandatory attribute with a size of 2 bytes. The second row is the second attribute of the traffic descriptor ME, namely the committed information rate (CIR) attribute, which specifies the committed information rate in bytes per second (byte / s). The default value is 0. The CIR attribute is set when the instance is created, 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, namely the peak information rate (PIR) attribute, which specifies the peak information rate in bytes per second (byte / s). The default value is 0. The PIR attribute is set when the instance is created, is a readable and writable attribute, and is an optional attribute with a size of 4 bytes.

[0146] Since the length of the CIR attribute field and the PIR attribute field is 4 bytes, and the unit of the CIR attribute and the PIR attribute is bytes per second (byte / s), the maximum value of the CIR attribute and the PIR attribute is 4,294,967,295 (i.e. 2 32-1), i.e. the maximum CIR or PIR configurable by the two attributes is 4,294,967,295 bytes / s, which is approximately equal to 34G bit / s. That is, according to the current standard, the master device can only configure the slave device with a CIR or PIR of 34G bit / s. However, the PON system has developed to 50G PON, or even future higher-rate PONs, i.e. the working line rate of the slave device can reach 50G bit / s or even higher line rate, and the master device needs to configure the slave device with a CIR or PIR of 50G bit / s or even higher line rate. Obviously, the field length of the CIR attribute and the PIR attribute in the current traffic descriptor ME is insufficient to support the configuration of 50G PON and future higher-rate PONs.

[0147] To this end, the present application provides various solutions for solving the CIR / PIR configuration problem of 50G PON and future higher-rate PONs.

[0148] In one solution, a new attribute of the traffic descriptor ME is defined, i.e. the rate amplification factor attribute to be introduced later, which together with the standard-defined CIR attribute determines the effective CIR of the slave device, and which together with the standard-defined PIR attribute determines the effective PIR of the slave device. For details, please refer to the related description in the corresponding embodiments of FIG. 2 and FIG. 4.

[0149] In another solution, the definition of CIR and PIR in the current standard is modified, i.e. the unit of the CIR and PIR is defined in relation to the line rate of the slave device and a preset threshold, rather than necessarily being bytes per second. For details, please refer to the related description in the corresponding embodiments of FIG. 6 and FIG. 7.

[0150] Next, the main flow of the first solution of the optical network communication method provided by the present application will be introduced in combination with FIG. 2 and FIG. 4:

[0151] As shown in FIG. 2, it is a schematic diagram of one embodiment of the optical network communication method provided by the present application. In the embodiment, the master device configures the attributes for the first slave device through a create message or a set message, and the first slave device is one of the plurality of slave devices connected to the master device. The embodiment takes the interaction between the master device and the first slave device as an example for illustration. Of course, the subject performing the action of the master device in the method can also be a device, module or chip in the master device, and the subject performing the action of the first slave device in the method can also be a device, module or chip in the first slave device, which is not limited in the embodiment. For example, as shown in FIG. 2, the optical network communication method comprises the following steps:

[0152] In 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.

[0153] 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 the optical fiber. The first message comprises a rate amplification factor. Optionally, the first message further comprises a first rate. The rate amplification factor is an adjustment coefficient of the first rate.

[0154] The first rate is CIR and / or PIR. For example, the first rate is CIR; or, the first rate is PIR; or, the first rate is CIR and PIR. In one implementation, the first rate can be a CIR value and / or a PIR value indicated by the master device to the first slave device through a CIR field and / or a PIR field in a 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 comprises the first rate. In another implementation, the first rate can be a CIR value and / or a PIR value indicated by the master device to the first slave device through a CIR field and / or a PIR field in the first message. For example, the first message comprises 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 a CIR value and / or a 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 first rate carried in the first message is taken as an example in the following description. It should be understood that “CIR carried in the first message” in the following description can be replaced by “CIR carried in the seventh message”, or by “default CIR”; and “PIR carried in the first message” in the following description can be replaced by “PIR carried in the seventh message”, or by “default PIR”.

[0155] The rate amplification factor is an adjustment coefficient of the first rate, i.e., 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 a second rate, which is a valid CIR and / or a valid PIR of the first slave device. The valid CIR of the first slave device can be understood as an effective CIR of the first slave device, and can also be understood as a CIR used by the first slave device when working; and the valid PIR of the first slave device can be understood as an effective PIR of the first slave device, and can also be understood as a PIR used by the first slave device when working.

[0156] 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 by the first message is equal to the effective CIR of the first slave device (i.e. the CIR used by the first slave device when working). For another example, the product of the rate amplification factor and the PIR carried by the first message is equal to the effective PIR of the first slave device (i.e. the PIR used by the first slave device when working).

[0157] Optionally, the rate amplification factor is an integer greater than 0. For example, if the rate amplification factor is 1, the second rate is equal to the first rate, i.e. the first slave device works according to the CIR value and / or the PIR value indicated by the first message; if the rate amplification factor is greater than 1, for example, the rate amplification factor is a (a is an integer greater than 1), the second rate is equal to a times the first rate, i.e. the first slave device works according to a times the CIR value indicated by the first message and / or a times the PIR value indicated by the first message. As can be seen, in the case that 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 the effective PIR of the first slave device can not be limited to the maximum rate indicated by 4 bytes. Thus, the CIR / PIR configuration problem of 50G PON and future higher-rate PONs is solved.

[0158] It should be noted that, since in the current standard and the development trend of future standards, 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, it can be understood that the first message includes the attribute value of the CIR attribute and / or the attribute value of the PIR attribute, in the case that the first message includes the first rate. In addition, the rate amplification factor is a newly defined attribute of the traffic descriptor ME, i.e. the rate amplification factor attribute. It can be understood that the first message includes the attribute value of the rate amplification factor attribute, in the case that the first message includes the rate amplification factor.

[0159] 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 216 (i.e. 16), indicating that the maximum value of the CIR (or PIR) used by the first slave device when working can be 16 times the attribute value of the CIR attribute (or the attribute value of the PIR attribute) carried by the first message. For 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 232 (i.e. 4,294,967,296), indicating that the maximum value of the CIR (or PIR) used by the first slave device when working can be 4,294,967,296 times the attribute value of the CIR attribute (or the attribute value of the PIR attribute) carried by the first message. 4 8 ​That is, 256 times of the attribute value of the CIR attribute (or the attribute value of the PIR attribute) carried in the first message can be the maximum value of the CIR (or the PIR) used by the first slave device when working.

[0160] For example, the attributes included in the traffic descriptor ME provided by the present application are shown in Table 2 below:

[0161] Table 2

[0162] In the example shown in Table 2, the present application newly defines the 10th attribute of the traffic descriptor ME, i.e., the rate scale factor attribute. Since the rate scale factor attribute is related to the CIR attribute or the PIR attribute, the rate scale factor can also be referred to as the CIR / PIR scale factor. The rate scale factor attribute can be defined as a readable attribute, i.e., the master device can read the attribute value of the rate scale factor attribute from the slave device (e.g., the first slave device) through a get process. The rate scale factor attribute can be defined as a writable attribute, i.e., the master device can configure the attribute value of the rate scale factor attribute for the slave device (e.g., the first slave device) through a create process or a set process. In addition, the rate scale factor attribute is a set-by-create attribute, i.e., the master device can set the attribute value of the rate scale 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 scale factor attribute is an optional configuration attribute. The default value of the rate scale factor is 1. Optionally, the size of the rate scale factor attribute is 2 bytes. The other attributes shown in Table 2 are the same as the current standard definition, which will not be described here.

[0163] It should be understood that the definitions of the rate scale factor attribute shown in Table 2 are only one example and are not strictly limited. For example, if other new attributes of the traffic descriptor ME are introduced in the standard, the rate scale factor attribute can also be the 11th attribute of the traffic descriptor ME. For another example, the rate scale factor can 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 introduced hereinafter.

[0164] It should be noted that in the embodiment, the first slave device is a registered slave device, and the first slave device has established an OMCI management channel with 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, the OMCI message includes a create flow related message (for example, a create request message, also referred to as a create message), a set flow related message (for example, a set request message, also referred to as a set message), and a get flow related message (for example, a get request message, also referred to as a get message). In the embodiment, the first message is a create request message or a set request message.

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

[0166] In a possible implementation, the first message is a create request message, that is, the message type of the first message is a create request, that is, a message sent by the master device to the first slave device when the master device creates an instance of the traffic descriptor ME of the first slave device for the first time. The identification information field of the managed entity of the first message includes identification information of the traffic descriptor managed entity, the message content field of the first message includes an attribute value of the rate amplification factor attribute, and the message content field of the first message further includes an attribute value of the CIR attribute and / or an attribute value of the PIR attribute.

[0167] An example is shown in FIG. 3A. The first and second bytes are transaction correlation identifier (TCI) field, which is used to identify the same group of request messages and response messages, for example, to match the request message (or command) from master device to slave device and the response message from slave device to master device. Generally, the value of transaction correlation field in a group of corresponding request and response messages is consistent. The third byte is message type (MT) field, which is used to indicate the purpose or action of the message, or in other words, the message type of the message. The first to fifth bits of the third byte are message type (MT) bits, which are used to indicate the message type, for example, create, delete, set, get, etc. The sixth bit of the third byte is acknowledge request (AR) bit, which is used to indicate whether the message needs to be acknowledged by the peer. The seventh bit of the third byte is acknowledge (AK) bit, which is used to indicate whether the message is acknowledged. The eighth bit of the third byte is reserved bit, which is fixed as 0. The message type of the example shown in FIG. 3A is create request type. The fourth byte is device identifier field, which is fixed as 0x0A for the baseline OMCI message format shown in FIG. 3A. The fifth to eighth bytes are message entity identifier, which includes entity class and the entity instance corresponding to the entity. In the example shown in FIG. 3A, the value of the fifth and sixth bytes is 280, which represents the traffic descriptor managed entity, i.e., the ME ID of the traffic descriptor managed entity. The ninth to fortieth bytes are message contents field, which is used to carry the message contents, i.e., to encapsulate the packet payload. The last four bytes are message integrity check (MIC) field, which is used for message integrity check.

[0168] Since the first byte of the message content 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 order and with the size of the attribute. Therefore, in combination with the aforementioned Table 2, it can be known that the attribute value of the first attribute in the message content field is the attribute value of the CIR attribute with 4 bytes, occupying the 9th to 12th bytes; the attribute value of the second attribute in the message content field is the attribute value of the PIR attribute with 4 bytes, occupying the 13th to 16th bytes; and so on, the attribute value of the ninth attribute in the message content field is the attribute value of the rate amplification factor attribute with 2 bytes, occupying the 29th to 30th bytes. The remaining bytes in the message content field (i.e. the 31st to 40th bytes) are filled with zero values. Compared with the create request message for configuring CIR / PIR in the conventional technology shown in Fig. 3B, it can be known that the 29th to 40th bytes in the message content field are all zero values in the conventional technology.

[0169] In another possible implementation, the first message is a set request message, i.e. the message type of the first message is set request. For example, the master device sends a set request message to the first slave device when it needs to reconfigure 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. Optionally, 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.

[0170] Further, the message content field of the first message further comprises an attribute mask, which is used to indicate which attribute values of which attributes are carried in the message content field. The attribute mask is 2 bytes (i.e. 16 bits) in size, thus, the attribute mask indicates at most 16 attributes. The attribute mask can be a bitmap used in get message (i.e. get request message), get response message, create response and set message (i.e. set request message), which indicates which attributes are requested or provided. The attribute mask corresponds to the order of the attributes after the ME ID of the traffic descriptor ME (i.e. the order of the attributes after the ME ID shown in Table 2) from the high bit to the low bit (i.e. from the 8th bit to the 1st bit). Since the CIR attribute is the 2nd attribute of the traffic descriptor entity (i.e. the 1st attribute after the ME ID attribute), the CIR attribute corresponds to the 1st bit in the attribute mask. The PIR attribute is the 3rd attribute of the traffic descriptor entity (i.e. the 2nd attribute after the ME ID attribute), 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 in the attribute mask corresponding to the CIR attribute is 1; if the message content field does not carry the attribute value of the CIR attribute, the 1st bit in the attribute mask corresponding to the CIR attribute is 0. The rest of the attributes are similar, which will not be described here.

[0171] In the present application, the attribute mask indicating the attribute value of 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 9th bit in the first attribute mask corresponds to the rate amplification factor attribute.

[0172] As shown in FIG. 3C, an example of the set request message is provided. The set request message shown in FIG. 3C is different from the create request message shown in FIG. 3A only in the message type field and the message contents field. The explanations of the rest of the fields can refer to the descriptions of the example shown in FIG. 3A. As shown in FIG. 3C, the message type indicated by the message type (MT) field in the third byte is the set request type. The message contents field is from the ninth byte to the fortieth byte. The ninth byte to the tenth byte is the attribute mask. The ninth byte to the tenth byte of the attribute mask corresponds to the order of the attributes after the ME ID in the traffic descriptor ME (i.e., the order of the attributes after the ME ID shown in Table 2) from the high bit to the low bit (i.e., from the eighth bit to the first bit). For example, the eighth bit of the ninth byte corresponds to the CIR attribute, the seventh bit of the ninth byte corresponds to the PIR attribute, and so on. The eighth bit of the tenth byte corresponds to the rate amplification factor attribute. In one example, as shown in FIG. 3C, 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, 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 1, indicating that the message contents field carries the attribute value of the PIR attribute. 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. In another example, if the first message carries the attribute value of the rate amplification factor attribute, the eighth bit of the ninth byte is 0, indicating that the message contents field does not carry 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. 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 the attribute mask can have other examples according to the types of the attribute values carried in the message contents field, which are not described herein.

[0173] In addition, the rest of the 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 the message contents field 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 each set-by-create attribute is allocated space in the create message in order and according to the size of the attribute. 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 byte to the (n+2)th byte of the message contents field, where n is an integer greater than or equal to 11 and less than or equal to 38.

[0174] In one example, if the set request message requests to configure the attribute values of all attributes of the traffic descriptor ME, according to the foregoing Table 2, the 11th-14th bytes are the attribute values of the 4-byte CIR attribute, the 15th-18th bytes are the attribute values of the 4-byte PIR attribute, and so on, the 31st-32nd bytes are the attribute values of the 2-byte rate amplification factor attribute, and the remaining bytes (i.e., the 33rd-40th bytes) in the message content field are filled with zero values. In another example, if the set request message requests to configure the CIR attribute, the PIR attribute, and the rate amplification factor attribute, according to the foregoing Table 2, the 11th-14th bytes are the attribute values of the 4-byte CIR attribute, the 15th-18th bytes are the attribute values of the 4-byte PIR attribute, the 19th-20th bytes are the attribute values of the 2-byte rate amplification factor attribute, and the remaining bytes (i.e., the 21st-40th bytes) in the message content field are filled with zero values. In another example, if the set request message requests to configure the CIR attribute (or the PIR attribute) and the rate amplification factor attribute, according to the foregoing Table 2, the 11th-14th bytes are the attribute values of the 4-byte CIR attribute (or the attribute values of the PIR attribute), the 15th-16th bytes are the attribute values of the 2-byte rate amplification factor attribute, and the remaining bytes (i.e., the 17th-40th bytes) in the message content field are filled with zero values. In another example, if the set request message requests to configure only the rate amplification factor attribute, the 11th-12th bytes are the attribute values of the 2-byte rate amplification factor attribute, and the remaining bytes (i.e., the 13th-40th bytes) in the message content field are filled with zero values. In actual applications, there can be other examples, which are not listed one by one here.

[0175] It should be noted that, compared with the set request message for configuring the CIR / PIR in the conventional technology shown in FIG. 3D, in the conventional technology, the 8th bit of the 10th byte of the message content field is 0 because the attribute values of the rate amplification factor attribute are not carried, and the message content field does not include the attribute values of the rate amplification factor attribute.

[0176] It should be understood that, in the embodiments, FIGS. 3A, 3B, 3C, and 3D are all introduced by taking the baseline OMCI message format as an example, and in actual applications, the various types of messages introduced in the foregoing FIGS. 3A, 3B, 3C, and 3D can also adopt the extended OMCI message format, which is not described here.

[0177] Optionally, the first message is encapsulated in a payload field of a downstream XG-PON encapsulation method (XGEM) frame. A header of the XGEM frame contains information for distinguishing different OMCI XGEM Ports, which are logical ports on the slave device for carrying data from a downstream PON port of the master device. The XGEM Ports of different slave devices are identified differently, and thus different slave devices can be distinguished according to the XGEM Port identification. In this embodiment, the XGEM port identification (XGEM port ID) in the header of the XGEM frame is the same as the identification information (e.g., ONU ID) of the first slave device, i.e., the XGEM port ID is the same as the ONU ID.

[0178] At step 202, the first slave device determines a second rate of the first slave device based on the rate amplification factor and the first rate.

[0179] The second rate is the effective CIR and / or PIR of the first slave device. The second rate is described in step 201 above, and thus is not described here.

[0180] In one possible implementation, the second rate is equal to the product of the first rate and the rate amplification factor. The first slave device determines the second rate based on the product of the first rate and the rate amplification factor. For example, the first slave device obtains a property value of 4,294,967,295 bytes / s (about 34.36 Gbit / s) for the CIR attribute from the first message, and a property value of 2 for the rate amplification factor attribute, and thus the effective CIR of the first slave device is the product of the property value of the CIR attribute and the property value of the rate amplification factor attribute, i.e., 8,589,934,590 bytes / s (about 68.72 Gbit / s). As can be seen, the master device can solve the CIR / PIR configuration problem of 50G PON and future higher-rate PONs by defining the rate amplification factor.

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

[0182] As shown in FIG. 4, another embodiment of the optical network communication method provided by the present application is shown. In this embodiment, the master device reads an attribute from the first slave device by a get message and a get response message, the first slave device being one of the plurality of 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 subject performing the action of the master device in this method can also be a device, a module or a chip in the master device; the subject performing the action of the first slave device in this method can also be a device, a module or a chip in the first slave device, which is not limited in this embodiment. For example, as shown in FIG. 4, the optical network communication method comprises the following steps:

[0183] In 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.

[0184] For example, the master device sends the 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. The second message comprises first indication information, the first indication information being used to instruct the first slave device to report a rate amplification factor, the rate amplification factor being an adjustment factor of the first rate. Optionally, the first indication information is also used to instruct the first slave device to report the first rate, the first rate being the CIR and / or PIR. The rate amplification factor and the first rate are used to determine the second rate, the second rate being the effective rate of the CIR and / or PIR of the first slave device. For the explanation of the first rate, the rate amplification factor and the second rate, please refer to the related description in the foregoing step 201, which is not repeated here.

[0185] In this embodiment, the first indication information can be an attribute mask, and the attribute mask is introduced in the foregoing step 201, which is not repeated here.

[0186] In a possible implementation, the first indication information is a first attribute mask, and the first attribute mask is used to indicate that the second message requests the first slave device to report an attribute value of the rate amplification factor attribute. For example, a bit corresponding to the rate amplification factor attribute in the first attribute mask is 1, indicating that the first slave device is requested 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, i.e., the 9th attribute after the ME ID attribute, the 9th bit in the first attribute mask corresponds to the rate amplification factor attribute, and the 9th bit in the first attribute mask is 1.

[0187] Optionally, the first attribute mask is also used to indicate that the first slave device reports an attribute value of a CIR attribute and / or an attribute value of a PIR attribute. In an example, the first attribute mask indicates that the first slave device reports the attribute value of the rate amplification factor attribute, the attribute value of the CIR attribute, and the attribute value of the PIR attribute. In this case, the 1st attribute in the first attribute mask is the CIR attribute, the bit corresponding to the CIR attribute in the first attribute mask is 1, indicating that the first slave device is requested to report the attribute value of the CIR attribute; the 2nd attribute in the first attribute mask is the PIR attribute, the bit corresponding to the PIR attribute in the first attribute mask is 1, indicating that the first slave device is requested to report the attribute value of the PIR attribute; and the 9th attribute in the first attribute mask is the rate amplification factor attribute, the bit corresponding to the rate amplification factor attribute in the first attribute mask is 1, indicating that the first slave device is requested to report the attribute value of the rate amplification factor attribute. It should be understood that, according to different attributes indicated by the first attribute mask of the message, the first attribute mask can also have other examples, which are not described herein.

[0188] It should be noted that, in the embodiment, the first slave device is a registered slave device, and the first slave device has established an OMCI management channel with 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, the OMCI message includes a create flow related message (for example, a create request message), a set flow related message (for example, a set request message), and a get flow related message (for example, a get request message). In the 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 identification information of a traffic descriptor managed entity, and the message content field of the second message includes the first indication information, i.e., the message content field of the second message includes the first attribute mask.

[0189] As shown in FIG. 5A, an example of the get message (i.e., get request message) provided by the present application is shown. The get request message shown in FIG. 5A is different from the create request message shown in FIG. 3A only in the message type field and the message contents field. The explanations of the remaining fields can refer to the descriptions of the example shown in FIG. 3A. As shown in FIG. 5A, the message type indicated by the message type (MT) field in the third byte is the get request type. The message contents field is from the ninth byte to the fortieth byte. The ninth byte and the tenth byte are the attribute mask, which is used to indicate which attributes are requested. The mapping rule of the attribute mask is the same as that of the attribute mask in the set request message shown in FIG. 3C. The specific description is omitted here. Specifically, the eighth bit of the ninth byte corresponds to the CIR attribute, the seventh bit of the ninth byte corresponds to the PIR attribute, and so on. The eighth bit of the tenth byte corresponds to the rate amplification factor attribute. In an example, as shown in FIG. 5A, if the second message requests to report the attribute value of the CIR attribute, the attribute value of the PIR attribute, and the attribute value of the rate amplification factor attribute, the eighth bit of the ninth byte is 1, which indicates that the CIR attribute is requested to be reported by the slave device. The seventh bit of the ninth byte is 1, which indicates that the PIR attribute is requested to be reported by the slave device. The eighth bit of the tenth byte is 1, which indicates that the rate amplification factor attribute is requested to be reported by the slave device. In another example, if the second message requests to report only the attribute value of the CIR attribute and the attribute value of the rate amplification factor attribute, the eighth bit of the ninth byte is 1, which indicates that the CIR attribute is requested to be reported by the slave device. The seventh bit of the ninth byte is 0, which indicates that the PIR attribute does not need to be reported. The eighth bit of the tenth byte is 1, which indicates that the rate amplification factor attribute is requested to be reported by the slave device. It should be understood that the attribute mask can have other examples according to the types of the attribute values requested to be reported by the second message, and the specific description is omitted here. In addition, the remaining bytes of the message contents field are filled with zero values.

[0190] It should be noted that, compared with the get request message for configuring the CIR / PIR in the prior art shown in FIG. 5B, in the prior art, the master device does not indicate the slave device to report the rate amplification factor attribute. Therefore, the eighth bit of the tenth byte of the message contents field is 0.

[0191] Optionally, the second message is encapsulated in a payload field of a downstream XGEM frame. A frame header (XGEM Header) of the downstream XGEM frame contains information for distinguishing different OMCI XGEM Ports (hereinafter referred to as XGEM Ports), which are logical ports on the slave device and used for carrying data from a downstream PON port of the master device. The XGEM Ports of different slave devices are identified differently, thus different slave devices can be distinguished according to the identification of the XGEM Ports. In this embodiment, the XGEM port identification (XGEM port ID) in the frame header (XGEM Header) of the downstream XGEM frame is the same as the identification information (e.g. ONU ID) of the first slave device, i.e. the XGEM port ID is the same as the ONU ID.

[0192] At 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.

[0193] 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 the optical fiber. The third message includes the rate amplification factor of the first slave device and the first rate. The rate amplification factor and the first rate are explained in the foregoing step 201, which will not be repeated here.

[0194] In addition, the third message is a response message of the second message. Since the second message is a get request message, the third message is a get response message, i.e. the message type of the third message is get response. In addition, 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, wherein 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. The first attribute mask is explained in the foregoing step 401, which will not be repeated here.

[0195] As shown in FIG. 5C, an example of the get response message provided by the present application is shown. The get response message shown in FIG. 5C is different from the create request message shown in FIG. 3A only in the message type field and the message contents field. The explanations of the rest of the fields can refer to the related descriptions of the example shown in FIG. 3A, which will not be repeated here. As shown in FIG. 5C, the message type indicated by the message type (MT) field in the 3rd byte is the get response type. The message contents field is from the 9th byte to the 40th byte. The 9th byte is used to indicate the processing result of the get operation. The first 4 bits of the 9th byte are fixed as "0000", i.e., the 8th-5th bits are fixed as "0000"; the last 4 bits of the 9th byte are used to indicate the reason of the processing result. "0000" of the 4th-1st bits shown in FIG. 5C indicates that the command processing is successful, i.e., the attribute mask (e.g., the first attribute mask) in the request message (e.g., the second message) is successfully acquired. The 10th-11th bytes are the attribute mask, which is used to indicate which attributes are provided. The mapping rule of the attribute mask is the same as that of the attribute mask in the set request message shown in FIG. 3C, which will not be repeated 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. In this embodiment, the second message and the third message both carry the first attribute mask are taken as an example for description. Specifically, the 8th bit of the 10th byte corresponds to the CIR attribute, the 7th bit of the 10th byte corresponds to the PIR attribute, and so on, and the 8th bit of the 11th byte corresponds to the rate amplification factor attribute. In one example, as shown in FIG. 5C, if the third 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, the 8th bit of the 10th byte is 1, indicating that the message contents field carries the attribute value of the CIR attribute, the 7th bit of the 10th byte is 1, indicating that the message contents field carries the attribute value of the PIR attribute, and the 8th bit of the 11th 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 value of the CIR attribute and the attribute value of the rate amplification factor attribute, 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 0, indicating that the message contents field does not carry the attribute value of the PIR attribute, and the 8th bit of the 10th 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 types of the attribute values carried by the third message, the first attribute mask can also have other examples, which will not be repeated here. In addition, the 37th-38th bytes carry an optional attribute mask, and the 39th-40th bytes carry an attribute execution mask.In addition, the rest of the bytes of the message content field are used to carry the attribute values of the attributes indicated by the attribute mask.

[0196] It should be noted that the message content field of the get response message is different from the message content field of the create request message. The first byte of the message content field of the create request message starts with the attribute value of the first set-by-create attribute, and each set-by-create attribute is assigned space in the create message in order and according to the size of the attribute. However, the message content field of the get 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) bytes of the message content field, where m is an integer greater than or equal to 12 and less than or equal to 34.

[0197] In one example, if the get response message carries the attribute values of all attributes of the traffic descriptor ME, it can be known in combination with the foregoing Table 2 that the 12th~15th bytes are the attribute value of the 4-byte CIR attribute, the 16th~19th bytes are the attribute value of the 4-byte PIR attribute, and so on, the 32nd~33rd bytes are the attribute value of the 2-byte rate amplification factor attribute, and the rest of the bytes (i.e., the 34th~36th bytes) in the message content field are filled with zero values. In another example, if the get response message provides the CIR attribute, the PIR attribute, and the rate amplification factor attribute to the host device, it can be known in combination with the foregoing Table 2 that the 12th~15th bytes are the attribute value of the 4-byte CIR attribute, the 16th~19th bytes are the attribute value of the 4-byte PIR attribute, the 20th~21st bytes are the attribute value of the 2-byte rate amplification factor attribute, and the rest of the bytes (i.e., the 22nd~36th bytes) in the message content field are filled with zero values. In another example, if the get response message provides the CIR attribute (or the PIR attribute) and the rate amplification factor attribute to the host device, it can be known in combination with the foregoing Table 2 that the 12th~15th bytes are the attribute value of the 4-byte CIR attribute (or the attribute value of the PIR attribute), the 16th~17th bytes are the attribute value of the 2-byte rate amplification factor attribute, and the rest of the bytes (i.e., the 18th~36th bytes) in the message content field are filled with zero values. In another example, if the get response message only provides the rate amplification factor attribute to the host device, the 12th~13th bytes are the attribute value of the 2-byte rate amplification factor attribute, and the rest of the bytes (i.e., the 14th~36th bytes) in the message content field are filled with zero values. In actual applications, there can be other examples, which are not listed one by one here.

[0198] It should be noted that, compared with the acquisition response message in which the CIR / PIR is configured in the prior art shown in FIG. 5D, the 8th bit of the 11th byte of the message content field is 0 due to the fact that the attribute value of the rate amplification factor attribute is not carried in the prior art, and the message content field does not contain the attribute value of the rate amplification factor attribute.

[0199] It should be understood that, in the embodiments, FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are all introduced in the baseline OMCI message format, and in actual applications, the various types of messages introduced in the foregoing FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D can also adopt the extended OMCI message format, which is not described herein.

[0200] 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 (for example, ONU ID) of the first slave device, that is, the XGEM port ID is the same as the ONU ID.

[0201] In the embodiments, the first slave device can receive the first indication information from the master device, to indicate that the first slave device reports the rate amplification factor and the first rate, and the rate amplification factor is the adjustment coefficient of the first rate (that is, 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, so as to realize the provision of the effective CIR / PIR of the first slave device to the master device. That is, on the basis of not changing the existing attribute, the value of the CIR / PIR used by the first slave device in the working state is expanded, and the CIR / PIR reporting problem of the 50G PON and future higher-rate PONs is solved.

[0202] The main process of the second solution of the optical network communication method provided in the present application will be introduced below in combination with FIG. 6 and FIG. 7:

[0203] As shown in FIG. 6, another embodiment of the optical network communication method provided in the present application is shown. In this embodiment, the master device configures the attribute for the first slave device, which is one of the slave devices connected to the master device, by a create message or a set message. This embodiment takes the interaction between the master device and the first slave device as an example for illustration. Of course, the subject performing the action of the master device in this method can also be a device, a module or a chip in the master device; the subject performing the action of the first slave device in this method can also be a device, a module or a chip in the first slave device, which is not limited in this embodiment. For example, as shown in FIG. 6, the optical network communication method comprises the following steps:

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

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

[0206] The fourth message comprises a third rate, and the third rate is CIR and / or PIR. Since the master device manages and maintains the CIR and PIR of the slave device through the CIR attribute and the PIR attribute of the traffic descriptor ME, it can be understood that the fourth message comprises the attribute value of the CIR attribute and / or the attribute value of the PIR attribute, that is, the fourth message carries the attribute value of the CIR attribute and / or the attribute value of the PIR attribute.

[0207] In addition, the unit of the third rate is related to the line rate of the first slave device and a preset threshold. In the case that the line rate of the first slave device is less than or equal to the preset threshold, the unit of the third rate is byte per second; in the case that the line rate of the first slave device is greater than the preset threshold, the unit of the third rate is N byte per second, and N is an integer greater than 0. The line rate of the first slave device can be the line rate used by the first slave device when it is working. It should be noted that before receiving the fourth message, the first slave device registers online in the master device, and the master device establishes an OMCI management channel with the first slave device, during which the master device can know the line rate used by the first slave device when it is working.

[0208] That is, compared with the CIR attribute and the PIR attribute in the prior art, the CIR attribute and the PIR attribute provided by the embodiment have different definitions. In the prior art, the unit of the attribute value of the CIR attribute is byte per second, and the unit of the attribute value of the PIR attribute is byte per second. In the present application, the unit of the CIR attribute and the unit of the PIR attribute are related to the line rate of the slave device to be configured by the master device and a preset threshold, and are not necessarily byte per second. For example, for the CIR attribute, in a case where 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 byte per second; in a case where 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 byte per second, N being an integer greater than 0. For example, for the PIR attribute, in a case where 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 byte per second; in a case where 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 byte per second, N being an integer greater than 0.

[0209] Optionally, the default value of N is 1. The value of N can be preconfigured or determined through negotiation between the master device and the slave device, which is not limited in the present application.

[0210] Optionally, the preset threshold is 9.95328 Gbit / s. In some scenarios, the preset threshold can also be referred to as 10 Gbit / s. Optionally, the preset threshold is less than 4,294,967,295 bytes / s (about 34.36 Gbit / s). Since the present embodiment does not modify the byte size of the attribute value carrying the CIR attribute or the byte size of the attribute value carrying the PIR attribute, the maximum value of the attribute value of the CIR attribute is still 4,294,967,295 bytes / s (about 34.36 Gbit / s), and the maximum value of the attribute value of the PIR attribute is still 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).

[0211] In addition, the fourth message of the embodiment can be a create request message or a set request message.

[0212] In a possible implementation, the fourth message is a create request message, i.e., the message type of the fourth message is create request, which is a message sent by the master device to the first slave device when the master device creates an instance of the traffic descriptor ME of the first slave device for the first time. 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 that of the create message for configuring CIR / PIR in the prior art, which is shown in the example of FIG. 3B and will not be repeated here.

[0213] In another possible implementation, the fourth message is a set request message, i.e., the message type of the fourth message is set request. For example, the master device sends a set request message to the first slave device when it is necessary to reconfigure the traffic descriptor ME of the first slave device. In this case, the identification information field of the fourth message includes the identification information of the traffic descriptor managed entity, and the message content field of the fourth message includes not only the attribute value of the CIR attribute and / or the attribute value of the PIR attribute, but also a second attribute mask. The second attribute mask is used to indicate that the message content field carries the attribute 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.

[0214] Optionally, the fourth message is encapsulated in the payload field of a downstream XGEM frame. The frame header (XGEM Header) of the downstream XGEM frame contains information for distinguishing different XGEM ports, which are logical ports on the slave device and are used to carry data from the downstream PON port of the master device. The XGEM ports of different slave devices have different identifications, so different slave devices can be distinguished according to the identifications of the XGEM ports. In this embodiment, the XGEM port identification (XGEM port ID) in the frame header (XGEM Header) of the downstream XGEM frame is the same as the identification information (e.g., ONU ID) of the first slave device, i.e., the XGEM port ID is the same as the ONU ID.

[0215] In 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.

[0216] 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 the preset threshold. For the explanation of the preset threshold, please refer to the foregoing step 601, which will not be repeated here. The valid CIR of the first slave device can be understood as the effective CIR of the first slave device, and can also be understood as the CIR used by the first slave device when working; the valid PIR of the first slave device can be understood as the effective PIR of the first slave device, and can also be understood as the PIR used by the first slave device when working.

[0217] In a possible implementation, the line rate of the first slave device is less than or equal to the preset threshold, and the first slave device determines the value of the third rate (i.e., the attribute value of the CIR attribute and / or the attribute value of the PIR attribute) as the valid CIR / PIR of the first slave device, with the unit of byte per second. For example, if the line rate of the first slave device is less than or equal to the preset threshold, and the attribute value of the CIR attribute is A, then the attribute value of the CIR attribute has the unit of byte per second, and the valid CIR of the first slave device is A byte per second; if the line rate of the first slave device is less than or equal to the preset threshold, and the attribute value of the PIR attribute is B, then the attribute value of the PIR attribute has the unit of byte per second, and the valid PIR of the first slave device is B byte per second. Wherein, A and B are integers greater than 0.

[0218] In another possible implementation, the line rate of the first slave device is greater than the preset threshold, and the first slave device determines 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 as the valid CIR / PIR of the first slave device, with the unit of byte per second. For example, if the line rate of the first slave device is greater than the preset threshold, and the attribute value of the CIR attribute is A, then the attribute value of the CIR attribute has the unit of N byte per second, and the first slave device determines the valid CIR of the first slave device as A*N byte per second; if the line rate of the first slave device is greater than the preset threshold, and the attribute value of the PIR attribute is B, then the attribute value of the PIR attribute has the unit of N byte per second, and the first slave device determines the valid PIR of the first slave device as B*N byte per second. Wherein, A, B and N are integers greater than 0.

[0219] In this embodiment, the third rate unit 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 third rate unit, i.e., determine the effective CIR / PIR of the first slave device, based on the line rate of the first slave device and the preset threshold. Therefore, even if the third rate has a limited value, the first slave device can determine the third rate unit 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. The CIR / PIR configuration problem of 50G PON and future higher rate PONs is solved.

[0220] As shown in FIG. 7, another embodiment of the optical network communication method provided in the present application is shown. In this embodiment, the master device reads the attribute from the first slave device, which is one of the plurality of slave devices connected to the master device, through a get message and a get response message. This embodiment is described by taking the interaction between the master device and the first slave device as an example. Of course, the subject performing the action of the master device in this method can also be a device, a module or a chip in the master device; the subject performing the action of the first slave device in this method can also be a device, a module or a chip in the first slave device, which is not limited in this embodiment. For example, as shown in FIG. 7, the optical network communication method includes the following steps:

[0221] In 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.

[0222] For example, the master device sends the fifth message to the first slave device through an optical fiber; correspondingly, the first slave device receives the fifth message from the master device through the optical fiber. 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 being CIR and / or PIR, and the unit of the third rate being related to the line rate of the first slave device and the preset threshold. For the explanation of the third rate, please refer to the related description in step 601 in the foregoing text, which is not repeated here.

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

[0224] In addition, the fifth message in this embodiment can be a get request message, i.e., the message type of the fifth message is a get request. In this case, the fifth message further includes identification information of the traffic descriptor managed entity, and the message content field of the fifth message includes the aforementioned second indication information (e.g., the aforementioned second attribute mask). The message format of the fifth message is the same as that of the get request message for configuring CIR / PIR in the prior art, and details are shown in the example in FIG. 5B, which will not be repeated here.

[0225] Optionally, the fifth message is encapsulated in the payload field of a downstream XGEM frame. The frame header (XGEM Header) of the downstream XGEM frame includes information for distinguishing different XGEM ports, which are logical ports on the slave device and are used to carry data from the downstream PON port of the master device. The XGEM ports of different slave devices have different identifications, and thus different slave devices can be distinguished according to the identifications of the XGEM ports. In this embodiment, the XGEM port identification (XGEM port ID) in the frame header (XGEM Header) of the downstream XGEM frame is the same as the identification information (e.g., ONU ID) of the first slave device, i.e., the XGEM port ID is the same as the ONU ID.

[0226] In step 702, the first slave device sends a sixth message to the master device, and correspondingly, the master device receives the sixth message from the first slave device.

[0227] For example, the first slave device sends the sixth message to the master device through the optical fiber; correspondingly, the master device receives the sixth message from the first slave device through the optical fiber. The sixth message includes a third rate of the first slave device. In the case that the line rate of the first slave device is less than or equal to a preset threshold, the third rate is in units of bytes per second; in the case that the line rate of the first slave device is greater than the preset threshold, the third rate is in units of N bytes per second, N is an integer greater than 0. For the explanation of the third rate, please refer to the relevant description in step 601 in the foregoing, which will not be repeated here.

[0228] In addition, the sixth message is a response message of the fifth message. Since the fifth message is an acquisition request message, the sixth message is an acquisition response message, i.e., the message type of the sixth message is acquisition 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 the sixth message is the same as that of the acquisition response message for configuring CIR / PIR in the prior art, and specific details are shown in the example of FIG. 5D in the foregoing, which will not be repeated here.

[0229] It should be understood that before the first slave device receives the fifth message, the first slave device registers online at 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 in the working time, and the master device can also know the line rate used in the working time of the first slave device. 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 by the sixth message, the line rate of the first slave device, and the preset threshold.

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

[0231] In the embodiment, the first slave device can receive the second indication information from the master device to indicate 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 the preset threshold, the first slave device reports the attribute value of the CIR attribute / PIR attribute after receiving the second indication information, and the master device determines the effective CIR / PIR of the first slave device by itself, thereby indirectly realizing the provision of the effective CIR / PIR of the first slave device to the master device. That is, without changing the existing attribute, the value of the CIR / PIR used by the first slave device in operation is extended, and the CIR / PIR reporting problem of the 50G PON and future higher-rate PONs is solved.

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

[0233] As shown in FIG. 8, the communication apparatus 80 can include a processor 801 and a transceiver 802, and the processor 801 is coupled with the transceiver 802. The aforementioned processor 801 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The aforementioned PLD can 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 can be one processor, or can include a plurality of processors, which is not limited specifically here.

[0234] The transceiver 802 can also be referred to as a transceiving unit, a transceiver, a transceiving device, etc. Alternatively, the device in the transceiving unit for implementing the receiving function can be regarded as a receiving unit, and the device in the transceiving unit for implementing the sending function can be regarded as a sending unit, i.e., the transceiving unit includes the receiving unit and the sending unit, the receiving unit can also be referred to as a receiver, an input port, a receiving circuit, etc., and the sending unit can be referred to as a transmitter, a transmitter, or a transmitting circuit, etc. Alternatively, when the communication apparatus 80 is configured to implement the function of the master device in the method shown in FIG. 2, FIG. 4, FIG. 6, or FIG. 7, the transceiver 802 can be configured to receive the uplink burst optical signal. Alternatively, the transceiver 802 supports receiving the burst optical signal at one or more uplink rates.

[0235] The communication apparatus 80 can further include a memory 803. The processor 801 is coupled to the memory 803. The memory 803 is mainly configured to store software programs and data. The memory 803 can exist independently and be connected to the processor 801. Alternatively, the memory 803 can be integrated with the processor 801, for example, in one or more chips. The memory 803 can store program codes for implementing the technical solutions of the embodiments of the present application and be controlled to execute by the processor 801. The executed computer programs of various types can also be regarded as the driver of the processor 801. The memory 803 can include a volatile memory such as a random-access memory (RAM), and can also include a non-volatile memory such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD), or a solid-state drive (SSD). The memory 803 can also include a combination of the above-mentioned memories. The memory 803 can refer to one memory or can include a plurality of memories. For example, the memory 803 is configured to store various data.

[0236] In one implementation, the communication apparatus 80 is configured to implement the function of the master device in the method embodiment corresponding to FIG. 2. Specifically, the processor 801 is configured to generate a first message, the first message including a rate amplification factor, the rate amplification factor being an adjustment coefficient of a first rate, the first rate being a guaranteed information rate CIR and / or a peak information rate PIR, the rate amplification factor and the first rate being used to determine a second rate of a first slave device, the second rate being an effective CIR and / or PIR of the first slave device. The transceiver 802 is configured to send the first message to the first slave device. Alternatively, the first message further includes the first rate.

[0237] In another implementation, the communication apparatus 80 is configured to implement the function of the first slave device in the method embodiment of FIG. 2. Specifically, the transceiver 802 is configured to receive a first message from a master device, the first message comprising a rate scaling factor, the rate scaling factor being a scaling factor of a first rate, the first rate being a guaranteed information rate CIR and / or a peak information rate PIR. The processor 801 is configured to determine a second rate of the first slave device based on the rate scaling factor and the first rate, the second rate being an effective CIR and / or PIR of the first slave device. Optionally, the first message further comprises the first rate.

[0238] In another implementation, the communication apparatus 80 is configured to implement the function of the master device in the method embodiment of FIG. 4. Specifically, the processor 801 is configured to generate a second message, the second message comprising first indication information, the first indication information being used to instruct the first slave device to report a rate scaling factor, the rate scaling factor being a scaling factor of a first rate, the first rate being a guaranteed information rate CIR and / or a peak information rate PIR. The transceiver 802 is configured to send the second message to the first slave device. In addition, the transceiver 802 is further configured to receive a third message from the first slave device, the third message comprising the rate scaling 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, and in this case, the third message further comprises the first rate.

[0239] In another implementation, the communication apparatus 80 is configured to implement the function of the first slave device in the method embodiment of FIG. 4. Specifically, the transceiver 802 is configured to receive a second message from a master device, the second message comprising first indication information, the first indication information being used to instruct the first slave device to report a rate scaling factor, the rate scaling factor being a scaling factor of a first rate, the first rate being a guaranteed information rate CIR and / or a peak information rate PIR. The processor 801 is configured to generate a third message, the third message comprising the rate scaling factor of the first slave device. In addition, the transceiver 802 is further configured 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, and in this case, the third message further comprises the first rate.

[0240] In another implementation, the communication apparatus 80 is configured to implement the function of the master device in the method embodiment of FIG. 6. Specifically, the processor 801 is configured to generate a fourth message, the fourth message comprising a third rate, the third rate being a guaranteed information rate CIR and / or a peak information rate PIR, a unit of the third rate being related to a line rate of the first slave device and a preset threshold, the line rate of the first slave device and the preset threshold being used to determine the unit of the third rate. The transceiver 802 is configured to send the fourth message to the first slave device.

[0241] In another implementation, the communication apparatus 80 is configured to implement the function of the first slave device in the method embodiment of FIG. 6. Specifically, the transceiver 802 is configured to receive a fourth message from the master device, the fourth message comprising a third rate, the third rate being a CIR and / or a PIR, and a unit of the third rate being related to a line rate of the first slave device and a preset threshold. The processor 801 is configured to determine the unit of the third rate based on the line rate of the first slave device and the preset threshold.

[0242] In another implementation, the communication apparatus 80 is configured to implement the function of the master device in the method embodiment of FIG. 7. Specifically, the processor 801 is configured to generate a fifth message, the fifth message comprising second indication information, the second indication information being used to instruct the first slave device to report a third rate, the third rate being a CIR and / or a PIR, and a unit of the third rate being related to a 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, the sixth message comprising the third rate of the first slave device.

[0243] In another implementation, the communication apparatus 80 is configured to implement the function of the first slave device in the method embodiment of FIG. 7. Specifically, the transceiver 802 is configured to receive a fifth message from the master device, the fifth message comprising second indication information, the second indication information being used to instruct the first slave device to report a third rate, the third rate being a CIR and / or a PIR, and a unit of the third rate being related to a line rate of the first slave device and a preset threshold. The processor 801 is configured to generate a sixth message, the sixth message comprising the third rate of the first slave device. The transceiver 802 is further configured to send the sixth message to the master device.

[0244] For details, please refer to the related description in the corresponding embodiments of FIG. 2, FIG. 4, FIG. 6 or FIG. 7, which will not be repeated here.

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

[0246] The communication apparatus 90 can comprise a processing module 901 (or a processing unit). Optionally, it can further comprise an interface module 902 (or a transceiving unit or a transceiving module) and a storage module 903 (or a storage unit). The interface module 902 is configured to implement communication with other devices. The interface module 902 can be, for example, a transceiving module or an input / output module.

[0247] In a possible design, one or more modules in FIG. 9 can be implemented by one or more processors, or by one or more processors and memories; or by one or more processors and transceivers; or by one or more processors, memories and transceivers, and the embodiments of the present application are not limited in this way. The processors, memories, transceivers can be separately arranged, or integrated together.

[0248] The communication apparatus 90 is provided with the function of the slave device (for example, the first slave device) described in the embodiments of the present application. For example, the communication apparatus 90 includes the slave device (for example, the first slave device) performing the steps corresponding to the modules or units or means of the slave device (for example, the first slave device) described in the embodiments of the present application, and the functions or units or means can be implemented by software, or by hardware, or by hardware executing corresponding software, or by a combination of software and hardware. For details, further reference can be made to the corresponding description in the foregoing method embodiments. For details, further reference can be made to the communication apparatus 80 in the corresponding embodiments of FIG. 8.

[0249] Alternatively, the communication apparatus 90 is provided with the function of the master device described in the embodiments of the present application. For example, the communication apparatus 90 includes the master device performing the steps corresponding to the modules or units or means of the master device described in the embodiments of the present application, and the functions or units or means can be implemented by software, or by hardware, or by hardware executing corresponding software, or by a combination of software and hardware. For details, further reference can be made to the corresponding description in the foregoing method embodiments. For details, further reference can be made to the communication apparatus 80 in the corresponding embodiments of FIG. 8.

[0250] Further, the present application provides a computer program product including 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 wholly or partially generated. For example, the method related to the slave device (e.g., the first slave device) in the foregoing FIG. 2, FIG. 4, FIG. 6 or FIG. 7 is implemented. For another example, the method related to the master device in the foregoing FIG. 2, FIG. 4, FIG. 6 or FIG. 7 is implemented. 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 computer readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) manner. The computer readable storage medium can be any available medium that can be used to store by the computer or data storage device such as server, data center, etc. integrated with one or more available medium sets. The available medium can be magnetic medium (e.g., floppy disk, hard disk, magnetic tape), optical medium (e.g., digital versatile disc (DVD)) or semiconductor medium (e.g., solid state disk (SSD)) etc.

[0251] Further, 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 (e.g., the first slave device) in the foregoing FIG. 2, FIG. 4, FIG. 6 or FIG. 7.

[0252] Further, 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 in the foregoing FIG. 2, FIG. 4, FIG. 6 or FIG. 7.

[0253] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be described herein.

[0254] The above examples are only used to illustrate the technical solutions of the present application, and not to limit them; although the present application has been described in detail with reference to the foregoing examples, those skilled in the art should understand that they can still modify the technical solutions recorded in the foregoing examples, or make equivalent replacements for part of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method of optical network communication, applied to an optical fiber network, the optical fiber network comprising a master device and a slave device, characterized in that, The method comprises: The slave device receives a first message from the master device, the first message comprising a rate amplification factor, the rate amplification factor being a coefficient of adjustment of a first rate, the first rate being 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 of claim 1, wherein, The default value of the rate amplification factor is 1.

3. The method of claim 1, wherein, The rate amplification factor takes an integer greater than 0.

4. The method of 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 of claim 1, wherein, The first message further comprises identification information of a traffic descriptor managed entity.

6. The method of claim 1, wherein, The first message further comprises 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 setup 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 downlink 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 identification 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 method of optical network communication, applied to an optical fiber network, the optical fiber network comprising a master device and a slave device, characterized in that, The method comprises: The master device sends a first message to a slave device, the first message comprising a rate amplification factor, the rate amplification factor being a coefficient of adjustment of a first rate, the first rate being a first guaranteed information rate CIR and / or a first peak information rate PIR, the rate amplification factor and the first rate being used to determine an effective CIR and / or an effective PIR.

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

14. The method of claim 12, wherein, The rate amplification factor takes an integer greater than 0.

15. The method of 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 of claim 12, wherein, The first message further comprises identification information of a traffic descriptor managed entity.

17. The method of claim 12, wherein, The first message further comprises 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 setup 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 of any one of claims 12-17, wherein, The master device is an optical line terminal OLT, and the slave device is an optical network unit ONU.

21. A method of optical network communication, applied to an optical fiber network, the optical fiber network comprising a master device and a slave device, the method comprising: Comprise: The slave device receives a second message from the master device, the second message comprising first indication information, the first indication information being used to instruct the slave device to report a rate amplification factor, the rate amplification factor being a coefficient of adjustment of a first rate, the first rate being 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, the third message comprising the rate amplification factor of the slave device.

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

23. The method of claim 21, wherein, The rate amplification factor takes an integer greater than 0.

24. The method of 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 of claim 24, 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.

26. The method of any one of claims 21-25, wherein, The second message further comprises identification information of a traffic descriptor managed entity, and the third message further comprises identification information of the traffic descriptor managed entity.

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

28. The method of any one of claims 21-25, wherein, The first indication information comprises a first attribute mask, and a bit corresponding to the rate amplification factor attribute in the first attribute mask is the 9th bit.

29. The method of any one of claims 21-25, wherein, The first indication information is further used for instructing the slave device to report the first rate, and the third message further comprises the first rate.

30. A method of optical network communication, applied to an optical fiber network, the optical fiber network comprising a master device and a slave device, the method comprising: Comprising: The master device sends a second message to the slave device, the second message comprising first indication information, the first indication information being used for instructing the slave device to report a rate amplification factor, the rate amplification factor being an adjustment coefficient of a first rate, the first rate being 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, the third message comprising the rate amplification factor of the slave device.

31. The method of claim 30, wherein, A default value of the rate amplification factor is 1.

32. The method of claim 30, wherein, The rate amplification factor takes an integer greater than 0 as a value.

33. The method of claim 30, wherein, The rate amplification factor and the first rate are used for determining an effective CIR and / or an effective PIR.

34. The method of 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 of any one of claims 30-34, wherein, The second message further comprises identification information of a traffic descriptor managed entity, and the third message further comprises identification information of the traffic descriptor managed entity.

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

37. The method of any one of claims 30-34, wherein, The first indication information comprises a first attribute mask, and a bit corresponding to the rate amplification factor attribute in the first attribute mask is the 9th bit.

38. The method of any one of claims 30-34, wherein, The first indication information is further used for instructing the slave device to report the first rate, and the third message further comprises the first rate.

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

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

41. A communication system, characterized by Comprising: The communication device in claim 39, and the communication device in claim 40.

42. A computer-readable storage medium, comprising: A computer program is stored, and the computer program is executable by a processor to make a computer execute the method in any one of claims 1 to 38.

43. A computer program product, characterised in that, Computer program instructions are included, and when the computer program instructions run on a computer, the computer program instructions make the computer execute the method in any one of claims 1 to 38.

Images