CN114402561B

CN114402561B - Method and apparatus for selecting a time division duplex time slot format specific to a user equipment

Info

Publication number: CN114402561B
Application number: CN202080064765.5A
Authority: CN
Inventors: 王继兵; 阿米尔·阿克拉姆; 埃里克·理查德·施陶费尔
Original assignee: Google LLC
Current assignee: Google LLC
Priority date: 2019-09-20
Filing date: 2020-09-02
Publication date: 2024-02-20
Anticipated expiration: 2040-09-02
Also published as: CN114402561A; WO2021055167A1; BR112022004996A2

Abstract

In some aspects, a network entity establishes (1305) a wireless connection between a base station and a user equipment based at least in part on a first time division duplex slot format, wherein the time division duplex slot format assigns communication resources of the wireless connection using a first arrangement of a combination of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments. The network then identifies (1310) one or more metrics associated with the wireless connection, and determines (1315) a second time division duplex slot format based on the one or more metrics using a second arrangement of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments. The network entity then reconfigures (1320) the wireless connection between the base station and the user equipment by instructing the user equipment to exchange communications over the wireless connection based on the second time division duplex slot format.

Description

Method and apparatus for selecting a time division duplex time slot format specific to a user equipment

Background

Wireless communication systems provide users with the flexibility to move while maintaining connections with other devices and networks. For example, a User Equipment (UE) maintains a connection with a wireless network by establishing a connection to a first base station, switching to a second base station, etc., while moving through an area. However, the dynamic nature of these connections presents challenges in maintaining the quality and/or efficiency level of the connection. To illustrate, a first connection between UEs near a center of a cell service provided by a base station has different transmission characteristics than a second connection between UEs at an edge of the cell service provided by the base station. These different transmission characteristics distort the communication transmitted using the first connection in a different manner than the communication transmitted over the second connection. As another example, the first UE may execute a service or application that utilizes more communication resources of the network relative to a service or application executed at the second UE. Thus, mobility and dynamic communication resource usage of the UE may make it difficult to maintain quality and/or efficiency levels of the corresponding connection to the network.

Disclosure of Invention

This document describes techniques and apparatuses for configuring a user equipment-specific Time Division Duplex (TDD) slot format. In some aspects, a network entity establishes a wireless connection between a base station and a user equipment based at least in part on a first Time Division Duplex (TDD) slot format. In an implementation, the TDD slot format assigns communication resources of the wireless connection using a first arrangement of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments. The network then identifies one or more metrics associated with the wireless connection, and determines a second TDD slot format based on the one or more metrics using a second arrangement of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments, wherein the second arrangement is different from the first arrangement. The network entity then reconfigures the wireless connection between the base station and the user equipment by instructing the user equipment to exchange communications over the wireless connection based on the second TDD slot format.

Some aspects of configuring a user equipment specific TDD slot format use a TDD slot format received from a user equipment. One or more implementations of a network entity establish a wireless connection between a base station and a user equipment based at least in part on a first TDD slot format that assigns communication resources using a first arrangement of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments. The network entity then receives a request from the user equipment indicating a second TDD slot format that assigns communication resources using a second arrangement of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments, wherein the second assignment is different from the first assignment. The network entity then reconfigures the wireless connection between the base station and the user equipment by instructing the user equipment to exchange communications over the wireless connection using the second TDD slot format.

Some aspects of configuring a user equipment specific TDD slot format configure the TDD slot format based on an operational state of the wireless communication system. In an implementation, a network entity establishes a wireless connection between a base station and a user equipment using a first TDD slot format that assigns communication resources of the wireless connection using a first configured uplink communication assignment, downlink communication assignment, and/or gap transmission assignment. The network entity then determines that a network interference level associated with the wireless communication system exceeds a threshold. In response to the network interference level exceeding the threshold, the network entity determines a second TDD slot format that assigns communication resources of the wireless connection based on a second arrangement of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments. In an implementation, the network entity then reconfigures the wireless connection between the base station and the user equipment by instructing the user equipment to exchange communications over the wireless connection using the second TDD slot format.

In some aspects, a user equipment establishes a wireless connection with a base station based at least in part on a first TDD slot format that assigns communication resources of the wireless connection using a first arrangement of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments. In response to establishing the wireless connection, the user equipment generates one or more metrics and transmits the metrics to the base station. The user equipment then receives a second TDD slot format that assigns communication resources of the wireless connection using a second arrangement of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments, wherein the second arrangement is different from the first arrangement. In an implementation, the user equipment then reconfigures the wireless connection based on the second TDD slot format.

In some implementations, a user equipment initiates an operation associated with a quality of service flow and communicates an indication of the quality of service flow associated with the operation to a base station. The user equipment then receives a TDD slot format that assigns communication resources of the wireless connection using an arrangement of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments, wherein the arrangement is based at least in part on the indication transmitted by the user equipment. In an implementation, the user equipment then establishes a wireless connection with the base station based on the TDD slot format and exchanges communications associated with the operation with the base station using the wireless connection.

The details of one or more implementations of selecting a user equipment specific TDD slot format are set forth in the accompanying drawings and the description below. Other features and advantages will be apparent from the description and drawings, and from the claims. This summary is provided to introduce a selection of subject matter that is further described in the detailed description and drawings. This summary is not, therefore, to be considered an essential feature of the description, nor is it intended to be used to limit the scope of the claimed subject matter.

Drawings

Details of configuring one or more aspects of a user equipment specific Time Division Duplex (TDD) slot format are described below. The use of the same reference symbols in different instances in the description and the figures indicates similar elements:

fig. 1 illustrates an example environment in which aspects of configuring a user equipment-specific Time Division Duplex (TDD) slot format can be implemented.

Fig. 2 illustrates an example device diagram of a device that may implement aspects of selecting a user device-specific TDD slot format.

Fig. 3 illustrates an example device diagram of a device that may implement aspects of selecting a user device-specific TDD slot format.

Fig. 4 illustrates an example environment 400 in which devices communicate with each other using a TDD slot format configuration.

Fig. 5 illustrates an example of a TDD slot format for assigning communication resources in accordance with one or more implementations.

Fig. 6 illustrates an example of a TDD slot format for assigning communication resources in accordance with one or more implementations.

Fig. 7 illustrates an example TDD slot format in accordance with one or more implementations.

Fig. 8 illustrates an example transaction diagram between various devices for selecting a user device specific TDD slot format.

Fig. 9 illustrates an example transaction diagram between various devices for selecting a user device specific TDD slot format.

Fig. 10 illustrates an example transaction diagram between various devices for selecting a user device specific TDD slot format.

Fig. 11 illustrates an example transaction diagram between various devices for selecting a user device specific TDD slot format.

Fig. 12 illustrates an example transaction diagram between various devices for selecting a user device specific TDD slot format.

Fig. 13 illustrates an example method for selecting a user equipment specific TDD slot format.

Fig. 14 illustrates an example method for selecting a user equipment specific TDD slot format.

Fig. 15 illustrates an example method for selecting a user equipment specific TDD slot format.

Fig. 16 illustrates an example method for selecting a user equipment specific TDD slot format.

Fig. 17 illustrates an example method for selecting a user equipment specific TDD slot format.

Detailed Description

Wireless networks provide users with the flexibility to move while maintaining connections with other devices and networks. However, these wireless networks have limited communication resources such that as more and more devices connect to the wireless network, allocation of these resources is challenging. As another challenge, the transmission environment of a mobile device in a wireless network continuously changes as the mobile device moves, thus affecting the efficiency of use of communication resources. In some cases, the service or application running at the first mobile device utilizes more communication resources than the service or application running at the second mobile device. Accordingly, there is a need to dynamically allocate and reallocate communication resources upon a change in the operating environment and/or state of a mobile device.

This document describes aspects of selecting a user equipment specific TDD slot format. In some aspects, a network entity establishes a wireless connection between a base station and a user equipment based at least in part on a first Time Division Duplex (TDD) slot format. In an implementation, the TDD slot format assigns communication resources of the wireless connection using a first arrangement of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments. The network then identifies one or more metrics associated with the wireless connection, and determines a second TDD slot format based on the one or more metrics using a second arrangement of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments, wherein the second arrangement is different from the first arrangement. The network entity then reconfigures the wireless connection between the base station and the user equipment by instructing the user equipment to exchange communications over the wireless connection based on the second TDD slot format.

Some aspects of configuring a user equipment specific TDD slot format use a TDD slot format received from a user equipment. One or more implementations of a network entity establish a wireless connection between a base station and a user device based at least in part on a first TDD slot format that assigns communication resources using a first arrangement of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments. The network entity then receives a request from the user equipment indicating a second TDD slot format that assigns communication resources using a second arrangement of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments, wherein the second arrangement is different from the first arrangement. The network entity then reconfigures the radio connection between the base station and the user equipment by instructing the user equipment to exchange communications over the radio connection using the second TDD slot format.

Some aspects of configuring a user equipment specific TDD slot format configure the TDD slot format based on an operational state of the wireless communication system. In an implementation, the network entity establishes a wireless connection between the base station and the user equipment using a first TDD slot format that assigns communication resources of the wireless connection using a first arrangement uplink communication assignment, downlink communication assignment, and/or gap transmission assignment. The network entity then determines that a network interference level associated with the wireless communication system exceeds a threshold. In response to the network interference level exceeding the threshold, the network entity determines a second TDD slot format for assigning communication resources of the wireless connection based on a second arrangement of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments. In an implementation, the network entity then reconfigures the wireless connection between the base station and the user equipment by instructing the user equipment to exchange communications over the wireless connection using the second TDD slot format.

Example Environment

Fig. 1 illustrates an example environment 100 including a user equipment 110 (UE 110), which user equipment 110 may communicate with a base station 120 (illustrated as base stations 121 and 122) through one or more wireless communication links 130 (wireless link 130) illustrated as wireless links 131 and 132. For simplicity, the user device 110 is implemented as a smart phone, but may be implemented as any suitable computing or electronic device, such as a mobile communication device, modem, cellular phone, gaming device, navigation device, media device, laptop, desktop computer, tablet computer, smart appliance, or vehicle-based communication system, or internet of things (IoT) such as a sensor or actuator. The base station 120 may be implemented in a macrocell, microcell, picocell, etc., or any combination thereof (e.g., evolved universal terrestrial radio access network node B, E-UTRAN node B, evolved node B, eNodeB, eNB, next generation node B, enode B, gNB, ng-eNB, etc.).

Base station 120 communicates with user equipment 110 using wireless links 131 and 132, which may be implemented as any suitable type of wireless link. Wireless links 131 and 132 include control and data communications such as a downlink of data and control information communicated from base station 120 to user equipment 110, an uplink of other data and control information communicated from user equipment 110 to base station 120, or both. Wireless link 130 may include one or more wireless links (e.g., radio links) or bearers implemented using any suitable communication protocol or standard or combination of communication protocols or standards, such as: third generation partnership project long term evolution (3 GPP LTE), fifth generation new radio (5G NR), etc. Multiple radio links 130 may be aggregated in carrier aggregation to provide higher data rates for UE 110. Multiple wireless links 130 from multiple base stations 120 may be configured for coordinated multipoint (CoMP) communication with UE 110.

The base stations 120 are collectively a radio access network 140 (e.g., RAN, evolved universal terrestrial radio access network, E-UTRAN, 5G NR RAN, or NR RAN). Base stations 121 and 122 in RAN 140 are connected to core network 150. Base stations 121 and 122 connect to core network 150 at 102 and 104 through NG2 interfaces for control plane signaling and using NG3 interfaces for user plane data communications when connected to a 5G core network or using S1 interfaces for control plane signaling and user plane signaling communications when connected to an Evolved Packet Core (EPC) network, respectively. Base stations 121 and 122 may communicate at 106 over an Xn interface using an Xn application protocol (XnAP) or over an X2 interface using an X2 application protocol (X2 AP) to exchange user plane and control plane data. User device 110 may connect to a public network, such as the internet 160, via core network 150 to interact with remote service 170.

Example apparatus

Fig. 2 illustrates an example device diagram 200 in which devices (e.g., one of UE110, base station 120) that manage aspects of radio access technology capabilities may be implemented. The user equipment 110 and the base station 120 may include additional functions and interfaces that have been omitted from fig. 2 for clarity.

User equipment 110 includes an antenna 202, a radio frequency front end 204 (RF front end 204), a LET transceiver 206, and a 5G NR transceiver 208 for communication with base stations 120 in RAN 140. The RF front end 204 of the user equipment 110 may couple or connect the LTE transceiver 206 and the 5G NR transceiver 208 to the antenna 202 to facilitate various types of wireless communications. The antenna 202 of the user equipment 110 may include an array of multiple antennas configured similarly or differently from each other. Antenna 202 and RF front end 204 may be tuned and/or tunable to one or more frequency bands defined by 3GPP LTE and 5G NR communication standards and implemented by LTE transceiver 206 and 5G NR transceiver 208. Additionally, the antenna 202, RF front end 204, LTE transceiver 206, and/or 5G NR transceiver 208 may be configured to support beamforming for transmission and reception of communications with the base station 120. By way of example and not limitation, antenna 202 and RF front end 204 may be implemented for operation in the below gigahertz frequency band, below 6GHZ frequency band, and/or above 6GHZ frequency band defined by 3GPP LTE and 5G NR communication standards.

The user device 110 also includes a processor 210 and a computer readable storage medium 212 (CRM 212). Processor 210 may be a single core processor or a multi-core processor composed of various materials such as silicon, polysilicon, high-K dielectric, copper, and the like. The computer-readable storage media described herein exclude propagating signals. CRM 212 may include any suitable memory or storage device, such as Random Access Memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read Only Memory (ROM), or flash memory, that may be used to store device data 214 for user device 110. Device data 214 includes user data, multimedia data, beamforming codebooks, applications, neural network tables, and/or operating systems for user device 110 that are executable by processor 212 to enable user plane communications, control plane signaling, and user interactions with UE 110.

The CRM 212 also includes a user equipment time division duplex configuration manager 216 (UE TDD configuration manager 216). Alternatively or additionally, UE TDD configuration manager 216 is an application that may be implemented in whole or in part as hardware logic or circuitry integrated with or separate from other components of UE 110. In some aspects, UE TDD configuration manager 216 receives a TDD slot format, such as from a base station or core network server, and manages communications transmitted from UE 110 and/or received by UE 110 based on the received TDD slot format. Alternatively or additionally, the UE TDD configuration manager 216 receives metrics such as UE-generated metrics (e.g., power headroom report, signal strength estimate, power status report) and analyzes the UE-generated metrics to determine modifications to the TDD slot format. For example, the UE TDD configuration manager analyzes the power headroom report and determines a modification to the TDD slot format based on the power headroom report, such as increasing the number of uplink slots and/or symbols in the TDD slot format, decreasing the number of uplink slots and/or symbols in the TDD slot format, adding gaps to the TDD slot format, removing gaps from the TDD slot format, increasing the number of downlink slots and/or symbols in the TDD slot format, decreasing the number of downlink slots and/or symbols in the TDD slot format, and so forth. In response to determining the modification to the TDD slot format, some implementations of UE TDD configuration manager 216 transmit a request to a base station (e.g., base station 120) requesting the modification to the TDD slot format.

The device diagram of the base station 120 shown in fig. 2 includes a single network node (e.g., a gNode B). The functionality of the base station 120 may be distributed across multiple network nodes or devices and may be distributed in any manner suitable for performing the functionality described herein. Base station 120 includes an antenna 252, a radio frequency front end 254 (RF front end 254), one or more LTE transceivers 256, and/or one or more 5GNR transceivers 258 for communicating with UE 110. The RF front end 254 of the base station 120 may couple or connect the LTE transceiver 256 and the 5GNR transceiver 258 to the antenna 252 to facilitate various types of wireless communications. The antenna 252 of the base station 120 may include an array of multiple antennas configured similarly or differently from each other. The antenna 252 and the RF front end 254 may be tuned and/or tunable to one or more frequency bands defined by the 3GPP LTE and 5GNR communication standards and implemented by the LTE transceiver 256 and/or the 5GNR transceiver 258. Additionally, antennas 252, RF front end 254, LTE transceiver 256, and/or 5G NR transceiver 258 may be configured to support beamforming, such as massive-MIMO, for transmission and reception of communications with UE 110.

The base station 120 also includes a processor 260 and a computer-readable storage medium 262 (CRM 262). Processor 260 may be a single core processor or a multi-core processor composed of various materials such as silicon, polysilicon, high-K dielectric, copper, and the like. CRM 262 may include any suitable memory or storage device such as Random Access Memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read Only Memory (ROM), or flash memory that may be used to store device data 264 for base station 120. The device data 264 includes network scheduling data, radio resource management data, beamforming codebooks, applications, and/or operating systems of the base station 120 that are executable by the processor 260 to enable communication with the user device 110.

CRM 262 also includes base station manager 266. Alternatively or additionally, the base station manager 266 may be implemented in whole or in part as hardware logic or circuitry that is integrated with or separate from other components of the base station 120. In at least some aspects, the base station manager 266 configures the LTE transceiver 256 and the 5GNR transceiver 258 for communication with the user equipment 110, as well as with a core network, such as the core network 150. In at least some aspects, base station manager 266 can cause base station 120 to exchange messages with UE 110 based on a TDD slot format, such as a TDD slot format identified by the base station TDD configuration manager.

The CRM 262 also includes a base station time division duplex configuration manager 268 (BS TDD configuration manager 268). Alternatively or additionally, BS TDD configuration manager 268 is an application that may be implemented in whole or in part as hardware logic or circuitry integrated with or separate from other components of base station 120. In some aspects, BS TDD configuration manager 268 determines a TDD slot format used when exchanging communications between a base station and a UE (e.g., UE 110). In an implementation, BS TDD configuration manager communicates a TDD slot format to base station manager 266 and/or UE 110. Sometimes, BS TDD configuration manager 268 receives metrics such as UE-generated metrics and/or base station-generated metrics (BS-generated metrics) and analyzes any combination of these metrics to determine modifications to the TDD slot format. For example, the BS TDD configuration manager analyzes the power headroom report and determines a modification to the TDD slot format based on the power headroom report, such as increasing the number of uplink slots and/or symbols in the TDD slot format, decreasing the number of uplink slots and/or symbols in the TDD slot format, adding gaps to the TDD slot format, removing gaps from the TDD slot format, increasing the number of downlink slots and/or symbols in the TDD slot format, decreasing the number of downlink slots and/or symbols in the TDD slot format, and so forth. In response to determining the modification to the TDD slot format, some implementations of BS TDD configuration manager 268 communicate the modified TDD slot format to base station manager 266 and/or UE 110 for exchanging communications between base station 120 and UE 110.

In one or more implementations, BS TDD configuration manager 268 receives a quality of service (QoS) flow identifier (QFI) indicating a QoS flow associated with UE 110, where the QoS flow corresponds to an exchange of information specific to a particular purpose (e.g., a particular application, a particular user, a particular service, etc.). In an implementation, qoS flows have varying priority and/or resource reservation mechanisms, where each QoS flow has a QoS profile describing the varying priority and/or resource reservation mechanism. Based on the QFI, the BS TDD configuration manager determines modifications to the TDD slot format aligned with the priority and resource requirements of the corresponding QoS flows and communicates the modified TDD slot format to the base station manager 266 and/or UE 110 for exchange of information between the base station and UE.

Sometimes BS TDD configuration manager 268 identifies the network interference level by any combination of measurements such as Reference Signal Received Power (RSRP), reference Signal Received Quality (RSRQ), uplink signal to interference and noise ratio (SINR), downlink SINR, uplink power interference level, downlink power interference level, received Signal Strength Indicator (RSSI), etc. In response to identifying that the network interference level has reached or exceeded the threshold, the BS TDD configuration manager determines a modification to the TDD slot format to improve (e.g., reduce) the network interference level, such as by modifying the TDD slot format to include more slots, reducing the number of downlink slots and/or symbols within the TDD slot format, and so forth.

Base station 120 also includes an inter-base station interface 270, such as an Xn and/or X2 interface, and base station manager 266 configures the inter-base station interface 270 to exchange user plane, control plane, and other information between other base stations 120 to manage communications of base station 120 with UE 110. The base station 120 includes a core network interface 272 and the base station manager 266 configures the core network interface 272 to exchange user plane, control plane, and other information with core network functions and/or entities.

In fig. 3, core network server 302 may provide all or part of the functions, entities, services, and/or gateways in core network 150. Each function, entity, service and/or gateway in the core network 150 may be provided as a service in the core network 150, distributed across multiple servers, or implemented on dedicated servers. For example, the core network server 302 may provide all or part of the services or functions of a User Plane Function (UPF), an access and mobility management function (AMF), a serving gateway (S-GW), a packet data network gateway (P-GW), a Mobility Management Entity (MME), an evolved packet data gateway (ePDG), and the like. The core network server 302 is illustrated as embodied on a single server comprising a processor 304 and a computer readable storage medium 306 (CRM 306). Processor 304 may be a single-core processor or a multi-core processor constructed of various materials such as silicon, polysilicon, high-K dielectric, copper, and the like. CRM 306 may include any suitable memory or storage device, such as Random Access Memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read Only Memory (ROM), hard disk drive, or flash memory, that may be used to store device data 308 for core network server 302. The device data 308 includes data for supporting core network functions or entities and/or an operating system of the core network server 302 that is executable by the processor 304.

The CRM 306 also includes one or more core network applications 310, which in one implementation are embodied on the CRM 306 (as shown). One or more core network applications 310 may implement functions such as UPF, AMF, S-GW, P-GW, MME, ePDG, and the like. Alternatively or additionally, one or more core network applications 310 may be implemented in whole or in part as hardware logic or circuitry integrated with or separate from other components of core network server 302.

The CRM 306 also includes a core time division duplex configuration manager 312 (core TDD configuration manager 312). Alternatively or additionally, the core TDD configuration manager 312 is an application that may be implemented in whole or in part as hardware logic or circuitry integrated with or separate from other components of the core network server 302. In some implementations, the core TDD configuration manager 312 determines a TDD slot format of a base station (e.g., base station 120) for use in exchanging communications with a UE (e.g., UE 110). In an implementation, the core TDD configuration manager communicates the TDD slot format to the base station 120, which in turn communicates the TDD slot format to the UE 110. Sometimes, the core TDD configuration manager 312 receives metrics such as UE-generated metrics and/or BS-generated metrics and analyzes and combines the metrics to determine modifications to the TDD slot format. For example, the core TDD configuration manager analyzes the power headroom report and determines a modification to the TDD slot format based on the power headroom report, such as increasing the number of uplink slots and/or symbols in the TDD slot format, decreasing the number of uplink slots and/or symbols in the TDD slot format, adding gaps to the TDD slot format, removing gaps from the TDD slot format, increasing the number of downlink slots and/or symbols to the TDD slot format, decreasing the number of downlink slots and/or symbols in the TDD slot format, and so forth. In response to determining the modification to the TDD slot format, some implementations of BS TDD configuration manager 268 communicate the modified TDD slot format to base station 120 and/or UE 110 for exchanging communications between base station 120 and UE 110.

In one or more implementations, the core TDD configuration manager 312 receives a QoS identifier indicating a QoS flow associated with the UE 110, such as from the base station 120. Based on the QoS identifier, the core TDD configuration manager determines modifications to the TDD slot format and communicates the modified TDD slot format to the base station 120 and/or UE 110 for exchanging communications between the base station and UE.

Sometimes, the core TDD configuration manager 312 identifies the network interference level by any combination of measurements, such as RSRP, RSRQ, SINR, RSSI. In response to identifying that the network interference level has reached or exceeded the threshold, the core TDD configuration manager determines a modification to the TDD slot format to improve (e.g., reduce) the network interference level, such as by modifying the TDD slot format to include more slots, reducing the number of downlink slots and/or symbols within the TDD slot format, and so forth. The core TDD configuration manager then communicates modifications to the TDD slot configuration to base station 120 and/or UE 110.

Core network server 302 also includes a core network interface 314 for communication of user plane and control plane data with core network 150, base station 120, or other functions or entities in UE 110. In an implementation, core network server 302 communicates the TDD slot format to base station 120 using core network interface 314. The core network server 302 may alternatively or additionally receive feedback and/or metrics from the base station 120 and/or the UE 110 (via the base station 120) using the core network interface 314.

Having described an example environment and example apparatus that may be used to select a UE-specific TDD slot format, consider now a discussion of TTD slot formats in accordance with one or more implementations.

TDD time slot format

Time division duplexing in a wireless communication system allows two connected devices to communicate with each other by sharing communication resources in time. Fig. 4 illustrates an example environment 400 in which a UE (e.g., UE 110) and a base station (e.g., base station 120) communicate with each other using a TDD slot format configuration.

Resource 402 represents one or more communication resources shared between UE 110 and base station 120. In this example, the resources 402 include a carrier frequency 404 shared between the UE 110 and the base station 120. In other words, base station 120 and UE 110 each transmit communications with each other using carrier frequency 404, where base station 120 transmits downlink communications 406 and UE 110 transmits uplink communications 408. In an implementation, the base station and the UE share the resource 402 based on a TTD slot format.

For exemplary purposes, consider now fig. 5, which illustrates an example 500 of a TDD slot format for assigning communication resources in accordance with one or more implementations. Example 500 includes a radio frame 502 representing a frame structure for communicating information in a wireless network, such as a 3gpp 5g network. A radio frame represents a unit of partitionable communication resources such as frequency resources and/or time resources.

For example, consider an implementation in which radio frame 502 corresponds to 10 milliseconds (ms) of information. Some implementations divide a radio frame by time and corresponding communication resources within the radio frame. For example, radio frame 502 includes subframes 504, 506, etc. up to subframe 508, which represents equally sized subframe partitions, where "size" indicates any measurable unit of communication resources, such as time. Referring to the example in which radio frame 502 includes 10ms of information, some implementations subdivide radio frame 502 into ten equal durations such that each subframe includes 1ms of information. However, it should be understood that a subframe may correspond to a partition of any size.

In an implementation, each subframe of the radio frame 502 partitions the communication resources into smaller units. For example, subframe 506 divides the communication resources into time slots, where the subframe may include any number of time slots, such as two time slots, four time slots, eight time slots, and so on. Alternatively or additionally, a subframe corresponds to one slot such that there is no segmentation within the subframe. For clarity, fig. 5 illustrates the time slots as partitions in time, but it should be understood that each time slot may alternatively or additionally partition other resources, such as frequency bands.

Subframe 506 includes a slot 510, which represents an example slot included in subframe 506, that includes any number of symbols, such as Orthogonal Frequency Division Modulation (OFDM) symbols. In an implementation, the TDD slot format splits communication resource assignments (e.g., downlink communication assignments, uplink communication assignments, gap transmission assignments) by time. For example, in slot 510, the TDD slot format assigns each symbol within a slot to either downlink or uplink communications. The TDD slot format assigns symbol 512 to an uplink communication, symbol 514 to a downlink communication, symbol 516 to an uplink communication, symbol 518 to a downlink communication, etc., until symbol 520 is assigned to an uplink communication. Thus, in an implementation, the TDD slot format assigns communication resources at the symbol level.

Consider now fig. 6, which illustrates another example in which a TDD slot format assigns communication resources of a wireless network. Similar to that described with reference to example 500, example 600 includes a radio frame 602 that partitions communication resources into a plurality of subframes (e.g., subframe 604, subframe 606, etc., until subframe 608), wherein each subframe further partitions communication resources into any number of slots (e.g., slot 610, slot 612, etc., until slot 614). In an implementation, the TDD slot format assigns communication resources at the slot level. For example, in example 600, the TDD slot format assigns slot 610 to an uplink communication, slot 612 to a downlink communication, and so on, wherein slot 614 is assigned to a downlink communication. When communication resources are assigned at the slot level, the TDD slot format assigns symbols within the corresponding slot. For example, in assigning time slots 612 to downlink communications, the TDD time slot format also assigns symbols 616 of the time slots to downlink communications. Thus, in an implementation, the TDD slot format assigns communication resources at the slot level.

Although example 500 and example 600 describe assigning symbols and slots to uplink and downlink communications, alternative or additional implementations use a TDD slot format to create transmission gaps, where the transmission gaps correspond to null transmissions (e.g., frequency bands and/or transmissions having power levels at noise power levels). Consider fig. 7, which illustrates an example 700 of a TDD slot format including assigning one or more communication resources to a gap transmission in accordance with one or more implementations.

Example 700 includes communication resources partitioned by time: partition 702, partition 704, partition 706, etc., until partition 708 and partition 710. In some implementations, partitions 702, 704, 706, 708, and 710 represent time slots, such as time slot 510 of fig. 5, time slots 610, 612, and 614 of fig. 6, and so on. In other implementations, partitions 702, 704, 706, 708, and 710 represent symbols, such as symbols 512, 514, 516, 518, and 520 of fig. 5, slot 612 of fig. 6, and so on. In example 700, the TDD slot format configures partition 702 and partition 710 as gap transmissions, denoted by "G" in fig. 7, and assigns partitions 704, 706, and 708 to downlink communications.

Example 700 also includes a plot 712 of power versus time illustrating communication transmissions between a UE and a base station using shared communication resources, such as downlink communication 406 and uplink communication 408 of fig. 4 of shared carrier frequency 404 between UE 110 and base station 120. More specifically, the power versus time plot 712 corresponds to communications based on the TDD slot formats represented by partitions 702, 704, 706, 708, and 710. For example, the portion of the power versus time table at time span 714 corresponds to communications (e.g., downlink communications) between the UE and the base station based on the TDD slot format assignment to partition 708. Here, the transmission has an arbitrary power level 716 to represent a communication transmission. The portion of the power versus time table at time span 718 also corresponds to TDD slot format based communications between the UE and the base station. However, at time span 718, the TDD slot format configures partition 710 as a gap transmission. Thus, neither the UE nor the base station uses the communication resources for transmission during this duration, since neither the UE nor the base station is assigned the communication resources associated with 710. This is further emphasized by the power level 720 corresponding to the noise floor power level, which power level 720 is lower than the power level 716. Thus, an implementation of the TDD slot format assigns gap transmissions to communication resources, which corresponds to not assigning communication resources to uplink or downlink communications.

Having described an example TTD slot format, consider now example signals and control transactions that can be used to select a UE-specific TDD slot format in accordance with one or more implementations.

Signaling and control transactions for communicating neural network formation configurations

Fig. 8-12 illustrate example signaling and control transaction diagrams between a base station, a user equipment, and/or a core network server according to one or more aspects of selecting a user equipment-specific TDD slot format. In an implementation, signaling and control transactions may be performed by any combination of base station 120 (fig. 1), UE 110 (fig. 1), and/or core network server 302 (fig. 3) using the elements of fig. 1-7.

The signaling and control transaction control diagram 800 of fig. 8 illustrates a first example of signaling and control transactions for selecting a UE-specific TDD slot format. As shown, at 805, the base station 120 establishes a wireless connection with the UE 110 based on the first TDD slot format, such as the communication established and described with the example 400 of fig. 4.

The first TDD slot format assigns communication resources in any suitable manner, such as by assigning uplink communications, downlink communications, and/or gap transmissions at the symbol level, such as those described with reference to example 500 of fig. 5. Alternatively or additionally, the first TDD slot format assigns communication resources at the slot level, such as those described with reference to example 600 of fig. 6. In some implementations, the base station determines the first TDD slot format, such as by using a default configuration for the first TDD slot format. Alternatively or additionally, the base station analyzes metrics such as UE-generated metrics and/or base station-generated metrics and selects a first TDD slot format based on the metrics, as further described. In turn, the base station 120 transmits downlink communications using the communication resources assigned to the downlink communications (using the TDD slot format), monitors the communication resources assigned to the uplink communications, and/or refrains from transmitting information in the communication resources assigned to the gap transmission.

Similarly, at 810, UE 110 establishes a wireless connection with base station 120 based on the first TDD slot format. In some implementations, the base station 120 communicates the first TDD slot format to the UE 110 (not shown), and the UE 110 exchanges communications with the base station over a wireless connection using the first TDD slot configuration. For example, UE 110 may transmit uplink communications using communication resources assigned to uplink communications (using TDD slot format), monitor communication resources assigned to downlink communications, and/or refrain from transmitting information in communication resources assigned to gap transmissions.

Based on the wireless connection, at 815, base station 120 generates a base station side (BS side metric), such as by generating metrics regarding uplink communications from UE 110. Any suitable type of metric may be generated, such as power information, uplink power headroom, uplink SINR, timing measurements, error metrics, internet Protocol (IP) layer throughput, end-to-end delay, end-to-end packet loss rate, and the like. Alternatively or additionally, the base station generates a network interference metric.

Similarly, at 820, UE 110 generates user equipment side (UE side) metrics based on the wireless connection such as, by way of example and not limitation, power headroom, signal power information, signal-to-interference plus noise ratio (SINR) information, channel Quality Indicator (CQI) information, channel State Information (CSI), doppler feedback, frequency band, block error rate (BLER), quality of service (QoS), hybrid automatic repeat request (HARQ) information (e.g., first transmission error rate, second transmission error rate, maximum retransmission), delay, radio Link Control (RLC), automatic repeat request (ARQ) metrics, received Signal Strength (RSSI). In response to generating the metrics, UE 110 communicates UE-side metrics to base station 120 at 825.

At 830, the base station 120 determines a second TDD slot format based at least in part on any combination of BS-side metrics and/or UE-side metrics. For example, BS TDD configuration manager 268 of fig. 2 analyzes the metrics to determine a second TDD slot format. When the metric indicates that the UE power energy level is below the threshold, some implementations of BS TDD configuration manager 268 determine to allocate more uplink communication assignments in the second TDD slot format (relative to uplink communication assignments in the first TDD slot format) to increase the power energy level received from UE 110. For example, BS TDD configuration manager 268 configures the second TDD slot format to assign consecutive slots and/or symbols to uplink communications. As another example, when a metric, such as a signal strength metric indicating that the UE is near the edge of the cell, indicates the location of the UE, BS TDD configuration manager 268 configures the second TDD slot format to assign consecutive slots and/or symbols to uplink communications to increase the range of the corresponding UE. As yet another example, base station 120 receives a battery level report from UE 110 and determines to add a gap transmission to the TDD slot format to reduce the number of slots and/or symbols monitored by UE 110 to conserve battery power. In some implementations, the base station 120 may alternatively or additionally instruct the UE 110 to perform Discontinuous Reception (DRX) during gap transmissions to conserve battery power.

At 835, the base station 120 reconfigures the wireless connection based on the second TDD slot format. For example, the base station 120 transmits the second TDD slot format to the UE 110 and instructs the UE 110 to transmit/receive information over the wireless connection based on the second TDD slot format. As another example, the base station 120 transmits/receives information over a wireless connection based on the second TDD slot format. In some implementations, the process is iteratively repeated at 840, wherein the base station 120 receives and/or analyzes the metrics to determine when to select a TDD slot format. This allows the base station to dynamically select a TDD slot format based on the current operating state and/or changes in operating state of the wireless communication system to improve signal quality, reduce bit errors, reduce network interference levels, improve data transfer, and the like. In other words, the base station 120 identifies the current operating state and/or changes in the operating state by analyzing BS-side metrics and/or UE-side metrics and selects a modified TDD slot format that addresses the problem identified by the metrics. By way of example and not limitation, the operating state of the wireless communication system may include any combination of channel conditions, UE configuration, UE capabilities, UE location, network interference levels, transmission medium properties, and the like. Accordingly, various implementations select a UE-specific TDD slot format by determining an operational state of a wireless communication system in which the UE operates and modifying the TDD slot format based on the operational state.

The signaling and control transaction control diagram 900 of fig. 9 illustrates a second example of signaling and control transactions for selecting a UE-specific TDD slot format. As shown, at 905, the core network server 302 determines a first TDD slot format. This may include the core network server determining a first TDD slot format based on the metric, determining the first TDD slot format in response to a request for the TDD slot format, and so on, using a default TDD slot format, such as a format defined by the wireless network system, when the wireless connection between the base station and the user device is first established. To illustrate, and as further described, core network server 302 sometimes receives communication metrics (e.g., power headroom, RSSI, uplink SINR) from base stations and/or UEs and analyzes the metrics to determine a TDD slot format that improves system performance (e.g., improves signal quality, reduces bit errors, reduces network interference levels, improves data delivery). At times, the core network server determines a TDD slot format that assigns communication resources at the symbol level (e.g., example 500), and at other times, the core network server determines a TDD slot format that assigns communication resources at the slot level (e.g., example 600).

In response to determining the first TDD slot format, at 910, the core network server communicates the first TDD slot format to the base station 120. Then, at 915, the base station 120 forwards the first TDD slot format to the user equipment.

At 920, base station 120 establishes a wireless connection with UE 110 based on the first TDD slot format. For example, the base station transmits downlink communications using communication resources assigned to the downlink communications (using TDD slot format), monitors communication resources assigned to uplink communications, and/or refrains from transmitting information in communication resources assigned to gap transmissions.

At 925, UE 110 establishes a wireless connection with base station 120 based on the first TDD slot format. For example, UE 110 may transmit uplink communications using communication resources assigned to uplink communications (using TDD slot format), monitor communication resources assigned to downlink communications, and/or refrain from transmitting information in communication resources assigned to gap transmissions.

In response to establishing the wireless connection, base station 120 generates BS-side metrics at 930 and UE 110 generates UE-side metrics at 940. In an implementation, base station 120 analyzes communications exchanged with UE 110 and generates metrics based on the communications, such as power information, uplink power headroom, uplink SINR, timing measurements, error metrics, internet Protocol (IP) layer throughput, end-to-end delay, end-to-end packet loss rate, and the like. Similarly, the UE analyzes the communications exchanged with the base station 120 and generates UE-side metrics based on the communications, such as power headroom, signal power information, SINR, CQI, CSI, doppler feedback, frequency band, BLER, qoS, RSSI, and the like. At 940, UE 110 communicates the UE-side metrics to base station 120. At 945, the base station 120 communicates any combination of metrics, such as any combination of BS-side metrics and/or UE-side metrics, to the core network server 302.

In response to receiving the metrics, the core network server determines a second TDD slot format at 950. This may include increasing a number of uplink communication assignments in the second TDD slot format relative to the first TDD slot format to increase a power energy level of the UE 110 at the base station 120, decreasing a number of downlink communication assignments to decrease a number of communication resources monitored by the UE 110, assigning gap transmissions in the second TDD slot format in response to a metric indicating that a network interference level exceeds a threshold, and so forth.

The core network server 302 then reconfigures the wireless connection using the second TDD slot format at 955. For example, the core network server 302 communicates a second TDD slot format and instructs the base station 120 to manage communications based on the second TDD slot format. Alternatively or additionally, core network server 302 instructs base station 120 to communicate the second TDD slot format to UE 110.

Optionally, at 960, the process iterates iteratively, wherein the core network server 302 receives and/or analyzes metrics to determine when to select a TDD slot format. This allows the core network server to dynamically select a TDD slot format based on changing operating states of the wireless communication system to improve signal quality and/or reduce bit errors. In other words, core network server 302 identifies the current operating state and/or changes in the operating state by analyzing BS-side metrics and/or UE-side metrics and selects a modified TDD slot format that addresses the problem identified by the metrics (e.g., selecting a TDD slot format that improves signal quality in the wireless network, reduces bit errors, reduces network interference levels, improves data delivery).

The signaling and control transaction control diagram 1000 of fig. 10 illustrates a third example of signaling and control transactions for selecting a user equipment specific TDD slot format. As shown, at 1005, the base station 120 establishes a wireless connection with the UE 110 based on the first TDD slot format, such as the communication established and described with the example 400 of fig. 4. The first TDD slot format assigns communication resources in any suitable manner, such as by assigning uplink communications, downlink communications, and/or gap transmissions at a symbol level (e.g., example 500) or slot level (e.g., example 600). In some implementations, the base station determines the first TDD slot format, such as by using a default configuration for the first TDD slot format. Alternatively or additionally, the base station analyzes metrics such as UE-generated metrics and/or BS-generated metrics and selects a first TDD slot format based on these metrics, as further described. In turn, the base station 120 transmits downlink communications using the communication resources assigned to the downlink communications (using the TDD slot format), monitors the communication resources assigned to the uplink communications, and/or refrains from transmitting information in the communication resources assigned to the gap transmission.

Similarly, at 1010, ue 110 establishes a wireless connection with base station 120 based on the first TDD slot format. In some implementations, the base station 120 communicates the first TDD slot format to the UE 110 (not shown), and the UE 110 exchanges communications with the base station over a wireless connection using the first TDD slot configuration. For example, UE 110 may transmit uplink communications using communication resources assigned to uplink communications (using TDD slot format), monitor communication resources assigned to downlink communications, and/or refrain from transmitting information in communication resources assigned to gap transmissions.

At 1015, UE 110 generates UE-side metrics based on the wireless connection. To illustrate, UE 110 generates any combination of power headroom, signal power information, SINR, CQI, CSI, BLER, RSSI, signal strength estimate, and the like.

At 1020, UE 110 determines a second TDD slot format. To illustrate, UE TDD configuration manager 216 of UE 110 analyzes the metrics generated at 1015 and identifies a TDD slot format that addresses the problem identified by the metrics (e.g., selects a TDD slot format that improves signal quality in the wireless network, reduces bit errors, reduces network interference levels, improves data delivery). For example, the UE TDD configuration manager analyzes the power headroom report and determines to increase the number of uplink slots and/or symbols in the TDD slot format to increase the UE power energy level.

In response to determining the second TDD slot format, UE 110 transmits a request for the second TDD slot format at 1025. For illustration, consider an example in which UE 110 and base station 120 each access a lookup table identifying a plurality of TDD slot formats, where the lookup table assigns a different identifier to each TDD slot format. In response to determining the second TDD slot format, some implementations of the UE TDD slot configuration manager identify an entry in a lookup table corresponding to the second TDD slot format and transmit a corresponding (lookup table) identifier in the request to indicate the second TDD slot format.

At 1030, in response to receiving the request, the base station 120 reconfigures the wireless connection based on the second TDD slot format. For example, BS TDD time slot configuration manager 268 communicates the second TDD time slot format to base station manager 266. In turn, the base station manager 266 configures the base station 120 to transmit, receive, and/or refrain from transmitting based on the second TD slot format. In some implementations, the base station 120 transmits an acknowledgement message to the UE 110 that the base station received and approved the second TDD slot format.

In some implementations, at 1035, the process is iteratively repeated, wherein UE 110 generates and analyzes metrics based on the wireless connection with base station 120. UE 110 determines when to select a TDD slot format and transmits a request for modification to the base station. This allows UE 110 to dynamically select a TDD slot format based on a current operating state and/or a change in operating state to improve signal quality, reduce bit errors, reduce network interference levels, improve data transfer, etc. In other words, UE 110 identifies problems in the changed operating environment by analyzing the UE-side metrics. In turn, UE 110 requests a modified TDD slot format from base station 120 that addresses the identified problem. In an implementation, UE 110 indicates the modified TDD slot format to the base station.

Although not illustrated in fig. 10, an alternative implementation of the signaling and control transaction control diagram 1000 includes signaling and control transactions with the core network server 302. For example, an alternative implementation of diagram 1000 includes core network server 302 determining and communicating a first TDD slot format of diagram 1000 to base station 120, such as those described at 905 and 910 of fig. 9. Alternatively or additionally, alternative implementations of diagram 1000 include core network server 302 receiving a request for a second TDD slot format and reconfiguring a wireless connection, such as those described at 955 of fig. 9.

The signaling and control transaction control diagram 1100 of fig. 11 illustrates a fourth example of signaling and control transactions for selecting a UE-specific TDD slot format. As shown, at 1105, the base station 120 establishes a wireless connection with the UE 110 based on the first TDD slot format, such as the communication established and described with the example 400 of fig. 4. The first TDD slot format assigns communication resources in any suitable manner, such as by assigning uplink communications, downlink communications, and/or gap transmissions at a symbol level (e.g., example 500) or slot level (e.g., example 600). In some implementations, the base station determines the first TDD slot format, such as by using a default configuration for the first TDD slot format. Alternatively or additionally, the base station analyzes metrics such as UE-generated metrics and/or BS-generated metrics and selects the first TDD slot format based on the metrics, as further described. In turn, the base station 120 transmits downlink communications using the communication resources assigned to the downlink communications (using the TDD slot format), monitors the communication resources assigned to the uplink communications, and/or refrains from transmitting information in the communication resources assigned to the gap transmission.

Similarly, at 1110, UE 110 establishes a wireless connection with base station 120 based on the first TDD slot format. In some implementations, the base station 120 communicates the first TDD slot format to the UE 110 (not shown), and the UE 110 exchanges communications with the base station over a wireless connection using the first TDD slot configuration. For example, UE 110 may transmit uplink communications using communication resources assigned to uplink communications (using TDD slot format), monitor communication resources assigned to downlink communications, and/or refrain from transmitting information in communication resources assigned to gap transmissions.

Based on the wireless connection, base station 120 generates a base station side (BS side metric) at 1115, such as by generating metrics regarding uplink communications from UE 110. Any suitable type of metric may be generated, such as power information, uplink power headroom, uplink SINR, timing measurements, error metrics, internet Protocol (IP) layer throughput, end-to-end delay, end-to-end packet loss rate, and the like. Alternatively or additionally, the base station generates a network interference metric.

Similarly, at 1120, UE 110 generates user equipment side (UE side) metrics based on the wireless connection, such as, by way of example and not limitation, power headroom, signal power information, SINR, CQI, CSI, doppler feedback, BLER, RSSI, and the like. In response to generating the UE-side metrics, UE 110 communicates the UE-side metrics to base station 120 at 1125.

At 1130, the base station 120 determines the network interference level by analyzing the UE-side metrics and/or BS-side metrics. In some implementations, the base station determines that the network interference level meets and/or exceeds a threshold. In response to determining that the network interference level meets or exceeds the threshold, the base station 120 determines, via the BS TDD configuration manager 268, a second TDD slot format that indicates a reduced network interference level, such as by adding a gap transmission to the second TDD slot format, reducing the number of downlink communication assignments in the second TDD slot format, and so forth.

At 1140, in response to determining the second TDD slot format, the base station 120 reconfigures the wireless connection based on the second TDD slot format. For example, BS TDD time slot configuration manager 268 communicates the second TDD time slot format to base station manager 266. In turn, the base station manager 266 instructs the base station 120 to transmit, receive, and/or refrain from transmitting based on the second TD slot format.

In some implementations, the process is iteratively repeated at 1145, wherein the base station analyzes the BS-side metric and/or the UE-side metric to determine when the network interference level meets or exceeds a threshold to determine when to select a TDD slot format. This allows the base station 120 to dynamically select a TDD slot format based on the current operating state and/or changes in operating state of the wireless communication system to improve signal quality, reduce bit errors, reduce network interference levels, improve data transfer, and the like. In other words, the base station 120 identifies problems (e.g., network interference level changes) in the changed operating environment by analyzing BS-side and/or UE-side metrics through the BS TDD configuration manager 268. The BS TDD configuration manager then generates a modified TDD slot format that solves the identified problem.

Although not illustrated in fig. 11, an alternative implementation of the signaling and control transaction control diagram 1100 includes signaling and control transactions with the core network server 302. For example, an alternative implementation of the diagram 1100 includes the core network server 302 determining and communicating a first TDD slot format of the diagram 1100 to the base station 120, such as those described at 905 and 910 of fig. 9. Alternatively or additionally, implementations of diagram 1000 include core network server 302 receiving BS-side and/or UE-side metrics and determining a second TDD slot format based on a network interference level, such as those described at 950 of fig. 9. In an implementation, the core network server corrects the network interference level by instructing the base station 120 and/or the UE 110 to reconfigure the wireless connection using the second TDD slot format, such as those described at 955 of fig. 9.

The signaling and control transaction control diagram 1200 of fig. 12 illustrates a fifth example of signaling and control transactions for selecting a user equipment specific TDD slot format. As shown, ue 110 initiates operations associated with QoS flows at 1205. For example, a user interacts with UE 110 through an input mechanism to invoke operations, such as invoking applications, music streaming services, social media services, video streaming services, voice over internet protocol (VoIP) services, online gaming applications, and so forth. In implementations, the invoked operations exchange, use, and/or request information (e.g., data) with a higher priority than other operations.

For illustration, consider an example in which a user invokes a VoIP service. To ensure seamless and real-time voice transmission (e.g., uninterrupted, continuous output, negligible output delay), qoS flows associated with VoIP applications have higher priority in wireless networks for data transmission, signaling exchanges, commands, etc. relative to other QoS flows. Thus, to ensure that the VoIP application receives the requested priority for communication resources in the wireless network, the UE requests a QoS flow at 1210, wherein in some cases the request includes an indication of one or more (requested) characteristics for the QoS flow

In response to receiving the request, the base station 120 determines a TDD slot format based on the requested QoS flow and/or characteristics included in the request at 1215. For example, based on the requested characteristics, the base station 120 estimates uplink communication resource requirements and/or downlink communication resource requirements based on these requirements and determines a TTD slot format that addresses these requirements. As one example, the base station 120 selects a TDD slot format that assigns more communication resources to uplink communications.

At 1220, the base station 120 establishes a wireless connection based on the TDD slot format, where in some cases the wireless connection corresponds to a QoS flow. For example, the base station 120 establishes the wireless connection based on a TDD slot format (e.g., example 500, example 600) that assigns communication resources, as further described.

Similarly, at 1225, UE 110 establishes a wireless connection with base station 120 based on the TDD slot format. In an implementation, UE 110 uses and/or dedicates communication resources to make wireless connections for QoS flows.

Having described signaling and control transactions that may be used to select a UE-specific TDD slot format, consider now some example methods in accordance with one or more implementations.

Example method

Example methods 1300, 1400, 1500, 1600, and 1700 are described with reference to fig. 13, 14, 15, 16, and 17 in terms of selecting one or more aspects of a UE-specific TDD slot format. The order in which the method blocks are described is not intended to be construed as a limitation, and any number of the described method blocks can be skipped or combined in any order to implement a method or alternative method. In general, any of the components, modules, methods, and operations described herein may be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or any combination thereof. Some operations of the example methods may be described in the general context of executable instructions stored on computer-readable storage memory local and/or remote to a computer processing system, and implementations may include software applications, programs, functions, and the like. Alternatively, or in addition, any of the functions described herein may be performed, at least in part, by one or more hardware logic components, such as, but not limited to, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems on a chip (socs), complex Programmable Logic Devices (CPLDs), and the like.

Fig. 13 illustrates an example method 1300 for selecting a UE-specific TDD slot format. In some implementations, the operations of method 1300 are performed by a network entity, such as base station 120, while in alternative or additional implementations, the operations of method 1300 are performed by core network server 302. In one or more examples, the operations correspond to at least some of the signaling and control transactions as described with respect to diagram 800 and/or diagram 900.

At 1305, the network entity establishes a wireless connection with the user equipment based on the first time division duplex slot format. For example, a base station (e.g., base station 120) establishes a wireless connection with a user equipment (e.g., UE 110) by exchanging communications with the UE based on a first Time Division Duplex (TDD) slot format, such as those described at 805 of fig. 8. As another example, a core network server (e.g., core network server 302) instructs a base station (e.g., base station 120) to establish a connection with a UE (e.g., UE 110). In an implementation, the core network server communicates a first TDD slot format to a base station, such as those described at 910 of fig. 9. Sometimes, the first TDD slot format assigns communication resources of the wireless connection using any arrangement of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments. For example, as described in example 500, the first TDD slot format indicates an assignment (e.g., uplink communication, downlink communication, gap transmission) for each symbol of a slot. As another example, as described in example 600, the first TDD slot format indicates an assignment (e.g., uplink communication, downlink communication, gap transmission) for each slot of a subframe. In some implementations, the first TDD slot format indicates the same assignment (e.g., all uplink communication assignments, all downlink communication assignments, all gap transmission assignments) for each symbol or slot. In other implementations, the first TDD slot format indicates a different assignment for each symbol or slot.

At 1310, the network entity identifies one or more metrics associated with the wireless connection. As one example, a network entity (e.g., base station 120) receives UE-side metrics generated by a UE (e.g., UE 110), such as those described at 820 of fig. 8 (e.g., signal strength estimates, power headroom reports, power status reports). Alternatively or additionally, the base station (e.g., base station 120) uses the communications exchanged over the wireless connection to generate BS-side metrics, such as those described at 815 of fig. 8. As another example, the base station forwards UE-side metrics and/or BS-side metrics to a core network server (e.g., core network server 302), such as those described at 945 of fig. 9.

In response to identifying the one or more metrics, the network entity determines a second Time Division Duplex (TDD) slot format based on the one or more metrics at 1315. To illustrate, a base station (e.g., base station 120) determines a second TDD slot format based on a metric (e.g., power status report) from a UE (e.g., UE 110). For example, the base station analyzes the power status report and determines that the battery level of the UE has fallen below a threshold. To preserve the battery life of the UE, the base station determines to add one or more gap transmissions to the second TDD slot format relative to the first TDD slot format as a way to reduce the number of transmissions monitored by the UE and preserve battery life/power. In some implementations, the base station 120 may alternatively or additionally instruct the UE 110 to perform Discontinuous Reception (DRX) during gap transmissions to conserve battery power. As another example, the base station receives a power headroom metric from the UE and determines to assign two or more consecutive resources (e.g., slots, symbols) to the uplink communication. In other words, the base station includes two or more uplink communication assignments in the second TDD slot format to increase the received power energy level (from the UE) at the base station.

In some implementations, the base station receives the quality of service flow identifiers and determines the communication resource conditions (e.g., diagram 1200) based on the corresponding quality of service flows. The base station then determines a second TDD slot format based on meeting the communication resource condition.

At 1320, the network entity reconfigures the wireless connection based on a second Time Division Duplex (TDD) slot format, such as those described at 835 of fig. 8 and/or 955 of fig. 9. For example, the base station (e.g., base station 120) communicates the second TDD slot format to the UE (e.g., UE 110) and instructs the UE to exchange communications over the wireless connection based on the second TDD slot format. Alternatively or additionally, a core network server (e.g., core network server 302) communicates the second TDD slot format to a base station (e.g., base station 120) and instructs the base station to communicate the second TDD slot format to a UE (e.g., UE 110). In an implementation, as indicated at 1325, the method 1300 repeats such that the network entity determines a modification to the TDD slot format based on the current operating state of the wireless communication system (as indicated by the received metrics) and/or a change in operating state to improve the overall performance of the wireless communication system, as further described.

Fig. 14 illustrates an example method 1400 for selecting a UE-specific TDD slot format. In some implementations, the operations of method 1400 are performed by a network entity, such as base station 120, while in alternative or additional implementations, the operations of method 1400 are performed by core network server 302. In one or more examples, the operations correspond to at least some of the signaling and control transactions as described with respect to diagram 1000.

At 1405, the network entity establishes a wireless connection with a user equipment based on a first Time Division Duplex (TDD) slot format. For example, a base station (e.g., base station 120) establishes a wireless connection with a UE (e.g., UE 110) by exchanging communications with the UE based on a first TDD slot format, such as those described at 1005 of fig. 10. As another example, a core network server (e.g., core network server 302) instructs a base station (e.g., base station 120) to establish a connection with a UE (e.g., UE 110). In an implementation, the core network server communicates a first TDD slot format to a base station, such as those described at 910 of fig. 9. Sometimes, the first TDD slot format assigns communication resources of the wireless connection using any arrangement of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments. For example, as described in example 500, the first TDD slot format indicates an assignment (e.g., uplink communication, downlink communication, gap transmission) for each symbol of a slot. As another example, as described in example 600, the first TDD slot format indicates an assignment (e.g., uplink communication, downlink communication, gap transmission) for each slot of a subframe. In some implementations, the first TDD slot format indicates the same assignment (e.g., all uplink communication assignments, all downlink communication assignments, all gap transmission assignments) for each symbol or slot. In other implementations, the first TDD slot format indicates a different assignment for each symbol or slot.

At 1410, a network entity receives a request indicating a second Time Division Duplex (TDD) slot format. As one example, a base station (e.g., base station 120) receives an indication from a UE (e.g., UE 110) that includes a second TDD slot format, such as those depicted at 1025 of diagram 1000. This allows UE 110 to dynamically select a TDD slot format based on a current operating state and/or a change in operating state of the wireless communication system to improve signal quality, reduce bit errors, reduce network interference levels, improve data transfer, etc., and request the selected TDD slot format implemented for the wireless connection.

Thus, at 1415, the network entity reconfigures the wireless connection based on a second Time Division Duplex (TDD) slot format, such as those described at 1030 of fig. 10 and/or 955 of fig. 9. For example, the base station (e.g., base station 120) communicates the second TDD slot format to the UE (e.g., UE 110) and instructs the UE to exchange communications over the wireless connection based on the second TDD slot format. Alternatively or additionally, a core network server (e.g., core network server 302) communicates the second TDD slot format to a base station (e.g., base station 120) and instructs the base station to communicate the second TDD slot format to a UE (e.g., UE 110). In an implementation, as indicated at 1420, the method 1400 is iteratively repeated such that the network entity receives modifications to the TDD slot format based on the current operating state and/or changes in the operating state, as further described.

Fig. 15 illustrates an example method 1500 for selecting a UE-specific TDD slot format. In some implementations, the operations of method 1500 are performed by a network entity, such as base station 120, while in alternative or additional implementations, the operations of method 1500 are performed by core network server 302. In one or more examples, the operations correspond to at least some of the signaling and control transactions as described with respect to diagram 1100 in which the TDD slot format is selected based on the network interference level.

At 1505, the network entity establishes a wireless connection with the user equipment based on a first Time Division Duplex (TDD) slot format. For example, a base station (e.g., base station 120) establishes a wireless connection with a UE (e.g., UE 110) by exchanging communications with the UE based on a first TDD slot format, such as those described at 1105 and/or 1110 of fig. 11. As another example, a core network server (e.g., core network server 302) instructs a base station (e.g., base station 120) to establish a connection with a UE (e.g., UE 110). In an implementation, the core network server communicates a first TDD slot format to a base station, such as those described at 910 of fig. 9. Sometimes, the first TDD slot format assigns communication resources of the wireless connection using any arrangement of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments. For example, as described in example 500, the first TDD slot format indicates an assignment (e.g., uplink communication, downlink communication, gap transmission) for each symbol of a slot. As another example, as described in example 600, the first TDD slot format indicates an assignment (e.g., uplink communication, downlink communication, gap transmission) for each slot of a subframe. In some implementations, the first TDD slot format indicates the same assignment (e.g., all uplink communication assignments, all downlink communication assignments, all gap transmission assignments) for each symbol or slot. In other implementations, the first TDD slot format indicates a different assignment for each symbol or slot.

At 1510, the network entity determines that the network interference level exceeds a threshold. As one example, a base station (e.g., base station 120) receives UE-side metrics from a UE (e.g., UE 110), such as those described at 1125 of fig. 11. Alternatively or additionally, a base station (e.g., base station 120) generates BS-side metrics, such as those described at 1115 of fig. 11. The base station analyzes any combination of UE-side metrics and/or BS-side metrics and determines that the network interference level exceeds a threshold. For example, the base station 120 analyzes RSRP, RSRQ, SINR, RSSI, etc., any combination to determine a network interference level.

Thus, in response to determining that the network interference level exceeds the threshold, the network entity determines a second Time Division Duplex (TDD) slot format at 1515. For example, a base station (e.g., base station 120) determines a slot format that indicates a reduced network interference level by adding a gap transmission assignment to a second TDD slot format, reducing a number of downlink communication assignments in the second TDD slot format, and so forth.

At 1520, the network entity reconfigures the wireless connection between the base station and the User Equipment (UE) based on a second Time Division Duplex (TDD) slot format, such as those described at 1140 of fig. 11 and/or 955 of fig. 9. For example, the base station (e.g., base station 120) communicates the second TDD slot format to the UE (e.g., UE 110) and instructs the UE to exchange communications over the wireless connection based on the second TDD slot format. Alternatively or additionally, a core network server (e.g., core network server 302) communicates the second TDD slot format to a base station (e.g., base station 120) and instructs the base station to communicate the second TDD slot format to a UE (e.g., UE 110). In an implementation, as indicated at 1525, the method 1500 is iteratively repeated such that the network entity monitors the network interference level and configures the TDD slot format to change the network interference level (e.g., reduce the interference level), as further described.

Fig. 16 illustrates an example method 1600 for selecting a UE-specific TDD slot format. In some implementations, the operations of method 1600 are performed by a UE, such as UE 110. In one or more examples, the operations correspond to at least some of the signaling and control transactions as described with respect to diagram 800 of fig. 8 and/or diagram 900 of fig. 9 in which the TDD slot format is selected based on the metric.

At 1605, the UE establishes a wireless connection with a base station based on a first Time Division Duplex (TDD) slot format. For example, the UE (e.g., UE 110) receives a first TDD slot format from a base station (e.g., base station 120), such as by the base station indicating an entry in a lookup table that includes a slot format pattern. In response to receiving the first TDD slot format, the UE establishes a wireless connection by exchanging communications based on the first TDD slot format, such as those described at 810 of fig. 1 and 925 of fig. 9.

At 1610, the UE generates one or more metrics. In one or more implementations, a UE (e.g., UE 110) generates metrics based on a communication exchange over a wireless connection, such as those described at 820 of fig. 8. Alternatively or additionally, the UE generates metrics, such as power status reports, describing the operating state of the UE while maintaining the wireless connection. The UE then transmits the metrics to the base station at 1615. For example, the UE (e.g., UE 110) transmits the metrics to the base station (e.g., base station 120) as described at 825 of fig. 8 and 940 of fig. 9.

At 1620, the UE receives a second Time Division Duplex (TDD) slot format. In an implementation, the UE (e.g., UE 110) receives a TDD slot format based on the metric transmitted at 1615, such as a TDD slot format that addresses the issues indicated by the metric (e.g., improving signal quality in the wireless network, reducing bit errors, reducing network interference levels, improving TDD slot formats for data transmission). Alternatively or additionally, the UE receives an indication to perform Discontinuous Reception (DRX) during the gap transmission as assigned in the second TTD slot format.

At 1625, the User Equipment (UE) reconfigures the wireless connection based on a second Time Division Duplex (TDD) slot format, such as those described at 835 of fig. 8 and/or 955 of fig. 9. For example, the UE (e.g., UE 110) exchanges communications over the wireless connection based on the second TDD slot format. In an implementation, the method 1600 iterates iteratively, as indicated at 1530, such that the UE generates and communicates metrics to the base station, and reconfigures the wireless connection using a TDD slot format based on the metrics, as further described.

Fig. 17 illustrates an example method 1700 for selecting a UE-specific TDD slot format. In some implementations, the operations of method 1700 are performed by a UE, such as UE 110. In one or more examples, these operations correspond to at least some of the signaling and control transactions as described with reference to diagram 1200 of fig. 12 in which the TDD slot format is selected based on the QoS flows.

At 1705, the UE initiates an operation associated with a quality of service flow. For example, a UE (e.g., UE 110) receives input invoking an application and/or service, where the application and/or service is associated (e.g., at 1205 of diagram 1200) with a QoS flow. To illustrate, a user initiates an audio streaming service, a social media service, a video streaming service, a voice over internet protocol (VoIP) service, an online gaming application, etc., that has communication resource conditions, such as traffic patterns, activity patterns, duty cycles, interrupt priorities, data priorities, etc., identified by the associated QoS flows.

The UE then transmits an indication of the quality of service flow to the base station at 1710. For example, the UE (e.g., UE 110) determines a QFI associated with the QoS flow by comparing the communication resource condition associated with the operation to the QoS profile and obtains the QFI from the QoS profile that matches the communication resource condition. The UE then transmits the QFI to the base station. Alternatively or additionally, the UE determines an identification of the initiated operation and transmits an indication of the identification of the initiated operation to the base station.

In response to transmitting the indication, the UE receives a Time Division Duplex (TDD) slot format based on the indication at 1715. A UE (e.g., UE 110) receives, for example, a modification to a TDD slot format for an existing wireless connection between the UE and a base station. Alternatively or additionally, the UE receives a TDD slot format for establishing a wireless connection between the UE and the base station for operation.

Thus, at 1720, the UE establishes a wireless connection with the base station based on a Time Division Duplex (TDD) slot format. For example, the UE (e.g., UE 110) establishes the wireless connection by exchanging communications based on the TDD slot format received at 1715, such as by assigning the exchanged communications based on communication resources as described in example 500 and/or example 600. The UE then exchanges communications associated with the operation using the wireless connection at 1725.

Several examples are described below:

an example method for selecting or configuring a slot format based on an operational state of a wireless communication system includes: establishing, by the base station, a wireless connection with the user equipment based at least in part on a first time division duplex slot format, the first time division duplex slot format assigning communication resources of the wireless connection using a first arrangement of one or more of: uplink communication assignment, downlink communication assignment or gap transmission assignment; identifying, by the base station, one or more metrics associated with the wireless connection; and reconfiguring the wireless connection between the base station and the user equipment by instructing the user equipment to exchange communications over the wireless connection based on a second time division duplex slot format, the second time division duplex slot format assigning communication resources of the wireless connection using a second arrangement of one or more of: the second arrangement is different from the first arrangement in terms of uplink communication assignment, downlink communication assignment, or gap transmission assignment.

Reconfiguring the wireless connection based on the second time division duplex slot format may be responsive to a trigger event. The trigger event may indicate a change in the state of the wireless connection, the transmission environment, the operating environment, and/or the user device. For example, a method may include identifying, by a base station, one or more metrics associated with a wireless connection. The method may include determining a second time division duplex slot format based on one or more metrics. Alternatively or additionally, the method may include receiving a request from the user equipment indicating the second time division duplex slot format. Alternatively or additionally, the method may include determining that a network interference level associated with the wireless communication system exceeds a threshold, and determining a second time division duplex slot format in response to the network interference level exceeding the threshold.

Determining the second time division duplex slot format may include determining to assign two or more consecutive slots to the uplink communication.

Identifying the one or more metrics may include receiving from the user device at least one of: estimating signal strength; a power headroom report; or a power status report. Identifying the one or more metrics may further include receiving a power status report from the user equipment; and determining from the power status report that the battery level of the user equipment has fallen below a threshold. Determining the second time division duplex slot format may include determining to add one or more gap transmissions to the second time division duplex slot format relative to the first time division duplex slot format.

The user equipment may be instructed to perform discontinuous reception during one or more gap transmissions.

Identifying one or more metrics associated with the wireless connection may include: a quality of service flow identifier associated with a quality of service flow is received from a user equipment. One or more communication resource conditions for the quality of service flow may be determined based on the quality of service flow identifier. The determining of the second time division duplex slot format may be based at least in part on one or more communication resource conditions of the quality of service stream.

The second time division duplex slot format may assign two or more consecutive communication resources to uplink communications. The two or more consecutive communication resources may comprise time slots or symbols.

The second time division duplex slot format may include one or more additional gap transmission assignments relative to the first time division duplex slot format.

The determined network interference level may include a downlink network interference level. Determining the second time division duplex slot format may include including one or more additional uplink communication assignments in the second time division duplex slot format relative to the first time division duplex slot format.

Determining the second time division duplex slot format may include determining to include one or more of the gap transmission assignments in the second time division duplex slot format based on the determined network interference level.

The base station may be a first base station. Determining that the network interference level in the wireless communication system exceeds the threshold may include receiving a third time division duplex slot format from the second base station; analyzing a third time division duplex time slot format; and determining, based on the analysis, that the third time division duplex slot format generates a network interference level that exceeds a threshold.

The third time division duplex slot format may include information indicating the location of the target user equipment and the target user equipment.

Another example method for selecting or configuring a slot format operating state of a wireless communication system includes: establishing, by the user equipment, a wireless connection with the base station based at least in part on a first time division duplex slot format, the first time division duplex slot format assigning communication resources of the wireless connection using a first arrangement of one or more of: uplink communication assignment, downlink communication assignment or gap transmission assignment; receiving a second time division duplex slot format from the base station, the second time division duplex slot format assigning communication resources of the wireless connection using a second arrangement of one or more of: an uplink communication assignment, a downlink communication assignment, or a gap transmission assignment, the second arrangement being different from the first arrangement; and reconfiguring the wireless connection based on the second time division duplex slot format.

The method may include generating, using the user equipment, one or more metrics associated with the wireless connection; one or more metrics are transmitted to the base station. The second time division duplex slot format may be based at least in part on one or more metrics.

Generating one or more metrics associated with the wireless connection may include generating at least one of: a power headroom report; a battery level report; or signal strength estimation.

The second time division duplex slot format may include one or more additional uplink communication assignments relative to the first time division duplex slot format.

An indication may be received from the base station that directional discontinuous reception was performed during one or more gap transmissions. One or more gap transmissions may be identified based on the first time division duplex slot format or the second time division duplex slot format.

One or more metrics may be analyzed. The third time division duplex slot format may be determined using a third arrangement of one or more of: the uplink communication assignment, the downlink communication assignment, or the gap transmission assignment, the third arrangement being different from the first arrangement and the second arrangement, the third arrangement being based at least in part on the one or more metrics. A request to reconfigure the wireless connection using a third time division duplex slot format may be transmitted to the base station.

Another example method for selecting or configuring a slot format operating state of a wireless communication system includes: initiating an operation associated with a quality of service flow using a user equipment; transmitting an indication of a quality of service flow associated with the operation to the base station; receiving a time division duplex slot format from a base station, the time division duplex slot format assigning communication resources of a wireless connection using an arrangement of one or more of: an uplink communication assignment, a downlink communication assignment, or a gap transmission assignment, the arrangement based at least in part on the indication; establishing a wireless connection with a base station based on a time division duplex slot format; and exchanging communications associated with the operation using the wireless connection.

The operations associated with the quality of service flow may include: voice over internet protocol services; a social media application; an audio streaming service; or a video streaming service.

Although aspects of selecting a UE-specific TDD slot format have been described in language specific to features and/or methods, the subject of the appended claims is not necessarily limited to the specific features or methods described. Rather, these specific features and methods are disclosed as example implementations of selecting UE-specific TDD slot formats, and other equivalent features and methods are intended to fall within the scope of the appended claims. Furthermore, various aspects are described, and it is to be understood that each aspect described may be implemented independently or in combination with one or more other described aspects.

Claims

1. A method for configuring a slot format based on an operational state of a user equipment in a wireless communication system, the method comprising:

establishing, by a base station, a wireless connection with the user equipment based at least in part on a first time division duplex slot format that assigns communication resources of the wireless connection using a first arrangement of one or more of: uplink communication assignment, downlink communication assignment, and gap transmission assignment;

receiving, by the base station, a battery level report from the user equipment;

determining a second time division duplex slot format based on the battery level report, the second time division duplex slot format using a second arrangement of one or more of the following to assign the communication resources of the wireless connection: an uplink communication assignment, a downlink communication assignment, and a gap transmission assignment, the second arrangement being different from the first arrangement; and

the wireless connection is reconfigured between the base station and the user equipment by instructing the user equipment to exchange communications over the wireless connection based on the second time division duplex slot format.

2. The method of claim 1, further comprising:

One or more metrics are received from the user device including at least one of:

estimating signal strength;

a power headroom report; and

and (5) reporting the power state.

3. The method of claim 2, wherein receiving the one or more metrics further comprises:

receiving the power status report from the user equipment; and

determining from the power status report that the battery level of the user equipment has fallen below a threshold, and

wherein determining the second time division duplex slot format comprises:

determining to add one or more gap transmissions to the second time division duplex slot format relative to the first time division duplex slot format.

4. A method according to claim 2 or 3, wherein receiving the one or more metrics associated with the user equipment comprises:

receiving a quality of service flow identifier associated with a quality of service flow from the user equipment; and

determining one or more communication resource conditions of the quality of service flow based on the quality of service flow identifier, and

wherein determining the second time division duplex slot format is based at least in part on the one or more communication resource conditions of the quality of service stream.

5. A method for configuring a slot format based on an operational state of a wireless communication system, the method comprising:

establishing, by a user equipment, a wireless connection with a base station based at least in part on a first time division duplex slot format that assigns communication resources of the wireless connection using a first arrangement of one or more of: uplink communication assignment, downlink communication assignment, and gap transmission assignment;

generating a battery level report using the user device;

transmitting the battery level report to the base station;

receiving a second time division duplex time slot format from the base station, the second time division duplex time slot format assigning the communication resources of the wireless connection using a second arrangement of one or more of: an uplink communication assignment, a downlink communication assignment, and a gap transmission assignment, the second arrangement being different from the first arrangement and based at least in part on the battery level report; and

the wireless connection is reconfigured based on the second time division duplex slot format.

6. The method of claim 5, further comprising:

generating one or more metrics associated with an operational state of the user device, the one or more metrics including at least one of:

A power headroom report;

a battery level report; and

and estimating signal strength.

7. The method of claim 5, wherein the second time division duplex slot format comprises:

one or more additional uplink communication assignments relative to the first time division duplex slot format; or alternatively

One or more additional gap transmission assignments relative to the first time division duplex slot format.

8. The method of claim 6 or 7, further comprising:

analyzing the one or more metrics;

determining a third time division duplex slot format using a third arrangement of one or more of: an uplink communication assignment, a downlink communication assignment, and a gap transmission assignment, the third arrangement being different from the first arrangement and the second arrangement, the third arrangement being based at least in part on the one or more metrics; and

a request to reconfigure the wireless connection using the third time division duplex slot format is transmitted to the base station.