Signaling framework for rate splitting

Abstract

Methods, systems, and devices are described for wireless communication at a first user equipment (UE). For example, a first UE may receive one or more control signaling messages including a first scheduling parameter for a common codeword associated with downlink data for the first UE and downlink data for a second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE. The first UE may receive a physical downlink shared channel message that includes a common codeword mapped to one or more first layers of the physical downlink shared channel message and a private codeword mapped to one or more second layers of the physical downlink shared channel message. Additionally or alternatively, the first UE may receive a first physical downlink shared channel message including a common codeword and a second physical downlink shared channel message including a private codeword.

Description

Cross-references

[0001] This patent application claims priority to U.S. patent application No. 17 / 833,264, entitled “SIGNALING FRAMEWORK FOR RATE SPLITTING,” filed by Khoshnevisan et al. on June 6, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0002] The following relates to wireless communications, and in particular to a signaling framework supporting rate splitting for a user equipment (UE). Background Art

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication for a communication device, which may be referred to as a user equipment (UE).

[0004] During wireless communication, a rate splitting technique may be used, wherein a message to be sent to a UE may be divided into at least a private portion and a public portion. The public portion may be combined with other such public portions of other messages to be sent to other UEs, and the combined public portion may be sent to a group of UEs including the UE in a public codeword. The private portion may be sent to the UE in a private codeword. However, some control signaling frameworks may not accommodate such communication schemes, or these communication schemes may not be very effective. Summary of the invention

[0005] 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.

[0006] An innovative aspect of the subject matter described in the present disclosure can be implemented in a method for wireless communication. The method may include: receiving one or more control signaling messages, the one or more control signaling messages including: one or more first scheduling parameters for a common codeword associated with downlink data for a first UE and downlink data for a second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE; and receiving a physical downlink shared channel message based on the one or more first scheduling parameters and the one or more second scheduling parameters, the physical downlink shared channel message including the common codeword mapped to one or more first layers of the physical downlink shared channel message and the private codeword mapped to one or more second layers of the physical downlink shared channel message.

[0007] An innovative aspect of the subject matter described in the present disclosure can be implemented in a device for wireless communication. An apparatus for wireless communication at a first UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: receive one or more control signaling messages, the one or more control signaling messages including: one or more first scheduling parameters for a common codeword associated with downlink data for a first UE and downlink data for a second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE; and receive a physical downlink shared channel message based on the one or more first scheduling parameters and the one or more second scheduling parameters, the physical downlink shared channel message including the common codeword mapped to one or more first layers of the physical downlink shared channel message and the private codeword mapped to one or more second layers of the physical downlink shared channel message.

[0008] Another innovative aspect of the subject matter described in the present disclosure can be implemented in an apparatus for wireless communication at a first UE. The apparatus may include: a component for receiving one or more control signaling messages, the one or more control signaling messages including: a component for one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for the second UE, and a component for one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE; and a component for receiving a physical downlink shared channel message based on the one or more first scheduling parameters and the one or more second scheduling parameters, the physical downlink shared channel message including the common codeword mapped to one or more first layers of the physical downlink shared channel message and the private codeword mapped to one or more second layers of the physical downlink shared channel message.

[0009] Another innovative aspect of the subject matter described in the present disclosure can be implemented in a non-transitory computer-readable medium storing code for wireless communication at a first UE. The code may include instructions executable by a processor to perform the following operations: receiving one or more control signaling messages, the one or more control signaling messages including: one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for the second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE; and receiving a physical downlink shared channel message based on the one or more first scheduling parameters and the one or more second scheduling parameters, the physical downlink shared channel message including the common codeword mapped to one or more first layers of the physical downlink shared channel message and the private codeword mapped to one or more second layers of the physical downlink shared channel message.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, one or more first scheduling parameters include a first modulation and coding scheme associated with a public codeword, one or more second scheduling parameters include a second modulation and coding scheme associated with a private codeword, and a first modulation and coding scheme index value associated with the first modulation and coding scheme may be less than a second modulation and coding scheme index value associated with the second modulation and coding scheme.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the number of one or more first layers of physical downlink shared channel messages may be less than the number of one or more second layers of physical downlink shared channel messages.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a first control signaling message in one or more control signaling messages includes one or more fields having one or more values ​​indicating that a common codeword may be mapped to one or more first layers of a physical downlink shared channel message, a private codeword may be mapped to one or more second layers of a physical downlink shared channel message, or both.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more fields include a second value indicating that the common codeword and the private codeword can be received in the physical downlink shared channel message.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, one or more control signaling messages include a first control signaling message that schedules the transmission of a common codeword and a second control signaling message that schedules the transmission of a private codeword, and the first control signaling message may be a group common control signaling message for a set of multiple UEs including the UE, and the second control signaling message may be for the first UE.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first control signaling message includes common parameters for the first UE and the second UE, common parameters for a common codeword and a private codeword, or both.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second control signaling message includes one or more parameters that may be associated with the private codeword and specific to the first UE.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second control signaling message omits one or more parameters included in the first control signaling message that may be associated with both the public codeword and the private codeword.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, one or more first scheduling parameters, one or more second scheduling parameters, or both include a modulation and coding scheme, a new data indicator, a redundancy version, one or more demodulated signal reference ports, a frequency domain resource allocation, a time domain resource allocation, a hybrid automatic repeat request identifier, or any combination thereof.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, downlink data for a first UE includes a first portion of one or more downlink messages for the first UE, and additional downlink data for the first UE includes a second portion of one or more downlink messages for the first UE, and a bit allocation between the first portion and the second portion may be based on a first channel quality associated with a public codeword and a second channel quality associated with a private codeword.

[0020] Another innovative aspect of the subject matter described in the present disclosure can be implemented in a method for wireless communication at a first UE. The method may include: receiving one or more control signaling messages, the one or more control signaling messages including one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for a second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE; receiving a first physical downlink shared channel message including the common codeword in a first time and frequency resource set based on the one or more first scheduling parameters; and receiving a second physical downlink shared channel message including the private codeword in a second time and frequency resource set that at least partially overlaps with the first time and frequency resource set based on the one or more second scheduling parameters.

[0021] Another innovative aspect of the subject matter described in the present disclosure can be implemented in a device for wireless communication at a first UE. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions can be executed by the processor to cause the device to: receive one or more control signaling messages, the one or more control signaling messages including one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for the second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE; based on the one or more first scheduling parameters, receive a first physical downlink shared channel message including the common codeword in a first time and frequency resource set; and based on the one or more second scheduling parameters, receive a second physical downlink shared channel message including the private codeword in a second time and frequency resource set that at least partially overlaps with the first time and frequency resource set.

[0022] Another innovative aspect of the subject matter described in the present disclosure can be implemented in an apparatus for wireless communication at a first UE. The apparatus may include: a component for receiving one or more control signaling messages, the one or more control signaling messages including one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for a second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE; a component for receiving a first physical downlink shared channel message including the common codeword in a first time and frequency resource set based on the one or more first scheduling parameters; and a component for receiving a second physical downlink shared channel message including the private codeword in a second time and frequency resource set that at least partially overlaps with the first time and frequency resource set based on the one or more second scheduling parameters.

[0023] Another innovative aspect of the subject matter described in the present disclosure can be implemented in a non-transitory computer-readable medium storing code for wireless communication at a first UE. The code may include instructions executable by a processor to perform the following operations: receiving one or more control signaling messages, the one or more control signaling messages including one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for a second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE; based on the one or more first scheduling parameters, receiving a first physical downlink shared channel message including the common codeword in a first time and frequency resource set; and based on the one or more second scheduling parameters, receiving a second physical downlink shared channel message including the private codeword in a second time and frequency resource set that at least partially overlaps with the first time and frequency resource set.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more control signaling messages include a first control signaling message scheduling transmission of a common codeword and a second control signaling message scheduling transmission of a private codeword.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a first control signaling message may be in a first control resource set associated with a first control resource set pool index value, and a second control signaling message may be in a second control resource set associated with a second control resource set pool index value.

[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing an interference cancellation procedure, the interference cancellation procedure comprising: decoding a common codeword, subtracting a portion of the combined signal corresponding to the common codeword from a combined signal comprising the common codeword and the private codeword, and decoding the private codeword based on a remaining portion of the combined signal corresponding to the private codeword, and wherein receiving a first physical downlink shared channel message, a second physical downlink shared channel message, or both can be based on the interference cancellation procedure.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second control signaling message includes a field having a first value indicating that the first UE can receive the common codeword through a first set of time and frequency resources.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first control signaling message includes a field having a first value indicating that the first UE can receive the private codeword through the second set of time and frequency resources.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a first control signaling message schedules the sending of a first physical downlink shared channel message, and a second control signaling message schedules the sending of a second physical downlink shared channel message, and the methods, apparatus, and non-transitory computer-readable media may also include operations, features, components, or instructions for jointly processing the first physical downlink shared channel message and the second physical downlink shared channel message based on one or more first scheduling parameters and one or more second scheduling parameters being common.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first set of time and frequency resources completely overlaps with the second set of time and frequency resources.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first control signaling message may be a group common control signaling message, and the second control signaling message may be for the first UE.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, downlink data for a UE includes a first portion of one or more downlink messages for the UE, and additional downlink data for the UE includes a second portion of one or more downlink messages for the UE, and a bit allocation between the first portion and the second portion may be based on a first channel quality associated with a public codeword and a second channel quality associated with a private codeword. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 An example of a wireless communication system supporting a signaling framework for rate splitting according to one or more aspects of the present disclosure is illustrated.

[0034] Figure 2A and Figure 2B Examples of a rate splitting transmission scheme and a rate splitting reception scheme supporting a signaling framework for rate splitting according to one or more aspects of the present disclosure are illustrated.

[0035] Figure 3 An example of a wireless communication system supporting a signaling framework for rate splitting according to one or more aspects of the present disclosure is illustrated.

[0036] Figure 4 An example of a wireless communication system supporting a signaling framework for rate splitting according to one or more aspects of the present disclosure is illustrated.

[0037] Figure 5 An example of a process flow supporting a signaling framework for rate splitting in accordance with one or more aspects of the present disclosure is illustrated.

[0038] Figure 6 An example of a process flow supporting a signaling framework for rate splitting in accordance with one or more aspects of the present disclosure is illustrated.

[0039] Figure 7 and Figure 8 A block diagram of a device supporting a signaling framework for rate splitting according to one or more aspects of the present disclosure is shown.

[0040] Fig. 9 A block diagram of a communications manager supporting a signaling framework for rate splitting is shown in accordance with one or more aspects of the present disclosure.

[0041] Fig.10 A diagram of a system including a device supporting a signaling framework for rate splitting is shown in accordance with one or more aspects of the present disclosure.

[0042] Fig.11 and Fig.12 A flow chart illustrating a method of supporting a signaling framework for rate splitting according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0043] In wireless communications, rate splitting techniques can be used to improve the characteristics of channels (such as broadcast channels), including increasing the number of degrees of freedom and capacity of wireless channels used for communication, among other aspects. In such methods, messages sent to individual user equipment (UEs) can be split into a "public" part and a "private" part (e.g., a public codeword (CW) and a private CW). The public parts of the messages sent to the individual UEs can be combined in a single public codeword, and each of the private parts can be kept separate from each other in a corresponding private CW (e.g., on a per-UE basis). The public CW can be sent to multiple UEs, and each private CW can be sent to an associated UE in the multiple UEs, respectively, so that each UE can receive all corresponding messages (including at least the public CW and the corresponding private CW). However, some control signaling frameworks may not be adapted to such communication schemes and communication schemes that require improvement.

[0044] Various aspects generally relate to rate splitting techniques, and more specifically to a control signaling framework for rate splitting. To support rate splitting, the network may send one or more downlink messages (e.g., physical downlink shared channel (PDSCH) messages) including a private CW and a public CW, each carrying a different portion of a message sent to a UE. In some examples, the network entity may allocate information of the message between the private CW and the public CW based on the channel conditions over which the private CW and the public CW are sent. For example, different downlink messages or different spatial layers of the same downlink message may be subject to different conditions, and it may be advantageous to allocate more or less information to the private CW or the public CW. In some examples, a single downlink message may carry both a private CW and a public CW. In some such examples, the private CW may be mapped to one or more first layers of the downlink message, and the public CW may be mapped to one or more second layers of the same downlink message. In other examples, each of the private CW and the public CW may be carried by a separate corresponding downlink message (e.g., a corresponding PDSCH). In either case, the network entity may send one or more control signaling messages (e.g., downlink control information (DCI) messages) indicating scheduling parameters for the private CW and the public CW. In some examples, the network entity may send a single control signaling message that may schedule or indicate both the private CW and the public CW. In methods utilizing multiple control signaling messages, different control signaling messages may schedule or indicate the private CW and the public CW separately. The control signaling message that schedules or indicates the public CW may be sent to multiple UEs (e.g., UEs to which data in the public CW is to be sent), and the control signaling message that schedules or indicates the private CW may be sent to the UE. In some examples, the control signaling message may indicate the presence of another CW to be sent (e.g., control signaling carrying a private CW may indicate that the corresponding public CW is also sent or will be sent, or vice versa), so that the UE can properly decode the CW and receive the data. In addition, the various control signaling methods described herein may use new or modified control signaling formats (e.g., DCI formats) that may be customized for use in rate splitting scenarios. For example, some control signaling formats described herein may include a reduced or modified number of parameters, or may include one or more new fields to be included in the control signaling.Finally, implementing the use of rate splitting may allow a UE to perform continuous interference cancellation using private CWs and common CWs.

[0045] Certain aspects of the subject matter described in the present disclosure may be implemented to achieve one or more of the following potential advantages. The techniques employed by the described communication devices may provide benefits and enhancements, including coordination of rate splitting techniques, which increase the freedom and capacity of the wireless communication network by dynamically allocating message information between public CWs and private CWs using different channel conditions. For example, by providing control signaling that enables the use of rate splitting, the wireless communication system may allocate more information to private CWs or public CWs to utilize better channel conditions of one CW relative to another CW, thereby increasing the freedom and capacity available to the wireless communication system. Additional benefits or enhancements may include reduced control signaling overhead and increased control signaling capabilities. For example, by using a modified or reduced control signaling format, control signaling overhead may be reduced because less control signaling information may be sent in one or more control signaling messages. Additionally or alternatively, the control signaling format may include one or more new fields that may indicate the presence or identification of a private CW, a public CW, or both. This functionality is not available in some current wireless communication systems. Finally, such an approach to a control signaling framework for rate splitting further provides improved transmission quality since the receiving UE may perform a continuous interference cancellation procedure on the received CWs, among other benefits.

[0046] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are then described with respect to a rate splitting scheme, a wireless communication system, and a process flow. Aspects of the present disclosure are further illustrated by and described with reference to device diagrams, system diagrams, and flow diagrams relating to a signaling framework for rate splitting.

[0047] Figure 1 An example of a wireless communication system 100 supporting a signaling framework for rate splitting according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0048] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100 and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other names. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which the network entity 105 and the UE 115 may support signal communications in accordance with one or more radio access technologies (RATs).

[0049] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1 . The UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

[0050] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0051] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0052] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next generation NodeB, or a giga NodeB (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a Home NodeB, a Home eNodeB, or other suitable terminology). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in a converged (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0053] In some examples, the network entity 105 can be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that can be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 can include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0054] The split of functionality between CU 160, DU 165, and RU 170 is flexible and may support different functionality depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, and RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between the CU 160 and the DU 165 or between the DU 165 and the RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of the CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by the other of the CU 160, DU 165, or RU 170). The CU 160 may be further functionally split into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. The CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and the DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to an interface (eg, a channel) between layers of a protocol stack supported by respective network entities 105 communicating over such communication links.

[0055] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to the core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as host entities or IAB hosts. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a host network entity 105 (e.g., a host base station 140). One or more host network entities 105 (e.g., IAB hosts) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by the DU 165 of the coupled IAB host. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0056] For example, an access network (AN) or RAN may include an access node (e.g., an IAB host), communications between an IAB node 104, and one or more UEs 115. The IAB host may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB host may refer to a RAN node that has a wired or wireless connection to the core network 130. The IAB host may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB host and the IAB node 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of part of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB hosts) via an Xn-C interface (which may be an example of part of a backhaul link).

[0057] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB host may be referred to as a parent node that communicates with one or more child nodes (e.g., an IAB host may relay transmissions for UEs through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104 , and a DU interface (eg, DU 165 ) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115 .

[0058] For example, the IAB node 104 may be referred to as a parent node that supports communications for a child IAB node, or as a child IAB node associated with an IAB host, or both. The IAB host may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB host may relay transmission to the UE 115 through the IAB node 104, or may directly signal the transmission to the UE 115, or both. The CU 160 of the IAB host may signal the establishment of a communication link to the IAB node 104 via the F1 interface, and the IAB node 104 may schedule transmission (e.g., transmission relayed from the IAB host to the UE 115) via the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling via the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB host, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0059] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the signaling framework for rate splitting as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0060] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where "device" may also be referred to as a unit, a station, a terminal, or a client, among other examples. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, among other examples, which may be implemented in various objects such as appliances or vehicles, meters, among other examples.

[0061] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 shown.

[0062] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a collection of RF spectrum resources having a defined physical layer structure for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between the device and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "sending," "receiving," or "communicating" when referring to the network entity 105 may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0063] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

[0064] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry either downlink or uplink communications (e.g., in an FDD mode), or may be configured to carry both downlink and uplink communications (e.g., in a TDD mode).

[0065] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers for a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., the network entity 105, the UE 115, or both) may have a hardware configuration that supports communication using a particular carrier bandwidth, or may be configured to support communication using one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0066] The signal waveform transmitted via the carrier may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity of communications with UE 115.

[0067] One or more parameter sets for a carrier may be supported, and a parameter set may include a subcarrier spacing ( ) and cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0068] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, a sampling period. seconds, of which may indicate the supported subcarrier spacing, and The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames, each having a specific duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0069] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into multiple time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include multiple symbol periods (e.g., depending on the length of a cyclic prefix added before each symbol period). In some wireless communication systems 100, a time slot may be further divided into multiple mini-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0070] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in the form of a burst of shortened TTIs (sTTIs)).

[0071] According to various techniques, physical channels may be multiplexed using carriers for communication. For example, physical control channels and physical data channels may be multiplexed for signaling via downlink carriers using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a group of UEs 115. For example, one or more of the UEs 115 may monitor or search the control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level for a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0072] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., using a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other) used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors (such as the capabilities of the network entity 105), such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0073] A macro cell typically covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access to a UE 115 with a service subscription to a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) than a macro cell, and the small cell may operate using the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to a UE 115 with a service subscription to a network provider, or may provide restricted access to a UE 115 associated with a small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

[0074] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0075] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0076] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and in some examples, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operation.

[0077] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0078] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not support transmission and reception concurrently). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for UEs 115 include entering a power saving deep sleep mode when not engaged in active communications, operating using limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a subcarrier or resource block (RB) set) within a carrier, within a guard band of a carrier, or outside a carrier.

[0079] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). The UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communications may include private communications or group communications and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety applications or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency are used interchangeably herein.

[0080] In some examples, a UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support various aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be conducted between UEs 115 without involving network entity 105.

[0081] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these items. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU170) using vehicle-to-network (V2N) communication, or both.

[0082] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), and the EPC or 5GC may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) that manages access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) that routes packets or interconnects to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for UEs 115 served by network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0083] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). In general, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the length of the wavelengths ranges from about one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide service to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to communications using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0084] The wireless communication system 100 may also operate using a super high frequency (SHF) region (also known as a centimeter band) that may be in the range of 3 GHz to 30 GHz, or an extremely high frequency (EHF) region (also known as a millimeter band) of the spectrum (e.g., from 30 GHz to 300 GHz). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between a UE 115 and a network entity 105 (e.g., a base station 140, a RU 170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, such technology may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be subject to even greater attenuation and shorter distances than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0085] The wireless communication system 100 may utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology using unlicensed bands (such as the 5 GHz industrial, scientific, and medical (ISM) band). When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration combined with component carriers operating using licensed bands (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0086] A network entity 105 (e.g., a base station 140, RU 170) or a UE 115 may be equipped with multiple antennas that may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or the UE 115 may be located within one or more antenna arrays or antenna panels that may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographic locations. The network entity 105 may include an antenna array having a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0087] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and increase spectral efficiency by sending or receiving multiple signals via different spatial layers. Such technology may be referred to as spatial multiplexing. Multiple signals may be, for example, sent by a transmitting device via different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO) in which multiple spatial layers are sent to the same receiving device, and multi-user MIMO (MU-MIMO) in which multiple spatial layers are sent to multiple devices.

[0088] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each antenna element may be defined by a set of beamforming weights associated with a particular orientation (e.g., for an antenna array of a transmitting device or a receiving device, or for some other orientation).

[0089] The network entity 105 or the UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify beam directions (e.g., by a transmitting device (such as the network entity 105) or by a receiving device (such as the UE 115)) for later transmission or reception by the network entity 105.

[0090] Some signals, such as data signals associated with a particular receiving device, may be transmitted by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115)). In some examples, a beam direction associated with transmission along a single beam direction may be determined based on signals transmitted along one or more beam directions. For example, UE 115 may receive one or more of the signals transmitted by network entity 105 along different directions and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0091] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or non-precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0092] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0093] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate via logical channels. The MAC layer may perform priority processing and multiplexing of logical channels to transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between the UE 115 and the network entity 105 or the core network 130. The PHY layer may map a transport channel to a physical channel.

[0094] UE 115 and network entity 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data via a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve the throughput of the MAC layer in poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0095] In some implementations, the network entity 105 may send control signaling to the UE 115 that may schedule the transmission of a private CW (p-CW) and a common CW (c-CW). In some examples, the p-CW and the c-CW may be scheduled to be transmitted on different spatial layers of a PDSCH transmission, and the scheduling may be done with a single control signaling message or with multiple control signaling messages (e.g., one control signaling message for the p-CW and another control signaling message for the c-CW). In other examples, the p-CW and the c-CW may be scheduled to be transmitted on separate PDSCH transmissions that may at least partially overlap in time, frequency, or both. In some examples, the control signaling message may include a field for indicating the presence of a p-CW, a c-CW, or both.

[0096] Figure 2A and Figure 2BAn example of a rate splitting transmission scheme 200 and a rate splitting reception scheme 201 that support a signaling framework for rate splitting according to one or more aspects of the present disclosure is illustrated. In wireless communications, rate splitting techniques can be used to improve the characteristics of a communication channel, including the degrees of freedom and capacity of a wireless channel. In such methods, messages sent to various UEs can be split into a "public" part and a "private" part. The public parts of the messages for various UEs can be combined in a single common codeword (CW), and each of the private parts can be kept separate in a corresponding private CW (e.g., on a per-UE basis). The public CW can be sent to multiple UEs, and each private CW can be sent to each of the multiple UEs, respectively, so that each UE can receive all of their corresponding messages.

[0097] For example, Figure 2A As depicted in FIG. 1 , UE 115-a and UE 115-b may each have messages that they want to receive, which are depicted as W1 and W2. Each of messages W1 and W2 may be split via message splitting 205-a and message splitting 205-b, respectively, thereby producing W messages representing portions of the message corresponding to the p-CW for UE 115-a. 1,p and W representing the portion of the message corresponding to c-CW 1,c Similar splitting of W2 produces W representing the portion of the message corresponding to the p-CW for UE 115-b. 2,p and W representing the portion of the message corresponding to the public codeword 2,c The split between private messages or codewords and public messages or codewords may be determined or selected based on one or more characteristics of a channel, one or more wireless devices, or any combination thereof. The combiner 210 may combine W 1,c and W 2,c , resulting in W which may have one or more layers c .W 1,p , W c and W 2,p Each of the CWs X1, X2, and X3 may be encoded by encoder 215-a, encoder 215-b, and encoder 215-c, respectively, to generate separate CWs X1, X2, and X3. c In some examples, encoder 215 may include one or more additional operations, including modulation, layer mapping, other operations, or any combination thereof. c X1 and X2 may be processed by pre-decoding 220 to produce H1 for UE 115-a and H2 for UE 115-b. In this manner, each UE receives the private portion of its message that is sent only to that UE, while also receiving the common portion of the message that is sent to both UE 115-a and UE 115-b.

[0098] exist Figure 2B , an example reception scheme for rate splitting is depicted. A UE may receive a transmission (e.g., H1 or H2) destined for the UE, and the UE may first decode the common message. The common message may be decoded for a variety of purposes. First, a portion of the individual message for each UE (W 1,c and W 2,c ) can be embedded in the public message W c In the example, the public message is data intended for the UE. Second, the private message can be decoded using successive interference cancellation or joint demodulation / decoding.

[0099] For example, the UE may estimate the number of packets corresponding to a common flow (eg, H1P c ) of an effective channel (e.g., at CE 225-a for a public flow), for public messages W c Decoded (e.g., at Decode Common Message 230), re-encoded into Common Stream X c (eg, at reconstruct common stream 235), multiplied by the estimated effective channel and subtracted from the received signal (eg, at remove from received signal 240), thereby generating Y 1,p UE can then use Y 1,p The private message is decoded (e.g., at decode private message 245), which may also be combined with or utilize the results of CE 225-b for the private flow. Optionally, decoding may also include demodulation, demapping (e.g., from one or more layers), other processing, or any combination thereof. The UE may then combine the public message W 1,c part of and private message Y 1,p to recover the complete message (W1) sent to the UE. Figure 2B The focus is on SIC decoding, but in another example, the UE can jointly demodulate or decode the public stream and the private stream. In this way, the wireless communication system can utilize rate splitting to improve the characteristics of the communication channel, including the freedom and capacity of the wireless channel.

[0100] Figure 3 An example of a wireless communication system 300 that supports a signaling framework for rate splitting in accordance with one or more aspects of the present disclosure is illustrated. The wireless communication system 300 may include a network entity 105-a and a UE 115-a that may communicate within a geographic coverage area 110-a that may be associated with the network entity 105-a. The network entity 105-a and the UE 115-a may communicate via one or more downlink communication links 305-a and one or more uplink communication links 305-b.

[0101] In wireless communications (e.g., NR communications), multiple layers may be used to transmit multiple CWs, and the multiple CWs may be mapped to different layers of a single PDSCH transmission. For example, given 5 layers, the first CW may be mapped to the first 2 layers and the second CW may be mapped to the remaining 3 layers (e.g., in a 2+3 partition or scheme). For example, in an example where a parameter (e.g., maxNrofCodeWordsScheduledByDCI) specifying the number (e.g., maximum number) of CWs to be scheduled is equal to or has a value of 2, control signaling (e.g., DCI) for scheduling PDSCH transmissions (e.g., PDSCH transmissions of a DCI format (such as 1_1)) may include separate fields for modulation and coding scheme (MCS), new data indicator (NDI), redundancy version (RV), or any combination thereof for multiple CWs. In some examples, one or more other scheduling parameters (such as HARQID, FDRA, TDRA, PRG size, other parameters, or any combination thereof) may be the same for two scheduled CWs. In some examples, the DCI may dynamically disable one or more of the CWs based on one or more of the MCS value or RV value of the corresponding CW being set to a reserved value (eg, in an example where the number of layers in the scheduling instance is 4 or less).

[0102] In some examples, multiple TRPs may be used to communicate with a UE. For example, a UE may be scheduled using two PDSCH messages that may not overlap in time, frequency, or both. Additionally or alternatively, the two PDSCH messages may at least partially overlap in time, frequency, or both. The two PDSCH messages may be scheduled via corresponding control signaling messages (e.g., DCI) that may be sent from different TRPs. Such operation in the case of PDSCH overlap (e.g., partial or complete overlap at least in the time domain) may be allowed in examples where two PDSCH transmissions are associated with different resource set values ​​(e.g., CORESET values ​​or CORESSETPoolIndex values, which may also be TRP identifiers). For example, in a scenario with two PDSCH transmissions and two CORESETs, each CORESET may be configured with a corresponding value of CORESETPoolIndex (e.g., 0 and 1, grouping the CORESETs into two groups).

[0103] In some examples, the wireless communication network may employ multicast group scheduling (e.g., for RRC_CONNECTEDUEs). In such a scenario, the common frequency resources (CFRs) used for group common PDCCH / PDSCH transmissions may be restricted to the frequency resources of the dedicated unicast BWP. In some examples, the group common PDCCH (GC-PDCCH) may carry a CRC that may be scrambled by a common radio network temporary identifier (RNTI), which may be used to schedule the GC-PDSCH that may be scrambled by the same RNTI. In some examples, the CFRs may be defined as multicast and broadcast service "(MBS) frequency regions".

[0104] The CFR may include various configuration items or parameters, including: a starting PRB; the number of PRBs (e.g., similar to the locationAndBandwidth parameter associated with a BWP); a PDSCH configuration multicast parameter that may be separate from the PDSCH configuration multicast parameter for a dedicated unicast BWP; a PDCCH configuration multicast parameter that may be separate from the PDCCH configuration multicast parameter for a dedicated unicast BWP; and a CORESET for GC-PDCCH that may be configured within the CFR. In some examples, two DCI formats may be used to multicast GC-PDCCH to schedule GC-PDSCH. The first format may be DCI format 4_1, which may have fields similar to existing fields in DCI format 1_0 (fallback DCI) with CRC scrambled with G-RNTI. In some examples, the size of such DCI format 4_1 may be aligned with DCI format 1_0 with CRC scrambled by C-RNTI monitored in the CSS. The second format may be DCI format 4_2, which may be similar to existing fields in DCI format 1_1 with CRC scrambled with G-RNTI. In some examples, the size of DCI format 4_2 may be configured for each CFR for all G-RNTIs via unicast RRC signaling.

[0105] In order to provide a control signaling framework for use in conjunction with the rate splitting method, the network entity 105-a may send scheduling parameters associated with c-CW and p-CW to the UE 115-a. These scheduling parameters may include one or more of an MCS parameter, an NDI parameter, an RV parameter, or other parameters. Depending on the specific framework used to send these scheduling parameters, the network entity 105-a may utilize a single control signaling message or multiple control signaling messages. In an example in which the network entity 105-a sends multiple control signaling messages, the first control signaling message may include parameters for c-CW, which may be the same across multiple co-scheduled UEs. In some examples, the first control signaling message may be a group common (GC) control signaling message, and the CRC of the first control signaling message may be scrambled with a group RNTI (G-RNTI). The same G-RNTI may be configured for all co-scheduled UEs. For example, an MBS control signaling message format (e.g., format 4_0, 4_1, or 4_2) may be used. In examples where the network entity 105 - a sends multiple control signaling messages, the multiple control signaling messages may or may not be self-contained.

[0106] In some examples, the network entity 105-a may send a PDSCH message 325 to the UE 115-a. The PDSCH message 325 may include both the c-CW 335 and the p-CW 340. The c-CW 335 may be mapped to one or more first spatial layers 345, and the p-CW 340 may be mapped to one or more second spatial layers 350. In some examples, the network entity 105-a may send control signaling 320, which may schedule both the c-CW 335 and the p-CW 340 for transmission in the PDSCH message 325. In some examples, the PDSCH message 325 may be UE-specific, as the p-CW 340 may be different from a p-CW for another UE. For example, the p-CW 340 may be scrambled with a C-RNTI.

[0107] In some examples, the control signaling 320 may be a DCI and may have a DCI format 1_1 with multiple CWs, such as a c-CW 335 and a p-CW 340. However, it may not be clear which CW listed or indicated in the DCI is the p-CW 340 and which CW is the c-CW 335. In some examples, the c-CW may be mapped to a first scheduled CW and the p-CW may be mapped to a second scheduled CW, or vice versa. In some such examples, the first scheduled CW may refer to the CW whose scheduling parameters are listed first in the DCI, and the second scheduled CW may refer to the CW whose scheduling parameters are listed second in the DCI. Additionally or alternatively, the first scheduled CW may refer to a CW mapped to one or more first spatial layers 345, and the second scheduled CW may refer to a CW mapped to one or more second spatial layers 350.

[0108] In some examples, c-CW 335 may be mapped to a scheduled CW having a smaller MCS index value, and p-CW may be mapped to a scheduled CW having a larger MCS index value. Additionally or alternatively, c-CW 335 may be mapped to a scheduled CW having a smaller number of layers, and p-CW 340 may be mapped to a scheduled CW having a larger number of layers.

[0109] In some examples, the control signaling 320 may include a field that may indicate whether the first scheduled CW or the second scheduled CW corresponds to the c-CW 335 or the p-CW 340. For example, the control signaling 320 may include a 1-bit field to indicate one of the following two possibilities: a first possibility that the first CW is the c-CW 335 and the second CW is the p-CW 340; or a second possibility that the first CW is the p-CW 340 and the second CW is the c-CW 335. Additionally or alternatively, the control signaling 320 may include a 2-bit field or two 1-bit fields to jointly indicate whether the two scheduled CWs are c-CW and p-CW of a rate splitting scheme (e.g., whether rate splitting MIMO is scheduled), and if so, indicate one of the following two possibilities: a first possibility that the first CW is c-CW 335 and the second CW is p-CW 340; or a second possibility that the first CW is p-CW 340 and the second CW is c-CW 335. An example of a DCI format that may include such a field is shown in Table 1.

[0110]

[0111] Table 1

[0112] In some examples, the control signaling 320 may be two levels of control signaling (e.g., two levels of DCI) that the network entity 105-a sends to schedule the PDSCH message 325. The first level of the control signaling 320 may be group common control signaling (e.g., group common DCI (GC-DCI)), which may indicate parameters that are the same across multiple UEs, parameters that are the same between the c-CW 335 and the p-CW 340, or both. For example, such parameters may include one or more of an MCS parameter, an NDI parameter, an RV parameter, a frequency domain resource allocation (FDRA), a time domain resource allocation (TDRA), or a HARQ ID. In some examples, one or more of the MCS parameter, the NDI parameter, or the RV parameter may be a parameter associated with the c-CW 335 and may be common or shared between multiple UEs, or may be a common parameter for both the c-CW 335 and the p-CW 340. In some examples, one or more of the FDRA parameter, TRDA parameter, HARQ ID, or other parameters may be indicated separately for c-CW 335 cw and p-CW 340, and may not be shared or applicable to both c-CW 335 and p-CW 340. In some examples, multiple co-scheduled UEs (including UE 115-a) may decode the first level of control signaling 320, and the first level of control signaling may reuse an MBS DCI format (e.g., DCI format 4_1 or 4_2) that may be scrambled with a G-RNTI. An example of such a first level DCI format is shown in Table 2.

[0113]

[0114] Table 2

[0115] The second level of control signaling 320 may be UE-specific control signaling (e.g., DCI) to indicate parameters specific to p-CW 340. The second level of control signaling 320 may include at least one or more of an MCS parameter, an NDI parameter, an RV parameter, a DMRS port specific to p-CW 340 for UE 115-a. Such a second level of control signaling 320 may use a format (e.g., a DCI format) that has not been previously used or defined in a wireless communication standard. For example, the new DCI format may not include one or more of FDRA, TDRA, HARQ-ID, or other parameters (e.g., because they may be included in the first level of control signaling 320). An example of such a new DCI format is shown in Table 3.

[0116]

[0117] Table 3 (*optional fields)

[0118] In such an approach, the UE 115-a decodes the first level control signaling 320. In examples where the UE 115-a does not decode it, the UE 115-a may not be able to obtain the c-CW 335, the p-CW 340, or both. In some examples, this may mean that the second level control signaling 320 may not be self-contained or independent.

[0119] Figure 4 An example of a wireless communication system 400 that supports a signaling framework for rate splitting in accordance with one or more aspects of the present disclosure is illustrated. The wireless communication system 400 may involve a network entity 105-b, which may be an example of one or more network entities discussed with respect to other figures. The wireless communication system 400 may involve a UE 115-b, which may be an example of a UE discussed with respect to other figures. In some examples, the UE 115-b may be located in a geographic coverage area 110-b that may be associated with the network entity 105-b. The network entity 105-b and the UE 115-b may communicate via one or more downlink communication links 305-c and one or more uplink communication links 305-d.

[0120] In some examples, network entity 105-b may send a first PDSCH message 425 and a second PDSCH message 430 to UE 115-b. First PDSCH message 425 may include c-CW 435, and second PDSCH message 430 may include p-CW 440. In some examples, first PDSCH message 425 and second PDSCH message 430 may at least partially overlap in time, frequency, or both. In some examples, first PDSCH message 425 and second PDSCH message 430 may completely overlap in time, frequency, or both.

[0121] In some examples, the network entity 105-b may send control signaling 420. The control signaling 420 may include first control signaling and second control signaling (e.g., DCI). The first DCI may be a GC-DCI for scheduling a first PDSCH message 425, which may be a GC-PDSCH and may carry a c-CW 435 that may be received by the UE 115-b and other devices (e.g., other UEs) participating in the rate splitting scheme. Such a first DCI may be received in a CORESET with a first CORESETPoolIndex value (e.g., a value of 0) and may reuse an MBS DCI format (e.g., DCI format 4_1 or 4_2) that may be scrambled with a G-RNTI. In some examples, a CORESET associated with a control channel parameter of a CFR (e.g., PDCCH configuration multicast) may be configured with a first CORESETPoolIndex value (e.g., a value of 0). An example of the first control signaling of a DCI format is depicted in Table 4.

[0122]

[0123] Table 4

[0124] In some examples, the control signaling 420 may include second control signaling that may be UE-specific and may schedule a second PDSCH message 430 carrying a p-CW 440 for the UE 115-b. In some examples, the second control signaling may have a DCI format (e.g., DCI format 1_0, 1_1, or 1_2). The UE 115-b may receive the second control signaling in a CORESET with a second CORESETPoolIndex value (e.g., a value of 1). In some examples, a CORESET that is not in or associated with a control channel parameter of the CFR (e.g., a PDCCH configuration for multicast) (e.g., a CORESET in a PDCCH configuration for unicast) may be configured with a second CORESETPoolIndex value (e.g., a value of 1). An example of the second control signaling in a DCI format is depicted in Table 5.

[0125]

[0126] Table 5

[0127] In some examples, the first control signaling and the second control signaling may be self-contained, but the UE 115-b may decode both the first control signaling and the second control signaling to perform continuous interference cancellation or joint demodulation / decoding using the c-CW 435 and the p-CW 440. However, even in examples where the UE 115-b does not decode the first control signaling, even if continuous interference cancellation or joint demodulation / decoding is not performed, the UE 115-b may still decode the p-CW 440 carried in the second PDSCH message 430. For example, even in examples where the UE 115-b does not detect or receive both the first control signaling and the second control signaling, the UE 115-b may still receive or decode one of the first PDSCH message 425 or the second PDSCH message 430. This may be possible because the first control signaling and the second control signaling may be self-contained (e.g., with respect to scheduling information). However, in this case, the UE 115-b may not be able to perform continuous interference cancellation or joint demodulation / decoding.

[0128] In some examples, the second control signaling may include a field (e.g., a new field not discussed in the wireless communication standard) for indicating the presence of c-CW 435 on the same resource as the scheduled p-CW 440. In some examples, UE 115-b may use the field to identify or determine whether successive interference cancellation or joint demodulation / decoding of the first PDSCH message 425 and the second PDSCH message 430 can be performed. For example, in an example where UE 115-b detects the second control signaling and the new field or flag indicates the presence of c-CW 435 but does not detect the first control signaling, UE 115-b may not decode p-CW 440 to save power (e.g., because the likelihood of successful decoding of p-CW 440 is low because UE 115-b cannot perform successive interference cancellation or joint demodulation / decoding. For another example, UE 115-b may use the new field or flag to verify that the first control signaling and the second control signaling are related (e.g., the corresponding scheduled PDSCHs can be processed jointly).

[0129] In some examples, the first control signaling may include a field (e.g., a new field not discussed in the wireless communication standard) for indicating the presence of p-CW 440 on the same resource as the scheduled c-CW 435. Such a field may be used as an alternative or in addition to other fields discussed herein. In some examples, UE 115-b may use the new field or flag to verify that the first control signaling and the second control signaling are related (e.g., the corresponding scheduled PDSCHs may be processed jointly).

[0130] In some examples, UE 115-b can determine whether the first DCI and the second DCI are related (e.g., whether the corresponding scheduled PDSCHs (such as the first PDSCH message 425 and the second PDSCH message 430) can be processed jointly) based on determining that some control signaling fields indicate the same scheduling parameters, such as time / frequency resources (e.g., FDRA, TDRA, or both).

[0131] Figure 5 An example of a process flow 500 for supporting a signaling framework for rate splitting according to one or more aspects of the present disclosure is illustrated. Specifically, a signaling framework using a single PDSCH message is described. The process flow 500 can implement various aspects of the present disclosure described herein. The elements described in the process flow 500 can be examples of similarly named elements described herein.

[0132] In the following description of process flow 500, operations between various entities or elements may be performed in different orders or at different times. Some operations may also be excluded from process flow 500, or other operations may be added. Although various entities or elements (e.g., network entity 105-c and UE 115-c) are shown as performing operations of process flow 500, some aspects of some operations may also be performed by other entities or elements of process flow 500 or by entities or elements not depicted in the process flow, or any combination thereof.

[0133] At 520, UE 115-c may receive one or more control signaling messages, which may include: one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for the second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE.

[0134] In some examples, the one or more first scheduling parameters include a first modulation and coding scheme associated with a public codeword. In some examples, the one or more second scheduling parameters include a second modulation and coding scheme associated with a private codeword. In some examples, a first modulation and coding scheme index value associated with the first modulation and coding scheme may be less than a second modulation and coding scheme index value associated with the second modulation and coding scheme.

[0135] In some examples, a first control signaling message in the one or more control signaling messages may include one or more fields having one or more values ​​indicating that a common codeword may be mapped to one or more first layers of a physical downlink shared channel message, a private codeword may be mapped to one or more second layers of a physical downlink shared channel message, or both. In some examples, the one or more fields include a second value that may indicate that a common codeword and a private codeword are to be received in a physical downlink shared channel message.

[0136] In some examples, the one or more control signaling messages include a first control signaling message that schedules the transmission of a common codeword and a second control signaling message that schedules the transmission of a private codeword. In some examples, the first control signaling message may be a group common control signaling message for a plurality of UEs including the UE, and the second control signaling message may be for the first UE.

[0137] In some examples, the first control signaling message may include common parameters for the first UE and the second UE, common parameters for the common codeword and the private codeword, or both. In some examples, the second control signaling message may include one or more parameters that may be associated with the private codeword and specific to the first UE.

[0138] In some examples, the second control signaling message omits one or more parameters included in the first control signaling message that may be associated with both the public codeword and the private codeword.

[0139] In some examples, one or more first scheduling parameters, one or more second scheduling parameters, or both include a modulation and coding scheme, a new data indicator, a redundancy version, one or more demodulated signal reference ports, a frequency domain resource allocation, a time domain resource allocation, a hybrid automatic repeat request identifier, or any combination thereof.

[0140] At 525, UE 115-c may receive a physical downlink shared channel message based on one or more first scheduling parameters and one or more second scheduling parameters, and the physical downlink shared channel message may include one or more first layer public codewords mapped to the physical downlink shared channel message and one or more second layer private codewords mapped to the physical downlink shared channel message.

[0141] In some examples, the number of one or more first layers of physical downlink shared channel messages may be less than the number of one or more second layers of physical downlink shared channel messages.

[0142] In some examples, the downlink data for the first UE may include a first portion of one or more downlink messages for the first UE, and the additional downlink data for the first UE may include a second portion of one or more downlink messages for the first UE. In some examples, the bit allocation between the first portion and the second portion may be based on a first channel quality associated with the public codeword and a second channel quality associated with the private codeword.

[0143] Figure 6 An example of a process flow 600 for supporting a signaling framework for rate splitting according to one or more aspects of the present disclosure is illustrated. Specifically, a signaling framework using a single PDSCH message is described. The process flow 600 can implement various aspects of the present disclosure described herein. The elements described in the process flow 600 can be examples of similarly named elements described herein.

[0144] In the following description of process flow 600, operations between various entities or elements may be performed in different orders or at different times. Some operations may also be excluded from process flow 600, or other operations may be added. Although various entities or elements (e.g., network entity 105-d and UE 115-d) are shown as performing operations of process flow 600, some aspects of some operations may also be performed by other entities or elements of process flow 600 or by entities or elements not depicted in the process flow, or any combination thereof.

[0145] At 620, UE 115-d may receive one or more control signaling messages comprising: one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for the second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE.

[0146] In some examples, the one or more control signaling messages include a first control signaling message that schedules the transmission of a common codeword and a second control signaling message that schedules the transmission of a private codeword. In some examples, the first control signaling message schedules the transmission of a first physical downlink shared channel message, and the second control signaling message schedules the transmission of a second physical downlink shared channel message. In some examples, the first control signaling message is a group common control signaling message, and the second control signaling message is for the first UE.

[0147] In some examples, the first control signaling message may be in a first control resource set associated with a first control resource set pool index value, and the second control signaling message may be in a second control resource set associated with a second control resource set pool index value.

[0148] In some examples, the first control signaling message may include a field having a first value indicating that the first UE will receive a private codeword via a second set of time and frequency resources. In some examples, the second control signaling message may include a field having a first value indicating that the first UE will receive a public codeword via a first set of time and frequency resources.

[0149] At 625, UE 115-d may receive a first physical downlink shared channel message that may include a common codeword in a first set of time and frequency resources based on one or more first scheduling parameters. In some examples, receiving the first physical downlink shared channel message may be based on an interference cancellation procedure.

[0150] At 630, UE 115-d may receive a second physical downlink shared channel message that may include a private codeword in a second set of time and frequency resources that at least partially overlaps with the first set of time and frequency resources based on one or more second scheduling parameters. In some examples, receiving the second physical downlink shared channel message may be based on an interference cancellation procedure.

[0151] In some examples, the first set of time and frequency resources completely overlaps with the second set of time and frequency resources. In some examples, the downlink data for the UE may include a first portion of one or more downlink messages for the UE, and the additional downlink data for the UE may include a second portion of one or more downlink messages for the UE. In some examples, the bit allocation between the first portion and the second portion can be based on a first channel quality associated with the public codeword and a second channel quality associated with the private codeword.

[0152] At 635, UE 115-d may perform an interference cancellation procedure that may include: decoding a public codeword; subtracting a portion of a combined signal that may include a public codeword and a private codeword from the combined signal; and decoding the private codeword based on a remaining portion of the combined signal that corresponds to the private codeword.

[0153] At 640 , the UE 115 - d may jointly process the first physical downlink shared channel message and the second physical downlink shared channel message based on one or more of the one or more first scheduling parameters and the one or more second scheduling parameters being common.

[0154] Figure 7A block diagram of a device 705 supporting a signaling framework for rate splitting according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The communication manager 720 may be implemented at least in part by one or both of a modem and a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0155] The receiver 710 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with signaling frames for rate splitting). The information may be communicated to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0156] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information associated with various information channels (e.g., a control channel associated with a signaling frame for rate splitting, a data channel, an information channel), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver component. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0157] The communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the signaling framework for rate splitting as described herein. For example, the communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0158] In some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports means for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0159] Additionally or alternatively, in some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0160] In some examples, the communication manager 720 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 may receive information from the receiver 710, transmit information to the transmitter 715, or be integrated in conjunction with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0161] According to the examples disclosed herein, the communication manager 720 may support wireless communication at the first UE. For example, the communication manager 720 may be configured to or otherwise support a component for receiving one or more control signaling messages. In some examples, the communication manager 720 may be configured to or otherwise support a component for: one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for the second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE. The communication manager 720 may be configured to or otherwise support a component for receiving a physical downlink shared channel message based on one or more first scheduling parameters and one or more second scheduling parameters, the physical downlink shared channel message including one or more first layer common codewords mapped to the physical downlink shared channel message and one or more second layer private codewords mapped to the physical downlink shared channel message.

[0162] Additionally or alternatively, according to the examples disclosed herein, the communication manager 720 may support wireless communication at the first UE. For example, the communication manager 720 may be configured to or otherwise support a component for receiving one or more control signaling messages, the one or more control signaling messages including one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for the second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE. The communication manager 720 may be configured to or otherwise support a component for receiving a first physical downlink shared channel message including a common codeword in a first time and frequency resource set based on the one or more first scheduling parameters. The communication manager 720 may be configured to or otherwise support a component for receiving a second physical downlink shared channel message including a private codeword in a second time and frequency resource set that at least partially overlaps with the first time and frequency resource set based on the one or more second scheduling parameters.

[0163] By including or configuring a communication manager 720 according to examples as described herein, the device 705 (e.g., a processor controlling or otherwise coupled to the receiver 710, the transmitter 715, the communication manager 720, or a combination thereof) may support techniques for reducing processing, reducing power consumption, more efficiently utilizing communication resources, or any combination thereof.

[0164] Figure 8 A block diagram of a device 805 supporting a signaling framework for rate splitting according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of the device 705 or UE 115 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The communication manager 820 may be implemented at least in part by one or both of a modem and a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0165] The receiver 810 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with signaling frames for rate splitting). The information may be communicated to other components of the device 805. The receiver 810 may utilize a single antenna or a collection of multiple antennas.

[0166] The transmitter 815 may provide means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information associated with various information channels (e.g., a control channel associated with a signaling frame for rate splitting, a data channel, an information channel), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 815 may be co-located with the receiver 810 in a transceiver component. The transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0167] The device 805 or its various components may be examples of components for performing various aspects of the signaling framework for rate splitting as described herein. For example, the communication manager 820 may include a control signaling component 825, a PDSCH receiving component 830, or any combination thereof. In some examples, the communication manager 820 or its various components may be configured to use or otherwise cooperate with the receiver 810, the transmitter 815, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.

[0168] According to the examples disclosed herein, the communication manager 820 may support wireless communication at the first UE. The control signaling component 825 may be configured to or otherwise support a component for receiving one or more control signaling messages including. In some examples, the scheduling parameter component 835 may be configured to or otherwise support a component for one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for the second UE, and the scheduling parameter component 835 may be configured to or otherwise support a component for one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE. The PDSCH reception component 830 may be configured to or otherwise support a component for receiving a physical downlink shared channel message based on one or more first scheduling parameters and one or more second scheduling parameters, the physical downlink shared channel message including one or more first layer common codewords mapped to the physical downlink shared channel message and one or more second layer private codewords mapped to the physical downlink shared channel message.

[0169] Additionally or alternatively, according to examples as disclosed herein, the communication manager 820 may support wireless communication at the first UE. The control signaling component 825 may be configured to or otherwise support a component for receiving one or more control signaling messages, the one or more control signaling messages including one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for the second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE. The PDSCH reception component 830 may be configured to or otherwise support a component for receiving a first physical downlink shared channel message including a common codeword in a first time and frequency resource set based on the one or more first scheduling parameters. The PDSCH reception component 830 may be configured to or otherwise support a component for receiving a second physical downlink shared channel message including a private codeword in a second time and frequency resource set that at least partially overlaps with the first time and frequency resource set based on the one or more second scheduling parameters.

[0170] Fig. 9 A block diagram of a communication manager 920 supporting a signaling framework for rate splitting according to one or more aspects of the present disclosure is shown. The communication manager 920 or its various components may be examples of components for performing various aspects of the signaling framework for rate splitting as described herein. For example, the communication manager 920 may include a control signaling component 925, a PDSCH reception component 930, an MCS component 935, a codeword reception component 940, a scheduling parameter component 945, an interference cancellation component 950, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0171] According to the examples disclosed herein, the communication manager 920 may support wireless communication at the first UE. The control signaling component 925 may be configured to or otherwise support a component for receiving one or more control signaling messages including. In some examples, the scheduling parameter component 945 may be configured to or otherwise support a component for one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for the second UE, and the scheduling parameter component 945 may be configured to or otherwise support a component for one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE. The PDSCH reception component 930 may be configured to or otherwise support a component for receiving a physical downlink shared channel message based on one or more first scheduling parameters and one or more second scheduling parameters, the physical downlink shared channel message including one or more first layer common codewords mapped to the physical downlink shared channel message and one or more second layer private codewords mapped to the physical downlink shared channel message.

[0172] In some examples, the one or more first scheduling parameters include a first modulation and coding scheme associated with a public codeword. In some examples, the one or more second scheduling parameters include a second modulation and coding scheme associated with a private codeword. In some examples, a first modulation and coding scheme index value associated with the first modulation and coding scheme is less than a second modulation and coding scheme index value associated with the second modulation and coding scheme.

[0173] In some examples, the number of one or more first layers of physical downlink shared channel messages is less than the number of one or more second layers of physical downlink shared channel messages.

[0174] In some examples, a first control signaling message among the one or more control signaling messages includes one or more fields having one or more values ​​indicating that a common codeword is mapped to one or more first layers of a physical downlink shared channel message, a private codeword is mapped to one or more second layers of a physical downlink shared channel message, or both.

[0175] In some examples, the one or more fields include a second value indicating that a common codeword and a private codeword are to be received in a physical downlink shared channel message.

[0176] In some examples, the one or more control signaling messages include a first control signaling message that schedules the transmission of a common codeword and a second control signaling message that schedules the transmission of a private codeword. In some examples, the first control signaling message is a group common control signaling message for a set of multiple UEs including the UE, and the second control signaling message is for the first UE.

[0177] In some examples, the first control signaling message includes common parameters for the first UE and the second UE, common parameters for a common codeword and a private codeword, or both.

[0178] In some examples, the second control signaling message includes one or more parameters associated with the private codeword and specific to the first UE.

[0179] In some examples, the second control signaling message omits one or more parameters associated with both the public codeword and the private codeword included in the first control signaling message.

[0180] In some examples, one or more first scheduling parameters, one or more second scheduling parameters, or both include a modulation and coding scheme, a new data indicator, a redundancy version, one or more demodulated signal reference ports, a frequency domain resource allocation, a time domain resource allocation, a hybrid automatic repeat request identifier, or any combination thereof.

[0181] In some examples, the downlink data for the first UE includes a first portion of one or more downlink messages for the first UE, and the additional downlink data for the first UE includes a second portion of one or more downlink messages for the first UE. In some examples, a bit allocation between the first portion and the second portion is based on a first channel quality associated with the public codeword and a second channel quality associated with the private codeword.

[0182] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communications at the first UE. In some examples, the control signaling component 925 may be configured to or otherwise support a component for receiving one or more control signaling messages, the one or more control signaling messages including one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for the second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE. In some examples, the PDSCH reception component 930 may be configured to or otherwise support a component for receiving a first physical downlink shared channel message including a common codeword in a first time and frequency resource set based on the one or more first scheduling parameters. In some examples, the PDSCH reception component 930 may be configured to or otherwise support a component for receiving a second physical downlink shared channel message including a private codeword in a second time and frequency resource set that at least partially overlaps with the first time and frequency resource set based on the one or more second scheduling parameters.

[0183] In some examples, the one or more control signaling messages include a first control signaling message that schedules the transmission of a common codeword and a second control signaling message that schedules the transmission of a private codeword.

[0184] In some examples, the first control signaling message is in a first control resource set associated with a first control resource set pool index value, and the second control signaling message is in a second control resource set associated with a second control resource set pool index value.

[0185] In some examples, the interference cancellation component 950 may be configured to or otherwise support components for performing interference cancellation procedures. In some examples, the interference cancellation component 950 may be configured to or otherwise support components for decoding a public codeword, the interference cancellation component 950 may be configured to or otherwise support components for subtracting a portion of the combined signal corresponding to the public codeword from a combined signal including a public codeword and a private codeword, and the interference cancellation component 950 may be configured to or otherwise support components for decoding a private codeword based on the remaining portion of the combined signal corresponding to the private codeword. In some examples, the PDSCH receiving component 930 may be configured to or otherwise support components for receiving a first physical downlink shared channel message, a second physical downlink shared channel message, or both based on an interference cancellation procedure.

[0186] In some examples, the second control signaling message includes a field having a first value indicating that the first UE is to receive a common codeword via a first set of time and frequency resources.

[0187] In some examples, the first control signaling message includes a field having a first value indicating that the first UE is to receive a private codeword via a second set of time and frequency resources.

[0188] In some examples, a first control signaling message schedules the transmission of a first physical downlink shared channel message and a second control signaling message schedules the transmission of a second physical downlink shared channel message, and the PDSCH receiving component 930 may be configured to or otherwise support a component for jointly processing the first physical downlink shared channel message and the second physical downlink shared channel message based on one or more first scheduling parameters and one or more second scheduling parameters being common.

[0189] In some examples, the first set of time and frequency resources completely overlaps with the second set of time and frequency resources.

[0190] In some examples, the first control signaling message is a group common control signaling message, and the second control signaling message is for the first UE.

[0191] In some examples, the downlink data for the UE includes a first portion of one or more downlink messages for the UE, and the additional downlink data for the UE includes a second portion of one or more downlink messages for the UE. In some examples, a bit allocation between the first portion and the second portion is based on a first channel quality associated with the public codeword and a second channel quality associated with the private codeword.

[0192] Fig.10 A diagram of a system including a device 1005 supporting a signaling framework for rate splitting according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of a device 705, a device 805, or a UE 115 as described herein, or include components thereof. The device 1005 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1005 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, a memory 1030, a code 1035, and a processor 1040. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1045).

[0193] I / O controller 1010 can manage input and output signals for device 1005. I / O controller 1010 can also manage peripheral devices that are not integrated into device 1005. In some cases, I / O controller 1010 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1010 can utilize an operating system, such as iOS. ® ANDROID ® , MS-DOS ® 、MS-WINDOWS ® , OS / 2 ® ,UNIX ® 、LINUX ® or another known operating system. Additionally or alternatively, I / O controller 1010 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1010 may be implemented as part of a processor (such as processor 1040). In some cases, a user may interact with device 1005 via I / O controller 1010 or via hardware components controlled by I / O controller 1010.

[0194] In some cases, the device 1005 may include a single antenna 1025. However, in some other cases, the device 1005 may have more than one antenna 1025, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1015 may communicate bidirectionally via one or more antennas 1025, a wired link, or a wireless link as described herein. For example, the transceiver 1015 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1015 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1025 for transmission; and demodulating packets received from one or more antennas 1025. The transceiver 1015 or the transceiver 1015 and one or more antennas 1025 may be examples of transmitters 715, transmitters 815, receivers 710, receivers 810, or any combination thereof or any components thereof as described herein.

[0195] Memory 1030 may include random access memory (RAM) and read-only memory (ROM). Memory 1030 may store computer-readable, computer-executable code 1035 including instructions that, when executed by processor 1040, cause device 1005 to perform various functions described herein. Code 1035 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1035 may not be directly executable by processor 1040, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1030 may include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0196] Processor 1040 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1040. Processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1030) to enable device 1005 to perform various functions (e.g., functions or tasks supporting a signaling framework for rate splitting). For example, device 1005 or a component of device 1005 may include processor 1040 and memory 1030 coupled to or coupled to processor 1040, and processor 1040 and memory 1030 are configured to perform various functions described herein.

[0197] According to the examples disclosed herein, the communication manager 1020 may support wireless communication at the first UE. For example, the communication manager 1020 may be configured to or otherwise support a component for receiving one or more control signaling messages. In some examples, the communication manager 1020 may be configured to or otherwise support a component for: one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for the second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE. The communication manager 1020 may be configured to or otherwise support a component for receiving a physical downlink shared channel message based on one or more first scheduling parameters and one or more second scheduling parameters, the physical downlink shared channel message including one or more first layer common codewords mapped to the physical downlink shared channel message and one or more second layer private codewords mapped to the physical downlink shared channel message.

[0198] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1020 may support wireless communication at the first UE. For example, the communication manager 1020 may be configured to or otherwise support a component for receiving one or more control signaling messages, the one or more control signaling messages including one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for the second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE. The communication manager 1020 may be configured to or otherwise support a component for receiving a first physical downlink shared channel message including a common codeword in a first time and frequency resource set based on the one or more first scheduling parameters. The communication manager 1020 may be configured to or otherwise support a component for receiving a second physical downlink shared channel message including a private codeword in a second time and frequency resource set that at least partially overlaps with the first time and frequency resource set based on the one or more second scheduling parameters.

[0199] By including or configuring a communications manager 1020 according to the examples described herein, the device 1005 may support techniques for improving communications reliability, reducing latency, improving user experience associated with reduced processing, reducing power consumption, more efficiently utilizing communications resources, improving coordination between devices, extending battery life, improving utilization of processing power, or any combination thereof.

[0200] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1015, one or more antennas 1025, or any combination thereof. Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported or performed by the processor 1040, the memory 1030, the code 1035, or any combination thereof. For example, the code 1035 may include instructions that are executable by the processor 1040 to cause the device 1005 to perform various aspects of the signaling framework for rate splitting as described herein, or the processor 1040 and the memory 1030 may be otherwise configured to perform or support such operations.

[0201] Fig.11 A flow chart illustrating a method 1100 for supporting a signaling framework for rate splitting according to one or more aspects of the present disclosure is shown. The operations of the method 1100 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1100 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 10 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0202] At 1105, the method may include receiving one or more control signaling messages. In some examples, the one or more control signaling messages may include one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for the second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE. The operations of 1105 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1105 may be performed as described in reference to Fig. 9 The described control signaling component 925 is performed.

[0203] At 1110, the method may include receiving a physical downlink shared channel message based on one or more first scheduling parameters and one or more second scheduling parameters, the physical downlink shared channel message including one or more first layer public codewords mapped to the physical downlink shared channel message and one or more second layer private codewords mapped to the physical downlink shared channel message. The operations of 1110 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1110 may be performed as described in reference to Fig. 9 The described PDSCH receiving component 930 is performed.

[0204] Fig.12 A flow chart illustrating a method 1200 for supporting a signaling framework for rate splitting according to one or more aspects of the present disclosure is shown. The operations of the method 1200 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1200 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 10 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0205] At 1205, the method may include receiving one or more control signaling messages including one or more first scheduling parameters for a common codeword associated with downlink data for a first UE and downlink data for a second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE. The operations of 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed as described in reference to Fig. 9 The described control signaling component 925 is performed.

[0206] At 1210, the method may include receiving a first physical downlink shared channel message including a common codeword in a first set of time and frequency resources based on one or more first scheduling parameters. The operations of 1210 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1210 may be performed as described in reference to Fig. 9 The described PDSCH receiving component 930 is performed.

[0207] At 1215, the method may include receiving a second physical downlink shared channel message including a private codeword in a second set of time and frequency resources that at least partially overlaps with the first set of time and frequency resources based on one or more second scheduling parameters. The operations of 1215 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1215 may be performed as described in reference to Fig. 9 The described PDSCH receiving component 930 is performed.

[0208] The following provides an overview of various aspects of the disclosure:

[0209] Aspect 1: A method for performing wireless communications at a first UE, comprising: receiving one or more control signaling messages, the one or more control signaling messages including: one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for a second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE; and receiving a physical downlink shared channel message based at least in part on the one or more first scheduling parameters and the one or more second scheduling parameters, the physical downlink shared channel message including the common codeword mapped to one or more first layers of the physical downlink shared channel message and the private codeword mapped to one or more second layers of the physical downlink shared channel message.

[0210] Aspect 2: A method according to Aspect 1, wherein the one or more first scheduling parameters include a first modulation and decoding scheme associated with the public codeword; the one or more second scheduling parameters include a second modulation and decoding scheme associated with the private codeword; and the first modulation and decoding scheme index value associated with the first modulation and decoding scheme is less than the second modulation and decoding scheme index value associated with the second modulation and decoding scheme.

[0211] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the number of the one or more first layers of the physical downlink shared channel message is less than the number of the one or more second layers of the physical downlink shared channel message.

[0212] Aspect 4: A method according to any one of Aspects 1 to 3, wherein the first control signaling message among the one or more control signaling messages includes one or more fields having one or more values, and the one or more values ​​indicate that the common codeword is mapped to the one or more first layers of the physical downlink shared channel message, the private codeword is mapped to the one or more second layers of the physical downlink shared channel message, or both.

[0213] Aspect 5: The method according to aspect 4, wherein the one or more fields include a second value, the second value indicating that the common codeword and the private codeword are to be received in the physical downlink shared channel message.

[0214] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the one or more control signaling messages include a first control signaling message for scheduling the sending of the common codeword and a second control signaling message for scheduling the sending of the private codeword; and the first control signaling message is a group common control signaling message for multiple UEs including the UE, and the second control signaling message is for the first UE.

[0215] Aspect 7: The method according to aspect 6, wherein the first control signaling message includes common parameters for the first UE and the second UE, common parameters for the common codeword and the private codeword, or both.

[0216] Aspect 8: The method according to any one of aspects 6 to 7, wherein the second control signaling message includes one or more parameters associated with the private codeword and specific to the first UE.

[0217] Aspect 9: The method according to any one of aspects 6 to 8, wherein the second control signaling message omits one or more parameters associated with both the public codeword and the private codeword included in the first control signaling message.

[0218] Aspect 10: A method according to any one of Aspects 1 to 9, wherein the one or more first scheduling parameters, the one or more second scheduling parameters, or both include a modulation and decoding scheme, a new data indicator, a redundant version, one or more demodulation signal reference ports, a frequency domain resource allocation, a time domain resource allocation, a hybrid automatic repeat request identifier, or any combination thereof.

[0219] Aspect 11: A method according to any one of Aspects 1 to 10, wherein the downlink data for the first UE includes a first part of one or more downlink messages for the first UE, and the additional downlink data for the first UE includes a second part of the one or more downlink messages for the first UE; and the bit allocation between the first part and the second part is at least partially based on a first channel quality associated with the public codeword and a second channel quality associated with the private codeword.

[0220] Aspect 12: A method for performing wireless communications at a first UE, comprising: receiving one or more control signaling messages, the one or more control signaling messages including one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for a second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE; receiving a first physical downlink shared channel message including the common codeword in a first time and frequency resource set based at least in part on the one or more first scheduling parameters; and receiving a second physical downlink shared channel message including the private codeword in a second time and frequency resource set that at least partially overlaps with the first time and frequency resource set based at least in part on the one or more second scheduling parameters.

[0221] Aspect 13: The method according to aspect 12, wherein the one or more control signaling messages include a first control signaling message scheduling the transmission of the common codeword and a second control signaling message scheduling the transmission of the private codeword.

[0222] Aspect 14: A method according to Aspect 13, wherein the first control signaling message is in a first control resource set associated with a first control resource set pool index value, and the second control signaling message is in a second control resource set associated with a second control resource set pool index value.

[0223] Aspect 15: The method according to any one of Aspects 13 to 14 also includes: performing an interference cancellation procedure, the interference cancellation procedure including: decoding the common codeword, subtracting the part of the combined signal corresponding to the common codeword from a combined signal including the common codeword and the private codeword, and decoding the private codeword based at least in part on the remaining part of the combined signal corresponding to the private codeword; and wherein receiving the first physical downlink shared channel message, the second physical downlink shared channel message, or both is at least in part based on the interference cancellation procedure.

[0224] Aspect 16: The method according to any one of aspects 13 to 15, wherein the second control signaling message includes a field having a first value, the first value indicating that the first UE is to receive the common codeword through the first set of time and frequency resources.

[0225] Aspect 17: A method according to any one of aspects 13 to 16, wherein the first control signaling message includes a field having a first value, the first value indicating that the first UE is to receive the private codeword through the second set of time and frequency resources.

[0226] Aspect 18: A method according to any one of Aspects 13 to 17, wherein the first control signaling message schedules the sending of the first physical downlink shared channel message, and the second control signaling message schedules the sending of the second physical downlink shared channel message, the method further comprising: jointly processing the first physical downlink shared channel message and the second physical downlink shared channel message at least in part based on the one or more first scheduling parameters and one or more of the one or more second scheduling parameters being common.

[0227] Aspect 19: The method according to any one of Aspects 13 to 18, wherein the first set of time and frequency resources completely overlaps with the second set of time and frequency resources.

[0228] Aspect 20: The method according to any one of aspects 13 to 19, wherein the first control signaling message is a group common control signaling message, and the second control signaling message is for the first UE.

[0229] Aspect 21: A method according to any one of Aspects 12 to 20, wherein the downlink data for the UE includes a first part of one or more downlink messages for the UE, and the additional downlink data for the UE includes a second part of the one or more downlink messages for the UE; and the bit allocation between the first part and the second part is at least partially based on a first channel quality associated with the public codeword and a second channel quality associated with the private codeword.

[0230] Aspect 22: An apparatus for performing wireless communications at a first UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 11.

[0231] Aspect 23: An apparatus for wireless communication at a first UE, comprising: at least one component for performing the method according to any one of aspects 1 to 11.

[0232] Aspect 24: A non-transitory computer-readable medium storing code for wireless communication at a first UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 11.

[0233] Aspect 25: An apparatus for performing wireless communications at a first UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 12 to 21.

[0234] Aspect 26: An apparatus for wireless communication at a first UE, comprising: at least one component for performing a method according to any one of aspects 12 to 21.

[0235] Aspect 27: A non-transitory computer-readable medium storing code for wireless communication at a first UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 12 to 21.

[0236] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0237] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0238] The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0239] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0240] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using the one or more instructions or codes. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the functions are implemented at different physical locations.

[0241] Computer-readable media include both non-transient computer storage media and communication media, and the communication media include any media that facilitates the transfer of computer programs from one location to another.Non-transient storage media can be any available media that can be accessed by a general or special computer.By way of example and not limitation, non-transient computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or can be used to carry or store desired program code components in the form of instructions or data structures and any other non-transient media that can be accessed by a general or special computer, or a general or special processor.Moreover, any connection is appropriately referred to as a computer-readable medium.For example, if software is sent from a website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwaves, coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwaves are included in the definition of computer-readable media. Disks and optical disks as used herein include CDs, laser optical disks, optical optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, and optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0242] As used herein, including in the claims, "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (in other words, A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0243] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, etc. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include resolving, retrieving, selecting, choosing, establishing, and other such similar actions.

[0244] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label regardless of the second reference label, or other subsequent reference labels.

[0245] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The specific embodiments include specific details to provide an understanding of the described technology. However, these technologies may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0246] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a first user equipment (UE), comprising: Receiving one or more control signaling messages, the one or more control signaling messages comprising: one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for a second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE; and A physical downlink shared channel message is received at least in part based on the one or more first scheduling parameters and the one or more second scheduling parameters, the physical downlink shared channel message including the common codeword mapped to one or more first layers of the physical downlink shared channel message and the private codeword mapped to one or more second layers of the physical downlink shared channel message.

2. The method according to claim 1, wherein: The one or more first scheduling parameters include a first modulation and coding scheme associated with the common codeword; The one or more second scheduling parameters include a second modulation and coding scheme associated with the private codeword; and A first modulation and coding scheme index value associated with the first modulation and coding scheme is less than a second modulation and coding scheme index value associated with the second modulation and coding scheme.

3. The method according to claim 1, wherein the number of the one or more first layers of the physical downlink shared channel message is less than the number of the one or more second layers of the physical downlink shared channel message.

4. The method of claim 1 , wherein a first control signaling message among the one or more control signaling messages comprises one or more fields having one or more values, the one or more values ​​indicating that the common codeword is mapped to the one or more first layers of the physical downlink shared channel message, the private codeword is mapped to the one or more second layers of the physical downlink shared channel message, or both.

5. The method of claim 4, wherein the one or more fields include a second value indicating that the common codeword and the private codeword are to be received in the physical downlink shared channel message.

6. The method according to claim 1, wherein: The one or more control signaling messages include a first control signaling message that schedules the transmission of the common codeword and a second control signaling message that schedules the transmission of the private codeword; and The first control signaling message is a group common control signaling message for a plurality of UEs including the UE, and the second control signaling message is for the first UE.

7. The method of claim 6, wherein the first control signaling message includes common parameters for the first UE and the second UE, common parameters for the common codeword and the private codeword, or both.

8. The method of claim 6, wherein the second control signaling message comprises one or more parameters associated with the private codeword and specific to the first UE.

9. The method of claim 6, wherein the second control signaling message omits one or more parameters associated with both the public codeword and the private codeword included in the first control signaling message.

10. The method of claim 1, wherein the one or more first scheduling parameters, the one or more second scheduling parameters, or both include a modulation and coding scheme, a new data indicator, a redundancy version, one or more demodulated signal reference ports, a frequency domain resource allocation, a time domain resource allocation, a hybrid automatic repeat request identifier, or any combination thereof.

11. The method according to claim 1, wherein: The downlink data for the first UE comprises a first portion of one or more downlink messages for the first UE, and the additional downlink data for the first UE comprises a second portion of the one or more downlink messages for the first UE; and An allocation of bits between the first portion and the second portion is based at least in part on a first channel quality associated with the public codeword and a second channel quality associated with the private codeword.

12. A method for wireless communication at a first user equipment (UE), comprising: receiving one or more control signaling messages, the one or more control signaling messages comprising one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for a second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE; receiving, in a first set of time and frequency resources, a first physical downlink shared channel message including the common codeword based at least in part on the one or more first scheduling parameters; as well as Based at least in part on the one or more second scheduling parameters, a second physical downlink shared channel message including the private codeword is received in a second set of time and frequency resources that at least partially overlaps with the first set of time and frequency resources.

13. The method of claim 12, wherein the one or more control signaling messages include a first control signaling message scheduling the transmission of the common codeword and a second control signaling message scheduling the transmission of the private codeword.

14. The method of claim 13, wherein the first control signaling message is in a first control resource set associated with a first control resource set pool index value, and the second control signaling message is in a second control resource set associated with a second control resource set pool index value.

15. The method according to claim 13, further comprising: Executing an interference cancellation procedure, the interference cancellation procedure comprising: Decoding the common codeword, subtracting a portion of the combined signal corresponding to the public codeword from a combined signal comprising the public codeword and the private codeword, and decoding the private codeword based at least in part on a remaining portion of the combined signal that corresponds to the private codeword; and Wherein receiving the first physical downlink shared channel message, the second physical downlink shared channel message, or both is based at least in part on the interference cancellation procedure.

16. The method of claim 13, wherein the second control signaling message includes a field having a first value, the first value indicating that the first UE is to receive the common codeword through the first set of time and frequency resources.

17. The method of claim 13, wherein the first control signaling message includes a field having a first value, the first value indicating that the first UE is to receive the private codeword over the second set of time and frequency resources.

18. The method of claim 13, wherein the first control signaling message schedules the sending of the first physical downlink shared channel message, and the second control signaling message schedules the sending of the second physical downlink shared channel message, the method further comprising: The first physical downlink shared channel message and the second physical downlink shared channel message are jointly processed based at least in part on one or more of the one or more first scheduling parameters and the one or more second scheduling parameters being common.

19. The method of claim 13, wherein the first set of time and frequency resources completely overlaps with the second set of time and frequency resources.

20. The method of claim 13, wherein the first control signaling message is a group common control signaling message, and the second control signaling message is for the first UE.

21. The method of claim 12, wherein: The downlink data for the UE comprises a first portion of one or more downlink messages for the UE, and the additional downlink data for the UE comprises a second portion of the one or more downlink messages for the UE; and An allocation of bits between the first portion and the second portion is based at least in part on a first channel quality associated with the public codeword and a second channel quality associated with the private codeword.

22. An apparatus for wireless communication at a first user equipment (UE), comprising: processor; and A memory coupled to the processor and storing instructions executable by the processor to cause the apparatus to perform the following operations: Receiving one or more control signaling messages, the one or more control signaling messages comprising: one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for a second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE; as well as A physical downlink shared channel message is received at least in part based on the one or more first scheduling parameters and the one or more second scheduling parameters, the physical downlink shared channel message including the common codeword mapped to one or more first layers of the physical downlink shared channel message and the private codeword mapped to one or more second layers of the physical downlink shared channel message.

23. The apparatus of claim 22, wherein: The one or more first scheduling parameters include a first modulation and coding scheme associated with the common codeword; The one or more second scheduling parameters include a second modulation and coding scheme associated with the private codeword; and A first modulation and coding scheme index value associated with the first modulation and coding scheme is less than a second modulation and coding scheme index value associated with the second modulation and coding scheme.

24. The apparatus of claim 22, wherein the number of the one or more first layers of the physical downlink shared channel message is less than the number of the one or more second layers of the physical downlink shared channel message.

25. An apparatus according to claim 22, wherein a first control signaling message among the one or more control signaling messages includes one or more fields having one or more values, and the one or more values ​​indicate that the common codeword is mapped to the one or more first layers of the physical downlink shared channel message, the private codeword is mapped to the one or more second layers of the physical downlink shared channel message, or both.

26. The apparatus of claim 22, wherein: The one or more control signaling messages include a first control signaling message that schedules the transmission of the common codeword and a second control signaling message that schedules the transmission of the private codeword; and The first control signaling message is a group common control signaling message for a plurality of UEs including the UE, and the second control signaling message is for the first UE.

27. An apparatus for wireless communication at a first user equipment (UE), comprising: processor; and A memory coupled to the processor and storing instructions executable by the processor to cause the apparatus to perform the following operations: receiving one or more control signaling messages, the one or more control signaling messages comprising one or more first scheduling parameters for a common codeword associated with downlink data for the first UE and downlink data for a second UE, and one or more second scheduling parameters for a private codeword associated with additional downlink data for the first UE; receiving, in a first set of time and frequency resources, a first physical downlink shared channel message including the common codeword based at least in part on the one or more first scheduling parameters; as well as Based at least in part on the one or more second scheduling parameters, a second physical downlink shared channel message including the private codeword is received in a second set of time and frequency resources that at least partially overlaps with the first set of time and frequency resources.

28. The apparatus of claim 27, wherein the one or more control signaling messages include a first control signaling message scheduling transmission of the common codeword and a second control signaling message scheduling transmission of the private codeword.

29. The apparatus of claim 28, wherein the first control signaling message is in a first set of control resources associated with a first set of control resource pool index value, and the second control signaling message is in a second set of control resources associated with a second set of control resource pool index value.

30. The apparatus of claim 28, wherein the first control signaling message schedules the transmission of the first physical downlink shared channel message and the second control signaling message schedules the transmission of the second physical downlink shared channel message, and the instructions are further executable by the processor to cause the apparatus to: The first physical downlink shared channel message and the second physical downlink shared channel message are jointly processed based at least in part on one or more of the one or more first scheduling parameters and the one or more second scheduling parameters being common.

Images