T-mobile Usa, Inc.

T-mobile Innovations LLC

Lin Zhang

Hsin Fu Henry Chiang

Syed Toaha Ahmad

Adnan Rahat

James J Bae

Hang Hoi Yau

Jaime Enrique Rodriguez Villate

Ming Shan Kwok

Yasmin Karimli

Egil Gronstad

Kun Lu

Jun Liu, Sr

Elizabeth Zhang

Jake Michael Reaves

Described herein are techniques, devices, and systems for managing, by service providers, telecommunication network selection data, which can include user equipment (UE) data and carrier configuration data. The UE data, which can be identified based on user selections of toggles displayed in user interfaces (UIs) of UEs, and the carrier configuration data, can be utilized for selections of networks and/or network services for the UEs. The carrier configuration data can be utilized to override the UE data.

User equipment (UE) data and carrier configuration data based cellular network management

The system determines that an application running user equipment (UE) is requesting a throughput intensive communication over a network. The throughput intensive communication can require a predetermined downlink and uplink throughput. The system sends a first indication to the network, specifying to a base station of the network that the UE is requesting the throughput intensive communication. The base station determines whether it can provide the downlink throughput and the uplink throughput to the UE. Upon determining that the base station cannot provide the downlink or the uplink throughput to the UE, the base station sends a first message to the UE, indicating that the throughput intensive communication is of low quality. Upon receiving the first message, the UE waits for a predetermined criterion to be satisfied before attempting to engage in the throughput intensive communication, thereby reducing network traffic by eschewing sending repeated requests for the throughput intensive communication.

Reducing network traffic associated with a throughput intensive communication over a wireless telecommunication network

Methods and systems are provided for differentiating an XR device from other devices when initiating communications with an Internet gateway. Initially the XR device sends a probe request to the Internet gateway, where the probe request includes an identifier of the device type and network requirements of the XR device. It is determined that the particular device type and network requirements in the probe request are supported by the Internet gateway, and is communicated to the XR device in the form of a probe response. A communication session is set up between the XR device, the Internet gateway, and a network, the communication session including QoS control based on the device type and network requirements of the XR device.

Extended reality device identification by internet gateway

A solution for handling network congestion includes detecting, by a wireless network, a network congestion condition; detecting, by the wireless network, a failed attempt, by a user equipment (UE), to initiate a data session (e.g., a voice over WiFi (VoWiFi) call) over a packet data network (PDN) through the wireless network; transmitting, by the wireless network, to the UE, a notification of network congestion; and transmitting, by the wireless network, to the UE, a retry parameter set including a maximum number of fast retries, a fast retry time interval, and a slow retry time interval. In some examples, the retry parameter set further includes a rate at which the slow retry time interval increases with a value of a slow retry counter, and/or a maximum number of slow retries. In some examples, the retry scheme varies based on the severity of the congestion and/or roaming conditions.

UE retry during network overload

A solution for handling network congestion includes: attempting, by a user equipment (UE), to initiate a data session (e.g., a voice over WiFi (VoWiFi) call) over a packet data network (PDN); receiving, by the UE, a notification of network congestion; based on at least a fast retry timer and a fast retry counter, attempting, by the UE, fast retries up to a maximum number of fast retries at a fast retry time interval; and based on at least none of the initial attempt and the fast retries initiating the data session, attempting, by the UE, slow retries at a slow retry time interval until the data session is initiated or a trigger condition halts the slow retries. In some examples, the UE receives a retry parameter set from the network including the maximum number of fast retries, the fast retry time interval, and the slow retry time interval.

Disclosed herein are techniques, devices, and systems for a mobile device to keep track of public land mobile networks (PLMNs) codes from a list(s) of equivalent PLMNs that the mobile device received at a time of performing a past registration procedure(s). For example, memory of the mobile device may store a PLMN code(s) from a list of equivalent PLMNs that the mobile device received from a mobility management entity (MME) or an access and mobility function (AMF) node. During a subsequent registration, the mobile device may send a message to another MME or another AMF node, and may receive a message, such as an ATTACH ACCEPT message or a REGISTRATION ACCEPT message, from the other MME or the other AMF node. In response to receiving the message, the mobile device can maintain the stored PLMN code(s) in the memory.

Growing community of inventors

Overland Park, KS, United States of America

Lin Zhang