Abstract: A network may include a proxy-call session control function (P-CSCF) of a communication network that is configured to determine, record, and report on call types of calls originating from user equipment associated with the communication network. In some cases, the P-CSCF may determine the call type based on radio access technology types reported by the originating user equipment and/or by a proxy control function associated with the call.

Abstract: When initiating a Voice-over-IP (VoIP) communication session between an originating device (MO) and a terminating device (MT) on a packet-switched network, network components associated with the MO may encounter a failure when preparing resources for the session, such as a failure to establish a dedicated bearer with the MO. This might typically cause the system to abort the session. Instead, the network components are configured to detect the failure and to initiate a handover to a circuit-switched communication network so that the session may be conducted through the circuit-switched communication network. The failure may be detected by a component of a Long-Term Evolution (LTE) Radio Access Network (RAN) of the network, by a Mobility Management Entity (MME) of the network, or by some other network component. Single Radio Voice Call Continuity (SRVCC) procedures may be used to implement the handover.

Abstract: Systems and methods for categorizing communication data are described herein. The systems and methods enable an IMS core network to register a user equipment as a 5G-capable device and store communication data in a manner that differentiates the communication data from non-5G devices. Once identified as a 5G-capable device and information that 5G coverage is available is received, the registration message from the user equipment to the IMS core is modified to configure the IMS core to store the communication data as 5G communication data rather than non-5G communication data.

Abstract: In a telecommunication network, a Serving Call Session Control Function (S-CSCF) may be coupled with a Fifth Generation (5G) Equipment Identity Register (EIR) via an N17? interface. In some examples, the S-CSCF can use the N17? interface instead of a diameter protocol for communicating with the 5G-EIR. The S-CSCF can send a request to the 5G-EIR including a Permanent Equipment Identifier (PEI) associated with a user equipment (UE). In response, the S-CSCF can receive identity data indicative of whether the UE is authorized, not authorized, partially authorized, or unknown. Based on the identity data, the S-CSCF can authenticate a user equipment (UE) accessing a network. In some examples, the S-CSCF may route requests between a 5G-EIR and an EIR. In some examples, this authentication step can comprise a second-level authentication to identify stolen or fraudulent devices and to prevent such devices from accessing the network.

Abstract: When initiating a Voice-over-IP (VoIP) communication session between an originating device (MO) and a terminating device (MT) on a packet-switched network, network components associated with the MO may encounter a failure when preparing resources for the session, such as a failure to establish a dedicated bearer with the MO. This might typically cause the system to abort the session. Instead, the network components are configured to detect the failure and to initiate a handover to a circuit-switched communication network so that the session may be conducted through the circuit-switched communication network. The failure may be detected by a component of a Long-Term Evolution (LTE) Radio Access Network (RAN) of the network, by a Mobility Management Entity (MME) of the network, or by some other network component. Single Radio Voice Call Continuity (SRVCC) procedures may be used to implement the handover.

Abstract: A routing device of a telecommunications network can receive an initiation request of a communication session. The initiation request can include a destination identifier associated with a terminal. The routing device can query a responder for terminal-associated serving-network information. The routing device can then forward the initiation request to a serving network identified by the serving-network information. In some examples, the responder can query a registry for network-attachment information indicating a current media path associated with the terminal. The responder can provide the serving-network information based at least in part on the network-attachment information. In some examples, the destination identifier can include a global name, and the serving-network information can include an associated local name In some examples, the routing device can include an S-CSCF or ISBC, the responder can include an ENUM server, or the registry can include an HSS.

Abstract: Systems and methods for categorizing communication data are described herein. The systems and methods enable an IMS core network to register a user equipment as a 5G-capable device and store communication data in a manner that differentiates the communication data from non-5G devices. Once identified as a 5G-capable device and information that 5G coverage is available is received, the registration message from the user equipment to the IMS core is modified to configure the IMS core to store the communication data as 5G communication data rather than non-5G communication data.

Abstract: A routing device of a telecommunications network can receive an initiation request of a communication session. The initiation request can include a destination identifier associated with a terminal. The routing device can query a responder for terminal-associated serving-network information. The routing device can then forward the initiation request to a serving network identified by the serving-network information. In some examples, the responder can query a registry for network-attachment information indicating a current media path associated with the terminal. The responder can provide the serving-network information based at least in part on the network-attachment information. In some examples, the destination identifier can include a global name, and the serving-network information can include an associated local name In some examples, the routing device can include an S-CSCF or ISBC, the responder can include an ENUM server, or the registry can include an HSS.