FTTR dynamic bandwidth allocation method and system based on master-slave gateway collaboration

Abstract

The embodiment of the invention provides an FTTR dynamic bandwidth allocation method and system based on master-slave gateway collaboration, and belongs to the technical field of communication. The method comprises the following steps: counting bandwidth demand information from a gateway; generating flow bandwidth request information according to the bandwidth demand information and sending the flow bandwidth request information to the main gateway; the master gateway receives the traffic bandwidth request information and makes a decision, determines the bandwidth allocation information of the slave gateway and informs the slave gateway of a decision result; and the slave gateway receives the decision result and performs data transmission according to the bandwidth allocation information of the slave gateway. The slave gateway counts the bandwidth demand information and requests the corresponding bandwidth from the master gateway according to the bandwidth demand information, the master gateway confirms the traffic bandwidth request information after receiving the traffic bandwidth request information, and the master gateway and the slave gateway cooperatively perform dynamic bandwidth allocation, so that bandwidth waste caused by static allocation of the master gateway can be avoided, and the bandwidth allocation efficiency is improved. And the real-time distribution according to the requirement is realized, and the bandwidth service is better provided for the slave gateway.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to an FTTR dynamic bandwidth allocation method based on master-slave gateway collaboration, an FTTR dynamic bandwidth allocation system based on master-slave gateway collaboration, and a machine-readable storage medium. Background Art

[0002] With the rapid development of network access technologies, the access of intelligent home gateways has evolved to the Fiber To The Room (FTTR) whole-house optical network. The FTTR system consists of a master gateway and several slave gateways. The master and slave gateways are networked through optical fibers or other forms. User devices can roam between the master and slave gateways, and the master gateway manages the slave gateways. Currently, FTTR networking devices are widely used in scenarios such as homes and hotels.

[0003] In the FTTR networking environment, the main ways for the master gateway to allocate uplink bandwidth to the slave gateways are as follows: Static bandwidth allocation, where a fixed bandwidth and time slices are allocated to the slave gateways. This differs greatly from the actual network traffic requirements of the slave gateways, resulting in bandwidth waste or insufficient bandwidth, causing high-priority services to be unsatisfied. Dynamic bandwidth allocation, where the master gateway monitors network congestion in real time and makes dynamic adjustments according to the congestion situation. However, this allocation method requires the master gateway to monitor in real time and predict the network traffic situation in the next time period, leading to disadvantages such as inaccurate prediction and latency. Current mainstream manufacturers can perform dynamic bandwidth allocation on the FTTR master gateway side, but they all require the master gateway to monitor and predict the traffic requirements of the slave gateways in the future for a period of time, inevitably bringing disadvantages such as inaccurate prediction, latency, and low efficiency. At the same time, it also increases the complexity and operating pressure on the master gateway side. Summary of the Invention

[0004] The purpose of the embodiments of this application is to provide an FTTR dynamic bandwidth allocation method and system based on master-slave gateway collaboration. In this method, the slave gateway statistics bandwidth demand information and requests the corresponding bandwidth from the master gateway according to the bandwidth demand information. After receiving the traffic bandwidth request information, the master gateway confirms it, and the master and slave gateways collaborate to perform dynamic bandwidth allocation, which can avoid the bandwidth waste caused by static allocation of the master gateway or the disadvantages of inaccurate prediction and untimely prediction brought by dynamic prediction of the master gateway, achieve real-time on-demand allocation, better provide bandwidth services for the slave gateways. At the same time, this collaboration method can also avoid the master gateway from monitoring the connected slave gateways in real time and reduce the operating pressure on the master gateway.

[0005] To achieve the above purpose, the embodiments of this application provide an FTTR dynamic bandwidth allocation method based on master-slave gateway collaboration, and the method includes:

[0006] The slave gateway statistics bandwidth demand information;

[0007] Generate traffic bandwidth request information according to the bandwidth requirement information and send it to the master gateway;

[0008] The master gateway receives the traffic bandwidth request information and makes a decision, determines the slave gateway bandwidth allocation information and informs the slave gateway of the decision result;

[0009] The slave gateway receives the decision result and performs data transmission according to the slave gateway bandwidth allocation information.

[0010] According to the above technical means, by the slave gateway counting the bandwidth requirement information and requesting the corresponding bandwidth from the master gateway according to the bandwidth requirement information, and the master gateway making a confirmation after receiving the traffic bandwidth request information, the master and slave gateways cooperate to perform dynamic bandwidth allocation, which can avoid the waste of bandwidth caused by the static allocation of the master gateway, or the disadvantages such as inaccurate and untimely prediction brought by the dynamic prediction of the master gateway, realize real-time on-demand allocation, better provide bandwidth services for the slave gateway, and at the same time, this cooperation method can also avoid the master gateway from performing real-time monitoring on the connected slave gateways and reduce the operation pressure of the master gateway.

[0011] In some feasible embodiments, the generating traffic bandwidth request information according to the bandwidth requirement information and sending it to the master gateway includes:

[0012] Generate a message type field according to the OMCI protocol field format;

[0013] Generate a message entity field according to the OMCI protocol field format;

[0014] Generate an extended message entity field according to the bandwidth requirement information;

[0015] Construct traffic bandwidth request information according to the message type field, the message entity field and the extended message entity field and send it to the master gateway.

[0016] According to the above technical means, an extension is made on the basis of the standard OMCI protocol, the format of the traffic bandwidth request information between the master and slave gateways is defined, and the bandwidth requirement information is carried by the extended message entity field to construct the traffic bandwidth request information, so as to realize that the slave gateway requests bandwidth from the master gateway according to real-time requirements.

[0017] In some feasible embodiments, the message type field adopts the field corresponding to the Get type defined by ITU-T G.984.4; the ME instance ID in the message entity field adopts the manufacturer's private entity type number.

[0018] According to the above technical means, setting the message type field to the field corresponding to the Get type can facilitate the master gateway to identify that the received message is a request message, and adopting the manufacturer's private entity type number can avoid conflicts with other entity types.

[0019] In some feasible embodiments, the bandwidth requirement information includes: uplink and downlink rates, uplink and downlink service types, uplink and downlink service priorities, and uplink and downlink usage durations; the extended message entity fields include: uplink bandwidth size field, uplink bandwidth time slice field, uplink bandwidth type field, uplink bandwidth priority field, uplink bandwidth reservation field, downlink bandwidth size field, downlink bandwidth time slice field, downlink bandwidth type field, downlink bandwidth priority field, and downlink bandwidth reservation field;

[0020] Generating the extended message entity fields according to the bandwidth requirement information includes:

[0021] Generating the uplink bandwidth size field according to the uplink rate;

[0022] Generating the uplink bandwidth time slice field according to the uplink usage duration;

[0023] Generating the uplink bandwidth type field according to the uplink service type;

[0024] Generating the uplink bandwidth priority field according to the uplink service priority;

[0025] Generating the downlink bandwidth size field according to the downlink rate;

[0026] Generating the downlink bandwidth time slice field according to the downlink usage duration;

[0027] Generating the downlink bandwidth type field according to the downlink service type;

[0028] Generating the downlink bandwidth priority field according to the downlink service priority.

[0029] According to the above technical means, the extended message fields generated according to the bandwidth requirement information include uplink bandwidth requirements and downlink bandwidth requirements. After receiving the requirements, the main gateway can allocate according to the actual requirements, which can avoid the waste of bandwidth caused by static allocation of the main gateway, or the disadvantages such as inaccurate and untimely dynamic prediction of the main gateway.

[0030] In some feasible embodiments, the slave gateway statistics bandwidth requirement information, including:

[0031] The slave gateway collects and statistics the number of bytes of the transmitted and received packets of the attached devices, and calculates the uplink and downlink rates per unit time;

[0032] Identifying the data packet protocol types passing through the protocol stack and hardware fast switching;

[0033] Determining the uplink and downlink service types according to the data packet protocol type;

[0034] Determining the corresponding service priority according to the service type;

[0035] Determine the uplink and downlink usage duration according to the statistical time of the uplink and downlink rates.

[0036] According to the above technical means, by collecting and statistically analyzing the data transmission and reception of the devices connected below from the gateway, the actual bandwidth demand information is determined, providing a basis for bandwidth allocation for the main gateway, so that the subsequently allocated bandwidth can not only meet the service requirements but also avoid bandwidth waste.

[0037] In some feasible embodiments, the main gateway receives the traffic bandwidth request information and makes a decision, determines the bandwidth allocation information for the slave gateway and informs the slave gateway of the decision result, including:

[0038] After the main gateway receives the traffic bandwidth request information, it reads the bandwidth priority field in the traffic bandwidth allocation request information;

[0039] Put the traffic bandwidth allocation request information into different priority queues according to the bandwidth priority field;

[0040] Make a bandwidth decision in different priority queues according to the set priority weight coefficients, determine the bandwidth allocation information for the slave gateway and inform the slave gateway of the decision result.

[0041] According to the above technical means, the main gateway puts the traffic bandwidth allocation request information into different priority queues according to the bandwidth priority field for bandwidth decision-making, simplifies the main gateway decision-making strategy, avoids complex decision-making strategies, and increases the complexity of the main gateway module.

[0042] In some feasible embodiments, in the same priority queue, the principle of first-in first-decision is adopted, and the bandwidth allocation request information received first is preferentially decided. First-in first-decision can ensure that the slave gateway that requests first is preferentially allocated traffic, avoiding being occupied by other slave gateways, resulting in continuously unsatisfactory network bandwidth for individual slave gateways and reducing the user experience.

[0043] In some feasible embodiments, before the slave gateway statistically analyzes the bandwidth demand information, the method further includes:

[0044] The main gateway sends a GET request to the slave gateway.

[0045] The second aspect of this application provides a dynamic bandwidth allocation system for FTTR based on the cooperation of the main and slave gateways. The system includes: a main gateway and a slave gateway connected to the main gateway;

[0046] The slave gateway is used to statistically analyze the bandwidth demand information, generate traffic bandwidth request information according to the bandwidth demand information and send it to the main gateway, and receive the decision result and perform data transmission according to the bandwidth allocation information of the slave gateway;

[0047] The master gateway is used to receive traffic bandwidth request information, make decisions, determine the bandwidth allocation information for the slave gateway, and inform the slave gateway of the decision result.

[0048] According to the above technical means, the system statistically obtains bandwidth demand information through the slave gateway and requests the corresponding bandwidth from the master gateway based on the bandwidth demand information. After receiving the traffic bandwidth request information, the master gateway confirms it, and the master and slave gateways cooperate to perform dynamic bandwidth allocation. This can avoid the waste of bandwidth caused by static allocation of the master gateway, or the disadvantages of inaccurate and untimely dynamic prediction of the master gateway, achieve real-time on-demand allocation, and better provide bandwidth services for the slave gateway. At the same time, this cooperative method can also avoid the master gateway from performing real-time monitoring on the connected slave gateways, reducing the operating pressure on the master gateway.

[0049] The third aspect of this application provides a machine-readable storage medium, on which instructions are stored, and these instructions are used to cause a machine to execute the FTTR dynamic bandwidth allocation method based on the cooperation of the master and slave gateways described in this application.

[0050] Through the above technical solution, a FTTR dynamic bandwidth allocation method based on the cooperation of the master and slave gateways is provided. This method statistically obtains bandwidth demand information through the slave gateway and requests the corresponding bandwidth from the master gateway based on the bandwidth demand information. After receiving the traffic bandwidth request information, the master gateway confirms it, and the master and slave gateways cooperate to perform dynamic bandwidth allocation. This can avoid the waste of bandwidth caused by static allocation of the master gateway, or the disadvantages of inaccurate and untimely dynamic prediction of the master gateway, achieve real-time on-demand allocation, and better provide bandwidth services for the slave gateway. At the same time, this cooperative method can also avoid the master gateway from performing real-time monitoring on the connected slave gateways, reducing the operating pressure on the master gateway.

[0051] Other features and advantages of the embodiments of this application will be described in detail in the subsequent specific implementation section. Brief Description of the Drawings

[0052] The drawings are used to provide a further understanding of the embodiments of this application, and constitute a part of the specification. Together with the following specific implementation, they are used to explain the embodiments of this application, but do not constitute a limitation to the embodiments of this application. In the drawings:

[0053] Figure 1 It is a schematic flowchart of a FTTR dynamic bandwidth allocation method based on the cooperation of the master and slave gateways provided by an embodiment of this application;

[0054] Figure 2 It is a block diagram of a FTTR dynamic bandwidth allocation system provided by an embodiment of this application. Detailed Description of the Embodiments

[0055] The following will describe in detail the specific implementation manners of the embodiments of the present application with reference to the accompanying drawings. It should be understood that the specific implementation manners described herein are only used to illustrate and explain the embodiments of the present application, and are not used to limit the embodiments of the present application.

[0056] Figure 1 It is a flowchart of a method for dynamically allocating bandwidth for FTTR based on the cooperation of master and slave gateways provided by an embodiment of the present application. As Figure 1 shown, an embodiment of the present invention provides a method for dynamically allocating bandwidth for FTTR based on the cooperation of master and slave gateways, and the method includes:

[0057] S1: The slave gateway statistically calculates bandwidth demand information, and the bandwidth demand information includes: uplink and downlink rates, uplink and downlink service types, uplink and downlink service priorities, and uplink and downlink usage durations.

[0058] In some feasible embodiments, the slave gateway statistically calculates the bandwidth demand information, including:

[0059] The slave gateway collects and statistically calculates the number of bytes of transmitted and received packets of the attached devices, and calculates the uplink and downlink rates per unit time. In actual implementation, the statistical time can be adjusted according to the required accuracy. For the time being, the uplink and downlink rates for one second are statistically calculated. If it is necessary to improve the statistical accuracy, for example, the uplink and downlink rates within 500 milliseconds can be statistically calculated, but the statistical time accuracy should not be too short. The statistical time accuracy is controlled between 100 and 1000 milliseconds to avoid too short statistical time and increase the data calculation amount of the slave gateway.

[0060] Identify the data packet protocol types passing through the protocol stack and hardware fast switching, such as identifying that the data packet type is UDP (Transmission Control Protocol), TCP (User Datagram Protocol), IGMP (Internet Group Management Protocol), etc. At the same time, identify the protocol types at a higher layer, such as RTSP (Real Time Streaming Protocol), SIP (Session initialization Protocol), and H248 protocol. The H248 protocol (also known as MEGACO, Media Gateway Control Protocol) is a protocol for controlling media gateways.

[0061] Determine the uplink and downlink service types according to the data packet protocol type. In the embodiments of the present application, if an RTSP data stream is recognized as a video data stream, then at this time, in the data packet data stream of the devices hung under the gateway, it is mainly an RTSP video stream service. If SIP and H248 protocols are recognized as standard voice protocols, and the data packet stream from the gateway is mainly a voice service, then the corresponding recognized service is a voice service at this time; if no video or voice service stream is recognized in the data packet stream passing through the slave gateway, it is recognized as a general service.

[0062] Determine the corresponding service priority according to the service type. In the embodiments of the present application, if a video service is recognized, the priority is high priority. If a voice service is recognized, the priority is medium priority. If no video or voice service stream is recognized, it is recognized as a general service with a low priority. In addition, if there are markings for IP (Internet Protocol Address) and DSCP (Differentiated Services Code Point) priorities in the packet type, then process according to the IP and DSCP priorities.

[0063] Determine the uplink and downlink usage durations according to the statistical time of the uplink and downlink rates. In the embodiments of the present application, use the statistical time of the uplink and downlink rates as the uplink and downlink usage durations. For example, if the statistical time of the uplink and downlink rates is 500 milliseconds, then the determined uplink and downlink usage duration is 500 milliseconds. In other feasible embodiments, the uplink and downlink usage durations can be determined by weighted calculation based on the service priority on the basis of the statistical time of the uplink and downlink rates. For example, the weighted value of a high-priority service can be set to 1.1. If a high-priority service is recognized and the statistical time of the uplink and downlink rates is 500 milliseconds, the uplink and downlink usage duration can be set to 550 milliseconds.

[0064] According to the above technical means, the slave gateway determines the actual bandwidth demand information by collecting and counting the data sending and receiving situations of the devices hung under it, providing a basis for the master gateway to allocate bandwidth, so that the subsequently allocated bandwidth can not only meet the service requirements but also avoid bandwidth waste.

[0065] S2: Generate a traffic bandwidth request message according to the bandwidth demand information and send it to the master gateway.

[0066] In some feasible embodiments, the generating a traffic bandwidth request message according to the bandwidth demand information and sending it to the master gateway includes:

[0067] Generate the message type field (Message Type) according to the OMCI protocol field format. In some feasible embodiments, the message type field adopts the field corresponding to the Get type defined in ITU-T G.984.4. Setting the message type field to the field corresponding to the Get type can facilitate the master gateway to recognize that the received message is a request message.

[0068] Generate the message entity field (Message Identifier) according to the OMCI protocol field format; the ME instance ID in the message entity field adopts the manufacturer's private entity type number. The first two bytes of the Message Identifier represent the ME type, and the last two bytes represent the ME instance ID. The maximum number of entity types supported by the ME type defined by ITU is 65535. Since the entity type numbers 1-171, 256-349, and 400-466 have been standardized and defined by ITU G.984.4 and ITU G.988, and 172-239 and 467-65279 are entity types reserved by ITU and undefined. The manufacturer's self-defined private entity type numbers are: 240-255, 350-399, and 65280-65535. Therefore, in this application, for the master and slave gateways and the bandwidth data allocation request, the manufacturer's private entity type number 65531, the hexadecimal number 0xFFFB, and the entity instance ID 0x0000 are used as the entity type and entity instance ID of the slave gateway bandwidth request. Using the manufacturer's private entity type number can avoid conflicts with other entity types.

[0069] Generate the extended message entity field (Message Contents) according to the bandwidth demand information; the extended message entity field includes: uplink bandwidth size field, uplink bandwidth time slice field, uplink bandwidth type field, uplink bandwidth priority field, uplink bandwidth reservation field, downlink bandwidth size field, downlink bandwidth time slice field, downlink bandwidth type field, downlink bandwidth priority field, and downlink bandwidth reservation field, as shown in Table 1.

[0070] The extended message entity field defined in the OMCI protocol field format is 32 bytes in total, with 16 bytes allocated for both the uplink and downlink bandwidths. The first six bytes are the bandwidth size, bandwidth time slice, bandwidth type, and bandwidth priority respectively, and the remaining 10 bytes are reserved fields for future use. Among them, the uplink bandwidth size field occupies 2 bytes, the uplink bandwidth time slice field occupies 2 bytes, the uplink bandwidth type field occupies 1 byte, the uplink bandwidth priority field occupies 1 byte, the uplink bandwidth reservation field occupies 10 bytes, the downlink bandwidth size field occupies 2 bytes, the downlink bandwidth time slice field occupies 2 bytes, the downlink bandwidth type field occupies 1 byte, the downlink bandwidth priority field occupies 1 byte, and the downlink bandwidth reservation field occupies 10 bytes.

[0071] According to the above technical means, the extended message field generated according to the bandwidth requirement information includes the uplink bandwidth requirement and the downlink bandwidth requirement. After receiving the requirements, the master gateway can allocate according to the actual requirements, which can avoid the waste of bandwidth caused by the static allocation of the master gateway, or the disadvantages such as inaccurate and untimely prediction brought by the dynamic prediction of the master gateway.

[0072] Construct the traffic bandwidth request information according to the message type field, the message entity field, and the extended message entity field and send it to the master gateway. In the embodiments of the present application, the traffic bandwidth request information is constructed according to the OMCI protocol field format defined by ITU-T G.984.4.

[0073] According to the above technical means, on the basis of the standard OMCI protocol, the format of the traffic bandwidth request information between the master gateway and the slave gateway is defined, and the bandwidth requirement information is carried by the extended message entity field to construct the traffic bandwidth request information, so as to realize that the slave gateway requests bandwidth from the master gateway according to real-time requirements.

[0074] In some feasible embodiments, generating an extended message entity field according to the bandwidth requirement information includes:

[0075] Generate an uplink bandwidth size field according to the uplink rate;

[0076] Generate an uplink bandwidth time slice field according to the uplink usage duration;

[0077] Generate an uplink bandwidth type field according to the uplink service type;

[0078] Generate an uplink bandwidth priority field according to the uplink service priority;

[0079] Generate a downlink bandwidth size field according to the downlink rate;

[0080] Generate a downlink bandwidth time slice field according to the downlink usage duration;

[0081] Generate a downlink bandwidth type field according to the downlink service type;

[0082] Generate a downlink bandwidth priority field according to the downlink service priority.

[0083] In the embodiments of the present application, the bandwidth type field is defined as follows: 0x00 is for ordinary services, 0x01 is for video services, 0x02 is for voice services, and 0x03 - 0x255 are reserved fields and are not specifically defined for the time being. There are three tentative bandwidth priorities, which are: 0x00 is for high priority, 0x01 is for medium priority, 0x02 is for low priority, and 0x03 - 0x255 are reserved priorities and are not specifically defined for the time being.

[0084] The slave gateway attaches the uplink and downlink bandwidth sizes, time slices, bandwidth types, and bandwidth priority requests to the data according to the defined message entity format and sends it to the master gateway. The uplink and downlink bandwidth sizes are the uplink and downlink rates calculated by the slave gateway. The bandwidth type is the identified bandwidth service type, i.e., video service, voice service, and ordinary service. The time slice is the statistical cycle time value of the uplink and downlink, with the unit of microseconds, and the bandwidth priority is the priority identified by the slave gateway.

[0085] S3: The master gateway receives the traffic bandwidth request information and makes a decision, determines the bandwidth allocation information for the slave gateway, and informs the slave gateway of the decision result.

[0086] In some feasible embodiments, when the master gateway receives the traffic bandwidth request information and makes a decision, determines the bandwidth allocation information for the slave gateway, and informs the slave gateway of the decision result, it includes:

[0087] After the master gateway receives the traffic bandwidth request information, it reads the bandwidth priority field in the traffic bandwidth allocation request information;

[0088] According to the bandwidth priority field, the traffic bandwidth allocation request information is placed into different priority queues;

[0089] In different priority queues, bandwidth decisions are made according to the set priority weight coefficients to determine the bandwidth allocation information for the slave gateway and inform the slave gateway of the decision result.

[0090] The master gateway maintains 3 priority queues, namely low, medium, and high priorities. In different priority queues, different weights are used for the allocated time slices, that is, the time slice allocated by the master gateway to the slave gateway is the applied time slice multiplied by the weight coefficient. In a feasible embodiment, the high-priority weight coefficient is 1, the medium-priority weight coefficient is 0.9, and the low-priority weight coefficient is 0.8. When the master gateway receives the traffic bandwidth allocation request information from the slave gateway, it first reads the bandwidth priority in the traffic bandwidth allocation information and enters different priority queues respectively. Then, in different priority queues, bandwidth decisions are made. Each bandwidth priority decision follows the first-in, first-out principle, i.e., FIFO, to simplify the master gateway decision strategy, avoid complex decision strategies, and increase the complexity of the master gateway module. The master gateway allocates the requested bandwidth information to the slave gateway and replies to the slave gateway's OMCI message. Subsequently, in the specific implementation process, the weight coefficients of different priorities can be adjusted.

[0091] In some feasible embodiments, in the same priority queue, the principle of first-in, first-decision is adopted, and the bandwidth allocation request information received first is preferentially decided. First-in, first-decision can ensure that the slave gateway that requests first is preferentially allocated traffic, avoiding being crowded out by other slave gateways, resulting in continuously unsatisfactory network bandwidth for individual slave gateways and reducing the user experience.

[0092] S4: Receive the decision result from the gateway and perform data transmission according to the bandwidth allocation information of the slave gateway.

[0093] According to the above technical means, by the slave gateway statistically collecting bandwidth demand information and requesting the corresponding bandwidth from the master gateway according to the bandwidth demand information, and the master gateway confirming after receiving the traffic bandwidth request information, the master and slave gateways cooperate to perform dynamic bandwidth allocation, which can avoid the waste of bandwidth caused by the static allocation of the master gateway, or the disadvantages such as inaccurate and untimely prediction brought by the dynamic prediction of the master gateway, realize real-time on-demand allocation, better provide bandwidth services for the slave gateway. At the same time, this cooperation method can also avoid the master gateway from performing real-time monitoring on the accessed slave gateways and reduce the operation pressure of the master gateway.

[0094] In some feasible embodiments, before the slave gateway statistically collects bandwidth demand information, the method further includes:

[0095] S0: The master gateway sends a GET request to the slave gateway, and the slave gateway responds to the GET request, generates traffic bandwidth request information according to the statistically collected bandwidth demand information and sends it to the master gateway.

[0096] The second aspect of this application provides an FTTR dynamic bandwidth allocation system based on the cooperation of the master and slave gateways, as Figure 2 shown, the system includes: a master gateway and slave gateways connected to the master gateway;

[0097] The slave gateway is used to statistically collect bandwidth demand information, generate traffic bandwidth request information according to the bandwidth demand information and send it to the master gateway, and receive the decision result and perform data transmission according to the bandwidth allocation information of the slave gateway;

[0098] The master gateway is used to receive the traffic bandwidth request information and make a decision, determine the bandwidth allocation information of the slave gateway and inform the slave gateway of the decision result.

[0099] According to the above technical means, this system can avoid the waste of bandwidth caused by the static allocation of the master gateway, or the disadvantages such as inaccurate and untimely prediction brought by the dynamic prediction of the master gateway, realize real-time on-demand allocation, better provide bandwidth services for the slave gateway. At the same time, this cooperation method can also avoid the master gateway from performing real-time monitoring on the accessed slave gateways and reduce the operation pressure of the master gateway.

[0100] The method of this application will be described below with specific embodiments.

[0101] One master gateway and three slave gateways (A, B, C), and the maximum uplink and downlink bandwidth of the master gateway is 1000M.

[0102] The master gateway A requests bandwidth data: 50M for the uplink, a time slice of 1000 us, the bandwidth type is ordinary service, and the priority is low priority; 500M for the downlink, a time slice of 1000 ms, the bandwidth type is video service, and the priority is high priority.

[0103] The master gateway B requests bandwidth data: 100M for the uplink, a time slice of 1000 us, the bandwidth type is voice service, and the priority is medium priority; 100M for the downlink, a time slice of 1000 ms, the bandwidth type is voice service, and the medium priority.

[0104] The master gateway C requests bandwidth data: 100M for the uplink, a time slice of 1000 us, the bandwidth type is video service, and the priority is high priority; 100M for the downlink, a time slice of 1000 ms, the bandwidth type is ordinary service, and the low priority.

[0105] The master gateway respectively receives the bandwidth request data of three slave gateways A, B, and C, parses the message fields, obtains the traffic bandwidth request information, and according to the priority, the uplink and downlink bandwidths respectively enter different priority queues. Adopting the principle of first come, first served, the bandwidth size and time slice required by the three slave gateways are respectively allocated. After receiving the reply, the slave gateways perform data transmission according to the bandwidth and time slice allocated by the master gateway. Since the traffic cycle unit counted by the slave gateway is in milliseconds, in the actual bandwidth application process, the microsecond is used as the unit for the transmission time slice.

[0106] If the bandwidth applied by a certain slave gateway exceeds the maximum bandwidth of the master gateway, it will be allocated according to the maximum bandwidth.

[0107] For example, if the slave gateway A applies for a downlink bandwidth of 1500M, but the maximum downlink bandwidth of the master gateway is 1000M, it will be allocated according to the maximum bandwidth of the master gateway, and the slave gateway A will be allocated 1000M for the downlink.

[0108] When a new slave gateway D is connected, but the slave gateway D does not support the master-slave bandwidth collaborative allocation method, the master gateway and the slave gateway D will allocate according to the ITU G.984.3 standard protocol method, and allocate fixed bandwidth and time slice.

[0109] A third aspect of this application provides a machine-readable storage medium, on which instructions are stored, and these instructions are used to make the machine execute the FTTR dynamic bandwidth allocation method based on master-slave gateway collaboration described in this application.

[0110] The method of this application utilizes the ITU-T G.984.4 OMCI protocol to enable the slave gateway to report traffic demand information, expand the ME private entity type, define the message format of the extended message entity, add the bandwidth request information of the slave gateway, and the request information includes fields such as uplink and downlink bandwidth sizes, time slices, service types, and service priorities. Under the current technical standard, the ME private entity type is expanded, and the actual bandwidth demand of the slave gateway is increased, making the bandwidth demand of the slave gateway more transparent to the master gateway, coordinating bandwidth allocation, avoiding phenomena such as inaccurate bandwidth prediction, excessive delay, or bandwidth waste caused by static allocation by the master gateway to the slave gateway, allocating bandwidth to the slave gateway more accurately, optimizing the user network experience, while also reducing the complexity and operating pressure on the master gateway side, and at the same time having better compatibility and scalability.

[0111] The optional implementation manners of the embodiments of this application have been described in detail above in conjunction with the accompanying drawings. However, the embodiments of this application are not limited to the specific details in the above implementation manners. Within the technical concept scope of the embodiments of this application, various simple variants can be made to the technical solutions of the embodiments of this application, and these simple variants all belong to the protection scope of the embodiments of this application.

[0112] In addition, it should be noted that, among the various specific technical features described in the above specific implementation manners, they can be combined in any appropriate manner without conflict. To avoid unnecessary repetition, the embodiments of this application do not separately describe various possible combination manners.

[0113] Those skilled in the art can understand that all or part of the steps of implementing the methods in the above embodiments can be completed by instructing relevant hardware through a program, and this program is stored in a storage medium, including several instructions for enabling a single-chip microcomputer, a chip, or a processor to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage medium includes: USB flash drives, mobile hard disks, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), magnetic disks, or optical discs and other various media that can store program codes.

[0114] In addition, any combination can be made among various different implementation manners of the embodiments of this application, as long as it does not violate the idea of the embodiments of this application, and it should also be regarded as the content disclosed in the embodiments of this application.

Claims

1. A dynamic bandwidth allocation method for FTTR based on master-slave gateway collaboration, characterized in that The method includes: Statistical bandwidth requirement information from the slave gateway; Generate traffic bandwidth request information according to the bandwidth requirement information and send it to the master gateway; The master gateway receives the traffic bandwidth request information and makes a decision, determines the slave gateway bandwidth allocation information and informs the slave gateway of the decision result; The slave gateway receives the decision result and performs data transmission according to the slave gateway bandwidth allocation information.

2. The FTTR dynamic bandwidth allocation method based on master-slave gateway collaboration according to claim 1, wherein, The generating traffic bandwidth request information according to the bandwidth requirement information and sending it to the master gateway includes: Generate a message type field according to the OMCI protocol field format; Generate a message entity field according to the OMCI protocol field format; Generate an extended message entity field according to the bandwidth requirement information; Construct traffic bandwidth request information according to the message type field, the message entity field and the extended message entity field and send it to the master gateway.

3. The FTTR dynamic bandwidth allocation method based on master-slave gateway collaboration according to claim 2, wherein, The message type field adopts the field corresponding to the Get type defined in ITU-T G.984.4; the ME instance ID in the message entity field adopts the manufacturer-private entity type number.

4. The method for dynamically allocating bandwidth of FTTR based on the cooperation of master and slave gateways according to claim 3, wherein, The bandwidth requirement information includes: uplink and downlink rates, uplink and downlink service types, uplink and downlink service priorities, and uplink and downlink usage durations; the extended message entity field includes: uplink bandwidth size field, uplink bandwidth time slice field, uplink bandwidth type field, uplink bandwidth priority field, uplink bandwidth reservation field, downlink bandwidth size field, downlink bandwidth time slice field, downlink bandwidth type field, downlink bandwidth priority field, and downlink bandwidth reservation field; Generating an extended message entity field according to the bandwidth requirement information includes: Generate an uplink bandwidth size field according to the uplink rate; Generate an uplink bandwidth time slice field according to the uplink usage duration; Generate an uplink bandwidth type field according to the uplink service type; Generate an uplink bandwidth priority field according to the uplink service priority; Generate a downlink bandwidth size field according to the downlink rate; Generate a downlink bandwidth time slice field according to the downlink usage duration; Generate a downlink bandwidth type field according to the downlink service type; Generate a downlink bandwidth priority field according to the downlink service priority.

5. The FTTR dynamic bandwidth allocation method based on master-slave gateway collaboration according to claim 4, wherein The slave gateway statistical bandwidth requirement information includes: The slave gateway collects and statistics the number of bytes of the transmitted and received packets of the attached devices, and calculates the uplink and downlink rates per unit time; Identify the data packet protocol types passing through the protocol stack and hardware fast switching; Determine the uplink and downlink service types according to the data packet protocol types; Determine the corresponding service priority according to the service type; Determine the uplink and downlink usage durations according to the statistical time of the uplink and downlink rates.

6. The FTTR dynamic bandwidth allocation method based on master-slave gateway collaboration according to claim 1, characterized in that The master gateway receives the traffic bandwidth request information and makes a decision, determines the slave gateway bandwidth allocation information and informs the slave gateway of the decision result, including: After receiving the traffic bandwidth request information, the master gateway reads the bandwidth priority field in the traffic bandwidth allocation request information; Put the traffic bandwidth allocation request information into different priority queues according to the bandwidth priority field; Perform bandwidth decision according to the set priority weight coefficients in different priority queues, determine the slave gateway bandwidth allocation information and inform the slave gateway of the decision result.

7. The method for dynamically allocating bandwidth of FTTR based on the cooperation of master and slave gateways according to claim 6, wherein In the same priority queue, adopt the principle of first-in first-decision, and give priority to decision-making on the bandwidth allocation request information received first.

8. The FTTR dynamic bandwidth allocation method based on master-slave gateway collaboration according to claim 1, wherein Before statistically obtaining bandwidth requirement information from the gateway, the method further includes: The master gateway sends a GET request to the slave gateway.

9. A dynamic bandwidth allocation system for FTTR based on the cooperation of master and slave gateways, characterized in that, The system includes: a master gateway and a slave gateway connected to the master gateway; The slave gateway is configured to statistically obtain bandwidth requirement information, generate traffic bandwidth request information according to the bandwidth requirement information, send the traffic bandwidth request information to the master gateway, receive a decision result, and perform data transmission according to the slave gateway bandwidth allocation information; The master gateway is configured to receive the traffic bandwidth request information, make a decision, determine the slave gateway bandwidth allocation information, and inform the slave gateway of the decision result.

10. A machine-readable storage medium, characterized in that, Instructions are stored on the machine-readable storage medium, and the instructions are used to cause the machine to execute the FTTR dynamic bandwidth allocation method based on master-slave gateway collaboration according to any one of claims 1-8 of the present application.

Images