Rate split multiple access messaging with repetition

Abstract

A transmitter may be configured to transmit information to a receiver that configures a repetition pattern of at least one of a public portion of a rate split multiple access (RSMA) message or a private portion of the RSMA message. The transmitter may be further configured to transmit at least one repetition of the at least one of the public portion or the private portion of the RSMA message to the receiver according to the repetition pattern. The receiver may be configured to receive the information configuring the repetition pattern. The receiver may be further configured to receive, from the transmitter, at least one repetition of the at least one of the public portion of the RSMA message or the private portion of the RSMA message after receiving the information configuring the repetition pattern.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the benefit of U.S. Non - Provisional Patent Application No. 18 / 063,034, entitled "RATE - SPLITTING MULTIPLE ACCESS MESSAGING WITH REPETITION", filed on December 7, 2022, which is hereby incorporated by reference in its entirety. Background Art Technical Field

[0003] This disclosure generally relates to communication systems, and more particularly to the reliability of message transmission implementing rate - splitting multiple access (RSMA) in wireless communication systems.

[0004] Introduction

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

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous evolution of mobile broadband promulgated by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., related to the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine - type communication (mMTC), and ultra - reliable low - latency communication (URLLC). Some aspects of 5G NR may be based on the 4G Long - Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the Invention

[0007] A simplified review of one or more aspects is presented below to provide a basic understanding of these aspects. This summary of the invention is not an extensive overview of all contemplated aspects, and is neither intended to identify key or critical elements of all aspects nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that follows.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a user equipment (UE) or a component thereof configured to receive information on a repetition pattern of at least one of a common part or a private part of a configured rate-split multiple access (RSMA) message from the apparatus. The apparatus may be further configured to receive at least one repetition of at least one of the common part or the private part of the RSMA message from the apparatus after receiving the information configuring the repetition pattern.

[0009] In another aspect of the present disclosure, another method, another computer-readable medium, and another apparatus are provided. The other apparatus may be a network node, a UE, or a component thereof configured to send information on a repetition pattern of at least one of a common part or a private part of a configured RSMA message to at least one UE. The other apparatus may be further configured to send at least one repetition of at least one of the common part or the private part of the RSMA message to the at least one UE according to the repetition pattern.

[0010] To achieve the foregoing and related purposes, one or more aspects include the features described in detail below and particularly pointed out in the claims. The following description and the drawings set forth in detail some illustrative features of one or more aspects. However, these features are only indicative of some of the various ways in which the principles of the various aspects may be employed, and this specification is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0012] Figure 2 is a diagram illustrating an example of a decomposed base station architecture.

[0013] Figure 3A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0014] Figure 3B is a diagram illustrating an example of a downlink channel within a subframe according to various aspects of the present disclosure.

[0015] Figure 3C FIG. is an illustration showing an example of a second frame according to various aspects of the present disclosure.

[0016] Figure 3D FIG. is an illustration showing an example of an uplink channel within a subframe according to various aspects of the present disclosure.

[0017] Figure 4 FIG. is an illustration showing an example of a base station and a user equipment (UE) in an access network.

[0018] Figure 5 FIG. is an illustration showing an example wireless communication system in which a rate-split multiple access (RSMA) message is divided into a common part and a private part for communication.

[0019] Figure 6 FIG. is an illustration showing an example architecture for the recovery of an RSMA message divided into a common part and a private part upon reception.

[0020] Figure 7 FIG. is an illustration showing an example repetition pattern of an RSMA message including a common part and a private part and a conventional message.

[0021] Figure 8 FIG. is an illustration showing an example call flow diagram of communication of an RSMA message having a repetition of at least one of a common part or a private part of the RSMA message.

[0022] Figure 9 FIG. is a flowchart showing an example of a method for wireless communication at a UE.

[0023] Figure 10 FIG. is a flowchart showing an example of a method for wireless communication at another device.

[0024] Figure 11 FIG. is an illustration showing an example of a hardware implementation of an example device.

[0025] Figure 12 FIG. is an illustration showing another example of a hardware implementation of another example device. DETAILED DESCRIPTION

[0026] The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. For the purpose of providing a thorough understanding of the various concepts, the detailed description includes specific details. However, the concepts and aspects described herein may be practiced without some or all of these specific details. In some instances, well-known structures, components, etc. are shown in block diagram form to avoid obscuring such concepts.

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

[0028] By way of example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in the processing system can execute software. Software should be construed broadly to mean instructions, instruction sets, computer-executable code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, executing threads, procedures, functions, etc., regardless of whether it is referred to in terms of software, firmware, middleware, microcode, hardware description language, or other terms.

[0029] Accordingly, in one or more example embodiments, the described functions can be implemented in hardware, software, or any combination thereof. If implemented in software, the functions can be stored or encoded on a computer-readable medium as one or more instructions or computer-executable code. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the above types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0030] Figure 1FIG. is a diagram illustrating an example of a wireless communication system and an access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a user equipment (UE) 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include macro cells (such as high-power cellular base stations) and / or small cells (such as low-power cellular base stations, including femto cells, pico cells, and micro cells).

[0031] The base station 102 configured for 4G long term evolution (LTE) (collectively referred to as an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN)) may interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). The base station 102 configured for 5G new radio (NR) (which may be collectively referred to as a next generation radio access network (RAN) (NG-RAN)) may interface with the core network 190 via a second backhaul link 134. In addition to other functions, the base station 102 may also perform one or more of the following: transfer of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracing, radio access network information management (RIM), paging, positioning, and delivery of warning messages.

[0032] In some aspects, the base stations 102 may communicate with each other directly or indirectly (e.g., via the EPC 160 or the core network 190) via a third backhaul link 136 (e.g., an X2 interface). The first backhaul link 132, the second backhaul link 134, and the third backhaul link 136 may be wired, wireless, or some combination thereof. At least some of the base stations 102 may be configured for integrated access and backhaul (IAB). Accordingly, such base stations may communicate wirelessly with other base stations (also configured for IAB).

[0033] At least some of the base stations 102 configured for IAB may have a split architecture including multiple units, some or all of which may be collocated or distributed and may communicate with each other. For example, Figure 2 the following illustrates an exemplary decomposed base station 200 architecture that includes at least one of a central unit (CU) 210, a distributed unit (DU) 230, a radio unit (RU) 240, a remote radio head (RRH), a remote unit, and / or another similar unit configured to implement one or more layers of a radio protocol stack.

[0034] Base station 102 can communicate wirelessly with UE 104. Examples of UE 104 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other device with similar functionality. Some of the UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.).

[0035] UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, cell phone, user agent, mobile client, client, or some other suitable term.

[0036] Each base station 102 can provide communication coverage for a corresponding geographic coverage area 110 (which may also be referred to as a "cell"). Potentially, two or more geographic coverage areas 110 may at least partially overlap, or one of the geographic coverage areas 110 may contain another of the geographic coverage areas. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a Home evolved Node B (eNB) (HeNB), which may provide service to a restricted group called a Closed Subscriber Group (CSG).

[0037] The communication link 120 between the base station 102 and the UE 104 may include an uplink (also referred to as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (also referred to as a forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The radio link or wireless link may be on one or more carriers or component carriers (CCs). The base station 102 and / or the UE 104 may use a spectrum with a bandwidth of up to Y MHz per carrier (e.g., Y may be equal to or approximately equal to 5, 10, 15, 20, 100, 400, etc.) allocated in carrier aggregation with a total of up to Yx megahertz (MHz) (e.g., x CCs) for transmission in each direction. These CCs may or may not be adjacent to each other. The allocation of CCs may be asymmetric with respect to the downlink and the uplink (e.g., more or fewer CCs may be allocated to the downlink compared to the uplink).

[0038] The CC may include a primary CC and one or more secondary CCs. The primary CC may be referred to as the primary cell (PCell), and each secondary CC may be referred to as a secondary cell (SCell). When the UE is known to both the base station at the access network level and at least one core network entity at the core network level (e.g., the AMF and / or the MME), and the UE can be configured to receive downlink control information in the access network (e.g., the UE may be in the RRC connected state), the PCell may also be referred to as the "serving cell". In some instances where carrier aggregation is configured for the UE, each of the PCell and one or more SCells may be a serving cell.

[0039] Certain UEs 104 may use device-to-device (D2D) communication links 158 to communicate with each other. The D2D communication link 158 may use the downlink / uplink WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as the physical sidelink broadcast channel (PSBCH), the physical sidelink discovery channel (PSDCH), the physical sidelink shared channel (PSSCH), and the physical sidelink control channel (PSCCH). D2D communication may be through various wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

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

[0041] The small cell 102' may operate in licensed and / or unlicensed spectrums. When operating in an unlicensed spectrum, the small cell 102' may adopt NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as that used by the Wi-Fi AP 150. The small cell 102' adopting NR in an unlicensed spectrum may enhance the coverage of the access network and / or increase the capacity of the access network.

[0042] The electromagnetic spectrum is generally subdivided into various categories, frequency bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating frequency bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Although a part of FR1 is greater than 6 GHz, in various documents and articles, FR1 is generally (interchangeably) referred to as the "sub-6 GHz" band. Similar naming issues sometimes occur with respect to FR2. Although different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) identified by the International Telecommunication Union (ITU) as the "millimeter wave" (or "mmWave" or simply "mmW") band, FR2 is generally (interchangeably) referred to as the "millimeter wave" in various documents and articles. In some aspects, "mmW" or "near mmW" may additionally or alternatively refer to the 60 GHz frequency range, which may include multiple channels outside 60 GHz. For example, the 60 GHz band may refer to a set of channels spanning from 57.24 GHz to 70.2 GHz.

[0043] According to the above, unless otherwise specifically stated, for the scope used in this article, the terms "sub-6 GHz", "sub-7 GHz", etc. may generally represent frequencies that may be less than 6 GHz, frequencies that may be less than 7 GHz, frequencies within FR1, and / or frequencies that may include mid-band frequencies. In addition, unless otherwise specifically stated, for the scope used in this article, the term "millimeter wave" and other similar references may generally represent frequencies that may include mid-band frequencies, frequencies within FR2, and / or frequencies within the EHF band.

[0044] Base station 102 can be implemented as a macro base station providing a large cell, or can be implemented as a small cell 102' having a small cell coverage area. Some base stations 102 can operate in traditional sub-6 GHz (or sub-7 GHz) spectrum, mmW frequencies, and / or near-mmW frequencies to communicate with UE 104. When such a base station operates at mmW or near-mmW frequencies, the base station can be referred to as an mmW base station 180. The mmW base station 180 can utilize beamforming 186 with the UE 104 to compensate for path loss and short range. The base station 180 and the UE 104 can each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.

[0045] The base station 180 can transmit a beamformed signal to the UE 104 in one or more transmission directions 182. The UE 104 can receive the beamformed signal from the base station 180 in one or more reception directions 184. The UE 104 can also transmit a beamformed signal to the base station 180 in one or more transmission directions. The base station 180 can receive the beamformed signal from the UE 104 in one or more reception directions. One or both of the base station 180 and / or the UE 104 can perform beam training to determine the optimal reception and / or transmission directions of one or both of the base station 180 and / or the UE 104. The transmission direction and the reception direction of the base station 180 can be the same or different. The transmission direction and the reception direction of the UE 104 can be the same or different.

[0046] In various different aspects, one or more of the base stations 102 / 180 can include and / or be referred to as a gNB, B node, eNB, access point, transceiver base station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmission reception point (TRP), or some other suitable term.

[0047] In some aspects, one or more of base stations 102 / 180 may be connected to EPC 160 and may provide a respective access point to EPC 160 for one or more of UEs 104. EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, an MBMS Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. MME 162 may communicate with a Home Subscriber Server (HSS) 174. MME 162 is a control node that processes signaling between UE 104 and EPC 160. Generally speaking, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are passed through Serving Gateway 166, where Serving Gateway 166 is connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP services 176. IP services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switched (PS) streaming service, and / or other IP services. BM-SC 170 may provide functions for MBMS user service configuration and delivery. BM-SC 170 may serve as an entry point for MBMS transmissions from content providers, may be used to authorize and initiate MBMS bearer services in a Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. MBMS Gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area for a particular broadcast service, and may be responsible for session management (start / stop) and for collecting eMBMS-related charging information.

[0048] In some other aspects, one or more of base stations 102 / 180 may be connected to Core Network 190 and may provide a respective access point to Core Network 190 for one or more of UEs 104. Core Network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. AMF 192 may communicate with a Unified Data Management (UDM) 196. AMF 192 is a control node that processes signaling between UE 104 and Core Network 190. Generally speaking, AMF 192 provides Quality of Service (QoS) flow and session management. All user IP packets are passed through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 is connected to IP services 197. IP services 197 may include the Internet, an intranet, IMS, a PS streaming service, and / or other IP services.

[0049] In some aspects, the UE 104 may be configured to receive information on a repetition pattern of at least one of a common part of an RSMA message or a private part of an RSMA message from the base station 102 / 180. The UE 104 may be further configured to receive at least one repetition 198 of at least one of a common part of an RSMA message or a private part of an RSMA message from the base station 102 / 180 after receiving the information configuring the repetition pattern.

[0050] Accordingly, the base station 102 / 180 may be configured to send information on a repetition pattern of at least one of a common part of an RSMA message or a private part of an RSMA message to at least one UE 104. The base station 102 / 180 may also be further configured to send at least one repetition 198 of at least one of a common part of an RSMA message or a private part of an RSMA message to at least one UE 104 according to the repetition pattern.

[0051] Although the present disclosure may focus on 5G NR, the concepts and various aspects described herein may be applicable to other similar fields, such as sixth-generation (6G) technology, 5G Advanced (5G-A), LTE, LTE-Advanced (LTE-A), Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM), and / or other wireless / radio access technologies.

[0052] Figure 2 A diagram illustrating an exemplary decomposed base station 200 architecture is shown. The deployment of a communication system such as a 5G NR system can be arranged in various ways with various components or constituent parts. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, RAN nodes, core network nodes, network elements, or network equipment (such as a base station, or one or more units (or one or more components) performing base station functionality) can be implemented in an aggregated or decomposed architecture. For example, a base station (or network node) can be implemented as an aggregated base station (also referred to as a self-standing base station or a monolithic base station) or a decomposed base station.

[0053] A centralized base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A split base station may be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more CUs, one or more DUs, or one or more RUs. In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0054] Base station type operations or network designs may consider the aggregation characteristics of base station functionality. For example, a split base station may be utilized in an IAB network, an open radio access network (O-RAN, such as a network configuration initiated by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Splitting may include distributing functions across two or more units at various physical locations, as well as virtually distributing the functions of at least one unit, which may enable flexibility in network design. The various units of a split base station or a split RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0055] The split base station 200 architecture may include one or more CUs 210, which may communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 through one or more split base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non RT) RIC 215 associated with a service management and orchestration (SMO) framework 205, or both. The CU 210 may communicate with one or more DUs 230 via a respective midhaul link, such as an F1 interface. The DU 230 may communicate with one or more RUs 240 via a respective fronthaul link. The RU 240 may communicate with a respective UE 104 via one or more radio frequency (RF) access links. In some embodiments, the UE 104 may be served simultaneously by multiple RUs 240.

[0056] Each of the units (i.e., CU 210, DU 230, RU 240, and the near RT RIC 225, non-RT RIC 215, and SMO framework 205) may include one or more interfaces or be coupled to one or more interfaces that are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or the associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via the transmission medium. For example, the units may include a wired interface that is configured to receive or transmit signals to one or more of the other units via a wired transmission medium. Additionally, the units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) that is configured to receive or transmit signals, or both, to one or more of the other units over a wireless transmission medium.

[0057] In some aspects, the CU 210 may host one or more higher layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function may utilize an interface that is configured to communicate signals with other control functions hosted by the CU 210. The CU 210 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU-UP)), control plane functionality (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some embodiments, the CU 210 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface (such as an E1 interface). As needed, the CU 210 may be implemented to communicate with the DU 230 for network control and signaling.

[0058] The DU 230 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 240. In some aspects, the DU 230 may host one or more of the radio link control (RLC) layer, the media access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least partially according to a functional split (such as those defined by the 3rd Generation Partnership Project (3GPP)). In some aspects, the DU 230 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 230 or with control functions hosted by the CU 210.

[0059] Lower layer functionality may be implemented by one or more RUs 240. In some deployments, the RUs 240 controlled by the DU 230 may correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both at least partially based on a functional split (such as a lower layer functional split). In such an architecture, the RUs 240 may be implemented to handle over-the-air (OTA) communication with one or more UEs 104. In some embodiments, the real-time and non-real-time aspects of communicating with the control plane and user plane of the RUs 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration may enable the implementation of the DU 230 and the CU 210 in a cloud-based RAN architecture (such as a vRAN architecture).

[0060] The SMO framework 205 can be configured to support the RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, and these dedicated physical resources can be managed via operation and maintenance interfaces (such as the O1 interface). For virtualized network elements, the SMO framework 205 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) 290) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements can include, but are not limited to, the CU 210, DU 230, RU 240, and the near RT RIC 225. In some specific implementations, the SMO framework 205 can communicate with the hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 211) via the O1 interface. Additionally, in some specific implementations, the SMO framework 205 can communicate directly with one or more RUs 240 via the O1 interface. The SMO framework 205 can also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205.

[0061] The non-RT RIC 215 can be configured to include logical functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and update, or policy-based guidance of applications / features in the near RT RIC 225. The non-RT RIC 215 can be coupled to or communicate with the near RT RIC 225 (such as via the A1 interface). The near RT RIC 225 can be configured to include logical functions that achieve near-real-time control and optimization of RAN elements and resources via an interface (such as via the E2 interface) through data collection and actions, and this interface connects one or more CUs 210, one or more DUs 230, or both, and the O-eNB to the near RT RIC 225.

[0062] In some specific implementations, to generate the AI / ML models to be deployed in the near-RT RIC 225, the non-RT RIC 215 may receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 225 and can be received from non-network data sources or from network functions at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to tune the RAN behavior or performance. For example, the non-RT RIC 215 may monitor the long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions via the SMO framework 205 (such as reconfiguration via O1) or via creating RAN management policies (such as A1 policies).

[0063] Figure 3A is a diagram illustrating an example of a first subframe 300 within the 5G NR frame structure. Figure 3B is a diagram illustrating an example of a downlink channel within a 5G NR subframe 330. Figure 3C is a diagram illustrating an example of a second subframe 350 within the 5G NR frame structure. Figure 3D is a diagram illustrating an example of an uplink channel within a 5G NR subframe 380. The 5G NR frame structure can be frequency division duplex (FDD), where for a specific set of subcarriers (carrier system bandwidth), the subframes within that set of subcarriers are dedicated to either the downlink or the uplink; or it can be time division duplex (TDD), where for a specific set of subcarriers (carrier system bandwidth), the subframes within that set of subcarriers are dedicated to both the downlink and the uplink. In the example provided by Figure 3A and Figure 3C the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly downlink) and subframe 3 is configured with slot format 34 (mostly uplink), where D is downlink, U is uplink, and F is flexibly used between downlink / uplink. Although subframes 3 and 4 are shown with slot formats 34 and 28 respectively, any particular subframe can be configured with any one of the various available slot formats 0 - 61. Slot formats 0 and 1 are full downlink and full uplink respectively. The other slot formats 2 - 61 include a mixture of downlink, uplink, and flexible symbols. The UE is configured to have a slot format by the received slot format indicator (SFI) (dynamically configured by downlink control information (DCI) or semi-statically / statically configured by RRC signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0064] Other wireless communication technologies may have different frame structures and / or different channels. For example, a 10 millisecond (ms) frame can be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. The subframe may also include mini-slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot can include 14 symbols, and for time slot configuration 1, each time slot can include 7 symbols. The symbols on the downlink can be cyclic prefix (CP) orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the uplink can be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the time slot configuration and numerology. For time slot configuration 0, different numerologies μ0 to 4 allow 1, 2, 4, 8, and 16 time slots per subframe, respectively. For time slot configuration 1, different numerologies 0 to 2 allow 2, 4, and 8 time slots per subframe, respectively. Thus, for time slot configuration 0 and numerology μ, there are 14 symbols per time slot and 2 μ time slots per subframe. The subcarrier spacing and symbol length / duration are functions of the numerology. The subcarrier spacing can be equal to 2 μ * 15 kilohertz (kHz), where μ is the numerology from 0 to 4. Thus, the subcarrier spacing for numerology μ = 0 is 15 kHz, and the subcarrier spacing for numerology μ = 4 is 240 kHz. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 3A to 3D An example of time slot configuration 0 with 14 symbols per time slot and numerology μ = 2 with 4 time slots per subframe is provided. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 microseconds (μs). Within a set of frames, there may be one or more different bandwidth parts (BWPs) that are frequency division multiplexed (see Figure 3B ). Each BWP can have a specific numerology.

[0065] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0066] As Figure 3AAs illustrated, some of the REs in the RE carry at least one pilot signal for the UE, such as a reference signal (RS). Broadly, the RS can be used for beam training and management, tracking and positioning, channel estimation, and / or other such purposes. In some configurations, the RS can include at least one demodulation RS (DM-RS) for channel estimation at the UE (designated as R for one particular configuration x , where 100x is the port number, but other DM-RS configurations are possible) and / or at least one channel state information (CSI) RS (CSI-RS). In some other configurations, the RS can additionally or alternatively include at least one beam measurement (or management) RS (BRS), at least one beam refinement RS (BRRS), and / or at least one phase tracking RS (PT-RS).

[0067] Figure 3B Examples of various downlink channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including nine resource element groups (REGs), each REG including four consecutive RES in an OFDM symbol. The PDCCH within a BWP can be referred to as a control resource set (CORESET). Additional BWPs can be located at higher and / or lower frequencies on the channel bandwidth. The primary synchronization signal (PSS) can be in symbol 2 of a particular subframe of the frame. A UE (such as Figure 1 UE 104) can use the PSS to determine subframe / symbol timing and the physical layer identity. The secondary synchronization signal (SSS) can be in symbol 4 of a particular subframe of the frame. A UE (such as Figure 1 UE 104) can use the SSS to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as system information blocks (SIBs)), and paging messages.

[0068] As Figure 3CAs illustrated, some of the REs in the RE carry DM-RS for channel estimation at the base station (for a specific configuration, which is indicated as R, but other DM-RS configurations are possible). The UE can send DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS can be sent in the previous one or two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS can be sent in different configurations. The UE can send a sounding reference signal (SRS). The SRS can be sent in the last symbol of the subframe. The SRS can have a comb structure, and the UE can send the SRS on one of the teeth of the comb. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the uplink.

[0069] Figure 3D Examples of various uplink channels within a subframe of a frame are illustrated. The PUCCH can be located at the position indicated in one configuration. The PUCCH carries uplink control information (UCI), which can include a scheduling request (SR), a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and a hybrid automatic repeat request (HARQ) acknowledgement (ACK) / negative acknowledgement (NACK) feedback. The PUSCH carries data and can additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0070] Figure 4It is a block diagram of the communication between the base station 410 in the access network 400 and the UE 450. In the downlink, IP packets from the EPC 160 can be provided to the controller / processor 475. The controller / processor 475 implements layer 2 (L2) and layer 3 (L3) functionality. L3 includes the RRC layer, and L2 includes the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, the RLC layer, and the Medium Access Control (MAC) layer. The controller / processor 475 provides RRC layer functionality associated with the broadcast of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with the mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0071] The transmit (TX) processor 416 and the receive (RX) processor 470 implement layer 1 (L1) functionality associated with various signal processing functions. L1, which includes the physical (PHY) layer, may include error detection for the transmission channel, forward error correction (FEC) encoding / decoding of the transmission channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 416 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols may then be split into parallel streams. Subsequently, each stream may be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is precoded in space to generate multiple spatial streams. Channel estimates from the channel estimator 474 may be used to determine the encoding and modulation schemes, as well as for spatial processing. The channel estimates may be derived from reference signals transmitted by the UE 450 and / or channel state feedback. Each spatial stream may then be provided to a different antenna 420 via a separate transmitter 418TX. Each transmitter 418TX may modulate a radio frequency (RF) carrier using the corresponding spatial stream for transmission.

[0072] At the UE 450, each receiver 454RX receives signals via at least one corresponding antenna 452. Each receiver 454RX recovers the information modulated onto the RF carrier and provides the information to the receive (RX) processor 456. The TX processor 468 and the RX processor 456 implement L1 functionality associated with various signal processing functions. The RX processor 456 may perform spatial processing on the information to recover any spatial streams destined for the UE 450. If multiple spatial streams are destined for the UE 450, they may be combined by the RX processor 456 into a single OFDM symbol stream. The RX processor 456 then uses a fast Fourier transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency-domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 410. These soft decisions may be based on the channel estimates computed by the channel estimator 458. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by the base station 410 on the physical channel. The data and control signals are then provided to the controller / processor 459, which implements L3 and L2 functionality.

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

[0074] Similar to the functionality described in connection with downlink transmissions performed by the base station 410, the controller / processor 459 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with the mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0075] Channel estimates derived by the channel estimator 458 based on reference signals or feedback transmitted by the base station 410 may be used by the TX processor 468 to select appropriate decoding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 468 may be provided to different antennas 452 via a separate transmitter 454TX. Each transmitter 454TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0076] Uplink transmissions are processed at the base station 410 in a manner similar to that described in connection with the receiver functionality at the UE 450. Each receiver 418RX receives signals via at least one corresponding antenna 420. Each receiver 418RX recovers the information modulated onto the RF carrier and provides the information to the RX processor 470.

[0077] The controller / processor 475 may be associated with a memory 476 that stores program code and data. The memory 476 may be referred to as a computer-readable medium. On the uplink, the controller / processor 475 provides demultiplexing between the transport channel and the logical channel, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the UE 450. The IP packets from the controller / processor 475 may be provided to the EPC 160. The controller / processor 475 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operations.

[0078] In some aspects, at least one of the TX processor 468, the RX processor 456, and the controller / processor 459 may be configured to perform aspects related to at least one repetition 198 of at least one of the common part of the RSMA message and the private part of the RSMA message related to Figure 1 ...

[0079] In some other aspects, at least one of the TX processor 416, the RX processor 470, and the controller / processor 475 may be configured to perform aspects related to at least one repetition 198 of at least one of the common part of the RSMA message and the private part of the RSMA message related to Figure 1 ...

[0080] Reference Figures 5 to 12 ... illustrates and describes various concepts and aspects related to RSMA message transmission in radio access and other wireless networks. RSMA is a non-orthogonal multiple access scheme in which UEs can be scheduled on the same set of time and frequency resources. That is, a transmitter (e.g., a base station or other network node) can superimpose different messages on different UEs on the same set of resources. In doing so, greater degrees of freedom and increased channel capacity can be achieved, for example, for broadcast channels, multicast channels, and other channels.

[0081] Broadly speaking, RSMA includes splitting each message intended for an individual UE into two parts: a common part and a private part. The common parts of the individual messages of at least two UEs are concatenated into a common message that is sent in a common stream to at least two UEs. However, the private parts of the individual messages are separately encoded and modulated into private streams for transmission to the corresponding UEs.

[0082] At the receiver, a UE can first decode the common message to obtain a part of the individual message intended for the UE. The UE can use the common message to perform successive interference cancellation (or another joint decoding technique) such that the UE can decode the private part of the individual message. In effect, the UE partially decodes some of the interference while treating the remaining interference as noise.

[0083] The successful decoding of the common and individual parts of individual messages depends on a clean channel estimate. In particular, the clean channel estimate can significantly factor into successive interference cancellation, which predicts the recovery of the private parts of individual messages. For example, since successive interference cancellation for recovering the private parts of individual messages depends on a clean channel estimate, failure to obtain such a channel estimate (e.g., due to imperfect or incorrect channel state information at the transmitter) can frustrate the recovery of individual messages.

[0084] In view of the foregoing, there is a need for enhancing the reliability of RSMA message reception and transmission when channel estimation fails. The present disclosure provides various techniques and methods for repeating at least a portion of the common and / or private parts of individual messages. Such repetition can improve reliability and / or reduce the latency experienced by RSMA message reception and transmission. For example, in the case where a UE fails to successfully decode an initial transmission of the common part of an individual message, repetition of the common part of the individual message can enable successive interference cancellation for recovering the common part of the individual message. In another example, repetition of the private part of an individual message can allow successful recovery of the private part when the initial transmission of the private part is not successfully decoded. Various other concepts and aspects related to RSMA message reception and transmission are described herein.

[0085] Figure 5 FIG. is an illustration of an example wireless communication system 500 in which RSMA messages are partitioned into a common part and a private part for communication. In some aspects, the transmitter 502 may be implemented as a base station or other network node. However, in some other aspects, the transmitter 502 may be implemented as a UE, such as a UE configured for D2D communication. In some aspects, each of the receivers 504a, 504b may be implemented as a UE.

[0086] As illustrated, the transmitter 502 may have multiple messages W1 and W2 to be sent to multiple receivers 504a, 504b. The transmitter 502 may schedule the individual messages W1 and W2 for the receivers 504a, 504b on the same set of resources. The transmitter 502 may include a first message splitter 512a that splits the first individual message W1 into a common part W 1,c and a private part W 1,p and a second message splitter 512b that splits the second individual message W2 into a common part W 2,c and a private part W 2,p . At the combiner 514 of the transmitter 502, the common parts W 1,c and W 2,c of the respective individual messages W1 and W2 may be concatenated into a common message W c .

[0087] The transmitter 502 may also include a first encoder 516a configured to encode the private part W of the first individual message W1 separately, a second encoder 516b configured to encode the common message W 1,p separately, and a third encoder 516c configured to encode the private part W of the second individual message W2 separately. The first encoder 516a and the third encoder 516c encode the private part W of the first individual message W1 c and the private part W of the second individual message W2 respectively, and modulate those private parts W 2,p onto a first private stream X1 or a second private stream X2, and map the first private stream X1 and the second private stream X2 to one or more layers. Similarly, the second encoder 516b encodes the common message W 1,p separately, and modulates the encoded common message W 2,p onto a common stream Xc, and maps the common stream Xc to one or more layers. 1,p 、W 2,p onto a first private stream X1 or a second private stream X2, and map the first private stream X1 and the second private stream X2 to one or more layers. Similarly, the second encoder 516b encodes the common message W c separately, and modulates the encoded common message W c onto a common stream Xc, and maps the common stream Xc to one or more layers.

[0088] The common stream Xc and the two private streams X1 and X2 are supplied to a pre - decoder 518. The pre - decoder 518 pre - decodes the common stream X c through P c . Similarly, the pre - decoder 518 pre - decodes the private streams X1 and X2 through P1 and P2 respectively. The transmitter 502 may send the message stream X to the receivers 504a, 504b, where the message stream X includes the pre - decoded common stream P c X c and the pre - decoded first private stream P1X1 and second private stream P2X2 (i.e., X = P c X c + P1X1 + P2X2).

[0089] The message stream X may reach the first receiver 504a through the first channel H1. Thus, the first receiver 504a may observe the message stream as Y1 = H1P c X c + H1P1X1 + H1P2X2 + N1, where N1 is the noise at the first receiver 504a. Similarly, the message stream X may reach the second receiver 504b through the second channel H2. Thus, the second receiver 504b may observe the message stream as Y2 = H2P c X c + H2P1X1 + H1P2X2 + N2, where N2 is the noise at the second receiver 504b.

[0090] Figure 6Is an example for being divided into a common part W upon reception 1,c And a private part W 1,p Of the RSMA message W1 of the exemplary architecture 600 for recovery. The receiver 604 that can be implemented as a UE can receive the RSMA message Y1 through the wireless channel H1, and the RSMA message Y1 includes the pre-coded common stream P c X c , the pre-coded private stream P1X1 intended for the receiver 604, and at least one other pre-coded private stream P2X2 intended for another receiver. The receiver 604 can further receive the RSMA message Y1 with some noise N1.

[0091] The receiver 604 can include a first channel estimator 612 configured to estimate the effective channel H1P corresponding to the common stream X c Of c . In addition, the receiver 604 can include a first decoder 614a configured to decode the common stream X c To recover the common message W c .

[0092] The receiver 604 can use the decoded common message W for at least two purposes c . First, the receiver 604 can identify the common part W of the individual message W1 that is intended for the receiver 604 in the decoded common message W c . The common part W of the individual message W1 1,c Can include some data intended for the receiver 604. However, to recover the complete individual message W1, the receiver 604 combines the common part W 1,c With the private part W 1,c . The second use of the common message W 1,p Is to decode the private part W of the individual message W1 by using successive interference cancellation of the effective channel estimation corresponding to the common stream H1P c . c Of 1,p .

[0093] The receiver 604 can include a reconstructor 616 configured to reconstruct the common stream X c . The reconstructor 616 can be configured to re-encode the common message W c Into the common stream X c . The reconstructor 616 can be further configured to multiply the reconstructed common stream X c With the estimated effective channel H1P corresponding to the common stream X c Of c .

[0094] The receiver 604 may also include a subtractor 618 configured to subtract the product of the estimated effective channel H1P c and the common stream X c from the received signal Y1. The subtractor may output the difference between the received signal Y1 and the product of the estimated effective channel H1P c and the common stream X c —i.e., Y1 - H1P c X c . The difference output by the subtractor 618 may correspond to the received private stream Y 1,p included in the received signal Y1, i.e., Y 1,p = Y1 - H1P c X c = H1P1X1 + H2P2X2 + N1, provided that the channel estimation is accurate enough and the decoding of the common message W c is successful.

[0095] Additionally, the receiver 604 may include a second decoder 614b configured to decode the received private stream Y 1,p . The second decoder 614b may output the decoding result of Y 1,p , which may correspond to the private part W 1,p of the individual message W1 (e.g., given a satisfactory channel estimation and the decoding of the common message W c ).

[0096] The receiver 604 may combine the common part W 1,c with the private part W 1,p in order to recover the individual message W1. As is apparent from the above, an accurate estimate of the effective channel H1P c for the common stream X c can increase the probability of successfully decoding the common message W c and enable the common message W c to be reconstructed accurately enough for successive interference cancellation. Thus, an accurate estimate of the effective channel H1P c for the common stream X c is a necessary condition (although not sufficient by itself) for successfully recovering the private part W 1,p and ultimately the individual message W1.

[0097] There is a possibility that the estimation of the effective channel fails or is inaccurate enough to prohibit successive interference cancellation, based on which successive interference cancellation predicts the recovery of the private part of an individual RSMA message. According to various aspects of the present disclosure, the potential failure of the recovery of the private part of an individual message can be mitigated by the repetition of at least a portion of the individual message.

[0098] In some aspects of the aspects described herein, a transmitter may be configured to transmit at least two instances of a common portion of an RSMA message (e.g., one instance may be an initial transmission of the common portion of the RSMA message, and another instance may be a retransmission of the initial transmission of the common portion of the RSMA message). The repetition of the common portion of the RSMA message may provide the receiver with some additional opportunities to accurately estimate the effective channel and / or reconstruct the common stream that is subtracted from the received signal carrying the common stream and at least two private streams.

[0099] In some other aspects described herein, a transmitter may be configured to transmit at least two instances of a private portion of an individual message (e.g., one instance may be an initial transmission of the private portion of the RSMA message, and another instance may be a retransmission of the initial transmission of the private portion of the RSMA message). Thus, if the receiver fails to recover the private portion of the individual message, there may be additional opportunities to do so.

[0100] In additional aspects, the repetition pattern may include the repetition of both the common portion and the private portion of the RSMA message. For example, each of the common portion and the private portion of the RSMA message may be transmitted at least twice.

[0101] Similar to the common portion and / or private portion of the RSMA message, some data transmitted to a UE in a traditional message (e.g., a message transmitted using an orthogonal multiple access scheme) may also be transmitted repeatedly. The repetition pattern to be applied to the traditional message may be configured in the same manner as RSMA message transmission and / or using the same signaling as RSMA message transmission.

[0102] Figure 7 FIG. 700 is a diagram illustrating an example repetition pattern for an RSMA message 712 including a private portion 714 and a common portion 716, as well as a traditional message 718. The traditional message 718 may be a message to which rate splitting is not applied. For example, the traditional message 718 may be any message not conveyed via rate splitting, such as some messages between a base station (e.g., gNBs) and a UE and some messages between UEs on a sidelink channel.

[0103] According to various aspects of the present disclosure, "slot aggregation" may refer to a configuration in which multiple time slots are aggregated together for communication between a UE and a network node. For example, a network node may configure downlink transmissions on a PDSCH in multiple time slots, where one DCI is used to schedule the multiple time slots. At least a portion of the downlink transmission may be repeated in those multiple PDSCH time slots. For example, the same TB may be repeated within each symbol allocation of each of the aggregated time slots, where the PDSCH is restricted to a single transmission layer.

[0104] The aggregation factor can be configured for the UE, for example, via RRC signaling received from a network node. The aggregation factor can indicate the number of consecutive time slots aggregated together (e.g., two, four, or eight). For example, time slot aggregation on the PDSCH can be configured at least in part by the RRC parameter pdsch-AggregationFactor in the pdsch-config information element (IE).

[0105] Wherein the symbol at which the downlink transmission starts in each of the plurality of aggregated time slots and the number of consecutive symbols spanned by the downlink transmission in each of the plurality of aggregated time slots can be conveyed via a start and length indicator value (SLIV), which can be applied in different functions to derive both the start symbol index and the number of consecutive symbols. The same SLIV can be applied across all aggregated time slots.

[0106] In some aspects, an error correction code can be applied to one or both of a common stream and / or a private stream that separately carry a common part and a private part of an individual message. The error correction code can implement incremental redundancy across aggregated time slots, where a cyclic buffer indicates how many bits the decoder must decode for a codeword. The cyclic buffer can include different redundancy versions (RVs) to indicate where in the encoded message the bits of the codeword start, and four different RVs can be defined with respect to the cyclic buffer. For example, RV0 can indicate that the codeword starts at bit zero (0) of the encoded message, RV1 can indicate that the codeword starts at approximately one quarter of the way through the encoded message, RV2 can indicate that the codeword starts at approximately half of the way through the encoded message, and RV3 can indicate that the codeword starts at approximately five sixths of the way through the encoded message. The initial transmission can be sent according to RV0, and when the end of the encoded message is reached for RV1, RV2, and RV3, the bits of the encoded message can wrap around to bit zero (0) of the encoded message (e.g., wrap around based on the cyclic buffer).

[0107] In some aspects of time slot aggregation, the RV to be applied at the nth transmission occasion of the TB is given according to Table 1 below, where n = 0, 1,..., pdsch-AggregationFactor – 1, and for a PDSCH scheduled without a corresponding PDCCH transmission using sps-Config and activated by DCI format 1_1 or 1_2, "rv indicated by the DCI scheduling the PDSCH" in Table 1 is assumed to be zero (0). id ”

[0108]

[0109] Table 1

[0110] When the pdsch-AggregationFactor parameter is configured in the pdsch-config IE, the SLIV for all aggregated slots may be the same. A transmitter (eg, a network node or another UE) may sequentially read the coded bits from the data buffer based on the RV order given in Table 1.

[0111] In some aspects, the UE may find the DCI for the scheduled PDSCH carrying RSMA messaging in the search space of the CORESET. The CORESET may be configured for the UE via a pdcch-Config IE that includes a ControlResourceSet field with a frequencyDomainResources parameter specifying the frequency resources assigned to the UE in the BWP (e.g., corresponding to the L1 parameter CORESET-freq-dom) and a duration parameter specifying the contiguous time duration of the CORESET in number of symbols.

[0112] Similarly, the search space may be configured for the UE via the SearchSpace field included in the pdcch-Config IE. The SearchSpace field may include: a controlResourceSetId parameter indicating a CORESET applicable to the search space; a monitoringSlotPeriodicityAndOffset parameter indicating a time slot for PDCCH monitoring configured as periodicity and offset (e.g., corresponding to the L1 parameters Monitoring-periodicity-PDCCH-slot and Monitoring-offset-PDCCH-slot, respectively); and a monitoringSymbolsWithinSlot parameter indicating symbols used for PDCCH monitoring in a time slot configured for PDCCH monitoring, as indicated via the aforementioned monitoringSlotPeriodicityAndOffset parameter (e.g., a value of

[0113] '1000000000000' may indicate that the UE should start searching from the first OFDM symbol of the PDCCH slot, a value of '0100000000000' may indicate that the UE should start searching from the second OFDM symbol of the PDCCH slot, etc.).

[0114] Some devices configured to communicate in various RANs and other wireless communication networks may be configured to implement diversity in the frequency domain and / or time domain according to various schemes. For example, some devices configured to communicate in a 5G NR network with Release 15 capabilities or Release 16 capabilities may implement frequency-domain diversity through non-contiguous RBs within a relatively wide BWP; however, frequency hopping (e.g., on the downlink) may be incompatible. Similarly, some devices configured to communicate in a 5G NR network with Release 15 capabilities or Release 16 capabilities may implement time-domain diversity through multi-slot aggregation (e.g., on the PDSCH), such as multi-slot repetition across a specific number of consecutive time slots (e.g., two time slots, four time slots, or eight time slots as configured by the pdsch-AggregationFactor parameter) on the same symbol allocation.

[0115] The above techniques and mechanisms can be applied to RSMA messaging, which can increase throughput, reduce latency, and improve reliability. When an RSMA message is split into a common part and a private part, repetition can be applied to only the common part, only the private part, or both the common part and the private part. In some aspects where both the common part and the private part of an individual message are repeated, the repetition pattern can be configured to include repetition of each of the common part and the private part of the individual message. In some aspects, the repetition factor (i.e., the number of repetitions) of the private part can be the same as or different from the repetition factor of the common part. That is, the private part can have a repetition factor X, while the common part can have a repetition factor Y, and X and Y can be equal or unequal.

[0116] In some aspects, the repetition pattern applied to the common part of an individual message and / or the private part of an individual message can be based on the respective priority or QoS of the common part and / or the private part. The priority or QoS of the common part or the private part can be related to the priority or QoS of the part of the individual message from which the individual message is derived. For example, if an individual message is associated with a relatively high priority or QoS, such as for ultra-reliable low-latency communication (URLLC), then the common part and / or the private part into which the individual message is divided can also be associated with a relatively high priority. In another example, a common message used for control signaling and / or carrying information for multiple UEs can be associated with a relatively high priority or QoS, for example because a larger number of UEs can benefit from the reliability of such a common message. Correlatively, a common message carrying information for only one UE and / or lacking any control signaling can be associated with a relatively low priority.

[0117] As illustrated by example repetition pattern 700, the rate-split individual message 712 may occupy one or more symbols of two time slots 722, 724. In one example, the private part 714 of the individual message 712 may be associated with a relatively higher priority or QoS than the common part 716. Thus, the repetition pattern 700 may include a greater number of repetitions for the private part 714 compared to the common part 716. For example, the repetition pattern 700 may be configured to include one or more symbols of three consecutive time slots 726, 728, 730 after the individual message 712. Given the relatively low priority and / or QoS of the common part 716, the repetition pattern of the common part 716 may be configured to include one or more symbols of two consecutive time slots 732, 734 after the time slots 726, 728, 730 occupied by the private part 714.

[0118] In some aspects, messages may be exchanged without rate splitting. Such messages may be referred to as "legacy" messages. Illustratively, some messages sent on the sidelink channel between a network node (e.g., gNB) and a UE may not employ rate splitting for downlink messages and / or uplink. However, legacy message 718 may be included as part of the repetition pattern 700. For example, legacy message 718 may occupy any remaining time slots (e.g., in a set of aggregated time slots) not occupied by the common and private parts of the message and their repetitions. In the illustrated aspect, legacy message 718 may occupy the last time slot 736 after the individual message 712 occupies time slots 722, 724, the private part 714 occupies time slots 726, 728, 730, and the common part 716 occupies time slots 732, 734.

[0119] In some aspects, the repetition factor of legacy message 718 may be the same as or different from the repetition factor of the private part 714 and / or the repetition factor of the common part 716. That is, the legacy message may be configured to have a repetition factor Z, and Z may be equal to or not equal to the repetition factor X of the private part 714 and / or the repetition factor Y of the common part 716. Each of the repetition factors X, Y, and Z may be configured via at least one of L1 signaling, L2 signaling, or L3 signaling. For example, a network node may configure at least one of X, Y, and / or Z and send an indication of at least one of X, Y, and / or Z via a MAC control element (CE), an RRC signaling message, a DCI message, and / or another L1 message, L2 message, or L3 message.

[0120] Figure 8 is a call flow diagram illustrating an example of a communication flow 800 of RSMA message reception and transmission that exemplifies repetition of at least one of a common part 826 or a private part 828 of an RSMA message 824. In some aspects, the transmitter 802 may be implemented as a base station, such as Figure 1Base station 102 / 180 or Figure 4 Base station 410, or a similar network node such as Figure 5 Transmitter 502. In some other aspects, transmitter 802 may be implemented as a UE, such as Figure 1 AP UE 104 or Figure 4 UE 450. Receiver 804 may be implemented as Figure 1 UE 104, Figure 4 UE 450, Figure 5 One of receivers 504a, 504b or Figure 6 At least one of receivers 604.

[0121] Transmitter 802 may configure a repetition pattern 822 for receiver 804, which repetition pattern includes multiple repetitions of at least one of a common part 826 and / or a private part 828 of RSMA message 824. For example, repetition pattern 822 may be configured across a set of aggregated consecutive time slots, and the repetition pattern may define which of the aggregated consecutive time slots include repetitions of the common part 826 of RSMA message 824 and / or which of the aggregated consecutive time slots include repetitions of the private part 828 of RSMA message 824. The RV may indicate the positioning of the repetition of the common part 826 or the private part 828 within the cyclic buffer.

[0122] Transmitter 802 may configure a repetition factor for one or more of the common part 826 and / or the private part 828 of RSMA message 824. In some aspects, transmitter 802 may further configure a repetition factor for a legacy message. For example, transmitter 802 may do at least one of the following: configure a repetition factor X for the private part 828 of RSMA message 824, configure a repetition factor Y for the common part 826 of the RSMA message, and / or configure a repetition factor Z for a legacy message.

[0123] Transmitter 802 may send information configuring a repetition pattern 822 of at least one of the common part 826 or the private part 828 of RSMA message 824 to at least one receiver 804. Transmitter 802 may send the information configuring repetition pattern 822 via at least one of L1 signaling, L2 signaling, and / or L3 signaling. For example, transmitter 802 may send the information configuring repetition pattern 822 via at least one of a DCI message, an RRC signaling message, a MAC CE, and / or another L1 signaling message, L2 signaling message, and / or L3 signaling message. In some aspects, the information configuring the repetition pattern may include information configuring at least one of an aggregation factor for time slot aggregation (e.g., pdsch - AggregationFactor), a CORESET, and / or a search space.

[0124] In some aspects, the transmitter 802 may configure the repetition pattern based on at least one of a priority or a QoS associated with at least one of a common part of the RSMA message or a private part of the RSMA message. In some aspects (such as those in which the transmitter 802 is implemented as a UE), at least one of the priority or the QoS may be indicated in sidelink control information (SCI), which may be carried on a sidelink channel (e.g., PSCCH). For example, the SCI may include a field associated with the priority, and such field may be filled with a value indicating the priority of the common part 826 and / or a value indicating the priority of the private part 828. In some other aspects, the repetition pattern may be based on whether the common part 826 of the RSMA message 824 includes control information and / or whether the common part 826 of the RSMA message 824 includes information for multiple receivers.

[0125] The receiver 804 may receive information configuring the repetition pattern 822 from the transmitter 802. The receiver 804 may derive a set of resources to monitor for repetitions of the common part 826 and / or the private part 828 of the message 824 based on the information configuring the repetition pattern 822. For example, the receiver 804 may derive an aggregation factor indicating which time slots include repetitions of the common part 826 and / or the private part 828 of the message 824, and the receiver 804 may derive a repetition factor indicating how many time slots include repetitions of the common part 826 of the message 824 and / or how many time slots include repetitions of the private part 828.

[0126] In some aspects, the transmitter 802 may set an RSRP threshold associated with at least one of a first priority of the common part 826 of the RSMA message 824, a second priority of the private part 828 of the RSMA message 824, or a third priority of another message. For example, when the transmitter 802 is implemented as a UE, the transmitter 802 may sense the medium for sidelink sensing operations to determine whether to transmit. The transmitter 802 may set the RSRP threshold based on the highest priority among the common part 826 and the private part 828 of the RSMA message 824 to be transmitted by the transmitter 802 and the priority of the sidelink transmission of the reserved medium. For example, the transmitter 802 may detect a sidelink transmission of the reserved medium associated with a lower priority, while each of the common part 826 and the private part 828 of the RSMA message 824 to be transmitted by the transmitter 802 may be associated with a higher priority. Based on the compared lower priority and higher priority, the transmitter 802 may configure the RSRP threshold to be relatively higher compared to the case where the sidelink transmission of the reserved medium is associated with a higher priority. In other words, the priority of another sidelink transmission of the reserved medium may be inversely proportional to the RSRP threshold - for example, the higher the priority of another sidelink transmission, the lower the transmitter 802 may set the RSRP threshold to avoid interfering with higher priority transmissions.

[0127] The transmitter 802 may send the RSMA message 824 (e.g., as described above with respect to Figure 5 to at least one receiver 804, which is divided into a common part 826 and a private part 828. Additionally, the transmitter 802 may send at least one repetition 830 of at least one of the common part 826 of the RSMA message 824 or the private part 828 of the RSMA message 824 to at least one receiver 804 according to a repetition pattern. In some aspects where the transmitter 802 is implemented as a UE, when at least one of the common part 826 of the RSMA message 824 and / or the private part 828 of the RSMA message 824 is scheduled via multiple configured grants, the transmitter 802 may send the common part 826 of the RSMA message 824 and the private part 828 of the RSMA message 824 on a sidelink channel in one of the same logical channel group or different logical channel groups.

[0128] In some aspects in which the transmitter 802 is implemented as a UE, the transmitter 802 may perform a sidelink sensing procedure to sense the medium before transmission. For example, the transmitter 802 may measure the energy or power on the resources of the sidelink channel, and the transmitter 802 may compare the value obtained from the measured energy or power with an RSRP threshold. In the case where the value fails to meet the RSRP threshold (e.g., the value is less than the RSRP threshold), the transmitter 802 may continue to transmit at least one repetition 830 of at least one of the common part 826 of the RSMA message 824 or the private part 828 of the RSMA message 824 according to a repetition pattern. However, in the case where the value meets the RSRP threshold (e.g., the value is greater than or equal to the RSRP threshold), the transmitter 802 may avoid transmitting at least one repetition of at least one of the common part 826 of the RSMA message 824 or the private part 828 of the RSMA message 824 according to a repetition pattern. For example, the transmitter 802 may back off from transmission for a certain period of time, and / or the transmitter 802 may sense the medium until energy or power that does not meet the RSRP threshold is measured.

[0129] The receiver 804 may receive the common part 826 and the private part 828 of the RSMA message 824 and / or one or more repetitions thereof. The receiver 804 may attempt to recover the RSMA message 824 using the common part 826 and the private part 828 of the RSMA message 824 and / or one or more repetitions thereof (e.g., as described above with respect to Figure 6 .

[0130] However, the receiver 804 may not successfully recover the RSMA message 824. For example, the receiver 804 may fail to successfully receive the common part 826 and / or the private part 828 and / or one or more repetitions 830 thereof. In some aspects, the receiver 804 may send a request 832 to the transmitter 802 for at least one additional repetition of at least one of the common part 826 of the RSMA message 824 or the private part 828 of the RSMA message 824. In some aspects, the request 832 may indicate a repetition factor for at least one additional repetition of at least one of the common part 826 of the RSMA message 824 or the private part 828 of the RSMA message 824. In some aspects, the receiver 804 may multiplex the request 832 with a HARQ feedback message. For example, a request for at least one additional repetition of the common part 826 of the RSMA message 824 may be multiplexed with a HARQ NACK for the common part 826 of the RSMA message 824. In some aspects, the transmitter 802 may allocate a set of periodic resources for such requests, and the receiver 804 may send the request 832 on the allocated set of periodic resources. The set of periodic resources may be scheduled to occur after a repetition of the common part 826 and / or the private part 828 of the RSMA message 824, which may provide the receiver 804 with sufficient time to perform a CRC check on the common and private messages and determine whether those CRC checks fail, in which case, another repetition may be requested or conveyed.

[0131] The transmitter 802 may receive the request 832, and based thereon, the transmitter 802 may send at least one additional repetition 834 of at least one of the common part 826 of the RSMA message 824 or the private part 828 of the RSMA message 824 to at least one receiver 804. The transmitter 802 may configure the number of additional repetitions 834 according to the repetition factor indicated by the request 832.

[0132] The receiver 804 may receive at least one additional repetition 834 of the common part 826 and / or the private part 828. Using the at least one additional repetition 834, the receiver 804 may recover the RSMA message 824 that the receiver 804 may not have successfully recovered before requesting the additional repetition 834.

[0133] Figure 9 is a flowchart of a wireless communication method 900. The method may be performed by a receiver such as a UE (e.g., UE 104, 450), another wireless communication device (e.g., receiver 504a, 504b, 604, 804, or device 1102), or one or more components thereof, or at the receiver, another wireless communication device, or one or more components thereof. According to various aspects, one or more of the illustrated blocks may be omitted, reordered, and / or performed concurrently.

[0134] At 902, the receiver may receive information on a repetition pattern of at least one of a common part of a configured RSMA message or a private part of an RSMA message from a transmitter. In some aspects, the transmitter may be a base station or other network node. In some other aspects, the transmitter may be a UE configured to communicate with the receiver on one or more sidelink channels. In some aspects, the common part of the RSMA message may be common to multiple receivers (e.g., UEs), while the private part of the RSMA message is specific to that receiver. The repetition pattern may indicate at least one of a repetition factor X of the private part of the RSMA message, a repetition factor Y of the common part of the RSMA message, and / or a repetition factor Z of a legacy message.

[0135] The receiver may receive information configuring the repetition pattern via at least one of L1 signaling, L2 signaling, and / or L3 signaling. For example, the receiver may receive information configuring the repetition pattern via at least one of a DCI message, an RRC signaling message, a MAC CE, and / or another L1 signaling message, L2 signaling message, and / or L3 signaling message. In some aspects, the information configuring the repetition pattern may include information configuring at least one of an aggregation factor (e.g., pdsch-AggregationFactor) for slot aggregation, a CORESET, and / or a search space.

[0136] In some aspects, the repetition pattern may be based on at least one of a priority or QoS associated with at least one of a common part of an RSMA message or a private part of an RSMA message. At least one of the priority or QoS may be indicated in an SCI. In some other aspects, the repetition pattern may be based on whether the common part of the RSMA message includes control information and / or whether the common part of the RSMA message includes information for multiple receivers.

[0137] In Figure 7 the context of, for example, the repetition pattern 700 may indicate at least one of a first set of time slots 722, 724 allocated to carry an individual message 712, a second set of time slots 726, 728, 730 allocated to carry the repeated private part 714 of the individual message 712, a third set of time slots 732, 734 allocated to carry the repeated common part 716 of the individual message 712, and / or a fourth set of time slots 736 allocated to carry a legacy message 718. In Figure 8 the context of, for example, the receiver 804 may receive information configuring the repetition pattern 822 from the transmitter 802.

[0138] At 904, after receiving information configuring a repetition pattern, the receiver may receive at least one repetition of at least one of the common part of the RSMA message or the private part of the RSMA message from the transmitter. In some aspects, when the common part of the RSMA message and the private part of the RSMA message are scheduled via multiple configured grants, the common part of the RSMA message and the private part of the RSMA message are received on a sidelink channel in one of the same logical channel group or different logical channel groups.

[0139] In the Figure 7 context of, for example, the receiver may receive one or more repetitions of the private part 714 of the individual message 712 on a set of symbols 726, 728, 730 and / or one or more repetitions of the common part 716 of the individual message 712 on another set of symbols 732, 734. In the Figure 8 context of, for example, the receiver 804 may receive a repetition 830 of at least one of the common part 826 and / or the private part 828 of the RSMA message 824 from the transmitter 802.

[0140] At 906, the receiver may send a request to the transmitter for at least one additional repetition of at least one of the common part of the RSMA message or the private part of the RSMA message. In some aspects, the request may indicate a repetition factor for at least one additional repetition of at least one of the common part of the RSMA message or the private part of the RSMA message. In some aspects, the receiver may multiplex the request with a HARQ feedback message. For example, the receiver may multiplex a request for at least one additional repetition of the common part of the RSMA message with a HARQ NACK for the common part of the RSMA message. In some aspects, a set of periodic resources may be allocated for such requests, and the receiver may send the request on the allocated set of periodic resources. The set of periodic resources may be scheduled to occur after a repetition of the common part and / or the private part of the RSMA message, which may provide the receiver with sufficient time to perform a CRC check on the common and private messages and determine whether those CRC checks fail, in which case another repetition may be requested or conveyed.

[0141] In the Figure 8 context of, for example, the receiver 804 may send a repetition request 832 to the transmitter 802. The repetition request 832 may indicate a request for at least one additional repetition of the common part 826 and / or the private part 828 of the RSMA message 824. Based on the repetition request 832, the receiver 804 may receive at least one additional repetition 834 of the common part 826 and / or the private part 828 of the RSMA message 824 from the transmitter 802.

[0142] Figure 10It is a flowchart of a method 1000 for wireless communication. In some aspects, the method 1000 may be executed by a transmitter such as a base station or a network node (e.g., base station 102 / 180, 410), a UE (e.g., UE 104, 450), another wireless communication device (e.g., transmitter 502, 802, device 1102 or device 1202), or one or more components thereof, or executed at the transmitter, the UE, the other wireless communication device, or one or more components thereof. According to various aspects, one or more of the illustrated blocks may be omitted, swapped, and / or executed concurrently.

[0143] At 1002, the transmitter may send information on a repetition pattern of at least one of a common part of a configured RSMA message or a private part of an RSMA message to at least one receiver. In some aspects, the common part of the RSMA message may be common to multiple receivers (e.g., UEs), while the private part of the RSMA message is specific to the receiver. The repetition pattern may indicate at least one of a repetition factor X of the private part of the RSMA message, a repetition factor Y of the common part of the RSMA message, and / or a repetition factor Z of a legacy message.

[0144] The transmitter may send information configuring the repetition pattern via at least one of L1 signaling, L2 signaling, and / or L3 signaling. For example, the transmitter may send information configuring the repetition pattern via at least one of a DCI message, an RRC signaling message, a MAC CE, and / or another L1 signaling message, L2 signaling message, and / or L3 signaling message. In some aspects, the information configuring the repetition pattern may include information configuring at least one of an aggregation factor (e.g., pdsch - AggregationFactor) for slot aggregation, a CORESET, and / or a search space.

[0145] In some aspects, the repetition pattern may be based on at least one of a priority or QoS associated with at least one of the common part of the RSMA message or the private part of the RSMA message. At least one of the priority or QoS may be indicated in the SCI. In some other aspects, the repetition pattern may be based on whether the common part of the RSMA message includes control information and / or whether the common part of the RSMA message includes information for multiple receivers.

[0146] At Figure 7In the context of, for example, the repeating pattern 700 may indicate at least one of a first set of time slots 722, 724 assigned to carry an individual message 712, a second set of repeating time slots 726, 728, 730 assigned to carry the repeated private part 714 of the individual message 712, a third set of repeating time slots 732, 734 assigned to carry the repeated common part 716 of the individual message 712, and / or a fourth set of time slots 736 assigned to carry a legacy message 718. In Figure 8 In the context of, for example, the transmitter 802 may send information configuring the repeating pattern 822 to the receiver 804.

[0147] At 1004, the transmitter may set an RSRP threshold associated with at least one of a first priority of the common part of the RSMA message, a second priority of the private part of the RSMA message, or a third priority of another message. For example, when the transmitter is implemented as a UE, the transmitter may sense the medium for sidelink sensing operations to determine whether to transmit. The transmitter may set the RSRP threshold based on the highest priority among the common part and the private part of the RSMA message to be transmitted by the transmitter and the priority of the sidelink transmission of the reserved medium. For example, the transmitter may detect a sidelink transmission of the reserved medium associated with a lower priority, while each of the common part and the private part of the RSMA message to be transmitted by the transmitter may be associated with a higher priority. Based on the compared lower priority and higher priority, the transmitter may configure the RSRP threshold to be relatively higher compared to the case where the sidelink transmission of the reserved medium is associated with the higher priority. In other words, the priority of the sidelink transmission of the reserved medium may be inversely proportional to the RSRP threshold - for example, the higher the priority of the other sidelink transmission, the lower the transmitter may set the RSRP threshold to avoid interfering with higher priority transmissions.

[0148] In Figure 8 In the context of, for example, the transmitter 802 may set an RSRP threshold associated with at least one of a first priority of the common part 826 of the RSMA message 824, a second priority of the private part 828 of the RSMA message 824, or a third priority of another message.

[0149] At 1006, the transmitter may send at least one repetition of at least one of the common part of the RSMA message or the private part of the RSMA message to at least one receiver according to the repeating pattern. In some aspects where the transmitter is implemented as a UE, when at least one of the common part of the RSMA message and / or the private part of the RSMA message is scheduled via multiple configured grants, the transmitter may send the common part of the RSMA message and the private part of the RSMA message on a sidelink channel in one of the same logical channel group or different logical channel groups.

[0150] In some aspects where the transmitter is implemented as a UE, the transmitter may perform a sidelink sensing procedure to sense the medium before transmission. For example, the transmitter may measure the energy or power on the resources of the sidelink channel, and the transmitter may compare the value obtained from the measured energy or power with an RSRP threshold. In the case where the value fails to meet the RSRP threshold (e.g., the value is less than the RSRP threshold), the transmitter may continue to transmit at least one repetition of at least one of the common part of the RSMA message or the private part of the RSMA message according to a repetition pattern. However, in the case where the value meets the RSRP threshold (e.g., the value is greater than or equal to the RSRP threshold), the transmitter may avoid transmitting at least one repetition of at least one of the common part of the RSMA message or the private part of the RSMA message according to a repetition pattern. For example, the transmitter may back off from transmitting for a certain period of time, and / or the transmitter may sense the medium until energy or power that does not meet the RSRP threshold is measured.

[0151] In Figure 7 the context of, for example, the transmitter may transmit one or more repetitions of the private part 714 of the individual message 712 on a set of symbols 726, 728, 730 and / or one or more repetitions of the common part 716 of the individual message 712 on another set of symbols 732, 734. In Figure 8 the context of, for example, the transmitter 802 may transmit a repetition 830 of at least one of the common part 826 and / or the private part 828 of the RSMA message 824 to the receiver 804.

[0152] At 1008, the transmitter may receive a request for at least one other repetition of at least one of the common part of the RSMA message or the private part of the RSMA message from at least one receiver. In some aspects, the request may indicate a repetition factor for at least one other repetition of at least one of the common part of the RSMA message or the private part of the RSMA message. In some aspects, the transmitter may receive a request multiplexed with a HARQ feedback message. For example, a request for at least one other repetition of the common part of the RSMA message may be multiplexed with a HARQ NACK for the common part of the RSMA message. In some aspects, the transmitter may allocate a set of periodic resources for such requests, and the transmitter may receive the requests on the allocated set of periodic resources. The set of periodic resources may be scheduled to occur after the repetition of the common part and / or the private part of the RSMA message, which may provide sufficient time for the receiver to perform CRC checks on the common message and the private message and determine whether those CRC checks fail, in which case another repetition may be requested or conveyed.

[0153] In Figure 8In the context of, for example, the transmitter 802 may receive a repeat request 832 from the receiver 804. The repeat request 832 may indicate a request for at least one additional repeat of the common portion 826 and / or the private portion 828 of the RSMA message 824. Based on the repeat request 832, the transmitter 802 may send at least one additional repeat 834 of the common portion 826 and / or the private portion 828 of the RSMA message 824 to the receiver 804.

[0154] At 1010, the transmitter may send at least one additional repeat of at least one of the common portion of the RSMA message associated with the request or the private portion of the RSMA message to at least one receiver.

[0155] In Figure 8 In the context of, for example, the transmitter 802 may receive a repeat request 832 from the receiver 804. The repeat request 832 may indicate a request for at least one additional repeat of the common portion 826 and / or the private portion 828 of the RSMA message 824. Based on the repeat request 832, the transmitter 802 may send at least one additional repeat 834 of the common portion 826 and / or the private portion 828 of the RSMA message 824 to the receiver 804.

[0156] Figure 11 FIG. 1100 is a diagram illustrating an example of a hardware implementation for the apparatus 1102. The apparatus 1102 may be a UE or a similar device, or the apparatus 1102 may be a component of a UE or a similar device. The apparatus 1102 may include a cellular baseband processor 1104 (also referred to as a modem) and / or a cellular RF transceiver 1122, which may be coupled together and / or integrated into the same package, component, circuit, chip, and / or other circuitry.

[0157] In some aspects, the apparatus 1102 may accommodate or may include one or more subscriber identity module (SIM) cards 1120, which may include one or more integrated circuits, chips, or similar circuitry and may be removable or embedded. The one or more SIM cards 1120 may carry identification and / or authentication information, such as an international mobile subscriber identity (IMSI) and / or an IMSI-related key. Additionally, the apparatus 1102 may include one or more of an application processor 1106, a Bluetooth module 1112, a wireless local area network (WLAN) module 1114, a global positioning system (GPS) module 1116, and / or a power source 1118 coupled to a secure digital (SD) card 1108 and a screen 1110.

[0158] The cellular baseband processor 1104 communicates with the UE 104 and / or the base station 102 / 180 via the cellular RF transceiver 1122. The cellular baseband processor 1104 may include a computer-readable medium / memory. The computer-readable medium / memory may be non-transitory. The cellular baseband processor 1104 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 1104, causes the cellular baseband processor 1104 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1104 when executing the software. The cellular baseband processor 1104 further includes a receiving component 1130, a communication manager 1132, and a transmitting component 1134. The communication manager 1132 includes one or more illustrated components. The components within the communication manager 1132 may be stored in the computer-readable medium / memory and / or be configured as hardware within the cellular baseband processor 1104.

[0159] In Figure 4 the context of, the cellular baseband processor 1104 may be a component of the UE 450 and may include at least one of the memory 460 and / or the TX processor 468, the RX processor 456, and / or the controller / processor 459. In one configuration, the device 1102 may be a modem chip and / or may be implemented as the baseband processor 1104, while in another configuration, the device 1102 may be the entire UE (e.g., Figure 4 the UE 450) and may include some or all of the above-described components, circuits, chips, and / or other circuits illustrated in the context of the device 1102. In one configuration, the cellular RF transceiver 1122 may be implemented as at least one of the transmitter 454TX and / or the receiver 454RX.

[0160] The receiving component 1130 may be configured to receive signaling on a wireless channel, such as signaling from a transmitter (e.g., the base station 102 / 180 or the UE 104). The transmitting component 1134 may be configured to transmit signaling on a wireless channel, such as signaling to a transmitter (e.g., the base station 102 / 180 or the UE 104). The communication manager 1132 may coordinate or manage some or all of the wireless communications performed by the device 1102, including wireless communications across the receiving component 1130 and the transmitting component 1134.

[0161] The receiving component 1130 may provide some or all of the data and / or control information included in the received signaling to the communication manager 1132, and the communication manager 1132 may generate and provide some or all of the data and / or control information to be included in the transmitted signaling to the transmitting component 1134. The communication manager 1132 may include various illustrated components, including one or more components configured to process the received data and / or control information and / or one or more components configured to generate data and / or control information for transmission. For example, the communication manager 1132 may include a repetition pattern component 1140, a channel estimation component 1142, and a message recovery component 1144.

[0162] The repetition pattern component 1140 may be configured to receive information on a repetition pattern of at least one of a common part of a configured RSMA message or a private part of an RSMA message from a transmitter, for example, as described in 902 in connection with Figure 9 In some aspects, the transmitter may be a base station 102 / 180 or other network node. In some other aspects, the transmitter may be a UE 104 configured to communicate with a receiver on one or more sidelink channels. In some aspects, the common part of the RSMA message may be common to multiple receivers (including the device 1102), while the private part of the RSMA message may be specific to the device 1102. The repetition pattern may indicate at least one of a repetition factor X of the private part of the RSMA message, a repetition factor Y of the common part of the RSMA message, and / or a repetition factor Z of a legacy message.

[0163] The repetition pattern component 1140 may receive information configuring the repetition pattern via at least one of L1 signaling, L2 signaling, and / or L3 signaling. For example, the repetition pattern component 1140 may receive information configuring the repetition pattern via at least one of a DCI message, an RRC signaling message, a MAC CE, and / or another L1 signaling message, L2 signaling message, and / or L3 signaling message. In some aspects, the information configuring the repetition pattern may include information configuring at least one of an aggregation factor (e.g., pdsch-AggregationFactor) for slot aggregation, a CORESET, and / or a search space.

[0164] In some aspects, the repetition pattern may be based on at least one of a priority or QoS associated with at least one of a common part of the RSMA message or a private part of the RSMA message. At least one of the priority or QoS may be indicated in the SCI. In some other aspects, the repetition pattern may be based on whether the common part of the RSMA message includes control information and / or whether the common part of the RSMA message includes information for multiple receivers.

[0165] After receiving information configuring a repetition pattern, the receiving component 1130 may receive at least one repetition of at least one of the common part of the RSMA message or the private part of the RSMA message from the transmitter, e.g., as described in 904 in connection with Figure 9 When the common part of the RSMA message and the private part of the RSMA message are scheduled via multiple configured grants, in some aspects, the common part of the RSMA message and the private part of the RSMA message are received on a sidelink channel in one of the same logical channel group or different logical channel groups.

[0166] The channel estimation component 1142 may receive the common part of the RSMA message or at least one repetition of the common part via the receiving component 1130. The channel estimation component 1142 may decode the common part of the RSMA message and may use the common part of the RSMA message to estimate the channel.

[0167] The message recovery component 1144 may perform successive interference cancellation based on the channel estimation from the common part of the RSMA message to recover the private part of the RSMA message. The message recovery component 1144 may combine the common part of the RSMA message and the private part of the RSMA message to recover the individual message transmitted by the transmitter.

[0168] However, if the message recovery component 1144 is unable to successfully recover the individual message, additional repetitions of the common part and / or the private part of the message may be requested.

[0169] The transmitting component 1134 may send a request for at least one additional repetition of at least one of the common part of the RSMA message or the private part of the RSMA message to the transmitter, e.g., as described in 906 in connection with Figure 9 In some aspects, the request may indicate a repetition factor for at least one additional repetition of at least one of the common part of the RSMA message or the private part of the RSMA message. In some aspects, the transmitting component 1134 may multiplex the request with a HARQ feedback message. For example, the transmitting component 1134 may multiplex a request for at least one additional repetition of the common part of the RSMA message with a HARQ NACK for the common part of the RSMA message. In some aspects, a set of periodic resources may be allocated for such requests, and the transmitting component 1134 may send the request on the allocated set of periodic resources. The set of periodic resources may be scheduled to occur after the repetition of the common part and / or the private part of the RSMA message, which may provide the message recovery component 1144 with sufficient time to perform CRC checks on the common and private messages and determine whether those CRC checks fail, in which case another repetition may be requested or conveyed.

[0170] The apparatus 1102 may include performingFigure 8 and Figure 9 some or all of the additional components of the boxes, operations, signaling, etc. of the algorithms in the aforementioned call flow diagrams and / or flowcharts of Figure 8 and Figure 9 Some or all of the boxes, operations, signaling, etc. in the aforementioned call flow diagrams and / or flowcharts of

[0171] In one configuration, device 1102 and in particular cellular baseband processor 1104 includes components for receiving information on a repeating pattern of at least one of a common part of a configuration RSMA message or a private part of an RSMA message from the device; and for receiving at least one repetition of at least one of a common part of an RSMA message or a private part of an RSMA message from the device after receiving the information on the configured repeating pattern.

[0172] In one configuration, the common part of the RSMA message is common to multiple UEs, and wherein the private part of the RSMA message is specific to device 1102.

[0173] In one configuration, the repeating pattern is based on at least one of a priority or QoS associated with at least one of a common part of the RSMA message or a private part of the RSMA message.

[0174] In one configuration, at least one of the priority or QoS is included in the SCI.

[0175] In one configuration, the repeating pattern includes at least one of a first repetition factor associated with a common part of the RSMA message or a second repetition factor associated with a private part of the RSMA message.

[0176] In one configuration, the information configuring the repeating pattern is received via at least one of L1 signaling, L2 signaling, or L3 signaling.

[0177] In one configuration, the repeating pattern is based on whether the common part of the RSMA message includes control information.

[0178] In one configuration, when the common part of the RSMA message and the private part of the RSMA message are scheduled via multiple configured grants, the common part of the RSMA message and the private part of the RSMA message are received on a sidelink channel in the same logical channel group or one of different logical channel groups.

[0179] In one configuration, apparatus 1102 and in particular cellular baseband processor 1104 may include components for sending to a transmitter a request for at least one additional repetition of at least one of the common part of the RSMA message or the private part of the RSMA message.

[0180] In one configuration, the request is multiplexed with HARQ feedback.

[0181] In one configuration, the request indicates a repetition factor for at least one additional repetition of at least one of the common part of the RSMA message or the private part of the RSMA message.

[0182] In one configuration, the request is sent on a set of periodic resources allocated for requests for additional repetitions.

[0183] The foregoing components may be one or more of the foregoing components of apparatus 1102 configured to perform the functions recited by the foregoing components. As described above, apparatus 1102 may include TX processor 468, RX processor 456, and controller / processor 459. Thus, in one configuration, the foregoing components may be TX processor 468, RX processor 456, and controller / processor 459 configured to perform the functions recited by the foregoing components.

[0184] Figure 12 FIG. 1200 is a diagram illustrating an example of a hardware implementation for apparatus 1202. Apparatus 1202 may be a base station or similar device or system, or apparatus 1202 may be a component of a base station or similar device or system. Apparatus 1202 may include a baseband unit 1204. The baseband unit 1204 may communicate via a cellular RF transceiver. For example, the baseband unit 1204 may communicate with UE 104 via a cellular RF transceiver (such as for downlink communication and / or uplink communication), and / or with base station 102 / 180 (such as for IAB).

[0185] The baseband unit 1204 may include a computer-readable medium / memory which can be non-transitory. The baseband unit 1204 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the baseband unit 1204, the software causes the baseband unit 1204 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the baseband unit 1204 when executing the software. The baseband unit 1204 further includes a receiving component 1230, a communication manager 1232, and a transmitting component 1234. The communication manager 1232 includes one or more of the illustrated components. The components within the communication manager 1232 can be stored in the computer-readable medium / memory and / or be configured as hardware within the baseband unit 1204. The baseband unit 1204 can be a component of the base station 410 and may include at least one of the memory 476 and / or the TX processor 416, the RX processor 470, and the controller / processor 475.

[0186] The receiving component 1230 can be configured to receive signaling on a wireless channel, such as signaling from a receiver (e.g., UE 104 or base station 102 / 180). The transmitting component 1234 can be configured to transmit signaling on a wireless channel to a receiver (e.g., UE 104 or base station 102 / 180). The communication manager 1232 can coordinate or manage some or all of the wireless communications performed by the device 1202, including the wireless communications across the receiving component 1230 and the transmitting component 1234.

[0187] The receiving component 1230 can provide some or all of the data and / or control information included in the received signaling to the communication manager 1232, and the communication manager 1232 can generate and provide some or all of the data and / or control information to be included in the transmitted signaling to the transmitting component 1234. The communication manager 1232 can include various illustrated components, including one or more components configured to process the received data and / or control information and / or one or more components configured to generate data and / or control information for transmission. In some aspects, the generation of the data and / or control information can include packetizing or otherwise reformatting the data and / or control information received from a core network (such as core network 190 or EPC 160) for transmission.

[0188] The communication manager 1232 may include a pattern generation component 1240, a threshold processing component 1242, a medium sensing component 1244, and / or a rate splitting component 1246. The pattern generation component 1240 may be configured to generate a pattern that specifies a respective repetition factor for at least one of a private portion of an RSMA message, a common portion of an RSMA message, and / or a legacy message (e.g., a message that is not rate split for transmission). The pattern generation component 1240 may be further configured to allocate resources for slot aggregation, which may carry the repetition.

[0189] The transmitting component 1234 may be configured to transmit information configuring a repetition pattern for at least one of the common portion or the private portion of an RSMA message to at least one receiver, e.g., as described in 1002 in connection with Figure 10 The repetition pattern may indicate at least one of a repetition factor X for the private portion of the RSMA message, a repetition factor Y for the common portion of the RSMA message, and / or a repetition factor Z for the legacy message.

[0190] The transmitting component 1234 may transmit the information configuring the repetition pattern via at least one of L1 signaling, L2 signaling, and / or L3 signaling. For example, the transmitting component 1234 may receive the information configuring the repetition pattern via at least one of a DCI message, an RRC signaling message, a MAC CE, and / or another L1 signaling message, L2 signaling message, and / or L3 signaling message. In some aspects, the information configuring the repetition pattern may include information configuring at least one of an aggregation factor (e.g., pdsch-AggregationFactor) for slot aggregation, a CORESET, and / or a search space.

[0191] In some aspects, the repetition pattern may be based on at least one of a priority or QoS associated with at least one of the common portion or the private portion of the RSMA message. At least one of the priority or QoS may be indicated in the SCI. In some other aspects, the repetition pattern may be based on whether the common portion of the RSMA message includes control information and / or whether the common portion of the RSMA message includes information for multiple receivers.

[0192] The threshold processing component 1242 may be configured to set an RSRP threshold associated with at least one of a first priority for the common portion of the RSMA message, a second priority for the private portion of the RSMA message, or a third priority for another message, e.g., as described in connection with Figure 10As described in 1004. For example, when the transmitter is implemented as a UE, the medium sensing component 1244 may sense the medium for sidelink sensing operations to determine whether to transmit. The threshold processing component 1242 may set the RSRP threshold based on the highest priority among the common part and the private part of the RSMA message to be transmitted by the transmission component 1234 and the priority of the sidelink transmission of the reserved medium. For example, the medium sensing component 1244 may detect a sidelink transmission of the reserved medium associated with a lower priority, while each of the common part and the private part of the RSMA message to be transmitted by the transmission component 1234 may be associated with a higher priority. Based on the comparison of the lower priority and the higher priority, the threshold processing component 1242 may configure the RSRP threshold to be relatively higher compared to the case where the sidelink transmission of the reserved medium is associated with a higher priority. In other words, the priority of the other sidelink transmission of the reserved medium may be inversely proportional to the RSRP threshold - for example, the higher the priority of the other sidelink transmission, the lower the threshold processing component 1242 may set the RSRP threshold to avoid interfering with higher priority transmissions.

[0193] The rate splitting component 1246 may be configured to split an individual RSMA message into a common part and a private part. In some aspects, the common part of the RSMA message may be common to multiple receivers (e.g., UEs), while the private part of the RSMA message is specific to that receiver.

[0194] The transmission component 1234 may be configured to transmit at least one repetition of at least one of the common part of the RSMA message or the private part of the RSMA message to at least one receiver according to a repetition pattern, e.g., as described in conjunction with Figure 10 1006. In some aspects where the device 1202 is implemented as a UE, when at least one of the common part of the RSMA message and / or the private part of the RSMA message is scheduled via multiple configured grants, the transmission component 1234 may transmit the common part of the RSMA message and the private part of the RSMA message on a sidelink channel in one of the same logical channel group or different logical channel groups.

[0195] In some aspects in which apparatus 1202 is implemented as a UE, the medium sensing component 1244 may be configured to perform a sidelink sensing procedure to sense the medium before transmission. For example, the medium sensing component 1244 may measure the energy or power on the resources of the sidelink channel, and the medium sensing component 1244 may compare the value obtained from measuring the energy or power with an RSRP threshold. In the case where the value fails to meet the RSRP threshold (e.g., the value is less than the RSRP threshold), the transmitting component 1234 may continue to transmit at least one repetition of at least one of the common part of the RSMA message or the private part of the RSMA message according to a repetition pattern. However, in the case where the value meets the RSRP threshold (e.g., the value is greater than or equal to the RSRP threshold), the transmitting component 1234 may avoid transmitting at least one repetition of at least one of the common part of the RSMA message or the private part of the RSMA message according to a repetition pattern. For example, the transmitting component 1234 may back off from transmitting for a certain period of time, and / or the medium sensing component 1244 may sense the medium until energy or power that does not meet the RSRP threshold is measured.

[0196] The receiving component 1230 may receive a request for at least one other repetition of at least one of the common part of the RSMA message or the private part of the RSMA message from at least one receiver, e.g., as described in 1008 in connection with Figure 10 In some aspects, the request may indicate a repetition factor for at least one other repetition of at least one of the common part of the RSMA message or the private part of the RSMA message. In some aspects, the receiving component 1230 may receive a request multiplexed with a HARQ feedback message. For example, a request for at least one other repetition of the common part of the RSMA message may be multiplexed with a HARQ NACK for the common part of the RSMA message. In some aspects, a set of periodic resources may be allocated for such requests, and the receiving component 1230 may receive the request on the allocated set of periodic resources. The set of periodic resources may be scheduled to occur after the repetition of the common part and / or the private part of the RSMA message, which may provide sufficient time for the receiver to perform CRC checks on the common message and the private message and determine whether those CRC checks fail, in which case another repetition may be requested or conveyed.

[0197] The transmitting component 1234 may transmit at least one other repetition of at least one of the common part of the RSMA message or the private part of the RSMA message associated with the request to at least one receiver, e.g., as described in 1010 in connection with Figure 10 In some aspects, the apparatus 1202 may include performing respectively

[0198] and Figure 8 and Figure 10Additional components of some or all of the boxes, operations, signaling, etc. of the algorithms in the foregoing call flow diagrams and / or flowcharts. Thus, Figure 8 and Figure 10 Some or all of the boxes, operations, signaling, etc. in the foregoing call flow diagrams and / or flowcharts of Figure 10 can be performed by components, and apparatus 1202 can include one or more of those components. These components can be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0199] In one configuration, apparatus 1202 and particularly baseband unit 1204 includes components for sending information on a repetition pattern for at least one of a common part of a configuration RSMA message or a private part of an RSMA message to at least one UE; and components for sending at least one repetition of at least one of a common part of an RSMA message or a private part of an RSMA message to at least one UE according to the repetition pattern.

[0200] In one configuration, the common part of the RSMA message is common to multiple UEs, and wherein the private part of the RSMA message is specific to at least one UE.

[0201] In one configuration, the repetition pattern is based on at least one of a priority or QoS associated with at least one of a common part of the RSMA message or a private part of the RSMA message.

[0202] In one configuration, at least one of the priority or QoS is included in the SCI.

[0203] In one configuration, the repetition pattern includes at least one of a first repetition factor associated with the common part of the RSMA message or a second repetition factor associated with the private part of the RSMA message.

[0204] In one configuration, the information configuring the repetition pattern is sent via at least one of L1 signaling, L2 signaling, or L3 signaling.

[0205] In one configuration, the repetition pattern is based on whether the common part of the RSMA message includes control information.

[0206] In one configuration, when the common part of the RSMA message and the private part of the RSMA message are scheduled via multiple configured grants, the common part of the RSMA message and the private part of the RSMA message are sent on a sidelink channel in one of the same logical channel group or different logical channel groups.

[0207] In one configuration, the apparatus 1202 and particularly the baseband unit 1204 may further include components for receiving from at least one UE a request associated with at least one other repetition of at least one of a common part of an RSMA message or a private part of the RSMA message; and components for transmitting to at least one UE at least one other repetition of at least one of a common part of the RSMA message associated with the request or a private part of the RSMA message.

[0208] In one configuration, the request is multiplexed with HARQ feedback.

[0209] In one configuration, the request indicates a repetition factor of at least one other repetition of at least one of a common part of the RSMA message or a private part of the RSMA message.

[0210] In one configuration, the request is transmitted on a set of periodic resources allocated for requests for other repetitions.

[0211] In one configuration, the apparatus 1202 and particularly the baseband unit 1204 may further include components for setting an RSRP threshold associated with at least one of a first priority of a common part of an RSMA message, a second priority of a private part of the RSMA message, or a third priority of another message.

[0212] In one configuration, the RSRP threshold is set based on the highest priority among the first priority, the second priority, or the third priority.

[0213] The foregoing components may be one or more of the foregoing components of the apparatus 1202 configured to perform the functions recited by the foregoing components. As described above, the apparatus 1202 may include a TX processor 416, an RX processor 470, and a controller / processor 475. Thus, in one configuration, the foregoing components may be the TX processor 416, the RX processor 470, and the controller / processor 475 configured to perform the functions recited by the foregoing components.

[0214] The specific order or hierarchy of the various blocks or operations in each of the above processes, flowcharts, and other diagrams disclosed herein is an illustration of an example method. Based on design preferences, the specific order or hierarchy of the blocks or operations in each of these processes, flowcharts, and other diagrams may be rearranged, omitted, and / or executed concurrently without departing from the scope of the present disclosure. Additionally, some blocks or operations may be combined or omitted. The appended method claims present the elements of the various blocks or operations in an example order and are not meant to be limited to the specific order or hierarchy presented.

[0215] The following examples are merely illustrative and may be combined with aspects of other embodiments or teachings described herein, but are not limited thereto.

[0216] Embodiment 1 is a device configured to: receive information on a repetition pattern of at least one of a common part of a configured RSMA message or a private part of the RSMA message from a transmitter; and after receiving the information configuring the repetition pattern, receive at least one repetition of at least one of the common part of the RSMA message or the private part of the RSMA message from the transmitter.

[0217] Embodiment 2 includes the device of Embodiment 1, and the common part of the RSMA message is common to a plurality of UEs, and wherein the private part of the RSMA message is specific to the UE.

[0218] Embodiment 3 includes the device of Embodiment 1, and the repetition pattern is based on at least one of a priority or QoS associated with at least one of the common part of the RSMA message or the private part of the RSMA message.

[0219] Embodiment 4 includes the device of Embodiment 3, and at least one of the priority or the QoS is included in the SCI.

[0220] Embodiment 5 includes the device of Embodiment 1, and the repetition pattern includes at least one of a first repetition factor associated with the common part of the RSMA message or a second repetition factor associated with the private part of the RSMA message.

[0221] Embodiment 6 includes the device of Embodiment 1, and the information configuring the repetition pattern is received via at least one of L1 signaling, L2 signaling, or L3 signaling.

[0222] Embodiment 7 includes the device of Embodiment 1, and the repetition pattern is based on whether the common part of the RSMA message includes control information.

[0223] Embodiment 8 includes the device of Embodiment 1, and when the common part of the RSMA message and the private part of the RSMA message are scheduled via a plurality of configured grants, the common part of the RSMA message and the private part of the RSMA message are received on a sidelink channel in one of the same logical channel group or different logical channel groups.

[0224] Embodiment 9 includes the device of Embodiment 1, and the device is further configured to: send a request for at least one other repetition of at least one of the common part of the RSMA message or the private part of the RSMA message to the transmitter.

[0225] Embodiment 10 includes the device of Embodiment 9, and the request is multiplexed with HARQ feedback.

[0226] Embodiment 11 includes the device of Embodiment 9, and the request indicates a repetition factor of at least one other repetition of at least one of the common part of the RSMA message or the private part of the RSMA message.

[0227] Embodiment 12 includes the device of Embodiment 1, and the request is sent on a set of periodic resources allocated for requests for other repetitions.

[0228] Embodiment 13 is a device configured to: send information about a repetition pattern of at least one of the common part of a configured RSMA message or the private part of the RSMA message to at least one UE; and send at least one repetition of at least one of the common part of the RSMA message or the private part of the RSMA message to the at least one UE according to the repetition pattern.

[0229] Embodiment 14 includes the device of Embodiment 13, and the common part of the RSMA message is common to multiple UEs, and wherein the private part of the RSMA message is specific to the at least one UE.

[0230] Embodiment 15 includes the device of Embodiment 13, and the repetition pattern is based on at least one of a priority or QoS associated with at least one of the common part of the RSMA message or the private part of the RSMA message.

[0231] Embodiment 16 includes the device of Embodiment 15, and at least one of the priority or the QoS is included in the SCI.

[0232] Embodiment 17 includes the device of Embodiment 13, and the repetition pattern includes at least one of a first repetition factor associated with the common part of the RSMA message or a second repetition factor associated with the private part of the RSMA message.

[0233] Embodiment 18 includes the device of Embodiment 13, and the information configuring the repetition pattern is sent via at least one of layer 1 L1 signaling, L2 signaling, or L3 signaling.

[0234] Embodiment 19 includes the device of Embodiment 13, and the repetition pattern is based on whether the common part of the RSMA message includes control information.

[0235] Embodiment 20 includes the device of Embodiment 13, and when the common part and the private part of the RSMA message are scheduled via multiple configured grants, the common part and the private part of the RSMA message are transmitted on a sidelink channel in one of the same logical channel group or different logical channel groups.

[0236] Embodiment 21 includes the device of Embodiment 13, and the device is further configured to: receive, from at least one UE, a request associated with at least one other repetition of at least one of the common part or the private part of the RSMA message; and transmit, to the at least one UE, the at least one other repetition of at least one of the common part or the private part of the RSMA message associated with the request.

[0237] Embodiment 22 includes the device of Embodiment 21, and the request is multiplexed with HARQ feedback.

[0238] Embodiment 23 includes the device of Embodiment 21, and the request indicates a repetition factor of the at least one other repetition of at least one of the common part or the private part of the RSMA message.

[0239] Embodiment 24 includes the device of Embodiment 21, and the request is transmitted on a set of periodic resources allocated for requests for other repetitions.

[0240] Embodiment 25 includes the device of Embodiment 13, and the device is further configured to: set an RSRP threshold associated with at least one of a first priority of the common part of the RSMA message, a second priority of the private part of the RSMA message, or a third priority of another message.

[0241] Embodiment 26 includes the device of Embodiment 25, and the RSRP threshold is set based on the highest priority among the first priority, the second priority, or the third priority.

[0242] The foregoing description is provided to enable a person of ordinary skill in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those of ordinary skill in the art, and the general principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims. Accordingly, the language employed herein is not intended to limit the scope of the claims to only those aspects shown herein, but is to be accorded the full scope consistent with the language of the claims.

[0243] As an example, the language “determine” can encompass a wide variety of actions and thus may not be limited to the concepts and aspects explicitly described or illustrated by the present disclosure. In some contexts, “determine” can include calculating, computing, processing, measuring, deriving, researching, looking up (e.g., looking up in a table, database, or another data structure), ascertaining, resolving, selecting, choosing, establishing, and the like. In some other contexts, “determine” can include communicating and / or memory operations / procedures for obtaining information or values, such as “receiving” (e.g., receiving information), “accessing” (e.g., accessing data in a memory), “detecting,” etc.

[0244] As another example, a reference to a singular element is not intended to mean "one and only one" (unless specifically stated otherwise), but rather "one or more". Additionally, terms such as "if", "when", and "while" are to be interpreted as meaning "under the condition that", rather than implying a direct temporal relationship or reaction. That is, these phrases (e.g., "when") do not imply an immediate action in response to the occurrence of an action or event or during the occurrence of an action or event, but rather imply that another action or event will occur when a condition is met, without requiring a specific or immediate time constraint or direct correlation for the occurrence of that other action or event. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration". Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or having an advantage over other aspects. Unless specifically stated, the term "some" means one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "any combination of A, B, C, or them" include any combination of A, B, and / or C, and may include multiple A's, multiple B's, or multiple C's. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "any combination of A, B, C, or thereof" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or will later be known to those of ordinary skill in the art are hereby expressly incorporated by reference and are intended to be covered by the claims. Additionally, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is explicitly recited in the claims. The words "module", "mechanism", "element", "device", etc. are not to be used in place of the word "component". Thus, no claim element is to be construed as a means-plus-function unless the element is expressly recited using the phrase "means for...".

Claims

1. A method for wireless communication at a user equipment (UE), the method comprising: Receiving information on a repetition pattern of at least one of a common part of a configured rate-split multiple access (RSMA) message or a private part of the RSMA message from a device; And After receiving the information configuring the repetition pattern, receiving at least one repetition of at least one of the common part of the RSMA message or the private part of the RSMA message from the device.

2. The method according to claim 1, wherein the common part of the RSMA message is common to multiple UEs, and wherein the private part of the RSMA message is specific to the UE.

3. The method according to claim 1, wherein the repetition pattern is based on at least one of a priority or a quality of service (QoS) associated with at least one of the common part of the RSMA message or the private part of the RSMA message.

4. The method according to claim 3, wherein at least one of the priority or the QoS is included in sidelink control information (SCI).

5. The method according to claim 1, wherein the repetition pattern includes at least one of a first repetition factor associated with the common part of the RSMA message or a second repetition factor associated with the private part of the RSMA message.

6. The method according to claim 1, wherein the information configuring the repetition pattern is received via at least one of layer 1 (L1) signaling, layer 2 (L2) signaling, or layer 3 (L3) signaling.

7. The method according to claim 1, wherein the repetition pattern is based on whether the common part of the RSMA message includes control information.

8. The method according to claim 1, wherein when the common part of the RSMA message and the private part of the RSMA message are scheduled via multiple configured grants, the common part of the RSMA message and the private part of the RSMA message are received on a sidelink channel in one of the same logical channel group or different logical channel groups.

9. The method according to claim 1, the method further comprising: Sending a request for at least one other repetition of at least one of the common part of the RSMA message or the private part of the RSMA message to the device.

10. The method according to claim 9, wherein the request is multiplexed with hybrid automatic repeat request (HARQ) feedback.

11. A method for wireless communication at a device, the method comprising: Sending information on a repetition pattern of at least one of a common part of a configured rate-split multiple access (RSMA) message or a private part of the RSMA message to at least one user equipment (UE); And Sending at least one repetition of at least one of the common part of the RSMA message or the private part of the RSMA message to the at least one UE according to the repetition pattern.

12. The method according to claim 11, wherein the common part of the RSMA message is common to multiple UEs, and wherein the private part of the RSMA message is specific to the at least one UE.

13. The method according to claim 11, wherein the repetition pattern is based on at least one of a priority or a quality of service (QoS) associated with at least one of the common part of the RSMA message or the private part of the RSMA message.

14. The method according to claim 13, wherein at least one of the priority or the QoS is included in sidelink control information (SCI).

15. The method according to claim 11, wherein the repetition pattern includes at least one of a first repetition factor associated with the common part of the RSMA message or a second repetition factor associated with the private part of the RSMA message.

16. The method according to claim 11, wherein the information configuring the repetition pattern is sent via at least one of layer 1 (L1) signaling, layer 2 (L2) signaling, or layer 3 (L3) signaling.

17. The method according to claim 11, wherein the repetition pattern is based on whether the common part of the RSMA message includes control information.

18. The method according to claim 11, wherein when the common part of the RSMA message and the private part of the RSMA message are scheduled via multiple configured grants, the common part of the RSMA message and the private part of the RSMA message are sent on a sidelink channel in one of the same logical channel group or different logical channel groups.

19. The method according to claim 11, the method further comprising: receiving, from at least one UE, a request associated with at least one other repetition of at least one of the common part of the RSMA message or the private part of the RSMA message; and sending, to the at least one UE, the at least one other repetition of at least one of the common part of the RSMA message or the private part of the RSMA message associated with the request.

20. The method according to claim 19, wherein the request is multiplexed with hybrid automatic repeat request (HARQ) feedback.

21. The method according to claim 19, wherein the request indicates a repetition factor of the at least one other repetition of at least one of the common part of the RSMA message or the private part of the RSMA message.

22. The method according to claim 11, the method further comprising: setting a reference signal received power (RSRP) threshold associated with at least one of a first priority of the common part of the RSMA message, a second priority of the private part of the RSMA message, or a third priority of another message.

23. The method according to claim 22, wherein the RSRP threshold is set based on the highest priority among the first priority, the second priority, or the third priority.

24. An apparatus for wireless communication, the apparatus comprising: a memory; and at least one processor, the at least one processor coupled to the memory and configured to: receive information on a repeating pattern of at least one of a common part of a configured rate-split multiple access (RSMA) message or a private part of the RSMA message from a transmitter; and after receiving the information configuring the repeating pattern, receive at least one repetition of at least one of the common part of the RSMA message or the private part of the RSMA message from the transmitter.

25. The apparatus according to claim 24, wherein the repeating pattern is based on at least one of a priority associated with at least one of the common part of the RSMA message or the private part of the RSMA message or quality of service (QoS).

26. The apparatus according to claim 24, wherein the repeating pattern includes at least one of a first repetition factor associated with the common part of the RSMA message or a second repetition factor associated with the private part of the RSMA message.

27. The apparatus according to claim 24, wherein the at least one processor is further configured to: send a request for at least one other repetition of at least one of the common part of the RSMA message or the private part of the RSMA message to the transmitter.

28. An apparatus for wireless communication, the apparatus comprising: a memory; and at least one processor, the at least one processor coupled to the memory and configured to: send information on a repeating pattern of at least one of a common part of a configured rate-split multiple access (RSMA) message or a private part of the RSMA message to at least one user equipment (UE); and send at least one repetition of at least one of the common part of the RSMA message or the private part of the RSMA message to the at least one UE according to the repeating pattern.

29. The apparatus according to claim 28, wherein the repeating pattern is based on at least one of a priority associated with at least one of the common part of the RSMA message or the private part of the RSMA message or quality of service (QoS).

30. The apparatus according to claim 28, wherein the at least one processor is further configured to: set a reference signal received power (RSRP) threshold associated with at least one of a first priority of the common part of the RSMA message, a second priority of the private part of the RSMA message, or a third priority of another message.

Images