Time domain window determination for wireless communication

Abstract

This disclosure relates to techniques for performing wireless communications, including determining an actual time window for maintaining power consistency and / or phase continuity associated with transmissions between a user equipment (UE) and a base station. Techniques for determining the length, start, and end of such a window are disclosed. Various rules can be used by the UE and / or base station to determine the window.

Description

Technical Field

[0001] This application relates to wireless communication, including determining a time-domain window for transmission while maintaining power consistency and / or phase continuity.

[0002] Related technical descriptions

[0003] The use of wireless communication systems is growing rapidly. Furthermore, wireless communication technology has evolved from solely voice communication to also include the transmission of data such as the internet and multimedia content.

[0004] Mobile electronic devices can take the form of smartphones or tablets that users typically carry. Wearable devices (also known as accessory devices) are a newer form of mobile electronic device, an example being a smartwatch. Additionally, low-cost, low-complexity wireless devices designed for static or dynamic deployment are rapidly increasing as part of the development of the “Internet of Things”. In other words, the required devices are becoming increasingly diverse in terms of complexity, capabilities, traffic patterns, and other characteristics. Generally, there is a desire to recognize and provide improved support for a wide range of desired wireless communication characteristics. One characteristic might be transmitting over a time period (e.g., multiple time slots, symbols, and / or milliseconds) while maintaining power consistency and / or phase continuity, for example, to facilitate channel estimation. Improvements in this field are expected. Summary of the Invention

[0005] This document presents implementation schemes of systems, apparatuses, and methods, particularly for performing packet filtering and related communications in wireless communication systems (e.g., New Radio (NR), LTE, etc.).

[0006] As mentioned above, there is a growing number of use cases for communicating with different types of user equipment (UE) devices with a wide range of capabilities and usage expectations on wireless networks. One usage expectation may include maintaining power consistency and / or phase continuity of one or more transmissions. Devices may exchange configuration information and determine appropriate time windows to maintain such transmission characteristics.

[0007] In some implementations, a user equipment (UE) may establish communication with a base station and transmit a capability report to that base station, the capability report including an indication of the maximum duration for which the UE can transmit with power consistency and / or phase continuity. The UE may receive from the base station a schedule of uplink and / or downlink transmissions within a first time period, the schedule including a first uplink transmission opportunity. The UE may determine multiple actual time-domain windows for performing uplink transmissions with power consistency and / or phase continuity during the first time period. The first uplink transmission opportunity may be subdivided into at least a first actual time-domain window and a second actual time-domain window. Multiple actual time-domain windows may be determined according to multiple rules used to determine the actual time-domain windows. These rules may include: determining a separate preliminary time-domain window if an uplink transmission opportunity is interrupted by a downlink transmission opportunity; determining a separate preliminary time-domain window if the length of a previous preliminary time-domain window is greater than the maximum duration; and adjusting any previous preliminary time-domain windows affected by an event that modifies the schedule of uplink and / or downlink transmissions within the first time period. The UE can transmit information to the base station during multiple real time-domain windows, wherein power consistency and / or phase continuity are maintained during the respective real time-domain windows.

[0008] In some implementations, the method at the base station may include establishing communication with the user equipment (UE) and receiving a capability report from the UE, the capability report including an indication of the maximum duration for which the UE is capable of transmitting with power consistency and / or phase continuity. The method may also include transmitting a schedule of uplink transmission opportunities to the UE within a first time period and determining multiple actual time-domain windows for receiving uplink transmissions with power consistency and / or phase continuity during the first time period, wherein at least one uplink transmission opportunity is separated into two or more actual time-domain windows according to multiple rules used to determine the actual time-domain windows. The multiple rules may include one or more of the following: determining a separate preliminary time-domain window when an uplink transmission opportunity is interrupted by a downlink transmission opportunity; determining a separate preliminary time-domain window when the length of a previous preliminary time-domain window is greater than the maximum duration; and / or determining whether an event modifies the schedule of uplink transmission opportunities within the first time period, and if the event modifies the schedule of uplink transmission opportunities within the first time period, adjusting the previous preliminary time-domain window affected by the event. The method may also include receiving information from the UE during an uplink transmission opportunity period in a first time period, wherein power consistency and / or phase continuity are maintained during the respective real time window periods of multiple real time windows.

[0009] In some embodiments, the apparatus may include a processor configured to enable the UE to establish communication with a base station and transmit to the base station an indication of the maximum duration for which the UE can transmit with power consistency and / or phase continuity. The UE may determine a schedule of uplink and / or downlink transmission opportunities within a first time period based at least in part on information received from the base station. The UE may determine one or more actual time-domain windows for uplink transmission, wherein at least one of the one or more actual time-domain windows for uplink transmission is shorter than the corresponding uplink opportunity in the schedule of uplink and / or downlink transmission opportunities. This determination may be based on one or more of the following: applying a configuration length L to divide the first time period into lengths not longer than L; determining that the uplink transmission opportunities in the schedule are separated from the downlink transmission opportunities; or determining that the length of the uplink transmission opportunity or the previously preliminary time-domain window is greater than the maximum duration. The UE may transmit information and reference signals to the base station during one or more actual time-domain windows, wherein power consistency and / or phase continuity are maintained during each corresponding actual time-domain window of the one or more actual time-domain windows.

[0010] The technologies described herein can be implemented in and / or used with a variety of different types of devices, including but not limited to mobile phones or smartphones (e.g., iPhones). TM Based on Android TM Phones), tablets (e.g., iPads) TM Samsung Galaxy TM ), portable gaming devices (e.g., Nintendo DS) TM PlayStation Portable TM Gameboy Advance TM iPhone TM Any of the following: wearable devices (e.g., smartwatches, smart glasses), laptops, PDAs, portable internet devices, music players, data storage devices, other handheld devices, vehicles, automobiles, unmanned aerial vehicles (e.g., drones) and unmanned flight controllers, other cellular network infrastructure equipment, servers, and various other computing devices.

[0011] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0012] A better understanding of the subject matter can be obtained by considering the following specific description of the implementation scheme in conjunction with the accompanying drawings.

[0013] Figure 1 An exemplary wireless communication system including accessory devices according to some embodiments is shown;

[0014] Figure 2 An exemplary wireless communication system is shown, according to some embodiments, in which two wireless devices are capable of performing direct device-to-device communication;

[0015] Figure 3 This is a block diagram illustrating an example wireless device according to some implementation schemes;

[0016] Figure 4 This is a block diagram illustrating an exemplary base station according to some implementation schemes;

[0017] Figure 5 This is a communication flowchart illustrating an exemplary method for determining a time-domain window according to some implementation schemes; and

[0018] Figures 6 to 13 The various aspects of determining the time-domain window according to some implementation schemes are shown.

[0019] While the features described herein are susceptible to various modifications and alternatives, specific embodiments thereof are illustrated by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit this document to the specific forms disclosed, but rather are intended to cover all modifications, equivalents, and alternatives falling within the substance and scope of the subject matter as defined by the appended claims. Detailed Implementation

[0020] Acronyms and Abbreviations

[0021] The following acronyms and abbreviations are used in this disclosure:

[0022] 3GPP: Third Generation Partnership Project

[0023] 3GPP2: Third Generation Partnership Project 2

[0024] GSM: Global System for Mobile Communications

[0025] UMTS: Universal Mobile Telecommunication System

[0026] LTE: Long Term Evolution

[0027] RRC: Radio Resource Control

[0028] MAC: Media Access Control

[0029] CE: Control Element

[0030] Tx: Transmit (or transmit)

[0031] Rx: Accept (or receive)

[0032] RS: Reference signal

[0033] CSI: Channel State Information

[0034] PDCP: Packet Data Convergence Protocol

[0035] RLC: Radio Link Control

[0036] the term

[0037] The following are definitions of the terms used in this disclosure:

[0038] Memory media—any device of any type of nontransitory memory device or storage device. The term "memory media" is intended to include mounting media such as CD-ROMs, floppy disks, or magnetic tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, e.g., hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. Memory media may also include other types of nontransitory memory or combinations thereof. Furthermore, memory media may reside in a first computer system executing a program, or may reside in a different second computer system connected to the first computer system via a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "memory media" may include two or more memory media that may reside in different locations on different computer systems, for example, connected via a network. Memory media may store program instructions (e.g., representing a computer program) that can be executed by one or more processors.

[0039] Carrier medium—the memory medium as described above, and physical transmission medium, such as buses, networks and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals or digital signals).

[0040] Programmable hardware elements—including a variety of hardware devices comprising multiple programmable functional blocks connected via programmable interconnects. Examples include FPGAs (Field-Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field-Programmable Object Arrays), and CPLDs (Complex PLDs). Programmable functional blocks can vary from fine-grained (combinatorial logic units or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as “configurable logic units.”

[0041] Computer system—any of all types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, networked appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations thereof. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0042] User equipment (UE) (or “UE device”) — any of various types of computer systems or devices that are mobile or portable and perform wireless communication. Examples of UE devices include mobile phones or smartphones (e.g., iPhone). TM Based on Android TM Phones), tablets (e.g., iPads) TM Samsung Galaxy TM ), portable gaming devices (e.g., Nintendo DS) TM PlayStation Portable TM Gameboy Advance TM iPhone TM Wearable devices (e.g., smartwatches, smart glasses), laptops, PDAs, portable internet devices, music players, data storage devices, other handheld devices, vehicles, automobiles, unmanned aerial vehicles (e.g., drones), and unmanned flight controllers, etc. Generally speaking, the term "UE" or "UE device" can be broadly defined as any electronic device, computing device, and / or telecommunications device (or a combination of these devices) that is easily transportable by the user and capable of wireless communication.

[0043] A wireless device is any of various types of computer systems or devices that perform wireless communication. A wireless device can be portable (or mobile), or it can be stationary or fixed in a location. A UE is an example of a wireless device.

[0044] A communication device is any of various types of computer systems or devices that perform communication, which may be wired or wireless. A communication device may be portable (or mobile), or it may be stationary or fixed in a location. A wireless device is one example of a communication device. A UE is another example of a communication device.

[0045] Base station—The term “base station” has the full range of its common meaning and includes at least a wireless communication station that is installed in a fixed location and used for communication as part of a wireless communication system.

[0046] Link budget constrained—encompassing the full range of its general meaning, and at least including the characteristics of a wireless device (e.g., a UE) that exhibits limited communication capabilities or limited power relative to devices that are not link budget constrained or relative to devices for which a Radio Access Technology (RAT) standard has been developed. Link budget constrained wireless devices may suffer from relatively limited receiving and / or transmitting capabilities, which may be due to one or more factors such as device design, device size, battery size, antenna size or design, transmit power, receive power, current transmission medium conditions, and / or other factors. Such devices may be referred to herein as “link budget constrained” (or “link budget limited”) devices. Devices may be inherently link budget constrained due to their size, battery power, and / or transmit / receive power. For example, a smartwatch communicating with a base station via LTE or LTE-A may be inherently link budget constrained due to its reduced transmit / receive power and / or reduced antenna. Wearable devices such as smartwatches are generally link budget constrained devices. Alternatively, the device may not be inherently link budget limited, for example, it may have sufficient size, battery power, and / or transmit / receive power for normal communication via LTE or LTE-A, but may be temporarily link budget limited due to current communication conditions, such as a smartphone at the cell edge. It should be noted that the term "link budget limited" includes or encompasses power limitations, and therefore a link-limited device can be considered a link budget-limited device.

[0047] A processing element (or processor) is a component or combination of components capable of performing the functions of a device (such as a user equipment device or a cellular network device). A processing element may include, for example: a processor and associated memory, portions or circuitry of individual processor cores, an entire processor core, a single processor, a processor array, circuitry such as an ASIC (Application-Specific Integrated Circuit), programmable hardware components such as a Field-Programmable Gate Array (FPGA), and any combination thereof.

[0048] Automatic—means an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuits, programmable hardware elements, ASICs, etc.) without requiring direct user input to specify or perform that action or operation. Therefore, the term "automatically" is the opposite of an operation performed or specified manually by a user, where the user provides input to directly perform the operation. An automatic process can be initiated by user-provided input, but the subsequent actions performed "automatically" are not specified by the user; that is, they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input specifying information (e.g., by typing information, selecting a checkbox, radio selection, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user's actions. The form can be automatically filled out by a computer system (e.g., software executed on the computer system) which analyzes the fields of the form and fills it out without any user input specifying answers for the fields. As indicated above, the user can invoke the automatic filling of the form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that are automatically performed in response to actions taken by the user.

[0049] "Configured as"—Various components can be described as being "configured as" to perform one or more tasks. In such contexts, "configured as" is a broad expression generally meaning "having" a "structure" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured as" can also be a broad expression generally meaning a structure that "has" a "circuit" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently powered on. Typically, the circuit forming the structure corresponding to "configured as" can include hardware circuitry.

[0050] For ease of description, various components may be described as performing one or more tasks. Such descriptions shall be interpreted as including the phrase “configured to”. The statement that a component is configured to perform one or more tasks is expressly intended not to invoke the interpretation of paragraph 6 of section 112 of title 35 of the United States Code.

[0051] Figures 1-2 —Wireless communication system

[0052] Figure 1 An example of a wireless cellular communication system is illustrated. It should be noted that... Figure 1This represents one of many possibilities, and the features of this disclosure can be implemented in any of various systems as needed. For example, the embodiments described herein can be implemented in any type of wireless device.

[0053] As shown in the figure, an exemplary wireless communication system includes a cellular base station 102 that communicates with one or more wireless devices 106A, 106B, etc., and an accessory device 107 via a transmission medium. Wireless devices 106A, 106B, and 107 may be user equipment, which may be referred to herein as "user equipment" (UE) or UE device.

[0054] Base station 102 may be a transceiver base station (BTS) or a cell site and may include hardware and / or software to enable wireless communication with UE device 106A, UE device 106B, and UE device 107. If base station 102 is implemented in an LTE environment, it may be referred to as an "eNodeB" or "eNB". If base station 102 is implemented in a 5G NR environment, it may alternatively be referred to as a "gNodeB" or "gNB". Base station 102 may also be equipped to communicate with network 100 (e.g., the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN), and / or the Internet, and various other possible networks). Therefore, base station 102 facilitates communication between UE device 106 and UE device 107 and / or communication between UE device 106 / 107 and network 100. Also as used herein, in relation to the UE, a base station may sometimes be considered to represent the network, taking into account both uplink (UL) and downlink (DL) communication of the UE. Therefore, a UE that communicates with one or more base stations in the network can also be understood as a UE that communicates with the network.

[0055] In other specific implementations, base station 102 may be configured to provide communication via one or more other wireless technologies, such as an access point that supports one or more WLAN protocols (such as 802.11a, b, g, n, ac, ad and / or ax, or LTE in an unlicensed frequency band (LAA)).

[0056] The communication area (or coverage area) of base station 102 may be referred to as a "cell". Base station 102 and UE 106 / 107 may be configured to communicate using any of the following technologies via a transmission medium: Radio Access Technology (RAT), LTE, Advanced LTE (LTE-A), NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), Wi-Fi, etc.

[0057] Therefore, base station 102 and other similar base stations (not shown) operating according to one or more cellular communication technologies can be provided as a cell network that can provide continuous or near-continuous overlapping services to UE devices 106A-N and UE devices 107 and similar devices within a geographical area via one or more cellular communication technologies.

[0058] It should be noted that, at least in some cases, UE devices 106 / 107 may be able to communicate using any of a variety of wireless communication technologies. For example, UE devices 106 / 107 may be configured to communicate using one or more of the following: GSM, UMTS, CDMA2000, LTE, LTE-A, NR, WLAN, Bluetooth, one or more Global Navigation Satellite Systems (GNSS, such as GPS or GLONASS), one and / or more mobile television broadcasting standards (e.g., ATSC-M / H). Other combinations of wireless communication technologies (including more than two wireless communication technologies) are also possible. Similarly, in some cases, UE devices 106 / 107 may be configured to communicate using only a single wireless communication technology.

[0059] UE 106A and UE 106B may include handheld devices such as smartphones or tablets, and / or may include any of a variety of devices with cellular communication capabilities. For example, one or more of UE 106A and UE 106B may be wireless devices designed for static or dynamic deployment, such as home appliances, measuring devices, control devices, etc. UE 106B may be configured to communicate with UE device 107, which may be referred to as accessory device 107. Accessory device 107 may be any of a variety of wireless devices, typically a wearable device with a small form factor and limited battery, output power, and / or communication capabilities relative to UE 106. As a common example, UE 106B may be a smartphone carried by a user, and accessory device 107 may be a smartwatch worn by the same user. UE 106B and accessory device 107 may communicate using any of a variety of short-range communication protocols such as Bluetooth or Wi-Fi. In some cases, UE106B and accessory device 107 may utilize ProSe technology, for example, in a manner supported by a cellular base station, to perform direct peer-to-peer communication. For instance, such ProSe communication may be performed as part of a relay link to support a radio resource control connection between accessory device 107 and BS 102, as described in the various embodiments herein.

[0060] UE 106B can also be configured to communicate with UE 106A. For example, UE 106A and UE 106B may be able to perform direct device-to-device (D2D) communication. D2D communication may be supported by cellular base station 102 (e.g., easily discovered by BS 102, and with various possible forms of assistance), or may be performed in ways not supported by BS 102. For example, it is possible that UE 106A and UE 106B can deploy and perform D2D communication (e.g., including discovery communication) even when BS 102 and other cellular base stations have no coverage.

[0061] The BS 102 can control one or more Transmit and Receive Points (TRPs) and can use the TRPs to communicate with the UE. The TRPs can be arranged alongside the BS and / or located in separate physical locations.

[0062] Figure 2 An exemplary BS 102 is shown communicating with UE device 106, which in turn communicates with accessory device 107. UE device 106 and accessory device 107 can be any of a mobile phone, tablet or any other type of handheld device, smartwatch or other wearable device, media player, computer, laptop, unmanned aerial vehicle (UAV), unmanned flight controller, vehicle, or virtually any type of wireless device. In some embodiments, the accessory device may be a wireless device designed to have low cost and / or low power consumption and may support communication with BS 102 thanks to a relay link with UE device 106 (and / or another companion device). For example, in Figure 2 In the exemplary scenarios described herein, a device that communicates with a cellular base station using a relay link with another wireless device may also be referred to herein as a remote wireless device, a remote device, or a remote UE device, and a wireless device providing such a relay link may also be referred to herein as a relay wireless device, a relay device, or a relay UE device. According to some implementations, such BS 102, UE 106, and accessory device 107 may be configured to perform radio resource control procedures on the remote wireless device according to the various techniques described herein.

[0063] Both UE 106 and accessory device 107 may include a device or integrated circuit, referred to as a cellular modem, for facilitating cellular communication. The cellular modem may include one or more processors (processing elements) configured to execute program instructions stored in memory and / or various hardware components described herein. UE 106 and / or accessory device 107 may each execute any of the method embodiments described herein by executing such stored instructions. Alternatively or additionally, UE 106 and / or accessory device 107 may include programmable hardware elements, such as FPGAs (Field-Programmable Gate Arrays), integrated circuits, and / or various other possible hardware components, configured (e.g., individually or in combination) to perform any of or any portion of any of the method embodiments described herein. The cellular modem described herein can be used in UE devices as defined herein, wireless devices as defined herein, or communication devices as defined herein. The cellular modem described herein can also be used in base stations or other similar network-side devices.

[0064] UE 106 and / or accessory device 107 may include one or more antennas for communicating according to one or more RAT standards using one or more wireless communication protocols. In some embodiments, one or both of UE 106 or accessory device 107 may be configured to communicate using a single shared radio component. The shared radio may be coupled to a single antenna or to multiple antennas (e.g., for MIMO) for performing wireless communication. Typically, the radio component may include any combination of baseband processor, analog radio frequency (RF) signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.) or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio component may use the aforementioned hardware to implement one or more receive chains and transmit chains.

[0065] Alternatively, UE 106 and / or accessory device 107 may include two or more radio components. For example, in some embodiments, UE 106 and / or accessory device 107 may include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to communicate. As another possibility, UE 106 and / or accessory device 107 may include one or more radio components shared among multiple wireless communication protocols, as well as one or more radio components uniquely used by a single wireless communication protocol. For example, UE 106 and / or accessory device 107 may include shared radio components for communication using either LTE or CDMA2000 1xRTT (or LTE or NR, or LTE or GSM), and for communication using Wi-Fi and BLUETOOTH. TM Each component communicates with a separate radio unit. Other configurations are also possible.

[0066] Figure 3 —Block diagram of UE device

[0067] Figure 3 A possible block diagram of a UE device, such as UE device 106 or 107, is shown. As shown, UE device 106 / 107 may include a System-on-Chip (SOC) 300, which may include components for various purposes. For example, as shown, SOC 300 may include a processor 302 and display circuitry 304, the processor 302 executing program instructions for UE device 106 / 107, and the display circuitry 304 performing graphics processing and providing display signals to a display 360. SOC 300 may also include motion sensing circuitry 370, which may detect motion of UE 106, for example, using a gyroscope, accelerometer, and / or any of various other motion sensing components. Processor 302 may also be coupled to memory management unit (MMU) 340, which may be configured to receive addresses from processor 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, flash memory 310) and / or other circuitry or devices, such as display circuitry 304, radio components 330, I / F 320, and / or display 360. MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, MMU 340 may be included as part of processor 302.

[0068] As shown in the figure, the SOC 300 can be coupled to various other circuits of the UE 106 / 107. For example, the UE 106 / 107 may include various types of memory (e.g., including NAND flash memory 310), connector interface 320 (e.g., for coupling to computer systems, docking stations, charging stations, etc.), display 360, and wireless communication circuitry 330 (e.g., for LTE, LTE-A, NR, CDMA2000, Bluetooth, Wi-Fi, NFC, GPS, etc.).

[0069] UE device 106 / 107 may include at least one antenna and, in some embodiments, may include multiple antennas 335a and 335b for performing wireless communication with a base station and / or other devices. For example, UE device 106 / 107 may use antennas 335a and 335b to perform wireless communication. As described above, UE device 106 / 107 may be configured in some embodiments to perform wireless communication using multiple wireless communication standards or radio access technologies (RATs).

[0070] The wireless communication circuitry 330 may include a Wi-Fi logic component 332, a cellular modem 334, and a Bluetooth logic component 336. The Wi-Fi logic component 332 enables the UE device 106 / 107 to perform Wi-Fi communication over an 802.11 network. The Bluetooth logic component 336 enables the UE device 106 / 107 to perform Bluetooth communication. The cellular modem 334 may be a low-power cellular modem capable of performing cellular communication according to one or more cellular communication technologies.

[0071] As described herein, UE 106 / 107 may include hardware and software components for implementing embodiments of this disclosure. For example, by executing program instructions stored on a storage medium (e.g., a non-transitory computer-readable storage medium), the processor 302 of UE device 106 / UE device 107 may be configured to implement part or all of the methods described herein. In other embodiments, processor 302 may be configured as a programmable hardware element, such as an FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Furthermore, processor 302 may be coupled to, for example, Figure 3Other components shown and / or interoperable with said other components are used to perform radio resource control procedures for remote wireless devices according to various embodiments disclosed herein. Processor 302 may also implement various other applications and / or end-user applications running on UE 106. Alternatively or additionally, one or more components of the wireless communication circuitry 330 (e.g., cellular modem 334) of UE device 106 / 107 may be configured, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), a processor configured as an FPGA (Field Programmable Gate Array), and / or a processor using dedicated hardware components that may include ASICs (Application-Specific Integrated Circuits) to implement part or all of the methods described herein.

[0072] Figure 4 —Block diagram of a base station

[0073] Figure 4 An exemplary block diagram of a base station 102 according to some embodiments is shown. It should be noted that... Figure 4 The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include a processor 404 capable of executing program instructions specific to base station 102. Processor 404 may also be coupled to a memory management unit (MMU) 440 or other circuitry or device, which may be configured to receive addresses from processor 404 and translate those addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450).

[0074] Base station 102 may include at least one network port 470. (As mentioned above...) Figure 1 and Figure 2 As described herein, network port 470 can be configured to be coupled to a telephone network and provide access to multiple devices, such as UE devices 106 / 107, that have access to the telephone network.

[0075] Network port 470 (or an additional network port) may also be configured, or alternatively configured, to be coupled to a cellular network, such as the core network of a cellular service provider. This core network may provide mobility-related services and / or other services to multiple devices, such as UE devices 106 / 107. For example, the core network may include, for instance, a Mobility Management Entity (MME) for providing mobility management services, a Serving Gateway (SGW) and / or a Packet Data Network Gateway (PGW) for providing external data connections such as to the Internet, and so on. In some cases, network port 470 may be coupled to a telephone network via the core network, and / or the core network may provide the telephone network (e.g., between other UE devices served by the cellular service provider).

[0076] Base station 102 may include at least one antenna 434 and possibly multiple antennas. One or more antennas 434 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE device 106 / 107 via radio component 430. Antenna 434 communicates with radio component 430 via communication link 432. Communication link 432 may be a receive link, a transmit link, or both. Radio component 430 may be configured to communicate via various wireless communication standards, including but not limited to LTE, LTE-A, NR, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0077] Base station 102 can be configured to perform wireless communication using multiple wireless communication standards. In some cases, base station 102 may include multiple radios that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio for performing communication according to LTE and a Wi-Fi radio for performing communication according to Wi-Fi. In such a case, base station 102 may be able to operate as both an LTE base station and a Wi-Fi access point. As another possibility, base station 102 may include a multi-mode radio component capable of performing communication according to any of multiple wireless communication technologies (e.g., LTE and NR, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0078] As further described herein, base station 102 may include hardware and software components for implementing or supporting embodiments of the features described herein. According to some embodiments, processor 404 of base station 102 may be configured to implement some or all of the methods described herein, for example by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, processor 404 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array), or as an ASIC (Application-Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 430, 432, 434, 440, 450, 460, 470, processor 404 of BS 102 may be configured to implement or support radio resource control procedures for remote wireless devices according to the various embodiments described herein, and / or any of the various other features of the features described herein.

[0079] Figure 5 —Determine the time domain window

[0080] Transmissions (e.g., uplink (UL) transmissions) can be grouped in various ways. For example, transmissions can be grouped into multiple time slots (and / or other time periods, such as symbols) based on techniques such as physical time slot-based repetition, available time slot-based repetition, and / or Transmission Block in Multi-Time Slot (TB) Processing (TBoMS).

[0081] In physical time slot-based repetition (e.g., also known as consecutive repetition), a transmission can be repeated within a given number of consecutive time slots or time periods (e.g., TB). For example, if the number of time periods is 10, a UL transmission can be repeated within any UL time period within the range of 10 consecutive time periods. For example, if the 10 time periods are indexed from 0 to 9 and time periods 0 to 4 and 6 to 9 are scheduled for uplink transmission, and time period 5 is scheduled for downlink (DL), then a UL transmission can be repeated 9 times (e.g., once for each of time periods 0 to 4 and 6 to 9).

[0082] In slot-based repetitions, a transmission (e.g., TB) can be repeated a given number of times over a series of time periods (e.g., until a given number is reached). For example, if the number is 10, a transmission can be repeated in every time period available for UL transmission (e.g., including UL and / or special (S) time periods) until 10 repetitions are performed. For example, if time periods 0 to 4 and 6 to 9 are scheduled for UL transmissions, time periods 5 and 10 are scheduled for DL ​​transmissions, and time period 11 is scheduled as a special time period (and is therefore considered available for UL), then 10 repetitions can be completed over 12 time periods (e.g., 0 to 11, where transmissions occur in all time periods except 5 and 10). The determination of available time slots for slot-based repetitions is discussed at the RAN1#106-e meeting. For example, the repetition of Physical UL Shared Channel (PUSCH) can be counted based on available time slots according to the following two steps:

[0083] Step 1: In addition to the Time Domain Resource Allocation (TDRA) in the scheduling PUSCH, configuration authorization (CG) configuration, or DL ​​control information (DCI) for activating DCI, the UE can determine the available time slots for a given number (e.g., K times) repetitions based on the Radio Resource Control (RRC) configuration. For example, the TDRA can describe how many symbols are allocated for transmission (and the locations of these symbols). In Step 1, the TDRA can be used to identify whether any particular time slot is valid for UL transmission.

[0084] Step 2: The UE can determine whether to discard a PUSCH repeat, but can still count any discarded PUSCH repeats in K repeats. Furthermore, for PUSCH repeat type A, semi-static flexible symbols can be considered available, such as for CG PUSCH and / or Dynamically Granted (DG) PUSCH.

[0085] According to TBoMS, a single TB (or packet, etc.) can be transmitted within multiple time periods (e.g., time slots and / or symbols, etc.). For example, the number of time periods used to transmit a TB may depend on the length of the TB and / or other factors (e.g., modulation and coding scheme (MCS, etc.).

[0086] One application of packet transmissions may include joint channel estimation (e.g., also known as demodulation (DM) reference signal (RS) (DM-RS) bundling). Joint channel estimation may include cross-slot channel estimation within consecutive time slots, cross-slot channel estimation within discontinuous time slots, cross-repetition channel estimation within a single time slot, and inter-slot frequency hopping with inter-slot bundling to achieve cross-slot channel estimation. For example, joint channel estimation within consecutive time slots can be performed using transmissions grouped into multiple consecutive time periods. Relevant aspects of joint channel estimation may include: power coherence and phase continuity, DM-RS placement in specific time slots, and DM-RS configuration.

[0087] Maintaining power consistency and phase continuity within packet transmissions can support joint (e.g., cross-slot) channel estimation across multiple transmissions (e.g., multiple PUSCH transmissions). A relevant factor for determining the time window with power consistency and phase continuity is the maximum duration during which the UE is able to maintain power consistency and / or phase continuity, for example, by enduring power consistency and / or phase continuity requirements.

[0088] According to some implementation schemes, for joint channel estimation (e.g., type A PUSCH repetition for the same TB), all repetitions may be covered by one or more consecutive or discontinuous configuration time-domain windows (TDWs). Each configuration TDW may consist of one or more consecutive physical time periods (e.g., time slots and / or symbols, etc.). The window length L of the configuration TDW may be explicitly configured with a single value. The start of the first configuration TDW may be the first PUSCH transmission. The start of other configuration TDWs may be implicitly determined before the first repetition. For paired spectrum and / or supplementary UL (SUL) band configurations, the configuration TDWs may be consecutive. The end of the last configuration TDW may be the end of the last PUSCH transmission. Within a configuration TDW, one or more actual TDWs (ATDWs) may be implicitly determined. The start of the first actual TDW may be the first PUSCH transmission within the configuration TDW. After the start of an actual TDW, the UE may maintain power consistency and phase continuity until one of the following conditions is met, at which point the actual TDW may end, and power consistency and / or phase continuity may no longer be maintained. In other words, power and / or phase can be maintained during an ATDW, and power and / or phase can be changed between one ATDW and the next. As one possible condition, the actual TDW may reach the end of the last PUSCH transmission within the configured TDW. As another possible condition, the actual TDW may reach its maximum duration. As yet another possible condition, events that violate power consistency and phase continuity may occur. For example, events may include, for instance, DL time slots based on an unpaired spectrum DL / UL configuration, DL receive / monitor timing on unpaired spectrum, high-priority transmissions, frequency hopping, and / or precoder cycles. Events can be instances that disrupt the power consistency and / or phase continuity of UL transmissions. Events can be changes in the purpose and / or transmission direction of time slots or other time periods. For example, an event may change whether a time slot is used for UL transmissions and / or may change the characteristics of UL transmissions (e.g., power and / or phase). In some implementations, the end of the ATDW may be the last available time slot / symbol of a PUSCH transmission that occurs just before the event, resulting in a violation of power consistency and phase continuity. Whether a new ATDW is generated if power consistency and phase continuity are violated due to an event may depend on the UE's ability to restart the DM-RS binding. If the UE is able to restart the DM-RS binding, a new ATDW can be generated after the event. The start of the new ATDW can be the first available slot / symbol transmitted in the PUSCH following the event. If the UE cannot restart the DM-RS binding, no new ATDW will be generated until the end of the TDW configuration. In some implementations, the UE's ability to restart the DM-RS binding may only apply to dynamic events.In some implementations, the ability to restart a DM-RS-bound UE can be applied to dynamic and / or non-dynamic events.

[0089] Various standards can include various types of repetition (e.g., for PUSCH). For example, some standards can include Type A and Type B repetition. Type A repetition can be per slot. In Type A, the same TDRA can be applied for each UL slot. Type B repetition can repeat TB within a slot. However, Type B excludes repetition across slot boundaries. Therefore, in Type B, repetition can be restarted in the next slot. A time-domain window can be applied to both repetition types.

[0090] Figure 5 This is a communication flowchart illustrating an exemplary method for determining one or more ATDWs according to some implementation schemes. Figure 5 The method allows for the configuration of the window length parameter and can address error propagation issues (e.g., a time-domain window length L longer than the maximum duration in the case of a UE missing an event). Figure 5 The method may include determining the length of the ATDW and configuring the start of the TDW, for example, for unpaired spectrum. Furthermore, Figure 5 The method can support half-duplex (HD) frequency division duplex (FDD) (HD-FDD) UEs.

[0091] In various implementation schemes, Figure 5 Some elements of the method shown may be executed simultaneously, in a different order than shown, replaced by other method elements, or omitted. Additional method elements may also be executed as needed.

[0092] Figure 5 Various aspects of the method can be implemented by a UE such as UE 106 or 107, a cellular network, and / or one or more BSs 102, as needed as shown in and described with reference to the figures, or more generally in combination with any of the computer systems, circuits, elements, components, or devices shown in the figures. For example, one or more processors (or processing elements) (among various possibilities, such as processors 302, 404, baseband processors, processors associated with communication circuits such as 330, 332, 334, 336, 430, or 432, processors associated with various core network elements, etc., and various possible processors) can enable the UE, network elements, and / or BS to perform some or all of the method elements shown. It should be noted that although described in a manner involving the use of communication technologies and / or features associated with LTE, NR, and / or 3GPP specification documents, Figure 5 This description describes at least some elements of the method, but it is not intended to limit this disclosure and can be used in any suitable wireless communication system as needed. Figure 5 Various aspects of the method. Similarly, although described in a manner related to UL transmission performed by the UE. Figure 5 The method contains at least some elements, but it should be understood that Figure 5 Various aspects of the method can be similarly used for DL ​​transmissions performed by the BS and / or transmissions between multiple UEs (e.g., sidelink and / or device-to-device (D2D) transmissions, etc.). For example, according to some implementation schemes, Figure 5 Various aspects of the method can be used to determine the ATDW characteristics of DL, sidelink, and / or D2D transmissions. Similarly, it is described in relation to physical time slot-based repetition, available time slot-based repetition, and multi-time slot intra-TB processing (TBoMS). Figure 5 The methods cover various aspects. However, Figure 5 This method can also be applied to other transmission types. Furthermore, Figure 5 This method can be applied to repetitions of type A and / or type B, as well as various possible repetitions. As shown in the figure, this method can be operated as follows.

[0093] According to some implementation schemes, the UE and BS can establish communication (502). The UE and BS can communicate using one or more radio access technologies (RATs) (e.g., including NR). The UE and BS can communicate using any frequency resources. The UE and BS can communicate using one or more frequency carriers (e.g., including licensed and / or unlicensed carriers). Furthermore, the UE and BS can use various duplex technologies, including full-duplex, time-division duplex (TDD), FDD, and / or half-duplex, such as HD-FDD. The UE and BS can use supplementary bands / carriers, such as SUL bands. The UE and BS can use paired and / or unpaired spectrum. The BS can provide one or more cells and / or cell groups, and communication between the UE and BS can use one or more cells and / or cell groups.

[0094] The BS can exchange configuration information with the UE. For example, the BS can use Radio Resource Control (RRC) and / or other higher-level signaling to negotiate parameters and / or configure the UE. Configuration information may include various parameters related to the determination of joint channel estimation, DM-RS binding and / or TDW, as well as various other parameters.

[0095] As part of the exchange of configuration information, the UE may provide the BS with information (e.g., a capability report) describing its capabilities in relation to the determination of a time-domain window. For example, the UE may provide information about the maximum duration for which it can maintain power consistency and / or phase continuity. For instance, the UE may report the maximum duration within a range of {2,3,4,5,6,7,8,9,10} time slots, as well as various other ranges. Other maximum durations may be used as needed, such as durations measured in symbols, milliseconds, and / or other time units. In some implementations, the UE may indicate different durations for different connections (e.g., different cells, different carriers, different frequency ranges, etc.).

[0096] As part of the configuration exchange, the UE and BS can negotiate one or more configuration TDW lengths L. For example, the BS can configure the UE with one or more L values. For instance, L values ​​can be in the range {0, 2, 3, 4, 5, 6, 7, 8, 9, 10}, and various other ranges. In some implementations, the BS can determine the L value based on the maximum duration (e.g., based on UE capability information). According to some implementations, an L value of 2 may mean a window length of 2 time slots, 3 may mean 3 time slots, and so on.

[0097] However, according to some implementations, the L value of 0 can have different meanings. For example, an L value of 0 can indicate that the window length is equal to all physical time slots used for transmission. According to some implementations, this value of 0 can be applied only to TDD communications (e.g., NRTDD).

[0098] As a possibility, L may be less than or equal to the maximum duration indicated by the UE (e.g., related).

[0099] As another possibility, L may be greater than (e.g., related) the maximum duration. In this case, the configured TDW can be divided into smaller ATDWs, as discussed further below.

[0100] It should be understood that other L values ​​may be used as needed, such as L values ​​measured in symbols, milliseconds, and / or other time units and / or L values ​​greater than 10 time slots. In some implementations, different L values ​​may be used for different connections (e.g., different UEs, different cells, different carriers, different frequency ranges, etc.). For example, the L value may be UE-specific. As another example, different L values ​​may be used for FDD and TDD communication, for example, in the same cell or different cells.

[0101] In some implementations, as part of the configuration exchange, the UE and BS may negotiate one or more rules for determining the ATDW. Therefore, the UE and BS may share a common set of rules used for such determination. In some implementations, different rules may be used for different connections (e.g., different cells, different carriers, different frequency ranges, etc.). For example, a set of rules may be cell-specific. As another example, different rules may be used for FDD and TDD communications, for example, in the same cell or different cells. In some implementations, some or all of the rules may be adopted in the standard, and therefore the UE and BS may share the rules without exchanging any indication of the rules.

[0102] In some implementations, configuration information may be updated from time to time (e.g., periodically and / or as needed). Such updates may include modifying and / or replacing one or more parameters, such as the maximum duration of the UE and / or the TDW length L.

[0103] According to some implementation schemes, the BS may transmit one or more instructions from a schedule to the UE (504). The schedule may apply at least to a first time period. The schedule may include one or more times for UL transmission (e.g., time slots, symbols, etc.) and / or one or more times for DL ​​transmission (e.g., time slots, symbols, etc.). For example, the schedule may include one or more UL transmission opportunities. A UL transmission opportunity may be a continuous time period of UL transmission (e.g., consisting of one or more consecutive times).

[0104] Schedules can be semi-static and / or dynamic. The BS can use RRC, Media Access Control (MAC), and / or DCI signaling to indicate schedules. Schedules can include duplex, such as TDD, HD-FDD, etc. For example, a schedule can be or can include a series of times (e.g., time slots, symbols, etc.), some of which can be assigned to UL, some to DL, and some of which can be assigned as “special” time slots that can be considered available for UL and / or DL. Schedules may also include protection periods associated with changed transmission directions.

[0105] As a possibility, duplex schedules such as one or two TDD UL / DL modes can be configured semi-statically. BS can dynamically indicate one or more changes to the schedule (e.g., using DCI, etc.).

[0106] The UE can determine the schedule, for example, based on instructions from the BS and possibly other information (e.g., standards).

[0107] In some implementations, the UE may send one or more confirmations of the schedule and / or any changes to the schedule to the BS.

[0108] According to some implementation schemes, the UE and BS can (e.g., independently) determine one or more actual duration windows (506). The UE and BS can determine the ATDW for a first time period. For example, uplink opportunities during the first time period can be divided into one or more ATDWs. The ATDW can be as long as the length of the corresponding UL opportunity in the schedule. In other words, UL opportunities can be separated into multiple ATDWs, or UL opportunities may not be separated and can be determined as a single ATDW.

[0109] The UE and BS can determine the ATDW using one or more rules (e.g., steps), such as a schedule based on a first time period and configuration information. For example, the UE and BS can determine the ATDW from UL / DL configuration, L, maximum duration, and dynamic signaling trigger events.

[0110] When the UE and BS can share a common set of rules, and both the UE and BS share the same understanding of the schedule, the UE and BS can (e.g., independently) determine the same ATDW. However, if the UE and BS do not share the same understanding of the schedule (e.g., because the UE did not correctly receive the DCI for updating the schedule), it is possible that the UE and BS can determine different ATDWs.

[0111] For example, the BS and / or UE may divide the configured TDW into one or more ATDWs according to the following steps. The time window determined in an earlier step may be referred to as the "preliminary time domain window" or "PDTW" compared to the "actual" window (e.g., ATDW) determined in the final step.

[0112] In various implementation schemes, some steps may be performed simultaneously in a different order than those shown, may be replaced by other steps, or may be omitted. Additional steps may also be performed as needed.

[0113] First, the BS and / or UE can apply a configuration length L to divide the first time period into one or more PTDWs. This step can only be applied if L is greater than 0. For example, for FDD repetition, if the first time period is 13 slots and L is 5 slots, the first time period can be divided into 3 PTDWs (e.g., slots 0 to 4, slots 5 to 9, and slots 10 to 12).

[0114] The BS and / or UE may determine the start and end of the PTDW as follows: The start time (e.g., time slot) of the first PTDW may be the first time (e.g., time slot) of UL transmission. The first PTDW may include a duration of L (e.g., time slot) starting from the first time. The end of the PTDW may be the Lth time or the end of the first time period. The PTDW may be continuous. For example, the following PTDW may start from the first time of UL transmission after the end of the previous PTDW. The first time (e.g., time slot) of UL transmission may be the first physical time (e.g., UL or special) of continuous UL repetition and may be the first available time based on the repetition of available time slots and TBoMS. For example, if the first physical time is a continuously repetitive DL time slot, the DL time slot may be skipped until the next time slot is a UL time slot, and the first UL time slot may be the first time slot of the PTDW. For repetition based on available time slots, the DL time slot and any unavailable UL time slots may be skipped until the first available UL time slot is the first time slot of the PTDW. For example, an unavailable UL time slot can be a UL time slot that has been designated for another purpose and cannot be used repeatedly, as well as various other time slots.

[0115] Second, the BS and / or UE can determine whether the PTDW or UL transmitter is interrupted (e.g., interrupted) by one or more DL transmitters (e.g., time slots, symbols, etc.) in the TDD UL / DL configuration. If the PTDW or UL transmitter is interrupted, it can be divided into multiple PTDWs, for example, before and after each interruption of a DL transmitter. For an example of the application of this step, see [link to relevant documentation]. Figure 6 and Figure 7 (Further discussion follows).

[0116] It should be understood that a PTDW or UL transmitter opportunity may consist of any number of consecutive times (e.g., time slots, symbols, etc.) available for UL transmission, including “special” time slots, subframes, etc. Interruptions or interruptions in a PTDW or UL transmitter opportunity may consist of one or more consecutive times (e.g., time slots, symbols, etc.) that are not available for UL transmission (e.g., those designated for DL ​​or protection periods, etc.).

[0117] Furthermore, it should be understood that UL transmission opportunities can be interrupted multiple times, for example, as long as the time unavailable for UL is not consecutive. For example, consider the schedule {U,S,D,U,D,D,U}, where “U” indicates UL, “D” indicates DL, and “S” indicates special. The UL transmission opportunity in this schedule is interrupted twice (e.g., by times “D” and “D,D”), and therefore, it can be divided into three PTDWs based on this step. In other words, after this step, the PTDWs will not be interrupted or interrupted; for example, each PTDW may only include the time available for UL transmission.

[0118] Therefore, after this step, the start time (e.g., time slot) of the first PTDW can be the first allocated time (e.g., time slot) of the UL transmission. The end of the PTDW can be the earlier of the following: the last time (e.g., time slot) of the UL transmission, the last time (e.g., time slot) of the first time period, and / or the last time within a length L starting from the start time of the PTDW (e.g., if L > 0). The PTDW can be continuous; for example, the next PTDW can start from the first time (e.g., time slot) of the UL transmission after the end of the previous PTDW.

[0119] If L=0, the PTDW length can be equal to all continuous time available for UL emission.

[0120] According to some implementation schemes, this step may not be applied to NR FDD or Supplemental UL (SUL) configurations.

[0121] Third, the BS and / or UE can determine whether the PTDW (e.g., after any previous step in the application) is greater than / longer than the maximum duration. Any PTDW longer than the maximum duration can be subdivided into two or more PTDWs not exceeding the maximum duration. For example, the length of a PTDW can be divided according to the maximum duration, such that any number of PTDWs equal to the maximum duration are generated, and the last PTDW may include any remaining portion. For example, the first "new" PTDW may include a length equal to the maximum duration. The second or subsequent new PTDW may include a length equal to the maximum duration or the remaining portion of the PTDW divided in that step. It should be noted that, according to some embodiments, this subdivision may not merge any PTDWs previously separated in earlier steps.

[0122] Fourth, the BS and / or half-duplex FDD UE can determine whether any PTDW conflicts with any Synchronization Signal Block (SSB) (e.g., overlaps). If so, the PTDW can be subdivided, for example, to avoid an SSB. For instance, the PTDW will be divided into two PTDWs before and after an SSB transmission. In some implementations, this step may only be applied in the context of HD-FDD operation. In some implementations, the network may avoid scheduling that would cause an SSB to conflict with a PUSCH transmission. In some implementations, this step may be similarly applied to one or more other types of RS. In some implementations, this step may be most relevant to half-duplex FDD communication, so any UE and / or BS performing other types of communication may skip this step, along with various other steps.

[0123] Fifth, the BS and / or UE may adjust any PTDW based on any relevant dynamic signaling triggering event (e.g., cancellation indication (CI), priority indication, slot format indication (SFI) (e.g., via DCI format 2_0, and various other formats) or other events). For example, a CI may cancel a UL opportunity at a certain time (e.g., making a time previously considered available for UL now available for UL). Due to such a CI, the PTDW including the canceled UL time may be shortened (e.g., if the canceled UL time is at the beginning or end of the PTDW) or divided into two PTDWs (e.g., thus creating a PTDW before the canceled UL time and a PTDW after the canceled UL time). As another example, a high-priority PUSCH transmission may conflict with a low-priority PUSCH repetition at a specific time. The low-priority PUSCH transmission may be canceled. Therefore, power level and phase continuity cannot be maintained after a high-priority PUSCH transmission. Therefore, the PTDW previously including a specific time may be shortened or divided (e.g., similar to the case of CI). As another example, consider configuring an authorized UL transmission type, such as when a transmission is not triggered by a DCI. A SFI can change a UL time slot to a DL time slot. In this case, a UL transmission used for CG type 1PUSCH repetition can be interrupted. Due to this SFI, the PTDW, including the time for switching to DL, can be shortened (e.g., if the switch to DL time is at the beginning or end of the PTDW) or divided into two PTDWs (e.g., resulting in one PTDW before the switch to DL time and one PTDW after the switch to DL time). As yet another example, an SFI can change a flexible time slot to a DL time slot. A flexible time slot (e.g., before the SFI) might be considered available for UL; however, after the SFI, a DL time slot might not be considered available. This could result in a shortened or divided PTDW, as discussed above.

[0124] In some implementations, a transmission scheduled by Dynamic Grant (DG) (e.g., whether UL or DL) may be considered to have a higher priority than a transmission scheduled by Configuration Grant (CG) (e.g., whether UL or DL). Therefore, higher-priority transmissions (e.g., those scheduled by DG) can be prioritized. Any PTDW can be adjusted as needed to accommodate this priority.

[0125] In some implementations, timing thresholds may exist to determine what is considered a dynamic signaling trigger event. For example, any event signaled a certain amount of time before a changed transmission time may be considered part of the schedule (e.g., and therefore resolved in a previous step), while any event signaled a certain amount of time after that threshold may be considered a dynamic event in this step.

[0126] After these steps are completed (e.g., in sequence), the resulting PTDW can be considered as an ATDW for maintaining power consistency and / or phase continuity of the transmission.

[0127] In some implementations, the end of the ATDW can be the last time (e.g., a time slot) within the ATDW for UL transmission.

[0128] The following provides some examples of HD-FDD repeat and / or TBoMS transmission scenarios.

[0129] As an option, the BS can configure a TDD UL / DL configuration mode for the HD-FDD UE (e.g., in 504). UL transmission and DL reception can be based on indications from the UL / DL configuration. The ATDW determination can follow the same steps discussed above.

[0130] As another possibility, all UL time slots can be considered available for TDW determination. To determine ATDW, the BS and / or UE can proceed according to the following steps: First, determine if the PTDW is greater than the maximum duration. If so, subdivide the PTDW as discussed above. Second, adjust any dynamic signaling trigger events, similar to those discussed above. Regarding dynamic signaling events, the following scenarios can be considered.

[0131] Scenario 1: Dynamic Grant (DG) DL transmission (e.g., PDSCH) conflicts with Configuration Grant (CG) UL transmission. DG PDSCH can be considered to have higher priority than CG UL transmission. The BS and / or UE can divide the PTDW into two ATDWs before / after the DL transmission.

[0132] Scenario 2: CG DL transmission conflicts with DG UL transmission. According to some implementations, DG UL transmissions may be considered higher priority. Therefore, this may not be considered a valid event, and thus the UL transmission may not be interrupted by the DL transmission. However, it should be understood that an additional ATDW can be added, or the existing ATDW can be extended, for example, by associating it with the additional UL transmission time. For example, if the additional UL transmission time interrupts the DL transmission or would cause the existing PTDW to violate another rule (e.g., by being longer than the maximum duration or longer than L), the BS and / or UE may add an additional ATDW to the time of the additional UL transmission. Alternatively, if the existing PTDW can be extended to include the additional UL transmission time without violating any other rules, the BS and / or UE can extend the earliest PTDW that can be extended in this way.

[0133] Scenario 3: CG DL transmission conflicts with CG UL transmission. This may not be considered a valid event, for example, because the two transmissions are associated with non-dynamic authorizations, such as those with the same priority. In some implementations, the UE may not expect this scenario to occur, and the BS may avoid scheduling such a scenario. In some implementations, if this scenario occurs, it can be handled based on which time slot arrives first. If the CG DL time slot arrives first, the CG UL transmission may be dropped, which may result in shortening or splitting the PTDW. Otherwise, the CG DL transmission may be dropped, which may result in adding an additional PTDW or extending a PTDW, as in Scenario 2.

[0134] Scenario 4: DG DL transmission conflicts with DG UL transmission. As in Scenario 3, this may not be considered a valid event, for example, because both transmissions are associated with dynamic grants, for example, having the same priority. In some implementations, the UE may not expect this scenario to occur, and the BS may avoid scheduling such a scenario. In some implementations, if this scenario occurs, it can be handled based on which time slot arrives first. If the DG DL time slot arrives first, the DG UL transmission can be dropped, for example, this might result in shortening or splitting the PTDW. Otherwise, the DG DL transmission can be dropped, which might result in adding an additional PTDW or extending a PTDW, as in Scenario 2.

[0135] Scenario 5: SSB and DG UL transmissions overlap. In some implementations, this can be considered an error condition. Therefore, the UE may not expect this scenario to occur frequently, and the BS may avoid scheduling it. In some implementations, if this scenario does occur, it can be considered a valid event. Therefore, the BS and / or UE can divide the added UL's PTDW into two ATDWs before / after the SSB transmission. Similarly, in the case of overlapping SSB and CG UL transmissions, the BS and / or UE can divide the UL's PTDW into two ATDWs before / after the SSB transmission.

[0136] According to some implementation schemes, the UE and the base station can communicate according to a schedule (508). For example, the UE can transmit to the BS during a first time period's UL opportunity. The UE can transmit during one or more ATDW periods (e.g., corresponding UL opportunities) and can maintain power consistency and / or phase continuity (e.g., individually) during the corresponding ATDW. In other words, for the duration of the first ATDW, the UE can maintain power consistency and / or phase continuity when transmitting to the BS. Similarly, for the duration of the second ATDW, the UE can maintain power consistency and / or phase continuity when transmitting to the BS. However, the UE may not maintain power consistency and / or phase continuity between different ATDWs. For example, for the duration of the first ATDW, the UE can maintain power consistency at a first power level when transmitting to the BS, and for the duration of the second ATDW, the UE can maintain power consistency at a second different power level when transmitting to the BS. Similarly, the phase of the second ATDW may not be consistent with the first ATDW.

[0137] The UE can transmit RS using UL transmission. For example, during ATDW, the UE can transmit bundled DM-RS, such as DM-RS with power consistency and / or phase continuity. The UE can transmit DM-RS at different powers in different ATDWs without phase continuity.

[0138] It should be understood that although the UE may not actively maintain power consistency and / or phase continuity across multiple ATDWs, changes in power level and / or phase may or may not occur. For example, multiple ATDWs may use the same power level, for instance, by chance.

[0139] According to some implementation schemes, the BS can estimate the channel based on transmissions from the UE during the corresponding ATDW period in one or more ATDWs (510). For example, the BS can perform a first cross-slot channel estimation for a first ATDW and a second cross-slot channel estimation for a second ATDW. For example, the BS can use DM-RS (and / or other RS ​​and / or information) transmitted by the UE to perform channel estimation for the ATDW. For the purpose of the corresponding channel estimation, the BS can present the power coherence and / or phase continuity of the corresponding ATDW.

[0140] Figures 6 to 13 —Examples determined by ATDW

[0141] Figure 6 and Figure 7An example of ATDW determination is shown, where the time-domain window length is set to be equal to all consecutive time available for UL transmission (e.g., L = 0). As mentioned above, in this configuration, the window length can be equal to all physical time slots used for transmission. The ATDW can be determined based on the DL time slots in the UL / DL configuration. This allows for the effective use of consecutive UL time slots to perform DM-RS bundled transmission. The possibility of error propagation (e.g., due to the UE missing an event, such as not receiving dynamic authorization) is avoided by the ATDW generated by the DL time slots in the UL / DL configuration. In the example shown, "L = Number of Repetitions" can indicate L = 0. In the example shown, it can be assumed that the consecutive time used for UL transmission (e.g., 4 time slots) is less than the maximum duration (e.g., 5 time slots or more, not shown).

[0142] It should be understood that in these examples, L = 0. Therefore, the BS and / or UE may not apply the first step discussed in 506. These examples illustrate the application of the second step.

[0143] Figure 6 An example of physical time slot-based repetition (e.g., consecutive repetition) with eight repetitions according to some implementations is shown. The second step may cause a change in one or more time windows. It should be understood that the BS and / or UE may also perform other steps discussed in 506, but they are not shown (e.g., because they may not have changed).

[0144] As shown in the figure, during the first time period (e.g., 8 times indicated by "continuous time slot repetition = 8"), there are two ATDWs that are separated by the DL time slot in the UL / DL mode, thus interrupting continuous UL transmission (e.g., during S and U times). According to some implementations, phase continuity and power consistency may not be maintained because the DL time slot interrupts the UL transmission opportunity. Therefore, as shown in the figure, UL transmission is divided into two ATDWs.

[0145] Figure 7 An example of repeating based on available time slots according to some implementation schemes is shown. The second step can cause changes to one or more time windows. Since DL time is not available for UL repeating, there are more (with) changes within the first time period. Figure 6 Compared to the total time (e.g., 11 time slots indicated by "Available Time Slot Repeat = 8"). The first time period may include 8 times (e.g., S and U) available for UL transmission. As shown, the DL time slots divide these times into three ATDWs with different lengths.

[0146] Figure 8 and Figure 9Examples are shown where "L = 6 time slots" is less than the maximum duration according to some implementation schemes. These examples illustrate the application of the first step and the second step discussed in 506.

[0147] Figure 8 An example is shown according to some implementations in a context of 12 repeated physical time slots. The first and second steps may cause changes to one or more time windows.

[0148] In the first step, the first time period is divided into two PTDWs with a length less than or equal to L. The first PTDW, for example, PTDW1, lasts for 6 time slots. The second (e.g., PTDW2) may begin at the first time of UL transmission after the end of PTDW1 (e.g., a special time slot). PTDW2 lasts for 4 time slots until the transmission ends.

[0149] In the second step, PTDW1 can be split into two ATDWs (e.g., ATDW 1 and 2) based on interruptions (e.g., DL slots). PTDW2 can be shortened based on DL slots (e.g., thus producing ATDW3).

[0150] Figure 9 An exemplary context based on available time slots is shown, according to some implementations, of repeating 12 UL times within a first time period of 16 times. The first and second steps may cause changes to one or more time windows.

[0151] In the first step, PTDW1 can be similar to Figure 8 PTDW1. PTDW2 may begin with the first UL transmission slot following the end of PTDW1. PTDW2 may last for 6 slots; for example, PTDW2 may be equal to the length L. PTDW3 may be consecutive to PTDW2 because the first slot following PTDW2 may be a UL slot.

[0152] In the second step, PTDW1 can be split into two ATDWs (e.g., ATDW 1 and 2) based on interruptions (e.g., DL slots), as in Figure 8 As in the example. PTDW2 can similarly be split into two ATDWs (e.g., ATDW 3 and 4) based on interruptions (e.g., DL slots). PTDW3 can remain unchanged in the second step and can become ATDW5.

[0153] Figure 10 and Figure 11 An example is shown where, according to some implementations, "L = 6 time slots" is greater than the maximum duration (e.g., 3 time slots). Both figures are in the context of consecutive time slot repetition, and the first time period comprises 12 time segments.

[0154] Figure 10 Examples are shown of how the first, second, and third steps of some implementation schemes cause changes to one or more time windows.

[0155] In the first step, two PTDWs with a length less than or equal to L are generated, such as PTDW 1 and 2. PTDW 2 can start from the first moment after the UL emission following the end of PTDW 1.

[0156] In the second step, PTDW1 can be divided into two PTDWs (1A and 1B) based on interruption (e.g., DL time). PTDW2 can be shortened based on DL time (e.g., becoming PTDW2A).

[0157] In the third step, the BS and / or UE can determine that PTDW1B is longer than the maximum duration (e.g., 3 time slots). Therefore, the BS and / or UE can divide PTDW1B into ATDWs (e.g., ATDW2 and ATDW3). Since PTDW1A and PTDW2A are not longer than the maximum duration, these can remain unchanged in the third time slot and can become ATDW 1 and 4 respectively.

[0158] Figure 11 Examples are shown of how steps one, two, three, and five of certain implementation schemes cause changes to one or more time windows. Figure 11 Dynamic events can occur. Specifically, UL opportunity 1101 can be cancelled (e.g., via a cancellation instruction transmitted by the BS and received by the UE). Before cancellation, Figure 11 The schedule for the first period can be compared with Figure 10 The schedule is the same as the one described above. Therefore, steps one, two, and three can be performed as described above. Figure 10 Perform as described (the difference being in) Figure 11 In the third step, the window is labeled PTDW to reflect the fact that it is not yet complete.

[0159] It should be understood that, for example, the dynamic signaling triggering event for canceling UL opportunity 1101 can occur at any time relative to the estimation of the steps. For example, 1101 can be canceled before, during, or after the estimation of steps 1 to 3.

[0160] In the fifth step, the BS and / or UE can determine that the cancellation of UL opportunity 1101 causes an interruption in PTDW1B1. Therefore, the BS and / or UE can divide PTDW1B1 into ATDW2 and ATDW3. The remaining PTDWs are unaffected by dynamic events.

[0161] As mentioned above, dynamic signaling triggering events have the lowest priority (e.g., resolved in the last step). Therefore, the impact of potentially missed dynamic events should be minimized, for example, relative to other possible sequences of steps that could resolve dynamic events earlier. For instance, if dynamic events are applied before the maximum duration (e.g., in the third step in the order described in 506), there will be three ATDWs derived from PTDW1 (e.g., instead of...). Figure 11 (4 of them). In other words, the hypothesis that choosing a different step order could produce a combination of ATDW3 and ATDW4 as a single ATDW.

[0162] Therefore, if the UE misses (e.g., fails to receive) the UL cancellation, the UE may assume an ATDW different from the BS.

[0163] Figure 12 An example of a physical time slot-based repetition (e.g., continuous repetition) with eight repetitions is shown according to some implementation schemes. Figure 12 The schedule may include SSB 1201 and various U and D times. The second and fourth steps may result in changes to one or more time windows.

[0164] In the second step, PTDW 1 and 2 can be generated, for example, based on DL interruption.

[0165] In the fourth step, PTDW2 can be divided into ATDW 2 and 3, for example, based on the SSB in time 1201. In some implementations, the SSB situation can be used for half-duplex FDD communication, so there may be no need to configure TDD UL / DL mode.

[0166] Figure 13 An example of a physical time slot-based repetition (e.g., continuous repetition) with eight repetitions comprising two time periods is shown according to some implementation schemes.

[0167] It should be understood that the BS and / or UE can Figure 5 The method can be applied to any number of consecutive time periods, such as time periods 1 and 2, as shown in the figure. For example, in 504, the BS can transmit instructions for the corresponding schedule in the corresponding time period. The schedule may be repeated or different. In 506, the UE and BS can determine the ATDW for each time period. The UE and / or BS can determine the ATDW for multiple time periods simultaneously or at different times (e.g., sequentially).

[0168] Time periods can have the same length (e.g., as in the example shown) or they can have different lengths (not shown).

[0169] Figure 12 The schedule for time period 1 is similar to Figure 6 That time period. For example... Figure 6 As shown, L can be equal to 0. Therefore, PTDW can have any length in the first and second steps (e.g., it may be longer than the maximum duration).

[0170] In the second step, the BS and / or UE can determine ATDW 1 and 2. It should be noted that the end of ATDW 2 can be determined based on the end of time period 1, even if the start of time period 2 (e.g., S) is available for UL transmission. Furthermore, in the second step, the BS and / or UE can determine ATDW 3 and 4. ATDW 3 can begin at the first time when UL transmission is available.

[0171] In some implementation schemes, Figure 5 The method can separate PTDWs without being based on time periods. Therefore, in such cases, ATDW3 can be combined with ATDW2.

[0172] Additional Information and Implementation Plan

[0173] In some implementations, a user equipment (UE) may establish communication with a base station and transmit a capability report to that base station, the capability report including an indication of the maximum duration for which the UE can transmit with power consistency and / or phase continuity. The UE may receive a schedule of uplink and / or downlink transmissions within a first time period from the base station. The UE may determine one or more actual time-domain windows for performing uplink transmissions with power consistency and / or phase continuity during the first time period, wherein the one or more actual time-domain windows are determined according to multiple rules used to determine the actual time-domain windows. The multiple rules may include one or more of the following: determining a separate preliminary time-domain window if an uplink transmission opportunity is interrupted by a downlink transmission opportunity; determining a separate preliminary time-domain window if the length of a previous preliminary time-domain window is greater than the maximum duration; and / or adjusting any previous preliminary time-domain windows affected by an event if an event modifies the schedule of uplink and / or downlink transmissions within the first time period. The UE may transmit information to the base station during one or more actual time-domain windows, wherein power consistency and / or phase continuity are maintained during each corresponding actual time-domain window of the one or more actual time-domain windows.

[0174] In some implementations, the method at the base station may include establishing communication with the user equipment (UE) and receiving a capability report from the UE, the capability report including an indication of the maximum duration for which the UE is capable of transmitting with power consistency and / or phase continuity. The method may also include transmitting a schedule of uplink and / or downlink transmissions for a first time period to the UE and determining one or more actual time-domain windows for receiving uplink transmissions with power consistency and / or phase continuity during the first time period, wherein the one or more actual time-domain windows are determined according to a plurality of rules for determining the actual time-domain windows. The plurality of rules may include one or more of the following: determining a separate preliminary time-domain window when an uplink transmission opportunity is interrupted by a downlink transmission opportunity; determining a separate preliminary time-domain window when the length of a previous preliminary time-domain window is greater than the maximum duration; and / or determining whether an event modifies the schedule of uplink and / or downlink transmissions for the first time period, and if the event modifies the schedule of uplink and / or downlink transmissions for the first time period, adjusting the previous preliminary time-domain window affected by the event. The method may also include receiving information from the UE during one or more real time-domain windows, wherein power consistency and / or phase continuity are maintained during each of the one or more real time-domain windows.

[0175] In some embodiments, the apparatus may include a processor configured to enable the UE to establish communication with a base station and transmit to the base station an indication of the maximum duration for which the UE can transmit with power consistency and / or phase continuity. The UE may determine a schedule of uplink and / or downlink transmission opportunities within a first time period based at least in part on information received from the base station. The UE may determine one or more actual time-domain windows for uplink transmission based on one or more of the following: applying a configuration length L to divide the first time period into lengths not longer than L; determining that the uplink transmission opportunities in the schedule are separated from the downlink transmission opportunities; or determining that the length of the uplink transmission opportunity or the previously preliminary time-domain window is greater than the maximum duration. The UE may transmit information and reference signals to the base station during one or more actual time-domain windows, wherein power consistency and / or phase continuity are maintained during each corresponding actual time-domain window of the one or more actual time-domain windows.

[0176] In a first set of embodiments, a user equipment (UE) can establish communication with a base station and transmit a capability report to that base station, the capability report including an indication of the maximum duration for which the UE can transmit with power consistency and / or phase continuity. The UE can receive from the base station a schedule of uplink and / or downlink transmissions within a first time period, the schedule including a first uplink transmission opportunity. The UE can determine multiple actual time-domain windows for performing uplink transmissions with power consistency and / or phase continuity during the first time period. The first uplink transmission opportunity can be subdivided into at least a first actual time-domain window and a second actual time-domain window. Multiple actual time-domain windows can be determined according to multiple rules used to determine the actual time-domain windows. The multiple rules may include: determining a separate preliminary time-domain window if an uplink transmission opportunity is interrupted by a downlink transmission opportunity; determining a separate preliminary time-domain window if the length of a previous preliminary time-domain window is greater than the maximum duration; and adjusting any previous preliminary time-domain windows affected by an event that modifies the schedule of uplink and / or downlink transmissions within the first time period. The UE can transmit information to the base station during multiple real time-domain windows, wherein power consistency and / or phase continuity are maintained during the respective real time-domain windows.

[0177] In some implementations, the processor is further configured to cause the UE to perform the following operation: receive from the base station an indication of a configured time-domain window length, wherein the indication of the configured time-domain window length is set to a value that indicates a corresponding uplink transmission for a schedule of uplink and / or downlink transmissions within a first time period, the configured time-domain window length being equal to the corresponding time length for the corresponding uplink transmission.

[0178] In some implementations, the processor is further configured to cause the UE to receive an indication of a configured time-domain window length from the base station, wherein the configured time-domain window length is UE-specific.

[0179] In some implementations, the processor is further configured to cause the UE to receive an indication of a configured time-domain window length from the base station, wherein the configured time-domain window length is cell-specific.

[0180] In some implementations, determining multiple actual time-domain windows based on multiple rules includes applying these multiple rules in a set order, which includes: first, determining a separate preliminary time-domain window if uplink transmission is interrupted by downlink transmission; second, determining a separate preliminary time-domain window if the length of a previous preliminary time-domain window is greater than the maximum duration; and third, adjusting any previous preliminary time-domain windows affected by an event if an event modifies the schedule of uplink and / or downlink transmissions within a first time period.

[0181] In some implementations, several rules also include determining a separate preliminary time-domain window if any previous preliminary time-domain window overlaps with the transmission of a synchronization signal block.

[0182] In some implementations, the processor is further configured to cause the UE to: receive an indication from the base station to configure a time-domain window length, wherein the multiple rules also include applying the configured time-domain window length to divide a first time period into one or more preliminary time-domain windows, wherein the application of the configured time-domain window length is executed before other rules among the multiple rules.

[0183] In some implementations, at least one of power coherence and / or phase continuity changes between a first real time-domain window and a second real time-domain window.

[0184] In a second set of embodiments, the method at the base station may include establishing communication with a user equipment (UE) and receiving a capability report from the UE, the capability report including an indication of the maximum duration for which the UE is capable of transmitting with power consistency and / or phase continuity. The method may also include transmitting a schedule of uplink transmission opportunities to the UE within a first time period and determining multiple actual time-domain windows for receiving uplink transmissions with power consistency and / or phase continuity during the first time period, wherein at least one uplink transmission opportunity is separated into two or more actual time-domain windows according to multiple rules used to determine the actual time-domain windows. The multiple rules may include one or more of the following: determining a separate preliminary time-domain window when an uplink transmission opportunity is interrupted by a downlink transmission opportunity; determining a separate preliminary time-domain window when the length of a previous preliminary time-domain window is greater than the maximum duration; and / or determining whether an event modifies the schedule of uplink transmission opportunities within the first time period, and if the event modifies the schedule of uplink transmission opportunities within the first time period, adjusting the previous preliminary time-domain window affected by the event. The method may also include receiving information from the UE during an uplink transmission opportunity period in a first time period, wherein power consistency and / or phase continuity are maintained during the respective real time window periods of multiple real time windows.

[0185] In some implementations, the method may further include: receiving a reference signal associated with information from the UE during a plurality of real time-domain windows, wherein power consistency and / or phase continuity are maintained for the reference signal during the respective real time-domain windows of the plurality of real time-domain windows; and performing a corresponding channel estimation for the respective real time-domain windows of the plurality of real time-domain windows based on the reference signal.

[0186] In some implementations, several rules also include: applying a configured time-domain window length to divide the uplink transmission opportunity of the first time period into one or more preliminary time-domain windows; and determining a separate preliminary time-domain window if any previous preliminary time-domain window overlaps with a synchronization signal block transmission.

[0187] In some implementations, the following rule (e.g., only) applies to half-duplex FDD communication: if any previous preliminary time-domain window overlaps with the transmission of the synchronization signal block, a separate preliminary time-domain window is determined.

[0188] In some implementations, determining multiple actual time-domain windows based on multiple rules includes applying these multiple rules in a set order, which includes: first, applying a configured time-domain window length to divide a first time period into one or more preliminary time-domain windows; second, determining a separate preliminary time-domain window when an uplink transmitter opportunity is interrupted by a downlink transmitter opportunity; third, determining a separate preliminary time-domain window when the length of a previous preliminary time-domain window is greater than the maximum duration; fourth, determining a separate preliminary time-domain window if any previous preliminary time-domain window overlaps with a synchronization signal block transmission; and fifth, determining whether an event modifies the schedule of uplink transmitter opportunities within the first time period, and if the event modifies the schedule of uplink transmitter opportunities within the first time period, adjusting the previous preliminary time-domain windows affected by the event.

[0189] In some implementations, the method may further include transmitting an indication to the UE of the configuration time-domain window length.

[0190] In some implementations, the method may further include: dividing a longer time period into multiple time periods, the multiple time periods including at least a first time period and a second time period; and determining a second or more actual time-domain windows for receiving uplink transmissions with power consistency and / or phase continuity during the second time period, wherein the second or more actual time-domain windows are determined according to multiple rules.

[0191] In some implementations, the method may further include: determining a schedule for updating uplink transmission opportunities within a first time period; and, in response to determining the schedule for updating uplink transmission opportunities within the first time period, transmitting an instruction to the UE using dynamic signaling for the update, wherein the update includes an event that modifies the schedule for uplink transmission opportunities within the first time period.

[0192] In a third set of embodiments, the apparatus may include a processor configured to enable the UE to establish communication with a base station and transmit to the base station an indication of the maximum duration for which the UE can transmit with power consistency and / or phase continuity. The UE may determine a schedule of uplink and / or downlink transmission opportunities within a first time period based at least in part on information received from the base station. The UE may determine one or more actual time-domain windows for uplink transmission, wherein at least one of the one or more actual time-domain windows for uplink transmission is shorter than the corresponding uplink opportunity in the schedule of uplink and / or downlink transmission opportunities. This determination may be based on one or more of the following: applying a configuration length L to divide the first time period into lengths not longer than L; determining that the uplink transmission opportunities in the schedule are separated from the downlink transmission opportunities; or determining that the length of the uplink transmission opportunity or the previously preliminary time-domain window is greater than the maximum duration. The UE may transmit information and reference signals to the base station during one or more actual time-domain windows, wherein power consistency and / or phase continuity are maintained during each corresponding actual time-domain window of the one or more actual time-domain windows.

[0193] In some implementations, determining one or more actual time-domain windows is performed sequentially, wherein the first step includes applying a configuration length L to divide the first time period into preliminary time-domain windows of length no longer than L.

[0194] In some implementations, the second step includes: determining whether any uplink launch opportunities in the schedule that were not previously separated into preliminary time-domain windows are separated from downlink launch opportunities; and separating any such uplink launch opportunities into corresponding preliminary time-domain windows before and after the downlink launch opportunities.

[0195] In some implementations, the third step includes: determining whether the length of any previous preliminary time-domain window is greater than the maximum duration; and separating any previous preliminary time-domain window whose length is greater than the maximum duration into corresponding preliminary time-domain windows whose length is less than or equal to the maximum duration.

[0196] In some implementations, the fourth step includes: determining whether any previously preliminary time-domain windows are affected by an event indicated by dynamic signaling received from the base station; and modifying any previously preliminary time-domain windows affected by the event based on the event.

[0197] In some implementations, one or more actual time-domain windows are determined to be further modified based on a schedule of dynamic signaling received from the base station, wherein the dynamic signaling includes one or more of the following: cancellation indication; priority indication; or time slot format indication.

[0198] In various implementation schemes, various combinations of the above implementation schemes can be combined together.

[0199] Another exemplary implementation may include a method comprising: a wireless device performing any or all of the foregoing examples.

[0200] Another exemplary embodiment may include a wireless device comprising: an antenna; a radio component coupled to the antenna; and a processing element operatively coupled to the radio component, wherein the device is configured to implement any or all of the foregoing examples.

[0201] Another exemplary embodiment may include an apparatus comprising a processing element configured to cause a wireless device to implement any or all of the foregoing examples.

[0202] Another set of exemplary embodiments may include a non-transitory computer-accessible memory medium comprising program instructions that, when executed at the device, cause the device to implement any or all of the portions of any of the foregoing examples.

[0203] Another exemplary set of implementations may include a computer program comprising instructions for performing any or all portions of any of the examples described above.

[0204] Another exemplary set of embodiments may include an apparatus that includes means for performing any or all elements of any of the examples described above.

[0205] By interpreting each message / signal X received by the user equipment (UE) in the DL as a message / signal X transmitted by the base station, and interpreting each message / signal Y transmitted by the UE in the UL as a message / signal Y received by the base station, any method described herein for operating the UE can serve as the basis for a corresponding method for operating the base station. Furthermore, methods described relative to the base station can be interpreted as methods used for the UE in a similar manner.

[0206] In addition to the exemplary embodiments described above, further embodiments of this disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.

[0207] In some embodiments, a non-transitory computer-readable storage medium may be configured to store program instructions and / or data, wherein if the program instructions are executed by a computer system, the computer system performs a method, such as any method embodiment of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset or combination of any such subset of any method embodiments described herein.

[0208] In some implementations, a device (e.g., UE 106 or 107) may be configured to include a processor (or a set of processors) and a memory medium, wherein the memory medium stores program instructions, and the processor is configured to read from the memory medium and execute the program instructions, wherein the program instructions can be executed to implement any of the various method implementations described herein (or any combination of the method implementations described herein, or any subset or combination of any such subset of any method implementations described herein). The device may be implemented in any of a variety of forms.

[0209] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0210] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. A method comprising: at a user equipment (UE): transmitting a capability report to a base station, the capability report including an indication of a maximum duration for which the UE can transmit with power consistency and / or phase continuity; receiving, from the base station, a configured time domain window length, wherein the configured time domain window length is less than or equal to the maximum duration and greater than 0; receiving, from the base station, a schedule of uplink transmissions for a first time period, the schedule including a first uplink transmission opportunity; determining a plurality of actual time domain windows for performing uplink transmissions with power consistency and / or phase continuity during the first time period, wherein the first uplink transmission opportunity is subdivided into at least a first actual time domain window and a second actual time domain window, wherein the plurality of actual time domain windows are determined according to a plurality of rules for determining actual time domain windows, the plurality of rules including: applying the configured time domain window length to divide the first time period into preliminary time domain windows (PTDWs), wherein a length of a first PTDW of the PTDWs is the configured time domain window length and a length of a second PTDW of the PTDWs is the configured time domain window length or a remaining portion of the first time period, wherein a start time of the first PTDW of the PTDWs is a first slot of uplink transmissions, wherein a start time of a subsequent PTDW of the PTDWs is a first slot of uplink transmissions after an end of a previous PTDW of the PTDWs; determining the plurality of actual time domain windows from the PTDWs, wherein determining an actual time domain window from a PTDW includes dividing the PTDW into actual time domain windows based on: if an uplink transmission opportunity is interrupted by a downlink transmission opportunity; and if a cancellation indication modifies the schedule of uplink transmissions; and transmitting information to the base station during the plurality of actual time domain windows, wherein power consistency and / or phase continuity is maintained during a respective actual time domain window.

2. The method of claim 1, further comprising: receiving, from the base station, an indication of a configured time domain window length, wherein the indication of the configured time domain window length is set to a value that indicates the configured time domain window length is equal to a respective time length for a respective uplink transmission of the schedule of uplink transmissions for the first time period.

3. The method of claim 1, further comprising: receiving, from the base station, an indication of a configured time domain window length, wherein the configured time domain window length is UE-specific.

4. The method of claim 1, wherein determining the plurality of actual time domain windows includes applying the plurality of rules according to a set order, the set order including: first, if an uplink transmission opportunity is interrupted by a downlink transmission opportunity, determining a separate preliminary time domain window; second, if a length of a previous preliminary time domain window is greater than the maximum duration, determining a separate preliminary time domain window; and third, if an event modifies the schedule of uplink transmissions for the first time period, adjusting any previous preliminary time domain windows affected by the event. ​ 5. The method of claim 1, the plurality of rules further comprising: determining a separate preliminary time domain window if any previous preliminary time domain window overlaps with a synchronization signal block transmission.

6. The method of claim 1, further comprising: receiving, from the base station, an indication of a configured time domain window length, the plurality of rules further comprising applying the configured time domain window length to partition a first time period into one or more preliminary time domain windows, wherein the applying the configured time domain window length is performed prior to other rules in the plurality of rules.

7. The method of claim 1, wherein at least one of power consistency and / or phase continuity changes between the first actual time domain window and the second actual time domain window.

8. A method comprising: at a base station: receiving, from a user equipment (UE), a capability report including an indication of a maximum duration for which the UE can transmit with power consistency and / or phase continuity; transmitting, to the UE, a configured time domain window length, wherein the configured time domain window length is less than or equal to the maximum duration and greater than 0; transmitting, to the UE, a schedule of uplink transmission opportunities within a first time period; determining a plurality of actual time domain windows for receiving uplink transmissions with power consistency and / or phase continuity during the first time period, wherein at least one uplink transmission opportunity is separated into two or more actual time domain windows according to a plurality of rules for determining actual time domain windows, the plurality of rules comprising: applying the configured time domain window length to partition the first time period into preliminary time domain windows (PTDWs), wherein a length of a first PTDW of the PTDWs is the configured time domain window length and a length of a second PTDW of the PTDWs is the configured time domain window length or a remaining portion of the first time period, wherein a start time of the first PTDW of the PTDWs is a first slot of an uplink transmission, wherein a start time of a subsequent PTDW of the PTDWs is a first slot of an uplink transmission after an end of a previous PTDW of the PTDWs; determining the plurality of actual time domain windows from the PTDWs, wherein determining an actual time domain window from a PTDW comprises partitioning the PTDW into actual time domain windows based on: if an uplink transmission opportunity is interrupted by a downlink transmission opportunity; and if a cancellation indication modifies the schedule of uplink transmission opportunities; and receiving, from the UE, information during the plurality of actual time domain windows, wherein power consistency and / or phase continuity is maintained during a respective actual time domain window of the plurality of actual time domain windows.

9. The method of claim 8, further comprising: receiving, from the UE during the plurality of actual time domain windows, a reference signal associated with the information, wherein power consistency and / or phase continuity is maintained for the reference signal during the respective actual time domain window of the plurality of actual time domain windows; and performing a respective channel estimation for the respective actual time domain window of the plurality of actual time domain windows based on the reference signal.

10. The method of claim 8, the plurality of rules further comprising: applying a configured time domain window length to divide a first time period of uplink transmission opportunities into one or more preliminary time domain windows; and determining a separate preliminary time domain window if any previous preliminary time domain window overlaps with a synchronization signal block transmission.

11. The method of claim 10, wherein determining the plurality of actual time domain windows comprises applying the plurality of rules according to a set order, the set order comprising: first, applying a configured time domain window length to divide a first time period into one or more preliminary time domain windows; second, determining a separate preliminary time domain window when an uplink transmission opportunity is interrupted by a downlink transmission opportunity; third, determining a separate preliminary time domain window when a length of a previous preliminary time domain window is greater than a maximum duration; fourth, determining a separate preliminary time domain window if any previous preliminary time domain window overlaps with a synchronization signal block transmission; and fifth, determining whether an event modifies a schedule of uplink transmission opportunities within the first time period, and adjusting any previous preliminary time domain window affected by the event if an event modifies a schedule of uplink transmission opportunities within the first time period.

12. The method of claim 10, further comprising: transmitting, to the UE, an indication of a configured time domain window length.

13. The method of claim 8, further comprising: dividing a longer time period into a plurality of time periods, the plurality of time periods comprising at least a first time period and a second time period; and determining a second one or more actual time domain windows for receiving uplink transmissions with power consistency and / or phase continuity during the second time period, wherein the second one or more actual time domain windows are determined according to the plurality of rules.

14. The method of claim 8, further comprising: determining to update the schedule of uplink transmission opportunities within the first time period; and in response to determining to update the schedule of uplink transmission opportunities within the first time period, transmitting, to the UE, an indication of the update using dynamic signaling, wherein the update comprises an event that modifies the schedule of uplink transmission opportunities within the first time period.

15. An apparatus comprising: a processor configured to cause a user equipment (UE) to: transmit, to a base station, a capability report comprising an indication of a maximum duration for which the UE can transmit with power consistency and / or phase continuity; receive, from the base station, a configured time domain window length, wherein the configured time domain window length is less than or equal to the maximum duration and greater than 0; receive, from the base station, a schedule of uplink transmissions within a first time period, the schedule comprising a first uplink transmission opportunity; determining a plurality of actual time domain windows for performing uplink transmissions with power consistency and / or phase continuity during the first time period, wherein the first uplink transmission opportunity is subdivided into at least a first actual time domain window and a second actual time domain window, wherein the plurality of actual time domain windows are determined according to a plurality of rules for determining actual time domain windows, the plurality of rules comprising: applying the configured time domain window length to divide the first time period into preliminary time domain windows (PTDWs), wherein a length of a first PTDW of the PTDWs is the configured time domain window length and a length of a second PTDW of the PTDWs is the configured time domain window length or a remaining portion of the first time period, wherein a start time of the first PTDW of the PTDWs is a first time slot of the uplink transmissions, wherein a start time of a subsequent PTDW of the PTDWs is a first time slot of the uplink transmissions after an end of a previous PTDW of the PTDWs; determining the plurality of actual time domain windows from the PTDWs, wherein determining an actual time domain window from a PTDW comprises dividing the PTDW into actual time domain windows based on: if the uplink transmission opportunity is interrupted by a downlink transmission opportunity; and if the cancellation indication modifies the schedule of uplink transmissions; and transmitting information to the base station during the plurality of actual time domain windows, wherein power consistency and / or phase continuity is maintained during a respective actual time domain window.

16. The apparatus of claim 15, wherein the processor is further configured to cause the UE to: receive, from the base station, an indication of a configured time domain window length, wherein the indication of the configured time domain window length is set to a value that indicates that the configured time domain window length is equal to a respective time length for a respective uplink transmission of the schedule of uplink transmissions within the first time period.

17. The apparatus of claim 15, wherein the processor is further configured to cause the UE to: receive, from the base station, an indication of a configured time domain window length, wherein the configured time domain window length is UE-specific.

18. The apparatus of claim 15, wherein determining the plurality of actual time domain windows comprises applying the plurality of rules according to a set order, the set order comprising: first, if the uplink transmission opportunity is interrupted by a downlink transmission opportunity, determining a separate preliminary time domain window; second, if a length of a previous preliminary time domain window is greater than a maximum duration, determining a separate preliminary time domain window; and third, if an event modifies a schedule of uplink transmissions within the first time period, adjusting any previous preliminary time domain windows affected by the event.

19. The apparatus of claim 15, the plurality of rules further comprising: if any previous preliminary time domain window overlaps with a synchronization signal block transmission, determining a separate preliminary time domain window.

20. The apparatus of claim 15, wherein the processor is further configured to cause the UE to: ​ receiving, from the base station, an indication of a configured time domain window length, the plurality of rules further comprising applying the configured time domain window length to divide a first time period into one or more preliminary time domain windows, wherein the applying the configured time domain window length is performed prior to other rules in the plurality of rules.

21. A computer program product comprising program instructions configured to cause an apparatus to implement a method according to any one of claims 1 to 14.

Images