QoS adjustment method and apparatus, radio access network device, and core network device

Abstract

The application provides a QoS adjustment method and device, a radio access network device and a core network device, and relates to the technical field of communication. The method comprises the following steps: in the case that a radio access network device cannot guarantee a guaranteed flow bit rate GFBR of a guaranteed bit rate GBR service, the radio access network device sends a first message to a core network device, wherein the first message comprises first information; wherein the first information comprises at least one of the following: a reason why the GFBR cannot be met; quality of service QoS parameter recommendation information; wherein the QoS parameter recommendation information at least comprises GFBR recommendation information. The method of the application embodiment realizes closed-loop adjustment of the GFBR parameter in the GBR service, improves the guarantee certainty of the GBR, and reduces the influence of the GBR user on ordinary users.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a QoS adjustment method, apparatus, wireless access network equipment, and core network equipment. Background Technology

[0002] For high-priority services with stable minimum rate requirements, it is usually necessary to establish a Guaranteed Bit Rate (GBR) service bearer and configure the Guaranteed Flow Bit Rate (GFBR) minimum rate parameter. The GFBR is determined by the Session Management Function (SMF) entity and sent to the base station. The base station tries its best to guarantee the minimum rate by prioritizing the allocation of resources and power.

[0003] To better guarantee GBR services, the protocol establishes a QoS notification mechanism for Guaranteed Bit Rate Quality of Service (GBR) flows. According to the protocol, the QoS profile issued by the core network optionally includes notification control. Notification control is applied to GBR QoS flows. If notification control is enabled and the Radio Access Network (RAN) detects that the GFBR (Gateway Flow Breakdown) cannot be completed, then for a given GBR QoS flow, the RAN sends a notification to the SMF (Session Management Function). Once environmental conditions improve and the GFBR can be satisfied, the RAN will send a new notification message to the SMF.

[0004] However, the above mechanism has limitations in guaranteeing GFBR and issues with public-private collaboration. For example, in certain scenarios, when multiple GBR users cluster in the same cell or when some GBR users move to locations with poor channel quality, the GFBR rate for all GBR users may be compromised. This could also consume a large amount of physical resource block (PRB) resources, leaving non-GBR users without resources or even experiencing dropped calls, severely impacting user experience. Summary of the Invention

[0005] The purpose of this application is to provide a QoS adjustment method, apparatus, wireless access network equipment, and core network equipment, which solves the problems of GFBR's inability to guarantee QoS and public-private network collaboration.

[0006] To achieve the above objectives, embodiments of this application provide a QoS adjustment method applied to a wireless access network device, the method comprising:

[0007] When the radio access network device is unable to guarantee the guaranteed stream bit rate (GFBR) of the guaranteed bit rate (GBR) service, the radio access network device sends a first message to the core network device, the first message including first information.

[0008] The first information includes at least one of the following:

[0009] The reason why GFBR cannot meet the requirements;

[0010] Recommended QoS parameters;

[0011] The QoS parameter recommendation information includes at least GFBR recommendation information.

[0012] Optionally, before the radio access network device sends the first message to the core network device, the method further includes:

[0013] Determine the first information related to the QoS parameters.

[0014] Optionally, determining the reason why the GFBR cannot be satisfied includes:

[0015] Based on channel conditions and service scheduling waiting delay, determine the reasons why the GFBR cannot be satisfied;

[0016] The channel conditions include at least one of the following:

[0017] Reference signal received power RSRP;

[0018] Signal interference plus noise SINR.

[0019] Optionally, the reasons why the GFBR cannot be satisfied are determined based on channel conditions and service scheduling waiting delay, including:

[0020] If the RSRP is less than the first threshold, the SINR is less than the second threshold, and there is no service scheduling waiting delay, the reason why the GFBR cannot be satisfied is determined to be a deterioration in channel conditions.

[0021] Optionally, determining the GFBR recommendation information includes:

[0022] When the reason why the GFBR cannot be met is due to deteriorating channel conditions, the category of the GBR service that the GFBR cannot guarantee is determined according to the 5G Quality of Service Indicator (5QI) corresponding to the GBR service that the GFBR cannot guarantee.

[0023] When the category of GBR service that the GFBR cannot guarantee is non-rigid, the GFBR recommendation information is determined based on the load of the first service, wherein the first service is a service other than the GBR service that the GFBR cannot guarantee under the radio access network device.

[0024] If the category of GBR service that GFBR cannot guarantee is rigid, then the GFBR recommendation information is determined as the first value.

[0025] Optionally, GFBR recommendation information is determined based on the load of the first service, including:

[0026] Calculate the product of the cell's average capacity and the pre-configured expansion threshold, and the difference between this product and the load of the first service.

[0027] If the difference is greater than the first value, the GFBR recommendation information is determined to be the difference.

[0028] If the difference is less than or equal to the first value, the GFBR recommendation information is determined to be the first value.

[0029] Optionally, when the first service is a GBR service, the load of the first service is the capacity corresponding to the GFBR of the first service;

[0030] When the first service is an NGBR (Not Guaranteed Bit Rate) service, the load of the first service is the capacity corresponding to the baseline rate of the first service.

[0031] Optionally, the method further includes:

[0032] If the GFBR recommendation information is determined to be the first value, delete the GBR dedicated carriers for GBR services that the GFBR cannot guarantee.

[0033] Optionally, the method further includes:

[0034] In the case where the GBR service that the GFBR cannot guarantee includes multiple GBR services, extract multiple first GBR services that are non-rigid, consume more resources than the first preset threshold, have a SINR less than the second preset threshold, and have an RSRP less than the third preset threshold.

[0035] Determine the GFBR recommendation information for each of the first GBR services.

[0036] Optionally, the method further includes:

[0037] The wireless access network device receives a second message sent by the core network device, the second message including: the reason why the GFBR cannot be satisfied and the verification result of the GFBR recommendation information;

[0038] If the verification result is successful, monitor the GBR services that the GFBR cannot guarantee;

[0039] If it is determined that the radio access network device can guarantee the GFBR before the GBR service adjustment that the GFBR cannot guarantee, a third message is sent to the core network device. The third message includes: an indication that the radio access network device can guarantee the GFBR before the GBR service adjustment that the GFBR cannot guarantee, and the GFBR before the GBR service adjustment that the GFBR cannot guarantee.

[0040] Embodiments of this application also provide a Quality of Service (QoS) adjustment method applied to core network equipment, the method comprising:

[0041] The core network equipment receives a first message sent by the radio access network equipment, the first message including first information related to GBR services that GFBR cannot guarantee;

[0042] Based on the first information, the core network equipment adjusts the QoS parameters of GBR services that the GFBR cannot guarantee;

[0043] The first information includes at least one of the following:

[0044] The reason why GFBR cannot meet the requirements;

[0045] Recommended QoS parameters;

[0046] The QoS parameter recommendation information includes at least GFBR recommendation information.

[0047] Optionally, the core network equipment adjusts the QoS parameters of GBR services that the GFBR cannot guarantee based on the first information, including:

[0048] The reasons why the GFBR cannot be satisfied and the GFBR recommendation information are verified;

[0049] If the verification passes, adjust the GFBR in the QoS parameters of the unguaranteed GBR service according to the GFBR recommendation information.

[0050] Optionally, the method further includes:

[0051] The core network device sends a second message to the radio access network device, the second message including: the reason why the GFBR cannot be satisfied and the verification result of the GFBR recommendation information.

[0052] Optionally, the method further includes:

[0053] The core network device receives a third message sent by the radio access network device, the third message including: an indication that the radio access network device can guarantee the GFBR before the adjustment of the GBR service that the GFBR cannot guarantee, and the GFBR before the adjustment of the GBR service that the GFBR cannot guarantee;

[0054] Based on the third message, the core network equipment adjusts the GFBR of the GBR service that the GFBR cannot guarantee back to the original GFBR.

[0055] This application embodiment also provides a Quality of Service (QoS) adjustment device, applied to a wireless access network device, the device comprising:

[0056] The first sending module is used to send a first message to the core network device when the radio access network device cannot guarantee the guaranteed stream bit rate (GFBR) of the guaranteed bit rate (GBR) service. The first message includes first information.

[0057] The first information includes at least one of the following:

[0058] The reason why GFBR cannot meet the requirements;

[0059] QoS parameter recommendation information;

[0060] The QoS parameter recommendation information includes at least GFBR recommendation information.

[0061] This application embodiment also provides a Quality of Service (QoS) adjustment device, applied to core network equipment, the device comprising:

[0062] The first receiving module is configured to receive a first message sent by a wireless access network device, the first message including first information related to GBR services that cannot be guaranteed by GFBR;

[0063] The first adjustment module is used to adjust the QoS parameters of GBR services that the GFBR cannot guarantee, based on the first information.

[0064] The first information includes at least one of the following:

[0065] The reason why GFBR cannot meet the requirements;

[0066] QoS parameter recommendation information;

[0067] The QoS parameter recommendation information includes at least GFBR recommendation information.

[0068] This application embodiment also provides a wireless access network device, including: a first transceiver and a first processor;

[0069] The first transceiver is used to send a first message to the core network device when the radio access network device cannot guarantee the guaranteed stream bit rate (GFBR) of the guaranteed bit rate GBR service. The first message includes first information.

[0070] The first information includes at least one of the following:

[0071] The reason why GFBR cannot meet the requirements;

[0072] QoS parameter recommendation information;

[0073] The QoS parameter recommendation information includes at least GFBR recommendation information.

[0074] This application embodiment also provides a core network device, including: a second transceiver and a second processor;

[0075] The second transceiver is used to receive a first message sent by a wireless access network device, the first message including first information related to GBR services that GFBR cannot guarantee;

[0076] The second processor is used to adjust the QoS parameters of GBR services that the GFBR cannot guarantee, based on the first information.

[0077] The first information includes at least one of the following:

[0078] The reason why GFBR cannot meet the requirements;

[0079] QoS parameter recommendation information;

[0080] The QoS parameter recommendation information includes at least GFBR recommendation information.

[0081] This application also provides a wireless access network device, including: a transceiver, a processor, a memory, and a program or instructions stored in the memory and executable on the processor; when the processor executes the program or instructions, it implements the steps of the QoS adjustment method applied to the wireless access network device as described above.

[0082] This application embodiment also provides a core network device, including: a transceiver, a processor, a memory, and a program or instructions stored in the memory and executable on the processor; when the processor executes the program or instructions, it implements the steps in the QoS adjustment method applied to the core network device as described above.

[0083] This application also provides a readable storage medium storing a program or instructions thereon, characterized in that, when the program or instructions are executed by a processor, they implement the steps of the QoS adjustment method applied to a wireless access network device as described above, or implement the steps of the QoS adjustment method applied to a core network device as described above.

[0084] The beneficial effects of the above technical solution in this application are as follows:

[0085] The QoS adjustment method of this application embodiment, when a radio access network (RAN) device cannot guarantee the guaranteed flow bit rate (GFBR) for a guaranteed bit rate (GBR) service, sends a first message to a core network device. The first message includes first information; wherein the first information includes at least one of the following: the reason why the GFBR cannot be met; and QoS parameter recommendation information; wherein the QoS parameter recommendation information includes at least GFBR recommendation information. This allows the core network device to perform corresponding closed-loop adjustments to the GFBR of the GBR service that the RAN device cannot guarantee, based on the reason why the GFBR cannot be met and / or the GFBR recommendation information. This enables the RAN device to meet the adjusted GFBR requirements of the unguaranteed GBR service, thereby improving the determinism of GBR guarantee and reducing the impact of GBR users on non-GBR users, thus solving the problems of unguaranteed GFBR and public-private network collaboration in existing mechanisms. Attached Figure Description

[0086] Figure 1 This is one of the flowcharts illustrating the Quality of Service (QoS) adjustment method according to an embodiment of this application.

[0087] Figure 2 This is a second flowchart illustrating the Quality of Service (QoS) adjustment method according to an embodiment of this application.

[0088] Figure 3 This is the third flowchart illustrating the Quality of Service (QoS) adjustment method according to an embodiment of this application.

[0089] Figure 4 This is one of the structural schematic diagrams of the Quality of Service (QoS) adjustment device according to an embodiment of this application;

[0090] Figure 5 This is a second schematic diagram of the structure of the QoS adjustment device according to an embodiment of this application;

[0091] Figure 6 This is one of the structural schematic diagrams of a wireless access network device according to an embodiment of this application;

[0092] Figure 7 This is a schematic diagram of the core network equipment in an embodiment of this application;

[0093] Figure 8 This is a second schematic diagram of the structure of a wireless access network device according to an embodiment of this application. Detailed Implementation

[0094] To make the technical problems, technical solutions and advantages of this application clearer, a detailed description will be provided below in conjunction with the accompanying drawings and specific embodiments.

[0095] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments.

[0096] In the various embodiments of this application, it should be understood that the sequence number of each process described below does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0097] In addition, the terms "system" and "network" are often used interchangeably in this article.

[0098] In the embodiments provided in this application, it should be understood that "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information.

[0099] like Figure 1 As shown, the Quality of Service (QoS) adjustment method of this application embodiment is applied to a wireless access network device and includes:

[0100] Step 101: If the radio access network device cannot guarantee the guaranteed stream bit rate (GFBR) of the guaranteed bit rate GBR service, the radio access network device sends a first message to the core network device, the first message including first information.

[0101] The first information includes at least one of the following:

[0102] The reason why GFBR cannot meet the requirements;

[0103] Recommended QoS parameters;

[0104] The QoS parameter recommendation information includes at least GFBR recommendation information.

[0105] It should be noted that the inability of the radio access network device to guarantee the GFBR of the GBR service can mean that the radio resources allocated by the radio access network device for the GBR service cannot meet the GFBR requirements of the GBR service, or that the radio resources of the target cell of the radio access network device cannot meet the GFBR requirements of the GBR service. Here, the target cell can refer to the cell where the GBR service is located.

[0106] In this step, the first message can be a Protocol Data Unit Session Resource Notify Transfer (PDU Session Resource Notify Transfer) message. Specifically, this can be achieved by adding a "cause for not fulfilled" field to the PDU Session Resource Notify Transfer message to carry the reason why the GFBR cannot fulfill the requirement, and / or by adding a "suggested QoS parameter list" field to carry QoS parameter recommendation information.

[0107] The QoS adjustment method of this application embodiment, when a radio access network (RAN) device cannot guarantee the guaranteed flow bit rate (GFBR) for a guaranteed bit rate (GBR) service, sends a first message to a core network device. The first message includes first information; wherein the first information includes at least one of the following: the reason why the GFBR cannot be met; and QoS parameter recommendation information; wherein the QoS parameter recommendation information includes at least GFBR recommendation information. Thus, the core network device, based on the reason why the GFBR cannot be met and / or the GFBR recommendation information, performs a closed-loop adjustment of the GFBR for the GBR service that the RAN device cannot guarantee, enabling the RAN device to meet the adjusted GFBR requirements for the unguaranteed GBR service. This improves the determinism of GBR guarantee while reducing the impact of GBR users on ordinary users (non-GBR users), solving the problems of unguaranteed GFBR and public-private collaboration in existing mechanisms.

[0108] Furthermore, as an optional implementation, before the radio access network device sends the first message to the core network device, the method further includes:

[0109] Determine the first information related to the QoS parameters.

[0110] In other words, if the radio access network device cannot guarantee the GFBR of the GBR service, it is first necessary to determine the first information related to the QoS parameters, and then send a first message including the first information to the core network device.

[0111] It should also be noted that, prior to step 101, the method may further include:

[0112] Receive a first indication message sent by the core network device, the first indication message being used to instruct the radio access network device to enable the Quality of Service Notification (QoS Notification) function;

[0113] With QoS Notification enabled, monitor whether the radio resources allocated by the radio access network equipment can meet the radio resources required by the GFBR of the GBR service.

[0114] It is important to emphasize that core network devices can configure notification control parameters through the N2 port to instruct radio access network devices to enable the QoS Notification function.

[0115] As an optional implementation, determining the reasons why the GFBR cannot be satisfied includes:

[0116] Based on channel conditions and service scheduling waiting delay, determine the reasons why the GFBR cannot be satisfied;

[0117] The channel conditions include at least one of the following:

[0118] Reference Signal Received Power (RSRP);

[0119] Signal to Interference plus Noise Ratio (SINR).

[0120] Among them, the service scheduling waiting delay is related to the logical channel priority.

[0121] It should be noted that there may be multiple reasons why GFBR fails to meet the requirements. In practical applications, different determination methods can be selected according to the specific reasons. This application does not limit this.

[0122] As a specific implementation, the reasons why the GFBR cannot be satisfied are determined based on channel conditions and service scheduling waiting delay, including:

[0123] If the RSRP is less than the first threshold, the SINR is less than the second threshold, and there is no service scheduling waiting delay, the reason why the GFBR cannot be satisfied is determined to be a deterioration in channel conditions.

[0124] It should be noted that when the GFBR cannot be met due to deteriorating channel conditions, the spectrum efficiency of GBR users decreases. While occupying a large amount of resources, the minimum guaranteed rate still cannot be met, and ordinary users may not be able to receive services. Therefore, it is necessary to adjust the GFBR of GBR services to reduce the resources occupied by the GFBR of GBR services, so that ordinary users can also receive the corresponding services and solve the existing public-private collaboration problem.

[0125] The specific implementation process of this method will be explained below:

[0126] When a wireless access network device detects that the GFBR (Gross Receiver Bridge) for a GBR service cannot be guaranteed, it starts a pre-configured timer to count whether the SINR of the GBR user corresponding to the GBR service that the GFBR cannot guarantee is less than the first threshold, whether the RSRP is less than the second threshold, and whether there is a scheduling waiting delay for the GBR service that the GFBR cannot guarantee within a preset time period. If the SINR is less than the first threshold, the RSRP is less than the second threshold, and there is no scheduling waiting delay within the preset time period, then the reason why the GFBR cannot guarantee the service is determined to be a deterioration in channel quality.

[0127] As an optional implementation, determining the GFBR recommendation information includes:

[0128] (1) If the reason why the GFBR cannot meet the requirements is that the channel conditions have deteriorated, the category of the GBR service that the GFBR cannot guarantee shall be determined according to the 5G Quality of Service Indicator (QI) corresponding to the GBR service that the GFBR cannot guarantee.

[0129] It should be noted that in this optional implementation, the GBR service defined in the 3GPP protocol is further subdivided into rigid GBR service and non-rigid GBR service based on whether the GBR service rate can be compressed. The definitions of the two types of services are as follows:

[0130] The rigid GBR service rate cannot be compressed. For example, in machine vision product inspection, the GFBR rate must be guaranteed and cannot be compressed, otherwise it may cause missed detections or false detections.

[0131] For non-rigid GBR services, such as 4K live streaming, GFBR can be appropriately compressed, and the service side can adaptively reduce the bitrate.

[0132] The rigid and non-rigid GBR services have different 5QI values, which allows the radio access network equipment (network side) to distinguish between the two service types using the 5QI value. One possible configuration is that rigid GBR services correspond to 5QIs 67, 75, and 82-86 (which can be based on protocol extensions), while the 5QIs for other GBR services are non-rigid 5QIs.

[0133] (2) If the category of the GBR service that the GFBR cannot guarantee is non-rigid, the GFBR recommendation information is determined according to the load of the first service, wherein the first service is a service other than the GBR service that the GFBR under the radio access network device cannot satisfy.

[0134] The first service can be one or more services under the wireless access network device, and the first service can be a GBR service or a Non-GBR service.

[0135] Specifically, when the first service is a GBR service, the load of the first service is the capacity corresponding to the GFBR of the first service.

[0136] When the first service is an NGBR (Not Guaranteed Bit Rate) service, the load of the first service is the capacity corresponding to the baseline rate of the first service.

[0137] (3) If the category of GBR service that the GFBR cannot guarantee is rigid, the GFBR recommendation information is determined as the first value.

[0138] Optionally, the first value can be 0.

[0139] It should be noted here that, as mentioned earlier, the rate of rigid GBR services cannot be compressed. Therefore, the GFBR of rigid GBR services cannot be adjusted. Thus, when a rigid GBR service is a GBR service that cannot be guaranteed by the GFBR, its GFBR recommendation information is set to this first value to ensure that the radio access network device cannot provide services to users of GBR services that the GFBR cannot guarantee, thereby further deleting the GBR dedicated load of GBR services that the GFBR cannot guarantee.

[0140] As a specific implementation, the GFBR recommendation information is determined based on the load of the primary service, including:

[0141] (1) Calculate the product of the cell's average capacity and the pre-configured expansion threshold, and the difference between the load of the first service and the product of the average cell capacity and the pre-configured expansion threshold.

[0142] It should be noted here that the pre-configured expansion threshold can also be called the pre-configured maximum threshold. Therefore, this step can be performed according to the following formula:

[0143] GFBR = Cell capacity × Coefficient (expansion threshold or configured maximum threshold) - Total capacity corresponding to the GFBR of all other GBR services - Total capacity corresponding to the MinBR of all other Non-GBR services.

[0144] MinBR represents the baseline rate for regular ToC users (Non-GBR service users), and this MinBR is used to ensure that ToC users do not experience disconnections.

[0145] (2) If the difference is greater than the first value, the GFBR recommendation information is determined to be the difference;

[0146] (3) If the difference is less than or equal to the first value, the GFBR recommendation information is determined to be the first value.

[0147] In other words, the specific implementation method is as follows: First, calculate the product of the average cell capacity and the pre-configured expansion threshold value, and the difference between this product and the load of the first service. If the difference is greater than a first value, such as 0, it indicates that the radio resources of the target cell can meet the calculated GEBR requirements, and the GFBR recommendation information is determined to be the difference. If the difference is less than or equal to the first value, it indicates that the radio resources allocated by the radio access network equipment cannot meet the GFBR requirements of the GBR that the GFBR cannot guarantee, and the GFBR recommendation information is determined to be the first value.

[0148] Furthermore, as an optional implementation, the method also includes:

[0149] If the GFBR recommendation information is determined to be the first value, delete the GBR dedicated carriers for GBR services that the GFBR cannot guarantee.

[0150] When the GFBR recommendation information is set to the first value, it is determined that the radio access network device cannot serve the GBR service that the GFBR cannot guarantee. Therefore, it is necessary to remove the GBR dedicated carrier for the GBR service that the GFBR cannot guarantee.

[0151] Furthermore, as an optional implementation, the method also includes:

[0152] In the case where the GBR service that the GFBR cannot guarantee includes multiple GBR services, extract multiple first GBR services that are non-rigid, consume more resources than the first preset threshold, have a SINR less than the second preset threshold, and have an RSRP less than the third preset threshold.

[0153] Determine the GFBR recommendation information for each of the first GBR services.

[0154] In other words, when the target GBR service includes multiple GBR services, i.e., when the GFBR of multiple GBR services cannot be satisfied, the GBR services that need GFBR adjustment can be selected according to the type of GBR service, the resources occupied, and the channel quality of the GBR services. Specifically, the first GBR service with a non-rigid service category, high resource consumption, and poor channel quality can be screened first (i.e., multiple non-rigid first GBR services with resource consumption higher than the first preset threshold, SINR lower than the second preset threshold, and RSRP lower than the third preset threshold can be prioritized). Then, the GFBR recommendation information of multiple first GBR services is determined in sequence. By adjusting the GFBR of multiple first GBR services, the resources occupied by the first GBR services are reduced, thereby increasing the resources that other GBR services and / or non-GBR services can occupy, ultimately ensuring that the GFBR of all GBR services and the MinBR of Non-GBR services are satisfied. An optional implementation process can be as follows: First, for GBR services that GFBR cannot guarantee, classify each GBR service according to rigid / non-rigid categories; second, for non-rigid GBR services, extract services whose resource consumption is higher than a first preset threshold, SINR is lower than a second preset threshold, and RSRP is lower than a third preset threshold, forming a first non-rigid GBR service set; third, determine the GFBR recommendation information for each GBR service in the first non-rigid GBR service set. Specifically, the order in which the GFBR recommendation information for each GBR service in the first non-rigid GBR service set is determined can be in descending order of resource consumption and ascending order of channel conditions.

[0155] Furthermore, as an optional implementation, the method also includes:

[0156] (1) The wireless access network device receives a second message sent by the core network device, the second message including: the reason why the GFBR cannot be satisfied and the verification result of the GFBR recommendation information;

[0157] In other words, after receiving the first message from the radio access network device, the core network device will verify the reason why the GFBR cannot be met and the GFBR recommendation information carried in the first message, and send the verification result to the radio access network device. For example, the specific verification can be that if the reason why the GFBR cannot be met is the deterioration of channel quality, and the recommended value in the GFBR recommendation information is less than the current GFBR, then the verification passes. After the verification passes, the core network device decides to use the GFBR recommendation information reported by the radio access network device to adjust the GFBR of the GBR service that the GFBR cannot guarantee to the recommended value in the corresponding GFBR recommendation information.

[0158] (2) If the verification result is successful, monitor the GBR services that the GFBR cannot guarantee;

[0159] (3) If it is determined that the radio access network device can guarantee the GFBR before the GBR service adjustment that the GFBR cannot guarantee, a third message is sent to the core network device. The third message includes: an indication that the radio access network device can guarantee the GFBR before the GBR service adjustment that the GFBR cannot guarantee, and the GFBR before the GBR service adjustment that the GFBR cannot guarantee.

[0160] The GFBR before adjustment is the GFBR before it was adjusted to the recommended value in the GFBR recommendation information.

[0161] It should be noted that the third message can be a PDU Session Resource Notify Transfer message. The radio access network device can ensure that the indication information of the GFBR before the adjustment of the GBR service that the GFBR cannot guarantee is carried in the cause for not fulfilled field, and the GFBR before the adjustment is carried in the suggested QoS parameterlist field.

[0162] In other words, after the GFBR adjusts the GBR for GBR services that the GFBR cannot guarantee, the radio access network equipment continuously monitors the GBR users whose parameters have been adjusted. If the channel conditions improve (e.g., SINR is higher than a certain threshold, and the original GFBR + other GFBRs and MinBR < average cell capacity * coefficient), the equipment reports a PDU Session Resource NotifyTransfer message to the SMF of the core network equipment. In this message, the Notification Cause is "fulfilled", the suggested QoS parameter list is the original QoS parameters before the adjustment, and the original GFBR and other QoS flow-related parameters are restored.

[0163] This application's QoS adjustment method proposes a closed-loop guarantee optimization scheme and related process for GBR services based on QoS Notification. On one hand, the radio access network device can identify the reasons for GFBR non-fulfillment based on SINR, RSRP, etc., and estimate the suggested QoS parameter adjustment values ​​based on network load. On the other hand, a "Cause for not fulfilled" and "suggested QoS parameter list" field is added to the PDU SessionResource Notify Transfer message, allowing the core network device to adjust GFBR-related parameters in a closed loop based on the cause values. Furthermore, the core network device can decide whether to adjust the relevant parameters of the GBR QoS flow in a closed loop based on the suggested QoS parameter values ​​according to the cause values ​​reported by the radio access network device, improving the certainty of GBR service guarantee while minimizing the impact on ordinary Non-GBR ToC users.

[0164] like Figure 2 As shown in the embodiments of this application, a QoS adjustment method is also provided, applied to core network equipment, the method comprising:

[0165] Step 201: The core network device receives a first message sent by the radio access network device, the first message including first information related to the GFBR of the GBR service that the GFBR cannot guarantee;

[0166] Step 202: Based on the first information, adjust the GFBR that cannot provide GBR services;

[0167] The first information includes at least one of the following:

[0168] The reason why GFBR cannot meet the requirements;

[0169] Recommended QoS parameters;

[0170] The QoS parameter recommendation information includes at least GFBR recommendation information.

[0171] According to the first information in the first message, this application embodiment adjusts the GFBR of GBR for GBR services that the GFBR cannot guarantee, realizes closed-loop adjustment of GFBR, improves the certainty of GBR service guarantee, minimizes the impact on ordinary users, and solves the existing public-private collaboration problem.

[0172] As an optional implementation, step 202, based on the first information, adjusts the QoS parameters of the GBR services that the GFBR cannot guarantee, including:

[0173] The reasons why the GFBR cannot be satisfied and the GFBR recommendation information are verified;

[0174] For example, the verification process is as follows: if the GFBR cannot be satisfied because the channel quality has deteriorated and the GFBR recommendation information is less than the current GFBR, then the verification passes; otherwise, the verification fails.

[0175] If the verification passes, adjust the QoS parameters of the GBR services that the GFBR cannot guarantee, based on the GFBR recommendation information.

[0176] Specifically, this step involves adjusting the GFBR of GBR services that GFBR cannot guarantee to the recommended values ​​in the GFBR recommendation information.

[0177] Furthermore, as an optional implementation, the method also includes:

[0178] The core network device sends a second message to the radio access network device, the second message including: the reason why the GFBR cannot be satisfied and the verification result of the GFBR recommendation information.

[0179] In this way, wireless access network devices can monitor GBR services that GFBR cannot guarantee based on the second message.

[0180] Furthermore, as an optional implementation, the method also includes:

[0181] The core network device receives a third message sent by the radio access network device, the third message including: an indication that the radio access network device can guarantee the GFBR before the adjustment of the GBR service that the GFBR cannot guarantee, and the GFBR before the adjustment of the GBR service that the GFBR cannot guarantee;

[0182] Based on the third message, the core network equipment adjusts the GFBR of the GBR service that the GFBR cannot guarantee back to the original GFBR.

[0183] Below, in conjunction with Figure 3 The QoS adjustment method of this application embodiment will be described as follows:

[0184] Step 301: The core network instructs the base station to enable the QoS Notification function; specifically, this step involves the core network device configuring Notification Control parameters through the N2 port to instruct the radio access network device (base station) to enable the QoS Notification function.

[0185] Step 302: The base station determines the reason why GFBR cannot be satisfied based on factors such as channel conditions and scheduling waiting delay, and puts GBR services that meet the preset conditions of SINR, RSRP, and scheduling waiting delay into the adjustment queue.

[0186] Specifically, this step is as follows: when the cell has GBR services that cannot guarantee GFBR, the radio access network equipment determines the reason why GFBR cannot be satisfied based on factors such as channel conditions.

[0187] It should be noted that there may be various reasons why a wireless access network device cannot guarantee GFBR. This application takes CASE A in Embodiment 1 as an example. Other reasons can be further expanded according to actual needs. CASE A is defined as follows:

[0188] CASE A: Deteriorating channel conditions prevent GFBR from meeting requirements. In this case, GBR users experience reduced spectral efficiency, failing to meet the minimum guaranteed rate despite consuming significant resources, and potentially leaving ordinary users without service.

[0189] Radio access network (RAN) devices can determine the reasons why GFBR (Guided Flow Protocol) cannot be satisfied based on RSRP (Restricted RSRP) and logical channel priority. For example, when GFBR cannot be satisfied, the RAN device starts a timer to count the SINR (Signal Indicator) and RSRP (Restricted RSRP) values ​​of GBR users and the service scheduling waiting delay over a period of time. If SINR and RSRP are both less than a certain preset threshold and there is no scheduling waiting delay, then the reason for GFBR failure is determined to be CASE A.

[0190] Step 303: The base station prioritizes adjusting non-rigid GBRs with SINR, RSRP below a preset threshold, and PRB resource usage above a preset threshold, and comprehensively considers the load of other network services to estimate and obtain GBR service parameter adjustment suggestions;

[0191] Specifically, this step can be as follows: If the base station identifies that the GFBR does not meet the requirements for CASE A, then it comprehensively considers the load of other network services and differentiates between rigid and non-rigid GBR services to estimate and obtain GBR-related parameter adjustment suggestions. One possible estimation method is as follows:

[0192] First, based on whether the GBR service rate can be compressed, the GBR service defined in the 3GPP protocol is further subdivided into rigid / non-rigid GBR services, and the definitions of the two services are as follows.

[0193] Rigid GBR services, such as machine vision product inspection, cannot have their bitrate compressed. The GFBR rate must be guaranteed and cannot be compressed, otherwise it may lead to missed or false detections. Non-rigid GBR services, such as 4K live streaming, can have their GFBR appropriately compressed, and the service side can adaptively reduce the bitrate.

[0194] Rigid and non-rigid GBR services correspond to different 5QI values, which are used by the network side to distinguish between the two service types. One possible configuration is that rigid GBR corresponds to 5QI 67, 75, and 82-86 (which can be based on protocol extensions), while the remaining GBR 5QIs are non-rigid 5QIs.

[0195] 1) If the GBR service is a non-rigid GBR service, the recommended GFBR value calculation formula is as follows:

[0196] GFBR = Average cell capacity * Coefficient (expansion threshold or configured maximum threshold) - Total capacity of all other services' GFBR / MinBR

[0197] MinBR represents the baseline rate for regular ToC users, ensuring they don't experience disconnections. If GFBR calculated using the above formula is less than 0, then the GBR dedicated loadout is deleted.

[0198] 2) If the GBR service is a rigid GBR, delete the dedicated GBR service directly.

[0199] 3) If the base station identifies that the GFBR of multiple GBR bearers cannot be satisfied, it will prioritize adjusting non-rigid GBR services with resource consumption exceeding a certain preset threshold and SINR and RSRP both below a certain threshold, until the GFBR / MinBR of all GBR and Non-GBR services are satisfied.

[0200] Step 304: The base station reports the reasons why the GFBR of all adjusted GBR services is not met and the recommended QoS parameters to be adjusted;

[0201] This step is specifically as follows:

[0202] The reporting of cause values ​​involves changes to the N2 interface protocol. One possible solution is to add a "Cause for not fulfilled" field to the PDU Session ResourceNotify Transfer message as follows. The optional cause values ​​for GFBR not being met are only defined for CASE A in this proposal. This can be expanded. If the cause is not determined to be CASE A, this field should not be filled in.

[0203] Step 305: The core network decides whether to adopt the recommended QoS parameters reported by the base station;

[0204] This step involves the core network equipment making QoS update decisions and executing. Specifically, the core network equipment's SMF verifies the reason value in the Notification message reported by the radio access network to determine whether to adopt the recommended QoS parameters reported by the radio access network equipment. For example, if the reason is not met (CASE A), and the recommended GFBR is lowered, the verification will pass. If the verification passes, the QoS modify process is initiated to modify the QoS parameters, achieving closed-loop management.

[0205] Step 306: The base station continuously monitors GBR users. If the channel conditions improve, it replies with the original QoS flow parameters such as 5QI and GFBR.

[0206] In other words, after the parameters are adjusted, the wireless access network equipment continuously monitors the GBR users whose parameters have been adjusted. If the channel conditions improve (e.g., SINR is higher than a certain threshold, and the original GFBR + other GFBRs and MinBR < cell average capacity * coefficient), it reports the SMF (Notification Cause in PDU Session Resource Notify Transfer is fulfilled, and the suggested QoS parameter list parameters are the original QoS parameters before adjustment) and restores the original GFBR and other QoS flow-related parameters.

[0207] like Figure 4 As shown in the illustration, this application also provides a Quality of Service (QoS) adjustment device, applied to a wireless access network device, the device comprising:

[0208] The first sending module 401 is used to send a first message to the core network device when the radio access network device cannot guarantee the guaranteed stream bit rate (GFBR) of the guaranteed bit rate (GBR) service. The first message includes the first information.

[0209] The first information includes at least one of the following:

[0210] The reason why GFBR cannot meet the requirements;

[0211] QoS parameter recommendation information;

[0212] The QoS parameter recommendation information includes at least GFBR recommendation information.

[0213] The QoS adjustment apparatus of this application embodiment sends a first message including first information to the core network device, enabling the core network device to perform closed-loop adjustment of the GFBR for GBR services that the radio access network device cannot guarantee based on the first message. This improves the deterministic guarantee of GBR services and reduces the impact on ordinary users.

[0214] Optionally, the device further includes:

[0215] The first determining module is used to determine the first information related to the QoS parameters.

[0216] Optionally, the first determining module includes:

[0217] The first determining submodule is used to determine the reason why the GFBR cannot be satisfied based on channel conditions and service scheduling waiting delay;

[0218] The channel conditions include at least one of the following:

[0219] Reference signal received power RSRP;

[0220] Signal interference plus noise SINR.

[0221] Specifically, the first determining submodule is used to: determine that the reason why the GFBR cannot be satisfied is the deterioration of channel conditions when the RSRP is less than the first threshold, the SINR is less than the second threshold, and there is no service scheduling waiting delay.

[0222] Optionally, the first determining module includes:

[0223] The second determining submodule is used to determine the category of the GBR service that the GFBR cannot guarantee, based on the 5G Quality of Service Indicator (5QI) corresponding to the GBR service that the GFBR cannot guarantee, when the reason why the GFBR cannot guarantee is the deterioration of channel conditions.

[0224] The third determining submodule is used to determine the GFBR recommendation information based on the load of the first service when the category of the GBR service that the GFBR cannot guarantee is non-rigid. The first service is a service other than the GBR service that the GFBR cannot guarantee under the radio access network device.

[0225] The fourth determination submodule is used to determine the GFBR recommendation information as the first value when the category of GBR service that the GFBR cannot guarantee is rigid.

[0226] Specifically, the fourth determining submodule includes:

[0227] The calculation unit is used to calculate the product of the cell's average capacity and the pre-configured expansion threshold, and the difference between the load of the first service;

[0228] The first determining unit is configured to determine the GFBR recommendation information as the difference when the difference is greater than the first value;

[0229] The second determining unit is configured to determine the GFBR recommendation information as the first value when the difference is less than or equal to the first value.

[0230] Optionally, when the first service is a GBR service, the load of the first service is the capacity corresponding to the GFBR of the first service;

[0231] When the first service is an NGBR (Not Guaranteed Bit Rate) service, the load of the first service is the capacity corresponding to the baseline rate of the first service.

[0232] Furthermore, the device also includes:

[0233] The deletion module is used to delete GBR dedicated carriers for GBR services that cannot be guaranteed by GFBR when the GFBR recommendation information is determined to be the first value.

[0234] Furthermore, the device also includes:

[0235] The extraction module is used to extract multiple first GBR services that are non-rigid, have resource consumption higher than a first preset threshold, SINR less than a second preset threshold, and RSRP less than a third preset threshold when the GBR services that the GFBR cannot guarantee include multiple GBR services.

[0236] The second determining module is used to determine the GFBR recommendation information for each of the first GBR services.

[0237] Furthermore, the device also includes:

[0238] The receiving module is configured to receive a second message sent by the core network device, the second message including: the reason why the GFBR cannot be satisfied and the verification result of the GFBR recommendation information;

[0239] The monitoring module is used to monitor GBR services that the GFBR cannot guarantee when the verification result is successful.

[0240] The second sending module is configured to send a third message to the core network device when it is determined that the radio access network device can guarantee the GFBR before the GBR service adjustment that the GFBR cannot guarantee. The third message includes: indication information that the radio access network device can guarantee the GFBR before the GBR service adjustment that the GFBR cannot guarantee, and the GFBR before the GBR service adjustment that the GFBR cannot guarantee.

[0241] like Figure 5As shown in the illustration, this application also provides a Quality of Service (QoS) adjustment device, applied to core network equipment, the device comprising:

[0242] The first receiving module 501 is used to receive a first message sent by the wireless access network device, the first message including first information related to GBR services that GFBR cannot guarantee;

[0243] The first adjustment module 502 is used to adjust the QoS parameters of GBR services that the GFBR cannot guarantee based on the first information.

[0244] The first information includes at least one of the following:

[0245] The reason why GFBR cannot meet the requirements;

[0246] Recommended QoS parameters;

[0247] The QoS parameter recommendation information includes at least GFBR recommendation information.

[0248] The QoS adjustment device of this application adjusts the GFBR of GBR services that the GFBR cannot guarantee based on the first information in the first message sent by the RFID device. This achieves closed-loop management of GBR services that the GFBR cannot guarantee, improves the certainty of GBR service guarantee, and reduces the impact on ordinary users.

[0249] Optionally, the first adjustment module 502 includes:

[0250] The verification submodule is used to verify the reasons why the GFBR cannot be satisfied and the GFBR recommendation information;

[0251] The adjustment submodule is used to adjust the GFBR for GBR services that the GFBR cannot guarantee, based on the GFBR recommendation information, if the verification passes.

[0252] Optionally, the device further includes:

[0253] The sending module is used to send a second message to the wireless access network device. The second message includes: the reason why the GFBR cannot be satisfied and the verification result of the GFBR recommendation information.

[0254] Optionally, the device further includes:

[0255] The second receiving module is used to receive a third message sent by the radio access network device. The third message includes: an indication that the radio access network device can guarantee the GFBR before the adjustment of the GBR service that the GFBR cannot guarantee, and the GFBR before the adjustment of the GBR service that the GFBR cannot guarantee.

[0256] The second adjustment module is used to adjust the GFBR of the GBR service that the GFBR cannot guarantee back to the original GFBR according to the third message.

[0257] like Figure 6 As shown, this application embodiment also provides a wireless access network device 600, including: a first transceiver 610 and a first processor 620;

[0258] The first transceiver 610 is used to send a first message to the core network device when the radio access network device cannot guarantee the guaranteed stream bit rate (GFBR) of the guaranteed bit rate (GBR) service. The first message includes first information.

[0259] The first information includes at least one of the following:

[0260] The reason why GFBR cannot meet the requirements;

[0261] QoS parameter recommendation information;

[0262] The QoS parameter recommendation information includes at least GFBR recommendation information.

[0263] The wireless access network device in this application embodiment sends a first message to the core network device, including the reason why the GFBR cannot be met and / or the GFBR recommendation information. This allows the core network device to make closed-loop adjustments to the GFBR for GBR services that the GFBR cannot guarantee based on the first message, thereby improving the certainty of GBR service guarantee and reducing the impact on ordinary users.

[0264] like Figure 7 As shown in the figure, this application embodiment also provides a core network device 700, including: a second transceiver 720 and a second processor 710;

[0265] The second transceiver 720 is used to receive a first message sent by a wireless access network device, the first message including first information related to GBR services that GFBR cannot guarantee;

[0266] The second processor 710 is used to adjust the QoS parameters of GBR services that the GFBR cannot guarantee, based on the first information.

[0267] The first information includes at least one of the following:

[0268] The reason why GFBR cannot meet the requirements;

[0269] QoS parameter recommendation information;

[0270] The QoS parameter recommendation information includes at least GFBR recommendation information.

[0271] The core network device in this application embodiment adjusts the GFBR of GBR services that cannot be guaranteed by the GFBR according to the first information in the first message sent by the radio access network device, thereby realizing closed-loop management of GBR services that cannot be guaranteed by the GFBR, improving the certainty of GBR service guarantee, and reducing the impact on ordinary users.

[0272] like Figure 8 As shown, this application embodiment also provides a wireless access network device, including: a transceiver 810, a processor 800, a memory 820, and a program or instructions stored in the memory 820 and executable on the processor 800; when the processor 800 executes the program or instructions, it implements the steps of the QoS adjustment method applied to the wireless access network device as described above.

[0273] The transceiver 810 is used to receive and send data under the control of the processor 800.

[0274] Among them, Figure 8 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 800) and memory (memory 820). The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 810 can be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium.

[0275] The processor 800 is responsible for managing the bus architecture and general processing, while the memory 820 can store the data used by the processor 800 during operation.

[0276] This application embodiment also provides a core network device, including: a transceiver, a processor, a memory, and a program or instructions stored in the memory and executable on the processor; when the processor executes the program or instructions, it implements the steps in the service quality adjustment method applied to the core network device as described above.

[0277] The transceiver is used to receive and send data under the control of the processor.

[0278] The structure of the core network equipment is similar to that of the wireless access network equipment; therefore, the interfaces of the core network equipment can be found in [reference needed]. Figure 8 The structure of a wireless access network device, wherein in the core network device, the bus architecture can include any number of interconnected buses and bridges, specifically linked together by various circuits of one or more processors represented by processors and memories represented by memory. The bus architecture can also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. A transceiver can be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium.

[0279] This application also provides a readable storage medium storing a program or instructions. When executed by a processor, the program or instructions implement the steps of the QoS adjustment method for wireless access network devices as described above, or implement the steps of the QoS adjustment method for core network devices as described above, achieving the same technical effect. To avoid repetition, these will not be elaborated further here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0280] It should be further noted that the user devices described in this specification include, but are not limited to, smartphones, tablets, etc., and many of the described functional components are referred to as modules in order to more specifically emphasize the independence of their implementation.

[0281] In this embodiment, the module can be implemented in software so that it can be executed by various types of processors. For example, an identified executable code module may include one or more physical or logical blocks of computer instructions, which may be constructed as objects, procedures, or functions. Nevertheless, the executable code of the identified module does not need to be physically located together, but may include different instructions stored in different bits, which, when logically combined, constitute the module and achieve the module's intended purpose.

[0282] In practice, an executable code module can be a single instruction or many instructions, and can even be distributed across multiple different code segments, different programs, and across multiple memory devices. Similarly, operational data can be identified within the module and can be implemented in any suitable form and organized within any suitable type of data structure. This operational data can be collected as a single dataset or distributed across different locations (including different storage devices), and can exist, at least in part, solely as electronic signals within the system or network.

[0283] When a module can be implemented using software, considering the current level of hardware technology, modules that can be implemented in software can be implemented using hardware circuits by those skilled in the art to achieve the corresponding functions, without considering cost. These hardware circuits include conventional very-large-scale integrated circuits (VLSI) or gate arrays, as well as existing semiconductors such as logic chips and transistors, or other discrete components. Modules can also be implemented using programmable hardware devices, such as field-programmable gate arrays, programmable array logic, and programmable logic devices.

[0284] The exemplary embodiments described above are with reference to the accompanying drawings. Many different forms and embodiments are feasible without departing from the spirit and teachings of this application. Therefore, this application should not be construed as limiting the exemplary embodiments set forth herein. Rather, these exemplary embodiments are provided to make this application complete and convey the scope of this application to those skilled in the art. In these drawings, component dimensions and relative dimensions may be exaggerated for clarity. The terminology used herein is for the purpose of describing particular exemplary embodiments only and is not intended to be limiting. As used herein, unless clearly indicated otherwise, the singular forms “a,” “an,” and “the” are intended to include all such forms. It will be further understood that the terms “comprising” and / or “including”, when used in this specification, indicate the presence of the stated features, integers, steps, operations, components, and / or elements, but do not exclude the presence or addition of one or more other features, integers, steps, operations, components, and / or groups thereof. Unless otherwise indicated, when stated, a range of values ​​includes the upper and lower limits of the range and any subranges in between.

[0285] The above description is the preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principles described in this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for adjusting Quality of Service (QoS), characterized in that, Applied to wireless access network devices, the method includes: When the radio access network device is unable to guarantee the guaranteed stream bit rate (GFBR) of the guaranteed bit rate (GBR) service, the radio access network device sends a first message to the core network device, the first message including first information. The first information includes at least one of the following: The reason why GFBR cannot meet the requirements; Recommended QoS parameters; The QoS parameter recommendation information includes at least GFBR recommendation information; Before the wireless access network device sends the first message to the core network device, the method further includes: Determine the first information related to the QoS parameters; The determination of the GFBR recommendation information includes: When the reason why the GFBR cannot be met is due to deteriorating channel conditions, the category of the GBR service that the GFBR cannot guarantee is determined according to the 5G Quality of Service Indicator (5QI) corresponding to the GBR service that the GFBR cannot guarantee. When the category of GBR service that the GFBR cannot guarantee is non-rigid, the GFBR recommendation information is determined based on the load of the first service, wherein the first service is a service other than the GBR service that the GFBR cannot guarantee under the radio access network device. If the category of GBR service that GFBR cannot guarantee is rigid, the GFBR recommendation information is determined to be a first value, and the GBR service is deleted; wherein, the first value is 0; Non-rigid GBR services are GBR services whose rates can be compressed; rigid GBR services are GBR services whose rates cannot be compressed.

2. The method according to claim 1, characterized in that, The reasons why the GFBR cannot be satisfied include: Based on channel conditions and service scheduling waiting delay, determine the reasons why the GFBR cannot be satisfied; The channel conditions include at least one of the following: Reference signal received power RSRP; Signal interference plus noise SINR.

3. The method according to claim 2, characterized in that, Based on channel conditions and service scheduling waiting delay, determine the reasons why the GFBR cannot be satisfied, including: If the RSRP is less than the first threshold, the SINR is less than the second threshold, and there is no service scheduling waiting delay, the reason why the GFBR cannot be satisfied is determined to be a deterioration in channel conditions.

4. The method according to claim 1, characterized in that, Based on the load of the first service, determine the GFBR recommendation information, including: Calculate the product of the cell's average capacity and the pre-configured expansion threshold, and the difference between this product and the load of the first service. If the difference is greater than the first value, the GFBR recommendation information is determined to be the difference. If the difference is less than or equal to the first value, the GFBR recommendation information is determined to be the first value.

5. The method according to claim 1 or 4, characterized in that, When the first service is a GBR service, the load of the first service is the capacity corresponding to the GFBR of the first service; When the first service is an NGBR (Not Guaranteed Bit Rate) service, the load of the first service is the capacity corresponding to the baseline rate of the first service.

6. The method according to claim 1 or 4, characterized in that, The method further includes: If the GFBR recommendation information is determined to be the first value, delete the GBR dedicated carriers for GBR services that the GFBR cannot guarantee.

7. The method according to claim 1, characterized in that, The method further includes: In the case where the GBR service that the GFBR cannot guarantee includes multiple GBR services, extract multiple first GBR services that are non-rigid, consume more resources than the first preset threshold, have a SINR less than the second preset threshold, and have an RSRP less than the third preset threshold. Determine the GFBR recommendation information for each of the first GBR services.

8. The method according to claim 1, characterized in that, The method further includes: The wireless access network device receives a second message sent by the core network device, the second message including: the reason why the GFBR cannot be satisfied and the verification result of the GFBR recommendation information; If the verification result is successful, monitor the GBR services that the GFBR cannot guarantee; If it is determined that the radio access network device can guarantee the GFBR before the GBR service adjustment that the GFBR cannot guarantee, a third message is sent to the core network device. The third message includes: an indication that the radio access network device can guarantee the GFBR before the GBR service adjustment that the GFBR cannot guarantee, and the GFBR before the GBR service adjustment that the GFBR cannot guarantee.

9. A method for adjusting Quality of Service (QoS), characterized in that, Applied to core network equipment, the method includes: The core network equipment receives a first message sent by the radio access network equipment, the first message including first information related to GBR services that GFBR cannot guarantee; Based on the first information, the core network equipment adjusts the QoS parameters of GBR services that the GFBR cannot guarantee; The first information includes at least one of the following: The reason why GFBR cannot meet the requirements; Recommended QoS parameters; The QoS parameter recommendation information includes at least GFBR recommendation information. When the category of the GBR service that GFBR cannot guarantee is non-rigid, the GFBR recommendation information is determined based on the load of a first service, where the first service is a service other than the GBR service that GFBR cannot guarantee under the radio access network device. When the category of the GBR service that GFBR cannot guarantee is rigid, the GFBR recommendation information is a first value, where the first value is 0. When the reason GFBR cannot meet the requirement is deteriorating channel conditions, the category of the GBR service is determined based on the 5G Quality of Service Indicator (5QI) corresponding to the GBR service; non-rigid GBR services are GBR services whose rates can be compressed; rigid GBR services are GBR services whose rates cannot be compressed.

10. The method according to claim 9, characterized in that, Based on the first information, the core network equipment adjusts the QoS parameters of GBR services that the GFBR cannot guarantee, including: The reasons why the GFBR cannot be satisfied and the GFBR recommendation information are verified; If the verification passes, adjust the QoS parameters of the GBR services that the GFBR cannot guarantee, based on the GFBR recommendation information.

11. The method according to claim 10, characterized in that, The method further includes: The core network device sends a second message to the radio access network device, the second message including: the reason why the GFBR cannot be satisfied and the verification result of the GFBR recommendation information.

12. The method according to claim 10, characterized in that, The method further includes: The core network device receives a third message sent by the radio access network device, the third message including: an indication that the radio access network device can guarantee the GFBR before the adjustment of the GBR service that the GFBR cannot guarantee, and the GFBR before the adjustment of the GBR service that the GFBR cannot guarantee; Based on the third message, the core network equipment adjusts the GFBR of the GBR service that the GFBR cannot guarantee back to the original GFBR.

13. A Quality of Service (QoS) adjustment device, characterized in that, Applied to wireless access network equipment, the device includes: The first sending module is used to send a first message to the core network device when the radio access network device cannot guarantee the guaranteed stream bit rate (GFBR) of the guaranteed bit rate (GBR) service. The first message includes first information. The first information includes at least one of the following: The reason why GFBR cannot meet the requirements; QoS parameter recommendation information; The QoS parameter recommendation information includes at least GFBR recommendation information; The device further includes: The first determining module is used to determine the first information related to the QoS parameters; The first determining module includes: The second determining submodule is used to determine the category of the GBR service that the GFBR cannot guarantee, based on the 5G Quality of Service Indicator (5QI) corresponding to the GBR service that the GFBR cannot guarantee, when the reason why the GFBR cannot guarantee is the deterioration of channel conditions. The third determining submodule is used to determine the GFBR recommendation information based on the load of the first service when the category of the GBR service that the GFBR cannot guarantee is non-rigid. The first service is a service other than the GBR service that the GFBR cannot guarantee under the radio access network device. The fourth determining submodule is used to determine the GFBR recommendation information as a first value and delete the GBR service when the category of the GBR service that the GFBR cannot guarantee is rigid; wherein, the first value is 0; Non-rigid GBR services are GBR services whose rates can be compressed; rigid GBR services are GBR services whose rates cannot be compressed.

14. A Quality of Service (QoS) adjustment device, characterized in that, Applied to core network equipment, the device includes: The first receiving module is configured to receive a first message sent by a wireless access network device, the first message including first information related to GBR services that cannot be guaranteed by GFBR; The first adjustment module is used to adjust the QoS parameters of GBR services that the GFBR cannot guarantee, based on the first information. The first information includes at least one of the following: The reason why GFBR cannot meet the requirements; QoS parameter recommendation information; The QoS parameter recommendation information includes at least GFBR recommendation information. When the category of the GBR service that GFBR cannot guarantee is non-rigid, the GFBR recommendation information is determined based on the load of a first service, where the first service is a service other than the GBR service that GFBR cannot guarantee under the radio access network device. When the category of the GBR service that GFBR cannot guarantee is rigid, the GFBR recommendation information is a first value, where the first value is 0. When the reason GFBR cannot meet the requirement is deteriorating channel conditions, the category of the GBR service is determined based on the 5G Quality of Service Indicator (5QI) corresponding to the GBR service. Non-rigid GBR services are GBR services whose rates can be compressed; rigid GBR services are GBR services whose rates cannot be compressed.

15. A wireless access network device, characterized in that, include: First transceiver and first processor; The first transceiver is used to send a first message to the core network device when the radio access network device cannot guarantee the guaranteed stream bit rate (GFBR) of the guaranteed bit rate (GBR) service. The first message includes first information. The first information includes at least one of the following: The reason why GFBR cannot meet the requirements; QoS parameter recommendation information; The QoS parameter recommendation information includes at least GFBR recommendation information; The determination of the GFBR recommendation information includes: When the reason why the GFBR cannot be met is due to deteriorating channel conditions, the category of the GBR service that the GFBR cannot guarantee is determined according to the 5G Quality of Service Indicator (5QI) corresponding to the GBR service that the GFBR cannot guarantee. When the category of GBR service that the GFBR cannot guarantee is non-rigid, the GFBR recommendation information is determined based on the load of the first service, wherein the first service is a service other than the GBR service that the GFBR cannot guarantee under the radio access network device. If the category of GBR service that GFBR cannot guarantee is rigid, the GFBR recommendation information is determined to be a first value, and the GBR service is deleted; wherein, the first value is 0; Non-rigid GBR services are GBR services whose rates can be compressed; rigid GBR services are GBR services whose rates cannot be compressed.

16. A core network device, characterized in that, include: Second transceiver and second processor; The second transceiver is used to receive a first message sent by a wireless access network device, the first message including first information related to GBR services that GFBR cannot guarantee; The second processor is used to adjust the QoS parameters of GBR services that the GFBR cannot guarantee, based on the first information. The first information includes at least one of the following: The reason why GFBR cannot meet the requirements; QoS parameter recommendation information; The QoS parameter recommendation information includes at least GFBR recommendation information. When the category of the GBR service that GFBR cannot guarantee is non-rigid, the GFBR recommendation information is determined based on the load of a first service, where the first service is a service other than the GBR service that GFBR cannot guarantee under the radio access network device. When the category of the GBR service that GFBR cannot guarantee is rigid, the GFBR recommendation information is a first value, where the first value is 0. Non-rigid GBR services are GBR services whose service rate can be compressed; rigid GBR services are GBR services whose service rate cannot be compressed.

17. A wireless access network device, comprising: A transceiver, a processor, a memory, and a program or instructions stored in the memory and executable on the processor; characterized in that, when the processor executes the program or instructions, it implements the steps of the Quality of Service (QoS) adjustment method as described in any one of claims 1 to 8.

18. A core network device, comprising: A transceiver, a processor, a memory, and a program or instructions stored in the memory and executable on the processor; characterized in that, when the processor executes the program or instructions, it implements the steps of the Quality of Service (QoS) adjustment method as described in any one of claims 9 to 12.

19. A readable storage medium having a program or instructions stored thereon, characterized in that, When the program or instructions are executed by the processor, they implement the steps of the QoS adjustment method as described in any one of claims 1 to 8, or implement the steps of the QoS adjustment method as described in any one of claims 9 to 12.

Images