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:
The present technology is directed to routing a user equipment (UE) to a network node, for example, a gNB or ng-eNB that supports a slice requirement of the UE. A first network node can receive a Radio Resource Control (RCC) connection request from a UE, and can determine that a slice requirement of the UE is not supported by the first network node. The first network node can further select a second network node that supports the slice requirement of the UE, and route the UE to connect to the second network node.
Abstract:
A first data plane is established between a user equipment device and a gateway device, wherein the user equipment device comprises a 3rd Generation Partnership Project (3GPP) user equipment device, and wherein the first data plane comprises a 3GPP data plane. A second data plane is established between the gateway device and an anchor device, wherein the second data plane comprises a Proxy Mobile Internet Protocol version 6 (PMIPv6) data plane. Mobility management is performed for the user equipment device via communications between the gateway device and the anchor device.
Abstract:
Systems and methods for providing access prioritization to a private Long Term Evolution (LTE) network operating in a Citizens Broadband Radio Service (CBRS) spectrum include receiving, at a network device of the private Long Term Evolution (LTE) network, a functional group associated with a user equipment (UE) and a traffic load of a cell of the private LTE network associated with the UE. An access priority associated with the functional group and the traffic load is determined and provided to a CBRS access point (AP) which controls access to the cell. The access priority indicates to the CBRS AP a priority with which the UE is allowed to access the cell and can include a high priority, a low priority, or no access indication.
Abstract:
Systems and methods for providing access prioritization to a private Long Term Evolution (LTE) network operating in a Citizens Broadband Radio Service (CBRS) spectrum include receiving, at a network device of the private Long Term Evolution (LTE) network, a functional group associated with a user equipment (UE) and a traffic load of a cell of the private LTE network associated with the UE. An access priority associated with the functional group and the traffic load is determined and provided to a CBRS access point (AP) which controls access to the cell. The access priority indicates to the CBRS AP a priority with which the UE is allowed to access the cell and can include a high priority, a low priority, or no access indication.
Abstract:
Techniques are described to provide a network location service for a user equipment (UE) when the UE is not served by a 3GPP radio; thereby enabling radio resource selection by the UE for Autonomous PC5 based communications. In one example, a method includes receiving, by a mobility element of a network, an attach request from a UE, wherein the attach request indicates an attach type associated with a network location service. The method may further include communicating, based on the attach type being associated with the network location service, an attach accept to the UE to trigger a location request for the UE, wherein the attach accept is communicated to the UE without the mobility element authenticating the UE; and communicating location information to the UE based on the location request.
Abstract:
Systems, methods, and computer-readable media are provided for modifying a network service of a requesting network member. A request, received from the requesting member, can include an identification of a sponsoring network member for a requested network service modification. A group can be generated and associated with the requesting member and with the sponsoring member. The group may also include a group policy referencing the requested network service modification. The sponsoring member can be provided with an activation key for activating the network service modification and a first network policy can be applied to the requesting member and a second network policy can be applied to the sponsoring member.
Abstract:
In one embodiment a router connects to a cellular network using at least one authentication credential stored on a smart card of the router. The router receives, from a client device coupled to the router, a Session Initiation Protocol (SIP) request to register with an Internet Protocol Multimedia Subsystem (IMS) network coupled to the cellular network. The router sends a SIP registration request for the client device to the IMS network, the SIP registration request comprising authorization information associated with the router, wherein the authorization information associated with the router is used by the IMS network to register the client device with the IMS network.
Abstract:
An example method is provided in one example embodiment and may include receiving a session request for a user equipment (UE) at a node, wherein the session request includes a timestamp for the UE and a retry count; determining if the session request is a stray session request; and maintaining session information for an existing session for the UE at the node if the session request is a stray session request. The method can include identifying the received session request as a stray request if the timestamp received in the request is less than a timestamp stored for an existing session for the UE. The method can also include identifying the received request as a stray request if the timestamp received is equal to the timestamp stored for the existing session and if the retry count received is less than or equal to a retry count stored for the session.
Abstract:
An example method is provided in one example embodiment and may include receiving an indication of a radio access technology (RAT) change for a user equipment (UE); determining availability of a preferred RAT type for a policy related rule associated with the UE, wherein the policy related rule includes, at least in part, the preferred RAT type for one or more service data flows for the UE; and configuring the one or more service data flows for the UE based, at least in part, on a change in availability of the preferred RAT type following the RAT change. In at least one case, the method can include routing downlink packets to the UE using the one or more service data flows for the preferred RAT type if the preferred RAT type is available.