Cisco Technology, Inc.

Anal Srivastava

Sangram Kishore Lakkaraju

Srinath Gundavelli

Rajesh S Pazhyannur

Vimal Srivastava

Shailender Potharaju

Anand K Oswal

Anton Okmyanskiy

Oliver James Bull

Mickael James Graham

Eric Philippe Hamel

Mahavir Dagdulal Karnavat

Sandeep Gautam

A method is provided for avoiding context transfers by a first Access and Mobility Management Function (AMF) connected to a first gNB to a second AMF when a user equipment (UE) in idle mode moves from the first gNB to a second gNB. The method may include provisioning the first AMF and the second AMF with the same tracking area identity (TAI), the first AMF and the second AMF s being connected to a respective enterprise gNB. The method may also include configuring the 5G packet core network comprising a session management function (SMF) in communications with the first AMF and the second AMF, to avoid transferring a UE context from the first AMF to the second AMF when the user equipment (UE) in the idle mode moves from a first AMF to the second AMF. The UE context remains with the first AMF.

Inter access and mobility management function idle mode mobility optimization

A target Access and Mobility Management Function (AMF) switches the path for network traffic to a User Equipment (UE) in an inter-AMF mobility event. The target AMF obtains a path switch request from a target next generation Node B (gNB). The path switch request includes a UE identifier and a source AMF identifier. The target AMF compares the source AMF identifier with a target AMF identifier, and responsive to a determination that the source AMF identifier is different than the target AMF identifier, the target AMF provides a UE context transfer request to the source AMF. The target AMF obtains the UE context from the source AMF and processes the path switch request to update a core network path for a session of the UE. The target AMF also provides a path switch response to the target gNB.

Inter-AMF connected mode handover optimization

A first access and mobility management function (AMF) in a network receives, from user equipment (UE), a registration request listing a first network slice and a second network slice. Upon determining that the first AMF supports the first, but not the second, network slice, the first AMF causes selection of (i) the first AMF as a session and mobility management (SM)-AMF to perform mobility management, and first session management signaling for the first network slice; and (ii) a second AMF as a session management only (SO)-AMF to perform only second session management signaling for the second network slice. The first AMF, acting as SM-AMF, performs the first session management signaling for a first data session on the first network slice, while the second AMF, acting as SO-AMF, performs only the second session management signaling for a second data session on the second network slice.

Dual access and mobility management function support for supporting optimized 5G core deployments

In one example embodiment, a server obtains a first indication of a first identifier associated with a user equipment in a wireless network, and first telemetry data associated with the first indication. The server obtains, from a network entity including a base station entity serving wireless communication in the wireless network, a second indication of the first identifier and second telemetry data associated with the second indication. The server determines that the first indication and the second indication match. In response to determining that the first indication and the second indication match, the server correlates the first telemetry data and the second telemetry data.

Telemetry data correlation for device-level assurance in wireless networks

An enterprise private network includes a simplified Third Generation Partnership Project (3GPP) core architecture for interworking between an Evolved Packet System (EPS) and a Fifth Generation (5G) system (5GS). The architecture includes an Evolved Packet Core (EPC) control plane (CP) (EPC CP) unit and a 5G core (5GC) CP (5GC CP) unit. The 5GC CP unit receives, from the EPC CP unit via an N26 interface, a message indicating a forward relocation request responsive to an indication of a handover of a Packet Data Network (PDN) connection at a user plane node from the EPS to the 5GS. The 5GC CP node establishes a Protocol Data Unit (PDU) session corresponding to the PDN connection based on PDN connection information in the message, which includes establishing a Quality of Service (QoS) Flow corresponding to an EPS bearer, and manages the PDU session at the user plane node.

User equipment (UE) mobility between evolved packet system (EPS) and fifth generation (5G) system (5GS) using a simplified 3GPP core architecture for interworking

A radio access network (RAN) of a neutral host network (NHN) provides communications in a plurality of small cells, and is a shared resource with shared access by a plurality of mobile network operators (MNOs) via a multi-operator core network (MOCN). A base station maintains a neighbor list of small cell frequencies of neighboring small cells of a small cell, and broadcasts, to a user equipment (UE), a system information message which includes the neighbor list. The base station additionally maintains a plurality of operator-specific neighbor lists of one or more macro-cell frequencies of one or more neighboring macro-cells, where each such list is associated with a respective one of a plurality of macro-cellular networks of the MNOs. The base station transmits, to the UE, a message including a selected one of the operator-specific neighbor lists associated with an identified one of the mobile network operators of the UE.

Neighbor lists for use in multi-operator core network based neutral host networks

A method is provided in one embodiment and includes receiving a request for a session at a network element; communicating a query for whitelist data to a provisioning element; receiving the whitelist data at the network element; and communicating a message to an access point that communicated the request, where the message is indicative of whether the session is to be accepted or denied based on the whitelist data. In more specific implementations, the network element is a gateway configured to receive the whitelist data via a RADIUS access accept message. In addition, source Internet protocol (IP) address verification associated with the session can be executed before a wireless device associated with the access point is permitted access to a network.

System and method for whitelist management

A femto gateway maintains information about the location of femto cells and areas served by mobile switching centers. The gateway maintains a mapping so that it selects a desired mobile switching center (MSC) and SGSN that is likely to be used if the user equipment leaves the coverage area of the femto cell and enters a macro cell or vice versa.

Growing community of inventors

Cupertino, CA, United States of America

Anal Srivastava