Transport block processing chain and method for processing data to be mapped into transport block

Abstract

This invention discloses a system and method related to a transport block processing chain for a transmitter. A code block determination circuit can be configured to determine the size of a code block mapped across multiple time slots of a radio entity shared channel (TBoMS) based on a TBoMS configuration. A rate matching circuit can be configured to rate match the bits of the code block with several bits available in a predetermined number of time slots across the TBoMS. Additionally, an interleaver can be configured to interleave the continuous outputs of the rate matching circuit based on time slots, such that code blocks crossing the time slot boundary between a first and a second time slot are interleaved within the first and second time slots.

Description

Technical Field

[0001] The subject matter disclosed herein is generally related to wireless communication systems. More specifically, the subject matter disclosed herein is related to mapping transport blocks across time slots allocated for uplink transmission in a wireless physical shared channel. [Cross-reference to related applications]

[0002] This application claims the benefit of priority of U.S. Patent Application No. 17 / 378,646, filed on July 16, 2021, and U.S. Provisional Patent Application No. 63 / 230,655, filed on August 6, 2021, under 35 U.S.C. § 119(e), the disclosures of which are incorporated herein by reference in their entirety.

Background Art

[0003] A wireless network (such as a fifth generation (5G) wireless network) can allocate resources for transmission over a physical shared channel. The form of allocation can be resources in multiple time slots, in which case the allocation corresponds to the transmission of the physical shared channel by repetition (e.g., type A or type B repetition). The resources can be indicated to the transmitter dynamically (e.g., via downlink control information (DCI)) or semi-statically (e.g., via the process of Configured Grant (CG) Physical Uplink Shared Channel (PUSCH) transmission). The resources can include a set of orthogonal frequency division multiplexing (OFDM) symbols and subcarriers (SCs) and additional configurations for physical shared channel transmission. The set of OFDM symbols can be continuous or discontinuous in time. The OFDM symbols can also be indicated in the form of a set of symbols in one or more time slots. The set of subcarriers can be a continuous or discontinuous set of subcarriers and can be indicated in the form of a resource block (RB) or a subset of resource blocks. The combination of OFDM symbols and subcarriers corresponds to a resource element (RE) carrying the coded bits of the PUSCH.

Summary of the Invention

[0004] Example embodiments provide a transport block processing chain for a transmitter, which may include a code block determination circuit and a rate matching circuit. The code block determination circuit may be configured to determine the size of code blocks mapped across multiple slots of a radio entity common channel according to a transport block over multiple slot (TBoMS) configuration. The rate matching circuit may be configured to rate match the bits of the code blocks with the number of bits available in the transport block across multiple slots of the radio entity common channel. In one embodiment, the multiple slots of the radio entity common channel according to the TBoMS configuration may be at least partially based on a legacy maximum transport block size (TBS). In another embodiment, the multiple slots of the radio entity common channel according to the TBoMS configuration may be at least partially based on a predetermined number of code blocks. In yet another embodiment, the predetermined number of code blocks may be at least partially based on a legacy maximum number of code blocks. In still another embodiment, the multiple slots of the radio entity common channel according to the TBoMS configuration may be at least partially based on the maximum TBS described in a standard document. In one embodiment, the transport block processing chain may further include an interleaver configured to interleave the consecutive outputs of the rate matching circuit based on slots such that code blocks spanning the slot boundary between a first slot and a second slot are interleaved within the first slot and the second slot.

[0005] An example embodiment provides a transport block processing chain for a transmitter, which may include a code block determination circuit, a rate matching circuit, and an interleaver. The code block determination circuit may be configured to determine the size of a code block mapped across at least one time slot boundary of time slots of a radio entity common channel. The rate matching circuit may be configured to rate match the bits of the code block with the number of bits available in a transport block across one or more time slots of the radio entity common channel. The interleaver may be configured to interleave the consecutive outputs of the rate matching circuit based on time slots such that a code block spanning a time slot boundary between a first time slot and a second time slot is interleaved within the first time slot and the second time slot. In one embodiment, a code block spanning a time slot boundary between a first time slot and a second time slot is segmented with a redundant version corresponding to the second time slot, the output of the rate matching circuit is restricted to a predetermined number of time slots, and the interleaver may be further configured to interleave the output of the rate matching circuit across the predetermined number of time slots. In another embodiment, the code block determination circuit may be further configured to determine the size of a code block mapped across multiple time slots of a radio entity common channel according to a TBoMS configuration, and the rate of the rate matching circuit may be further configured to match the bits of the code block with the number of bits available in a transport block across multiple time slots of the radio entity common channel. In yet another embodiment, the multiple time slots of the radio entity common channel in the TBoMS configuration may be at least partially based on a predetermined number of code blocks, the maximum TBS described in a standard document, or a combination thereof.

[0006] A method for processing data to be mapped into a transport block, the method may include: determining, by a code block determination circuit according to a TBoMS configuration, the size of a code block of data mapped across multiple time slots of a radio entity common channel; and rate matching the bits of the code block with the number of bits available in a transport block across multiple time slots of the radio entity common channel by a rate matching circuit. In one embodiment, the multiple time slots of the radio entity common channel according to the TBoMS configuration may be at least partially based on a legacy maximum TBS. In another embodiment, the multiple time slots of the radio entity common channel according to the TBoMS configuration may be at least partially based on a predetermined number of code blocks. In yet another embodiment, the predetermined number of code blocks may be at least partially based on a legacy maximum number of code blocks. In still another embodiment, the multiple time slots of the radio entity common channel according to the TBoMS configuration may be at least partially based on the maximum TBS described in a standard document. In one embodiment, the method may further include interleaving, by an interleaver, the consecutive outputs of the rate matching circuit based on time slots such that a code block spanning a time slot boundary between a first time slot and a second time slot is interleaved within the first time slot and the second time slot.

[0007] Example embodiments provide a method for processing data to be mapped into transport blocks, where the method includes: determining, by a code block determination circuit, the size of a code block of data mapped across at least one time slot boundary of time slots of a radio entity common channel; rate matching, by a rate matching circuit, the bits of the code block with the number of bits available in a transport block across one or more time slots of the radio entity common channel; and interleaving, by an interleaver, the consecutive outputs of the rate matching circuit based on time slots such that a code block spanning a time slot boundary between a first time slot and a second time slot is interleaved within the first time slot and the second time slot. In one embodiment, the method may further include segmenting, by the code block determination circuit, a code block spanning a time slot boundary between a first time slot and a second time slot with a redundant version corresponding to the second time slot, and where the output of the rate matching circuit is restricted to a predetermined number of time slots, and where the method may further include interleaving, by the interleaver, the output of the rate matching circuit across the predetermined number of time slots. In another embodiment, the method may further include: determining, by the code block determination circuit, the size of code blocks mapped across multiple time slots of a radio entity common channel according to a TBoMS configuration; and matching, by the rate of the rate matching circuit, the bits of the code block with the number of bits available in a transport block across multiple time slots of the radio entity common channel. In yet another embodiment, multiple time slots of a radio entity common channel according to a TBoMS configuration may be at least partially based on a predetermined number of code blocks, the maximum TBS set forth in a standard document, or a combination thereof.

Embodiment

[0009] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. However, those of ordinary skill in the art will understand that the disclosed aspects may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to obscure the subject matter disclosed herein.

[0010] Throughout this specification, reference to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment disclosed herein. Thus, the appearances of the phrases "in one embodiment," "in an embodiment," "according to one embodiment" (or other phrases with similar meanings) throughout this specification in various places may not necessarily all refer to the same embodiment. Additionally, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In this regard, as used herein, the term "exemplary" means "serving as an example, instance, or illustration." Any embodiment described herein as "exemplary" should not be construed as necessarily being preferred or better than other embodiments. Additionally, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. Further, depending on the context of the discussion herein, singular terms may include the corresponding plural forms, and plural terms may include the corresponding singular forms. Similarly, hyphenated terms (e.g., "two-dimensional," "pre-determined," "pixel-specific," etc.) may be used interchangeably with the corresponding non-hyphenated versions (e.g., "two dimensional," "predetermined," "pixel specific," etc.), and capitalized terms (e.g., "Counter Clock," "Row Select," "PIXOUT," etc.) may be used interchangeably with the corresponding non-capitalized versions (e.g., "counter clock," "row select," "pixout," etc.). Such occasional interchangeable use should not be regarded as inconsistent with each other.

[0011] Further, depending on the context of the discussion herein, singular terms may include the corresponding plural forms, and plural terms may include the corresponding singular forms. It should be further noted that the various diagrams (including component diagrams) illustrated and discussed herein are for illustrative purposes only and are not drawn to scale. For example, for clarity, the dimensions of some of the elements may be enlarged relative to other elements. Additionally, when considered appropriate, reference numerals have been repeated in the figures to indicate corresponding and / or similar elements.

[0012] The terms used herein are for the purpose of describing some example embodiments only and are not intended to limit the claimed subject matter. As used herein, unless the context clearly indicates otherwise, the singular forms "a / an" and "the" are also intended to include the plural forms. It should be further understood that the term "comprises and / or comprising" when used in this specification specifies the presence of the stated features, integers, steps, operations, elements, and / or components, but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0013] It should be understood that when an element or layer is referred to as being on, "connected to" or "coupled to" another element or layer, the element or layer can be directly on, directly connected to or coupled to the other element or layer, or intervening elements or layers may be present. In contrast, when an element is referred to as being "directly on" another element or layer, "directly connected to" or "directly coupled to" another element or layer, no intervening elements or layers are present. Like numerals refer to like elements throughout. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0014] The terms "first", "second", etc. as used herein are labels for the nouns preceded by such terms and do not imply any type of ordering (e.g., spatial, temporal, logical, etc.), unless so specifically defined. Additionally, the same reference numerals may be used across two or more diagrams to refer to parts, components, blocks, circuits, units, or modules having the same or similar functionality. However, this usage is for simplicity of illustration and ease of discussion only; it does not imply that the construction or architectural details of such components or units are the same across all embodiments, or that such commonly referred to parts / modules are the only way to implement some of the example embodiments disclosed herein.

[0015] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this subject matter belongs. It should be further understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein. As used herein, the term "module" refers to any combination of software, firmware, and / or hardware configured to provide the functionality described herein in connection with the module. For example, the software may be embodied as a software package, code, and / or instruction set or instructions, and the term "hardware" as used in any implementation described herein may include, alone or in any combination, for example, assemblies, hardwired circuitry, programmable circuitry, state machine circuitry, and / or firmware that stores instructions executed by the programmable circuitry. The modules may collectively or individually be embodied as circuitry that forms part of a larger system, such as, but not limited to, an integrated circuit (IC), a system-on-a-chip (SoC), an assembly, etc. FIGS. 1 through 40 described below and various embodiments for illustrating the subject matter disclosed herein are by way of example only and should not be taken as limiting the scope of the subject matter disclosed herein in any way. It should be understood that the subject matter disclosed herein may be implemented in any suitably configured system or device.

[0018] The following documents are hereby incorporated by reference into this disclosure as if fully set forth herein: 3GPP TS 38.211 v15.6.0, "NR; Physical channels and modulation"; 3GPP TS 38.212 v15.6.0, "NR; Multiplexing and Channel coding"; 3GPP TS 38.213 v15.6.0, "NR; Physical Layer Procedures for Control"; 3GPP TS 38.214 v15.6.0, "NR; Physical Layer Procedures for Data"; 3GPP TS 38.321 v15.6.0, "NR; Medium Access Control (MAC) protocol specification"; and 3GPP TS 38.331 v15.6.0, "NR; Radio Resource Control (RRC) Protocol Specification".

[0019] Figures 1 to 5 depict various example embodiments implemented in a wireless communication system and in the use of orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication techniques. The descriptions of Figures 1 to 3 are not meant to imply physical or architectural limitations on the ways in which different embodiments may be implemented. Different embodiments of the subject matter disclosed herein may be implemented in any suitably configured communication system.

[0020] Figure 1 depicts an example embodiment of a wireless communication network 100 according to the subject matter disclosed herein. The example embodiment of the wireless network depicted in Figure 1 is for illustrative purposes only. Other embodiments of the wireless network 100 may be used without departing from the principles of the subject matter disclosed herein. As depicted in FIG. 1, the wireless network 100 includes gNB 101 (e.g., a base station (BS)), gNB 102, and gNB 103. gNB 101 can communicate with gNB 102 and gNB 103. gNB 101 can also communicate with at least one network 130, such as the Internet, a private Internet Protocol (IP) network, or other data networks.

[0022] gNB 102 can provide wireless broadband access to the network 130 for a first plurality of UEs within the coverage area 120 of gNB 102. The first plurality of UEs can include: UE 111, which can be located in a small business (SB); UE 112, which can be located in Enterprise I; UE 113, which can be located in a WiFi hotspot (HS); UE 114, which can be located in a first residence I; UE 115, which can be located in a second residence I; and UE 116, which can be a mobile device (M), such as, but not limited to, a cellular phone, a wireless laptop, a wireless PDA, or the like. gNB 103 can provide wireless broadband access to the network 130 for a second plurality of UEs within the coverage area 125 of gNB 103. The second plurality of UEs can include UE 115 and UE 116. In some embodiments, one or more of gNBs 101 to 103 can communicate with each other and with UEs 111 to 116 using 5G / NR, LTE, LTE-A, WiMAX, WiFi, and / or other wireless communication technologies.

[0023] Depending on the network type, the term "base station" or "BS" may refer to any component (or collection of components) configured to provide wireless access to the network, such as a transmit point (TP), a transmit-receive point (TRP), an evolved Node B (eNodeB or eNB), a 5G / NR base station (gNB), a macro cell, a femtocell, a Wi-Fi access point (AP), or other wireless-enabled device. The base station may provide wireless access according to one or more wireless communication protocols, such as 5G / NR 3GPP new radio (NR) interface / access, long term evolution (LTE), LTE advanced (LTE-A), high speed packet access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. For convenience, the terms "BS" and "TRP" may be used interchangeably herein to refer to a network infrastructure component that provides wireless access to a remote terminal. Additionally, depending on the network type, the term "user equipment" or "UE" may refer to any component, such as a "mobile station", a "subscriber station", a "remote terminal", a "wireless terminal", a "reception point", or a "user device". For convenience, the terms "user equipment" and "UE" may be used herein to refer to a remote wireless device that wirelessly accesses a BS, whether the UE is a mobile device (such as, but not limited to, a mobile phone or a smartphone) or a device that is typically considered stationary (such as, but not limited to, a desktop computer or a vending machine).

[0024] The dashed lines depict the approximate extent of coverage area 120 and coverage area 125, which are depicted as approximately circular for illustrative and explanatory purposes only. It should be clearly understood that the coverage areas associated with a gNB (such as coverage area 120 and coverage area 125) may have other shapes, including irregular shapes, depending on the configuration of the gNB and variations in the radio environment associated with natural and man-made obstacles.

[0025] As described in more detail below, one or more of UEs 111 to 116 may include circuitry, programming, or a combination thereof for efficient control signaling designed to improve resource utilization. In some embodiments, and one or more of gNBs 101 to 103 may include circuitry, programming, or a combination thereof for efficient control signaling designed to improve resource utilization.

[0026] Although FIG. 1 depicts an example of a wireless network, various changes may be made to FIG. 1. For example, the wireless network 100 may include any number of gNBs and any number of UEs in any suitable configuration. Additionally, the gNB 101 may communicate directly with any number of UEs and provide those UEs with wireless broadband access to the network 130. Similarly, each of the gNBs 102 to 103 may communicate directly with the network 130 and provide the UEs with direct wireless broadband access to the network 130. In addition, the gNB 101, gNB 102, and / or gNB 103 may provide access to other or additional external networks, such as but not limited to an external telephone network or other types of data networks.

[0027] FIG. 2 depicts an example embodiment of the gNB 102 according to the subject matter disclosed herein. The embodiment of the gNB 102 depicted in FIG. 2 is for illustrative purposes only, and the gNBs 101 and 103 of FIG. 1 may have the same or similar configurations. However, gNBs come in a wide variety of configurations, and it should be understood that FIG. 2 does not limit the scope of the subject matter disclosed herein to any particular implementation of a gNB.

[0028] As depicted in FIG. 2, the gNB 102 may include multiple antennas 201a to 201n, multiple radio frequency (RF) transceivers 202a to 202n, receive (RX) processing circuitry 203, and transmit (TX) processing circuitry 204. The gNB 102 may also include a controller / processor 205, a memory 206, and / or a backhaul or network interface 207.

[0029] The RF transceivers 202a to 202n may receive incoming RF signals from the antennas 201a to 201n. The received RF signals may be signals transmitted by UEs in the network 100. The RF transceivers 202a to 202n may down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals may be sent to the RX processing circuitry 203, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuitry 203 may transmit the processed baseband signal to the controller / processor 255 for further processing.

[0030] The TX processing circuit system 204 can receive analog or digital data (such as but not limited to voice data, web data, e-mail, or interactive video game data) from the controller / processor 225. The TX processing circuit system 204 can encode, multiplex, and / or digitize the outgoing baseband data to generate a processed baseband or IF signal. The RF transceivers 202a to 202n can receive the outgoing processed baseband or IF signal from the TX processing circuit system 204, and can up-convert the baseband or IF signal into an RF signal transmitted via the antennas 201a to 201n.

[0031] The controller / processor 205 can include one or more processors or other processing devices that can control the overall operation of the gNB 102. For example, the controller / processor 205 can control the reception of forward channel signals and the transmission of reverse channel signals according to well-known principles by means of the RF transceivers 202a to 202n, the RX processing circuit system 203, and the TX processing circuit system 204. The controller / processor 205 can also support additional functions, such as more advanced wireless communication functions. For example, the controller / processor 205 can support beamforming or directional routing operations, in which the outgoing / incoming signals from / to the multiple antennas 201a to 201n can be weighted in different ways to effectively direct the outgoing signal in the desired direction. Any one of a wide variety of other functions can be supported by the controller / processor 205 in the gNB 102.

[0032] The controller / processor 205 may also be capable of executing programs and other processes stored in the memory 206, such as an operating system (OS). The controller / processor 205 can move data into or out of the memory 206 as needed by executing processes, and the memory 206 can be coupled to the controller / processor 205. A portion of the memory 206 can include random-access memory (RAM), and another portion of the memory 206 can include flash memory or other read-only memory (ROM).

[0033] The controller / processor 205 may also be coupled to a backhaul or network interface 207. The backhaul or network interface 207 may allow the gNB 102 to communicate with other devices or systems via a backhaul connection or via the network. The interface 207 may support communication via any suitable wired or wireless connection. For example, when the gNB 102 is implemented as part of a cellular communication system (such as a gNB supporting 5G / NR, LTE, or LTE-A), the interface 207 may allow the gNB 102 to communicate with other gNBs via a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, the interface 207 may allow the gNB 102 to communicate via a wired or wireless local area network or via a wired or wireless connection to a larger network (such as the Internet). The interface 207 may include any suitable structure that supports communication via a wired or wireless connection (such as Ethernet or an RF transceiver).

[0034] Although FIG. 2 depicts an example of the gNB 102, various changes may be made to FIG. 2. For example, the gNB 102 may include any number of the components shown in FIG. 2. As a specific example, an access point may include several interfaces 207, and the controller / processor 205 may support a routing function for routing data between different network addresses. As another specific example, although depicted as including a single instance of the TX processing circuitry 204 and a single instance of the RX processing circuitry 203, the gNB 102 may include multiple instances of each (such as one per RF transceiver). Additionally, the various components in FIG. 2 may be combined, further subdivided, or omitted, and additional components may be added according to specific needs.

[0035] FIG. 3 depicts an example embodiment of a UE 116 according to the subject matter disclosed herein. The embodiment of the UE 116 depicted in FIG. 3 is for illustrative purposes only, and the UEs 111 to 115 of FIG. 1 may have the same or similar configurations. However, the UE may assume a wide variety of configurations, and FIG. 3 does not limit the UE to any particular implementation.

[0036] As depicted in FIG. 3, the UE 116 may include an antenna 301, an RF transceiver 302, TX processing circuitry 303, a microphone 304, and RX processing circuitry 305. The UE 116 may also include a speaker 360, a processor 307, an input / output (I / O) interface 308, a touch screen 309 (or other input device), a display 310, and a memory 311. The memory 311 may include an OS 312 and one or more applications 313.

[0037] The RF transceiver 310 can receive an incoming RF signal transmitted by the gNB of the network 100 from the antenna 305. The RF transceiver 310 can down-convert the incoming RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal can be sent to the RX processing circuitry 325, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuitry 325 can transmit the processed baseband signal to the speaker 330 (such as for voice data) or to the processor 340 for further processing (such as for web browsing data).

[0038] The TX processing circuitry 303 can receive analog or digital voice data from the microphone 304, or other outgoing baseband data (such as web data, email, or interactive video game data) from the processor 307. The TX processing circuitry 303 can encode, multiplex, and / or digitize the outgoing baseband data to generate a processed baseband or IF signal. The RF transceiver 302 can receive the outgoing processed baseband or IF signal from the TX processing circuitry 303, and can up-convert the baseband or IF signal to an RF signal transmitted via the antenna 301.

[0039] The processor 307 can include one or more processors or other processing devices, and can execute the OS 312 stored in the memory 311 to control the overall operation of the UE 116. For example, the processor 307 can control the reception of forward channel signals and the transmission of reverse channel signals by the RF transceiver 302, the TX processing circuitry 303, and the RX processing circuitry 305 according to well-known principles. In some embodiments, the processor 307 can be at least one microprocessor or microcontroller.

[0040] The processor 370 may also be capable of executing other processes and programs resident in the memory 311, such as processes for beam management. The processor 307 can move data into or out of the memory 311 as needed by executing processes. In some embodiments, the processor 307 can be configured to execute the application program 313 based on the OS 361 or in response to signals received from the gNB or from an operator. The processor 307 can also be coupled to the I / O interface 308, which can provide the UE 116 with the ability to connect to other devices, such as but not limited to laptop computers and handheld computers. The I / O interface 308 is a communication path between these accessories and the processor 307.

[0041] The processor 307 may also be coupled to the touch screen 309 and the display 310. An operator of the UE 116 may use the touch screen 309 to input data into the UE 116. The display 310 may be a liquid crystal display, a light emitting diode display, or other display capable of presenting text and / or at least limited graphics, such as from a website).

[0042] The memory 311 may be coupled to the processor 307. A portion of the memory 311 may include RAM, and another portion of the memory 311 may include flash memory or other ROM.

[0043] Although FIG. 3 depicts an exemplary embodiment of the UE 116, various changes may be made to FIG. 3. For example, the various components in FIG. 3 may be combined, further subdivided, or omitted, and additional components may be added according to specific needs. As a specific example, the processor 340 may be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Additionally, although FIG. 3 depicts the UE 116 configured as a mobile phone or smartphone, the UE may be configured to operate as other types of mobile or stationary devices.

[0044] To meet the demand for wireless data traffic that has increased since the self-deployment of 4G communication systems, efforts have been made to develop improved 5G / NR or pre-5G / NR communication systems. Therefore, 5G / NR or pre-5G / NR communication systems may also be referred to as "super 4G networks" or "post-LTE systems". The 5G / NR communication system can be considered to be implemented in a higher frequency (millimeter wave) band (e.g., 28 GHz or 60 GHz band, or generally higher than 6 GHz band) to achieve higher data rates, or implemented in a lower frequency band (such as below 6 GHz) to achieve robust coverage and mobility support. To reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are used in the 5G / NR communication system. Additionally, in the 5G / NR communication system, research and development for system network improvement are ongoing based on the following: advanced small cells, cloud radio access network (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multi-point (CoMP), receiver interference cancellation, and the like.

[0045] A communication system may include: a downlink (DL), which refers to the transmission from a base station or one or more transmission points to a UE; and an uplink (UL), which refers to the transmission from a UE to a base station or to one or more receiving points.

[0046] A unit for DL transmission or UL transmission on a cell may be referred to as a time slot and may include one or more symbols. A symbol may also serve as an additional time unit. A frequency (or bandwidth (BW)) unit may be referred to as a resource block (RB). One RB may include several subcarriers (SCs). For example, a time slot may have a duration of 0.5 milliseconds or 1 millisecond, include 14 symbols, and an RB may include 12 SCs with SC spacing of 30 kHz or 15 kHz, respectively. A unit of one RB in frequency and one symbol in time may be referred to as a physical RB (PRB).

[0047] The DL signal may include a data signal for transmitting information content, a control signal for transmitting DL control information (DCI), and a reference signal (RS), which may also be referred to as a pilot signal. The gNB transmits data information or DCI via a respective physical DL shared channel (PDSCH) or physical DL control channel (PDCCH). The PDSCH or PDCCH may be transmitted via a variable number of time slot symbols including one time slot symbol. For simplicity, the DCI format for scheduling PDSCH reception by the UE may be referred to as the DL DCI format, and the DCI format for scheduling PUSCH transmission from the UE is called the UL DCI format.

[0048] The gNB may transmit one or more of multiple types of RSs including channel state information RS (CSI-RS) and demodulation RS (DM-RS). The CSI-RS may be mainly intended for the UE to perform measurements and provide channel state information (CSI) to the gNB. For channel measurements, non-zero power CSI-RS (NZP CSI-RS) resources may be used. For interference measurement reports (IMRs), CSI interference measurement (CSI-IM) resources may be used. The CSI process may include NZP CSI-RS and CSI-IM resources.

[0049] The UE may determine CSI-RS transmission parameters via DL control signaling or higher layer signaling from the gNB, such as radio resource control (RRC) signaling. The transmission situation of the CSI-RS may be indicated by DL control signaling or configured by higher layer signaling. The DM-RS is typically transmitted only within the BW of a respective PDCCH or PDSCH, and the UE may use the DM-RS to demodulate data or control information.

[0050] FIG. 4A depicts an exemplary embodiment of a DL time slot structure 400 according to the subject matter disclosed herein. The exemplary embodiment of the DL time slot structure 400 depicted in FIG. 4A is for illustrative purposes only. FIG. 4 does not limit the scope of the subject matter disclosed herein to any particular implementation. It should be noted that in the DL time slot structure 400 described below, DCI information need not be located as depicted in FIG. 4A and may be located elsewhere as needed.

[0051] As depicted in FIG. 4A, DL time slot 401 may include symbols 402, where the gNB may transmit, for example, data information, DCI, or DM-RS. The DL system BW may include RBs. Each RB may includeSCs. For the PDSCH transmission BW, the UE may allocate RBs for a total ofSCs 403. The PDCCH that transmits DCI may be transmitted via a control channel element (CCE), which substantially spans the DL system BW. The first time slot symbol 404 may be used by the gNB to transmit the PDCCH. The second time slot symbol 405 may be used by the gNB to transmit the PDCCH or PDSCH. The remaining time slot symbols 406 may be used by the gNB to transmit the PDSCH and CSI-RS. In some time slots, the gNB may also transmit synchronization signals and channels that carry system information, such as a synchronization signals and primary broadcast channel (SS / PBCH) block.

[0052] UL signals may also include a data signal that carries information content, a control signal that transmits UL control information (UCI), a DM-RS associated with demodulation of the data or UCI, a sounding RS (SRS) that enables the gNB to perform UL channel measurements, and a random access (RA) preamble that enables the UE to perform random access. The UE may transmit data information or UCI via a respective physical UL shared channel (PUSCH) or a physical UL control channel (PUCCH). The PUSCH or PUCCH may be transmitted via a variable number of symbols in a time slot that includes one symbol. When the UE transmits data information and UCI simultaneously, the UE may multiplex the two in the PUSCH.

[0053] The UCI may include: hybrid automatic repeat request acknowledgement (HARQ-ACK) information indicating correct or incorrect detection of a transport block (TB) or a code block group (CBG) in the PDSCH; a scheduling request (SR) indicating to the UE whether the UE has data in a buffer; and a CSI report enabling the gNB to select appropriate parameters for PDSCH or PDCCH transmission to the UE.

[0054] The CSI report from the UE may include: a channel quality indicator (CQI) informing the gNB of the maximum modulation and coding scheme (MCS) for the UE to detect a TB with a predetermined block error rate (BLER) (such as 10% BLER); a precoding matrix indicator (PMI) informing the gNB how to combine signals from multiple transmitter antennas according to the multiple-input multiple-output (MIMO) transmission principle; a CSI-RS resource indicator (CRI) indicating the CSI-RS resource associated with the CSI report; and a rank indicator (RI) indicating the transmission rank of the PDSCH.

[0055] The UL RS may include DM-RS and SRS. The DM-RS may typically be transmitted only within the BW of each individual PUSCH or PUCCH transmission. The gNB may use the DM-RS to demodulate the information in each individual PUSCH or PUCCH. The SRS may be transmitted by the UE to provide UL CSI to the gNB, and for a TDD system, the SRS transmission may also provide the PMI for DL transmission. Additionally, to establish synchronization or an initial higher-layer connection with the gNB, the UE may transmit a physical random access channel (PRACH).

[0056] FIG. 4B depicts an exemplary embodiment of a UL time slot structure 410 for PUSCH transmission or PUCCH transmission according to the subject matter disclosed herein. The embodiment of the UL time slot structure 410 depicted in FIG. 4B is for illustrative purposes only. FIG. 4B does not limit the scope of the subject matter disclosed herein to any particular implementation. It should be noted that in the UL time slot structure 410 described below, UCI information need not be located as depicted in FIG. 4B and may be located elsewhere as desired.

[0057] As depicted in FIG. 4B, time slot 411 may include symbols 412, where the UE transmits, for example, data information, UCI, or DM-RS. The UL system BW may include N RBs. Each RB may include. For PUSCH transmission BW (“X” = “S”) or for PUCCH transmission BW (“X” = “C”), the UE may allocate RBs for a total of SCs 413. The last one or more symbols of the time slot may be used for, for example, multiplexed SRS transmission 414 or short PUCCH transmission from one or more UEs.

[0058] FIG. 5A depicts a block diagram of an exemplary embodiment of a transmitter structure 501 using OFDM according to the subject matter disclosed herein. The embodiment of the transmitter structure 501 depicted in FIG. 5A is for illustrative purposes only, and the actual implementation may have the same or a similar configuration. FIG. 5A does not limit the scope of the subject matter disclosed herein to any particular implementation.

[0059] As depicted in FIG. 5A, information bits such as DCI bits or data information bits 502 may be encoded by an encoder module 503, rate-matched with a specified time / frequency resource by a rate matcher module 504, and modulated by a modulator module 505. Subsequently, the modulated encoded symbols and the DM-RS or CSI-RS module 506 may be mapped to SCs by an SC mapping module 507 controlled by a transmission bandwidth module 508. An inverse fast Fourier transform (IFFT) may be performed by a filter module 509. A cyclic prefix (CP) may be added to the output of the filter module 509. The resulting signal may be filtered by a common interface unit (CIU) filter module 510 and transmitted by an RF module 511 as a transmitted signal 512.

[0060] FIG. 5B depicts a block diagram of an exemplary embodiment of an OFDM receiver structure 531 according to the subject matter disclosed herein. The embodiment of the receiver structure 531 depicted in FIG. 5B is for illustrative purposes only, and the actual implementation may have the same or a similar configuration. FIG. 5B does not limit the scope of the subject matter disclosed herein to any particular implementation. As depicted in FIG. 5B, the received signal 532 may be filtered by a filter module 533. A CP removal module 534 may remove the cyclic prefix. A filter module 535 may apply a fast Fourier transform (FFT). An SC demapping module 536 may demap the SC selected by a BW selector module 537. The received symbols may be demodulated by a channel estimator and demodulator module 538. A rate dematching module 539 may restore the rate matching, and a decoder module 540 may decode the resulting bits to provide data information bits 541. DL transmissions and UL transmissions may be based on an orthogonal frequency division multiplexing (OFDM) waveform that includes a variant of a DFT preamble called DFT-spread OFDM.

[0061] As previously mentioned, the goal of the 3GPP Rel-17 SID for RedCap NR devices is to support the same set of use cases in FR2 as in the case of FR1. Beam refinement may be a key feature for FR2 operation in NR. An important issue is regarding the implementation of the beam refinement procedure for a RedCap UE in the RRC_INACTIVE state (also referred to herein as the RRC inactive state or inactive mode). Accordingly, the subject matter disclosed herein provides a set of beam refinement procedures to enable RedCap in inactive mode transmissions in FR2.

[0062] Figure 6 illustrates a typical legacy processing flow 600 in Rel-16 at a transmitter for uplink and downlink transmissions of physical shared channels (PUSCH / PDSCH). At 601, allocation can be in the form of resources in a single time slot corresponding to the transmission of a physical shared channel transmission. The allocation can be in the form of resources over multiple time slots, in which case the allocation corresponds to the transmission of the physical shared channel by repetition (e.g., type A or type B repetition). The resources can be indicated to the transmitter dynamically (e.g., via DCI) or semi-statically (e.g., via the procedure for CG PUSCH transmission). The resources can include a set of OFDM symbols and subcarriers and additional configurations for physical shared channel transmission. The set of OFDM symbols can be continuous or discontinuous in time. The OFDM symbols can also be indicated in the form of a set of symbols in one or more time slots. The set of subcarriers can be a continuous or discontinuous set of subcarriers and can be indicated in the form of a resource block or a subset of a resource block. The combination of OFDM symbols and subcarriers corresponds to a resource element carrying the coded bits of the PUSCH.

[0063] Except at the mapping process 607 at the end of the processing sequence 600, most of the physical shared channel processing can mainly involve virtual resources and time slots. The resources can be grouped into physical resources and virtual resources. Physical resources can be resources corresponding to the actual time / frequency resources used by the transmitter for RF transmission of signals corresponding to the physical shared channel. Virtual resources can be resources used by the transmitter in the process of generating the coded bits and modulation symbols corresponding to the physical shared channel. As used herein, references to "time slot", "symbol", or "resource" indicate the virtual versions of those terms. Such references in this document indicate the physical terms only when explicitly appended with the term "physical".

[0064] At 602, the transmitter determines the transport block size (TBS) based on the allocated resources and the configured resources (such as Demodulation Reference Signal (DMRS) resources) of the transmission burden. At 603, the information bits contained in the transport block (TB) and code block (CB) are determined. At 604, low-density parity check (LDPC) coding is performed on the different code blocks that can form the transport block. At 605, the output codewords of each code block are rate matched (RM) to the number of available coded bits for the transmission of the code block in the physical shared channel. At 606, the interleaver maps the rate-matched output to modulation symbols. At 607, mapping is performed from virtual symbols to physical symbols, which are then transmitted on the different allocated resource elements of the physical shared channel.

[0065] When scheduling Rel-16 entity common channels by repetition / aggregation, process 600 may be substantially repeated with slight differences for each repetition. For example, each repetition may be used to transmit the same TB; and in each repetition, different redundancy version (RV) indices that can change the RM output for each repetition may be used.

[0066] FIG. 7 depicts an example of physical and virtual resources that can be allocated to a UE in Rel-16. In FIG. 7, time resources have been allocated as three (3) UL time slots 701a to UL time slot 701c for PUSCH transmission. In each time slot, starting from the second symbol (symbol number 2) in the time slot, there are six (6) consecutively allocated OFDM symbols. Depending on the time division duplex (TDD) configuration, the UL time slots can be allocated as continuous, discontinuous, or a combination of continuous and discontinuous time slots. In the example of FIG. 7, if it is assumed that the TDD configuration results in mode DDSUU (S: 10D, 4U), then this TDD configuration corresponds to the UE to which physical time slots 701a to physical time slot 701c are allocated.

[0067] When performing processing involving PUSCH in Rel-16, the UE can use virtual allocations 702a to virtual allocation 702c in FIG. 7 that respectively correspond to three consecutive UL time slots 701a to UL time slot 701c. Therefore, a mapping 703 exists between virtual resources 702a to virtual resources 702c and physical resources 701a to physical resources 701c, as indicated in FIG. 7. Determination of TBS and maximum data rate

[0068] In Rel-16, the determination of the TBS of the transport block can use the following equation (1), (1) where is the number of layers for physical common channel transmission, and are the modulation order and coding rate respectively specified by the modulation and coding scheme (MCS) index, and is the total number of available resources in the scheduled time slot. The TBS is approximately equal to, where the difference in size between the TBS and is related to the addition of cyclic redundancy code (CRC), code block segmentation, and the finite nature of the TBS values allowed in the specification.

[0069] For PUSCH (TS 6.1.4.2, TS 38.214): If - and transform precoding is disabled and Table 5.1.3.1-2 is used, or - and transform precoding is disabled and a table other than Table 5.1.3.1-2 is used, or - With transform pre - coding enabled, the UE shall first determine the following specified TBS: The UE shall first determine the number of REs (N RE ) in the time slot: - The UE first determines the number of REs allocated to the PUSCH within a PRB by -, where is the number of sub - carriers in the frequency domain of a physical resource block, is the number of symbols allocated to the PUSCH in the time slot, is the number of REs of the DM - RS per PRB in the allocated duration without data including the burden of the DM - RS CDM group, as described for the PUSCH with configured grant in Sub - clause 6.1.2.3 or as indicated by DCI format 0_1 or as described for DCI format 0_0 in Sub - clause 6.2.2, and is the burden configured by the higher - layer parameter xOverhead in PUSCH - ServingCellConfig. If not configured (values from 6, 12, or 18), it is assumed to be 0. For Msg3 transmission, it is always set to 0. - The UE determines the total number of REs allocated to the PUSCH by, where is the total number of PRBs allocated to the UE. - Next, proceed with steps 2 to 4 as defined in Sub - clause 5.1.3.2

[0070] For PDSCH (TS 5.1.3.2, TS 38.214): The UE shall first determine the number of REs (N RE ) in the time slot. - The UE first determines the number of REs allocated to the PDSCH within a PRB () by, where is the number of sub - carriers in a physical resource block, is the number of symbols allocated to the PUSCH in the time slot, is the number of REs of the DM - RS per PRB in the scheduled duration without data including the burden of the DM - RS CDM group, as indicated by DCI format 1_1 or as described for format 1_0 in Sub - clause 5.1.6.2, and is the burden configured by the higher - layer parameter xOverhead in PDSCH - ServingCellConfig. If xOverhead in PDSCH - ServingCellconfig is not configured (values from 0, 6, 12, or 18), it is set to 0. If the PDSCH is scheduled by the PDCCH and the CRC is scrambled by SI - RNTI, RA - RNTI, or P - RNTI, it is assumed to be 0. - The UE determines the total number of REs allocated to the PDSCH () by, where n PRBThe total number of PRBs allocated for the UE. 2) Obtain the intermediate number of information bits (N info ). If Use step 3 as the next step for TBS determination Otherwise Use step 4 as the next step for TBS determination End if the following situation occurs 3) When, the TBS determination is as follows - The quantized intermediate number of information bits, where. - Use Table 5.1.3.2-1 to find the closest TBS not less than. 4) When, the TBS determination is as follows. - The quantized intermediate number of information bits, where and the relationship in the rounding function is broken towards the next largest integer. - If , where Otherwise If , where Otherwise End if the following situation occurs End if the following situation occurs

[0071] The New Radio (NR) standard specifies the maximum data rate achievable for a given UE capability. The following text from Specification No. 38.306 specifies the procedure for calculating the maximum data rate. 4.1.2 Supported Maximum Data Rates for DL / UL For NR, the approximate data rate for a given number of aggregated carriers in a band or band combination is calculated as follows. Where J is the number of aggregated component carriers in the band or band combination R max = 948 / 1024 For the jth CC, Is the maximum number of supported layers given by the maximum of the higher layer parameter maxNumberMIMO-LayersPDSCH for the downlink and the higher layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH for the uplink. Is the maximum supported modulation order given by the higher layer parameter supportedModulationOrderDL for the downlink and the higher layer parameter supportedModulationOrderUL for the uplink. Is the scaling factor given by the higher layer parameter scalingFactor, and can take the values 1, 0.8, 0.75 and 0.4. Is the numerology (as defined in TS 38.211 [6]) Is the average OFDM symbol duration in a subframe of the numerology, i.e.,. Note that normal cyclic prefix is used. Is the maximum RB allocation in the bandwidth with the numerology, as defined in 5.3 TS 38.101-1 [2] and 5.3 38.101-2 [3], where is the maximum bandwidth supported by the UE in a given band or band combination. Is the overhead, and takes the following values 0.14, for the frequency range FR1 of the DL 0.18, for the frequency range FR2 of the DL 0.08, for the frequency range FR1 of the UL 0.10, for the frequency range FR2 of the UL Note 1: For SUL cell operation, count only for one of the UL or SUL carriers (the one with the higher data rate). Note 2: For UL Tx switching between carriers, for the carrier with the maximum supported UL data rate, count only for the supported MIMO layer combinations that result in the highest combined data rate across carriers. The approximate maximum data rate can be calculated as the maximum of the approximate data rates calculated using the above formula for each of the supported bands or band combinations. For single carrier NR SA operation, the UE shall support a data rate for the carrier that is not less than the data rate calculated using the above formula, where the and components are not less than 4. Note: As an example, the value 4 in the above components corresponds to, and. For EUTRA in the case of MR-DC, the approximate data rate for a given number of aggregated carrier in a band or band combination is calculated as follows. Data rate (in megabits per second) = Where J is the number of aggregated EUTRA component carriers in the MR-DC band combination is the total maximum number of DL - SCH transport block bits received or the total maximum number of UL - SCH transport block bits transmitted within 1 millisecond TTI for the Jth CC, derived from TS36.213

[19] based on the maximum MIMO layers supported by the UE for the jth CC, the maximum modulation order for the jth CC, and the number of PRBs based on the bandwidth of the jth CC according to the indicated UE capabilities. The approximate maximum data rate can be calculated as the maximum of the approximate data rates calculated using the above formula for each of the supported frequency bands or frequency band combinations. For MR - DC, the approximate maximum data rate is calculated as the sum of the approximate maximum data rates from NR and EUTRA.

[0072] The following example of rate matching and the interleaving procedure applied to PUSCH are described in 3GPP TS 38.212. By denoting the rate - matched output sequence length of the th coding block, the value of is determined as follows: Set for to if the th coding block is not scheduled for transmission, as indicated by the CBGTI according to clause 5.1.7.2 for DL - SCH and clause 6.1.5.2 for UL - SCH in [6, TS 38.214], then ; otherwise if ; otherwise ; end if the following situation occurs; end if the following situation occurs End of loop where - is the number of transport layers to which the transport block is mapped; - is the modulation order; - is the total number of coding bits available for the transmission of the transport block; - if the CBGTI does not exist in the DCI scheduling the transport block, then, and if the CBGTI exists in the DCI scheduling the transport block, then is the number of coded blocks of the transport block. Represented by the number of redundant versions () transmitted ( = 0, 1, 2, or 3), the rate - matched output bit sequence () is generated as follows, where is given by Table 5.4.2.1 - 2 according to the value of and the LDPC base graph: ;; and if ;; end if the following situation occurs; end when the following situation occurs Table 5.4.2.1 - 2: Start positions of different redundant versions LDPC base graph 1 LDPC base graph 2 0 1 2 3 5.4.2.2 Bit Interleaving According to the following, a bit sequence is interleaved with a bit sequence, where the value is the modulation order. For to for to; end of loop end of loop

[0073] For slot aggregation, Rel-16 follows Table 6.1.2.1-2 to determine the redundancy version (RV) index of the registration management (RM) output for each slot. For PUSCH repetition type A, when K > 1, the same symbol allocation is applied across K consecutive slots, and the PUSCH is restricted to a single transmission layer. The UE shall repeat the TB across K consecutive slots, applying the same symbol allocation in each slot. Determine the redundancy version to be applied to the nth transmission occasion of the TB according to Table 6.1.2.1-2, where n = 0, 1,... K-1. Table 6.1.2.1-2: Redundancy versions for PUSCH transmission rv indicated by the DCI scheduling the PUSCH id rv to be applied to the nth transmission occasion (repetition type A) or the nth actual repetition (repetition type B) id n mod 4 = 0 n mod 4 = 1 n mod 4 = 2 n mod 4 = 3 0 0 2 3 1 2 2 3 1 0 3 3 1 0 2 1 1 0 2 3 TDD Configuration

[0074] In Rel-16, the network can (either semi-statically (e.g., radio resource control (RRC)) or dynamically) provide the UE with a set of configurations indicating the specific configuration of UL slots and resources, where the specific configuration specifies the possible transmission directions on these slots and resources. The configuration of the resources can be referred to as the TDD configuration.

[0075] In a TDD configuration, each OFDM symbol (OFDM symbol; OS) in the UL frame structure can have one of three possible indications: uplink (UL), downlink (DL), or flexible (Flexible; F). If the OS has an indication of UL or DL, the possible transmission direction on this symbol can be only UL or DL respectively, while the indication of F provides transmission in both directions on the OS, where the actual transmission depends on other factors such as the type of transmission scheduling.

[0076] The TDD configuration can be set in a semi-static manner. That is, the UE can be equipped with an RRC configuration indicating a specific time slot structure that is configured to repeat periodically. The time slot structure can span one or more time slots and can configure the UL / DL / F indication for the OS in those time slots. The semi-static TDD configuration can be a common configuration for all UEs in a cell or a dedicated configuration for each UE. When both a common and a dedicated TDD configuration exist, the role of the dedicated configuration can be to only overwrite the indication of the OS indicated as F in the common configuration. In this case, the overall indication of the OS of the UE will be specified as follows. If the common TDD configuration provides a UL indication, or the common TDD configuration provides an F indication and the dedicated TDD configuration provides a UL indication, then UL is indicated. If the common TDD configuration provides a DL indication, or the common TDD configuration provides an F indication and the dedicated TDD configuration provides a DL indication, then DL is indicated. If both the common and the dedicated TDD configurations provide an F indication, then F is indicated.

[0077] A dynamic TDD configuration can also be provided to the UE. The dynamic TDD configuration can be referred to as a slot format indication (Slot Format Indication; SFI). Providing the dynamic TDD configuration can be performed by first configuring the UE to monitor the indication of DCI format 2_0 carrying the SFI field. The SFI field indicates a UL / DL / F configuration for one or more time slots. The UL / DL / F configuration is intended to overwrite the indication of the OS in those time slots that are semi-statically indicated as F. Therefore, if the UE is configured to monitor the SFI, the overall indication of the OS of the UE will be specified as follows. If it is semi-statically indicated as UL, or F and the dynamic TDD configuration provides a UL indication, then UL is indicated. If it is semi-statically indicated as DL, or F and the dynamic TDD configuration provides a DL indication, then DL is indicated. If both the semi-static and the dynamic TDD configurations indicate it as F, then F is indicated.

[0078] The actual transmission in the OS may depend on the signal being transmitted (e.g., PDSCH, PUSCH, PDCCH, PUCCH, RS, etc.) and the scheduling type (e.g., dynamic scheduling, configured grant type 1 or type 2, semi-persistent scheduling, scheduling with repetition type A or type B). For PUSCH transmission, the PUSCH UL transmission may be cancelled due to a conflict with the TDD configuration of the OS allocated for the PUSCH. Cancellation indication

[0079] For the cancellation indication in Rel-16, the network may provide the UE with a dynamic indication to cancel / forbid UL transmission in specific resources. The network may choose to perform cancellation of UL transmissions of some UEs to release the corresponding resources for other transmissions (e.g., transmission of data with low latency requirements). The UE may receive the cancellation indication via DCI format 2_4, which contains an indication of the time / frequency resources in which the UE should cancel / avoid UL transmission. Overlap of UL transmissions

[0080] Regarding the overlap of UL transmissions in Rel-16, the UE may encounter a situation where multiple UL signals are scheduled in resources that may overlap in time and / or frequency. In this case, the UE may have to handle this situation by continuing to transmit all signals simultaneously, multiplexing the information of one UL transmission onto another and / or cancelling the transmission of one or more of the UL transmissions.

[0081] The behavior of the UE depends on the type of UL transmission. That is, the UE may be scheduled by different types of PUSCH (dynamic grant or configured grant transmission). Additionally, the UE may be scheduled by PUSCH or PUCCH transmission that may be associated with a priority index. When such signals overlap in time, the priority index may allow the UE to determine the appropriate behavior. For example, if the UE has PUCCH and / or PUSCH that overlap in time, and if the overlapping signals have the same priority index, it may be appropriate to multiplex the information of one or more of the PUCCH onto other PUCCH or onto other PUSCH in the set of overlapping signals. Alternatively, if the UE has PUCCH and / or PUSCH that overlap in time, and if the overlapping signals have different priority indexes, the UE may have to cancel some of the UL signals with a lower priority index and continue to transmit the UL signals with a higher priority index.

[0082] Thus, in some cases, if it conflicts in time with other UL signals that may have a higher priority index than PUSCH, for example, the UE may have to cancel the PUSCH transmission. If the transmission overlaps in time with a DG-PUSCH of the same HARQ process ID, the UE may also cancel the CG-PUSCH transmission. Overlap between dynamically scheduled DL signals and UL signals scheduled by a higher layer

[0083] In Rel-16, the UE can be scheduled to transmit UL signals either dynamically (e.g., via scheduling DCI received from the gNB) or via a higher layer (e.g., via configured grant type 1 or 2). In unpaired spectrum, a situation can occur when the UE is indicated by a higher layer to transmit a PUSCH and then receives a dynamic schedule of a DL signal such as PDSCH or CSI-RS. In this case, in Rel-16, the UE discards the UL transmission based on a specific timeline that allows the UE to handle the DL reception request. The following text from the specification describes such operations. Thus, dynamically scheduled PDSCH and / or CSI-RS can be a source for cancelling some UL PUSCHs. For operations on a single carrier in unpaired spectrum, if the UE is configured by a higher layer to transmit SRS or PUCCH or PUSCH or PRACH in a set of symbols of a time slot, and the UE detects a DCI format that indicates to the UE the reception of CSI-RS or PDSCH in a subset of symbols from the set of symbols, then - The UE does not expect to cancel the transmission in the symbols from the set of symbols that occurs after a number of symbols less than the PUSCH preparation time assumed for the corresponding UE processing capability [6, TS 38.214] relative to the last symbol of the CORESET in which the UE detects the DCI format, and corresponds to the minimum SCS configuration between the SCS configuration of the PDCCH carrying the DCI format and the SCS configuration of the SRS, PUCCH, PUSCH, or, where if it is 15 kHz or higher, the SCS configuration corresponding to the PRACH; otherwise - The UE cancels the PUCCH, or PUSCH, or the actual repetition of the PUSCH determined by clauses 9 and 9.2.5 or clause 6.1 of [6. TS 38.214], or the PRACH transmission in the remaining symbols from the set of symbols, and cancels the SRS transmission in the remaining symbols from the subset of symbols

[0084] In Rel-16, schedulable UEs can receive DL signals dynamically (e.g., via scheduling DCI received from the gNB) or via a higher layer (e.g., via semi-persistent scheduling). Within unpaired spectrum, this situation can occur when the UE can be instructed by a higher layer to receive the PDSCH and then receive dynamic scheduling of ULL signals such as PUSCH, PUCCH, SRS-RS, or PRACH. In this case, Rel-16 instructs the UE to continue with UL transmission and cancel the DL reception request. The following text from the specification describes this operation. Thus, dynamically scheduled UL signals can be the source for canceling some DL PDSCHs. If the UE is configured by a higher layer to receive CSI-RS or PDSCH in a symbol set of a time slot, and the UE detects a DCI format 2_0 with a time slot format value other than 255, the time slot format value indicating a time slot format with a symbol subset from the symbol set as uplink or flexible, or the UE detects a DCI format that indicates PUSCH, PUCCH, SRS, or PRACH in at least one symbol of a transmission symbol set, then the UE cancels CSI-RS reception in the symbol set of the time slot or cancels PDSCH reception in the time slot. UCI Multiplexing on PUSCH

[0085] Figure 8 depicts a UE multiplexing uplink control information (UCI) on a PUSCH when scheduled resources overlap, which is allowed in Rel-16. As depicted in Figure 8, UCI carrying DL HARQ feedback can be scheduled on the PUSCH in the overlapping resources and multiplexed on the PUSCH at, for example, 801. When PUCCH and PUSCH are multiplexed, Rel-16 specifies timeline 1 and timeline 2 restrictions between different signals. Timeline 2 represents the minimum time between all scheduled PDSCHs and the resources of the multiplexed signals through which the HARQ feedback will be multiplexed. The following is from TS 38.213. If the UE will transmit multiple overlapping PUCCHs in a time slot or overlapping PUCCHs and PUSCHs in a time slot, and when appropriate, as described in clauses 9.2.5.1 and 9.2.5.2, then the UE is configured to multiplex different UCI types in one PUCCH, and for at least one of the multiple overlapping PUCCHs or PUSCHs in response to the UE's DCI format detection, the UE multiplexes all corresponding UCI types if the following conditions are met. If either PUCCH transmission or PUSCH transmission is in response to the UE's DCI format detection, then the UE expects the first symbol of the earliest PUCCH or PUSCH in the group of overlapping PUCCHs and PUSCHs in the time slot to meet the following timeline conditions - Given by the maximum value before the symbol with a CP starting after the last symbol of any corresponding PDSCH, where for the i-th PDSCH with a corresponding HARQ-ACK transmission on the PUCCH in the group of overlapping PUCCH and PUSCH, , is selected for the i-th PDSCH after [6, TS 38.214] based on the UE PDSCH processing capability of the i-th PDSCH and the SCS configuration, where the minimum SCS configuration among the SCS configurations corresponding to the PDCCH scheduling the i-th PDSCH (if present), the i-th PDSCH, the PUCCH with the corresponding HARQ-ACK transmission for the i-th PDSCH, and all PUSCH in the group of overlapping PUCCH and PUSCH.

[0086] Timeline 2 in Figure 8 can illustrate the decoding time necessary to decode the PDSCH and determine the HARQ feedback value to be multiplexed. Timeline 1 in Figure 8 is the minimum duration between all DCIs involved in scheduling the PUCCH and / or PUSCH signals to be multiplexed and the scheduled resources themselves. The following text is from TS 38.214. - If non-periodic CSI reporting is not multiplexed in the PUSCH in the group of overlapping PUCCH and PUSCH, then not before the symbol with a CP starting after the last symbol of the following - Any PDCCH with a DCI format scheduling the overlapping PUSCH, and - Any PDCCH scheduling a PDSCH or SPS PDSCH version with the corresponding HARQ-ACK information in the overlapping PUCCH in the slot If there is at least one PUSCH in the group of overlapping PUCCH and PUSCH, it is given by the maximum value, where for the i-th PUSCH in the group of overlapping PUCCH and PUSCH, , and is selected for the i-th PUSCH after [6, TS 38.214] based on the UE PUSCH processing capability of the i-th PUSCH and the SCS configuration, where the minimum SCS configuration among the SCS configurations corresponding to the PDCCH scheduling the i-th PUSCH (if present), the PDCCH scheduling the PDSCH with the corresponding HARQ-ACK transmission on the PUCCH in the group of overlapping PUCCH / PUSCH, and all PUSCH in the group of overlapping PUCCH and PUSCH. - If there is no PUSCH in the group of overlapping PUCCH and PUSCH, it is given by the maximum value of, where for the i-th PDSCH having the corresponding HARQ-ACK transmission on the PUCCH in the group of overlapping PUCCHs,, is selected based on the UE PUSCH processing capability of the PUCCH serving cell in the configured case. If the PUSCH processing capability is not configured for the PUCCH serving cell, it is selected based on the UE PUSCH processing capability 1. is selected based on the minimum SCS configuration between the SCS configuration of the PDCCH scheduling the i-th PDSCH (if any) having the corresponding HARQ-ACK transmission on the PUCCH in the group of overlapping PUCCHs and the SCS configuration of the PUCCH serving cell.

[0087] Timeline 1 in Figure 8 illustrates the duration for preparing the PUSCH signal and can be specified between the first symbol of the overlapping resources and each DCI of any of the signals involved in the scheduling multiplexing scenario. This can ensure that the multi-signal is known early enough to prepare the corresponding PUSCH. It should be noted that without knowing that the multiplexing effect has not occurred, the UE can technically continue to prepare the PUSCH by determining the TBS, establishing the code blocks, and performing encoding based on the allocated PUSCH resources, as depicted in Figure 6. However, the determination of the RM output should not be performed before knowing the effect of multiplexing. Therefore, timeline 2 can be considered to intend to allow sufficient time for processing the RM output, rather than the entire PUSCH preparation time.

[0088] When processing UCI multiplexing with scheduled PUSCH having repetitions, it may seem that there is no difference between different PUSCHs in the repetitions; that is, considering the actual PUSCH affected by multiplexing, keep timeline 1 and timeline 2 in Figure 8. UE Capability

[0089] Another aspect of Rel-16 NR is the ability to perform Carrier Aggregation (CA). In CA, the UE is able to use multiple component carriers (CCs) for transmission, thereby allowing the UE to utilize a larger bandwidth than possible with a single component carrier. Rel-16 NR allows various modes of carrier aggregation, which include intra-band frequency aggregation with contiguous component carriers, intra-band frequency aggregation with non-contiguous component carriers, and inter-band frequency aggregation with non-contiguous component carriers.

[0090] The classification of the CA mode can depend on the set of frequency bands containing the serving component carriers used. The set of frequency bands can be referred to as a band combination. In NR, carrier aggregation is applied across cells. The UE is initially connected to one cell in the CA, which is called the Primary Cell (PCell). Subsequently, the UE finds and connects to multiple other cells in the CA, which are called Secondary Cells (SCells). The UE in the CA can use each cell for the transmission and reception of different combinations of signals. For example, the UE can transmit / receive PUSCH on one cell and transmit / receive the sounding reference signal (SRS) on another cell.

[0091] However, the standard specifies certain timeline rules and conditions for such simultaneous transmission / reception of signals in the CA. Even with the timeline rules and requirements, the standard does not require every NR-connected UE to be able to perform such simultaneous use of component carriers in the CA. The fact is that the UE may have the ability to perform a certain transmission / reception task in the CA while not having the ability to perform other tasks.

[0092] Another factor affecting the UE's capabilities is whether it is assumed to be Frequency Division Duplex (FDD) or Time Division Duplex (TDD). The UE may or may not be able to perform a task on an FDD band / band combination, while the UE may not be able to or may be able to perform the same task on a TDD band / band combination. To make full use of the UE's capabilities and better optimize the use of the network, the gNB can be informed of the UE's capabilities that are subsequently considered when the gNB schedules the transmission / reception of the UE in the network.

[0093] UE capabilities refer to the mechanism by which the UE can inform the gNB of its ability to perform certain transmission / reception tasks. One UE capability reported to the gNB informs the gNB of the UE's ability to perform a specific task. The UE capabilities mechanism provides the UE with the flexibility to report its capabilities in different transmission scenarios.

[0094] The UE may report its ability to perform certain tasks in any scenario, in which case the UE reports its ability per UE. The UE may report its ability to perform certain tasks in a specific frequency band, in which case the UE reports its ability per frequency band. The UE may report its ability to perform certain tasks in a specific frequency band combination in CA, in which case the UE reports its ability per frequency band combination or per BC. The UE may report its ability to perform certain tasks in CA in certain scenarios (i.e., not necessarily always for a given frequency band combination). In this case, a mechanism called a feature set can be used to allow such flexibility in reporting, in which case the UE reports its ability per feature set or per FS in that case. Other ways of reporting UE capabilities are also possible.

[0095] UE capabilities can inform the gNB that the UE can / cannot transmit certain UL signals in certain frequency bands, for example. The UE capabilities mechanism has the flexibility to indicate that the UE can perform a task in certain scenarios and indicate that the UE cannot perform the same task in other scenarios. For example, some UE capabilities can be signaled to the gNB per frequency band, i.e., for a given task, the UE can have different capabilities for different frequency bands. Some UE capabilities can be common across frequency bands / frequency band combinations, i.e., the capabilities are per UE. In the case of CA, the UE capabilities can be signaled per frequency band combination. With respect to CA, the ability of the UE to perform certain tasks can depend on the frequency band combination involved in CA. For example, when the frequency band combination in CA is intra-band, the UE may be able to perform simultaneous transmission of two UL signals, but may not be able to perform the transmission in the case of inter-band CA.

[0096] In Release-15 NR, simultaneous transmission of UL signals in CA is not always allowed. The fact is that allowing simultaneous transmission of UL signals in CA can be governed by the UE's ability for the specific frequency band combination used in CA.

[0097] The following specific rules apply to Release-15. In the case of carrier aggregation within a band or inter-band CA band-band combinations where simultaneous SRS and PUCCH / PUSCH transmissions are not allowed, it is not expected that the UE is configured to have SRS from one carrier and PUSCH / UL DM-RS / UL PT-RS / PUCCH format from a different carrier in the same symbol. In the case of in-band CA or inter-band CA band-band combinations where simultaneous SRS and PRACH transmissions are not allowed, the UE shall not transmit SRS resources from one carrier and PRACH from a different carrier simultaneously. In the case of inter-band carrier aggregation, subject to the UE's capabilities, the UE may transmit SRS and PUCCH / PUSCH simultaneously across component carriers in different bands. In the case of inter-band carrier aggregation, subject to the UE's capabilities, the UE may transmit PRACH and SRS simultaneously across component carriers in different bands.

[0098] Table 1 provides a list of UE capabilities in Rel-15 as parameters related to the simultaneous transmission of UL signals in CA. Table 1 Definition of parameters Per M FDD-TDD DIFF FR1-FR2 DIFF ca-BandwidthClassDL-EUTRA Defines the class defined by the aggregated transmission bandwidth configuration for DL and the maximum number of component carriers supported by the UE, as specified in TS 36.101

[14] . This field does not exist when all FeatureSetEUTRA-DownlinkId:s in the corresponding FeatureSetsPerBand are zero. Band No N / A N / A ca-BandwidthClassDL-NR Defines the class defined by the aggregated transmission bandwidth configuration for DL and the maximum number of component carriers supported by the UE, as specified in TS 38.101-1 [2] and TS 38.101-2 [3]. This field does not exist when all FeatureSetDownlinkId:s in the corresponding FeatureSetsPerBand are zero. For FR1, the value 'F' shall not be used as it is not valid in TS 38.101-1 [2]. Band No N / A N / A ca-BandwidthClassUL-EUTRA Defines, for UL, the class defined by the aggregated transmission bandwidth configuration and the maximum number of component carriers supported by the UE, as specified in TS 36.101

[14] . This field does not exist when all FeatureSetEUTRA-UplinkId:s in the corresponding FeatureSetsPerBand are zero. Band No N / A N / A ca-BandwidthClassUL-NR Defines, for UL, the class defined by the aggregated transmission bandwidth configuration and the maximum number of component carriers supported by the UE, as specified in TS 38.101-1 [2] and TS 38.101-2 [3]. This field does not exist when all FeatureSetUplinkId:s in the corresponding FeatureSetsPerBand are zero. For FR1, the value 'F' shall not be used as it is not valid in TS 38.101-1 [2]. Band No N / A N / A Definition of parameters Per M FDD-TDD DIFF FR1-FR2 DIFF channelBWs-DL Indicates the channel bandwidths supported by the UE for each subcarrier spacing. The absence of channelBWs-DL (without suffix) for a band or the absence of a specific scs-XXkHz entry for a supported subcarrier spacing means that for a given band or specific SCS entry, the UE supports the channel bandwidths defined in [5, 10, 15, 20, 25, 30, 40, 50, 60, 80, 100] and [50, 100, 200] as defined in clause 5.3.5 of TS 38.101-1 version 15.7.0 [2] and TS 38.101-2 version 15.7.0 [3]. For IAB-MT, to determine whether the IAB-MT supports a channel bandwidth of 100 MHz, the network checks channelBW-DL-IAB-r16. For FR1, the bits in channelBWs-DL (without tail bits) starting from the leading / leftmost bit indicate 5 MHz, 10 MHz, 15 MHz, 20 MHz, 25 MHz, 30 MHz, 40 MHz, 50 MHz, 60 MHz, and 80 MHz. For FR2, channelBWs-DL (without tail bits) starting from the leading / leftmost bit indicates 50 MHz, 100 MHz, and 200 MHz. The third / rightmost bit (for 200 MHz) shall be set to 1. For IAB-MT, the third / rightmost bit (for 200 MHz) is ignored. To determine whether the IAB-MT supports a channel bandwidth of 200 MHz, the network checks channelBW-DL-IAB-r16. For FR1, the leading / leftmost bit in channelBWs-DL-v1590 indicates 70 MHz, the second leftmost bit indicates 45 MHz, the third leftmost bit indicates 35 MHz, and all the remaining bits in channelBWs-DL-v1590 shall be set to 0. Note: To determine whether the UE supports a specific SCS for a given band, the network verifies supportedSubCarrierSpacingDL and scs-60kHz. To determine whether the UE supports a channel bandwidth of 90 MHz, the network may ignore this capability and instead verify channelBW-90mhz and supportedBandwidthCombinationSet. For serving cells with other channel bandwidths, the network verifies channelBWs-DL, supportedBandwidthCombinationSet, supportedBandwidthCombinationSetIntraENDC, asymmetricBandwidthCombinationSet (for bands supporting asymmetric channel bandwidths as defined in clause 5.3.6 of TS 38.101-1 [2]), and supportedBandwidthDL. Band Yes N / A N / A channelBWs-UL Indicates the channel bandwidths supported by the UE for each subcarrier spacing. For a band without channelBWs-UL (no tail bits) or for a specific scs-XXkHz entry not existing for the supported subcarrier spacing, it means that for a given band or specific SCS entry, the UE supports the channel bandwidths defined in item 5.3.5 of TS 38.101-1 version 15.7.0 [2] and TS 38.101-2 version 15.7.0 [3] among [5, 10, 15, 20, 25, 30, 40, 50, 60, 80, 100] and [50, 100, 200]. For IAB-MT, to determine whether the IAB-MT supports a 100 MHz channel bandwidth, the network checks channelBW-UL-IAB-r16. For FR1, the bits in channelBWs-UL (no tail bits) starting from the preamble / leftmost bit indicate 5 MHz, 10 MHz, 15 MHz, 20 MHz, 25 MHz, 30 MHz, 40 MHz, 50 MHz, 60 MHz, and 80 MHz. For FR2, the channelBWs-UL (no tail bits) starting from the preamble / leftmost bit indicate 50 MHz, 100 MHz, and 200 MHz. The third / rightmost bit (for 200 MHz) shall be set to 1. For IAB-MT, the third / rightmost bit (for 200 MHz) is ignored. To determine whether the IAB-MT supports a 200 MHz channel bandwidth, the network checks channelBW-UL-IAB-r16. For FR1, the preamble / leftmost bit in channelBWs-UL-v1590 indicates 70 MHz, the second leftmost bit indicates 45 MHz, the third leftmost bit indicates 35 MHz, and all the remaining bits in channelBWs-UL-v1590 shall be set to 0. Note: To determine whether the UE supports a specific SCS for a given band, the network verifies supportedSubCarrierSpacingUL and scs-60kHz. To determine whether a UE supports a channel bandwidth of 90 MHz, the network may ignore this capability and instead verify channelBW-90mhz and supportedBandwidthCombiantionSet. For serving cells with other channel bandwidths, the network verifies channelBWs-UL, supportedBandwidthCombinationSet, supportedBandwidthCombinationSetIntraENDC, asymmetricBandwidthCombinationSet (for bands supporting asymmetric channel bandwidths as defined in clause 5.3.6 of TS 38.101-1 [2]), and supportedBandwidthUL. Band Yes N / A N / A multipleRateMatchingEUTRA-CRS-r16 Indicates whether the UE supports multiple E-UTRA CRS rate matching patterns, which are only supported by FR1. The capability signaling includes the following parameters: -maxNumberPatterns-r16 indicates the maximum total number of LTE-CRS rate matching patterns within an NR carrier using 15 kHz SCS. The UE may report a value greater than 2 only if the UE reports a value of maxNumberNon-OverlapPatterns-r16 greater than 1. -maxNumberNon-OverlapPatterns-r16 indicates the maximum number of non-overlapping LTE-CRS rate matching patterns within an NR carrier using 15 kHz SCS. The UE may include this feature only if the UE indicates support for rateMatchingLTE-CRS. Band No N / A Only FR1 overlapRateMatchingEUTRA-CRS-r16 Indicates whether the UE supports two overlapping LTE-CRS rate matching patterns within a part of an NR carrier overlapping with an LTE carrier using 15 kHz SCS. If the UE supports this feature, the UE needs to report multipleRateMatchingEUTRA-CRS-r16. Band No N / A Only FR1 pdsch-256QAM-FR2 Indicates whether the UE supports the 256QAM modulation scheme for PDSCH in FR2 as defined in subclause 7.3.1.2 of TS 38.211 [6]. Band No N / A Only FR2 pusch-256QAM Indicates whether the UE supports the 256QAM modulation scheme for PUSCH as defined in subclause 6.3.1.2 of TS 38.211 [6]. Band No N / A N / A rateMatchingLTE-CRS Indicates whether the UE supports receiving a PDSCH with resource mapping that excludes the REs determined by the higher layer configured LTE-carrier configuration common RS as specified in TS 38.214

[12] . Band Yes N / A N / A separateCRS-RateMatching-r16 Indicates whether the UE supports rate matching for the configured CRS pattern associated with the CORESETPoolIndex (if configured), and applied to the PDSCH scheduled by DCI detected on the CORESET with the same CORESETPoolIndex value. UEs indicating support for this feature shall support multiDCI-MultiTRP-r16 and overlapRateMatchingEUTRA-CRS-r16. This only applies to 15 MHz SCS. Band No N / A Only FR1 Definition of parameters Per M FDD-TDD DIFF FR1-FR2 DIFF oneFL-DMRS-ThreeAdditionalDMRS-DL Define whether the UE supports the DM-RS mode for DL transmissions with 1-symbol prepended DM-RS with three additional DM-RS symbols. FS No N / A N / A oneFL-DMRS-TwoAdditionalDMRS-DL Define the support for the DM-RS mode for DL transmissions with 1-symbol prepended DM-RS with two additional DM-RS symbols and more than one antenna port. FS Yes N / A N / A Definition of parameters Per M FDD-TDD DIFF FR1-FR2 DIFF channelBW-90mhz Indicate whether the UE supports a channel bandwidth of 90 MHz. For FR1, the UE shall indicate support according to TS 38.101-1 [2], Table 5.3.5-1. FSPC CY N / A Only FR1 maxNumberMIMO-LayersPDSCH Define the maximum number of spatial multiplexing layers supported by the UE for DL reception. For a single CC stand-alone NR, it must have the ability to transmit to support at least 4 MIMO layers in a band where 4Rx is specified as mandatory for a given UE and at least 2 MIMO layers in FR2. If not present, the UE does not support MIMO on this carrier. FSPC CY N / A N / A supportedBandwidthDL Indicate the maximum DL channel bandwidth supported by the UE for a given SCS within a single CC (and in the case of DAPS handover within the frequencies of the source and target cells), as defined in Table 5.3.5-1 in TS 38.101-1 [2] for FR1 and Table 5.3.5-1 in TS 38.101-2 [3] for FR2. For FR1, unless indicated as optional as appropriate, all the bandwidths listed in Table 5.3.5-1 of TS 38.101-1 for each frequency band shall be mandatory for a single CC. For FR2, the mandatory CBW settings are 50 MHz, 100 MHz, and 200 MHz. When this field is included in a band combination with a single band entry and a single CC entry (i.e., a non-CA band combination), the UE shall indicate the maximum channel bandwidth of the band according to TS 38.101-1 [2] and TS 38.101-2 [3]. Note: To determine whether the UE supports a 90 MHz channel bandwidth, the network may ignore this capability and instead verify channelBW-90mhz and supportedBandwidthCombinationSet. For serving cells with other channel bandwidths, the network verifies channelBWs-DL, supportedBandwidthCombinationSet, supportedBandwidthCombinationSetIntraENDC, asymmetricBandwidthCombinationSet (for bands that support asymmetric channel bandwidths as defined in clause 5.3.6 of TS 38.101-1 [2]), and supportedBandwidthDL. FSPC CY N / A N / A supportedModulationOrderDL In the maximum data rate calculation defined in 4.1.2, indicates the maximum supported modulation order to be applied to the downlink in the carrier. If included, as long as the UE supports a higher value of modulation for the downlink, the network may use a modulation order higher than the value indicated in this field on this serving cell. If not included: - For FR1, the network uses the modulation order signaled in pdsch-256QAM-FR1. - For FR2, if signaled, the network uses the modulation order signaled per band (i.e., pdsch-256QAM-FR2). If not signaled in a given band, the network shall use the modulation order 64QAM. In all cases, it shall be ensured that the data rate does not exceed the maximum data rate (DataRate) and the maximum data rate per CC (DataRateCC) according to TS 38.214

[12] . FSPC No N / A N / A Definition of Parameters Per M FDD-TDD DIFF FR1-FR2 DIFF channelBW-90mhz Indicates whether the UE supports a channel bandwidth of 90 MHz. For FR1, the UE shall indicate support according to Table 5.3.5-1 in TS 38.101-1 [2]. FSPC CY N / A FR1 only maxNumberMIMO-LayersCB-PUSCH Defines the maximum number of supported MIMO layers at the UE for PUSCH transmission using codebook precoding. UEs indicating support for this feature shall also indicate support for the PUSCH codebook consistency subset. This feature is not supported for SUL. FSPC No N / A N / A maxNumberMIMO-LayersNonCB-PUSCH Defines the maximum number of supported MIMO layers at the UE for PUSCH transmission using non-codebook precoding. This feature is not supported for SUL. UEs supporting non-codebook based on PUSCH transmission shall indicate support for maxNumberMIMO-LayersNonCB-PUSCH, maxNumberSRS-ResourcePerSet, and maxNumberSimultaneousSRS-ResourceTx simultaneously. FSPC No N / A N / A supportedBandwidthUL Indicates the maximum UL channel bandwidth supported by the UE for a given SCS within a single CC (and in the case of DAPS handover between the source and target cell frequencies), as defined in Table 5.3.5-1 in TS 38.101-1 [2] for FR1 and Table 5.3.5-1 in TS 38.101-2 [3] for FR2. For FR1, all the bandwidths listed in Table 5.3.5-1 of TS 38.101-1 for each frequency band shall be mandatory for a single CC, unless indicated as optional as appropriate. For FR2, the mandatory CBW settings are 50 MHz, 100 MHz, and 200 MHz. When this field is included in a band combination with a single band entry and a single CC entry (i.e., a non-CA band combination), the UE shall indicate the maximum channel bandwidth of the band according to TS 38.101-1 [2] and TS 38.101-2 [3]. Note: To determine whether the UE supports a 90 MHz channel bandwidth, the network may ignore this capability and instead verify channelBW-90mhz and supportedBandwidthCombiantionSet. For serving cells with other channel bandwidths, the network verifies channelBWs-UL, supportedBandwidthCombinationSet, supportedBandwidthCombinationSetIntraENDC, asymmetricBandwidthCombinationSet (for bands supporting asymmetric channel bandwidths as defined in clause 5.3.6 of TS 38.101-1 [2]), and supportedBandwidthUL. FSPC CY N / A N / A supportedModulationOrderUL In the maximum data rate calculation defined in 4.1.2, indicates the maximum supported modulation order to be applied for the uplink in the carrier. If included, the network may use a modulation order higher than the value indicated in this field on this serving cell as long as the UE supports a higher value of modulation for the uplink. If not included, - For FR1 and FR2, if transmitting, the network uses the modulation order for transmission per band (i.e., pusch-256QAM). If not transmitting in a given band, the network shall use the modulation order 64QAM. In all cases, it shall be ensured that the data rate does not exceed the maximum data rate (DataRate) and the maximum data rate per CC (DataRateCC) according to TS 38.214

[12] . FSPC No N / A N / A Definition of parameters Per M FDD-TDD DIFF FR1-FR2 DIFF dl-64QAM-MCS-TableAlt Indicates whether the UE supports an alternative 64QAM MCS table for the PDSCH. UE No No Yes maxLayersMIMO-Adaptation-r16 Indicates whether the UE supports a network architecture of maxMIMO-Layers per DL BWP. If the UE supports this feature, the UE needs to report maxLayersMIMO-Indication. UE No No Yes maxLayersMIMO-Indication Indicates whether the UE supports a network architecture of maxMIMO-Layers as specified in TS 38.331 [9]. UE Yes No No mux-HARQ-ACK-PUSCH-DiffSymbol Indicates whether the UE supports HARQ-ACK multiplexed once per time slot on the PUSCH with / without non-periodic CSI when the start OFDM symbol of the PUSCH is different from the start OFDM symbol of the PUCCH resource on which the HARQ-ACK will be transmitted. This only applies to non-shared spectrum channel access. For shared spectrum channel access, mux-HARQ-ACK-PUSCH-DiffSymbol-r16 applies. UE Yes No Yes oneFL-DMRS-ThreeAdditionalDMRS-UL Defines whether the UE supports a DM-RS mode for UL transmission with 1-symbol pre-loaded DM-RS with three additional DM-RS symbols. UE No No Yes oneFL-DMRS-TwoAdditionalDMRS-UL Support for a DM-RS pattern for UL transmissions with 1-symbol preloaded DM-RS with 2 additional DM-RS symbols and more than 1 antenna port is defined. UE Yes No Yes pdsch-256QAM-FR1 Indicates whether the UE supports the 256QAM modulation scheme for PDSCH in FR1 as defined in 7.3.1.2 of TS 38.211 [6]. UE Yes No Only FR1 pdsch-MappingTypeA Indicates whether the UE supports receiving PDSCH using PDSCH mapping type A with less than seven symbols. This field shall be set to supported. UE Yes No No pdsch-MappingTypeB Indicates whether the UE supports receiving PDSCH using PDSCH mapping type B. UE Yes No No pdsch-RE-MappingFR1-PerSymbol / pdsch-RE-MappingFR1-PerSlot Indicates the maximum number of supported PDSCH resource element (RE) mapping patterns in FR1, each mapping pattern described as a resource (including NZP / ZP CSI-RS, CRS, CORESET, and SSB) or a bitmap. The number of overlapping patterns in symbols in a CC and in slots in a CC is limited by the respective capability parameter. The value n10 means 10 RE mapping patterns and n16 means 16 RE mapping patterns, and so on. The UE shall set the fields pdsch-RE-MappingFR1-PerSymbol and pdsch-RE-MappingFR1-PerSlot to at least n10 and n16, respectively. In the exceptional case where the UE does not include the fields, the network may assume that the UE supports the required minimum value anyway. UE Yes No Only FR1 pdsch-RE-MappingFR2-PerSymbol / pdsch-RE-MappingFR2-PerSlot Indicates the maximum number of supported PDSCH resource element (RE) mapping patterns for FR2, where each mapping pattern is described as a resource (including NZP / ZP CSI-RS, CORESET, and SSB) or a bitmap. The number of overlapping patterns in symbols in a CC and in slots in a CC is limited by respective capability parameters. The value n6 means 6 RE mapping patterns and n16 means 16 RE mapping patterns, and so on. The UE shall set the fields pdsch-RE-MappingFR2-PerSymbol and pdsch-RE-MappingFR2-PerSlot to at least n6 and n16, respectively. In the exceptional case where the UE does not include the fields, the network may assume, in any case, that the UE supports the required minimum value. UE Yes No Only FR2 rateMatchingCtrlResrcSetDynamic Indicates whether the UE supports dynamic rate matching for DL control resource sets. UE Yes No No rateMatchingResrcSetDynamic Indicates whether the UE supports receiving a PDSCH with resource mapping based on a dynamic indication in the scheduling DCI as specified in TS 38.214

[12] , where the resource mapping excludes the REs corresponding to a resource set configured with RB symbol-level granularity indicated by bitmaps (see patternType in RateMatchPattern in TS 38.331 [9]). UE No No No rateMatchingResrcSetSemi-Static Indicates whether the UE supports receiving PDSCH with resource mapping according to the semi-static configuration specified in TS 38.214

[12] , where the resource mapping excludes the REs corresponding to the resource set with RB symbol-level granularity indicated by bitmaps and controlResourceSet (see patternType in RateMatchPattern in TS 38.331 [9]). UE Yes No No Mapping Across Slot; MAS

[0099] The subject matter disclosed herein provides techniques for processing Mapping Across Slot (MAS) for transport blocks, which can be used by transmitters (UE or gNB) in a wireless network such as a 5G wireless network. MAS processes the TBs of resource mapping sizes across multiple time slots, and the transmitter continuously transmits exactly one transmission of the TB of the transmission size across the time slot boundary. In one embodiment, the TBS determination for MAS processing sets the coding rate to be equal to, the available resources correspond to multiple time slots, and the resulting TBS is. The MAS processing can be performed by a TB processing chain similar to the processing chain depicted in FIG. 6 but modified as described herein in conjunction with FIGS. 9 to 40. The TB processing chain for providing MAS processing for transport blocks can include circuits and / or modules that perform the functionality described in conjunction with MAS processing. That is, the functionality associated with TBS determination, TB selection and CB determination, coding, rate matching, interleaving, and mapping from virtual resources to physical resources can be performed by one or more circuits and / or one or more modules.

[0100] FIG. 9 illustrates some details of codewords that can be transmitted across multiple time slots depending on the size of the data block according to the subject matter disclosed herein. For each of the multiple code block groups (CBGs), the number of code blocks belonging to one CBG is. The condition for code blocks that do not cross the time slot boundary is divided by. For MAS processing as disclosed herein, if the number of information bits is and the target rate is, then the total number of coding bits is, which can be distributed across the REs of multiple time slots. The size and the number of code blocks are and respectively. The number of coding bits per code block is. When the code blocks cross the time slot boundary, the MAS technique can provide a greater opportunity for the code blocks crossing the time slot boundary to maintain a sudden decrease in channel quality in some time slots.

[0101] Figure 10 depicts an example scenario 1000 where a data block according to the subject matter disclosed herein is small enough to fit into a single code block CB1 that spans a timeslot boundary. Using a Multi-Slot TBS (M-TBS) determination process, the code block CB1 can be mapped across timeslots into a single transport block 1001 such that, in the example of Figure 10, one code block 1001 spans two consecutive timeslots (e.g., timeslot 1002 and timeslot 1003). Rate matching can be used to allow the code block CB1 to exist on both timeslot 1002 and timeslot 1003 (e.g., across the timeslot boundary 1004).

[0102] Figure 11 depicts an example scenario 1100 where a relatively large data block according to the subject matter disclosed herein is adapted to two code blocks CB1 and code block CB2. That is, the two code blocks CB1 and code block CB2 are mapped into a single transport block 1101 that spans two consecutive timeslots (e.g., timeslot 1102 and timeslot 1103). The transport block 1101 spans the timeslot boundary 1104 between timeslot 1102 and timeslot 1103.

[0103] Figure 12 illustrates an example scenario 1200 where a relatively extremely large data block according to the subject matter disclosed herein is adapted to a plurality of code blocks CB1 to code block CBP. The individual code blocks CB1 to code block CBP are mapped into a single transport block 1201 that spans (in this example) three consecutive timeslots 1202 to timeslot 1204. The transport block 1201 spans the timeslot boundary 1205 and the timeslot boundary 1206.

[0104] Figure 13 depicts an example scenario 1300 according to the subject matter disclosed herein when not divided by. In Figure 13, the MAS selects code blocks CB1 to code block CB4 that are mapped into a single transport block 1301 that spans three consecutive timeslots 1302 to timeslot 1304. The MAS allows the use of a longer RM output such that all data bits of the code blocks CB1 to code block CB4 are transmitted in one transport block. When CBG is enabled, the retransmission by the MAS involves the retransmission of the CBG for which the transmission has failed. TB mapping across non-contiguous resources

[0105] Resource allocation for MAS PUSCH transmission can include resources that are non-contiguous in time. Figure 14 depicts an example of a scenario 1400 where the resources available for MAS PUSCH transmission are non-contiguous. Scenario 1400 depicts two timeslots 1401 and timeslot 1402, where each timeslot contains 14 symbols. The non-contiguous resources allocated for MAS PUSCH are indicated at 1403.

[0106] The discontinuous resource allocation can be the result of, for example, a PDSCH / PUSCH retransmission type B resource allocation mechanism, where some intermediate resources are not available due to a conflict with the TDD symbol configuration. In such discontinuous resource allocation scenarios, the UE can utilize the set of resources available for type B repetition for the transmission of a MAS transmission across all available resources, as indicated by, for example, resource 1404. Based on the capabilities of MAS PUSCH transmission, the allocation of discontinuous resources can be a specific resource allocation technique for MAS transmission that allows such configuration of discontinuous resources.

[0107] If the allocated resources are the result of a repetition type B scheduling, the determination of the transport block for the original transmission can be the same. Alternatively, if the UE is indicated the allocated resources as the resources for the original transmission, the transport block can be determined based on the allocated resources. The transport block determination can follow the Rel-16 TBS determination technique or alternatively the multi-slot TBS (M-TBS) determination technique. Channel coding and code block segmentation can follow the Rel-16 process. Rate matching can be provided by the techniques described below. Example 1

[0108] The first exemplary embodiment disclosed herein provides multi-slot TBS mapping-with-repetition (M-MWR). M-MWR includes the possibility of scheduling higher TBS values that cannot use the typical MWR-based or Rel-16-based TBS determination process. The TBS value determined by M-MWR is mapped to the allocated resources of one time slot, resulting in a higher coding rate per time slot than the coding rate indicated by the normally configured MCS index.

[0109] The TBS determination using the typical MWR process sets the coding rate equal to, the available resources correspond to a single time slot, and the resulting TBS is. In contrast, the TBS determination for M-MWR calculates the sum of intermediate TBS values, where each intermediate TBS value corresponds to the TBS determination for each time slot of K time slots by setting the coding rate of the time slot equal to and setting the available resources to the resources available in the time slot. Example 2

[0110] MAS can be configured such that the MAS mapping of the transport block avoids crossing the time slot boundary. A condition for the code blocks not to cross the time slot boundary is to ensure that the rate matching output of each code block fits within the resources of one time slot. This condition can be expressed as follows. Assume is the number of coding bits available in the time slot. Assume and. Then, the condition for the code blocks not to cross the time slot boundary can be equivalent to the following. For each code block,, there exists, such that (2) and. (3)

[0111] In this case, the value of may correspond to a time slot containing code blocks, and the condition ensures that the number of code blocks is fully present in the time slot. When the scheduling / configuration is based on the transmission of MAS, the gNB can ensure that these conditions are met. Example 3

[0112] FIG. 15 depicts three positions in the MAS transport block processing chain 1500 that can perform a cancellation indication (CI) according to the subject matter disclosed herein. The MAS transport block processing chain depicted in FIG. 15 can be part of the TX processing circuitry 303 in an exemplary embodiment of the UE 116 depicted in FIG. 3. In one embodiment, the processor 307 of the UE 116 can control the operation of the MAS TB processing chain depicted in FIG. 15. In another embodiment, a processor (not shown) that is part of the TX processing circuitry 303 can control the operation of the MAS TB processing chain depicted in FIG. 15.

[0113] The operation 1500 of the MAS transport block processing chain can include a TBS determination operation 1501, a code block segmentation operation 1502, a channel coding operation 1503, a rate matching operation 1504, and a puncturing operation 1505. In one embodiment, the channel coding operation 1503 can be performed by an encoder 503, and the rate matching operation 1504 can be performed by a rate matcher 504 in the transmitter structure 501 depicted in FIG. 5A. One or more of operations 1501 to 1505 can be performed by circuitry and / or modules.

[0114] FIG. 16A depicts an example scenario 1600a of a UE receiving a cancellation indication in a time slot for a UL MAS transmission. In the example depicted in FIG. 16A, six time slots 1601 to 1606 have been allocated for MAS-based transmission. Code blocks CB1 to CB13 have been mapped into time slots 1601 to 1606. A CI 1607 has been received indicating the cancellation of the transmission in time slot 1604.

[0115] There can be various sources of cancellation indication. In the case of UL transmission (e.g., MAS PUSCH), examples of cancellation sources include, but are not limited to: the UE receiving DCI format 2_0 carrying an SFI value that indicates the time slot format conflicting with the UL transmission; conflict with the semi-static DL / UL time slot format; the UE receiving DCI format 2_4 carrying a CI request that explicitly indicates cancellation of the UL transmission in a specified time slot; temporal conflict with other UL signals having a different priority index from the PUSCH; conflict between CG-PUSCH and DG-PUSCH of the same HARQ process; and conflict between dynamically scheduled PDSCH and / or CSI-RS and CG-PUSCH. Although there may be different cancellation mechanisms for DL transmission (e.g., MAS PDSCH), for UL transmission, the main mechanism for handling cancellation can be the same.

[0116] Referring back to FIG. 15, the first location 1510 where the cancellation indication can be processed is at the rate matching operation 1504 by changing the output of the rate matching operation 1504. The resources remaining after applying the cancellation indication at the time slot level can be determined first. Some entire time slots can be cancelled, for example, based on the cancellation indication. For the determined set of code blocks, the output of the rate matching can be changed based on the remaining resources. In the case of this example, 13 code blocks are reallocated across the remaining resources for MAS transmission.

[0117] The second location 1511 where the cancellation indication can be processed is at the output of the rate matching operation 1504 by performing puncturing of the output of the rate matching operation 1504. This method can maintain the transmission of some or all of the original code blocks and code blocks that have been determined based on the scheduled MAS transmission. There are four variations for the method using the second location 1511.

[0118] The first variation of handling CI by performing puncturing involves cancelling all CB transmissions within the time slot of the cancellation indication, as depicted in FIG. 16B. If the part of the coded sequence corresponding to the cancelled CB within the time slot extends to an adjacent time slot, then the part of the CB that is transmitted to the adjacent time slot is also extended. As depicted by the example scenario 1600b in FIG. 16B, a part of CB7 in transmission time slot 1603 and a part of CB9 in time slot 1605 are transmitted.

[0119] The second variation of handling CI by performing puncturing involves cancelling the CB transmissions within the indicated time slot. That is, if the part of the coded sequence corresponding to the cancelled CB extends to an adjacent time slot, it is also cancelled. As depicted by the example scenario 1600c in FIG. 16C, a part of CB7 in time slot 1603 and a part of CB9 in time slot 1605 are cancelled.

[0120] The third variation of the punch-through handling CI involves canceling all CB transmissions within the indicated time slots, and if a portion of the coded sequence corresponding to the canceled CB extends into adjacent time slots, all transmissions in these adjacent time slots are also canceled. The cancellation continues for adjacent cells until there are no more canceled CBs with extended portions. As depicted by the example scenario 1600d in FIG. 16D, the transmissions in time slots 1602 to 1605 are canceled.

[0121] The fourth variation of the punch-through handling CI depicted by the example scenario 1600e in FIG. 16E involves canceling all time slots within the MAS PUSCH transmission.

[0122] For performing the four variations of the punch-through handling CI depicted in FIGS. 16B to 16E, an indication of the transmission in the canceled time slots should be received at a time sufficiently prior to the cancellation of the time slots such that the transmitter (at the UE) has sufficient time to perform the appropriate cancellation. It is worth noting that such methods can provide a robust handling of the cancellation indication. For example, in the case where the transmitter (e.g., the UE in the case of MAS PUSCH) misses the cancellation indication, the receiver (e.g., the gNB) can make a decision to ignore the transmitted CBs in the canceled time slots without affecting the transmission of the remaining CBs in other resources.

[0123] The third location 1512 where the cancellation indication can be processed is at the TBS determination operation 1501, and outputs a code block segmentation operation 1502 by changing the TBS determination and / or CB segmentation. The UE may not necessarily follow the previously determined CB and can perform different physical shared channel transmissions in the available resources after the cancellation. In this case, the remaining resources are first determined after applying the cancellation indication at the time slot level, that is, some entire time slots are canceled based on the cancellation indication. Thus, the canceled time slots within the set of allocated time slots for MAS transmission will result in two separate groups of consecutive time slots, and the transmitter can consider the two separate groups of time slots as resources available for physical shared channel transmission. For example, canceling time slot 1604 in the example scenario 1600a depicted in FIG. 16A leaves time slots 1601, 1602, and 1603 as one group of available time slots, and time slots 1605 and 1606 as another group of available time slots. The transmitter can then use these resources for physical shared channel transmission.

[0124] In the group of consecutive resources remaining after the cancellation indication, several options are available for physical shared channel transmission. The first option is that the transmitter can send Rel-16 transmissions in each of the time slots. In this case, the transmissions can all be repetitions of the initially expected TB for MAS transmission. If the TBS of the original MAS transmission is greater than the maximum allowable TBS threshold for individual Rel-16 transmissions, the transmission of this TB can be cancelled. Additionally, the original TB may not be successfully transmitted as a repetition in the set of Rel-16 physical shared channel transmissions unless the achievable coding rate is met.

[0125] Alternatively, for the first option of the group of consecutive resources remaining after the cancellation indication, the TB to be transmitted in the remaining time slots can be determined separately for each time slot. The parameters for determining the TB (such as the MCS index and coding rate) can be set to the values provided for the original MAS transmission. As yet another alternative to the first option, the coding rate for each physical shared channel transmission can be set to the effective coding rate that would be achieved for each time slot when performing the original MAS transmission.

[0126] For the second option of the group of consecutive resources remaining after the cancellation indication, the transmitter can send MAS transmissions in the available set of consecutive time slots. For example, in the example given above, the transmitter can send two MAS transmissions, one spanning time slots 1601 to 1603, and one spanning time slots 1605 to 1606. A similar process for TB determination follows that of the first option for the group of consecutive resources remaining after the cancellation indication. If the TBS is greater than the maximum allowable TBS threshold, the TB can be set to the initially determined TB, and the MAS transmission is cancelled. The amount of resources determined for each MAS transmission can also depend on the limitation on the achievable coding rate, as described elsewhere in this document. As an alternative to the second option, a new TB can be determined for each of the new MAS transmissions.

[0127] For the third option of the group of consecutive resources remaining after the cancellation indication, the transmitter can determine which type of physical shared channel (conventional or MAS) will be transmitted in the available resources. That is, the transmitter can decide to perform conventional transmissions in the time slots while performing MAS transmissions across some other time slots. For example, the decision to do so can be based on the target TB and selecting the minimum amount of resources that match the TBS for a given coding rate. Example 3a The decision to perform PUSCH transmission in response to a cancellation indication can be configured in different ways, e.g., via RRC configuration or via a dynamic indication. If the cancellation is via RRC configuration, all MAS PUSCH transmissions can be configured to be processed in case of cancellation according to a specific method. Alternatively, different types of MAS PUSCH transmissions can be processed in different ways (e.g., dynamically scheduled MAS PUSCH transmissions, CG-based MAS PUSCH, and the like). For dynamically scheduled MAS PUSCH or CG2-based MAS PUSCH, the way in which the cancellation can be processed can be indicated in the scheduling / activation PDCCH. Restrictions related to scheduling MAS PUSCH after a cancellation indication

[0129] There may be restrictions on the determination of the scheduling of MAS transmissions in response to a cancellation indication. Two cases can be distinguished. The first case is whether there is a TBS threshold value on the scheduled MAS transmission. The second case is whether there is a restriction on the overall coding rate achievable when scheduling a MAS transmission with the original TBS after receiving a cancellation indication. TBS threshold value on the scheduled MAS PUSCH

[0130] The TBS determination for MAS transmission can include resources from multiple time slots, and thus it may be possible that the resulting TBS may be too large (e.g., due to implementation issues). Therefore, the final TBS available for MAS transmission can be limited by an upper value limit. Consider the TBS determination procedure that generates a value that can be marked as an intermediate value obtained from the procedure for determining the TBS. Subsequently, the final TBS value can be given as the minimum between the intermediate value and the threshold value. (4)

[0131] The value of the threshold can be, for example, a multiplication factor of the maximum TBS value obtained from the Rel-16 TBS determination procedure. The maximum TBS value obtained from the Rel-16 TBS determination procedure can be calculated to be equal to (corresponding to the maximum resource allocation for PUSCH, and four (4) transmission layers and the highest available coding rate). Therefore, for some suitable values, can be equal to. Restrictions on the overall coding rate achievable

[0132] When receiving a cancellation indication for some time slots, the transmitter can prevent the transmission of the original MAS transmission and can choose to transmit a set of physical shared channel transmissions in the remaining resources, where each transmission transmits a TB determined based on the resources of the original MAS transmission. The newly determined transmissions can be Rel-16 transmissions (i.e., one physical shared channel transmission per time slot) or MAS transmissions (i.e., each transmission can span more than one time slot and the number of time slots in each such transmission can be determined).

[0133] Due to the natural reduction in the amount of available resources after cancellation, the achievable coding rate per transmission for newly determined entity common channel transmissions can be greater than the original achievable coding rate. More specifically, if the number of available coding bits per transmission is less than the TBS, the achievable coding rate per entity common channel can be greater than 1. In this case, one transmission may not be able to transmit the TBS.

[0134] When such a situation occurs, the receiver may depend on a set of transmissions (not just one entity common channel transmission) to decode the TB. However, the success of the decoding operation of the TB may also depend on the RV index used for such transmissions.

[0135] To clarify the previous point, consider the case where the TBS of the original TB is equal to. After the time slot cancellation, assume that the available number of coding bits in all resources is equal to, where. In this case, if the set of newly determined transmissions contains two entity common channel transmissions, each of which contains half of the resources, the coding rate of each transmission is equal to 2. Two cases can be distinguished.

[0136] In the first case, if the RV indices of the two transmissions are the same, the total coding rate of the two transmissions remains unchanged, and thus, the decoding attempt of the TB based on the two transmissions may fail. In the second case, if the RV indices of the two transmissions are different, the total coding rate can be less than or equal to 1, and thus, the decoding attempt of the TB based on the two transmissions may have a chance of success.

[0137] The two cases highlight the importance of determining the coding rate per time slot related to the specified RV index of the newly determined transmissions, which is formalized next. However, first assume that the newly determined transmissions inherently have some configuration attributes from the original MAS transmission configuration (such as modulation order, DMRS configuration, number of transmission layers, burden, etc.).

[0138] Assume that the set of new entity common channel transmissions is indicated by a set of indices, where the first transmission corresponds to the index, the second transmission corresponds to, and so on. When determining the new set of transmissions, the transmitter can be configured to use a fixed RV version for all new transmissions, or the transmitter can be configured with a series of RV indices, where each transmission sequentially uses one index from the sequence. Assume that the unique set of RV indices used by the transmission is marked as. For each, assume that is the index of the transmission in the new set of transmissions that uses the RV index. Assume that represents the amount of coding bits available for the transmission with the index.

[0139] For successful decoding, the total coding rate of the TB should be less than or equal to. This translates to the following condition: (5) or. (6)

[0140] This condition translates to the sum of the unique scrambling bits across all transmissions being greater than. Depending on the type of scheduled transmission, this condition can be further simplified. For example, in a first scenario, when the newly determined transmission is a MAS (multi-slot based) transmission, the amount of available scrambling bits per transmission can depend on how many slots are used for the scheduled MAS transmission. In this case, the number of slots included in each transmission can be selected such that the foregoing condition is satisfied.

[0141] In a second scenario where the newly determined PUSCH is a Rel-16 (one-slot based) PUSCH transmission, all transmissions include a fixed number of resource elements and can thus have a fixed number of available scrambling bits per transmission. Let this number be denoted as. In this case, the condition simplifies to. (7) Example 4

[0142] In one embodiment, MAS may be allowed to further segment the RM output sequence across the slot boundaries surrounding the boundary. For example, FIG. 17A depicts an example MAS transmission of two CBs CBG1 and CBG2 across three slots 1701 to 1703. The segmentation can cause the RM output sequence corresponding to the CB to be divided into multiple parts, as depicted in FIG. 17B. The segmented parts can be considered completely independent transmissions (i.e., the receiver can use them separately in decoding the CB), or the parts can be used jointly for decoding in a similar RV-like fashion.

[0143] Taking into account the resulting segmentation of the CBs involved, the RV version of each of the transmission parts can be determined. According to the subject matter disclosed herein, the RV version of each part can be determined to use the same RV index of the original CB. Alternatively, a series of RV indices can be specified based on determining which RV indices of consecutive CB parts. For example, the RV index sequence can be configured, such as 0, 2, 1, 3. Subsequently, the RV index of each part of the CB iterates sequentially (and cyclically) on this sequence starting from the RV index of the original CB. In FIG. 17B, consider the RV index of the original CB2RV1 to be 0. Subsequently, the first part of the CB can have an RV index equal to 0, and the second part of the CB can have an RV index equal to 2.

[0144] Performing segmentation can be done in different ways. Referring to the TB processing chain 1800 in FIG. 18, one method for segmenting the code block can be as follows. The TBS determination operation 1801 calculates the TBS based on the resources of all the slots. The CB segmentation operation 1802 receives the TBS as input and provides the CB as specified in Rel-16 (using the same). The coding operation 1803 codes the CB into a codeword as specified in Rel-16, followed by the rate matching operation 1804.

[0145] Operations 1801 through 1804 may be performed by one or more circuits and / or modules. RM operation 1804 may vary according to the subject matter disclosed hereinbelow. Initially, RM operation 1804 may be set with a set of time slots, in which write code bits will be allocated, and the number of write code bits available for each time slot is labeled as for the th time slot, where. The total number of available write code bits is, and the ratio of each CB can be determined from. For each CB, a pointer is maintained, where specific bits will be allocated in the RM procedure. For, the pointer may be referred to as. All in the pointers are initialized to the bits corresponding to the RV index. represents the length of the encoder output of the th CB (which should all be the same). Index is set equal to 1 and index is set equal to 1. The next bit to be allocated in the th time slot is represented by, and that bit is set to.

[0146] When (loop above time slot) and (loop above CB): The number of bits is allocated from the encoder output of the th CB to the number of bits of the th time slot. The pointer is set to. If, then set, set, and set to the RV index of the specified index that is a part of the number of CBs in the time slot. Otherwise, if, then set. If, then and. If, then set.

[0147] Alternatively, the RM operation may vary as follows. RM operation 1804 may be set with a set of time slots, in which write code bits will be allocated, and there is provided the number of write code bits available for each time slot, labeled as for the th time slot, where. The total number of available write code bits is, and the ratio of each CB can be determined from. For each CB,, if there exists and, such that, (8) (9) then in the case of maximum satisfaction of the condition, the RM size of the CB is broken into values corresponding to the time slots. (10)

[0148] If, then the CB is broken into 2 RM sizes of. (11)

[0149] For multiple RM blocks of multiple time slots, the RV index of each part can be determined as described herein in relation to the segmentation of CBs across time slots.

[0150] In one embodiment, a CB spanning a time slot boundary may be changed to be restricted within only one of the time slots it originally spanned. The time slot within which the CB is restricted may be the time slot that originally contained the largest portion of the CB, or based on some other rule for selecting which time slot the CB is restricted in. Determining the RM output of each CB in each time slot follows the concepts disclosed herein.

[0151] When a part of the segment CB is transmitted only during actual transmission, it is referred to as a transmission part in this text. The determination of the RV index of the transmission part can follow the RV determination disclosed in this text. FIG. 19A depicts an example MAS transmission of CBs in two CB groups CBG1 and CB group CBG2 across three time slots 1901 to 1903. The segmentation and transmission of the transmission parts 1904 and 1905 of CB CB2RV2 and CB CB3RV1 are depicted in FIG. 19B respectively. Example 5

[0152] MAS processing can also be used to handle retransmissions. For the retransmission case, consider the situation when the CBG has not been configured. Subsequently, requesting a retransmission of the MAS transmission involves repeating all CBs. The retransmission can be scheduled in the same time slots (in terms of number and available REs) as the original time slots. In this case, the retransmission can be performed in the same way as the original transmission of the individual time slots. Alternatively, the retransmission can be scheduled in a different set of time slots with a different number of available REs. In this embodiment, it can be ensured by the gNB that the processes of TBS determination, coding, and rate matching accurately generate and retransmit the TB transmitted in the initial transmission. In the case where the gNB is interested in such retransmissions (e.g., performing chase combining), it can also be ensured by the gNB that the resource allocation and coding procedures in the scheduled time slots result in the same retransmission of the initial transmission RV version of the CBs.

[0153] In an alternative embodiment, the transmitter can be made to transmit the same TB used in the original transmission. In this alternative embodiment, certain resource allocations for the scheduled time slots can be determined. Knowing that the scheduled resources are for retransmission, the transmitter knows that the TB can be the same TB determined in the original transmission, and thus the transmitter does not determine a new TB according to the TBS determination process. Assuming that the number of layers and modulation order are indicated to be the same as in the original transmission, the transmitter can then infer the effective coding rate from the known number of available resources and the TBS. The transmitter can then continue with the coding and rate matching procedures to perform the retransmission. When determining the resource allocation for the retransmission, it can be ensured by the gNB that this procedure results in the necessary RV transmission of the original codewords.

[0154] When a time slot cancellation occurs in the original MAS transmission, the retransmission of the MAS transmission can be as follows. If it is indicated to cancel the transmission in the time slot of the MAS transmission, various techniques for handling the transmission in the remaining resources can be used. The techniques can involve sending the original TB in one or more other regular and / or MAS transmissions, or sending a set of different and independent TBs in one or more other regular and / or MAS transmissions.

[0155] In the case of transmitting the original TB, the retransmission request can naturally correspond to the TB transmission. The transmission type (regular / MAS) and resources for retransmission can follow the process of transmission repetition described above.

[0156] In the case of transmitting multiple different TBs, the retransmission request should provide an indication of which TB is requested. The indication can be in the form of an additional indication for repetition in the scheduling request, or as a separate resource indicating the retransmission request for each of the transmitted TBs. Since the TB is formed upon receiving the time slot cancellation indication, an explicit configuration for the feedback for each of those TBs can be indicated together with the time slot cancellation indication. Implicit rules can be used to determine the resources for the feedback for each of the transmitted TBs. Example 6

[0157] The resources for MAS transmission can all be configured dynamically. That is, MAS transmission can be scheduled by transmitting DCI in the PDCCH. The DCI can include the resource allocation and configuration for all the time slots in the MAS. For the individual time slot MAS allocation, the DCI information can include a set of configuration parameters, each containing the resource allocation and configuration for the time slot. This can provide maximum flexibility in scheduling at the cost of a high signaling burden. Alternatively, the system can limit the MAS transmission to only include time slots with the same resource allocation; in this case, the DCI can only include the resource allocation and configuration corresponding to one time slot and the number indicating how many time slots are included in the MAS transmission. This can limit the signaling burden at the cost of limited scheduling flexibility.

[0158] To further limit the signaling burden, the configuration for MAS transmission can be RRC-configured. For example, some information (such as the number of time slots of MAS transmission) and / or some resource allocation information (e.g., time, frequency, DMRS configuration, etc.) can be RRC-configured, while other information can be transmitted dynamically via the scheduling DCI. Alternatively, all the information can be RRC-configured, where the DCI only carries an indication of whether this DCI schedules a regular transmission or a MAS transmission.

[0159] For the two types of configured grant (CG) transmissions, the information about MAS transmission can be similar to the RRC configuration described above. In this case, the CG configuration can indicate the time slot of the first time slot in the MAS transmission, and the remaining time slots follow the indicated time slot. Alternatively, the CG configuration can indicate the time positions of different transmission moments within the CG period. FIG. 20 depicts a CG period 2001 in an example CG configuration that can include a set of regular transmission moments and a set of MAS transmission moments according to the subject matter disclosed herein.

[0160] Multiple CG configurations can be configured to allow the transmitter to have various variations of CG configurations with and / or without MAS transmission. For CG type 2 (semi-persistent scheduling), one CG configuration can be used to indicate both the regular transmission time and the MAS transmission time. For example, the CG configuration can provide an indication for a specific time slot. The activated PDCCH can have an additional indication of the CG that will be used for regular transmission. Alternatively, if the PDCCH indicates that the CG will be used for MAS transmission, the indicated time slot can be considered as the first time slot in the MAS transmission time, and the first time slot includes additional time slots after each indicated time slot. Redundancy version (RV) enhancement

[0161] One embodiment disclosed herein provides an enhancement to RV-based transmission to address the following problem. Consider a TBS of size. The TBS can generally be segmented into CBs, where. The size of each CB is. Each CB is coded into a codeword of size, where for LDPC base graph 1,, and for LDPC base graph 2,. The codeword is then provided as an input to the rate matching block, which produces the allocated segments of the codeword with length.

[0162] When is extremely small, as depicted in Figure 21A, RV-based retransmission may not optimally utilize the coded bits. In such cases, adding more RV indices can be beneficial, as depicted in Figure 21B. In contrast, if is larger, then using only some RV indices can be very beneficial, as illustrated in Figures 22A and 22B. For example, consider an L with the length indicated in Figure 21A. Figure 22A shows the corresponding instance RM output for Figure 21A, but L has the length depicted in Figure 22A. Specifically, Figure 22A shows an example scenario where L is substantially larger than half of the length of the entire codeword (e.g., ). RV1 and RV3 will then slightly overlap and will overall cover the codeword, and RV2 and RV4 can be removed. Figure 22B shows the corresponding instance RM output for Figure 22A, where RV2 and RV4 are removed.

[0163] Therefore, the following rule can be adopted to determine the optimal number of RV versions: is the smallest integer such that (12) or. (13) where is the size of the code block, which is equal to.

[0164] The number of RV indices can be freely selected according to Equation (12) or Equation (13). Note that if changes across time slots, one value can be selected to produce a suitable value (e.g., the minimum value among all time slots).

[0165] Another method may be a value selected from a set of possible RV indices. The selection may be explicitly indicated by the gNB. Alternatively, the selection may be the closest value among the set to the value. The set of possible RV indices may be selected as a power of to ensure that the RV boundary does not change with the dynamic selection of. TB / CB limitations

[0166] The TBoMS (Transport Block handling over multiple slots PUSCH, also referred to as MAS herein) for scheduling the TB to be transmitted may generate a corresponding TBS based on the TBS determination rule. In this aspect, the TBS value of the TBoMS may have an upper limit, which is the maximum TBS value that can be obtained in legacy NR (Rel-16). Another upper limit may be based on the corresponding obtained maximum data rate. That is, the obtained maximum data rate may not exceed the corresponding maximum data rate in legacy NR (Rel-16). Yet another upper limit may be based on the corresponding data rate, where for the same configuration parameters, the obtained data rate of the TBoMS should not exceed the corresponding obtained data rate of the legacy PDSCH / PUSCH. The configuration parameters may be the scheduled parameters of the TBoMS. Examples of such parameters include but are not limited to hierarchy, BW, number of layers, MCS, and may be based on the indicated UE capabilities or a combination thereof.

[0167] The parameters indicated in the UE capabilities may not necessarily be equal to the configured parameters of the TBoMS. When using the parameters indicated in the UE capabilities, it should be noted that the UE capabilities may be indicated per frequency range, per component carrier (CC), per frequency band, per band combination (BC), and / or per feature set. For each case providing a set of parameters, the limit values may be calculated. For example, for each feature set containing parameters related to the TBoMS, the limit values may be calculated. Alternatively, one or more limit values may be calculated by taking the representative value of each parameter from the corresponding values of the parameters across different combinations such as feature sets.

[0168] In one embodiment, the TBoMS may be limited to the number of obtained CBs. That is, the number of CBs that can be configured for the TBoMS may be limited. Since the number of CBs is derived from the TBS, limiting the number of CBs can be implicitly achieved by limiting the TBS as described above.

[0169] In another embodiment, the number of CBs can be explicitly limited to a certain maximum value. This maximum limit can be implemented by limiting the number of CBs to the minimum value of and the value obtained by operating according to the legacy specification. The value of can be specified as an absolute number applicable to any UE with TBoMS feature capabilities. Alternatively, the value of can depend on the UE capabilities, i.e., the UE can indicate the maximum number of CBs that can be supported per TBoMS within the TBoMS feature capabilities. The limitation of the number of CBs can be described per CC, per band, per BC, per feature set, or per Feature Set per Component Carrier (FSPC). The limitation of the number of CBs can also be part of the TBoMS feature and can thus follow the UE transmission granularity associated with the TBoMS capabilities.

[0170] In one exemplary embodiment, the transport block processing chain for a transmitter can include a code block determination circuit and a rate matching circuit. The code block determination circuit can be configured to determine the size of code blocks mapped across multiple time slots of a radio entity common channel according to a transport block over multiple time slots (TBoMS) configuration, and the rate matching circuit can be configured to rate match the bits of the code blocks with the number of bits available in the transport block over multiple time slots across the radio entity common channel. In another exemplary embodiment, the multiple time slots of the radio entity common channel according to the TBoMS configuration can be based on the legacy maximum transport block size (TBS). In yet another exemplary embodiment, the multiple time slots of the radio entity common channel according to the TBoMS configuration can be based on a predetermined number of code blocks, and the predetermined number of code blocks can be based on the legacy maximum number of code blocks. In still another exemplary embodiment, the multiple time slots of the radio entity common channel according to the TboMS configuration can be based on the maximum transport block size (TBS) set forth in a standard document. Example 1 of RM and interleaver operations

[0171] The first exemplary embodiment of RM determination and interleaver operation includes consecutive RM determination and a consecutive interleaver. The RM output of the CBs can be determined for all time slots, and the interleaver operation can be performed across all time slots. In this case, the interleaver size will be determined based on the entire CB RM output of all time slots. FIGS. 23A and 23B depict the operation of the first exemplary embodiment of RM and interleaver operations for consecutive RM determination and a consecutive interleaver according to the subject matter disclosed herein. In FIGS. 23A and 23B, it is assumed that a multi-time slot entity common channel transmission has two time slots and three CBs, and the modulation order is 4.

[0172] In FIG. 23A, it is known that the RM output of CB2 crosses the time slot boundary between time slot 1 and time slot 2. The RM output of CB2 can be assumed to be a continuous RM output. In this embodiment, interleaver operation is applied across the entire RM output. Since the modulation order is 4, the interleaver operation of CB2 causes the coded bits to be transmitted in two interleaved time slots, as depicted in FIG. 23B. Example 1a of RM and interleaver operation

[0173] A first variation of the embodiment depicted in FIGS. 23A and 23B can be when segmenting the RM output with a new RV, and the new RV is used to determine the RM output of each time slot. This is illustrated in FIGS. 24A and 24B, which respectively depict the RM and interleaver outputs for a multi-time slot physical common channel with two time slots, three CBs, a modulation order of 4, and a segmented CB RM output with a new RV according to the subject matter disclosed herein. The RM output of CB2 can be assumed to be a segmented RM output, where time slot 2 has a new RV. The first variation applies interleaver operation across the entire RM output. Since the modulation order is 4, the interleaver operation of CB2 causes the coded bits to be transmitted in two interleaved time slots, as depicted in FIG. 24B. Example 1b of RM and interleaver operation

[0174] A second variation of the embodiment depicted in FIGS. 23A and 23B can be similar to the first variation of FIGS. 25A and 25B, but within a clearly limited number of time slots during multi-time slot physical common channel transmission. The feature of this second variation (limiting continuous RM, limiting continuous interleaver) can be the limitation on the number of time slots. More specifically, FIGS. 25A and 25B respectively depict the RM and interleaver outputs, where for a multi-time slot physical common channel with four time slots, three CBs, and a modulation order of 4. In this variation, the RM operation takes the entire codeword of the CB as input and provides the coded bits rate-matched over the physical common channel resources in a separate set of time slots. The RM operation provides a continuous set of coded bits to the interleaver as input, and the interleaver also operates on the RM output of the set of time slots to provide the mapping of the coded bits to the symbols of each time slot. This variation allows the RM outputs of different sets of time slots to be either continuous RM outputs or RM outputs with a new RV. A restriction can also be provided to the gNB so as not to schedule multi-time slot physical common channel transmission where the CB experiences boundary crossing between sets of time slots. Example 2 of RM and interleaver operation

[0175] A second example of RM determination and interleaver operation for a multi-slot physical shared channel with two time slots, three CBs, modulation order of 4, and continuous CB RM output is depicted in FIGS. 26A and 26B. The interleaver operation is performed independently across each time slot. In this case, the interleaver size will be determined based on the CB RM output of a particular time slot. This may work when the RM output is determined for all time slots or when the RM output is determined independently for each time slot. When the RM output is determined for all time slots, the rate matching procedure described herein can be extended by considering across all time slots as the RM size. However, in that case, the interleaving procedure disclosed herein cannot be directly extended because the time slot boundaries should still be identified for interleaver operation. Assume that the number of time slots mapped by a certain CB is. For, the number of coding bits available in the th time slot is such that. Subsequently, the interleaving procedure disclosed herein can be applied separately to each by replacing with and considering the input sequence in the existing procedure.

[0176] In FIG. 26A, the RM output of CB2 is a continuous RM output. This variation only applies the interleaver operation in FIG. 26B to the RM output across each time slot.

[0177] When the RM output is a segmented output with a new RV index, there is a similar behavior, as depicted in FIGS. 27A and 27B, which are the RM and interleaver outputs for a multi-slot physical shared channel with two time slots, three CBs, modulation order of 4, and segmented CB RM output with a new RV according to the subject matter disclosed herein.

[0178] The systematic bits available in the codeword corresponding to the CB are the bits important for the decoding operation. Therefore, it may be beneficial for the interleaver to map the systematic bits onto reliable bits according to the modulation scheme used (e.g., 16QAM). A possible problem with this example embodiment of the RM and interleaver is that, compared to the example embodiments of FIGS. 23A and 23B, ultimately fewer systematic bits may be mapped onto reliable bits. This possible problem can be avoided by using the following first variation modified from the example embodiments of FIGS. 23A and 23B. Embodiment 2a of RM and interleaver operation

[0179] Example 2a of RM and interleaver operations is similar to the example embodiments of FIGS. 27A and 27B. In the example embodiments of FIGS. 27A and 27B, the interleaver operations can be performed independently across each time slot, and the interleaver size can be determined based on the CB RM output of a particular time slot. The RM output can allocate the information bits among the time slots such that the information bits are mapped to reliable bit positions via the interleavers of different time slots. Examples of the operations of Example 2a of RM and interleaver operations are illustrated in FIGS. 28A and 28B respectively, where the multi-time slot physical common channel transmission can be assumed to have two time slots and three CBs, and the modulation order is 4.

[0180] For a particular CB, the RM operations of the variations of FIGS. 28A and 28B can process the systematic bits and the parity bits separately when determining the inputs to the interleavers for different time slots. Assume that the number of time slots in the multi-time slot PUSCH is. For, the number of coding bits available in the th time slot is. Assume that a small number of codewords corresponding to the CB are numbered from to, where is the length of the codeword. Assume that from to bits correspond to the systematic bits of the codeword. Assume that indicates the bit corresponding to the start of the RM output (e.g., indicated by the RV index of the multi-time slot physical common channel transmission). In addition to the output bits from the RM operations, assume that a subset indicating the size of the systematic bits will be part of the output of the RM operations for all time slots of the multi-time slot physical common channel transmission. The determination can vary depending on how the RM operation selects the total amount of output bits. For example, the RM output of the time slots can be determined by continuously selecting bits starting from the th bit of the codeword and a total of bits while performing a modulo- operation.

[0181] The RM operation can be described as follows: First, the determination part is. Alternatively,. These parts determine the ratio of the systematic bits to be allocated in each time slot. Next, the systematic bits are continuously allocated to the time slots according to the ratio of the systematic bits. The number of systematic bits allocated to the th time slot is. Finally, the remaining bits from the RM output are allocated to the time slots according to the ratio of the systematic bits. The number of bits allocated to the th time slot can be subject to a suitable rounding operation to determine the integer number of bits.

[0182] Another way to describe the RM operation also interleaves and maps the bits in the time slots as follows. For all codeword bits from to, for all time slots, continuous allocation is made for the time slots. In other words, the bits from 0 to are allocated in the first time slot, the bits from to are allocated in the second time slot. The bits from to are allocated in the th time slot. After bits have been allocated, the previous procedure is repeated starting from the bits from to. This continues for the bits from to.

[0183] This procedure divides the RM output into segments, where the time slots can allocate portions of the segments based on their respective RM sizes. This procedure can be generalized to any number of segments as follows.

[0184] First, for all codewords from to, for all time slots, allocate continuously for the time slots. In other words, allocate bits from 0 to in the first time slot, bits from to in the second time slot. Allocate bits from to in the time slot.

[0185] Next, after allocating bits, repeat the above procedure starting from bits from to. This continues for bits from to.

[0186] The value can be optionally selected to allow an equal distribution of information bits among the time slots. The number can be selected based on different criteria (e.g.,,, and others). Figure 29 illustrates an example of the RM output method, where and. can be selected at this time. RV selection

[0187] The RM operation of the example embodiments of FIGS. 26A and 26B is slot-based, and the RM output of each CB is based on the selected RV index. The RM operation can be enhanced by a set of RV indices that is the set of RV indices for Rel-16 PUSCH, or it can be a different set of RV indices that may have been increased. In this enhancement, the RM output of the CB in the time slot can be based on the index. The enhancement includes techniques for selecting such indices. There are several options below.

[0188] The first option includes that the RV indices of the CBs in each time slot follow the selection of RV indices according to the Rel-16 procedure for time slot aggregation. An alternative option stipulates that the RV indices of the CBs can be incremented for each time slot in the multi-time slot entity common channel transmission. Another alternative option includes that the RV indices of the CBs in each time slot can be the maximum RV index, where its start position is less than the termination position of the RM output from the previous time slot. That is, for a given set of time slots in a multi-time slot entity common channel transmission, is the RM size of the number of time slots of the CB, and is the start position of the RM output of the first time slot (this can be the start position corresponding to a specific RV index specified for the multi-time slot entity common channel transmission). Subsequently, for the time slot, calculate the value, and then use the RV index whose start position is the largest one less than or equal to. This alternative option can include selecting the RV index with the start position closest to.

[0189] Yet another option includes making the RM size corresponding to the difference between the start positions of two consecutive RV indices. Subsequently, (or or ) can be calculated, and the RV indices of each consecutive time slot are incremented.

[0190] Another option could be that the transmitter is configurable with multiple possible RV selection sequences, where the RV indices of different CB segments follow the pattern of one of these sequences. The selection of which sequence to use could be performed, for example, as follows. The DCI scheduling multi-slot physical shared channel transmissions could include a field for selecting an index for the RV sequence to be used in the multi-slot physical shared channel transmissions. This field could be the same RV index field in DCI format 0_1. Alternatively, the field could be a different field or the same field but with an increased number of bits to accommodate a larger number of RV sequences. The transmitter could be configured with a larger set of RV sequences. Subsequently, only a subset of such sequences to be used by the transmitter could be configured by the gNB. The selection of such a subset could be using RRC configuration or via a MAC CE. Among the selected subset, the specific sequence to be used is indicated to the transmitter via a field indicated in the scheduling DCI for the multi-slot physical shared channel transmissions. The selection of this field could be the same RV index field in DCI format 0_1. Alternatively, the field could be a different field or could be the same field but with an increased number of bits to accommodate a larger number of RV sequences.

[0191] When a CB spans a slot boundary, the RV index of the newly formed segment could follow the sequence indicated by the DCI described previously. An example of this operation is explained next, where it is assumed that the transmitter is configured with a set of RV sequences as indicated in the following table. Assume that the UE is indicated by RV index 0 via the scheduling DCI. In the case where one coded CB spans three slots, the RM outputs for the three slots will use RV indices 0, 1, and 2.

[0192] The table that the UE follows to determine the RV sequence for CB segments across slots could be the Rel-16 table for determining the RV sequence for slot aggregation across slots. Alternatively, a new table could be defined for determining the RV sequence for CB segments across slots, similar to (but not limited to) Table 2 below. Table 2 rv indicated by DCI scheduling PUSCH id rv to be applied to the nth slot of the portion of the slot set that contains the coded CB in the multi-slot PUSCH id n mod 4 = 0 n mod 4 = 1 n mod 4 = 2 n mod 4 = 3 0 0 1 2 3 1 1 2 3 0 2 2 3 0 1 3 3 0 1 2 4 0 3 1 2 5 3 0 2 1

[0193] As an alternative example, the transmitter may select RV indices for the time slots across CB to ensure that the maximum number of information bits are mapped to higher-order symbols with high reliability. For example, in the case of using 16QAM modulation, depending on their respective positions within the 16QAM symbol, some bits have higher decoding reliability than the rest. If information bits are transmitted in the coded bit positions of a time slot, approximately half of the information bits will be mapped to unreliable bit positions. In this case, the RV index for the next time slot can be selected such that half of the bits that are unreliably transmitted will be retransmitted in the new time slot rather than selecting an RV index that may cause the transmission of the coded bits not to be transmitted.

[0194] Generally speaking, for an M-QAM modulation scheme, there may be different levels of reliability for the information bits. Assume the number of levels is. Each level represents a different level of reliability in correct decoding. Ideally, the information bits will be mapped to the most reliable bit positions. However, if such mapping is not possible within a time slot, then RV index selection can be performed to ensure that the information bits that are not mapped to the most reliable bits will be mapped to the most reliable one in the upcoming time slot.

[0195] As an alternative to this condition, each information bit will have a specific reliability "guarantee" when transmitted. The concept of "guarantee" as used herein may depend on the number of repeated transmissions of the information bit and the level of reliability of each repetition. For example, in 16-QAM with two levels of reliability, if it is transmitted once in the most reliable position, or twice in two unreliable positions, then the information bit can be considered to have a satisfactory transmission. RV index selection can then be performed to ensure the maximum number of bits transmitted with the guaranteed reliability.

[0196] As a simplified alternative example, for the reliability of each level, where levels 1 to correspond to the most reliable to the least reliable, for a given level, if it maps to any bit of reliability 1 to reliability, the information bit can be considered reliable. RV index selection can be performed to ensure that the maximum number of information bits map to reliable bits. Example 3 of RM and interleaver operations

[0197] For Example 3 of RM and interleaver operations, the interleaver operation is similar to the continuous interleaver operation described previously. However, the size of the interleaver can be finite. That is, the interleaver operation can be a continuous interleaver operation, but with a maximum interleaver size. The interleaver size limit can be implemented by resetting the interleaver operation after each setting of the interleaver input bits equal to the maximum interleaver size. In this case, multiple interleaver operations can be performed on the entire RM output (e.g., when the RM output size is greater than the maximum interleaver size).

[0198] The interleaver size limit can alternatively be implemented by restricting the RM output size to be equal to the maximum interleaver size. In this case, the number of bits of the RM output can be limited to the maximum interleaver size.

[0199] Yet another way to enforce the interleaver size limit can be by performing the resource allocation of TboMS such that both the RM output and the interleaver input are within the maximum interleaver size limit.

[0200] The interleaver size limit can be in the form of a value that sets the maximum interleaver size. The value can be specified in different ways. For example, the value can be specified as an absolute value regardless of other configurations of TboMS. In this case, this specified absolute value can be explicitly mentioned in the Rel-16 specification. Alternatively, the absolute value can be in the form of a numerical value. For example, the numerical value can be in the form of bits, where the value is an example. Another alternative can be that the absolute value can be specified as a relationship with one or more other parameters in the Rel-16 specification, where these parameters may not be particularly related to any configuration of TboMS. For example, it can be in the form of a portion of other parameters in the specification, such as the maximum TBS value obtained in Rel-16, or any other function of other parameters in the specification.

[0201] In yet another way, the value is specified to be related to a specific configuration of the scheduled TboMS or a specific configuration of UE capabilities related to the use of TboMS indicated by the UE. For example, the value may depend on any one or more of the parameters, such as the scheduled MCS, the scheduled resources in time and / or frequency, the scheduled number of layers, the scheduled number of time slots, the resource allocation mechanism, the scheduling type of TboMS (dynamic, configured grant, other), the transport block size, the number of TB CBs, the configured CBG, and / or UE capabilities.

[0202] For example, the value may depend on the scheduled BW, MCS, the number of layers, and UE capabilities. The value may also be specified to be related to the corresponding interleaver size obtained in legacy NR (e.g., Rel-15 / 16). This corresponding value may be the value obtained when using the same / similar scheduled parameters for scheduling transmissions in legacy NR (e.g., Rel-15 / 16).

[0203] The value may be determined based on the scheduled parameters of TboMS, such as the layer, modulation order, coding rate, MCS, bandwidth, the number of layers, and others. For example, if TboMS is scheduled with a 50 MHz bandwidth, the value may be determined based on the scheduled bandwidth. Alternatively, the value may be determined based on the indicated UE capabilities of the supported parameters for TboMS, such as the layer, modulation order, coding rate, MCS, bandwidth, the number of layers, and others. For example, if TboMS is scheduled with a 50 MHz bandwidth and the UE indicates the ability to support up to 100 MHz, the value may be calculated based on the value of 100 MHz.

[0204] In the case where the determination depends on UE capabilities, the value used in the determination may be for each frequency band in each frequency band combination indicated by the UE capabilities.

[0205] It can be calculated as the value of the TBS that is the legacy (Rel-16) counterpart corresponding to the scheduled TboMS. The legacy counterpart of the TBS may mean the TBS value calculated according to the legacy specification procedures and using the scheduled / configured parameters and UE capabilities. For example, it may be the TBS value calculated according to the legacy procedures using the parameters of the scheduled TboMS, such as but not limited to the layer, modulation order, coding rate, MCS, bandwidth, and the number of layers; or the values of these parameters may be indicated by their respective UE capabilities.

[0206] It can be calculated using the legacy specification procedure as the expected input interleaver size. For example, it can be equivalent to the number of available coding bits in the legacy PDSCH / PUSCH scheduling using the same scheduled / configured parameters as for TboMS. The number of available coding bits can be given by, where all parameters are given by the Rel-16 TBS determination equation. Alternative operations of the interleaver in the third embodiment

[0207] As a first alternative operation, it may not be expected that the UE processes an interleaver input size greater than the Rel-15 / 16 limit, which corresponds to the parameters for each frequency band in the band combination that the UE has declared support for, and this limit corresponds to the amount of available coding bits or coding bits per CB in section 5.4.2.1 of 38.212 V16.4.0.

[0208] As a second operation alternative example, it may be unexpected for the UE to process the interleaver input size, which is given in section 5.4.2.1 of 38.212, and assuming the following are the number of REs (NRE), modulation order (Qm), number of layers (ʋ), according to 6.1.4.2 in 38.214 for UL-SCH and 5.1.3.2 in TS 38.214 for DL-SCH / PCH, it can be determined that, as in 5.4.2.1 of 38.212: The maximum number of layers for a TB of UL-SCH is given by, where: If the higher layer parameter maxMIMO-Layers of PUSCH-ServingCellConfig of the serving cell is configured, it is given by that parameter, Otherwise, if the higher layer parameter maxRank of pusch-Config of the serving cell is configured, it is given by the maximum value of maxRank across all BWPs of the serving cell, Otherwise, it is given by the maximum number of layers of PUSCH supported by the UE for the serving cell. The maximum number of layers for a TB of DL-SCH / PCH is given by the minimum value of and 4, where If the higher layer parameter maxMIMO-Layers of PDSCH-ServingCellConfig of the serving cell is configured, it is given by that parameter, Otherwise, it is given by the maximum number of layers of PDSCH supported by the UE for the serving cell. If the higher layer parameter mcs-Table given by pdsch-Config of at least one DL BWP of the serving cell is set to "qam256", it is assumed that the maximum modulation order of DL-SCH is; otherwise, it is assumed that the maximum modulation order of DL-SCH is. If the higher layer parameter mcs-Table or mcs-TableTransformPrecoder given by pusch-Config or configuredGrantConfig of at least one UL BWP of the serving cell is set to "qam256", it is assumed that the maximum modulation order of UL-SCH is; otherwise, it is assumed that the maximum modulation order of UL-SCH is. is given by Table 5.4.2.1-1 (Table 3), where if no other downlink bandwidth part is configured for the UE, the value of DL-SCH is determined according to the initial downlink bandwidth part.. Table 3 (Table 5.4.2.1-1): Value Are the maximum number of PRBs of all configured DL BWPs and UL BWPs of the carrier across DL-SCH and UL-SCH respectively Less than 33 32 33 to 66 66 67 to 107 107 108 to 135 135 136 to 162 162 163 to 217 217 Greater than 217 273

[0209] As a third operation alternative example, it may be unexpected for the UE to process the interleaver input size, which is given in part 5.4.2.1 of 38.212, and assuming the following are the number of REs (NRE), modulation order (Qm), number of layers (), it can be determined according to 6.1.4.2 in 38.214 for UL-SCH and 5.1.3.2 in TS 38.214 for DL-SCH / PCH. The maximum number of layers for a TB for UL-SCH is given by the maximum number of layers of the PUSCH supported by the UE for the serving cell; the maximum number of layers for a TB for DL-SCH / PCH is given by the maximum number of layers of the PDSCH supported by the UE for the serving cell; if the UE supports 256QAM for the serving cell, then assume the maximum modulation order for DL-SCH is; otherwise assume the maximum modulation order for DL-SCH is; if the UE supports 256QAM for the serving cell, then assume the maximum modulation order for UL-SCH is; otherwise assume the maximum modulation order for UL-SCH is; given by Table 5.4.2.1-1 (Table 4); and. Table 4 (Table 5.4.3.1-1): Values The maximum number of PRBs corresponding to the maximum channel bandwidth supported by the UE for the serving cell, corresponding to the 'largest or smallest' subcarrier spacing configured for the serving cell or the subcarrier spacing of the active BWP of the serving cell Less than 33 32 33 to 66 66 67 to 107 107 108 to 135 135 136 to 162 162 163 to 217 217 Greater than 217 273

[0210] As a fourth operation alternative for the configured TBoMS, if the parameters associated with the TBoMS satisfy the UE capabilities indicated in the feature set, the configured TBoMS is said to satisfy the feature set. It is not expected that the UE processes the interleaver input size, which is given in part 5.4.2.1 of 38.212, and assuming the following are the number of REs (NRE), modulation order (Qm), number of layers (), it can be determined according to 6.1.4.2 in 38.214 for UL-SCH and 5.1.3.2 in TS 38.214 for DL-SCH / PCH. The maximum number of layers for a TB of UL-SCH is given by the maximum number of layers of PUSCH supported by the UE within the set of feature sets that are satisfied; the maximum number of layers for a TB of DL-SCH / PCH is given by the maximum number of layers of PDSCH supported by the UE within the set of feature sets that are satisfied; if the UE supports 256QAM within the set of feature sets that are satisfied, the maximum modulation order of DL-SCH is assumed to be; otherwise the maximum modulation order of DL-SCH is assumed to be; if the UE supports 256QAM within the set of feature sets that are satisfied, the maximum modulation order of UL-SCH is assumed to be; otherwise the maximum modulation order of UL-SCH is assumed to be; is given by Table 5.4.2.1-1 (Table 5); and. Table 5 (Table 5.4.2.1-1): values The maximum number of PRBs corresponding to the maximum channel bandwidth supported by the UE for the serving cell, corresponding to the 'maximum or minimum' subcarrier spacing configured for the serving cell or the subcarrier spacing of the active BWP of the serving cell Less than 33 32 33 to 66 66 67 to 107 107 108 to 135 135 136 to 162 162 163 to 217 217 Greater than 217 273

[0211] In other words, this operation alternative corresponds to calculating the interleaver size limit in a way that maximizes the limit value using the parameters selected from the satisfied feature set.

[0212] As a fifth operation alternative for the configured TBoMS, if the parameters associated with the TBoMS satisfy the UE capabilities indicated in the feature set, the configured TBoMS is said to satisfy the feature set. For each satisfied feature set, it is not expected that the UE processes the interleaver input size, which is given in part 5.4.2.1 of 38.212, and assuming the following are the number of REs (NRE), modulation order (Qm), number of layers (), it can be determined according to 6.1.4.2 in 38.214 for UL-SCH and 5.1.3.2 in TS 38.214 for DL-SCH / PCH. The maximum number of layers for a TB for UL-SCH is given by the maximum number of layers of the PUSCH supported by the UE in the satisfied feature set; the maximum number of layers for a TB for DL-SCH / PCH is given by the maximum number of layers of the PDSCH supported by the UE in the satisfied feature set; if the UE supports 256QAM in the satisfied feature set, it is assumed that the maximum modulation order for DL-SCH is; otherwise, it is assumed that the maximum modulation order for DL-SCH is; if the UE supports 256QAM in the satisfied feature set, it is assumed that the maximum modulation order for UL-SCH is; otherwise, it is assumed that the maximum modulation order for UL-SCH is; given by Table 5.4.2.1-1 (Table 6); and. Table 6 (Table 5.4.2.1-1): values The maximum number of PRBs corresponding to the maximum channel bandwidth supported by the UE for the serving cell, corresponding to the configured'maximum or minimum' subcarrier spacing for the serving cell or the subcarrier spacing of the active BWP of the serving cell Less than 33 32 33 to 66 66 67 to 107 107 108 to 135 135 136 to 162 162 163 to 217 217 Greater than 217 273

[0213] In other words, the fifth operation alternative corresponds to selecting the minimum interleaver size limit across all satisfied feature sets. Example 4 of RM and interleaver operation

[0214] In the fourth embodiment, the interleaver operation can be a continuous interleaver operation, but for a certain unit across resources. The unit of the resource can be a time slot, in which case the fourth embodiment is similar to Embodiment 2 of RM and interleaver operations. The unit of the resource can be the entire set of time slots of the TBoMB, in which case the fourth embodiment is similar to Embodiment 1 of RM and interleaver operations. The unit of the resource can be different from a time slot or the entire set of time slots of the TBoMS. For example, the unit of the resource can be a set of time-continuous or non-continuous resources, which may or may not span different time slots.

[0215] In some cases, the RM output can include multiple such units of resources. In some cases, the definition of the unit can depend on its relative position with respect to the RM output. For example, the first unit in the RM output can correspond to certain resources with certain configurations, while the second unit or subsequent units in the RM output can correspond to different configurations of resources. In this case, the interleaver operation can be continuous in the context of one unit, while the independent interleaver operation can occur across different units. Mapping from virtual resources to physical resources

[0216] The subject matter disclosed herein includes a method of performing mapping from virtual resources to physical resources in the context of multi-time slot physical shared channel transmission processing. That is, the transmitter can be indicated as a set of physical resources for transmission for multi-time slot physical shared channel transmission. It can be assumed that the set of resources includes time slots. Each of the time slots can be associated with a global identifier of the time slot position in the system, such as an identifier based on the System Frame Number (SFN). For the i-th time slot, the set can include an index assigned for the transmitter for OFDM symbols for use in multi-time slot physical shared channel transmission, where each symbol corresponds to a set of REs for each allocated SC. The set of time slots can be continuous or non-continuous. It can be assumed that the time slots are sorted in time according to their time indices, that is, if i < j, then the i-th time slot appears before the j-th time slot in time. The set of symbols can have UL symbols, DL symbols, or F symbols. For the indication of the set, no assumptions are made about the rules related to the transmission directions authorized for those symbols. For example, some of the symbols in the set can have DL / UL symbols. However, the transmitter should comply with the transmission rules indicated by the network or gNB that allocates the symbols.

[0217] It is also possible to indicate to the transmitter a set of virtual resources in the process of multi-slot physical shared channel transmission. It can be assumed that this set of resources contains N time slots. For the i-th time slot, the set contains the indices of the OFDM symbols allocated for the transmitter for use in multi-slot physical shared channel transmission. The number of virtual sets may be the same as or different from the number of physical time slots. The set of virtual symbols may be the same as or different from the set of physical symbols. The indication of the set may be performed dynamically or semi-statically.

[0218] The indication of virtual resources may be separate from the indication of physical resources. Alternatively, the indication of virtual resources may be implicitly inferred from the set of physical resources. For example, the set of virtual resources may be determined by considering the set of physical resources and omitting the resources corresponding to the physical resources that are not allowed to be transmitted in the expected direction (e.g., the DL and / or F transmission directions specified by the TDD configuration in the case of multi-slot PUSCH).

[0219] Based on the allocation of physical resources and virtual resources, several methods follow the mapping from virtual resources to physical resources.

[0220] In the case where the virtual and physical sets are the same, i.e., M = N and all time slots in the set of physical time slots are consecutive, the resources corresponding to the symbols in M may be mapped to the resources corresponding to the symbols in N.

[0221] When the virtual and physical sets are the same, i.e., M = N and not all time slots in the set of physical time slots are consecutive, the set of physical time slots contains several subsets, where each subset contains consecutive time slots. In this case, the resources corresponding to the symbols in M may be mapped to the resources corresponding to the symbols in N. For example, if the set of four time slots contains two subsets, each subset containing two consecutive time slots. For example, this may be the case of multi-slot PUSCH and a TDD configuration of the form DDSUUDDSUU for all U time slots allocated for multi-slot PUSCH. This may also occur due to the dynamic indication of the time slot format. For example, consider the TDD configuration FFFFFF. The following pattern of the configuration UUUUDD may be indicated to the UE via the SFI indication. After performing the necessary PUSCH processing for the multi-slot PUSCH, the UE receives another SFI indication that changes the pattern to UUDDUU, in which case the UE may perform multi-slot PUSCH transmission on the newly determined set of physical time slots. As another example, none of the four time slots are consecutive. For example, this may be the case of multi-slot PUSCH and a TDD configuration of the form DDSUDDSUDDSUDDSU for all U time slots allocated for multi-slot PUSCH.

[0222] In the case where the number of physical slots is less than the virtual slots that can correspond to the following usage cases in Rel-16 (i.e.,), the UE may be allocated a set of physical slots for the transmission of multi-slot PUSCH. The UE may then determine that all physical slots are feasible for transmission, and thus the corresponding virtual slots are the same as the physical slots. Subsequently, some physical slots may become inapplicable for transmission due to, for example, dynamic changes in the TDD configuration. In this case, the UE has different mapping options. For the first option, the UE may continuously map the virtual slots to the physical slots in its respective order. Therefore, the additional virtual slots without physical slots to be mapped are ultimately the last ones in the set of virtual slots. For the second option, the UE may continuously map the virtual slots to the physical slots in its respective order. If the determination of the virtual slots is based on the physical slots, the UE may also skip the virtual slots with the original physical slots that are no longer available.

[0223] In the case where the number of physical slots is greater than the virtual slots (i.e.,), for example, if the slots for multi-slot PUSCH processing are indicated to the UE when the UE determines the virtual slots from the physical slots, and it is determined that some slots are not suitable for UL transmission, it may occur that the UE has different mapping options.

[0224] For the first option, the UE may continuously map the virtual slots to the physical slots in its respective order. If the physical slot is not suitable for transmission, skip the physical slot without skipping the corresponding virtual slot. For example, the set of virtual slots may be numbered from 1 to 4, and the physical slots are numbered from 1 to 5, where the third slot is not suitable. Then, the mapping from virtual to physical is: 1 to 1, 2 to 2, 3 to 4, 4 to 5.

[0225] For the second option, the UE may continuously map the virtual slots to the physical slots in its respective order. If the physical slot is not suitable for transmission, skip the physical slot and also skip the corresponding virtual slot. For example, assume the set of virtual slots may be numbered from 1 to 4, and the physical slots are numbered from 1 to 5, where the third slot is not suitable. Then, the mapping from virtual to physical is: 1 to 1, 2 to 2, 4 to 4, none to 5.

[0226] As is clear from the examples, it is possible for some physical slots to end up being mapped from virtual slots with no content. In this case, the UE may avoid sending any content in those specific slots. Alternatively, the UE may re-transmit other virtual slots in those physical slots. For example, in the above example where the mapping results in none to 5, the mapping of none to 5 can be replaced by 1 to 5 or 4 to 5. Another possibility is that some virtual slots may not be mapped to any physical slots. UCI Multiplexing via Multi-Slot PUSCH

[0227] A technique to prevent UCI multiplexing by multi-slot PUSCH is that it may not be expected that the UE has a UCI multiplexing situation by multi-slot PUSCH. Alternatively, the UE can be instructed to process UCI multiplexing by multi-slot PUSCH in a way that does not actually result in the occurrence of UCI multiplexing. For example, if such a multiplexing situation occurs, the UE can cancel the UCI transmission or the multi-slot PUSCH transmission. In the case of canceling the multi-slot PUSCH transmission, the affected time slot can then be canceled, or the affected time slot and all subsequent time slots can be canceled. In the case of such a cancellation, it should be expected that the UE cancels the transmission in the OFDM symbols within an appropriate cancellation timeline.

[0228] Figure 30 depicts an example situation where a multi-slot PUSCH is scheduled and UCI has been scheduled to be multiplexed in one of the time slots forming the multi-slot PUSCH. In Figure 30, for time slots 3002 to 3004, a multi-slot PUSCH schedule appears at 3001. After the multi-slot PUSCH schedule, for time slots 3006 and 3003, a UCI PDSCH is scheduled at 3005.

[0229] The situation depicted in Figure 30 is considered from a timeline perspective in Figure 31 and then from a performance perspective. Different methods for handling UCI multiplexing are as follows. That is, when the UE determines that a UCI multiplexing situation will occur by one or more time slots in the multi-slot PUSCH, the following options can be executed.

[0230] As a first option, the UE can adapt the interleaver output for all time slots in the multi-slot PUSCH. For this option, the Rel-16 timeline associated with UCI multiplexing on the multi-slot PUSCH (indicated as timeline 1 in Figure 31) should be adapted to provide sufficient time to adapt the earlier time slots in the multi-slot PUSCH that may precede the time slots where UCI multiplexing occurs. It may be sufficient to only adapt timeline 1 in Figure 31 in order to actually determine the interleaver behavior with UCI multiplexing. Timeline 2 in Figure 31 allows the UE to determine the exact value of the UCI bits to be multiplexed, which may not require an adaptation similar to Rel-16 timeline 1 in Figure 31. Alternatively, both timeline 1 and timeline 2 in Figure 31 can be adapted similar to the adaptation provided for timeline 1. This method works together with all the前述 embodiments of RM and interleaver operations.

[0231] From the perspective of self-efficacy, this allows the UE to inherently and naturally multiplex in Rel-16, i.e., the UE can recalculate the RM output and the interleaver output for the updated amount of resources available after UCI multiplexing. From the perspective of UE implementation, this also allows for easy handling of UCI multiplexing. However, from the scheduling perspective, this can be fully constrained.

[0232] The UE can adapt the interleaver output of the affected time slot and subsequent possible time slots by puncturing the interleaver output at the position where the RE is used to transmit the symbol carrying the UCI bit. This solution can cause bad decoding of the multi-time slot PUSCH. That is, puncturing the RE for the UCI bit can remove the important coding bits of the CB carried in the punctured time slot, which can severely reduce the probability of successfully decoding the affected CB. This adverse effect related to unsuccessful decoding can exist in all cases of puncturing. FIGS. 32 and 33 depict the punctured time slots of Example 1 and Example 2 for RM and interleaver operations, respectively.

[0233] For Example 1 and Example 1a, the interleaving of the entire time slot of the affected CB has occurred and cannot be redone. In other words, for a CB mapped on M time slots, the interleaved input sequence can be given as, where and are the number of coding bits available in the th time slot. Then, the interleaved output sequence will be, where the bits from to correspond to the bits mapped in time slot i. If UCI multiplexing occurs in time slot i, and if the resulting rate matching size becomes, the UE should select bits out of the bits from to for transmission. One way to do this can be to transmit from to. This corresponds to the selection / puncturing of consecutive bits from the interleaver output. An alternative can be used for the selection / puncturing of consecutive bits from the interleaver input, which can be implemented as follows. First, select the bit positions from the original interleaver input sequence corresponding to the original interleaver output from to. Then, some of these values can be selected from these values, and the corresponding values in the original interleaver output can be transmitted. A possible selection of bits can be by incrementing the order of the bit positions in. In this case, the interleaver operation may not be performed again due to the change in the rate matching size, as previously described. A general selection of bits can be by selecting bits, where the function is the selection function that determines which bit to select in the th position. The function corresponds to one possible selection previously described.

[0234] If UCI multiplexing occurs in a time slot and if the resulting rate matching size becomes, then another alternative could be to perform interleaving again. One way to perform interleaving again could be to select bit positions from the original interleaver input sequence corresponding to the original interleaver output sequence from to as the new interleaver input sequence. Then, the interleaver operation can be applied to this sequence to obtain a new interleaver output sequence. This corresponds to consecutive bit selection / hitting from the interleaver output. Another alternative could be to select bit positions from the original interleaver input sequence corresponding to the original interleaver output from to, and select bit positions from the bit positions. This corresponds to consecutive bit selection / hitting from the interleaver input. Then, a new length interleaver sequence is constructed, and the interleaver operation can be applied to this sequence to obtain a new interleaver output sequence. In this case, re - executing the interleaver operation can be restricted to the time slot. The general selection of bit positions can be performed using a function similar to the functions described previously.

[0235] If UCI multiplexing occurs in a time slot and if the resulting rate matching size becomes, then another alternative could be to perform interleaving and all subsequent time slots by using a length sequence as the new interleaver input. This interleaver input sequence can be formed by selecting certain bit positions from consecutive original interleaver input sequences in the previously described interleaver input or output. One possible way could be to select bit positions from the original interleaver input sequence corresponding to the original interleaver output from to. One possible such way could be to use from to. This corresponds to consecutive bit selection / hitting from the interleaver output. Alternatively, consecutive bit selection / hitting from the interleaver input as described previously can be used, or a generalized selection function can be used.

[0236] Another consideration could involve how to calculate for each CB in the case where a time slot involves multiple CBs. For example, consider two CBs mapped in a time slot with original RM sizes of and respectively, where the sizes correspond to the total RM size, and consider that the total RM size is reduced due to UCI multiplexing. Then, there are several possible ways to calculate the new RM size for each CB and satisfy the following: Equal size: ; Equal reduction:, ; Weighted size: (or ), or ), (or ); or Weighted reduction: (or ), or ), (or

[0237] From the UE implementation perspective and the impact on this specification, this solution could be quite complex.

[0238] An alternative to the previous method could be for the UE to re-determine the RM output for all time slots containing CBs affected by UCI multiplexing. This involves timeline adaptation to allow the UE sufficient time to perform the relevant processing before the first time slot containing the affected CB. There are three options for timeline adaptation, two of which are depicted in Figure 34, which depicts a multi-time slot shared channel with four time slots 3401, time slot 3402, time slot 3403, and 3404 and four code blocks CB1, code block CB2, code block CB3, code block CB4.

[0239] The first option could be for the timeline to start from the first time slot containing the affected CB that provides sufficient time to perform the relevant processing. In Figure 34, for the first option, the timeline 3405 starts from time slot 3403, which is the starting time slot containing CB4. The second option could be for the timeline 3406 to start from the first time slot containing a CB that does not exist in earlier time slots. In Figure 34, the timeline starts from time slot 3402 (i.e., the first time slot before time slot 3404), which contains a code block (i.e., CB2) that does not exist in earlier time slots. The third option could be for the timeline that allows sufficient time to perform the relevant processing to start from the first time slot of the multi-time slot PUSCH.

[0240] For embodiments 2 and 2a that rely on slot-based interleaver configurations, the UE can re-determine the RM output for the affected time slots and potentially subsequent time slots. This can be done after Rel-16 operation for RM determination due to UCI multiplexing, which is facilitated by the slot-based operation of the interleaver. In this case, when a time slot is affected by UCI multiplexing, resulting in a new RM size compared to the original, a new interleaver input sequence can be selected from the original input sequence by choice. In this case, the input sequences for all later time slots k can also be interleaved and adjusted to, or can remain the same as before. Alternatively, a new interleaver input sequence can be selected from the original input sequence using the general selection function described previously. Another consideration could be how to calculate for each CB in the case where a time slot involves multiple CBs, and the variables described previously can be applied.

[0241] In cases where such implementations are used, the UE can also perform intelligent RM determination operations that allow for better decoding of the affected CBs. This operation can be explained in the following example. Consider the example depicted in Figure 35, where the multi-time slot PUSCH spans two time slots with three CBs and RV3, and the RM output for each CB is depicted.

[0242] Assume that UCI multiplexing occurs on the second time slot of a multi-time slot PUSCH, which causes a portion of the coded bits in time slot 2 to no longer be available for the CB in the PUSCH. When adapting the RM output of the CB affected by the no-longer-available bits, one option could be to equally reduce the amount of available coded bits among those affected bits. However, this method may not provide the best decoding performance for the TB, as depicted in Figure 36, which depicts the RM output of a multi-slot PUSCH with two time slots, three CBs, RV3, and with UCI multiplexing. The RM outputs of the affected CBs are processed equally. In this case, due to the omission of system bits used for the RM output, CB2 is very adversely affected. CB3 is not adversely affected.

[0243] A technique better than the one depicted in Figure 36 could be to adapt the RM outputs of the two CBs in different ways according to the type of coded bits included. For example, one RM output could equally reduce the amount of parity bits from both CBs until all the parity bits of one CB are omitted, and then all the remaining omissions could be distributed among the CBs with remaining parity bits, etc. This method is depicted in Figure 37, which depicts the RM output of a multi-slot PUSCH with two time slots, three CBs, and RV3, and with UCI multiplexing. The RM outputs of the affected CBs maintain the system bits.

[0244] In the example depicted in Figure 38, the RM output of each CB of a multi-time slot PUSCH spanning four time slots with three CBs and RV0 is depicted.

[0245] Consider an example scenario where UCI multiplexing occurs on the third time slot of a multi-time slot PUSCH, which causes a portion of the coded bits in time slot 3 to no longer be available for the CB in the PUSCH. Figure 39 depicts the RM output corresponding to Figure 38, where the amount of available coded bits is equally reduced among the affected bits. In this case, due to the omission of system bits used for the RM output (even for such a small number of omitted bits), CB3 is very adversely affected. CB2 is not affected. Figure 40 depicts the RM output corresponding to Figure 38, where the affected CBs maintain the system bits. Implementing an intelligent RM decision method could be approximately determining the new RM output sizes for each CB in the affected time slot. If the RM outputs of the CBs at the time slot before UCI multiplexing are,, …,, then the RM outputs of the CBs after UCI multiplexing are,, …,. Then, the following options can be used to determine the values of each CB in the time slot.

[0246] The first option could determine equality among all the CBs in the affected time slot.

[0247] The second option may be to make the number of CBs in the time slot be. For the number of CBs in the CBs, make the initial scheduling such that the amounts of information bits and parity bits to be transmitted in the time slot are and respectively. Also, will be relabeled as to distinguish the new RM sizes of each CB. And make the new RM size of the time slot equal to. Then, set to be equal to. If, then reduce all values of by, and consider the CBs with non-zero values, which are a new CB set of size. Make the increase of this CB set equal to the amount of. If, and if for all the original CBs,, then increase all the original CBs by an equal amount until. If, then repeat the determination of whether.

[0248] For all embodiments disclosed herein, if the transport block contains a single code block, the operations may be performed per transport block, or if the transport block contains multiple code blocks, the operations may be performed per code block. The described operations do not depend on how the coding bits corresponding to the code region are mapped to time resources. An example of a potential mapping of coding bits to time resources is depicted in FIG. 41, where one transport block contains three code blocks and the coding bits are mapped to four time slots 4101, time slot 4102, time slot 4103, and time slot 4104. In the first example mapping mechanism depicted at the top of FIG. 41, the allocated code block mapping distributes the coding bits from each code block across all time slots. In the second example mapping mechanism depicted at the bottom of FIG. 41, the consecutive / local code block mapping sequentially maps the coding bits from the code blocks across all time slots. In both example mapping mechanisms (and mapping mechanisms not explicitly depicted), the operations described herein may be performed per code block, where if further mapped onto time slots, then the output of the operations described herein is then mapped according to the mapping mechanism being used. For example, for the consecutive rate matching operation, a consecutive amount of coding bits is selected per code block, and the coding bits are to be mapped across all time slots regardless of whether the code block is in two time slots or four time slots. As another example, for the RV-index-based segmented rate matching operation, the rate matching operation may select, per code block, a set of coding bits to be mapped in each time slot, where for each time slot, the set of coding bits is selected based on the RV index. This is independent of whether the code block is in two time slots or four time slots. Similar behavior may exist, such as for other rate matching operations and interleaver operations. Additionally, although other figures herein may be understood to describe different embodiments in terms of consecutive / local code block mapping, it should be understood that other mappings may apply, including but not limited to the allocated code block mapping.

[0249] The embodiments of the subject matter and the operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware (including the structures disclosed in this specification and their structural equivalents), or in a combination of one or more of them. Alternatively or additionally, program instructions can be encoded on an artificially generated propagated signal (for example, a machine-generated electrical, optical, or electromagnetic signal) that is generated to encode information for transmission to a suitable receiver device for execution by a data processing device. A computer storage medium can be or be included in a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination thereof. Further, when a computer storage medium is not a propagated signal, the computer storage medium can be a source or destination of computer program instructions encoded in an artificially generated propagated signal. The computer storage medium can also be one or more separate physical components or media (for example, multiple CDs, disks, or other storage devices) or be included in one or more separate physical components or media. Additionally, the operations described in this specification can be implemented as operations performed by a data processing device on data stored on one or more computer-readable storage devices or received from other sources.

[0250] Although this specification may contain many specific implementation details, the implementation details should not be construed as limitations on the scope of any claimed subject matter, but rather as descriptions of features specific to particular embodiments. Certain features that are described in the context of separate embodiments in this specification can also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment can also be implemented separately in multiple embodiments or in any suitable sub-combination. Additionally, although the features may be described above as acting in certain combinations and even initially claimed as such, one or more features from the claimed combination can in some cases be deleted from the combination, and the claimed combination can be directed to a sub-combination or variation of a sub-combination.

[0251] Similarly, although the operations are depicted in the drawings in a particular order, this should not be understood as requiring that the operations be performed in the particular order shown or in sequential order, or that all of the operations shown be performed to achieve a desirable result. In some cases, multitasking and parallel processing can be advantageous. Additionally, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

[0252] Accordingly, specific embodiments of the subject matter have been described herein. Other embodiments are within the scope of the following claims. In some cases, the acts recited in the claims can be performed in a different order and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order or sequential order shown to achieve desirable results. In certain implementations, multitasking and parallel processing may be advantageous.

[0253] As those skilled in the art will recognize, the novel concepts described herein can be modified and varied across a wide range of applications. Accordingly, the scope of the claimed subject matter should not be limited to any of the particular illustrative teachings discussed above, but is actually defined by the following claims.

Brief Description of the Drawings

[0008] In the following sections, aspects of the subject matter disclosed herein will be described with reference to the exemplary embodiments shown in the drawings, wherein: FIG. 1 depicts an example embodiment of a wireless communication network according to the subject matter disclosed herein. FIG. 2 depicts an example embodiment of a base station according to the subject matter disclosed herein. FIG. 3 depicts an example embodiment of a user equipment according to the subject matter disclosed herein. FIG. 4A depicts an example embodiment of a downlink time slot structure. FIG. 4B depicts an example embodiment of an uplink time slot structure for physical uplink shared channel transmission or physical uplink control channel transmission. FIG. 5A depicts a block diagram of an example embodiment of a transmitter structure using OFDM according to the subject matter disclosed herein. FIG. 5B depicts a block diagram of an example embodiment of an OFDM receiver structure according to the subject matter disclosed herein. FIG. 6 illustrates a typical legacy processing flow at a transmitter for uplink and downlink of a physical shared channel in Release 16. FIG. 7 depicts an example of physical and virtual resources that can be allocated to a UE in Release 16. FIG. 8 depicts the multiplexing of uplink control information on a physical uplink shared channel when scheduled resource overlap occurs in Release 16. FIG. 9 illustrates some details of codewords that can be transmitted across a time slot depending on the size of a data block according to the subject matter disclosed herein. FIG. 10 depicts an example scenario according to the subject matter disclosed herein where the data block is small enough to fit into a single code block spanning a time slot boundary. FIG. 11 depicts an example scenario according to the subject matter disclosed herein where a relatively large data block is fitted into two code blocks. FIG. 12 illustrates an example scenario according to the subject matter disclosed herein where a relatively extremely large data block is fitted into multiple code blocks. FIG. 13 depicts an example scenario according to the subject matter disclosed herein when not divided by time. FIG. 14 depicts an example of a scenario where the resources available for mapping PUSCH transmission across time slots are discontinuous according to the subject matter disclosed herein. FIG. 15 depicts three positions in a transport block processing chain according to the subject matter disclosed herein where a processing cancellation indication can be executed in operation. FIGS. 16A to 16E depict example scenarios according to the subject matter disclosed herein where a cancellation indication in one time slot of an uplink cross-time slot mapped transmission is received and processed by a transmitter. FIG. 17A depicts an example cross-time slot mapped transmission of two code block groups across three time slots according to the subject matter disclosed herein. FIG. 17B depicts an example cross-time slot mapped transmission of two code block groups across three time slots with code block segmentation according to the subject matter disclosed herein. FIG. 18 depicts an example operation of a transport block processing chain according to the subject matter disclosed herein. FIG. 19A depicts an example cross-time slot mapped transmission of code blocks in two code block groups across three time slots according to the subject matter disclosed herein. FIG. 19B depicts an example cross-time slot mapped transmission of code blocks in two code block groups with segmentation across three time slots according to the subject matter disclosed herein.Figure 20 depicts a configured authorization period in a configured authorization configuration that may include a set of regular transmission times and a set of cross-slot mapped transmission times according to the subject matter disclosed herein. Figure 21A depicts an example scenario where the codeword length is too small. Figure 21B depicts an example scenario where an additional redundant version according to the subject matter disclosed herein has been added to the transport block. Figures 22A and 22B depict example scenarios where a less redundant version according to the subject matter disclosed herein is available for the transport block. Figures 23A and 23B depict example continuous rate matching outputs of code blocks and corresponding interleaver outputs that are known to cross the slot boundary between slots according to the subject matter disclosed herein. Figures 24A and 24B depict example segmented code block rate matching outputs and corresponding interleaver outputs with new redundant versions according to the subject matter disclosed herein. Figures 25A and 25B depict example limited continuous rate matching outputs of code blocks and corresponding limited continuous interleaver outputs according to the subject matter disclosed herein. Figures 26A and 26B depict example continuous rate matching outputs and corresponding interleaver outputs that independently cross each slot according to the subject matter disclosed herein. Figures 27A and 27B depict example segmented code block rate matching outputs and corresponding interleaver outputs with new redundant versions that independently cross each slot according to the subject matter disclosed herein. Figures 28A and 28B depict example rate matching outputs and corresponding interleaver outputs where system bits and parity bits are processed separately when determining the input to the interleaver for different slots according to the subject matter disclosed herein. Figure 29 illustrates an example of a rate matching output that has been segmented according to the subject matter disclosed herein. Figure 30 depicts an example scenario where a multi-slot PUSCH is scheduled and uplink control information has been scheduled to be multiplexed in one of the slots that form the multi-slot PUSCH. Figure 31 depicts the example scenario of Figure 30 from a timeline perspective. Figure 32 depicts an example punctured slot of a first embodiment of rate matching and interleaver operation according to the subject matter disclosed herein. Figure 33 depicts an example punctured slot of a first embodiment of rate matching and interleaver operation according to the subject matter disclosed herein. Figure 34 depicts a timeline adaptation of a multi-slot shared channel with four slots and four code blocks for uplink control information multiplexing according to the subject matter disclosed herein. Figure 35 depicts example rate matching outputs for each code block of a multi-slot PUSCH that spans two slots, has three code blocks, RV3, and has UCI multiplexing according to the subject matter disclosed herein. Figure 36 depicts example rate matching outputs of a multi-slot PUSCH that has two slots, three code blocks, RV3, and has UCI multiplexing according to the subject matter disclosed herein. Figure 37 depicts example rate matching outputs of a multi-slot PUSCH that has two slots, three code blocks, RV3, and has UCI multiplexing with system bits that maintain the code block according to the subject matter disclosed herein.FIG. 38 depicts an example rate matching output of a multi-slot PUSCH across four time slots with three CBs and RV0 according to the subject matter disclosed herein. FIG. 39 depicts a rate matching output corresponding to FIG. 38 according to the subject matter disclosed herein, where the amount of available puncturing bits is equally reduced among the affected bits. FIG. 40 depicts a rate matching output corresponding to FIG. 38 according to the subject matter disclosed herein, where the affected code blocks maintain system bits. FIG. 41 depicts alternative code blocks mapped to per-code-block time slots when the transport block contains one or more code blocks according to the subject matter disclosed herein.

Claims

1. A transport block processing chain for a transmitter, comprising: A code block determination circuit configured to determine the size of multiple code blocks generated by segmenting the transport blocks and mapped across multiple time slots allocated for uplink transmission in a shared radio entity channel, based on Radio Resource Control (RRC) configured for Transport Block over Multiple Slots (TBoMS); a rate matching circuit configured to rate match the bits of the multiple code blocks with several bits available in the transport blocks spanning the multiple time slots of the shared radio entity channel; and an interleaver configured to interleave the successive outputs of the rate matching circuit based on time slots, such that code blocks crossing the time slot boundary between a first time slot and a second time slot are interleaved within the first time slot and the second time slot, wherein the interleaver is configured to operate independently across each of the first time slot and the second time slot.

2. The transport block processing chain as described in claim 1, wherein the plurality of time slots of the radio entity shared channel configured according to the TBoMS are at least partially based on the maximum transport block size (TBS) as set forth in the previous version of the 3GPP standard document.

3. The transport block processing chain as described in claim 1, wherein the plurality of time slots of the radio entity shared channel configured according to the TBoMS are at least partially based on a predetermined number of code blocks.

4. The transport block processing chain as described in claim 3, wherein the predetermined number of code blocks is at least partially based on the maximum number of code blocks set forth in the previous version of the 3GPP standard document.

5. The transport block processing chain as described in claim 1, wherein the plurality of time slots of the radio entity shared channel configured according to the TBoMS are at least partially based on the maximum transport block size (TBS) as set forth in the 3GPP standard document.

6. A method for processing data to be mapped into a transport block, the method comprising: The code block determination circuit determines the size of multiple code blocks, which are data generated by segmenting the transport blocks and mapped across multiple time slots allocated for uplink transmission in the Radio Entity Shared Channel, based on the Radio Resource Control (RRC) configuration for Transport Block over Multiple Slots (TBoMS). A rate matching circuit rate-matches the bits of the multiple code blocks with several bits available in the transport blocks spanning the multiple time slots of the Radio Entity Shared Channel. An interleaver interleaves the successive outputs of the rate matching circuit based on the time slots, such that code blocks crossing the time slot boundary between a first time slot and a second time slot are interleaved within the first and second time slots, wherein the interleaver operation is performed independently across each of the first and second time slots.

7. The method as described in claim 6, wherein the plurality of time slots of the radio entity shared channel configured according to the TBoMS are based at least in part on the maximum transport block size (TBS) as set forth in the previous version of the 3GPP standard document.

8. The method as described in claim 6, wherein the plurality of time slots of the wireless entity shared channel configured according to the TBoMS are at least partially based on a predetermined number of code blocks.

9. The method of claim 8, wherein the predetermined number of code blocks is based at least in part on the maximum number of code blocks set forth in a previous version of the 3GPP standard document.

10. The method of claim 6, wherein the plurality of time slots of the radio entity shared channel configured according to the TBoMS are based at least in part on the maximum transport block size (TBS) as set forth in the 3GPP standard document.

Images