Abstract:
In some implementations, a telecommunications network can include a core network device. The core network device can receive from a session-originating device an initiation request of a communication session, the initiation request including information of a destination and information of media capabilities. The core network device can determine network-location information of the destination, retrieve from a capability registry modification information corresponding to the network-location information, and modify the information of the media capabilities based at least in part on the modification information. The core network device can transmit the initiation request including the modified information of the media capabilities to another core network device corresponding to the network-location information. The core network device can also determine that the information of the one or more media capabilities does not correspond to the retrieved capability information and transmit a session-failure indication to the session-originating device.
Abstract:
Systems and methods for network-controlled scam/robocall handling are described. When an incoming call destined for a user device is detected, if the user device is subscribed to network-controlled scam/robocall handling, the incoming call is handled at the network according to the subscription. If user preferences are specified, the call may be blocked, forwarded to another number, sent directly to voice mail, or delivered to the device. How a call is handled may be determined based on a category associated with an originating number of the incoming call.
Abstract:
In some implementations, a telecommunications network can include an anchoring network device. The anchoring network device can receive, from a first party of a communication session, a service message including information of a first session attribute and associated with identification information of a party of the communication session. The anchoring network device can retrieve, from an authorization registry, authorization information corresponding to the identification information. In response to the authorization information indicating the first session attribute is not permitted, the anchoring network device can determine a status message based at least in part on the service message and transmit the status message via a communications interface. The status message can include a service-failure message or a second service message including information of a second, different session attribute.
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 system and method that fork incoming calls to a destination device or a device that is associated with the destination device is disclosed. The system receives a request to register multiple device for IMS services, receives an incoming call to a destination mobile device, identifies one or more associated mobile devices, and determines one or more forked devices. The system transmits a first notification to each forked device, the first notification indicating that the forked device may accept or reject the incoming call request, and the system receives an acceptance or rejection from one or more forked devices.
Abstract:
Telecommunication network components configured to manage a pre-establishment phase of a communication session of user equipment are described herein. The components may receive a session-failure indication, e.g., during the pre-establishment phase. The components may determine action data based at least in part on the received session-failure indication. In response to the action data indicating a retry, the components may re-initiate the communication session via an access network indicated in the action data. User equipment may transmit a session-failure indication indicative of a detected failure condition preventing establishment of the communication session.
Abstract:
User equipment communicating with a telecommunications network may be configured to selectively initiate a communication session with another device via a first access network of a first type. During a pre-establishment phase, the user equipment may measure the first access network to provide a first measurement. In response to the first measurement corresponding to a first service-interruption condition, the user equipment may cancel the communication session, tune a radio of the user equipment to communicate with a second access network of a second, different type, and re-initiate the communication session with the other device via the second access network. The user equipment may, after the canceling, receive a retry invitation to the communication session via the second access network, tune the radio thereto, and re-initiate the communication session with the other device via the second access network.
Abstract:
Telecommunication network components configured to manage a handover of a communication session of user equipment from a packet-switched access network to a circuit-switched access network are described herein. The components may receive a handover request from user equipment, allocate circuit-switched access network resources, and request a session transfer. When the session transfer is invalid, e.g., during a pre-establishment phase of a communication session, the components may reject the transfer within a selected time and provide an invalid-handover message. Components may, in response to an invalid handover request, transmit a rejection of the session transfer and a fallback-trigger message.
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; receiving, at a subscriber information node, from a call session control function (e.g., over an N70 interface), a first message triggering proxy node restoration; based on at least receiving the first message triggering proxy node restoration, transmitting, by the subscriber information node, to a management node, a second 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:
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.