WO2025148659A1 - Low-delay communication method based on all-optical network - Google Patents

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

CROSS-REFERENCE TO RELATED APPLICATIONS

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

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

With the continuous development of optical networks, bandwidth network services are moving towards the fifth generation fixed communication (Fifth Generation Fixed Network, referred to as F5G) era with 10G PON (gigabit broadband) and WI-FI6 (gigabit WI-FI) as the mainstream. Compared with previous generations of fixed access technology, F5G has a series of excellent features such as ultra-high network access rate, all-optical connection, and excellent network experience. F5G home private network is based on fiber to the home, extending optical fiber to the room, realizing all-optical networking in the home, and combining 10G PON (gigabit broadband) and WI-FI6 (gigabit WI-FI) technology to achieve gigabit coverage of the whole house, solve the problems of insufficient coverage of home WI-FI signals and substandard speed, and achieve safe and reliable gigabit coverage of the whole house.

In the transmission link of broadband equipment, multiple devices are connected to form a network in a point-to-multipoint (P2MP) manner. The link is long and there are many devices. There will be more concurrent scenarios and data volume problems, which will lead to data congestion and scheduling lags, resulting in increased service delays. Therefore, the service scheduling method of related technologies cannot meet the needs of carrying low-latency services.

Public Content

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.

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

For all-optical network links, a rigid pipe is configured on the link consisting of the FTTR slave device, the FTTR master device and the optical line terminal OLT;

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

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

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 execute the steps in any one of the above method embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

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

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;

3 is a flow chart of a method for transmitting a data stream in an uplink direction through a rigid pipe according to an embodiment of the present disclosure;

4 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;

FIG5 is a flow chart of a DBA collaborative scheduling method according to an embodiment of the present disclosure;

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

FIG7 is an exemplary diagram of a method for dividing a DBA subframe according to an embodiment of the present disclosure;

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;

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;

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;

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

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings and in combination with the embodiments.

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.

The embodiment of the present disclosure can be run on the network architecture shown in Figure 1. As shown in Figure 1, the network architecture includes: an optical line terminal (Optical Line Terminal, referred to as OLT), a fiber to the room (Fiber To The Room, referred to as 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 following disclosed embodiments, 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 the actual situation, and the embodiment of the present disclosure does not limit it.

In one implementation, the embodiment of the present disclosure may be run in a PON+FTTR+WI-FI system, wherein the above network architecture is an intermediate link of the PON+FTTR+WI-FI system.

In this embodiment, a method running on the above network architecture is provided. FIG. 2 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 FIG. 2 , the process includes the following steps:

Step S201, for an all-optical network link, a rigid pipe is configured on a link consisting of a FTTR slave device, a FTTR master device and an optical line terminal OLT;

In one embodiment, the all-optical network link can be a link of the above-mentioned PON+FTTR+WI-FI system, or a PON+OLT+ONU link, or a PON+OLT+ONT link, or a PON+OLT+MDU link, or a PON+OLT+Switch link. Among them, for the PON+OLT+ONU link, the passive optical network (Passive Optical Network, referred to as PON) is a fiber optic transmission technology, including OLT and optical network unit (Optical Network Unit, referred to as ONU). In this link, the optical fiber transmission is from OLT to ONU, and then the ONU provides network connection. For the PON+OLT+ONT link, it is similar to the PON+OLT+ONU link, but the optical network terminal (Optical Network Terminal, referred to as ONT) is used instead of ONU. ONT usually refers to the user terminal equipment, which is used to connect to the PON network and provide network services. For the PON+OLT+MDU link, the Multi-Dwelling Unit (MDU) is usually an apartment building or a multi-family residence. In this link, PON technology is used to extend the fiber transmission from the OLT to the various terminal units in the MDU. For the PON+OLT+Switch link, in some scenarios, it may be necessary to combine the PON network with an Ethernet switch (Switch) to provide higher network scalability and connectivity. In this link configuration, the fiber transmission goes from the OLT to the switch, and then the switch connects to other devices or networks.

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

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 command line interface.

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.

Configure link interfaces: Configure the relevant link interfaces on the FTTR slave and FTTR master devices. This can be performed according to the device model and specific operating system.

Configure OLT interface: Configure the interface connected to the FTTR on the optical line terminal OLT. This can include defining the port on the OLT, VLAN settings, etc.

Connect the device and OLT: Use optical fiber to connect the optical ports between the FTTR slave device and the FTTR master device, and connect the optical fiber between the FTTR master device and the OLT. Ensure that the connection is correct and reliable.

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.

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

Step S202, identifying the data stream, and transmitting the data stream through a rigid pipeline when the data stream contains a characteristic identifier.

Through the present disclosure, firstly, the present disclosure adopts a rigid pipe configuration method. In 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. This rigid pipe configuration method can effectively reduce data transmission delay and improve the stability and reliability of data transmission.

Secondly, the present disclosure also adopts a method of data stream identification. In the case where the data stream contains a feature identifier, a rigid pipeline is used to transmit the data stream. This method of data stream identification can distinguish low-latency services from other services based on feature identifiers, thereby giving priority to transmitting low-latency services and improving the transmission efficiency and response speed of low-latency services.

Through the above rigid pipeline configuration and data flow identification method, the present disclosure can solve the problem that the service scheduling method in the related art cannot meet the demand for carrying low-latency services. It can reduce transmission delay, improve the stability and reliability of data transmission, and can give priority to the transmission of low-latency services to meet the demand of low-latency services.

In one embodiment, the characteristic identifier includes GEMPORTID (GEM PORT-ID, GEM port identifier, where GEM is Gigabit-capable passive optical network Encapsulation Method).

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

In an exemplary implementation, for services that need to go through a rigid pipe, a feature identifier is given, and it is agreed that this feature identifier can be identified as a rigid pipe, and the transferability of this feature identifier is guaranteed. That is, on the entire PON+FTTR+WI-FI link, the data flow can be identified as entering a rigid pipe on the FTTR slave device, FTTR master device, and OLT by matching the feature identifier.

FIG3 is a flow chart of a method for transmitting a data stream through a rigid pipe in an upstream direction according to an embodiment of the present disclosure. In one implementation, 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:

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 into the FTTR master device;

Step S302: The FTTR main device receives an upstream data stream, and a rigid pipe is configured between the FTTR main device and the optical line terminal OLT, so that the upstream data flows from the rigid pipe into the optical line terminal OLT.

In an exemplary embodiment, for the uplink direction, the FTTR slave device side allocates different transmission containers (Transmission Container, abbreviated as TCONT) and GEMPORT (GEM port) to identify rigid pipes according to the WI-FI slices of different services received, that is, the ALLOCID and GEMPORTID corresponding to the given rigid pipe are matched to enter 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 according to the matching ALLOCID and GEMPORTID, thereby realizing end-to-end low-latency collaborative transmission from WI-FI to PON in the uplink direction.

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

Through Wi-Fi slicing, network administrators can dynamically divide Wi-Fi network resources and allocate network slices to specific user groups or application scenarios according to needs, thus realizing flexible resource configuration and management. Each slice can be configured with different quality of service (QoS), bandwidth restrictions, security policies, etc. to meet the needs of different users and applications.

FIG4 is a flow chart of a method for transmitting a data stream through a rigid pipe in a downstream direction according to an embodiment of the present disclosure. In one implementation, 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:

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 based on the rigid pipe;

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.

In an exemplary implementation, for 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 by the same service is consistent with the upstream direction, and the rigid pipe in the downstream direction is identified by the GEMPORTID for priority scheduling transmission. On the FTTR slave device to the WI-FI side, different Differentiated Services Code Point (DSCP) values are assigned for priority scheduling according to different service flows identified by different GEMPORTs. In this way, end-to-end low-latency priority scheduling transmission from PON to WI-FI in the downstream direction is achieved.

In one embodiment, 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, the process includes:

The FTTR receives the downstream data flow from the device and assigns a DSCP value to the downstream data flow so that the downstream data flow is sent to the WI-FI station with priority.

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 site,

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 site;

Step S502, the optical line terminal OLT allocates an upstream bandwidth to the FTTR master device based on the second bandwidth request;

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

FIG6 is an example diagram of a method for DBA collaborative scheduling according to an embodiment of the present disclosure. In an exemplary implementation, 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 the data to wait for the DBA to allocate bandwidth after arriving at the FTTR slave device and the FTTR master device, thereby reducing the uplink path delay.

In one implementation, the method further includes a DBA subframe division method, and the DBA subframe division method includes:

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

FIG7 is an example diagram of a method for dividing DBA subframes according to an embodiment of the present disclosure. In an exemplary implementation, as shown in FIG7 , the number of subframes divided into each frame of 125us can be freely selected. For example, subframe 1, subframe 2, subframe 3, subframe 4. Of course, FIG7 is only an example. Each frame of 125us 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 in detail here. And 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 to allocate different bandwidths to different subframes. When the subframe division of one frame in the DBA cycle is determined, the subframe division of the remaining three frames is the same as the first frame.

First, taking 2.5G asymmetric mode, one-byte bandwidth granularity, 125us per frame divided into four subframes, and 100Mbps bandwidth allocation as an example, the calculation method is given and examples are given for uniform and uneven subframe division. Within the subframe, in addition to the burst overhead, the software can configure the corresponding start time and stop time as needed.

If uniform subframe division is considered, the maximum bandwidth that can be allocated per frame of 125us is 19440 bytes, 19440/4＝4860 bytes. In fact, considering the burst overhead, the start time of the first subframe entry is delayed by 50 bytes, so 0, 4860, 9720, and 14580 bytes can be considered as the start time of each subframe division. With 100Mbps bandwidth, the bandwidth allocated per frame of 125us is (100000000/8)/(1000000/125)≈1562 bytes, and 1562/4≈390 bytes are allocated per subframe on average. Therefore, in the case of uniform subframe division, one of the options for uniform division of four subframes is: subframe, 49 to 439 bytes; subframe, 4860 to 5250 bytes; subframe, 9720 to 10110 bytes; subframe, 14580 to 14969 bytes.

If uneven subframe division is considered, the bandwidth allocated to each 125us frame is still 1562 bytes, and the subframes within each frame can be freely allocated. For example, consider that the start time of four subframes is 50, 10000, 11000, and 15000 bytes, and the bandwidth allocated to each subframe is 800, 80, 332, and 350 bytes, respectively. According to the above allocation, the uneven division of the four subframes can be selected as follows: subframe, 50 to 849 bytes; subframe, 10000 to 10079 bytes; subframe, 11000 to 11331 bytes; subframe, 15000 to 15349 bytes.

Secondly, further, considering 100Mbps bandwidth and evenly dividing each frame into four subframes, a subframe division implementation example 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.

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

FIG8 is a flow chart 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. In one implementation, as shown in FIG8 , in a DBA scheduling period, adjusting the number and bandwidth configuration of DBA subframes based on the service type of a data stream includes:

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

Step S802, determining delay and bandwidth based on service type;

Step S803, classifying and prioritizing the delay and bandwidth;

Step S804: adjusting the number and bandwidth configuration of DBA subframes based on the results of classification and priority sorting.

In an exemplary implementation, taking into account 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.

On the one hand, the service type can be determined by identifying the relevant protocol messages. For example, if a Session Initiation Protocol (SIP) message is received, it can be identified as a voice call service; if a multicast join message is received, it can be identified as an Internet Protocol Television (IPTV) video service. On the other hand, the required delay and bandwidth are determined according to the identified service type, and different services are directly classified and prioritized in terms of delay and bandwidth. For example, voice services require higher delay than IPTV, and IPTV requires more bandwidth than voice. According to the characteristics of the service in terms of delay and bandwidth, the DBA subframe division method is adjusted to meet the service requirements in terms of delay and bandwidth. After the bandwidth is allocated, the allocation of different services needs to be recorded to facilitate unified adjustments after the addition of new services.

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

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.

FIG9 is a flow chart 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 implementation, as shown in FIG9 , in the message request reporting stage, 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 identifies the FTTR slave device within the short window period, including:

Step S901, the FTTR master device calculates the 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;

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 time period, so that the FTTR master device can identify the FTTR slave device within the short windowing time period.

FIG. 10 is an example diagram of a method for sending an empty entry after a pre-equalization delay according to an embodiment of the present disclosure, and FIG. 11 is an example diagram of a method for allocating an empty entry first without using a pre-equalization delay according to an embodiment of the present disclosure. In an exemplary implementation, as shown in FIG. 10 and FIG. 11, in the serial number (SN) reporting stage, in order to reduce the impact of windowing on the uplink path delay, the silent windowing is reduced from the original two frames of 250us to a certain period of time within one frame, and the specific time period can be set according to actual conditions. Adjusting the windowing size requires comprehensive consideration of the relationship between the response time of the FTTR slave device, the random delay, and the maximum loop delay between the FTTR master device and the FTTR slave device. Considering that the optical fiber distance between the FTTR master device and the FTTR slave device is x kilometers (km), the maximum random delay is y microseconds (us), the pre-equalization delay in FIG. 10 and the SN request start time in FIG. 11 are zus, and the response time of the FTTR slave device is 35±1us, with a maximum of 36us. Since the optical transmission delay corresponding to 1km is 10us, the optical transmission delay is 10xus; considering that the response delay of the FTTR slave device generally fluctuates by 2us, 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.

Considering that the maximum fiber distance between the FTTR master and the FTTR slave is 1km, and the random delay is 0 to 11us, that is, x=1, y=11, z=12, the maximum loop delay is 36+10=46us, and the silent window is 10+2+11=23us. 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+46us, and a 23us silent window is opened from tz.

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

To summarize, the purpose of the above method is to set the pre-equalization delay and the empty entry in order 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.

In one implementation, 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 identifies the FTTR slave device within the short window period, including:

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

In an exemplary embodiment, as shown in FIG11 , the FTTR master device does not use the pre-equalization delay method, but allocates empty entries first, with the start time being 12us, i.e., t0+12us. Similarly, the earliest time that the FTTR master device receives the SN response is at least t0+46us, and the latest time in the silent window is the same.

To summarize, 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.

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, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present disclosure, 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, magnetic disk, optical disk), and includes a number of instructions for 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.

An embodiment of the present disclosure further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.

In an exemplary embodiment, the above-mentioned computer-readable storage medium may include, but is not limited to: 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, and other media that can store computer programs.

An embodiment of the present disclosure further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

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.

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 herein.

Obviously, those skilled in the art should understand that the above modules or steps of the present disclosure can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that 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 executed in a different order than here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present disclosure is not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present disclosure and is not intended to limit the present disclosure. For those skilled in the art, the present disclosure may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the principles of the present disclosure shall be included in the protection scope of the present disclosure.

Claims (13)

A low-latency communication method based on an all-optical network, comprising: For all-optical network links, rigid pipes are configured on the link consisting of the fiber-to-the-room FTTR slave device and the FTTR master device and the optical line terminal OLT; A data stream is identified, and if the data stream contains a characteristic identifier, the data stream is transmitted through the rigid pipe. The method according to claim 1, wherein the characteristic identifier includes a gigabit passive optical network encapsulation mode port identifier GEMPORTID. The method according to claim 1, wherein, 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; identifying a data stream, and transmitting the data stream through the rigid pipe when the data stream contains a characteristic identifier, comprises: The FTTR slave device receives an uplink data stream sent from a WI-FI site, and a rigid pipe is configured between the FTTR slave device and the FTTR master device so that the uplink data flows from the rigid pipe into the FTTR master device; The FTTR main device receives the upstream data flow, and a rigid pipe is configured between the FTTR main device and the optical line terminal OLT, so that the upstream data flows from the rigid pipe into the optical line terminal OLT. The method according to claim 1, wherein, 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; identifying a data stream, and transmitting the data stream through the rigid pipe when the data stream contains a characteristic identifier, comprises: 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 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. The method according to claim 4, wherein the FTTR master device receives the downstream data stream, and after configuring 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, the method further comprises: The FTTR receives the downstream data stream from the device and allocates 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 site. The method according to claim 3, wherein the method further comprises a method for collaborative scheduling using dynamic bandwidth allocation DBA, wherein the method for collaborative scheduling of DBA comprises: before the FTTR slave device receives an uplink data stream sent from a WI-FI site, 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 site; 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 an upstream bandwidth to the FTTR main device based on the second bandwidth request; The FTTR master device allocates an upstream bandwidth to the FTTR slave device based on the first bandwidth request. The method according to claim 1, wherein the method further comprises a DBA subframe division method, and the DBA subframe division method comprises: In a DBA scheduling period, the number and bandwidth configuration of DBA subframes are adjusted based on the service type of the data flow. 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 flow comprises: Identifying the message type of the data flow to determine the service type; Determining latency and bandwidth based on the service type; classifying and prioritizing said delays and bandwidths; The number and bandwidth configuration of the DBA subframes are adjusted based on the results of the classification and prioritization. The method according to claim 1, wherein the method further comprises a method of using a short window, and the method of setting the short window comprises: During the message request reporting stage, 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 time period. The method according to claim 9, wherein, in the message request reporting stage, 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, comprising: The FTTR master device calculates a pre-equalization delay based on a response time of the FTTR slave device, a random delay between the FTTR master device and the FTTR slave device, and a loop delay between the FTTR master device and the FTTR slave device, and sends a null entry after the pre-equalization delay; The FTTR master device uses the sum of the pre-equalization delay and the delay occupied by the empty entry as the short window time period, so that the FTTR master device can identify the FTTR slave device within the short window time period. The method according to claim 9, wherein, in the message request reporting stage, 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, comprising: The FTTR master device uses the delay occupied by the empty entry as a short window time period, so that the FTTR master device can identify the FTTR slave device within the short window time period. A computer-readable storage medium having a computer program stored therein, wherein the computer program, when executed by a processor, implements the steps of the method described in any one of claims 1 to 11. An electronic device comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the method described in any one of claims 1 to 11 when executing the computer program.