Abstract:
A system and method for dynamic enablement of a RLC mode of a Data Radio Bearer (DRB) based on UE radiofrequency (RF) conditions. A threshold value for a network characteristic is provided to a gNodeB. Changes in the network characteristic correlates to changes in RF channel conditions of the UE. The trigger configures the gNodeB to identify when the network characteristic meets the threshold value for selectively controlling operation of the gNodeB at one of a plurality of different operation modes including an initial radio link control (RLC) mode based on the network characteristic. A Protocol Data Unit (PDU) session is established with the gNodeB operating in an initial RLC mode with the possibility to dynamically switch to a different RLC mode based on RF channel conditions.
Abstract:
Techniques are presented herein for provisioning network devices based on device type. In one example, a packet core gateway of a cellular core network identifies a device type of a network device and obtains an indication to provision the network device. In response to obtaining the indication to provision the network device, the packet core gateway provisions the network device with one or more network resources based on the device type of the network device.
Abstract:
In one illustrative example, a user plane function (UPF) node may receive, from a controller node, a configuration of an allocated bandwidth for a predefined service classification associated with different predefined types of a communication resource at the UPF node, for each one of a plurality of different predefined service classifications associated with different predefined types of the communication resource. The UPF node may monitor a total bandwidth usage for each predefined service classification. Based on identifying that the total bandwidth usage exceeds a threshold limit, the UPF node may send, to the controller node, a message which indicates a request for readjusting the allocated bandwidth for the predefined service classification, and indicating the total bandwidth usage. The different predefined types of the communication resource may be different network slices at the UPF node, or different Quality of Service (QoS) Flow resource types at the UPF node, as examples.
Abstract:
Systems, methods, and computer-readable media are provided for an efficient roaming management method using a single association identifier token for associating with different access points. In one aspect of the present disclosure, a network controller includes memory having computer-readable instructions stored therein and one or more processors. The one or more processors are configured to execute the computer-readable instructions to receive a request from an endpoint to connect to a first access point; generate association identification token (e.g., PMK and PMKID) for the endpoint to connect to the first access point; and distribute the association identification token to a second access point prior to the endpoint attempting to connect to the second access point, the association identification token being used by the second access point to validate a subsequent request by the endpoint to connect to the second access point.
Abstract:
An example method is provided and may include retrieving by a user equipment (UE) an access point (AP) Media Access Control (MAC) address for an AP to which the UE is connected; reporting location information for the UE to an evolved Packet Data Gateway over an SWu interface using Internet Key Exchange version 2 (IKEv2) protocol, wherein the location information includes, at least in part, a UE location in GPS coordinates, a service set identifier, the retrieved AP MAC address and cell identity information for the UE; and populating a location database with the location information. The method can include embedding the location information in an identity initiator (Idi) of an IKE Authentication Request (IKE_AUTH_REQ) message using a Network Access Identifier (NAI) and communicating the location information from the ePDG to a PGW over an S2b interface using a private extension information element of GPRS Tunneling Protocol version 2 (GTPv2).
Abstract:
Techniques are presented herein for provisioning network devices based on device type. In one example, a packet core gateway of a cellular core network identifies a device type of a network device and obtains an indication to provision the network device. In response to obtaining the indication to provision the network device, the packet core gateway provisions the network device with one or more network resources based on the device type of the network device.
Abstract:
A user plane function (UPF) node may receive a packet for traffic associated with a user equipment (UE). During packet classification, the UPF node may identify that a packet filter for the packet is not found in a packet filter set of an existing Quality of Service (QoS) Flow. In response, the UPF node may configure the packet filter in the packet filter set of the QoS Flow based on a flow tuple of the packet. The UPF node may send, to a control plane function node, a message which indicates a request for adding the flow tuple to the QoS Flow. The message may be for triggering communication of a message which indicates a session modification command for receipt by the UE, for adding an uplink packet filter that is based on the flow tuple for the QoS Flow.
Abstract:
An example method is provided and may include receiving a DIAMETER-based error over an SWm interface by a first evolved packet data gateway (ePDG) for a user equipment (UE) attempting to connect to the first ePDG; determining an Internet Key Exchange version two (IKEv2) error type corresponding to the DIAMETER-based error; and communicating the IKEv2 error type to the UE over an SWu interface. In some cases, the IKEv2 error type can be included in a notify payload or in a vendor ID payload for an IKE authentication response (IKE_AUTH_RESP) message. By distinguishing the IKEv2 error type, the UE can determine whether the error is a temporary or a permanent type and can determine whether to attempt to connect again to the first ePDG after a period of time or attempt to connect to another ePDG, which can help to reduce unnecessary signaling and provide better connectivity and user experience.
Abstract:
An example method is provided and may include receiving a DIAMETER-based error over an SWm interface by a first evolved packet data gateway (ePDG) for a user equipment (UE) attempting to connect to the first ePDG; determining an Internet Key Exchange version two (IKEv2) error type corresponding to the DIAMETER-based error; and communicating the IKEv2 error type to the UE over an SWu interface. In some cases, the IKEv2 error type can be included in a notify payload or in a vendor ID payload for an IKE authentication response (IKE_AUTH_RESP) message. By distinguishing the IKEv2 error type, the UE can determine whether the error is a temporary or a permanent type and can determine whether to attempt to connect again to the first ePDG after a period of time or attempt to connect to another ePDG, which can help to reduce unnecessary signaling and provide better connectivity and user experience.
Abstract:
An example method is provided and may include retrieving by a user equipment (UE) an access point (AP) Media Access Control (MAC) address for an AP to which the UE is connected; reporting location information for the UE to an evolved Packet Data Gateway over an SWu interface using Internet Key Exchange version 2 (IKEv2) protocol, wherein the location information includes, at least in part, a UE location in GPS coordinates, a service set identifier, the retrieved AP MAC address and cell identity information for the UE; and populating a location database with the location information. The method can include embedding the location information in an identity initiator (Idi) of an IKE Authentication Request (IKE_AUTH_REQ) message using a Network Access Identifier (NAI) and communicating the location information from the ePDG to a PGW over an S2b interface using a private extension information element of GPRS Tunneling Protocol version 2 (GTPv2).