Abstract: A computer device may include a memory storing instructions and processor configured to execute the instructions to host a network function container that implements a microservice for a network function in a wireless communications network, wherein the network function container is deployed by a container orchestration platform; host a service proxy container associated with the network function container, wherein the service proxy container is deployed by the container orchestration platform; and configure the hosted service proxy container to apply a wireless network policy to the microservice for the network function. The processor may be further configured to intercept messages associated with the microservice for the network function using the configured service proxy container; and apply the wireless network policy to the intercepted messages using the configured service proxy container.

Abstract: A method, a network device, and a non-transitory computer-readable storage medium are described in relation to an EASDF secure service. The EASDF secure service may include a network-side service that may validate access and authorization to use a domain name system (DNS) resolver device, such as an edge application server discovery function. The network-side service may validate access and authorization of an end device based on tokens. The EASDF secure service may include an end device-side service that includes a token with a DNS query to the DNS resolver device. The end device-side service may further provide authorization regarding access and use of applications, networks, and application devices that host applications and/or assets by the end device at the end device. The end device-side service may determine access and/or authorization based on tokens and a validation procedure performed at the end device.

Abstract: Systems and methods provide for application-enabled multicast control. A network device receives first parameters for an application executed on a first user equipment (UE) device and receives second parameters for the application executed on a second UE device. The network device detects, based on the first and second parameters, a multicast opportunity for the application and provides, to an application server for the first UE device and the second UE device, a multicast target address to initiate multicast streaming to the first UE device and the second UE device.

Abstract: Systems and methods described herein provide dynamic network slicing. A network device receives, from an application server, application performance requirements for an application and receives capability and performance information of an existing network slice that is servicing a User Equipment (UE) device using the application. The network device determines, based on the capability and performance information, that a new network slice is needed to support the application performance requirements for the UE device; and sends a signal to initiate a slice creation process for the new network slice.

Abstract: A method, a network device, a system, and a non-transitory computer-readable storage medium are described in relation to an gateway type monitoring event service. The gateway type monitoring event service may include providing a current gateway type associated with an end device and a network to an application function. The current gateway type may be used by the application function to perform a network operation or procedure.

Abstract: A method, a network device, a system, and a non-transitory computer-readable storage medium are described in relation to an RAT type monitoring event service. The RAT type monitoring event service may include providing a current RAT type associated with an end device and a network to an application function. The RAT type monitoring event service may also include providing a notification to the application function when the end device changes its RAT type. The current RAT type may be used by the application function to perform a network operation or procedure. The application function may subscribe to a monitoring and event notification associated with the RAT type monitoring event service.

Abstract: In some implementations, a domain name system (DNS) server may receive, from a user equipment (UE), a DNS request message that indicates location information. The DNS server may select a node for the UE based on the location information. The DNS server may transmit, to the UE, an indication of the node.

Abstract: Systems and methods described herein enable network slice selection from different service providers using embedded Subscriber Identity Modules (eSIMs). A user equipment (UE) device stores a first eSIM associated with a first service provider of a first mobile network and a second eSIM associated with a second service provider of a second mobile network. The UE device also stores policy rules governing selection of the first eSIM and the second eSIM, wherein the policy rules limit use of second eSIM to a network slice on the second mobile network. The UE device initiates a session connection request associated with an application and directs the session connection request through one of the first eSIM or the second eSIM based on the policy rules.

Abstract: A method, a network device, and a non-transitory computer-readable storage medium are described in relation to an registration support service. The registration support service may include providing an end device with registration support information that may facilitate a re-registration of the end device with an access and mobility management function, a mobility management entity, or the like. The registration support information may include a time period and/or a location with which the end device may initiate a registration procedure. The registration support information may be generated based on historical behavior of the end device.

Abstract: One or more computing devices, systems, and/or methods for managing security associated with applications are provided. In an example, a central security gateway may determine first security policy information associated with a first application. The central security gateway may establish a first encrypted connection with a first device of the first application. The central security gateway may manage, based upon the first security policy information and using the first encrypted connection, security associated with the first application. The central security gateway may determine second security policy information associated with a second application. The central security gateway may establish a second encrypted connection with a second device of the second application. The central security gateway may manage, based upon the second security policy information and using the second encrypted connection, security associated with the second application.

Abstract: A method may include identifying network slices associated with transmitting data in a network and determining, by a routing device, that a failure associated with a path used to transmit data has occurred. The method may also include determining, by the routing device, whether the failure is associated with one of the plurality of network slices. The method may further include prioritizing, by the routing device, a route selection process in response to determining that the failure is associated with one of the plurality of network slices.

Abstract: A device may receive performance requirements for a service, and may receive RAN factors that influence a RAN, core factors that influence a core network, and transport factors that influence a transport network. The device may determine a RAN capability to satisfy the performance requirements, and may determine a core capability to satisfy the performance requirements. The device may determine a transport capability to satisfy the performance requirements, and may determine RAN configuration settings, core configuration settings, and transport configuration settings based on the RAN capability, the core capability, and the transport capability, respectively. The device may generate a RAN SON based on the RAN configuration settings, a core SON based on the core configuration settings, and a transport SON based on the transport configuration settings. The device may create a network slice based service area based on the RAN SON, the core SON, and the transport SON.

Abstract: A method, a device, and a non-transitory computer-readable storage medium are described in which an predictive discontinuous reception (DRX) bypass service is provided. The bypass service may provide flow control signaling that enables an uplink grant to be transmitted to an end device regardless of the DRX mode. The bypass service may provide for an immediate grant for uplink data and may improve latency. The bypass service may also provide flow control signaling for downlink data that may cause the end device to wake up from a DRX mode and receive downlink data. The bypass service also provides predictive scheduling that allows an external network, such as a multi-access edge computing network to establish a DRX-free downlink connection before completion of data processing. The flow control signaling may include a quality of service flow identifier value that correlates to the bypass service.

Abstract: One or more computing devices, systems, and/or methods for managing security associated with applications are provided. In an example, a central security gateway may determine first security policy information associated with a first application. The central security gateway may establish a first encrypted connection with a first device of the first application. The central security gateway may manage, based upon the first security policy information and using the first encrypted connection, security associated with the first application. The central security gateway may determine second security policy information associated with a second application. The central security gateway may establish a second encrypted connection with a second device of the second application. The central security gateway may manage, based upon the second security policy information and using the second encrypted connection, security associated with the second application.

Abstract: Systems and methods described herein provide for User Equipment (UE)-initiated authentication and authorization updates to Network Slice-Specific Authentication and Authorization (NSSAA). A network device in a core network receives a message from a user device outside of the core network, wherein the message includes a request to initiate a NSSAA procedure. The network device initiates the NSSAA procedure in response to the request. The systems and methods also provide for UE-initiated authorization revocation of NSSAA.

Abstract: A method, a network device, and a non-transitory computer-readable storage medium are described in relation to an EASDF secure service. The EASDF secure service may include a network-side service that may validate access and authorization to use a domain name system (DNS) resolver device, such as an edge application server discovery function. The network-side service may validate access and authorization of an end device based on tokens. The EASDF secure service may include an end device-side service that includes a token with a DNS query to the DNS resolver device. The end device-side service may further provide authorization regarding access and use of applications, networks, and application devices that host applications and/or assets by the end device at the end device. The end device-side service may determine access and/or authorization based on tokens and a validation procedure performed at the end device.

Abstract: A system described herein may receive a set of attributes associated with a particular User Equipment (“UE”), such as a location of the UE, Quality of Service (“QoS”) parameters, or UE power class. The system may identify a set of radio access network (“RAN”) configuration parameters based on the received set of attributes associated with the particular UE, wherein the RAN configuration parameters include radio frequency (“RF”) channel configuration parameters such as an orthogonal frequency-division multiplexing (“OFDM”) slot format. The system may provide the identified set of RAN configuration parameters to the RAN, and the RAN may utilize the RF channel configuration parameters included in the identified set of RAN configuration parameters to configure one or more channels between the RAN and the particular UE.

Abstract: Systems and methods described herein provide a slice management and prioritization service on a per user equipment (UE) device level. A network device in a core network may receive a notification that a UE device has exhausted a quota of available simultaneous data radio bearers (DRBs) and, afterwards, receive an indication that an application on the UE device has requested a new protocol data unit (PDU) session on a requested network slice that is not currently active for the UE device. The network device may identify relative priorities for the requested network slice and active network slices for the UE device; determine, based on the relative priorities, if the new PDU session can preempt a DRB for an active PDU session; and delete the active PDU session when it is determined the new PDU session can preempt a DRB for an active PDU session.

Abstract: A system comprises one or more devices. The devices may be configured to: receive information pertaining to a multicast broadcast service (MBS) session; identify, based on the information, User Equipment devices (UEs) that have joined the MBS session; identify at least two modulation schemes that are to be used by the UEs during the MBS session; receive multicast data from a network component; transmit, during the MBS session, the received multicast data to the UEs using the identified at least two modulation schemes.

Abstract: A network device may maintain a list of existing slice identifiers, associated with slices of a core network, that are in use in active UE sessions, and may receive a slice identifier associated with a slice of the core network and provided in a request to establish a session between a UE and the slice of the core network. The network device may determine whether the slice identifier matches an existing slice identifier included in the list, and may create a new network address, with an address of the network device and the slice identifier, based on the slice identifier failing to match an existing slice identifier included in the list. The network device may utilize the new network address to establish the session between the UE and the slice of the core network.