Slot pattern for repetition of slot types

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive an indication of a timeslot pattern for repetition of a transport block in a timeslot specifying a timeslot type. The UE may receive scheduling information that schedules the repetitions. The UE may transmit or receive the repetitions according to the slot pattern for the specified slot type based at least in part on the repetitions. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Patent Application No. 17 / 885,398, filed on August 10, 2022, entitled “SLOT PATTERN FOR REPETITIONS OF SLOT TYPE” and assigned to the assignee of this application. The disclosure of the prior application is considered a part of and incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and more particularly to techniques and apparatus for indicating a repetitive slot pattern for a specified slot type. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth or transmit power). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region, or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink, CP-OFDM or single carrier frequency division multiplexing (SC-FDM) on the uplink (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM), and supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. Summary of the invention

[0006] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving an indication of a slot pattern for repetitions of a transport block in slots of a specified slot type. The method may include receiving scheduling information for scheduling the repetitions. The method may include sending or receiving the repetitions according to the slot pattern for the specified slot type based at least in part on the repetitions.

[0007] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include sending an indication of a slot pattern for repetitions of a transport block in slots of a specified slot type. The method may include sending the scheduling information scheduling the repetitions. The method may include sending or receiving the repetitions according to the slot pattern for the specified slot type based at least in part on the repetitions.

[0008] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive an indication of a time slot pattern for repetitions of a transmission block in a time slot of a specified time slot type. The one or more processors may be configured to receive scheduling information for scheduling the repetitions. The one or more processors may be configured to send or receive the repetitions according to the time slot pattern for the specified time slot type based at least in part on the repetitions.

[0009] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send an indication of a slot pattern for repetitions of a transport block in a slot of a specified slot type. The one or more processors may be configured to send the scheduling information for scheduling the repetitions. The one or more processors may be configured to send or receive the repetitions according to the slot pattern for the specified slot type based at least in part on the repetitions.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive an indication of a slot pattern for repetitions of a transport block in a slot of a specified slot type. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive scheduling information for scheduling the repetitions. The instruction set, when executed by one or more processors of the UE, may cause the UE to send or receive the repetitions according to the slot pattern for the specified slot type based at least in part on the repetitions.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network entity. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to send an indication of a slot pattern for repetitions of a transmission block in a slot of a specified slot type. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to send the scheduling information for scheduling the repetitions. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to send or receive the repetitions according to the slot pattern for the specified slot type based at least in part on the repetitions.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving an indication of a slot pattern for repetitions of a transport block in slots of a specified slot type. The apparatus may include means for receiving scheduling information for scheduling the repetitions. The apparatus may include means for sending or receiving the repetitions according to the slot pattern for the specified slot type based at least in part on the repetitions.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending an indication of a slot pattern for repetitions of a transport block in slots of a specified slot type. The apparatus may include means for sending the scheduling information scheduling the repetitions. The apparatus may include means for sending or receiving the repetitions according to the slot pattern for the specified slot type based at least in part on the repetitions.

[0014] Aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, wireless communication devices, or processing systems as substantially described with reference to and as illustrated in the drawings and description.

[0015] The foregoing has broadly outlined the features and technical advantages of examples according to the present disclosure in an effort to make the following specific embodiments better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples can be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and method of operation) and the associated advantages will be better understood according to the following description. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to fully understand the above features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate some typical aspects of the present disclosure and should not be considered to limit the scope of the present disclosure, as the description may recognize the existence of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0017] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0018] Figure 2 is a diagram illustrating an example base station communicating with a user equipment (UE) in a wireless network according to the present disclosure.

[0019] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0020] FIG. 4A to FIG. 4C is a diagram illustrating an example of full-duplex communication according to the present disclosure.

[0021] Figure 5 is a diagram illustrating an example of a full-duplex communication mode according to the present disclosure.

[0022] Figure 6 is a diagram illustrating an example of full-duplex communication according to the present disclosure.

[0023] Figure 7 is a diagram illustrating an example of a time slot mode according to the present disclosure.

[0024] Figure 8 is a diagram illustrating an example of a slot pattern for repetition based on a slot type according to the present disclosure.

[0025] Fig. 9 is a diagram of an example associated with indicating a repetitive time slot pattern according to the present disclosure.

[0026] Fig.10 is a diagram illustrating an example of a slot pattern for repetition based on a slot type according to the present disclosure.

[0027] Fig.11 is a diagram illustrating an example of a time slot type split for repetition according to the present disclosure.

[0028] Fig.12 is a diagram illustrating an example of scheduling repetition according to the present disclosure.

[0029] Fig.13 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0030] Fig.14 is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.

[0031] Fig.15 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0032] Fig.16 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0033] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It will be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any amount of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functionality, or structures and functionality other than the various aspects of the disclosure set forth herein or different from the various aspects of the disclosure set forth herein. Any aspect of the present disclosure disclosed herein may be embodied by one or more elements of a claim.

[0034] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination of hardware and software. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0035] Figure 11 is a diagram illustrating an example of a wireless network according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), or other network entities. The base station 110 is an entity that communicates with the UE 120. The base station 110 (sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​a base station 110 or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0036] Base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station.

[0037] The wireless network 100 may be a heterogeneous network including different types of base stations 110, such as macro base stations, pico base stations, femto base stations, or relay base stations. These different types of base stations 110 may have different transmit power levels, different coverage areas, or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts). Figure 1In the example shown, BS 110a may be a macro base station for macrocell 102a, BS 110b may be a pico base station for picocell 102b, and BS 110c may be a femto base station for femtocell 102c. A base station may support one or more (e.g., three) cells. A network controller 130 may be coupled to or communicate with a set of base stations 110 and may provide coordination and control for the base stations 110. The network controller 130 may communicate with the base stations 110 via a backhaul communication link. The base stations 110 may also communicate directly with each other or indirectly via a wireless or wired backhaul communication link.

[0038] In some aspects, the term "base station" (e.g., base station 110) or "network entity" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network entity" may refer to one device configured to perform one or more functions, such as those described herein in conjunction with base station 110. In some aspects, the term "base station" or "network entity" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network entity" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network entity" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network entity" may refer to one of the base station functions, but not another base station function. In this way, a single device may include more than one base station.

[0039] In some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move depending on the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected to each other or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 using any suitable transport network through various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0040] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a base station 110 or a UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown, BS 110d (eg, a relay base station) may communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communications between BS 110a and UE 120d. Base stations 110 that relay communications may be referred to as relay stations, relay base stations, or relays.

[0041] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate via a wireless medium.

[0042] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, or location tags, which may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices, or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, or electrically coupled.

[0043] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may also be referred to as a radio technology or air interface. Frequency may also be referred to as a carrier or frequency channel. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0044] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by base station 110.

[0045] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, or channels by frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. Similar naming issues sometimes arise in conjunction with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in various documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

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

[0047] In view of the above examples, unless otherwise specifically stated, it should be understood that when used herein, the term "sub-6 GHz" can broadly refer to frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that when used herein, the term "millimeter wave" can broadly refer to frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 or FR5, or can be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0048] In some aspects, UE 120 may include a communications manager 140. As described in greater detail elsewhere herein, communications manager 140 may receive an indication of a slot pattern for repetition of transport blocks in slots of a specified slot type. Communications manager 140 may receive scheduling information scheduling the repetitions, and send or receive repetitions according to the slot pattern for the specified slot type based at least in part on the repetitions. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0049] In some aspects, a network entity (e.g., base station 110) may include a communication manager 150. As described in greater detail elsewhere herein, the communication manager 150 may send an indication of a slot pattern for repetition of a transport block in slots of a specified slot type. The communication manager 150 may send scheduling information scheduling the repetitions, and send or receive repetitions according to the slot pattern for the specified slot type based at least in part on the repetitions. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0050] As indicated above, Figure 1are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0051] Figure 2 is a diagram illustrating an example base station 110 communicating with a UE 120 in a wireless network according to the present disclosure. The base station 110 may correspond to Figure 1 Similarly, UE 120 may correspond to Figure 1 UE 120. Base station 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ≥ 1). UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ≥ 1).

[0052] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0053] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from the base station 110 or other base stations 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in a housing.

[0054] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0055] One or more antennas (e.g., antennas 234a to 234t or antennas 252a to 252r) may include or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. An antenna panel, antenna group, set of antenna elements, or antenna array may include one or more antenna elements (in a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or coupled to one or more transmit or receive components (such as Figure 2 One or more antenna elements of one or more components).

[0056] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, or a TX MIMO processor 266. The transceiver may be used by a processor (e.g., the controller / processor 280) and a memory 282 to perform aspects of any of the methods described herein.

[0057] At the base station 110, uplink signals from the UE 120 or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 where applicable, and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein.

[0058] A controller / processor of a network entity (eg, controller / processor 240 of base station 110), controller / processor 280 of UE 120, or Figure 2Any other component of the base station 110 may perform one or more techniques associated with UE subband filtering as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, or Figure 2 Any other component that can execute or guide e.g. Fig.13 The process of 1300 Fig.14 1400 or other processes as described herein. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly or after compilation, conversion, or interpretation) by one or more processors of base station 110 or UE 120, may cause the one or more processors, UE 120, or base station 110 to perform or direct, for example, Fig.13 The process of 1300 Fig.14 The operations of process 1400 or other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, or interpreting instructions, etc.

[0059] In some aspects, the UE 120 includes: means for receiving an indication of a slot pattern for repetition of a transport block in a slot of a specified slot type; means for receiving scheduling information for scheduling the repetition; and / or means for sending or receiving repetitions according to the slot pattern for the specified slot type based at least in part on the repetition. Means for the UE 120 to perform operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0060] In some aspects, a network entity (e.g., base station 110) includes: means for sending an indication of a slot pattern for repetition of a transport block in a slot of a specified slot type; means for sending scheduling information for scheduling the repetition; and / or means for sending or receiving repetitions according to the slot pattern for a specified slot type based at least in part on the repetition. In some aspects, means for the network entity to perform operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

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

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

[0063] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0064] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0065] Figure 33 is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units, such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0066] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium, and the wireless interface being configured to receive signals or transmit signals to one or more of the other units via a wireless transmission medium, or both.

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

[0068] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers, at least in part, according to a functional partition such as that defined by 3GPP. In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0069] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc., based at least in part on functional splitting (e.g., functional splitting defined by 3GPP) (such as lower layer functional splitting). In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0070] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RTRIC 315 configured to support the functionality of the SMO framework 305.

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

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

[0073] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0074] FIG. 4A to FIG. 4C is a diagram illustrating an example of full-duplex (FD) communication according to the present disclosure. Figure 4A The first full-duplex scenario 400 depicted in FIG. 4 includes UE1 402 and two base stations (eg, network entities or TRPs) 404-1, 404-2, wherein UE1 402 is transmitting uplink transmissions to base station 404-1 and is receiving downlink transmissions from base station 404-2. Figure 4A In the first full-duplex scenario 400, FD is enabled for UE1 402 but not for base stations 404-1, 404-2. Figure 4BThe second full-duplex scenario 410 depicted in FIG. 4 includes two UEs (shown as UE1 402-1 and UE2 402-2) and a base station 404, where UE1 402-1 is receiving downlink transmissions from the base station 404 and UE2 402-2 is sending uplink transmissions to the base station 404. In the second full-duplex scenario 410, FD is enabled for the base station 404, but FD is not enabled for UE1 402-1 and UE2 402-2. Figure 4C 4. A third full-duplex scenario 420 including UE1 402 and base station 404 is depicted in FIG. 4, wherein UE1 402 is receiving downlink transmissions from base station 404 and UE1 402 is sending uplink transmissions to base station 404. In the third full-duplex scenario 420, FD is enabled for both UE1 402 and base station 404.

[0075] As indicated above, FIG. 4A to FIG. 4C Some examples are provided. Other examples can be found in the FIG. 4A to FIG. 4C Different than described.

[0076] Figure 5 is a diagram illustrating an example of a full-duplex communication mode 500 according to the present disclosure. In a first mode 502, a first network entity (shown as BS1) and a second network entity (shown as BS2) may be full-duplex devices (e.g., may be capable of communicating in a full-duplex manner). A first UE and a second UE may be half-duplex UEs (e.g., may not be capable of communicating in a full-duplex manner). The first network entity may perform downlink transmissions to the first UE, and uplink transmissions may be received on the first network entity from the second UE. The first network entity may experience self-interference from downlink to uplink based at least in part on the downlink transmissions to the first UE and the uplink transmissions received from the second UE. The first network entity may experience interference from the second network entity. The first UE may experience cross-link interference (CLI) from the second network entity and the second UE.

[0077] In the second mode 504, the first network entity and the second network entity may be full-duplex devices. The first UE and the second UE may be full-duplex UEs. The first network entity may perform downlink transmissions to the first UE, and the first network entity may receive uplink transmissions from the first UE. The first UE may experience SI from uplink to downlink based at least in part on the downlink transmissions from the first network entity and the uplink transmissions to the first network entity. The first UE may experience CLI from the second network entity and the second UE.

[0078] In the third mode 506, the first UE and the second UE may be full-duplex UEs and may communicate in a multi-TRP configuration. The first network entity may receive uplink transmissions from the first UE, and the second network entity may perform downlink transmissions to the first UE and the second UE. The first UE may experience SI from uplink to downlink based at least in part on the uplink transmissions to the first network entity and the downlink transmissions from the second network entity.

[0079] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0080] Figure 6 600 is a diagram illustrating an example of full-duplex communication according to the present disclosure. In some cases, a wireless communication device (such as a UE or a network entity) may support full-duplex operation. Full-duplex operation may include the wireless communication device transmitting and receiving almost simultaneously.

[0081] The UE may operate in an in-band full-duplex mode. In an in-band full-duplex mode, the UE may transmit and receive on the same time and frequency resources. The uplink and downlink may share the same time and frequency resources. For example, in the first full-duplex communication 602, the time and frequency resources used for the uplink may completely overlap with the time and frequency resources used for the downlink. For another example, in the second full-duplex communication 604, the time and frequency resources used for the uplink may partially overlap with the time and frequency resources used for the downlink.

[0082] Full-duplex operation may include a sub-band full-duplex (SBFD) mode. The SBFD mode may also be referred to as a sub-band frequency division duplex mode or a flexible duplex mode. SBFD communication 606 shows that the wireless communication device may transmit and receive at the same time (in the same SBFD time slot), but the wireless communication device may transmit and receive on different frequency domain resources. For example, a network entity may operate in SBFD mode. The network entity may schedule a first UE to receive downlink communications in an SBFD time slot. The network entity may schedule a second UE to send uplink communications in the same SBFD time slot. However, uplink communications may interfere with the first UE that is receiving downlink communications. To address this issue, the downlink time / frequency resources in the SBFD time slot may be separated from the uplink time / frequency resources in the SBFD time slot by a gap (e.g., in time or frequency), which may be used to reduce self-interference and improve latency and uplink coverage. The gap may be a frequency offset or frequency gap (guard band) between the downlink time / frequency resources and the uplink time / frequency resources in the same SBFD time slot.

[0083] In some cases, the timeslot configuration may include a combination of downlink timeslots, uplink timeslots, or SBFD timeslots.

[0084] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The examples described are different.

[0085] Figure 7 is a diagram illustrating an example 700 of a time slot pattern according to the present disclosure.

[0086] To increase reliability, a transport block or other communications may be repeated multiple times, and these may be referred to as repetitions. Repetitions may be used for physical uplink shared channel (PUSCH) communications and physical uplink control channel (PUCCH) communications. Repetitions may be used for physical downlink shared channel (PDSCH). The UE may send or receive repetitions using a configured slot mode. The configured slot mode may include a combination of downlink slots, uplink slots, full-duplex slots, or SBFD slots within the bandwidth of a carrier (e.g., component carrier (CC) bandwidth or channel bandwidth) or bandwidth part (BWP). Example 700 illustrates four repetitions of a transport block in multiple slots, including three SBFD slots and one uplink slot (time division duplex (TDD) slot).

[0087] Although the UE can currently transmit repetitions in slots of different types (TDD vs. SBFD), different slot types may have different uplink qualities due to self-interference and inter-gNB interference present in SBFD slots. In this sense, using the same MCS and transmit power across repetitions in a mix of TDD and SBFD slots may not give the same target performance across the slots.

[0088] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0089] Figure 8 are diagrams illustrating examples 800 and 802 of slot patterns for repetition based on slot type according to the present disclosure.

[0090] According to various aspects described herein, a UE can enhance repeated transmission or reception by using a repetitive time slot pattern based at least in part on a time slot type. In some aspects, a UE can use a repetitive time slot pattern for repetition in a time slot of a specified time slot type. The repetitive time slot pattern can be within and different from a configured time slot pattern (indicated by a time slot format indicator (SFI)) that can be used for all communications. The repetitive time slot pattern can be limited to repetition of only one type of time slot. Therefore, the UE can achieve the same target performance for communications across repetitions.

[0091] In some aspects, the UE may use a repetitive slot pattern for two slot types, but adjust the MCS or transmit power for one of the slot types. Thus, the UE may achieve better target performance across repetitions. For example, the UE may add a power offset to uplink transmissions in an SBFD slot. The maximum transmit power may be higher for the SBFD slot type. The maximum power reduction (MPR) for the SBFD slot type may be lower than the maximum power reduction (MPR) for the TDD slot type. The MPR may be the amount by which the transmit power may be reduced from the maximum power. In another example, the repetitions in the SBFD slot may have a lower MCS than the repetitions in the TDD slot. The network entity may configure a greater transmit power for the repetitions in the SBFD than for the TDD slot. For PUSCH communications, the network entity may experience SI and inter-gNB CLI, while for the physical downlink shared channel (PDSCH), the UE may experience inter-UE CLI. In some aspects, the UE may receive an indication of the MCS for a specified slot type, wherein the MCS for the specified slot type is different from the MCS for another slot type. The UE may determine the size of the transport block based at least in part on the MCS.

[0092] In some aspects, for PxSCH (PUSCH or PDSCH) repetition across different slot types, the network entity may send an indication of different MCS values ​​for SBFD slots and TDD slots. The indication may be explicit, with two MCS bit fields in the downlink control information (DCI), or with one MCS value and one difference (MCs increment). The indication may be based on the RRC configuration (e.g., a fixed MCS increment). This may be applicable to RRC-configured granted PUSCH (CG-PUSCH). The same MCS bit field in the DCI may be interpreted differently in each slot type. For example, there may be two different MCS lookup tables or two RRC-configured MCS tables for TDD and SBFD slots. In some aspects, the transport block size may be determined based on the minimum value of the MCS for the slot type. There may be two transport block sizes for these two slot types, which may be applicable to a single DCI that schedules multiple PDSCH or PUSCH transport blocks. Note that PxSCH repetition can refer to higher layer configured repetition (e.g., semi-persistent (SPS) or CG) or dynamically granted repetition (e.g., downlink and uplink DCI formats). PUSCH repetition can refer to PUSCH repetition type A and type B. Repetition can be inter-slot or intra-slot (PUSCH type B).

[0093] In some aspects, the UE may control the amount of each slot type in a repeating slot pattern. For example, a repeating slot pattern may allow three full-duplex (eg, SBFD) slots and one TDD slot. Thus, the UE may better control the target performance across repetitions.

[0094] Example 800 illustrates a configured slot pattern of six slots. The network entity may send an indication of a repeating slot pattern. Example 800 illustrates that the repeating slot pattern is limited to a specified slot type (e.g., SBFD), where four repetitions are sent only in slots of the specified slot type. TDD slots for uplink (UL) are not used. In some aspects, the specified slot type may be the slot type of the slot in which the repetition begins. For example, if the first repetition (for PUSCH or PDSCH) is a full-duplex slot (e.g., UL subband), the remaining slots used for repetition are limited to full-duplex slot types. The specified slot type to be used may be based on a fixed slot offset from a scheduling DCI (to indicate the slot type), or the specified slot type may be the slot type of the first available slot. The indication from the network entity may be an RRC message (e.g., repetition = "SBFD slot") or a DCI that explicitly specifies the specified slot type.

[0095] Example 802 shows a repetition slot pattern where the first three repetitions are sent in a SBFD slot type and the fourth repetition is sent in a TDD slot. However, the UE adjusts the MCS and / or transmit power in the TDD slot so that the target performance is closer to the SBFD slot.

[0096] As indicated above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 The examples described are different.

[0097] Fig. 9 is a diagram of an example 900 associated with indicating a repeating time slot pattern according to the present disclosure. Fig. 9 As shown, a network entity 910 (e.g., base station 110) can communicate with a UE 920 (e.g., UE 120). In some aspects, the network entity 910 and the UE 920 can be part of a wireless network (e.g., wireless network 100). The UE 920 and the network entity 910 can be in communication with each other. Fig. 9 The illustrated operations have previously established a wireless connection. The network entity 910 may be operating in SBFD mode (e.g., transmitting and receiving simultaneously on different frequency domain resources). In some aspects, the UE 920 may be operating in half-duplex mode. In some other aspects, the UE 120 may be operating in full-duplex mode.

[0098] As indicated by reference numeral 925, the network entity 910 may send an SFI to indicate the configured slot pattern. As indicated by reference numeral 930, the network entity 910 may send an indication of a repetition slot pattern for repetition of the transport block. The repetition slot pattern may explicitly or implicitly indicate a specified slot type for repetition. The explicit indication may specify the specified slot type. The implicit indication may indicate that the slot type of the identified slot or the first available slot will be the specified slot type.

[0099] As shown by reference numeral 935, the network entity 910 may send scheduling information for scheduling repetitions (or for repeated transport blocks). The scheduling information may include DCI for dynamic scheduling or higher layer configuration. The higher layer configuration may include an RRC message for configuring SPS or CG. As shown by reference numeral 940, the network entity 910 and the UE 920 may use a repeated time slot pattern to send or receive repetitions of transport blocks.

[0100] As indicated above, Fig. 9 are provided as examples. Other examples can be found in the Fig. 9 The examples described are different.

[0101] Fig.10 are diagrams illustrating examples 1000 , 1002 , and 1004 of slot patterns for repetition based on slot type according to the present disclosure.

[0102] Example 1000 shows a configured slot pattern of six slots. The UE may identify five repetitive slots for a transport block (in PDSCH or PUSCH). In example 1000, these slots are the last five consecutive slots, which include three SBFD slots, one TDD slot (for PUSCH), and another SBFD slot. In some aspects, the UE may count repetitions in slot types other than the specified slot type in the repetition count of the transport block and discard (e.g., not send) repetitions of other slot types. In example 1000, the specified slot type is SBFD, and therefore repetition #4 in the TDD slot type is counted in the repetition count of the transport block, but discarded. Alternatively, the UE may not count repetitions in slot types other than the specified slot type in the repetition count of the transport block. The UE may still discard repetitions of other slot types. The counter may only count repetitions that are not discarded.

[0103] In some aspects, the count may be for physical time slots, which are time slots that exist in time according to the configured time slot pattern. Example 1002 shows an example of a repeat count in a configured TDD time slot pattern with physical time slots. The count may start at the first time slot and continue for five consecutive physical time slots (repeat count: 5). In some aspects, the count may be only for available time slots. That is, the UE may identify time slots based on time and / or frequency resource availability. Example 1004 shows an example of counting available time slots. Two uplink time slots are available time slots with unavailable time slots between them. The count may start at the first available time slot and continue with any other available time slot (repeat count: 2). The count of physical time slots or available time slots may be for PDSCH repetitions or PUSCH repetitions.

[0104] In more detail, as a first option, if physical slot counting is enabled, the UE may identify a set of consecutive (consecutive) time slots for PUSCH or PDSCH repetitions. The repetition counter may be incremented in each time slot. If a repetition occurs in a time slot of another type (not a specified time slot type), the repetition is discarded. The time slot type for discarding repetitions may be an uplink time slot type, a SBFD time slot type, or a downlink time slot type. As a second option, if physical slot counting is enabled, a set of consecutive time slots for PUSCH or PDSCH repetitions is identified. If a repetition occurs in a time slot of another time slot type, the repetition is discarded. The repetition counter is incremented only if the repetition is not discarded.

[0105] As a third option, if the available slot count is enabled, the UE may identify a set of slots for PUSCH repetition based on time and / or frequency resource availability. For PDSCH repetition based on the available slot count, if the slot has sufficient time and / or frequency resources for PDSCH transmission based on the RRC TDD-DL-UL slot mode and UL-DL subband configuration, the slot may be considered available. Note that the identified slots for PDSCH may not be continuous. The repetition counter may be incremented in each identified slot. If a repetition occurs in a slot of another slot type, the repetition is discarded. As a fourth option, if the available slot count is enabled, the UE may identify a set of slots for PUSCH or PDSCH repetition based on time and / or frequency resource availability. If a repetition occurs in a slot of another slot type, the repetition is discarded. The repetition counter may be incremented only if the repetition is not discarded. These options are examples and may not indicate any priority order.

[0106] As indicated above, Fig.10 are provided as examples. Other examples can be found in the Fig.10 The examples described are different.

[0107] Fig.11 is a diagram illustrating an example 1100 of splitting slot types for repetition according to the present disclosure.

[0108] In some aspects, to overcome the low signal to interference plus noise ratio (SINR) of the SBFD time slot, the network entity may indicate more repetitions for the SBFD time slot compared to the TDD time slot. For example, the network entity may send an indication of a repetition time slot pattern (for PUSCH or PDSCH) that divides the repetition of the transport block into two quantities for two time slot types. The indication may indicate a first repetition amount N1 for the first time slot type (e.g., SBFD) and a second repetition amount N2 for the second time slot type (e.g., TDD). The sum of N1 and N2 may be the total amount of repetitions configured for the transport block.

[0109] Example 1100 shows a configured slot pattern of 10 slots. The network entity may send an indication specifying N1 as 4 and specifying N2 as 2. Example 1100 shows "F Rep 1 / 4" in a SBFD slot for using 1 of 4 repetitions of a SBFD slot. After 3 repetitions in a SBFD slot, there is "T Rep 1 / 2" in a TDD slot showing 1 of 2 repetitions of a TDD slot being used. Example 1100 further shows how the remaining repetitions are counted. TDD and SBFD repetitions may have the same resource allocation or different resource allocations.

[0110] In some aspects, the network entity may provide the indication in a time domain resource allocation (TDRA) table, in a DCI, or in a medium access control control element (MACCE) via RRC signaling. In some aspects, the TDRA table may have multiple sets (of N1 and N2), and the DCI may explicitly point to one of the sets. In some aspects, the TDRA or DCI may indicate a total number of repetitions of a transport block, N, and for each N, there may be an RRC table that specifies the values ​​of N1 and N2. The UE may determine the size of the transport block by combining N1 and N2.

[0111] The UE may use a slot counter for each slot type. For example 1100, this may include a counter for SBFD slots and a counter for TDD slots. The use of separate counters may be applicable to the available slot counts and may provide more flexibility and adjustments to existing configured slot patterns.

[0112] As indicated above, Fig.11 are provided as examples. Other examples can be found in the Fig.11 The examples described are different.

[0113] Fig.12 is a diagram illustrating an example 1200 of scheduling repetitions according to the present disclosure.

[0114] In some aspects, when some frequency resources for SBFD slot repetition are unavailable (e.g., guard bands or subbands in the opposite direction), the UE may determine that the transport block size is the same for the SBFD repetition, and the UE may rate match (allocate data for transmission) or puncture (use data scheduled for another communication) the PxSCH communication for the unavailable resources. Example 1200 illustrates repetitions transmitted in resources scheduled for PDSCH communication. In some aspects, the UE may scale the transport block size based on the available resource blocks in the SBFD slot.

[0115] As indicated above, Fig.12 are provided as examples. Other examples can be found in the Fig.12 The examples described are different.

[0116] Fig.13 is a diagram illustrating an example process 1300 performed, for example, by a UE according to the present disclosure. The example process 1300 is one in which a UE (eg, UE 120, UE 920) performs operations associated with using a repetitive slot pattern for repetition based on a slot type.

[0117] like Fig.13As shown, in some aspects, process 1300 may include receiving an indication of a slot pattern for repetition of transport blocks in slots of a specified slot type (block 1310). For example, a UE (e.g., using Fig.15 The communication manager 1508 and / or receiving component 1502 depicted in FIG. 1504 may receive an indication of a slot pattern for repetition of transport blocks in slots of a specified slot type, as described above.

[0118] like Fig.13 As further shown, in some aspects, process 1300 may include receiving scheduling information for scheduling repetitions (block 1320). For example, a UE (eg, using Fig.15 The communication manager 1508 and / or receiving component 1502 depicted in FIG. 1504 may receive scheduling information for scheduling repetitions, as described above.

[0119] like Fig.13 As further shown, in some aspects, process 1300 may include sending or receiving repetitions according to a slot pattern for a specified slot type based at least in part on the repetitions (block 1330). Fig.15 The communication manager 1508 and / or the transmitting component 1504 depicted in FIG. 1504 may transmit or receive repetitions according to a slot pattern based at least in part on the repetitions for a specified slot type, as described above.

[0120] Process 1300 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0121] In a first aspect, the repetitions are limited to a specified time slot type, and the specified time slot type is based at least in part on a fixed time slot type.

[0122] In a second aspect, alone or in combination with the first aspect, the repetitions are limited to a specified slot type, and the specified slot type is based at least in part on a slot type of the first available slot or a slot type indicated by a slot offset from the scheduling information.

[0123] In a third aspect, alone or in combination with one or more of the first and second aspects, the repetitions are limited to specified time slot types and the scheduling information indicates the specified time slot types.

[0124] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the process 1300 includes receiving a radio resource control message that configures the UE to use only a specified time slot type.

[0125] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the designated time slot type is time division duplex or sub-band full duplex.

[0126] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 1300 includes counting repetitions in time slots of other time slot types other than the specified time slot type into a repetition count of a transmission block, and discarding repetitions in time slots of other time slot types.

[0127] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, process 1300 includes skipping counting repetitions in time slots of other time slot types other than the specified time slot type into a repetition count of a transmission block, and discarding repetitions in time slots of other time slot types.

[0128] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 1300 includes including repetitions in physical time slots of a specified time slot type and repetitions in physical time slots of other time slot types other than the specified time slot type into a repetition count of a transmission block.

[0129] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the physical time slots are contiguous physical time slots.

[0130] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, a timeslot type is designated for transmission on a physical uplink shared channel.

[0131] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, a time slot type is designated for transmission on a physical downlink shared channel.

[0132] In a twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, process 1300 includes: counting repetitions in available time slots of a specified time slot type and repetitions in available time slots of other time slot types except the specified time slot type into a repetition count of a transmission block.

[0133] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, a time slot type is designated for transmission on a physical uplink shared channel.

[0134] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, a time slot type is designated for transmission on a physical downlink shared channel.

[0135] In a fifteenth aspect, either alone or in combination with one or more of aspects one to fourteen, process 1300 comprises: counting repetitions in physical time slots of a specified time slot type into a repetition count of a transmission block, and skipping counting repetitions in physical time slots of other time slot types except the specified time slot type into the repetition count of the transmission block.

[0136] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, a time slot type is designated for transmission on a physical uplink shared channel.

[0137] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, a time slot type is designated for transmission on a physical downlink shared channel.

[0138] In an eighteenth aspect, either alone or in combination with one or more of aspects one to seventeen, process 1300 comprises: counting repetitions in available time slots of a specified time slot type into a repetition count of a transmission block, and skipping counting repetitions in available time slots of other time slot types except the specified time slot type into the repetition count of the transmission block.

[0139] In a nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, a time slot type is designated for transmission on a physical uplink shared channel.

[0140] In a twentieth aspect, alone or in combination with one or more of the first to nineteenth aspects, a time slot type is designated for transmission on a physical downlink shared channel.

[0141] In a twenty-first aspect, either alone or in combination with one or more of the first to twentieth aspects, process 1300 includes discarding repetitions in slots of other slot types except for a designated slot type.

[0142] In aspect 22, either alone or in combination with one or more of aspects 1 to 21, time slots of a specified time slot type are a first quantity of time slots and repetitions in time slots of another time slot type are a second quantity of time slots, and the sum of the first quantity of time slots and the second quantity of time slots is equal to the total repetition count of the transport block.

[0143] In a twenty-third aspect, either alone or in combination with one or more of the first to twenty-second aspects, a designated time slot type is sub-band full duplex and another time slot type is time division duplex.

[0144] In a twenty-fourth aspect, either alone or in combination with one or more of aspects one to twenty-third, process 1300 includes using a first counter to count repetitions in time slots of a specified time slot type, and using a second counter to count repetitions in time slots of another time slot type.

[0145] In aspect twenty-fifth, alone or in combination with one or more of aspects one to twenty-fourth, process 1300 comprises: receiving an indication of an MCS for a specified time slot type, wherein the MCS for the specified time slot type is different from the MCS for another time slot type; and determining a size of a transport block based at least in part on the MCS.

[0146] although Fig.13 Example blocks of process 1300 are shown, but in some aspects, process 1300 may include Fig.13 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1300. Additionally or alternatively, two or more of the blocks in the process 1300 may be performed in parallel.

[0147] Fig.14 is a diagram illustrating an example process 1400, performed, for example, by a network entity, according to the present disclosure. The example process 1400 is one in which a network entity (eg, base station 110, network entity 910) performs operations associated with indicating a repeating slot pattern for repetition based on a slot type.

[0148] like Fig.14 As shown, in some aspects, process 1400 may include sending an indication of a slot pattern for repetition of transport blocks in slots of a specified slot type (block 1410). For example, a network entity (e.g., using Fig.16 The communication manager 1608 and / or the transmitting component 1604 depicted in FIG. 1 may transmit an indication of a slot pattern for repetition of transport blocks in slots of a specified slot type, as described above.

[0149] like Fig.14 As further shown, in some aspects, process 1400 may include sending scheduling information for scheduling repetitions (block 1420). For example, a network entity (e.g., using Fig.16 The communication manager 1608 and / or the sending component 1604 depicted in FIG. 10 can send scheduling information for the scheduled repetitions, as described above.

[0150] like Fig.14 As further shown, in some aspects, process 1400 may include sending or receiving repetitions according to a time slot pattern for a specified time slot type based at least in part on the repetitions (block 1430). Fig.16The communication manager 1608 and / or the transmitting component 1604 depicted in FIG. 10 can transmit or receive repetitions according to a slot pattern based at least in part on the repetitions for a specified slot type, as described above.

[0151] Process 1400 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0152] In a first aspect, the repetitions are limited to a specified timeslot type and the scheduling information indicates the specified timeslot type.

[0153] In a second aspect, alone or in combination with the first aspect, process 1400 includes sending an indication of an MCS for a specified timeslot type.

[0154] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1400 includes sending an indication of a first amount of slots of a specified slot type and a second amount of slots of another slot type via a resource allocation or DCI.

[0155] although Fig.14 Example blocks of process 1400 are shown, but in some aspects, process 1400 may include Fig.14 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1400. Additionally or alternatively, two or more blocks of the blocks of process 1400 may be performed in parallel.

[0156] Fig.15 is a diagram of an example apparatus 1500 for wireless communication according to the present disclosure. Apparatus 1500 may be a UE (e.g., UE 120, UE 920), or a UE may include apparatus 1500. In some aspects, apparatus 1500 includes a receiving component 1502 and a transmitting component 1504, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1500 may communicate with another apparatus 1506 (such as a UE, a base station, or another wireless communication device) using receiving component 1502 and transmitting component 1504. As further shown, apparatus 1500 may include a communication manager 1508. Communication manager 1508 may control and / or otherwise manage one or more operations of receiving component 1502 and / or transmitting component 1504. In some aspects, communication manager 1508 may include a communication manager 1508 in conjunction with Figure 2 The communication manager 1508 may be one or more antennas, modems, controllers / processors, memories, or combinations thereof of the described UE. Figure 1 and Figure 2 The communication manager 140 depicted in or similar to Figure 1 and Figure 2 For example, in some aspects, the communication manager 1508 can be configured to perform one or more of the functions described as being performed by the communication manager 140. In some aspects, the communication manager 1508 can include a receiving component 1502 and / or a sending component 1504. The communication manager 140 can include a repeating component 1510 and / or a counting component 1512, among others.

[0157] In some aspects, the apparatus 1500 may be configured to perform Figures 1 to 12 Additionally or alternatively, the apparatus 1500 may be configured to perform one or more processes described herein, such as Fig.13 The process 1300. In some aspects, Fig.15 The device 1500 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.15 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0158] The receiving component 1502 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1506. The receiving component 1502 may provide the received communications to one or more other components of the device 1500. In some aspects, the receiving component 1502 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1500. In some aspects, the receiving component 1502 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0159] Transmit component 1504 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1506. In some aspects, one or more other components of device 1500 may generate communications and may provide the generated communications to transmit component 1504 for transmission to device 1506. In some aspects, transmit component 1504 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1506. In some aspects, transmit component 1504 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1504 can be co-located with the receive component 1502 in a transceiver.

[0160] The receiving component 1502 can receive an indication of a slot pattern for repetition of transport blocks in slots of a specified slot type. The receiving component 1502 can receive scheduling information for scheduling the repetitions. The sending component 1504 can send or receive the repetitions according to the slot pattern for the specified slot type based at least in part on the repetitions.

[0161] The receiving component 1502 can receive a radio resource control message that configures the UE to use only a specified slot type. The repeating component 1510 can count repetitions in slots of other slot types except the specified slot type into a repetition count of the transport block. The repeating component 1510 can discard repetitions in slots of other slot types.

[0162] The counting component 1512 can skip counting repetitions in slots of other slot types except the specified slot type into the repetition count of the transport block. The repeating component 1510 can discard repetitions in slots of other slot types.

[0163] The counting component 1512 can include repetitions in physical time slots of the specified time slot type and repetitions in physical time slots of other time slot types except the specified time slot type in the repetition count of the transport block. The counting component 1512 can include repetitions in available time slots of the specified time slot type and repetitions in available time slots of other time slot types except the specified time slot type in the repetition count of the transport block.

[0164] The counting component 1512 can include repetitions in physical slots of the specified slot type in the repetition count of the transport block. The counting component 1512 can skip including repetitions in physical slots of other slot types than the specified slot type in the repetition count of the transport block.

[0165] The counting component 1512 can count repetitions in available time slots of the specified time slot type into a repetition count of the transport block. The counting component 1512 can skip counting repetitions in available time slots of other time slot types except the specified time slot type into a repetition count of the transport block. The repeating component 1510 can discard repetitions in time slots of other time slot types except the specified time slot type.

[0166] The counting component 1512 can use a first counter to count repetitions in slots of a specified slot type and a second counter to count repetitions in slots of another slot type.

[0167] Receiving component 1502 can receive an indication of a modulation and coding scheme (MCS) for a specified slot type, wherein the MCS for the specified slot type is different than the MCS for another slot type.Repeating component 1510 can determine a size of a transport block based at least in part on the MCS.

[0168] Fig.15 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.15 The components shown may include additional components, fewer components, different components, or components arranged in a different manner. Fig.15 Two or more components shown may be implemented in a single component, or Fig.15 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.15 The assembly of (one or more) components shown may be described as being executable by Fig.15 Another collection of components shown performs one or more functions.

[0169] Fig.16 is a diagram of an example apparatus 1600 for wireless communication according to the present disclosure. Apparatus 1600 may be a network entity (e.g., base station 110, network entity 910), or a network entity may include apparatus 1600. In some aspects, apparatus 1600 includes a receiving component 1602 and a transmitting component 1604, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1600 may communicate with another apparatus 1606 (such as a UE, a base station, or another wireless communication device) using receiving component 1602 and transmitting component 1604. As further shown, apparatus 1600 may include a communication manager 1608. Communication manager 1608 may control and / or otherwise manage one or more operations of receiving component 1602 and / or transmitting component 1604. In some aspects, communication manager 1608 may include a communication manager 1608 in conjunction with Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the described network entities. The communications manager 1608 may be Figure 1 and Figure 2 The communication manager 150 depicted in or similar to Figure 1 and Figure 2 For example, in some aspects, the communication manager 1608 can be configured to perform one or more of the functions described as being performed by the communication manager 150. In some aspects, the communication manager 1608 can include a receiving component 1602 and / or a sending component 1604. The communication manager 1608 can include a generating component 1610, among others.

[0170] In some aspects, the apparatus 1600 may be configured to perform Figures 1 to 12 Additionally or alternatively, the apparatus 1600 may be configured to perform one or more processes described herein, such as Fig.14 The process 1400. In some aspects, Fig.16 The device 1600 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.16 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0171] The receiving component 1602 may receive communications from the device 1606, such as reference signals, control information, data communications, or a combination thereof. The receiving component 1602 may provide the received communications to one or more other components of the device 1600. In some aspects, the receiving component 1602 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1600. In some aspects, the receiving component 1602 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described network entities.

[0172] Transmit component 1604 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1606. In some aspects, one or more other components of device 1600 may generate communications and may provide the generated communications to transmit component 1604 for transmission to device 1606. In some aspects, transmit component 1604 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1606. In some aspects, transmit component 1604 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network entities. In some aspects, the transmit component 1604 can be co-located with the receive component 1602 in a transceiver.

[0173] The sending component 1604 may send an indication of a slot pattern for repetition of transport blocks in slots of a specified slot type. The generating component 1610 may generate the indication based at least in part on the configured slot pattern, transport block size, traffic conditions, channel conditions, UE capabilities, and / or slot type configuration. The sending component 1604 may send scheduling information for scheduling repetitions. The sending component 1604 may send or receive repetitions according to the slot pattern for the specified slot type based at least in part on the repetitions.

[0174] Transmitting component 1604 can transmit an indication of the MCS for the specified slot type.Transmitting component 1604 can transmit an indication of a first amount of slots of the specified slot type and a second amount of slots of another slot type via a resource assignment or downlink control information.

[0175] Fig.16 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.16 The components shown may include additional components, fewer components, different components, or components arranged in a different manner. Fig.16 Two or more components shown may be implemented in a single component, or Fig.16 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.16 The assembly of (one or more) components shown may be described as being executable by Fig.16 Another collection of components shown performs one or more functions.

[0176] The following provides an overview of some aspects of the disclosure:

[0177] Aspect 1: A wireless communication method performed by a user equipment (UE), comprising: receiving an indication of a time slot pattern for repetition of a transmission block in a time slot of a specified time slot type; receiving scheduling information for scheduling the repetition; and sending or receiving the repetition according to the time slot pattern for the specified time slot type based at least in part on the repetition.

[0178] Aspect 2: The method according to aspect 1, wherein the repetition is limited to the specified time slot type, and the specified time slot type is based at least in part on a fixed time slot type.

[0179] Aspect 3: A method according to aspect 1, wherein the repetition is limited to the specified time slot type, and the specified time slot type is at least partially based on the time slot type of the first available time slot or the time slot type indicated by the time slot offset from the scheduling information.

[0180] Aspect 4: The method according to aspect 1, wherein the repetition is limited to the designated time slot type and the scheduling information indicates the designated time slot type.

[0181] Aspect 5: The method according to any one of aspects 1 to 4 further includes: receiving a radio resource control message configuring the UE to use only the designated time slot type.

[0182] Aspect 6: The method according to any one of aspects 1 to 5, wherein the designated time slot type is time division duplex or sub-band full duplex.

[0183] Aspect 7: The method according to any one of Aspects 1 to 6 further includes: counting repetitions in time slots of other time slot types except the specified time slot type into the repetition count of the transmission block; and discarding the repetitions in the time slots of other time slot types.

[0184] Aspect 8: The method according to any one of Aspects 1 to 6 further includes: skipping counting repetitions in time slots of other time slot types except the specified time slot type into the repetition count of the transmission block; and discarding the repetitions in the time slots of other time slot types.

[0185] Aspect 9: The method according to any one of Aspects 1 to 6 further includes: counting repetitions in physical time slots of the specified time slot type and repetitions in physical time slots of other time slot types except the specified time slot type into the repetition count of the transmission block.

[0186] Aspect 10: The method according to aspect 9, wherein the physical time slots are consecutive physical time slots.

[0187] Aspect 11: The method according to aspect 9, wherein the designated time slot type is used for transmission on a physical uplink shared channel.

[0188] Aspect 12: The method according to aspect 9, wherein the designated time slot type is used for transmission on a physical downlink shared channel.

[0189] Aspect 13: The method according to any one of Aspects 1 to 6 further includes: counting the repetitions in the available time slots of the specified time slot type and the repetitions in the available time slots of other time slot types except the specified time slot type into the repetition count of the transmission block.

[0190] Aspect 14: The method according to aspect 13, wherein the designated time slot type is used for transmission on a physical uplink shared channel.

[0191] Aspect 15: The method according to aspect 13, wherein the designated time slot type is used for transmission on a physical downlink shared channel.

[0192] Aspect 16: The method described in any one of Aspects 1-6 further includes: counting repetitions in physical time slots of the specified time slot type into the repetition count of the transmission block; and skipping counting repetitions in physical time slots of other time slot types except the specified time slot type into the repetition count for the transmission block.

[0193] Aspect 17: The method according to aspect 16, wherein the designated time slot type is used for transmission on a physical uplink shared channel.

[0194] Aspect 18: The method according to aspect 16, wherein the designated time slot type is used for transmission on a physical downlink shared channel.

[0195] Aspect 19: The method according to any one of Aspects 1-6 also includes: counting repetitions in available time slots of the specified time slot type into the repetition count of the transmission block; and skipping counting repetitions in available time slots of other time slot types except the specified time slot type into the repetition count for the transmission block.

[0196] Aspect 20: The method according to aspect 19, wherein the designated time slot type is used for transmission on a physical uplink shared channel.

[0197] Aspect 21: The method according to aspect 19, wherein the designated time slot type is used for transmission on a physical downlink shared channel.

[0198] Aspect 22: The method according to any one of Aspects 1 to 212 further includes: discarding repetitions in time slots of other time slot types except the designated time slot type.

[0199] Aspect 23: A method according to any one of Aspects 1 to 22, wherein the time slots of the specified time slot type are a first number of time slots, and the repetitions in the time slots of another time slot type are a second number of time slots, and wherein the sum of the first number of time slots and the second number of time slots is equal to the total repetition count of the transmission block.

[0200] Aspect 24: The method according to aspect 23, wherein the designated time slot type is sub-band full duplex and the another time slot type is time division duplex.

[0201] Aspect 25: The method according to aspect 23 or 24 further includes: using a first counter to count the repetitions in the time slots of the specified time slot type, and using a second counter to count the repetitions in the time slots of the other time slot type.

[0202] Aspect 26: The method according to aspects 7 to 25 also includes: receiving an indication of a modulation and coding scheme (MCS) for the specified time slot type, wherein the MCS for the specified time slot type is different from the MCS for another time slot type; and determining the size of the transmission block at least in part based on the MCS.

[0203] Aspect 27: A method of wireless communication performed by a network entity, comprising: sending an indication of a time slot pattern for repetition of a transmission block in a time slot of a specified time slot type; sending scheduling information for scheduling the repetition; and sending or receiving the repetition according to the time slot pattern for the specified time slot type based at least in part on the repetition.

[0204] Aspect 28: The method according to aspect 27, wherein the repetition is limited to the specified time slot type and the scheduling information indicates the specified time slot type.

[0205] Aspect 29: The method according to aspect 27 or 28, further comprising: sending an indication of a modulation and coding scheme (MCS) for the specified time slot type.

[0206] Aspect 30: The method according to any one of aspects 27 to 29 further comprises: sending an indication of the first amount of time slots of the specified time slot type and the second amount of time slots of another time slot type via resource allocation or downlink control information.

[0207] Aspect 31: An apparatus for performing wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 1-30.

[0208] Aspect 32: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 30.

[0209] Aspect 33: An apparatus for wireless communication, comprising: at least one component for performing the method according to one or more of aspects 1 to 30.

[0210] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 30.

[0211] Aspect 35: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 30.

[0212] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of these aspects.

[0213] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware or hardware and software. "Software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures or functions, etc., whether it is described in software, firmware, middleware, microcode, hardware description language or other terms. As used herein, "processor" is implemented by hardware or a combination of hardware and software. It will be apparent that the system or method described herein can be implemented in different forms of hardware or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods does not limit various aspects. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software codes, because those skilled in the art will understand that software and hardware can be designed to implement these systems or methods based at least in part on the description herein.

[0214] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0215] Although specific combinations of features are stated in the claims or disclosed in the specification, these combinations are not intended to limit the disclosure of the various aspects. Many of these features can be combined in ways not specifically described in the claims or disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of these items (including a single member). As an example, "at least one of a, b, or c" is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0216] Any element, action or instruction used herein should not be interpreted as key or necessary unless clearly stated. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one project is intended to be referred to, the phrase "only one" or similar terms are used. In addition, as used herein, the terms "have", "have", "have" and similar terms are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: receiving an indication of a slot pattern for repetition of transport blocks in slots of a specified slot type; receiving scheduling information for scheduling the repetition; and The repetitions are sent or received according to the slot pattern based at least in part on the repetitions being for the designated slot type.

2. The UE of claim 1, wherein the repetition is limited to the specified timeslot type, and the specified timeslot type is based at least in part on a fixed timeslot type.

3. The UE of claim 1 , wherein the repetition is limited to the specified time slot type, and the specified time slot type is based at least in part on a time slot type of the first available time slot or a time slot type indicated by a time slot offset from the scheduling information. 4 . The UE of claim 1 , wherein the repetition is limited to the designated time slot type and the scheduling information indicates the designated time slot type. 5 . The UE of claim 1 , wherein the one or more processors are configured to receive a radio resource control message that configures the UE to use only the specified time slot type. The UE according to claim 1 , wherein the designated time slot type is time division duplex or sub-band full duplex.

7. The UE of claim 1, wherein the one or more processors are configured to: counting repetitions in time slots of other time slot types except the designated time slot type into a repetition count of the transport block; and Said repetitions in said time slots of other time slot types are discarded.

8. The UE of claim 1, wherein the one or more processors are configured to: skipping counting repetitions in time slots of other time slot types except the specified time slot type into a repetition count of the transport block; and Said repetitions in said time slots of other time slot types are discarded.

9. The UE of claim 1, wherein the one or more processors are configured to count repetitions in physical time slots of the designated time slot type and repetitions in physical time slots of other time slot types except the designated time slot type into a repetition count of the transport block.

10. The UE according to claim 9, wherein the physical time slots are consecutive physical time slots.

11. The UE of claim 9, wherein the designated time slot type is used for transmission on a physical uplink shared channel.

12. The UE of claim 9, wherein the designated time slot type is used for transmission on a physical downlink shared channel.

13. The UE of claim 1, wherein the one or more processors are configured to count repetitions in available time slots of the designated time slot type and repetitions in available time slots of other time slot types except the designated time slot type into a repetition count of the transport block.

14. The UE of claim 13, wherein the designated timeslot type is used for transmission on a physical uplink shared channel.

15. The UE of claim 13, wherein the designated time slot type is used for transmission on a physical downlink shared channel.

16. The UE of claim 1, wherein the one or more processors are configured to: counting the repetitions in the physical timeslots of the specified timeslot type into the repetition count of the transport block; and Skipping counting repetitions in physical timeslots of other timeslot types except the designated timeslot type into the repetition count of the transport block.

17. The UE of claim 16, wherein the designated timeslot type is used for transmission on a physical uplink shared channel.

18. The UE of claim 16, wherein the designated time slot type is used for transmission on a physical downlink shared channel.

19. The UE of claim 1, wherein the one or more processors are configured to: counting repetitions in available time slots of the specified time slot type into a repetition count of the transport block; and Counting repetitions in available time slots of other time slot types except the designated time slot type into the repetition count of the transport block is skipped.

20. The UE of claim 19, wherein the designated timeslot type is used for transmission on a physical uplink shared channel.

21. The UE of claim 19, wherein the designated timeslot type is used for transmission on a physical downlink shared channel.

22. The UE of claim 1, wherein the one or more processors are configured to discard repetitions in slots of other slot types except the designated slot type.

23. The UE of claim 1, wherein the time slots of the specified time slot type are a first quantity of time slots and the repetitions in time slots of another time slot type are a second quantity of time slots, and wherein the sum of the first quantity of time slots and the second quantity of time slots is equal to a total repetition count of the transport block.

24. The UE of claim 23, wherein the designated time slot type is sub-band full duplex, and the another time slot type is time division duplex.

25. The UE of claim 23, wherein the one or more processors are further configured to use a first counter to count the repetitions in the time slots of the specified time slot type, and use a second counter to count the repetitions in the time slots of the other time slot type.

26. The UE of claim 1, wherein the one or more processors are configured to: receiving an indication of a modulation and coding scheme (MCS) for the designated timeslot type, wherein the MCS for the designated timeslot type is different from an MCS for another timeslot type; and A size of the transport block is determined based at least in part on the MCS.

27. A network entity for wireless communication, comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: sending an indication of a slot pattern for repetition of transport blocks in slots of a specified slot type; sending scheduling information for scheduling the repetition; and The repetitions are sent or received according to the slot pattern based at least in part on the repetitions being for the designated slot type.

28. The network entity of claim 27, wherein the repetition is limited to the specified time slot type and the scheduling information indicates the specified time slot type.

29. The network entity of claim 27, wherein the one or more processors are configured to send an indication of a modulation and coding scheme (MCS) for the specified timeslot type.

30. The network entity of claim 27, wherein the one or more processors are configured to send an indication of the first amount of timeslots of the specified timeslot type and the second amount of timeslots of another timeslot type via a resource allocation or downlink control information.

Images