Patent classifications
H04L2101/375
Domain name system (DNS) translations for co-located gateway user planes in wireless communication networks
To serve User Equipment (UEs) in a wireless communication network, a control-plane transfers a co-located User Plane Function (UPF) request for a wireless access point ID to a naming system. The naming system detects a co-location translation fault for the wireless access point ID and transfers the wireless access point ID to a controller. The controller determines co-located UPFs for the wireless access node. The controller transfers co-location translation information for the wireless access point ID and co-located UPF IDs to the naming system. The control-plane transfers another co-located UPF request for the wireless access point ID to the naming system. The naming system translates the wireless access point ID into the set of co-located UPF IDs. The naming system transfers the co-located UPF IDs to the control-plane. The control-plane signals the co-located UPFs to serve the UE over the wireless access point.
Static IP handling per access point name
A cellular communication system uses a policy control rule function (PCRF) to allow or deny a particular user or user group access to a given access point name (APN). An allowed APN may support static IP address assignment for that user/user group. By restricting requested APNs via a test in the PCRF, frequent changes to the user's home service server (HSS)/home location registry (HLR) supporting static IP address can be avoided while ensuring that designated users will have access to an APN that supports the needed IP address pool.
UE Mobility Across Super-Cells
Systems and methods are disclosed for a 3G gateway. In a first embodiment, a method is disclosed for a network, comprising: receiving a relocation request message at a home nodeB gateway (HNBGW), the HNBGW coupled to an operator core network, the relocation request message including a target super cell identifier and a user equipment (UE) identifier; sending a second relocation request message from the HNBGW to a coordinating node, the coordinating node having as its identifier the target super cell identifier; querying a lookup table at the coordinating node using the UE identifier to determine a target cell identifier; replacing, in the second relocation request message, the target super cell identifier with the target cell identifier to create a third relocation request message; and sending the third relocation request message to a target cell identified by the target cell identifier.
Systems and methods for providing low latency services via an evolved packet core network
A controller may create pseudo-slices to provide differentiated levels of service and/or execution of services at different edge locations within an Evolved Packet Core (“EPC”) network based on existing identifiers that are used to configure control plane and/or user plane function of the network. Each pseudo-slice may allow User Equipment (“UE”) to directly exchange user plane traffic with remote nodes in the core network for latency insensitive services, or with local nodes at the closer edge locations for low latency services. The different classes of service provided by the controller may be based on an Access Point Name (“APN”), Quality-of-Service Class Identifier (“QCI”), Service Provider Identifier (“SPID”), Allocation and Retention Priority (“ARP”), and/or other request or profile identifiers. The controller may also create pseudo-slices to leverage Fifth Generation (“5G”) connectivity when exchanging the user plane traffic in an EPC network that supports 5G Non-Standalone Access (“NSA”).
EDGE COMPUTING MANAGEMENT DEVICE AND OPERATING METHOD OF EDGE COMPUTING MANAGEMENT DEVICE
The present disclosure relates to an edge computing (multi-access edge computing, MEC) technology and, to an edge computing management device and an operating method of an edge computing management device, which provide a data roaming service by utilizing an edge computing cloud (MEC cloud) that exists in a communication provider network.
UE AND COMMUNICATION CONTROL METHOD
A user equipment (UE) with a transmission/reception unit is provided. The UE comprises: when a timer for a Single Network Slice Selection Assistance Information (S-NSSAI) and a Data Network Name (DNN) is operating, the transmission/reception unit initiates an Evolved Packet System (EPS) Session Management (ESM) procedure in the EPS by using a Access Point Name (APN); the APN is same as the DNN; and the transmission/reception unit receives a value of the timer in a Protocol Data Unit (PDU) session establishment reject message.
Systems and methods for providing low latency services via an evolved packet core network
A controller may create pseudo-slices to provide differentiated levels of service and/or execution of services at different edge locations within an Evolved Packet Core (“EPC”) network based on existing identifiers that are used to configure control plane and/or user plane function of the network. Each pseudo-slice may allow User Equipment (“UE”) to directly exchange user plane traffic with remote nodes in the core network for latency insensitive services, or with local nodes at the closer edge locations for low latency services. The different classes of service provided by the controller may be based on an Access Point Name (“APN”), Quality-of-Service Class Identifier (“QCI”), Service Provider Identifier (“SPID”), Allocation and Retention Priority (“ARP”), and/or other request or profile identifiers. The controller may also create pseudo-slices to leverage Fifth Generation (“5G”) connectivity when exchanging the user plane traffic in an EPC network that supports 5G Non-Standalone Access (“NSA”).
STATIC IP HANDLING PER ACCESS POINT NAME
A cellular communication system uses a policy control rule function (PCRF) to allow or deny a particular user or user group access to a given access point name (APN). An allowed APN may support static IP address assignment for that user/user group. By restricting requested APNs via a test in the PCRF, frequent changes to the user's home service server (HSS)/home location registry (HLR) supporting static IP address can be avoided while ensuring that designated users will have access to an APN that supports the needed IP address pool.
Methods, systems, and computer readable media for supporting mobile originated data multicasting in a communications network
Methods, systems, and computer readable media for supporting mobile originated data multicasting in a communications network are disclosed. One method includes receiving, from a consumer network function (NF) in a communications network, a deliver request message containing mobile originated (MO) data corresponding to a protocol data unit (PDU) session, wherein NIDD context information stored at NEF and referred by a context identifier in the deliver request message includes a subscriber identifier and a data network identifier associated with a user device requesting the PDU session and determining that a rule entry belonging to a plurality of rule entries contained in a multicasting ruleset matches at least one of the subscriber identifier and the data network identifier included in the NIDD context information that is stored at the NEF and referred by the context identifier in the deliver request message. The method further includes accessing a list of NF identity objects in the rule entry in response to determining the rule entry matches at least one of the subscriber identifier and/or the data network identifier and delivering the MO data to each of a plurality of NF endpoints specified in the rule entry in accordance with a routing condition indicated in each of the NF identity objects respectively associated with each of the NF endpoints.
Slice allocation and interface to applications
A user equipment (UE) modem stores a route selection policy (URSP), the URSP associating each of a plurality of data network name (DNN) identifiers and a corresponding slice, wherein a first DNN identifier (ID) is associated with a first DNN and a first slice and a second DNN ID is associated with the first DNN and a second slice different than the first slice. The modem establishes a first protocol data unit (PDU) session with the first DNN and the first slice in response to receiving a first indication to start a first network interface associated with the first DNN ID. The modem establishes a second PDU session with the first DNN and the second slice in response to receiving a second indication to start a second network interface associated with the second DNN ID.