Abstract: A wireless communication network handles Session Management Function (SMF) outage in a Tracking Area (TA). An external SMF that is outside the TA registers with an internal Network Repository Function (NRF) that is inside in the TA. The internal NRF detects the SMF outage for an internal SMF inside the TA. The internal NRF receives an SMF request from an internal Access and Mobility Management Function (AMF) inside the TA. In response to the SMF outage, the internal NRF transfers an SMF response to the internal AMF that indicates the external SMF. The external SMF receives network signaling from the internal AMF and responsively directs an external User Plane Function (UPF) that is outside the TA to exchange user data with internal wireless access nodes that are inside the TA.

Abstract: Systems, devices, and techniques described herein relate to migrating a communication session from a path including a stressed user plane function (UPF) to a path including a replacement UPF. A communication session may traverse a first path including the first UPF. After establishing the communication session, the first UPF may be determined to be stressed. In response, the communication session can be proactively migrated to a second path including a second UPF. According to various implementations, the existing communication session can be maintained during the migration, thereby substantially eliminating interruptions caused by the stressed first UPF.

Abstract: Policy based dual connectivity traffic steering is described herein. A master Long-Term Evolution (LTE) base station may operate in conjunction with a secondary New Radio (NR) base station to provide dual connectivity to user equipment (UE) operating in an environment. The LTE base station can steer traffic between the LTE base station and the NR base station based at least in part on policy information received at the LTE base station. The policy information can indicate, for a particular UE and for a particular Quality of Service (QoS) Class Identifier (QCI), whether the LTE base station can transfer a communication to the NR base station. Thus, traffic steering determinations can be based on the policy information, quality identifiers, device capability, signal strength(s), load level(s), and the like, thereby providing a flexible framework for steering wireless traffic in a dual connectivity environment.

Abstract: Techniques for handling emergency calls in a fifth generation (5G) telecommunication network are discussed herein. Some 5G-compatible user equipment (UEs) support 5G emergency calls, while other 5G-compatible UEs do not support 5G emergency calls. If a UE supports 5G emergency calls, the 5G telecommunication network may instruct the UE during network registration to use the 5G telecommunication network for any emergency calls attempted later. However, if a UE does not support 5G emergency calls, the 5G telecommunication network may instruct the UE during network registration to instead use Long-Term Evolution (LTE) emergency fallback procedures for emergency calls. Such LTE emergency fallback procedures can cause the 5G telecommunication network to steer the UE to LTE for an emergency call almost immediately after receiving a service request from the UE, even though the 5G telecommunication network itself supports emergency calls.

Abstract: Systems, devices, and techniques described herein relate to prioritizing access by first user equipment (UEs) connected to a first radio access technology (RAT) type over access by second UEs connected to a second RAT type responsive to a failure of a core network node. A node of the core network, such as a session management node, may determine that another node of the core network has failed based on a negative response or no response from that other node. The node may then prioritize access based on RAT types of requesting UEs.

Abstract: Restricting mobility between networks by identifying and rejecting incoming mobility events (e.g. handovers) from unknown cell sites based on a cellID included in a handover request. Core network nodes e.g. MME, AMF, SMF, can detect and reject the incoming mobility events by comparing Cell ID with a white list or referring to a database. This improves over current 3GPP specifications and network vendor implementations that support restriction policies on the source but not on the target.

Abstract: Systems, devices, and techniques described herein relate to migrating a communication session from a path including a stressed user plane function (UPF) to a path including a replacement UPF. A communication session may traverse a first path including the first UPF. After establishing the communication session, the first UPF may be determined to be stressed. In response, the communication session can be proactively migrated to a second path including a second UPF. According to various implementations, the existing communication session can be maintained during the migration, thereby substantially eliminating interruptions caused by the stressed first UPF.

Abstract: Systems, devices, and techniques described herein relate to efficient Evolved Packet System (EPS) fallback. A method may include receiving a rejection message that indicates a rejection to set up a call through a 5th Generation (5G) network by a 5G Radio Access Network (RAN). In response to receiving the rejection message, the method may include transmitting a request to establish a dedicated bearer through a 4th Generation (4G) network. A confirmation that the second dedicated bearer has been established through the 4G network may be received within a predetermined time after transmitting the request.

Abstract: In a telecommunication network, network slices can be identified by slice identifiers used within a core network. The same slice identifiers can also be used by elements of an IP Multimedia Subsystem (IMS) to identify the network slices. For example, a Home Subscriber Server (HSS) can be provisioned with user data associated with a user equipment (UE), including a slice identifier of a network slice that the UE is assigned to use. The HSS can provide the slice identifier to an S-CSCF in the IMS when the UE registers with the IMS. The S-CSCF can share the slice identifier with other IMS elements, such as a P-CSCF and/or one or more application servers. Accordingly, the IMS elements can determine key performance indicators (KPIs) and perform other operations in association with usage of network slices by UEs, based on the same slice identifiers used within the core network.

Abstract: Systems, devices, and techniques described herein relate to intelligently allocating network resources to Quality of Service (QoS)-sensitive data traffic. An example method includes identifying a request to deliver QoS-sensitive services to a User Equipment (UE) over at least one delivery network. The at least one delivery network may include at least one reserved resource and at least one pooled resource. The QoS-sensitive services are determined to be delivered over the at least one pooled resource. In addition, delivery of the QoS-sensitive services is caused over the at least one pooled resource.

Abstract: Restricting mobility between networks by identifying and rejecting incoming mobility events (e.g. handovers) from unknown cell sites based on a cellID included in a handover request. Core network nodes e.g. MME, AMF, SMF, can detect and reject the incoming mobility events by comparing Cell ID with a white list or referring to a database. This improves over current 3GPP specifications and network vendor implementations that support restriction policies on the source but not on the target.

Abstract: Systems, devices, and techniques described herein relate to efficient Evolved Packet System (EPS) fallback. A method may include receiving a rejection message that indicates a rejection to set up a call through a 5th Generation (5G) network by a 5G Radio Access Network (RAN). In response to receiving the rejection message, the method may include transmitting a request to establish a dedicated bearer through a 4th Generation (4G) network. A confirmation that the second dedicated bearer has been established through the 4G network may be received within a predetermined time after transmitting the request.

Abstract: Systems, devices, and techniques described herein relate to migrating a communication session from a path including a stressed user plane function (UPF) to a path including a replacement UPF. A communication session may traverse a first path including the first UPF. After establishing the communication session, the first UPF may be determined to be stressed. In response, the communication session can be proactively migrated to a second path including a second UPF. According to various implementations, the existing communication session can be maintained during the migration, thereby substantially eliminating interruptions caused by the stressed first UPF.

Abstract: Systems, devices, and techniques described herein relate to intelligently allocating network resources to Quality of Service (QoS)-sensitive data traffic. An example method includes identifying a request to deliver QoS-sensitive services to a User Equipment (UE) over at least one delivery network. The at least one delivery network may include at least one reserved resource and at least one pooled resource. The QoS-sensitive services are determined to be delivered over the at least one pooled resource. In addition, delivery of the QoS-sensitive services is caused over the at least one pooled resource.

Abstract: A system, e.g., associated with a telecommunications network, includes first and second registry devices. In some examples, the first registry device receives a registration message. The second registry device receives a query specifying a type (NFType) of a network function and forwards the query to the first registry device based at least in part on the NFType. The first registry device responds, and the second registry device forwards the response. In some examples, the query specifies a service class and the second registry device forwards the query based at least in part on the service class. In some examples, the first registry device sends an indication of the registration to the second registry device, and the second registry device responds to the query based at least in part on the received indication and on at least one of an NFType or a service class of the query.

Abstract: Systems, devices, and techniques described herein relate to prioritizing access by first user equipment (UEs) connected to a first radio access technology (RAT) type over access by second UEs connected to a second RAT type responsive to a failure of a core network node. A node of the core network, such as a session management node, may determine that another node of the core network has failed based on a negative response or no response from that other node. The node may then prioritize access based on RAT types of requesting UEs.

Abstract: A telecommunication system can include a network flow controller (e.g., SMF) and a network-charging node (e.g., CHF). The flow controller can generate a first charging-event record associated with a network session. The flow controller can detect an outage at least partly by determining that no network-charging node is available to receive the first charging-event record and, in response, mark the first charging-event record to provide a first marked charging-event record. The flow controller can store the first marked charging-event record in a buffer. After the marking, the flow controller can determine that a network-charging node is available to receive the first marked charging-event record, and, in response, send the first marked charging-event record to the network-charging node. The network-charging node can determine a charging-data record indicating occurrence of an event during the outage.

Abstract: A solution for establishing a data traffic (e.g., PDU) session for a user equipment (UE) on a network (e.g., 5G cellular network) comprises receiving, by an access node (e.g., AMF), from a network repository (e.g., NRF), identification of a plurality of available session management nodes (e.g., SMFs), wherein the identification of the plurality of available session management nodes indicates whether each session management node supports a first traffic type or a second traffic type (e.g., IPv4 or (IPv6); determining, by the access node, a requested traffic type identified by the UE; determining a match between supported and requested traffic types; based at least on the match, selecting a session management node from the plurality of available session management nodes; and based at least on selecting the session management node, establishing the traffic session with the UE and the selected session management node.

Abstract: A solution for establishing a data traffic (e.g., PDU) session for a user equipment (UE) on a network (e.g., 5G cellular network) comprises receiving, by a session management node, a request for the data traffic session for the UE; determining a requested traffic type for the data traffic session, wherein the requested traffic type comprises a first traffic type or a second traffic type; determining whether the session management node is connected to a first user plane function that can support the requested traffic type; based at least on determining that the first user plane function cannot support the requested traffic type, connecting, by the session management node, to a second user plane function that can support the requested traffic type; and based at least on connecting to the second user plane function, establishing the requested data traffic session for the UE using the second user plane function.

Abstract: A solution for establishing a data traffic (e.g., PDU) session for a user equipment (UE) on a network (e.g., 5G cellular network) comprises receiving, by a session management node, a request for the data traffic session for the UE; determining a requested traffic type for the data traffic session, wherein the requested traffic type comprises a first traffic type or a second traffic type; determining whether the session management node is connected to a first user plane function that can support the requested traffic type; based at least on determining that the first user plane function cannot support the requested traffic type, connecting, by the session management node, to a second user plane function that can support the requested traffic type; and based at least on connecting to the second user plane function, establishing the requested data traffic session for the UE using the second user plane function.