Network resource scheduling method applied to FTTR scene and related device

Abstract

The embodiment of the invention discloses a network resource scheduling method applied to an FTTR scene and a related device. The main gateway is connected with a plurality of slave gateways, and each slave gateway provides air interface resources for the STA in the coverage area. Wherein the first STA connected with the first slave gateway sends a high-priority service, and the second STA connected with the second slave gateway sends a first-priority service. And if the main gateway finds that the high-priority service is subjected to frame loss or congestion and the like according to the transmission quality parameter of the high-priority service, the main gateway sends a message to a second slave gateway to indicate the second slave gateway to reduce uplink air interface resources of the low-priority service. That is to say, the master gateway performs air interface resource scheduling on the plurality of slave gateways according to the actual transmission quality of the service, so that the air interface resource allocation among the plurality of slave gateways is optimized, the uplink air interface resource can be preempted more easily by the high-priority service, the interference of the low-priority service on the transmission of the high-priority service is reduced, and the transmission efficiency of the high-priority service is improved. And the uplink transmission quality of the high-priority service is improved.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a network resource scheduling method and related devices applied to FTTR scenarios. Background Art

[0002] With the emergence of new high-traffic application services such as ultra-high-definition video, higher and higher requirements are placed on the bandwidth, latency and other performance of network communications. In this context, fiber to the room (FTTR) technology came into being. FTTR is a networking technology that lays optical fiber to every room to achieve full network coverage. It can achieve network coverage without dead ends and achieve a gigabit network transmission rate, easily meeting people's network needs in daily life and office. FTTR is usually composed of a master gateway and multiple slave gateways to form a whole-house network.

[0003] Currently, resource allocation based on service priority is usually performed by each slave gateway, which prioritizes each accessed service to ensure that high-priority services are transmitted first. However, in a scenario with multiple slave gateways, it is possible that a high-priority service accessed by a slave gateway and a low-priority service accessed by other slave gateways may occupy channel resources, making it easy for high-priority services to be congested or lose frames, reducing the transmission quality of high-priority services. Summary of the invention

[0004] The embodiment of the present application provides a network resource scheduling method and related devices applied to FTTR scenarios, so that high-priority services can more easily seize uplink air interface resources, reduce the interference of low-priority services on the transmission of high-priority services, and improve the uplink transmission quality of high-priority services.

[0005] In the first aspect, an embodiment of the present application provides a network resource scheduling method applied to an FTTR scenario, and the method applies a master gateway. Among them, the master gateway establishes communication with the first slave gateway and the second slave gateway respectively, and the master gateway receives a high-priority service from the first station (STA) and sent through the first slave gateway, and receives a first low-priority service from the second STA and sent through the second slave gateway. Specifically, the master gateway obtains the uplink transmission quality parameters of the high-priority service sent by the first STA, and determines whether the transmission of the high-priority service has frame loss or congestion based on the uplink transmission quality parameters of the high-priority service. If frame loss or congestion occurs in the transmission of the high-priority service, the master gateway sends a first downlink message to the second slave gateway to schedule network resources for the second slave gateway, wherein the first downlink message is used to instruct the second slave gateway to reduce the uplink air interface resources of the first low-priority service.

[0006] In this embodiment, if the master gateway discovers frame loss or congestion in high-priority services based on the transmission quality parameters of high-priority services, the master gateway sends a message to the second slave gateway to instruct the second slave gateway to reduce the uplink radio resource of low-priority services. Then, high-priority services can more easily preempt the uplink radio resource, and the interference of low-priority services on the transmission of high-priority services is reduced, improving the uplink transmission quality of high-priority services.

[0007] In some possible embodiments, the master gateway obtaining the uplink transmission quality parameters of high-priority services sent by the first STA includes: the master gateway receiving an uplink message sent by the first slave gateway, where the uplink message is used to indicate the frame loss information of high-priority services. That is to say, the first slave gateway can detect the frame loss information of high-priority services from the first STA in real time and report the frame loss information by sending an uplink message to the master gateway, enabling the master gateway to obtain the frame loss information of high-priority services in real time, so as to perform network resource scheduling on the slave gateway as soon as possible, facilitating the retransmission of high-priority services as soon as possible and having better transmission quality.

[0008] In some possible embodiments, the first downlink message is used to instruct the second slave gateway to send a clear to send (CTS) frame with the destination address being the second slave gateway, and this CTS frame can also be referred to as a CTS-to-self frame. The second STA can detect the CTS-to-self frame. After receiving the CTS-to-self frame sent by the second slave gateway, the second STA pauses sending the first low-priority service on the uplink and will no longer preempt the radio resource, reducing the interference on the uplink transmission of high-priority services and improving the retransmission success rate of high-priority services.

[0009] In some possible embodiments, the first downlink message is further used to instruct the second slave gateway to pause sending downlink low-priority services to the second STA. That is to say, the situation where low-priority services occupy the downlink radio resource is also reduced, reducing the interference of low-priority services on the downlink transmission of high-priority services and improving the downlink transmission quality of high-priority services.

[0010] In some possible embodiments, the method further includes: if the master gateway determines that frame loss occurs in the transmission of high-priority services, the master gateway sends a second downlink message to the first slave gateway, and the second downlink message is used to instruct the first slave gateway to send a trigger frame to the first STA, where the trigger frame is used to indicate the retransmission time slot of high-priority services. That is to say, if frame loss occurs in high-priority services, the master gateway will actively notify the first slave gateway to preferentially allocate the uplink retransmission time slot for high-priority services, facilitating the timely retransmission of the frame-lost high-priority services.

[0011] In some possible embodiments, the master gateway obtaining the uplink transmission quality parameter of the high-priority service sent by the first STA includes: the master gateway obtaining the round-trip time (RTT) of the transmission control protocol (TCP) acknowledgment packet of the high-priority service. If the RTT is greater than a second preset value, congestion occurs in the transmission of the high-priority service. Here, a specific implementation manner for determining congestion is provided, which has a good practical effect.

[0012] In some possible embodiments, the master gateway obtaining the uplink transmission quality parameter of the high-priority service sent by the first STA includes: the master gateway obtaining the time interval between two consecutive uplink MAC protocol data units (MPDUs) of the high-priority service. If the transmission time interval between two consecutive uplink MPDUs of the high-priority service is greater than a third preset value, congestion occurs in the transmission of the high-priority service. Here, another specific implementation manner for determining congestion is provided, which expands the implementation manners achievable by this solution.

[0013] In some possible embodiments, the first downlink message is used to indicate at least one of the following information: the first downlink message is used to indicate that the second slave gateway delays sending the downlink TCP acknowledgment packet corresponding to the first low-priority service from the master gateway to the second STA; the first downlink message is used to indicate that the second slave gateway delays sending the uplink TCP acknowledgment packet corresponding to the first low-priority service from the second STA to the master gateway; the first downlink message is used to indicate that the second slave gateway delays sending the downlink data packet of the first low-priority service from the master gateway to the second STA; the first downlink message is used to indicate that the second slave gateway delays sending the uplink data packet of the first low-priority service from the second STA to the master gateway. In this embodiment, the master gateway instructs the second slave gateway to throttle the first low-priority service, so as to facilitate reserving more uplink air interface resources for the high-priority service, which is beneficial to alleviating the congestion of the high-priority service and can effectively reduce the interference of the low-priority service on the transmission of the high-priority service.

[0014] In some possible embodiments, the method further includes at least one of the following: the master gateway delays sending a downlink TCP acknowledgment packet corresponding to the first low-priority service from the server to the second slave gateway; the master gateway delays sending an uplink TCP acknowledgment packet corresponding to the first low-priority service from the second slave gateway to the server; the master gateway delays sending a downlink data packet of the first low-priority service from the server to the second slave gateway; the master gateway delays sending an uplink data packet of the first low-priority service from the second slave gateway to the server. In this embodiment, the master gateway can also actively throttle the first low-priority service, so as to facilitate reserving more uplink radio resources for high-priority services, which is beneficial to alleviating the congestion of high-priority services, can effectively reduce the interference of low-priority services on the transmission of high-priority services, and enriches the implementation manners of this solution.

[0015] In some possible embodiments, the first downlink message is used to instruct the second slave gateway to increase the Enhanced Distributed Channel Access (ECDA) contention window corresponding to the first low-priority service, reducing the possibility of the first low-priority service preempting uplink radio resources, so that high-priority services can obtain a higher transmission priority, which is beneficial to alleviating the congestion of high-priority services.

[0016] In some possible embodiments, the method further includes: the master gateway receives a second low-priority service from the first STA and sent through the first slave gateway; if the master gateway determines that the transmission of the high-priority service has frame loss or congestion according to the uplink transmission quality parameter of the high-priority service, the master gateway sends a third downlink message to the first slave gateway, and the third downlink message is used to instruct the first slave gateway to reduce the uplink radio resources of the second low-priority service. That is to say, in a scenario where the first slave gateway is associated with both low-priority services and high-priority services, the master gateway can also notify the first slave gateway to reduce the uplink radio resources of the low-priority service, further ensuring that high-priority services can more easily preempt uplink radio resources, reducing the interference of low-priority services on the transmission of high-priority services, and improving the uplink transmission quality of high-priority services.

[0017] In a second aspect, an embodiment of the present application provides a master gateway, which includes a processing unit and a transceiver unit. The transceiver unit is configured to: receive high-priority services sent from a first STA and forwarded by a first slave gateway, and first low-priority services sent from a second STA and forwarded by a second slave gateway. The processing unit is configured to: obtain the uplink transmission quality parameters of the high-priority services sent by the first STA. If the processing unit determines that frame loss or congestion occurs in the transmission of the high-priority services based on the uplink transmission quality parameters of the high-priority services, the transceiver unit is configured to: send a first downlink message to the second slave gateway, where the first downlink message is used to instruct the second slave gateway to reduce the uplink radio resources allocated to the first low-priority services.

[0018] In some possible implementation manners, the transceiver unit is configured to receive an uplink message sent by the first slave gateway, where the uplink message is used to indicate the frame loss information of the high-priority services.

[0019] In some possible implementation manners, the first downlink message is used to instruct the second slave gateway to send a CTS frame with the destination address being the second slave gateway, and the CTS frame is used to instruct the second STA to suspend sending the first low-priority services.

[0020] In some possible implementation manners, the first downlink message is further used to instruct the second slave gateway to suspend sending downlink low-priority services to the second STA.

[0021] In some possible implementation manners, if the processing unit determines that frame loss occurs in the transmission of the high-priority services, the transceiver unit is further configured to: send a second downlink message to the first slave gateway, where the second downlink message is used to instruct the first slave gateway to send a trigger frame to the first STA, and the trigger frame is used to indicate the retransmission time slot of the high-priority services.

[0022] In some possible implementation manners, the processing unit is specifically configured to obtain the RTT of the TCP acknowledgment packet of the high-priority services; if the RTT is greater than a first preset value, it indicates that congestion occurs in the transmission of the high-priority services.

[0023] In some possible implementation manners, the processing unit is specifically configured to obtain the time interval between two consecutive uplink MPDUs of the high-priority services; if the transmission time interval between two consecutive uplink MPDUs of the high-priority services is greater than a second preset value, it indicates that congestion occurs in the transmission of the high-priority services.

[0024] In some possible implementation manners, the first downlink message is used to indicate at least one of the following information: The first downlink message is used to indicate that the second slave gateway delays sending a downlink TCP acknowledgment packet corresponding to the first low-priority service from the master gateway to the second STA; The first downlink message is used to indicate that the second slave gateway delays sending an uplink TCP acknowledgment packet corresponding to the first low-priority service from the second STA to the master gateway; The first downlink message is used to indicate that the second slave gateway delays sending a downlink data packet of the first low-priority service from the master gateway to the second STA; The first downlink message is used to indicate that the second slave gateway delays sending an uplink data packet of the first low-priority service from the second STA to the master gateway.

[0025] In some possible implementation manners, the transceiver unit is further configured to perform at least one of the following processes: delaying sending a downlink TCP acknowledgment packet corresponding to the first low-priority service from the server to the second slave gateway; delaying sending an uplink TCP acknowledgment packet corresponding to the first low-priority service from the second slave gateway to the server; delaying sending a downlink data packet of the first low-priority service from the server to the second slave gateway; delaying sending an uplink data packet of the first low-priority service from the second slave gateway to the server.

[0026] In some possible implementation manners, the first downlink message is used to indicate that the second slave gateway increases the EDCA contention window corresponding to the first low-priority service.

[0027] In some possible implementation manners, the transceiver unit is further configured to receive a second low-priority service from the first STA and sent through the first slave gateway. If the processing unit determines that there is a frame loss or congestion in the uplink transmission of the high-priority service according to the uplink transmission quality parameter of the high-priority service, the transceiver unit is further configured to: send a third downlink message to the first slave gateway, and the third downlink message is used to indicate that the first slave gateway reduces the uplink air interface resources of the second low-priority service.

[0028] In a third aspect, an embodiment of the present application provides an FTTR system, and the FTTR system includes a master gateway and a plurality of slave gateways introduced in any implementation manner of the second aspect, and the master gateway communicates with the plurality of slave gateways respectively.

[0029] In a fourth aspect, an embodiment of the present application provides a chip, and the chip includes a processor, and the processor is configured to execute the method introduced in any implementation manner of the first aspect.

[0030] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, and a computer program is stored on the computer-readable storage medium. When the computer program is executed by a computer, the method introduced in any implementation manner of the first aspect is implemented.

[0031] As can be seen from the above technical solutions, the embodiments of the present application have the following advantages:

[0032] In the embodiments of the present application, the master gateway is connected to multiple slave gateways, and each slave gateway provides air interface resources for STAs within its coverage area. Among them, the first STA connected to the first slave gateway sends high-priority services, and the second STA connected to the second slave gateway sends low-priority services. If the master gateway discovers that there are frame losses or congestion in the high-priority services according to the transmission quality parameters of the high-priority services, the master gateway sends a message to the second slave gateway to instruct the second slave gateway to reduce the uplink air interface resources of the low-priority services. That is to say, the master gateway will perform air interface resource scheduling on multiple slave gateways according to the actual transmission quality of the services, optimize the air interface resource allocation among multiple slave gateways, so that the high-priority services can more easily preempt the uplink air interface resources, and reduce the interference of low-priority services on the transmission of high-priority services, thereby improving the uplink transmission quality of high-priority services. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 It is a schematic diagram of the system architecture of FTTH;

[0034] Figure 2 It is a schematic diagram of the system architecture of FTTR;

[0035] Figure 3 It is the first flowchart of the network resource scheduling method applied to the FTTR scenario in the embodiments of the present application;

[0036] Figure 4 It is the second flowchart of the network resource scheduling method applied to the FTTR scenario in the embodiments of the present application;

[0037] Figure 5 It is the third flowchart of the network resource scheduling method applied to the FTTR scenario in the embodiments of the present application;

[0038] Figure 6 It is the fourth flowchart of the network resource scheduling method applied to the FTTR scenario in the embodiments of the present application;

[0039] Figure 7 It is a schematic diagram of an application scenario of the network resource scheduling method applied to the FTTR scenario in the embodiments of the present application;

[0040] Figure 8 It is a schematic diagram of a structure of the master gateway in the embodiments of the present application;

[0041] Figure 9 It is another schematic diagram of a structure of the master gateway in the embodiments of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0042] The embodiments of the present application provide a network resource scheduling method and related devices applied to the FTTR scenario. The master gateway performs air interface resource scheduling on multiple slave gateways according to the actual transmission quality of services, optimizes the air interface resource allocation among the multiple slave gateways, enables high-priority services to more easily preempt uplink air interface resources, reduces the interference of low-priority services to the transmission of high-priority services, and improves the uplink transmission quality of high-priority services.

[0043] It should be noted that the terms "first", "second", etc. in the specification, claims and above-mentioned drawings of the present application are used to distinguish similar objects, rather than to limit a specific order or sequence. It should be understood that the above terms can be interchanged under appropriate circumstances, so that the embodiments described in the present application can be implemented in an order other than that described in the present application. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or are inherent to these processes, methods, products or devices.

[0044] Figure 1 It is a schematic diagram of the system architecture of FTTH. The optical line terminal (OLT) is connected to the upper-layer network-side devices (such as switches, routers, etc.), and is connected to one or more optical distribution networks (ODNs) at the lower layer. The ODN includes a passive optical splitter for optical power distribution, a backbone optical fiber connected between the passive optical splitter and the OLT, and a branch optical fiber connected between the passive optical splitter and the ONU. When transmitting data downstream, the ODN transmits the downstream data of the OLT to each optical network unit (ONU) through the splitter, and the ONU selectively receives the downstream data carrying its own identifier. When transmitting data upstream, the ODN combines the optical signals sent by N ONUs into one optical signal and transmits it to the OLT. The ONU provides a user-side interface for the OAN and is also connected to the ODN. If the ONU also provides user port functions, such as providing an Ethernet user port or a plain old telephone service (POTS) user port, it is called an optical network termination (ONT).

[0045] Based on FTTH, to solve the problem of WIFI coverage in the home network, the optical fiber can be further extended into the household rooms. Install an ONU inside the room, which reduces the distance between the user terminal and the ONU and improves the signal quality. This application scenario is called FTTR.

[0046] Figure 2 It is a schematic diagram of the system architecture of FTTR. The FTTR network and the FTTH network can be regarded as two-level PON systems. The OLT in the first-level PON system (FTTH) is deployed in the central computer room, and the ONU is deployed in the home information box. The master gateway in the second-level PON system (FTTR) can replace the ONU in FTTH and be deployed in the home information box. This master gateway has similar functions to the OLT in the FTTH scenario in the FTTR scenario, and at the same time, this master gateway can also have similar functions to the ONU in the FTTH scenario. That is to say, the master gateway in FTTR is a device that combines the functions of OLT and ONU and can be used as a network device that plays a connecting role between FTTH and FTTR. The slave gateways in FTTR can be deployed in each room of the home and are used to connect to the user terminal. This slave gateway and the ONU in FTTH are essentially the same type of network device. The difference is that the ONU in FTTH is generally deployed in the information box and there is usually an access point (AP) between it and the user terminal. In FTTR, the slave gateway enters each room and this slave gateway also has the function of an AP and can directly perform a WiFi connection with the user terminal. For the convenience of introduction, the user terminal will be uniformly referred to as a station (STA) hereinafter, and each STA performs service transmission with the master gateway through the connected slave gateway.

[0047] It should be understood that multiple slave gateways can be deployed in FTTR, and each slave gateway is connected to the branch port of the corresponding optical splitter. Moreover, the number of optical splitters in FTTR is not limited in this application, and the master gateway is connected to each optical splitter in a cascaded manner. The master gateway can realize the unified management and configuration of all slave gateways. For example, as the control center of the home network, the master gateway can configure the WiFi hotspots throughout the house as a unified network, optimize the channels to avoid interference, and can control the roaming and handover of the user terminal, reduce the network handover time, and improve the user experience.

[0048] Next, the network resource scheduling method applied to the FTTR scenario provided by the embodiments of this application will be introduced. Figure 3 It is the first process schematic diagram of the network resource scheduling method applied to the FTTR scenario in the embodiments of this application. As Figure 3As shown in the figure, the network resource scheduling method applied to the FTTR scenario includes the following steps. It should be understood that the STA sending information or data to the slave gateway and the slave gateway sending information or data to the master gateway is called uplink transmission, and the master gateway sending information or data to the slave gateway and the slave gateway sending information or data to the STA is called downlink transmission. The network resources used for transmitting services between the master gateway and the slave gateway are called optical link resources, and the network resources used for transmitting services between the slave gateway and the STA are called air interface resources.

[0049] 101. Transmit high-priority services between slave gateway 1 and the master gateway.

[0050] 102. Transmit low-priority service 1 between slave gateway 2 and the master gateway.

[0051] It should be noted that the FTTR scenario involved in this application includes a master gateway and multiple slave gateways, and each slave gateway accesses at least one STA. In this FTTR scenario, at least one STA accessed by a slave gateway is transmitting high-priority services. Here, the STA transmitting high-priority services is denoted as STA1, the slave gateway accessed by STA1 is denoted as slave gateway 1, and STA1 transmits high-priority services to the master gateway through slave gateway 1. In this FTTR scenario, there is also at least one STA accessed by a slave gateway that is transmitting low-priority services. In some possible cases, the number of low-priority services is large, and the low-priority services will preempt most of the air interface resources, resulting in less air interface resources available for high-priority services and affecting the transmission quality of high-priority services. The embodiments of this application do not limit the number of slave gateways and STAs transmitting low-priority services. For the sake of easy introduction, the STA transmitting low-priority service 1 is denoted as STA2, the slave gateway accessed by STA2 is denoted as slave gateway 2, and STA2 transmits low-priority service 1 to the master gateway through slave gateway 2. The following mainly introduces the way for the master gateway to perform network resource scheduling on slave gateway 2. For other slave gateways transmitting low-priority services, the master gateway performs network resource scheduling on them in a similar way, which will not be elaborated here one by one.

[0052] 103. The master gateway obtains the uplink transmission quality parameters of high-priority services.

[0053] In the embodiments of this application, the quality of high-priority service transmission can be reflected by various different scenarios. For example, if high-priority services experience frame loss or congestion, it indicates that the transmission quality of high-priority services is poor. For different scenarios, the detection methods of uplink transmission quality parameters will also vary. The following will detail the specific implementation methods for the master gateway to obtain the uplink transmission quality parameters of high-priority services for different scenarios.

[0054] 104. The master gateway determines whether high-priority services have experienced frame loss or congestion. If so, execute step 105.

[0055] 105. The master gateway sends a downlink message 1 to the slave gateway 2.

[0056] If the master gateway detects frame loss or congestion in the high-priority service associated with the slave gateway 1, it indicates that the uplink radio resources that can be preempted by this high-priority service are insufficient. Without changing the overall uplink radio resources, it is necessary to reduce the uplink radio resources preempted by the low-priority service. This downlink message 1 is used to instruct the slave gateway 2 to reduce the uplink radio resources of the low-priority service 1, so that the slave gateway 1 can provide more uplink radio resources for the high-priority service, and the high-priority service can more easily preempt the uplink radio resources, which is beneficial to ensuring the timeliness and reliability of the high-priority service retransmission and also beneficial to alleviating the congestion of the high-priority service.

[0057] 106. The slave gateway 2 reduces the uplink radio resources of the low-priority service 1.

[0058] It should be noted that the embodiments of the present application provide multiple implementation methods for reducing the uplink radio resources of low-priority services for different scenarios, which will be introduced in detail below.

[0059] 107. The master gateway sends a downlink message 2 to the slave gateway 1.

[0060] In some possible scenarios, in addition to associating with high-priority services, the slave gateway 1 also associates with low-priority services. For example, the slave gateway 1 may also transmit the low-priority service 2 to the master gateway. Therefore, if the master gateway detects frame loss or congestion in the high-priority service associated with the slave gateway 1, it will send a downlink message 2 to the slave gateway 1. This downlink message 2 is used to instruct the slave gateway 1 to reduce the uplink radio resources of the low-priority service 2. So that the high-priority service can more easily preempt the uplink radio resources.

[0061] 108. The slave gateway 1 reduces the uplink radio resources of the low-priority service 2.

[0062] It should be noted that the specific implementation method of step 108 is similar to that of step 106, and reference can be made to the detailed introduction of the implementation method of step 106 below.

[0063] Figure 4 This is the second process schematic diagram of the network resource scheduling method applied to the FTTR scenario in the embodiments of the present application. As Figure 4 shown, this method is applied to the scenario where frame loss occurs in high-priority services, and the method specifically includes the following steps.

[0064] 201. STA1 sends a high-priority service.

[0065] It should be understood that the high-priority services sent by STA1 will be transmitted to the main gateway through the secondary gateway 1. That is to say, the high-priority services sent by STA1 will first be transmitted to the secondary gateway 1, and then the secondary gateway 1 will send the high-priority services to the main gateway.

[0066] 202. Obtain the frame loss information of the high-priority services from the secondary gateway 1.

[0067] The secondary gateway 1 will perform real-time detection on the received high-priority services to determine the frame loss information of the high-priority services. In a possible implementation, each uplink data packet pair of the high-priority services sent by STA1 has a corresponding sequence number, and these sequence numbers are consecutive. If the secondary gateway 1 finds a discontinuity in the sequence numbers by identifying the sequence numbers of the uplink data packets, it means that frame loss has occurred in the high-priority services. Here, the frame loss information can be the sequence numbers corresponding to the uplink data packets with frame loss.

[0068] 203. The secondary gateway 1 sends an uplink message 1 to the main gateway.

[0069] Among them, the uplink message 1 carries the frame loss information of the high-priority services obtained from the secondary gateway. It should be understood that if there is no frame loss in the actual high-priority services, this frame loss information can also indicate no frame loss. It should be understood that the secondary gateway 1 will also send a block acknowledge (BA) frame to STA1 according to the frame loss information to inform STA1 of the sequence numbers corresponding to the uplink data packets with frame loss, facilitating STA1 to retransmit the uplink data packets with frame loss later.

[0070] 204. The main gateway determines whether frame loss has occurred in the high-priority services. If so, step 205 is executed.

[0071] It should be noted that this application does not limit the specific rules for the main gateway to determine frame loss in high-priority services. For example, as long as there is frame loss in one uplink data packet of a high-priority service, it is considered that frame loss has occurred in the high-priority service; for example, when the number of uplink data packets with frame loss in a high-priority service reaches a threshold, it is considered that frame loss has occurred in the high-priority service. In some possible implementations, it can also be determined by the secondary gateway 1 whether frame loss has occurred in the high-priority services, and the judgment result is sent to the main gateway through the uplink message 1. If the main gateway determines that frame loss has occurred in the high-priority services according to the uplink message 1, step 205 is executed.

[0072] 205. The main gateway sends a downlink message 1 to the secondary gateway 2.

[0073] If the master gateway determines that frame loss occurs in high-priority services, the master gateway will schedule slave gateway 2. Specifically, the master gateway instructs slave gateway 2 to send a clear to send (CTS) frame with the destination address being slave gateway 2 by sending a downlink message 1 to slave gateway 2. The CTS frame may also be referred to as a CTS-to-self frame. The duration information included in the CTS-to-self frame indicates the time when the air interface resources are about to be occupied. The STA that can detect the CTS-to-self frame will update its own network allocation vector (NAV) timer to avoid conflicts. The duration of the NAV timer is set to the duration of the silent interval, that is, the CTS-to-self frame can be used to reserve air interface resources.

[0074] 206. Send a CTS-to-self frame from gateway 2.

[0075] Slave gateway 2 sends a CTS-to-self frame according to the instruction of downlink message 1 sent by the master gateway, and STA2 can also detect the CTS-to-self frame.

[0076] 207. STA2 suspends sending uplink low priority service 1.

[0077] After STA2 receives the CTS-to-self frame sent from gateway 2, it sets the NAV timer and suspends sending the uplink low-priority service 1 within the set time. It will no longer occupy air interface resources, reduce interference with the uplink transmission of high-priority services, and improve the retransmission success rate of high-priority services.

[0078] 208. The gateway 2 stops sending the downlink low priority service 1.

[0079] In some possible implementations, the downlink message 1 sent by the master gateway to the slave gateway 2 is also used to instruct the slave gateway 2 to suspend sending downlink low-priority service 1, thereby reducing the situation where low-priority service 1 occupies downlink air interface resources, reducing the interference of low-priority service 1 on downlink transmission of high-priority service, and improving the downlink transmission quality of high-priority service.

[0080] 209. The master gateway sends a downlink message 3 to the slave gateway 1.

[0081] It should be noted that if the master gateway determines that a high priority service has frame loss, the master gateway will schedule slave gateway 1 to retransmit the high priority service. Specifically, the master gateway sends a downlink message 3 to slave gateway 1 to instruct slave gateway 1 to send a trigger frame to STA1.

[0082] 210. A trigger frame is sent from gateway 1 to STA1.

[0083] The gateway 1 sends a trigger frame to the STA1 according to the indication of the downlink message 3 sent by the master gateway, which is used to indicate the retransmission time slot for high-priority services, so that the STA1 can retransmit the lost-frame high-priority services in a timely manner.

[0084] 211. The STA1 retransmits the high-priority service.

[0085] Specifically, the STA1 retransmits the lost-frame high-priority service according to the retransmission time slot allocated for it by the gateway 1, and the retransmitted high-priority service is transmitted to the master gateway through the gateway 1.

[0086] Figure 5 This is the third flowchart of the network resource scheduling method applied to the FTTR scenario in the embodiments of the present application. As Figure 5 shown, this method is applied to the scenario where high-priority services are congested, and the method specifically includes the following steps.

[0087] 301. The master gateway determines whether high-priority services are congested. If so, step 302 is executed.

[0088] In a possible implementation manner, the master gateway can obtain the round-trip time (RTT) of high-priority services. If the RTT of high-priority services is greater than the first preset value, it indicates that the high-priority services sent by the STA1 to the gateway 1 are congested. As an example, the STA1 establishes a Transmission Control Protocol (TCP) connection with the upper-layer server, and the master gateway and the gateway 1 are responsible for forwarding the TCP packets between the STA1 and the upper-layer server. The master gateway records the time t1 when forwarding the downlink TCP acknowledgment packet corresponding to the high-priority service, and the master gateway records the time t2 when forwarding the uplink TCP acknowledgment packet corresponding to the high-priority service. The RTT of the high-priority service is calculated by t2 - t1. As another example, the gateway 1 can also calculate the RTT of the high-priority service in a similar manner and report it to the master gateway. The gateway 1 records the time t3 when forwarding the downlink TCP acknowledgment packet corresponding to the high-priority service, and the gateway 1 records the time t4 when forwarding the uplink TCP acknowledgment packet corresponding to the high-priority service. The RTT of the high-priority service is calculated by t4 - t3. Although the RTTs of the high-priority services recorded by the gateway 1 and the master gateway are different, different preset values can be configured for different situations as the basis for determining whether high-priority services are congested.

[0089] In another possible implementation, the master gateway can obtain the transmission time interval between two consecutive uplink MAC Protocol Data Units (MPDUs) of high-priority services. If the transmission time interval between two consecutive uplink MPDUs of high-priority services is greater than a second preset value, it indicates that congestion occurs in the high-priority services sent by STA1 to the slave gateway 1. As an example, when the slave gateway 1 receives an uplink MPDU of a high-priority service, it records the time t1. When the slave gateway 1 receives the next uplink MPDU of the high-priority service, it records the time t2. t2 - t1 is the transmission time interval between two consecutive uplink MPDUs of the high-priority service. The slave gateway 1 reports the transmission time interval between two consecutive uplink MPDUs of the high-priority service to the master gateway. As another example, the master gateway can also calculate the transmission time interval between two consecutive uplink MPDUs of the high-priority service in a similar manner. When the master gateway receives an uplink MPDU of a high-priority service, it records the time t3. When the master gateway receives the next uplink MPDU of the high-priority service, it records the time t4. t4 - t3 is the transmission time interval between two consecutive uplink MPDUs of the high-priority service.

[0090] 302. The master gateway sends a downlink message 1 to the slave gateway 2.

[0091] If the master gateway determines that congestion occurs in the high-priority services, the master gateway will schedule the slave gateway 2. Specifically, the master gateway instructs the slave gateway 2 to perform at least one of the following steps 303 to 306 by sending a downlink message 1 to the slave gateway 2, so as to smoothly reduce the speed of the low-priority service 1, thereby facilitating reserving more uplink air interface resources for the high-priority services, being beneficial to alleviating the congestion situation of the high-priority services, and effectively reducing the interference of the low-priority services on the transmission of the high-priority services.

[0092] 303. The slave gateway 2 delays sending a downlink TCP acknowledgment packet of the low-priority service 1 to STA2.

[0093] 304. The slave gateway 2 delays sending an uplink TCP acknowledgment packet of the low-priority service 1 to the master gateway.

[0094] It should be understood that STA2 will first establish a TCP connection with the upper-layer server. The master gateway and the slave gateway 2 are responsible for forwarding the TCP packets between STA2 and the upper-layer server. Based on the established TCP connection, STA2 performs the uplink and downlink transmissions of low-priority service 1. The transmission rate of TCP packets = (TCP window size / RTT of TCP packets) × Maximum Segment Size (MSS). When the RTT of TCP packets increases, the transmission rate of TCP packets also decreases. Then, the slave gateway 2 can throttle the TCP service by delaying the sending of downlink TCP acknowledgment packets or delaying the sending of uplink TCP acknowledgment packets, which is equivalent to throttling low-priority service 1.

[0095] 305. The slave gateway 2 delays sending the downlink data packets of low-priority service 1 to STA2.

[0096] 306. The slave gateway 2 delays sending the uplink data packets of low-priority service 1 to the master gateway.

[0097] It should be understood that different from the above steps 303 and 304, the slave gateway 2 can also directly throttle low-priority service 1 by delaying the sending of downlink data packets or uplink data packets of low-priority service 1.

[0098] It should be noted that for the above steps 303 to 306, the master gateway can determine the specific duration of delay in any of the steps 303 to 306 according to the actual congestion degree of high-priority services, and notify the slave gateway 2 to execute through downlink message 1.

[0099] 307. The slave gateway 2 increases the Enhanced Distributed Channel Access (ECDA) contention window corresponding to low-priority service 1.

[0100] In some possible implementation manners, the downlink message 1 sent by the master gateway to the slave gateway 2 is also used to instruct the slave gateway 2 to increase the ECDA contention window corresponding to low-priority service 1. In this way, the possibility of low-priority service 1 preempting the uplink air interface resources is reduced, so that high-priority services can obtain a higher transmission priority, which is beneficial to alleviating the congestion of high-priority services.

[0101] Figure 6 This is the fourth process schematic diagram of the network resource scheduling method applied to the FTTR scenario in the embodiments of the present application. As Figure 6 shown, this method is applied to the scenario where high-priority services are congested, different from the above Figure 5 shown embodiments, Figure 6The illustrated embodiment mainly throttles the low-priority service 1 through the master gateway. The method specifically includes the following steps.

[0102] 401. The master gateway determines whether there is congestion in the high-priority service. If so, at least one of the following steps 402 to 405 is executed.

[0103] It should be understood that the specific implementation of step 401 is similar to that of the above step 301, and will not be elaborated here.

[0104] 402. The master gateway delays sending the downlink TCP acknowledgment packet of the low-priority service 1 to the slave gateway 2.

[0105] 403. The master gateway delays sending the uplink TCP acknowledgment packet of the low-priority service 1 to the server.

[0106] 404. The master gateway delays sending the downlink data packet of the low-priority service 1 to the slave gateway 2.

[0107] 405. The master gateway delays sending the uplink data packet of the low-priority service 1 to the server.

[0108] It should be noted that steps 402 to 405 of the embodiment of the present application are similar to steps 303 to 306 of the above Figure 5 illustrated embodiment, except that the execution entity changes from the slave gateway 2 to the master gateway. The specific description can refer to steps 303 to 306 and will not be elaborated here. It should be understood that in practical applications, Figure 5 the illustrated embodiment can also be combined with Figure 6 the illustrated embodiment, that is to say, if the master gateway determines that there is congestion in the high-priority service, Figure 5 steps 302 to 307 of the illustrated embodiment and Figure 6 steps 402 to 405 of the illustrated embodiment can all be executed.

[0109] It should be noted that the above embodiments only provide some examples of the resource scheduling method for high-priority service frame loss and congestion. In practical applications, other methods can also be used to perform resource scheduling for high-priority service frame loss and congestion. For example, for the scenario of high-priority service frame loss introduced above, steps 302 to 307 or steps 402 to 405 can also be executed to ensure the timeliness and reliability of high-priority service retransmission. Another example is that for the scenario of high-priority service congestion introduced above and Figure 4 and Figure 5 and Figure 6 steps 205 - 207 can also be executed to relieve the congestion of high-priority services.

[0110] A possible application scenario is provided below in combination with the introduction of the above embodiments. Figure 7 This is a schematic diagram of an application scenario of the network resource scheduling method applied to the FTTR scenario in the embodiment of the present application. As Figure 7 shown, this FTTR scenario includes a main gateway, slave gateways 1 to 4, and each slave gateway accesses at least one STA. Among them, two STAs accessing slave gateway 1 respectively transmit high-priority services and low-priority services, and the STAs accessing slave gateways 2 to 4 all transmit low-priority services. The uplink services sent by each STA are sent to the main gateway through the respective slave gateways to which they are connected. In order to preferentially ensure the transmission quality of high-priority services, the main gateway can obtain the transmission quality parameters of high-priority services in real time and determine whether there are dropped frames or congestion in high-priority services. If the main gateway finds that there are dropped frames or congestion in high-priority services, the main gateway will schedule each slave gateway associated with low-priority services, that is, the main gateway will send a downlink message to each slave gateway associated with low-priority services to instruct each slave gateway to reduce the uplink air interface resources of the low-priority services associated with it. For example, the slave gateway can notify the corresponding STA to suspend sending uplink data packets of low-priority services; for another example, the slave gateway can also smoothly reduce the speed of low-priority services. Thus, it can ensure that high-priority services can be preferentially transmitted, reduce the interference of low-priority services on high-priority services, and improve the transmission quality of high-priority services.

[0111] Figure 8 This is a schematic diagram of the structure of the main gateway in the embodiment of the present application. As Figure 8 shown, the main gateway includes: a processing unit 501 and a transceiver unit 502. The transceiver unit 502 is used to perform the operations of data or message transceiver of the main gateway in any of the embodiments shown above Figures 3 to 6 shown, and the processing unit 501 is used to perform other operations of the main gateway except for the transceiver operations in any of the embodiments shown above Figures 3 to 6 shown. It should be understood that the main gateway provided in the embodiment of the present application can also be implemented in other ways. For example, the unit division in the above main gateway is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system. In addition, each functional unit in various embodiments of the present application can be integrated in a processing unit, or can be individual independent physical units, or two or more functional units can be integrated in a processing unit. The above integrated units can be implemented in the form of hardware or in the form of software functional units.

[0112] Figure 9 This is another schematic diagram of the structure of the main gateway in the embodiment of the present application. As Figure 9As shown in the figure, the main gateway includes a processor 601 and an interface circuit 602. The interface circuit 602 can be a transceiver or an input / output interface. The interface circuit 602 is configured to receive signals from other devices outside the main gateway and transmit them to the processor 601, or to send signals from the processor 601 to other devices outside the main gateway. The processor 601 is configured to execute the other operations of the main gateway in any of the embodiments shown above Figures 3 to 6 except for the transceiver operations. Optionally, the main gateway may further include a memory 603, where the memory 603 is configured to store program instructions and data.

[0113] The embodiment of the present application further provides a chip. The chip integrates a circuit for implementing the functions of the above-mentioned processor 601 and one or more interfaces. As an example, the chip integrates a memory. As another example, when the chip does not integrate a memory, it can be connected to an external memory through an interface. The chip can complete the method steps of any one or more of the foregoing embodiments. Alternatively, the chip implements the actions performed by the data processing device in the above embodiments according to the program code stored in the memory.

[0114] The embodiment of the present application further provides a computer-readable storage medium, including a program or instructions. When the program or instructions are run on a computer, the method executed by the processor 601 in the above method embodiments is implemented.

[0115] It should be understood that the processor mentioned in the embodiments of the present application can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented by software, the processor can be a general-purpose processor that implements by reading the software code stored in the memory.

[0116] As an example, the processor in the embodiments of the present application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor can be a microprocessor or any conventional processor.

[0117] In embodiments of the present application, the memory may be a random access memory (RAM), a flash memory, a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), a register, a hard disk, a removable hard disk, a CD-ROM, or any other form of storage medium well-known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and the storage medium may be located in an ASIC. Additionally, the ASIC may be located in a network device or a terminal device. Of course, the processor and the storage medium may also exist as discrete components in a network device or a terminal device.

[0118] In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.

[0119] When implemented using hardware, the method provided by the embodiments of the present application may be implemented without reading software code or instructions. For example, it may be implemented by a CPU, a DSP, an ASIC, an FPGA, other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.

[0120] When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are executed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a terminal device, or other programmable devices. The computer program or instructions may be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer-readable storage medium may be any available medium that the computer can access or a data storage device such as a server integrating one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a DVD; or it may be a semiconductor medium, such as a solid state disk (SSD).

[0121] Finally, it should be noted that the above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims described above.

Claims

1. A network resource scheduling method applied to the Fiber to the Room (FTTR) scenario, characterized in that, Including: The main gateway receives high-priority services from the first station STA and forwards them through the first slave gateway; The main gateway receives the first low-priority service from the second STA and forwards it through the second slave gateway; The main gateway obtains the uplink transmission quality parameters of the high-priority service; If the main gateway determines that frame loss or congestion occurs in the transmission of the high-priority service according to the uplink transmission quality parameters of the high-priority service, the main gateway sends a first downlink message to the second slave gateway, and the first downlink message is used to instruct the second slave gateway to reduce the uplink radio resource of the first low-priority service.

2. The method according to claim 1, wherein The main gateway obtains the uplink transmission quality parameters of the high-priority service sent by the first STA, including: the main gateway receives an uplink message sent by the first slave gateway, and the uplink message is used to indicate the frame loss information of the high-priority service.

3. The method according to claim 2, wherein The first downlink message is used to instruct the second slave gateway to send a Clear to Send (CTS) frame with the destination address being the second slave gateway, and the CTS frame is used to instruct the second STA to suspend sending the first low-priority service.

4. The method according to claim 2 or 3, characterized in that, The first downlink message is also used to instruct the second slave gateway to suspend sending the downlink low-priority service to the second STA.

5. The method according to any one of claims 2 to 4, characterized in that The method further includes: If the main gateway determines that frame loss occurs in the transmission of the high-priority service, the main gateway sends a second downlink message to the first slave gateway, and the second downlink message is used to instruct the first slave gateway to send a trigger frame to the first STA, and the trigger frame is used to indicate the retransmission time slot of the high-priority service.

6. The method according to claim 1, characterized in that, The main gateway obtains the uplink transmission quality parameters of the high-priority service sent by the first STA, including: the main gateway obtains the Round-Trip Time (RTT) of the Transmission Control Protocol (TCP) acknowledgment packet of the high-priority service. If the RTT is greater than the first preset value, congestion occurs in the transmission of the high-priority service.

7. The method according to claim 1, characterized in that, The main gateway obtains the uplink transmission quality parameters of the high-priority service sent by the first STA, including: the main gateway obtains the time interval between two consecutive uplink MAC Protocol Data Units (MPDUs) of the high-priority service. If the transmission time interval between two consecutive uplink MPDUs of the high-priority service is greater than the second preset value, congestion occurs in the transmission of the high-priority service.

8. The method according to claim 6 or 7, characterized in that, The first downlink message is used to indicate at least one of the following information: The first downlink message is used to instruct the second slave gateway to delay sending the downlink TCP acknowledgment packet corresponding to the first low-priority service from the main gateway to the second STA; The first downlink message is used to instruct the second slave gateway to delay sending the uplink TCP acknowledgment packet corresponding to the first low-priority service from the second STA to the main gateway; The first downlink message is used to instruct the second slave gateway to delay sending the downlink data packet of the first low-priority service from the main gateway to the second STA; The first downlink message is used to instruct the second slave gateway to delay sending the uplink data packets of the first low-priority service from the second STA to the master gateway.

9. The method according to any one of claims 6 to 8, characterized in that, The method further includes at least one of the following: The master gateway delays sending the downlink TCP acknowledgment packet corresponding to the first low-priority service from the server to the second slave gateway; The master gateway delays sending the uplink TCP acknowledgment packet corresponding to the first low-priority service from the second slave gateway to the server; The master gateway delays sending the downlink data packets of the first low-priority service from the server to the second slave gateway; The master gateway delays sending the uplink data packets of the first low-priority service from the second slave gateway to the server.

10. The method according to any one of claims 6 to 9, characterized in that, The first downlink message is used to instruct the second slave gateway to increase the Enhanced Distributed Channel Access (EDCA) contention window corresponding to the first low-priority service.

11. The method according to any one of claims 1 to 10, characterized in that, The method further includes: The master gateway receives the second low-priority service from the first STA and sent through the first slave gateway; If the master gateway determines that there is frame loss or congestion in the transmission of the high-priority service according to the uplink transmission quality parameter of the high-priority service, the master gateway sends a third downlink message to the first slave gateway, and the third downlink message is used to instruct the first slave gateway to reduce the uplink radio resource of the second low-priority service.

12. A main gateway, characterized in that, Including: A processing unit and a transceiver unit; The transceiver unit is configured to: receive the high-priority service from the first Station (STA) and sent through the first slave gateway and the first low-priority service from the second STA and sent through the second slave gateway; The processing unit is configured to: obtain the uplink transmission quality parameter of the high-priority service; If the processing unit determines that there is frame loss or congestion in the transmission of the high-priority service according to the uplink transmission quality parameter of the high-priority service, the transceiver unit is configured to: send a first downlink message to the second slave gateway, and the first downlink message is used to instruct the second slave gateway to reduce the uplink radio resource allocated to the first low-priority service.

13. The master gateway according to claim 12, characterized in that, The transceiver unit is configured to receive the uplink message sent by the first slave gateway, and the uplink message is used to indicate the frame loss information of the high-priority service.

14. The master gateway according to claim 13, characterized in that, The first downlink message is used to instruct the second slave gateway to send a Clear to Send (CTS) frame with the destination address being the second slave gateway, and the CTS frame is used to instruct the second STA to suspend sending the first low-priority service.

15. The master gateway according to claim 13 or 14, characterized in that, The first downlink message is further used to instruct the second slave gateway to suspend sending the downlink low-priority service to the second STA.

16. The master gateway according to any one of claims 13 to 15, characterized in that If the processing unit determines that there is frame loss in the transmission of the high-priority service, the transceiver unit is further configured to: send a second downlink message to the first slave gateway, and the second downlink message is used to instruct the first slave gateway to send a trigger frame to the first STA, and the trigger frame is used to indicate the retransmission time slot of the high-priority service.

17. The main gateway according to claim 12, characterized in that, The processing unit is specifically configured to obtain the round-trip time (RTT) of the transmission control protocol (TCP) acknowledgment packet of the high-priority service; if the RTT is greater than a first preset value, congestion occurs in the transmission of the high-priority service.

18. The main gateway according to claim 12, wherein The processing unit is specifically configured to obtain the time interval between two consecutive uplink media access control protocol data units (MPDUs) of the high-priority service; if the transmission time interval between two consecutive uplink MPDUs of the high-priority service is greater than a second preset value, congestion occurs in the transmission of the high-priority service.

19. The master gateway according to claim 17 or 18, characterized in that, The first downlink message is used to indicate at least one of the following information: The first downlink message is used to instruct the second slave gateway to delay sending the downlink TCP acknowledgment packet corresponding to the first low-priority service from the master gateway to the second STA. The first downlink message is used to instruct the second slave gateway to delay sending the uplink TCP acknowledgment packet corresponding to the first low-priority service from the second STA to the master gateway. The first downlink message is used to instruct the second slave gateway to delay sending the downlink data packet of the first low-priority service from the master gateway to the second STA. The first downlink message is used to instruct the second slave gateway to delay sending the uplink data packet of the first low-priority service from the second STA to the master gateway.

20. The master gateway according to any one of claims 17 to 19, characterized in that The transceiver unit is further configured to perform at least one of the following processes: Delay sending the downlink TCP acknowledgment packet corresponding to the first low-priority service from the server to the second slave gateway. Delay sending the uplink TCP acknowledgment packet corresponding to the first low-priority service from the second slave gateway to the server. Delay sending the downlink data packet of the first low-priority service from the server to the second slave gateway. Delay sending the uplink data packet of the first low-priority service from the second slave gateway to the server.

21. The master gateway according to any one of claims 17 to 20, characterized in that The first downlink message is used to instruct the second slave gateway to increase the enhanced distributed channel access (EDCA) contention window corresponding to the first low-priority service.

22. The main gateway according to any one of claims 12 to 21, characterized in that, The transceiver unit is further configured to receive the second low-priority service from the first STA and sent through the first slave gateway; if the processing unit determines that frame loss or congestion occurs in the transmission of the high-priority service according to the uplink transmission quality parameter of the high-priority service, the transceiver unit is further configured to: send a third downlink message to the first slave gateway, and the third downlink message is used to instruct the first slave gateway to reduce the uplink radio resource of the second low-priority service.

23. A chip, characterized in that, The chip includes a processor, and the processor is configured to execute the method according to any one of claims 1 to 11.

24. A Fiber to the Room (FTTR) system, characterized in that, The FTTR system includes a master gateway and a plurality of slave gateways according to any one of claims 12 to 22, and the master gateway communicates with the plurality of slave gateways respectively.

Images