Abstract: Systems and methods described herein provide binding support function (BSF) service registration and discovery for environments using oversubscribed network addresses. A network device in a core network receives a registration request from a binding support device. The registration request includes a binding group identifier associated with the binding support device. The network device stores, based on the registration request, a profile for the binding support device that includes the binding group identifier and receives, from a policy control device, a discovery request for a that includes a unique identifier of user equipment (UE) device. The network device provides, to the policy control device, a response to the discovery request that identifies the binding support device.

Abstract: A network device may receive a context creation request based on a protocol data unit (PDU) session establishment request for establishing a PDU session with a user device, and may generate a policy context request based on receiving the context creation request. The network device may provide the policy context request to a policy control function (PCF), and may receive, from the PCF and based on the policy context request, policy rules for the PDU session. The network device may receive, from the PCF, a terminate PDU session notification indicating that a binding support function (BSF) is unreachable, and may generate, based on the terminate PDU session notification, a PDU session release command that includes a cause code indicating an issue with the BSF and an instruction to not reinitiate the PDU session. The network device may cause the PDU session release command to be provided to the user device.

Abstract: A network device may receive an indication of movement of a user device, associated with multiple packet data unit (PDU) sessions, from a first radio access network (RAN) to a second RAN, and may maintain, based on the indication, a particular PDU session, of the multiple PDU sessions, associated with a default flow. The network device may release, based on the indication, the multiple PDU sessions other than the particular PDU session, and may handle the multiple PDU sessions, other than the particular PDU session, in accordance with a handling option.

Abstract: In some implementations, a first network function device included in a core network may receive an indication of a user data management (UDM) group identifier that is associated with a UDM network function device included in the core network. The first network function device may determine, based on the UDM group identifier, a user data repository (UDR) group identifier associated with a UDR network function device that is associated with the UDM network function device. The first network function device may transmit, to one or more second network function devices included in the core network, an indication of the UDR group identifier.

Abstract: In some implementations, a network device may obtain a message that includes service parameter data associated with an application. The service parameter data may indicate a revalidation time. The network device may generate, based on the service parameter data, a user equipment route selection policy (URSP) rule associated with the application that includes the revalidation time indicated by the service parameter data. The URSP rule may expire at the revalidation time. The network device may transmit the URSP rule for a user equipment (UE) that executes the application. The network device may receive a state indication message associated with the UE that is triggered at the revalidation time.

Abstract: A network device may select a first user plane function for establishing, with a user equipment, a protocol data unit session with a single flow and may receive an application function trigger associated with a first new flow for a first application of the user equipment. The network device may cause a first traffic filter to be provided to the user equipment to enable the user equipment to route first application traffic, based on the first traffic filter, to a second user plane function and a first multi-access edge computing device associated with the second user plane function.

Abstract: Systems and methods described herein provide binding support function (BSF) service registration and discovery for environments using oversubscribed network addresses. A network device in a core network receives a registration request from a binding support device. The registration request includes a binding group identifier associated with the binding support device. The network device stores, based on the registration request, a profile for the binding support device that includes the binding group identifier and receives, from a policy control device, a discovery request for a that includes a unique identifier of user equipment (UE) device. The network device provides, to the policy control device, a response to the discovery request that identifies the binding support device.

Abstract: A first network device may receive, from a second network device, a first policy control create request and may provide, to the second network device, a common policy control request trigger. The first network device may receive a second policy control create request associated with a user equipment (UE) and may cause a UE policy to be provided to the UE. The first network device may receive, from a third network device, a third policy control create request and may provide a network device policy to the third network device. The first network device may receive, from the second network device, a policy control update request based on the common policy control request trigger and may generate an updated UE policy or an updated network device policy based on the policy control update request.

Abstract: A network device executes an account management function that pre-authorizes network service unit consumption by multiple subscribers that are members of a same, shared network service account. The account management function receives, from multiple charging systems distributed within the network, network unit consumption charges associated with each of the multiple subscribers, where the network device is centrally located within a network relative to multiple locations associated with the plurality of charging systems. The account management function updates a consumption counter for the same, shared network service account based on the network unit consumption charges associated with the multiple subscribers received from the multiple charging systems distributed within the network.

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: Methods, devices, and computer-readable mediums may provide receiving, at a request to establish an access and mobility (AM) policy control association in relation to an establishment of a data session requested by a user associated with a user equipment (UE) device; generating a query to a network device via a network interface, for AM policy control data and for at least one of UE policy control data or session management (SM) policy control data; receiving the AM policy control data and the at least one of the UE policy control data or the SM policy control data from the network device, creating the AM policy control association based on the received AM policy control data; and storing the at least one of the UE policy control data or the SM policy control data.

Abstract: A network device of a core network may maintain a mapping table that maps core network slices with quality of service (QoS) class identifiers (QCIs) based on service profile identifiers (SPIDs), and may receive, from a user device, a request for service with a particular QCI included in the QCIs of the mapping table. The network device may identify a particular SPID of the SPIDs in the mapping table based on the particular QCI of the service, and may generate a flow request based on the particular SPID. The network device may cause the flow request to be provided to a radio access network (RAN) associated with the user device, to cause the RAN to select a RAN slice for provision of the service to the user device.

Abstract: Systems and methods described herein allow mobile network operators to provide an adaptive quality of service (QoS) approach for application providers. A network device in a core network receives a QoS monitoring report based on QoS monitoring by an access station. The QoS monitoring report includes data for QoS parameters for network services in a default QoS flow supporting a protocol data unit (PDU) session. Based on the QoS monitoring report, the network device determines if the default QoS flow supports a required service level for the PDU session. When the network device determines that the default QoS flow does not support the required service level for the PDU session, the network device automatically activates a dedicated QoS flow to support the PDU session with the required service level.

Abstract: A network device may select a first user plane function for establishing, with a user equipment, a protocol data unit session with a single flow and may receive an application function trigger associated with a first new flow for a first application of the user equipment. The network device may select a second user plane function for the first new flow and may create a first traffic filter for the first new flow. The network device may cause the first traffic filter to be provided to the user equipment so that first application traffic is routed, based on the first traffic filter, to the second user plane function and a first multi-access edge computing device associated with the second user plane function.

Abstract: A system described herein may provide a technique for a policy and/or rules element of a core network, such as a Policy Control Function (“PCF”), to identify a first network slice with which a communication session between a User Equipment (“UE”) and a core network, such as a protocol data unit (“PDU”) session, is associated. The policy and/or rules element may identify a second network slice with which the communication session should be associated, such as based on traffic monitoring, network congestion monitoring, or other criteria, and may output an indication, indicating a second network slice, to a session control element, such as an Session Management Function (“SMF”). The session control element may cause the communication session to be moved from the first network slice to the second network slice based on receiving the indication.

Abstract: A method may include storing information identifying network slices associated with transmitting data in a network, information identifying a maximum number of user equipment (UE) devices that can be registered for each network slice and/or information identifying a maximum number of data sessions that can be established for each network slice based on locations or areas associated with the UE devices. The method may also include receiving, from a first UE device, a registration request or a request for a data session and identifying a first slice associated with the first UE device. The method may further include determining, based on a location or area associated with the first UE device, whether a maximum number of UE devices that can be registered for the first slice has been reached and/or a maximum number of data sessions that can be served by the first slice has been reached.

Abstract: A device may include a processor configured to determine that Quality of Service (QoS) monitoring is to be performed for a communication session; generate a QoS monitoring policy for the communication session; and provide the QoS monitoring policy to a Session Management Function (SMF) associated with the communication session. The processor may be further configured to receive a QoS monitoring report for the communication session from the SMF and perform an action based on the received QoS monitoring report.

Abstract: A network device may receive a PDU session create message associated with establishing a PDU session with a user device and via a RAN, and may receive a first 5QI value and a second 5QI value associated with the PDU session. The network device may attempt to establish the PDU session with the first 5QI value and via the RAN, and may receive an indication that the first 5QI value is not supported for establishing the PDU session. The network device may cause the PDU session to be established with the second 5QI value, and via the RAN, based on the indication that the first 5QI value is not supported for establishing the PDU session.

Abstract: A method, a network device, and a non-transitory computer-readable storage medium are described in relation to an event reporting service. The event reporting service may enable network devices, such as an application function, to subscribe to usage reporting in which notifications for a usage event may be reported periodically or non-singularly. The event reporting service may include data instances in messages exchanged between core network devices that configures the usage and event notification.

Abstract: A device may include a processor configured to determine, in a core network associated with a radio access network, that a user equipment (UE) device, associated with an enterprise, has attached to the core network via a base station in the radio access network. The processor may be further configured to obtain a mapping between a plurality of applications associated with the enterprise and a plurality of Quality of Service (QoS) classes; identify an application, of the plurality of applications, for a communication session associated with the UE device; select a QoS class, from the plurality of QoS classes based on the identified application and the obtained mapping; and process messages associated with the communication session based on the selected QoS class.