Methods and apparatus for wireless communication and non-transient computer-readable media
By identifying and handling conflicts between legacy TTI and shortened TTI communications using user equipment, the problems of poor transmission efficiency and resource utilization in wireless communication systems are resolved, resulting in more efficient communication transmission.
Patent Information
- Application Number
- CN202310211461.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2017-07-26
- Filing Date
- 2017-12-20
- Publication Date
- 2025-10-28
- Estimated Expiration
- 2037-12-20
AI Technical Summary
Existing wireless communication systems suffer from a conflict between legacy TTI communication and shortened TTI communication, resulting in poor transmission efficiency and resource utilization, which has not been effectively resolved, especially in LTE and NR technologies.
By identifying and handling potential conflicts between legacy TTI communications and shortened TTI communications through user equipment (UE), determining whether to transmit communications within a threshold time, and optimizing the transmission process, this includes identifying potential conflicts in the UE, determining transmission priorities, and performing appropriate communication transmissions.
It effectively resolves the conflict between the old TTI and sTTI communication, improves transmission efficiency and resource utilization, and optimizes the performance of wireless communication systems.
Smart Images

Figure CN116170886B_ABST
Abstract
Description
[0001] This application is a divisional application of Chinese patent application No. 201780085601.9 (International Application No. PCT / US2017 / 067595), filed on December 20, 2017, entitled "Technology and apparatus for handling conflicts between legacy Transmission Time Interval (TTI) communication and shortened TTI communication". background Technical Field
[0003] The various aspects of this disclosure generally relate to wireless communications, and more particularly to techniques and apparatus for resolving conflicts between legacy TTI communications and shortened TTI (sTTI) communications. Background Technology
[0005] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is an enhancement set of the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).
[0006] Wireless communication networks may include several base stations (BSs) capable of supporting communication between several user equipments (UEs). UEs can communicate with the BS via downlinks and uplinks. A downlink (or forward link) refers to the communication link from the BS to the UE, while an uplink (or reverse link) refers to the communication link from the UE to the BS. As will be described in more detail herein, a BS can refer to a B-node, gNB, access point (AP), radio headend, transmit / receive point (TRP), new radio (NR) BS, 5G B-node, etc.
[0007] The multiple access technologies mentioned above have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, country, region, and even global levels. New Radio (NR) (also known as 5G) is an enhancement set to the LTE mobile standard issued by the 3rd Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and better integrating with other open standards that support beamforming, multiple-input multiple-output (MIMO) antenna technologies and carrier aggregation, using OFDM with cyclic prefix (CP) on the downlink (DL) and CP-OFDM and / or SC-FDM (e.g., also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink (UL). However, with the continued growth in demand for mobile broadband access, there is a need for further improvements to LTE and NR technologies. Preferably, these improvements should be applicable to other multiple access technologies and telecommunications standards that employ them. Summary of the Invention
[0008] In one aspect of this disclosure, a method, apparatus (equipment), and computer program product are provided.
[0009] In some aspects, the method may include: identifying a potential conflict between a scheduled legacy transport time interval (TTI) communication and a scheduled shortened TTI (sTTI) communication, the legacy TTI communication having a longer legacy TTI duration than the sTTI duration associated with the sTTI communication; determining by the UE whether the legacy TTI communication should be transmitted within a threshold time; and transmitting by the UE at least in part based on the determination of the sTTI communication, the legacy TTI communication, or any combination thereof.
[0010] In some aspects, the apparatus may include a memory and at least one processor coupled to the memory. The at least one processor may be configured to: identify a potential conflict between a scheduled legacy transmission time interval (TTI) communication and a scheduled shortened TTI (sTTI) communication, the legacy TTI communication having a longer legacy TTI duration than the sTTI duration associated with the sTTI communication; determine whether the legacy TTI communication should be transmitted within a threshold time; and transmit at least one of the sTTI communication, the legacy TTI communication, or any combination thereof, at least in part based on the determination.
[0011] In some aspects, the apparatus may include: means for identifying a potential conflict between a scheduled legacy transmission time interval (TTI) communication and a scheduled shortened TTI (sTTI) communication, the legacy TTI communication having a longer legacy TTI duration than the sTTI duration associated with the sTTI communication; means for determining whether the legacy TTI communication should be transmitted within a threshold time; and means for transmitting at least one of the sTTI communication, the legacy TTI communication, or any combination thereof, at least in part based on the determination.
[0012] In some aspects, a computer program product may include a non-transient computer-readable medium storing computer-executable code. This code may include: code for identifying a potential conflict between a scheduled legacy transport time interval (TTI) communication and a scheduled shortened TTI (sTTI) communication, the legacy TTI communication having a longer legacy TTI duration than the sTTI duration associated with the sTTI communication; code for determining whether the legacy TTI communication should be transmitted within a threshold time; and code for transmitting at least one of the sTTI communication, the legacy TTI communication, or any combination thereof, at least in part based on the determination.
[0013] The aspects generally include, as described herein with reference to and illustrated in the accompanying drawings, methods, apparatus, systems, computer program products, non-transient computer-readable media, user equipment, wireless communication devices, and processing systems.
[0014] The foregoing has broadly outlined the features and technical advantages of the examples according to this disclosure in an effort to facilitate a better understanding of the following detailed description. Additional features and advantages will be described thereafter. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for implementing the same purposes as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, in both their organization and manner of operation, and their associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each drawing is provided for illustrative and descriptive purposes and does not define any limitation on the claims. Attached Figure Description
[0015] Figure 1 This is a diagram illustrating an example of a wireless communication network.
[0016] Figure 2 This is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless communication network.
[0017] Figure 3 This is a diagram illustrating an example of frame structure in a wireless communication network.
[0018] Figure 4 This is a diagram illustrating two example subframe formats with a normal cyclic prefix.
[0019] Figure 5 This is a diagram illustrating an example logical architecture of a distributed radio access network (RAN).
[0020] Figure 6 This is a diagram illustrating an example physical architecture for distributed RAN.
[0021] Figure 7 This is a diagram illustrating an example of a downlink (DL) centralized wireless communication architecture.
[0022] Figure 8 This is a diagram illustrating an example of an uplink (UL) centralized wireless communication architecture.
[0023] Figure 9-11 These are flowcharts of various example wireless communication methods.
[0024] Figure 12 It is a conceptual data flow diagram that explains the data flow between different modules / devices / components in the example equipment.
[0025] Figure 13 This is a diagram illustrating an example of the hardware implementation of an equipment employing a processing system. Detailed Implementation
[0026] The detailed description that follows, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and is not intended to imply any configuration in which the concepts described herein can be practiced. This detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.
[0027] Several aspects of a telecommunications system will now be presented with reference to various equipment and methods. These equipment and methods will be described in detail below and explained in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.
[0028] As an example, an element, or any part of an element, or any combination of elements, may be implemented using a "processing system" comprising one or more processors. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in the processing system may execute software. Software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms.
[0029] Accordingly, in one or more example embodiments, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, these functions may be stored or encoded as one or more instructions or code on a computer-readable medium. A computer-readable medium includes a computer storage medium. The storage medium may be any available medium capable of being accessed by a computer. By way of example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), compact disc ROM (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, combinations of computer-readable media of the foregoing types, or any other medium that can be used to store computer-executable code in the form of instructions or data structures and is accessible by a computer.
[0030] An access point (“AP”) may include, be implemented as, or be referred to as a B-node, radio network controller (“RNC”), evolved B-node (eNB), base station controller (“BSC”), base transceiver station (“BTS”), base station (“BS”), transceiver function (“TF”), radio router, radio transceiver, basic service set (“BSS”), extended service set (“ESS”), radio base station (“RBS”), B-node (NB), gNB, 5G NB, NR BS, transmit and receive point (TRP), or some other term.
[0031] An access terminal (“AT”) may include, be implemented as, or be referred to as: an access terminal, subscriber station, subscriber unit, mobile station, remote station, remote terminal, user terminal, user agent, user equipment, user gear (UE), user station, wireless node, or some other term. In some aspects, an access terminal may include a cellular phone, smartphone, cordless phone, Session Initiation Protocol (“SIP”) phone, Wireless Local Loop (“WLL”) station, personal digital assistant (“PDA”), tablet, netbook, smartbook, ultrabook, handheld device with wireless connectivity, station (“STA”), or some other suitable processing device connected to a wireless modem. Accordingly, one or more aspects taught herein can be incorporated into telephones (e.g., cellular phones, smartphones), computers (e.g., desktop computers), portable communication devices, portable computing devices (e.g., laptops, personal data assistants, tablets, netbooks, smartbooks, ultrabooks), wearable devices (e.g., smartwatches, smart glasses, smart bracelets, smart wristbands, smart rings, smart clothing, etc.), medical devices or equipment, biometric sensors / devices, entertainment devices (e.g., music devices, video devices, satellite radios, gaming devices, etc.), automotive components or sensors, smart meters / sensors, industrial manufacturing equipment, GPS devices, or any other suitable device configured to communicate via wireless or wired media. In some aspects, a node is a wireless node. A wireless node may, for example, provide connectivity to or to a network (e.g., a wide area network, such as the Internet or cellular networks) via wired or wireless communication links. Some UEs may be considered machine-type communication (MTC) UEs, which may include remote devices capable of communicating with a base station, another remote device, or some other entity. Machine-type communication (MTC) can refer to communication involving at least one remote device at at least one end of the communication, and can include forms of data communication involving one or more entities that do not necessarily require human interaction. An MTC UE can include a UE capable of MTC communication with an MTC server and / or other MTC devices via, for example, a Public Land Mobile Network (PLMN). Examples of MTC devices include sensors, meters, location tags, monitors, drones, robots / robotic devices, and so on. MTC UEs, and other types of UEs, can be implemented as NB-IoT (Narrowband Internet of Things) devices.
[0032] It should be noted that although the aspects herein may be described using terms commonly associated with 3G and / or 4G wireless technologies, the aspects of this disclosure may be applied in other generations of communication systems, including NR technologies, such as 5G and later generations.
[0033] Figure 1This is a diagram illustrating a network 100 in which various aspects of this disclosure can be practiced. Network 100 can be an LTE network or some other wireless network, such as a 5G or NR network. Wireless network 100 may include several BS 110s (shown as BS110a, BS 110b, BS 110c, and BS 110d) and other network entities. A BS is an entity that communicates with a user equipment (UE) and may also be referred to as a base station, NR BS, B-node, gNB, 5G NB, access point, TRP, etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of a BS and / or the BS subsystem serving that coverage area, depending on the context in which the term is used.
[0034] A BS can provide communication coverage for macrocells, picocells, femtocells, and / or any type of cell. Macrocells can cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by UEs with service subscriptions. Picocells can cover a relatively small geographic area and allow unrestricted access by UEs with service subscriptions. Femtocells can cover a relatively small geographic area (e.g., a residential area) and allow restricted access by UEs associated with that femtocell (e.g., UEs in a Closed Subscriber Group (CSG)). A BS used for macrocells may be referred to as a macro BS. A BS used for picocells may be referred to as a pico BS. A BS used for femtocells may be referred to as a femto BS or a home BS. Figure 1 In the example shown, BS110a can be a macro BS for macro cell 102a, BS 110b can be a pico BS for pico cell 102b, and BS 110c can be a femto BS for femto cell 102c. A BS can support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “B node,” “5G NB,” and “cell” are used interchangeably herein.
[0035] In some examples, the cell may not be stationary, and the geographical area of the cell may move depending on the location of the mobile BS. In some examples, BSs may interconnect with each other and / or interconnect to one or more other BSs or network nodes (not shown) in access network 100 via various types of backhaul interfaces (such as direct physical connections, virtual networks, and / or similar devices using any suitable transport network).
[0036] The wireless network 100 may also include a relay station. A relay station is an entity capable of receiving data transmissions from an upstream station (e.g., a BS or a UE) and transmitting those data transmissions to a downstream station (e.g., a UE or a BS). A relay station can also be a UE capable of relaying transmissions for other UEs. Figure 1 In the example shown, relay station 110d can communicate with macro BS 110a and UE 120d to facilitate communication between BS 110a and UE 120d. A relay station may also be referred to as a relay BS, relay base station, relay, etc.
[0037] Wireless network 100 can be a heterogeneous network comprising different types of Base Stations (BSs) (e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs may have high transmit power levels (e.g., 5 to 40 watts), while pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 watts).
[0038] Network controller 130 can be coupled to a group of BSs and provide coordination and control over these BSs. Network controller 130 can communicate with each BS via backhaul. These BSs can also communicate with each other directly or indirectly, for example, via wireless or wired backhaul.
[0039] UEs 120 (e.g., 120a, 120b, 120c) may be distributed throughout the wireless network 100, and each UE may be stationary or mobile. A UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. A UE may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), an in-vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, or any other suitable device configured to communicate via wireless or wired media. Some UEs may be considered evolved or enhanced machine-type communications (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, and remote devices such as sensors, meters, monitors, location tags, etc., which can communicate with a base station, another device (e.g., a remote device), or some other entity. Wireless nodes can provide connectivity to or to a network (e.g., a wide area network, such as the Internet or a cellular network) via wired or wireless communication links, for example. Some UEs can be considered Internet of Things (IoT) devices. Some UEs can be considered Customer Premises Equipment (CPE).
[0040] exist Figure 1 In the diagram, a solid line with a double arrow indicates a desired transmission between the UE and the serving BS, which is the BS designated to serve the UE on the downlink and / or uplink. A dashed line with a double arrow indicates a potential interference transmission between the UE and the BS.
[0041] Generally, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.
[0042] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., a base station) allocates resources for communication among some or all of the equipment and apparatus within the scheduling entity's service area or cell. Within this disclosure, as further discussed below, the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, the subordinate entity utilizes the resources allocated by the scheduling entity.
[0043] A base station is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity to schedule resources for one or more subordinate entities (e.g., one or more other UEs). In this example, the UE is acting as the scheduling entity, and other UEs utilize the resources scheduled by the UE for wireless communication. A UE can act as a scheduling entity in a peer-to-peer (P2P) network and / or in a mesh network. In the mesh network example, UEs may optionally communicate directly with each other in addition to communicating with the scheduling entity.
[0044] Thus, in a wireless communication network with scheduled access to time-frequency resources and with cellular, P2P, and mesh configurations, a scheduling entity and one or more subordinate entities can use the scheduled resources to communicate.
[0045] As indicated above, Figure 1 This is provided merely as an example. Other examples are possible and may differ from those provided. Figure 1 The example described.
[0046] Figure 2 It shows that it can be Figure 1 Block diagram 200 shows the design of base station 110 and UE 120, one of the base stations and one of the UEs. Base station 110 may be equipped with T antennas 234a to 234t, while UE 120 may be equipped with R antennas 252a to 252r, where generally T≥1 and R≥1.
[0047] At base station 110, transmit processor 220 can receive data destined for one or more UEs from data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQI) received from each UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS(s) selected for each UE, and provide data symbols for all UEs. Transmit processor 220 can also process system information (e.g., semi-static resource allocation information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper-layer signaling, etc.), and provide overhead symbols and control symbols. Transmit processor 220 can also generate reference symbols for reference signals (e.g., CRS) and synchronization signals (e.g., primary synchronization signal (PSS) and secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and can provide T output symbol streams to T modulators (MODs) 232a to 232t. Each modulator 232 can process its own output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t can be transmitted via T antennas 234a to 234t, respectively. According to some aspects described in more detail below, position coding can be used to generate synchronization signals to convey additional information.
[0048] At UE 120, antennas 252a to 252r can receive downlink signals from base station 110 and / or other base stations and can provide the received signals to demodulators (DEMODs) 254a to 254r respectively. Each demodulator 254 can condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain an input sample. Each demodulator 254 can further process the input sample (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 256 can obtain the received symbols from all R demodulators 254a to 254r, perform MIMO detection on these received symbols where applicable, and provide detected symbols. Receive (RX) processor 258 can process (e.g., demodulate and decode) these detected symbols, provide the decoded data to UE 120 to data sink 260, and provide the decoded control information and system information to controller / processor 280. Channel processor can determine RSRP, RSSI, RSRQ, CQI, etc.
[0049] On the uplink, at UE 120, transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., reports including RSRP, RSSI, RSRQ, CQI, etc.). Transmit processor 264 can also generate reference symbols for one or more reference signals. Symbols from transmit processor 264 can be pre-encoded by TX MIMO processor 266 where applicable, further processed by modulators 254a to 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to base station 110. At base station 110, uplink signals from UE 120 and other UEs can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 where applicable, and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. The receiver processor 238 can provide decoded data to the data sink 239 and decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the network controller 130 via the communication unit 244. The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292.
[0050] Figure 2 The controllers / processors 240 and 280 and / or (and any other) components in the BS 110 and UE 120 may respectively direct operations at the BS 110 and UE 120 to handle conflicts between legacy TTI and sTTI communications. For example, the controllers / processors 280 and / or other processors and modules at the BS 110 may perform or direct operations at the UE 120 to handle conflicts between legacy TTI and sTTI communications. Figure 9 Method 900 Figure 10 Method 1000 Figure 11 The operation of method 1100, and / or other methods described herein. In some respects, Figure 2 One or more of the components shown can be used to perform Figure 9 Example method 900 Figure 10 Method 1000 Figure 11 Method 1100, and / or other methods using the techniques described herein. Memory 242 and 282 may store data and program code for use by BS 110 and UE 120, respectively. Scheduler 246 may schedule the UE for data transmission on the downlink and / or uplink.
[0051] As indicated above, Figure 2This is provided merely as an example. Other examples are possible and may differ from those provided. Figure 2 The example described.
[0052] Figure 3 An example frame structure 300 for FDD in a telecommunications system (e.g., LTE) is shown. The transmission timeline of each of the downlink and uplink can be divided into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10 milliseconds (ms)) and may be divided into 10 subframes with indices 0 to 9. Each subframe may include two time slots. Each radio frame may thus include 20 time slots with indices 0 to 19. Each time slot may include L symbol periods, for example, for a normal cyclic prefix (e.g., ... Figure 3 (As shown) is 7 symbol periods, or 6 symbol periods for the extended cyclic prefix. The 2L symbol periods in each subframe can be assigned indices from 0 to 2L-1.
[0053] While this article describes some technologies using terms such as frames, subframes, and time slots, these technologies are equally applicable to other types of wireless communication architectures that can be referred to in 5G NR using terms other than "frame," "subframe," and "time slot." In some respects, a wireless communication architecture can refer to a communication unit with periodic time bounds defined by wireless communication standards and / or protocols.
[0054] In some telecommunications systems (e.g., LTE), the Base Station (BS) can transmit the Primary Synchronization Signal (PSS) and Secondary Synchronization Signal (SSS) on the downlink at the center of the system bandwidth used for each cell supported by the BS. The PSS and SSS can be transmitted in subframes 0 and 5 of each radio frame with a normal cyclic prefix, respectively, in symbol periods 6 and 5, as follows: Figure 3 As shown in the diagram. The PSS and SSS can be used by the UE for cell search and acquisition. The BS can transmit cell-specific reference signals (CRS) across the system bandwidth of each cell supported by the BS. The CRS can be transmitted in certain symbol periods of each subframe and can be used by the UE to perform channel estimation, channel quality measurement, and / or other functions. The BS can also transmit the Physical Broadcast Channel (PBCH) in symbol periods 0 to 3 of slot 1 in certain radio frames. The PBCH can carry some system information. The BS can transmit other system information in certain subframes, such as System Information Blocks (SIBs) on the Physical Downlink Shared Channel (PDSCH). The BS can transmit control information / data on the Physical Downlink Control Channel (PDCCH) for the first B symbol periods of a subframe, where B can be configurable for each subframe. The BS can transmit traffic data and / or other data on the PDSCH for the remaining symbol periods of each subframe.
[0055] In other systems (e.g., such NR or 5G systems), B nodes can transmit these or other signals at these locations or different locations within a subframe.
[0056] As indicated above, Figure 3 This is provided merely as an example. Other examples are possible and may differ from those provided. Figure 3 The example described.
[0057] Figure 4 Two example subframe formats, 410 and 420, with normal cyclic prefixes are shown. Available time-frequency resources can be divided into resource blocks. Each resource block can cover 12 subcarriers in a time slot and may include several resource elements. Each resource element can cover one subcarrier in one symbol period and can be used to transmit a modulation symbol that can be real or complex.
[0058] Subframe format 410 can be used with two antennas. The CRS can be transmitted from antennas 0 and 1 during symbol periods 0, 4, 7, and 11. The reference signal is a signal known a priori to both the transmitter and receiver and may also be referred to as a pilot. The CRS is a cell-specific reference signal, generated, for example, at least in part, based on the cell identity (ID). Figure 4 In this configuration, for a given resource element with a marker Ra, modulation symbols can be transmitted from antenna a on that resource element, and modulation symbols may not be transmitted from other antennas on that resource element. Subframe format 420 can be used with four antennas. CRS can be transmitted from antennas 0 and 1 in symbol periods 0, 4, 7, and 11, and from antennas 2 and 3 in symbol periods 1 and 8. For both subframe formats 410 and 420, CRS can be transmitted on uniformly spaced subcarriers, which can be determined at least in part based on the cell ID. Depending on its cell ID, CRS can be transmitted on the same or different subcarriers. For both subframe formats 410 and 420, resource elements not used for CRS can be used to transmit data (e.g., traffic data, control data, and / or other data).
[0059] The PSS, SSS, CRS, and PBCH in LTE are described in 3GPP TS 36.211, which is publicly available, entitled “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation”.
[0060] For FDD in some telecommunications systems (e.g., LTE), an interleaving structure can be used for both the downlink and uplink. For example, a Q-strand interleaving with indices 0 to Q–1 can be defined, where Q can be equal to 4, 6, 8, 10, or some other value. Each interleaving may include subframes spaced Q frames apart. Specifically, interleaving q may include subframes q, q+Q, q+2Q, etc., where q∈{0,…,Q–1}.
[0061] Wireless networks can support Hybrid Automatic Repeat Request (HARQ) for data transmission on both the downlink and uplink. For HARQ, a transmitter (e.g., a BS) can send one or more transmissions of a packet until the packet is correctly decoded by a receiver (e.g., a UE) or encounters some other termination condition. For synchronous HARQ, all transmissions of the packet can be sent in single-stranded subframes. For asynchronous HARQ, each transmission of the packet can be sent in any subframe.
[0062] The UE may be located within the coverage of multiple service base stations (BSs). One of these BSs can be selected to serve the UE. The serving BS can be selected, at least in part, based on various criteria such as received signal strength, received signal quality, path loss, etc. Received signal quality can be quantified by signal-to-noise ratio (SINR), reference signal received quality (RSRQ), or some other metric. The UE may operate in a strong interference scenario, in which the UE may observe severe interference from one or more interfering BSs.
[0063] While aspects of the examples described herein may be associated with LTE technology, aspects of this disclosure may be applied to other wireless communication systems, such as NR or 5G technology.
[0064] New Radio (NR) can refer to a radio configured to operate under a new air interface (e.g., different from an air interface based on Orthogonal Frequency Division Multiple Access (OFDMA)) or a fixed transport layer (e.g., different from Internet Protocol (IP)). In various respects, NR may utilize OFDM with CP (referred to herein as Cyclic Prefix OFDM or CP-OFDM) and / or SC-FDM on the uplink, and may utilize CP-OFDM on the downlink, including support for half-duplex operation using TDD. In various respects, NR may, for example, utilize OFDM with CP (referred to herein as CP-OFDM) and / or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) on the uplink, and may utilize CP-OFDM on the downlink, including support for half-duplex operation using TDD. NR may include enhanced mobile broadband (eMBB) services targeting wide bandwidth (e.g., 80 MHz or more), millimeter wave (mmW) services targeting high carrier frequencies (e.g., 60 GHz), massive MTC (mMTC) services targeting non-backward compatible MTC technologies, and / or mission-critical services targeting ultra-reliable low latency communication (URLLC) services.
[0065] It supports a single-component carrier bandwidth of 100MHz. An NR resource block can span 12 subcarriers with a subcarrier bandwidth of 75kHz over a duration of 0.1ms. Each radio frame can include 50 subframes with a length of 10ms. Therefore, each subframe can have a length of 0.2ms. Each subframe can indicate the link direction (e.g., DL or UL) for data transmission, and the link direction for each subframe can be dynamically switched. Each subframe can include DL / UL data and DL / UL control data. See below for further details. Figure 7 and 8 A more detailed description of the UL and DL subframes used for NR.
[0066] It supports beamforming and dynamically configurable beam direction. It also supports MIMO transmission with precoding. MIMO configuration in DL can support up to 8 transmit antennas (with up to 8 streams and up to 2 streams per UE for multi-layer DL transmission). Multi-layer transmission with up to 2 streams per UE is supported. Up to 8 serving cells can be used to support the aggregation of multiple cells. Alternatively, NR can support different air interfaces in addition to OFDM-based interfaces. NR networks can include entities such as central cells or distributed cells.
[0067] The RAN may include a Central Unit (CU) and a Distributed Unit (DU). An NR BS (e.g., gNB, 5G B-node, B-node, Transmitter Receiver Point (TRP), Access Point (AP)) may correspond to one or more BSs. NR cells may be configured as Access Cells (ACells) or Data Cells Only (DCells). For example, the RAN (e.g., a Central Unit or a Distributed Unit) may configure these cells. A DCell may be a cell used for carrier aggregation or dual connectivity but not for initial access, cell selection / reselection, or handover. In some cases, a DCell may not transmit synchronization signals—in some cases, a DCell may transmit SS. An NR BS may transmit downlink signals to the UE to indicate the cell type. The UE may communicate with the NR BS based at least in part on this cell type indication. For example, the UE may determine which NR BS to consider for cell selection, access, handover, and / or measurement based at least in part on the indicated cell type.
[0068] As indicated above, Figure 4 This is provided merely as an example. Other examples are possible and may differ from those provided. Figure 4 The example described.
[0069] Figure 5 An example logical architecture of a distributed RAN 500 according to various aspects of this disclosure is described. A 5G access node 506 may include an access node controller (ANC) 502. The ANC may be the central unit (CU) of the distributed RAN 500. A backhaul interface to the next-generation core network (NG-CN) 504 may terminate at the ANC. A backhaul interface to the adjacent next-generation access node (NG-AN) may terminate at the ANC. The ANC may include one or more TRPs 508 (which may also be referred to as a BS, NR BS, B-node, 5G NB, AP, gNB, or some other term). As mentioned above, TRPs can be used interchangeably with "cell".
[0070] TRP 508 can be a Distributed Unit (DU). A TRP can be connected to one ANC (ANC 502) or more ANCs (not described). For example, for RAN sharing, Radio as a Service (RaaS), and service-specific AND deployments, a TRP can be connected to more than one ANC. A TRP may include one or more antenna ports. A TRP can be configured to individually (e.g., dynamically selected) or jointly (e.g., jointly transmitted) serve traffic to the UE.
[0071] The RAN 500's local architecture can be used to interpret the fronthaul definition. This architecture can be defined as supporting fronthaul solutions across different deployment types. For example, the architecture can be based at least in part on transport network capabilities (e.g., bandwidth, latency, and / or jitter).
[0072] This architecture can share features and / or components with LTE. Depending on various aspects, the next-generation AN (NG-AN)510 can support dual connectivity with NR. NG-AN can share a common outgoing route for both LTE and NR.
[0073] This architecture enables collaboration between and within each TRP 508. For example, collaboration can be pre-configured within a TRP and / or across TRPs via ANC 502. Depending on the circumstances, inter-TRP interfaces may or may not be required.
[0074] Depending on various factors, the RAN 500 architecture allows for dynamic configuration of split logical functions. PDCP, RLC, and MAC protocols can be adaptively placed at the ANC or TRP.
[0075] Depending on certain aspects, a BS may include a central unit (CU) (e.g., ANC 502) and / or one or more distributed units (e.g., one or more TRP 508).
[0076] As indicated above, Figure 5 This is provided merely as an example. Other examples are possible and may differ from those provided. Figure 5 The example described.
[0077] Figure 6 An example physical architecture of the distributed RAN 600 according to various aspects of this disclosure is described. A centralized core network unit (C-CU) 602 can host core network functions. The C-CU can be deployed centrally. C-CU functionality can be offloaded (e.g., to Advanced Radio Services (AWS)) to attempt to handle peak capacity.
[0078] The Centralized RAN Unit (C-RU) 604 can store one or more ANC functions. Optionally, the C-RU can store core network functions locally. The C-RU can be deployed in a distributed manner. The C-RU can be located closer to the network edge.
[0079] The Distributed Unit (DU) 606 can store one or more TRPs. The DU can be located at the edge of a network with radio frequency (RF) functionality.
[0080] As indicated above, Figure 6 This is provided merely as an example. Other examples are possible and may differ from those provided. Figure 6 The example described.
[0081] Figure 7 Figure 700 illustrates an example of a DL-centered subframe or wireless communication structure. The DL-centered subframe may include a control portion 702. The control portion 702 may be present in the initial or beginning portion of the DL-centered subframe. The control portion 702 may include various scheduling and / or control information corresponding to different portions of the DL-centered subframe. In some configurations, the control portion 702 may be a physical DL control channel (PDCCH), such as... Figure 7 As indicated in the document.
[0082] The DL-centered subframe may also include a DL data portion 704. The DL data portion 704 may sometimes be referred to as the payload of the DL-centered subframe. The DL data portion 704 may include communication resources for conveying DL data from a scheduling entity (e.g., UE or BS) to a lower-level entity (e.g., UE). In some configurations, the DL data portion 704 may be a Physical DL Shared Channel (PDSCH).
[0083] The DL-centered subframe may also include a UL short burst portion 706. The UL short burst portion 706 may sometimes be referred to as a UL burst, UL burst portion, shared UL burst, short burst, UL short burst, shared UL short burst, shared UL short burst portion, and / or various other suitable terms. In some aspects, the UL short burst portion 706 may include one or more reference signals. Additionally or alternatively, the UL short burst portion 706 may include feedback information corresponding to various other portions of the DL-centered subframe. For example, the UL short burst portion 706 may include feedback information corresponding to the control portion 702 and / or the data portion 704. Non-limiting examples of information that may be included in the UL short burst section 706 include ACK signals (e.g., PUCCH ACK, PUSCH ACK, immediate ACK), NACK signals (e.g., PUCCH NACK, PUSCH NACK, immediate NACK), scheduling requests (SR), buffer status reports (BSR), HARQ indicators, channel state indicators (CSI), channel quality indicators (CQI), probe reference signals (SRS), demodulation reference signals (DMRS), PUSCH data, and / or various other suitable types of information. The UL short burst section 706 may include additional or alternative information, such as information relating to the random access channel (RACH) protocol, scheduling requests, and various other suitable types of information.
[0084] like Figure 7As explained herein, the end of the DL data portion 704 may be temporally separated from the beginning of the UL short burst portion 706. This time separation may sometimes be referred to as a gap, protection period, protection interval, and / or various other suitable terms. This interval provides time for switching from DL communication (e.g., reception operations performed by a subordinate entity (e.g., UE)) to UL communication (e.g., transmissions performed by a subordinate entity (e.g., UE)). The foregoing is merely one example of a DL-centric wireless communication architecture, and alternative architectures with similar characteristics may exist without departing from the aspects described herein.
[0085] As indicated above, Figure 7 This is provided merely as an example. Other examples are possible and may differ from those provided. Figure 7 The example described.
[0086] Figure 8 Figure 800 illustrates an example of a UL central subframe or wireless communication structure. The UL central subframe may include a control section 802. The control section 802 may be present in the initial or beginning portion of the UL central subframe. Figure 8 The control section 802 in the above reference can be similar to the one described above. Figure 7 The control section 702 is described. In some configurations, the control section 802 may be a physical DL control channel (PDCCH).
[0087] The UL-centered subframe may also include a UL long burst portion 804. The UL long burst portion 804 may sometimes be referred to as the payload of the UL-centered subframe. This UL portion may refer to the communication resources used to transmit UL data from a lower-level entity (e.g., UE) to a scheduling entity (e.g., UE or BS).
[0088] like Figure 8 As explained, the end of control section 802 may be time-separated from the start of UL long burst section 804. This time separation may sometimes be referred to as a gap, protection period, protection interval, and / or various other suitable terms. This interval provides time for switching from DL communication (e.g., a receiving operation performed by a scheduling entity) to UL communication (e.g., a transmission performed by a scheduling entity).
[0089] The UL-centered subframe may also include the UL short burst portion 806. Figure 8 The UL short burst portion 806 in the above reference can be similar to the above reference. Figure 7 The UL short burst portion 706 is described, and may include the above combination. Figure 7 Any information described herein. The foregoing is merely one example of a UL-centric wireless communication architecture, and alternative architectures with similar characteristics may exist without departing from the aspects described herein.
[0090] In some environments, two or more subordinate entities (e.g., UEs) may use sidelink signaling to communicate with each other. Real-world applications of such sidelink communication may include public safety, proximity services, UE-to-network relay, vehicle-to-vehicle (V2V) communication, Internet of Things (IoE) communication, IoT communication, mission-critical mesh networks, and / or various other suitable applications. Generally, sidelink signaling can refer to a signal that is relayed from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without requiring the relaying of that communication by a scheduling entity (e.g., UE or BS), even if the scheduling entity may be used for scheduling and / or control purposes. In some examples, sidelink signaling may use licensed spectrum (unlike wireless LANs, which typically use unlicensed spectrum).
[0091] In one example, a wireless communication structure (such as a frame) may include both UL-centered subframes and DL-centered subframes. In this example, the ratio of UL-centered to DL-centered subframes in a frame can be dynamically adjusted, at least in part, based on the amount of UL data and DL data transmitted. For example, if there is more UL data, the ratio of UL-centered to DL-centered subframes can be increased. Conversely, if there is more DL data, the ratio of UL-centered to DL-centered subframes can be decreased.
[0092] As indicated above, Figure 8 This is provided merely as an example. Other examples are possible and may differ from those provided. Figure 8 The example described.
[0093] In legacy LTE radio access technologies, the transmission of PUCCH and PUSCH communications within a given legacy TTI (e.g., a 1ms subframe) can depend on the UE's capabilities. For example, if the UE is capable of parallel transmission, it can concurrently transmit (e.g., using power splitting) both control communications on the PUCCH and data communications on the PUSCH. If the UE is not capable of parallel transmission, it can configure one or more uplink transmissions according to one or more rules. For example, if the UE has data to transmit, it can transmit uplink control information (UCI) on the PUSCH. If the UE does not have data to transmit, it can transmit UCI on the PUCCH.
[0094] In radio access technologies capable of using shortened TTIs (sTTIs), such as New Radio, there may be instances where combinations of PUSCH, PUCCH, sPUSCH, and / or sPUCCH communications need to be transmitted within the same time interval (e.g., subframes, time slots, and / or other types of wireless communication structures). Achieving parallel transmission in these scenarios is difficult due to the different lengths of the TTIs for PUSCH and / or PUCCH communications and the sTTIs for sPUSCH and / or sPUSCH communications. The techniques described herein facilitate the configuration of uplink communication transmissions when the UE identifies potential conflicts between scheduled TTI communications and scheduled sTTI communications. In some respects, the UE can prioritize sTTI communications compared to TTI communications due to the stricter turnaround times and stricter latency sensitivity.
[0095] Figure 9 This is a flowchart of wireless communication method 900. This method can be implemented by a UE (e.g., Figure 1 (UE 120, Equipment 1200 / 1200', etc.) to execute.
[0096] In 910, the UE can identify potential conflicts between scheduled legacy transport time interval (TTI) communications and scheduled shortened TTI (sTTI) communications, where the legacy TTI communication has a longer legacy TTI duration than the sTTI duration associated with the sTTI communication. For example, when legacy TTI communications and sTTI communications overlap in time, the UE can determine that the legacy TTI communication conflicts with the sTTI communication. In some aspects, the UE can receive permission for these communications, and this permission can indicate that the legacy TTI communication and the sTTI communication will be transmitted in the overlapping time period (e.g., the same time slot, subframe, etc.).
[0097] In some contexts, TTI communication can refer to communication with a duration of 1 millisecond, or the duration used in LTE. In other contexts, this can be referred to as legacy TTI communication. In some contexts, legacy TTI communication is Physical Uplink Control Channel (PUCCH) communication. In some contexts, legacy TTI communication is Physical Uplink Shared Channel (PUSCH) communication.
[0098] In some respects, sTTI communication can refer to communication with a duration of less than 1 millisecond, communication with a configurable length (e.g., 143 microseconds in some respects), etc. In some respects, sTTI communication can have a shorter duration than older TTI communication. In some respects, sTTI communication is shortened Physical Uplink Control Channel (sPUCCH) communication. In some respects, sTTI communication is shortened Physical Uplink Shared Channel (sPUSCH) communication. In some respects, sTTI communication includes both sPUCCH and sPUSCH communication.
[0099] In 920, the UE can determine whether legacy TTI communication should be transmitted within a threshold time. In some aspects, legacy TTI communication can be associated with a final deadline for preparing legacy TTI communication for transmission, and the UE can determine whether that final deadline has passed. In this case, the threshold time can be greater than zero (e.g., the amount of time between the final deadline for preparing legacy TTI communication for transmission and the actual transmission). Additionally or alternatively, the threshold time is equal to zero, which can indicate that transmission of legacy TTI communication has begun. As used herein, determining whether legacy TTI communication should be transmitted within the threshold time can refer to: determining whether transmission of legacy TTI communication has begun, determining whether the final deadline has passed before the start of transmission of legacy TTI communication, etc.
[0100] In some respects, the threshold time is determined at least in part based on one or more of the following: a timing advance value associated with the UE, the PUCCH format of TTI communication (e.g., the legacy PUCCH format), or some combination thereof.
[0101] At 930, the UE may transmit at least one of sTTI communication, legacy TTI communication, or any combination thereof, at least in part based on this determination. In some aspects, transmitting at least one of sTTI communication or legacy TTI communication includes transmitting sTTI communication multiplexed with uplink control information from legacy TTI communication, at least in part based on the determination that legacy TTI communication is not transmitted within a threshold time. In this way, the UE can prioritize latency-sensitive sTTI communication while also transmitting UCI from legacy TTI communication, thereby increasing throughput and reducing latency.
[0102] In some aspects, transmitting at least one of sTTI communication or legacy TTI communication includes transmitting sTTI communication multiplexed with at least a portion of the legacy TTI communication based at least in part on determining that the legacy TTI communication is not transmitted within a threshold time. In some aspects, a portion of the legacy TTI communication is determined based at least in part on one or more of the following: the length of the sTTI communication, the format of the sTTI communication when it is a shortened Physical Uplink Control Channel (sPUCCH) communication, or some combination thereof. In some aspects, if the sPUCCH is configured to be less than or equal to a threshold size (e.g., equal to two bits), the UE may multiplex only the ACK / NACK bits of the legacy TTI communication with the sPUCCH communication (and / or sPUSCH communication). In some aspects, if the sPUCCH is configured to be greater than or equal to a threshold size (e.g., equal to one time slot), the UE can multiplex ACK / NACK bits, and / or Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), and / or Rank Indicator (RI) with sPUCCH communication (and / or sPUSCH communication). In some aspects, transmitting at least one of sTTI communication or legacy TTI communication includes transmitting only sTTI communication (without transmitting legacy TTI communication) based at least in part on the determination that legacy TTI communication is not transmitted within a threshold time. For example, UCIs (such as PUCCH) from legacy TTI communication may not be piggybacked or multiplexed onto sTTI communication. In this way, the UE can prioritize sTTI communication while transmitting a portion of legacy TTI communication, thereby increasing throughput and reducing latency.
[0103] In some aspects, transmitting at least one of sTTI communication or legacy TTI communication includes transmitting legacy TTI communication and discarding sTTI communication based at least in part on determining that legacy TTI communication will be transmitted within a threshold time. In this way, the UE can save UE resources (e.g., processing resources, memory resources, etc.) by transmitting legacy TTI communication that has already been processed (e.g., to avoid reprocessing the legacy TTI communication at a later time).
[0104] In some aspects, legacy TTI communication is Physical Uplink Control Channel (PUCCH) communication. In some aspects, transmitting at least one of sTTI communication or legacy TTI communication includes: transmitting the PUCCH communication based at least in part on determining that the PUCCH communication will be transmitted within a threshold time and that the PUCCH communication has a first format, and then discarding the sTTI communication. In some aspects, the first format includes at least one of format 1, format 1a, format 1b, or format 3. In some cases, puncturing a subset of PUCCH symbols when the PUCCH is format 1, format 1a, format 1b, or format 3 may cause interference across different uplink transmissions due to loss of orthogonality. Furthermore, if PUCCH communication is in progress (e.g., according to a deadline), discarding the PUCCH communication may interfere with other transmissions multiplexed on the same resources as the PUCCH communication(s). Therefore, in this case, when the transmission of PUCCH communication has already begun (e.g., according to a deadline), the UE cannot puncture the PUCCH communication and can discard the sTTI communication, thereby reducing interference. In some aspects, transmitting at least one of sTTI communication or legacy TTI communication includes: at least in part based on determining that PUCCH communication needs to be transmitted within a threshold time and that the PUCCH communication has a first format for transmitting the sTTI communication, and discarding one or more overlapping symbols of the PUCCH communication (e.g., symbols overlapping with the sTTI communication) and the remainder of the PUCCH communication (e.g., portions for which there are insufficient resources to transmit). In this way, sTTI communication can be prioritized.
[0105] In some aspects, transmitting at least one of sTTI or legacy TTI communication includes: puncturing the PUCCH communication and transmitting the sTTI communication based at least in part on determining that the PUCCH communication is to be transmitted within a threshold time and that the PUCCH communication has a second format. In some aspects, the second format includes at least one of format 2, format 4, or format 5. When the PUCCH is format 2, format 4, or format 5, it may be possible to puncture a subset of PUCCH symbols without causing interference. However, resuming the transmission of PUCCH communication after interrupting PUCCH communication to transmit sTTI communication may be difficult. Therefore, in some aspects, the UE may puncture the PUCCH communication and may discard the remainder of the PUCCH communication (e.g., the portion of the PUCCH communication after the time the PUCCH communication was punctured). In some aspects, puncturing may refer to interrupting legacy TTI communication that has already begun in order to transmit sTTI communication. In this way, the UE can prioritize delay-sensitive sTTI communication. As described elsewhere in this document, in some respects, sTTI communication may be multiplexed with at least a portion of legacy TTI communication. For example, in some respects, sTTI communication may be multiplexed only with the ACK / NACK bits of legacy TTI communication. In some respects, sTTI communication may not be multiplexed with the ACK / NACK bits of legacy TTI communication. In some respects, other UCIs of legacy TTI communication (such as CQI, PMI, and / or RI) may be multiplexed with sTTI communication. In some respects, sTTI communication may not be multiplexed with other UCIs of legacy TTI communication.
[0106] In some aspects, legacy TTI communication is Physical Uplink Shared Channel (PUSCH) communication. In some aspects, transmitting at least one of sTTI communication or legacy TTI communication includes: puncturing the PUSCH communication and transmitting the sTTI communication based at least in part on determining that the PUSCH communication will be transmitted within a threshold time. In some aspects, the UE may discard the remainder of the PUSCH communication (e.g., the portion of the PUSCH communication after the puncturing time). In this way, the UE can prioritize latency-sensitive sTTI communication. In some aspects, a portion of the PUSCH communication (e.g., UCI piggybacked on the PUSCH) may be multiplexed with sTTI communication, thereby increasing throughput and reducing latency. In some aspects, a portion of legacy TTI communication is determined at least in part based on one or more of the following: the length of the sTTI communication, the format of the sTTI communication when the sTTI communication is a shortened Physical Uplink Control Channel (sPUCCH) communication, or some combination thereof, as described above.
[0107] In some aspects, sTTI communication includes both sPUCCH communication and sPUSCH communication. In some aspects, transmitting at least one of sTTI communication or legacy TTI communication includes transmitting both sPUCCH communication and sPUSCH communication in parallel, at least partially based on the determination that the UE is capable of transmitting parallel transmissions. In some aspects, transmitting at least one of sTTI communication or legacy TTI communication includes using sPUSCH communication to transmit uplink control information, at least partially based on the determination that the UE cannot transmit parallel transmissions and that the UE has data to transmit on sPUSCH. In this way, throughput can be increased and UCI transmissions can be prioritized.
[0108] In some respects, the UE is configured to limit the number of sTTI communication lengths supported on a carrier-aggregated PUCCH group. For example, the UE can be configured to support only one uplink sTTI length per PUCCH group (e.g., an sTTI with two symbol lengths, an sTTI with one slot length, etc.). In this way, the UE can perform power splitting across multiple concurrent uplink transmissions with different TTI lengths (e.g., legacy TTI lengths and a limited number of sTTI lengths (such as one sTTI length)). If more than a threshold number of sTTI lengths are supported, the UE may not be able to transmit concurrently on legacy TTIs and / or multiple sTTIs of different lengths, resulting in no information being transmitted. By limiting the number of supported sTTI lengths, the UE can ensure that sufficient power is available for concurrent transmission.
[0109] In some respects, for the reasons mentioned above, the UE is configured to limit the number of sTTI communication lengths supported by PUCCH groups aggregated across multiple carriers. In other respects, the UE is configured to split transmission power across PUCCH groups aggregated across multiple carriers for at least one of sTTI or legacy TTI communication. For example, if the UE supports different sTTI lengths across different PUCCH groups, the UE may employ a semi-static power splitting scheme. In this case, the UE may semi-statically configure the maximum transmission power for each PUCCH group. In some respects, transmission power is split to ensure that it does not exceed the UE's maximum transmission power. For example, the sum of the maximum transmission power across all PUCCH groups may be less than or equal to the UE's maximum transmission power. In this way, the UE can ensure that its maximum transmission power is not exceeded.
[0110] although Figure 9 An example box of a wireless communication method is shown, but in some aspects, the method may include more than Figure 9 The boxes shown may include more boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, Figure 9 Two or more boxes shown can be executed in parallel.
[0111] Figure 10 This is a flowchart of a wireless communication method 1000. This method can be implemented by a UE (e.g., Figure 1 (UE120, Equipment 1200 / 1200', etc.) to execute.
[0112] In 1005, the UE can generate transmissions on a shortened Physical Uplink Control Channel (sPUCCH) and / or a shortened Physical Uplink Shared Channel (sPUSCH). In some aspects, the transmissions may include Uplink Control Information (UCI). In other aspects, the transmissions may not include UCI.
[0113] At 1010, the UE can determine whether PUCCH communication should be transmitted within a threshold time. If PUCCH communication is not transmitted within the threshold time (1010—No), the UE can multiplex the UCI from the PUCCH communication with the sTTI communication (1015) and can transmit the multiplexed communication (1020). In some aspects, the sTTI communication may include a UCI (e.g., a UCI from sPUCCH communication and / or sPUSCH communication). In some aspects, the UE can transmit the multiplexed communication on sPUCCH and / or sPUSCH.
[0114] If PUCCH communication is to be transmitted within a threshold time (1010—Yes), the UE can determine the format of the PUCCH communication (1025). At 1030, if the format of the PUCCH communication is format 1, format 1a, format 1b, and / or format 3, the UE can discard sTTI communication (e.g., sPUCCH communication and / or sPUSCH communication).
[0115] At 1035, if the PUCCH communication format is format 2, format 4, and / or format 5, the UE can puncture the PUCCH communication using sTTI communication (e.g., sPUCCH communication and / or sPUSCH communication). Furthermore, at 1040, the UE can discard the remaining PUCCH communication (e.g., at a point in time after puncturing has occurred).
[0116] although Figure 10 An example box of a wireless communication method is shown, but in some aspects, the method may include more than Figure 10 The boxes shown may include more boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, Figure 10 Two or more boxes shown can be executed in parallel.
[0117] Figure 11 This is a flowchart of wireless communication method 1100. This method can be performed by a UE (e.g., Figure 1(UE120, Equipment 1200 / 1200', etc.) to execute.
[0118] In 1105, the UE can generate transmissions on a shortened Physical Uplink Control Channel (sPUCCH) and / or a shortened Physical Uplink Shared Channel (sPUSCH). In some aspects, the transmissions may include UCI. In some aspects, the transmissions may not include UCI.
[0119] At 1110, the UE can determine whether the PUSCH communication should be transmitted within a threshold time. If the PUSCH communication is not transmitted within the threshold time (1110—No), the UE can (e.g., if the PUSCH communication includes a UCI) multiplex the UCI from the PUSCH communication with the sTTI communication, or can (e.g., if the PUSCH communication does not include a UCI) discard the PUSCH communication (1115), and can transmit the multiplexed communication (1120). In some aspects, the sTTI communication may include a UCI (e.g., a UCI from the sPUCCH communication and / or the sPUSCH communication). In some aspects, the UE can transmit the multiplexed communication on the sPUCCH and / or the sPUSCH. In this way, the UE can (e.g., by multiplexing a portion of the PUSCH communication (such as a UCI) with the sTTI communication) prioritize the transmission of the sTTI communication while increasing throughput.
[0120] If the PUCCH communication is to be transmitted within a threshold time (1110—Yes), the UE can determine whether the transmission of the PUSCH communication has started (1125). At 1130, if the transmission of the PUSCH communication has not yet started and the final deadline for discarding the PUSCH communication has passed (e.g., the PUSCH communication is to be transmitted within a positive threshold time), the UE can discard the sTTI communication (e.g., sPUCCH communication and / or sPUSCH communication). In this way, the UE can save UE resources (e.g., processing resources, memory resources, etc.) by transmitting legacy TTI communication that has already been processed and / or has started transmission (e.g., to avoid reprocessing and / or retransmitting the legacy TTI communication at a later time).
[0121] At 1135, if PUCCH communication transmission has already begun, the UE can puncture PUSCH communication using sTTI communication (e.g., sPUCCH communication and / or sPUSCH communication). Furthermore, at 1140, the UE can discard the remaining PUSCH communication (e.g., at a point in time after puncturing has occurred). In this way, the UE can prioritize delay-sensitive sTTI communication.
[0122] although Figure 11An example box of a wireless communication method is shown, but in some aspects, the method may include more than Figure 11 The boxes shown may include more boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, Figure 11 Two or more boxes shown can be executed in parallel.
[0123] Figure 12 This is a conceptual data flow diagram 1200 illustrating the data flow between different modules / devices / components in example equipment 1202. Equipment 1202 may be a UE, such as one or more of the UEs described herein. In some aspects, equipment 1202 includes a receiving module 1204, an identification module 1206, a determination module 1208, and / or a transmission module 1210.
[0124] The receiving module 1204 may receive data 1212 from the eNB 1250, such as one or more uplink grants and / or downlink grants for legacy TTI communications and / or sTTI communications. The receiving module 1204 may provide such data as data 1214 to the identification module 1206. The identification module 1206 may identify potential conflicts between scheduled legacy TTI communications and scheduled sTTI communications, and may provide data 1216 regarding potential conflicts to the determination module 1208. The determination module 1208 may determine whether legacy TTI communications should be transmitted within a threshold time, and may provide data 1218 regarding this determination to the transmission module 1210. The transmission module 1210 may transmit at least one of sTTI communications, legacy TTI communications, or any combination thereof, as data 1220, based at least in part on data 1220.
[0125] The equipment may include execution Figure 9 , 10 And / or 11, additional modules for each block of the algorithm in the aforementioned flowchart. Thus, Figure 9 , 10 Each block in the aforementioned flowchart of 11 and / or 11 may be executed by a module, and the apparatus may include one or more of those modules. Each module may be one or more hardware components specifically configured to implement the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.
[0126] Figure 12 The number and arrangement of modules shown are provided as an example. In practice, there may be more... Figure 12 The modules shown can be more modules, fewer modules, different modules, or modules with different arrangements. Furthermore, Figure 12 The two or more modules shown can be implemented within a single module, or Figure 12 The single module shown can be implemented as multiple distributed modules. Additionally or alternatively, Figure 12 The set of modules shown (e.g., one or more modules) can perform actions described as being performed by... Figure 12 The other set of modules shown in the diagram performs one or more functions.
[0127] Figure 13 Figure 1300 illustrates an example of a hardware implementation of device 1202' employing processing system 1302. Device 1202' may be a UE, such as one or more UEs described elsewhere in this document.
[0128] Processing system 1302 can be implemented using a bus architecture generally represented by bus 1304. Depending on the specific application and overall design constraints of processing system 1302, bus 1304 may include any number of interconnect buses and bridges. Bus 1304 links various circuits together, including one or more processors and / or hardware modules (represented by processor 1306, module 1204, 1206, 1208, and / or 1210, and computer-readable medium / memory 1308). Bus 1304 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art and will therefore not be described further.
[0129] Processing system 1302 may be coupled to transceiver 1310. Transceiver 1310 is coupled to one or more antennas 1312. Transceiver 1310 provides means for communicating with various other devices via a transmission medium. Transceiver 1310 receives signals from one or more antennas 1312, extracts information from the received signals, and provides the extracted information to processing system 1302 (specifically, receiving module 1204). Additionally, transceiver 1310 receives information from processing system 1302 (specifically, transmission module 1210) and generates signals to be applied to one or more antennas 1312, at least in part, based on the received information. Processing system 1302 includes processor 1306 coupled to computer-readable medium / memory 1308. Processor 1306 is responsible for general processing, including the execution of software stored on computer-readable medium / memory 1308. When executed by processor 1306, the software causes processing system 1302 to perform the various functions described above for any particular apparatus. The computer-readable medium / memory 1308 may also be used to store data manipulated by the processor 1306 during software execution. The processing system further includes at least one module selected from modules 1204, 1206, 1208, and / or 1210. Each module may be a software module running in the processor 1306, a software module residing in / stored in the computer-readable medium / memory 1308, one or more hardware modules coupled to the processor 1306, or some combination thereof. The processing system 1302 may be a component of the UE 120 and may include memory 282 and / or at least one of the following: a TX MIMO processor 266, an RX processor 258, and / or a controller / processor 280.
[0130] In some aspects, the apparatus 1202 / 1202' for wireless communication includes means for identifying potential conflicts between scheduled legacy transmission time interval (TTI) communications and scheduled shortened TTI (sTTI) communications, means for determining whether legacy TTI communications should be transmitted within a threshold time, means for transmitting at least one of sTTI communications, legacy TTI communications, or any combination thereof, at least in part based on the determination, and so on. The aforementioned means may be one or more of the aforementioned modules of apparatus 1202 and / or processing systems 1302 in apparatus 1202' configured to perform the functions described by the aforementioned means. As described above, processing system 1302 may include TX MIMO processor 266, RX processor 258, and / or controller / processor 280. Thus, in one configuration, the aforementioned means may be TXMIMO processor 266, RX processor 258, and / or controller / processor 280 configured to perform the functions described by the aforementioned means.
[0131] Figure 13This is provided as an example. Other examples are possible and may differ from this combination. Figure 13 The example described.
[0132] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is an explanation of the exemplary method. Based on design preferences, it should be understood that the specific order or hierarchy of the boxes in these process / flowcharts can be rearranged. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of the various boxes in an exemplary order, and are not intended to be limited to the specific order or hierarchy presented.
[0133] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but should be granted the full scope consistent with the language of the claims, wherein references to the singular form of an element, unless specifically stated otherwise, are not intended to mean “one and only one,” but rather “one or more.” The term “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as superior to or overriding other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “at least one of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C," "at least one of A, B, and C," and "A, B, C, or any combination thereof" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. Elements of all aspects described throughout this disclosure that are presently or hereafter known to those skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly stated in the claims. No claim element should be construed as means plus function unless the element is explicitly stated using the phrase "means for...".
Claims
1. A wireless communication method, comprising: The user equipment (UE) receives permission for scheduled Transmission Time Interval (TTI) communication and scheduled Shortened Transmission Time Interval (sTTI) communication, wherein the TTI communication has a longer TTI duration than the sTTI duration associated with the sTTI communication. The UE identifies potential conflicts between the TTI communication and the sTTI communication based on the permission granted. The UE determines whether the TTI communication should be transmitted within a threshold time, the threshold time being equal to or less than the amount of time between the final deadline for preparing the TTI communication for transmission and the actual transmission of the TTI communication; as well as The UE transmits the sTTI communication or at least one of the TTI communications based at least in part on the determination.
2. The method as described in claim 1, wherein, Transmitting the sTTI communication or at least one of the TTI communications includes: transmitting the sTTI communication multiplexed with uplink control information from the TTI communication based at least in part on determining that the TTI communication is not transmitted within the threshold time.
3. The method as described in claim 1, wherein, Transmitting the sTTI communication or at least one of the TTI communications includes: transmitting the sTTI communication multiplexed with at least a portion of the TTI communication based at least in part on determining that the TTI communication is not transmitted within the threshold time.
4. The method of claim 3, wherein, The portion of the TTI communication is determined based, at least in part, on one or more of the following: The length of the STTI communication, The format of the sTTI communication when the sTTI communication is a shortened physical uplink control channel (sPUCCH) communication, or A certain combination of them.
5. The method of claim 1, wherein, The threshold time is determined based at least in part on one or more of the following: The timing advance value associated with the UE, The physical uplink control channel (PUCCH) format of the TTI communication, or A certain combination of them.
6. The method of claim 1, wherein, Transmitting the sTTI communication or at least one of the TTI communications includes: transmitting the TTI communication at least in part based on determining that the TTI communication is to be transmitted within the threshold time and discarding the sTTI communication.
7. The method of claim 1, wherein, The TTI communication is the Physical Uplink Control Channel (PUCCH) communication. and Transmitting at least one of the sTTI communication or the TTI communication includes: transmitting the PUCCH communication at least in part based on determining that the PUCCH communication is to be transmitted within the threshold time and that the PUCCH communication has a first format, and discarding the sTTI communication.
8. The method of claim 7, wherein, The first format includes at least one of the following: Format 1, Format 1a, Format 1b, or Format 3.
9. The method of claim 1, wherein, The TTI communication is the Physical Uplink Control Channel (PUCCH) communication. and Transmitting the sTTI communication or at least one of the TTI communications includes: transmitting the sTTI communication at least in part based on determining that the PUCCH communication is to be transmitted within the threshold time and that the PUCCH communication has a first format, and discarding one or more overlapping symbols of the PUCCH communication and the remainder of the PUCCH communication.
10. The method of claim 1, wherein, The TTI communication is the Physical Uplink Control Channel (PUCCH) communication. and Transmitting the sTTI communication or at least one of the TTI communications includes: at least in part based on determining that the PUCCH communication is to be transmitted within the threshold time and that the PUCCH communication has a second format to puncture the PUCCH communication and transmit the sTTI communication.
11. The method of claim 10, wherein, The second format includes at least one of the following: Format 2 Format 4, or Format 5.
12. The method of claim 10, further comprising discarding the remainder of the PUCCH communication.
13. The method of claim 1, wherein, The TTI communication is Physical Uplink Shared Channel (PUSCH) communication; and Transmitting the sTTI communication or at least one of the TTI communications includes: puncturing the PUSCH communication and transmitting the sTTI communication based at least in part on determining that the PUSCH communication is to be transmitted within the threshold time.
14. The method of claim 13, further comprising discarding the remainder of the PUSCH communication.
15. The method of claim 1, wherein, The STTI communication includes at least one of the following: Communication via the shortened physical uplink control channel sPUCCH. Communication via the shortened physical uplink shared channel sPUSCH, or A certain combination of them.
16. The method of claim 1, wherein, The sTTI communication includes both the shortened physical uplink control channel sPUCCH communication and the shortened physical uplink shared channel sPUSCH communication.
17. The method of claim 16, wherein, Transmitting the sTTI communication or at least one of the TTI communications includes: transmitting both the sPUCCH communication and the sPUSCH communication in parallel, at least in part based on determining that the UE is capable of transmitting parallel transmissions.
18. The method of claim 16, wherein, Transmitting at least one of the sTTI communications or the TTI communications includes: using the sPUSCH communications to transmit uplink control information based at least in part on the determination that the UE cannot transmit parallel transmissions and that the UE has data to transmit on the sPUSCH.
19. The method of claim 16, wherein, Transmitting at least one of the sTTI communications or the TTI communications includes: using the sPUCCH communications to transmit uplink control information based at least in part on the determination that the UE cannot transmit parallel transmissions and that the UE does not have data to transmit on the sPUSCH.
20. The method of claim 1, wherein, The threshold time indicates whether the TTI communication transmission has started.
21. The method of claim 1, wherein, The UE is configured to limit the number of lengths of the sTTI communications supported on at least one of the following: Carrier aggregation physical uplink control channel (PUCCH) group Multiple carriers clustered into a PUCCH group, or A certain combination of them.
22. The method of claim 1, wherein, The UE is configured to aggregate Physical Uplink Control Channel (PUCCH) group split transmission power across multiple carriers for transmitting at least one of the sTTI communications or the TTI communications.
23. An apparatus for wireless communication, comprising: Memory; as well as At least one processor, said at least one processor being coupled to the memory and configured to: Receive permission for scheduled Transmission Time Interval (TTI) communication and scheduled Shortened Transmission Time Interval (sTTI) communication, wherein the TTI communication has a longer TTI duration than the sTTI duration associated with the sTTI communication; Based on the permission, potential conflicts between the TTI communication and the sTTI communication are identified; Determine whether the TTI communication should be transmitted within a threshold time, the threshold time being equal to or less than the amount of time between the final deadline for preparing the TTI communication for transmission and the actual transmission of the TTI communication; as well as The sTTI communication or at least one of the TTI communications is transmitted based at least in part on the determination.
24. The apparatus of claim 23, wherein, The at least one processor is configured, when transmitting the sTTI communication or at least one of the TTI communications, to transmit the sTTI communication multiplexed with uplink control information from the TTI communication, based at least in part on the determination that the TTI communication is not transmitted within the threshold time.
25. The apparatus of claim 23, wherein, The at least one processor is configured, when transmitting the sTTI communication or at least one of the TTI communications, to transmit the sTTI communication multiplexed with at least a portion of the TTI communication based at least in part on the determination that the TTI communication is not transmitted within the threshold time.
26. The apparatus of claim 25, wherein, The portion of the TTI communication is determined based, at least in part, on one or more of the following: The length of the STTI communication, The format of the sTTI communication when the sTTI communication is a shortened physical uplink control channel (sPUCCH) communication, or A certain combination of them.
27. The apparatus of claim 23, wherein, The threshold time is determined based at least in part on one or more of the following: The timing advance value associated with the device, The physical uplink control channel (PUCCH) format of the TTI communication, or A certain combination of them.
28. The apparatus of claim 23, wherein, The at least one processor is configured, when transmitting the sTTI communication or at least one of the TTI communications, to transmit the TTI communication and discard the sTTI communication, based at least in part on the determination that the TTI communication is to be transmitted within the threshold time.
29. The apparatus of claim 23, wherein, The TTI communication is the Physical Uplink Control Channel (PUCCH) communication. and Transmitting at least one of the sTTI communication or the TTI communication includes: transmitting the PUCCH communication at least in part based on determining that the PUCCH communication is to be transmitted within the threshold time and that the PUCCH communication has a first format, and discarding the sTTI communication.
30. The apparatus of claim 29, wherein, The first format includes at least one of the following: Format 1, Format 1a, Format 1b, or Format 3.
31. The apparatus of claim 23, wherein, The TTI communication is the Physical Uplink Control Channel (PUCCH) communication. and Transmitting the sTTI communication or at least one of the TTI communications includes: transmitting the sTTI communication at least in part based on determining that the PUCCH communication is to be transmitted within the threshold time and that the PUCCH communication has a first format, and discarding one or more overlapping symbols of the PUCCH communication and the remainder of the PUCCH communication.
32. The apparatus of claim 23, wherein, The TTI communication is the Physical Uplink Control Channel (PUCCH) communication. and Transmitting the sTTI communication or at least one of the TTI communications includes: at least in part based on determining that the PUCCH communication is to be transmitted within the threshold time and that the PUCCH communication has a second format to puncture the PUCCH communication and transmit the sTTI communication.
33. The apparatus of claim 32, wherein, The second format includes at least one of the following: Format 2 Format 4, or Format 5.
34. The apparatus of claim 32, wherein, The at least one processor is further configured to discard the remainder of the PUCCH communication.
35. The apparatus of claim 23, wherein, The TTI communication is Physical Uplink Shared Channel (PUSCH) communication; and Transmitting the sTTI communication or at least one of the TTI communications includes: puncturing the PUSCH communication and transmitting the sTTI communication based at least in part on determining that the PUSCH communication is to be transmitted within the threshold time.
36. The apparatus of claim 35, wherein, The at least one processor is further configured to discard the remainder of the PUSCH communication.
37. The apparatus of claim 23, wherein, The STTI communication includes at least one of the following: Communication via the shortened physical uplink control channel sPUCCH. Communication via the shortened physical uplink shared channel sPUSCH, or A certain combination of them.
38. The apparatus of claim 23, wherein, The sTTI communication includes both the shortened physical uplink control channel sPUCCH communication and the shortened physical uplink shared channel sPUSCH communication.
39. The apparatus of claim 38, wherein, Transmitting the sTTI communication or at least one of the TTI communications includes: transmitting both the sPUCCH communication and the sPUSCH communication in parallel, at least in part based on determining that the device is capable of transmitting parallel transmissions.
40. The apparatus of claim 38, wherein, Transmitting the sTTI communication or at least one of the TTI communications includes: using the sPUSCH communication to transmit uplink control information based at least in part on the determination that the device cannot transmit parallel transmissions and that the device has data to be transmitted on the sPUSCH.
41. The apparatus of claim 38, wherein, Transmitting the sTTI communication or at least one of the TTI communications includes: using the sPUCCH communication to transmit uplink control information based at least in part on the determination that the device cannot transmit parallel transmissions and that the device does not have data to transmit on the sPUSCH.
42. The apparatus of claim 23, wherein, The threshold time indicates whether the TTI communication transmission has started.
43. The apparatus of claim 23, wherein, The device is configured to limit the number of lengths of the sTTI communications supported on at least one of the following: Carrier aggregation physical uplink control channel (PUCCH) group Multiple carriers clustered into a PUCCH group, or A certain combination of them.
44. The apparatus of claim 23, wherein, The device is configured to aggregate Physical Uplink Control Channel (PUCCH) group split transmission power across multiple carriers for transmitting at least one of the sTTI communications or the TTI communications.
45. An apparatus for wireless communication, comprising: A means for receiving permission for scheduled Transmission Time Interval (TTI) communication and scheduled Shortened Transmission Time Interval (sTTI) communication, wherein the TTI communication has a longer TTI duration than the sTTI duration associated with the sTTI communication. A means for identifying potential conflicts between the TTI communication and the sTTI communication based on the permission granted; A means for determining whether the TTI communication should be transmitted within a threshold time, the threshold time being equal to or less than the amount of time between the final deadline for preparing the TTI communication for transmission and the actual transmission of the TTI communication; as well as A means for transmitting the sTTI communication or at least one of the TTI communications based at least in part on the determination.
46. A non-transient computer-readable medium storing computer-executable code for wireless communication, comprising code for: Receive permission for scheduled Transmission Time Interval (TTI) communication and scheduled Shortened Transmission Time Interval (sTTI) communication, wherein the TTI communication has a longer TTI duration than the sTTI duration associated with the sTTI communication; Based on the permission, potential conflicts between the TTI communication and the sTTI communication are identified; Determine whether the TTI communication should be transmitted within a threshold time, the threshold time being equal to or less than the amount of time between the final deadline for preparing the TTI communication for transmission and the actual transmission of the TTI communication; as well as The sTTI communication or at least one of the TTI communications is transmitted based at least in part on the determination.
Citation Information
Patent Citations
Management of dynamic transmission time interval scheduling for low latency communications
US20160295584A1
Method for reducing transmission resource of control channel in short TTI, and device using same
WO2016143968A1