Dynamic bandwidth capacity control for enterprises

Abstract

Embodiments of the present disclosure relate to dynamic bandwidth capacity control for an enterprise. Systems and methods provide burdenable private bandwidth reservation and control solutions for enterprises, which may be implemented using 5G and 4G core devices. That is, an enterprise can purchase / sign a predetermined amount of bandwidth (e.g., 1Gbps) that a communication service provider (CSP) will reserve for connected client devices of the enterprise that meet a set of criteria (i.e., dynamic bandwidth capacity control (DBCC) group criteria) defined by the enterprise / CSP. Client devices that meet the DBCC group criteria may be "bound" to the DBCC group session. If the bound client device no longer satisfies the DBCC group criteria, the client device may unbind from the DBCC group session. When a client device binds to and unbinds from a DBCC group session, an example may dynamically modify an aggregated bandwidth capacity control policy defining a bandwidth allocation for the client device bound to the DBCC group session.

Description

Background Art

[0001] Best-effort delivery is a conventional network configuration protocol for the consumer market. In the case of best-effort delivery, the Communication Service Provider (CSP) does not guarantee the quality of service or bandwidth for users. Generally speaking, a network using best-effort delivery will serve users in the order in which they request bandwidth. Accordingly, the network performance (e.g., network delay, packet loss, latency, etc.) experienced by users may vary based on factors such as network traffic load, network equipment capacity, etc.

[0002] The concept of network slicing introduced by the 5G standard provides enterprises with an alternative solution to best-effort delivery. Network slicing can refer to the creation and operation of multiple virtual networks (i.e., network slices) on a common physical network. For example, 5G devices / infrastructure can be "divided" into network slices (e.g., 5% of a specific antenna capacity can be allocated to a specific network slice, 5% of the connection connecting the antenna to the core 5G infrastructure can be allocated to the network slice, 5% of the core 5G devices associated with the connection can be allocated to the network slice, etc.).

[0003] Network slices within a 5G network can be dedicated to specific use cases and / or customers (e.g., enterprises). For example, an enterprise can pay / contract with a CSP to obtain a "slice" of a 5G network dedicated to the enterprise. A network slice can include an end-to-end network customized to meet the specialized requirements requested by the enterprise. For this reason, network slicing is sometimes considered a private (or quasi-private) 5G network solution for an enterprise. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] According to one or more various examples, the present disclosure is described in detail with reference to the following figures. The figures are provided for illustration purposes only and are examples only.

[0005] Figure 1 An example network deployment is shown that may be implemented for an enterprise according to various examples of the presently disclosed technology.

[0006] Figure 2 An example policy control function (PCF) system is shown that may be used to implement dynamic bandwidth capacity control (DBCC) according to various examples of the presently disclosed technology.

[0007] Figure 3 An example state transition representation for a DBCC group session according to various examples of the presently disclosed technology is shown.

[0008] Figure 4Example computing components that may be used to implement DBCC according to various examples of the presently disclosed technology are shown.

[0009] Figure 5 Another example computing component that may be used to implement DBCC according to various examples of the presently disclosed technology is shown.

[0010] Figure 6 Depicted is a block diagram of an example computer system in which various examples described herein may be implemented.

[0011] The drawings are not exhaustive and do not limit the disclosure to the precise forms disclosed. DETAILED DESCRIPTION

[0012] As mentioned above, network slicing provides enterprises with an alternative solution to best-effort delivery. For example, an enterprise can pay / contract with a CSP to obtain a "slice" of a 5G network dedicated to the enterprise. A network slice can include an end-to-end network customized to meet the specialized requirements requested by the enterprise. For this reason, network slicing is sometimes considered a private (or quasi-private) 5G network solution for an enterprise.

[0013] While network slicing may be an attractive new solution for some large enterprises, it may be cost-prohibitive for many small and medium-sized businesses. This is in part because the equipment and other resources required to build out 5G networks may be expensive. Relatedly, the resources required to operate and maintain network slices may be substantial. Accordingly, network slicing solutions generally only make economic sense for large enterprises that can make such large equipment and resource investments and benefit from them. More traditional private networks (i.e., independent networks that include devices that are completely dedicated to a specific user / enterprise) require similar investments and are therefore often not an appropriate solution for small and medium-sized enterprises.

[0014] Implementing network slicing is also challenging from a CSP perspective. For example, many CSPs continue to operate 4G networks and 4G+5G hybrid networks (sometimes referred to as "non-standalone 5G networks") that utilize 4G core equipment. Generally speaking, 4G core equipment does not support network slicing. Accordingly, many CSPs can only use a subset of their core equipment to implement network slicing, which may limit the availability and performance of network slicing solutions.

[0015] For at least the reasons stated above, there is a need for alternative solutions to network slicing and traditional private networks that: (a) are more affordable and easier to implement for small and medium-sized enterprises; and (b) can be implemented using traditional 4G core equipment currently utilized by many CSPs.

[0016] In this context, examples of the currently disclosed technology provide enterprises with an affordable private bandwidth reservation and control solution that can be implemented using 5G and 4G core equipment. That is, an enterprise can purchase / sign a predetermined amount of bandwidth (e.g., 1 Gbps), and the CSP will reserve the predetermined amount of bandwidth for the enterprise's connected client devices that meet the set of standards defined by the enterprise / CSP. Such standards can be referred to as dynamic bandwidth capacity control (DBCC) group standards. Examples of DBCC group standards may include: (1) the client device is connected to the network; (2) the connected client device is a registered client device of the enterprise; (3) the connected client device is connected between 7:00 am and 6:00 pm; and 4) the connected client device is within a defined geographic area (e.g., the location of the enterprise). Accordingly, client devices that meet the DBCC group standards can be "bound" to a DBCC group session. If the bound client device no longer meets the DBCC group standards (e.g., the client device is disconnected from the network, or the client device leaves the location of the enterprise), the client device can be unbound from the DBCC group session.

[0017] When client devices are bound to and unbound from a DBCC group session, the example can dynamically modify an aggregate bandwidth capacity control policy that defines bandwidth allocations for client devices bound to the DBCC group session. For example, if a client device is unbound from a DBCC group session, the example can modify the aggregate bandwidth capacity control policy so that the remaining bound client devices are allocated a larger share of the predetermined amount of bandwidth (e.g., 1 Gbps) reserved for client devices bound to the DBCC group session. Conversely, if a new client device is bound to the DBCC group session, the example can modify the aggregate bandwidth capacity control policy so that the bound client devices are allocated a reduced share of the predetermined amount of bandwidth (e.g., 1 Gbps) reserved for client devices bound to the DBCC group session.

[0018] An example of the presently disclosed technology may be implemented by a Policy Control Function (PCF) system of a CSP (as used herein, a PCF system may refer to a system and / or network function that manages access to network resources, governs network behavior, and / or implements dynamic control of network quality of service). The PCF system may: (1) receive a request from a client device to initiate a network session; (2) in response to determining that the requested network session matches a dynamic bandwidth capacity control (DBCC) group criterion, bind the client device to a DBCC group session; (3) in response to binding the client device to the DBCC group session, modify an aggregate bandwidth capacity control policy that defines bandwidth allocation for client devices bound to the DBCC group session, wherein the aggregate bandwidth capacity control policy includes a predetermined total amount of bandwidth reserved for client devices bound to the DBCC group session; and (4) based on the modified aggregate bandwidth capacity control policy, send an instruction to reduce bandwidth allocation for at least one other client device that was bound to the DBCC group session before the client device. In various examples, in response to the client device being unbound from the DBCC group session, the PCF system may: (1) re-modify the aggregate bandwidth capacity control policy; and (2) send instructions to increase bandwidth allocation for at least one other client device still bound to the DBCC group session according to the re-modified aggregate bandwidth capacity control policy. As described above, the DBCC group criteria may be enterprise-specific (e.g., a small or medium-sized enterprise). In these examples, the DBCC group criteria may include at least one of the following criteria: (a) the client device is connected to a network associated with the network session; (b) the client device is connected to the network within a specified time interval (e.g., between 7:00 a.m. and 6:00 p.m.); (c) the client device is connected to the network in a specified geographic area (e.g., the location of the enterprise); and (d) the client device is a registered client device of the enterprise. In various examples, the request for the client device to initiate a network session may be received from a network function (e.g., a 5G SMF network function or a 4G PCEF network function). Similarly, instructions to reduce bandwidth allocation for at least one other client device that was previously bound to the DBCC group session by the client device may be sent to the network function. As mentioned above, the network functions may be associated with 4G or 5G network infrastructure.

[0019] As described above, examples of currently disclosed technology provide an affordable alternative to network slicing. This is in part because examples of currently disclosed technology do not involve "slicing" (i.e., dividing / devoting) a certain percentage of the core 5G infrastructure to a private enterprise. Instead, a certain amount of bandwidth is reserved / guaranteed for the enterprise's connected client devices that meet a set of standards defined by the enterprise / operator (i.e., DBCC group standards). This is a subtle but important distinction. In addition, unlike network slicing, which can only be implemented on standalone 5G core devices / networks, examples of currently disclosed technology can be implemented with 4G core devices / networks and non-standalone 5G core devices / networks (i.e., 4G+5G hybrid networks). Accordingly, examples of currently disclosed technology can more efficiently (and cheaper) use existing core equipment / infrastructure currently operated by many CSPs.

[0020] Examples of the presently disclosed technology will now be described in more detail with reference to the following drawings.

[0021] First, it may be useful to describe a network or system in which the above-described dynamic bandwidth capacity control method may be implemented. Figure 1 An example network deployment 100 is shown that may be implemented for an enterprise, such as a business, educational institution, government entity, medical facility, or other organization. The diagram shows an example of a configuration implemented for an enterprise having multiple users (or at least multiple client devices 110) at a geographic site 102.

[0022] The geographic site 102 may include a main network, which may be, for example, an office network, a home network, or other network device. The geographic site 102 network may be a private network, such as a network that may include security and access control to restrict access to authorized users of the private network. For example, authorized users may include corporate employees, residential residents, corporate customers, etc. at the geographic site 102. In the example shown, the geographic site 102 includes a controller 104 that communicates with the network 120. As shown, in various examples, the controller 104 may communicate with a network function 120a associated with the network 120. The controller 104 may provide the geographic site 102 with communication with the network 120, although it may not be the only point at which the geographic site 102 communicates with the network 120. Although the geographic site 102 may include multiple controllers and / or multiple communication point networks 120, a single controller 104 is shown. In some examples, the controller 104 communicates with the network 120 through a router (not shown). In other examples, the controller 104 provides router functionality to devices in the geographic site 102.

[0023] The controller 104 may be operable to configure and manage network devices, such as at a geographic site 102. The controller 104 may be operable to configure and / or manage switches, routers, access points, and / or client devices connected to the network. The controller 104 itself may be an access point or provide the functionality of an access point.

[0024] The controller 104 can communicate with one or more switches 108 and / or wireless access points (APs) 106a-106c. The switches 108 and wireless APs 106a-106c provide network connections to various client devices 110a-110j. Using the connections to the switches 108 or APs 106a-106c, client devices in the client devices 110a-110j can access network resources, including other devices on the geographic site 102 and the network 120.

[0025] Examples of client devices may include: desktop computers, laptop computers, servers, network servers, authentication servers, authentication-authorization-accounting (AAA) servers, Domain Name System (DNS) servers, Dynamic Host Configuration Protocol (DHCP) servers, Internet Protocol (IP) servers, Virtual Private Network (VPN) servers, network policy servers, mainframes, tablet computers, e-readers, netbook computers, televisions and similar monitors (e.g., smart TVs), content receivers, set-top boxes, personal digital assistants (PDAs), mobile phones, smart phones, smart terminals, dumb terminals, virtual terminals, electronic game consoles, virtual assistants, Internet of Things (IOT) devices, etc.

[0026] Within the geographic site 102, a switch 108 is included as an example of an access point to a network established for wired client devices 110i-110j within the geographic site 102. The client devices 110i-110j can connect to the switch 108 and, through the switch 108, be able to access other devices within the network deployment 100. The client devices 110i-110j can also access the network 120 through the switch 108. The client devices 110i-110j can communicate with the switch 108 through a wired 112 connection. In the example shown, the switch 108 communicates with the controller 104 through the wired 112 connection, although the connection can also be wireless.

[0027] Wireless APs 106a-106c are included as another example of access points for a network established for client devices 110a-110h in geographic site 102. Each of APs 106a-106c may be a combination of hardware, software, and / or firmware configured to provide wireless network connectivity to wireless client devices 110a-110h. In the example shown, APs 106a-106c may be managed and configured by controller 104. APs 106a-106c communicate with controller 104 and the network via connection 112, which may be a wired or wireless interface.

[0028] AP generally refers to a networking device that allows wireless client devices to connect to a wireless network. The AP may include a processor, a memory, and an I / O interface, the I / O interface including a wired network interface (such as an IEEE 802.3 Ethernet interface) and a wireless network interface (such as an IEEE 802.11 Wi-Fi interface), although the examples of the present disclosure are not limited to these interfaces. The AP may include a memory, the memory including a hierarchy of read-write memory (i.e., volatile memory) and permanent memory (i.e., non-volatile memory) such as ROM, EPROM, and flash memory. In addition, as used herein, AP may refer to a receiving point for any convenient wireless access technology that is known or may become known in the future. Specifically, the term AP is not intended to be limited to APs based on IEEE 802.11.

[0029] The network 120 may be a public or private network, such as the Internet, or other communication network to allow connection to the geographic site 102 and access to the servers 160a-160b. The network 120 may be implemented using the core equipment of the CSP, such as telecommunication lines (e.g., telephone lines, coaxial cables, fiber optic cables, satellite communications, cellular communications, etc.), intermediate network equipment (e.g., switches, routers, gateways, servers, and / or controllers), etc. As described above, the core equipment used to implement the network 120 may include any combination of 4G and 5G core equipment.

[0030] As shown, the network 120 may include / implement a network function 120a. As used herein, a network function may refer to a functional building block within a network infrastructure. In other words, the core infrastructure of the network may be decomposed into multiple microservices called network functions. Examples of network functions for 5G networks include a core access and mobility management function (AMF) and a session management function (SMF) that can communicate with a unified data manager (UDM). Examples of 4G network functions may include a policy and charging enforcement function (PCEF), a policy and charging rules function (PCRF), and the like. Accordingly, the network function 120a may include various types of 5G and / or 4G network functions. As described above, these network functions may be coupled to the CSP's policy control function (PCF) system (see, e.g., Figure 2 The network function 120a may communicate with the PCF system 210 of the CSP to implement dynamic bandwidth capacity control according to examples of the presently disclosed technology. For example, the network function 120a may send a request for a client device to initiate a network session on the network 120 to the PCF system of the CSP. The network function 120a may also receive instructions from the PCF system of the CSP to modify the bandwidth allocation for client devices bound to the DBCC group session in response to other client devices binding to or unbinding from the DBCC group session. The network function 120a may then relay these instructions to the client devices via the above-mentioned paths / mechanisms. Accordingly, the client devices may modify their policy settings / configurations based on the bandwidth allocation modification instructions.

[0031] Figure 2 An example policy control function (PCF) system 210 that can be used to implement dynamic bandwidth capacity control according to various examples of the disclosed technology is shown. As shown, the PCF system 210 can be implemented by a network 200. The network 200 can be a 4G network, a 4G+5G hybrid network (sometimes referred to as a non-standalone 5G network), a 5G network, etc. In various examples, the network 200 can be combined with Figure 1 The networks 120 described are the same / similar.

[0032] As described above, examples of the currently disclosed technology provide enterprises with affordable private bandwidth reservation and control solutions that can be implemented using 4G and 5G core devices (e.g., 4G and / or 5G core devices used to implement network 200). That is, an enterprise (e.g., enterprise 250) can purchase / sign a predetermined amount of bandwidth (e.g., 1 Gbps), and the CSP will reserve the predetermined amount of bandwidth for the enterprise's connected client devices that meet the set of standards defined by the enterprise / CSP (e.g., DBCC group standards 212). Such standards may be referred to as dynamic bandwidth capacity control (DBCC) group standards. Accordingly, client devices that meet the DBCC group standards can be "bound" to a DBCC group session (e.g., DBCC group session 214). If the bound client device no longer meets the DBCC group standards (e.g., the client device is disconnected from network 200, or the client device leaves the location of enterprise 250), the client device can be unbound from the DBCC group session. As client devices are bound to and unbound from a DBCC group session, an example (e.g., DBCC group controller 216) may dynamically modify an aggregate bandwidth capacity control policy that defines bandwidth allocations for client devices bound to the DBCC group session. For example, if a client device is unbound from a DBCC group session, the example may modify the aggregate bandwidth capacity control policy such that the remaining bound client devices are allocated a larger share of a predetermined amount of bandwidth (e.g., 1 Gbps) reserved for client devices bound to the DBCC group session. Conversely, if a new client device is bound to the DBCC group session, the example may modify the aggregate bandwidth capacity control policy such that the bound client devices are allocated a reduced share of a predetermined amount of bandwidth (e.g., 1 Gbps) reserved for client devices bound to the DBCC group session.

[0033] As described above, examples of the presently disclosed technology may be implemented by a CSP's PCF system. As used herein, a PCF system may refer to a system and / or network function that manages access to network resources, governs network behavior, and / or implements dynamic control of network service quality. For example, the PCF system 210 may be a dual-mode network function that provides policy control for a 4G network, a 4G+5G hybrid network (sometimes referred to as a non-independent 5G network), a 5G network, and the like. Accordingly, the PCF system 210 may support dynamic management of network policies (including bandwidth allocation policies), security policies, service policies, and the like. In other words, the PCF system 210 may act as a centralized policy decision point to govern business and manage user experience between different CSP services and enterprises.

[0034] As shown, PCF 210 may include a DBCC group controller 216 that dynamically modifies an aggregate bandwidth capacity control policy that defines bandwidth allocation for client devices bound to DBCC group sessions 214. As described above, client devices bound to DBCC group sessions 214 may be client devices that meet DBCC group criteria 212—DBCC group criteria 212 may be stored by PCF system 210. DBCC group criteria 212 may be enterprise specific. For example, DBCC group criteria 212 may be enterprise 250 specific and may be defined by enterprise 250 and / or CSP that provision network 200. Examples of criteria for DBCC group criteria 212 may include any one or a combination of the following: (1) connected to network 200; (2) connected to network 200 within a specified time interval; (3) connected to network 200 within a specified geographic area (e.g., the location of enterprise 250); and (4) being a registered client device of enterprise 250. In some examples, the DBCC group criteria 212 may also include rules / criteria used by the DBCC group controller 216 to determine an aggregate bandwidth capacity control policy that defines bandwidth allocation for client devices bound to the DBCC group session 214. For example, the DBCC group criteria 212 may include a maximum bandwidth for each client device (e.g., 0.1 Gbps). As another example, the DBCC group criteria 212 may provide that certain client devices bound to the DBCC group session 214 (e.g., client devices that are critical to the operation of the enterprise 250) should be allocated a larger share of the predetermined amount of bandwidth (e.g., 1 Gbps) reserved for the enterprise 250 than other client devices bound to the DBCC group session 214. In some examples, the DBCC group criteria 212 may provide that the unallocated portion of the predetermined amount of bandwidth reserved for the enterprise 250 may be allocated to client devices external to the enterprise 250 when the client devices of the enterprise 250 do not need the unallocated portion of the bandwidth. For example, if 1 Gbps of bandwidth is reserved for enterprise 250, but (1) DBCC group standards 212 dictates that the maximum bandwidth per client device is 0.1 Gbps, and (2) there are only 56 client devices bound to DBCC group session 214 at a given time - DBCC group standards 212 may dictate that up to 0.24 Gbps of bandwidth can be made available to client devices not associated with enterprise 250 and / or DBCC group session 214. Here, 0.2 Gbps (i.e., 1-(0.56+0.24)) may still remain reserved for enterprise 250 to accommodate the burst of new client devices bound to DBCC group session 214.

[0035] In various examples, each client device bound to a DBCC group session 214 may have its own associated network session that connects the client device to the network 200. These network sessions may be independent of the DBCC group session 214. The DBCC group session 214 may be a group-level logical session that the DBCC group controller 216 uses to determine an aggregate bandwidth capacity control policy that defines bandwidth allocation for client devices (logically) bound to the DBCC group session 214. Network sessions that connect client devices to the network 200 that meet / match the DBCC group criteria 212 may be logically bound to the DBCC group session 214. Conversely, network sessions that connect client devices to the network 200 that do not meet / match the DBCC group criteria 212 may not be logically bound to the DBCC group session 214. In some examples, the DBCC group session 214 may include aggregate information for network sessions that are logically bound to it (sometimes referred to as selectively joined network sessions). As described above, selectively joined network sessions may include network sessions that match the DBCC group criteria 212.

[0036] As described above, as client devices are bound to and unbound from a DBCC group session 214, the DBCC group controller 216 may dynamically modify the aggregate bandwidth capacity control policy that defines bandwidth allocations for client devices bound to the DBCC group session 214. Such modifications generally affect client devices previously bound to the DBCC group session 214 (in the case where new client devices are bound to the DBCC group session 214) and / or client devices still bound to the DBCC group session 214 (in the case where previously bound client devices are unbound from the DBCC group session 214). For example, in response to one or more new client devices being bound to the DBCC group session 214, the DBCC group controller 216 may modify the aggregate bandwidth capacity control policy such that bandwidth allocations are reduced for client devices previously (and still) bound to the DBCC group session 214. In other words, as more and more client devices are bound to the DBCC group session 214, the "share of the bandwidth pie" may be reduced for these client devices. In contrast, in response to one or more client devices being unbound from the DBCC group session 214, the DBCC group controller 216 may modify the aggregate bandwidth capacity control policy such that bandwidth allocation is increased for client devices that are still bound to the DBCC group session 214. In other words, as fewer and fewer client devices are bound to the DBCC group session 214, the "share of the bandwidth pie" may be increased for these client devices. In some examples, the DBCC group controller 216 may not modify the aggregate bandwidth capacity control policy in response to each client device being bound to or unbound from the DBCC group session 214. Instead, the DBCC group controller 216 may modify the aggregate bandwidth capacity control policy based on a numerical interval of client devices bound to the DBCC group session 214. For example, when 1-10 client devices are bound to the DBCC group session 214, the DBCC group controller 216 may govern a first aggregate bandwidth capacity control policy, when 11-20 client devices are bound to the DBCC group session 214, the DBCC group controller 216 may govern a second aggregate bandwidth capacity control policy, when 21-30 client devices are bound to the DBCC group session 214, the DBCC group controller 216 may govern a third aggregate bandwidth capacity control policy, and so on. In other words, only a transition from one value interval to another value interval may trigger a modification of the aggregate bandwidth capacity control policy. Compared with a solution that modifies the aggregate bandwidth capacity control policy in response to each binding or unbinding of the DBCC group session 214, this solution can be implemented more efficiently.

[0037] As described above, when a client device (or a network session associated with a client device) satisfies DBCC group criteria 212, the client device may be bound to a DBCC group session 214. When a client device no longer satisfies DBCC group criteria 212, the client device may be unbound from the DBCC group session 214. For example, if a client device leaves the location of enterprise 250, it may no longer satisfy DBCC group criteria 212 and may be unbound from DBCC group session 214. As another example, DBCC group criteria 212 may require that a client device be connected to network 200 between 7:00 AM and 6:00 PM. Accordingly, at 6:00 PM (or 6:01 PM, depending on the particular criteria), all client devices bound to DBCC group session 214 may be unbound. In various examples, DBCC group controller 216 may perform the above-described binding and unbinding operations.

[0038] As shown, in response to modifying the aggregate bandwidth capacity control policy for the DBCC group session 214, the DBCC group controller 216 can send a DBCC policy update instruction 230 to the network function 202. Accordingly, the network function 202 can relay the DBCC policy update instruction 230 to the affected client devices of the enterprise 250, and the affected client devices can adjust their bandwidth allocation configurations in response to the DBCC policy update instruction 230. As described above, the network function 202 can be a network function associated with the network 200. For example, in the case where the network 200 is a 4G network, the network function 202 can include a PCEF network function. In the case where the network 200 is a 5G network, the network function can include an SMF network function.

[0039] As shown, in some examples, the network function 202 can send a DBCC group session initiation request 222 to the PCF system 210. The DBCC group session initiation request 222 can include a request to initiate a DBCC group session for one or more client devices that meet the DBCC group criteria 212. Similarly, the network function 202 can send a DBCC group session update request 224 (e.g., to update the aggregate bandwidth capacity control policy for the DBCC group session 214 in response to the binding / unbinding of the client device) and / or a DBCC group session termination request 226 (e.g., to terminate the DBCC group session 214) to the PCF system 210. However, in other examples, the DBCC group controller 216 can determine to initiate, modify / update and / or terminate a DBCC group session without such a request.

[0040] Although in Figure 2Only one DBCC group session is depicted in the specific example of , but PCF system 210 / DBCC group controller 216 can manage any number of DBCC group sessions associated with any number of enterprises. As described above, each of these DBCC group sessions / enterprises can have its own personalized DBCC group standards.

[0041] Figure 3 An example state transition representation 300 for a dynamic bandwidth capacity control (DBCC) group session according to various examples of the disclosed technology is shown. The operations depicted in the state transition representation 300 may be performed by a PCF system of a CSP such as Figure 2 PCF system 210) is executed.

[0042] For example, the PCF system may perform operation 302 to receive a first bind request for a DBCC group session. This may result in an idle state of the DBCC group session until the PCF system triggers the DBCC group session bind at operation 304. As shown, triggering the DBCC group session bind may result in a suspended state of the DBCC group session.

[0043] As shown, in some examples, a DBCC group session can be associated with a DBCC task. Accordingly, the PCF system can start the DBCC task at operation 306, resulting in a mediation state of the DBCC group session. Here, the DBCC task can be a process for mediating a DBCC group session and an individual client device network session.

[0044] As shown, after starting the DBCC task, the PCF system can perform various mediation operations. For example, mediation operations 308a and 308b can cause the suspension of the DBCC task-and return to the suspended state of the DBCC group session. In contrast, mediation operation 310 can cause the completion of the DBCC task and return to the idle state of the DBCC group session. Further, mediation operation 312 can cause the frozen state of the DBCC group session. When the count of suspension exceeds the threshold / maximum value, this means that the DBCC task has been interrupted too many times and the frozen state can be triggered. Entering the frozen state can reduce the impact on the network session of the individual client device, thereby reducing the possibility of the re-authentication signaling storm in the network. Accordingly, the PCF system can reject new bind requests until the DBCC task is completed via operation 314, which can return the DBCC group session to the idle state.

[0045] As shown, starting from an idle state, a final unbind operation 316 and / or a DBCC session timeout operation 318 may terminate the DBCC group session.

[0046] Figure 4An example computing component 400 is shown that can be used to implement dynamic bandwidth capacity control (DBCC) according to various examples of the disclosed technology. Figure 4 , the computing component 400 may be, for example, a server computer, a controller, or any other similar computing component capable of processing data. Figure 4 In an example implementation of , computing component 400 includes a hardware processor 402 and a machine-readable storage medium 404. In various examples, computing component 400 can be coupled to a policy control function (PCF) system (e.g., Figure 2 The PCF system 210 is associated with the PCF system 210.

[0047] The hardware processor 402 may be one or more central processing units (CPUs), semiconductor-based microprocessors, and / or other hardware devices suitable for retrieving and executing instructions stored in the machine-readable storage medium 404. The hardware processor 402 may fetch, decode, and execute instructions (such as instructions 406-412) to control a process or operation for burst preloading for available bandwidth estimation. As an alternative or in addition to retrieving and executing instructions, the hardware processor 402 may include one or more electronic circuits including electronic components for performing the functions of one or more instructions, such as a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or other electronic circuits.

[0048] A machine-readable storage medium, such as machine-readable storage medium 404, may be any electronic storage device, magnetic storage device, optical storage device, or other physical storage device that contains or stores executable instructions. Thus, machine-readable storage medium 404 may be, for example, a random access memory (RAM), a non-volatile RAM (NVRAM), an electrically erasable programmable read-only memory (EEPROM), a storage device, an optical disk, or the like. In some embodiments, machine-readable storage medium 404 may be a non-transitory storage medium, wherein the term "non-transitory" does not encompass transient propagating signals. As described in detail below, machine-readable storage medium 404 may be encoded with executable instructions, such as instructions 406-412.

[0049] Hardware processor 402 can execute instructions 406 to receive a request for a client device to initiate a network session. In various examples, the request for a client device to initiate a network session can be from a network function (e.g., Figure 2 The network function 202 receives the received information. As described above, the network function can be associated with a 4G core device / infrastructure and / or a 5G core device / infrastructure.

[0050] In response to determining that the requested network session matches dynamic bandwidth capacity control (DBCC) group criteria, hardware processor 402 can execute instructions 408 to bind the client device to the DBCC group session. As described above, the DBCC group criteria can be enterprise-specific and can be defined by the enterprise and / or a CSP providing services to the enterprise. Examples of DBCC groups can include: (1) the client device is connected to a network associated with the network session; (2) the client device is connected to the network within a specified time interval (e.g., 7:00 a.m.-6:00 p.m.); (3) the client device is connected to the network in a specified geographic area (e.g., the location of the enterprise); and / or (4) the client device is a registered client device of the enterprise.

[0051] In response to binding the client device to the DBCC group session, the hardware processor 402 can execute instructions 410 to modify the aggregate bandwidth capacity control policy that defines the bandwidth allocation for the client device bound to the DBCC group session. As described above, the aggregate bandwidth capacity control policy can include a predetermined total amount of bandwidth (e.g., 1 Gbps) reserved for the client device bound to the DBCC group session.

[0052] According to the modified aggregate bandwidth capacity control policy, the hardware processor 402 can execute instructions 412 to send instructions to reduce bandwidth allocation for at least one other client device that was bound to the DBCC group session before the client device. In various examples, the instructions to reduce bandwidth allocation for at least one other client device that was bound to the DBCC group session before the client device can be sent to a network function (e.g., Figure 2 network function 202).

[0053] In some examples, the hardware processor 402 may execute further instructions to: (1) re-modify the aggregate bandwidth capacity control policy in response to the client device being unbound from the DBCC group session; and (2) send instructions to increase the bandwidth allocation for at least one other client device that is still bound to the DBCC group session based on the re-modified aggregate bandwidth capacity control policy.

[0054] Figure 5Another example computing component 500 that can be used to implement dynamic bandwidth capacity control according to various examples of the disclosed technology is depicted. Figure 5 , the computing component 500 may be, for example, a server computer, a controller, or any other similar computing component capable of processing data. Figure 5 In an example implementation of , computing component 500 includes a hardware processor 502 and a machine-readable storage medium 504. As with computing component 400, computing component 500 may be coupled to a policy control function (PCF) system (e.g., Figure 2 The PCF system 210 is associated with the PCF system 210.

[0055] Hardware processor 502 and machine-readable storage medium 504 may be the same / similar to hardware processor 402 and machine-readable storage medium 404, respectively. Accordingly, machine-readable storage medium 504 may be encoded with executable instructions, such as instructions 506-508.

[0056] In response to a client device being unbound from a dynamic bandwidth capacity control (DBCC) session, the hardware processor 502 may execute instructions 506 to modify an aggregate bandwidth capacity control policy that defines bandwidth allocations for client devices bound to a DBCC group session. The aggregate bandwidth capacity control policy may include a predetermined total amount of bandwidth (e.g., 1 Gbps) reserved for client devices bound to the DBCC group session. Relatedly, all client devices bound to the DBCC group session may have a network session that meets the DBCC group criteria associated with the DBCC group session. As described above, the criteria for the DBCC group may be enterprise-specific. Examples of DBCC group criteria may include: (1) being connected to a network associated with the DBCC group session; (2) being connected to the network within a specified time interval; (3) being connected to the network in a specified geographic area; and / or (4) being a registered client device of the enterprise.

[0057] According to the modified aggregate bandwidth capacity control policy, hardware processor 502 may execute instruction 508 to send instructions to increase bandwidth allocation for at least one other client device that is still bound to the DBCC group session. In some examples, instructions to increase bandwidth allocation for at least one other client device that is still bound to the DBCC group session may be sent to a network function (e.g., Figure 2 As described above, the network function may be associated with a 4G core device / infrastructure and / or a 5G core device / infrastructure.

[0058] In some examples, the hardware processor 502 may execute further instructions to: (1) receive a request for a second client device to initiate a network session; (2) in response to determining that the requested network session matches the DBCC group criteria, bind the second client device to the DBCC group session; (3) in response to binding the second client device to the DBCC group session, re-modify the aggregate bandwidth capacity control policy; and (4) according to the re-modified aggregate bandwidth capacity control policy, send instructions to reduce the bandwidth allocation for at least one client device that was previously bound to the DBCC group session by the second client device. As described above, the request for a client device to initiate a network session may be from a network function (e.g., Figure 2 Received by network function 202).

[0059] Figure 6 A block diagram of an example computer system 600 is depicted in which various embodiments described herein may be implemented. The computer system 600 includes a bus 602 or other communication mechanism for communicating information, one or more hardware processors 604 coupled to the bus 602 for processing information. The hardware processor(s) 604 may be, for example, one or more general purpose microprocessors.

[0060] The computer system 600 also includes a main memory 606 (such as a random access memory (RAM), cache, and / or other dynamic storage device) coupled to the bus 602 for storing information and instructions to be executed by the processor 604. The main memory 606 may also be used to store temporary variables or other intermediate information during the execution of instructions to be executed by the processor 604. These instructions, when stored in a storage medium accessible to the processor 604, make the computer system 600 a special-purpose machine customized to perform the operations specified in the instructions.

[0061] The computer system 600 also includes a read only memory (ROM) 608 or other static storage device coupled to the bus 602 for storing static information and instructions for the processor 604. A storage device 610, such as a magnetic disk, optical disk, or USB thumb drive (flash drive), is provided and coupled to the bus 602 for storing information and instructions.

[0062] The computer system 600 may be coupled to a display 612, such as a liquid crystal display (LCD) (or touch screen), via the bus 602 for displaying information to a computer user. An input device 614, including alphanumeric and other keys, is coupled to the bus 602 for communicating information and command selections to the processor 604. Another type of user input device is a cursor control 616, such as a mouse, trackball, or cursor direction keys, for communicating direction information and command selections to the processor 604 and for controlling cursor movement on the display 612. In some embodiments, the same direction information and command selections as a cursor control may be achieved via receiving touches on a touch screen without a cursor.

[0063] The computing system 600 may include a user interface module to implement a GUI, which may be stored in a mass storage device as executable software code executed by the computing device(s). This module and other modules may include, by way of example, components (such as software components, object-oriented software components, class components, and task components), processes, functions, properties, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables.

[0064] In general, the terms "component", "engine", "system", "database", "data store", etc., as used herein, may refer to logic embodied in hardware or firmware, or to a collection of software instructions that may have entry and exit points, written in a programming language such as Java, C, or C++. Software components may be compiled and linked into executable programs, installed in a dynamic link library, or may be written in an interpreted programming language such as BASIC, Perl, or Python. It will be understood that software components may be called from other components or from themselves, and / or may be called in response to detected events or interrupts. Software components configured to execute on a computing device may be provided on a computer-readable medium (such as a compressed disk, digital video disk, flash drive, disk, or any other tangible medium), or provided as a digital download (and may be initially stored in a compressed format or installable format that requires installation, decompression, or decryption prior to execution). Such software code may be stored in part or in whole on a memory device of an executing computing device for execution by the computing device. Software instructions may be embedded in firmware, such as an EPROM. It will also be understood that hardware components may be composed of connected logic units (such as gates and flip-flops), and / or may be composed of programmable units (such as programmable gate arrays or processors).

[0065] The computer system 600 may implement the techniques described herein using custom hardwired logic, one or more ASICs or FPGAs, firmware, and / or program logic that is combined with the computer system to make the computer system 600 a special purpose machine or to program the computer system 600. According to one embodiment, the computer system 600 performs the techniques herein in response to the processor(s) 604 executing one or more sequences of one or more instructions contained in the main memory 606. These instructions may be read into the main memory 606 from another storage medium, such as the storage device 610. Execution of the sequences of instructions contained in the main memory 606 causes the processor(s) 604 to perform the process steps described herein. In alternative embodiments, hardwired circuitry may be used in place of or in combination with software instructions.

[0066] The term "non-transitory medium" and similar terms used herein refer to any medium that stores data and / or instructions that cause a machine to operate in a particular manner. Such non-transitory media may include non-volatile media and / or volatile media. Non-volatile media include, for example, optical or magnetic disks, such as storage device 610. Volatile media include dynamic memory, such as main memory 606. Common forms of non-transitory media include, for example, floppy disks, foldable disks, hard disks, solid-state drives, tapes or any other magnetic data storage media, CD-ROMs, any other optical data storage media, any physical media with a pattern of holes, RAM, PROMs and EPROMs, FLASH-EPROMs, NVRAMs, any other memory chips or cassettes, and network versions thereof.

[0067] Non-transitory media are distinct from transmission media, but can be used in conjunction with transmission media. Transmission media participate in the transfer of information between non-transitory media. For example, transmission media include coaxial cables, copper wires, and optical fibers, including the wires that comprise bus 602. Transmission media can also take the form of acoustic or light waves, such as those generated during radio wave communications and infrared data communications.

[0068] Computer system 600 also includes a communication interface 618 coupled to bus 602. Network interface 618 provides bidirectional data communication coupled to one or more network links connected to one or more local networks. For example, communication interface 618 can be an integrated services digital network (ISDN) card, a cable modem, a satellite modem, or a modem for providing data communication connections to telephone lines of corresponding types. As another example, network interface 618 can be a local area network (LAN) card for providing data communication connections to a compatible LAN (or a WAN component communicating with a WAN). Wireless links can also be implemented. In any such implementation, network interface 618 sends and receives electrical signals, electromagnetic signals, or optical signals carrying digital data streams representing various types of information.

[0069] A network link typically provides data communications to other data devices through one or more networks. For example, a network link can provide a connection through a local network to a host or to data devices operated by an Internet Service Provider (ISP). The ISP, in turn, provides data communications services through a global packet data communications network now commonly referred to as the "Internet." Both local area networks and the Internet use electrical, electromagnetic, or optical signals that carry digital data streams. The signals through the various networks and the signals on the network link and through the communication interface 618 are example forms of transmission media that carry digital data to and from the computer system 600.

[0070] Computer system 600 can send messages and receive data, including program code, through the network(s), network links and communications interface 618. In the Internet example, a server can send the code for a requested application through the Internet, an ISP, a local network and communications interface 618.

[0071] The received code may be executed by processor 604 as it is received, and / or stored in storage device 610 or other non-volatile storage for later execution.

[0072] Each process, method, and algorithm described in the preceding section may be embodied in a code component executed by one or more computer systems or computer processors including computer hardware, and the code component executed by one or more computer systems or computer processors including computer hardware may be fully or partially automated. One or more computer systems or computer processors may also operate to support the execution of related operations in a "cloud computing" environment or as "software as a service" (SaaS). These processes and algorithms may be implemented in part or in full in a dedicated circuit. The various features and processes described above may be used independently of each other, or may be combined in various ways. Different combinations and sub-combinations are intended to fall within the scope of the present disclosure, and certain methods or process blocks may be omitted in some implementations. The methods and processes described herein are also not limited to any particular order, and the blocks or states associated therewith may be executed in other appropriate orders, or may be executed in parallel, or in some other manner. Blocks or states may be added to the disclosed example embodiments, or blocks or states may be removed from the disclosed example embodiments. The execution of certain operations or processes may be distributed among computer systems or computer processors, not only residing in a single machine, but also deployed between multiple machines.

[0073] As used herein, circuits can be implemented using any form of hardware, software, or a combination thereof. For example, one or more processors, controllers, ASICs, PLAs, PALs, CPLDs, FPGAs, logic components, software routines, or other mechanisms can be implemented to form circuits. In implementation, the various circuits described herein can be implemented as discrete circuits, or the functions and features described can be shared in part or together in one or more circuits. Even if various features or functional elements can be described or required to be protected as separate circuits individually, these features and functions can also be shared in one or more common circuits, and such descriptions should not require or imply that separate circuits are required to implement such features or functions. In the case where the circuit is implemented in whole or in part with software, such software can be implemented to operate together with a computing or processing system (such as computer system 600) that can implement the functions described therefor.

[0074] As used herein, the term "or" may be understood to be inclusive or exclusive. In addition, descriptions of resources, operations, or structures in the singular should not be interpreted to exclude the plural. Conditional language such as "can," "may," "might," or "could" is generally intended to convey that certain embodiments include and other embodiments do not include certain features, elements, and / or steps, unless otherwise specifically stated or understood otherwise in the context of use.

[0075] The terms and phrases used in this document and variations thereof should be construed as open ended and not restrictive, unless expressly stated otherwise. Adjectives such as "conventional," "traditional," "normal," "standard," "known," and terms of similar meaning should not be construed as limiting the items described to items available as of a given time period or as of a given time, but should be construed as covering conventional, traditional, normal, or standard technologies available or known at any time now or in the future. In some cases, the presence of broad words and phrases such as "one or more," "at least," "but not limited to," or other similar phrases should not be construed to mean that a narrower case is intended or required where such broad phrases may not be present.

Claims

1. A method comprising: Receiving a request from a client device to initiate a network session; In response to determining that the requested network session matches dynamic bandwidth capacity control DBCC group criteria, binding the client device to a DBCC group session; In response to binding the client device to the DBCC group session, modifying an aggregate bandwidth capacity control policy that defines bandwidth allocation for client devices bound to the DBCC group session, wherein the aggregate bandwidth capacity control policy includes a predetermined total amount of bandwidth reserved for client devices bound to the DBCC group session; as well as Instructions are sent to reduce bandwidth allocation for at least one other client device that was previously bound to the DBCC group session by the client device according to the modified aggregate bandwidth capacity control policy.

2. The method according to claim 1, further comprising: In response to the client device being unbound from the DBCC group session, re-modifying the aggregate bandwidth capacity control policy; as well as According to the re-modified aggregate bandwidth capacity control policy, an instruction is sent to increase bandwidth allocation for at least one other client device that is still bound to the DBCC group session.

3. The method of claim 1, wherein the DBCC group standard is enterprise specific.

4. The method of claim 3, wherein the DBCC group criteria include at least one of the following criteria: The client device is connected to a network associated with the network session; The client device is connected to the network within a specified time interval; The client device is connected to the network in a specified geographic area; and The client device is a registered client device of the enterprise.

5. The method according to claim 1, wherein the method is implemented by a policy control function (PCF) system of a communication service provider (CSP), and the DBCC group standard is stored in the PCF system of the CSP.

6. The method according to claim 1, wherein: The request for the client device to initiate the network session is received from a network function; and The instruction to reduce bandwidth allocation for the at least one other client device that was bound to the DBCC group session prior to the client device is sent to the network function.

7. The method of claim 6, wherein the network function is associated with a 4G network infrastructure.

8. A policy control function PCF system, comprising: one or more processing resources; as well as a non-transitory computer-readable medium coupled to the one or more processing resources, the non-transitory computer-readable medium storing instructions that, when executed by the one or more processing resources, cause the PCF system to: Receiving a request from a client device to initiate a network session; In response to determining that the requested network session matches dynamic bandwidth capacity control DBCC group criteria, binding the client device to a DBCC group session; In response to binding the client device to the DBCC group session, modifying an aggregate bandwidth capacity control policy that defines bandwidth allocation for client devices bound to the DBCC group session, wherein the aggregate bandwidth capacity control policy includes a predetermined total amount of bandwidth reserved for client devices bound to the DBCC group session; as well as Instructions are sent to reduce bandwidth allocation for at least one other client device that was previously bound to the DBCC group session by the client device according to the modified aggregate bandwidth capacity control policy.

9. The PCF system of claim 8, wherein the instructions further cause the PCF system to: In response to the client device being unbound from the DBCC group session, re-modifying the aggregate bandwidth capacity control policy; and According to the re-modified aggregate bandwidth capacity control policy, an instruction is sent to increase bandwidth allocation for at least one other client device that is still bound to the DBCC group session.

10. The PCF system of claim 8, wherein the DBCC group standard is enterprise specific.

11. The PCF system of claim 10, wherein the DBCC group criteria include at least one of the following criteria: The client device is connected to a network associated with the network session; The client device is connected to the network within a specified time interval; The client device is connected to the network in a specified geographic area; and The client device is a registered client device of the enterprise.

12. The PCF system of claim 8, wherein the instructions further cause the PCF system to: receiving a request for initiating a second network session from a second client device; In response to determining that the requested network session matches second DBCC group criteria, binding the second client device to a second DBCC group session, wherein the second DBCC group criteria and the second DBCC group session are associated with a second enterprise; in response to binding the second client device to the second DBCC group session, modifying a second aggregate bandwidth capacity control policy that defines bandwidth allocation for client devices bound to the second DBCC group session, wherein the second aggregate bandwidth capacity control policy includes a second predetermined total amount of bandwidth reserved for client devices bound to the second DBCC group session; as well as In accordance with the modified second aggregate bandwidth capacity control policy, an instruction is sent to reduce bandwidth allocation for at least one other client device that was bound to the second DBCC group session before the second client device.

13. The PCF system of claim 12, wherein the second predetermined total amount of bandwidth reserved for client devices bound to the second DBCC group session is greater than the predetermined total amount of bandwidth reserved for client devices bound to the DBCC group session.

14. The PCF system of claim 8, wherein: A request for the client device to initiate the network session is received from a network function; and The instruction to reduce bandwidth allocation for the at least one other client device that was bound to the DBCC group session prior to the client device is sent to the network function.

15. The PCF system of claim 14, wherein the network function is associated with a 4G network infrastructure.

16. A non-transitory computer readable medium storing instructions that, when executed by one or more processing resources, cause the one or more processing resources to: In response to a client device being unbound from a dynamic bandwidth capacity control DBCC session, modifying an aggregate bandwidth capacity control policy that defines bandwidth allocation for client devices bound to the DBCC group session, wherein: The aggregate bandwidth capacity control policy includes a predetermined total amount of bandwidth reserved for client devices bound to the DBCC group session, and All client devices bound to the DBCC group session have a network session that meets the DBCC group criteria associated with the DBCC group session; as well as Instructions are sent to increase bandwidth allocation for at least one other client device still bound to the DBCC group session according to the modified aggregate bandwidth capacity control policy.

17. The non-transitory computer readable medium storing instructions of claim 16, wherein the instructions further cause the one or more processing resources to: receiving a request for initiating a network session from a second client device; In response to determining that the requested network session matches the DBCC group criteria, binding the second client device to the DBCC group session; In response to binding the second client device to the DBCC group session, re-modifying the aggregate bandwidth capacity control policy; as well as According to the re-modified aggregate bandwidth capacity control policy, an instruction is sent to reduce bandwidth allocation for at least one client device that was bound to the DBCC group session before the second client device.

18. The non-transitory computer readable medium storing instructions of claim 16, wherein the DBCC group standard is enterprise specific.

19. The non-transitory computer readable medium storing instructions of claim 17, wherein the DBCC group criteria comprises at least one of the following criteria: connecting to a network associated with the DBCC group session; connecting to said network at specified intervals; connecting to said network in a specified geographical area; as well as Is a registered client device of the enterprise.

20. The non-transitory computer readable medium storing instructions of claim 16, wherein: A request for the client device to initiate the network session is received from a network function; The instruction to reduce bandwidth allocation for the at least one other client device that was bound to the DBCC group session prior to the client device is sent to the network function; and The network functions are associated with 4G network infrastructure.

Images