Abstract: Systems and methods for tracking and logging mute events that occur during communication sessions are disclosed. The method includes generating a disruption report that includes one or more aspects of a mute event detected during a communication session. The disruption report is communicated to a network for further analysis.

Abstract: Systems and methods for tracking and logging mute events that occur during communication sessions are disclosed. The method includes generating a disruption report that includes one or more aspects of a mute event detected during a communication session. The disruption report is communicated to a network for further analysis.

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 and methods are described for implementing an emergency services address management system for mobile devices. A mobile device may implement “voice over Wi-Fi” or otherwise communicate via wireless networks that do not provide address or location data. An emergency services address management system may associate E911 addresses with individual access points of the wireless networks, and may provide the associated E911 address instead of a default E911 address (which may be a home or billing address that is relatively distant from the user's current location) when a user of the mobile device makes a voice call to an emergency service. The system may identify access points for which an E911 address is not known, and may obtain or generate an E911 address using information from various sources, including the user, satellite-based or cellular-based location services, or other mobile devices that have accessed the wireless network via the access point.

Abstract: Systems, devices, and techniques described herein relate to automatically resetting interrupted connections associated with a core network and/or an Internet Protocol (IP) Multimedia Subsystem (IMS) network, in order to successfully establish a dedicated tunnel through the core network and the IMS network. An example method includes transmitting, to the core network, a first request for services associated with a minimum Quality of Service (QoS) level and determining that a wait time has expired without having received a response confirming that a dedicated tunnel corresponding to the QoS level has been established. Next, the method can include transmitting, to the core network, a second request to reset a connection associated with the core network and the IMS network.

Abstract: Techniques for network-based and sender-based data packet prioritization for downlink transmissions are discussed herein. Packets can be tagged or associated with information indicative of a priority of the packet for downlink transmission to a user equipment (UE). A priority level can be determined based on an application identifier or type associated with a data request, a level of user interaction with the UE, network conditions, and other factors. Packets can be received by a PDCP layer of a base station for sending based on the priority. Packets may be associated with a primary priority level associated with a QCI level and a secondary priority level based on UE and/or network factors discussed herein. Packets associated with a same QCI may be prioritized to optimize transmission of downlink data associated with a single UE or between transmission of downlink data associated with a plurality of UEs.

Abstract: Techniques for network-based and sender-based data packet prioritization for downlink transmissions are discussed herein. Packets can be tagged or associated with information indicative of a priority of the packet for downlink transmission to a user equipment (UE). A priority level can be determined based on an application identifier or type associated with a data request, a level of user interaction with the UE, network conditions, and other factors. Packets can be received by a PDCP layer of a base station for sending based on the priority. Packets may be associated with a primary priority level associated with a QCI level and a secondary priority level based on UE and/or network factors discussed herein. Packets associated with a same QCI may be prioritized to optimize transmission of downlink data associated with a single UE or between transmission of downlink data associated with a plurality of UEs.

Abstract: A component of a cellular communication system is configured to prioritize data packets based on packet tags that have been associated with the data packets. The packet tags may comprise an application identifier and a customer identifier, as examples. A Packet Data Convergence Protocol (PDCP) layer of a radio protocol stack receives a data packet and associated packet tags and assigns the data packet to a preferred transmission queue or a non-preferred transmission queue, based on the packet tags associated with the data packet. In order to manage queue overflows, data packets of the non-preferred transmission queue may be discarded when they have been queued for more than a predetermined length of time. Data packets of the preferred transmission queue, however, are retained regardless of how long they have been queued.

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: User equipment (UE) can select a connection type for a retry of a failed call based on system information blocks (SIBs) received from a serving base station of a first radio access layer of a telecommunication network. When the UE experiences a call setup failure of a call attempted through the serving base station of the first radio access layer, the UE can determine whether neighbor information within the SIBs includes information about a neighboring base station of a second radio access layer. If it does, the UE can select a retry connection type as a connection to the neighboring base station of the second radio access layer. If it does not, the UE can select the retry connection type as a connection to an alternate network. The UE can then retry the call through the selected retry connection type.

Abstract: A flow controller executing at a network element of a telecommunication network can use packet characteristics of a data packet to select, from a set of QoE goals, a QoE goal for the data packet. The set of QoE goals can include prioritizing throughput, prioritizing lower latency, prioritizing reliability, and/or other QoE goals. The flow controller can also determine a routing scheme associated with the selected QoE goal, and cause the data packet to be routed to a user equipment via an LTE connection and/or a 5G connection according to the routing scheme.

Abstract: A flow controller executing at a network element of a telecommunication network can dynamically allocate portions of spectrum to use for different types of network traffic and/or different user equipments (UEs). For example, the flow controller can use packet characteristics, UE characteristics, and/or network characteristics to determine a state of the telecommunication network. Based on the state of the telecommunication network, the flow controller can determine that certain portions of spectrum should be used to transport certain traffic, and in turn cause base stations to use those portions of spectrum for corresponding connections with one or more UEs. The allocated portions of spectrum can include frequencies in low band spectrum, mid-band spectrum, and/or high band spectrum.

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 service type symbol may be presented on a display of a communication device to indicate a type of service supported or unsupported on the communication device over a network to which the communication device is presently connected. The communication device may determine a value of a parameter, may determine, based at least in part on the value of the parameter, a service type symbol from a set of multiple different service type symbols to present on a display of the communication device, and may present the symbol on the display. Service type symbols might include, among others, a video symbol corresponding to a video streaming service, a voice symbol corresponding to a voice calling service, a basic data symbol corresponding to a basic data service.

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 cellular system having both 4th-Generation (4G) and 5th-Generation (5G) cellular networks may be configured to use Non-Standalone (NSA) dual connectivity, in which wireless data transmissions may be made using either 4G Long-Term Evolution (LTE) or 5G New Radio (NR) radio access networks. Data packets submitted for wireless transmission are associated with one or more packet tags, such as an application identifier and a customer identifier. A radio protocol stack receives the data packets and associated packet tags and determines for each data packet, based on the associated packet tags, whether to transmit the packet using the LTE radio access network or the NR radio access network. This determination may be based in part on a routing policy that has been created and/or provided by a cellular services provider.

Abstract: Systems, devices, and techniques described herein relate to selectively implementing an expedited retransmission time. In some examples, a call setup message is transmitted to a first network system associated with a first network access technology. A transfer request may be received from the first network system. The transfer request may indicate handover or redirection to a second network system associated with a second network access technology. Upon expiration of the expedited retransmission time after receiving the transfer request, the call setup message can be retransmitted to the second network system.

Abstract: Systems and methods for sending text messages in audio form over voice calls. When a user receives an incoming voice call, the system can enable a user to type a “text” message to the caller. Rather than being sent as a text message, however, the system can send the text message directly to the microphone of the user's equipment (UE) as a voice synthesized audio file, or text-to microphone (TTM) message. The audio file is then sent from the user's UE to the caller's UE, in effect “reading” the text message to the caller. The caller hears the contents of the message, in the form of a voice synthesized audio file over the speaker of the caller's UE. The system can mute the microphones on one or both UEs during the TTM process to create a virtually silent process from the user's standpoint.

Abstract: An application such as a contacts management application may be configured to display information for multiple contacts. The displayed information may include carrier information for certain contacts, indicating which of multiple cellular communication carriers provides cellular communication services for each contact. This may allow a user to provide recommendations to the user's contacts, such as promotional messages suggesting that the contacts switch to the carrier of the user. In some embodiments, a control may be displayed that automatically initiates a promotional message to a particular contact.

Abstract: Registration of a user equipment (UE) with a circuit-switched (CS) network can be controlled in an “on-demand” fashion by waiting for a trigger event before registering the UE with an available CS network. In some embodiments, CS registration of a UE may be triggered when the mobility management entity (MME) node receives, from the UE, a service request that was sent using Non-Access Stratum (NAS) protocol, such as an extended service request (ESR) or a short message service (SMS) over NAS request. In some embodiments, CS registration of a first UE may be triggered when the MME node receives, from a home subscriber server (HSS), a notification of an incoming session request originating from a second UE to establish a communication session over a CS network with the first UE.