Low-delay communication method based on all-optical network

Abstract

Embodiments of the present disclosure provide a low-delay communication method based on an all-optical network. The method comprises: for an all-optical network link, configuring a rigid pipeline on a link composed of an FTTR secondary device, an FTTR primary device, and an optical line terminal (OLT); identifying a data stream, and in the case that the data stream comprises a feature identifier, transmitting the data stream by means of the rigid pipeline.

Description

Low-latency communication method based on all-optical network

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] The present disclosure is based on Chinese patent application CN202410036145.0 filed on January 10, 2024, entitled “Low-latency communication method based on all-optical network”, and claims the priority of the patent application, and all the contents disclosed therein are incorporated into the present disclosure by reference. Technical Field

[0003] The embodiments of the present disclosure relate to the technical field of communications, and in particular, to a low-latency communication method based on an all-optical network. Background Art

[0004] With the continuous development of optical networks, broadband network services are moving towards the fifth generation fixed network (F5G) era, with 10G PON (gigabit broadband) and WI-FI6 (gigabit WI-FI) as the mainstream. Compared with previous generations of fixed access technologies, F5G has a series of excellent features such as ultra-high network access speed, all-optical connection, and excellent network experience. The F5G home private network extends fiber to every room on the basis of fiber-to-the-home (FTTH) to achieve all-optical networking within the home. In combination with 10G PON (gigabit broadband) and WI-FI6 (gigabit WI-FI) technologies, it achieves gigabit coverage throughout the home, solving problems such as insufficient home WI-FI signal coverage and substandard speeds, and achieving safe and reliable gigabit coverage throughout the home.

[0005] In broadband device transmission links, multiple devices are connected in a point-to-multipoint (P2MP) network. This results in longer links and more devices, leading to more concurrent scenarios and data volumes. This leads to data congestion and scheduling lags, which increase service latency. Therefore, the service scheduling methods used in related technologies cannot meet the requirements for carrying low-latency services.

[0006] Public content

[0007] The embodiments of the present disclosure provide a low-latency communication method based on an all-optical network, so as to at least solve the problem that the service scheduling method in the related art cannot meet the demand for carrying low-latency services.

[0008] According to one embodiment of the present disclosure, a low-latency communication method based on an all-optical network is provided, comprising:

[0009] For all-optical network links, rigid pipes are configured on the link consisting of the FTTR slave device, the FTTR master device, and the optical line terminal OLT;

[0010] A data stream is identified, and if the data stream contains a characteristic identifier, the data stream is transmitted through the rigid pipe.

[0011] According to another embodiment of the present disclosure, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is configured to execute the steps of any one of the above method embodiments when running.

[0012] According to another embodiment of the present disclosure, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the steps in any one of the above method embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] FIG1 is a schematic diagram of a network architecture according to an embodiment of the present disclosure;

[0014] FIG2 is a flow chart of a low-latency communication method based on an all-optical network according to an embodiment of the present disclosure;

[0015] FIG3 is a flowchart of a method for transmitting a data stream in an uplink direction through a rigid pipe according to an embodiment of the present disclosure;

[0016] FIG4 is a flow chart of a method for transmitting a data stream in a downlink direction through a rigid pipe according to an embodiment of the present disclosure;

[0017] FIG5 is a flowchart of a DBA collaborative scheduling method according to an embodiment of the present disclosure;

[0018] FIG6 is an exemplary diagram of a method for DBA collaborative scheduling according to an embodiment of the present disclosure;

[0019] FIG7 is an exemplary diagram of a method for dividing DBA subframes according to an embodiment of the present disclosure;

[0020] 8 is a flowchart of a method for adjusting the number and bandwidth configuration of DBA subframes based on the service type of a data stream according to an embodiment of the present disclosure;

[0021] 9 is a flowchart of a method for enabling an FTTR master device to identify an FTTR slave device within a short window period according to an embodiment of the present disclosure;

[0022] FIG10 is an exemplary diagram of a method for sending a null entry after a pre-equalization delay according to an embodiment of the present disclosure;

[0023] FIG. 11 is an exemplary diagram of a method of allocating empty entries first instead of using a pre-equalization delay method according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0024] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings and in conjunction with embodiments.

[0025] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0026] The embodiment of the present disclosure can run on the network architecture shown in Figure 1. As shown in Figure 1, the network architecture includes: an optical line terminal (OLT), a fiber to the room (FTTR) master device, and a FTTR slave device. Among them, the optical line terminal OLT is communicatively connected to the FTTR master device, the FTTR master device is communicatively connected to the FTTR slave device, and the FTTR slave device is communicatively connected to multiple station (STA) devices (for example, STA1, STA2). In the embodiment disclosed below, the optical line terminal OLT is communicatively connected to a FTTR master device, and the FTTR master device is communicatively connected to a FTTR slave device as an example. Of course, this is only an example. Therefore, the optical line terminal OLT can also be connected to multiple FTTR master devices, and the FTTR master device can also be connected to multiple FTTR slave devices. The specific number can be set according to actual conditions, and the embodiment of the present disclosure does not limit it.

[0027] In one implementation, the embodiments of the present disclosure may operate in a PON+FTTR+WI-FI system, wherein the aforementioned network architecture is an intermediate link of the PON+FTTR+WI-FI system.

[0028] In this embodiment, a method operating on the above network architecture is provided. FIG2 is a flow chart of a low-latency communication method based on an all-optical network according to an embodiment of the present disclosure. As shown in FIG2 , the process includes the following steps:

[0029] Step S201: For an all-optical network link, a rigid pipe is configured on a link consisting of an FTTR slave device, an FTTR master device, and an optical line terminal OLT.

[0030] In one embodiment, the all-optical network link can be the link of the above-mentioned PON+FTTR+WI-FI system, or it can be a PON+OLT+ONU link, or a PON+OLT+ONT link, or a PON+OLT+MDU link, or a PON+OLT+Switch link. For the PON+OLT+ONU link, the passive optical network (PON) is a fiber optic transmission technology that includes an OLT and an optical network unit (ONU). In this link, optical fiber transmission is from the OLT to the ONU, and the ONU then provides network connectivity. The PON+OLT+ONT link is similar to the PON+OLT+ONU link, but an optical network terminal (ONT) is used instead of the ONU. An ONT generally refers to a user-end device used to connect to the PON network and provide network services. For the PON+OLT+MDU link, a multi-dwelling unit (MDU) is typically an apartment building or multi-family residence. In this type of link, PON technology is used to extend fiber transmission from the OLT to the various terminal units in the MDU. In some scenarios, for a PON+OLT+Switch link, it may be necessary to combine the PON network with an Ethernet switch to provide greater network scalability and connectivity. In this link configuration, fiber transmission runs from the OLT to the switch, which then connects to other devices or networks.

[0031] In an exemplary embodiment, the following method may be used:

[0032] Define a pipe: Define a rigid pipe in the optical network and determine the starting and ending points of the pipe. This can be done through the network management system or the command line interface.

[0033] Configure pipe properties: Allocate appropriate bandwidth and other properties to the rigid pipe. This can include determining the pipe's transmission rate, capacity, and quality of service requirements.

[0034] Configure link interfaces: Configure the relevant link interfaces on the FTTR slave and FTTR master devices. This can be performed based on the device model and specific operating system.

[0035] Configuring the OLT interface: Configuring the interface on the optical line terminal (OLT) that connects to the FTTR. This may include defining the port on the OLT, VLAN settings, etc.

[0036] Connecting devices to the OLT: Use optical fibers to connect the optical ports between the FTTR slave device and the FTTR master device, and between the FTTR master device and the OLT. Ensure that the connections are correct and reliable.

[0037] Configure link protection: As needed, you can configure link protection to improve link reliability and redundancy. You can use redundant links, backup links, or other protection mechanisms.

[0038] Testing and verification: After completing configuration, perform testing and verification to ensure the normal operation of the link. This includes testing the link's connectivity, bandwidth performance, and other indicators.

[0039] Step S202: Identify the data stream, and if the data stream contains a characteristic identifier, transmit the data stream through a rigid pipe.

[0040] This disclosure firstly adopts a rigid pipe configuration approach. In an all-optical network link, this rigid pipe is deployed across the link consisting of the FTTR slave device, the FTTR master device, and the optical line terminal (OLT). This rigid pipe configuration can effectively reduce data transmission latency and improve the stability and reliability of data transmission.

[0041] Secondly, the present disclosure also employs a data stream identification method. When a data stream contains a signature identifier, a rigid pipeline is used to transmit the data stream. This data stream identification method can distinguish low-latency services from other services based on the signature identifier, thereby prioritizing the transmission of low-latency services and improving their transmission efficiency and response speed.

[0042] Through the rigid pipeline configuration and data flow identification method described above, this disclosure addresses the issue of related art service scheduling methods failing to meet the requirements for carrying low-latency services. It reduces transmission latency, improves the stability and reliability of data transmission, and prioritizes the transmission of low-latency services, meeting these requirements.

[0043] In one embodiment, the characteristic identifier includes a GEMPORTID (GEM PORT-ID, GEM port identifier, where GEM stands for Gigabit-capable passive optical network Encapsulation Method).

[0044] In one embodiment, the characteristic identifier includes one or more of the following: GEMPORTID, Allocation Identifier (ALLOCID for short), wherein ALLOCID is a factor for allocating bandwidth based on downlink frames in the uplink direction.

[0045] In an exemplary embodiment, for services requiring a rigid pipe, a characteristic identifier is given, and it is agreed that this characteristic identifier can be identified as a rigid pipe, and the transferability of this characteristic identifier is guaranteed. That is, across the entire PON+FTTR+Wi-Fi link, the data flow can be identified as entering a rigid pipe at the FTTR slave device, FTTR master device, and OLT by matching the characteristic identifier.

[0046] FIG3 is a flow chart of a method for transmitting a data stream in an upstream direction through a rigid pipe according to an embodiment of the present disclosure. In one embodiment, as shown in FIG3 , a rigid pipe is configured on a link consisting of an FTTR slave device, an FTTR master device, and an optical line terminal (OLT); a data stream is identified, and when the data stream contains a characteristic identifier, the data stream is transmitted through the rigid pipe, including:

[0047] Step S301: The FTTR slave device receives an uplink data stream sent from a Wi-Fi site, and configures a rigid pipe between the FTTR slave device and the FTTR master device so that the uplink data flows from the rigid pipe to the FTTR master device.

[0048] Step S302: The FTTR main device receives an upstream data stream, and configures a rigid pipe between the FTTR main device and the optical line terminal (OLT) so that the upstream data flows from the rigid pipe to the optical line terminal (OLT).

[0049] In an exemplary embodiment, for the uplink direction, the FTTR slave device side allocates different transmission containers (TCONT) and GEMPORTs (GEM ports) to identify rigid pipes based on the WI-FI slices of different services received. That is, given the ALLOCID and GEMPORTID corresponding to the rigid pipe, the matching ALLOCID and GEMPORTID enters the rigid pipe for low-latency priority scheduling and sending, thereby reducing the uplink transmission delay between the FTTR master device and the FTTR slave device; on the FTTR master device side, the rigid pipe TCONT and GEMPORT between the OLT and the FTTR master device are allocated according to the corresponding service flow transmitted to the FTTR master device side by the rigid pipe GEMPORTID of the FTTR slave device, and the rigid pipe low-latency priority scheduling and sending between the OLT and the FTTR master device are also performed based on the matching ALLOCID and GEMPORTID, thereby realizing end-to-end low-latency collaborative transmission from WI-FI to PON in the uplink direction.

[0050] Among them, Wi-Fi Slicing is a technology based on Network Function Virtualization (NFV) and Software Defined Networking (SDN). It aims to divide the wireless local area network (Wi-Fi) network into multiple logical slices to provide personalized network services for different users or applications.

[0051] Wi-Fi slicing allows network administrators to dynamically partition Wi-Fi network resources and assign network slices to specific user groups or application scenarios based on demand, enabling flexible resource configuration and management. Each slice can be configured with different Quality of Service (QoS), bandwidth limits, security policies, and more to meet the needs of different users and applications.

[0052] FIG4 is a flow chart of a method for transmitting a data stream in a downstream direction through a rigid pipe according to an embodiment of the present disclosure. In one embodiment, as shown in FIG4 , a rigid pipe is configured on a link consisting of an FTTR slave device, an FTTR master device, and an optical line terminal (OLT); a data stream is identified, and when the data stream contains a characteristic identifier, the data stream is transmitted through the rigid pipe, including:

[0053] Step S401: The optical line terminal OLT configures a rigid pipe between the optical line terminal OLT and the FTTR main device based on the downstream data flow, so that the downstream data flow flows into the FTTR main device through the rigid pipe;

[0054] Step S402: The FTTR master device receives the downstream data stream and configures a rigid pipe between the FTTR master device and the FTTR slave device so that the downstream data stream flows into the FTTR slave device based on the rigid pipe.

[0055] In an exemplary embodiment, in the downstream direction, between the optical line terminal (OLT) and the FTTR master device, and between the FTTR master device and the FTTR slave device, the GEMPORTID used for the same service is the same as in the upstream direction. This GEMPORTID identifies the rigid pipe in the downstream direction for priority scheduling. On the FTTR slave device to Wi-Fi side, different Differentiated Services Code Point (DSCP) values ​​are assigned to different service flows based on different GEMPORT identifiers for priority scheduling. This achieves end-to-end low-latency priority scheduling transmission in the downstream direction from PON to Wi-Fi.

[0056] In one embodiment, the FTTR master device receives a downstream data stream, and configures a rigid pipe between the FTTR master device and the FTTR slave device so that the downstream data stream flows into the FTTR slave device based on the rigid pipe, including:

[0057] The FTTR receives downstream data flows from the device and assigns a DSCP value to the downstream data flows so that the downstream data flows are preferentially sent to the Wi-Fi station.

[0058] FIG5 is a flow chart of a dynamic bandwidth allocation (DBA) collaborative scheduling method according to an embodiment of the present disclosure. In one embodiment, as shown in FIG5 , the method further includes using a DBA collaborative scheduling method. The DBA collaborative scheduling method includes: before the FTTR slave device receives an uplink data stream sent from a WI-FI station,

[0059] Step S501: The FTTR slave device sends a first bandwidth request to the FTTR master device based on the uplink request frame sent by the WI-FI station;

[0060] Step S502: The optical line terminal OLT allocates an uplink bandwidth to the FTTR master device based on the second bandwidth request;

[0061] Step S503: The FTTR master device allocates uplink bandwidth to the FTTR slave device based on the first bandwidth request.

[0062] FIG6 is an example diagram of a method for DBA collaborative scheduling according to an embodiment of the present disclosure. In an exemplary embodiment, as shown in FIG6 , in order to reduce the DBA waiting time, an exemplary DBA collaborative method may be adopted. The collaborative DBA trigger detection condition is: the FTTR slave device receives the uplink transmission request frame of the STA (for example, STA1 and STA2). The post-perception implementation method is: when the FTTR slave device receives the STA uplink transmission request, the FTTR slave device sends a bandwidth request to the FTTR master device at this time. After receiving the bandwidth request from the FTTR slave device, the FTTR master device sends a bandwidth request to the optical line terminal OLT, so that the FTTR slave device and the FTTR master device prepare the uplink bandwidth in advance, which greatly reduces the time for data to wait for DBA to allocate bandwidth after arriving at the FTTR slave device and the FTTR master device, thereby reducing the uplink path delay.

[0063] In one embodiment, the method further includes a DBA subframe division method, and the DBA subframe division method includes:

[0064] In a DBA scheduling cycle, the number of DBA subframes and bandwidth configuration are adjusted based on the service type of the data flow.

[0065] FIG7 is an example diagram of a method for dividing DBA subframes according to an embodiment of the present disclosure. In an exemplary embodiment, as shown in FIG7 , the number of subframes divided into each 125 us frame can be freely selected. For example, subframe 1, subframe 2, subframe 3, subframe 4. Of course, FIG7 is only an example. Each 125 us frame can also be divided into subframe 1, subframe 2, subframe 3, subframe 4, ... subframe N. The specific number of subframes can be selected according to actual conditions and will not be described here. Moreover, the size of each subframe is not fixed, and both uniform and uneven divisions are possible. It can be evenly distributed and kept the same, with the same start time interval for each subframe and the same bandwidth allocated; it can also be freely adjusted according to actual needs, and different bandwidths can be allocated to different subframes. When the subframe division of one frame within the DBA cycle is determined, the subframe division of the remaining three frames is the same as the first frame.

[0066] First, using 2.5G asymmetric mode, one-byte bandwidth granularity, and 100Mbps bandwidth allocation, this paper describes the calculation method and provides examples for uniform and uneven subframe division. Within a subframe, in addition to the burst overhead, the software can configure the corresponding start and stop times as needed.

[0067] If uniform subframe allocation is considered, the maximum bandwidth allocated per 125us frame is 19440 bytes: 19440 / 4 = 4860 bytes. To account for burst overhead, the start time of the first subframe entry is delayed by 50 bytes. Therefore, the start times of each subframe can be considered to be 0, 4860, 9720, and 14580 bytes. For a 100Mbps bandwidth, the bandwidth allocated per 125us frame is (1000000000 / 8) / (1000000 / 125) ≈ 1562 bytes, resulting in an average of 1562 / 4 ≈ 390 bytes per subframe. Therefore, if uniform subframe allocation is considered, the four possible subframe allocations are: subframes 49 to 439 bytes; subframes 4860 to 5250 bytes; subframes 9720 to 10110 bytes; and subframes 14580 to 14969 bytes.

[0068] If uneven subframe allocation is considered, the allocated bandwidth per 125µs frame remains 1562 bytes, and subframes within each frame can be freely allocated. For example, consider four subframes with start times of 50, 10,000, 11,000, and 15,000 bytes, respectively, and the allocated bandwidth per subframe is 800, 80, 332, and 350 bytes, respectively. Based on this allocation, the four subframes can be unevenly allocated as follows: subframes from 50 to 849 bytes; subframes from 10,000 to 10,079 bytes; subframes from 11,000 to 11,331 bytes; or subframes from 15,000 to 15,349 bytes.

[0069] Secondly, further, considering 100Mbps bandwidth and evenly dividing each frame into four subframes, a subframe division embodiment is given for four modes: 2.5G asymmetric, 2.5G symmetric, 10G asymmetric, and 10G symmetric. The specific results are shown in the following table.

[0070] In one implementation, if 50 GPON is needed later, bandwidth configuration can also be performed according to this method.

[0071] FIG8 is a flowchart of a method for adjusting the number and bandwidth configuration of DBA subframes based on the service type of a data flow according to an embodiment of the present disclosure. In one embodiment, as shown in FIG8 , adjusting the number and bandwidth configuration of DBA subframes based on the service type of a data flow within a DBA scheduling period includes:

[0072] Step S801, identifying the message type of the data flow to determine the service type;

[0073] Step S802: Determine the delay and bandwidth based on the service type;

[0074] Step S803: classify and prioritize latency and bandwidth;

[0075] Step S804: Adjust the number and bandwidth configuration of DBA subframes based on the results of classification and priority sorting.

[0076] In an exemplary embodiment, considering that different services require different subframe division methods, it is necessary to identify different service types, consider requirements such as latency and traffic, and provide a suitable DBA subframe division method to improve the flexibility and adaptability of the DBA allocation method.

[0077] On the one hand, the service type can be determined by identifying relevant protocol messages. For example, a Session Initiation Protocol (SIP) message can be identified as a voice call service; a multicast join message can be identified as an Internet Protocol Television (IPTV) video service. On the other hand, the required latency and bandwidth are determined based on the identified service type. Different services are then directly classified and prioritized based on latency and bandwidth. For example, voice services have higher latency requirements than IPTV, and IPTV has higher bandwidth requirements than voice services. Based on the latency and bandwidth characteristics of the services, the DBA subframe division method is adjusted to meet the service's latency and bandwidth requirements. After bandwidth allocation, the allocation status of different services needs to be recorded to facilitate unified adjustments when new services are added.

[0078] In one embodiment, the method further includes using a short windowing method, and the short windowing setting method includes:

[0079] During the message request reporting phase, the FTTR master device sets a short window based on the response time of the FTTR slave device, the random delay between the FTTR master device and the FTTR slave device, and the loop delay between the FTTR master device and the FTTR slave device, so that the FTTR master device can identify the FTTR slave device within the short window period.

[0080] FIG9 is a flowchart of a method for enabling an FTTR master device to identify an FTTR slave device within a short window period according to an embodiment of the present disclosure. In one embodiment, as shown in FIG9 , during the message request reporting phase, the FTTR master device sets a short window based on the response time of the FTTR slave device, the random delay between the FTTR master device and the FTTR slave device, and the loop delay between the FTTR master device and the FTTR slave device, so that the FTTR master device can identify the FTTR slave device within the short window period, including:

[0081] Step S901: The FTTR master device calculates a pre-equalization delay based on the response time of the FTTR slave device, the random delay between the FTTR master device and the FTTR slave device, and the loop delay between the FTTR master device and the FTTR slave device, and sends a null entry after the pre-equalization delay.

[0082] In step S902 , the FTTR master device uses the sum of the pre-equalization delay and the delay occupied by the empty entry as the short windowing period, so that the FTTR master device can identify the FTTR slave device within the short windowing period.

[0083] Figure 10 illustrates an example method for sending empty entries after a pre-equalization delay according to an embodiment of the present disclosure. Figure 11 illustrates an example method for allocating empty entries first, without pre-equalization delay, according to an embodiment of the present disclosure. In an exemplary embodiment, as shown in Figures 10 and 11, during the sequence number (SN) reporting phase, to reduce the impact of windowing on upstream path delay, the silent window is reduced from the original 250µs over two frames to a specific time period within one frame. The specific time period can be set based on actual conditions. Adjusting the window size requires comprehensive consideration of the relationship between the FTTR slave's response time, random delay, and the maximum loop delay between the FTTR master and slave. Considering the fiber distance between the FTTR master and slave to be x kilometers (km) and the maximum random delay to be y microseconds (µs), the pre-equalization delay in Figure 10 and the SN request start time in Figure 11 to be zus, the FTTR slave's response time to be 35±1µs, with a maximum of 36µs. Since the optical transmission delay corresponding to 1 km is 10 us, the optical transmission delay is 10xus. Considering that the response delay of the FTTR slave device generally fluctuates by 2 us, the silent window is 10x+2+yus. The maximum loop delay is the sum of the FTTR slave device response time and the optical transmission delay, 10x+36us.

[0084] Considering a maximum fiber distance of 1 km between the FTTR master and slave devices, and a random delay of 0 to 11 μs (i.e., x = 1, y = 11, z = 12), the maximum loop delay is 36 + 10 = 46 μs, and the quiet window is 10 + 2 + 11 = 23 μs. When the FTTR master sends a downlink frame at t0, due to the loop delay and the response time of the FTTR slave, tz = t0 + 46 μs, and a 23 μs quiet window begins at tz.

[0085] In Figure 10, a pre-equalization delay of 12 us is pre-specified through the Upstream_Overhead PLOAM (Physical Layer OAM, where OAM stands for Operations, Administrations and Maintenance) message. The SN request start time in the downlink frame is 0, that is, time t0, followed by an empty entry. Even if the minimum response time of the FTTR slave device is 34 us, due to the FTTR slave device response time and the pre-equalization delay, the time when the FTTR master device receives the FTTR slave device SN response is offset by at least 46 us relative to t0, ensuring that it is within the silent window. Since the silent window is 23 us, the latest SN response received can also be guaranteed to be within the window.

[0086] To sum up, the purpose of the above method is to set the pre-equalization delay and the empty entry to ensure that after the FTTR master device sends an instruction to the FTTR slave device, the time point when the FTTR master device receives the feedback information from the FTTR slave device is within the quiet window.

[0087] In one embodiment, during the message request reporting phase, the FTTR master device sets a short window based on the response time of the FTTR slave device, the random delay between the FTTR master device and the FTTR slave device, and the loop delay between the FTTR master device and the FTTR slave device, so that the FTTR master device can identify the FTTR slave device within the short window period, including:

[0088] The FTTR master device uses the delay occupied by the empty entry as a short window period, so that the FTTR master device can identify the FTTR slave device within the short window period.

[0089] In an exemplary embodiment, as shown in Figure 11, the FTTR master does not use pre-equalization delay. Instead, it allocates empty entries, starting at 12us, or t0+12us. Similarly, the earliest time the FTTR master receives an SN response is at least t0+46us, and the latest within the silent window is the same.

[0090] In summary, by allocating empty entries first, it can be ensured that after the FTTR master device sends an instruction to the FTTR slave device, the time point when the FTTR master device receives the feedback information from the FTTR slave device is within the quiet window.

[0091] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by adding the necessary general hardware platform with the help of software, of course, it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present disclosure is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, disk, CD-ROM), including a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present disclosure.

[0092] An embodiment of the present disclosure further provides a computer-readable storage medium, in which a computer program is stored. The computer program is configured to execute the steps of any one of the above method embodiments when run.

[0093] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0094] An embodiment of the present disclosure further provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0095] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0096] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail here.

[0097] Obviously, those skilled in the art should understand that the modules or steps of the present disclosure described above can be implemented using a general-purpose computing device, they can be concentrated on a single computing device, or distributed across a network composed of multiple computing devices, they can be implemented using program code executable by the computing device, and thus, they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be performed in a different order than herein, or they can be fabricated into separate integrated circuit modules, or multiple modules or steps can be fabricated into a single integrated circuit module for implementation. Thus, the present disclosure is not limited to any particular combination of hardware and software.

[0098] The foregoing description is merely a preferred embodiment of the present disclosure and is not intended to limit the present disclosure. Those skilled in the art will readily appreciate that various modifications and variations of the present disclosure are possible. Any modifications, equivalent substitutions, or improvements made within the principles of the present disclosure shall be included within the scope of protection of the present disclosure.

Claims

1. A low-latency communication method based on an all-optical network, comprising: For an all-optical network link, configure a rigid pipe on the link composed of a fiber to the room FTTR slave device, the FTTR master device, and the optical line terminal OLT; Identify the data stream, and when the data stream contains a feature identifier, transmit the data stream through the rigid pipe.

2. The method according to claim 1, wherein, The feature identifier includes a Gigabit Passive Optical Network encapsulation mode port identifier GEMPORTID.

3. The method according to claim 1, wherein, For an all-optical network link, configure a rigid pipe on the link composed of the FTTR slave device, the FTTR master device, and the optical line terminal OLT; identify the data stream, and when the data stream contains a feature identifier, transmit the data stream through the rigid pipe, including: The FTTR slave device receives an upstream data stream sent from a WI-FI station, and configures a rigid pipe between the FTTR slave device and the FTTR master device, so that the upstream data flows into the FTTR master device through the rigid pipe; The FTTR master device receives the upstream data stream, and configures a rigid pipe between the FTTR master device and the optical line terminal OLT, so that the upstream data flows into the optical line terminal OLT through the rigid pipe.

4. The method according to claim 1, wherein For an all-optical network link, configure a rigid pipe on the link composed of the FTTR slave device, the FTTR master device, and the optical line terminal OLT; identify the data stream, and when the data stream contains a feature identifier, transmit the data stream through the rigid pipe, including: The optical line terminal OLT configures a rigid pipe between the optical line terminal OLT and the FTTR master device based on the downstream data stream, so that the downstream data stream flows into the FTTR master device based on the rigid pipe; The FTTR master device receives the downstream data stream, and configures a rigid pipe between the FTTR master device and the FTTR slave device, so that the downstream data stream flows into the FTTR slave device based on the rigid pipe.

5. The method according to claim 4, wherein After the FTTR master device receives the downstream data stream and configures a rigid pipe between the FTTR master device and the FTTR slave device, so that the downstream data stream flows into the FTTR slave device based on the rigid pipe, it includes: The FTTR slave device receives the downstream data stream, and assigns a Differentiated Services Code Point DSCP value to the downstream data stream, so that the downstream data stream is preferentially sent to the WI-FI station.

6. The method according to claim 3, wherein The method further includes using a method of coordinated scheduling with dynamic bandwidth allocation DBA. The method of coordinated scheduling with DBA includes: before the FTTR slave device receives an upstream data stream sent from a WI-FI station, The FTTR slave device sends a first bandwidth request to the FTTR master device based on an upstream request frame sent from the WI-FI station; The FTTR master device sends a second bandwidth request to the optical line terminal OLT based on the first bandwidth request; The optical line terminal OLT allocates upstream bandwidth to the FTTR master device based on the second bandwidth request; The FTTR master device allocates uplink bandwidth for the FTTR slave device based on the first bandwidth request.

7. The method according to claim 1, wherein The method further includes a method for DBA subframe partitioning, and the method for DBA subframe partitioning includes: Within a DBA scheduling period, adjust the number and bandwidth configuration of DBA subframes based on the service type of the data stream.

8. The method according to claim 7, wherein Within a DBA scheduling period, adjusting the number and bandwidth configuration of DBA subframes based on the service type of the data stream includes: Identify the packet type of the data stream to determine the service type; Determine the latency and bandwidth based on the service type; Classify and prioritize the latency and bandwidth; Adjust the number and bandwidth configuration of the DBA subframes based on the results of the classification and prioritization.

9. The method according to claim 1, wherein The method further includes a method for using short windows, and the method for setting short windows includes: During the packet request reporting phase, the FTTR master device sets a short window based on the response time of the FTTR slave device, the random latency between the FTTR master device and the FTTR slave device, and the loop latency between the FTTR master device and the FTTR slave device, so that the FTTR master device can identify the FTTR slave device within the time period of the short window.

10. The method according to claim 9, wherein During the packet request reporting phase, the FTTR master device sets a short window based on the response time of the FTTR slave device, the random latency between the FTTR master device and the FTTR slave device, and the loop latency between the FTTR master device and the FTTR slave device, so that the FTTR master device can identify the FTTR slave device within the time period of the short window, including: The FTTR master device calculates a pre - equalization latency based on the response time of the FTTR slave device, the random latency between the FTTR master device and the FTTR slave device, and the loop latency between the FTTR master device and the FTTR slave device, and sends an empty entry after the pre - equalization latency; The FTTR master device uses the sum of the pre - equalization latency and the latency occupied by the empty entry as the time period of the short window, so that the FTTR master device can identify the FTTR slave device within the time period of the short window.

11. The method according to claim 9, wherein During the packet request reporting phase, the FTTR master device sets a short window based on the response time of the FTTR slave device, the random latency between the FTTR master device and the FTTR slave device, and the loop latency between the FTTR master device and the FTTR slave device, so that the FTTR master device can identify the FTTR slave device within the time period of the short window, including: The FTTR master device uses the latency occupied by the empty entry as the time period of the short window, so that the FTTR master device can identify the FTTR slave device within the time period of the short window.

12. A computer-readable storage medium storing a computer program therein, wherein, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 11.

13. An electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein when the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 11.

Images