Abstract: Described is allocating and deallocating server instances (e.g., comprising baseband unit resources) of a distributed unit based on need for user equipment session handling. For example, when user equipment sessions load a server instance to a threshold capacity, an additional server instance can be allocated to handle new user equipment sessions. Any selected carrier subgroup, which can correspond to a cell's carriers, can be selected for assigning any newly incoming, unassigned user equipment sessions associated with the selected carrier subgroup to the newly allocated, additional server instance. As prior sessions end, the load decreases on the server that had reached the threshold capacity. When the total hub load decreases, deallocation of a no-longer used server instance can be performed. Deallocation can include transferring any remaining session, e.g., long-lasting sessions, to a different server instance.

Abstract: Described is centralized scheduling of baseband unit resources of a hub, including allocating and deallocating baseband unit resources of a distributed unit instance based on anticipated and/or actual demand for the resources. For example, when user equipment transitions to a connected state, a corresponding message can be detected and used to determine whether sufficient baseband unit resources exist to handle the traffic of the newly connecting user equipment. If not, additional baseband unit resources are allocated, coupled to a node (cell), and the node scheduled to handle the user equipment traffic. When user equipment transitions to an inactive state, the corresponding command can be detected and used to determine whether the baseband unit resources are still needed for other traffic. If not, the baseband unit resources are deallocated.

Abstract: The disclosed technology is directed towards load balancing baseband units in a communications network. A baseband physical layer 1 unit’s functions are disaggregated into Layer 1 (L1) distributed units and radio units, instead of deploying full-fledged baseband units at a service’ provider’s service areas (cells). A load balancer scales up the number of active distributed units based on increased actual demand, and scales down the active distributed units based on decreased demand. The L1 distributed units and radio units can be software-defined network functions, and need not be collocated, whereby the distributed units can be in the cloud or hub remotely located relative to the radio units deployed at the service areas. Examples of load balancing can be load balancing of transmitted data per carrier, per subcarrier, per user equipment, per transmission time interval (TTI / slot), per bearer, or per channel.

Abstract: Described is pooling baseband units into a hub and mapping radio units associated with the hub to baseband units of the group based on respective resource capacity data of the respective baseband units and an estimated resource usage data of a device that couples to a baseband unit. In one alternative, estimated peak resource usage data of a radio unit over an operation interval is used to select a baseband unit, generally based on which baseband unit of the pool has the least remaining resource capacity, to which the radio unit is mapped for the operation interval. In another alterative, estimated peak resource usage data resource (usage and duration) of a user equipment session is used to dynamically map the user equipment session to a baseband unit, generally selected by which baseband unit of the pool has the least remaining resource capacity.

Abstract: Described is allocating and deallocating baseband unit resources of a distributed unit based on anticipated and/or actual demand for the resources. For example, when user equipment transitions to a connected state, a corresponding message can be detected and used to determine whether sufficient baseband unit resources are needed to handle the traffic of the newly connecting user equipment. If not, additional baseband unit resources are allocated. When user equipment transitions to an inactive state, the corresponding command can be detected and used to determine whether the baseband unit resources are still needed for other traffic. If not, baseband unit resources are deallocated; that is, if a distributed unit's resources are no longer needed, the distributed unit's resources are deactivated to reduce resource consumption. Deallocation can be performed by changing the resources to a power conservation (e.g., sleep) state, with allocation performed by changing such resources back to an active state.

Abstract: Aspects of the subject disclosure may include, for example, a network API service that receives network event data and provides performance hints to a resource manager that manages application containers at edge cloud locations. Network event data may be received from access networks, core networks, nodes within access networks or core networks, or the like. Performance hints may allow booting of application containers at edge cloud locations. Other embodiments are disclosed.

Abstract: A method performed by a processing system includes receiving a request from a first user endpoint device to establish a mobile terminating connection to a second user endpoint device, determining whether an access certificate that is associated with the second user endpoint device has been received from the first user endpoint device, terminating the mobile terminating connection at the processing system when the access certificate is determined to be received from the first user endpoint device, identifying a private Internet Protocol address that is associated with the second user endpoint device when the access certificate is determined to be received from the first user endpoint device, and establishing a connection from the processing system to the second user endpoint device, separate from the mobile terminating connection from the first user endpoint device to the processing system, using the private internet protocol address of the second user endpoint device.

Abstract: Aspects of the subject disclosure may include, for example, a network API service that receives network event data and provides performance hints to a resource manager that manages application containers at edge cloud locations. Network event data may be received from access networks, core networks, nodes within access networks or core networks, or the like. Performance hints may allow booting of application containers at edge cloud locations. Other embodiments are disclosed.

Abstract: The disclosed technology is directed towards associating a distributed unit (a baseband function) with a radio unit, corresponding to a service area, when the radio unit transitions from an idle state to an active state with respect to serving user equipment. When an idle radio unit receives a message requesting connection from a formerly idle user equipment, or user equipment to be served due to a handover, the message triggers assignment of a distributed unit to the radio unit, whereby the radio unit becomes active to serve the user equipment. If insufficient distributed unit capacity exists, a new distributed unit is dynamically instantiated and assigned to the radio unit. When a radio unit transitions from active to idle, the radio unit is disassociated from the distributed unit. If a distributed unit is not associated with any radio unit, the distributed unit is deactivated to reduce resource consumption.

Abstract: The disclosed technology is directed towards load balancing baseband units in a communications network. A baseband physical layer 1 unit's functions are disaggregated into Layer 1 (L1) distributed units and radio units, instead of deploying full-fledged baseband units at a service? provider's service areas (cells). A load balancer scales up the number of active distributed units based on increased actual demand, and scales down the active distributed units based on decreased demand. The L1 distributed units and radio units can be software-defined network functions, and need not be collocated, whereby the distributed units can be in the cloud or hub remotely located relative to the radio units deployed at the service areas. Examples of load balancing can be load balancing of transmitted data per carrier, per subcarrier, per user equipment, per transmission time interval (TTI/slot), per bearer, or per channel.

Abstract: The disclosed technology is directed towards associating a distributed unit (a baseband function) with a radio unit, corresponding to a service area, when the radio unit transitions from an idle state to an active state with respect to serving user equipment. When an idle radio unit receives a message requesting connection from a formerly idle user equipment, or user equipment to be served due to a handover, the message triggers assignment of a distributed unit to the radio unit, whereby the radio unit becomes active to serve the user equipment. If insufficient distributed unit capacity exists, a new distributed unit is dynamically instantiated and assigned to the radio unit. When a radio unit transitions from active to idle, the radio unit is disassociated from the distributed unit. If a distributed unit is not associated with any radio unit, the distributed unit is deactivated to reduce resource consumption.

Abstract: A method, computer-readable medium, and apparatus for supporting services for customer traffic using edge clouds are disclosed. For example, a processing system may receive an indication of a set of customer devices of a customer of a network provider and an indication of a service of an edge cloud to be applied to customer traffic of the customer devices, support configuration of a network of the network provider to support a customer segment for the customer including configuration of a gateway of the network and a switch of the network that is associated with the edge cloud, support configuration of a virtual network between the switch and an edge cloud element supporting the service, and support configuration of the switch to support an association of the customer segment and the virtual network for supporting routing of the customer traffic to the service via the virtual network.

Abstract: Aspects of the subject disclosure may include, for example, a network API service that receives network event data and provides performance hints to a resource manager that manages application containers at edge cloud locations. Network event data may be received from access networks, core networks, nodes within access networks or core networks, or the like. Performance hints may allow booting of application containers at edge cloud locations. Other embodiments are disclosed.

Abstract: A system to control access to domains, servers, or content, among other things. There may be individualized or global policies. Policy servers or other devices may interface with databases, DNS servers, firewalls, programmable virtualized routers, or dynamic host configuration protocol servers, among other devices to dynamically update various policy enforcement elements.

Abstract: Aspects of the subject disclosure may include, for example, a network API service that receives network event data and provides performance hints to a resource manager that manages application containers at edge cloud locations. Network event data may be received from access networks, core networks, nodes within access networks or core networks, or the like. Performance hints may allow booting of application containers at edge cloud locations. Other embodiments are disclosed.

Abstract: The disclosed technology is directed towards associating a distributed unit (a baseband function) with a radio unit, corresponding to a service area, when the radio unit transitions from an idle state to an active state with respect to serving user equipment. When an idle radio unit receives a message requesting connection from a formerly idle user equipment, or user equipment to be served due to a handover, the message triggers assignment of a distributed unit to the radio unit, whereby the radio unit becomes active to serve the user equipment. If insufficient distributed unit capacity exists, a new distributed unit is dynamically instantiated and assigned to the radio unit. When a radio unit transitions from active to idle, the radio unit is disassociated from the distributed unit. If a distributed unit is not associated with any radio unit, the distributed unit is deactivated to reduce resource consumption.

Abstract: A method, computer-readable medium, and apparatus for supporting services for customer traffic using edge clouds are disclosed. For example, a processing system may receive an indication of a set of customer devices of a customer of a network provider and an indication of a service of an edge cloud to be applied to customer traffic of the customer devices, support configuration of a network of the network provider to support a customer segment for the customer including configuration of a gateway of the network and a switch of the network that is associated with the edge cloud, support configuration of a virtual network between the switch and an edge cloud element supporting the service, and support configuration of the switch to support an association of the customer segment and the virtual network for supporting routing of the customer traffic to the service via the virtual network.

Abstract: The disclosed technology is directed towards load balancing baseband units in a communications network. A baseband physical layer 1 unit's functions are disaggregated into Layer 1 (L1) distributed units and radio units, instead of deploying full-fledged baseband units at a service' provider's service areas (cells). A load balancer scales up the number of active distributed units based on increased actual demand, and scales down the active distributed units based on decreased demand The L1 distributed units and radio units can be software-defined network functions, and need not be collocated, whereby the distributed units can be in the cloud or hub remotely located relative to the radio units deployed at the service areas. Examples of load balancing can be load balancing of transmitted data per carrier, per subcarrier, per user equipment, per transmission time interval (TTI/slot), per bearer, or per channel.

Abstract: A system to control access to domains, servers, or content, among other things. There may be individualized or global policies. Policy servers or other devices may interface with databases, DNS servers, firewalls, programmable virtualized routers, or dynamic host configuration protocol servers, among other devices to dynamically update various policy enforcement elements.

Abstract: Methods, systems, and apparatuses, among other things, may direct client requests to an Edge Cloud location satisfying application requirements associated with the request. Moreover, a domain name service (DNS) query may be received, one or more requests associated with DNS query may be determined, a server may be identified based on the one or more requests, and the DNS query may be redirected to the identified server.