Information exchange methods, rate adjustment methods, FTTR equipment, media and software products

Abstract

This application provides an information interaction method, a rate adjustment method, an FTTR device, a medium, and a program product, relating to the field of optical communication technology. The method is applied to an FTTR master device in an FTTR network. The method includes: responding to non-standard rate support information from the FTTR master device, non-standard rate support information from the FTTR slave device, and preset non-standard rate switching conditions, determining to perform a non-standard rate switch with the FTTR slave device; sending non-standard line rate information to the FTTR slave device based on the standard line rate; receiving non-standard line rate confirmation information sent by the FTTR slave device in response to the non-standard line rate information based on the standard line rate; and synchronously switching the line rate with the FTTR slave device based on the non-standard line rate information, so as to perform service information interaction with the FTTR slave device based on the non-standard line rate corresponding to the non-standard line rate information. This application can generate and configure non-standard rates according to actual needs.

Description

Technical Field

[0001] This application relates to the field of optical communication technology, and in particular to an information exchange method, a rate adjustment method, an FTTR device, a medium, and a program product. Background Technology

[0002] With the continuous development of optical communication technology, bandwidth network services are gradually moving towards the F5.5G era, dominated by FTTR (Fiber to the Room) and 50G-PON. FTTR is a new type of fiber optic access technology that extends fiber optic cables from the entry point to every room in a home or business. By deploying a main unit (MFU) and multiple slave units (SFU) indoors, and combining technologies such as 10G-PON, 50G-PON, Wi-Fi 6, and Wi-Fi 7, it achieves gigabit coverage throughout the house, solving problems such as signal attenuation due to wall penetration, insufficient coverage, and substandard speeds in traditional Wi-Fi.

[0003] However, the line rates defined in existing FTTR standards are fixed, including only a limited number such as 2.48832 Gbit / s, 9.95328 Gbit / s, and 49.7664 Gbit / s. In practical applications, the bandwidth requirements of homes and businesses are diverse and continuously growing, and different deployment scenarios may require different non-standard line rates. Because existing standards do not clearly define the implementation methods for non-standard line rates, equipment manufacturers cannot flexibly generate and configure non-standard rates according to actual needs. Summary of the Invention

[0004] This application provides an information interaction method, a rate adjustment method, an FTTR device, a medium, and a program product, which can generate and configure non-standard rates according to actual needs.

[0005] In a first aspect, embodiments of this application provide an information interaction method applied to an FTTR master device in a fiber-to-the-room (FTTR) network, wherein the FTTR network further includes an FTTR slave device communicating with the FTTR master device. The method includes: in response to non-standard rate support information of the FTTR master device, non-standard rate support information of the FTTR slave device, and preset non-standard rate switching conditions, determining to perform a non-standard rate switch with the FTTR slave device; sending non-standard line rate information to the FTTR slave device based on a standard line rate, wherein the non-standard line rate information is obtained based on the non-standard rate support information of the FTTR master device and the non-standard rate support information of the FTTR slave device; receiving non-standard line rate confirmation information sent by the FTTR slave device for the non-standard line rate information based on the standard line rate; and synchronously switching line rates with the FTTR slave device based on the non-standard line rate information, so as to perform service information interaction with the FTTR slave device based on the non-standard line rate corresponding to the non-standard line rate information.

[0006] Secondly, embodiments of this application provide an information interaction method applied to an FTTR slave device in an FTTR network, wherein the FTTR network further includes an FTTR master device communicating with the FTTR slave device. The method includes: receiving non-standard line rate information sent by the FTTR master device based on a standard line rate, wherein the non-standard line rate information is obtained based on non-standard rate support information of the FTTR master device and non-standard rate support information of the FTTR slave device; sending non-standard line rate confirmation information for the non-standard line rate information to the FTTR master device based on the standard line rate; and synchronously switching line rates with the FTTR master device based on the non-standard line rate information, so as to perform information interaction with the FTTR master device based on the non-standard line rate corresponding to the non-standard line rate information.

[0007] Thirdly, embodiments of this application provide a rate adjustment method, including: obtaining a frame parameter adjustment strategy and a frequency increase coefficient; adjusting the standard line rate between at least two FTTR devices according to the frame parameter adjustment strategy and the frequency increase coefficient to obtain a non-standard line rate.

[0008] Fourthly, embodiments of this application provide an FTTR device, comprising: at least one processor; at least one memory for storing at least one program; and when at least one of the programs is executed by at least one of the processors, implementing the information interaction method as described in the first or second aspect, or implementing the rate adjustment method as described in the third aspect.

[0009] Fifthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions for performing the information interaction method as described in the first or second aspect, or for performing the rate adjustment method as described in the third aspect.

[0010] Sixthly, embodiments of this application provide a computer program product, including a computer program or computer instructions, the computer program or computer instructions being stored in a computer-readable storage medium, a processor of a computer device reading the computer program or computer instructions from the computer-readable storage medium, and the processor executing the computer program or computer instructions to cause the computer device to perform the information interaction method as described in the first or second aspect, or to perform the rate adjustment method as described in the third aspect.

[0011] In this embodiment, the FTTR master device first obtains its own non-standard rate support information and the non-standard rate support information of the FTTR slave device, and then determines whether to perform a non-standard rate switch based on a preset non-standard rate switching condition. If the condition is met, the master device determines to perform a non-standard rate switch with the FTTR slave device. Subsequently, the master device sends non-standard line rate information to the FTTR slave device based on the standard line rate. This non-standard line rate information is generated jointly based on the master device's own non-standard rate support information and the slave device's non-standard rate support information. Next, the master device receives confirmation information returned by the slave device for the non-standard line rate information based on the standard line rate, to confirm that the slave device has successfully received and is ready to execute the rate configuration. Finally, the master device synchronously switches the line rate with the slave device based on the non-standard line rate information and interacts with the slave device using the switched non-standard line rate. In this way, the master device can flexibly generate non-standard line rate information not defined by the standard protocol based on the non-standard rate capabilities supported by both the master and slave devices. It can also complete the reliable deployment and application of the rate through signaling interaction and synchronous switching mechanisms. This solves the technical problem that the existing FTTR standard only supports a limited number of fixed line rates and cannot flexibly generate non-standard line rates, enabling the FTTR system to flexibly generate differentiated non-standard line rates according to the actual deployment scenario.

[0012] Other features and advantages of this application will be set forth in the following description and will be apparent in part from the description or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the structures particularly pointed out in the description, claims and drawings. Attached Figure Description

[0013] Figure 1 This is a flowchart illustrating the information interaction method provided in the main device side embodiment of this application; Figure 2 This is a flowchart illustrating the information interaction method provided by the device-side embodiment of this application; Figure 3 This is a schematic diagram of the DLL layer management channel provided in an embodiment of this application; Figure 4 This is a flowchart illustrating the rate adjustment method provided in an embodiment of this application; Figure 5 This is a schematic diagram of a specific implementation of the frame parameter adjustment strategy provided in the embodiments of this application; Figure 6 This is a schematic diagram illustrating another specific implementation of the frame parameter adjustment strategy provided in the embodiments of this application; Figure 7 This is a schematic diagram illustrating another specific implementation of the frame parameter adjustment strategy provided in the embodiments of this application; Figure 8 This is a schematic diagram illustrating another specific implementation of the frame parameter adjustment strategy provided in the embodiments of this application; Figure 9 This is a schematic diagram illustrating another specific implementation of the frame parameter adjustment strategy provided in the embodiments of this application; Figure 10 This is a schematic diagram illustrating another specific implementation of the frame parameter adjustment strategy provided in the embodiments of this application; Figure 11 This is a schematic diagram of the rate control module provided in an embodiment of this application; Figure 12 This is a signaling interaction flowchart of the information interaction method provided in the embodiments of this application; Figure 13 This is a schematic diagram of the FTTR device provided in the embodiments of this application. Detailed Implementation

[0014] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0015] It should be noted that although functional modules are divided in the device schematic diagram and a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first," "second," etc., in the specification, claims, and the aforementioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0016] In the description of the embodiments of this application, unless otherwise expressly limited, terms such as setting, installing, and connecting should be interpreted broadly, and those skilled in the art can reasonably determine the specific meaning of the above terms in the embodiments of this application in combination with the specific content of the technical solution.

[0017] In this application, the terms "furthermore," "exemplarily," or "optionally" are used as examples, illustrations, or descriptions and should not be construed as being more preferred or advantageous than other embodiments or designs. The use of terms such as "furthermore," "exemplarily," or "optionally" is intended to present the relevant concepts in a specific manner.

[0018] In related technologies, with the continuous development of optical communication technology, bandwidth network services are gradually moving towards the F5.5G era, with FTTR (Fiber to the Room) and 50G-PON as the mainstream. FTTR is a new type of fiber optic access technology that extends fiber optic cables from the entry point to every room in a home or business. By deploying a main unit (MFU) and multiple slave units (SFU) indoors, and combining technologies such as 10G-PON, 50G-PON, Wi-Fi 6, and Wi-Fi 7, gigabit coverage can be achieved throughout the house, solving problems such as signal attenuation due to wall penetration, insufficient coverage, and substandard speeds in traditional Wi-Fi.

[0019] However, existing FTTR technology still has the following drawbacks: First, the rigidity of line speeds prevents flexible generation of non-standard rates: According to the ITU-T G.fin and G.Xfin series standards, FTTR systems primarily offer two fixed line speeds: 2.48832 Gbit / s and 9.95328 Gbit / s. The future G.HS-fin standard will support 49.7664 Gbit / s. For non-standard line speeds, such as 3.125 Gbit / s, 12.5 Gbit / s, and 24.8832 Gbit / s, existing standards do not provide implementation methods. With the diversified growth of bandwidth demands from households and businesses, and the cost pressures and long cycles of upgrading from standard to higher speed generations, non-standard line speeds are gradually becoming a common and smooth transition solution. However, existing technologies cannot flexibly support the generation and configuration of these speeds.

[0020] Second, there is a lack of a rate capability negotiation mechanism between master and slave devices: FTTR systems adopt a point-to-multipoint (P2MP) fiber optic topology, with the MFU and multiple SFUs connected via an indoor distributed fiber optic network. In actual deployments, different batches of MFUs and SFUs may have generational differences, and their supported line rate capabilities may vary. The current technology lacks a rate capability negotiation mechanism between MFUs and SFUs, making it impossible to know the frame parameter adjustment strategies and frequency increase coefficients supported by the other party when a device connects. This results in new devices failing to fully utilize their performance advantages, or older devices experiencing problems such as dropped connections or communication failures at newer speeds.

[0021] Third, there is a lack of intelligent rate decision-making capabilities based on service type: different services have different network performance requirements: services such as 4K / 8K video streaming and large file downloads require high throughput bandwidth, while services such as cloud gaming, VR / AR, and real-time audio and video calls have higher requirements for low latency. In existing FTTR technology solutions, the rate upgrade strategy is usually fixed or relies on manual configuration, and it is impossible to dynamically select the optimal rate upgrade method (such as prioritizing latency reduction or bandwidth increase) according to the actual service type, resulting in a mismatch between bandwidth resources and user experience.

[0022] To address at least one of the aforementioned technical problems, embodiments of this application provide an information interaction method, a rate adjustment method, an FTTR device, a medium, and a program product. The FTTR master device first obtains its own non-standard rate support information and the non-standard rate support information of the FTTR slave device, and makes a judgment based on preset non-standard rate switching conditions. If the conditions are met, it determines to perform a non-standard rate switch with the FTTR slave device. Subsequently, the master device sends non-standard line rate information to the FTTR slave device based on the standard line rate. This non-standard line rate information is jointly generated based on the master device's own non-standard rate support information and the slave device's non-standard rate support information. Next, the master device receives confirmation information returned by the slave device regarding the non-standard line rate information based on the standard line rate, confirming that the slave device has successfully received and is ready to execute the rate configuration. Finally, the master device synchronously switches the line rate with the slave device based on the non-standard line rate information and interacts with the slave device using the switched non-standard line rate. In this way, the master device can flexibly generate non-standard line rate information not defined by the standard protocol based on the non-standard rate capabilities supported by both the master and slave devices. It can also complete the reliable deployment and application of the rate through signaling interaction and synchronous switching mechanisms. This solves the technical problem that the existing FTTR standard only supports a limited number of fixed line rates and cannot flexibly generate non-standard line rates, enabling the FTTR system to flexibly generate differentiated non-standard line rates according to the actual deployment scenario.

[0023] This application also provides an information exchange method, applied to the FTTR master device in an FTTR network, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the information interaction method provided in the first aspect of this application.

[0024] like Figure 1 As shown, the method includes, but is not limited to, the following steps: Step S101: In response to the non-standard rate support information of the FTTR master device, the non-standard rate support information of the FTTR slave device and the preset non-standard rate switching conditions, determine to perform non-standard rate switching with the FTTR slave device, and send non-standard line rate information to the FTTR slave device based on the standard line rate. The non-standard line rate information is obtained based on the non-standard rate support information of the FTTR master device and the non-standard rate support information of the FTTR slave device. Step S102: Based on the standard line rate, receive the non-standard line rate confirmation information sent by the FTTR slave device for the non-standard line rate information; Step S103: Based on the non-standard line rate information, the line rate is switched synchronously with the FTTR slave device to exchange service information with the FTTR slave device based on the non-standard line rate corresponding to the non-standard line rate information.

[0025] In step S102, the non-standard line rate information is obtained based on the non-standard rate support information of the FTTR master equipment and the non-standard rate support information of the FTTR slave equipment.

[0026] It should be noted that the FTTR master device is the core device in the FTTR network, connecting to the operator's fiber optic cable and serving as the management and control center for the entire home or business optical network. FTTR slave devices are extension devices that communicate with the FTTR master device through an indoor fiber optic distributed network, distributed in various rooms to provide network coverage for different areas.

[0027] Standard line rate refers to the rate used when the FTTR master and FTTR slave initially establish communication, such as 2.48832 Gbit / s as defined by the G.fin standard, 9.95328 Gbit / s as defined by the G.Xfin standard, or 49.7664 Gbit / s as defined by the G.HS-fin standard.

[0028] Table 1 shows the standard line rate, frame period, frame length, and bandwidth granularity for each standard.

[0029] Table 1. Comparison of Standard Line Rate Parameters under Various Standards

[0030] In Table 1 above, the G.fin, G.Xfin, and G.HS-fin standards correspond to the line rate levels of 2.5G, 10G, and 50G FTTR systems, respectively. The frame period is 125µs for all standards; the difference lies in the frame length and bandwidth granularity, which increase with the rate level. Based on this, by introducing a frequency scaling factor n, various non-standard line rates can be flexibly generated on top of the aforementioned standard rates.

[0031] Non-standard rate support information refers to the rate configuration capabilities supported by the equipment (including FTTR master equipment and FTTR slave equipment) other than the standard line rate, specifically including frame parameter adjustment strategies and frequency increase coefficients.

[0032] Preset non-standard rate switching conditions are used to trigger non-standard rate switching decisions and serve as the basis for the FTTR master device to determine whether a non-standard rate switch is necessary. These preset conditions can be triggered based on service type or external commands. The FTTR master device, based on these preset conditions and its own non-standard rate support information as well as that of the FTTR slave device, makes a comprehensive judgment and determines to perform a non-standard rate switch with the FTTR slave device when the condition is met.

[0033] In practical applications, the FTTR master device first obtains its own non-standard rate support information and that of the FTTR slave device, and then makes a judgment based on preset non-standard rate switching conditions. When the preset non-standard rate switching conditions are met, the FTTR master device determines that a non-standard rate switch with the FTTR slave device is required, and sends non-standard line rate information to the FTTR slave device based on the standard line rate. This non-standard line rate information is generated jointly based on the non-standard rate support information of both the FTTR master device and the FTTR slave device, rather than relying on a fixed rate value defined by the standard, thus enabling flexible generation of non-standard line rate information.

[0034] In step S102, after receiving the non-standard line rate information sent by the FTTR master device, the FTTR slave device verifies the message. If the verification passes, it adjusts its own rate configuration according to the target frame parameters and target frequency increase coefficient in the non-standard line rate information, and then sends an acknowledgment message to the FTTR master device. The FTTR master device receives the acknowledgment message based on the standard line rate to confirm that the FTTR slave device has successfully received the non-standard line rate information. Through the above acknowledgment mechanism, reliable transmission of rate switching commands and correct response from the slave device are ensured.

[0035] In step S103, the FTTR master device adjusts its strategy and target frequency increase coefficient according to the target frame parameters in the non-standard line rate information, and synchronously performs line rate switching with the FTTR slave device. When the non-standard line rate information includes a scheduling superframe count (SFC), the FTTR master device and the FTTR slave device synchronously perform switching when they reach the time specified by the SFC at the current time point. The switching method can be dynamic switching (without restarting the device) or restart switching.

[0036] The FTTR master and slave devices re-register and authenticate based on the target frame parameters and target frequency increase coefficients in the non-standard line rate information. During this process, the FTTR master and slave devices will switch rates accordingly, ultimately exchanging information at the non-standard line rate, such as for high-throughput data downloads or low-latency audio and video calls. Simultaneously, after determining the non-standard line rate information, the FTTR master and slave devices store this information in a power-off storable storage medium to ensure that registration and authentication can be performed directly from the non-standard line rate during rate switching and upon the next startup.

[0037] In this embodiment, the FTTR master device first obtains its own non-standard rate support information and the non-standard rate support information of the FTTR slave device, and then determines whether to perform a non-standard rate switch based on a preset non-standard rate switching condition. If the condition is met, the master device decides to switch to a non-standard rate with the FTTR slave device. Subsequently, the master device sends non-standard line rate information to the FTTR slave device based on the standard line rate. This non-standard line rate information is generated jointly by the master device's own non-standard rate support information and the slave device's non-standard rate support information. Next, the master device receives confirmation information returned by the slave device regarding the non-standard line rate information based on the standard line rate, confirming that the slave device has successfully received and is ready to execute the rate configuration. Finally, the master device synchronously switches the line rate with the slave device based on the non-standard line rate information and interacts with the slave device using the switched non-standard line rate. In this way, the master device can flexibly generate non-standard line rate information not defined by the standard protocol based on the non-standard rate capabilities supported by both the master and slave devices. It can also complete the reliable deployment and application of the rate through signaling interaction and synchronous switching mechanisms. This solves the technical problem that the existing FTTR standard only supports a limited number of fixed line rates and cannot flexibly generate non-standard line rates, enabling the FTTR system to flexibly generate differentiated non-standard line rates according to the actual deployment scenario.

[0038] In some embodiments, determining to perform a non-standard rate switch with an FTTR slave device in response to non-standard rate support information of the FTTR master device, non-standard rate support information of the FTTR slave device, and preset non-standard rate switching conditions includes: obtaining service type information of the FTTR slave device; determining to perform a non-standard rate switch with the FTTR slave device in response to service type information of the FTTR slave device, non-standard rate support information of the FTTR master device, non-standard rate support information of the FTTR slave device, and preset non-standard rate switching conditions; wherein the preset non-standard rate switching conditions include: determining that the line rate needs to be increased based on the service type information of the FTTR slave device, and that the non-standard rate support information of the FTTR master device and the non-standard rate support information of the FTTR slave device have the same information.

[0039] In this embodiment, service type information is used to characterize the types of services currently carried by the FTTR slave device. Different services have different network performance requirements. For example, services such as 4K / 8K video streaming and large file downloads require high throughput bandwidth, while services such as cloud gaming, VR / AR, and real-time audio and video calls have higher requirements for low latency.

[0040] In practical applications, the FTTR master device obtains the current service type information from the FTTR slave device and determines whether to increase the line rate based on this information. In one example, when the service type information indicates that the currently carried service is a high-throughput service or a low-latency service, the FTTR master device determines that an increase in the line rate is necessary.

[0041] If an increase in line speed is determined, the FTTR master device further checks whether its non-standard rate support information matches that of the FTTR slave device. If they match, the preset non-standard rate switching conditions are met, and the non-standard rate switching is allowed. If they do not match, the preset non-standard rate switching conditions are not met, and the rate switching is not performed, maintaining the current standard line speed. This method ensures that the non-standard rate after switching is supported by both the master and slave devices, avoiding communication interruptions or device disconnections due to rate mismatch.

[0042] In this embodiment, the FTTR master device determines whether it is necessary to increase the line rate based on the service type information of the slave device. When it is determined that an increase is needed, it further determines whether the non-standard rate support information of both parties is the same. Only when both conditions are met is the rate switching triggered. This ensures both the necessity of rate switching and the matching of capabilities between the two parties, avoiding unnecessary power consumption and signaling overhead caused by blind or ineffective switching.

[0043] In some embodiments, obtaining the service type information of the FTTR slave device includes: sending a service type request to the FTTR slave device; and receiving the service type information of the FTTR slave device sent by the FTTR slave device in response to the service type request.

[0044] In this embodiment, the FTTR master device actively obtains the current service type information of the FTTR slave device by sending a service type request to the FTTR slave device. The service type request is used to instruct the FTTR slave device to report the service type information it is currently carrying.

[0045] After receiving a service type request from the FTTR master device, the FTTR slave device collects the service type information it is currently carrying and sends the collected service type information to the FTTR master device. The FTTR master device receives this service type information, thereby obtaining the current service type of the FTTR slave device.

[0046] In one example, the FTTR master device sends a service type request to the FTTR slave device. Upon receiving this request, the FTTR slave device can collect the service type information it is currently carrying through its built-in SoC chip, service identification module, or AI module, and report the collected service type information to the FTTR master device. The FTTR master device receives the service type information sent by the FTTR slave device in response to the service type request, thereby obtaining the FTTR slave device's service type information. Service type information can include high-throughput services (such as video streaming and large file downloads), low-latency services (such as cloud gaming, VR / AR, and real-time audio / video calls), or ordinary services (such as web browsing).

[0047] The FTTR master device determines whether to increase the line rate based on the service type information obtained from the FTTR slave device. When the service type information includes high-throughput or low-latency services, it determines that an increase in line rate is necessary. For example, if the service type information reported by the FTTR slave device includes service types such as "4K video playback" or "VR gaming," the FTTR master device determines that the current line rate cannot meet the bandwidth or latency requirements of that service and therefore determines that an increase in line rate is needed, i.e., it determines to perform a non-standard rate switch.

[0048] As an optional implementation, the FTTR master device can send service type requests to all FTTR slave devices via broadcast or to a specific FTTR slave device via unicast. When using broadcast, all FTTR slave devices report their own service type information; when using unicast, only the addressed FTTR slave device reports its service type information. The specific method used can be flexibly selected based on the actual application scenario.

[0049] In practical applications, when an FTTR master device needs to obtain service type information from an FTTR slave device, it sends a service type request message to the FTTR slave device through the DLL layer management channel. This request message can be encapsulated and transmitted using standard or custom F-PLOAM messages, FMCI messages (i.e., messages from the FMCC management channel), uplink / downlink frame indication bits from the embedded OAM management channel, or WMCC management channel messages. As one implementation method, the service type request can be implemented by extending custom fields of the F-PLOAM message; for example, defining specific opcodes in reserved fields of the F-PLOAM message to indicate that the message is a service type request.

[0050] After receiving a service type request from the FTTR master device, the FTTR slave device collects the service type information it is currently carrying and reports the collected service type information to the FTTR master device through the DLL layer management channel. The FTTR master device receives this service type information, thereby obtaining the current service type of the FTTR slave device.

[0051] In this embodiment, the FTTR master device actively obtains the service type information of the FTTR slave device by sending a request, providing a data basis for subsequent rate switching decisions, so that rate switching can be triggered according to actual service needs and avoid blind switching.

[0052] In some embodiments, the preset non-standard rate switching condition further includes receiving a rate upgrade instruction sent by the operator's network management platform.

[0053] In this embodiment, the preset non-standard rate switching condition can also be receiving a rate upgrade command sent by the operator's network management platform. The operator's network management platform refers to the operator's network management system, used for unified management and configuration of devices in the FTTR network. The rate upgrade command is a control command issued by the operator's network management platform to instruct the FTTR master device to upgrade the line rate.

[0054] When operators determine that upgrading FTTR line rates is necessary to improve user experience, they can bypass service type-based judgments and directly trigger non-standard rate switching through the operator's network management platform or on-site service by maintenance personnel. The operator's network management platform can send rate upgrade commands to the FTTR master device based on network policies, user package upgrades, or user experience improvement needs. Upon receiving the rate upgrade command, the FTTR master device determines that the preset non-standard rate switching conditions are met and executes the step of sending non-standard line rate information to the FTTR slave device.

[0055] It should be noted that the triggering method provided in this embodiment and the triggering method based on service type information are two different implementation methods. When the FTTR master device receives a rate upgrade instruction sent by the operator's network management platform, it can directly trigger the non-standard rate switching process without performing service type collection and rate capability matching judgment. This provides operators with flexible network management tools, making it easier for operators to proactively optimize user experience according to actual operational needs.

[0056] In some embodiments, before sending non-standard line rate information to the FTTR slave device based on the standard line rate, the method further includes: sending a non-standard rate query message to the FTTR slave device; and receiving a non-standard rate capability reporting message sent by the FTTR slave device in response to the non-standard rate query message, wherein the non-standard rate capability reporting message contains non-standard rate support information of the FTTR slave device.

[0057] In this embodiment, the non-standard rate query message is used to query the non-standard rate capabilities supported by the FTTR slave device. The FTTR master device and the FTTR slave device transmit messages through a DLL layer management channel, through which the non-standard rate query message is sent. The DLL layer management channel includes any one of the following: F-PLOAM management channel, FMCC management channel, embedded OAM management channel, or WMCC management channel.

[0058] In practical applications, when an FTTR master device needs to obtain non-standard rate support information from an FTTR slave device, it sends a non-standard rate query message to the FTTR slave device through the DLL layer management channel. The non-standard rate query message can reuse or extend the F-PLOAM or FMCI messages defined in the standard. For example, in the G.Xfin standard FTTR system, this can be achieved through a custom F-PLOAM message. This query message contains an opcode indicating that it is a query message requesting the FTTR slave device to report its non-standard rate support information.

[0059] It should be further noted that non-standard rate query messages can reuse or extend the F-PLOAM or FMCI messages defined in the standard. For example, in the G.Xfin standard FTTR system, rate capability query and setting functions can be implemented through a custom F-PLOAM message. Specifically, the FTTR master and FTTR slave devices query and set rate capabilities through the Get_Set_Rate_Capabilities message. The format of the Get_Set_Rate_Capabilities message is shown in Table 2.

[0060] Table 2. Get_Set_Rate_Capabilities message format

[0061] Table 2 (continued from the previous table)

[0062] In practical applications, when an FTTR master device needs to query the rate capabilities of an FTTR slave device, it sets the opcode S in the Get_Set_Rate_Capabilities message to 0. Upon receiving this message, the FTTR slave device recognizes the opcode as 0, thus determining it to be a query message and requiring it to report its own rate capabilities.

[0063] As an optional implementation, the FTTR master device can send non-standard rate query messages to all FTTR slave devices via broadcast, or it can send them to a specific FTTR slave device via unicast. When using broadcast, the SFU-ID in the message is set to the broadcast ID, and used in conjunction with the vendor ID and VSSN for addressing; when using unicast, the SFU-ID in the message is set to the ID assigned to the specific FTTR slave device. The specific method used can be flexibly selected according to the actual application scenario; for example, broadcast can be used during system initialization, while unicast can be used when querying a specific device.

[0064] After receiving a non-standard rate query message from the FTTR master device, the FTTR slave device first performs addressing based on the SFU-ID, vendor ID, and VSSN to determine if the query message is directed to this device. If the SFU-ID is a broadcast ID, it further checks whether the vendor ID and VSSN match; if the SFU-ID is an ID assigned to this device, it determines that the message is directed to this device. If the query message is directed to this device, the FTTR slave device extracts the opcode from the message. If the opcode is identified as a query opcode (S=0), the slave device sends its non-standard rate support information to the FTTR master device via a non-standard rate capability reporting message. The FTTR master device receives this reporting message, thereby obtaining the non-standard rate support information from the FTTR slave device.

[0065] It should be noted that non-standard rate capability reporting messages can reuse or extend the F-PLOAM messages defined in the standard. Specifically, FTTR slave devices can report their rate support capabilities through the SFU_Rate_Capabilities message. The format of the SFU_Rate_Capabilities message is shown in Table 3.

[0066] Table 3 SFU_Rate_Capabilities message format

[0067] Table 3 (continued from the previous table)

[0068] It should be noted that non-standard rate support information includes frame parameter adjustment strategies and frequency increase coefficients. The frame parameter adjustment strategy refers to the adjustment strategies for frame parameters supported by the device, including frame length, bandwidth granularity, frame rate, and frame period. The frequency increase coefficient is a proportional coefficient for the standard line rate supported by the device, and the frequency increase coefficient is any number greater than zero. FTTR reports the set of frame parameter adjustment strategies and the set of frequency increase coefficients supported by the device in its rate capability reporting message.

[0069] As an optional implementation, the FTTR slave device can proactively report non-standard rate support information to the FTTR master device without waiting for a query from the FTTR master device. For example, after completing registration and authentication, the FTTR slave device can proactively send an SFU_Rate_Capabilities message to the FTTR master device to inform the master device of its own non-standard rate capabilities, thereby reducing signaling interaction processes.

[0070] In this embodiment, the FTTR master device obtains the non-standard rate support information of the slave device by sending a query message, which provides a data basis for the subsequent generation of non-standard line rate information and rate switching decisions. This enables the master device to generate matching non-standard line rate information according to the actual capabilities of the slave device, avoiding communication interruption or device disconnection caused by rate mismatch.

[0071] In some embodiments, the non-standard rate support information includes a frame parameter adjustment strategy and a frequency increase coefficient; the frequency increase coefficient is a proportional coefficient of the standard line rate supported by the device, and the frequency increase coefficient is any number greater than zero; the frame parameter adjustment strategy is an adjustment strategy for rate-related parameters supported by the device, and the rate-related parameters include at least one of frame length, bandwidth granularity, frame rate, and frame period; the non-standard line rate information includes a target frame parameter adjustment strategy and a target frequency increase coefficient, wherein the frame parameter adjustment strategy in the non-standard rate support information of the FTTR master device and the frame parameter adjustment strategy in the non-standard rate support information of the FTTR slave device both include the target frame parameter adjustment strategy, and the frequency increase coefficient in the non-standard rate support information of the FTTR master device and the frequency increase coefficient in the non-standard rate support information of the FTTR slave device both include the target frequency increase coefficient.

[0072] In this embodiment, the non-standard rate support information includes frame parameter adjustment strategies and frequency boosting coefficients.

[0073] The frequency upscaling factor is a proportionality coefficient representing the standard line rate supported by the equipment, and it can be any number greater than zero. It's important to note that the frequency upscaling factor indicates the multiple of the line rate the equipment can support relative to the standard line rate. For example, when the frequency upscaling factor n = 1.25, it means the equipment can support a non-standard rate of 1.25 times the standard line rate; when the frequency upscaling factor n = 1.25587, it means the equipment can support a non-standard rate of 1.25587 times the standard line rate. Because the frequency upscaling factor is any number greater than zero, various non-standard line rates can be flexibly generated by selecting different frequency upscaling factor values, rather than being limited to the few fixed rate values ​​defined by the standard.

[0074] The frame parameter adjustment strategy refers to the frame parameter adjustment strategies supported by the device. Frame parameters include at least one of frame length, bandwidth granularity, frame rate, and frame period. It should be noted that the frame parameter adjustment strategy instructs the device how to adjust frame parameters when the rate is increased to achieve the target non-standard line rate. The frame parameter adjustment strategy includes at least one of the following: Strategy 1: Multiply the current frame rate by the frequency boosting factor, keep the current frame length and current bandwidth granularity unchanged, and divide the current frame period by the frequency boosting factor.

[0075] Strategy 2: Multiply the current frame rate by the frequency boosting factor, keep the current frame period unchanged, multiply the current frame length by the frequency boosting factor, and multiply the current bandwidth granularity by the frequency boosting factor.

[0076] Non-standard line rate information includes the target frame parameter adjustment strategy and the target frequency increase coefficient.

[0077] It should be noted that the non-standard line rate information is generated jointly by the FTTR master device and the FTTR slave device based on the non-standard rate support information of the FTTR master device itself and the non-standard rate support information of the FTTR slave device. It is used to instruct the FTTR slave device to perform rate switching.

[0078] The target frame parameter adjustment strategy is determined from the intersection of the frame parameter adjustment strategies in the non-standard rate support information of the FTTR master device and the FTTR slave device. In other words, both the frame parameter adjustment strategies in the non-standard rate support information of the FTTR master device and the FTTR slave device include the target frame parameter adjustment strategy. In other words, the target frame parameter adjustment strategy is a frame parameter adjustment strategy supported by both the FTTR master device and the FTTR slave device.

[0079] The target frequency increase factor is determined from the intersection of the frequency increase factors in the non-standard rate support information of the FTTR master device and the non-standard rate support information of the FTTR slave device. In other words, both the frequency increase factors in the non-standard rate support information of the FTTR master device and the non-standard rate support information of the FTTR slave device contain the target frequency increase factor. In other words, the target frequency increase factor is a frequency increase factor supported by both the FTTR master device and the FTTR slave device.

[0080] For example, suppose the non-standard rate support information of the FTTR master device is: support for strategy one and strategy two, and support for frequency increase coefficients of 1.25, 1.5, and 2; the non-standard rate support information of the FTTR slave device is: support for strategy one, and support for frequency increase coefficients of 1.25 and 1.5. Then the intersection of the frame parameter adjustment strategies of the FTTR master device and the FTTR slave device is strategy one, and the intersection of the frequency increase coefficients of the FTTR master device and the FTTR slave device is 1.25 and 1.5. Therefore, the FTTR master device can determine the target frame parameter adjustment strategy as strategy one, and the target frequency increase coefficient can be selected from 1.25 and 1.5 (for example, selecting the higher value of 1.5), thereby generating non-standard line rate information.

[0081] In this way, the non-standard line rate information generated by the FTTR master device is supported by both the FTTR master device and the FTTR slave device, thereby ensuring the feasibility of rate switching and avoiding communication interruption or device disconnection due to rate mismatch.

[0082] In some embodiments, the frame parameter adjustment strategy includes at least one of the following: Multiply the current frame rate by the target frequency boosting factor, keep the current frame length and current bandwidth granularity unchanged, and divide the current frame period by the target frequency boosting factor; The current frame rate is multiplied by the target frequency increase factor, the current frame period remains unchanged, the current frame length is multiplied by the target frequency increase factor, and the current bandwidth granularity is multiplied by the target frequency increase factor.

[0083] In this embodiment, the frame parameter adjustment strategy is used to instruct the FTTR master and FTTR slave devices how to adjust frame parameters during non-standard rate switching to achieve the target non-standard line rate. In this embodiment, frame parameters include frame length, bandwidth granularity, frame rate, and frame period.

[0084] It should also be noted that the basic logic of frame parameter adjustment is as follows: first, the current frame rate is multiplied by the frequency increase coefficient to complete the frequency increase operation and reach the target frame rate. Then, the frame parameters such as frame length, bandwidth granularity and frame period are adjusted synchronously to match the frame parameters with the target frame rate.

[0085] Frame parameter adjustment strategies include at least one of the following: Strategy 1: Multiply the current frame rate by the target frequency increase factor, keep the current frame length and current bandwidth granularity unchanged, and divide the current frame period by the target frequency increase factor.

[0086] It should be noted that in Strategy 1, both the FTTR master and slave devices first multiply the current frame rate by the target boost factor to complete the boost operation and achieve the target frame rate. Then, keeping the current frame length and bandwidth granularity unchanged, the current frame period is divided by the target boost factor. As the frame period shortens, the frame rate is increased to the target frame rate (i.e., the current frame rate multiplied by the target boost factor), thus achieving a match between the frame parameters and the target frame rate.

[0087] Taking the G.fin standard as an example, the standard line rate is 2.48832 Gbit / s, the frame period is 125 µs, the frame length is 38880 bytes, and the bandwidth granularity is 2 bytes. When the target frequency increase factor n=1.25, the FTTR master and FTTR slave devices first multiply the frame rate by 1.25 to determine the target frame rate as 3.1104 Gbit / s. Then, keeping the frame length of 38880 bytes and the bandwidth granularity of 2 bytes unchanged, the frame period is changed from 125 µs divided by 1.25 to 100 µs. At this time, the frame rate becomes 2.48832 × 1.25 = 3.1104 Gbit / s, thus achieving the matching of frame parameters with the target frame rate.

[0088] Because the frame period is shortened in Strategy 1, the data frame transmission interval is reduced, thus effectively reducing data transmission latency. This is suitable for latency-sensitive business scenarios such as cloud gaming, VR / AR, and real-time audio / video calls. When the FTTR master device determines that it needs to provide low-latency service support for the FTTR slave device, Strategy 1 can be selected as the target frame parameter adjustment strategy.

[0089] Strategy 2: Multiply the current frame rate by the target frequency increase factor, keep the current frame period unchanged, multiply the current frame length by the target frequency increase factor, and multiply the current bandwidth granularity by the target frequency increase factor.

[0090] It should be noted that in Strategy 2, both the FTTR master and slave devices first multiply the current frame rate by the target frequency increase factor to complete the frequency increase operation and reach the target frame rate. Then, keeping the current frame period unchanged, the current frame length and the current bandwidth granularity are multiplied by the target frequency increase factor respectively. As the frame length increases, each frame can carry more data, and the frame rate is thus increased to the target frame rate, thereby achieving the matching of frame parameters with the target frame rate.

[0091] Taking the G.fin standard as an example, the standard line rate is 2.48832 Gbit / s, the frame period is 125 µs, the frame length is 38880 bytes, and the bandwidth granularity is 2 bytes. When the target frequency increase factor n=1.25, the FTTR master and FTTR slave devices first multiply the frame rate by 1.25 to determine the target frame rate as 3.1104 Gbit / s. Then, keeping the frame period unchanged at 125 µs, the frame length is multiplied by 1.25 from 38880 bytes to 48600 bytes, and the bandwidth granularity is multiplied by 1.25 from 2 bytes to 2.5 bytes. At this point, the frame rate becomes 2.48832 × 1.25 = 3.1104 Gbit / s, achieving the matching of frame parameters with the target frame rate.

[0092] Because the frame length is increased in Strategy 2, each frame can carry more data, thus effectively improving data transmission throughput. This is suitable for business scenarios requiring high throughput, such as 4K / 8K video streaming and large file downloads. When the FTTR master device determines that it needs to provide high-throughput service support for the FTTR slave device, Strategy 2 can be prioritized as the target frame parameter adjustment strategy.

[0093] It should be further clarified that Strategy 1 and Strategy 2 are two parallel frame parameter adjustment methods. The FTTR master device can select one as the target frame parameter adjustment strategy based on the service type information. When the service type is a low-latency service, Strategy 1 is preferred; when the service type is a high-throughput service, Strategy 2 is preferred. Both strategies can flexibly generate various non-standard line rates without significantly altering the existing standard frame format.

[0094] It should also be noted that the frequency boosting factor can take any value greater than zero, including but not limited to typical values ​​such as 1.25, 1.25587, 1.31615, 1.40657, 1.5, 1.5625, 2, and 2.5. By selecting different frequency boosting factors and combining them with the two strategies mentioned above, various non-standard line rates can be flexibly generated. For example, based on the G.fin standard (standard line rate 2.48832 Gbit / s), when n=1.25, 3.1104 Gbit / s is generated; when n=1.5, 3.73248 Gbit / s is generated; when n=2, 4.97664 Gbit / s is generated; and when n=2.5, 6.2208 Gbit / s is generated. Based on the G.Xfin standard (standard line rate 9.95328 Gbit / s), the speed generated is 12.4416 Gbit / s when n=1.25, 14.92992 Gbit / s when n=1.5, 19.90656 Gbit / s when n=2, and 24.8832 Gbit / s when n=2.5. Based on the G.HS-fin standard (standard line rate 49.7664 Gbit / s), the speed generated is 62.208 Gbit / s when n=1.25, 74.6496 Gbit / s when n=1.5, 99.5328 Gbit / s when n=2, and 124.416 Gbit / s when n=2.5.

[0095] In this embodiment, two frequency enhancement strategies are employed to match frame parameters with the target frame rate, thereby flexibly generating various non-standard line rates. Furthermore, the two strategies can be flexibly selected according to different service requirements, satisfying diverse business scenario demands.

[0096] In some embodiments, the method for determining that the non-standard rate support information of the FTTR master device and the non-standard rate support information of the FTTR slave device have the same information includes: in response to the fact that the frame parameter adjustment strategy in the non-standard rate support information of the FTTR master device and the frame parameter adjustment strategy in the non-standard rate support information of the FTTR slave device contain the same frame parameter adjustment strategy, and the frequency increase coefficient in the non-standard rate support information of the FTTR master device and the frequency increase coefficient in the non-standard rate support information of the FTTR slave device contain the same frequency increase coefficient, determining that the non-standard rate support information of the FTTR master device and the non-standard rate support information of the FTTR slave device have the same information.

[0097] In this embodiment, the non-standard rate support information includes frame parameter adjustment strategies and frequency boosting coefficients. Therefore, to determine whether the non-standard rate support information of the FTTR master device and the FTTR slave device has the same information, it is necessary to determine the frame parameter adjustment strategies and frequency boosting coefficients. Specifically, the FTTR master device determines whether its frame parameter adjustment strategy is the same as that of the FTTR slave device. Specifically, the FTTR master device obtains its own set of supported frame parameter adjustment strategies and the set of supported frame parameter adjustment strategies reported by the FTTR slave device, and then determines whether the two sets intersect. If they intersect, it is determined that the frame parameter adjustment strategies of the FTTR master device and the FTTR slave device contain the same frame parameter adjustment strategy.

[0098] The FTTR master device determines whether its own frequency increase factor and the frequency increase factor of the FTTR slave device are the same. Specifically, the FTTR master device obtains its own set of supported frequency increase factors and the set of supported frequency increase factors reported by the FTTR slave device, and then determines whether the two sets have an intersection. If there is an intersection, it is determined that the frequency increase factor of the FTTR master device and the frequency increase factor of the FTTR slave device contain the same frequency increase factor.

[0099] When both of the above dimensions intersect, that is, when the frame parameter adjustment strategy of the FTTR master device and the frame parameter adjustment strategy of the FTTR slave device contain the same frame parameter adjustment strategy, and the frequency increase coefficient of the FTTR master device and the frequency increase coefficient of the FTTR slave device contain the same frequency increase coefficient, the FTTR master device determines that its non-standard rate support information and the non-standard rate support information of the FTTR slave device have the same information.

[0100] For example, suppose the FTTR master device supports frame parameter adjustment strategies {strategy one, strategy two} and supports frequency boosting coefficients {1.25, 1.5, 2}; the FTTR slave device supports frame parameter adjustment strategy {strategy one} and supports frequency boosting coefficients {1.25, 1.5}. Then the FTTR master device determines that the frame parameter adjustment strategies have an intersection {strategy one}, and the frequency boosting coefficients have an intersection {1.25, 1.5}. Since both dimensions intersect, it is determined that the non-standard rate support information of the FTTR master device and the non-standard rate support information of the FTTR slave device contain the same information.

[0101] For example, suppose the FTTR master device supports frame parameter adjustment strategy {Strategy 1}, supporting frequency increase coefficients {1.25, 1.5}; the FTTR slave device supports frame parameter adjustment strategy {Strategy 2}, supporting frequency increase coefficients {1.25, 1.5}. The FTTR master device determines that the frame parameter adjustment strategies do not overlap. Although the frequency increase coefficients may overlap, because the frame parameter adjustment strategies do not overlap, it determines that the non-standard rate support information of the FTTR master device and the FTTR slave device are not identical. In this case, the FTTR master device decides not to perform a rate switch and maintains the current standard line rate.

[0102] By assessing these two dimensions, the FTTR master device can accurately determine whether it and the FTTR slave device share a common non-standard rate configuration. Only when both dimensions intersect can the FTTR master device confirm the existence of identical information, thus ensuring that the subsequently generated non-standard line rate information is supported by both the FTTR master and FTTR slave devices, avoiding communication interruptions or device disconnections due to rate mismatches.

[0103] In some embodiments, the method for determining non-standard line rate information includes: obtaining at least one identical frame parameter adjustment strategy contained in both the frame parameter adjustment strategy in the non-standard rate support information of the FTTR master device and the frame parameter adjustment strategy in the non-standard rate support information of the FTTR slave device; determining a frame parameter adjustment strategy as the target frame parameter adjustment strategy in the non-standard line rate information from the at least one identical frame parameter adjustment strategy; obtaining at least one identical frequency increase coefficient contained in both the non-standard rate support information of the FTTR master device and the non-standard rate support information of the FTTR slave device; and determining the largest identical frequency increase coefficient as the target frequency increase coefficient in the non-standard line rate information from the at least one identical frequency increase coefficient.

[0104] In this embodiment, the FTTR master device first obtains the set of frame parameter adjustment strategies it supports and the set of frame parameter adjustment strategies supported by the FTTR slave device. Then, it takes the intersection of the two sets to obtain at least one identical frame parameter adjustment strategy. The FTTR master device then selects one of these at least one identical frame parameter adjustment strategies as the target frame parameter adjustment strategy.

[0105] As an optional implementation, when multiple identical frame parameter adjustment strategies exist, the FTTR master device can select one based on the service type information of the FTTR slave device. If the service type is a low-latency service, strategy one is preferred as the target frame parameter adjustment strategy because strategy one can effectively reduce latency by shortening the frame period; if the service type is a high-throughput service, strategy two is preferred as the target frame parameter adjustment strategy because strategy two can effectively improve throughput by increasing the frame length and bandwidth granularity.

[0106] Under the target frame parameter adjustment strategy, the FTTR master device obtains the set of frequency increase coefficients it supports and the set of frequency increase coefficients supported by the FTTR slave device. Then, it takes the intersection of the two sets to obtain at least one identical frequency increase coefficient. The FTTR master device selects the frequency increase coefficient with the largest value from this at least one identical frequency increase coefficient as the target frequency increase coefficient. In other words, the target frequency increase coefficient is a frequency increase coefficient supported by both devices under the target frame parameter adjustment strategy. It should be noted that the target frame parameter adjustment strategy and the target frequency increase coefficient are bound together; that is, the target frequency increase coefficient is determined under the selected target frame parameter adjustment strategy to ensure that the selected strategy and coefficients can be matched and executed, avoiding invalid configurations due to mismatch between strategy and coefficients.

[0107] For example, assuming the FTTR master device supports a set of frequency increase coefficients of {1.25, 1.5, 2}, and the FTTR slave device supports a set of frequency increase coefficients of {1.25, 1.5}, then the common frequency increase coefficients are {1.25, 1.5}. The FTTR master device selects the largest value, 1.5, as the target frequency increase coefficient. Choosing the largest common frequency increase coefficient allows for the maximum improvement in line speed, thereby better meeting the needs of high-bandwidth services.

[0108] It should be noted that the execution order of determining the target frame parameter adjustment strategy and determining the target frequency increase coefficient is not restricted. The target frame parameter adjustment strategy can be determined first and then the target frequency increase coefficient can be determined first and then the target frame parameter adjustment strategy can be determined, or they can be executed simultaneously. The specific implementation method can be flexibly selected according to actual needs.

[0109] In this embodiment, the FTTR master device determines the target frame parameter adjustment strategy and the target frequency increase coefficient by taking the intersection of the frame parameter adjustment strategies and the intersection of the frequency increase coefficients of both parties. This ensures that the generated non-standard line rate information is supported by both the master and slave devices, avoiding communication interruptions or device disconnections caused by rate mismatch. Furthermore, selecting the largest identical frequency increase coefficient as the target frequency increase coefficient maximizes the rate increase and better meets the needs of high-bandwidth services.

[0110] In some embodiments, the non-standard line rate information includes a target frame parameter adjustment strategy and a target frequency increase coefficient; based on the non-standard line rate information, the line rate is switched synchronously with the FTTR slave device, including: based on the target frame parameter adjustment strategy and the target frequency increase coefficient, synchronously re-registering and re-authenticating with the FTTR slave device.

[0111] In this embodiment, the FTTR master device can carry a Scheduled Superframe Count (SFC) in the non-standard line rate information sent to the FTTR slave device. The Scheduled SFC is a 16-bit integer representing the value of the 16 least significant bits of the future SFC, used to indicate the specific time point at which the FTTR master and FTTR slave device perform rate switching. For example, if the current frame SFC is 10000, and the future SFC is set to 30000, then after 20000 × 0.125 = 2500ms, the SFC will become 30000, and the FTTR master and FTTR slave device will simultaneously perform rate switching at that time. Through the Scheduled SFC mechanism, it can be ensured that the FTTR master and FTTR slave device perform switching synchronously at the same time, avoiding communication interruptions caused by inconsistent switching times.

[0112] Re-registration and authentication constitute the rate switching process. Based on the target frame parameter adjustment strategy and target frequency increase factor, the FTTR master and FTTR slave simultaneously initiate re-registration and authentication at the time specified by the scheduling SFC. During this process, the switch from the standard line rate to the target non-standard line rate is completed. Specifically, following the FTTR standard registration and authentication process, the FTTR master and FTTR slave re-complete ranging, negotiation, and registration processes according to the non-standard line rate corresponding to the target frame parameter adjustment strategy and target frequency increase factor. Once registration and authentication are complete, the rate switching is considered complete, ensuring a stable and reliable communication link is established at the new rate.

[0113] Before re-registration and authentication, the FTTR master and FTTR slave devices can store the target frame parameter adjustment strategy and target frequency increase coefficient in a power-off storable storage medium. During re-registration and authentication, the target frame parameter adjustment strategy and target frequency increase coefficient are read from the storage medium for registration and authentication. This ensures that registration and authentication can be performed directly from the non-standard line rate on the next startup without the need for renegotiation and switching.

[0114] After synchronous re-registration and authentication are completed, the FTTR master device and the FTTR slave device will exchange service information at the non-standard line rate after the switch.

[0115] It should be noted that the switching method can be either dynamic switching (without restarting the device) or restart switching. In dynamic switching, the FTTR master and FTTR slave devices complete the rate switching and re-registration authentication without restarting, resulting in shorter switching time and a better user experience. In restart switching, the FTTR master and FTTR slave devices complete the rate switching and re-registration authentication by restarting, achieving a more thorough rate switching.

[0116] In this embodiment, the FTTR master device and the FTTR slave device achieve synchronous re-registration and authentication through scheduling SFC, and complete the rate switching through re-registration and authentication, establishing a stable and reliable communication link, ensuring the synchronization and reliability of rate switching, and realizing smooth rate upgrade.

[0117] This application also provides an information exchange method, applied to an FTTR slave device in an FTTR network, referring to... Figure 2 , Figure 2 This is a flowchart illustrating the information interaction method provided in the second aspect of this application.

[0118] like Figure 2 As shown, the method includes, but is not limited to, the following steps: Step S201: Receive non-standard line rate information sent by the FTTR master device based on the standard line rate. The non-standard line rate information is obtained based on the non-standard rate support information of the FTTR master device and the non-standard rate support information of the FTTR slave device. Step S202: Based on the standard line rate, send non-standard line rate confirmation information to the FTTR master device for non-standard line rate information; Step S203: Based on the non-standard line rate information, the line rate is switched synchronously with the FTTR master equipment to exchange information with the FTTR master equipment based on the non-standard line rate corresponding to the non-standard line rate information.

[0119] In step S201, the FTTR slave device is an extension device connected to the FTTR master device via an indoor fiber optic distributed network, distributed in various rooms to provide network coverage for each area. The standard line rate refers to the rate used when the FTTR slave device and the FTTR master device initially establish communication, such as 2.48832 Gbit / s as defined by the G.fin standard, 9.95328 Gbit / s as defined by the G.Xfin standard, or 49.7664 Gbit / s as defined by the G.HS-fin standard.

[0120] Non-standard line rate information is generated jointly by the FTTR master device and the FTTR slave device based on the master device's own non-standard rate support information and the slave device's non-standard rate support information. It serves as specific configuration information to instruct the slave device to perform rate switching. Non-standard rate support information refers to the rate configuration capabilities supported by the devices (including the FTTR master and slave devices) other than standard line rates, specifically including frame parameter adjustment strategies and frequency increase coefficients. Non-standard line rate information includes target frame parameter adjustment strategies and target frequency increase coefficients. The target frame parameter adjustment strategy is determined from frame parameter adjustment strategies supported by both the FTTR master and slave devices, and the target frequency increase coefficient is determined from frequency increase coefficients supported by both. Therefore, the non-standard line rate information received by the FTTR slave device based on the standard line rate is supported by both the master and slave devices, ensuring the feasibility of rate switching.

[0121] In practical applications, after determining that a non-standard rate switch is needed, the FTTR master device sends the non-standard line rate information to the FTTR slave device through the DLL layer management channel. The FTTR slave device receives this non-standard line rate information through the DLL layer management channel.

[0122] In step S202, after receiving the non-standard line rate information sent by the FTTR master device, the FTTR slave device first verifies the message. Specifically, the FTTR slave device performs a message integrity check (MIC check) on the received message to confirm that the message has not been tampered with during transmission and comes from a legitimate sender. The MIC check is calculated using the default PLOAM_IK in the case of broadcast messages, and using a shared PLOAM_IK specifically derived by the FTTR slave device in the case of directed messages.

[0123] If the verification passes, the FTTR slave device extracts the target frame parameter adjustment strategy and target frequency increase coefficient from the non-standard line rate information, preparing to switch to the target non-standard line rate. After completing the rate configuration, the FTTR slave device sends an acknowledgment message to the FTTR master device based on the standard line rate, informing the FTTR master device that it has successfully received and is ready to execute the rate configuration.

[0124] The above confirmation mechanism ensures reliable transmission of rate switching commands and correct responses from slave devices, avoiding rate switching failures caused by message loss or verification failures.

[0125] In step S203, after sending the confirmation information, the FTTR slave device adjusts its strategy and target frequency increase coefficient according to the target frame parameters in the non-standard line rate information, and waits to synchronize with the FTTR master device to perform line rate handover. When the non-standard line rate information contains a Scheduled Superframe Count (SFC), the FTTR slave device will synchronize with the FTTR master device to perform handover if it reaches the time specified by the SFC at the current time. Through the SFC scheduling mechanism, the FTTR master device and the FTTR slave device are guaranteed to perform handover synchronously at the same time, avoiding communication interruptions caused by inconsistent handover times.

[0126] When a switchover is required, the FTTR master and FTTR slave devices re-register and authenticate based on the non-standard line rate. This re-registration and authentication is the rate switching process, and service information is exchanged using this non-standard line rate, such as high-throughput data downloads or low-latency audio and video calls. Simultaneously, the FTTR master and FTTR slave devices store the non-standard line rate in a power-off storable storage medium to ensure that registration and authentication can be performed directly from this non-standard line rate upon the next startup, without the need for renegotiation and switchover.

[0127] In this embodiment, the FTTR slave device receives non-standard line rate information sent by the FTTR master device based on the standard line rate. This non-standard line rate information is generated by the master device according to the non-standard rate support information of both parties, enabling the slave device to obtain a non-standard rate configuration that matches its own capabilities. By replying with confirmation information to the master device, reliable transmission of rate switching commands and correct response from the slave device are ensured, avoiding switching failures caused by message loss or verification failures. By synchronously switching line rates with the master device based on the non-standard line rate information and exchanging service information at the switched non-standard line rate, it is ensured that the master and slave devices perform the switching synchronously at the same time, avoiding communication interruptions or data loss caused by inconsistent switching times. This achieves reliable deployment and smooth upgrade of non-standard line rates, ensuring service continuity.

[0128] In some embodiments, before receiving non-standard line rate information sent by the FTTR master device based on the standard line rate, the method further includes: sending service type information to the FTTR master device in response to a service type request sent by the FTTR master device.

[0129] In this embodiment, the service type information is used to characterize the type of service currently carried by the FTTR slave device, which may include, but is not limited to, high-throughput services, low-latency services, or ordinary services. The FTTR slave device can collect the service type information it is currently carrying through a built-in SoC chip, service identification module, or AI module. The specific identification method can be flexibly selected according to the actual application scenario.

[0130] After receiving a service type request from the FTTR master device, the FTTR slave device reports the collected service type information to the FTTR master device through the DLL layer management channel.

[0131] As an optional implementation, the FTTR slave device can also proactively report its own service type information to the FTTR master device before receiving the service type request sent by the FTTR master device, without waiting for the master device's request, thereby reducing the signaling interaction process.

[0132] In this embodiment, the FTTR slave device reports service type information in response to the master device's service type request, providing a data basis for the master device's rate switching decision, enabling rate switching to be triggered according to actual service needs and avoiding blind switching.

[0133] In some embodiments, before receiving non-standard line rate information sent by the FTTR master device based on the standard line rate, the method further includes: in response to receiving a non-standard rate query message sent by the FTTR master device, sending a non-standard rate capability reporting message to the FTTR master device, wherein the non-standard rate capability reporting message contains non-standard rate support information of the FTTR slave device, and the non-standard rate query message includes at least one of a standard or custom F-PLOAM message, a standard or custom FMCI message, and uplink / downlink frame indication bits of the embedded OAM management channel.

[0134] In this embodiment, the non-standard rate query message is used to request the FTTR slave device to report its non-standard rate support information. The FTTR master device and the FTTR slave device transmit messages through a DLL layer management channel, through which the non-standard rate query message is sent. The non-standard rate query message can reuse or extend the message format defined in the standard, specifically including at least one of the following: standard or custom F-PLOAM message, standard or custom FMCI message (i.e., message from the FMCC management channel), and uplink / downlink frame indication bits of the embedded OAM management channel. The FTTR slave device receives the non-standard rate query message through the DLL layer management channel.

[0135] As an optional implementation, non-standard rate query messages can be implemented by customizing reserved fields in F-PLOAM messages, such as defining specific message type IDs and opcodes in the F-PLOAM message. Alternatively, it can be implemented by extending custom fields in FMCI messages, or by utilizing reserved indicator bits in uplink and downlink frames in the embedded OAM management channel to carry rate query information. All of the above methods can achieve the transmission of non-standard rate query messages, and the FTTR master device can choose the appropriate method according to actual needs.

[0136] After receiving a non-standard rate query message from the FTTR master device, the FTTR slave device performs addressing based on the SFU-ID, vendor ID, and VSSN to determine whether the query message is directed to its own device. If it is determined to be directed to its own device, the slave device sends its non-standard rate support information to the FTTR master device via a non-standard rate capability reporting message. The non-standard rate support information includes frame parameter adjustment strategies and frequency increase coefficients, which can be found in the relevant descriptions in the foregoing embodiments and will not be repeated here.

[0137] As an optional implementation, FTTR slave devices can also proactively report non-standard rate support information to the FTTR master device without waiting for a query from the master device, thereby reducing signaling interaction processes.

[0138] In some embodiments, the non-standard rate support information includes a frame parameter adjustment strategy and a frequency increase coefficient; the frequency increase coefficient is a proportional coefficient of the standard line rate supported by the device, and the frequency increase coefficient is any number greater than zero; the frame parameter adjustment strategy is an adjustment strategy for rate-related parameters supported by the device, and the rate-related parameters include at least one of frame length, bandwidth granularity, frame rate, and frame period; the non-standard line rate information includes a target frame parameter adjustment strategy and a target frequency increase coefficient, wherein the frame parameter adjustment strategy in the non-standard rate support information of the FTTR master device and the frame parameter adjustment strategy in the non-standard rate support information of the FTTR slave device both include the target frame parameter adjustment strategy, and the frequency increase coefficient in the non-standard rate support information of the FTTR master device and the frequency increase coefficient in the non-standard rate support information of the FTTR slave device both include the target frequency increase coefficient.

[0139] For details regarding the frame parameter adjustment strategy and frequency boosting coefficient in this embodiment, please refer to the above embodiment; they will not be repeated here.

[0140] In some embodiments, the frame parameter adjustment strategy includes at least one of the following: Multiply the current frame rate by the target frequency boosting factor, keep the current frame length and current bandwidth granularity unchanged, and divide the current frame period by the target frequency boosting factor; The current frame rate is multiplied by the target frequency increase factor, the current frame period remains unchanged, the current frame length is multiplied by the target frequency increase factor, and the current bandwidth granularity is multiplied by the target frequency increase factor.

[0141] For details on the specific frame parameter adjustment strategy in this embodiment, please refer to the above embodiment; it will not be repeated here.

[0142] In some embodiments, the non-standard line rate information includes the target frame parameter adjustment strategy and the target frequency increase coefficient; based on the non-standard line rate information, the line rate is switched synchronously with the FTTR master equipment, including: based on the target frame parameter adjustment strategy and the target frequency increase coefficient, synchronously re-registering and authenticating with the FTTR master equipment.

[0143] In this embodiment, the FTTR master device can carry a Scheduled Superframe Count (SFC) in the non-standard line rate information sent to the FTTR slave device. The Scheduled SFC is a 16-bit integer representing the value of the 16 least significant bits of the future SFC, used to indicate the specific time point at which the FTTR master and FTTR slave device perform rate switching. For example, if the current frame SFC is 10000, and the future SFC is set to 30000, then after 20000 × 0.125 = 2500ms, the SFC will become 30000, and the FTTR master and FTTR slave device will simultaneously perform rate switching at that time. Through the Scheduled SFC mechanism, it can be ensured that the FTTR master and FTTR slave device perform switching synchronously at the same time, avoiding communication interruptions caused by inconsistent switching times.

[0144] Re-registration and authentication constitute the rate switching process. Based on the target frame parameter adjustment strategy and target frequency increase factor, the FTTR master and FTTR slave simultaneously initiate re-registration and authentication at the time specified by the scheduling SFC. During this process, the switch from the standard line rate to the target non-standard line rate is completed. Specifically, following the FTTR standard registration and authentication process, the FTTR master and FTTR slave re-complete ranging, negotiation, and registration processes according to the non-standard line rate corresponding to the target frame parameter adjustment strategy and target frequency increase factor. Once registration and authentication are complete, the rate switching is considered complete, ensuring a stable and reliable communication link is established at the new rate.

[0145] Before re-registration and authentication, the FTTR master and FTTR slave devices store the target frame parameter adjustment strategy and target frequency increase coefficient in a power-off storable storage medium. During re-registration and authentication, the target frame parameter adjustment strategy and target frequency increase coefficient are read from the storage medium for registration and authentication. This ensures that registration and authentication can be performed directly from the non-standard line rate on the next startup without the need for renegotiation and switching.

[0146] After synchronous re-registration and authentication are completed, the FTTR master device and the FTTR slave device will exchange service information at the non-standard line rate after the switch.

[0147] It should be noted that the switching method can be either dynamic switching (without restarting the device) or restart switching. In dynamic switching, the FTTR master and FTTR slave devices complete the rate switching and re-registration authentication without restarting, resulting in shorter switching time and a better user experience. In restart switching, the FTTR master and FTTR slave devices complete the rate switching and re-registration authentication by restarting, achieving a more thorough rate switching.

[0148] In this embodiment, the FTTR master device and the FTTR slave device achieve synchronous re-registration and authentication through scheduling SFC, and complete the rate switching through re-registration and authentication, establishing a stable and reliable communication link, ensuring the synchronization and reliability of rate switching, and realizing smooth rate upgrade.

[0149] In some embodiments, based on the standard line rate, sending non-standard line rate confirmation information to the FTTR master device includes: in response to receiving the non-standard line rate information, performing message integrity verification on the non-standard line rate information; if the verification passes, configuring the rate of the FTTR slave device based on the non-standard line rate information, and sending an confirmation message to the FTTR master device.

[0150] In this embodiment, after the FTTR slave device receives the non-standard line rate information sent by the FTTR master device, it first performs an integrity check on the message. The message integrity check is a MIC check, used to confirm that the message has not been tampered with during transmission and comes from a legitimate sender.

[0151] Specifically, MIC verification uses the default PLOAM_IK for broadcast messages and a shared PLOAM_IK derived specifically from the FTTR slave device for directed messages. MIC verification prevents unauthorized devices from forging messages to deceive the FTTR slave device, thus ensuring communication security.

[0152] If the verification passes, the FTTR slave device extracts the target frame parameter adjustment strategy and target frequency increase coefficient from the non-standard line rate information, and configures its own rate accordingly. Specifically, the FTTR slave device configures its own frame parameters according to the target frame parameter adjustment strategy and target frequency increase coefficient, preparing to switch to the target non-standard line rate.

[0153] After completing the rate configuration, the FTTR slave device sends an acknowledgment message to the FTTR master device to inform the master device that it has successfully received and completed the rate configuration and can perform subsequent synchronization handover operations.

[0154] The above verification mechanism ensures the legality and integrity of rate control commands; the confirmation mechanism after configuration ensures reliable transmission of rate switching commands and correct response from slave devices.

[0155] In some embodiments, the FTTR slave device and the FTTR master device transmit messages through a DLL layer management channel; the DLL layer management channel includes any one of the F-PLOAM management channel, FMCC management channel, embedded OAM management channel, or WMCC management channel.

[0156] In this embodiment, refer to Figure 3 , Figure 3 This is a schematic diagram of the DLL layer management channel.

[0157] Non-standard rate capability negotiation and control distribution between FTTR master and FTTR slave devices can be achieved through message transmission via the DLL layer management channel. For example... Figure 3 As shown, the DLL layer management channel includes any one of the following: F-PLOAM management channel, FMCC management channel, embedded OAM management channel, or WMCC management channel.

[0158] Specifically, the F-PLOAM management channel is the physical layer OAM channel for indoor fiber optic networks, used to transmit physical layer operation, management, and maintenance messages. FTTR master and FTTR slave devices can use this channel to transmit non-standard rate query messages, non-standard rate capability reporting messages, and non-standard line rate information. The FMCC management channel is the fiber optic management and control channel, used by FTTR master and FTTR slave devices to transmit FMCI messages, enabling the querying, reporting, and distribution of non-standard rate capabilities and rate control messages. The embedded OAM management channel is an OAM channel embedded in data frames, allowing FTTR master and FTTR slave devices to use indicator bits in uplink and downlink frames to carry non-standard rate control information. The WMCC management channel is the WLAN management and control channel, which can also be used to transmit non-standard rate negotiation and control messages. All of the above channels are DLL layer management channels defined in the FTTR standard. Signaling interactions between FTTR master and FTTR slave devices, such as non-standard rate capability negotiation, service type acquisition, distribution of non-standard line rate information, and confirmation message transmission, can be transmitted through any of these channels.

[0159] Through the aforementioned DLL layer management channel, the FTTR master device and the FTTR slave device can complete the entire signaling interaction process, including non-standard rate capability negotiation, service type collection, non-standard line rate information distribution, and confirmation message reply, without the need to define additional physical channels or interfaces, thus exhibiting good compatibility.

[0160] This application also provides a rate adjustment method, referring to... Figure 4 , Figure 4 This is a flowchart illustrating a rate adjustment method provided in a third aspect embodiment of this application.

[0161] like Figure 4 As shown, the method includes, but is not limited to, the following steps: Step S401: Obtain the frame parameter adjustment strategy and frequency boosting coefficient; Step S402: Adjust the standard line rate between at least two FTTR devices according to the frame parameter adjustment strategy and frequency increase coefficient to obtain the non-standard line rate.

[0162] In step S401, the FTTR device includes at least an FTTR master device and an FTTR slave device. The frame parameter adjustment strategy and frequency boosting coefficient can be obtained by the FTTR device in various ways. As one implementation, the FTTR device can read pre-configured frame parameter adjustment strategies and frequency boosting coefficients from local storage media. As another implementation, the FTTR device can receive frame parameter adjustment strategies and frequency boosting coefficients sent by other devices (such as the FTTR master device or network management platform) through the DLL layer management channel. As yet another implementation, the FTTR device can receive configuration commands input by the user through a user management interface or command-line interface, and obtain the frame parameter adjustment strategy and frequency boosting coefficients according to the configuration commands. This application embodiment does not specifically limit the acquisition method.

[0163] In step S402, the FTTR device adjusts the standard line rate according to the frame parameter adjustment strategy and the frequency increase factor. Specifically, the FTTR device first determines the target frame rate by multiplying the standard line rate by the frequency increase factor, and then adjusts the frame parameters according to the frame parameter adjustment strategy to match the frame parameters with the target frame rate, thereby obtaining the non-standard line rate.

[0164] In this embodiment, the FTTR device can adjust the standard line rate according to the frame parameter adjustment strategy and frequency boosting coefficient to obtain a non-standard line rate, thereby realizing the flexible generation of non-standard line rates and solving the problem that the existing FTTR standard only supports a limited number of fixed line rates and cannot flexibly generate non-standard line rates.

[0165] In some embodiments, the frequency increase factor is a proportionality coefficient of the standard line rate, and the frequency increase factor is any number greater than zero; the frame parameter adjustment strategy is an adjustment strategy for rate-related parameters supported by the FTTR device, and the rate-related parameters include at least one of frame length, bandwidth granularity, frame rate, and frame period.

[0166] In this embodiment, the frequency increase factor is a proportional coefficient of the standard line rate, and the frequency increase factor is any number greater than zero. For example, the frequency increase factor can take typical values ​​such as 1.25, 1.25587, 1.31615, 1.40657, 1.5, 1.5625, 2, 2.5, etc., but is not limited to these. The frame parameter adjustment strategy is the frame parameter adjustment strategy supported by the FTTR device. The frame parameters include frame length, bandwidth granularity, frame rate, and frame period.

[0167] The FTTR device adjusts the standard line rate based on the acquired frame parameter adjustment strategy and frequency boosting factor. The standard line rate refers to the rate used by the FTTR device when initially establishing communication, such as 2.48832 Gbit / s as defined by the G.fin standard, 9.95328 Gbit / s as defined by the G.Xfin standard, or 49.7664 Gbit / s as defined by the G.HS-fin standard.

[0168] Frame parameter adjustment strategies include at least one of the following: Strategy 1: Multiply the current frame rate by the frequency increase factor, keep the current frame length and bandwidth granularity unchanged, and divide the current frame period by the frequency increase factor. This strategy increases the frame rate by shortening the frame period and is suitable for latency-sensitive business scenarios.

[0169] Strategy 2: Multiply the current frame rate by a frequency increase factor, keep the current frame period unchanged, multiply the current frame length by the frequency increase factor, and multiply the current bandwidth granularity by the frequency increase factor. This strategy increases the frame rate by increasing the frame length and bandwidth granularity, and is suitable for business scenarios with high throughput requirements.

[0170] It should be noted that in the two strategies mentioned above, the FTTR device first multiplies the current frame rate by the frequency boosting factor to complete the frequency boosting operation and reach the target frame rate. Then, it synchronously adjusts frame parameters such as frame length, bandwidth granularity, and frame period to match the frame parameters with the target frame rate.

[0171] As one implementation method, FTTR equipment can employ a strategy to adjust the standard line rate. For example, based on the G.fin standard, the standard line rate is 2.48832 Gbit / s, the frame period is 125 µs, the frame length is 38880 bytes, and the bandwidth granularity is 2 bytes. When the frequency increase factor n=1.25, the FTTR equipment first multiplies the frame rate by 1.25 to determine the target frame rate as 3.1104 Gbit / s. Then, keeping the frame length and bandwidth granularity unchanged, it changes the frame period from 125 µs divided by 1.25 to 100 µs, thus obtaining the non-standard line rate of 3.1104 Gbit / s.

[0172] As another implementation method, the FTTR device can use Strategy 2 to adjust the standard line rate. Also based on the G.fin standard, when the frequency increase factor n=1.25, the FTTR device first multiplies the frame rate by 1.25 to determine the target frame rate as 3.1104 Gbit / s. Then, keeping the frame period unchanged at 125us, the frame length is multiplied by 1.25 to become 48600 bytes, and the bandwidth granularity is multiplied by 1.25 to become 2.5 bytes, thus obtaining the non-standard line rate of 3.1104 Gbit / s.

[0173] In this way, the FTTR equipment adjusts the standard line rate according to the frame parameter adjustment strategy and the frequency increase coefficient to obtain the non-standard line rate, thus realizing the flexible generation of the non-standard line rate.

[0174] In some embodiments, the frame parameter adjustment strategy includes at least one of the following: Multiply the current frame rate by the frequency boosting factor, keep the current frame length and current bandwidth granularity unchanged, and divide the current frame period by the frequency boosting factor; The current frame rate is multiplied by the frequency boosting factor, the current frame period remains unchanged, the current frame length is multiplied by the frequency boosting factor, and the current bandwidth granularity is multiplied by the frequency boosting factor.

[0175] In this embodiment, under strategy one, the FTTR device first performs a frequency boosting operation by multiplying the current frame rate by a boosting factor to reach the target frame rate. Then, keeping the current frame length and bandwidth granularity unchanged, it divides the current frame period by the boosting factor to match the frame parameters with the target frame rate. Because the frame period is shortened, the data frame transmission interval is reduced, effectively lowering data transmission latency.

[0176] In Strategy 2, the FTTR device first performs a frequency boosting operation by multiplying the current frame rate by a boosting factor to reach the target frame rate. Then, keeping the current frame period unchanged, it multiplies the current frame length and current bandwidth granularity by the boosting factor to match the frame parameters with the target frame rate. Because the frame length is increased, each frame can carry more data, effectively improving data transmission throughput.

[0177] The technical solution of the present invention will be further described in detail below with reference to the accompanying drawings.

[0178] The following is passed Figures 5 to 10 The six specific implementation methods shown illustrate the application of the frame parameter adjustment strategy. In other words, the following embodiments are used to illustrate how, after determining the target frame parameter adjustment strategy and the target frequency increase coefficient, the FTTR master device and the FTTR slave device adjust the frame parameters based on the target frame parameter adjustment strategy and the target frequency increase coefficient to achieve the switching of non-standard line rates.

[0179] It should be noted that the following embodiments illustrate implementation methods for multi-rate FTTR systems based on different standards (G.fin, G.Xfin, G.HS-fin) and different frame parameter adjustment methods (Method A: frame period divided by n, Method B: frame length and bandwidth granularity multiplied by n). In each embodiment, n is the frequency boosting coefficient, and n is any number greater than zero.

[0180] Example 1 like Figure 5As shown, in the first implementation, the frame format is consistent with the G.fin standard. The downlink frame consists of three parts: the downlink physical layer header (DS PHY Header), the downlink physical coding sublayer header (DS PCS Header), and the downlink physical coding sublayer payload (DS PCS payload). The downlink line rate is 2.48832×n Gbit / s, the downlink frame period is 125 / nus, the downlink frame length is 38880 bytes, and the bandwidth granularity is 2 bytes. The uplink S-FTR burst consists of two parts: the uplink physical layer header (USPHY Header) and the uplink physical layer payload (US PHY payload). The uplink line rate is 2.48832×n Gbit / s, and the uplink frame period is 125 / n us. Here, n is the frequency boosting factor.

[0181] When n=1, the line rate, frame period, frame length, bandwidth granularity, and other parameters are completely consistent with the G.fin standard. By increasing the frequency, n can also be set to typical values ​​such as 1.25, 1.25587, 1.31615, 1.40657, 1.5, 1.5625, 2, and 2.5, thereby achieving non-standard line rates such as 3.1104 Gbit / s, 3.125 Gbit / s, 3.275 Gbit / s, 3.5 Gbit / s, 3.73248 Gbit / s, 3.888 Gbit / s, 4.97664 Gbit / s, and 6.2208 Gbit / s. Simultaneously, the frame period changes accordingly to 100µs, 99.5µs, 95µs, 88.9µs, 83.3µs, 80µs, 62.5µs, and 50µs to meet the demands of high-bandwidth, low-latency services.

[0182] Example 2 like Figure 6 As shown, in the second implementation, the frame format is consistent with the G.Xfin standard. The downlink frame consists of three parts: the downlink X physical layer header (DS XPHY Header), the downlink X physical coding sublayer header (DS XPCS Header), and the downlink X physical coding sublayer payload (DS XPCS payload). The downlink line rate is 9.95328×n Gbit / s, the downlink frame period is 125 / n us, the downlink frame length is 155520 bytes, and the bandwidth granularity is 16 bytes. The uplink S-FTR burst consists of two parts: the uplink X physical layer header (US XPHY Header) and the uplink X physical layer payload (US XPHY payload). The uplink line rate is 9.95328×n Gbit / s, and the uplink frame period is 125 / n us. Here, n is the frequency boosting factor.

[0183] It should be noted that the downlink frame in this embodiment also includes control fields such as Physical Synchronization (PSync), Superframe Count (SFC) structure, Optical Channel (OC) structure, Downlink Payload Length Header (HLend), Bandwidth Map (BWmap), and Downlink Physical Layer OAM (F-PLOAMd). The definitions of the above fields are consistent with the G.Xfin standard.

[0184] When n=1, the line rate, frame period, frame length, and bandwidth granularity are completely consistent with the G.Xfin standard. By increasing the frequency, n can also be 1.25, 1.25587, 1.31615, 1.40657, 1.5, 1.5625, 2, 2.5, etc., thus achieving non-standard line rates such as 12.4416 Gbit / s, 12.5 Gbit / s, 13.1 Gbit / s, 14 Gbit / s, 14.92992 Gbit / s, 15.552 Gbit / s, 19.90656 Gbit / s, and 24.8832 Gbit / s. Simultaneously, the frame period changes accordingly to 100us, 99.5us, 95us, 88.9us, 83.3us, 80us, 62.5us, 50us, etc., to meet the requirements of high-bandwidth, low-latency services.

[0185] Example 3 like Figure 7 As shown, in the third implementation, the frame format is consistent with the G.HS-fin standard. The downlink frame consists of three parts: the downlink high-speed physical layer header (DS HS-PHY Header), the downlink high-speed physical coding sublayer header (DS HS-PCS Header), and the downlink high-speed physical coding sublayer payload (DS HS-PCS payload). The downlink line rate is 49.7664 × n Gbit / s, the downlink frame period is 125 / n us, the downlink frame length is 777600 bytes, and the bandwidth granularity is 64 bytes. The uplink S-FTR burst consists of two parts: the uplink high-speed physical layer header (US HS-PHY Header) and the uplink high-speed physical layer payload (US HS-PHY payload). The uplink line rate is 49.7664 × n Gbit / s, and the uplink frame period is 125 / n us. Here, n is the frequency boosting factor.

[0186] It should be noted that the downlink frame in this embodiment also includes control fields such as Physical Synchronization (PSync), Superframe Count (SFC) structure, Optical Channel (OC) structure, Downlink Payload Length Header (H-Lend), Bandwidth Map (BWmap), and Downlink Physical Layer OAM (F-PLOAMd). The definitions of the above fields are consistent with the G.HS-fin standard.

[0187] When n=1, the line rate, frame period, frame length, bandwidth granularity, and standard G.HS-fin are completely consistent. By increasing the frequency, n can also be 1.25, 1.25587, 1.31615, 1.40657, 1.5, 1.5625, 2, 2.5, etc., achieving non-standard line rates such as 62.208 Gbit / s, 62.5 Gbit / s, 65.5 Gbit / s, 70 Gbit / s, 74.6496 Gbit / s, 77.76 Gbit / s, 99.5328 Gbit / s, and 124.416 Gbit / s. Simultaneously, the frame period changes to 100µs, 99.5µs, 95µs, 88.9µs, 83.3µs, 80µs, 62.5µs, and 50µs, respectively, to meet the requirements of high-bandwidth, low-latency services.

[0188] Example 4 like Figure 8 As shown, in the fourth implementation, the frame format is consistent with the G.fin standard. The downlink frame consists of three parts: the downlink physical layer header (DS PHY Header), the downlink physical coding sublayer header (DS PCS Header), and the downlink physical coding sublayer payload (DS PCS payload). The downlink line rate is 2.48832×n Gbit / s, the downlink frame period is 125µs, the downlink frame length is 38880×n bytes, and the bandwidth granularity is 2×n bytes. The uplink S-FTR burst consists of two parts: the uplink physical layer header (US PHY Header) and the uplink physical layer payload (US PHY payload). The uplink line rate is 2.48832×n Gbit / s, and the uplink frame period is 125µs. Here, n is the frequency boosting factor.

[0189] It should be noted that the downlink frame in this embodiment also includes control fields such as Physical Synchronization (PSync), Identification (Ident), Downlink Physical Layer OAM (F-PLOAMd), Bit Interleaving Parity (BIP), Downlink Payload Length (Plend), and Uplink Bandwidth Map (Upstream BWmap). The definitions of the above fields are consistent with the G.fin standard.

[0190] When n=1, the line rate, frame period, frame length, and bandwidth granularity are completely consistent with the G.fin standard. By increasing the frequency, n can also be typical values ​​such as 1.25, 1.5, 1.5625, 2, and 2.5, thereby achieving non-standard line rates such as 3.1104 Gbit / s, 3.73248 Gbit / s, 3.888 Gbit / s, 4.97664 Gbit / s, and 6.2208 Gbit / s. Simultaneously, the frame lengths correspondingly become 48600 bytes, 58320 bytes, 60750 bytes, 77760 bytes, and 97200 bytes, and the bandwidth granularity correspondingly becomes 2.5 bytes, 3 bytes, 3.125 bytes, 4 bytes, and 5 bytes, to meet the demands of high-bandwidth services.

[0191] Example 5 like Figure 9 As shown, in the fifth implementation, the frame format is consistent with the G.Xfin standard. The downlink frame consists of three parts: the downlink X physical layer header (DS XPHY Header), the downlink X physical coding sublayer header (DS XPCS Header), and the downlink X physical coding sublayer payload (DS XPCS payload). The downlink line rate is 9.95328×n Gbit / s, the downlink frame period is 125 µs, the downlink frame length is 155520×n bytes, and the bandwidth granularity is 16×n bytes. The uplink S-FTR burst consists of two parts: the uplink X physical layer header (US XPHY Header) and the uplink X physical layer payload (US XPHY payload). The uplink line rate is 9.95328×n Gbit / s, and the uplink frame period is 125 µs. Here, n is the frequency boosting factor.

[0192] It should be noted that the downlink frame in this embodiment also includes control fields such as Physical Synchronization (PSync), Superframe Count (SFC) structure, Optical Channel (OC) structure, Downlink Payload Length Header (HLend), Bandwidth Map (BWmap), and Downlink Physical Layer OAM (F-PLOAMd). The definitions of the above fields are consistent with the G.Xfin standard.

[0193] When n=1, the line rate, frame period, frame length, and bandwidth granularity are completely consistent with the G.Xfin standard. By increasing the frequency, n can also be typical values ​​such as 1.25, 1.5, 1.5625, 2, and 2.5, thereby achieving non-standard line rates such as 12.4416 Gbit / s, 14.92992 Gbit / s, 15.552 Gbit / s, 19.90656 Gbit / s, and 24.8832 Gbit / s. Simultaneously, the frame lengths correspondingly become 194400 bytes, 233280 bytes, 243000 bytes, 311040 bytes, and 388800 bytes, and the bandwidth granularity correspondingly becomes 20 bytes, 24 bytes, 25 bytes, 32 bytes, and 40 bytes, to meet the demands of high-bandwidth services.

[0194] Example 6 like Figure 10 As shown, in the sixth implementation, the frame format is consistent with the G.HS-fin standard. The downlink frame consists of three parts: the downlink high-speed physical layer header (DS HS-PHY Header), the downlink high-speed physical coding sublayer header (DS HS-PCS Header), and the downlink high-speed physical coding sublayer payload (DS HS-PCS payload). The downlink line rate is 49.7664 × n Gbit / s, the downlink frame period is 125 μs, the downlink frame length is 777600 × n bytes, and the bandwidth granularity is 64 × n bytes. The uplink S-FTR burst consists of two parts: the uplink high-speed physical layer header (US HS-PHY Header) and the uplink high-speed physical layer payload (US HS-PHY payload). The uplink line rate is 49.7664 × n Gbit / s, and the uplink frame period is 125 μs. Here, n is the frequency boosting factor.

[0195] It should be noted that the downlink frame in this embodiment also includes control fields such as Physical Synchronization (PSync), Superframe Count (SFC) structure, Optical Channel (OC) structure, Downlink Payload Length Header (HLend), Bandwidth Map (BWmap), and Downlink Physical Layer OAM (F-PLOAMd). The definitions of the above fields are consistent with the G.HS-fin standard.

[0196] When n=1, the line rate, frame period, frame length, bandwidth granularity, and standard G.HS-fin are completely consistent. By increasing the frequency, n can also be a typical value such as 1.25, 1.5, 1.5625, 2, or 2.5, thus achieving non-standard line rates such as 62.208 Gbit / s, 74.6496 Gbit / s, 77.76 Gbit / s, 99.5328 Gbit / s, and 124.416 Gbit / s. Simultaneously, the frame lengths become 972,000 bytes, 1,166,400 bytes, 1,215,000 bytes, 1,555,200 bytes, and 1,944,000 bytes, respectively, and the bandwidth granularity becomes 80 bytes, 96 bytes, 100 bytes, 128 bytes, and 160 bytes, respectively, to meet the demands of high-bandwidth services.

[0197] To more intuitively illustrate the specific changes in frame parameters under different frequency boosting coefficients, Tables 4 to 6 below summarize and explain the non-standard line rate, frame period, frame length, and bandwidth granularity of the G.fin, G.Xfin, and G.HS-fin standards under different frequency boosting coefficients.

[0198] Table 4. Comparison of Typical Non-Standard Line Rate Parameters for G.fin Standard

[0199] Table 5: Comparison of Typical Non-Standard Line Rate Parameters for G.Xfin Standard

[0200] Table 6. Comparison of Typical Non-Standard Line Rate Parameters for G.HS-fin Standard

[0201] As can be seen from Tables 4 to 6, without significantly altering the existing standard frame format, various non-standard line rates can be flexibly generated by introducing a frequency boosting coefficient n and combining it with two frame parameter adjustment methods.

[0202] The following combination Figure 11 The following is an exemplary description of the rate control module of the FTTR network in the embodiments of this application. Figure 11 The rate control module shown can be applied to the interaction methods of the above embodiments to realize rate capability negotiation, service type collection, rate control issuance, and rate control execution.

[0203] like Figure 11As shown, the FTTR network in this embodiment integrates a rate capability negotiation module, a service type acquisition module, a rate control distribution module, and a rate control execution module. By performing rate control through the above four modules, the rate of the FTTR master device and the FTTR slave device can be smoothly upgraded to meet the requirements of high bandwidth and low latency services.

[0204] Specifically, the rate capability negotiation module is deployed on both the FTTR master and FTTR slave devices to facilitate the interaction and negotiation of rate capabilities during the device registration and authentication process. The FTTR master device uses this module to send non-standard rate query messages to the FTTR slave devices, while the FTTR slave devices use this module to report their supported set of frame parameter adjustment strategies and frequency boosting coefficients to the FTTR master device, thereby enabling mutual awareness of rate capabilities between the master and slave devices.

[0205] The service type acquisition module is deployed on both the FTTR master and FTTR slave devices to collect and report the service type information currently carried by the FTTR slave devices. The FTTR slave devices identify the current service type (such as high-throughput service or low-latency service) through built-in SoC chips, service identification modules, or AI modules, and report it to the FTTR master device through this module, providing a service-level data foundation for rate switching decisions.

[0206] The rate control distribution module is deployed on the FTTR master device. It is used to make rate switching decisions based on the rate capability negotiation results and service type collection results, and to distribute non-standard line rate information. Specifically, this module performs an intersection judgment based on the non-standard rate support information of the FTTR master device and the FTTR slave device. It determines the target frame parameter adjustment strategy and target frequency increase coefficient from the frame parameter adjustment strategies and frequency increase coefficients supported by both parties, generates non-standard line rate information, and distributes it to the FTTR slave device through the DLL layer management channel.

[0207] The rate control execution module is deployed on both the FTTR master and slave devices. It synchronously performs rate switching at the time specified by the scheduling SFC, re-registering and authenticating at the new non-standard line rate, and then exchanging service information using this new rate. Simultaneously, this module stores the target frame parameter adjustment strategy and target frequency increase coefficient in a power-off storable storage medium to ensure that the device can directly perform registration and authentication from the new non-standard line rate upon the next startup.

[0208] like Figure 12 As shown, taking three FTTR slave devices (SFU1, SFU2, SFU3) connected to the FTTR master device as an example, the signaling interaction flow of the information interaction method provided in this application embodiment is illustrated.

[0209] Specifically, each FTTR slave device first registers and authenticates using the standard line rate. During the registration and authentication process, the FTTR master device negotiates rate capabilities with each FTTR slave device. Specifically, the FTTR master device queries each FTTR slave device for its non-standard rate support information via a rate query message, and each FTTR slave device reports its supported frame parameter adjustment strategies and frequency increase coefficients to the FTTR master device via a rate capability reporting message.

[0210] After completing the rate capability negotiation, the FTTR master device sends a service type request to each FTTR slave device. Each FTTR slave device collects the service type information it is currently carrying through its built-in SoC chip, service identification module or AI module, and reports the service type information to the FTTR master device through a service type reporting message.

[0211] The FTTR master device makes rate switching decisions based on its own and each FTTR slave device's non-standard rate support information and service type information. If it determines that rate switching is permitted, it sends rate control messages to each FTTR slave device. The rate control message includes the target frame parameter adjustment strategy, the target frequency increase factor, and the scheduling SFC.

[0212] After receiving the rate control message, each FTTR slave device performs an integrity check on the message. If the check passes, it sets its own rate configuration according to the rate control message and replies with an acknowledgment message to the FTTR master device.

[0213] When the time specified by the scheduling SFC arrives, the FTTR master device and each FTTR slave device synchronously switch to the non-standard line rate corresponding to the target frame parameter adjustment strategy and the target frequency increase coefficient, and transmit data at the switched non-standard line rate to achieve a smooth upgrade of the FTTR master device and FTTR slave device rates.

[0214] It should be noted that SFU1, SFU2, and SFU3 in this embodiment use the same rate when switching rates.

[0215] Figure 13 This is a schematic diagram of the structure of an FTTR device provided in one embodiment of this application. Figure 13 As shown, the FTTR device 1300 includes a memory and a processor. The number of memories and processors can be one or more. Figure 13 Taking a memory 1301 and a processor 1302 as an example; the memory 1301 and processor 1302 in the network device can be connected via a bus or other means. Figure 13 Taking the example of a connection between China and Israel via a bus.

[0216] The memory 1301, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the methods provided in any embodiment of this application. The processor 1302 implements the information interaction method provided in any of the above embodiments by running the software programs, instructions, and modules stored in the memory 1301.

[0217] Memory 1301 may primarily include a program storage area and a data storage area, wherein the program storage area may store the operating system and application programs required for at least one function. Furthermore, memory 1301 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, memory 1301 further includes memory remotely located relative to processor 1302, and these remote memories can be connected to the device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0218] One embodiment of this application also provides a computer-readable storage medium storing computer-executable instructions for performing information interaction methods or rate adjustment methods as provided in any embodiment of this application.

[0219] An embodiment of this application also provides a computer program product, including a computer program or computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer program or computer instructions from the computer-readable storage medium and executes the computer program or computer instructions, causing the computer device to perform an information interaction method or rate adjustment method as provided in any embodiment of this application.

[0220] The system architecture and application scenarios described in this application are intended to more clearly illustrate the technical solutions of this application and do not constitute a limitation on the technical solutions provided in this application. Those skilled in the art will understand that as system architectures evolve and new application scenarios emerge, the technical solutions provided in this application are also applicable to similar technical problems.

[0221] Those skilled in the art will understand that all or some of the steps in the methods disclosed above, as well as the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, or suitable combinations thereof.

[0222] In hardware implementations, the division between functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0223] The terms “component,” “module,” “system,” etc., used in this specification are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, or a computer. As illustrated, applications running on computing devices and computing devices can both be components. One or more components may reside in a process or execution thread, and components may be located on a single computer or distributed among two or more computers. Furthermore, these components can be executed from various computer-readable media on which various data structures are stored. Components can communicate, for example, via local or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system, or a network, such as the Internet interacting with other systems via signals).

[0224] The above description, with reference to the accompanying drawings, illustrates some embodiments of this application, but does not limit the scope of this application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and spirit of this application shall be within the scope of this application.

Claims

1. An information exchange method applied to an FTTR master device in a fiber-to-the-room (FTTR) network, wherein the FTTR network further includes an FTTR slave device communicating with the FTTR master device, characterized in that, The method includes: In response to the non-standard rate support information of the FTTR master device, the non-standard rate support information of the FTTR slave device, and the preset non-standard rate switching conditions, it is determined to perform a non-standard rate switching with the FTTR slave device, and non-standard line rate information is sent to the FTTR slave device based on the standard line rate. The non-standard line rate information is obtained based on the non-standard rate support information of the FTTR master device and the non-standard rate support information of the FTTR slave device. Based on the standard line rate, receive non-standard line rate confirmation information sent by the FTTR slave device in response to the non-standard line rate information; Based on the non-standard line rate information, the line rate is switched synchronously with the FTTR slave device to exchange information with the FTTR slave device based on the non-standard line rate corresponding to the non-standard line rate information.

2. The method according to claim 1, characterized in that, The step of determining to perform a non-standard rate switch with the FTTR slave device in response to the non-standard rate support information of the FTTR master device, the non-standard rate support information of the FTTR slave device, and preset non-standard rate switching conditions includes: Obtain the service type information of the FTTR slave device; In response to the service type information of the FTTR slave device, the non-standard rate support information of the FTTR master device, the non-standard rate support information of the FTTR slave device, and preset non-standard rate switching conditions, it is determined to perform a non-standard rate switch with the FTTR slave device; wherein, the preset non-standard rate switching conditions include: determining that the line rate needs to be increased based on the service type information of the FTTR slave device, and the non-standard rate support information of the FTTR master device and the non-standard rate support information of the FTTR slave device having the same information.

3. The method according to claim 2, characterized in that, The step of obtaining the service type information of the FTTR slave device includes: Send a service type request to the FTTR slave device; Receive the service type information of the FTTR slave device sent by the FTTR slave device in response to the service type request.

4. The method according to claim 2, characterized in that, The preset non-standard rate switching conditions also include receiving a rate upgrade instruction sent by the operator's network management platform.

5. The method according to claim 1, characterized in that, Before sending non-standard line rate information to the FTTR slave device based on the standard line rate, the method further includes: Send a non-standard rate query message to the FTTR slave device; The system receives a non-standard rate capability reporting message sent by the FTTR slave device in response to the non-standard rate query message, wherein the non-standard rate capability reporting message contains non-standard rate support information of the FTTR slave device.

6. The method according to claim 1, characterized in that, The non-standard rate support information includes frame parameter adjustment strategies and frequency increase coefficients; the frequency increase coefficient is a proportional coefficient of the standard line rate supported by the device, and the frequency increase coefficient is any number greater than zero; the frame parameter adjustment strategy is an adjustment strategy for rate-related parameters supported by the device, and the rate-related parameters include at least one of frame length, bandwidth granularity, frame rate, and frame period. The non-standard line rate information includes a target frame parameter adjustment strategy and a target frequency increase coefficient. The frame parameter adjustment strategy in the non-standard rate support information of the FTTR master device and the frame parameter adjustment strategy in the non-standard rate support information of the FTTR slave device both include the target frame parameter adjustment strategy. The frequency increase coefficient in the non-standard rate support information of the FTTR master device and the frequency increase coefficient in the non-standard rate support information of the FTTR slave device both include the target frequency increase coefficient.

7. The method according to claim 6, characterized in that, The frame parameter adjustment strategy includes at least one of the following: The current frame rate is multiplied by the target frequency boosting factor, while keeping the current frame length and current bandwidth granularity unchanged, and the current frame period is divided by the target frequency boosting factor; The current frame rate is multiplied by the target frequency boosting factor, while keeping the current frame period unchanged. The current frame length is multiplied by the target frequency boosting factor, and the current bandwidth granularity is multiplied by the target frequency boosting factor.

8. The method according to claim 1, characterized in that, The method for determining whether there is identical information between the non-standard rate support information of the FTTR master device and the non-standard rate support information of the FTTR slave device includes: In response to the fact that the frame parameter adjustment strategy in the non-standard rate support information of the FTTR master device and the frame parameter adjustment strategy in the non-standard rate support information of the FTTR slave device contain the same frame parameter adjustment strategy, and the frequency increase coefficient in the non-standard rate support information of the FTTR master device and the frequency increase coefficient in the non-standard rate support information of the FTTR slave device contain the same frequency increase coefficient, it is determined that the non-standard rate support information of the FTTR master device and the non-standard rate support information of the FTTR slave device have the same information.

9. The method according to claim 8, characterized in that, The method for determining the non-standard line speed information includes: Obtain at least one identical frame parameter adjustment strategy contained in both the frame parameter adjustment strategy in the non-standard rate support information of the FTTR master device and the frame parameter adjustment strategy in the non-standard rate support information of the FTTR slave device; determine one frame parameter adjustment strategy from the at least one identical frame parameter adjustment strategy as the target frame parameter adjustment strategy in the non-standard line rate information; Obtain at least one identical frequency increase coefficient contained in both the non-standard rate support information of the FTTR master device and the non-standard rate support information of the FTTR slave device; determine the largest identical frequency increase coefficient from the at least one identical frequency increase coefficient as the target frequency increase coefficient in the non-standard line rate information.

10. The method according to claim 1, characterized in that, The non-standard line rate information includes the target frame parameter adjustment strategy and the target frequency increase coefficient; The step of synchronously switching line rates with the FTTR slave device based on the non-standard line rate information includes: Based on the target frame parameter adjustment strategy and the target frequency increase coefficient, the device synchronously re-registers and re-authenticates with the FTTR slave device.

11. An information exchange method, applied to an FTTR slave device in an FTTR network, wherein the FTTR network further includes an FTTR master device communicating with the FTTR slave device, characterized in that, The method includes: The non-standard line rate information sent by the FTTR master device is received based on the standard line rate, and the non-standard line rate information is obtained based on the non-standard rate support information of the FTTR master device and the non-standard rate support information of the FTTR slave device. Based on the standard line rate, send non-standard line rate confirmation information for the non-standard line rate information to the FTTR master device; Based on the non-standard line rate information, the line rate is switched synchronously with the FTTR master equipment to exchange information with the FTTR master equipment based on the non-standard line rate corresponding to the non-standard line rate information.

12. The method according to claim 11, characterized in that, Before receiving the non-standard line rate information sent by the FTTR master device based on the standard line rate, the method further includes: In response to the service type request sent by the FTTR master device, service type information is sent to the FTTR master device.

13. The method according to claim 11, characterized in that, Before receiving the non-standard line rate information sent by the FTTR master device based on the standard line rate, the method further includes: In response to receiving a non-standard rate query message sent by the FTTR master device, a non-standard rate capability reporting message is sent to the FTTR master device. The non-standard rate capability reporting message contains non-standard rate support information of the FTTR slave device. The non-standard rate query message includes at least one of the following: a standard or custom F-PLOAM message, a standard or custom FMCI message, and uplink / downlink frame indication bits of the embedded OAM management channel.

14. The method according to claim 11, characterized in that, The non-standard rate support information includes frame parameter adjustment strategies and frequency increase coefficients; the frequency increase coefficient is a proportional coefficient of the standard line rate supported by the device, and the frequency increase coefficient is any number greater than zero; the frame parameter adjustment strategy is an adjustment strategy for rate-related parameters supported by the device, and the rate-related parameters include at least one of frame length, bandwidth granularity, frame rate, and frame period. The non-standard line rate information includes a target frame parameter adjustment strategy and a target frequency increase coefficient. The frame parameter adjustment strategy in the non-standard rate support information of the FTTR master device and the frame parameter adjustment strategy in the non-standard rate support information of the FTTR slave device both include the target frame parameter adjustment strategy. The frequency increase coefficient in the non-standard rate support information of the FTTR master device and the frequency increase coefficient in the non-standard rate support information of the FTTR slave device both include the target frequency increase coefficient.

15. The method according to claim 14, characterized in that, The frame parameter adjustment strategy includes at least one of the following: The current frame rate is multiplied by the target frequency boosting factor, while keeping the current frame length and current bandwidth granularity unchanged, and the current frame period is divided by the target frequency boosting factor; The current frame rate is multiplied by the target frequency boosting factor, while keeping the current frame period unchanged. The current frame length is multiplied by the target frequency boosting factor, and the current bandwidth granularity is multiplied by the target frequency boosting factor.

16. The method according to claim 11, characterized in that, The non-standard line rate information includes the target frame parameter adjustment strategy and the target frequency increase coefficient; The step of synchronously switching line rates with the FTTR master equipment based on the non-standard line rate information includes: Based on the target frame parameter adjustment strategy and the target frequency increase coefficient, the device is synchronously re-registered and re-authenticated with the FTTR master device.

17. The method according to claim 11, characterized in that, The step of sending non-standard line rate confirmation information to the FTTR master device based on the standard line rate includes: In response to receiving the non-standard line rate information, a message integrity check is performed on the non-standard line rate information; If the verification passes, the rate of the FTTR slave device is configured based on the non-standard line rate information, and an acknowledgment message is sent to the FTTR master device.

18. The method according to claim 11, characterized in that, The FTTR slave device and the FTTR master device transmit messages through a DLL layer management channel; the DLL layer management channel includes any one of the following: F-PLOAM management channel, FMCC management channel, embedded OAM management channel, or WMCC management channel.

19. A rate adjustment method, characterized in that, include: Obtain the frame parameter adjustment strategy and frequency boosting coefficient; The standard line rate between at least two FTTR devices is adjusted according to the frame parameter adjustment strategy and the frequency increase coefficient to obtain the non-standard line rate.

20. The method according to claim 19, characterized in that, The frequency increase coefficient is a proportional coefficient of the standard line rate, and the frequency increase coefficient is any number greater than zero; the frame parameter adjustment strategy is an adjustment strategy of rate-related parameters supported by the FTTR device, and the rate-related parameters include at least one of frame length, bandwidth granularity, frame rate, and frame period.

21. The method according to claim 19, characterized in that, The frame parameter adjustment strategy includes at least one of the following: The current frame rate is multiplied by the frequency boosting factor, while keeping the current frame length and current bandwidth granularity unchanged, and the current frame period is divided by the frequency boosting factor; The current frame rate is multiplied by the frequency boosting factor, the current frame period remains unchanged, the current frame length is multiplied by the frequency boosting factor, and the current bandwidth granularity is multiplied by the frequency boosting factor.

22. An FTTR device, characterized in that, include: At least one processor; At least one memory for storing at least one program; When at least one of the programs is executed by at least one of the processors, it implements the information interaction method as described in any one of claims 1 to 18, or the rate adjustment method as described in any one of claims 19 to 21.

23. A computer-readable storage medium storing computer-executable instructions, characterized in that, The computer-executable instructions are used to execute the information interaction method as described in any one of claims 1 to 18, or to execute the rate adjustment method as described in any one of claims 19 to 21.

24. A computer program product, comprising a computer program or computer instructions, characterized in that, The computer program or the computer instructions are stored in a computer-readable storage medium. The processor of the FTTR device reads the computer program or the computer instructions from the computer-readable storage medium and executes the computer program or the computer instructions, causing the FTTR device to perform the information interaction method according to any one of claims 1 to 18, or to perform the rate adjustment method according to any one of claims 19 to 21.

Images