Indication of network condition at remote UE

Abstract

This disclosure provides systems, devices, apparatuses, and methods, including computer programs encoded on a storage medium, for indicating, at a local UE, a network condition at a remote UE. The local UE may be a first UE that receives, from a second UE (e.g., a remote UE), a first indication of a reduced network condition at the second UE. The first indication may be associated with at least one of a TMMBr, a TMMBn, a reduced bit rate, or a reduced downlink schedule. The first UE may display, at the first UE, a second indication of the reduced network condition at the second UE based on the first indication received from the second UE.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application serial number 17 / 804,896, entitled “INDICATION OF NETWORK CONDITION AT A REMOTE UE” and filed on June 1, 2022, which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly to indicating at a local user equipment (UE) network conditions at a remote UE. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at city, country, region, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] The following presents a summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive review of all envisioned aspects. This summary is neither intended to identify the key or important elements of all aspects, nor to describe the scope of any or all aspects. Its only purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a first user equipment (UE), which is configured to receive a first indication of a reduced network condition at the second UE from a second UE, the first indication being associated with at least one of a temporary maximum media stream bit rate request (TMMBr), a temporary maximum media stream bit rate notification (TMMBn), a reduced bit rate, or a reduced downlink scheduling; and based on the first indication received from the second UE, display a second indication of the reduced network condition at the second UE at the first UE.

[0008] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a second UE configured to receive a local indication of a reduced network condition at the second UE; and to send an indication of a reduced network condition at the second UE to a first UE, the indication being associated with at least one of TMMBr, TMMBn, a reduced bit rate, or a reduced downlink scheduling.

[0009] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features are only indicative of only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0011] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0012] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0014] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0015] Figure 3 is a diagram illustrating an example in which a first user equipment (UE) communicates with a second UE.

[0016] Figure 4 is a call flow diagram illustrating communication between a first UE and a second UE.

[0017] Figure 5 is a diagram illustrating bits of an extended header and / or in-band signaling.

[0018] Figure 6 is a flow chart of a method of performing wireless communications at a first UE.

[0019] Figure 7 is a flow chart of a method of performing wireless communications at a first UE.

[0020] Figure 8 is a flow chart of a method of performing wireless communications at a second UE.

[0021] Fig. 9 is a flow chart of a method of performing wireless communications at a second UE.

[0022] Fig.10 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities. DETAILED DESCRIPTION

[0023] A communication (such as a video call or a voice call) between a first user equipment (UE) and a second UE may be degraded during the call process based on a degraded network condition at the first UE and / or the second UE. For example, a video call may become blurry, experience lags in the video data stream, etc. A user of a first UE (e.g., a local UE) may suspect that the degraded network condition is at the local UE, even when the degraded network condition is actually at the second UE 404 (e.g., a remote UE) with which the first UE 402 is communicating. Therefore, the user of the first UE may unnecessarily reset / restart the first UE and / or close / reset an application executed at the first UE in an attempt to improve the network condition that the user suspects is degraded at the first UE. The aspects presented herein enable the first UE / local UE to determine which UE is experiencing a degraded network condition, and indicate the determination to the user of the first UE via a user interface (UI) of the first UE. The second UE / remote UE may also display an indication to the user of the second UE via the UI of the second UE, indicating which UE is experiencing a degraded network condition. The aspects presented herein may help the user of the first UE and / or the second UE avoid making unnecessary adjustments when the network condition at another UE results in lower performance.

[0024] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0025] Several aspects of the telecommunication system are also presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0026] As an example, an element or any part of an element or any combination of elements can be implemented as a "processing system", which includes one or more processors. The example of a processor includes a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gate logic part, a discrete hardware circuit and other suitable hardware configured to perform various functions described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other terms, software should be broadly interpreted as meaning an instruction, an instruction set, a code, a code segment, a program code, a program, a subroutine, a software component, an application, a software application, a software package, a routine, a subroutine, an object, an executable, a thread of execution, a process, a function or any combination thereof.

[0027] Therefore, in one or more example aspects, specific implementations and / or use cases, the described functions may be implemented with hardware, software, or any combination thereof. If implemented with software, the functions may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0028] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user equipment, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may be specifically for use cases or applications, or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases may be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) equipment or systems in conjunction with one or more technologies herein. In some practical environments, the equipment in conjunction with the various aspects and features described may also include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / accumulators, etc.) The various techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0029] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0030] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0031] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0032] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units (such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both). The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding user equipment (UE) 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be served simultaneously by multiple RUs 140.

[0033] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units on a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0034] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functions (i.e., central unit-user plane (CU-UP)), control plane functions (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0035] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional split such as that defined by 3GPP. In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0036] Lower layer functionality may be implemented by one or more RUs 140. In some deployments, a RU 140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0037] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN, such as an open eNB (O-eNB) 111, via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0038] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or communicate with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.

[0039] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0040] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102, or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmission diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0041] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0042] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0043] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) that is identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0044] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz–71GHz), FR4 (71GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0045] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used in this document, it can broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" is used in this document, it can broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2 and / or FR5, or may be within the EHF band.

[0046] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or different. The transmit direction and receive direction of the UE 104 may be the same or different.

[0047] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include disaggregated base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0048] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that processes signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, the LMF 166, the positioning determination entity (PDE), the serving mobile location center (SMLC), the mobile positioning center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurement results and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the positioning of the UE 104. The NG-RAN may determine the positioning of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, positioning estimates, and optional speed calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or the serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0049] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0050] See again Figure 1 , in some aspects, UE 104 may include a remote UE indication component 198 configured to receive from a second UE a first indication of a reduced network condition at the second UE, the first indication being associated with at least one of a temporary maximum media stream bitrate request (TMMBr), a temporary maximum media stream bitrate notification (TMMBn), a reduced bitrate, or a reduced downlink scheduling; and based on the first indication received from the second UE, display at the first UE a second indication of a reduced network condition at the second UE. In some aspects, the remote UE 103 may include a TMMBr component 199 configured to receive a local indication of a reduced network condition at the second UE; and send to the first UE an indication of a reduced network condition at the second UE, the indication being associated with at least one of TMMBr, TMMBn, a reduced bitrate, or a reduced downlink scheduling. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0051] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2DFIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and both UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The slot format is configured for the UE via a received slot format indicator (SFI) (dynamically configured via DL control information (DCI) or semi-statically / statically configured via radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0052] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes of the same size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4 or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is conventional or extended. For a conventional CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0053]

[0054] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Accordingly, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a parameter set μ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0055] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0056] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0057] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information such as system information blocks (SIBs) that are not sent via the PBCH, and paging messages.

[0058] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0059] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0060] Figure 3 3 is a block diagram of a second UE 310 communicating with a first UE 350 in an access network. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functions. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functions associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0061] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Subsequently, each stream can be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from a reference signal and / or channel state feedback sent by the first UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier for transmission using a corresponding spatial stream.

[0062] At the first UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial stream destined for the first UE 350. If multiple spatial streams are destined for the first UE 350, they may be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the second UE 310. These soft decisions may be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the second UE 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functions.

[0063] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0064] Similar to the functions described in conjunction with DL transmission by the second UE 310, the controller / processor 359 provides RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0065] The TX processor 368 may use channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the second UE 310 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via corresponding transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0066] UL transmissions are processed at the second UE 310 in a manner similar to that described in conjunction with the receiver functionality at the first UE 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0067] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0068] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 The remote UE indication component 198 combines various aspects.

[0069] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The TMMBr component 199 combines various aspects.

[0070] Wireless communication systems can be configured to share available system resources and provide various telecommunication services (e.g., telephone, video, data, messaging, broadcasting, etc.) based on multiple access technologies that support communication with multiple users (such as CDMA systems, TDMA systems, FDMA systems, OFDMA systems, SC-FDMA systems, and TD-SCDMA systems, etc.). In many cases, common protocols that facilitate communication with wireless devices are adopted in various telecommunication standards. For example, communication methods associated with eMBB, mMTC, and ultra-reliable low-latency communications (URLLC) may be incorporated into the 5G NR telecommunication standard, while other aspects may be incorporated into the 4G LTE standard. Since mobile broadband technology is part of the ongoing evolution, further improvements in mobile broadband remain useful for the continued development of such technology.

[0071] Figure 4 4 is a call flow diagram 400 illustrating communications between a first UE 402, a second UE 404, and a network 403. The first UE 402 may be a local UE, and the second UE 404 may be a remote UE communicating with the local UE. Communications (such as a video call or a voice call) between the first UE 402 and the second UE 404 may be degraded during the call process based on degraded network conditions at the first UE 402 and / or the second UE 404. For example, a video call may become blurry, experience lags in the video data stream, etc. The degraded quality of experience (QoE) of a user of the first UE 402 (e.g., the local UE) may cause the user to suspect that the degraded network conditions are at the first UE 402 (e.g., the local UE), even though the degraded network conditions may actually be at the second UE 404 (e.g., the remote UE) with which the first UE 402 is communicating.

[0072] Degraded network conditions suspected by the user at the first UE 402 may cause the user of the first UE 402 to reset / restart the first UE 402 in an attempt to improve the network conditions suspected by the user at the first UE 402. In other examples, the user may close / reset applications executing at the first UE 402 based on the suspected degraded network conditions at the first UE 402. However, if the degraded network conditions are actually at the second UE 404, resetting / restarting the first UE 402 or closing / resetting the applications of the first UE 402 may not result in improved QoE for the user of the first UE 402. In addition, power consumption at the first UE 402 may increase because restarting the applications and / or devices may consume an increased amount of power compared to allowing the applications and / or devices to continue executing.

[0073] Without indicating to the user of the first UE 402 which end of the communication link between the first UE 402 and the second UE 404 is experiencing the degraded network condition, the user may attempt to reset / restart the first UE 402 or close / reset the application of the first UE 402, even if the user understands that the degraded network condition may potentially be at the second UE 404. However, because the user may not be able to determine which UE is associated with the degraded network condition, the user may unnecessarily perform such procedures when attempting to troubleshoot the degraded QoE.

[0074] At 406 , the second UE 404 may detect the degraded network condition at the second UE 404 , such that an indication may be provided to the user of the first UE 402 as to which UE is associated with the degraded network condition based on the detection at 406 . Figure 4It is illustrated that at 408, the second UE 404 may provide an indication of a reduced network condition to the network. The network may then provide an indication 409 to the first UE. In some aspects, the indication 409 may include the information provided at 408. In other aspects, the indication 409 may indicate that the condition of the first UE 402 is good, which may protect the privacy of the information of the second UE 404. The indication may allow the user of the first UE 402 to more accurately identify the cause of the degraded QoE. Therefore, the first UE 402 may be configured to indicate / display whether the reduced network condition is associated with the first UE 402 or the second UE 404 via the user interface (UI) of the first UE 402 at 420. The second UE / remote UE may also display an indication to the user of the second UE via the UI of the second UE, which indicates which UE is experiencing the reduced network condition. In the example, the indication displayed via the UI of the first UE 402 at 420 may also indicate the cause of the degraded QoE. Such an indication may be displayed at 420 via the UI of the first UE 402 for both audio and video calls. In another example, an indication may be displayed at the UI of the second UE 404 so that a second user of the second UE 404 may similarly determine the cause of the degraded QoE at the second UE 404.

[0075] In the case of a video call, a codec and a maximum bit rate may be negotiated between the first UE 402 and the second UE 404. A "codec" refers to software or hardware that compresses and decompresses digital video data. In the context of video compression / decompression, a codec is a portmanteau of the sounds and meanings of "coder" and "decoder." A device that only compresses may be referred to as an "encoder" and a device that only decompresses may be referred to as a "decoder," and a codec may perform both functions. The codec and maximum bit rate for the video call may be negotiated based on a session description protocol (SDP) associated with a signal exchange between the first UE 402 and the second UE 404.

[0076] At 408, the second UE 404 may send an indication of the reduced network conditions at the second UE 404 to the network 403 and / or to the first UE 402, for example, via the network 403, for the user of the first UE 402 to confirm which end of the communication link between the first UE 402 and the second UE 404 is experiencing the reduced network conditions. The video call may be associated with a temporary maximum media stream bitrate request (TMMBr) and / or a temporary maximum media stream bitrate notification (TMMBn). If the first UE 402 or the second UE 404 experiences reduced network conditions, reduced channel conditions, network congestion, etc., which results in a reduced QoE associated with one or both UEs, the UE associated with the reduced QoE may send a TMMBr to the other UE to request an adjustment (e.g., increase or decrease) of the bitrate. In the event that the first UE 402 and the second UE 404 do not perform negotiation, such as in a non-IP Multimedia Subsystem (IMS) example, at 408, the reduced network conditions at the second UE 404 can be indicated to the first UE 402 based on the reduced downlink scheduling for the second UE 404.

[0077] In one example, if the first UE 402 and the second UE 404 are communicating via a video call and the network conditions at the second UE 404 are reduced, the second UE 404 may send a TMMBr to the first UE 402 via the network 403 so that the first UE 402 can adjust the bit rate (e.g., transmit / Tx bit rate to the second UE 404). The reduced bit rate received by the second UE 404 associated with the reduced network conditions at the second UE 404 may prevent the video call from being downgraded to an audio call. Therefore, TMMBr may be similar to a feedback mechanism to the first UE 402 indicating the video quality at the second UE 404. TMMBr may indicate to the first UE 402 whether to increase / decrease the Tx / transmission bit rate to the second UE 404.

[0078] The first UE 402 may indicate / display, at 420, via a UI of the first UE 402, the degraded network condition associated with the second UE 404 based on receiving the TMMBr from the second UE 404 at 408. For example, the indication displayed via the UI of the first UE 402 at 420 may explicitly indicate to the user of the first UE 402 that the network condition is degraded at the remote end of the communication link between the first UE 402 and the second UE 404. In an example associated with a privacy implication at the second UE 404, the first UE 402 may indicate / display, at 420, via the UI of the first UE 402, that the network condition at the local end of the communication link between the first UE 402 / the first UE 402 and the second UE 404 is at a sufficient level (e.g., not degraded). Based on such an indication, the user of the first UE 402 may not suspect that the local condition at the first UE 402 is degraded during the video / audio call with the second UE 404.

[0079] If TMMBr is not received from the second UE 404 at 408, but the bit rate associated with the communication between the first UE 402 and the second UE 404 is decreasing, the first UE 402 may indicate / notify the user of the first UE 402 via the UI of the first UE 402 that the network condition of the session is degraded. That is, if the first UE 402 repeatedly receives a request for a bit rate or a reduction in the bit rate, the first UE 402 may determine that the network condition of the session is degraded and may indicate the degraded session condition via the UI of the first UE 402. The second UE 404 may send TMMBr to the first UE 404 during the video call based on the condition (such as network congestion, packet loss, jitter, etc.) detected at the second UE 402 at 406 at 408. The first UE 402 may correspond to a media transmitter, which may act on the request received from the second UE 404 at 408 to reduce the transmission media bit rate.

[0080] After receiving the TMMBr from the second UE 404 at 408, the first UE 402 may send a response to the second UE 404 via the network 403 at 410. The response may be sent to the second UE 404 via the TMMBr at 410. For example, after the first UE 402 receives the TMMBr from the second UE 404 at 408, the first UE 402 may send the TMMBr to the second UE 404 at 410, which may be used as an ACK, which may be received by the second UE at 411. For example, after the second UE 404 detects a bad / good network condition at the second UE 404 and sends the TMMBr to the first UE 402 at 408 to reduce / increase the transmission bit rate, the first UE may send the TMMBr to the second UE 404 at 410 to acknowledge the TMMBr received from the second UE 404. The first UE 402 may also reconfigure the encoding bit rate of the codec / encoder / decoder. For example, at 412, the first UE 402 may adjust a communication bit rate with the second UE based on the indication of the reduced network condition at the second UE 404 received at 408 and / or the TMMBn sent at 410. At 414, the first UE 402 may request and / or receive block error rate (BLER) information or grant information associated with uplink / downlink communications of the second UE 404. After adjusting the communication bit rate at 412 and / or receiving the BLER / grant information at 414, the first UE 402 may send a communication to the second UE 404 based on the adjustment (e.g., increase / decrease) to the bit rate at 416.

[0081] Some processes of the first UE 402 may be based on more than one TMMBr. For example, the first UE 402 may receive one or more subsequent indications of a reduced network condition at the second UE 404, for example, via the network at 418. The one or more subsequent indications received at 418 may correspond to one or more TMMBrs received within a predefined duration to reduce the transmission bit rate during the video call based on the second UE 404 being unable to recover from the reduced network condition detected at 406 within the predefined duration. The first UE 402 may perform multiple 50% reductions in the bit rate (e.g., starting from the maximum bit rate negotiated for the session). If the bit rate is reduced to a minimum bit rate / threshold, at 420, the first UE 402 may indicate / display to the user of the first UE 402 via the UI of the first UE 402 that the network condition is reduced at the remote end of the communication link between the second UE 404 / first UE 402 and the second UE 404. The first UE 402 may also downgrade the video call to an audio call based on reaching the minimum bit rate / threshold. The indication / notification displayed via the UI of the first UE 402 at 420 may allow the user of the first UE 402 to determine which end of the communication link is causing the downgrade to the audio call.

[0082] The reason for the degraded quality of the video call may correspond to degraded channel conditions and / or congestion at the remote end of the communication link between the first UE 402 and the second UE 404. The user of the first UE 402 may or may not be notified of the reason causing the degraded quality at the remote end of the communication link. For example, the user of the first UE 402 may be notified via the UI of the first UE 402 only that there is a degraded network condition at the second UE 404 without further indication / explanation.

[0083] Based on the in-band process, the indication / notification displayed via the UI of the first UE 402 at 420 can also be performed for audio calls or other calls that do not use real-time transport protocol (RTP) feedback. The indication / notification displayed via the UI of the first UE 402 at 420 can also be applicable to video calls in which the TMMBr and TMMBn processes are not negotiated between the first UE 402 and the second UE 404 during call initiation. The RTP extension header (e.g., with 2-bit granularity) included in the single-byte RTP packet can be used to send an indication of the in-band reduced network condition at 408. When the first UE 402 receives the RTP packet, the first UE 402 can determine that the second UE 404 (e.g., the transmitting UE) is experiencing a reduced network condition and can reduce the transmission bit rate to the second UE 404. The extension header can be based on the SDP negotiation associated with the signal exchange between the first UE 402 and the second UE 404. In one example, if the first UE 402 and the second UE 404 are communicating based on an audio call or a video call, and the second UE 404 is experiencing degraded network conditions or has degraded downlink scheduling, the second UE 404 may send a 1-byte RTP packet to the first UE 402 to indicate that the network conditions at the second UE 404 are degraded.

[0084] The first UE 402 may indicate / display the degraded network condition at the second UE 404 to a user of the first UE 402 via a UI of the first UE 402 at 420. The indication based on the RTP extension header may be sent in-band to reduce additional signaling between the first UE 402 and the second UE 404. Thus, the indication from the second UE 404 to the first UE 402 may be based on in-band signaling or an in-band RTP extension header.

[0085] Figure 5 5 is a diagram illustrating bits of an extended header and / or in-band signaling. The extended header and / or in-band signaling may indicate an extended identifier (ID), channel conditions, uplink / downlink grants, a measurement of reference signal received power (RSRP), a measurement of reference signal received quality (RSRQ), a measurement of received signal strength indicator (RSSI), and / or a signal to interference plus noise ratio (SINR). Diagram 500 may correspond to a 1-byte extended header of a format based on an RTP packet.

[0086] The 1-byte extended header may include the initial 4 bits reserved for the ID of the RTP packet and the remaining 4 bits for the length (len) of other parameters. That is, bits 0-3 may indicate the extended ID, bits 4-7 may indicate channel conditions, uplink / downlink grant information, RSRP / RSRQ / RSSI measurements, SINR, etc. In some examples, the extended header may be extended to 2 bytes to accommodate more network status information. Based on the bit information / RTP packet, the first UE may indicate / display the condition at the remote end of the communication link between the second UE / first UE and the second UE via the UI of the first UE. The reason for the reduced network condition at the second UE may also be indicated / displayed via the UI of the first UE. The extended header and / or in-band signaling technology may be performed for audio calls and other situations where the video feedback mechanism is not implemented.

[0087] The SDP or RTP extension mapping may be negotiated during the video call setup. The RTP extension packet may be sent based on a predefined network condition occurring at the second UE. Thus, a TMMBr or RTP packet may be sent from the second UE to the first UE, which may indicate the network condition at the second UE. The first UE may indicate / display the network condition at the remote end of the communication link between the first UE and the second UE via the UI of the first UE based on the TMMBr or RTP packet, so that the user of the first UE can determine which end of the communication link may be associated with the reduced network condition.

[0088] Figure 6 600 is a flow chart of a method of wireless communication. The method may be performed by a first UE (e.g., UE 104, 350, 402, device 1004, etc.), which may include a memory 360 and may correspond to the entire UE 104, 350, 402 or device 1004 or a component of the UE 104, 350, 402 or device 1004, such as a TX processor 368, an RX processor 356, a controller / processor 359, a cellular baseband processor 1024, and / or an application processor 1006.

[0089] At 602, the first UE may receive from the second UE a first indication of a reduced network condition at the second UE, the first indication being associated with at least one of TMMBr, TMMBn, a reduced bit rate, or a reduced downlink scheduling. Figure 4 , the first UE 402 may receive an indication of a reduced network condition at the second UE 404 from the second UE 404 at 408. The indication received from the second UE 404 at 408 may be TMMBr and / or indicate a communication bit rate or downlink schedule associated with the second UE 404. The reception at 602 may be based on Fig.10 The remote UE instructs component 198 of the device 1004 to execute.

[0090] At 604, the first UE may display, at the first UE, a second indication of a degraded network condition at the second UE based on the first indication received from the second UE. Figure 4 , the first UE 402 may display an indication of a degraded network condition at the second UE 404 at 420 based on the indication of a degraded network condition at the second UE 404 received from the second UE 404 at 408. The display at 604 may be based on Fig.10 The remote UE instructs component 198 of the device 1004 to execute.

[0091] Figure 7 700 is a flow chart of a method of wireless communication. The method may be performed by a first UE (e.g., UE 104, 350, 402, device 1004, etc.), which may include a memory 360 and may correspond to the entire UE 104, 350, 402 or device 1004 or a component of the UE 104, 350, 402 or device 1004, such as a TX processor 368, an RX processor 356, a controller / processor 359, a cellular baseband processor 1024, and / or an application processor 1006.

[0092] At 702, the first UE may receive from the second UE a first indication of a reduced network condition at the second UE, the first indication being associated with at least one of TMMBr, TMMBn, a reduced bit rate, or a reduced downlink scheduling. Figure 4 , the first UE 402 may receive an indication of a reduced network condition at the second UE 404 from the second UE 404 at 408. The indication received from the second UE 404 at 408 may be TMMBr and / or indicate a communication bit rate or downlink schedule associated with the second UE 404. The reception at 702 may be based on Fig.10 The remote UE instructs component 198 of the device 1004 to execute.

[0093] At 704, the first UE may send TMMBn as a confirmation of the first indication based on TMMBn, the first indication corresponding to TMMBr. Figure 4 , the first UE 402 may send the TMMBn to the second UE 404 at 410. The TMMBn sent to the second UE 404 at 410 may be in response to the indication of the degraded network condition at the second UE 404 received from the second UE 404 at 408. The sending at 704 may be based on Fig.10 The remote UE instructs component 198 of the device 1004 to execute.

[0094] At 706, the first UE may adjust a bit rate for communication with the second UE based on the first indication of degraded network conditions at the second UE received from the second UE. Figure 4 , the first UE 402 may adjust the communication bit rate with the second UE 404 at 412 based on the indication of the reduced network conditions at the second UE 404 received from the second UE 404 at 408. The adjustment at 706 may be based on Fig.10 The remote UE instructs component 198 of the device 1004 to execute.

[0095] At 708, the first UE may send a request for at least one of BLER information associated with the second UE or grant information associated with the second UE based on the first indication of degraded network conditions at the second UE received from the second UE. Figure 4 , the first UE 402 may send a request for / receive a response to the BLER and / or grant information associated with the second UE 404 at 414. The first UE 402 may send a request for / receive a response to the BLER and / or grant information at 414 based on the indication of the degraded network condition at the second UE 404 received from the second UE 404 at 408. The sending at 708 may be based on Fig.10 The remote UE instructs component 198 of the device 1004 to execute.

[0096] At 710, the first UE may receive one or more subsequent indications of degraded network conditions at the second UE, the one or more subsequent indications associated with one or more requests for a reduced bit rate for a predefined duration or to reduce the reduced bit rate to a minimum threshold. Figure 4 , the first UE 402 may receive one or more subsequent indications of reduced network conditions at the second UE 404 from the second UE 404 at 418. The one or more subsequent indications received from the second UE 404 at 418 may be associated with a reduced bit rate or a reduction in the bit rate to a minimum threshold for a predefined duration. The reception at 710 may be based on Fig.10 The remote UE instructs component 198 of the device 1004 to execute.

[0097] At 712, the first UE may display, at the first UE, a second indication of a degraded network condition at the second UE based at least on the first indication received from the second UE. Figure 4, the first UE 402 may display an indication of a degraded network condition at the second UE 404 at 420 based on the indication of the degraded network condition at the second UE 404 received from the second UE 404 at 408. The display at 712 may be based on Fig.10 The remote UE instructs component 198 of the device 1004 to execute.

[0098] Figure 8 800 is a flow chart of a method of wireless communication. The method may be performed by a second UE (e.g., UE 103, 310, 404, device 1004, etc.), which may include a memory 376 and may correspond to the entire UE 103, 310, 404 or device 1004 or a component of the UE 103, 310, 404 or device 1004, such as the TX processor 316, the RX processor 370, the controller / processor 375, the cellular baseband processor 1024 and / or the application processor 1006.

[0099] At 802, the second UE may receive a local indication of a degraded network condition at the second UE. Figure 4 , the second UE 404 may detect a degraded network condition at the second UE 404 at 406. The receiving at 802 may be based on Fig.10 The TMMBr component 199 of the device 1004 is executed.

[0100] At 804, the second UE may send an indication of a reduced network condition at the second UE to the first UE, the indication being associated with at least one of TMMBr, TMMBn, a reduced bit rate, or a reduced downlink scheduling. Figure 4 , the second UE 404 may send an indication of a reduced network condition at the second UE 404 to the first UE 402 at 408. The indication sent to the first UE 402 at 408 may be TMMBr and / or indicate a communication bit rate or downlink schedule associated with the second UE 404. The sending at 804 may be based on Fig.10 The TMMBr component 199 of the device 1004 is executed.

[0101] Fig. 9 900 is a flow chart of a method of wireless communication. The method may be performed by a second UE (e.g., UE 103, 310, 404, device 1004, etc.), which may include a memory 376 and may correspond to the entire UE 103, 310, 404 or device 1004 or a component of the UE 103, 310, 404 or device 1004, such as the TX processor 316, the RX processor 370, the controller / processor 375, the cellular baseband processor 1024 and / or the application processor 1006.

[0102] At 902, the second UE may receive a local indication of a degraded network condition at the second UE. Figure 4 , the second UE 404 may detect a degraded network condition at the second UE 404 at 406. The receiving at 902 may be based on Fig.10 The TMMBr component 199 of the device 1004 is executed.

[0103] At 904, the second UE may send an indication of a reduced network condition at the second UE to the first UE, the indication being associated with at least one of TMMBr, TMMBn, a reduced bit rate, or a reduced downlink scheduling. Figure 4 , the second UE 404 may send an indication of a reduced network condition at the second UE 404 to the first UE 402 at 408. The indication sent to the first UE 402 at 408 may be TMMBr and / or indicate a communication bit rate or downlink schedule associated with the second UE 404. The sending at 904 may be based on Fig.10 The TMMBr component 199 of the device 1004 is executed.

[0104] At 906, the second UE may receive TMMBn as a confirmation of the indication sent to the first UE, the indication corresponding to TMMBr, and the adjusted bit rate for communications from the first UE is adjusted based on TMMBn being received as a confirmation of the indication sent to the first UE. For example, see Figure 4 , the second UE 404 may receive TMMBn from the first UE 402 at 411, which may indicate the adjusted communication bit rate with the first UE 402. The TMMBn received from the first UE 402 at 411 may be in response to the indication of the reduced network condition at the second UE 404 sent to the first UE 402 at 408. The reception at 906 may be based on Fig.10 The TMMBr component 199 of the device 1004 is executed.

[0105] At 908, the second UE may receive a request for at least one of BLER information associated with the second UE or grant information associated with the second UE based on the indication of the degraded network condition at the second UE sent to the first UE. Figure 4, the second UE 404 may receive a request for / send a response to the BLER and / or grant information associated with the second UE 404 at 414. The second UE 404 may receive a request for / send a response to the BLER and / or grant information at 414 based on the indication of the reduced network condition at the second UE 404 sent to the first UE 402 at 408. The receiving at 908 may be based on Fig.10 The TMMBr component 199 of the device 1004 is executed.

[0106] At 910, the second UE may receive communications from the first UE based on the adjusted bit rate associated with the indication of reduced network conditions at the second UE sent to the first UE. Figure 4 , the second UE 404 may receive communications from the first UE 402 at 416 based on the adjusted bit rate associated with the reduced network condition of the second UE 404 indicated to the first UE 402 at 408. The reception at 910 may be based on Fig.10 The TMMBr component 199 of the device 1004 is executed.

[0107] At 912, the second UE may send one or more subsequent indications of reduced network conditions at the second UE based on one or more requests for reduced bit rates, the one or more requests for reduced bit rates being at least one of sent to the first UE within a predefined duration or associated with reducing the reduced bit rate to a minimum threshold. For example, see Figure 4 , the second UE 404 may send one or more subsequent indications of reduced network conditions at the second UE 404 to the first UE 402 at 418. The one or more subsequent indications sent to the first UE 402 at 418 may be associated with a reduced bit rate for a predefined duration or a reduction in the bit rate to a minimum threshold. The sending at 912 may be based on Fig.10 The TMMBr component 199 of the device 1004 is executed.

[0108] Fig.101000 is a diagram illustrating an example of a hardware implementation for an apparatus 1004. The apparatus 1004 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1004 may include a cellular baseband processor 1024 (also referred to as a modem) coupled to one or more transceivers 1022 (e.g., a cellular RF transceiver). The cellular baseband processor 1024 may include on-chip memory 1024'. In some aspects, the apparatus 1004 may also include one or more subscriber identity module (SIM) cards 1020 and an application processor 1006 coupled to a secure digital (SD) card 1008 and a screen 1010. The application processor 1006 may include on-chip memory 1006'. In some aspects, the device 1004 may also include a Bluetooth module 1012, a WLAN module 1014, an SPS module 1016 (e.g., a GNSS module), one or more sensor modules 1018 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; an optical and / or radio wave detection device, an optical and / or radio wave ranging device, a sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional module of a memory 1026, a power source 1030, and / or a camera 1032. The Bluetooth module 1012, the WLAN module 1014, and the SPS module 1016 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1012, the WLAN module 1014, and the SPS module 1016 may include their own dedicated antennas and / or communicate using an antenna 1080. The cellular baseband processor 1024 communicates with the UE 104 and / or with the RU associated with the network entity 1002 through the transceiver 1022 via one or more antennas 1080. The cellular baseband processor 1024 and the application processor 1006 may each include a computer-readable medium / memory 1024', 1006', respectively. The additional modules of the memory 1026 may also be considered as computer-readable media / memory. Each computer-readable medium / memory 1024', 1006', 1026 may be non-transitory. The cellular baseband processor 1024 and the application processor 1006 are each responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 1024 / application processor 1006, enables the cellular baseband processor 1024 / application processor 1006 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1024 / application processor 1006 when executing the software.The cellular baseband processor 1024 / application processor 1006 may be a component of the UE 350 / 310 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1004 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1024 and / or the application processor 1006, while in another configuration, the device 1004 may be the entire UE (e.g., see. Figure 3 350) and includes additional modules of device 1004.

[0109] As discussed above, the remote UE indication component 198 is configured to receive from the second UE a first indication of a reduced network condition at the second UE, the first indication being associated with at least one of TMMBr, TMMBn, a reduced bit rate, or a reduced downlink scheduling; and based on the first indication received from the second UE, display at the first UE a second indication of a reduced network condition at the second UE. Also as discussed above, the TMMBr component 199 is configured to receive a local indication of a reduced network condition at the second UE; and send to the first UE an indication of a reduced network condition at the second UE, the indication being associated with at least one of TMMBr, TMMBn, a reduced bit rate, or a reduced downlink scheduling. The remote UE indication component 198 and / or the TMMBr component 199 may be within the cellular baseband processor 1024, within the application processor 1006, or within both the cellular baseband processor 1024 and the application processor 1006. The remote UE indication component 198 and / or the TMMBr component 199 can be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above.

[0110] As shown, the device 1004 may include multiple components configured for various functions. In a first configuration, the device 1004 and specifically the cellular baseband processor 1024 and / or the application processor 1006 include: a component for receiving a first indication of a reduced network condition at the second UE from the second UE, the first indication being associated with at least one of TMMBr, TMMBn, a reduced bit rate, or a reduced downlink scheduling; and a component for displaying a second indication of a reduced network condition at the second UE at the first UE based on the first indication received from the second UE. The device 1004 also includes a component for adjusting a bit rate for communication with the second UE based on the first indication of a reduced network condition at the second UE received from the second UE. The device 1004 also includes a component for sending TMMBn as a confirmation of the first indication, wherein the first indication corresponds to TMMBr, and the bit rate for communication with the second UE is adjusted based on the TMMBn being sent as a confirmation of the first indication. The apparatus 1004 also includes means for receiving one or more subsequent indications of reduced network conditions at the second UE, the one or more subsequent indications associated with one or more requests for a reduced bit rate, wherein a second indication is displayed at the first UE based on at least one of receiving the one or more subsequent indications within a predefined duration or reducing the reduced bit rate to a minimum threshold. The apparatus 1004 also includes means for sending a request for at least one of BLER information associated with the second UE or grant information associated with the second UE based on the first indication of reduced network conditions at the second UE received from the second UE.

[0111] In a second configuration, the apparatus 1004, and specifically the cellular baseband processor 1024 and / or the application processor 1006, includes: means for receiving a local indication of reduced network conditions at a second UE; and means for sending an indication of reduced network conditions at the second UE to a first UE, the indication being associated with at least one of TMMBr, TMMBn, reduced bit rate, or reduced downlink scheduling. The apparatus 1004 also includes means for receiving communications from the first UE based on the adjusted bit rate associated with the indication of reduced network conditions at the second UE sent to the first UE. The apparatus 1004 also includes means for receiving TMMBn as a confirmation of the indication sent to the first UE, wherein the indication corresponds to TMMBr, and the adjusted bit rate for communications from the first UE is adjusted based on TMMBn being received as a confirmation of the indication sent to the first UE. The apparatus 1004 also includes means for sending one or more subsequent indications of reduced network conditions at the second UE based on one or more requests for a reduced bit rate, wherein the one or more requests for a reduced bit rate are at least one of sent to the first UE within a predefined duration or associated with reducing the reduced bit rate to a minimum threshold. The apparatus 1004 also includes means for receiving a request for at least one of BLER information associated with the second UE or grant information associated with the second UE based on the indication of reduced network conditions at the second UE sent to the first UE.

[0112] The component may be a remote UE indication component 198 and / or a TMMBr component 199 of the apparatus 1004 configured to perform the functions recited by the component. As described above, the apparatus 1004 may include a TX processor 368 / 316, an RX processor 356 / 370, and a controller / processor 359 / 375. Therefore, in one configuration, the component may be a TX processor 368 / 316, an RX processor 356 / 370, and a controller / processor 359 / 375 configured to perform the functions recited by the component.

[0113] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is only an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. In addition, some blocks can be combined or omitted. The attached method claims provide the elements of each block in a sample order, but are not limited to the specific order or hierarchy provided.

[0114] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when ..." and "at ..." do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ...", do not mean an instant action in response to the occurrence of an action or during the occurrence of an action, but only mean that if the condition is met, the action will occur without a specific or instantaneous time constraint to make the action occur. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having an advantage over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, data may be directly received / sent between the first device and the second device, or indirectly received / sent between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will be known later to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device" cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0115] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0116] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0117] Aspect 1 is a method for performing wireless communication at a first UE, the method comprising: receiving a first indication of reduced network conditions at a second UE from the second UE, the first indication being associated with at least one of TMMBr, TMMBn, reduced bit rate, or reduced downlink scheduling; and displaying a second indication of the reduced network conditions at the second UE at the first UE based on the first indication received from the second UE.

[0118] Aspect 2 may be combined with aspect 1 and further comprises adjusting a bit rate for communication with the second UE based on the first indication of the degraded network condition at the second UE received from the second UE.

[0119] Aspect 3 can be combined with any one of Aspects 1 to 2, and also includes sending the TMMBn as a confirmation of the first indication, wherein the first indication corresponds to the TMMBr, and the bit rate used for the communication with the second UE is adjusted based on the TMMBn being sent as the confirmation of the first indication.

[0120] Aspect 4 may be combined with any one of Aspects 1 to 3, and includes the second indication displayed at the first UE indicating at least one of the degraded network condition at the second UE, the undegraded network condition at the first UE, the session condition of the first UE, or the session condition of the second UE.

[0121] Aspect 5 can be combined with any one of Aspects 1 to 4, and also includes receiving one or more subsequent indications of the reduced network conditions at the second UE, the one or more subsequent indications being associated with one or more requests for the reduced bit rate, wherein the second indication is displayed at the first UE based on at least one of receiving the one or more subsequent indications within a predefined duration or reducing the reduced bit rate to a minimum threshold.

[0122] Aspect 6 may be combined with any one of aspects 1 to 5, and includes the degraded network condition at the second UE corresponding to at least one of increased network congestion or degraded channel condition associated with the second UE.

[0123] Aspect 7 can be combined with any one of Aspects 1 to 6, and also includes sending a request for at least one of BLER information associated with the second UE or grant information associated with the second UE based on the first indication of the reduced network condition at the second UE received from the second UE.

[0124] Aspect 8 may be combined with any one of Aspects 1 to 7, and includes the first indication of the reduced network condition at the second UE corresponding to at least one of in-band signaling from the second UE or an RTP packet indicating the reduced network condition at the second UE.

[0125] Aspect 9 can be combined with any one of aspects 1 to 8, and includes that the at least one of the in-band signaling or the RTP packet indicates at least one of an RTP extended header ID, channel conditions, grant information, RSRP, RSRQ, RSSI or SINR.

[0126] Aspect 10 may be combined with any one of Aspects 1 to 9, and includes a first number of bits associated with the first indication received from the second UE indicating the RTP extended header ID, and a second number of bits associated with the first indication received from the second UE indicating one or more of the channel condition, the grant information, the RSRP, the RSRQ, the RSSI or the SINR.

[0127] Aspect 11 may be combined with any one of aspects 1 to 10, and includes displaying, at the first UE, the second indication indicating a cause of the degraded network condition at the second UE based on the first indication corresponding to the RTP packet.

[0128] Aspect 12 is a method for wireless communication at a second UE, the method comprising: receiving a local indication of reduced network conditions at the second UE; and sending an indication of the reduced network conditions at the second UE to a first UE, the indication being associated with at least one of TMMBr, TMMBn, reduced bit rate, or reduced downlink scheduling.

[0129] Aspect 13 may be combined with aspect 12, and further comprises receiving communications from the first UE based on the adjusted bit rate associated with the indication of the reduced network condition at the second UE sent to the first UE.

[0130] Aspect 14 can be combined with any one of Aspects 12 to 13, and also includes receiving the TMMBn as a confirmation of the indication sent to the first UE, wherein the indication corresponds to the TMMBr, and the adjusted bit rate for the communication from the first UE is adjusted based on the TMMBn being received as the confirmation of the indication sent to the first UE.

[0131] Aspect 15 may be combined with any one of Aspects 12 to 14 and also includes sending one or more subsequent indications of the reduced network condition at the second UE based on one or more requests for the reduced bit rate, wherein the one or more requests for the reduced bit rate are sent to the first UE within a predefined duration or are associated with reducing the reduced bit rate to a minimum threshold.

[0132] Aspect 16 may be combined with any one of aspects 12 to 15, and includes the degraded network condition at the second UE corresponding to at least one of increased network congestion or degraded channel condition associated with the second UE.

[0133] Aspect 17 may be combined with any one of aspects 12 to 16, and further comprises receiving a request for at least one of BLER information associated with the second UE or grant information associated with the second UE based on the indication of the reduced network condition at the second UE sent to the first UE.

[0134] Aspect 18 may be combined with any one of aspects 12 to 17, and includes the indication of the reduced network condition at the second UE corresponding to at least one of in-band signaling to the first UE or an RTP packet indicating the reduced network condition at the second UE.

[0135] Aspect 19 may be combined with any one of aspects 12 to 18, and includes the in-band signaling or the at least one of the RTP packets indicating at least one of an RTP extended header ID, channel conditions, grant information, RSRP, RSRQ, RSSI or SINR.

[0136] Aspect 20 may be combined with any one of Aspects 12 to 19, and includes a first number of bits associated with the indication sent to the first UE indicating the RTP extended header ID, and a second number of bits associated with the indication sent to the first UE indicating one or more of the channel condition, the grant information, the RSRP, the RSRQ, the RSSI or the SINR.

[0137] Aspect 21 is an apparatus for wireless communication, wherein the apparatus is configured to implement the method according to any one of aspects 1 to 20.

[0138] Aspect 22 is an apparatus for wireless communication, the apparatus comprising means for implementing the method according to any one of aspects 1 to 20.

[0139] Aspect 23 may be combined with any of aspects 21 to 22, and further comprises at least one of a transceiver or an antenna coupled to at least one processor of the apparatus.

[0140] Aspect 24 is a non-transitory computer readable medium storing computer executable code, which, when executed by at least one processor, causes the at least one processor to implement the method according to any one of aspects 1 to 20.

Claims

1. An apparatus for wireless communication at a first user equipment (UE), comprising: Memory; as well as at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: receiving, from a second UE, a first indication of reduced network conditions at the second UE, the first indication being associated with at least one of a temporary maximum media stream bitrate request (TMMBr), a temporary maximum media stream bitrate notification (TMMBn), a reduced bitrate, or a reduced downlink scheduling; as well as A second indication of the degraded network condition at the second UE is displayed at the first UE based on the first indication received from the second UE.

2. The apparatus of claim 1, wherein the at least one processor is further configured to adjust a bit rate for communication with the second UE based on the first indication of the degraded network condition at the second UE received from the second UE.

3. The apparatus of claim 2, wherein the at least one processor is further configured to send the TMMBn as a confirmation of the first indication, wherein the first indication corresponds to the TMMBr, and the bit rate for the communication with the second UE is adjusted based on the TMMBn being sent as the confirmation of the first indication.

4. The apparatus of claim 1, wherein the second indication displayed at the first UE indicates at least one of the degraded network condition at the second UE, the undegraded network condition at the first UE, the session condition of the first UE, or the session condition of the second UE.

5. The apparatus of claim 1 , wherein the at least one processor is further configured to receive one or more subsequent indications of the reduced network condition at the second UE, the one or more subsequent indications being associated with one or more requests for the reduced bit rate, wherein the second indication is displayed at the first UE based on at least one of receiving the one or more subsequent indications within a predefined duration or reducing the reduced bit rate to a minimum threshold.

6. The apparatus of claim 1, wherein the degraded network condition at the second UE corresponds to at least one of increased network congestion or degraded channel conditions associated with the second UE.

7. The apparatus of claim 1 , wherein the at least one processor is further configured to send a request for at least one of block error rate (BLER) information associated with the second UE or grant information associated with the second UE based on the first indication of the reduced network condition at the second UE received from the second UE.

8. The apparatus of claim 1, wherein the first indication of the reduced network condition at the second UE corresponds to at least one of in-band signaling from the second UE or a real-time transport protocol (RTP) packet indicating the reduced network condition at the second UE.

9. The apparatus of claim 8, wherein the at least one of the in-band signaling or the RTP packet indicates at least one of an RTP extended header identifier (ID), a channel condition, grant information, a reference signal received power (RSRP), a reference signal received quality (RSRQ), a received signal strength indicator (RSSI), or a signal to interference plus noise ratio (SINR).

10. The apparatus of claim 9, wherein a first number of bits associated with the first indication received from the second UE indicates the RTP extended header ID, and a second number of bits associated with the first indication received from the second UE indicates one or more of the channel condition, the grant information, the RSRP, the RSRQ, the RSSI, or the SINR.

11. The apparatus of claim 8, wherein the second indication is displayed at the first UE based on the first indication corresponding to the RTP packet, the second indication indicating a cause of the degraded network condition at the second UE.

12. The apparatus of claim 1, further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

13. An apparatus for wireless communication at a second user equipment (UE), comprising: Memory; as well as at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: receiving a local indication of degraded network conditions at the second UE; as well as An indication of the reduced network condition at the second UE is sent to the first UE, the indication being associated with at least one of a temporary maximum media stream bitrate request (TMMBr), a temporary maximum media stream bitrate notification (TMMBn), a reduced bitrate, or a reduced downlink scheduling.

14. The apparatus of claim 13, wherein the at least one processor is further configured to receive communications from the first UE based on an adjusted bit rate associated with the indication of the reduced network condition at the second UE sent to the first UE.

15. An apparatus according to claim 14, wherein the at least one processor is further configured to receive the TMMBn as a confirmation of the indication sent to the first UE, wherein the indication corresponds to the TMMBr, and the adjusted bit rate for the communication from the first UE is adjusted based on the TMMBn being received as the confirmation of the indication sent to the first UE.

16. An apparatus according to claim 13, wherein the at least one processor is further configured to send one or more subsequent indications of the reduced network condition at the second UE based on one or more requests for the reduced bit rate, wherein the one or more requests for the reduced bit rate are at least one of sent to the first UE within a predefined duration or associated with reducing the reduced bit rate to a minimum threshold.

17. The apparatus of claim 13, wherein the degraded network condition at the second UE corresponds to at least one of increased network congestion or degraded channel conditions associated with the second UE.

18. The apparatus of claim 13, wherein the at least one processor is further configured to receive a request for at least one of block error rate (BLER) information associated with the second UE or grant information associated with the second UE based on the indication of the reduced network condition at the second UE sent to the first UE.

19. The apparatus of claim 13, wherein the indication of the reduced network condition at the second UE corresponds to at least one of in-band signaling to the first UE or a real-time transport protocol (RTP) packet indicating the reduced network condition at the second UE.

20. The apparatus of claim 19, wherein the at least one of the in-band signaling or the RTP packet indicates at least one of an RTP extended header identifier (ID), a channel condition, grant information, a reference signal received power (RSRP), a reference signal received quality (RSRQ), a received signal strength indicator (RSSI), or a signal to interference plus noise ratio (SINR).

21. An apparatus according to claim 20, wherein a first number of bits associated with the indication sent to the first UE indicates the RTP extended header ID, and a second number of bits associated with the indication sent to the first UE indicates one or more of the channel condition, the grant information, the RSRP, the RSRQ, the RSSI, or the SINR.

22. A method of wireless communication at a first user equipment (UE), the method comprising: receiving, from a second UE, a first indication of reduced network conditions at the second UE, the first indication being associated with at least one of a temporary maximum media stream bitrate request (TMMBr), a temporary maximum media stream bitrate notification (TMMBn), a reduced bitrate, or a reduced downlink scheduling; as well as A second indication of the degraded network condition at the second UE is displayed at the first UE based on the first indication received from the second UE.

23. The method of claim 22, further comprising adjusting a bit rate for communications with the second UE based on the first indication of the degraded network condition at the second UE received from the second UE.

24. The method of claim 23, further comprising sending the TMMBn as a confirmation of the first indication, wherein the first indication corresponds to the TMMBr, and the bit rate used for the communication with the second UE is adjusted based on the TMMBn being sent as the confirmation of the first indication.

25. The method of claim 22, wherein the second indication displayed at the first UE indicates at least one of the degraded network condition at the second UE, the undegraded network condition at the first UE, the session status of the first UE, or the session status of the second UE.

26. The method of claim 22, further comprising receiving one or more subsequent indications of the reduced network condition at the second UE, the one or more subsequent indications being associated with one or more requests for the reduced bit rate, wherein the second indication is displayed at the first UE based on at least one of receiving the one or more subsequent indications within a predefined duration or reducing the reduced bit rate to a minimum threshold.

27. The method of claim 22, wherein the degraded network condition at the second UE corresponds to at least one of increased network congestion or degraded channel conditions associated with the second UE.

28. The method of claim 22, further comprising sending a request for at least one of block error rate (BLER) information associated with the second UE or grant information associated with the second UE based on the first indication of the reduced network condition at the second UE received from the second UE.

29. The method of claim 22, wherein the first indication of the reduced network condition at the second UE corresponds to at least one of in-band signaling from the second UE or a real-time transport protocol (RTP) packet indicating the reduced network condition at the second UE.

30. A method of wireless communication at a second user equipment (UE), the method comprising: receiving a local indication of degraded network conditions at the second UE; as well as An indication of the reduced network condition at the second UE is sent to the first UE, the indication being associated with at least one of a temporary maximum media stream bitrate request (TMMBr), a temporary maximum media stream bitrate notification (TMMBn), a reduced bitrate, or a reduced downlink scheduling.

Images