Abstract: The systems, devices, and techniques described herein are directed to scheduling wireless communications and verifying connections, for example, in an emergency call context. An emergency call scheduler can be installed in an application layer of user equipment to manage call scheduling. During an emergency situation, the emergency call scheduler can attempt to establish a communication based on a priority of network technologies (e.g., LTE, 4G, 3G, 2G) or a base station being in a subscriber network. As a call is established, a connection may be verified based at least in part on satisfying one or more handshake protocols and based at least in part on transmitting or receiving voice and/or data packets. Based on a location of the user equipment, or as a network topology is updated, a centralized server can update the emergency call scheduler to change the call scheduling priority.

Abstract: One or more timers can be used by an originating UE during setup of a communication session. The timer(s) can be triggered by an originating UE sending a request or receiving a response that uses a first signaling protocol. The timer(s) can further be terminated by the originating UE sending a request or receiving a response that uses a second signaling protocol different from the first signaling protocol, so long as the request/response using the second signaling protocol occurs before timeout of the timer(s).

Abstract: Systems, devices, and techniques described herein are directed to device service capability discovery. An initiating user equipment (UE) can transmit a request to establish a communication session (e.g., a voice call, a video call, etc.) with a destination UE. The initiating UE can also transmit a request for capability information associated with the destination UE. The destination UE can provide capability information associated with features beyond those required for the communication session. Thus, capability information for a plurality of features can be determined in parallel with establishing a communication between an initiating UE and a destination UE. In some cases, an initiating UE can receive an error message in response to signaling to establish the communication session, in which case the initiating UE can update capability information associated with the destination UE.

Abstract: A fifth generation (5G) radio access network (RAN) can determine that a user equipment (UE) should fall back to engaging in a communication session over an LTE-based Evolved Packet System (EPS) instead of a 5G system. However, to avoid interrupting setup operations that may be occurring separately for that communication session in an IP Multimedia Subsystem (IMS) apart from the 5G system, the EPS fallback can be delayed such that setup in the IMS can proceed at least to a point at which IMS signaling messages are less likely to be undeliverable due to the EPS fallback.

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: An originating user equipment (UE) that initiates a communication session as a real time text (RTT)-based communication may be configured to automatically downgrade the communication session in response to identifying one or more attributes of a response to a session request that indicate a communication session cannot be established with a full set of features requested by the user. For example, the originating UE can determine that a response to a session request indicates at least one of (i) an inability to establish the communication session, or (ii) an ability to establish the communication session without support for the exchange of the non-voice content via the RTT media stream. Based on this determination, a communication session can be established that does not support the exchange of the non-voice content via the RTT media stream. In this manner, rich RTT features are sacrificed in order to connect the user.

Abstract: Non-text content may be exchanged in real time text (RTT) messages over a telecommunications network as part of an enhanced RTT (eRTT) service. A first UE can receive, from a second UE over a telecommunications network, capability information indicating whether the second UE is capable of exchanging text content and/or non-text content via RTT messages. Using this capability information, the first UE may determine whether to enable eRTT functionality on the first UE by determining whether to display a user interface element(s) in a selectable state on the display next to a RTT conversation window. The selectable user interface element(s), upon selection, allows a user of the first UE to create new non-text content, or select particular non-text content from available non-text content, for inclusion in a RTT message. The first UE may thereafter send non-text content in the RTT message to the second UE.

Abstract: Techniques for automatically initiating the transmission of a silent emergency message via a mobile computing device are provided. A mobile device may receive a plurality of indications of a plurality of external buttons of the mobile computing device being pressed over a time interval. Based on the plurality of indications, the mobile computing device may determine that two or more external buttons have been pressed in a fixed sequence over the time interval. In response to determining that the two or more external buttons of the mobile computing device have been pressed in the fixed sequence, the mobile computing device may silently transmit a message to a computing device associated with an emergency contact, without activating a display screen of the device or making sounds.

Abstract: Methods and computing systems for SIP backend polling based on nonzero SIP subscribe expiration are described. A SIP server receives from a SIP client a Session Initiation Protocol (SIP) subscribe message indicating a nonzero expiration time. Based at least on receipt of the subscribe message indicating a nonzero expiration time, the SIP server initiates a backend polling session to a backend server. The SIP server receives, via the backend polling session, state information and provides the state information to the SIP client.

Abstract: Systems and methods for providing improved connection setup on networks is disclosed. At initial call setup, the system can choose between transmission control protocol (TCP) and user datagram protocol (UDP) based on current network conditions. When network conditions—e.g., signal strength and/or signal quality—are such that establishing the connection is likely to be unreliable, then the system can automatically choose TCP for improved reliability. When network conditions are good, on the other hand, then the system can automatically choose UDP for improved speed and efficiency. The system may also switch back and forth between TCP and UDP during use because of changing network conditions. This can reduce dropped connections, poor quality connections, dropped packets, and other errors.

Abstract: Multiple timers used by a device during setup of a communication session may include a first timer and a second timer, each configured to expire after different periods of time, and each configured to start in response to the device sending a Session Initiation Protocol (SIP) request using a SIP INVITE method. The first timer is stopped on receipt of the first SIP response, which may include a 100 Trying SIP response, while the second timer is stopped on receipt of a non-100 Trying SIP response. If the first timer expires, the device may send an additional SIP request using the SIP INVITE method as a retry mechanism while the second timer continues to run. If the second timer expires, the device may halt the session setup and reattempt using a different type of access network.

Abstract: A first user equipment (UE)—during a real time text (RIT) communication session with a second UE—may make a control function available to a local user of the first UE, who may invoke the control function to break up his/her RTT content within organized conversation bubbles. In an example process, after displaying first text character(s)—which was input by the local user—within a first conversation bubble designated for the first UE (or the local user thereof), the first UE may detect an invocation of the control function, followed by additional user input requesting to type one or more second text characters. Invocation of the control function prior to the additional user input requesting to type the second text character(s) may cause the first UE to display the second text character(s) within a second conversation bubble designated for the first UE, rather than the first conversation bubble.

Abstract: Systems and methods for optimized call handling during e911 calls. Normally, when a user equipment (UE) is connected to a public safety answering point (PSAP)—e.g., is on a 911 call—all incoming calls are automatically routed to voicemail. In contrast, the systems and methods disclosed herein enable calls that were dialed within a predetermined time window of the 911 call to be sent through to call-waiting to enable the user to accept or reject the call. The system can use a “guard timer” to determine whether a call is within the predetermined time window. The system can include a single guard timer for all incoming calls—e.g., “any call made from the UE within the previous X minutes prior to the 911 call.” The system can also include individual guard timers for each call that expire separately relative to the call's proximity to the 911 call.

Abstract: Systems and methods for improved e911 call handling. The system enables users to create multiple categories of callers. When a user makes a 911 (emergency) call, different categories of users receive different treatment. A call from a public safety access point (PSAP), for example, can be routed to the user's user equipment (UE). A caller on a favorites list may also receive the same, or similar, treatment. General callers, on the other hand, can be sent directly to voicemail, as is currently the practice for all callers. The system can enable certain callers to be sent to the UE to activate call-waiting, even though the user is on an emergency call, rather than being sent to voicemail with no explanation. The system can be used to provide this service to family members, healthcare professionals, PSAPs, and other important callers.

Abstract: Systems and methods for improved e911 call handling. The system enables users to create multiple categories of callers. When a user makes a 911 (emergency) call, different categories of users receive different treatment. A call from a public safety access point (PSAP), for example, can receive a recorded message or a text message indicating that the user is already connected to a PSAP. A caller on a favorites list may also receive the same, or similar, treatment. General callers, on the other hand, can be sent to voicemail, as is currently the practice for all callers. The system can enable callers to be informed as to why the user is not answering, rather than being sent to voicemail with no explanation. The system can be used to provide this additional information to family members, business contacts, PSAPs, and other important callers.

Abstract: Non-text content may be exchanged in real time text (RTT) messages over a telecommunications network as part of an enhanced RTT (eRTT) service. A first UE can receive, from a second UE over a telecommunications network, capability information indicating whether the second UE is capable of exchanging text content and/or non-text content via RTT messages. Using this capability information, the first UE may determine whether to enable eRTT functionality on the first UE by determining whether to display a user interface element(s) in a selectable state on the display next to a RTT conversation window. The selectable user interface element(s), upon selection, allows a user of the first UE to create new non-text content, or select particular non-text content from available non-text content, for inclusion in a RTT message. The first UE may thereafter send non-text content in the RTT message to the second UE.

Abstract: A user equipment (UE) and an Internet Protocol (IP) Multimedia Subsystem (IMS) node may exchange fallback indicators in SIP signaling for purposes of controlling fallback procedures implemented by the UE. By sending fallback indicators to an IMS node in a SIP request, a UE is able to inform the IMS node of its capabilities in regards to particular fallback radio access technologies (RATs) that are supported by the UE. The IMS node may respond to the UE with a SIP response that includes information indicating which of the supported Fallback RATs the UE is authorized to use (if any), and which of the supported Fallback RATs the UE is not authorized to use (if any). In this way, the IMS node can control a fallback procedure at the UE by indicating which Fallback RATs are usable by the UE to reattempt communication sessions that cannot be established on an existing RAT.

Abstract: Systems and methods for preventing aggressive or abusing signaling on networks are disclosed. When a user equipment (UE), such as a cell phone, sends a request to a network (e.g., a REGISTER, SUBSCRIBE, or PUBLISH request), a network entity can start a “guard timer” and/or increment a “guard counter.” The guard timer can comprise a predetermined amount of time within which one or more additional requests from the same UE will be ignored. Similarly, the guard timer can be used in conjunction with a guard counter. The guard counter can enable a UE to make a predetermined number of requests before the guard timer expires. If the UE exceeds the guard counter before the guard timer expires, any additional requests will be ignored. When the guard timer expires, the guard counter is reset to zero to enable the UE to make additional requests.

Abstract: Multiple timers used by a device during setup of a communication session may include a first timer and a second timer, each configured to expire after different periods of time, and each configured to start in response to the device sending a Session Initiation Protocol (SIP) request using a SIP INVITE method. The first timer is stopped on receipt of the first SIP response, which may include a 100 Trying SIP response, while the second timer is stopped on receipt of a non-100 Trying SIP response. If the first timer expires, the device may send an additional SIP request using the SIP INVITE method as a retry mechanism while the second timer continues to run. If the second timer expires, the device may halt the session setup and reattempt using a different type of access network.

Abstract: Methods and computing systems may cause SIP backend polling based on nonzero SIP subscribe expiration. A SIP server receives from a SIP client a Session Initiation Protocol (SIP) subscribe message indicating a nonzero expiration time. Based at least on receipt of the subscribe message indicating a nonzero expiration time, the SIP server initiates a backend polling session to a backend server. The SIP server receives, via the backend polling session, state information and provides the state information to the SIP client.