Network congestion processing method and apparatus, electronic device, and storage medium

Abstract

The application discloses a network congestion processing method and device, electronic equipment and storage medium, and belongs to the technical field of communication. The method comprises the following steps: determining a network congestion cause based on an uplink transmission parameter; and performing network congestion processing based on the network congestion cause.

Description

Technical Field

[0001] This application belongs to the field of communication technology, and specifically relates to a network congestion handling method, apparatus, electronic device and storage medium. Background Technology

[0002] When users browse videos or web pages on electronic devices, poor network signal can cause slow loading or buffering. However, if the device cannot recognize that network congestion is the cause, it cannot perform rapid data recovery in this abnormal scenario.

[0003] Currently, most methods for identifying congestion are implemented at the application layer or framework layer, resulting in low efficiency and accuracy, and failing to achieve timely and effective congestion handling. Summary of the Invention

[0004] The purpose of this application is to provide a network congestion handling method, apparatus, electronic device, and storage medium that can improve the effectiveness and timeliness of congestion handling.

[0005] In a first aspect, embodiments of this application provide a network congestion handling method, the method comprising:

[0006] Determine the cause of network congestion based on uplink transmission parameters;

[0007] Based on the aforementioned network congestion causes, network congestion processing is performed. Secondly, embodiments of this application provide a network congestion processing apparatus, which includes:

[0008] The congestion cause determination module is used to determine the cause of network congestion based on uplink transmission parameters;

[0009] The congestion handling execution module is used to perform network congestion handling based on the reasons for network congestion.

[0010] Thirdly, embodiments of this application provide an electronic device including a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions, when executed by the processor, implementing the steps of the method described in the first aspect.

[0011] Fourthly, embodiments of this application provide a readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect.

[0012] Fifthly, embodiments of this application provide a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the method as described in the first aspect.

[0013] In a sixth aspect, embodiments of this application provide a computer program product stored in a storage medium, which is executed by at least one processor to implement the method described in the first aspect.

[0014] In this embodiment of the application, the cause of network congestion is determined by the uplink transmission parameters, avoiding the low efficiency and accuracy caused by identifying congestion at the application layer or framework layer, thereby improving the efficiency and accuracy of congestion identification. Then, based on the cause of network congestion, network congestion processing is performed to improve the effectiveness and timeliness of congestion processing. Attached Figure Description

[0015] Figure 1 This is a flowchart illustrating a network congestion handling method provided in some embodiments of this application;

[0016] Figure 2 This is a schematic diagram of the NR user plane protocol stack provided in some embodiments of this application;

[0017] Figure 3 This is a flowchart illustrating a network congestion handling method provided in some embodiments of this application;

[0018] Figure 4 These are schematic diagrams of the network congestion processing apparatus provided in some embodiments of this application;

[0019] Figure 5 These are schematic diagrams of the structure of electronic devices provided in some embodiments of this application;

[0020] Figure 6 A schematic diagram of the hardware structure of an electronic device for implementing some embodiments of this application. Detailed Implementation

[0021] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0022] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0023] First, let's introduce the following: 5G is a next-generation mobile communication technology with two network deployment schemes: Non-Standalone (NSA) and Standalone (SA), which have significant differences. NSA networks are deployed on existing 4G infrastructure, with some services and functions still relying on the 4G network. Its advantages include reduced construction costs and rapid coverage. NSA transmits 5G signals by modifying 4G base stations, resulting in fast initial deployment and low cost, allowing for rapid 5G adoption and enabling as many users as possible to enjoy it. SA, on the other hand, requires the construction of independent base stations, leading to higher time costs for large-scale coverage. However, SA offers higher speeds and lower latency. NSA networks will coexist with existing SA networks for a long time.

[0024] Most global operators have deployed NSA-based eMBB (Enhanced Mobile Broadband) to strengthen mobile broadband networks, leveraging mature LTE network coverage while utilizing the high throughput of the gNB in ​​EUTRA NR Dual-Connectivity (ENDC). However, this also leads to increased terminal power consumption, as LTE+NR dual-connectivity consumes more power than LTE single-connectivity due to the additional power required by the NR connection, impacting user battery life.

[0025] Currently, most methods for identifying congestion are implemented at the application or framework layer, which are not efficient or accurate enough.

[0026] When users browse short videos on TikTok or WeChat, if the NR network signal is weak, the videos may load slowly or buffer. However, if the terminal cannot recognize that the problem is caused by network congestion, it cannot perform rapid data recovery in this abnormal scenario.

[0027] Once network congestion is detected, appropriate congestion handling can be implemented to improve the user experience when watching short videos. Therefore, the ability to identify congestion scenarios is very important.

[0028] The network congestion handling method, apparatus, electronic device, and storage medium provided in this application will be described in detail below with reference to the accompanying drawings and through specific embodiments and application scenarios.

[0029] Figure 1 This is a flowchart illustrating a network congestion handling method provided in some embodiments of this application. The execution subject of this method can be an electronic device, such as a terminal; Figure 1 As shown, the method includes the following steps:

[0030] Step 100: Determine the cause of network congestion based on uplink transmission parameters;

[0031] Optionally, uplink transmission parameters can be used to characterize the transmission quality of the uplink network, uplink scheduling parameters, or other uplink transmission parameters.

[0032] Alternatively, the cause of network congestion can be the reason for the network congestion.

[0033] Optionally, the values ​​of the uplink transmission parameters can reflect the transmission status of the uplink network and can indicate the cause of network congestion in the event of network congestion.

[0034] Step 110: Based on the cause of network congestion, perform network congestion processing.

[0035] Optionally, the cell accessed by the terminal can be an NR cell;

[0036] Optionally, the cell accessed by the terminal can be an LTE cell;

[0037] Optionally, the cell accessed by the terminal can be a cell of any communication system;

[0038] Optionally, in order to address congestion in a timely manner, network congestion handling can be performed based on the cause of the congestion after the cause has been determined, in order to alleviate network congestion.

[0039] In this embodiment of the application, the cause of network congestion is determined by the uplink transmission parameters, avoiding the low efficiency and accuracy caused by identifying congestion at the application layer or framework layer, thereby improving the efficiency and accuracy of congestion identification. Then, based on the cause of network congestion, network congestion processing is performed to improve the effectiveness and timeliness of congestion processing.

[0040] Optionally, the uplink transmission parameters include at least one of the following: power headroom (PHR), BSR index, number of resource blocks, and index value of modulation and coding scheme.

[0041] Optionally, at the MAC layer, the reporting of the BSR index is used to provide the gNB with information on the uplink data volume of the UE.

[0042] Optionally, the NR MAC layer can select the corresponding table based on the size of the BSR field (3GPP 38.321). Table 1 is an example of a 5-bit buffer size table. The terminal can report the BSR index to the network, so that the network can know the range of buffered data that the terminal is waiting for.

[0043] Table 1: Buffer size levels(in bytes)for 5-bit Buffer Size field

[0044]

[0045] Optionally, resource blocks are allocated to the terminal by the network, and together with the MCS, they determine the number of resource blocks to be transmitted. The more resource blocks (RBs) there are, the more transmittable resources the network allocates, and the higher the speed.

[0046] Optionally, a custom resource block (Custom_Resource Block, Custom_RB) can be defined, which can be called the resource block quantity threshold, to determine whether the number of resource blocks allocated by the network is lower than the resource block quantity threshold Custom_RB;

[0047] Optionally, the number of resource blocks can be the number of resource blocks corresponding to the resources allocated to the terminal by the network side.

[0048] Optionally, Power Headroom Report (PHR) refers to the power headroom reported by the UE to the network side. The PHR value can be sent by the MAC layer control unit. The PHR reporting process provides the serving gNB with information about the difference between the nominal UE maximum transmit power and the power of UL-SCH or SRS transmissions on each active serving cell, as well as information about the differences between nominal values. This includes the UE's maximum power and the estimated power used for UL-SCH and PUCCH transmissions on the SpCell and PUCCH SCell. Primarily, it provides the gNB with adjustable power headroom information for TPC scheduling use in closed-loop power control.

[0049] Optionally, the power margin PHR is calculated from the terminal's maximum transmit power - the expected transmit power of PUSCH. Generally, the worse the signal, the larger the calculated expected transmit power and the smaller the power margin.

[0050] Optionally, a custom power headroom (Custom_Power Headroom, Custom_PHR) can be defined, which can be called the power headroom threshold; it can be determined whether the power headroom is lower than the power headroom threshold Custom_PHR.

[0051] Optionally, an index for a custom modulation and coding scheme (Custom_Modulation and CodingScheme, Custom_MCS) can be defined, which can be called the index threshold of the modulation and coding scheme.

[0052] Optionally, the better the cell signal and the higher the signal-to-noise ratio, the larger the index value (UL MCS) of the uplink modulation and coding scheme is generally; a custom MCS can be defined to determine whether the MCS allocated by the network is lower than the threshold Custom_MCS.

[0053] In this embodiment, the cause of network congestion is determined based on the power headroom (PHR), BSR index, number of resource blocks, and index value of modulation and coding scheme. The impact of various uplink transmission parameters on network quality is comprehensively considered to improve the accuracy of network congestion cause judgment.

[0054] Optionally, before determining the cause of network congestion based on uplink transmission parameters, the method further includes:

[0055] Network congestion is determined based on the uplink scheduled transport block size and the size of the uplink data packets to be sent.

[0056] Optionally, the transport block size for uplink scheduling can be the TB size for uplink scheduling.

[0057] Optionally, the terminal can identify whether uplink congestion is occurring in the NR cell based on the MAC layer BSR report and the uplink scheduling TB size.

[0058] Optionally, the size of the uplink packets to be sent can be indicated by a BSR report.

[0059] Figure 2 These are schematic diagrams of the NR user plane protocol stack provided in some embodiments of this application, such as... Figure 2 As shown, the NR protocol stack is responsible for handling data in the wireless link between the terminal and the network. It is also divided into the control plane and the user plane. Data transmission goes through the user plane. The terminal-side modem communicates with the user plane protocol layer, the transport layer TCP / UDP, and the network layer IP.

[0060] The NR user plane protocol includes the Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Medium Access Control (MAC), and Physical Layer (PHY).

[0061] The MAC layer data has a corresponding buffer for the Data Radio Bearer (DRB). Buffers of different sizes are represented by a BSR index. Different BSR indices correspond to a corresponding BSR value range. The "BS value" is used to represent the size of the uplink packets to be sent in the current buffer. The terminal can report the BSR index to the network to apply for uplink PUSCH resources for uplink transmission, and the network can know how much uplink resources to allocate to the current terminal. Affected by factors such as network coverage and network load, after the terminal applies for a certain size of BS value, the uplink PUSCH resource scheduling (TB size) allocated by the network may be much smaller than the size of the data packets cached by the terminal. At this time, uplink congestion will occur, resulting in uplink data packets staying at the terminal all the time and unable to be sent to the network side, and thus no downlink data packets will arrive. The application layer performance is that loading videos and web pages is stuck or videos cannot be played and web pages cannot be loaded. Therefore, network congestion can be determined based on the size of the uplink packets to be sent in the cache and the transmission block size of the uplink scheduling.

[0062] Optionally, the transmission block of the uplink scheduling is used to transmit the uplink packets to be sent. Therefore, network congestion can be determined when the size of the transmission block of the uplink scheduling is smaller than the size of the uplink packets to be sent in the cache.

[0063] In some embodiments of the present application, it can be checked whether "BS value" > "(PUSCH UL Grant TBsize)*factor (0 < factor < 1)" is satisfied, and if so, network congestion can be determined.

[0064] In some embodiments of the present application, factor = 0.5, BS value = 74, PUSCH UL Grant TBsize = 128. Since "BS value" > "(PUSCH UL Grant TB size)*factor" is satisfied, it can be determined that network congestion has occurred.

[0065] In some embodiments of this application, factor = 0.5, BS value = 10, PUSCH UL Grant TBsize = 128, and if “BS value” < “(PUSCH UL Grant TB size)*factor”, then it can be determined that no network congestion has occurred.

[0066] In some embodiments of this application, factor = 0.5, BS value = 10, PUSCH UL Grant TBsize = 20, and if “BS value” = “(PUSCH UL Grant TB size)*factor”, then it can be determined that no network congestion has occurred.

[0067] In this embodiment of the application, network congestion is determined when the size of the uplink scheduled transport block is smaller than the size of the buffered uplink data packets to be sent. This clarifies the scenarios that cause network congestion and improves the efficiency and accuracy of congestion identification.

[0068] Optionally, determining network congestion based on the uplink scheduled transport block size and the size of the uplink data packets to be sent includes:

[0069] Obtain at least one uplink scheduled transport block size value and at least one uplink data packet size value, wherein the at least one uplink scheduled transport block size value and at least one uplink data packet size value are values ​​obtained after each BSR index report, or values ​​obtained periodically;

[0070] Each time the uplink scheduled transport block size value and the uplink data packet size value are obtained, the uplink scheduled transport block size value and the uplink data packet size value are compared to obtain comparison information.

[0071] Network congestion is determined to have occurred if at least one comparison message indicates that the uplink scheduled transport block size is less than the size of the uplink data packet to be sent.

[0072] Optionally, after each BSR index report, the uplink scheduled transport block size and the uplink data packet size can be obtained, and the uplink scheduled transport block size and the uplink data packet size can be compared. If at least one comparison indicates that the uplink scheduled transport block size is less than the uplink data packet size, network congestion can be determined.

[0073] Optionally, after each reporting of the BSR index, the transmission block size value of the uplink scheduling and the size value of the uplink data packet to be sent can be obtained, and the transmission block size value of the uplink scheduling and the size value of the uplink data packet to be sent can be compared. When the comparison information indicates that the transmission block size value of the uplink scheduling is less than the size value of the uplink data packet to be sent for T1 consecutive times, network congestion can be determined, where T1 is a positive integer greater than or equal to 1.

[0074] Optionally, the transmission block size value of the uplink scheduling and the size value of the uplink data packet to be sent can be obtained periodically. After each obtaining of the transmission block size value of the uplink scheduling and the size value of the uplink data packet to be sent, the transmission block size value of the uplink scheduling and the size value of the uplink data packet to be sent can be compared. When at least one comparison information indicates that the transmission block size value of the uplink scheduling is less than the size value of the uplink data packet to be sent, network congestion can be determined.

[0075] Optionally, the transmission block size value of the uplink scheduling and the size value of the uplink data packet to be sent can be obtained periodically. After each obtaining of the transmission block size value of the uplink scheduling and the size value of the uplink data packet to be sent, the transmission block size value of the uplink scheduling and the size value of the uplink data packet to be sent can be compared. When the comparison information indicates that the transmission block size value of the uplink scheduling is less than the size value of the uplink data packet to be sent for T1 consecutive times, network congestion can be determined, where T1 is a positive integer greater than or equal to 1.

[0076] In some embodiments of the present application, timer T1 can be started when obtaining the transmission block size value of the uplink scheduling and the size value of the uplink data packet to be sent, and it can be determined whether the transmission block size value of the uplink scheduling is less than the size value of the uplink data packet to be sent cached. Only when the size value of the uplink data packet to be sent cached is less than the transmission block size value of the uplink scheduling, the timer is turned off. If the timer times out, network congestion can be determined.

[0077] In some embodiments of the present application, it can be checked whether "BS value" > "(PUSCH UL Grant TB size)*factor (0 < factor < 1)" is satisfied for T1 consecutive times (for example, the preset duration is in seconds, counted once per second, and T1 seconds is equal to T1 times of counting), then network congestion can be determined.

[0078] In some embodiments of the present application, the scenarios where network congestion is likely to occur in practice can include the scenarios where factor < 0.5.

[0079] Optionally, factor can take an optimal value according to actual tests or user experience or communication quality requirements. For example, it can be 0.7, or it can be 0.5, or it can be 0.4.

[0080] In this embodiment of the application, network congestion is determined by repeatedly obtaining the uplink scheduled transport block size value and the uplink data packet size value, thereby further improving the efficiency and accuracy of congestion identification.

[0081] Optionally, the uplink transmission parameters include power headroom (PHR) and BSR index;

[0082] The determination of network congestion causes based on uplink transmission parameters includes:

[0083] If the power margin PHR is greater than or equal to the power margin threshold (Custom_PHR) and the number of resource blocks is less than the resource block number threshold (Custom_RB), the cause of network congestion is determined to be: the size of the transmission resource block allocated by the network side is lower than the preset transmission resource block threshold.

[0084] For example, if the power margin threshold is 50 and the resource block number threshold is 40, if the power margin is 60, it can be determined that the power margin PHR is greater than the power margin threshold. If the resource block number is 35, it can be determined that the resource block number is less than the resource block number threshold. Therefore, the cause of network congestion can be determined as: the size of the transmission resource block allocated by the network side is lower than the preset transmission resource block threshold.

[0085] For example, if the power margin threshold is 40 and the resource block number threshold is 45, if the power margin is 60, it can be determined that the power margin PHR is greater than the power margin threshold. If the resource block number is 35, it can be determined that the resource block number is less than the resource block number threshold. Therefore, the cause of network congestion can be determined as: the size of the transmission resource block allocated by the network side is lower than the preset transmission resource block threshold.

[0086] If the reported BSR index is less than the index threshold and the number of resource blocks is less than the resource block number threshold, the cause of network congestion is determined to be: the size of the transmission resource blocks allocated by the network side is lower than the preset transmission resource block threshold.

[0087] For example, if the index threshold is 20 and the resource block number threshold is 45, and the reported BSR index is 15, it can be determined that the reported BSR index is less than the index threshold. If the resource block number is 40, it can be determined that the resource block number is less than the resource block number threshold. Therefore, the cause of network congestion can be determined as follows: the size of the transmission resource block allocated by the network side is lower than the preset transmission resource block threshold.

[0088] For example, if the index threshold is 15 and the resource block number threshold is 40, and the reported BSR index is 30, then it can be determined that the reported BSR index is greater than or equal to the index threshold. If the resource block number is 35, then it can be determined that the resource block number is less than the resource block number threshold. Therefore, the cause of network congestion can be determined as follows: the size of the transmission resource block allocated by the network side is lower than the preset transmission resource block threshold.

[0089] Optionally, it is possible to determine the cause of network congestion based on whether the most recently reported BSR index has reached the maximum index.

[0090] Optionally, it is possible to determine whether the condition of PHR < Custom_PHR or BSR_index > = Max_index is satisfied. If not, it is possible to determine whether the number of RBs within T1 time is less than the defined Custom_RB (for example, default = 10 RBs). If it is satisfied, it can be indicated that the transmission resources allocated by the network are below the threshold.

[0091] Optionally, the execution of network congestion handling includes:

[0092] Clearing the uplink buffer data;

[0093] Among them, the uplink buffer data includes at least one of the following: PDCP uplink buffer data, RLC uplink buffer data.

[0094] Optionally, when it is determined that the cause of network congestion is that the size of the transmission resource block allocated by the network side is lower than the preset transmission resource block threshold, the PDCP UL buffer can be reset, thereby clearing the PDCP uplink buffer data.

[0095] Optionally, when it is determined that the cause of network congestion is that the size of the transmission resource block allocated by the network side is lower than the preset transmission resource block threshold, the RLC UL buffer can be reset, thereby clearing the RLC uplink buffer data.

[0096] Optionally, after clearing the uplink buffer data, it further includes:

[0097] In the case of network congestion, perform target processing;

[0098] Among them, the target processing includes at least one of the following: increasing the BSR index reported to the network side, reporting the maximum BSR index to the network side.

[0099] Optionally, when it is determined that the transmission resources allocated by the network are below the threshold, the size of the next reported BSR index can be set to the maximum BSR index, or the BSR index reported to the network side can be increased, which may possibly obtain more resource blocks for uplink scheduling by the network.

[0100] Optionally, after performing the target processing, it is possible to re-determine whether the current scenario belongs to a congested scenario. If it is not congested, continuously keep sending the increased BSR index or the maximum BSR index.

[0101] For example, if it is determined that the network-allocated transmission resources are below a threshold, the size of the BSR index reported in the next timer T1 can be set to the maximum BSR index.

[0102] In this embodiment of the application, increasing the BSR index reported to the network side or reporting the largest BSR index to the network side can effectively alleviate network congestion.

[0103] Optionally, the network congestion handling process includes at least one of the following:

[0104] Clear PDCP uplink cache data;

[0105] Clear RLC uplink cache data;

[0106] Increase the BSR index reported to the network side;

[0107] Report the largest BSR index to the network side.

[0108] Optionally, if it is determined that the transmission resources allocated by the network are below the threshold, the PDCP UL buffer can be reset to clear the current PDCP uplink buffer data; the RLC UL buffer can also be reset to clear the current RLC uplink buffer data; the BSR size of the next T1 timer can also be set to the maximum BSR index, which may allow more uplink scheduling from the network to be obtained. In this case, it can be re-evaluated to see if the current situation is congested. If there is no congestion, the maximum BSR index can be continuously sent.

[0109] Optionally, if congestion persists after performing network congestion handling, a cell replacement process can be initiated to replace the access cell with another cell, and the BSR index can be de-set to its maximum value.

[0110] In some embodiments of this application, after uplink congestion in the cell is detected, the buffer is cleared and the maximum BSR is reported to attempt to restore data. If congestion still occurs, the cell replacement process is initiated so that the terminal's data services can be restored quickly.

[0111] In this embodiment, when the transmission resources allocated by the network side are below a threshold, corresponding congestion processing is performed to alleviate the congestion problem caused by the transmission resources allocated by the network side being below the threshold. The congestion processing is targeted, improving the effectiveness and timeliness of congestion processing.

[0112] Optionally, the uplink transmission parameters include power headroom (PHR) and BSR index;

[0113] The determination of network congestion causes based on uplink transmission parameters includes:

[0114] If the power margin (PHR) is less than the power margin threshold and the index value of the modulation and coding scheme is less than the index threshold of the modulation and coding scheme, the cause of network congestion is determined to be: the network-side coverage capability is lower than the coverage capability threshold and the uplink interference value is higher than the interference threshold.

[0115] For example, if the power margin threshold is 50 and the modulation and coding scheme index threshold is MCS-5, and the power margin is 30, then it can be determined that the power margin PHR is less than the power margin threshold. If the modulation and coding scheme index value is MCS-4, then it can be determined that the modulation and coding scheme index value is less than the modulation and coding scheme index threshold. Therefore, the cause of network congestion can be determined as follows: the network coverage capability is lower than the coverage capability threshold and the uplink interference value is higher than the interference threshold.

[0116] For example, if the power margin threshold is 40 and the modulation and coding scheme index threshold is MCS-5, and the power margin is 30, then it can be determined that the power margin PHR is less than the power margin threshold. If the modulation and coding scheme index value is MCS-4, then it can be determined that the modulation and coding scheme index value is less than the modulation and coding scheme index threshold. Therefore, the cause of network congestion can be determined as follows: the network coverage capability is lower than the coverage capability threshold and the uplink interference value is higher than the interference threshold.

[0117] If the reported BSR index is greater than or equal to the index threshold, and the index value of the modulation and coding scheme is less than the index threshold of the modulation and coding scheme, the cause of network congestion is determined to be: the network coverage capability is lower than the coverage capability threshold, and the uplink interference value is higher than the interference threshold.

[0118] For example, if the index threshold is 20 and the index threshold of the modulation and coding scheme is MCS-5, and the reported BSR index is 30, then it can be determined that the reported BSR index is greater than or equal to the index threshold. If the index value of the modulation and coding scheme is MCS-4, then it can be determined that the index value of the modulation and coding scheme is less than the index threshold of the modulation and coding scheme. Therefore, it can be determined that the network-side coverage capability is lower than the coverage capability threshold and the uplink interference value is higher than the interference threshold.

[0119] For example, if the index threshold is 15 and the index threshold of the modulation and coding scheme is MCS-4, and the reported BSR index is 30, then it can be determined that the reported BSR index is greater than or equal to the index threshold. If the index value of the modulation and coding scheme is MCS-3, then it can be determined that the index value of the modulation and coding scheme is less than the index threshold of the modulation and coding scheme. Therefore, it can be determined that the network-side coverage capability is lower than the coverage capability threshold and the uplink interference value is higher than the interference threshold.

[0120] Optionally, if it is determined that PHR < custom_phr or BSR_index = Max_index is satisfied, it can be determined whether the modulation and coding scheme (MCS) of the cell is lower than custom_mcs. If the condition is satisfied, it indicates that the network-side coverage ability is lower than the coverage ability threshold and the uplink interference value is higher than the interference threshold.

[0121] Optionally, the performing network congestion handling includes:

[0122] Switching the accessed cell to the target cell;

[0123] Performing the network congestion handling when the terminal experiences network congestion in the target cell.

[0124] Optionally, when it is determined that the cause of network congestion is that the network-side coverage ability is lower than the coverage ability threshold and the uplink interference value is higher than the interference threshold, cell switching can be performed to switch to a cell with better communication services.

[0125] For example, it can be determined that all current NR cells are congested. To avoid affecting the user data experience, the congestion status can be reported to the NAS layer for decision-making; the NAS layer can perform optimization actions according to the cell replacement algorithm, so that the user switches to other cells with better experience.

[0126] In some embodiments of the present application, when the terminal resides in a cell with poor signal coverage or in a NR cell with high network load, the untimely transmission of uplink packets will cause more TCP packet retransmissions, thus affecting the smooth playback experience of the application. It can be determined whether the current cell is congested through the MAC layer BSR report and PUSCH uplink scheduling, and after identifying the uplink congestion of the cell, trigger clearing the buffer Buffer and reporting the maximum buffer status report BSR to attempt to restore data. If it is still congested, enter the cell replacement process, thereby improving the user data experience in a specific network scenario.

[0127] In the embodiments of the present application, when the terminal resides in a cell with poor signal coverage or in a LTE / ENDC cell with high network load, the untimely transmission of uplink packets will cause more TCP packet retransmissions, thus affecting the smooth playback experience of the application. The embodiments of the present application are also applicable to the LTE network. When the LTE cell is congested, the same method can be adopted to replace the resident cell to achieve fast data recovery, thereby improving the user data experience in a specific network scenario.

[0128] In this embodiment of the application, when the power headroom (PHR) is greater than or equal to the power headroom threshold or the reported BSR index is greater than or equal to the index threshold, and the number of resource blocks is less than the resource block number threshold, the cause of network congestion is determined to be: the size of the transmission resource blocks allocated by the network side is lower than the preset transmission resource block threshold; when the power headroom (PHR) is greater than or equal to the power headroom threshold or the reported BSR index is less than the index threshold, and the number of resource blocks is less than the resource block number threshold, the cause of network congestion is determined to be: the size of the transmission resource blocks allocated by the network side is lower than the preset transmission resource block threshold; judgment conditions that fit the actual situation of the communication network are set for each cause of network congestion, thereby improving the accuracy of network congestion cause judgment.

[0129] Figure 3 This is a flowchart illustrating some embodiments of the network congestion handling method provided in this application, such as... Figure 3 As shown, the process includes:

[0130] Step 301. Start the network congestion handling procedure;

[0131] Step 302. Terminal registers with NR cell A;

[0132] Step 303. The terminal establishes an LTE data bearer;

[0133] Optionally, if the terminal successfully establishes an LTE data bearer, the NR data PDU session is established, and the terminal can send and receive data.

[0134] Step 304. Determine if there are any uplink data packets to be sent;

[0135] The terminal checks if there are any data packets sent from the upper layer application in the PDCP layer. If the PDCP buffer size is not 0 for N seconds, it means that there are uplink data packets waiting to be sent; otherwise, the network congestion handling process ends.

[0136] Step 305. Obtain the transport block size value of at least one uplink scheduling and the size value of at least one uplink data packet to be sent;

[0137] The terminal determines the current BS value based on the BS index of the NR cell MAC layer. It can know the current network scheduling based on the TB size of the ULGrant in the PUSCH of the network scheduling. The terminal counts the size of the uplink data packets to be sent at least once, such as the BS value per second of the NR cell and the uplink scheduled transport block size, such as PUSCH UL Grant TBsize.

[0138] Step 306. Compare the uplink scheduled transport block size with the uplink data packet size;

[0139] The terminal can compare the transport block size value of the uplink scheduling with the size value of the uplink data packet to be sent, and obtain comparison information; and start timer T1. This timer serves as a time offset to more accurately determine that the conditions for cell congestion can be met multiple times instead of just once.

[0140] Step 307. Determine whether the comparison information indicates that the transport block size value of the uplink scheduling is less than the size value of the uplink data packet to be sent.

[0141] Optionally, it can be checked whether timer T1 has expired. After the timer expires, proceed to 308; otherwise, continue with 305.

[0142] Optionally, when the comparison information indicates that the transport block size value of the uplink scheduling is less than the size value of the uplink data packet to be sent, proceed to 308.

[0143] Step 308. Determine that network congestion has occurred.

[0144] Optionally, network congestion can be determined when at least one piece of comparison information indicates that the transport block size value of the uplink scheduling is less than the size value of the uplink data packet to be sent.

[0145] Optionally, it can be checked whether "BSvalue" > "(PUSCH UL Grant TB size)*factor (0 < factor < 1)" is satisfied continuously for T1 times (counted once per second, and T1 seconds equal T1 counts). If so, proceed to 309; if the condition is not met, continue with 305.

[0146] Step 309. Determine whether the power headroom PHR is greater than or equal to the power headroom threshold, or determine whether the reported BSR index is less than the index threshold.

[0147] Determine whether the condition PHR < custom_phr or BSR_index >= Max_index is satisfied; if not, proceed to 310; if so, proceed to 315.

[0148] Step 310. Determine whether the number of resource blocks is less than the resource block number threshold.

[0149] Determine whether the number of RBs within T1 time is less than the defined custom_RB (default = 10 RBs). If this condition is met, it indicates that the cause of network congestion is that the size of the transport resource block allocated by the network side is lower than the preset transport resource block threshold, and then proceed to 311; otherwise, end the process.

[0150] Step 311. Clear the PDCP uplink cached data.

[0151] Optionally, the PDCP UL buffer can be reset to clear the current PDCP uplink buffer data;

[0152] Step 312. Clear RLC uplink cache data;

[0153] Optionally, the RLC UL buffer can be reset to clear the current RLC uplink buffer data;

[0154] Step 313. Increase the BSR index reported to the network side, or report the largest BSR index to the network side;

[0155] Optionally, the BSR size of the next T1 timer can be set to the maximum BSR index, which may allow more uplink scheduling from the network to be obtained. At this point, the system enters step 305 to determine whether the current situation is congested. If there is no congestion, the maximum BSR index will continue to be sent. If there is still congestion, the subsequent cell replacement process will be initiated. If the cell is replaced with another cell, the BSR index will no longer be set to the maximum value.

[0156] Step 314. Determine whether the power margin PHR is less than the power margin threshold, or whether the reported BSR index is greater than or equal to the index threshold.

[0157] Optionally, if after executing 310 to 313, the power margin PHR is less than the power margin threshold, or after executing 310 to 313, the power margin PHR is less than the power margin threshold, or the reported BSR index is greater than or equal to the index threshold, or the reported BSR index is greater than or equal to the index threshold, then proceed to 315.

[0158] Step 315. Determine whether the index value of the modulation and coding scheme is less than the index threshold of the modulation and coding scheme;

[0159] Optionally, if the modulation and coding scheme index value MCS is lower than the modulation and coding scheme index threshold Custom_MCS, the network congestion cause is determined to be: the network coverage capability is lower than the coverage capability threshold, and the uplink interference value is higher than the interference threshold; otherwise, the congestion process ends.

[0160] Step 316. Determine uplink congestion in NR cell A;

[0161] If the condition is met in step 315, then it is determined that there is uplink congestion in NR cell A.

[0162] Step 317. Report the congestion status;

[0163] Optionally, if all NR cells are currently congested, in order to avoid affecting the user's data experience, the congestion status is reported to the NAS layer for decision-making.

[0164] Step 318. Switch the access cell to the target cell;

[0165] Optionally, the NAS layer can perform optimization actions based on the cell replacement algorithm, thereby enabling users to switch to other cells with a better experience;

[0166] The network congestion handling process described above will be executed again after the switchover until network congestion no longer occurs.

[0167] In this embodiment, when a terminal camps in a cell with poor signal coverage or in an LTE or NR cell with heavy network load, untimely uplink packet transmission can lead to numerous TCP data packet retransmissions, affecting the smooth playback experience of the application. In this case, MAC layer BSR reports and uplink scheduling can be used to determine if the current cell is congested. If congestion conditions are met, a cell switching process is initiated to change the camped cell, achieving rapid data recovery and improving the user's data experience in specific network scenarios.

[0168] In this embodiment of the application, the cause of network congestion is determined by the uplink transmission parameters, avoiding the low efficiency and accuracy caused by identifying congestion at the application layer or framework layer, thereby improving the efficiency and accuracy of congestion identification. Then, based on the cause of network congestion, network congestion processing is performed to improve the effectiveness and timeliness of congestion processing.

[0169] The network congestion handling method provided in this application can be executed by a network congestion handling device. This application uses the execution of the network congestion handling method by a network congestion handling device as an example to illustrate the network congestion handling device provided in this application.

[0170] Figure 4 These are schematic diagrams of the network congestion processing apparatus provided in some embodiments of this application, such as... Figure 4 As shown, the device 400 includes: a congestion cause determination module 410 and a congestion processing execution module 420; wherein:

[0171] The congestion cause determination module 410 is used to determine the cause of network congestion based on uplink transmission parameters;

[0172] The congestion handling execution module 420 is used to perform network congestion handling based on the network congestion cause.

[0173] In this embodiment, the cause of network congestion is determined by uplink transmission parameters, avoiding the low efficiency and accuracy of congestion identification at the application layer or framework layer, thus improving the efficiency and accuracy of congestion identification. Based on the cause of network congestion, network congestion processing is then performed, improving the effectiveness and timeliness of congestion handling. Optionally, the uplink transmission parameters include at least one of the following: Power Headroom (PHR), BSR index, number of resource blocks, and index value of the modulation and coding scheme.

[0174] Optionally, the device further includes:

[0175] The network congestion determination module is used to determine whether network congestion has occurred based on the uplink scheduled transport block size and the size of the uplink data packets to be sent.

[0176] Optionally, the network congestion determination module is specifically used for:

[0177] Obtain at least one uplink scheduled transport block size value and at least one uplink data packet size value, wherein the at least one uplink scheduled transport block size value and at least one uplink data packet size value are values ​​obtained after each BSR index report, or values ​​obtained periodically;

[0178] Each time the uplink scheduled transport block size value and the uplink data packet size value are obtained, the uplink scheduled transport block size value and the uplink data packet size value are compared to obtain comparison information.

[0179] Network congestion is determined to have occurred if at least one comparison message indicates that the uplink scheduled transport block size is less than the size of the uplink data packet to be sent.

[0180] Optionally, the uplink transmission parameters include power headroom (PHR) and BSR index;

[0181] The network congestion cause determination module is specifically used for:

[0182] If the power margin PHR is greater than or equal to the power margin threshold and the number of resource blocks is less than the resource block number threshold, the cause of network congestion is determined to be: the size of the transmission resource block allocated by the network side is lower than the preset transmission resource block threshold.

[0183] If the reported BSR index is less than the index threshold and the number of resource blocks is less than the resource block number threshold, the cause of network congestion is determined to be: the size of the transmission resource blocks allocated by the network side is lower than the preset transmission resource block threshold.

[0184] Optionally, the congestion handling execution module is specifically used for:

[0185] Clear upstream cache data;

[0186] The uplink cache data includes at least one of the following: PDCP uplink cache data and RLC uplink cache data.

[0187] Optionally, the congestion handling execution module is further configured to:

[0188] In the event of network congestion, perform target processing;

[0189] The target processing includes at least one of the following: increasing the BSR index reported to the network side, and reporting the largest BSR index to the network side.

[0190] Optionally, the congestion handling execution module is specifically used for at least one of the following:

[0191] Clear PDCP uplink cache data;

[0192] Clear RLC uplink cache data;

[0193] Increase the BSR index reported to the network side;

[0194] Report the largest BSR index to the network side.

[0195] Optionally, the uplink transmission parameters include Power Headroom (PHR) and BSR index; the network congestion cause determination module is specifically used for at least one of the following:

[0196] If the power margin (PHR) is less than the power margin threshold and the index value of the modulation and coding scheme is less than the index threshold of the modulation and coding scheme, the cause of network congestion is determined to be: the network-side coverage capability is lower than the coverage capability threshold and the uplink interference value is higher than the interference threshold.

[0197] If the reported BSR index is greater than or equal to the index threshold, and the index value of the modulation and coding scheme is less than the index threshold of the modulation and coding scheme, the cause of network congestion is determined to be: the network coverage capability is lower than the coverage capability threshold, and the uplink interference value is higher than the interference threshold.

[0198] Optionally, the congestion handling execution module is specifically used for:

[0199] Switch the access cell to the target cell;

[0200] If network congestion occurs in the target cell, the terminal performs the network congestion handling.

[0201] In this embodiment, the cause of network congestion is determined by uplink transmission parameters, avoiding the low efficiency and accuracy caused by congestion identification at the application layer or framework layer, thus improving the efficiency and accuracy of congestion identification. Based on the cause of network congestion, network congestion processing is then performed, improving the effectiveness and timeliness of congestion processing. The network congestion processing device in this embodiment can be an electronic device or a component within an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or other devices besides a terminal. For example, the electronic device can be a mobile phone, tablet computer, laptop computer, PDA, in-vehicle electronic device, mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc. It can also be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This embodiment does not specifically limit the specific type of device.

[0202] The network congestion processing device in this application embodiment can be a device with an operating system. The operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit the specific operating system used.

[0203] The network congestion handling device provided in this application embodiment can achieve... Figures 1 to 3 The various processes implemented in the method implementation examples will not be described again here to avoid repetition.

[0204] Optionally, Figure 5 These are schematic diagrams of the structure of electronic devices provided in some embodiments of this application, such as... Figure 5 As shown, this application embodiment also provides an electronic device 500, including a processor 501 and a memory 502. The memory 502 stores a program or instructions that can run on the processor 501. When the program or instructions are executed by the processor 501, they implement the various steps of the above-described network congestion processing method embodiment and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0205] It should be noted that the electronic devices in the embodiments of this application include the mobile electronic devices and non-mobile electronic devices described above.

[0206] Figure 6 A schematic diagram of the hardware structure of an electronic device for implementing some embodiments of this application.

[0207] The electronic device 600 includes, but is not limited to, components such as: radio frequency unit 601, network module 602, audio output unit 603, input unit 604, sensor 605, display unit 606, user input unit 607, interface unit 608, memory 609, and processor 610.

[0208] Those skilled in the art will understand that the electronic device 600 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 610 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 6 The electronic device structure shown does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0209] The processor 610 is used to determine the cause of network congestion based on uplink transmission parameters;

[0210] The processor 610 is used to perform network congestion processing based on the network congestion cause.

[0211] In this embodiment, the cause of network congestion is determined by uplink transmission parameters, avoiding the low efficiency and accuracy of congestion identification at the application layer or framework layer, thus improving the efficiency and accuracy of congestion identification. Based on the cause of network congestion, network congestion processing is then performed, improving the effectiveness and timeliness of congestion handling. Optionally, the uplink transmission parameters include at least one of the following: Power Headroom (PHR), BSR index, number of resource blocks, and index value of the modulation and coding scheme.

[0212] Optionally, the processor 610 is also used for:

[0213] Network congestion is determined based on the uplink scheduled transport block size and the size of the uplink data packets to be sent.

[0214] Optionally, the processor 610 is also used for:

[0215] Obtain at least one uplink scheduled transport block size value and at least one uplink data packet size value, wherein the at least one uplink scheduled transport block size value and at least one uplink data packet size value are values ​​obtained after each BSR index report, or values ​​obtained periodically;

[0216] Each time the uplink scheduled transport block size value and the uplink data packet size value are obtained, the uplink scheduled transport block size value and the uplink data packet size value are compared to obtain comparison information.

[0217] Network congestion is determined to have occurred if at least one comparison message indicates that the uplink scheduled transport block size is less than the size of the uplink data packet to be sent.

[0218] Optionally, the uplink transmission parameters include power headroom (PHR) and BSR index;

[0219] Processor 610 is also used for:

[0220] If the power margin PHR is greater than or equal to the power margin threshold and the number of resource blocks is less than the resource block number threshold, the cause of network congestion is determined to be: the size of the transmission resource block allocated by the network side is lower than the preset transmission resource block threshold.

[0221] If the reported BSR index is less than the index threshold and the number of resource blocks is less than the resource block number threshold, the cause of network congestion is determined to be: the size of the transmission resource blocks allocated by the network side is lower than the preset transmission resource block threshold.

[0222] Optionally, the processor 610 is also used for:

[0223] Clear upstream cache data;

[0224] The uplink cache data includes at least one of the following: PDCP uplink cache data and RLC uplink cache data.

[0225] Optionally, the processor 610 is also used for:

[0226] In the event of network congestion, perform target processing;

[0227] The target processing includes at least one of the following: increasing the BSR index reported to the network side, and reporting the largest BSR index to the network side.

[0228] Optionally, the processor 610 is also used for at least one of the following:

[0229] Clear PDCP uplink cache data;

[0230] Clear RLC uplink cache data;

[0231] Increase the BSR index reported to the network side;

[0232] Report the largest BSR index to the network side.

[0233] Optionally, the uplink transmission parameters include power headroom (PHR) and BSR index;

[0234] Processor 610 is also used in at least one of the following:

[0235] If the power margin (PHR) is less than the power margin threshold and the index value of the modulation and coding scheme is less than the index threshold of the modulation and coding scheme, the cause of network congestion is determined to be: the network-side coverage capability is lower than the coverage capability threshold and the uplink interference value is higher than the interference threshold.

[0236] If the reported BSR index is greater than or equal to the index threshold, and the index value of the modulation and coding scheme is less than the index threshold of the modulation and coding scheme, the cause of network congestion is determined to be: the network coverage capability is lower than the coverage capability threshold, and the uplink interference value is higher than the interference threshold.

[0237] Optionally, the processor 610 is used for:

[0238] Switch the access cell to the target cell;

[0239] If network congestion occurs in the target cell, the terminal performs the network congestion handling.

[0240] In this embodiment, the cause of network congestion is determined by uplink transmission parameters, avoiding the low efficiency and accuracy caused by congestion identification at the application layer or framework layer, thus improving the efficiency and accuracy of congestion identification. Based on the cause of network congestion, network congestion processing is then performed, improving the effectiveness and timeliness of congestion processing. It should be understood that in this embodiment, the input unit 604 may include a graphics processing unit (GPU) 6041 and a microphone 6042. The GPU 6041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 606 may include a display panel 6061, which may be configured using a liquid crystal display, organic light-emitting diode, or other similar methods. The user input unit 607 includes a touch panel 6071 and at least one of other input devices 6072. The touch panel 6071 is also called a touchscreen. The touch panel 6071 may include a touch detection device and a touch controller. Other input devices 6072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, joysticks, etc., which will not be described in detail here.

[0241] The memory 609 can be used to store software programs and various data. The memory 609 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 609 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 609 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0242] Processor 610 may include one or more processing units; optionally, processor 610 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 610.

[0243] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described network congestion handling method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0244] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0245] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described network congestion handling method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0246] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0247] This application provides a computer program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the network congestion handling method embodiments described above, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0248] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0249] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0250] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for handling network congestion, characterized in that, include: Determine the cause of network congestion based on uplink transmission parameters; Based on the aforementioned reasons for network congestion, perform network congestion handling; Prior to determining the cause of network congestion based on uplink transmission parameters, the method further includes: Network congestion is determined based on the uplink scheduled transport block size and the size of the uplink data packets to be sent; The uplink transmission parameters include Power Headroom (PHR) and BSR index; determining the cause of network congestion based on the uplink transmission parameters includes: If the power margin PHR is greater than or equal to the power margin threshold and the number of resource blocks is less than the resource block number threshold, the cause of network congestion is determined to be: the size of the transmission resource block allocated by the network side is lower than the preset transmission resource block threshold. If the reported BSR index is less than the index threshold and the number of resource blocks is less than the resource block number threshold, the cause of network congestion is determined to be: the size of the transmission resource blocks allocated by the network side is lower than the preset transmission resource block threshold.

2. The network congestion handling method according to claim 1, characterized in that, The uplink transmission parameters include: power headroom (PHR), BSR index, number of resource blocks, and index value of modulation and coding scheme.

3. The network congestion handling method according to claim 1, characterized in that, The determination of network congestion based on the uplink scheduling transport block size and the size of the uplink data packets to be sent includes: Obtain at least one uplink scheduled transport block size value and at least one uplink data packet size value, wherein the at least one uplink scheduled transport block size value and at least one uplink data packet size value are values ​​obtained after each BSR index report, or values ​​obtained periodically; Each time the uplink scheduled transport block size value and the uplink data packet size value are obtained, the uplink scheduled transport block size value and the uplink data packet size value are compared to obtain comparison information. Network congestion is determined to have occurred if at least one comparison message indicates that the uplink scheduled transport block size is less than the size of the uplink data packet to be sent.

4. The network congestion handling method according to claim 1, characterized in that, The network congestion handling process includes: Clear upstream cache data; The uplink cache data includes at least one of the following: PDCP uplink cache data and RLC uplink cache data.

5. The network congestion handling method according to claim 4, characterized in that, After clearing the upstream cache data, the following is also included: In the event of network congestion, perform target processing; The target processing includes at least one of the following: increasing the BSR index reported to the network side, and reporting the largest BSR index to the network side.

6. The network congestion handling method according to claim 1, characterized in that, The network congestion handling process includes at least one of the following: Clear PDCP uplink cache data; Clear RLC uplink cache data; Increase the BSR index reported to the network side; Report the largest BSR index to the network side.

7. The network congestion handling method according to claim 1, characterized in that, The uplink transmission parameters include Power Headroom (PHR) and BSR index; The determination of network congestion causes based on uplink transmission parameters includes: If the power margin (PHR) is less than the power margin threshold and the index value of the modulation and coding scheme is less than the index threshold of the modulation and coding scheme, the cause of network congestion is determined to be: the network-side coverage capability is lower than the coverage capability threshold and the uplink interference value is higher than the interference threshold. If the reported BSR index is greater than or equal to the index threshold, and the index value of the modulation and coding scheme is less than the index threshold of the modulation and coding scheme, the cause of network congestion is determined to be: the network coverage capability is lower than the coverage capability threshold, and the uplink interference value is higher than the interference threshold.

8. The network congestion handling method according to claim 7, characterized in that, The network congestion handling process includes: Switch the access cell to the target cell; The network congestion handling is performed when the terminal experiences network congestion in the target cell.

9. A network congestion handling device, characterized in that, include: The congestion cause determination module is used to determine the cause of network congestion based on uplink transmission parameters; A congestion handling execution module is used to perform network congestion handling based on the reasons for network congestion. The device further includes: The network congestion determination module is used to determine the occurrence of network congestion based on the uplink scheduled transport block size and the size of the uplink data packets to be sent. The uplink transmission parameters include Power Headroom (PHR) and BSR index; The network congestion cause determination module is specifically used for: If the power margin PHR is greater than or equal to the power margin threshold and the number of resource blocks is less than the resource block number threshold, the cause of network congestion is determined to be: the size of the transmission resource block allocated by the network side is lower than the preset transmission resource block threshold. If the reported BSR index is less than the index threshold and the number of resource blocks is less than the resource block number threshold, the cause of network congestion is determined to be: the size of the transmission resource blocks allocated by the network side is lower than the preset transmission resource block threshold.

10. The network congestion processing apparatus according to claim 9, characterized in that, The uplink transmission parameters include: power headroom (PHR), BSR index, number of resource blocks, and index value of modulation and coding scheme.

11. The network congestion processing apparatus according to claim 9, characterized in that, The network congestion determination module is specifically used for: Obtain at least one uplink scheduled transport block size value and at least one uplink data packet size value, wherein the at least one uplink scheduled transport block size value and at least one uplink data packet size value are values ​​obtained after each BSR index report, or values ​​obtained periodically; Each time the uplink scheduled transport block size value and the uplink data packet size value are obtained, the uplink scheduled transport block size value and the uplink data packet size value are compared to obtain comparison information. Network congestion is determined to have occurred if at least one comparison message indicates that the uplink scheduled transport block size is less than the size of the uplink data packet to be sent.

12. The network congestion processing apparatus according to claim 9, characterized in that, The congestion handling execution module is specifically used for: Clear upstream cache data; The uplink cache data includes at least one of the following: PDCP uplink cache data and RLC uplink cache data.

13. The network congestion handling apparatus according to claim 12, characterized in that, The congestion handling execution module is further configured to: In the event of network congestion, perform target processing; The target processing includes at least one of the following: increasing the BSR index reported to the network side, and reporting the largest BSR index to the network side.

14. The network congestion handling apparatus according to claim 9, characterized in that, The congestion handling execution module is specifically used for at least one of the following: Clear PDCP uplink cache data; Clear RLC uplink cache data; Increase the BSR index reported to the network side; Report the largest BSR index to the network side.

15. The network congestion handling apparatus according to claim 9, characterized in that, The uplink transmission parameters include Power Headroom (PHR) and BSR index; the network congestion cause determination module is specifically used for at least one of the following: If the power margin (PHR) is less than the power margin threshold and the index value of the modulation and coding scheme is less than the index threshold of the modulation and coding scheme, the cause of network congestion is determined to be: the network-side coverage capability is lower than the coverage capability threshold and the uplink interference value is higher than the interference threshold. If the reported BSR index is greater than or equal to the index threshold, and the index value of the modulation and coding scheme is less than the index threshold of the modulation and coding scheme, the cause of network congestion is determined to be: the network coverage capability is lower than the coverage capability threshold, and the uplink interference value is higher than the interference threshold.

16. The network congestion handling apparatus according to claim 15, characterized in that, The congestion handling execution module is specifically used for: Switch the access cell to the target cell; The network congestion handling is performed when the terminal experiences network congestion in the target cell.

17. An electronic device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the network congestion handling method as described in any one of claims 1-8.

18. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the network congestion handling method as described in any one of claims 1-8.

Images