Abstract: Solutions for providing a data traffic session with proxy-call session control function (P-CSCF) restoration include: receiving an indication, by an application server (AS), that a user equipment (UE) is registered with a first proxy node (e.g., a P-CSCF); subscribing, by the AS, with a status repository, to a status of the first proxy node; receiving, by the AS, from the status repository, an indication that the first proxy node is unavailable; based on at least receiving the indication that the first proxy node is unavailable, transmitting, by the AS, to a subscriber information node, a first message triggering proxy node restoration; receiving an indication, by the AS, that the UE is registered with a second proxy node different than the first proxy node; and based on at least receiving a session initiation message, establishing the data traffic session for the UE with the second proxy node.

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: A network operator can partition network elements, including elements of an IP Multimedia Subsystem (IMS) or Policy and Charging Rules Functions (PCRFs) into groups reserved for specific types of subscribers. When a user equipment (UE) registers with an IMS, elements of the IMS can contact a Home Subscriber Server (HSS) to determine a subscriber type associated with the UE. Based on the UE's subscriber type, an IMS element can determine an application server or other IMS element to contact about the UE based on identifying application servers or IMS elements that are also associated with the same subscriber type as the UE. Similarly, an IMS element can determine a PCRF to contact about the UE based on identifying a PCRF that is associated with the same subscriber type as the UE.

Abstract: An IP Multimedia Subsystem Service Control Point (IMS-SCP) module of a carrier network may provide trigger management for a request for a circuit switched (CS) call. For example, an IMS-SCP module may receive an request for a CS call associated with a user equipment. The IMS-SCP module may determine handling of the request for the CS call includes one or more first operations by a first feature platform and one or more second operations by a second feature platform. In response to the determining, the IMS-SCP module may perform trigger management associated with the request for the CS call. The trigger management may include invoking, by the IMS-SCP module, the one or more first operations of the first feature platform and, subsequent to the invoking the one or more first operations, invoking the one or more second operations of the second feature platform.

Abstract: Improved systems and method are described for addressing issues when an S-CSCF goes appears non-responsive or an application server appears non responsive. Profile recovery is executed through application servers which may allow additional options in efficiencies in maintain applications while recovering from the non-responsive devices.

Abstract: Telecommunications network components configured to manage call control of a communication session of user equipment are described herein. An anchoring network device may proxy signaling traffic for the communication session. The anchoring network device may determine a routing identifier based at least in part on which access network, or which type of access network, is carrying the communication session, and may transmit state information of the communication session to a call-control server in association with the routing identifier. The call-control server may provide control information of the communication session to the anchoring network device in response to the state information. The anchoring network device may modify the communication session, e.g., by adding or dropping one or more parties, in response to the control information. The routing identifier may be determined based at least in part on capabilities of a communication session indicated in a session-initiation message.

Abstract: An Internet Protocol Multimedia Subsystem (IMS) application server can initially attempt to route a terminating call invite to a user equipment (UE) via a packet-switched (PS) domain radio access network (RAN). However, if that initial attempt fails, the application server can follow either a PS retry option to reattempt routing the terminating call invite via a PS-domain RAN, or a circuit-switched (CS) retry option to instead reattempt routing the terminating call invite via a CS-domain RAN. In some examples, if Home Subscriber Server (HSS) data indicates that the UE is connected to a Long-Term Evolution (LTE) RAN and that CS-domain location information for the UE is older than a threshold, the application server can enable the PS retry option. However, if the UE is connected to an LTE RAN but the CS-domain location information is more recent than the threshold, the application server can instead enable the CS retry option.

Abstract: In some examples, an authentication node of a telecommunications network can receive an authentication request from a terminal, and an authentication-control message. The authentication node can skip an authentication operation with respect to the authentication request in response to the authentication-control message. In some examples, a relay node of the telecommunications network can detect an overload or service-interruption condition and determine, in response, the authentication-control message. The relay node can send the authentication-control message to the authentication node. In some examples, an authentication node can detect that its load level satisfies a predetermined criterion and, in response, skip an authentication operation and send a first message. Another authentication node can receive an indication of the first message and, in response, perform a second authentication operation.

Abstract: Systems and methods for selectively routing a connect to a network through a control function associated with the network. The system can distinguish between control functions based on functionalities associated with the control function itself or capabilities associated with a user device. The system can select between the control functions based at least in part on an identifier associated with the user device, a subscriber account associated with the user device, or another trait of the connection. The system can select the control function based on a determination made by a control node associated with the network and may be further based on a Network Resource Function, a Domain Name System server, internal static listings of the control functions, or other resource that associates one or more identifiers with the control function. The system can obtain the identifier once the user device requests a connection with the network and provide the identifier to the control node.

Abstract: Techniques for allowing access based online charging in cases of multiple user agents (multi-UAs) scenarios where the instances are registered to different telephony application servers (TASs) are discussed herein. For example, a user device may support a native number and multiple virtual numbers linked via a user account. When servicing a call, the user device may determine a served number to service the call from. If the served number is not the native number but a virtual number, the native-line server may handle the call session, but the online charging session will be handled by the virtual-line server. The native-line server may use session initiation protocol (SIP) information to send updated information for charging parameters to the virtual-line server, including network access transfer for accuracy in online charging logic.

Abstract: A first carrier may support inbound roaming requests for subscribers of a trusted second carrier. For example, the first carrier may receive an inbound roaming request from a UE. The first carrier may determine a second carrier that is a home carrier of the UE is a trusted carrier associated with the first carrier. In response, an IMS procedure associated with the UE may be performed including communicating, by a first CSCF node of the first carrier, with a first HSS of the second carrier, using a same protocol as used by the first CSCF node to communicate with a second HSS of the first carrier and communicating, by the first CSCF node, with a first AS of the second carrier, using a same protocol as used by the first CSCF node to communicate with a second AS of the first carrier.

Abstract: An IP Multimedia Subsystem Service Control Point (IMS-SCP) module of a carrier network may provide trigger management for a request for a circuit switched (CS) call. For example, an IMS-SCP module may receive an request for a CS call associated with a user equipment. The IMS-SCP module may determine handling of the request for the CS call includes one or more first operations by a first feature platform and one or more second operations by a second feature platform. In response to the determining, the IMS-SCP module may perform trigger management associated with the request for the CS call. The trigger management may include invoking, by the IMS-SCP module, the one or more first operations of the first feature platform and, subsequent to the invoking the one or more first operations, invoking the one or more second operations of the second feature platform.

Abstract: Techniques for allowing access based online charging in cases of multiple user agents (multi-UAs) scenarios where the instances are registered to different telephony application servers (TASs) are discussed herein. For example, a user device may support a native number and multiple virtual numbers linked via a user account. When servicing a call, the user device may determine a served number to service the call from. If the served number is not the native number but a virtual number, the native-line server may handle the call session, but the online charging session will be handled by the virtual-line server. The native-line server may use session initiation protocol (SIP) information to send updated information for charging parameters to the virtual-line server including network access transfer for accuracy in online charging logic.

Abstract: Systems and methods for selectively routing a connect to a network through a control function associated with the network. The system can distinguish between control functions based on functionalities associated with the control function itself or capabilities associated with a user device. The system can select between the control functions based at least in part on an identifier associated with the user device, a subscriber account associated with the user device, or another trait of the connection. The system can select the control function based on a determination made by a control node associated with the network and may be further based on a Network Resource Function, a Domain Name System server, internal static listings of the control functions, or other resource that associates one or more identifiers with the control function. The system can obtain the identifier once the user device requests a connection with the network and provide the identifier to the control node.

Abstract: In some examples, an authentication node of a telecommunications network can receive an authentication request from a terminal, and an authentication-control message. The authentication node can skip an authentication operation with respect to the authentication request in response to the authentication-control message. In some examples, a relay node of the telecommunications network can detect an overload or service-interruption condition and determine, in response, the authentication-control message. The relay node can send the authentication-control message to the authentication node. In some examples, an authentication node can detect that its load level satisfies a predetermined criterion and, in response, skip an authentication operation and send a first message. Another authentication node can receive an indication of the first message and, in response, perform a second authentication operation.

Abstract: A network operator can partition network elements, including elements of an IP Multimedia Subsystem (IMS) or Policy and Charging Rules Functions (PCRFs) into groups reserved for specific types of subscribers. When a user equipment (UE) registers with an IMS, elements of the IMS can contact a Home Subscriber Server (HSS) to determine a subscriber type associated with the UE. Based on the UE's subscriber type, an IMS element can determine an application server or other IMS element to contact about the UE based on identifying application servers or IMS elements that are also associated with the same subscriber type as the UE. Similarly, an IMS element can determine a PCRF to contact about the UE based on identifying a PCRF that is associated with the same subscriber type as the UE.

Abstract: An IP Multimedia Subsystem Service Control Point (IMS-SCP) module of a carrier network may provide trigger management for a request for a circuit switched (CS) call. For example, an IMS-SCP module may receive an request for a CS call associated with a user equipment. The IMS-SCP module may determine handling of the request for the CS call includes one or more first operations by a first feature platform and one or more second operations by a second feature platform. In response to the determining, the IMS-SCP module may perform trigger management associated with the request for the CS call. The trigger management may include invoking, by the IMS-SCP module, the one or more first operations of the first feature platform and, subsequent to the invoking the one or more first operations, invoking the one or more second operations of the second feature platform.

Abstract: Telecommunications network components configured to manage call control of a communication session of user equipment are described herein. An anchoring network device may proxy signaling traffic for the communication session. The anchoring network device may determine a routing identifier based at least in part on which access network, or which type of access network, is carrying the communication session, and may transmit state information of the communication session to a call-control server in association with the routing identifier. The call-control server may provide control information of the communication session to the anchoring network device in response to the state information. The anchoring network device may modify the communication session, e.g., by adding or dropping one or more parties, in response to the control information. The routing identifier may be determined based at least in part on capabilities of a communication session indicated in a session-initiation message.

Abstract: Telecommunications network components configured to manage call control of a communication session of user equipment are described herein. An anchoring network device may proxy signaling traffic for the communication session. The anchoring network device may determine a routing identifier based at least in part on which access network, or which type of access network, is carrying the communication session, and may transmit state information of the communication session to a call-control server in association with the routing identifier. The call-control server may provide control information of the communication session to the anchoring network device in response to the state information. The anchoring network device may modify the communication session, e.g., by adding or dropping one or more parties, in response to the control information. The routing identifier may be determined based at least in part on capabilities of a communication session indicated in a session-initiation message.

Abstract: A first communication provider supports an IP multimedia subsystem (IMS) having a border session control function (BGCF) that receives SIP requests. The SIP requests correspond to different SIP methods and specify various feature tags. The feature tags correspond to available services or media types that may be available from the IMS of a second communication provider. When receiving a SIP request that addresses a user supported by the second communication provider, the BGCF of the first communication provider checks the method and feature tag of the SIP request to make sure that they are supported by IMS of the second communication provider. If they are not, the SIP is rejected and a failure message is returned. The BGCF may also modify certain parameters of the SIP request, such as by removing one or more offered codecs or preconditions.