BACKGROUND

[0001] Wireless communication systems provide users with the flexibility to maintain connectivity to other devices and networks while being mobile. A user equipment (UE), for example, maintains connectivity with a wireless network while moving through an area by establishing a connection to a first base station, handing over to a second base station, and so forth. The dynamic nature of these connections, however, poses challenges to maintaining a level of quality and/or efficiency with the connection. To illustrate, a first connection between a UE close to a center of cell service provided by a base station has different transmission properties than a second connection between a UE at the edge of the cell service provided by the base station. These different transmission properties cause the communications transmitted using the first connection to distort in different ways than communications transmitted over the second connection. As another example, a first UE may execute a service or application that utilizes more communication resources of a network relative to a service or application executed at a second UE. Thus, the mobility and dynamic communication resource usage of UEs can make maintaining the level of quality and/or efficiency of a corresponding connection to a network difficult.

SUMMARY

[0002] This document describes techniques and apparatuses for configuring a time division duplex (TDD) slot format specific to a user equipment. 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 implementations, a TDD slot format assigns communication resources of a wireless connection using a first arrangement of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments. Afterwards, the network 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 the uplink communication assignments, downlink communication assignments, and/or gap transmission assignments, where 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 directing the user equipment to exchange communications over the wireless connection based on the second TDD slot format.

[0003] Some aspects of configuring a TDD slot format specific to a user equipment use a TDD slot format received from the user equipment. One or more implementations of a network entity establish a wireless connection between a base station and the 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. Afterward, the network entity receives, from the user equipment, a request that indicates a second TDD slot format that assigns the communication resources using a second arrangement of the uplink communication assignments, downlink communication assignments, and/or gap transmission assignments, where 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 directing the user equipment to exchange communications over the wireless connection using the second TDD slot format.

[0004] Some aspects of configuring a TDD slot format specific to a user equipment configures the TDD slot format based on an operating state of a wireless communication system. In implementations, 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 arrangement uplink communication assignments, downlink communication assignments, and/or gap transmission assignments. Afterward, the network entity determines that a network interference level associated with the wireless communication system exceeds a threshold value. In response to the network interference level exceeding the threshold value, the network entity determines a second TDD slot format that assigns the communication resources of the wireless connection based on a second arrangement of the uplink communication assignments, downlink communication assignments, and/or gap transmission assignments. In implementations, the network entity then reconfigures the wireless connection between the base station and the user equipment by directing the user equipment to exchange communications over the wireless connection using the second TDD slot format.

[0005] 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 metric(s) to the base station. Afterwards, the user equipment receives a second TDD slot format that assigns the communication resources of the wireless connection using a second arrangement of the uplink communication assignments, downlink communication assignments, and/or gap transmission assignments, where the second arrangement is different from the first arrangement. In implementations, the user equipment then reconfigures the wireless connection based on the second TDD slot format. [0006] In some implementations, a user equipment initiates an operation associated with a Quality-of-Service flow, and transmits, to a base station, an indication of the Quality-of Service flow associated with the operation. Afterward, the user equipment receives a TDD slot format that assigns communication resources of a wireless connection using an arrangement of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments, where the arrangement is based, at least in part, on the indication transmitted by the user equipment. In implementations, the user equipment then establishes the 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.

[0007] The details of one or more implementations of selecting a TDD slot format specific to a user equipment are set forth in the accompanying drawings and the following description. Other features and advantages will be apparent from the description and drawings, and from the claims. This summary is provided to introduce subject matter that is further described in the Detailed Description and Drawings. Accordingly, this summary should not be considered to describe essential features nor used to limit the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The details of one or more aspects of configuring a Time Division Duplex (TDD) slot format specific to a user equipment are described below. The use of the same reference numbers in different instances in the description and the figures indicate similar elements:

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

FIG. 2 illustrates an example device diagram of devices that can implement various aspects of selecting a TDD slot format specific to a user equipment. FIG. 3 illustrates an example device diagram of a device that can implement various aspects of selecting a TDD slot format specific to a user equipment.

FIG. 4 illustrates an example environment 400 in which devices communicate with one another using TDD slot format configurations.

FIG. 5 illustrates an example of a TDD slot format that assigns communication resources in accordance with one or more implementations.

FIG. 6 illustrates an example of a TDD slot format that assigns communication resources in accordance with one or more implementations.

FIG. 7 illustrates example TDD slot formats in accordance with one or more implementations.

FIG. 8 illustrates an example transaction diagram between various devices for selecting a TDD slot format specific to a user equipment.

FIG. 9 illustrates an example transaction diagram between various devices for selecting a TDD slot format specific to a user equipment.

FIG. 10 illustrates an example transaction diagram between various devices for selecting a TDD slot format specific to a user equipment.

FIG. 11 illustrates an example transaction diagram between various devices for selecting a TDD slot format specific to a user equipment.

FIG. 12 illustrates an example transaction diagram between various devices for selecting a TDD slot format specific to a user equipment.

FIG. 13 illustrates an example method for selecting a TDD slot format specific to a user equipment. FIG. 14 illustrates an example method for selecting a TDD slot format specific to a user equipment.

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

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

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

DETAILED DESCRIPTION

[0009] Wireless networks provide users with the flexibility to maintain connectivity to other devices and networks while being mobile. However, these wireless networks have finite communication resources, making the allocation of these resources challenging as more and more devices connect to the wireless network. As another challenge, the transmission environment of a mobile device in the wireless network continuously changes as the mobile device moves, thus impacting the usage efficiency of the communications resources. In some cases, a service or application running at a first mobile device utilizes more of the communication resources relative to a service or application running at a second mobile device. Thus, there is a need to dynamically allocate and reallocate the communication resources as the operating environment and/or state of a mobile device changes.

[0010] This document describes aspects of selecting a TDD slot format specific to a user equipment. In some aspects, a network entity establishes a wireless connection between a base station and the user equipment based, at least in part, on a first time-division-duplex (TDD) slot format. In implementations, a TDD slot format assigns communication resources of a wireless connection using a first arrangement of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments. Afterwards, the network 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 the uplink communication assignments, downlink communication assignments, and/or gap transmission assignments, where 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 directing the user equipment to exchange communications over the wireless connection based on the second TDD slot format.

[0011] Some aspects of configuring a TDD slot format specific to a user equipment 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 the 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. Afterward, the network entity receives, from the user equipment, a request that indicates a second TDD slot format that assigns the communication resources using a second arrangement of the uplink communication assignments, downlink communication assignments, and/or gap transmission assignments, where 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 directing the user equipment to exchange communications over the wireless connection using the second TDD slot format.

[0012] Some aspects of configuring a TDD slot format specific to a user equipment configure the TDD slot format based on an operating state of a wireless communication system. In implementations, 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 arrangement uplink communication assignments, downlink communication assignments, and/or gap transmission assignments. Afterward, the network entity determines that a network interference level associated with the wireless communication system exceeds a threshold value. In response to the network interference level exceeding the threshold value, the network entity determines a second TDD slot format that assigns the communication resources of the wireless connection based on a second arrangement of the uplink communication assignments, downlink communication assignments, and/or gap transmission assignments. In implementations, the network entity then reconfigures the wireless connection between the base station and the user equipment by directing the user equipment to exchange communications over the wireless connection using the second TDD slot format.

[0013] 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 metric(s) to the base station. Afterward, the user equipment receives a second TDD slot format that assigns the communication resources of the wireless connection using a second arrangement of the uplink communication assignments, downlink communication assignments, and/or gap transmission assignments, where the second arrangement is different from the first arrangement. In implementations, the user equipment then reconfigures the wireless connection based on second

TDD slot format. [0014] In some implementations, a user equipment initiates an operation associated with a Quality-of-Service flow, and transmits, to a base station, an indication of the Quality-of Service flow associated with the operation. Afterwards, the user equipment receives a TDD slot format that assigns communication resources of a wireless connection using an arrangement of uplink communication assignments, downlink communication assignments, and/or gap transmission assignments, where the arrangement is based, at least in part, on the indication transmitted by the user equipment. In implementations, the user equipment then establishes the 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.

Example Environment

[0015] FIG. 1 illustrates an example environment 100 which includes a user equipment 110 (UE 110) that can communicate with base stations 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 UE 110 is implemented as a smartphone 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 computer, desktop computer, tablet computer, smart appliance, vehicle-based communication system, or an Intemet-of-Things (IoT) device such as a sensor or an actuator. The base stations 120 (e.g, an Evolved Universal Terrestrial Radio Access Network Node B, E-UTRAN Node B, evolved Node B, eNodeB, eNB, Next Generation Node B, gNode B, gNB, ng-eNB, or the like) may be implemented in a macrocell, microcell, small cell, picocell, and the like, or any combination thereof. [0016] The base stations 120 communicate with the UE 110 using the wireless links 131 and 132, which may be implemented as any suitable type of wireless link. The wireless links 131 and 132 include control and data communication, such as downlink of data and control information communicated from the base stations 120 to the user equipment 110, uplink of other data and control information communicated from the UE 110 to the base stations 120, or both. The wireless links 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 3rd Generation Partnership Project Long-Term Evolution (3GPP LTE), Fifth Generation New Radio (5G NR), and so forth. Multiple wireless links 130 may be aggregated in a carrier aggregation to provide a higher data rate for the UE 110. Multiple wireless links 130 from multiple base stations 120 may be configured for Coordinated Multipoint (CoMP) communication with the UE 110.

[0017] The base stations 120 are collectively a Radio Access Network 140 (e.g., RAN, Evolved Universal Terrestrial Radio Access Network, E-UTRAN, 5GNRRAN or NR RAN). The base stations 121 and 122 in the RAN 140 are connected to a core network 150. The base stations 121 and 122 connect, at 102 and 104 respectively, to the core network 150 through an NG2 interface for control-plane signaling and using an NG3 interface for user-plane data communications when connecting to a 5G core network, or using an SI interface for control -plane signaling and user-plane data communications when connecting to an Evolved Packet Core (EPC) network. The base stations 121 and 122 can communicate using an Xn Application Protocol (XnAP) through an Xn interface or using an X2 Application Protocol (X2AP) through an X2 interface, at 106, to exchange user-plane and control-plane data. The user equipment 110 may connect, via the core network 150, to public networks, such as the Internet 160 to interact with a remote service 170.

Example Devices

[0018] FIG. 2 illustrates an example device diagram 200 of devices ( e.g ., the UE 110, one of the base stations 120) that can implement various aspects of managing inter-radio access technology capabilities. The UE 110 and/or the base station 120 may include additional functions and interfaces that are omitted from FIG. 2 for the sake of clarity.

[0019] The UE 110 includes antennas 202, a radio frequency front end 204 (RF front end 204), an LTE transceiver 206, and a 5GNR transceiver 208 for communicating with the base station 120 in the RAN 140. The RF front end 204 of the UE 110 can couple or connect the LTE transceiver 206, and the 5G NR transceiver 208 to the antennas 202 to facilitate various types of wireless communication. The antennas 202 of the UE 110 may include an array of multiple antennas that are configured similarly to or differently from each other. The antennas 202 and the RF front end 204 can be tuned to, and/or be tunable to, one or more frequency bands defined by the 3GPP LTE and 5GNR communication standards and implemented by the LTE transceiver 206, and/or the 5G NR transceiver 208. Additionally, the antennas 202, the RF front end 204, the LTE transceiver 206, and/or the 5GNR transceiver 208 may be configured to support beamforming for the transmission and reception of communications with the base station 120. By way of example and not limitation, the antennas 202 and the RF front end 204 can be implemented for operation in sub-gigahertz bands, sub-6 GHZ bands, and/or above 6 GHz bands that are defined by the 3GPP LTE and 5G NR communication standards.

[0020] The UE 110 also includes processor(s) 210 and computer-readable storage media 212 (CRM 212). The processor 210 may be a single core processor or a multiple core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. The computer-readable storage media described herein excludes propagating signals. The 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 useable to store device data 214 of the UE 110. The device data 214 includes user data, multimedia data, beamforming codebooks, applications, and/or an operating system of the user equipment 110, which are executable by processor(s) 210 to enable user-plane communication, control-plane signaling, and user interaction with the UE 110.

[0021] CRM 212 also includes a user equipment time division duplex configuration manager 216 (UE TDD configuration manager 216). Alternately or additionally, the UE TDD configuration manager 216 is an application, which may be implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the UE 110. In some aspects, the UE TDD configuration manager 216 receives a TDD slot format, such as from a base station or a core network server, and manages communications transmitted from, and/or received by, the UE 110 based on the received TDD slot format. Alternately or additionally, the UE TDD configuration manager 216 receives metrics, such as UE-generated metrics (e.g, power headroom report, a signal strength estimation, a power status report), and analyzes the UE- generated metrics to determine a modification to the TDD slot format. For example, the UE TDD configuration manager analyzes a power headroom report, and determines a modification to the TDD slot format based on the power headroom report, such as increasing a number of uplink slots and/or symbols in the TDD slot format, reducing a 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 a number of downlink slots and/or symbols to the TDD slot format, reducing a 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 the UE TDD configuration manager 216 transmit a request to a base station ( e.g ., base station 120) that requests the modification to the TDD slot format.

[0022] The device diagram for 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 fashion suitable to perform the functions described herein. The base station 120 includes antennas 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 the UE 110. The RF front end 254 of the base station 120 can couple or connect the LTE transceivers 256 and the 5GNR. transceivers 258 to the antennas 252 to facilitate various types of wireless communication. The antennas 252 of the base station 120 may include an array of multiple antennas that are configured similarly to, or different from, each other. The antennas 252 and the RF front end 254 can be tuned to, and/or be tunable to, one or more frequency bands defined by the 3GPP LTE and 5G NR. communication standards, and implemented by the LTE transceivers 256, and/or the 5G NR. transceivers 258. Additionally, the antennas 252, the RF front end 254, the LTE transceivers 256, and/or the 5G NR. transceivers 258 may be configured to support beamforming, such as Massive-MTMO, for the transmission and reception of communications with the UE 110.

[0023] The base station 120 also include processor(s) 260 and computer-readable storage media 262 (CRM 262). The processor 260 may be a single core processor or a multiple core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. 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 useable to store device data 264 of the base station 120. The device data 264 includes network scheduling data, radio resource management data, beamforming codebooks, applications, and/or an operating system of the base station 120, which are executable by processor(s) 260 to enable communication with the user equipment 110.

[0024] CRM 262 also includes a base station manager 266. Alternately or additionally, the base station manager 266 may be implemented in whole or part as hardware logic or circuitry 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 transceivers 256 and the 5G NR transceivers 258 for communication with the user equipment 110, as well as communication with a core network, such as the core network 150. In at least some aspects, the base station manager 266 may cause the base station 120 to exchange messages with the UE 110 based on a TDD slot format, such as the TDD slot format identified by a base station TDD configuration manager.

[0025] CRM 262 also includes a base station time-division-duplex configuration manager 268 (BS TDD configuration manager 268). Alternatively, or additionally, the BS TDD configuration manager 268 is an application, which may be implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the base station 120. In some aspects, a BS TDD configuration manager 268 determines a TDD slot format to use in exchanging communications between the base station and a UE ( e.g ., UE 110). In implementations, the BS TDD configuration manager communicates the TDD slot format to the base station manager 266 and/or the UE 110. At times, the 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 the metrics to determine a modification to the TDD slot format. For example, the BS TDD configuration manager analyzes a power headroom report, and determines a modification to the TDD slot format based on the power headroom report, such as increasing a number of uplink slots and/or symbols in the TDD slot format, reducing a 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 a number of downlink slots and/or symbols to the TDD slot format, reducing a 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 the BS TDD configuration manager 268 transmits the modified TDD slot format to the base station manager 266 and/or the UE 110 to use in exchanging communications between the base station 120 and the UE 110.

[0026] In one or more implementations, the BS TDD configuration manager 268 receives a Quality-of-Service (QoS) flow identifier (QFI) that indicates a QoS flow associated with the UE 110, where a QoS flow corresponds to an exchange of information dedicated to a particular purpose (e.g. , a particular application, a particular user, a particular service, etc.). In implementations, QoS flows have varying priorities and/or resource reservation mechanisms, where each QoS flow has a QoS profile that describes the varying priorities and/or resource reservation mechanisms. Based on the QFI, the BS TDD configuration manager determines a modification to the TDD slot format that aligns with the priority and resource needs of the corresponding QoS flow, and transmits the modified TDD slot format to the base station manager 266 and/or the UE 110 to use in exchanging information between the base station and UE.

[0027] At times, the BS TDD configuration manger 268 identifies a network interference level through any combination of measurements, such as a reference signal received power (RSRP), a reference signal received quality (RSRQ), an uplink signal to interference and noise ratio (SINR), a downlink SINR, an uplink power interference level, a downlink power interference level, a received signal strength indicator (RSSI), and so forth. In response to identifying the network interference level has met or exceeded a threshold value, 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 gaps, reducing the number of downlink slots and/or symbols within the TDD slot format, etc.

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

[0029] In FIG. 3, the core network server 302 may provide all or part of a function, entity, service, and/or gateway in the 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 embodied on a dedicated server. For example, the core network server 302 may provide all or a portion 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 so forth. The core network server 302 is illustrated as being embodied on a single server that includes processor(s) 304 and computer-readable storage media 306 (CRM 306). The processor 304 may be a single-core processor or a multiple-core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. 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 drives, or Flash memory useful to store device data 308 of the core network server 302. The device data 308 includes data to support a core network function or entity, and/or an operating system of the core network server 302, which are executable by processor(s) 304.

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

[0031] 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, which may be implemented in whole or 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 for a base station ( e.g ., base station 120) to use in exchanging communications with a UE (e.g., UE 110). In implementations, 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. At times, the core TDD configuration manager 312 receives metrics, such as UE- generated metrics and/or BS generated metrics and analyzes and combination of the metrics to determine a modification to the TDD slot format. For example, the core TDD configuration manager analyzes a power headroom report, and determines a modification to the TDD slot format based on the power headroom report, such as increasing a number of uplink slots and/or symbols in the TDD slot format, reducing a 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 a number of downlink slots and/or symbols to the TDD slot format, reducing a 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 the BS TDD configuration manager 268 transmits the modified TDD slot format to the base station 120 and/or the UE 110 to use in exchanging communications between the base station 120 and the UE 110.

[0032] In one or more implementations, the core TDD configuration manager 312 receives a QoS identifier that indicates a QoS flow associated with the UE 110, such as from base station 120. Based on the QoS identifier, the core TDD configuration manager determines a modification to the TDD slot format and transmits the modified TDD slot format to the base station 120 and/or the UE 110 to use in exchanging communications between the base station and UE.

[0033] At times, the core TDD configuration manger 312 identifies a network interference level through any combination of measurements, such as RSRP, RSRQ, SINR, RSSI, and so forth. In response to identifying the network interference level has met or exceeded a threshold value, 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 gaps, reducing the number of downlink slots and/or symbols within the TDD slot format, etc. Afterward, the core TDD configuration manager communicates the modification to the TDD slot configuration to the base station 120 and/or the UE 110. [0034] The core network server 302 also includes a core network interface 314 for communication of user-plane and control-plane data with the other functions or entities in the core network 150, base stations 120, or UE 110. In implementations, the core network server 302 communicates TDD slot formats to the base station 120 using the core network interface 314. The core network server 302 alternately or additionally receives feedback and/or metrics from the base station 120 and/or the UE 110 (by way of the base station 120) using the core network interface 314.

[0035] Having described an example environment and example devices that can be utilized for selecting a TDD slot format specific to a UE, consider now a discussion of TTD slot formats in accordance with one or more implementations.

TDD Slot Formats

[0036] Time division duplexing in a wireless communication system allows two connected devices to communicate with one another 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 one another using TDD slot format configurations.

[0037] Resources 402 represent one or more communication resources shared between a UE 110 and a base station 120. In this example, resources 402 include a carrier frequency 404 shared between the UE 110 and the base station 120. In other words, the base station 120 and the UE 110 each transmit communications to one another using the carrier frequency 404, where the base station 120 transmits downlink communications 406, and the UE 110 transmits uplink communications 408. In implementations, the base station and the UE share the resources 402 based on a TTD slot format. [0038] To demonstrate, consider now FIG. 5 that illustrates an example 500 of a TDD slot format assigning communication resources in accordance with one or more implementations. Example 500 includes a radio frame 502 that represents a frame structure used to communicate information in a wireless network, such as a 3 GPP 5G network. The radio frame represents a unit of partitionable communication resources, such as frequency resources and/or time resources.

[0039] Consider, for example, an implementation in which the radio frame 502 corresponds to 10 milliseconds (ms) of information. Some implementations partition the radio frame, and corresponding communication resources within the radio frame, by time. For instance, radio frame 502 includes subframe 504, subframe 506, and so forth, up to subframe 508, that represent subframe partitions of equal size, where “size” indicates any measurable unit of a communication resource, such as time. Referring to the example in which the radio frame 502 includes 10 ms of information, some implementations subdivide the radio frame 502 into ten equal time durations such that each subframe includes 1 ms of information. It is to be appreciated, however, that a subframe can correspond to a partition of any size.

[0040] In implementations, each subframe of the radio frame 502 partitions the communication resources into smaller units. Subframe 506, for example, partitions the communication resources into slots, where a subframe can include any number of slots, such as two slots, four slots, eight slots, and so forth. Alternatively, or additionally, a subframe corresponds to one slot such that there is no partitioning within the subframe. For clarity, FIG. 5 illustrates the slots as partitions in time, but it is to be appreciated that each slot alternately or additionally partitions other resources, such as frequency bands.

[0041] Subframe 506 includes slot 510 that represents an example slot included in subframe 506 that includes an arbitrary number of symbols, such as Orthogonal Frequency Division Modulation (OFDM) symbols. In implementations, a TDD slot format partitions the communication resource assignments ( e.g ., downlink communication assignments, uplink communication assignments, gap transmission assignments) by time. For example, in the slot 510, the TDD slot format assigns each symbol within the slot to downlink communications or uplink communications. The TDD slot format assigns symbol 512 to uplink communications, symbol 514 to downlink communications, symbol 516 to uplink communications, symbol 518 to downlink communications, and so forth, up to assigning symbol 520 to uplink communications. Thus, in implementations, a TDD slot format assigns the communication resources at a symbol level.

[0042] Consider now FIG. 6 that illustrates another example in which a TDD slot format assigns the 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 multiple subframes (e.g., subframe 604, subframe 606, and so forth, up to subframe 608), where each subframe further partitions the communication resources into an arbitrary number of slots (e.g., slot 610, slot 612, and so forth, up to slot 614). In implementations, a TDD slot format assigns communication resources at a slot level. For instance, in example 600, the TDD slot format assigns slot 610 to uplink communications, slot 612 to downlink communications, and so forth, with slot 614 assigned to downlink communications. In assigning the communication resources at a slot level, the TDD slot format assigns the symbols within the respective slot. For instance, in assigning the slot 612 to downlink communications, the TDD slot format assigns symbols 616 of the slot to downlink communications as well. Thus, in implementations, a TDD slot format assigns the communication resources at the slot level.

[0043] While the example 500 and example 600 describe assigning symbols and slots to uplink communications and downlink communications, alternate or additional implementations use TDD slot formats to create transmission gaps, where a transmission gap corresponds to an empty transmission ( e.g . , a frequency band and/or transmission with a power level at a noise power level). Consider FIG. 7 that illustrates example 700 that includes a TDD slot format that assigns one or more communication resources to gap transmissions in accordance with one or more implementations.

[0044] Example 700 includes communication resources partitioned by time: partition 702, partition 704, partition 706, and so forth, up to partition 708 and partition 710. In some implementations partitions 702, 704, 706, 708 and 710 represent slots, such slot 510 of FIG. 5, slots 610, 612, and 614 of FIG. 6, etc. 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, etc. In example 700, a TDD slot format configures partition 702 and partition 710 as gap transmissions, denoted in FIG. 7 with a “G”, and assigns partitions 704, 706 and 708 to downlink communications.

[0045] Example 700 also includes a power-versus-time graph 712 that illustrates communication transmissions between a UE and a base station that use a shared communication resource, such as the downlink communications 406 and uplink communications 408 of FIG. 4 between the UE 110 and the base station 120 that share carrier frequency 404. More particularly, the power-versus-time graph 712 corresponds to communications based on the TDD slot format denoted 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 between the UE and base station based on the TDD slot format assignment to partition 708 (e.g., downlink communications). Here, the transmissions have an arbitrary power level 716 to signify communication transmissions. The portion of the power-versus-time table at time span 718 also corresponds to communications between the UE and the base station based on the TDD slot format. However, at time span 718, the TDD slot format configures partition 710 as a gap transmission. Accordingly, since neither the UE or the base station are assigned the communication resource associated with 710, neither the UE nor the base station transmit using the communication resources during this time duration. This is further emphasized by power level 720 that corresponds to a noise floor power level, which is lower than power level 716. Thus, implementations of the TDD slot format assign gap transmissions to the communication resources, which correspond to not assigning the communication resource to either uplink or downlink communications.

[0046] Having described example TTD slot formats, consider now example signal and control transactions that can be used to select a TDD slot format specific to a UE in accordance with one or more implementations.

Signaling and Control Transactions to Communicate Neural Network Formation

Configurations

[0047] FIGs. 8-12 illustrate example signaling and control transaction diagrams between a base station, a user equipment, and/or a core network server in accordance with one or more aspects of a select TDD slot format specific to a user equipment. In implementations, the signaling and control transactions may be performed by any combination of the base station 120 (FIG. 1), the UE 110 (FIG. 1), and/or the core network server 302 (FIG. 3) using elements of FIGs. 1-7.

[0048] A first example of signaling and control transactions for selecting a TDD slot format specific to a UE is illustrated by the signaling and control transaction control diagram 800 of FIG. 8. As illustrated, at 805 the base station 120 establishes a wireless connection based on a first TDD slot format with the UE 110, such as that the communications established and described with example 400 of FIG. 4.

[0049] The first TDD slot format assigns communication resources in any suitable manner, such by assigning uplink communications, downlink communications, and/or gap transmissions at a symbol level, such as that described with reference to example 500 of FIG. 5. Alternatively, or additionally, the first TDD slot format assigns communication resources at a slot level, such as that 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 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 (using the TDD slot format) to downlink communications, monitors the communication resources assigned to uplink communications, and/or refrains from transmitting information in communication resources assigned to gap transmissions.

[0050] Similarly, at 810, the UE 110 establishes the wireless connection with the 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 illustrated), and the UE 110 exchanges communications with the base station over the wireless connection using the first TDD slot configuration. For instance, the UE 110 transmits uplink communications using the communication resources assigned (using the TDD slot format) to uplink communications, monitors the communication resources assigned to downlink communications, and/or refrains from transmitting information in communication resources assigned to gap transmissions. [0051] Based on the wireless connection, the base station 120 generates base station-side (BS-side metrics) at 815, such as by generating metrics on uplink communications from the UE 110. Any suitable type of metric can be generated, such as power information, uplink power headroom, uplink SINR, timing measurements, error metrics, Internet Protocol (IP) layer throughput, end-to-end latency, end-to-end packet loss ratio, etc. Alternatively, or additionally, the base station generates network interference metrics.

[0052] Similarly, at 820, the UE 110 generates user equipment-side (UE-side) metrics based on the wireless connection, such as, by way of example and not of 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 bands, 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 retransmissions), latency, Radio Link Control (RLC), Automatic Repeat reQuest (ARQ) metrics, received signal strength (RSSI). In response to generating the metrics, the UE 110 communicates the UE-side metrics to the base station 120 at 825.

[0053] At 830, the base station 120 determines a second TDD slot format based, at least in part, on any combination of the BS-side metrics and/or UE-side metrics. For instance, the BS TDD configuration manager 268 of FIG. 2 analyzes the metrics to determine the second TDD slot format. When the metrics indicate that a UE power energy level is below a threshold value, some implementations of the 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 the UE 110. For instance, the BS TDD configuration manager 268 configures the second TDD slot format to assign contiguous slots and/or symbols to uplink communications. As another example, when the metrics indicate a location of the UE, such as a signal strength metric that indicates the UE is located near an edge of a cell, the BS TDD configuration manager 268 configures the second TDD slot format to assign contiguous slots and/or symbols to uplink communications to increase a range of the corresponding EE. As yet another example, the base station 120 receives a battery level report from the EE 110, and determines to add gap transmissions to the TDD slot format to reduce a number of slots and/or symbols monitored by the EE 110 to conserve battery power. In some implementations, the base station 120 alternately or additionally directs the UE 110 to perform discontinuous reception (DRX) during gap transmissions to conserve battery power.

[0054] At 835, the base station 120 reconfigures the wireless connection based on the second TDD slot format. For instance, the base station 120 communicates the second TDD slot format to the UE 110 and directs 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 the wireless connection based on the second TDD slot format. In some implementations, the process iteratively repeats at 840, where 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 a current and/or changes in an operating state of a wireless communication system to improve signal quality, reduce bit errors, reduce network interference levels, improve data delivery, etc. In other words, the base station 120 identifies the a current and/or changes in the operating state by analyzing the BS-side metrics and/or the UE-side metrics and selects a modified TDD slot format that addresses problems identified by the metrics. The operating state of the wireless communication system can include, by way of example and not of limitation, any combination of channel conditions, a UE configuration, UE capabilit(ies), UE location, network interference levels, transmission medium properties, etc. Thus, various implementations select a TDD slot format specific to a EE by determining the operating state of the wireless communication system in which the EE operates, and modifying the TDD slot format based on the operating state.

[0055] A second example of signaling and control transactions for selecting a TDD slot format specific to a EE is illustrated by the signaling and control transaction control diagram 900 of FIG. 9. As illustrated, at 905 the core network server 302 determines a first TDD slot format. This can include the core network server determining to use a default TDD slot format when first establishing a wireless connection between a base station and a user equipment, such as a format defined by a wireless network system, determining the first TDD slot format based upon metrics, determining the first TDD slot format in response to a request for a TDD slot format, and so forth. To illustrate, and as further described, the core network server 302 receives, at times, communication metrics from a base station and/or a UE ( e.g ., power headroom, RSSI, uplink SINR) and analyzes the metrics to determine a TDD slot format that improves a system performance (e.g., improves a 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 a symbol level (e.g, example 500), while other times, the core network server determines a TDD slot format that assigns the communication resources on a slot level (e.g, example 600).

[0056] In response to determining the first TDD slot format, the core network server communicates the first TDD slot format to the base station 120 at 910. In turn, at 915, the base station 120 forwards the first TDD slot format to the user equipment. [0057] At 920, the base station 120 establishes, with the UE 110, a wireless connection based on the first TDD slot format. The base station, for instance, transmits downlink communications using the communication resources assigned (using the TDD slot format) to downlink communications, monitors the communication resources assigned to uplink communications, and/or refrains from transmitting information in communication resources assigned to gap transmissions.

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

[0059] In response to establishing the wireless connection, the base station 120 generates BS-side metrics at 930, while the UE 110 generates UE-side metrics at 940. In implementations, the base station 120 analyzes communications exchanged with the 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 latency, end-to-end packet loss ratio, and so forth. Similarly, the UE analyzes 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 bands, BLER, QoS, RSSI, etc. At 940, the UE 110 communicates the UE-side metrics to the base station 120. At 945, the base station 120 communicates any combination of metrics to the core network server 302, such as any combination of BS-side metrics and/or UE-side metrics. [0060] In response to receiving the metrics, the core network server determines a second TDD slot format at 950. This can 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, reducing a number of downlink communication assignments to reduce a number of communication resources monitored by the UE 110, assigning gap transmissions in the second TDD slot format in response to the metrics indicating a network interference level exceeds a threshold value, and so forth.

[0061] Afterwards, at 955, the core network server 302 reconfigures the wireless connection using the second TDD slot format. For instance, the core network server 302 communicates the second TDD slot format and directs the base station 120 to manage communications based on the second TDD slot format. Alternately or additionally, the core network server 302 directs the base station 120 to communicate the second TDD slot format to the UE 110.

[0062] Optionally, at 960, the process iteratively repeats, where the core network server 302 receives and/or analyzes the 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 a changing operating state of the wireless communication system to improve signal quality and/or reduce bit errors. In other words, the core network server 302 identifies a current and/or changes in the operating state by analyzing the BS-side metrics and/or the UE-side metrics, and selects a modified TDD slot format that addresses problems identified by the metrics ( e.g ., selects a TDD slot format that improves a signal quality in the wireless network, reduces bit errors, reduces network interference levels, improves data delivery). [0063] A third example of signaling and control transactions for selecting a TDD slot format specific to a user equipment is illustrated by the signaling and control transaction control diagram 1000 of FIG. 10. As illustrated, at 1005 the base station 120 establishes a wireless connection based on a first TDD slot format with the UE 110, such as the communications established and described with 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 at a 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. Alternately 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 (using the TDD slot format) to downlink communications, monitors the communication resources assigned to uplink communications, and/or refrains from transmitting information in communication resources assigned to gap transmissions.

[0064] Similarly, at 1010, the UE 110 establishes the wireless connection with the 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 illustrated), and the UE 110 exchanges communications with the base station over the wireless connection using the first TDD slot configuration. For instance, the UE 110 transmits uplink communications using the communication resources assigned (using the TDD slot format) to uplink communications, monitors the communication resources assigned to downlink communications, and/or refrains from transmitting information in communication resources assigned to gap transmissions. [0065] At 1015, the UE 110 generates UE-side metrics based on the wireless connection. To illustrate, the UE 110 generates any combination of power headroom, signal power information, SINR, CQI, CSI, BLER, RSSI, signal strength estimation, and so forth.

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

[0067] In response to determining the second TDD slot format, the UE 110 transmits a request for the second TDD slot format at 1025. To illustrate, consider an example in which the UE 110 and the base station 120 each have access to a look-up table that identifies multiple TDD slot formats, where the look-up 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 the entry in the look-up table that corresponds to the second TDD slot format, and transmits the respective (look-up table) identifier in the request to indicate the second TDD slot format.

[0068] At 1030, in response to receiving the request, the base station 120 reconfigures the wireless connection based on the second TDD slot format. For instance, the BS TDD slot configuration manager 268 communicates the second TDD slot format to the 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 acknowledge message to the UE 110 that the base station received and approved of the second TDD slot format.

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

[0070] While not illustrated in FIG. 10, alternate implementations of the signaling and control transaction control diagram 1000 include signaling and control transactions with the core network server 302. For instance, alternate implementations of diagram 1000 include the core network server 302 determining and communicating the first TDD slot format of the diagram 1000 to the base station 120, such as that described at 905 and 910 of FIG. 9. Alternately or additionally, alternate implementations of diagram 1000 include the core network server 302 receiving the request for the second TDD slot format, and reconfiguring the wireless connection, such as that described at 955 of FIG. 9.

[0071] A fourth example of signaling and control transactions for selecting a TDD slot format specific to a UE is illustrated by the signaling and control transaction control diagram 1100 of FIG. 11. As illustrated, at 1105 the base station 120 establishes a wireless connection based on a first TDD slot format with the UE 110, such as the communications established and described with 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 at a 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. Alternately 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 (using the TDD slot format) to downlink communications, monitors the communication resources assigned to uplink communications, and/or refrains from transmitting information in communication resources assigned to gap transmissions.

[0072] Similarly, at 1110, the UE 110 establishes the wireless connection with the 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 illustrated), and the UE 110 exchanges communications with the base station over the wireless connection using the first TDD slot configuration. For instance, the UE 110 transmits uplink communications using the communication resources assigned (using the TDD slot format) to uplink communications, monitors the communication resources assigned to downlink communications, and/or refrains from transmitting information in communication resources assigned to gap transmissions.

[0073] Based on the wireless connection, the base station 120 generates base station-side (BS-side metrics) at 1115, such as by generating metrics on uplink communications from the UE 110. Any suitable type of metric can be generated, such as power information, uplink power headroom, uplink SINR, timing measurements, error metrics, Internet Protocol (IP) layer throughput, end-to-end latency, end-to-end packet loss ratio, etc. Alternately or additionally, the base station generates network interference metrics.

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

[0075] At 1130, the base station 120 determines a network interference level by analyzing the UE-side metrics and/or the BS-side metrics. In some implementations, the base station determines that the network interference level meets and/or exceeds a threshold value. In response to determining that the network interference level meets or exceeds the threshold value, the base station 120, by way of the BS TDD configuration manager 268, determines a second TDD slot format that is directed to reducing the network interference level, such as by adding gap transmissions to the second TDD slot format, reducing a number of downlink communication assignments in the second TDD slot format, etc.

[0076] 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 instance, the BS TDD slot configuration manager 268 communicates the second TDD slot format to the base station manager 266. In turn, the base station manager 266 directs the base station 120 to transmit, receive, and/or refrain from transmitting based on the second TD slot format.

[0077] In some implementations, the process iteratively repeats at 1145, where the base station analyzes BS-side metrics and/or UE-side metrics to determine when the network interference level meets or exceeds a threshold value to determine when to select a TDD slot format. This allows the base station 120 to dynamically select a TDD slot format based on a current and/or changes in the operating state of the wireless communication system to improve signal quality, reduce bit errors, reduce network interference levels, improve data delivery, etc. In other words, the base station 120, by way of the BS TDD configuration manager 268, identifies problems in the changing operating environment ( e.g ., a network interference level changing) by analyzing the B S-side and/or UE-side metrics. The B S TDD configuration manager then generates a modified TDD slot format that addresses the identified problems.

[0078] While not illustrated in FIG. 11, alternate implementations of the signaling and control transaction control diagram 1100 include signaling and control transactions with the core network server 302. For instance, alternate implementations of diagram 1100 include the core network server 302 determining and communicating the first TDD slot format of the diagram 1100 to the base station 120, such as that described at 905 and 910 of FIG. 9. Alternately or additionally, implementations of diagram 1000 include the core network server 302 receiving the BS-side and/or UE-side metrics and determining the second TDD slot format based on network interference levels, such as that described at 950 of FIG. 9. In implementations, the core network server reconfigures the wireless connection to correct for network interference levels by directing the base station 120 and/or the UE 110 to use the second TDD slot format, such as that described at 955 of FIG. 9.

[0079] A fifth example of signaling and control transactions for selecting a TDD slot format specific to a user equipment is illustrated by the signaling and control transaction control diagram 1200 of FIG. 12. As illustrated, at 1205, the UE 110 initiates an operation associated with a QoS flow. For instance, a user interacts with the UE 110 through an input mechanism to invoke an operation, such as invoking an application, a music streaming service, a social media service, a video streaming service, a voice-over-Internet-Protocol (VoIP) service, an online gaming application, and so forth. In implementations, the invoked operation exchange, uses, and/or requests information ( e.g ., data) at a higher priority relative to other operations.

[0080] To illustrate, consider an example in which a user invokes a VoIP service. To ensure seamless and real-time voice transmission (e.g., uninterrupted, contiguous output, negligible output latency), a QoS flow associated with a VoIP application has higher priority for data transmissions, signaling exchanges, commands, and so forth, in the wireless network relative to other QoS flows. Accordingly, to ensure that the VoIP application receives a requested priority for the communication resources in the wireless network, the UE requests the QoS flow at 1210, where, in some cases, the request includes an indication of one or more (requested) characteristics for the QoS flows

[0081] In response to receiving the request, the base station 120 determines, at 1215, a TDD slot format based on the requested QoS flow and/or characteristic(s) included in the request. For instance, based on the requested characteristic(s), the base station 120 estimates uplink communication resource needs, and/or downlink communication resource needs based on these demands and determines a TTD slot format that addresses these needs. As one example, the base station 120 selects a TDD slot format that assigns more communication resources to uplink communications.

[0082] 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 the QoS flow. For instance, the base station 120 establishes a wireless connection based on the TDD slot format assigning the communication resources as further described (e.g, example 500, example 600). [0083] Similarly, at 1225, the UE 110 establishes the wireless connection with the base station 120 based on the TDD slot format. In implementations, the UE 110 uses and/or dedicates the communication resources the wireless connection for the QoS flow.

[0084] Having described signaling and control transactions that can be used for selecting a TDD slot format specific to a UE, consider now some example methods that are in accordance with one or more implementations.

Example Methods

[0085] Example methods 1300, 1400, 1500, 1600, and 1700 are described with reference to FIGs. 13, 14, 15, 16, and 17 in accordance with one or more aspects selecting a TDD slot format specific to a UE. The order in which the method blocks are described are 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 an alternate method. Generally, any of the components, modules, methods, and operations described herein can 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 that is local and/or remote to a computer processing system, and implementations can include software applications, programs, functions, and the like. Alternatively, or additionally, any of the functionality described herein can be performed, at least in part, by one or more hardware logic components, such as, and without limitation, Field-programmable Gate Arrays (FPGAs), Application-specific Integrated Circuits (ASICs), Application-specific Standard Products (ASSPs), System-on-a-chip systems (SoCs), Complex Programmable Logic Devices (CPLDs), and the like. [0086] FIG. 13 illustrates an example method 1300 for selecting a TDD slot format specific to a UE. In some implementations, operations of the method 1300 are performed by a network entity, such as the base station 120, while in alternate or additional implementations, operations of the method 1300 are performed by the 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.

[0087] At 1305, a network entity establishes a wireless connection with a user equipment based on a 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 that described at 805 of FIG. 8. As another example, a core network server (e.g., core network server 302) directs a base station (e.g, base station 120) to establish a connection with a UE (e.g., UE 110) In implementations, the core network server communicates the first TDD slot format to the base station, such as that described at 910 of FIG. 9. At times, 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 instance, as described in the example 500, the first TDD slot format indicates an assignment for each symbol of a slot, (e.g., uplink communications, downlink communications, gap transmissions). As another example, as described in the example 600, the first TDD slot format indicates an assignment for each slot of a subframe, (e.g., uplink communications, downlink communications, gap transmissions). In some implementations, first TDD slot format indicates a same assignment to each symbol or slot (e.g., all uplink communication assignments, all downlink communication assignments, all gap transmission assignments). In other implementations, the first TDD slot format indicates different assignments to each symbol or slot.

[0088] At 1310, the network entity identifies one or more metrics associated with the wireless connection. As one example, the network entity ( e.g ., base station 120) receives UE-side metrics that are generated by a UE (e.g., UE 110), such as those described at 820 of FIG. 8 (e.g, a signal strength estimation, a power headroom report, a power status report). Alternately or additionally, the base station (e.g, base station 120) generates BS-side metrics using communications exchanged over the wireless connection, such as those described at 815 of FIG. 8. As another example, the base station forwards the UE-side metrics and/or the BS-side metrics to the core network server (e.g, core network server 302), such as that described at 945 of FIG. 9.

[0089] 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 the second TDD slot format based on metrics from a UE (e.g, UE 110), such as a power status report. The base station, for example, analyzes the power status report and determines that a battery level of the UE has fallen below a threshold value. To preserve the UE’s battery life, 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 a number of transmissions that are monitored by the UE and preserve the battery life/power. In some implementations, the base station 120 alternatively or additionally directs the UE 110 to perform discontinuous reception (DRX) during the 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 contiguous resources (e.g, slot, symbol) to uplink communications. In other words, the base station includes two or more uplink communication assignments in the second TDD slot format to increase a received power energy level at the base station (from the UE).

[0090] In some implementations, the base station receives a Quality-of-Service flow identifier and determines communication resource condition(s) based on a corresponding Quality- of-Service flow ( e.g ., diagram 1200). In turn, the base station determines the second TDD slot format based on fulfilling the communication resource condition(s).

[0091] At 1320, the network entity reconfigures the wireless connection based on the second time-division-duplex (TDD) slot format, such as that described at 835 of FIG. 8 and/or at 955 of FIG. 9. For instance, the base station (e.g., base station 120) communicates the second TDD slot format to the UE (e.g, UE 110) and directs the UE to exchange communications over the wireless connection based on the second TDD slot format. Alternately or additionally, the core network server (e.g, core network server 302) communicates the second TDD slot format to the base station (e.g., base station 120), and directs the base station to communication the second TDD slot format to the UE (e.g, UE 110). In implementations, the method 1300 repeats, as indicated at 1325, such that the network entity determines modifications to the TDD slot format based on a current and/or changes in the operating state of the wireless communication system (as indicated by the received metrics) to improve an overall performance of the wireless communication system as further described.

[0092] FIG. 14 illustrates an example method 1400 for selecting a TDD slot format specific to a UE. In some implementations, operations of the method 1400 are performed by a network entity, such as the base station 120, while in alternate or additional implementations, operations of the method 1400 are performed by the 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.

[0093] At 1405, a 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 that described at 1005 of FIG. 10. As another example, a core network server (e.g, core network server 302) directs a base station (e.g, base station 120) to establish a connection with a UE (e.g, UE 110) In implementations, the core network server communicates the first TDD slot format to the base station, such as that described at 910 of FIG. 9. At times, 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 instance, as described in the example 500, the first TDD slot format indicates an assignment for each symbol of a slot, (e.g., uplink communications, downlink communications, gap transmissions). As another example, as described in the example 600, the first TDD slot format indicates an assignment for each slot of a subframe, (e.g., uplink communications, downlink communications, gap transmissions). In some implementations, first TDD slot format indicates a same assignment to each symbol or slot (e.g, all uplink communication assignments, all downlink communication assignments, all gap transmission assignments). In other implementations, the first TDD slot format indicates different assignments to each symbol or slot.

[0094] At 1410, the network entity receives a request that indicates 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 the second TDD slot format, such as that described at 1025 of the diagram 1000. This allows the UE 110 to dynamically select a TDD slot format based on a current and/or changes in the operating state of a wireless communication system to improve signal quality, reduce bit errors, reduce network interference levels, improve data delivery, etc., and request the selected TDD slot format to be implemented for the wireless connection.

[0095] Accordingly, at 1415, the network entity reconfigures the wireless connection based on the second time-division-duplex (TDD) slot format, such as that described at 1030 of FIG. 10 and/or at 955 of FIG. 9. For instance, the base station ( e.g ., base station 120) communicates the second TDD slot format to the UE (e.g., UE 110) and directs the UE to exchange communications over the wireless connection based on the second TDD slot format. Alternately or additionally, the core network server (e.g, core network server 302) communicates the second TDD slot format to the base station (e.g., base station 120), and directs the base station to communication the second TDD slot format to the UE (e.g., UE 110). In implementations, the method 1400 iteratively repeats, as indicated at 1420, such that the network entity receives modifications to the TDD slot format based on a current, and/or changes to, the operating state as further described.

[0096] FIG. 15 illustrates an example method 1500 for selecting a TDD slot format specific to a UE. In some implementations, operations of the method 1500 are performed by a network entity, such as the base station 120, while in alternate or additional implementations, operations of the method 1500 are performed by the 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 a TDD slot format is selected based on a network interference level. [0097] At 1505, a 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 that described at 1105 and/or 1110 of FIG. 11. As another example, a core network server (e.g, core network server 302) directs a base station (e.g, base station 120) to establish a connection with a UE (e.g, UE 110). In implementations, the core network server communicates the first TDD slot format to the base station, such as that described at 910 of FIG. 9. At times, 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 instance, as described in the example 500, the first TDD slot format indicates an assignment for each symbol of a slot, (e.g., uplink communications, downlink communications, gap transmissions). As another example, as described in the example 600, the first TDD slot format indicates an assignment for each slot of a subframe, (e.g., uplink communications, downlink communications, gap transmissions). In some implementations, first TDD slot format indicates a same assignment to each symbol or slot (e.g, all uplink communication assignments, all downlink communication assignments, all gap transmission assignments). In other implementations, the first TDD slot format indicates different assignments to each symbol or slot.

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

[0099] Accordingly, in response to determining that the network interference level exceeds the threshold value, the network entity determines a second time-division-duplex (TDD) slot format at 1515. Abase station ( e.g ., base station 120), for example, determines a slot format that is directed to reducing the network interference level by adding gap transmission assignments to the second TDD slot format, reducing a number of downlink communication assignments in the second TDD slot format, etc.

[0100] At 1520, the network entity reconfigures the wireless connection between the base station and the user equipment (UE) based on the second time-division-duplex (TDD) slot format, such as that described at 1140 of FIG. 11 and/or at 955 of FIG. 9. For instance, the base station (e.g., base station 120) communicates the second TDD slot format to the UE (e.g, UE 110) and directs the UE to exchange communications over the wireless connection based on the second TDD slot format. Alternately or additionally, the core network server (e.g, core network server 302) communicates the second TDD slot format to the base station (e.g, base station 120), and directs the base station to communication the second TDD slot format to the UE (e.g, UE 110). In implementations, the method 1500 iteratively repeats, as indicated at 1525, such that the network entity monitors network interference levels, and configures the TDD slot format to improve network interference levels (e.g, reduce interference levels) as further described.

[0101] FIG. 16 illustrates an example method 1600 for selecting a TDD slot format specific to a UE. In some implementations, operations of the method 1600 are performed by a UE, such as the 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 a TDD slot format is selected based on metrics.

[0102] At 1605, a UE establishes a wireless connection with a base station based on a first time-division-duplex (TDD) slot format. For instance, a UE ( e.g ., UE 110) receives the first TDD slot format from a base station (e.g., base station 120), such as by the base station indicating an entry in a look-up table that includes slot format patterns. In response to receiving the first TDD slot format, the UE establishes the wireless connection by exchanging communications based on the first TDD slot format, such as that described at 810 of FIG. 1 and at 925 of FIG. 9.

[0103] At 1610, the UE generates one or more metrics. In one or more implementations, the UE (e.g, UE 110) generates the metrics based on communication exchanges over the wireless connections, such as those described at 820 of FIG. 8. Alternately or additionally, the UE generates metrics that describe an operating state of the UE while maintaining the wireless connection, such as a power status report. Afterwards, the UE transmits the metrics to the base station at 1615. For instance, 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 at 940 of FIG. 9.

[0104] At 1620, the UE receives a second time-division-duplex (TDD) slot format. In implementations, the UE (e.g, UE 110) receives a TDD slot format based on the metrics transmitted at 1615, such as a TDD slot format that addresses problems indicated by the metrics (e.g, a TDD slot format that improves a signal quality in the wireless network, reduces bit errors, reduces network interference levels, improves data delivery). Alternatively, or additionally, the UE receives directions to perform discontinuous reception (DRX) during gap transmissions as assigned in the second TTD slot format. [0105] At 1625, the user equipment (UE) reconfigures the wireless connection based on the second time-division-duplex (TDD) slot format, such as that described at 835 of FIG. 8 and/or at 955 of FIG. 9. For instance, the UE ( e.g ., UE 110) exchanges communications over the wireless connection based on the second TDD slot format. In implementations, the method 1600 iteratively repeats, as indicated at 1530, such that the UE generates and communicates metrics to a base station, and reconfigures a wireless connection using a TDD slot format based on the metrics as further described.

[0106] FIG. 17 illustrates an example method 1700 for selecting a TDD slot format specific to a UE. In some implementations, operations of the method 1700 are performed by a UE, such as the 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 1200 of FIG. 12 in which a TDD slot format is selected based on a QoS flow.

[0107] At 1705, a UE initiates an operation associated with a Quality-of-Service flow. For example, a UE (e.g., UE 110) receives input that invokes an application and/or a service, where the application and/or service is associated with a QoS flow (e.g, at 1205 of diagram 1200). To illustrate, a user launches an audio streaming service, a social media service, a video streaming service, a voice-over-Intemet-Protocol (VoIP) service, an online gaming application, and so forth, that has communication resource conditions identified by an associated QoS flow, such as a traffic pattern, an activity pattern, a duty cycle, an interrupt priority level, a data priority level, and so forth.

[0108] Afterwards, at 1710, the UE transmits an indication of the Quality-of-Service flow to the base station. For example, the UE (e.g, UE 110) determines a QFI associated with the QoS flow by comparing communication resource condition(s) associated with the operation to QoS profiles and obtains the QFI from a QoS profile that matches the communication resource condition(s). Afterwards, the UE transmits the QFI to the base station. Alternately 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.

[0109] In response to transmitting the indication, the UE receives a time-division-duplex (TDD) slot format that is based on the indication at 1715. The UE ( e.g ., UE 110) receives, for example, a modification to a TDD slot format used for an existing wireless connection between the UE and the base station. Alternately or additionally, the UE receives a TDD slot format to use in establishing a wireless connection between the UE and the base station for the operation.

[0110] Accordingly, at 1720, the UE establishes a wireless connection with the base station based on the 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 by exchanging communications based on communication resource assignments as described in example 500 and/or example 600. Afterwards, at 1725, the UE exchanges communications associated with the operation using the wireless connection.

[0111] In the following, several examples are described:

[0112] An example method for selecting or configuring a slot format based on an operating state of a wireless communication system comprises: establishing, by a base station, a wireless connection with a 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: uplink communication assignments, downlink communication assignments, or gap transmission assignments; 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 directing the user equipment to exchange communications over the wireless connection based on a second time-division-duplex slot format that assigns the communication resources of the wireless connection using a second arrangement of the one or more: uplink communication assignments, downlink communication assignments, or gap transmission assignments, the second arrangement being different from the first arrangement.

[0113] The reconfiguring the wireless connection based on the second time-division- duplex slot format may be responsive to a trigger event. The trigger event may be indicative of a change in the wireless connection, a transmission environment, an operating environment and/or state of the user equipment. For example, the method may include identifying, by the base station, one or metrics associated with the wireless connection. The method may include determining the second time-division-duplex slot format, based on the one or more metrics. Alternatively, or additionally, the method may include receiving, from the user equipment, a request that indicates 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 value and determining, in response to the network interference level exceeding the threshold value, the second time-division-duplex slot format.

[0114] The determining the second time-division-duplex slot format may comprise determining to assign two or more contiguous slots to uplink communications.

[0115] The identifying the one or more metrics may comprise receiving, from the user equipment, at least one of: a signal strength estimation; a power headroom report; or a power status report. The identifying the one or more metrics may further comprise receiving the power status report from the user equipment; and determining, from the power status report, that a battery level of the user equipment has fallen below a threshold value. The determining the second time- division-duplex slot format may comprise 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.

[0116] The user equipment may be directed to perform discontinuous reception during the one or more gap transmissions.

[0117] The identifying the one or more metrics associated with the wireless connection may comprise: receiving, from the user equipment, a Quality-of-Service flow identifier associated with a Quality-of-Service flow. One or more communication resource conditions of the Quality- of-Service flow may be determined based on the Quality-of-Service flow identifier. The determining the second time-division-duplex slot format may be based, at least in part, on the one or more communication resource conditions of the Quality-of-Service flow.

[0118] The second time-division-duplex slot format may assign two or more contiguous communication resources to uplink communications. The two or more contiguous communication resources may comprise slots or symbols.

[0119] 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.

[0120] A determined network interference level may comprise a downlink network interference level. The determining the second time-division-duplex slot format may comprise 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.

[0121] The determining the second time-division-duplex slot format may comprise determining to include one or more of the gap transmission assignments in the second time- division-duplex slot format based on a determined network interference level. [0122] The base station may be a first base station. Determining that the network interference level in the wireless communication system exceeds the threshold value may comprise receiving a third time-division-duplex slot format from a second base station; analyzing the third time-division-duplex slot format; and determining, based on the analyzing, that the third time- division-duplex slot format generates the network interference level that exceeds the threshold value.

[0123] The third time-division-duplex slot format may include information that indicates a target user equipment and a location of the target user equipment.

[0124] Another example method for selecting or configuring a slot format operating state of a wireless communication system comprises: establishing, by the 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: uplink communication assignments, downlink communication assignments, or gap transmission assignments; receiving, from the base station, a second time-division-duplex slot format that assigns the communication resources of the wireless connection using a second arrangement of the one or more: uplink communication assignments, downlink communication assignments, or gap transmission assignments, the second arrangement being different from the first arrangement; and reconfiguring the wireless connection based on second time-division-duplex slot format.

[0125] The method may include generating, using the user equipment, one or more metrics associated with the wireless connection; transmitting the one or more metrics to the base station. The second time-division-duplex slot format may be based, at least on part, on the one or more metrics. [0126] The generating the one or more metrics associated with the wireless connection may comprise generating at least one of: a power headroom report; a battery level report; or signal strength estimation.

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

[0128] 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.

[0129] An indication to perform directional-discontinuous reception during one or more gap transmissions may be received from the base station. The 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.

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

[0131] Another example method for selecting or configuring a slot format operating state of a wireless communication system comprises: initiating, using the user equipment, an operation associated with a Quality-of-Service flow; transmitting, to the base station, an indication of the Quality-of Service flow associated with the operation; receiving, from the base station, a time- division-duplex slot format that assigns communication resources of a wireless connection using an arrangement of one or more: uplink communication assignments, downlink communication assignments, or gap transmission assignments, the arrangement based, at least on part, on the indication; establishing a wireless connection with the base station based on time-division-duplex slot format; and exchanging communications associated with the operation using the wireless connection.

[0132] The operation associated with the Quality of Service flow may comprise: a voice- over-internet-protocol service; a social media application; an audio streaming service; or a video streaming service.

[0133] Although aspects of selecting a TDD slot format specific to a UE 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, the specific features and methods are disclosed as example implementations of selecting a TDD slot format specific to a UE, and other equivalent features and methods are intended to be within the scope of the appended claims. Further, various different aspects are described, and it is to be appreciated that each described aspect can be implemented independently or in connection with one or more other described aspects.