SPS and multiple PDSCH configurations for multiple TBs in rate splitting and DCI

Abstract

A user equipment (UE) may receive and decode a plurality of types of transport blocks. The UE may receive, via a transceiver, downlink control information (DCI) indicating at least a first transmission parameter for the UE for a first type of transport block and a second transmission parameter for a second type of transport block for rate splitting with a second UE. The UE may receive, via the transceiver, the transport block of the first type based on the first transmission parameter during a first physical downlink shared channel (PDSCH) occasion. The UE may receive, via the transceiver, the second type of transport block based on the second transmission parameter and a third type of transport block based on a third transmission parameter during a second PDSCH occasion.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. non-provisional patent application No. 18 / 046,749, entitled “SPS and Multi-PDSCH Configuration and DCI forMultiple TB Case” and filed on October 14, 2022, which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates to wireless communications, and more particularly to semi-persistent scheduling (SPS) or multiple physical downlink shared channel (PDSCH) configurations and downlink control information (DCI) for multiple transport block (TB) cases. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, or even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability, such as those associated with the Internet of Things (IoT), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Summary of the invention

[0006] The systems, methods and devices of the disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

[0007] In some aspects, the technology described herein relates to a method for wireless communication for a user equipment (UE), the method comprising: receiving downlink control information (DCI) indicating at least a first transmission parameter for a first type of transport block for the UE and a second transmission parameter for a second type of transport block for rate splitting with a second UE. The method comprises: receiving the first type of transport block based on the first transmission parameter during a first physical downlink shared channel (PDSCH) opportunity. The method comprises: receiving the second type of transport block based on the second transmission parameter and receiving the third type of transport block based on a third transmission parameter during a second PDSCH opportunity.

[0008] The present disclosure also provides a device (e.g., UE) comprising a memory storing computer-executable instructions and at least one processor configured to execute these computer-executable instructions to perform the above method, a device comprising components for executing the above method, and a non-transitory computer-readable medium storing computer-executable instructions for executing the above method.

[0009] One innovative aspect of the subject matter described in the present disclosure may be implemented in a method of wireless communication at a base station (BS), the method comprising: transmitting a DCI indicating at least a first transmission parameter for a first type of transport block for a UE and a second transmission parameter for a second type of transport block for rate splitting with a second UE. The method comprises: transmitting a first transport block of the first type based on the first transmission parameter during a first PDSCH opportunity. The method comprises: transmitting a second type of transport block based on the second transmission parameter and transmitting a third type of transport block based on a third transmission parameter during a second PDSCH opportunity.

[0010] The present disclosure also provides a device (e.g., a BS) comprising a memory storing computer-executable instructions and at least one processor configured to execute these computer-executable instructions to perform the above method, a device comprising components for executing the above method, and a non-transitory computer-readable medium storing computer-executable instructions for executing the above method.

[0011] Details of one or more specific implementations of the subject matter described in the present disclosure are set forth in the accompanying drawings and the following description. Other features, aspects, and advantages will become apparent from the specification, drawings, and claims. Note that the relative sizes of the following drawings may not be drawn to scale. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0013] Figure 2A is a diagram illustrating an example of the first frame.

[0014] Figure 2B is a diagram illustrating an example of a DL channel within a subframe.

[0015] Figure 2C is a diagram illustrating an example of the second frame.

[0016] Figure 2D is a diagram illustrating an example of a subframe.

[0017] Figure 3 is a diagram illustrating an example of a base station (BS) and a user equipment (UE) in an access network.

[0018] Figure 4 A diagram illustrating an example decomposed base station architecture is shown.

[0019] Figure 5 is a diagram illustrating a transmission process for rate splitting.

[0020] Figure 6 is a diagram illustrating a reception process for rate splitting.

[0021] Figure 7 is a diagram illustrating semi-persistent scheduling.

[0022] Figure 8 is a diagram illustrating different transport block types on scheduled physical downlink control channel opportunities.

[0023] Fig. 9 is a diagram illustrating two levels of downlink control information for scheduling different transport block types.

[0024] Fig.10 is a diagram illustrating example downlink control information for scheduling different transport block types.

[0025] Fig.11 is a diagram of an example DCI for providing transmission parameters for different transport block types.

[0026] Fig.12 is a message diagram illustrating example messages between a base station and a UE.

[0027] Fig.13 is a conceptual data flow diagram illustrating the flow of data between different elements / components in an example base station.

[0028] Fig.14 is a conceptual data flow diagram illustrating the data flow between different parts / components in an example UE.

[0029] Fig.15is a flow chart of an example method for a UE to receive different types of transport blocks.

[0030] Fig.16 is a flow chart of an example method for a base station to send different types of transport blocks.

[0031] The same reference numbers and designations in different drawings represent the same elements. DETAILED DESCRIPTION

[0032] For the purpose of describing the innovative aspects of the present disclosure, the following description refers to certain specific implementations. However, one of ordinary skill in the art will readily recognize that the teachings herein can be applied in a variety of different ways. Some examples in the present disclosure are based on wireless and wired local area network (LAN) communications in accordance with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 wireless standard, the IEEE 802.3 Ethernet standard, and the IEEE 1901 Power Line Communication (PLC) standard. However, the specific implementations described can be implemented in any device, system, or network capable of sending and receiving RF signals in accordance with any of the following wireless communication standards: including the IEEE 802.11 standard, the IEEE 802.3 Ethernet standard, and the IEEE 1901 Power Line Communication (PLC) standard. Standard, Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), GSM / General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunked Radio (TETRA), Wideband CDMA (W-CDMA), Evolution-Data Optimized (EV-DO), 1xEV-DO, EV-DO Revision A, EV-DO Revision B, High Speed ​​Packet Access (HSPA), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Evolved High Speed ​​Packet Access (HSPA+), Long Term Evolution (LTE), AMPS, or any other known signal used for communication within a wireless network, cellular network, or Internet of Things (IOT) network (such as, a system utilizing 3G, 4G or 5G technology or further specific implementations thereof).

[0033] In wireless communications, data for a particular user is typically encoded as a single message for that user. Academic research has explored the possibility of using rate splitting techniques to send user data through a combination of private and public messages. Such techniques may enable greater freedom and / or greater capacity. While such benefits are theoretically possible, the signaling overhead for rate splitting techniques within actual communication networks may reduce the potential benefits of rate splitting. Therefore, efficient signaling techniques may be desired to avoid a significant increase in the signaling overhead of rate splitting techniques.

[0034] In one aspect, the present disclosure provides a technique for signaling a user equipment (UE) to transmit parameters for multiple PDSCH opportunities with potential rate splitting. For example, multiple PDSCH opportunities may be indicated by a semi-persistent scheduling (SPS) configuration or a multi-PDSCH DCI. Since rate splitting may depend on other UEs, signaling may provide transmission parameters for different types of transport blocks (such as dedicated transport blocks, private transport blocks for rate splitting, and public transport blocks for rate splitting). Downlink control information (DCI) may indicate transmission parameters for at least a first type of transport block and a second type of transport block. In some cases, transmission parameters for a third type of transport block may be included in the DCI or derived from other transmission parameters. The UE may receive a dedicated transport block based on a first transmission parameter. Based on the corresponding transmission parameters, the UE may receive a private transport block for rate splitting and a public transport block for rate splitting during a PDSCH opportunity. The UE may use a rate splitting decoding process to first decode the public transport block and then use interference cancellation to decode the private transport block.

[0035] Certain implementations of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages: A UE may benefit from increased throughput using rate splitting without significantly increasing signaling overhead.

[0036] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0037] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic components, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. The processor may include an interface or be coupled to an interface that can obtain or output a signal. The processor may obtain a signal via an interface and output a signal via an interface. In some specific implementations, the interface may be a printed circuit board (PCB) transmission line. In some other specific implementations, the interface may include a wireless transmitter, a wireless transceiver, or a combination thereof. For example, the interface may include a radio frequency (RF) transceiver, which may be implemented to receive or transmit a signal, or both. One or more processors in a processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0038] Therefore, in one or more example implementations, the functions described herein may be implemented with hardware, software, or any combination thereof. If implemented with software, the functions may be stored or encoded on a computer-readable medium as one or more instructions or codes. Computer-readable media include computer storage media, which may be referred to as non-transitory computer-readable media. Non-transitory computer-readable media do not include transient signals. The storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, a combination of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

[0039] Figure 11 is a diagram illustrating an example of a wireless communication system and an access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, a relay device 105, an evolved packet core (EPC) 160, and another core network 190 (such as a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) or a small cell (a low-power cellular base station). The macro cell includes a base station. The small cell includes a femto cell, a pico cell, and a micro cell. The small cell includes a femto cell, a pico cell, and a micro cell. The base station 102 may be configured as a disaggregated RAN (D-RAN) or an open RAN (O-RAN) architecture, in which functionality is split between multiple units (such as a central unit (CU), one or more distributed units (DUs), or radio units (RUs). Such an architecture may be configured to utilize a protocol stack that is logically split between one or more units (such as one or more CUs and one or more DUs). In some aspects, the CU may be implemented within an edge RAN node, and in some aspects, one or more DUs may be co-located with the CU, or may be geographically distributed in one or more RAN nodes. The DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU). In general, the base station 102 may be referred to as a network entity.

[0040] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0041] In some implementations, one or more of the UEs 104 may include a multi-TB decoder component 140 configured to decode multiple transport block (TB) types scheduled together. The multi-TB decoder component 140 may include a DCI component 140 configured to receive downlink control information (DCI) indicating at least a first transmission parameter for a first type of transport block for the UE and a second transmission parameter for a second type of transport block for rate splitting with a second UE. The multi-TB decoder component 140 may include a single TB decoder 144 configured to receive a first transport block of the first type based on the first transmission parameter during a first physical downlink shared channel (PDSCH) opportunity. The multi-TB decoder component 140 may include a rate splitting decoder 146 configured to receive a second type of transport block based on the second transmission parameter and a third type of transport block based on the third transmission parameter during a second PDSCH opportunity. The multi-TB decoder component 140 may optionally include a configuration component 148 configured to receive a second type of transport block based on a second transmission parameter and a third type of transport block based on a third transmission parameter during a second PDSCH opportunity.

[0042] In some implementations, one or more of the base stations 102 may include a multi-TB transmitter component 120 configured to transmit multiple transport block types scheduled together. The multi-TB transmitter component 120 may include a DCI transmitter 122 configured to transmit a DCI indicating at least a first transmission parameter for a first type of transport block for a UE and a second transmission parameter for a second type of transport block for rate splitting with a second UE. The multi-TB transmitter component 120 may include a single TB transmitter 124 configured to transmit a first type of first transport block based on a first transmission parameter during a first physical downlink shared channel (PDSCH) opportunity. The multi-TB transmitter component 120 may include a rate splitting transmitter 126 configured to transmit a second type of transport block based on a second transmission parameter and a third type of transport block based on a third transmission parameter during a second PDSCH opportunity.

[0043] The base station 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can be connected to the EPC 160 through a first backhaul link 132 (such as an S1 interface), which can be wired or wireless. The base station 102 configured for 5G NR (collectively referred to as the Next Generation RAN (NG-RAN)) can interact with the core network 190 through a second backhaul link 184, which can be wired or wireless. In addition to other functions, the base station 102 can also perform one or more of the following functions: transmission of user data, wireless channel encryption and decryption, integrity protection, header compression, mobility control functions (such as handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (such as through the EPC 160 or the core network 190) over a third backhaul link 134 (such as an X2 interface). The third backhaul link 134 may be wired or wireless.

[0044] Base station 102 can communicate wirelessly with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' can have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells can be referred to as a heterogeneous network. A heterogeneous network can also include a home evolved B node (eNB) (HeNB) that can provide services to a restricted group called a closed subscriber group (CSG). A communication link 112 between base station 102 and UE 104 can include UL (also known as a reverse link) transmission from UE 104 to base station 102 or DL ​​(also known as a forward link) transmission from base station 102 to UE 104. The communication link 112 can use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming, or transmit diversity. The communication link can be through one or more carriers. For each carrier allocated in the carrier aggregation for transmission in each direction with a total of up to YxMHz (x component carriers), the base station 102 / UE 104 can use a spectrum with a bandwidth of up to YMHz (such as 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.). The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (such as more or fewer carriers may be allocated for DL ​​than for UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0045] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through various wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on IEEE 802.11 standards, LTE, or NR.

[0046] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available prior to communication.

[0047] The small cell 102' may operate in a licensed or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed spectrum as the 5 GHz unlicensed spectrum used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may boost coverage of the access network or increase capacity of the access network.

[0048] Whether a small cell 102' or a large cell (such as a macro base station), the base station 102 may include an eNB, a gNodeB (gNB), or other types of base stations. Some base stations (such as gNB 180) may operate in one or more frequency bands within the electromagnetic spectrum.

[0049] The electromagnetic spectrum is often subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the “sub-6GHz” band in various documents and articles. A similar naming issue sometimes occurs with FR2, which is often (interchangeably) referred to as the “millimeter wave” band in various documents and articles, although it is different from the extremely high frequency (EHF) band (30GHz to 300GHz) identified as the “millimeter wave” (mmW) band by the International Telecommunication Union (ITU).

[0050] In view of the above aspects, unless otherwise specifically stated, it should be understood that if used herein, the term "below 6 GHz" or the like may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, it may broadly represent frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band. Communications using mmW radio frequency bands have extremely high path loss and short range. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for such path loss and short range.

[0051] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Generally speaking, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, or other IP services. The BM-SC 170 may provide functions for MBMS user service configuration and delivery. BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services in a public land mobile network (PLMN), and may be used to schedule MBMS delivery. MBMS gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area of ​​a broadcast specific service, and may be responsible for session management (start / stop) and for collecting eMBMS related billing information.

[0052] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may communicate with a unified data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Generally speaking, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, or other IP services.

[0053] The base station may include or be referred to as a gNB, a node B, an eNB, an access point, a base transceiver, a wireless base station, a wireless transceiver, a transceiver functional unit, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), or some other appropriate term. The base station 102 provides an access point to the EPC 160 or the core network 190 for the UE 104. Examples of UE 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (such as an MP3 player), a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of the UEs 104 may be referred to as IoT devices (such as parking meters, gas pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0054] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM and other wireless technologies, including future 6G technologies.

[0055] Figure 2A is a diagram 200 illustrating an example of a first frame. Figure 2B is a diagram 230 illustrating an example of a DL channel within a subframe. Figure 2C is a diagram 250 illustrating an example of a second frame. Figure 2D 280 is a diagram illustrating an example of a subframe. The 5G NR frame structure may be FDD, where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be TDD, where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. A subset of the total cell bandwidth of a cell is referred to as a bandwidth part (BWP), and bandwidth adaptation is achieved by configuring the UE with a BWP and informing the UE which of the configured BWPs is currently the active BWP.

[0056] exist Figure 2A , Figure 2CIn the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and X can be used flexibly between DL / UL, and subframe 3 is configured with slot format 34 (most of which are UL). Although subframes 3 and 4 are shown as having slot formats 34 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0 to 61. Slot formats 0 and 1 are both DL and both UL, respectively. Other slot formats 2 to 61 include a mix of DL, UL and flexible symbols. The slot format is configured for the UE by a received slot format indicator (SFI) (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0057] Other wireless communication technologies may have different frame structures or different channels. A frame (10 milliseconds (ms)) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include mini-slots, which may include 7, 4, or 2 symbols. Each time slot may contain 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbols on the DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of time slots in a subframe is based on the time slot configuration and parameter set. For slot configuration 0, different parameter sets μ0 to 5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Thus, for slot configuration 0 and parameter set μ, there are 14 symbols per slot and 2 per subframe. μ time slots. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 5. Thus, parameter set μ=0 has a subcarrier spacing of 15kHz, and parameter set μ=5 has a subcarrier spacing of 480kHz. Symbol length / duration is inversely related to subcarrier spacing. FIG. 2A to FIG. 2DAn example is provided for slot configuration 0 with 14 symbols per slot and parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 microseconds (μs).

[0058] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0059] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) for channel estimation at the UE (indicated as R for a particular configuration). x , where 100x is the port number, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS). RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0060] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including nine RE groups (REGs), each REG including four consecutive REs in an OFDM symbol. The primary synchronization signal (PSS) may be within symbol 2 of a specific subframe of the frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identity. The secondary synchronization signal (SSS) may be within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (SSB). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information such as System Information Blocks (SIBs) not sent through the PBCH, and paging messages.

[0061] like Figure 2CAs illustrated, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first one or the first two symbols of the PUSCH. The PUCCH DM-RS may be sent in different configurations depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used.

[0062] The UE may send a sounding reference signal (SRS). The SRS resource set configuration may define the resources used for SRS transmission. For example, as shown in the figure, the SRS configuration may specify that the SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one comb tooth for each SRS port. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling for the UL. The SRS may also be used for channel estimation to select a pre-decoder for downlink MIMO.

[0063] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), or UCI.

[0064] Figure 31 is a diagram of an example of a base station 102 and a UE 104 in an access network. UE 104 may be an example of a receiving device. In the DL, IP packets from EPC 160 may be provided to controller / processor 375. Controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (such as MIB, SIB), RRC connection control (such as RRC connection paging, RRC connection establishment, RRC connection modification and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification) and handover support functions; RLC layer functionality associated with transmission of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling and logical channel prioritization.

[0065] The transmit (Tx) processor 316 and receive (Rx) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transmission channel, forward error correction (FEC) decoding / decoding of the transmission channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The Tx processor 316 handles the mapping to the signal constellation based on various modulation schemes (such as binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can be split into parallel streams. Each stream can be mapped to an OFDM subcarrier, multiplexed with a reference signal (such as a pilot) in the time domain or frequency domain, and combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine coding and modulation schemes, as well as for spatial processing. The channel estimate may be derived from a reference signal or channel condition feedback sent by the UE 104. Each spatial stream may be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0066] At the UE 104, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (Rx) processor 356. The Tx processor 368 and the Rx processor 356 implement layer 1 functionality associated with various signal processing functions. The Rx processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 104. If multiple spatial streams are destined for the UE 104, they can be combined into a single OFDM symbol stream by the Rx processor 356. The Rx processor 356 uses a fast Fourier transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 102. These soft decisions can be based on channel estimates calculated by the channel estimator 358. These soft decisions are decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 102. These data and control signals are provided to the controller / processor 359 which implements layer 3 and layer 2 functionality.

[0067] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using an ACK or NACK protocol to support HARQ operations.

[0068] Similar to the functionality described in conjunction with DL transmissions performed by the base station 102, the controller / processor 359 provides RRC layer functionality associated with system information (such as MIB, SIB) acquisition, RRC connection and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling and logical channel prioritization.

[0069] Channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 102 may be used by the Tx processor 368 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the Tx processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0070] UL transmissions are processed at the base station 102 in a manner similar to that described in conjunction with the receiver functionality at the UE 104. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to an Rx processor 370.

[0071] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from the UE 104. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using an ACK or NACK protocol to support HARQ operations.

[0072] At least one of the Tx processor 368, the Rx processor 356, and the controller / processor 359 may be configured to cause the UE 104 to perform operations related to Figure 1 The memory 360 may include various aspects related to the multi-TB decoder component 140 of the present invention. For example, the memory 360 may include executable instructions that define the multi-TB decoder component 140. The Tx processor 368, the Rx processor 356, and / or the controller / processor 359 may be configured to execute the multi-TB decoder component 140.

[0073] At least one of the Tx processor 316, the Rx processor 370, and the controller / processor 375 may be configured to cause the base station 102 to perform operations related to Figure 1 For example, the memory 376 may include executable instructions that define the multi-TB transmitter component 120. The Tx processor 316, the Rx processor 370, and / or the controller / processor 375 may be configured to execute the multi-TB transmitter component 120.

[0074] Figure 4 A diagram illustrating an example disaggregated base station 400 architecture is shown. The disaggregated base station 400 architecture may include one or more central units (CUs) 410 that may communicate directly with a core network 420 via a backhaul link, or indirectly with the core network 420 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 425 via an E2 link, or a non-real-time (non-RT) RIC 415 associated with a service management and orchestration (SMO) framework 405, or both. The CU 410 may communicate with one or more distributed units (DUs) 430 via respective midhaul links, such as an F1 interface. The DU 430 may communicate with one or more radio units (RUs) 440 via respective fronthaul links. The RU 440 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 440.

[0075] Each of the units (i.e., CU 410, DU 430, RU 440, and near-RT RIC 425, non-RT RIC 415, and SMO framework 405) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

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

[0077] DU 430 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RU 440. In some aspects, DU 430 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to functional divisions such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 430 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 430 or with control functions hosted by CU 410.

[0078] The lower layer functionality may be implemented by one or more RUs 440. In some deployments, a RU 440 controlled by a DU 430 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 440 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of communicating with the control plane and user plane of the RU 440 may be controlled by the corresponding DU 430. In some scenarios, this configuration may enable the implementation of the DU 430 and the CU 410 in a cloud-based RAN architecture (such as a vRAN architecture).

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

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

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

[0082] Figure 5 5 is a diagram illustrating a transmission process 500 for rate splitting. A transmitting device, such as a base station 102, may generate a message (W1) for each UE 104 (e.g., UE 104a and 104b) for transmission. The transmitting device may perform a message splitting operation 510 on each message. The message splitting operation 510 may divide each message into a private message W1 and a private message W2. 1,p and public message W 1,c The combiner 520 can combine the public message W 1,c and W 2,c Connect to public stream W c . Public Stream W c And each private message (e.g., W 1,p and W 2,p ) is provided to the encoder 530. The encoder 530 may perform encoding, modulation, and mapping to one or more layers. The encoder 530 outputs the encoded private streams X1, X2 and the encoded public stream X c At pre-decoding 540, the common stream X c By pre-decoder P c The private streams are pre-coded by P1 and P2 and transmitted by Tx antennas (from one TRP / gNB or multiple TRPs in CoMP scenarios). For example, the output transmission can be X=(P c X c +P1X1+P2X2). The output transmission may be subject to channel conditions and noise. For example, the signal received at UE 104a may be Y1=H1P c X c +H1P1X1+H1P2X2+N1.

[0083] Figure 6 is a diagram illustrating a reception process 600 for rate splitting. UE 104a may receive signal Y1， And perform channel estimation 610 on the public stream and perform channel estimation 620 on the private stream. At block 630, UE 104a may decode the public stream to obtain the public message W c UE 104a can receive the public message W c Extract the common message W for UE 104a 1,c At block 640, UE 104a may c Rebuild public stream X c and multiplied by the estimated effective channel to perform successive interference cancellation. At block 650, UE 104a may subtract the common stream X from the received signal Y1. c Assuming that the channel estimation is completely correct and the decoding is successful, Y 1,p =Y1-H1P c X c =H1P1X1+H1P2X2+N1. UE 104a may then calculate the 1,p Send private message to W 1,p Decoding 660 may include demodulation and demapping as well as decoding. UE 104a may combine W 1,c and W 1,p to obtain the original message W1.

[0084] Figure 7700 is a diagram illustrating semi-persistent scheduling (SPS). The base station 102 may configure the UE 104 with an SPS configuration, for example, via radio resource control (RRC) signaling. The SPS configuration may define SPS parameters such as a periodicity (p) 710, a start time parameter (K0) 712, and a HARQ feedback timing parameter (K1) 714. The parameter p 710 specifies the time between two SPS PDSCH opportunities 730. The parameter K0 712 specifies the time period between the activation DCI 720 and the first PDSCH opportunity 730. The parameter K1 714 specifies the PUCCH slot 740 on which the HARQ-ACK is sent after receiving the PDSCH. The UE may be configured with multiple SPS configurations. The base station 102 may activate the SPS configuration by sending an activation DCI 720. In some implementations, the activation DCI 720 may be a format 1_1 DCI scrambled with a configured scheduling (CS) radio network temporary identifier (RNTI). The activation DCI 720 may carry additional transmission parameters for receiving TBs on the PDSCH opportunities 730 defined by the SPS configuration. For example, the DCI 720 may include time domain resource allocation (TDRA), frequency domain resource allocation (FDRA), modulation and coding scheme (MCS), and demodulation reference signal (DMRS) information (e.g., antenna port). In some cases, the base station 102 may not send TBs on the PDSCH opportunities 730, and the UE 104 may send HARQ-NACK in the PUCCH slot 740.

[0085] Figure 8 is a diagram illustrating the use of DCI to change the transmission parameters of an SPS configuration. Initially, the SPS configuration may not be activated and no PDSCH is transmitted on the configured PDSCH opportunity 730. After the UE 104 receives the activation DCI 720, the UE may receive a TB on each of the configured PDSCH opportunities 730. If the base station 102 determines that the transmission parameters are to be changed, the base station 102 may send a reactivation DCI 820 with new transmission parameters for the SPS configuration. The UE 104 may receive a TB on the PDSCH opportunity 730 based on the new transmission parameters. The base station 102 may deactivate the SPS configuration by sending an SPS release DCI 830, after which the UE 104 may not receive a TB on the configured PDSCH opportunity 830.

[0086] In one aspect, SPS can be used to schedule transmission using rate splitting techniques. However, in rate splitting techniques, different streams (e.g., X1 and X2) for a UE are scheduled to transmit at the same time. c) may be encoded or pre-coded based on different transmission parameters (e.g., MCS and PMI). Thus, SPS may schedule two transport blocks (TBs) for rate splitting. In addition, since transmissions to the first UE 104a may not always be aligned with transmissions to the second UE 104b, SPS scheduling may also schedule separate TBs for regular (e.g., non-rate splitting) transmissions. That is, SPS for a UE configured for rate splitting may involve scheduling three or more types of TBs.

[0087] Fig. 9 900 is a diagram illustrating different transport block types on a scheduled PDSCH opportunity 730. The PDSCH opportunity 730 may be scheduled by an SPS configuration 910. The SPS configuration 910 may include parameters p 710, K0 712, and K1 714 that define the PDSCH opportunity 730. The SPS configuration 910 may also include a parameter M 912 that specifies a number of PDSCH opportunities in a pattern. The SPS configuration 910 may also include a bitmap 914 of length M, where each bit indicates whether the PDSCH opportunity 730 is a regular opportunity or a rate split opportunity.

[0088] The transmission parameters of the PDSCH opportunity 730 may be indicated by, for example, an activation DCI 720 or a multi-PDSCH DCI 910. The PDSCH opportunity 730 may include a regular opportunity and a rate split opportunity. On a regular opportunity, the UE 104 may receive a first type of TB 930 (e.g., TB-0) according to a first transmission parameter. On a rate split opportunity, the UE 104 may receive a second type of TB 940 (e.g., TB-1 for a public stream) and a third type of TB 950 (e.g., TB-2 for a private stream). The PDSCH opportunity 730 for rate splitting may be associated with two sets of transmission parameters. The activation DCI 720 and / or the multi-PDSCH DCI 910 may need to carry additional information for additional transport blocks. For example, each transport block may include an information set indicating MCS, TDRA, FDRA, redundancy version, and DMRS port. In some specific implementations, the activation DCI 720 and / or the multi-PDSCH DCI 920 may include a parameter M 912 and / or a bitmap 914.

[0089] Fig.101000 is an illustration of using two-level DCI 1010 to schedule different transport block types. The two-level DCI 1010 may include a first-level DCI 1012 and a second-level DCI 1014. The first-level DCI 1012 may provide transmission parameters for up to two types of TBs. For example, the first-level DCI 1012 may indicate transmission parameters for regular occasions (e.g., TB-0) and public messages (e.g., TB-1). The second-level DCI 1014 may be linked to the first-level DCI 1012. For example, the second-level DCI 1014 may be sent on a PDCCH resource defined based on the first-level DCI 1012, so that blind decoding is not necessary. The second-level DCI 1014 may provide additional information, such as transmission parameters for private messages (e.g., TB-2).

[0090] Fig.11 1 is a diagram illustrating an example DCI 1100 for providing transmission parameters for different transport block types. DCI 1100 may be based on DCI format 1_1 and may be used to activate an SPS configuration (e.g., activate DCI 720). In some implementations, DCI format 1_1 may be extended to include the information discussed herein, or a new DCI format may be defined for providing transmission parameters for different transport block types.

[0091] The DCI 1100 may include multiple fields, such as a carrier indicator field 1102, a format identifier field 1104, a BWP indicator field 1106, a FDRA field 1108, a TDRA field 1110, a VRB to PRB mapping field 1112, a PRB bundling size indicator field 1114, a rate matching indicator field 1116, a ZP CSI-RS trigger field 1118, an MCS field 1120, a new data indicator field 1122, a redundancy version field 1124, a HARQ process number field 1126, a downlink allocation index field 1128, a TPC command field 1130, a PUCCH resource indicator field 1132, a PDSCH to HARQ timing indicator field 1134, an antenna port field 1136, a TCI field 1138, an SRS request field 1140, a CBGTI field 1142, a CBGFI field 1144 and / or a DRMS ​​sequence field 1146.

[0092] In some implementations, some fields (e.g., indicated by a vertical line fill pattern) are optional or variable in length, depending on the parameters configured by the higher layers. In some implementations, some fields may be applicable to each type of TB (e.g., indicated by a diagonal fill pattern). The DCI 1100 may include a set of additional TB fields 1150 corresponding to each of the fields applicable to each type of TB. For example, for a rate split scenario with three types of TBs, the FDRA field 1108, the TDRA field 1110, the MCS field 1120, the new data indicator field 1122, the redundant version field 1124, and / or the antenna port field 1136 may be repeated in the additional TB field 1150. In some implementations, different types of TBs may utilize the same transmission parameters, or the transmission parameters may be derived from the parameters configured for other types of TBs. In this case, multiple sets of parameters may not be included in the DCI 1100. For example, the DCI 1100 may have a variable length based on (eg, SPS configuration or L1 / L2 / L3 indication), or the additional TB field 1150 may be padded with zeros.

[0093] In some implementations, regular occasion messages and private messages have different parameters. DCI 1100 may include fields applicable to each type of TB. For example, a first set of fields may apply to TB-0 (e.g., regular occasion messages), a second set of fields may apply to TB-1 (e.g., public messages), and a third set of fields may apply to TB-2 (e.g., private messages).

[0094] In some implementations, the regular occasion message and the private message may have the same parameters, which may allow a reduction in the size of the DCI compared to the previous example. For example, the DCI 1100 may include a first set of fields applicable to TB-0 and TB-2 and a second set of fields applicable to TB-1. In some implementations, an indicator at the SPS configuration 910 or L1 / L2 / L3 may indicate whether the regular occasion message and the private message have the same transmission parameters. On the other hand, the size of the DCI 1100 may be signaled, and which fields may be applicable to which types of TBs may be implied from the size of the DCI 1100.

[0095] In one aspect, rate splitting may be applicable to larger UE groups and / or changing UE groups. In addition, the channel conditions of each UE may change over time. In some implementations, the SPS configuration 910 may indicate a set of transmission parameters associated with each PDSCH opportunity 730 (e.g., by extending the bitmap 914 to use multiple bits for each PDSCH opportunity 730).

[0096] Fig.121 is a message diagram 1200 illustrating example messages between base station 102 and UE 104. UE 104 may be an example of UE 104 including multi-TB decoder component 140. Base station 102 may include multi-TB transmitter component 120.

[0097] In some implementations, the UE 104 can optionally send a capability message 1210 to the base station 102. For example, the capability message 1210 can be an RRC message. The capability message 1210 can indicate, for example, that the UE 104 is capable of decoding using rate splitting.

[0098] Base station 102 may send configuration 1220. Configuration 1220 may be, for example, an RRC message. For example, configuration 1220 may include SPS configuration 910.

[0099] In some implementations, the base station 102 may optionally send an indication 1230. The indication 1230 may provide additional information about the SPS configuration 910 or a DCI for multiple TBs. The indication 1230 may be an RRC message or a MAC-CE. For example, the indication 1230 may indicate a difference between a first transmission parameter for a first type of TB and a second transmission parameter for a second type of TB or a third transmission parameter for a third type of TB. As another example, the indication 1230 may indicate a size of the DCI (e.g., DCI 1100). The indication 1230 may further indicate one or more of a second transmission parameter or a third transmission parameter that is different from the first transmission parameter.

[0100] The base station 102 may transmit the DCI 1100 to activate the SPS configuration 910. The DCI 1100 may include a set 1232 of first transmission parameters, a set 1234 of second transmission parameters, and a set 1236 of third transmission parameters.

[0101] The base station 102 may transmit a PDSCH 1240 on the PDSCH opportunity 730. For example, the PDSCH 1240 may carry a first type of TB 920. The UE 104 may decode the TB 920 using a conventional decoding process and a first set of transmit parameters 1232. The UE 104 may acknowledge the PDSCH 1240 by transmitting a PUCCH 1250.

[0102] The base station 102 may transmit a PDSCH 1260 on another PDSCH opportunity 730. For example, the PDSCH 1260 may carry a second type of TB 940 and a third type of TB 950. The UE 104 may decode the TB 940 and the TB 950 using the rate split decoding process 600 and the second set of transmission parameters 1234 and the third set of transmission parameters 1236. The UE 104 may acknowledge the PDSCH 1260 by transmitting a PUCCH 1270.

[0103] The base station 102 may continue to send the PDSCH according to the mode indicated by the bitmap 914. In some implementations, the base station 102 may send a reactivation DCI 820 to update any of the transmission parameters 1232, 1234, 1236. The base station 102 may send an SPS release DCI 830 to stop the SPS configuration 910.

[0104] Fig.13 13 is a conceptual data flow diagram 1300 illustrating the data flow between different parts / components in an example base station 102, which may be an example of a base station 102 including a multi-TB transmitter component 120. The multi-TB transmitter component 120 may be composed of Figure 3 The memory 376 and the Tx processor 316, the Rx processor 370 and / or the controller / processor 375 of the multi-TB transmitter component 120 can be implemented. For example, the memory 376 can store executable instructions defining the multi-TB transmitter component 120, and the Tx processor 316, the Rx processor 370 and / or the controller / processor 375 can execute these instructions.

[0105] Base station 102 may include a receiver component 1350, which may include, for example, a radio frequency (RF) receiver for receiving signals as described herein. Base station 102 may include a transmitter component 1352, which may include, for example, an RF transmitter for transmitting signals as described herein. In one aspect, receiver component 1350 and transmitter component 1352 may be co-located on a host such as a Figure 3 In the transceiver indicated by Tx / Rx318.

[0106] As about Figure 1 As discussed, multi-TB transmitter component 120 can include DCI transmitter 122, single-TB transmitter 124, and rate splitting transmitter 126. In some implementations, multi-TB transmitter component 120 can include configuration component 1310.

[0107] Receiver component 1350 can receive a UL signal including capability message 1210 or PUCCH 1250 or 1270 from UE 104. Receiver component 1350 can provide capability message 1210 to configuration component 1310. Receiver component 1350 can provide PUCCH to DCI transmitter 122.

[0108] Configuration component 1310 may be configured to send a configuration of multiple PDSCH opportunities including a first PDSCH opportunity and a second PDSCH opportunity. For example, configuration component 1310 may generate SPS configuration 910. For example, configuration component 1310 may determine the SPS configuration for UE 104 based on the downlink scheduling for UE 104. Specifically, if UE 104 is configured to receive a data packet stream, configuration component 1310 may generate SPS configuration 910 to periodically deliver data packets. In some specific implementations, the first PDSCH opportunity is used for a first type of TB (e.g., a conventional TB), and the second PDSCH opportunity is used to perform rate splitting with a second type of TB and a third type of TB. Therefore, the configuration of the second PDSCH opportunity may also be based on downlink scheduling for at least a second UE. That is, configuration component 1310 may identify the time period during which both the first UE and the second UE are to receive data packets, and schedule the second transmission opportunity to use rate splitting during these periods. Configuration component 1310 can output the configuration message to transmitter component 1352 for transmission, eg, as an RRC configuration message.

[0109] The DCI transmitter 122 may be configured to transmit a DCI (e.g., activate DCI 720) indicating at least a first transmission parameter for a first type of transport block for a UE and a second transmission parameter for a second type of transport block for rate splitting with a second UE. For example, the DCI transmitter 122 may receive a configuration of a PDCCH opportunity from the configuration component 1310. The DCI transmitter 122 may receive uplink control information (UCI), which may include, for example, HARQ feedback, a precoding matrix indicator (PMI), a channel quality indicator (CQI), a rank indicator (RI), and / or a layer indicator (LI). The DCI transmitter 122 may determine the transmission parameters for the TB based on the SPS configuration and the UCI. For example, the DCI transmitter 122 may adapt the transmission parameters to the current channel conditions. The DCI transmitter 122 may output the DCI 720 for transmission via the transmitter component 1352.

[0110] The single TB transmitter 124 may be configured to transmit a first transport block of a first type based on a first transmission parameter during a first PDSCH opportunity 730. The single TB transmitter 124 may receive the first transmission parameter from the DCI transmitter 122. The single TB transmitter 124 may receive data for transmission from a higher layer data source. The single TB transmitter 124 may encode the data for transmission according to the first transmission parameter. The single TB transmitter 124 may output a transport block for transmission via a transmitter component 1352.

[0111] The rate split transmitter 126 may be configured to transmit the second type of transport block based on the second transmission parameter and to transmit the third type of transport block based on the third transmission parameter during the second PDSCH opportunity 730. The rate split transmitter 126 may receive the second transmission parameter and the third transmission parameter from the DCI transmitter 122. The rate split transmitter 126 may receive data for transmission from a higher layer data source. The rate split transmitter 126 may transmit a message W1 to the first UE and a message W2 to the second UE, as described above with respect to Figure 5 As discussed. The rate split transmitter 126 can output an encoded transport block (eg, X) for transmission via a transmitter component 1352.

[0112] The various components of base station 102 may be provided for performing the functions described herein (including Fig.16 ) In some examples, a component for sending, outputting, or transmitting (or a component for outputting for sending) may include Figure 3 The transceiver 318TX and / or antenna 320 of the base station 102 shown in FIG. Fig.13 The transmitter component 1352 of the base station 102 in FIG. The means for configuring or indicating may include the Figure 3 Controller / processor 375, memory 376 and various other processors and / or Fig.13 various components.

[0113] In some cases, a device may not actually send, for example, signals and / or data, but may have an interface (components for outputting) for outputting signals and / or data for transmission. For example, a processor may output signals and / or data to an RF front end via a bus interface for transmission. Similarly, a device may not actually receive signals and / or data, but may have an interface (components for obtaining) for obtaining signals and / or data received from another device. For example, a processor may obtain (or receive) signals and / or data from an RF front end via a bus interface for reception. In various aspects, the RF front end may include various components, including, for example, Figure 3 The transmit and receive processors, transmit and receive MIMO processors, modulators, demodulators, etc. depicted in the examples in FIG. 1 are shown in FIG. 1 . Fig.13 are examples, and many other examples and configurations of base station 102 are possible.

[0114] Fig.14 14 is a conceptual data flow diagram 1400 illustrating the flow of data between different parts / components in an example UE 104, which may include a multi-TB decoder component 140. The multi-TB decoder component 140 may be implemented by the memory 360 and the Tx processor 368, the Rx processor 356, and / or the controller / processor 359. For example, the memory 360 may store executable instructions defining the multi-TB decoder component 140, and the Tx processor 368, the Rx processor 356, and / or the controller / processor 359 may execute these instructions.

[0115] UE 104 may include a receiver component 1470, which may include, for example, an RF receiver for receiving signals as described herein. UE 104 may include a transmitter component 1472, which may include, for example, an RF transmitter for transmitting signals as described herein. In one aspect, receiver component 1470 and transmitter component 1472 may be co-located on a host such as a Figure 3 In the Tx / Rx 352 transceiver.

[0116] As about Figure 1 As discussed, the multi-TB decoder component 140 can include a DCI component 142, a single TB decoder 144, and a rate split decoder 146. In some implementations, the multi-TB decoder component 140 can optionally include a capability component 1410 and a configuration component 148.

[0117] Receiver component 1470 may receive DL signals described herein, such as configuration 1220, indication 1230, DCI 1100, PDSCH 1240, and PDSCH 1260. Receiver component 1470 may provide configuration 1220 or indication 1230 to configuration component 148. Receiver component 1470 may provide DCI 1100 to DCI component 142. Receiver component 1470 may provide PDSCH 1240 (or a single TB carried thereon) to single TB decoder 144. Receiver component 1470 may provide PDSCH 1260 (or a TB carried thereon) to rate split decoder 146.

[0118] The configuration component 148 may be configured to receive a configuration of a plurality of PDSCH opportunities including a first PDSCH opportunity and a second PDSCH opportunity. For example, the configuration component 148 may receive the configuration via the receiver component 1470 (and / or via the single TB decoder 144 or the rate split decoder 146 that decodes the RRC message). In some implementations, the configuration is an SPS configuration 910 including a bitmap 914 indicating different types of PDSCH opportunities. The configuration component 148 may provide the SPS configuration including the type of TB associated with each PDSCH opportunity to the DCI component 142.

[0119] The DCI component 142 may be configured to receive a DCI 1100 indicating at least a first transmission parameter for a first type of transport block for a UE and a second transmission parameter for a second type of transport block for rate splitting with a second UE. For example, the DCI 1100 may include a first transmission parameter 1232 and a second transmission parameter 1234. In some implementations, the DCI 1100 may also include a third transmission parameter 1236. In some implementations, the DCI 1100 may include a difference between two sets of transmission parameters or other indications of how to determine the transmission parameter set. The DCI 1100 may activate or reactivate the SPS configuration. The DCI component 142 may determine the first transmission parameter, the second transmission parameter, and / or the third transmission parameter for each PDSCH opportunity 730 based on the SPS configuration and the DCI 1100. The DCI component 142 may output the first transmission parameter, the second transmission parameter, and / or the third transmission parameter to the single TB decoder 144 and / or the rate split decoder 146.

[0120] The single TB decoder 144 may be configured to receive a first type of transport block based on a first transmission parameter during a first PDSCH opportunity. For example, the single TB decoder 144 may receive the first transmission parameter 1232 from the DCI component 142. The single TB decoder 144 may receive a TB received on the PDSCH from the receiver component 1470. The single TB decoder 144 may decode the TB based on the first transmission parameter. The single TB decoder 144 may output a HARQ ACK / NACK on the PUCCH based on whether the decoding is successful and based on the timing of the SPS configuration or the DCI 1100 (e.g., parameter K1 714).

[0121] The rate split decoder 146 may be configured to receive a second type of transport block based on the second transmission parameter and receive a third type of transport block based on the third transmission parameter during the second PDSCH opportunity. For example, the rate split decoder 146 may be configured to perform the above description of Figure 6The decoding process 600 discussed. For example, the rate split decoder 146 may receive the second transmission parameter and the third transmission parameter from the DCI component 142. The rate split decoder 146 may receive the TB from the receiver component 1470. For example, the received signal may include both the second TB and the third TB. The rate split decoder 146 may first decode the second TB (e.g., W c ) is decoded, and then the third TB (for example, W 1，p ) before decoding. In some implementations, the rate split decoder 146 may combine the third TB for the UE with a portion of the second TB. The rate split decoder 146 may output a HARQ ACK / NACK on the PUCCH based on whether the decoding is successful and based on the SPS configuration or the timing of the DCI 1100 (e.g., parameter K1 714).

[0122] In some implementations, the capability component 1410 can be configured to output an indication of the UE's ability to perform rate splitting for transmission. For example, the capability component 1410 can output the RRC capability message 1210 via the transmitter component 1472.

[0123] The various components of base station 102 may be provided for performing the functions described herein (including Fig.15 ) In some examples, a component for sending, outputting, or transmitting (or a component for outputting for sending) may include Figure 3 The transceiver 354TX and / or antenna 352 and / or Fig.14 The transmitter component 1472 of the UE 104 in FIG. 1472 may include Figure 3 controller / processor 359, memory 360 and other various processors, and / or as discussed above Fig.14 various components.

[0124] In some cases, a device may not actually send, for example, signals and / or data, but may have an interface (components for outputting) for outputting signals and / or data for transmission. For example, a processor may output signals and / or data to an RF front end via a bus interface for transmission. Similarly, a device may not actually receive signals and / or data, but may have an interface (components for obtaining) for obtaining signals and / or data received from another device. For example, a processor may obtain (or receive) signals and / or data from an RF front end via a bus interface for reception. In various aspects, the RF front end may include various components, including, for example, Figure 3 The transmit and receive processors, transmit and receive MIMO processors, modulators, demodulators, etc. depicted in the examples in FIG. 1 are shown in FIG. 1 . Fig.14are examples, and many other examples and configurations of UE 104 are possible.

[0125] Fig.15 1 is a flow chart of an example method 1500 for receiving different types of transport blocks by a UE 104. The method 1500 may be performed by a UE 104, such as a UE 104, which may include a memory 360, and may be the entire UE 104 or a component of the UE 104, such as a multi-TB decoder component 140, a Tx processor 368, an Rx processor 356, or a controller / processor 359. The method 1500 may be performed by a multi-TB decoder component 140 in communication with a multi-TB transmitter component 120 of a base station 102. Optional blocks are shown with dashed lines.

[0126] At block 1510, the method 1500 may optionally include receiving a configuration of a plurality of PDSCH opportunities including a first PDSCH opportunity and a second PDSCH opportunity. In some implementations, for example, the UE 104, the Rx processor 356, or the controller / processor 359 may execute the multi-TB decoder component 140 or the configuration component 148 to receive a configuration 1220 of a plurality of PDSCH opportunities 730 including a first PDSCH opportunity and a second PDSCH opportunity. Thus, the UE 104, the Rx processor 356, or the controller / processor 359 executing the multi-TB decoder component 140 or the configuration component 148 may provide a component for receiving a configuration of a plurality of PDSCH opportunities including a first PDSCH opportunity and a second PDSCH opportunity.

[0127] At block 1520, the method 1500 may optionally include receiving an indication of a difference between the first transmit parameter and the second transmit parameter or between the first transmit parameter and the third transmit parameter. In some implementations, for example, the UE 104, the Rx processor 356, or the controller / processor 359 may execute the multi-TB decoder component 140 or the configuration component 148 to receive an indication of a difference between the first transmit parameter and the second transmit parameter or between the first transmit parameter and the third transmit parameter. In some implementations, the configuration includes a bitmap 714 indicating whether each of the plurality of PDSCH opportunities is used for rate splitting and a size 712 of the bitmap. In some implementations, the configuration 1220 is an SPS configuration 910. Thus, the UE 104, the Rx processor 356, or the controller / processor 359 executing the multi-TB decoder component 140 or the configuration component 148 may provide a component for receiving an indication of a difference between the first transmit parameter and the second transmit parameter or between the first transmit parameter and the third transmit parameter.

[0128] At block 1530, method 1500 may optionally include receiving an indication of the size of the first DCI. In some implementations, for example, UE 104, Rx processor 356, or controller / processor 359 may execute multi-TB decoder component 140 or configuration component 148 to receive an indication of the size of the first DCI 1100. For example, the indication may be an RRC message or a MAC-CE. In some implementations, the indication also indicates one or more of a second transmission parameter or a third transmission parameter that is different from the first transmission parameter. Thus, UE 104, Rx processor 356, or controller / processor 359 executing multi-TB decoder component 140 or configuration component 148 may provide a component for receiving an indication of the size of the first DCI.

[0129] At block 1540, the method 1500 includes receiving a DCI indicating at least a first transmission parameter for a first type of transport block for the UE and a second transmission parameter for a second type of transport block for rate splitting with a second UE. In some implementations, for example, the UE 104, the Rx processor 356, or the controller / processor 359 may execute the multi-TB decoder component 140 or the DCI component 142 to receive at least a first transmission parameter 1232 (e.g., fields 1108, 1110, 1120, 1122, 1124, and 1136) for the first type of transport block for the UE and a second transmission parameter 1234 (e.g., additional TB field 1150) for the second type of transport block for rate splitting with the second UE. In some implementations, the DCI 1100 includes the first transmission parameter and the second transmission parameter. In some implementations, the DCI also includes a third transmission parameter for a third type of transport block. In some implementations, the second transmission parameter or the third transmission parameter is based on the first transmission parameter. For example, the second transmission parameter or the third transmission parameter may be based on the difference received in block 1520. Thus, the UE 104, the Rx processor 356, or the controller / processor 359 executing the multi-TB decoder component 140 or the DCI component 142 may provide means for receiving a DCI indicating at least first transmission parameters for a first type of transport block for the UE and second transmission parameters for a second type of transport block for rate splitting with a second UE.

[0130] At block 1550, the method 1500 may optionally include receiving a second DCI having a third transmission parameter. In some implementations, for example, the UE 104, the Rx processor 356, or the controller / processor 359 may execute the multi-TB decoder component 140 or the configuration component 148 to receive a second DCI (e.g., the second-level DCI 1014) having the third transmission parameter 1236. Thus, the UE 104, the Rx processor 356, or the controller / processor 359 executing the multi-TB decoder component 140 or the DCI component 142 may provide a component for receiving a second DCI having a third transmission parameter.

[0131] At block 1560, the method 1500 includes receiving a first type of transport block based on the first transmission parameter during the first PDSCH opportunity. In some implementations, for example, the UE 104, the Rx processor 356, or the controller / processor 359 may execute the multi-TB decoder component 140 or the single TB decoder 144 to receive the first type of transport block (e.g., TB-0) based on the first transmission parameter 1232 during the first PDSCH opportunity 730. Thus, the UE 104, the Rx processor 356, or the controller / processor 359 executing the multi-TB decoder component 140 or the single TB decoder 144 may provide a component for receiving the first type of transport block based on the first transmission parameter during the first PDSCH opportunity.

[0132] At block 1570, the method 1500 includes receiving a second type of transport block based on the second transmission parameter and receiving a third type of transport block based on the third transmission parameter during the second PDSCH opportunity. In some implementations, for example, the UE 104, the Rx processor 356, or the controller / processor 359 may execute the multi-TB decoder component 140 or the rate split decoder 146 to receive a second type of transport block (e.g., TB-1) based on the second transmission parameter 1234 and a third type of transport block (e.g., TB-2) based on the third transmission parameter 1236 during the second PDSCH opportunity 730. Thus, the UE 104, the Rx processor 356, or the controller / processor 359 executing the multi-TB decoder component 140 or the rate split decoder 146 may provide a component for receiving a second type of transport block based on the second transmission parameter and receiving a third type of transport block based on the third transmission parameter during the second PDSCH opportunity.

[0133] At block 1580, the method 1500 may optionally include receiving a second DCI including a fourth transmission parameter for a single transport block of the first type. In some implementations, for example, the UE 104, the Rx processor 356, or the controller / processor 359 may execute the multi-TB decoder component 140 or the DCI component 142 to receive a second DCI including a fourth transmission parameter for a single transport block of the first type. In some implementations, in the case where the DCI format is used for signaling for multiple TBs, the second DCI may be the same size as the first DCI, and the second DCI may be padded (e.g., with zeros) after the fourth transmission parameter. Thus, the UE 104, the Rx processor 356, or the controller / processor 359 executing the multi-TB decoder component 140 or the DCI component 142 may provide a component for receiving a second DCI including a fourth transmission parameter for a single transport block of the first type.

[0134] Fig.16 1 is a flow chart of an example method 1600 for a base station to transmit different types of TBs. The method 1600 may be performed by a base station, such as the base station 102, which may include the memory 376 and which may be the entire base station 102 or a component of the base station 102, such as the multi-TB transmitter component 120, the Tx processor 316, the Rx processor 370, or the controller / processor 375. The method 1600 may be performed by the multi-TB transmitter component 120 in communication with the multi-TB decoder component 140 of the UE 104.

[0135] At block 1610, the method 1600 may optionally include: transmitting a configuration of a plurality of PDSCH opportunities including a first PDSCH opportunity and a second PDSCH opportunity. In some implementations, for example, the base station 102, the Tx processor 316, or the controller / processor 375 may execute the multi-TB transmitter component 120 or the configuration component 1310 to transmit a configuration of a plurality of PDSCH opportunities 730 including a first PDSCH opportunity and a second PDSCH opportunity. Thus, the base station 102, the Tx processor 316, or the controller / processor 375 executing the multi-TB transmitter component 120 or the configuration component 1310 may provide a component for transmitting a configuration of a plurality of PDSCH opportunities including a first PDSCH opportunity and a second PDSCH opportunity.

[0136] At block 1620, the method 1600 may optionally include sending an indication of a difference between the first transmit parameter and the second transmit parameter or the first transmit parameter and the third transmit parameter. In some implementations, for example, the base station 102, the Tx processor 316, or the controller / processor 375 may execute the multi-TB transmitter component 120 or the configuration component 1310 to send an indication of a difference between the first transmit parameter 1232 and the second transmit parameter 1234 or the third transmit parameter 1236. In some implementations, the configuration includes a bitmap 714 indicating whether each of the plurality of PDSCH opportunities is used for rate splitting and a size 712 of the bitmap. In some implementations, the configuration 1220 is an SPS configuration 910. Thus, the base station 102, the Tx processor 316, or the controller / processor 375 executing the multi-TB transmitter component 120 or the configuration component 1310 may provide a component for sending an indication of a difference between the first transmit parameter and the second transmit parameter or the first transmit parameter and the third transmit parameter.

[0137] At block 1630, method 1600 may optionally include sending an indication of the size of the first DCI. In some implementations, for example, the base station 102, Tx processor 316, or controller / processor 375 may execute the multi-TB transmitter component 120 or the configuration component 1310 to send an indication of the size of the first DCI 1100. For example, the indication may be an RRC message or a MAC-CE. In some implementations, the indication also indicates one or more of a second transmission parameter or a third transmission parameter that is different from the first transmission parameter. Thus, the base station 102, Tx processor 316, or controller / processor 375 executing the multi-TB transmitter component 120 or the configuration component 1310 may provide a component for sending an indication of the size of the first DCI.

[0138] At block 1640, the method 1600 includes sending a DCI indicating at least a first transmission parameter for a first type of transport block for the UE and a second transmission parameter for a second type of transport block for rate splitting with a second UE. In some implementations, for example, the base station 102, the Tx processor 316, or the controller / processor 375 may execute the multi-TB transmitter component 120 or the DCI transmitter 122 to send at least a DCI 1100 indicating a first transmission parameter 1232 for a first type of transport block (e.g., TB-0) for the UE 104a and a second transmission parameter 1234 for a second type of transport block (e.g., TB-1) for rate splitting with the second UE 104b. In some implementations, the DCI 1100 includes the first transmission parameter and the second transmission parameter. In some implementations, the DCI also includes a third transmission parameter for a third type of transport block. In some implementations, the second transmission parameter or the third transmission parameter is based on the first transmission parameter. For example, the second transmission parameter or the third transmission parameter may be based on the difference received in block 1520. Thus, the base station 102, Tx processor 316, or controller / processor 375 executing the multi-TB transmitter component 120 or DCI transmitter 122 may provide a component for indicating at least a first transmission parameter for a first type of transport block for a UE and a second transmission parameter for a second type of transport block for rate splitting with a second UE.

[0139] At block 1650, the method 1600 may optionally include transmitting a second DCI having a third transmission parameter. In some implementations, for example, the base station 102, the Tx processor 316, or the controller / processor 375 may execute the multi-TB transmitter component 120 or the DCI transmitter 122 to transmit a second DCI (e.g., the second-level DCI 1014) having the third transmission parameter 1236. Thus, the base station 102, the Tx processor 316, or the controller / processor 375 executing the multi-TB transmitter component 120 or the DCI transmitter 122 may provide a component for transmitting a second DCI having the third transmission parameter.

[0140] At block 1660, the method 1600 includes transmitting a first type of transport block based on a first transmission parameter during a first PDSCH opportunity. In some implementations, for example, the base station 102, the Tx processor 316, or the controller / processor 375 may execute the multi-TB transmitter component 120 or the single TB transmitter 124 to transmit the first type of transport block 920 based on the first transmission parameter 1232 during the first PDSCH opportunity 730. Thus, the base station 102, the Tx processor 316, or the controller / processor 375 executing the multi-TB transmitter component 120 or the single TB transmitter 124 may provide a component for transmitting the first type of transport block based on the first transmission parameter during the first PDSCH opportunity.

[0141] At block 1670, the method 1600 includes transmitting the second type of transport block based on the second transmission parameter and transmitting the third type of transport block based on the third transmission parameter during the second PDSCH opportunity. In some implementations, for example, the base station 102, the Tx processor 316, or the controller / processor 375 may execute the multi-TB transmitter component 120 or the rate splitting transmitter 126 to transmit the second type of transport block 940 based on the second transmission parameter 1234 and transmit the third type of transport block 950 based on the third transmission parameter 1236 during the second PDSCH opportunity 730. Thus, the base station 102, the Tx processor 316, or the controller / processor 375 executing the multi-TB transmitter component 120 or the rate splitting transmitter 126 may provide a component for transmitting the second type of transport block based on the second transmission parameter and transmitting the third type of transport block based on the third transmission parameter during the second PDSCH opportunity.

[0142] At block 1680, the method 1600 may optionally include sending a second DCI including a fourth transmission parameter for a single transport block of the first type. In some implementations, for example, the base station 102, the Tx processor 316, or the controller / processor 375 may execute the multi-TB transmitter component 120 or the DCI transmitter 122 to send a second DCI including a fourth transmission parameter for a single transport block of the first type. In some implementations, where the DCI format is used for signaling for multiple TBs, the second DCI may be the same size as the first DCI, and the second DCI may be padded (e.g., with zeros) after the fourth transmission parameter. Thus, the base station 102, the Tx processor 316, or the controller / processor 375 executing the multi-TB transmitter component 120 or the DCI transmitter 122 may provide a component for sending a second DCI including a fourth transmission parameter for a single transport block of the first type.

[0143] The various illustrative logic components, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the specific implementations disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been generally described in terms of functionality and is exemplified in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0144] The hardware and data processing apparatus for implementing the various illustrative logic components, logic blocks, modules and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed using a general purpose single-chip or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic component, a discrete hardware component or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some specific implementations, specific processes and methods may be performed by circuits specific to a given function.

[0145] In one or more aspects, the functions described may be implemented in hardware, digital electronic circuitry, computer software, firmware, including the structures disclosed in this specification and their structural equivalents, or any combination thereof. Specific implementations of the subject matter described in this specification may also be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, which are encoded on computer storage media for execution by data processing apparatus or to control the operation of data processing apparatus.

[0146] If implemented in software, the function may be stored as one or more instructions or codes on a computer-readable medium or sent via a computer-readable medium. The process of the method or algorithm disclosed herein may be implemented in a processor executable software module that may reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, and communication media include any medium that can realize the transfer of a computer program from one place to another. The storage medium may be any available medium that a computer can access. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, disk storage devices or other magnetic storage devices, or any other medium that can be used to store the desired program code in the form of an instruction or data structure and can be accessed by a computer. In addition, any connection may be appropriately referred to as a computer-readable medium. Disks and optical disks as used herein include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and blue-ray disks, wherein disks generally reproduce data magnetically, and optical disks reproduce data optically with lasers. The above combination should also be included in the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as a code and instruction set, or any combination of code and instruction sets, on a machine-readable medium or computer-readable medium, which may be incorporated into a computer program product.

[0147] Various modifications to the specific implementations described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other specific implementations without departing from the spirit or scope of the disclosure. Therefore, the claims are not intended to be limited to the specific implementations shown herein, but are to be consistent with the broadest scope consistent with the disclosure, the principles and novel features disclosed herein.

[0148] Additionally, one of ordinary skill in the art will readily recognize that the terms "upper" and "lower" are sometimes used for ease of describing the drawings and indicate relative positions corresponding to the orientation of the drawings on a correctly oriented page, and may not reflect the correct orientation of any device as implemented.

[0149] Certain features described in this specification in the context of a single implementation may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented in multiple implementations individually or in any suitable subcombination. Furthermore, while some features are described above as working in a particular combination and even initially claimed as such, in some cases one or more features from a claimed combination may be cut out of the combination, and a claimed combination may involve subcombinations or variations of subcombinations.

[0150] Similarly, although the operations are depicted in a specific order in the figure, this should not be understood as requiring such operations to be performed in the specific order shown or in a sequential order, or to perform all the illustrated operations to achieve the desired result. In addition, the accompanying drawings can schematically depict one or more example processes in the form of a flow chart. However, other operations not depicted can be incorporated into the schematically illustrated example process. For example, one or more additional operations can be performed before, after, at the same time, or between any operations in the illustrated operation. In some environments, multitasking and parallel processing are advantageous. In addition, the separation of various system components in the specific implementation described above should not be understood as requiring such separation in all specific implementations, but it should be understood that the described program components and systems can usually be integrated together in a single software product, or be packaged in multiple software products. In addition, other specific implementations are within the scope of the following claims. In some cases, the actions recorded in the claims can be performed in different orders and still achieve the desired result.

[0151] Example aspects

[0152] 1. A method for wireless communication at a UE, the method comprising:

[0153] receiving downlink control information (DCI) indicating at least first transmission parameters for a first type of transport block for the UE and second transmission parameters for a second type of transport block for rate splitting with a second UE;

[0154] receiving a transport block of the first type based on the first transmit parameter during a first physical downlink shared channel (PDSCH) opportunity; and

[0155] The second type of transport blocks are received based on the second transmission parameters and the third type of transport blocks are received based on third transmission parameters during a second PDSCH opportunity.

[0156] 2. A method as described in clause 1, the method further comprising: receiving a configuration of multiple PDSCH opportunities including the first PDSCH opportunity and the second PDSCH opportunity.

[0157] 3. A method as described in clause 2, wherein the configuration includes a bitmap indicating whether each PDSCH opportunity in the plurality of PDSCH opportunities is used for rate splitting and a size of the bitmap.

[0158] 4. A method according to clause 2 or 3, wherein the configuration is semi-persistent scheduling (SPS)

[0159] configuration, and the DCI is an activation DCI for the SPS configuration.

[0160] 5. A method as described in clause 4, wherein the DCI comprises a bitmap indicating whether each PDSCH opportunity in the plurality of PDSCH opportunities is used for rate splitting.

[0161] 6. A method according to any of clauses 1 to 5, wherein the DCI comprises the first transmission parameter and the second transmission parameter.

[0162] 7. A method according to any of clauses 1 to 6, wherein the DCI further comprises the third transmission parameters for the third type of transport blocks.

[0163] 8. The method of any of clauses 1 to 7, wherein the second transmit parameter or the third transmit parameter is based on the first transmit parameter.

[0164] 9. The method of clause 8, further comprising receiving an indication of a difference between the first transmit parameter and the second transmit parameter or the first transmit parameter and the third transmit parameter.

[0165] 10. A method as described in any of clauses 1 to 9, further comprising: receiving an indication of a size of the first DCI.

[0166] 11. A method according to clause 10, wherein the indication further indicates the first sending parameter

[0167] One or more of the second sending parameters or the third sending parameters having different numbers.

[0168] 12. A method according to any one of clauses 1 to 11, further comprising: receiving a second DCI including a fourth transmission parameter for a single transport block of the first type, the second DCI being the same size as the first DCI, and the second DCI being padded after the fourth transmission parameter.

[0169] 13. A method according to any of clauses 1 to 11, further comprising: receiving a second DCI having the third transmission parameters.

[0170] 14. A method for wireless communication at a base station, the method comprising:

[0171] sending downlink control information (DCI) indicating at least first transmission parameters for a first type of transport block for a first user equipment (UE) and second transmission parameters for a second type of transport block for rate splitting with a second UE;

[0172] transmitting a first transport block of the first type based on the first transmission parameter during a first physical downlink shared channel (PDSCH) opportunity; and

[0173] The second PDSCH opportunity is used to transmit the first transmission parameter based on the second transmission parameter.

[0174] The method includes transmitting a transport block of the second type and transmitting a transport block of the third type based on a third transmission parameter.

[0175] 15. A method as described in clause 14, further comprising: transmitting a configuration of a plurality of PDSCH opportunities including the first PDSCH opportunity and the second PDSCH opportunity.

[0176] 16. A method as described in clause 15, wherein the configuration comprises a bitmap indicating whether each of the plurality of PDSCH opportunities is used for rate splitting and a size of the bitmap.

[0177] 17. A method according to clause 15 or 16, wherein the configuration is a semi-persistent scheduling (SPS) configuration and the DCI is an activation DCI for the SPS configuration.

[0178] 18. A method as described in clause 17, wherein the DCI comprises a bitmap indicating whether each PDSCH opportunity of the plurality of PDSCH opportunities is used for rate splitting.

[0179] 19. A method as described in any of clauses 14 to 18, wherein the DCI comprises the first transmit parameter and the second transmit parameter.

[0180] 20. A method according to any of clauses 14 to 19, wherein the DCI further comprises the third transmission parameters for the third type of transport blocks.

[0181] 21. A method according to any of clauses 14 to 20, wherein the second send parameter or the third send parameter is based on the first send parameter.

[0182] 22. The method of clause 21, further comprising sending an indication of a difference between the first transmit parameter and the second transmit parameter or the first transmit parameter and the third transmit parameter.

[0183] 23. A method as described in any of clauses 14 to 22, further comprising sending an indication of the size of the first DCI.

[0184] 24. A method according to clause 23, wherein the indication further indicates the first sending parameter

[0185] One or more of the second sending parameters or the third sending parameters having different numbers.

[0186] 25. A method according to any one of clauses 14 to 24, the method further comprising: sending a second DCI including a fourth transmission parameter for a single transport block of the first type, wherein the second DCI is the same size as the first DCI and the second DCI is padded after the fourth transmission parameter.

[0187] 26. A method as described in any of clauses 14 to 24, further comprising sending a second DCI with the third transmission parameters.

[0188] 27. An apparatus for wireless communication, the apparatus comprising: a memory storing computer executable instructions; and a processor configured to execute the instructions and cause the apparatus to perform a method according to any one of clauses 1 to 13.

[0189] 28. An apparatus for wireless communication, the apparatus comprising: a memory storing computer executable instructions; and a processor configured to execute the instructions and cause the apparatus to perform the method according to any one of clauses 14 to 26.

[0190] 29. A user equipment (UE) comprising: a transceiver; a memory storing computer executable instructions; and a processor configured to execute the instructions and cause the UE to perform a method according to any one of clauses 1 to 13.

[0191] 30. A base station comprising: a transceiver; a memory storing computer executable instructions; and a processor configured to execute the instructions and cause the base station to perform the method according to any of clauses 14 to 26.

[0192] 31. An apparatus for wireless communication, the apparatus comprising means for performing a method according to any of clauses 1 to 13.

[0193] 32. An apparatus for wireless communication, the apparatus comprising means for performing the method of any of clauses 14 to 26.

[0194] 33. A non-transitory computer-readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform the method of any one of clauses 1 to 13.

[0195] 34. A non-transitory computer-readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform the method of any one of clauses 14 to 26.

[0196] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but to conform to the full scope consistent with the language claims, wherein the elements mentioned in the singular are not intended to represent "one and only one", unless specifically so stated, but "one or more". The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specifically stated, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof", including any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are or later will be known to one of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims. Words such as "module," "mechanism," "element," "device," etc. cannot replace the word "component." Therefore, no claim element will be understood to be a part plus function unless the element is explicitly stated using the phrase "component for..."

Claims

1. A method for wireless communication at a UE, the method comprising: receiving downlink control information (DCI) indicating at least first transmission parameters for a first type of transport block for the UE and second transmission parameters for a second type of transport block for rate splitting with a second UE; receiving a transport block of the first type based on the first transmit parameter during a first physical downlink shared channel (PDSCH) opportunity; as well as The second type of transport blocks are received based on the second transmission parameters and the third type of transport blocks are received based on third transmission parameters during a second PDSCH opportunity.

2. The method according to claim 1, further comprising: A configuration of a plurality of PDSCH opportunities including the first PDSCH opportunity and the second PDSCH opportunity is received. 3 . The method of claim 2 , wherein the configuration comprises a bitmap indicating whether each of the plurality of PDSCH opportunities is used for rate splitting and a size of the bitmap. 4 . The method of claim 2 , wherein the configuration is a semi-persistent scheduling (SPS) configuration, and the DCI is an activation DCI for the SPS configuration. 5 . The method of claim 4 , wherein the DCI comprises a bitmap indicating whether each of the plurality of PDSCH opportunities is used for rate splitting. The method according to claim 1 , wherein the DCI comprises the first transmission parameter and the second transmission parameter.

7. The method of claim 1, wherein the DCI further comprises the third transmission parameter for the third type of transport block. The method according to claim 1 , wherein the second transmission parameter or the third transmission parameter is based on the first transmission parameter.

9. The method according to claim 8, further comprising: An indication of a difference between the first transmit parameter and the second transmit parameter or the first transmit parameter and the third transmit parameter is received.

10. The method according to claim 1, further comprising: An indication of a size of the first DCI is received.

11. The method of claim 10, wherein the indication further indicates one or more of the second transmission parameter or the third transmission parameter that is different from the first transmission parameter.

12. The method according to claim 1, further comprising: A second DCI including fourth transmission parameters for a single transport block of the first type is received, the second DCI being the same size as the first DCI and being padded after the fourth transmission parameters.

13. The method according to claim 1, further comprising: A second DCI having the third transmission parameters is received.

14. A method for wireless communication at a base station, the method comprising: sending downlink control information (DCI) indicating at least first transmission parameters for a first type of transport block for a first user equipment (UE) and second transmission parameters for a second type of transport block for rate splitting with a second UE; transmitting a first transport block of the first type based on the first transmission parameter during a first physical downlink shared channel (PDSCH) opportunity; as well as The second type of transport blocks are transmitted based on the second transmission parameters and the third type of transport blocks are transmitted based on third transmission parameters during a second PDSCH opportunity.

15. The method according to claim 14, further comprising: A configuration of a plurality of PDSCH opportunities including the first PDSCH opportunity and the second PDSCH opportunity is transmitted. 16 . The method of claim 15 , wherein the configuration comprises a bitmap indicating whether each of the plurality of PDSCH opportunities is used for rate splitting and a size of the bitmap.

17. The method of claim 15, wherein the configuration is a semi-persistent scheduling (SPS) configuration, and the DCI is an activation DCI for the SPS configuration.

18. The method of claim 17, wherein the DCI comprises a bitmap indicating whether each of the plurality of PDSCH opportunities is used for rate splitting. The method of claim 14 , wherein the DCI comprises the first transmission parameter and the second transmission parameter.

20. The method of claim 14, wherein the DCI further comprises the third transmission parameters for the third type of transport blocks.

21. The method of claim 14, wherein the second transmission parameter or the third transmission parameter is based on the first transmission parameter.

22. The method according to claim 21, further comprising: An indication of a difference between the first transmit parameter and the second transmit parameter or the first transmit parameter and the third transmit parameter is transmitted.

23. The method of claim 14, further comprising sending an indication of a size of the first DCI.

24. The method of claim 23, wherein the indication further indicates one or more of the second transmission parameter or the third transmission parameter that is different from the first transmission parameter.

25. The method according to claim 14, further comprising: A second DCI including a fourth transmission parameter for the single transport block of the first type is transmitted, wherein the second DCI has the same size as the first DCI and is padded after the fourth transmission parameter.

26. The method of claim 14, further comprising: Send a second DCI with the third transmission parameters.

27. A user equipment (UE), the user equipment (UE) comprising: Transceiver; a memory storing computer executable instructions; and a processor configured to execute the instructions and cause the UE to: receiving, via the transceiver, downlink control information (DCI), the downlink control information (DCI) indicating at least first transmission parameters for a first type of transport block for the UE and second transmission parameters for a second type of transport block for rate splitting with a second UE; receiving, via the transceiver, a transport block of the first type based on the first transmit parameter during a first physical downlink shared channel (PDSCH) opportunity; as well as The second type of transport blocks are received via the transceiver during a second PDSCH opportunity based on the second transmission parameters and a third type of transport blocks are received based on third transmission parameters.

28. The UE of claim 27, wherein the at least one processor is configured to receive, via the transceiver, a configuration of multiple PDSCH opportunities including the first PDSCH opportunity and the second PDSCH opportunity, wherein the configuration includes a bitmap indicating whether each of the multiple PDSCH opportunities is used for rate splitting and a size of the bitmap.

29. The UE of claim 27, wherein the DCI further comprises the third transmission parameter for the third type of transport block.

30. A base station, comprising: Transceiver; a memory storing computer executable instructions; and a processor configured to execute the instructions and cause the base station to: sending downlink control information (DCI) indicating at least first transmission parameters for a first type of transport block for a first user equipment (UE) and second transmission parameters for a second type of transport block for rate splitting with a second UE; transmitting a first transport block of the first type based on the first transmission parameter during a first physical downlink shared channel (PDSCH) opportunity; as well as The second type of transport blocks are transmitted based on the second transmission parameters and the third type of transport blocks are transmitted based on third transmission parameters during a second PDSCH opportunity.

Images