Abstract: A system described herein may provide a technique for the rate-controlled forwarding of traffic to a base station of a radio access network (“RAN”). The rate of the forwarding of the traffic may be based on a latency sensitivity of the traffic, metrics associated with the base station, and an ingress capacity of the base station. The metrics associated with the base station may include congestion and/or load metrics, radio frequency (“RF”) metrics, or other suitable metrics. The latency sensitivity of the traffic may be determined based on a source and/or destination of the traffic, a network slice associated with the traffic, or other suitable traffic attributes. After receiving the rate-controlled traffic, the base station may perform scheduling and/or queueing of the traffic in order to wirelessly provide the traffic to one or more User Equipment (“UEs”).

Abstract: A User Equipment (“UE”) described herein may connect or request connection to a base station of a wireless network. The base station may implement multiple frequency bands, and connecting or requesting connection to the base station may include connecting or requesting connection via a particular frequency band of the multiple frequency bands. The UE may provide an indication of the particular frequency band to a core of the wireless network. The core may select a set of parameters for communications between the UE and the wireless network based on the indication of the particular frequency band. Additionally, or alternatively, the core may provide an indication of the particular frequency band to a device that provides a service to the UE via the wireless network, and the device may select parameters for the service based on the indication of the particular frequency band.

Abstract: Systems and methods described herein use group segmentation of applications (referred to herein as “slicing classes”), based on common service requirements, to allow carriers to assign UE traffic to network slices. A UE stores slicing class definitions for use with UE Route Selection Policies (URSP). Each of the slicing class definitions include network quality of service (QoS) characteristics that are applicable to network traffic for multiple software applications. The UE maps the software applications to corresponding slicing class identifiers associated with the slicing class definitions. The UE also stores URSP rules for associating a slicing class identifier with a network slice identifier. A UE operating system sends, to a modem, one of the slicing class identifiers for an application that is requesting attachment to a wireless network. The modem sends a registration request with a selected network slice identifier based on the received slicing class identifier and the URSP rules.

Abstract: A method, a system, and a non-transitory storage medium provide for encoding a general packet radio service (GPRS)-tunnel endpoint identifier (GTP-TEID) with data identifying radio frequency (RF) bandwidths supported in a local radio environment (LRE) from which a user equipment (UE) device accesses the wireless access station; sending, via a signaling channel, the GTP-TEID to a core network device; notifying one or more core network devices of an RF bandwidth category level corresponding to the RF bandwidths; and applying at least one of a policy rule or a charging rule to a packet data unit (PDU) session for the UE device, based on the RF bandwidth category level.

Abstract: A method, a device, and a non-transitory storage medium are described in which a radio access network slice and core network slice service is provided based on RAN-CN network slice pairing information. A radio access network slice and/or a core network slice uses the RAN-CN network slice pairing information to select network resources to support sessions of end devices. The RAN-CN network slice pairing information may include location information, radio access network slice information, core network slice information correlated to different types or applications or services available to end devices. The RAN-CN network slice pairing information may include information indicating current and available radio access network resources pertaining to the radio access network slices and threshold resources that may be used to support the different types of applications or services.

Abstract: A system described herein may provide a technique for the differentiated Quality of Service (“QoS”) treatment of different traffic types associated with the same application (e.g., a “multi-persona” application) by a wireless network, without the exposure of an application identifier of the application to the wireless network. The application may provide a traffic type indication, based on which a User Equipment (“UE”) may establish one or more QoS flows or other types of communication sessions with the wireless network, where the QoS flows or other types of communication sessions are associated with a network slice that is associated with the traffic type. The communication sessions may include Data Radio Bearers (“DRBs”), backhaul links, protocol data unit (“PDU”) sessions, or other suitable types of communication sessions.

Abstract: A network device may provide, to a content server device, an upload policy for uploading data, and may receive a notification indicating that the user device is attached to a network associated with a network identifier. The network device may receive a request identifying data to be uploaded by a user device to the content server device, and may determine a time window, a data size, and the network identifier associated with the upload policy and the network. The network device may determine whether the request complies with the time window, the data size, and the network identifier, and may determine whether a quantity of tokens associated with the network identifier is zero. The network device may provide, to the user device, a response indicating approval of the data to be uploaded, and may receive an indication that uploading the data is complete.

Abstract: Systems and methods described include receiving traffic associated with a multi-access edge computing (MEC) application hosted at a MEC network; determining an Internet Protocol (IP) address associated with the MEC application, wherein the IP address indicates a priority of the traffic associated with the MEC application; modifying a header of the traffic to include the IP address associated with the MEC application; transmitting the traffic to a wireless station; and routing the traffic based on the priority associated with the MEC application.

Abstract: A method, a device, and a non-transitory storage medium are described in which an blockchain-based network information management service is provided. The service provides blockchain mechanisms that allows for the management and disbursement of network information among network devices of a RAN, a core network, and an application layer network. The service may define a structure for the network information that may be used by RAN devices, core devices, and application layer devices of different vendors and third parties.

Abstract: A method, a system, and a non-transitory storage medium provide for encoding a general packet radio service (GPRS)-tunnel endpoint identifier (GTP-TEID) with data identifying radio frequency (RF) bandwidths supported in a local radio environment (LRE) from which a user equipment (UE) device accesses the wireless access station; sending, via a signaling channel, the GTP-TEID to a core network device; notifying one or more core network devices of an RF bandwidth category level corresponding to the RF bandwidths; and applying at least one of a policy rule or a charging rule to a packet data unit (PDU) session for the UE device, based on the RF bandwidth category level.

Abstract: A system described herein may provide a technique for the differentiated Quality of Service (“QoS”) treatment of different traffic types associated with the same application (e.g., a “multi-persona” application) by a wireless network, without the exposure of an application identifier of the application to the wireless network. The application may provide a traffic type indication, based on which a User Equipment (“UE”) may establish one or more QoS flows or other types of communication sessions with the wireless network, where the QoS flows or other types of communication sessions are associated with a network slice that is associated with the traffic type. The communication sessions may include Data Radio Bearers (“DRBs”), backhaul links, protocol data unit (“PDU”) sessions, or other suitable types of communication sessions.

Abstract: A device may receive data identifying user devices within a geographical area of a base station, respective services provided by the base station to the user devices, the geographical area, an earth station within the geographical area, an infrastructure within the geographical area, and other base stations located geographically adjacent to the geographical area. The device may determine, based on the received data, interfering beams of the base station that interfere with the earth station, and may include data identifying the interfering beams, in a first list of beams to be deemphasized. The device may determine, based on the received data, beams of the base station to be emphasized based on the infrastructure, and may include data identifying the beams to be emphasized, in a second list. The device may control the base station based on the first list and the second list.

Abstract: Systems and methods described include receiving traffic associated with a multi-access edge computing (MEC) application hosted at a MEC network; determining an Internet Protocol (IP) address associated with the MEC application, wherein the IP address indicates a priority of the traffic associated with the MEC application; modifying a header of the traffic to include the IP address associated with the MEC application; transmitting the traffic to a wireless station; and routing the traffic based on the priority associated with the MEC application.

Abstract: A method, a system, and a non-transitory storage medium provide for encoding a general packet radio service (GPRS)-tunnel endpoint identifier (GTP-TEID) with data identifying radio frequency (RF) bandwidths supported in a local radio environment (LRE) from which a user equipment (UE) device accesses the wireless access station; sending, via a signaling channel, the GTP-TEID to a core network device; notifying one or more core network devices of an RF bandwidth category level corresponding to the identified RF bandwidths; and applying at least one of a policy rule or a charging rule to a packet data unit (PDU) session for the UE device, based on the RF bandwidth category level.

Abstract: A computer device may include a memory configured to store instructions and a processor configured to execute the instructions to determine network slices for a plurality of user equipment (UE) devices associated with a base station wherein a particular network slice identifies a particular service category or a UE device attribute category associated with particular ones of the plurality of UE devices, determine a distribution of network slices for the base station based on the determined network slices for the plurality of UE devices, and determine an adjustment for an optimization parameter based on the distribution of network slices for the base station. The computer device may be further configured to adjust the optimization parameter for the base station based on the determined adjustment, wherein adjusted optimization parameter is used by the base station to manage data traffic associated with the plurality of UE devices.

Abstract: A network device may receive, from a user equipment, a dataset identifying: applications utilized by the user equipment, network protocol types associated with the applications, and network addresses associated with the applications. The network device may segregate the dataset based on the network protocol types and to generate a segregated dataset. The network device may determine, based on the segregated dataset, a policy that causes particular application traffic associated with a particular network protocol type to be allocated to a particular network slice of the network. The network device may cause the policy to be provided to the user equipment to cause the user equipment to allocate the particular application traffic associated with the particular network protocol type to the particular network slice of the network.

Abstract: A system described herein may provide a technique for the rate-controlled forwarding of traffic to a base station of a radio access network (“RAN”). The rate of the forwarding of the traffic may be based on a latency sensitivity of the traffic, metrics associated with the base station, and an ingress capacity of the base station. The metrics associated with the base station may include congestion and/or load metrics, radio frequency (“RF”) metrics, or other suitable metrics. The latency sensitivity of the traffic may be determined based on a source and/or destination of the traffic, a network slice associated with the traffic, or other suitable traffic attributes. After receiving the rate-controlled traffic, the base station may perform scheduling and/or queueing of the traffic in order to wirelessly provide the traffic to one or more User Equipment (“UEs”).

Abstract: Systems and methods described herein use group segmentation of applications (referred to herein as “slicing classes”), based on common service requirements, to allow carriers to assign UE traffic to network slices. A UE stores slicing class definitions for use with UE Route Selection Policies (URSP). Each of the slicing class definitions include network quality of service (QoS) characteristics that are applicable to network traffic for multiple software applications. The UE maps the software applications to corresponding slicing class identifiers associated with the slicing class definitions. The UE also stores URSP rules for associating a slicing class identifier with a network slice identifier. A UE operating system sends, to a modem, one of the slicing class identifiers for an application that is requesting attachment to a wireless network. The modem sends a registration request with a selected network slice identifier based on the received slicing class identifier and the URSP rules.

Abstract: Systems and methods described herein use group segmentation of applications (referred to herein as “slicing classes”), based on common service requirements, to allow carriers to assign UE traffic to network slices. A UE stores slicing class definitions for use with UE Route Selection Policies (URSP). Each of the slicing class definitions include network quality of service (QoS) characteristics that are applicable to network traffic for multiple software applications. The UE maps the software applications to corresponding slicing class identifiers associated with the slicing class definitions. The UE also stores URSP rules for associating a slicing class identifier with a network slice identifier. A UE operating system sends, to a modem, one of the slicing class identifiers for an application that is requesting attachment to a wireless network. The modem sends a registration request with a selected network slice identifier based on the received slicing class identifier and the URSP rules.

Abstract: A system may receive an indication that a user device is connecting to a network and determine, based on a profile associated with the user device, that a priority associated with the user device is to be modified when congestion associated with the network reaches a level. The system may send, to a base station, a first request to monitor the congestion associated with the network. The system may receive, from the base station, an indication that the congestion associated with the network has reached the level. The system may send, to the base station, a second request to modify the priority associated with the user device when the congestion associated with the network is at the level.