Bandwidth throttling in wireless access networks

Abstract

This disclosure relates to bandwidth throttling in a radio access network. Specifically, it relates to systems, methods, and software for managing bandwidth allocated to a user equipment (UE). In one embodiment, a bandwidth management system collects cell load information from multiple cells within a radio access network (RAN) and processes the cell load information to determine the cell load state of each cell. The system performs bandwidth throttling on the UE by: determining the location of the UE, identifying the cell load state of one or more cells in an area of ​​the RAN corresponding to the UE's location, determining whether the area of ​​the RAN is overloaded based on the cell load state, and controlling a degradation of the bandwidth allocated to the UE in the RAN in response to determining that the area is overloaded.

Description

Technical Field

[0001] This disclosure relates to the field of communication systems, and more particularly to radio access networks (RAN). Background Technology

[0002] The Radio Access Network (RAN) is part of a mobile communication system that interacts with mobile devices (e.g., User Equipment (UE)) via radio access technologies to connect the mobile devices to the core network for service delivery. The RAN comprises multiple base stations providing coverage for mobile devices over geographical areas in the form of cells. Mobile devices provide subscribers with access to various types of data services offered by service providers. Data service usage can increase due to the variety of mobile devices and the number of data services available to subscribers, especially with the rollout of next-generation networks (e.g., fifth-generation (5G)) offering improved speeds and connectivity. As the number of subscribers with multiple devices increases, along with the growing volume of applications and data services, RAN resources can become overloaded. Therefore, service providers continue to seek solutions for scenarios where RAN components become overloaded. Summary of the Invention

[0003] This document describes a system and associated method for managing bandwidth allocated to UEs in a RAN. The system described herein monitors the cell load status of RAN cells and identifies which cells are currently or will be overloaded. When a UE is located in an overloaded area or region within the RAN (i.e., one or more cells in that area are overloaded or about to be overloaded based on predetermined traffic), the system can degrade the bandwidth allocated to the UE in the RAN. Degrading the UE's bandwidth in this manner provides the following technical advantages: preventing RAN resources in overloaded areas from being consumed by a small number of heavy users in that area.

[0004] One embodiment includes a bandwidth management system comprising at least one processor and a memory. The processor causes the bandwidth management system to collect cell load information of multiple cells within a RAN and processes the cell load information to determine the cell load state of each cell. The processor causes the bandwidth management system to perform bandwidth throttling for a UE (User Equipment) of a user within the RAN by: determining the location of the UE; identifying the cell load state of one or more cells in an area of ​​the RAN corresponding to the UE's location; determining whether the area of ​​the RAN is overloaded based on the cell load state of the one or more cells in the area; and, in response to determining that the area is overloaded, controlling the degradation of bandwidth allocated to the UE in the RAN.

[0005] In another embodiment, the processor causes the bandwidth management system to generate a bandwidth throttling request, which requests a change in the policy for the UE to degrade the bandwidth allocated to the UE, and sends the bandwidth throttling request to the policy control element.

[0006] In another embodiment, the bandwidth management system is implemented in the billing system, and the processor causes the bandwidth management system to perform bandwidth throttling for the UE in response to receiving a billing request from the UE.

[0007] In another embodiment, the processor causes the bandwidth management system to perform bandwidth throttling for the UE in response to receiving an initial billing request for a new data session for the UE.

[0008] In another embodiment, the processor causes the bandwidth management system to perform bandwidth throttling for the UE in response to receiving a temporary billing request for an ongoing data session of the UE.

[0009] In another embodiment, the processor causes the bandwidth management system to trigger a tariff discount for the UE in response to determining that the area is underloaded.

[0010] In another embodiment, the billing system includes a 5G billing function (CHF).

[0011] In another embodiment, the billing system includes an online billing system (OCS).

[0012] In another embodiment, the billing system includes an offline billing system (OFCS).

[0013] Another embodiment includes a method for managing bandwidth allocated to a UE. The method includes collecting cell load information of multiple cells within a RAN and processing the cell load information to determine the cell load state of each cell. The method further includes performing bandwidth throttling for a UE whose location is determined to be that of a user within the RAN, identifying the cell load state of one or more cells in an area of ​​the RAN corresponding to the UE's location, determining whether the area of ​​the RAN is overloaded based on the cell load state of the one or more cells in the area, and controlling a degradation of the bandwidth allocated to the UE in the RAN in response to determining that the area is overloaded.

[0014] In another embodiment, controlling the degradation of bandwidth allocated to the UE includes generating a bandwidth throttling request that requests a change in the policy for the UE to degrade the bandwidth allocated to the UE, and sending the bandwidth throttling request to the policy control element.

[0015] In another embodiment, bandwidth throttling is performed at a bandwidth management system implemented in the billing system, and performing bandwidth throttling includes performing bandwidth throttling for the UE in response to receiving a billing request from the UE.

[0016] In another embodiment, performing bandwidth throttling includes performing bandwidth throttling for the UE in response to receiving an initial billing request for a new data session for the UE.

[0017] In another embodiment, performing bandwidth throttling includes performing bandwidth throttling for the UE in response to receiving a temporary billing request for an ongoing data session of the UE.

[0018] In another embodiment, the method further includes triggering a tariff discount for the UE in response to determining that the area is underloaded.

[0019] Another embodiment includes a bandwidth management system comprising means for collecting cell load information of multiple cells within a RAN, and means for processing the cell load information to determine the cell load state of each cell. The bandwidth management system further includes means for performing bandwidth throttling by determining that the UE is a user of the RAN, identifying the cell load state of one or more cells in an area of ​​the RAN corresponding to the UE's location, determining whether an area of ​​the RAN is overloaded based on the cell load state of one or more cells in the area, and controlling the degradation of bandwidth allocated to the UE in the RAN in response to determining that the area is overloaded.

[0020] Other embodiments may include computer-readable media, other systems, or other methods, as described below.

[0021] The foregoing summary provides a basic understanding of some aspects of this specification. This summary is not a broad overview of this specification. It is not intended to identify key or essential elements of this specification, nor is it intended to define any scope of particular embodiments of this specification, or any scope of the claims. Its sole purpose is to introduce some concepts of this specification in a simplified form as a prelude to the more detailed description that follows. Attached Figure Description

[0022] Some embodiments of the invention will now be described by way of example only and with reference to the accompanying drawings. In all the drawings, the same reference numerals denote the same elements or elements of the same type.

[0023] Figure 1 A communication system is shown in an illustrative embodiment.

[0024] Figure 2 The non-roaming architecture of a next-generation network is illustrated in the illustrative embodiment.

[0025] Figure 3 A PCC architecture for an LTE network is shown in an illustrative embodiment.

[0026] Figure 4This is a block diagram of the bandwidth management system in an illustrative embodiment.

[0027] Figure 5 This is a flowchart illustrating a method for managing bandwidth allocated to a UE in an illustrative embodiment.

[0028] Figure 6 The illustrated embodiment shows a geographical area served by the RAN.

[0029] Figure 7 This is a block diagram of a billing system including a bandwidth management system in an illustrative embodiment.

[0030] Figure 8 This is a flowchart illustrating a method for managing bandwidth allocated to a UE, performed in a billing system according to an illustrative embodiment.

[0031] Figures 9 to 10 This is a message diagram illustrating the interaction between CHF and PCF in the illustrative embodiment. Detailed Implementation

[0032] The accompanying drawings and the following description illustrate specific exemplary embodiments. Therefore, it should be understood that those skilled in the art will be able to design various arrangements, which, while not explicitly described or shown herein, embody the principles of the invention and are included within the scope of the embodiments. Furthermore, any examples described herein are intended to aid in understanding the principles of the embodiments and should be understood as not being limited to such specific examples and conditions. Therefore, the inventive concepts(s) are not limited to the specific embodiments or examples described below, but are defined by the claims and their equivalents.

[0033] Figure 1 A communication system 100 is illustrated in an illustrative embodiment. The communication system 100 is a carrier's cellular network or mobile telecommunications network, where the last link is wireless. The communication system 100 is a third-generation (3G) network, a fourth-generation (4G) network (e.g., a Long Term Evolution (LTE) network), a next-generation network (e.g., 5G or later), or another type of network. The communication system 100 provides voice, data, or other communication services to a number of devices, referred to herein as User Equipment 110. UE 110 can be enabled for voice services, data services, machine-to-machine (M2M) or machine-type communication (MTC) services, and / or other services. UE 110 can be an end-user device, such as a mobile phone (e.g., a smartphone) or mobile device, a tablet computer or PDA, a computer with a mobile broadband adapter, etc. UE 110 can be operated by a user or subscriber of the communication system 100; therefore, the terms "UE," "user," and "subscriber" are used interchangeably.

[0034] Communication system 100 includes one or more radio access networks (RANs) 120 that communicate with UE 110 via a radio interface. RAN 120 may support Evolved UMTS Terrestrial Radio Access Network (E-UTRAN), Wireless Local Area Network (WLAN) access, New Radio Access Technology (RAT), etc. As an example, RAN 120 may include E-UTRAN or Next Generation RAN (NG-RAN). RAN 120 includes multiple base stations 122 distributed across a geographic area. Base station 122 includes entities that communicate with UE 110 using wireless communication technologies and engage UE 110 with core network 130. Base station 122 includes devices configured to engage with UE 110 via an air interface, such as antennas, transmitters, receivers, etc., and devices configured to engage with core network 130, such as routers, controllers, etc. Each base station 122 provides radio coverage to cell 124 (or multiple cells). One or more of the base stations 122 may communicate on licensed spectrum or via 3GPP access, and one or more of the base stations 122 may communicate on unlicensed spectrum or non-3GPP access. In one embodiment, one or more of the base stations 122 may include an evolved Node B (eNodeB) of E-UTRAN. In another embodiment, one or more of the base stations 122 may include a gNodeB (NR base station) of NG-RAN and / or an ng-eNodeB (LTE base station supporting a 5G core network).

[0035] Core network 130 is the central part of communication system 100 that interconnects RAN 120 and data network 140. One example of core network 130 is the Evolved Packet Core (EPC) network proposed by 3GPP for LTE. Another example of core network 130 is the 5G core network proposed by 3GPP. Core network 130 is able to access data network 140 to provide data services to UE 110, such as web browsing, online gaming, streaming video, streaming audio, etc. Data network 140 can be a public or private data network outside the operator, or an internal data network within the operator (e.g., for IMS services). One example of data network 140 is the Internet.

[0036] The core network 130 includes multiple network elements or network functions (NFs), which may include servers, devices, equipment (including hardware), software instances running on dedicated hardware, virtualization functions instantiated on a suitable platform (e.g., cloud infrastructure), etc. In this embodiment, the core network 130 includes a policy control element 132 and a charging system 134. The policy control element 132 includes means, components, or modules (including hardware) configured to handle policy decisions (which may also be referred to as making policy and charging control (PCC) decisions) for data sessions established through the core network 130. The policy control element 132 manages a policy 136 (or policy rule) for each UE / subscriber and determines the parameter settings of the session based on the policy 136. For example, the policy control element 132 may determine the quality of service (QoS) settings for a user session, such as bandwidth (e.g., guaranteed bit rate and maximum bit rate), priority, etc., based on the policy 136 specified for the user. Examples of policy control elements 132 are the policy and charging rule function (PCRF) and the policy control function (PCF). The billing system 134 includes means, components, or modules (including hardware) configured to pre-bill users’ sessions. The billing system 134 may include an online billing system (OCS) configured to perform online billing, an offline billing system (OFCS) configured to perform offline billing, a billing function (CHF) in 5G that supports converged online and offline billing, or another type of billing system.

[0037] The communication system 100 further includes a network management system (NMS) 150. The network management system 150 is a system for monitoring, maintaining, and managing the RAN 120 and / or core network 130, and provides network operators with the ability to view and manage the operations of the RAN 120 and / or core network 130. The network management system 150 may include a performance management (PM) subsystem configured to collect performance metrics or measures (i.e., key performance indicators (KPIs)) from the RAN 120 and / or core network 130. The network management system 150 may include a configuration management (CM) subsystem configured to monitor, update, and report network configuration parameters to the RAN 120 and / or core network 130.

[0038] In one embodiment, the communication system 100 may represent a next-generation network (e.g., a 5G network). Figure 2 A non-roaming architecture 200 for a next-generation network is shown in an illustrative embodiment. Figure 2The architecture in this document is a reference point representation, as further described in 3GPP TS23.501 (v16.7.0) (which is incorporated herein by reference as if fully included herein). The control plane of architecture 200 includes Authentication Server Function (AUSF) 210, Unified Data Management Function (UDM) 212, Network Slice Selection Function (NSSF) 213, Access and Mobility Management Function (AMF) 214, Session Management Function (SMF) 216, Policy Control Function (PCF) 218, Application Function (AF) 220, and Charging Function (CHF) 240. The user plane of architecture 200 includes one or more User Plane Functions (UPF) 224 communicating with the Data Network (DN) 140. The (R)Access Network ((R)AN) 120 and the UE 110 are able to access the control plane and user plane of the core network. (R)AN 120 is a communication network in which the last link to the end user equipment (e.g., the UE) is radio.

[0039] AUSF 210 is configured to support authentication for UE 110. UDM 212 is configured to store UE 110's subscription data / information. UDM 212 can store three types of user data: subscription, policy, and session-related context (e.g., UE location). AMF 214 is configured to provide UE-based authentication, authorization, mobility management, etc. SMF 216 is configured to provide the following functions: Session Management (SM), UE Internet Protocol (IP) address allocation and management, UPF 224 selection and control, PCF 218-oriented engagement termination, policy enforcement and QoS control portions, lawful interception, SM portion termination of NAS messages, Downlink Data Notification (DNN), roaming functionality, handling local enforcement to apply Service Level Agreement (SLA) QoS, charging data collection and charging interface, etc. If UE 110 has multiple sessions, a different SMF can be assigned to each session to manage them individually, and different functions can potentially be provided for each session. PCF 218 is configured to support a unified policy framework for managing network behavior and provides policy rules for control plane functions such as QoS enforcement, accounting, access control, and traffic routing. AF 220 provides PCF 218 with information about packet flows. Based on this information, PCF 218 is configured to determine policy rules regarding mobility and session management to enable AMF 214 and SMF 216 to operate correctly. CHF 240 is configured to provide session / service accounting and support converged online and offline accounting.

[0040] UPF 224 supports various user plane operations and functions as part of the service, such as packet routing and forwarding, traffic handling (e.g., QoS enforcement), anchoring for intra / inter-RAT mobility (where applicable), packet inspection and policy rule enforcement, lawful interception (UP collection), traffic settlement and reporting, etc. DN 140 is not part of the core network and provides Internet access, carrier services, third-party services, etc.

[0041] Architecture 200 includes the following reference points: Reference point N1 is implemented between UE 110 and AMF 214. Reference point N2 is implemented between (R)AN 120 and AMF 214. Reference point N3 is implemented between (R)AN 120 and UPF 224. Reference point N4 is implemented between SMF 216 and UPF 224. Reference point N5 is implemented between PCF 218 and AF 220. Reference point N6 is implemented between UPF 224 and DN140. Reference point N7 is implemented between SMF 216 and PCF 218. Reference point N8 is implemented between UDM 212 and AMF 214. Reference point N9 is implemented between the two UPF 224s. Reference point N10 is implemented between UDM 212 and SMF 216. Reference point N11 is implemented between AMF 214 and SMF 216. Reference point N12 is implemented between AMF 214 and AUSF 210. Reference point N13 is implemented between UDM 212 and AUSF 210. Reference point N14 is implemented between the two AMFs. In non-roaming mode, reference point N15 is implemented between PCF 218 and AMF 214. Reference point N22 is implemented between NSSF 213 and AMF 214. Reference point N28 is implemented between CHF 240 and PCF 218, and reference point N40 is implemented between CHF and SMF 216.

[0042] In another embodiment, communication system 100 may represent an LTE network. Figure 3A PCC architecture 300 for an LTE network is illustrated in an illustrative embodiment. The PCC architecture 300 includes a Policy and Charging Rules Function (PCRF) 302 and a Policy and Charging Enforcement Function (PCEF) 304, which together provide a PCC solution. PCRF 302 includes policy control decisions and flow-based charging control functions. Therefore, PCRF 302 is a node or entity in the network that formulates PCC rules for services requested by users; this is referred to herein as making PCC decisions. PCRF 302 may have a policy engine (not shown) that makes PCC decisions based on policies and / or charging rules defined for users. PCEF 304 includes service data flow detection, policy enforcement, and flow-based charging functions. Therefore, PCEF 304 is a node that enforces PCC rules for services requested by end users. For example, PCEF 304 can establish bearer connections for services, modify existing bearer connections, ensure that only authorized service data flows are established, ensure that QoS limits are not exceeded, and so on. PCEF 304 is typically implemented in gateways between user and data networks, such as the Packet Data Network Gateway (P-GW) 306 in an EPC network.

[0043] The PCC architecture 300 further includes OCS 308, OFCS 310, Bearer Binding and Event Reporting Function (BBERF) 312, Application Function (AF) 314, Subscriber Profile Repository (SPR) 316, and Traffic Detection Function (TDF) 318. OCS 308 provides online billing for services / sessions accessed by users. Additionally, OCS 308 stores the online billing rules / plans for end users, which PCRF 302 can use when making PCC decisions. For example, online billing rules can define whether a user is a prepaid subscriber and can define tariffs for different services requested by the user. OCS 308 engages with PCRF 302 via the Sy reference point or another suitable reference point to exchange billing rules / plans with OCS 308, and also engages with P-GW 306 via the Gy reference point or another suitable reference point. OFCS 310 provides offline billing for services / sessions accessed by end users. OFCS 310 is coupled to P-GW 306 via the Gz reference point or another suitable reference point.

[0044] The AF 314 is a component for applications requiring dynamic policy and / or charging control. The AF 314 communicates with the PCRF 302 to deliver dynamic session information for PCC decisions and receives session-specific information and notifications about bearer-level events. For example, the AF 314 can provide the PCRF 302 with the IP address, port number, bit rate, latency sensitivity, etc., for a requested service. The PCRF 302 can then use this information when making a PCC decision. The AF 314 communicates with the PCRF 302 via an Rx reference point or other suitable protocol interface. An example of the AF 314 is the Proxy Call Session Control Function (PCSCF) in an IP Multimedia Subsystem (IMS).

[0045] SPR 316 stores user profiles for end users. These profiles may include policy rules (and possibly billing rules) used by PCRF 302 to make PCC decisions. Policy rules manage which network services an end user is allowed to access, the bandwidth level provided, the permitted service(s) time(s), and the permitted service duration. Policy rules and billing rules are collectively referred to herein as the user's (or subscriber's) service plan (or PCC plan). SPR 316 engages with PCRF 302 via the Diameter Sp interface or any other protocol used to exchange policy rules with PCRF 302.

[0046] TDF 318 is a functional entity that performs application detection and reports the detected applications and their service data flow descriptions to PCRF 302. If a service data flow description cannot be provided to PCRF 302, TDF 318 can also perform gating, redirection, and bandwidth limiting. TDF 318 engages with PCRF 302 via the diameter Sd interface or any other suitable protocol interface to send traffic data (real-time or historical) for PCC determination.

[0047] The network operator of communication system 100 or another telecommunications network may wish to trigger bandwidth / speed throttling in overloaded areas of the RAN to prevent bandwidth from being consumed by heavy users and to allow a larger number of users in these areas to better allocate and use bandwidth. For example, sporting events, concerts, marches, protests, and / or other types of events may overload the available capacity on one or more cells of the RAN. To address this and / or other issues, a bandwidth management system can be implemented in communication system 100. At a high level, the bandwidth management system can degrade the bandwidth allocated to UE 110 when UE 110 is located in an area of ​​RAN 120 that is experiencing overload. One technical advantage of bandwidth throttling is that available network resources in congested or overloaded areas of RAN 120 can be allocated to a larger number of users in an efficient and equitable manner.

[0048] Figure 4 This is a block diagram of a bandwidth management system 400 in an illustrative embodiment. The bandwidth management system 400 includes network nodes, servers, circuitry, logic, hardware, means, etc., configured to control or manage the bandwidth available to or provided to UE 110 served by RAN 120. In this embodiment, the bandwidth management system 400 includes the following subsystems: a network interface component 402, a cell status manager 404, and a bandwidth controller 406. The network interface component 402 is a hardware component that exchanges messages, signaling, or packets with other components, such as RAN 120, network management system 150, core network 130, and / or other systems. For example, the network interface component 402 can receive performance metrics / indicators of cell 124 of RAN 120 from network management system 150, core network 130, or directly from RAN 120. Network interface component 402 can operate using various protocols or reference points, including Sy reference points, Rx reference points, Sp reference points and / or other reference points using the diameter-based protocol, N28 reference points, N40 reference points, N15 reference points, N7 reference points defined for next-generation networks and / or other reference points.

[0049] Cell State Manager 404 includes circuitry, logic, hardware, means, etc., configured to collect, obtain, or otherwise gather cell load information 410 of RAN 120 and determine the cell load state 412 of cell 124 in RAN 120 based on the cell load information 410. Cell load is a measure of the amount of resources used in a cell, such as the availability of resources. Therefore, cell load state 412 is a measure or level of load in cell 124. For example, cell load state 412 may be an integer between "0" and "9" indicating the load level in cell 124, may be a category indicating the load level in cell 124 such as "overloaded," "normal," and "underloaded," or another type of value. Cell State Manager 404 may obtain cell load information 410 from RAN measurements (e.g., counters providing information about cell load, counters estimating potential traffic in cell 124, counters providing the number of connected devices in cell 124, etc.). Cell load information 410 can be obtained through a file-based mechanism (e.g., FTP interface), via an API interface (e.g., RESTful) from RAN 120, from the RAN monitoring system (e.g., network management system 150), or from the AMF, or through other means. Cell status manager 404 can store cell load information 410 and cell load status 412 in a data storage device, database, etc.

[0050] The bandwidth controller 406 includes circuitry, logic, hardware, and mechanisms configured to degrade the bandwidth allocated to UE 110 when UE 110 is located in a congested or overloaded area of ​​RAN 120. The bandwidth controller 406 determines whether the area of ​​RAN 120 is congested or overloaded based on the cell load state 412 of a single cell 124 or multiple cells 124 in the area of ​​RAN 120. The bandwidth controller 406 can degrade the bandwidth allocated to UE 110 by sending bandwidth throttling requests to policy control elements 132 of the core network 130 (e.g., PCF 218, PCRF 302, etc.).

[0051] The bandwidth management system 400 may include Figure 4 Various other components or subsystems are not specifically shown in the document.

[0052] One or more subsystems of the bandwidth management system 400 may be implemented on a hardware platform consisting of analog and / or digital circuit systems. One or more subsystems of the bandwidth management system 400 may be implemented on a processor 430 that executes instructions 434 stored in memory 432. The processor 430 includes integrated hardware circuitry configured to execute instructions 434, and memory 432 is a non-transitory computer-readable storage medium for data, instructions 434, applications, etc., and is accessible by the processor 430. Alternatively, one or more subsystems of the bandwidth management system 400 may be implemented on an edge cloud 440, one or more edge servers 442, or other architectures (e.g., multi-access edge computing (MEC) architecture).

[0053] Figure 5 This is a flowchart illustrating a method 500 for managing bandwidth allocated to UE 110 in an illustrative embodiment. The steps of method 500 will be referred to... Figure 4 The method 500 is described using a bandwidth management system 400, but those skilled in the art will understand that it can be performed in other systems. The steps in the flowcharts described herein do not include all steps and may include other steps not shown, and these steps may be performed in an alternative order.

[0054] Cell Status Manager 404 receives, collects, obtains, or gathers cell load information 410 from multiple cells 124 within RAN 120 (step 502). For example, Cell Status Manager 404 may receive performance metrics / indicators (e.g., from Network Management System 150), traffic reports or logs, or other messages or information for RAN 120 via Network Interface Component 402. Cell load information 410 may indicate the number of active or connected devices in cell 124 (e.g., the number of RRC connections), the uplink (UL) and / or downlink (DL) usage of active or connected devices in cell 124, the utilization rate of physical resource blocks (PRBs) in cell 124, etc. Cell load information 410 may indicate or include IP latency measurements, IP throughput measurements in DL and UL, predetermined IP throughput in DL and UL, etc. Cell load information 410 may be pushed to Cell Status Manager 404 periodically (e.g., every five minutes) or in real time, or Cell Status Manager 404 may request cell load information 410 periodically, in response to events, etc. Then, the cell status manager 404 stores cell load information 410, such as in a database.

[0055] Cell State Manager 404 processes cell load information 410 to determine the cell load state 412 for each of cells 124 (step 504). As described above, cell load state 412 is a measure or level of load in cell 124. In one embodiment, cell State Manager 404 may determine cell load state 412 based on the average number of connected devices (e.g., UEs) in cell 124 and the maximum number of connected devices specified for cell 124. In another embodiment, cell State Manager 404 may determine cell load state 412 based on the average sum of DL usage of connected devices in cell 124 and the maximum sum of DL usage of the maximum number of connected devices in cell 124. In yet another embodiment, cell State Manager 404 may determine cell load state 412 based on the average sum of UL usage of connected devices in cell 124 and the maximum sum of UL usage of the maximum number of connected devices in cell 124. Cell State Manager 404 may use the above-described parameters or combinations of other parameters to determine cell load state 412 of cell 124. Then, the cell state manager 404 can store the cell load state 412 for cell 124, such as in a database. The cell load state 412 can be updated by the cell state manager 404 as needed.

[0056] The bandwidth controller 406 performs bandwidth throttling for the UE 110 attached to or served by the RAN 120 based on the cell load state 412 of cell 124 (step 506). The bandwidth controller 406 may initiate bandwidth throttling for the UE 110 in response to a triggering condition. For example, the bandwidth controller 406 may receive a message about the UE 110 (optional step 520), such as a request for a new session or service, a billing request, etc. However, in other embodiments, bandwidth throttling may be triggered in other ways.

[0057] To perform bandwidth throttling, bandwidth controller 406 determines the location of UE 110 (step 508). For example, bandwidth controller 406 may query a location database (via network interface component 402) to obtain the location information of UE 110, process received messages or signaling about UE 110 to identify the location of UE 110, or obtain the location of UE 110 in another manner. Bandwidth controller 406 identifies the cell load status 412 of one or more cells 124 in the area of ​​RAN 120 corresponding to the location of UE 110 (step 510). Figure 6 A geographic area 600 served by RAN 120 is shown in an illustrative embodiment. This geographic area 600 includes a plurality of base stations 122, and although not shown, each of the base stations 122 forms one or more cells 124. Bandwidth controller 406 can determine an area 610 of RAN 120 corresponding to the location of UE 110. For example, area 610 of interest may correspond to the location of sporting events, concerts, marches, protests, and / or other types of events. In one embodiment, area 610 of interest may include a single cell 124 of RAN 120. For example, Figure 6 The leftmost region 610 shown includes a single cell 124 of RAN 120 (provided by a single base station 122). In another embodiment, the region of interest 610 may include multiple cells 124 of RAN 120, such as the tracking area of ​​UE 110, a campus, a city, etc. For example, Figure 6 The rightmost region 610 shown includes multiple cells 124 of RAN 120 (provided by multiple base stations 122). The bandwidth controller 406 identifies one or more cells among the cells 124 located within the defined region 610 and identifies the cell load state 412 of the one or more cells 124 found within the defined region 610.

[0058] exist Figure 5In this process, the bandwidth controller 406 determines whether area 610 of the RAN 120 corresponding to the location of UE 110 is overloaded based on the cell load state 412 of one or more cells 124 in area 610 (step 512). Area 610 is considered overloaded or in an overloaded state when the load on one or more cells 124 in area 610 exceeds or is about to exceed a threshold. For one example, assume area 610 comprises a single cell 124. The bandwidth controller 406 may identify the cell load state 412 of cell 124 as a load level (e.g., an integer between "1-9"), a classification (e.g., "overloaded", "normal", or "underloaded"), or another value. When the load level of cell 124 exceeds the overload threshold, the classification of cell 124 indicates "overloaded", or cell 124 is otherwise indicated as overloaded, the bandwidth controller 406 may determine that area 610 is overloaded. For another example, assume area 610 comprises multiple cells 124. The bandwidth controller 406 can identify the cell load state 412 of each cell in the cells 124 of region 610. In one embodiment, the bandwidth controller 406 can determine that region 610 is overloaded when any cell in the cells 124 of region 610 has a load level exceeding an overload threshold, is classified as “overloaded,” or is otherwise indicated as overloaded. In another embodiment, the bandwidth controller 406 can determine that region 610 is overloaded when a threshold number or threshold percentage of the cells 124 in region 610 is indicated as overloaded.

[0059] In response to determining that region 610 is overloaded, bandwidth controller 406 controls the degradation of bandwidth allocated to UE 110 in RAN 120 (step 514). Therefore, when in overloaded region 610, the bandwidth allocated to UE 110 is throttled. When region 610 is not overloaded, bandwidth controller 406 may not perform degradation of the bandwidth allocated to UE 110 (step 516).

[0060] The bandwidth controller 406 can control bandwidth degradation in various ways. In one embodiment, the bandwidth controller 406 can generate a bandwidth throttling request that requests a change to the policy 136 of the UE 110 to degrade the bandwidth allocated to the UE 110 (optional step 522), and send the bandwidth throttling request to the policy control element 132 in the core network 130 via the network interface component 402 (optional step 524). For example, the bandwidth controller 406 can send the bandwidth throttling request to the PCF 218 of the next-generation network, to the PCRF 302 of the LTE network, and so on. In response to the bandwidth throttling request, the policy control element 132 can change the policy 136 of the UE 110 or make a policy decision to reduce the bandwidth allocated to the UE 110.

[0061] The bandwidth controller 406 may consider other criteria, which can be configured by the network operator, when determining whether to degrade the bandwidth allocated to UE 110. For example, criteria may include whether the user of UE 110 belongs to a specific user profile, whether the service requested by the user belongs to a specific category (based on rating groups and / or service identifiers), whether UE 110 has been allocated a specific network segment, whether the user's data usage has reached a defined threshold, and so on. Any combination of the above criteria or other criteria may be considered by the bandwidth controller 406 when determining whether to degrade the bandwidth allocated to UE 110 when area 610 is considered overloaded.

[0062] In one embodiment, the bandwidth management system 400 can be implemented in the billing system 134 of the communication system 100. Therefore, bandwidth throttling of the UE 110 can be provided through the billing system 134. Figure 7 This is a block diagram of a billing system 134 including a bandwidth management system 400 in an illustrative embodiment. In this embodiment, the billing system 134 may include a 5G CHF 240, an OCS 308, and / or an OFCS 310, such as Figure 7 As shown. However, other types of billing systems are also considered in this article.

[0063] OCS 308 is configured to perform online billing and may include or provide the following subsystems: Online Billing Function (OCF) 710, Account Balance Management Function (ABMF) 712, and Rating Function (RF) 714. OCF 710 includes circuitry, logic, hardware, means, etc., configured to control session-based and event-based billing (e.g., Session-Based Billing Function (SBCF) and Event-Based Billing Function (EBCF)). ABMF 712 includes circuitry, logic, hardware, means, etc., configured to store subscriber account balances. RF 714 includes circuitry, logic, hardware, means, etc., configured to determine, on behalf of OCF 710, a value of resource usage (described in the billing events received by OCF 710) based on rates defined by the network operator. OCF 710 provides information obtained from the billing events to RF 714 and receives rating outputs (in monetary or non-monetary units) as a return. RF 714 can handle data volume ratings, session / connection time ratings, service event ratings, etc. OCS 308 may include... Figure 7 Various other components or subsystems not specifically shown in the text.

[0064] In general, online billing is a billing mechanism where billing information can affect the services provided in real time, thus requiring direct interaction between the billing mechanism and session / service control. The Charging Trigger Function (CTF) in a network element sends an “initial” billing event for the service to the OCS 308. The OCS 308 can then authorize the start of the service after successfully enforcing credit control on the user’s account. The OCS 308 retains credit from the user’s account and returns a quota (e.g., a unit specifying the allowed number of minutes or bytes) to the CTF. The CTF uses the granted quota to monitor resource consumption of the service within the network element. When the quota is exhausted, the CTF either issues another “temporary” billing event requesting further allocation of units or terminates the service. If the service is terminated at some point, the CTF reports the consumed units to the OCS 308 and issues a “final” billing event, which typically results in a balance adjustment. Credit control for the service is then terminated, and the OCS 308 returns the value of any unused quota to the user’s account.

[0065] OFCS 310 is configured to perform offline billing and may include or provide the following subsystems: Billing Data Function (CDF) 720 and Billing Gateway Function (CGF) 722. CDF 720 includes circuitry, logic, hardware, means, etc., configured to receive billing events from the CTF, format the billing events into Billing Data Records (CDRs), and send the CDRs to CGF 722. CGF 722 includes circuitry, logic, hardware, means, etc., configured to associate session CDRs and forward CDR files with associated CDRs to the billing domain for subscriber billing and / or inter-operator settlement. OFCS 310 may include... Figure 7 Various other components or subsystems are not specifically shown in the document.

[0066] In general terms, offline billing is a process in which billing information for network resource usage is collected simultaneously with the resource usage itself. Offline billing can be of two types: session-based or event-based. In event-based billing, the CTF (Consumer Transaction Function) of a network element reports usage or service provided, where the service is provided in a single operation. For example, the CTF might report usage in a Diameter Settlement Request (ACR) event. Session-based billing is the process of reporting service usage and billing data using start, interim, and stop events. During service, the CTF may send multiple ACR intervals depending on the progress of the session. Billing information is then passed through a logical billing function, enabling the generation of a CDR (Consumer Transaction Record) or another type of billing record. The CDR is passed to the network operator's billing domain for user billing and / or inter-operator settlement.

[0067] The CHF 240 is configured to support converged online and offline billing. Therefore, the CHF 240 combines the functionality of OCF (Online Billing Function) and CDF (Cost Data Function).

[0068] Figure 8 This is a flowchart illustrating a method 800 for managing bandwidth allocated to UE 110, performed in a charging system according to an illustrative embodiment. Method 800 includes steps similar to those of method 500 described above, and these steps will use the same reference numerals. In this embodiment, the cell state manager 404 of the bandwidth management system 400 collects cell load information 410 (step 502) of multiple cells 124 within RAN 120 and processes the cell load information 410 to determine the cell load state 412 of each of the cells 124 (step 504). The bandwidth controller 406 of the bandwidth management system 400 performs bandwidth throttling for UE 110 attached to or served by RAN 120 based on the cell load state 412 of the cells 124 (step 506). In this embodiment, bandwidth throttling is triggered upon receiving a charging request 750 from UE 110 (step 802). Billing request 750 can be an “initial” billing request for a new data session of UE 110, a “temporary” billing request for a continuing data session of UE 110, and so on. For example, when a data session begins, 4G P-GW 306 sends a Diameter Credit Control Request [Initial] (Gy CCR-i) to OCS 308, 5G SMF 216 sends a Data Billing Request [Initial] to CHF 240, and so on.

[0069] In response to receiving a charging request 750, the bandwidth controller 406 determines the location of UE 110 (step 508). In one embodiment, the bandwidth controller 406 can obtain the location of UE 110 from the charging request. The charging request contains user location information that allows determination of the Tracking Area Code (CCR) and cell identity. For example, the CCR includes attribute value pairs (AVPs) (i.e., 3GPP user location information) that indicate the origin area where UE 110 is initiating a data session. This AVP allows indication of geographic location, with granularity down to cell identity. For example, the 3GPP user location information AVP includes:

[0070] • Mobile Area Code (MCC)

[0071] • Mobile Country Code (MNC)

[0072] • Tracking Area Code (TAC)

[0073] • E-UTRAN Cell Identifier (ECI)

[0074] In another example, the "User Location Information" field is defined in 5G under "PDU Session Billing Information" sent between SMF 216 and CHF 240 via the Billing Interface (Nchf) interface (N40). This User Location Information includes at least one parameter (e.g., eutraLocation, nrLocation, n3gaLocation) indicating the Tracking Area Identity (TAI) and Cell Identity (ECGI) of the UE 110, as well as the global identity of the eNodeB (globalENbI) or gNodeB (globalNgenbId) where the UE 110 is currently located.

[0075] Then, the bandwidth controller 406 determines the cell load state 412 of one or more cells 124 in area 610 of RAN 120 corresponding to the location of UE 110 (step 510). Based on the cell load state 412 of one or more cells 124 in area 610, the bandwidth controller 406 determines whether area 610 corresponding to the location of UE 110 is overloaded (step 512). When area 610 is determined to be overloaded, the bandwidth controller 406 controls the degradation of the bandwidth allocated to UE 110 in RAN 120 (step 514). For example, the bandwidth controller 406 generates a bandwidth throttling request 752 to degrade the bandwidth allocated to UE 110 (optional step 522) and sends the bandwidth throttling request 752 to policy control element 132 (optional step 524). For example, the bandwidth controller 406 may send the bandwidth throttling request 752 to PCF 218 of the next-generation network via reference point N28. Figures 9 to 10 This is a message diagram illustrating the interaction between CHF 240 and PCF 218 in an illustrative embodiment. Figure 9 In this configuration, CHF240 is configured to notify PCF 218 when a policy counter state changes. Therefore, when bandwidth controller 406 determines that region 610 is overloaded, it sets the policy counter defined for location-load-state to "overloaded" and sends a bandwidth throttling request 752 to PCF 218 via reference point N28 in the form of an Nchf_SpendingLimitControl_Notify request. PCF 218 responds with an Nchf_SpendingLimitControl_Notify response. Figure 10In this context, PCF 218 subscribes to the policy counter from CHF 240. Therefore, PCF 218 sends a subscription request to CHF 240 via reference point N28 in the form of an Nchf_SpendingLimitControl_Subscribe request. When bandwidth controller 406 determines that region 610 is overloaded, it sets the policy counter defined for location-load-status to "overloaded" and sends a bandwidth throttling request 752 to PCF 218 via reference point N28 in the form of an Nchf_SpendingLimitControl_Subscribe response.

[0076] In another example, bandwidth controller 406 may send bandwidth throttling request 752 as a diameter CCR or credit control response (CCA) to PCRF 302 of the LTE network via the Sy reference point. In another example, bandwidth controller 406 may send bandwidth throttling request 752 as a diameter ACR or settlement response (ACA) to PCRF 302 of the LTE network via the Gz reference point. In response to bandwidth throttling request 752, policy control element 132 may change policy 136 or make a policy decision for UE 110, causing the bandwidth allocated to UE 110 in RAN 120 to be degraded.

[0077] When area 610 is not overloaded, bandwidth controller 406 may not degrade the bandwidth allocated to UE 110 (step 516). Furthermore, bandwidth controller 406 may determine whether area 610 is underloaded. For example, bandwidth controller 406 may identify the cell load state 412 of cell 124 as a load level (e.g., an integer between "1-9"), a classification (e.g., "overloaded", "normal", or "underloaded"), or another value. When the load level of cell 124 is below an overload threshold or below an underload threshold, and the classification of cell 124 indicates "underloaded," or cell 124 is otherwise indicated as underloaded, bandwidth controller 406 may determine that area 610 is underloaded. When area 610 is deemed underloaded, bandwidth controller 406 may trigger a tariff discount for UE 110 (step 804). Therefore, UE 110 may experience lower tariffs as a benefit of being in underloaded area 610 located in RAN 120.

[0078] Despite the bandwidth management system 400 Figure 7While shown as part of the billing system 134, the bandwidth management system 400 can be implemented in other elements of the communication system 100. For example, the bandwidth management system 400 can be implemented in another element of the AMF 214, SMF216, or next-generation network. The bandwidth management system 400 can also be implemented in another element of the P-GW 306, PCEF 304, or LTE network. The bandwidth management system 400 can also be a standalone service queried by the billing system 134, policy control element 132, or another network element.

[0079] Any of the various elements or modules shown in the figures or described herein can be implemented as hardware, software, firmware, or a combination thereof. For example, an element can be implemented as dedicated hardware. A dedicated hardware element can be referred to as a “processor,” a “controller,” or some similar term. When provided by a processor, functionality can be provided by a single dedicated processor, a single shared processor, or multiple separate processors, some of which may be shared. Furthermore, the explicit use of the terms “processor” or “controller” should not be construed as referring only to hardware capable of executing software, and may implicitly include, but is not limited to, digital signal processor (DSP) hardware, network processors, application-specific integrated circuits (ASICs) or other circuit systems, field-programmable gate arrays (FPGAs), read-only memory (ROM) for storing software, random access memory (RAM), non-volatile storage devices, logic, or some other physical hardware components or modules.

[0080] Furthermore, an element can be implemented as instructions executable by a processor or computer to perform the element's function. Some examples of instructions are software, program code, and firmware. When executed by a processor, instructions can operate to instruct the processor to perform the element's function. Instructions can be stored on a processor-readable storage device. Some examples of storage devices are digital or solid-state memory, magnetic storage media such as disks and tapes, hard disk drives, or optically readable digital data storage media.

[0081] As used in this application, the term "circuit system" may refer to one or more, or all of the following:

[0082] (a) Hardware-only circuit implementations (such as implementations only in analog and / or digital circuit systems);

[0083] (b) A combination of hardware circuitry and software, such as (if applicable):

[0084] (i) A combination of (multiple) analog and / or digital hardware circuits with software / firmware; and

[0085] (ii) Any part of a hardware processor(s) having software (including multiple digital signal processors(s)), software, and memory(s) that works together to enable a device such as a mobile phone or server to perform various functions; and

[0086] (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (such as firmware) to operate, but the software may not exist when it is not required for operation.

[0087] The definition of "circuit system" applies to all uses of the term in this application, including in any claim. As a further example, as used in this application, the term "circuit system" also covers implementations of hardware circuitry or processors (or processors) or hardware circuitry or processors and their accompanying software and / or firmware. For example, and if applicable to a particular claim element, the term "circuit system" also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0088] Although specific embodiments have been described herein, the scope of this disclosure is not limited to those specific embodiments. The scope of this disclosure is defined by the appended claims and any of their equivalents.

Claims

1. A bandwidth management system, comprising: At least one processor and memory; The at least one processor enables the bandwidth management system to: Collect cell load information from multiple cells within the Radio Access Network (RAN); The cell load information is processed to determine the cell load status for each cell in the cells; as well as Bandwidth throttling can be performed in the following ways: Receive messages about the user equipment (UE) of the RAN user; Determine the location of the UE; Identify the region of interest corresponding to the location of the UE, the region of interest including multiple cells of the RAN; Identify the cell load status of each cell in the region of interest; Based on the cell load status of the cells in the region of interest, the RAN is determined to be overloaded when a threshold number of cells in the region of interest are overloaded; as well as When the region is overloaded, the bandwidth allocated to the UE is degraded.

2. The bandwidth management system according to claim 1, wherein the at least one processor causes the bandwidth management system to: Generate a bandwidth throttling request, the bandwidth throttling request being used to request a change in the policy for the UE to degrade the bandwidth allocated to the UE; and The bandwidth throttling request is sent to the policy control element.

3. The bandwidth management system according to claim 1, wherein: The bandwidth management system is implemented in the billing system, which is configured to perform billing for sessions of users of the RAN; as well as The at least one processor enables the bandwidth management system to: In response to receiving a billing request for the UE, the bandwidth throttling for the UE is performed.

4. The bandwidth management system of claim 3, wherein the at least one processor enables the bandwidth management system to: In response to receiving an initial billing request for a new data session for the UE, the bandwidth throttling for the UE is performed.

5. The bandwidth management system of claim 3, wherein the at least one processor causes the bandwidth management system to: In response to receiving a temporary billing request for an ongoing data session of the UE, the bandwidth throttling for the UE is performed.

6. The bandwidth management system of claim 3, wherein the at least one processor causes the bandwidth management system to: When the region is underloaded, a tariff discount is triggered for the UE.

7. The bandwidth management system according to claim 3, wherein: The billing system includes the 5G billing function CHF for 5G networks.

8. The bandwidth management system according to claim 3, wherein: The billing system includes the Online Billing System (OCS) for the Long Term Evolution (LTE) network.

9. The bandwidth management system according to claim 3, wherein: The billing system includes the Offline Billing System (OFCS) for LTE networks.

10. A method for managing bandwidth within a Radio Access Network (RAN), the method comprising: Collect cell load information from multiple cells within the RAN; The cell load information is processed to determine the cell load status for each cell in the cells; as well as Bandwidth throttling can be performed in the following ways: Receive messages about the user equipment (UE) of the RAN user; Determine the location of the UE; Identify the region of interest corresponding to the location of the UE, the region of interest including multiple cells of the RAN; Identify the cell load status of each cell in the cells within the region of interest; Based on the cell load status of the cells in the region of interest, the RAN is determined to be overloaded when a threshold number of cells in the region of interest are overloaded; as well as When the region is overloaded, the bandwidth allocated to the UE is degraded.

11. The method of claim 10, wherein controlling the degradation of bandwidth allocated to the UE comprises: Generate a bandwidth throttling request, the bandwidth throttling request being used to request a change in the policy for the UE so that the bandwidth allocated to the UE is degraded; as well as The bandwidth throttling request is sent to the policy control element.

12. The method according to claim 10, wherein: The bandwidth throttling is performed at the bandwidth management system, which is implemented in the billing system, which is configured to perform billing for sessions of users of the RAN. as well as Performing the bandwidth throttling includes: in response to receiving a billing request for the UE, performing the bandwidth throttling for the UE.

13. The method according to claim 12, wherein: Performing the bandwidth throttling includes: in response to receiving an initial billing request for a new data session for the UE, performing the bandwidth throttling for the UE.

14. The method according to claim 12, wherein: Performing the bandwidth throttling includes: in response to receiving a temporary billing request for an ongoing data session for the UE, performing the bandwidth throttling for the UE.

15. The method of claim 12, further comprising: When the region is underloaded, a tariff discount is triggered for the UE.

Images