Network congestion mitigation

By detecting and responding to network congestion in the base station of the wireless cellular network, performing appropriate processes such as packet priority and quality of service management, the problem of network congestion in the wireless cellular network is solved, and communication with low latency and high throughput is achieved .

CN119096587APending Publication Date: 2024-12-06CTRL-LABS CORP
View PDF 0 Cites 2 Cited by

Patent Information

Application Number
CN202380036404.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-27
Filing Date
2023-04-26
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

The prior art is difficult to effectively reduce network congestion in wireless cellular networks, especially in low-latency communication environments, and lacks effective mechanisms to alleviate network congestion in RANs.

Method used

The base station of a wireless cellular network performs corresponding processes to reduce congestion by detecting the level and type of network congestion, including determining packet priority, discarding packets, releasing wireless bearers, transmitting explicit congestion notifications, setting up updated service quality and starting active queues Management process.

Benefits of technology

By adaptively selecting and performing different processes, network congestion can be effectively reduced or alleviated, ensuring low-latency and high-throughput communication, and reducing the interference of network congestion to applications such as augmented reality or virtual reality.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096587A_ABST
    Figure CN119096587A_ABST
Patent Text Reader

Abstract

The disclosure herein relates to reducing network congestion for wireless communications. In one aspect, a base station of a wireless cellular network determines a level of network congestion from a plurality of candidate levels of network congestion. In one aspect, a base station determines whether the type of network congestion includes uplink congestion or downlink congestion. In one aspect, the base station determines one or more processes for reducing network congestion according to the determined level of network congestion and the determined type of network.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications, including but not limited to reducing network congestion for wireless communications. Background Art

[0002] Cellular communication technology (e.g., 3rd generation mobile communication technology (3G), 4th generation mobile communication technology (4G), 5th generation mobile communication technology (5G)) allows high data rate communication. In one example, a user equipment (UE) or an application server (AS) can generate data and transmit the data to a base station. The base station can provide or forward data from the UE or from the AS to another UE. Alternatively or additionally, the base station can provide or forward data from another base station to another UE. The network between one or more UEs and the base station can be referred to as a radio access network (RAN). Therefore, a UE or AS located in one geographic area can communicate with another UE located in another geographic area through one or more RANs.

[0003] Typically, communications may be affected by network congestion. For example, multiple UEs or ASs may attempt to transmit data at the same time. However, there is no suitable mechanism to alleviate or reduce network congestion for low-latency communications, especially when the network congestion occurs within the RAN. Summary of the invention

[0004] Various embodiments disclosed herein relate to a base station of a wireless cellular network. In some embodiments, the base station includes at least one processor configured to determine the level of network congestion from a plurality of candidate levels of network congestion. In some embodiments, the at least one processor is configured to determine whether the type of network congestion includes uplink congestion or downlink congestion. In some embodiments, the at least one processor is configured to determine one or more processes for reducing network congestion based on the determined level of network congestion and the determined type of network congestion. In some embodiments, the at least one processor is configured to execute the determined one or more processes.

[0005] In some embodiments, the type of network congestion includes downlink congestion. In some embodiments, the one or more processes include one or more first processes performed in response to determining that the level of downlink congestion is a first level of downlink congestion that is above a threshold. In some embodiments, the one or more processes include one or more second processes performed in response to determining that the level of downlink congestion is a second level of downlink congestion that is below a threshold. In some embodiments, the one or more first processes include at least one of the following: determining a priority of a group of packages; discarding one or more packets in the group of packages according to the determined priority; or releasing one or more radio bearers. In some embodiments, the one or more second processes include at least one of the following: causing the wireless interface to transmit an explicit congestion notification (ECN) to the core network; determining a recommended downlink bit rate; causing the wireless interface to transmit a recommended downlink bit rate to the core network; setting a downlink bearer with an updated quality of service; or starting an active queue management process for downlink traffic. In some embodiments, the one or more first processes include one or more second processes (and may include one or more other processes). In some embodiments, the at least one processor is configured to, in response to the type of network congestion being downlink congestion, cause the wireless interface to transmit a medium access control control element (MAC CE) notification to a user equipment (UE). In some embodiments, the UE is configured to reduce a duty cycle for monitoring the downlink in response to the MAC CE notification.

[0006] In some embodiments, the type of network congestion includes uplink congestion. In some embodiments, the one or more processes include: one or more first processes performed in response to determining that the level of uplink congestion is a first level of uplink congestion above a threshold, and one or more second processes performed in response to determining that the level of uplink congestion is a second level of uplink congestion below a threshold. In some embodiments, the one or more first processes include at least one of the following: performing congestion control by allowing part of the uplink traffic according to the quality of service; or releasing one or more radio bearers. In some embodiments, the one or more second processes include at least one of the following: determining a recommended uplink bit rate; causing the wireless interface to transmit a media access control control element (MAC CE) notification indicating the recommended uplink bit rate to a user equipment (UE); setting a new uplink bearer with an updated quality of service; or starting an active queue management process for uplink traffic. In some embodiments, the one or more first processes include one or more second processes. In some embodiments, the type of network congestion includes both uplink congestion and downlink congestion.

[0007] Various embodiments disclosed herein relate to a communication method. In some embodiments, the method includes determining, by a base station of a wireless cellular network, a level of network congestion from a plurality of candidate levels of network congestion. In some embodiments, the method includes determining, by the base station, whether the type of network congestion includes uplink congestion or downlink congestion. In some embodiments, the method includes determining, by the base station, one or more processes for reducing network congestion based on the determined level of network congestion and the determined type of network congestion. In some embodiments, the method includes executing, by the base station, the determined one or more processes.

[0008] In some embodiments, the type of network congestion includes downlink congestion. In some embodiments, the one or more processes include one or more first processes performed in response to determining that the level of downlink congestion is a first level of downlink congestion that is higher than a threshold. In some embodiments, the one or more processes include one or more second processes performed in response to determining that the level of downlink congestion is a second level of downlink congestion that is lower than a threshold. In some embodiments, the one or more first processes include at least one of the following: determining a priority of a group of packets by a base station; discarding one or more packets in the group of packets according to the determined priority by the base station; or releasing one or more radio bearers by the base station. In some embodiments, the one or more second processes include at least one of the following: transmitting an explicit congestion notification (ECN) by a base station to a core network; determining a recommended downlink bit rate by a base station; transmitting a recommended downlink bit rate by a base station to a core network; setting a new downlink bearer with an updated quality of service by a base station; or initiating an active queue management process for downlink traffic by a base station. In some embodiments, the one or more first processes include one or more second processes. In some embodiments, the method includes transmitting a media access control control element (MAC CE) notification to a user equipment (UE) by a base station in response to the type of network congestion including downlink congestion. In some embodiments, the UE is configured to reduce the duty cycle of monitoring the downlink in response to the MAC CE notification.

[0009] In some embodiments, the type of network congestion includes uplink congestion, and the one or more processes include: one or more first processes performed in response to determining that the level of uplink congestion is a first level of uplink congestion above a threshold, and one or more second processes performed in response to determining that the level of uplink congestion is a second level of uplink congestion below a threshold. In some embodiments, the one or more first processes include at least one of the following: performing congestion control by allowing part of the uplink traffic according to the quality of service; or releasing one or more radio bearers. In some embodiments, the one or more second processes include at least one of the following: determining a recommended uplink bit rate; transmitting a media access control control element (MAC CE) notification indicating the recommended uplink bit rate to a user equipment (UE) by a base station; setting a new uplink bearer with an updated quality of service; or starting an active queue management process for the uplink traffic. In some embodiments, the one or more first processes include one or more second processes.

[0010] It will be appreciated that any feature described herein as being suitable for incorporation into one or more aspects or embodiments of the present disclosure is intended to be universal in any and all aspects and embodiments of the present disclosure. Other aspects of the present disclosure may be understood by those skilled in the art from the specification, claims and drawings of the present disclosure. The above general description and the following detailed description are exemplary and illustrative only, and are not limitations of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings are not intended to be drawn to scale. Like reference numbers and names in the various drawings refer to like elements. For clarity, not every component may be labeled in every drawing.

[0012] Figure 1 is a schematic diagram of an example wireless communication system according to an example implementation of the present disclosure.

[0013] Figure 2 is a schematic diagram illustrating example components of a base station and a user equipment according to an example embodiment of the present disclosure.

[0014] Figure 3 is a schematic diagram of a network congestion controller according to an example implementation of the present disclosure.

[0015] Figure 4 is an example IP layer data frame including a field for congestion control according to an example implementation of the present disclosure.

[0016] Figure 5 is an example of a medium access control element for congestion control according to an example implementation of the present disclosure.

[0017] Figure 6 is a flow chart illustrating a process of reducing or alleviating network congestion according to an example implementation of the present disclosure.

[0018] Figure 7 is a flow chart illustrating a process of reducing downlink congestion according to an example implementation of the present disclosure.

[0019] Figure 8 is a flow chart illustrating a process of reducing uplink congestion according to an example embodiment of the present disclosure. DETAILED DESCRIPTION

[0020] Before turning to the drawings showing some embodiments in detail, it should be understood that the present disclosure is not limited to the details or methods set forth in the specification or shown in the drawings. It should also be understood that the terminology used herein is for descriptive purposes only and should not be considered as limiting.

[0021] The disclosure herein relates to reducing or alleviating network congestion of cellular communications (e.g., 3G, 4G, 5G). In one aspect, a base station of a wireless cellular network determines a level of network congestion from a plurality of candidate levels of network congestion. In one aspect, the base station determines whether the type of network congestion includes uplink congestion or downlink congestion. In one aspect, the base station determines one or more processes to reduce network congestion based on the determined level of network congestion and the determined type of network congestion. In one aspect, the base station performs the determined one or more processes. Advantageously, by selecting or executing different processes based on the level of network congestion and the type of network congestion, network congestion can be adaptively reduced or alleviated by various granular methods.

[0022] For example, if the level of downlink congestion is below a first threshold (e.g., moderate downlink congestion or mild downlink congestion), the base station may: i) transmit an explicit congestion notification (ECN) to the core network; ii) determine a recommended downlink bit rate and transmit the recommended downlink bit rate to the core network; iii) set a new downlink bearer / flow with an updated quality of service (QoS); iv) start an active queue management (AQM) process for downlink (DL) traffic; or v) perform any combination thereof. For example, if the level of downlink congestion is above a first threshold (e.g., severe downlink congestion), the base station may: i) discard one or more packets based on quality of service priority; ii) release one or more radio bearers; or iii) perform a combination thereof. In addition, if the level of downlink congestion is above a first threshold (e.g., severe downlink congestion), the base station may perform one or more processes performed for moderate downlink congestion or mild downlink congestion.

[0023] For example, if the level of uplink congestion is lower than a second threshold (e.g., moderate uplink congestion or light uplink congestion), the base station may: i) determine a recommended uplink bit rate and transmit a media access control control element (MAC CE) notification indicating the recommended uplink bit rate to a user equipment (UE); ii) set up a new uplink bearer / flow with an updated QoS; iii) start an AQM process for uplink (UL) traffic; or iv) perform any combination thereof. For example, if the level of uplink congestion is higher than a second threshold (e.g., heavy uplink congestion), the base station may: i) allow part of the uplink traffic according to the QoS; ii) release one or more radio bearers; iii) set up a new uplink bearer / flow with an updated QoS; iv) start an AQM process for UL traffic; or v) perform any combination thereof. Additionally, if the level of uplink congestion is above a second threshold (eg, severe uplink congestion), the base station may perform one or more processes performed for moderate uplink congestion or mild uplink congestion.

[0024] In one aspect, the base station may provide a message or notification that complies with a physical layer communication protocol to the UE to quickly resolve network congestion. For example, for uplink congestion, the base station may determine a recommended uplink bit rate and transmit a MAC CE notification indicating the recommended uplink bit rate to the UE. The UE may adjust the transmission data rate based on the recommended uplink bit rate in response to the MAC CE notification indicating the recommended uplink bit rate, and skip or bypass some transmissions (e.g., buffer status report (BSR) transmission / status report (SR) transmission) to alleviate or reduce uplink congestion. By providing a notification that complies with a physical layer communication protocol rather than an IP layer communication protocol (e.g., ECN), congestion at the RAN between the base station and the UE may be quickly resolved or alleviated. Therefore, communications with low latency and high throughput, such as for augmented reality or virtual reality, may be provided in a seamless manner with less interference due to network congestion.

[0025] Figure 1An example wireless communication system 100 is shown. The wireless communication system 100 may include base stations 110A, 110B (also referred to as "wireless communication nodes 110" or "stations 110") and user equipment (UE) 120AA...120AN, 120BA...120BN (also referred to as "wireless communication devices 120" or "terminal devices 120"). The wireless communication link may be a cellular communication link that complies with 3G, 4G, 5G or other cellular communication protocols. In one example, the wireless communication link supports, adopts or is based on orthogonal frequency division multiple access (OFDMA). In one aspect, UE 120AA...120AN is located within a geographic boundary relative to base station 110A and can communicate with base station 110A or communicate through base station 110A. Similarly, UE 120BA...120BN is located within a geographic boundary relative to base station 110B and can communicate with base station 110B or communicate through base station 110B. The network between UE 120 and base station 110 may be referred to as a radio access network (RAN). Figure 1 The base stations 110 shown in FIG. 1 may be more, fewer, or include the same Figure 1 The base station 110 shown in FIG. 1 is a different base station.

[0026] In some embodiments, UE 120 may be a user device, such as a mobile phone, a smart phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, a wearable computing device (e.g., a head mounted display, a smart watch), etc. Each UE 120 may communicate with a base station 110 via a corresponding wireless communication link. For example, UE 120 may transmit data to base station 110 via a wireless communication link (e.g., a 3G, 4G, 5G or other cellular communication link), and / or receive data from base station 110 via a wireless communication link (e.g., a 3G, 4G, 5G or other cellular communication link). Example data may include audio data, image data, text, etc. Communication or transmission of data by UE 120 to base station 110 may be referred to as uplink communication. Communication or reception of data by UE 120 from base station 110 may be referred to as downlink communication.

[0027] In some embodiments, the base station 110 may be an evolved node B (eNB), a serving eNB, a target eNB, a femto station, or a pico station. The base station 110 may be communicatively coupled to another base station 110 or other communication device via a wireless communication link and / or a wired communication link. The base station 110 may receive data (or RF signals) from the UE 120 in an uplink communication. Additionally or alternatively, the base station 110 may provide data to another UE 120, another base station, or another communication device. Thus, the base station 110 allows communication between multiple UEs 120 associated with the base station 110, or communication between other UEs associated with different base stations.

[0028] In some embodiments, the wireless communication system 100 includes a core network 170. The core network 170 may be a component or an aggregation of multiple components that ensures a reliable and secure connection of the UE 120 to the network. The core network 170 may be communicatively coupled to one or more base stations 110A, 110B via a communication link. The communication link between the core network 170 and the base station 110 may be a wireless communication link (e.g., 3G, 4G, 5G or other cellular communication link) or a wired communication link (e.g., Ethernet, optical communication link, etc.). In some embodiments, the core network 170 includes a user plane function (UPF), an access and mobility management function (AMF), a policy control function (PCF), etc. The UPF may perform packet routing and forwarding, packet inspection, quality of service (QoS) processing, and provide an external protocol data unit (PDU) session for interconnecting data networks (DN). The AMF may perform registration management, reachability management, connection management, etc. The PCF may help operators (or operating equipment) to easily create and seamlessly deploy policies in wireless networks. The core network 170 may include additional components for managing or controlling the operation of the wireless network. In one aspect, the core network 170 may receive a message to perform network congestion control and perform the requested network congestion control. For example, the core network 170 may receive an explicit congestion notification (ECN) from the base station 110 and / or the UE 120 and perform network congestion control according to the ECN. For example, the core network 170 may adjust or control the amount of data generated in response to the ECN. Additionally or alternatively, the core network 170 may adjust or control the amount of data transmitted and / or received in response to the ECN.

[0029] In some embodiments, the wireless communication system 100 includes an application server 160. The application server 160 may be a component or device that generates, manages, or provides content data. The application server 160 may be communicatively coupled to one or more base stations 110A, 110B via a communication link. The communication link between the application server 160 and the base station 110 may be a wireless communication link (e.g., a 3G, 4G, 5G, or other cellular communication link) or a wired communication link (e.g., Ethernet, an optical communication link, etc.). In one aspect, the application server 160 may receive a request for data from the UE 120 via the base station 110, and provide the requested data to the UE 120 via the base station 110. In one aspect, the application server 160 may receive a message to perform network congestion control, and perform the requested network congestion control. For example, the application server 160 may receive an explicit congestion notification (ECN) from the base station 110, the UE 120, or the core network 170, and perform network congestion control according to the ECN. For example, the application server 160 may adjust or control the amount of data generated in response to the ECN. Additionally or alternatively, application server 160 may adjust or control the amount of data transmitted and / or received in response to the ECN.

[0030] In some embodiments, the communication between the base station 110, the UE 120, the application server 160 and the core network 170 is based on one or more layers of the Open Systems Interconnection (OSI) model. The OSI model may include multiple layers, including: a physical layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, a non-access stratum (NAS) layer or an Internet Protocol (IP) layer and other layers.

[0031] Figure 2 1 is a schematic diagram showing example components of a base station 110 and a user equipment 120 according to an example embodiment of the present disclosure. In some embodiments, the UE 120 includes a wireless interface 222, a processor 224, a storage device 226, and one or more antennas 228. These components may be embodied in hardware, software, firmware, or a combination thereof. In some embodiments, the UE 120 includes a Figure 2 More, fewer, or more of the components shown may be included. Figure 2For example, UE 120 may include an electronic display and / or input devices. For example, UE 120 may include Figure 2 The antennas and wireless interfaces shown in FIG. 2 include antenna 228 and wireless interface 222 .

[0032] Antenna 228 can be a component that receives radio frequency (RF) signals and / or transmits RF signals through a wireless medium. The frequency of the RF signal can be between 200 megahertz (MHz) and 100 gigahertz (GHz). The RF signal can have packets, symbols or frames corresponding to the data used for communication. Antenna 228 can be a dipole antenna, a patch antenna, a loop antenna or any suitable antenna for wireless communication. In one aspect, a single antenna 228 is used to transmit and receive RF signals. In one aspect, different antennas 228 are used to transmit and receive RF signals. In one aspect, multiple antennas 228 are used to support multiple-input, multiple-out (MIMO) communications.

[0033] The wireless interface 222 includes or is embodied as a transceiver for transmitting and receiving RF signals through one or more antennas 228. The wireless interface 222 can communicate with the wireless interface 212 of the base station 110 through a wireless communication link. In one configuration, the wireless interface 222 is coupled to one or more antennas 228. In one aspect, the wireless interface 222 can receive an RF signal at an RF frequency received through the antenna 228 and down-convert the RF signal to a baseband frequency (e.g., 0 to 1 GHz). The wireless interface 222 can provide the down-converted signal to the processor 224. In one aspect, the wireless interface 222 can receive a baseband signal for transmission at a baseband frequency from the processor 224 and up-convert the baseband signal to generate an RF signal. The wireless interface 222 can transmit the RF signal through the antenna 228.

[0034] The processor 224 is a component that processes data. The processor 224 may be embodied as a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a logic circuit, etc. The processor 224 may obtain instructions from the storage device 226 and execute these instructions. In one aspect, the processor 224 may receive down-converted data at a baseband frequency from the wireless interface 222 and decode or process the down-converted data. For example, the processor 224 may generate audio data or image data based on the down-converted data and present the audio indicated by the audio data and / or the image indicated by the image data to the user of the UE 120. In one aspect, the processor 224 may generate or obtain data for transmission at a baseband frequency and encode or process the data. For example, the processor 224 may encode or process image data or audio data at a baseband frequency and provide the encoded or processed data to the wireless interface 222 for transmission.

[0035] The storage device 226 is a component that stores data. The storage device 226 may be embodied as a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a register, a hard disk, a removable disk, a CD-ROM, or any device that can be used to store data. The storage device 226 may be embodied as a non-transitory computer-readable medium that stores instructions executable by the processor 224 to perform various functions of the UE 120 disclosed herein. In some embodiments, the storage device 226 and the processor 224 are integrated into a single component.

[0036] In some embodiments, the base station 110 includes a wireless interface 212, a processor 214, a storage device 216, and one or more antennas 218. These components may be embodied in hardware, software, firmware, or a combination thereof. Figure 2 More, fewer, or more of the components shown may be included. Figure 2 For example, base station 210 may include an electronic display and / or input device. For example, base station 210 may include Figure 2 The antennas and wireless interfaces shown in FIG. 2 include antenna 218 and wireless interface 212 .

[0037] Antenna 218 may be a component that receives radio frequency (RF) signals and / or transmits RF signals over a wireless medium. Antenna 218 may be a dipole antenna, a patch antenna, a loop antenna, or any suitable antenna for wireless communication. In one aspect, a single antenna 218 is used to both transmit and receive RF signals. In one aspect, different antennas 218 are used to transmit and receive RF signals. In one aspect, multiple antennas 218 are used to support multiple-input multiple-output (MIMO) communications.

[0038] The wireless interface 212 includes or is embodied as a transceiver for transmitting and receiving RF signals through one or more antennas 228. The wireless interface 212 can communicate with the wireless interface 222 of the UE 120 through a wireless communication link. In one configuration, the wireless interface 212 is coupled to one or more antennas 218. In one aspect, the wireless interface 212 can receive an RF signal at an RF frequency received through the antenna 218 and down-convert the RF signal to a baseband frequency (e.g., 0 to 1 GHz). The wireless interface 212 can provide the down-converted signal to the processor 224. In one aspect, the wireless interface 212 can receive a baseband signal for transmission at a baseband frequency from the processor 214, and up-convert the baseband signal to generate an RF signal. The wireless interface 212 can transmit the RF signal through the antenna 218.

[0039] The processor 214 is a component for processing data. The processor 214 can be embodied as an FPGA, an ASIC, a logic circuit, etc. The processor 214 can obtain instructions from the storage device 216 and execute these instructions. In one aspect, the processor 214 can receive down-converted data at baseband frequency from the wireless interface 212, and decode or process the down-converted data. For example, the processor 214 can generate audio data or image data based on the down-converted data. In one aspect, the processor 214 can generate or obtain data for transmission at baseband frequency, and encode or process the data. For example, the processor 214 can encode or process image data or audio data at baseband frequency, and provide the encoded or processed data to the wireless interface 212 for transmission. In one aspect, the processor 214 can set, specify, schedule or allocate communication resources for different UEs 120. For example, the processor 214 can set different modulation schemes, time slots, channels, frequency bands, etc. for each UE 120 to avoid interference. The processor 214 may generate data (or an uplink configuration grant (UL CG)) indicating the configuration of communication resources and provide the data (or UL CG) to the wireless interface 212 for transmission to the UE 120 .

[0040] The storage device 216 is a component that stores data. The storage device 216 may be embodied as a RAM, a flash memory, a ROM, an EPROM, an EEPROM, a register, a hard disk, a removable disk, a CD-ROM, or any device that can be used to store data. The storage device 216 may be embodied as a non-transitory computer-readable medium that stores instructions executable by the processor 214 to perform various functions of the base station 110 disclosed herein. In some embodiments, the storage device 216 and the processor 214 are integrated into a single component.

[0041] Figure 3 is a schematic diagram of a network congestion controller 300 according to an example embodiment of the present disclosure. The network congestion controller 300 may be implemented as part of the base station 110, and / or any one or more network nodes of the core network / cellular network. The network congestion controller 330 may be implemented as an FPGA, an ASIC, or any logic circuit. The network congestion controller 300 may be implemented as part of the processor 214. In some embodiments, the network congestion controller 300 includes a congestion detector 310, an uplink (UL) congestion controller 320, and a downlink (DL) congestion controller 330. These components may operate together to reduce or alleviate network congestion. In some embodiments, the network congestion controller 300 includes a congestion detector 310, an uplink (UL) congestion controller 320, and a downlink (DL) congestion controller 330. These components may operate together to reduce or alleviate network congestion. Figure 3 The components shown in the figure may be more, fewer, or include the same Figure 3 The components shown in the figure are different components.

[0042] In some embodiments, the congestion detector 310 is a component for detecting / monitoring / measuring network congestion. In one aspect, the congestion detector 310 detects one or more types of network congestion. Examples of types of network congestion may include uplink congestion, downlink congestion, base station node congestion, or any combination thereof. The congestion detector 310 may determine the type of network congestion by determining whether the network congestion occurs for uplink traffic / communication, downlink traffic / communication, or both. In one method, the congestion detector 310 may monitor the buffer state for transmission / reception to determine the type of network congestion. For example, the congestion detector 310 may determine that the type of network congestion is downlink congestion in response to the buffer for downlink communication in the wireless interface 212 being full or having data exceeding a threshold amount within a time period. For example, the wireless interface 212 may determine, check, or monitor the number of UL active users, UL SR or BSR, interference, and / or physical resource block (PRB) utilization within a time period to determine UL congestion and the corresponding congestion level (mild / medium / severe). In one approach, the congestion detector 310 may monitor the amount of unsuccessful transmissions / receptions to determine the type of network congestion. For example, the congestion detector 310 may determine that the type of network congestion is uplink congestion in response to the number of unsuccessful uplink communications across multiple UEs in a time period exceeding a threshold number. Similarly, the congestion detector 310 may determine that the type of network congestion is downlink congestion in response to the number of unsuccessful downlink communications across multiple UEs in a time period exceeding a threshold number. In some embodiments, the congestion detector 310 receives a message indicating the type of network congestion from another device (e.g., UE 120, core network 170, application server 160, or another communication device), and may determine the type of network congestion indicated by the received message.

[0043] In some embodiments, the congestion detector 310 detects or determines the level of network congestion. The congestion detector 310 can determine or select the level of network congestion from multiple candidate levels of network congestion. Examples of multiple candidate levels of uplink congestion may include heavy uplink congestion (e.g., first level congestion), medium uplink congestion (e.g., second level congestion), light uplink congestion (e.g., third level congestion), etc. For example, heavy uplink congestion may have uplink congestion exceeding a first threshold amount; medium uplink congestion may have uplink congestion exceeding a second threshold amount and / or less than a first threshold amount; and light uplink congestion may have uplink congestion less than a second threshold amount, wherein the first threshold amount is higher than the second threshold amount. Although three levels of uplink congestion are provided as examples, different numbers of levels of uplink congestion may be provided. Similarly, examples of multiple candidate levels of downlink congestion may include heavy downlink congestion, medium downlink congestion, light downlink congestion, etc. For example, heavy downlink congestion may have downlink congestion exceeding a third threshold amount; medium downlink congestion may have downlink congestion exceeding a fourth threshold amount; and light downlink congestion may have downlink congestion less than a fourth threshold amount, wherein the third threshold amount is higher than the fourth threshold amount. Although three levels of downlink congestion are provided as examples, different numbers of levels of downlink congestion may be provided. In one method, the congestion detector 310 may monitor a buffer state for transmission / reception, and may determine a level of network congestion corresponding to the buffer state. In one method, the congestion detector 310 may monitor the amount of unsuccessful transmission / reception, and may determine a level of network congestion corresponding to the amount of unsuccessful transmission / reception. In some embodiments, the congestion detector 310 receives a message indicating a level of network congestion from another device (e.g., UE120, core network 170, application server 160, or another communication device), and may determine the level of network congestion indicated by the received message.

[0044] In some embodiments, the UL congestion controller 320 is a component that performs or initiates one or more processes for reducing uplink congestion. In one example, if the level of uplink congestion is below a threshold (e.g., medium uplink congestion or light uplink congestion), the UL congestion controller 320 can determine a recommended uplink bit rate and can cause the wireless interface 212 to transmit a MAC CE notification indicating the recommended uplink bit rate to the UE 120. The UE 120 can adjust the data rate of the uplink transmission, for example, by skipping or bypassing the BSR / SR transmission, or notify the application layer (e.g., of the wireless interface 222 or the processor 224) to adjust the data rate. Additionally or alternatively, if the level of uplink congestion is below a threshold (e.g., medium uplink congestion or light uplink congestion), the UL congestion controller 320 can set a new uplink bearer / flow with an updated QoS, or start an AQM process to reduce or alleviate UL traffic. In one example, if the level of uplink congestion is higher than a threshold (e.g., severe uplink congestion), the UL congestion controller 320 may allow part of the uplink traffic according to QoS priority. Additionally or alternatively, if the level of uplink congestion is higher than a threshold (e.g., severe uplink congestion), the UL congestion controller 320 may release one or more radio bearers using a back-off timer so that the UE 120 may not immediately (or within a time period set by the back-off timer) attempt to retry reestablishing the released bearers. In some embodiments, if the level of uplink congestion is higher than a threshold (e.g., severe uplink congestion), the UL congestion controller 320 may perform one or more processes for mild uplink congestion or moderate uplink congestion described herein.

[0045] In one aspect, the UL congestion controller 320 may generate a message or notification in accordance with a physical layer communication protocol to resolve network congestion, and may cause the wireless interface 212 to transmit the message or notification to the UE 120. For example, for uplink congestion, the UL congestion controller 320 may determine a recommended uplink bit rate, and may generate a MAC CE notification / signaling indicating the recommended uplink bit rate. The UL congestion controller 320 may cause the wireless interface 212 to transmit the MAC CE notification to the UE 120. The UE 120 may skip or bypass a transmission (e.g., a buffer status report (BSR) transmission / status report (SR) transmission) or notify an application layer (e.g., of the wireless interface 222 or the processor 224) to adjust a data rate in response to the MAC CE notification indicating the recommended uplink bit rate. By providing a notification in accordance with a physical layer communication protocol rather than an IP layer communication protocol (e.g., ECN), congestion at the RAN between the base station 110 and the UE 120 may be quickly reduced, resolved, or alleviated. Thus, one or more communications with low latency and high throughput, for example for augmented reality or virtual reality, may be provided in a seamless manner with less interference due to network congestion.

[0046] In some embodiments, the DL traffic controller 330 is a component that executes or initiates one or more processes for reducing downlink congestion. In one example, if the level of downlink congestion is below a threshold (e.g., medium downlink congestion or light downlink congestion), the DL traffic controller 330 may cause the wireless interface 212 to transmit an explicit congestion notification (ECN) to the core network 170. Additionally or alternatively, if the level of downlink congestion is below a threshold (e.g., medium downlink congestion or light downlink congestion), the DL traffic controller 330 may determine a recommended downlink bit rate, and may cause the wireless interface 212 to transmit the recommended downlink bit rate to the core network 170, so that the core network 170 may perform data rate adjustment or traffic shaping according to the recommended downlink bit rate. Alternatively or additionally, if the level of downlink congestion is below a threshold (e.g., medium downlink congestion or light downlink congestion), the DL traffic controller 330 may set a new downlink bearer / flow with an updated QoS, or initiate an AQM process to reduce or alleviate DL traffic. In one example, if the level of downlink congestion is higher than a threshold (e.g., severe downlink congestion), the DL traffic controller 330 may drop one or more packets based on QoS priority. Additionally or alternatively, if the level of downlink congestion is higher than a threshold (e.g., severe downlink congestion), the DL traffic controller 330 may release one or more radio bearers using a backoff timer indication. In some embodiments, if the level of downlink congestion is higher than a threshold (e.g., severe downlink congestion), the DL congestion controller 330 may also perform one or more processes for light downlink congestion or moderate downlink congestion described herein.

[0047] In some embodiments, the DL traffic controller 330 may generate a physical layer message or notification and may cause the wireless interface 212 to transmit such a physical layer message or notification. For example, the DL traffic controller 330 may cause the wireless interface 212 to generate a MAC CE notification to cause the UE 120 to set or configure a connected mode discontinuous reception (CDRX) setting and may cause the wireless interface 212 to transmit the MAC CE notification to the UE 120. The UE 120 may set or configure the CDRX setting in response to receiving the MAC CE notification to reduce the duty cycle for monitoring the downlink. By reducing the duty cycle for monitoring the downlink, the UE 120 may reduce power consumption. In addition, by providing notifications that comply with a physical layer communication protocol rather than an IP layer communication protocol (e.g., ECN), the UE 120 may adjust its configuration in a rapid manner.

[0048] Figure 44 is an example IP layer data frame 400 including fields for congestion control according to an example embodiment of the present disclosure. In some embodiments, the data frame 400 includes fields 410, 420, 430, 440, 450, and 460. The IP layer data frame 400 may be provided by the base station 110. For example, the IP layer data frame 400 may be provided for the ECN. In some embodiments, the IP layer data frame 400 may also be provided by the UE 120, the application server 160, the core network 170, or any communication device.

[0049] In one aspect, fields 410 to 430 may be general packet radio service tunneling protocol user plane (GTP-U) tunnel header information. In some embodiments, one or more bits or data for congestion control may be provided in field 410. Field 410 may be / include an IP header (field) that includes an ECN bit (e.g., two bits) in a differentiated services code point (DSCP) for GTP-U tunnel network congestion control. Field 420 may be / include a user datagram protocol (UDP) field, and field 430 may be a GTP-U field. In some embodiments, according to the ECN bit in field 410, the core network 170 and / or the application server 160 may perform network congestion control. For example, '01' or '10' of the ECN bit in field 410 may indicate that the sender of the data frame 400 is capable of ECN. For example, '00' of the ECN bits in field 410 may indicate that the sender of data frame 400 is not using ECN. For example, '11' of the ECN bits in field 410 may indicate whether network congestion is detected. The core network 170 and / or the application server 160 may initiate a process to reduce network congestion, such as by performing traffic shaping, reducing downlink data rate, etc., in response to receiving '11' in the ECN bits.

[0050] In one aspect, fields 440 to 460 may be application IP packets. In some embodiments, one or more bits or data for congestion control may be provided in any of fields 440 to 450. Field 440 may be an IP header including an ECN bit (e.g., two bits) for application layer network congestion control. Field 450 may be a transmission control protocol (TCP) / UDP field. Field 460 may be a field including application data. In some embodiments, based on the ECN bit in field 440, the core network 170 and / or the application server 160 may perform network congestion control in a manner similar to that described above with respect to the ECN bit in field 410.

[0051] Figure 5 is an example MAC CE 500 for congestion control according to an example implementation of the present disclosure. In some embodiments, MAC CE 500 includes fields 510 to 540 and 550A to 550E. MAC CE 500 may be provided / sent by base station 110. For example, MAC CE 500 may be provided to cause, trigger, or initiate network congestion control.

[0052] Field 510 may include or indicate a logical channel identifier (LCID) to which the recommended bit rate or recommended bit rate query applies. Field 520 may include or indicate whether the recommended bit rate or recommended bit rate query applies to the uplink or downlink. For example, '0' may indicate a downlink, while '1' may indicate an uplink (or vice versa). Fields 530, 540 may include or indicate a recommended bit rate. Fields 550A to 550E may be reserved fields.

[0053] In one aspect, the reserved fields 550A to 550E may be utilized / reutilized / configured to perform, trigger, initiate, or cause network congestion control. Each reserved field 550 may have one bit. In one method, two bits (or two reserved fields in each reserved field 550) may be utilized to indicate the level of network congestion. For example, '00' may indicate that no network congestion is detected, '01' or '10' may indicate that light RAN congestion / medium RAN congestion is detected, and '11' may indicate that heavy RAN congestion is detected. The base station 110 may utilize fields 530, 540 and two bits of the reserved fields 550A to 550E to notify the UE 120 of the current RAN network congestion direction and the level of network congestion. For example, for light RAN congestion / moderate RAN congestion, base station 110 may send field 520 indicating uplink congestion, UL bit rate recommendation in fields 530 and 540 and '01' in reserved field 550 to notify or enable UE 120 to adjust the UL service bit rate to alleviate RAN network congestion.

[0054] Figure 6 6 is a flow chart illustrating a process 600 for reducing network congestion according to an example embodiment of the present disclosure. In some embodiments, the process 600 is performed by the base station 110. In some embodiments, the process 600 is performed by other entities. In some embodiments, the process 600 includes: Figure 6 More, fewer, or more steps than those shown in Figure 6 The steps shown in the are different steps.

[0055] In one method, the base station 110 determines 610 the type of network congestion. Examples of the type of network congestion include uplink congestion, downlink congestion, or both. The congestion detector 310 can determine the type (e.g., direction) of network congestion by determining whether the network congestion occurs for the uplink, downlink, or both. In one method, the base station 110 can monitor the buffer status for transmission / reception to determine the type of network congestion. In one method, the base station 110 can monitor the amount (e.g., level, degree) of unsuccessful transmission / reception to determine the type of network congestion. In some embodiments, the base station 110 receives a message indicating the type of network congestion from another device (e.g., UE 120, core network 170, application server 160, or another communication device), and determines the type of network congestion indicated by the received message.

[0056] In one method, the base station 110 determines 620 a level (e.g., amount, range, degree) of network congestion. The base station 110 may determine or select a level of network congestion from a plurality of candidate levels of network congestion. Examples of a plurality of candidate levels of uplink congestion may include heavy uplink congestion, medium uplink congestion, light uplink congestion, etc. Similarly, examples of a plurality of candidate levels of downlink congestion may include heavy downlink congestion, medium downlink congestion, light downlink congestion, etc. In one method, the base station 110 may monitor a buffer status for transmission / reception, and may determine a level of network congestion corresponding to the buffer status. In one method, the base station 110 may monitor the amount of unsuccessful transmission / reception within a time period, and determine a level of network congestion corresponding to the amount of unsuccessful transmission / reception. In some embodiments, base station 110 receives a message indicating a level of network congestion from another device (eg, UE 120, core network 170, application server 160, or another communication device) and may determine the level of network congestion indicated by the received message.

[0057] In one approach, the base station 110 determines 630 one or more processes for reducing network congestion based on the determined type of network congestion and the determined level of network congestion. For example, if the determined type of network congestion is downlink congestion, the base station 110 may select one or more processes from a set of processes for reducing downlink congestion based on the level of downlink congestion. Figure 7 An example of determining or selecting one or more processes for reducing downlink congestion based on the level of downlink congestion is provided. For example, if the determined type of network congestion is uplink congestion, the base station 110 can select one or more processes from a set of processes for reducing uplink congestion based on the level of uplink congestion. Figure 8 An example of determining or selecting one or more processes for reducing uplink congestion according to the level of uplink congestion is provided. If the determined type of network congestion is both uplink congestion and downlink congestion, the base station 110 may select one or more processes from a set of processes for reducing uplink congestion according to the level of uplink congestion, and may select one or more processes from a set of processes for reducing downlink congestion according to the level of downlink congestion.

[0058] In one approach, the base station 110 performs 640 the one or more processes determined.

[0059] Figure 7is a flow chart illustrating a process 700 for reducing downlink congestion according to an example embodiment of the present disclosure. In some embodiments, the process 700 is performed by the base station 110. In some embodiments, the process 700 is performed by other entities. In some embodiments, the process 700 is performed as Figure 7 In some embodiments, process 700 includes: Figure 7 More, fewer, or including the same steps as shown in Figure 7 The steps shown in the are different steps.

[0060] In one approach, the base station 110 determines 710 from step 610 that the type of network congestion is downlink congestion. For example, the congestion detector 310 may determine that the type of network congestion is downlink congestion in response to a buffer for downlink communications being full or having more than a threshold amount of data in a time period. For example, the congestion detector 310 may determine that the type of network congestion is downlink congestion in response to a number of unsuccessful downlink communications in a time period exceeding a threshold amount.

[0061] In one method, the base station 110 determines 720 whether the level of downlink congestion is heavy downlink congestion or light downlink congestion / medium downlink congestion. For example, heavy downlink congestion may have downlink congestion exceeding a threshold amount, wherein light downlink congestion / medium downlink congestion may have downlink congestion less than a threshold amount.

[0062] In one method, in response to the base station 110 determining that the level of downlink congestion is severe downlink congestion, the base station 110 may select 730 one or more first processes for reducing downlink congestion. The one or more first processes for reducing downlink congestion may include at least one of: determining a priority of a group of packets; dropping one or more packets in the group of packets according to the determined priority; or releasing one or more radio bearers with a backoff timer indication. The one or more first processes for reducing downlink congestion may also include at least one of: transmitting an ECN to the core network 170; determining a recommended downlink bit rate; transmitting a recommended downlink bit rate to the core network 170; setting a new downlink bearer / flow with an updated QoS; or initiating an AQM process to reduce or alleviate DL traffic.

[0063] In one method, in response to the base station 110 determining that the level of downlink congestion is light downlink congestion / moderate downlink congestion, the base station 110 may select 735 one or more second processes for reducing downlink congestion. The one or more second processes for reducing downlink congestion may include at least one of: transmitting an ECN to the core network 170; determining a recommended downlink bit rate; transmitting a recommended downlink bit rate to the core network 170; setting a new downlink bearer / flow with an updated QoS; or initiating an AQM process to reduce or alleviate DL traffic. Therefore, the one or more first processes for reducing downlink congestion may include one or more second processes for reducing downlink congestion.

[0064] In one method, one or more first processes and / or one or more second processes may include transmitting a MAC CE notification to UE 120. In response to the MAC CE notification, UE 120 may reduce a duty cycle for monitoring the downlink. By reducing the duty cycle for monitoring the downlink, UE 120 may reduce power consumption. In addition, by providing a notification that complies with a physical layer communication protocol rather than an IP layer communication protocol (e.g., ECN), UE 120 may adjust its configuration in a prompt manner.

[0065] Figure 8 is a flow chart illustrating a process 800 for reducing uplink congestion according to an example embodiment of the present disclosure. In some embodiments, the process 800 is performed by the base station 110. In some embodiments, the process 800 is performed as Figure 8 In some embodiments, process 800 is performed by other entities. In some embodiments, process 800 includes: Figure 8 More, fewer, or including the same steps as shown in Figure 8 The steps shown in the are different steps.

[0066] In one approach, the base station 110 determines 810 from step 610 that the type of network congestion is uplink congestion. For example, the congestion detector 310 may determine that the type of network congestion is uplink congestion in response to a buffer for uplink communications being full or having more than a threshold amount of data in a time period. For example, the congestion detector 310 may determine that the type of network congestion is uplink congestion in response to a number of unsuccessful uplink communications in a time period exceeding a threshold amount.

[0067] In one method, the base station 110 determines 820 whether the level of uplink congestion is heavy uplink congestion or light uplink congestion / medium uplink congestion. For example, heavy uplink congestion may have uplink congestion exceeding a threshold amount, wherein light uplink congestion / medium uplink congestion may have uplink congestion less than a threshold amount. In some embodiments, in order to determine whether the type of network congestion is uplink congestion and the corresponding congestion level (light / medium / heavy), the base station 110 may determine, check or monitor the number of UL active users, UL SR or BSR, and interference / PRB utilization within a time period.

[0068] In one method, in response to the base station 110 determining that the level of uplink congestion is severe uplink congestion, the base station 110 may select / initiate / implement 830 one or more processes for reducing uplink congestion. The one or more first processes for reducing uplink congestion may include at least one of the following: performing congestion control by allowing part of the uplink traffic according to the quality of service; or releasing one or more radio bearers. The one or more first processes for reducing / suppressing / alleviating uplink congestion may also include at least one of the following: determining a recommended uplink bit rate; transmitting a MAC CE notification indicating the recommended uplink bit rate to a user equipment (UE); or setting up a new uplink bearer / flow with an updated QoS; or initiating an AQM process to reduce or alleviate UL traffic.

[0069] In one method, in response to the base station 110 determining that the level of uplink congestion is light uplink congestion / moderate uplink congestion, the base station 110 may select 835 one or more second processes for reducing uplink congestion. The one or more second processes for reducing uplink congestion may also include at least one of: determining a recommended uplink bit rate; transmitting a MAC CE notification indicating the recommended uplink bit rate to a user equipment (UE); setting up a new uplink bearer / flow with an updated QoS; or initiating an AQM process to reduce or alleviate UL traffic. Therefore, the one or more first processes for reducing uplink congestion may include one or more second processes for reducing uplink congestion.

[0070] In one aspect, providing MAC CE notifications can help reduce or alleviate network congestion in a prompt manner. For example, UE 120 can skip or bypass transmission (e.g., buffer status report (BSR) transmission / status report (SR) transmission) or notify the application layer (e.g., of wireless interface 222 or processor 224) to reduce the UL transmission data rate in response to a MAC CE notification indicating a recommended uplink bit rate. By providing notifications that comply with a physical layer communication protocol rather than an IP layer communication protocol (e.g., ECN), congestion at the RAN between base station 110 and UE 120 can be quickly resolved or alleviated. Therefore, communications with low latency and high throughput, such as for augmented reality or virtual reality, can be provided in a seamless manner with less interference due to network congestion.

[0071] Now that some illustrative embodiments have been described, it will be apparent that the foregoing, which has been presented by way of example, is illustrative and not restrictive. Specifically, although many of the examples presented herein involve specific combinations of method actions or system elements, these actions and these elements may be combined in other ways to achieve the same purpose. The actions, elements, and features discussed in conjunction with one embodiment are not intended to be excluded from similar roles in other embodiments or from the embodiments.

[0072] The hardware and data processing components for implementing the various processes, operations, illustrative logic, logic blocks, modules and circuits described in conjunction with the embodiments disclosed herein can be implemented or executed using the following components designed to perform the functions described herein: a general-purpose single-chip processor or a general-purpose multi-chip processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof. A general-purpose processor may be a microprocessor, or may be any conventional processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of multiple computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration. In some embodiments, specific processes and methods may be performed by circuit systems specific to a given function. A memory (e.g., a memory, a storage unit, a storage device, etc.) may include one or more devices (e.g., RAM, ROM, flash memory, hard disk storage, etc.) for storing data and / or computer code, which is used to complete or facilitate the various processes, various layers and various modules described in this disclosure. The memory may be or may include volatile memory or non-volatile memory, and may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. According to an exemplary embodiment, the memory is communicatively connected to the processor via the processing circuit, and the memory includes computer code for executing (e.g., by the processing circuit and / or the processor) one or more processes described herein.

[0073] The present disclosure contemplates methods, systems, and program products on any machine-readable medium for implementing various operations. The various embodiments of the present disclosure can be implemented using existing computer processors, or by a dedicated computer processor for an appropriate system combined for this purpose or another purpose, or by a hard-wired system. The various embodiments within the scope of the present disclosure include multiple program products, which include machine-readable media, which are used to carry or have machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available medium that can be accessed by a general-purpose computer or a special-purpose computer, or other machines with a processor. As an example, such machine-readable media can include RAM, ROM, EPROM, EEPROM, or other optical disk storage, disk storage, or other magnetic storage devices, or can include any other medium as follows: the other medium can be used to carry or store the desired program code in the form of machine-executable instructions or data structures, and can be accessed by a general-purpose computer or a special-purpose computer, or other machines with a processor. The above combinations are also included in the scope of machine-readable media. Machine-executable instructions, for example, include instructions and data that cause a general-purpose computer, a special-purpose computer, or a special-purpose processing machine to perform a certain function or a certain group of functions.

[0074] The words and terms used herein are for descriptive purposes and should not be considered limiting. The use of "comprises," "including," "having," "containing," "involving," "characterized by," "characterized by," and variations thereof herein is meant to encompass the items listed thereafter, their equivalents and additional items, and alternative embodiments consisting exclusively of the items listed thereafter. In one embodiment, the systems and methods described herein consist of one element, action, or component of each element, action, or component described, each combination of more than one of each element, action, or component described, or all of the elements, actions, or components described.

[0075] Any reference to an embodiment or element or action of the systems and methods herein in the singular may also encompass embodiments including a plurality of these elements, and any reference to any embodiment or element or action herein in the plural may also encompass embodiments including only a single element. References in the singular or plural are not intended to limit the systems or methods of the present disclosure, their parts, actions or elements to a singular or plural configuration. References to any action or element based on any information, action or element may include embodiments in which the action or element is based at least in part on any information, action or element.

[0076] Any embodiment disclosed herein may be combined with any other embodiment or example, and references to "an embodiment," "some embodiments," or "an embodiment," etc. are not necessarily mutually exclusive, but are intended to indicate that a particular feature, structure, or characteristic described in conjunction with the embodiment may be included in at least one embodiment or example. These terms as used herein do not necessarily all refer to the same embodiment. Any embodiment may be combined, inclusively or exclusively, with any other embodiment in any manner consistent with the various aspects and embodiments disclosed herein.

[0077] Where reference numerals are provided after technical features in the drawings, detailed description or any claims, these reference numerals have been included to increase the intelligibility of the drawings, detailed description and claims. Therefore, the presence or absence of these reference numerals has no limiting effect on the scope of any claim element.

[0078] The systems and methods described herein may be embodied in other specific forms without departing from the characteristics of the present invention. Unless otherwise expressly indicated, references to "approximately," "about," "substantially," or other terms of degree include variations of plus or minus 10% (+ / -10%) from a given measurement, unit, or range. Coupled elements may be electrically, mechanically, or physically coupled to each other directly, or may be electrically, mechanically, or physically coupled to each other through intermediate elements. Accordingly, the scope of the systems and methods described herein is indicated by the appended claims rather than the preceding description, and modifications within the meaning and range of equivalents of the claims are included therein.

[0079] The term "coupled" and variations thereof include two components being directly joined to one another or indirectly joined to one another. Such joining may be constant (e.g., permanent or fixed) or movable (e.g., removable or releasable). Such joining may be achieved by the two components being directly coupled or coupled to one another, by the two components being coupled to one another using a separate intermediate component, and by the two components being coupled to one another through any additional intermediate components, or by the two components being coupled to one another using an intermediate component that is integrally formed as a single, unitary body with one of the two components. If "coupled" or variations thereof are modified by additional terms (e.g., directly coupled), the general definition of "coupled" provided above is modified by the plain language meaning of the additional terms (e.g., "directly coupled" means that the two components are joined without any separate intermediate components), thereby producing a narrower definition than the general definition of "coupled" provided above. Such coupling may be mechanical, electrical, or fluid.

[0080] References to "or" may be interpreted as inclusive, such that any term described using "or" may mean any of a single described term, more than one described term, and all described terms. References to "at least one of 'A' and 'B'" may include only 'A', only 'B', and both 'A' and 'B'. Such references used in conjunction with "including" or other public terms may include additional items.

[0081] Various modifications may be made to the elements and actions described, such as variations in size, dimensions, structure, shape, and proportion of various elements, and variations in parameter values, mounting arrangements, use of materials, colors, orientations, without departing substantially from the teachings and advantages of the subject matter disclosed herein. For example, an element shown as being integrally formed may be composed of multiple parts or elements, the positions of the elements may be reversed or otherwise modified, and the nature or number or position of discrete elements may be changed or modified. Other substitutions, modifications, alterations, and omissions may also be made in the design, operating conditions, and arrangement of the disclosed elements and operations without departing from the scope of the present disclosure.

[0082] References herein to the positions of elements (e.g., "top," "bottom," "above," "below") are only used to describe the orientation of the various elements in the drawings. The orientation of the various elements may be different according to other exemplary embodiments, and these variations are intended to be encompassed by the present disclosure.

Claims

1. A base station of a wireless cellular network, comprising: at least one processor, the at least one processor being configured to: determining a level of network congestion from a plurality of candidate levels of network congestion, determining whether the type of network congestion includes uplink congestion or downlink congestion, determining one or more processes for reducing the network congestion based on the determined level of network congestion and the determined type of network congestion, and The determined one or more processes are executed.

2. The base station according to claim 1, wherein: The type of network congestion includes downlink congestion, and the one or more processes include: one or more first processes performed in response to determining that the level of downlink congestion is a first level of downlink congestion above a threshold, and One or more second processes are performed in response to determining that the level of downlink congestion is a second level of downlink congestion below the threshold.

3. The base station according to claim 2, wherein: The one or more first processes include at least one of the following: Prioritize a set of groups; discarding one or more packets in the group of packets according to the determined priority; or Release one or more radio bearers.

4. The base station according to claim 3, wherein: The one or more second processes include at least one of the following: Enable the radio interface to transmit an explicit congestion notification (ECN) to the core network; determining a recommended downlink bit rate; causing the wireless interface to transmit the recommended downlink bit rate to the core network; Setting up a downlink bearer with an updated quality of service; or Initiate active queue management process for downlink traffic.

5. The base station according to claim 4, wherein: The one or more first processes include the one or more second processes.

6. The base station according to claim 4 or 5, wherein: The at least one processor is configured to: in response to the type of network congestion being the downlink congestion, cause the wireless interface to transmit a media access control element (MAC CE) notification to a user equipment (UE), wherein the UE is configured to reduce a duty cycle for monitoring the downlink in response to the MAC CE notification.

7. The base station according to claim 1, wherein: The type of network congestion includes the uplink congestion, and the one or more processes include: one or more first processes performed in response to determining that the level of uplink congestion is a first level of uplink congestion above a threshold, and one or more second processes performed in response to determining that the level of uplink congestion is a second level of uplink congestion below the threshold; and preferably, one or more of the following: i. wherein the one or more first processes include at least one of the following: Perform congestion control by allowing some uplink traffic based on quality of service; or releasing one or more radio bearers; ii. wherein the one or more second processes include at least one of the following: determining a recommended uplink bit rate; causing a radio interface to transmit a medium access control control element (MAC CE) notification indicating the recommended uplink bit rate to a user equipment (UE); Setting up a new uplink bearer with updated quality of service; or Initiate active queue management process for uplink traffic; iii. wherein the one or more first processes include the one or more second processes.

8. A base station according to any one of the preceding claims, wherein: The type of network congestion includes both the uplink congestion and the downlink congestion.

9. A method comprising: Determining, by a base station of the wireless cellular network, the level of network congestion from a plurality of candidate levels of network congestion; Determining, by the base station, whether the type of the network congestion includes uplink congestion or downlink congestion; Determining, by the base station, one or more processes for reducing the network congestion according to the determined level of the network congestion and the determined type of the network congestion; as well as The determined one or more processes are performed by the base station.

10. The method according to claim 9, wherein: The type of network congestion includes downlink congestion, and the one or more processes include: one or more first processes performed in response to determining that the level of downlink congestion is a first level of downlink congestion above a threshold, and One or more second processes are performed in response to determining that the level of downlink congestion is a second level of downlink congestion below the threshold.

11. The method according to claim 10, wherein: The one or more first processes include at least one of the following: Determining, by the base station, a priority of a group of packets; The base station discards one or more packets in the group of packets according to the determined priority; or One or more radio bearers are released by the base station.

12. The method according to claim 11, wherein: The one or more second processes include at least one of the following: Transmitting, by the base station, an explicit congestion notification (ECN) to a core network; determining, by the base station, a recommended downlink bit rate; transmitting, by the base station, the recommended downlink bit rate to the core network; Setting, by the base station, a new downlink bearer with updated quality of service; or An active queue management process is initiated by the base station for downlink traffic.

13. The method according to claim 12, wherein: The one or more first processes include the one or more second processes.

14. The method according to any one of claims 9 to 13, further comprising: The base station transmits a media access control element (MAC CE) notification to a user equipment (UE) in response to the type of network congestion including the downlink congestion, wherein the UE is configured to reduce a duty cycle of monitoring the downlink in response to the MAC CE notification.

15. The method according to any one of claims 9 to 14, wherein: The type of network congestion includes the uplink congestion, and the one or more processes include: one or more first processes performed in response to determining that the level of uplink congestion is a first level of uplink congestion above a threshold, and one or more second processes performed in response to determining that the level of uplink congestion is a second level of uplink congestion below the threshold; and preferably, one or more of the following: i. wherein the one or more first processes include at least one of the following: Perform congestion control by allowing some uplink traffic based on quality of service; or releasing one or more radio bearers; and The one or more second processes include at least one of the following: determining a recommended uplink bit rate; transmitting, by the base station to a user equipment (UE), a media access control element (MAC CE) notification indicating the recommended uplink bit rate; Setting up a new uplink bearer with updated quality of service; or Initiate active queue management process for uplink traffic; ii. wherein the one or more first processes include the one or more second processes.

Citation Information

Cited By

  • Coding rate adjusting method and related equipment

    CN119363294A

  • Control signal transmission method for second-level refreshing of ten-thousand-level measuring points in intelligent centralized control system

    CN122395119A