Method and apparatus for transmit or receive centric frequency domain resource allocation
The centralized frequency domain resource allocation method solves the problem of inconsistent frequency domain resource allocation between different UEs, improves the success rate and efficiency of sidelink communication, and supports multiple communication types.
Patent Information
- Application Number
- CN202380034218.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-22
- Filing Date
- 2023-04-13
- Publication Date
- 2024-11-26
AI Technical Summary
In sidelink communication, frequency domain resource allocation between UEs with different RB set configurations suffers from inconsistent interpretation and resource configuration confusion, leading to communication failures and inefficiency.
The central frequency domain resource allocation (FDRA) method is adopted, including minimum RB set configuration, Tx central RB set configuration and Rx central RB set configuration. The UE is instructed to use the minimum overlapping frequency RB set configuration through signaling to ensure communication consistency and efficiency.
It improves the success rate and efficiency of sidelink communication, ensures the consistency of frequency domain resource allocation between different UEs, and supports different types of sidelink communication, such as unicast, multicast and broadcast.
Smart Images

Figure CN119032533A_ABST
Abstract
Description
[0001] Cross-references
[0002] This patent application claims priority to U.S. patent application No. 17 / 727,408, entitled “METHOD AND APPARATUS FOR TRANSMITTING OR RECEIVING CENTRIC FREQUENCY DOMAIN RESOURCE ALLOCATION,” filed by Liu et al. on April 22, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field
[0003] The present disclosure relates to wireless communications, and in particular to transmitting or receiving centric frequency domain resource allocation. Background Art
[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more network entities, each of which supports wireless communication of communication devices, which may be referred to as user equipment (UE).
[0005] A UE may perform sidelink communications with one or more other UEs. In an example of sidelink communication Mode 2, a sidelink UE may autonomously schedule sidelink communication resources with another sidelink UE (e.g., without receiving scheduling information from a network entity). In this Mode 2 case, a scheduled sidelink UE (e.g., a transmitting sidelink UE (TxUE)) may communicate with other sidelink UEs with different settings, capabilities, etc. In addition, different sidelink UEs may use different subbands for communication, such as different UEs may use different subband subsets (which may partially overlap in the frequency domain in some examples), different resource block (RB) set guard band settings, etc. Sidelink UEs having different RB set configurations may become a problem for the scheduled sidelink UEs because the frequency domain resource allocation (FDRA) configuration / interpretation may be based on the RB set configuration. Summary of the invention
[0006] The described technology relates to improved methods, systems, devices and apparatuses for supporting transmission or reception of centered frequency domain resource allocation (FDRA). For example, the described technology provides various modes for resource block (RB) set configuration between sidelink user equipment (UE) to improve FDRA signaling. One mode includes a minimum RB set configuration (e.g., per 20MHz subband) based on the minimum overlapping RB set in all possible RB set configurations. The minimum RB set configuration mode improves sidelink communication by ensuring that at least a transmitting sidelink UE (Tx UE) and a receiving sidelink UE (Rx UE) monitor overlapping RBs in the frequency domain. Another mode includes a transmission-centered (Tx-centered) RB set configuration based on the assumption / configuration of the transmitting sidelink UE (Tx UE). The Tx-centered RB set configuration improves sidelink communication performed by the Tx UE, such as multicast and / or broadcast sidelink communication, by maximizing the use of RBs available for the Tx UE. Another mode includes a receiver-centered (Rx-centered) RB set configuration based on the assumption / configuration of the receiving sidelink UE (Rx UE). The Rx-centric RB set configuration improves the sidelink communication of the Rx UE by maximizing the use of the RBs available to the Rx UE. Thus, the Tx UE may send or otherwise provide an indication (e.g., an implicit indication or an explicit indication) of the RB set configuration to one or more Rx UEs. The RB set configuration may be selected based on the type of sidelink communication being performed and may be from an available RB set configuration (e.g., from a minimum RB set configuration, a Tx-centric RB set configuration, or an Rx-centric RB set configuration). The sidelink UE may perform sidelink communication according to the indicated RB set configuration.
[0007] A method for wireless communication at a UE is described. The method may include: sending signaling including an indication of an RB set configuration to one or more sidelink UEs, the RB set configuration based on a type of sidelink communication to be performed and from a set of available RB set configurations including at least a minimum overlapping frequency RB set configuration; and performing the sidelink communication with the one or more sidelink UEs according to the RB set configuration.
[0008] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to send signaling including an indication of an RB set configuration to one or more sidelink UEs, the RB set configuration being based on a type of sidelink communication to be performed and from a set of available RB set configurations including at least a minimum overlapping frequency RB set configuration, and to perform the sidelink communication with the one or more sidelink UEs according to the RB set configuration.
[0009] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for sending signaling including an indication of an RB set configuration to one or more sidelink UEs, the RB set configuration based on a type of sidelink communication to be performed and from a set of available RB set configurations including at least a minimum overlapping frequency RB set configuration; and means for performing the sidelink communication with the one or more sidelink UEs according to the RB set configuration.
[0010] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: send signaling including an indication of an RB set configuration to one or more sidelink UEs, the RB set configuration based on a type of sidelink communication to be performed and from a set of available RB set configurations including at least a minimum overlapping frequency RB set configuration; and perform the sidelink communication with the one or more sidelink UEs according to the RB set configuration.
[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: identifying RB sets having frequencies overlapping in each RB set configuration in available RB set configurations within a sub-band; and selecting RB sets for RB set configurations based on the identification, wherein the minimum overlapping frequency RB set configuration includes RB sets having frequencies overlapping within the sub-band.
[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing sidelink communications including using RB sets to send SCI messages, multicast messages, groupcast messages, radio resource control (RRC) messages, or any combination thereof.
[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for configuring a physical sidelink control channel (PSCCH) for transmission within a set of RBs based on a set of RBs having frequencies overlapping within a sub-band.
[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for configuring a portion of a physical sidelink shared channel (PSSCH) for sending an SCI message within a set of RBs based on a set of RBs having frequencies overlapping within a sub-band.
[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: identifying an RB set of the UE that can be used to send broadcast transmissions, multicast transmissions, or both, wherein the type of sidelink communication includes broadcast transmissions, multicast transmissions, or both; and selecting an RB set for RB set configuration of the UE based on the type of sidelink communication, wherein the RB set can be associated with a transmitter-centric RB set configuration in the available RB set configurations.
[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for identifying a set of RBs for a UE based on an active bandwidth portion of the UE.
[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving an indication of a requested RB set configuration from a sidelink UE; and selecting the requested RB set configuration as the RB set configuration based on the indication.
[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, providing an indication may include operations, features, components, or instructions for: identifying an RB set configuration indication state for one or more side link UEs based on a type of side link communication to be performed; and selecting a minimum overlapping frequency RB set configuration as the RB set configuration based on the RB set configuration indication state.
[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, providing an indication may include operations, features, components, or instructions for configuring one or more SCI messages to indicate an RB set configuration, wherein the signaling includes the one or more SCI messages.
[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining an update type of sidelink communication to be performed for subsequent sidelink communication to be performed; and transitioning from an RB set configuration to an updated RB set configuration for subsequent sidelink communication based on the update type of the sidelink communication.
[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the type of side link communication performed includes at least one of unicast side link communication, broadcast side link communication, groupcast side link communication, multicast side link communication, or a combination thereof.
[0022] A method for wireless communication at a UE is described. The method may include: receiving signaling including an indication of an RB set configuration from a set of available RB set configurations based on a type of sidelink communication to be performed, the set of available RB set configurations including at least a minimum overlapping frequency RB set configuration; and performing the sidelink communication with a transmitting sidelink UE according to the RB set configuration.
[0023] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to receive signaling including an indication of an RB set configuration from a set of available RB set configurations based on a type of sidelink communication to be performed, the set of available RB set configurations including at least a minimum overlapping frequency RB set configuration; and perform the sidelink communication with a transmitting sidelink UE according to the RB set configuration.
[0024] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving signaling, the signaling including an indication of an RB set configuration from a set of available RB set configurations based on a type of sidelink communication to be performed, the set of available RB set configurations including at least a minimum overlapping frequency RB set configuration; and means for performing the sidelink communication with a transmitting sidelink UE according to the RB set configuration.
[0025] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive signaling including an indication of an RB set configuration from a set of available RB set configurations based on a type of sidelink communication to be performed, the set of available RB set configurations including at least a minimum overlapping frequency RB set configuration; and perform the sidelink communication with a transmitting sidelink UE according to the RB set configuration.
[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for determining, based on the indication, RB sets in the RB set configurations having frequencies that overlap within each of the available RB set configurations.
[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing sidelink communications including receiving SCI messages, multicast messages, groupcast messages, RRC messages, or any combination thereof using RB sets.
[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the PSCCH may be configured for transmission within a set of RBs based on the set of RBs having frequencies overlapping within a sub-band.
[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a portion of the PSSCH may be configured to send an SCI message within a set of RBs based on the set of RBs having frequencies overlapping within a sub-band.
[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, for an SCI two message, rate matching is performed on frequency resources around an interlace across one or more RB sets indicated in an SCI one message.
[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, frequency resources surrounding a set of RBs are rate matched to receive an SCI two message, wherein the frequency resources are available for receiving an SCI one message.
[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, frequency resources surrounding a set of RBs are rate matched to receive a PSSCH.
[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, after a received signal indicates that the RB set configuration may have overlapping frequencies, frequency resources around the extended RB set are rate matched.
[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: identifying an RB set of a transmitting sidelink UE that can be used to transmit a broadcast transmission, a multicast transmission, or both, wherein the type of the sidelink communication includes a broadcast transmission, a multicast transmission, or both; and based on the type of the sidelink communication, performing the sidelink communication using the RB set for RB set configuration of the transmitting sidelink UE, wherein the RB set can be associated with a transmitter-centric RB set configuration in the available RB set configurations.
[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a set of RBs for a transmitting side link UE may be based on an active bandwidth portion of the transmitting side link UE.
[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, obtaining an indication may include operations, features, components, or instructions for: receiving an SCI message indicating an identifier associated with a transmitting side link UE; and identifying an RB set configuration based on the identifier.
[0037] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that the RB set spans frequency resources outside the configured RB set of the UE; and puncturing the frequency resources outside the configured RB set based on the determination.
[0038] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending an indication of a requested RB set configuration to a transmitting sidelink UE, wherein the RB set configuration includes the requested RB set configuration.
[0039] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the RB set configuration may be based on an active bandwidth portion of the UE.
[0040] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a minimum overlapping frequency RB set configuration may be selected as the RB set configuration based on an RB set configuration indication state of the UE.
[0041] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, obtaining the indication may include operations, features, means, or instructions for receiving one or more SCI messages indicating a RB set configuration.
[0042] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the type of side link communication performed includes at least one of unicast side link communication, broadcast side link communication, groupcast side link communication, multicast side link communication, or a combination thereof.
[0043] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, obtaining an indication may include operations, features, components, or instructions for: receiving an SCI message indicating a frequency domain resource allocation; and identifying an RB set configuration based on the frequency domain resource allocation. BRIEF DESCRIPTION OF THE DRAWINGS
[0044] Figure 1 An example of a wireless communication system supporting transmission or reception of centered frequency domain resource allocation (FDRA) according to one or more aspects of the present disclosure is illustrated.
[0045] Figure 2 An example of a wireless communication system supporting transmission or reception of a centralized FDRA according to one or more aspects of the present disclosure is illustrated.
[0046] Figure 3 An example of RB set configuration supporting transmission or reception of a centralized FDRA according to one or more aspects of the present disclosure is illustrated.
[0047] Figure 4 An example of RB set configuration supporting transmission or reception of a centralized FDRA according to one or more aspects of the present disclosure is illustrated.
[0048] Figure 5 An example of RB set configuration supporting transmission or reception of a centralized FDRA according to one or more aspects of the present disclosure is illustrated.
[0049] Figure 6 An example of RB set configuration supporting transmission or reception of a centralized FDRA according to one or more aspects of the present disclosure is illustrated.
[0050] Figure 7 An example of RB set configuration supporting transmission or reception of a centralized FDRA according to one or more aspects of the present disclosure is illustrated.
[0051] Figure 8 An example of RB set configuration supporting transmission or reception of a centralized FDRA according to one or more aspects of the present disclosure is illustrated.
[0052] Fig. 9 An example of an RB set switching configuration supporting transmission or reception of a centralized FDRA according to one or more aspects of the present disclosure is illustrated.
[0053] Fig.10 and Fig.11 A block diagram of a device supporting sending or receiving a centralized FDRA according to one or more aspects of the present disclosure is shown.
[0054] Fig.12A block diagram of a communication manager supporting send or receive centric FDRA according to one or more aspects of the present disclosure is shown.
[0055] Fig.13 A diagram of a system including a device supporting sending or receiving a centralized FDRA according to one or more aspects of the present disclosure is shown.
[0056] Figures 14 to 17 A flow chart illustrating a method of supporting sending or receiving a centralized FDRA according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION
[0057] A user equipment (UE) may communicate with one or more other UEs according to various sidelink communication technologies. One or more components of a network entity may transmit signaling that configures a UE to communicate according to sidelink communication mode 1 or sidelink communication mode 2, wherein one sidelink UE configures sidelink communication. In an example of sidelink communication mode 2, a sidelink UE may autonomously schedule sidelink communication resources with another sidelink UE (e.g., without receiving scheduling information from a network entity). In this mode 2 case, a scheduled sidelink UE (e.g., a transmitting sidelink UE (Tx UE)) may communicate with other sidelink UEs having different settings, capabilities, etc. Different sidelink UEs may communicate using different subbands, such as different UEs may use different subband subsets (which may partially overlap in the frequency domain in some examples), different resource block (RB) set protection band settings, etc.
[0058] Sidelink nodes (e.g., UEs) with different RB set configurations may become a problem for scheduling sidelink UEs because frequency domain resource allocation (FDRA) configuration / interpretation may be based on the RB set configuration. In addition, such differences in RB set configurations may make it difficult to communicate sidelink control information-1 (SCI-1) and / or SCI-2 messages between sidelink devices with different RB set configurations. Different types of sidelink communications may benefit from some RB set configurations over other RB set configurations.
[0059] The described technology relates to improved methods, systems, devices and apparatuses for supporting transmission or reception of central FDRA. For example, the described technology provides various modes for RB set configuration between sidelink UEs. One mode includes a minimum RB set configuration based on the minimum overlapping RB set among all possible RB set configurations (e.g., based on each 20MHz subband). Another mode includes a transmission central (Tx central) RB set configuration based on the assumption / configuration of the Tx UE. Another mode includes a receiver central (Rx central) RB set configuration based on the assumption / configuration of the receiving sidelink UE (Rx UE). Therefore, the Tx UE can send or otherwise provide an indication of the RB set configuration to one or more Rx UEs (e.g., an implicit indication or an explicit indication). The RB set configuration can be selected based on the type of sidelink communication to be performed and can be from an available RB set configuration (e.g., from a minimum RB set configuration, a Tx central RB set configuration, or an Rx central RB set configuration). The sidelink UE can perform sidelink communication according to the indicated RB set configuration.
[0060] First, various aspects of the present disclosure are described in the context of a wireless communication system. Various aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow charts related to sending or receiving centered frequency domain resource allocation.
[0061] Figure 1 An example of a wireless communication system 100 supporting transmission or reception of centered frequency domain resource allocation according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).
[0062] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, etc. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).
[0063] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or both stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of communicating with various types of devices such as Figure 1 Communicating with other UEs 115 or network entities 105 as shown.
[0064] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.
[0065] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other directly (e.g., directly between each network entity 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .
[0066] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a home Node B, a home evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).
[0067] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).
[0068] The functional split between CU 160, DU 165, and RU 175 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, and RU 175. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DUs 165 and RUs 170, such that the DUs 165 may support one or more layers of the protocol stack, and the RUs 170 may support one or more different layers of the protocol stack. The DUs 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to an interface (eg, channel) between layers of a protocol stack supported by the respective network entities 105 communicating over those communication links.
[0069] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.
[0070] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an IAB node 104, and one or more UEs 115. An IAB donor may facilitate connectivity between a core network 130 and an AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. An IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of part of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) via an Xn-C interface (which may be an example of part of a backhaul link).
[0071] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., an IAB donor may relay transmissions to a UE through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of IAB node 104 may provide a Uu interface for child IAB node 104 to receive signaling from parent IAB node 104 , and a DU interface (eg, DU 165 ) may provide a Uu interface for parent IAB node 104 to signal to child IAB node 104 or UE 115 .
[0072] For example, the IAB node 104 may be referred to as a parent node that supports communications to a child IAB node, and may be referred to as a child IAB node associated with an IAB donor. The IAB donor may include a CU 160 having a wired or wireless connection (e.g., a backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay transmissions to the UE 115 through the IAB node 104, and may directly signal the UE 115 of the transmissions. The CU 160 of the IAB donor may signal the IAB node 104 of the communication link establishment via the F1 interface, and the IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to the UE 115) through the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling through the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .
[0073] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support sending or receiving centralized frequency domain resource allocation as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may be additionally or alternatively performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).
[0074] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.
[0075] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1shown.
[0076] The UE 115 and the network entity 105 may communicate with each other wirelessly via one or more communication links 125 (e.g., access links) via one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).
[0077] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be located according to a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be made by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.
[0078] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry either downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry both downlink communications and uplink communications (e.g., in TDD mode).
[0079] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communication over a particular carrier bandwidth, or may be configurable to support communication over one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate over a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.
[0080] The signal waveform transmitted through the carrier may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM techniques, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a subcarrier resource, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.
[0081] One or more parameter sets for a carrier may be supported, where the parameter set may include subcarrier spacing (Δf) and cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.
[0082] The time interval of the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·Nf ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).
[0083] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into multiple micro time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.
[0084] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).
[0085] Physical channels may be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels may be multiplexed on a downlink carrier using, for example, one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .
[0086] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., via a carrier), and may be associated with an identifier used to distinguish adjacent cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) within which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.
[0087] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. Small cells may be associated with lower power network entities 105 (e.g., lower power base stations 140) than macro cells, and small cells may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with small cells (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications on one or more cells.
[0088] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.
[0089] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.
[0090] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and in some examples, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operation.
[0091] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may allow automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, wildlife monitoring, weather and geographic event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.
[0092] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for UE 115 include entering a power-saving deep sleep mode when not engaged in active communications, operating with limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a subcarrier or resource block (RB) set) within a carrier, within a guard band of a carrier, or outside a carrier.
[0093] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.
[0094] In some examples, a UE 115 may be able to communicate directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), and the one or more UEs may support aspects of such D2D communication configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in the group may be outside the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each other UE 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .
[0095] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these items. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, the vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.
[0096] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access layer (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.
[0097] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.
[0098] The wireless communication system 100 may also operate in a super high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also known as a centimeter band) or in an extremely high frequency (EHF) region of a spectrum (e.g., from 30 GHz to 300 GHz) (also known as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between a UE 115 and a network entity 105 (e.g., a base station 140, a RU 170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, this may facilitate the use of antenna arrays within the device. However, there may be even greater atmospheric attenuation and a shorter range for the propagation of EHF transmissions than for SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.
[0099] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations in an unlicensed band may be based on a carrier aggregation configuration in conjunction with a component carrier (e.g., LAA) operating in a licensed band. Operations in an unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.
[0100] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located in different geographic locations. The network entity 105 may have an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.
[0101] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. The multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.
[0102] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).
[0103] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as network entity 105, or by a receiving device, such as UE 115) beam directions for later transmission or reception by the network entity 105.
[0104] Some signals, such as data signals associated with a particular receiving device, may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115)). In some examples, the beam direction associated with the transmission along the single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.
[0105] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured beam set across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may or may not be precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-faceted codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115) or to send signals along a single direction (e.g., to send data to a receiving device).
[0106] When receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105), the receiving device (e.g., UE 115) may perform receiving operations (e.g., directional listening) according to multiple receiving configurations. For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing the received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).
[0107] The wireless communication system 100 can be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication at the bearer layer or the PDCP layer can be IP-based. The RLC layer can perform packet segmentation and reorganization to communicate on the logical channel. The MAC layer can perform priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use error detection technology, error correction technology, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer can provide the establishment, configuration and maintenance of the RRC connection of the radio bearer that supports user plane data between the UE 115 and the network entity 105 or the core network 130. At the PHY layer, the transport channel can be mapped to the physical channel.
[0108] UE 115 and network entity 105 may support retransmission of data to increase the possibility of successfully receiving data. Hybrid automatic repeat request (HARQ) feedback is a technology for increasing the possibility of correctly receiving data through a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve the throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.
[0109] UE 115 (e.g., a transmitting sidelink UE) may send signaling to one or more sidelink UEs including an indication of an RB set configuration based at least in part on the type of sidelink communication to be performed and from a set of available RB set configurations including at least a minimum overlapping frequency RB set configuration. UE 115 may perform sidelink communication with the one or more sidelink UEs according to the RB set configuration.
[0110] UE 115 (e.g., a receiving sidelink UE) may receive signaling that includes an indication of an RB set configuration from a set of available RB set configurations based at least in part on the type of sidelink communication to be performed, the set of available RB set configurations including at least the minimum overlapping frequency RB set configurations. UE 115 may perform sidelink communication with the transmitting sidelink UE according to the RB set configurations.
[0111] Figure 2 An example of a wireless communication system 200 supporting sending or receiving a centralized FDRA according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may implement aspects of the wireless communication system 100. The wireless communication system 200 may include UE 205, UE 210, UE 215, and UE 220, which may be examples of corresponding devices described herein.
[0112] In some aspects, the wireless communication system 200 can perform various aspects of sidelink communications via a PC5 sidelink interface. In general, the UE 205 can be considered to be a transmitting sidelink UE (e.g., Tx UE) that performs sidelink communications with one or more receiving sidelink UEs (e.g., Rx UEs) (such as UE 210, UE 215, and / or UE 220) via a PC5 interface. In some aspects, the wireless communication system 200 can operate in a Mode 2 sidelink use case, where the UE 205 is managing various aspects of sidelink communications via a PC5 interface.
[0113] Conventional wireless communications between a network entity and a UE (e.g., between a gNB / base station and a UE over a Uu cellular interface) include the network entity making decisions regarding parameter configurations (such as RB set configurations). For example, the network entity may identify or otherwise determine UE capabilities (e.g., via UE capability message signaling, UE assistance information message signaling, etc.) and schedule resources for the UE (such as RB set configurations) based on the UE capabilities and other considerations.
[0114] However, the sidelink communication via the PC5 interface may include Tx UE and Rx UE being more equal regarding such allocation and scheduling decisions. That is, with some exceptions such as anchor client scenarios, the sidelink communication may not include nodes with a natural role, such as a gNB making allocation and scheduling decisions via the Uu interface. In addition, the UEs participating in the sidelink communication may not necessarily be identical in terms of capabilities, supported configurations, etc. For example, different UEs may use different subband subsets, which may partially overlap in some scenarios (e.g., UE0 uses subband 0 / 1, while UE1 uses subband 1 / 2). Another example includes RB set guard band settings. For example, depending on the filter implementation, some UEs may be able to use smaller guard bands when compared to other UEs.
[0115] Such issues may become a problem in some scenarios. For example, for distributed sidelink nodes (e.g., UEs) with different RB set configurations, this may become a problem because the FDRA interpretation performed by the Rx UE may depend on the RB set configuration of the UE. This may cause the Tx UE and the Rx UE to have different interpretations of the FDRA configuration / indication, which may cause decoding failures of sidelink communications (e.g., PSSCH and / or PSCCH decoding failures). For example, the Rx UE may not know how the Tx UE performs PSSCH transmission in the edge RBs. In addition, this may cause confusion about where the Tx UE sends SCI-1 and / or SCI-2 messages (e.g., which RB(s) are used), so that Rx UEs with different RB set configurations can successfully receive and decode those messages. Additionally, in order to utilize edge RBs (e.g., to improve resource utilization / efficiency), how the Tx sidelink UE and / or Rx sidelink UE selects a common RB set configuration.
[0116] In addition, the sidelink communication may include different types of sidelink communication, such as unicast, groupcast, broadcast, SCI-1 message, SCI-2 message, etc. Based on the different types of sidelink communication to be performed (e.g., unicast vs. groupcast), there may be different considerations on how the Tx UE and the Rx UE reach an agreement / understanding on the RB set configuration.
[0117] Thus, aspects of the techniques described herein provide various mechanisms for supporting RB set configuration between a Tx UE (e.g., UE 205 in this example) and one or more Rx UEs (e.g., UE 210, UE 215, and / or UE 220 in this example) to perform sidelink communications via a PC5 interface. In summary, three modes of RB set configuration are described, but aspects of one or more of the three modes may be combined in some cases. For ease of reference, the three modes of RB set configuration may include a minimum RB set configuration, a Tx-centric RB set configuration, and an Rx-centric RB set configuration.
[0118] The minimum RB set configuration may be based on the minimum RB set of all possible / available RB set configurations (e.g., on a per 20 MHz sub-band basis) such that the Tx UE and Rx UE have a common understanding of the FDRA indication (e.g., which RB(s) are available) within each 20 MHz sub-band. This may be applied prior to exchanging Remaining Minimum System Information (RMSI), System Information Blocks (SIBs), and / or RRC configuration signaling to configure the RB set configuration. This may generally provide a common basis for SCI-1 / 2 rate matching (e.g., such that SCI-1 / 2 decoding may not depend on the configured RB set configuration signaling). This may be compared to the Tx-centric and Rx-centric RB set configuration examples that depend, at least to some extent, on RMSI / SIB or RRC message exchanges.
[0119] The Tx-centric RB set configuration may generally define the RB set guard band based on the perspective of the Tx UE. The Tx-centric RB set configuration may be used for broadcast and / or multicast type sidelink communications, where the Tx UE sends sidelink communications (e.g., PSSCH) based on its own RB set configuration (e.g., its own set of available RB set configurations), and the Rx UE decodes the sidelink communications based on the RB set configuration of the Tx UE. Various aspects of the Tx-centric RB set configuration may be based on RMSI / SIB or RRC message exchanges to indicate the Tx-centric RB set configuration to the Rx UE.
[0120] The Rx-centric RB set configuration may generally define the RB set guard band based on the set of available RB set configurations for the Rx UE. For example, the Rx-centric RB set configuration may be used for unicast type sidelink communications. The Rx-centric RB set configuration may include the Tx UE applying different RB set configurations for different target Rx UEs (e.g., because the RB set configuration may be defined by each Rx UE). For example, various aspects of the Rx-centric RB set configuration may be based on RRC message exchanges, where the Rx UE indicates to the Tx UE the RB set configuration it requests / supports / configured.
[0121] Aspects of the techniques described herein also provide mechanisms to support situations where the Tx UE uses a different RB set than the Rx UE, RB set configuration switching by the Tx UE based on initial setup and the type of broadcast being performed (eg, type of sidelink communication), and the like.
[0122] For example, UE 205 (e.g., a Tx UE in this example) may be configured with a set of available RB set configurations 225. The set of available RB set configurations 225 may include one or more RB set configurations 230 that may be used / configured by UE 205 (where each RB set configuration includes one or more RB sets, and each RB in the RB set spans 12 subcarriers / tones in the frequency domain). UE 205 may identify, determine, or otherwise select an RB set configuration 235 from the set of available RB set configurations 225 according to the techniques discussed herein, which may be based on the type of sidelink communication being performed. In some aspects, the set of available RB set configurations may include at least a minimum overlapping frequency RB set configuration (e.g., a minimum RB set configuration, illustrated as RB set configuration 240). That is, UE 205 may configure an RB set configuration 235 that may include an RB set configuration 240 for an Rx UE.
[0123] For example, the UE 205 may identify, determine, or otherwise select the RB set configuration 235 based on the type of sidelink communication being performed (e.g., based on whether the sidelink communication includes PSCCH communication and / or PSSCH communication, including unicast sidelink communication, multicast sidelink communication, or broadcast sidelink communication, etc.). This may include the UE 205 identifying or otherwise determining which RB(s) within each RB set configuration 230 are overlapping. For example, the RB set configuration 240 may include RBs that are common to each RB set configuration 230 in the set of available RB set configurations 225 (e.g., overlapping RBs in the frequency domain). For example, as illustrated by the shaded area 245, the RB set configuration 240 may include RBs that are common to each RB set configuration 230 and overlap with each RB set configuration 230.
[0124] UE 205 may send, provide, or otherwise communicate signaling including an indication of RB set configuration 235 to one or more sidelink UEs (e.g., Rx UEs such as UE 210, UE 215, and / or UE 220). UE 205 may perform sidelink communication with the Rx UEs according to the indicated RB set configuration.
[0125] In some examples, this may include the UE 205 indicating the RB set configuration 235 and / or the RB set configuration 240. For example, the RB set configuration 240 may be a minimum RB set configuration that may be used for PSCCH / PSSCH communications, such as SCI-1 and / or SCI-2 transmissions. The UE 205 may configure the RB set configuration 235 to the receiving sidelink UE for sidelink communications, such as sidelink data communications on the PSSCH. The method may include performing SCI-1 / 2 communications on the RB set configuration 240 (e.g., the minimum RB set configuration) to support the Rx UE to successfully receive and decode the SCI-1 / 2 communications. Subsequent sidelink communications may be performed using the RB set configuration 240, or may use the RB set configuration 235.
[0126] Figure 3 An example of an RB set configuration 300 supporting transmission or reception of a centralized FDRA according to one or more aspects of the present disclosure is illustrated. The RB set configuration 300 may implement various aspects of the wireless communication system 100 and / or 200. Various aspects of the RB set configuration 300 may be implemented at or by a UE performing sidelink communication, which may be an example of a corresponding device described herein.
[0127] As discussed herein, aspects of the techniques described herein support a Tx UE sending, providing, or otherwise communicating signaling including an indication of an RB set configuration to one or more sidelink UEs (e.g., Rx UEs). The Tx UE may identify or otherwise select an RB set configuration based on the type of sidelink communication being performed. For example, the type of sidelink communication may include SCI-1 / SCI-2 sidelink communication, unicast sidelink communication, multicast sidelink communication, and / or broadcast sidelink communication, etc.
[0128] In some aspects, the Tx UE may identify, determine, or otherwise select an RB set configuration from a set of available RB set configurations 305, which may include multiple RB set configurations 310 (of which only five RB set configurations 310 are shown by way of example). Each RB set configuration 310 may include one or more RB sets, each RB set including one or more RBs, and each RB spans 12 subcarriers / tones in the frequency domain. For ease of reference, only one RB set configuration 310 is marked. The set of available RB set configurations 305 may include at least a minimum overlapping frequency RB set configuration (illustrated as RB set configuration 315). RB set configuration 315 may generally include RBs (e.g., frequency resources, where each RB generally spans 12 subcarriers / tones in the frequency domain and spans one symbol in the time domain) that are shared or otherwise overlapped between the RB set configurations 310 in the set of available RB set configurations 305. That is, the RB set configuration 315 may include RBs that are shared between some or all of the RB set configurations 310 in the set of available RB set configurations 305, or include RBs that overlap within some or all of the RB set configurations in the set of available RB set configurations 305. The Tx UE may send, provide, or otherwise communicate signaling indicating the RB set configuration 315 to one or more sidelink UEs (e.g., Rx UEs), and perform sidelink communication according to the indicated RB set configuration 315. For example, as illustrated by the shaded area 320, the RB set configuration 315 may include RBs that are shared by each RB set configuration 310 and overlap with each RB set configuration 310.
[0129] RB set configuration 300 illustrates an example of a minimum RB set configuration discussed herein. For example, the Tx UE may identify or otherwise determine an RB set with overlapping frequencies from the RB set configuration 310 in the set of available RB set configurations 305. The Tx UE may select, identify, or otherwise determine an RB set for an RB set configuration 315 within a sub-band, such as a 20 MHz sub-band. Thus, the RBs included in the RB set configuration 315 may be shared among all available RB set configurations 310 in the set of available RB set configurations 305.
[0130] In general, distributed sidelink communications may be improved using a common configuration, determination, assumption, etc. of an RB set configuration before the RB set configuration may be configured or otherwise delivered (e.g., via RMIS / SIB or RRC message exchange). In the case where the available RB sets allowed within a sub-band have an embedded structure (e.g., the minimum RB set is "inside" or otherwise overlaps with all other RB sets), the minimum RB set configuration may be utilized to support certain treatments. Thus, the Tx UE may define a minimum RB set configuration for a 20 MHz sub-band based on all possible RB set configurations. The minimum RB set configuration may be explicitly defined (e.g., based on signaling indicating the RB set configuration 315) and / or implicitly derived from all RB set configurations (e.g., using the intersection of all supported RB sets). That is, in an implicit example, the signaling may refer to a configuration / indication of an available RB set configuration for the Tx UE and / or Rx UE.
[0131] In some aspects, for certain non-limiting use cases, a minimum RB set configuration (e.g., RB set configuration 315) may be supported. One use case may include SCI-1 / 2 messages being restricted to the minimum RB set configuration, even when normal sidelink communications are performed using a larger RB set configuration that covers (e.g., overlaps) the minimum RB set configuration. In this use case, other nodes (e.g., Rx UEs) may be able to decode SCI message transmissions without knowing the RB set configuration of the Tx UE. Another use case may include that for multicast / broadcast or for an initial RRC message exchange to establish (e.g., configure) an extended Tx / Rx RB set configuration, transmissions may use the minimum RB set configuration, while unicast sidelink communications after the Tx / Rx RB set configuration is RRC configured may use a larger RB set.
[0132] Thus, the Tx UE may signal an indication of the RB set configuration 315 to the Rx UE (e.g., explicit signaling indicating the RB set configuration 315 and / or implicitly using signaling indicating the available RB set configuration set 305). The Tx UE may perform sidelink communication with the Rx UE according to the RB set configuration 315 via the PC5 sidelink interface.
[0133] Figure 4 An example of an RB set configuration 400 supporting transmission or reception of a centralized FDRA according to one or more aspects of the present disclosure is illustrated. The RB set configuration 400 may implement aspects of the wireless communication system 100 and / or 200 and / or the RB set configuration 300. Various aspects of the RB set configuration 400 may be implemented at or by a UE performing sidelink communication, which may be an example of a corresponding device described herein.
[0134] As discussed herein, aspects of the techniques described herein support a Tx UE sending, providing, or otherwise communicating signaling including an indication of an RB set configuration to one or more sidelink UEs (e.g., Rx UEs). The Tx UE may identify or otherwise select an RB set configuration based on the type of sidelink communication being performed. For example, the type of sidelink communication may include SCI-1 / SCI-2 sidelink communication, unicast sidelink communication, multicast sidelink communication, and / or broadcast sidelink communication, etc.
[0135] In some aspects, the Tx UE may identify, determine, or otherwise select an RB set configuration 405 (e.g., an actually configured RB set configuration) that may include multiple RB sets from the set of available RB set configurations. The set of available RB set configurations may include at least a minimum overlapping frequency RB set configuration (illustrated as RB set configuration 410). RB set configuration 410 may generally include RBs that are shared or otherwise overlapped between RB set configurations in the set of available RB set configurations. The Tx UE may send, provide, or otherwise communicate signaling indicating the RB set configuration 405 to one or more sidelink UEs (e.g., Rx UEs), and perform sidelink communications based on the RB set configuration 405 and / or the RB set configuration 410.
[0136] RB set configuration 400 illustrates another example of aspects of the minimum RB set configuration discussed herein. For example, the Tx UE may identify or otherwise determine RB sets with overlapping frequencies from RB set configurations in a set of available RB set configurations. The Tx UE may select, identify or otherwise determine RB sets for RB set configurations within a sub-band, such as a 20 MHz sub-band.
[0137] Generally speaking, the PSCCH may be carried on a subset of RBs / symbols of a subchannel (eg, the first two or three symbols and the first X RBs in a subchannel, depending on the RB set configuration). However, without knowing the RB set configuration, the Rx UE may not be able to identify the location of the PSCCH.
[0138] Thus, aspects of the techniques described herein provide for limiting the PSCCH location within a subchannel to a minimum RB set configuration (e.g., RB set configuration 410) within a subband (e.g., a 20 MHz subband). That is, a Tx UE may configure a PSCCH for transmission within an RB set based on an RB set having overlapping frequencies within a subband (e.g., having frequencies overlapping within a subband).
[0139] For example, PSCCH resource mapping may be restricted to a minimum RB set in a subchannel and a 20MHz subband. PSCCH may use different minimum RB sets (e.g., different 20MHz subbands). Within a given subband, PSCCH may take / use different subchannels / interlaces. PSCCH decoding may be supported even if the Rx UE does not receive an S-SSB or RRC configuration that defines the actual RB set configuration. That is, the location of the PSCCH may be fixed regardless of the RB set configuration.
[0140] That is, the Tx UE may signal an indication of the RB set configuration 405 to the Rx UE. The RB set configuration may include a plurality of RBs 425, of which only nine RBs 425 are shown by way of example. The RB set configuration 405 may be associated with a configuration RB set guard band #x-1 (e.g., illustrated as RB set 415), a minimum RB set (illustrated as RB set configuration 410), and a configuration RB set guard band #x (illustrated as RB set 420). RB 435 may generally be an unused RB included in the interlace of the RB set configuration 405. In this example, the PSCCH 430 is configured to be transmitted within the minimum RB set (e.g., RB set configuration 410) based on RB sets having overlapping frequencies within a subband. Therefore, in this example, in the case where the Rx UE is configured with the RB set configuration 405, the PSCCH (e.g., SCI message) may be transmitted in the RB set configuration 410 (e.g., the minimum overlapping RB within the available RB set configuration set). In some aspects, the Rx UE may rate match the PSSCH around the PSCCH 430 carried in the smallest set of RBs (eg, RB set configuration 410).
[0141] Figure 5 An example of an RB set configuration 500 supporting transmission or reception of a centralized FDRA according to one or more aspects of the present disclosure is illustrated. The RB set configuration 500 may implement aspects of the wireless communication system 100 and / or 200 and / or the RB set configuration 300 and / or 400. Various aspects of the RB set configuration 500 may be implemented at or by a UE performing sidelink communication, which may be an example of a corresponding device described herein.
[0142] As discussed herein, aspects of the techniques described herein support a Tx UE sending, providing, or otherwise communicating signaling including an indication of an RB set configuration to one or more sidelink UEs. The Tx UE may identify or otherwise select an RB set configuration based on the type of sidelink communication being performed. For example, the type of sidelink communication may include SCI-1 / SCI-2 sidelink communication, unicast sidelink communication, multicast sidelink communication, and / or broadcast sidelink communication, etc.
[0143] In some aspects, the Tx UE may identify, determine, or otherwise select an RB set configuration from a set of available RB configurations, which may include multiple RB set configurations. The set of available RB set configurations may include at least a minimum overlapping frequency RB set configuration. The minimum RB set configuration may typically include RBs that are shared or otherwise overlapped between RB set configurations in the set of available RB set configurations. The Tx UE may send, provide, or otherwise communicate signaling indicating the RB set configuration to one or more sidelink UEs (e.g., Rx UEs), and perform sidelink communication according to the indicated RB set configuration.
[0144] RB set configuration 500 illustrates another example of various aspects of the minimum RB set configuration discussed herein. For example, the Tx UE may identify or otherwise determine RB sets with overlapping frequencies from the RB set configurations in the set of available RB set configurations. The Tx UE may select, identify or otherwise determine RB sets for RB set configurations within a sub-band, such as a 20 MHz sub-band.
[0145] Generally speaking, when the RB set configuration may be a Tx-centric RB set configuration, the Rx UE may need to identify or otherwise determine an identifier (ID) of the Tx UE in order to adjust the RB set configuration for reception. The ID of the Tx UE may generally be carried or otherwise indicated in the SCI-2 message. In addition, the Tx UE may determine to provide an indication to the Rx UE in the SCI-2 to use a different RB set configuration assumption (e.g., a Tx / Rx-centric RB set configuration or a minimum RB set configuration) when decoding sidelink communications.
[0146] RB set configuration 500 illustrates an example in which SCI-2 resource elements carrying PSSCH 550 are restricted to a minimum RB set containing scheduled SCI-1 (e.g., carried in PSCCH 545). For example, a Tx UE may indicate a first configured RB set (e.g., RB set configuration 505) and a second configured RB set (e.g., RB set configuration 510). Each RB set configuration may include a plurality of RBs 520, of which only nine RBs 520 are shown by way of example. RB 555 may be an unused RB in an interlace. As discussed with respect to RB set configuration 400, PSCCH 545 (e.g., carrying SCI-1) may be transmitted in a minimum RB set configuration 515 in RB set configuration 505. RB set configuration 515 may be between RB set 530 including configured RB set guard band #x-1 and RB set 535 (e.g., configured RB set guard band #x). RB set configuration 510 may also include a minimum RB set configuration (e.g., RB set configuration 525) between RB set 535 and RB set 540 (e.g., configuring RB set guard band #x+1). Thus, in this example, the Tx UE may configure at least a portion of PSSCH 550 to be used to send an SCI message (e.g., SCI-2 message) within the RB set based on an overlap (e.g., based on the minimum RB set configuration for carrying PSCCH 545).
[0147] The Rx UE may perform rate matching according to various aspects of the described techniques. That is, the SCI-2 resource elements may be rate matched with resource elements within the minimum RB set (e.g., RB set configuration 515 and / or RB set configuration 525) and around the first PSSCH demodulation reference signal (DMRS). If the SCI-1FDRA indicates scheduling of PSSCH transmissions across multiple 20MHz sub-bands, there may be multiple resource mapping options.
[0148] One option may include the Rx UE rate matching frequency resources around the interleaving across multiple RBs (e.g., one or more RB sets) indicated in the SCI-1 message for the SCI-2 message. For example, the SCI-2 may rate match frequency resources in scheduled interleaved RBs that are included in the minimum RB set of the scheduled subband and / or in the gaps between the scheduled minimum RB sets (e.g., RB set 535). The FDRA indicated in the SCI-1 may have indicated a scheduled 20 MHz subband. This may be different from other techniques where the SCI-2 rate matches all scheduled subchannels.
[0149] Another option may include the Rx UE performing rate matching on frequency resources around the RB set to receive the PSSCH message. That is, for data resource elements in the PSSCH (e.g., instead of SCI-2 resource elements), the Rx UE may use a fully configured RB set as an SCI message that may indicate which RB set configuration to apply. In this option, whether the RB set configuration configured based on the RRC / RMIS / SIB configuration is known to the Tx UE and / or the Rx UE, the PSSCH may be rate matched based on the configured RB set or the minimum RB set. For RMIS / SIB transmission and / or RRC message exchange, the extended or actual RB set configuration may be unknown. The PSSCH resource elements may be rate matched to the allocated interleaving in the allocated minimum RB set, and rate matched to RBs in the allocated interleaving but between adjacent allocated minimum RB sets. With the RRC / RMSI / SIB configured RB set, the PSSCH may be rate matched to the edge RBs within the configured RB set but outside the minimum RB set. The data resource elements in the PSSCH may be rate matched around the PSCCH and SCI-2 resource elements in the smallest RB set.
[0150] Figure 6 An example of an RB set configuration 600 supporting transmission or reception of a centralized FDRA according to one or more aspects of the present disclosure is illustrated. The RB set configuration 600 may implement aspects of the wireless communication system 100 and / or 200 and / or the RB set configurations 300, 400, and / or 500. Various aspects of the RB set configuration 600 may be implemented at or by a UE performing sidelink communication, which may be an example of a corresponding device described herein.
[0151] As discussed herein, aspects of the techniques described herein support a Tx UE sending, providing, or otherwise communicating signaling including an indication of an RB set configuration to one or more sidelink UEs. The Tx UE may identify or otherwise select an RB set configuration based on the type of sidelink communication being performed. For example, the type of sidelink communication may include SCI-1 / SCI-2 sidelink communication, unicast sidelink communication, multicast sidelink communication, and / or broadcast sidelink communication, etc.
[0152] In some aspects, the Tx UE may identify, determine, or otherwise select an RB set configuration from a set of available RB set configurations, which may include multiple RB set configurations. The set of available RB set configurations may include at least a minimum overlapping frequency RB set configuration. The minimum RB set configuration may typically include RBs that are shared or otherwise overlapped between RB set configurations in the set of available RB set configurations. The Tx UE may send, provide, or otherwise communicate signaling indicating the RB set configuration to one or more sidelink UEs (e.g., Rx UEs), and perform sidelink communication according to the RB set configuration.
[0153] RB set configuration 600 illustrates another example of aspects of the minimum RB set configuration discussed herein. For example, the Tx UE may identify or otherwise determine RB sets with overlapping frequencies from the RB set configurations in the set of available RB set configurations. The Tx UE may select, identify or otherwise determine RB sets for RB set configurations within a sub-band, such as a 20 MHz sub-band.
[0154] RB set configuration 600 illustrates an example in which SCI-2 resource elements carrying PSSCH 650 are restricted to a minimum RB set containing scheduled SCI-1 (e.g., carried in PSCCH 645). For example, a Tx UE may indicate a first configured RB set (e.g., RB set configuration 605) and a second configured RB set (e.g., RB set configuration 610). Each RB set configuration may include a plurality of RBs 620, of which only nine RBs 620 are shown by way of example. RB 655 may be an unused RB in an interlace. As discussed with respect to RB set configuration 400, PSCCH 645 (e.g., carrying SCI-1) may be sent in a minimum RB set configuration 615 in RB set configuration 605. RB set configuration 615 may be between RB set 630 including configured RB set guard band #x-1 and RB set 635 (e.g., configured RB set guard band #x). RB set configuration 610 may also include a minimum RB set configuration (e.g., RB set configuration 625) between RB set 635 and RB set 640 (e.g., configuring RB set guard band #x+1). Thus, in this example, the Tx UE may configure at least a portion of PSSCH 650 to be used to send an SCI message (e.g., SCI-2 message) within the RB set based on an overlap (e.g., based on the minimum RB set configuration for carrying PSCCH 645).
[0155] As discussed above, the Rx UE may perform rate matching according to various aspects of the described techniques. That is, the SCI-2 resource elements may be rate matched with resource elements within the minimum RB set (e.g., RB set configuration 615) and around the first PSSCH DMRS. If the SCI-1FDRA indicates scheduling of PSSCH transmissions across multiple 20MHz sub-bands, there may be multiple resource mapping options.
[0156] One option may include the Rx UE rate matching frequency resources around the RB set to receive the SCI-2 message, where the frequency resources (e.g., RBs) are used to receive the SCI-1 message. For example, the SCI-2 may be rate matched to frequency resources in the scheduled interleaved RBs and included in the smallest set of RBs carrying the associated SCI-2 (e.g., within a 20 MHz sub-band).
[0157] In some aspects, this may include the Rx UE rate matching frequency resources surrounding the extended RB set (eg, RB 620) after the received signal indicates that the RB set configuration has overlapping frequencies.
[0158] Figure 7 An example of an RB set configuration 700 supporting transmission or reception of a centralized FDRA according to one or more aspects of the present disclosure is illustrated. The RB set configuration 700 may implement aspects of the wireless communication system 100 and / or 200 and / or RB set configurations 300, 400, 500, and / or 600. Various aspects of the RB set configuration 700 may be implemented at or by a UE performing sidelink communication, which may be an example of a corresponding device described herein.
[0159] As discussed herein, aspects of the techniques described herein support a Tx UE sending, providing, or otherwise communicating signaling including an indication of an RB set configuration to one or more sidelink UEs. The Tx UE may identify or otherwise select an RB set configuration based on the type of sidelink communication being performed. For example, the type of sidelink communication may include SCI-1 / SCI-2 sidelink communication, unicast sidelink communication, multicast sidelink communication, and / or broadcast sidelink communication, etc.
[0160] In some aspects, the Tx UE may identify, determine, or otherwise select an RB set configuration from a set of available RB set configurations, which may include multiple RB set configurations. The set of available RB set configurations may include at least a minimum overlapping frequency RB set configuration. The minimum RB set configuration may typically include RBs that are shared or otherwise overlapped between RB set configurations in the set of available RB set configurations. The Tx UE may send, provide, or otherwise communicate signaling indicating the RB set configuration to one or more sidelink UEs (e.g., Rx UEs), and perform sidelink communication according to the indicated RB set configuration.
[0161] RB set configuration 700 illustrates an example of a Tx-centric RB set configuration configured for sidelink communication. For broadcast and / or multicast messages, the Tx-centric RB set configuration can support the Tx UE to use a common RB set configuration for all Rx UEs. Therefore, the Tx UE can identify, select or otherwise determine the RB set of the Tx UE that can be used to send broadcast and / or multicast transmissions. In the non-limiting example illustrated by RB set configuration 700, this can include the Tx UE identifying RB set 705, RB set 710, RB set 715 and RB set 720 that can be used to perform multicast and / or broadcast transmissions. The Tx UE can select the RB set of the Tx UE for RB set configuration based on the type of sidelink communication (e.g., multicast and / or broadcast sidelink communication).
[0162] In this non-limiting example, the Rx UE may be configured with RB set 725 and RB set 730 for sidelink communication. The Rx UE may also identify or otherwise determine the RB set of the Tx UE that can be used for sidelink communication, and perform sidelink communication based on the identification. In the non-limiting example illustrated by RB set configuration 700, this may include the Tx UE identifying or otherwise selecting RB sets (e.g., RB set 705, RB set 710, and RB set 715) for sidelink communication (e.g., for multicast and / or broadcast transmission to the Rx UE). That is, the RB set configuration may include RB set 705, RB set 710, and RB set 715.
[0163] In some aspects, the FDRA for sidelink transmissions (including the RB sets used and the RB sets for each RB set) can be transmitter-dependent and (pre-)configured via RMSI / SIB / RRC. For the Tx UE, there can be a single set of RB set settings, and all transmissions can follow these settings. If there are multiple Tx UEs with different RB set settings (e.g., with different RB set configurations) from which the Rx UE is interested in receiving sidelink communications, the Rx UE may need to apply different RB set settings when receiving transmissions, where the applied RB set settings are transmitter-dependent. In some examples, the Tx-centric RB set configuration may be included in or otherwise signaled in RMSI / SIB signaling, and / or (pre-)configured via an RRC message with a minimum RB set configuration. In some aspects, the identified RB set of the Tx UE may be based on the active BWP of the Tx UE.
[0164] In some examples, the Rx UE may identify or otherwise determine the ID of the Tx UE for transmission in order to apply the correct RB set setting (e.g., RB set configuration). For example, the SCI-2 may carry or otherwise convey an indication of the ID of the Tx UE. Thus, the Rx UE may receive an SCI message (e.g., SCI-2) indicating the ID of the Tx UE and identify or otherwise determine the RB set configuration based on the ID.
[0165] Therefore, SCI-2 can be rate matched around the minimum RB set to support reception of SCI-2 when the Rx UE does not know which Tx-centric RB set configuration is applied to the sidelink communication. SCI-1 can also be restricted to the minimum RB set configuration to support the Rx UE to receive the FDRA indication for SCI-2. This may affect the channel estimation procedure because the channel estimation can be performed assuming the minimum RB set configuration and decoding SCI-2, but the channel estimation can be repeated if the actual RB set configuration is different (e.g., wider). In the Tx-centric RB set configuration scenario, the Tx UE can ensure that all Rx UEs can support the guard band RB set configuration.
[0166] In some aspects where the RBs used by the Tx UE exceed the RB set that the Rx UE can receive (filter), the Rx UE can perform puncturing for the RBs outside its reception range, or the Tx UE can fall back to the minimum RB set configuration and retransmit. For the Rx UE, if the RBs used by the Tx UE exceed the RB set that the receiver can receive (filter), the reception can still be successful, where the RBs outside the reception range are specifically punctured by the receiver. For multicast transmission, in the case where an Rx UE does not support such RB set configuration and PSCCH / PSSCH decoding fails, NACK can be reported. Retransmission can fall back to the minimum RB set configuration.
[0167] Thus, as shown in RB set configuration 700, a Tx UE (e.g., UE0 in this example) can perform sidelink communication using RB set 705, RB set 710, and RB set 715, wherein RB set 705 and RB set 710 are respectively within RB set 725 and RB set 730 of a Rx UE (e.g., UE1 in this example). That is, RBs in a portion of RB set 705 outside of the reception RB set 725 of UE1 may be punctured. Thus, according to these techniques, the Rx UE may puncture RBs (e.g., frequency resources) outside of the reception range of the Rx UE.
[0168] Figure 8 An example of an RB set configuration 800 supporting transmission or reception of a centralized FDRA according to one or more aspects of the present disclosure is illustrated. The RB set configuration 800 may implement aspects of the wireless communication system 100 and / or 200 and / or RB set configurations 300, 400, 500, 600, and / or 700. Aspects of the RB set configuration 800 may be implemented at or by a UE performing sidelink communication, which may be an example of a corresponding device described herein.
[0169] As discussed herein, aspects of the techniques described herein support a Tx UE sending, providing, or otherwise communicating signaling including an indication of an RB set configuration to one or more sidelink UEs. The Tx UE may identify or otherwise select an RB set configuration based on the type of sidelink communication being performed. For example, the type of sidelink communication may include SCI-1 / SCI-2 sidelink communication, unicast sidelink communication, multicast sidelink communication, and / or broadcast sidelink communication, etc.
[0170] In some aspects, the Tx UE may identify, determine, or otherwise select an RB set configuration from a set of available RB set configurations, which may include multiple RB set configurations. The set of available RB set configurations may include at least a minimum overlapping frequency RB set configuration. The minimum RB set configuration may typically include RBs that are shared or otherwise overlapped between RB set configurations in the set of available RB set configurations. The Tx UE may send, provide, or otherwise communicate signaling indicating the RB set configuration to one or more sidelink UEs (e.g., Rx UEs), and perform sidelink communication according to the indicated RB set configuration.
[0171] RB set configuration 800 illustrates an example of an Rx-centric RB set configuration configured for sidelink communication. In this design, the Rx UE may send or otherwise provide (and the Tx UE may receive or otherwise obtain) an indication of a requested RB set configuration (e.g., for the Rx UE) and identify or otherwise select the requested RB set configuration as the RB set configuration for the Rx UE to use for sidelink communication.
[0172] For Rx-centric RB set configuration, the Tx UE may know which intended Rx UE is used for sidelink transmission, and therefore use the parameters of the Rx UE for the FDRA indication (e.g., the FDRA indication may be based on the available RB set configuration of the Rx UE). That is, various aspects of the Rx-centric RB set configuration may be based on the Tx UE identification or otherwise know the Rx UE parameters (e.g., request / available RB set configuration). To support this, the Rx UE may notify the Tx UE of its parameters, and / or there may be an earlier signaling exchange (e.g., UE capability message signaling) between the Tx UE and the Rx UE to determine the requested RB set configuration of the Rx UE. In some aspects, the Rx-centric RB set configuration may be used for unicast sidelink transmission. The Rx-centric RB set configuration may also be used for groupcast and / or broadcast sidelink transmission. In some aspects, the Tx UE may signal the Rx-centric RB set configuration to the Rx UE with a matching interpretation of the FDRA (e.g., the request / supported RB set configuration of the Rx UE may be known).
[0173] FDRA interpretation is usually Rx UE dependent. In the case of Rx centric RB set configuration, the Rx UE can simply use its own RB set and guard band configuration to interpret the FDRA indicated in the SCI message from the Tx UE. This can allow the Rx UE to avoid decoding SCI-2 before interpreting the FDRA, thereby avoiding rate matching changes of SCI-2.
[0174] Thus, the Rx-centric RB set configuration may support that the indicated FDRA (including the RB sets used and the RB sets for each RB set) for the sidelink transmission is Rx UE-dependent. For unicast sidelink transmission, the Tx UE may find out the RB set configuration of the Rx UE (e.g., receive an indication thereof) and then use the RB set configuration of the Rx UE to send sidelink communications. In the non-limiting example illustrated by RB set configuration 800, this may include the Tx UE (UE0 in this example) being configured with RB set configuration 805, RB set configuration 810, RB set configuration 815, and RB set configuration 820. The first Rx UE (UE1 in this example) may be configured with or otherwise support RB set configuration 825 and RB set configuration 830. The second Rx UE (UE2 in this example) may be configured with or otherwise support RB set configuration 835 and RB set configuration 840.
[0175] The Tx UE may identify or otherwise determine the RB set configuration of the Rx UE (UE1 and UE2 in this example). For example, the Tx UE may receive or otherwise obtain an indication of the requested RB set configuration from each Rx UE. This may be based on RRC signaling exchanged between the Tx UE and each Rx UE. In some examples, this may be based on a minimum RB set configuration. The Rx UE may use their requested RB set configuration to receive side link transmissions from the Tx UE. For example, the first Rx UE may receive side link transmissions in the RB set configuration 825 and in at least a portion of the RB set configuration 830. The second Rx UE may receive side link transmissions in at least a portion of the RB set configuration 835 and the RB set configuration 840. That is, the RB set configuration 805 of the Tx UE includes more RBs (e.g., wider bandwidth in the frequency domain) than the corresponding RB set configuration 825 of the first Rx UE. Thus, the Tx UE may not send sidelink transmissions to the first Rx UE in edge RBs to save resources, since the first Rx UE will not be able to receive those transmissions. Alternatively, the Tx UE may perform sidelink transmissions in edge RBs and the Rx UE may puncture those RBs. Thus, each Rx UE may receive sidelink transmissions using its own settings (e.g., RB set configuration) based on the indication of the requested RB set configuration being adopted by the Tx UE.
[0176] Fig. 9An example of an RB set switching configuration 900 supporting transmission or reception of a centralized FDRA according to one or more aspects of the present disclosure is illustrated. The RB set switching configuration 900 may implement aspects of the wireless communication system 100 and / or 200 and / or RB set configurations 300, 400, 500, 600, 700, and / or 800. Aspects of the RB set switching configuration 900 may be implemented at or by a UE performing sidelink communication, which may be an example of a corresponding device described herein.
[0177] As discussed herein, aspects of the techniques described herein support a Tx UE sending, providing, or otherwise communicating signaling including an indication of an RB set configuration to one or more sidelink UEs. The Tx UE may identify or otherwise select an RB set configuration based on the type of sidelink communication being performed. For example, the type of sidelink communication may include SCI-1 / SCI-2 sidelink communication, unicast sidelink communication, multicast sidelink communication, and / or broadcast sidelink communication, etc.
[0178] In some aspects, the Tx UE may identify, determine, or otherwise select an RB set configuration from a set of available RB set configurations, which may include multiple RB set configurations. The set of available RB set configurations may include at least a minimum overlapping frequency RB set configuration. The minimum RB set configuration may typically include RBs that are shared or otherwise overlapped between RB set configurations in the set of available RB set configurations. The Tx UE may send, provide, or otherwise communicate signaling indicating the RB set configuration to one or more sidelink UEs (e.g., Rx UEs), and perform sidelink communication according to the RB set configuration.
[0179] Various aspects of the technology described herein provide mechanisms to support distinguishing FDRA modes. That is, the three modes of RB set configuration discussed (e.g., minimum RB set configuration, Tx-centric RB set configuration, and Rx-centric RB set configuration) may introduce issues regarding how a sidelink node determines which mode to apply.
[0180] One option may include the Tx UE identifying or otherwise determining the RB set configuration indication state for the Rx UE, and selecting or otherwise determining the RB set configuration based on the indication state. For example, the RB set configuration mode to be applied may be based on the type of sidelink communication being performed and any implicit / explicit indication of the RB set configuration. As a non-limiting example, this may include using the broadcast type indication used in SCI-2 to carry or otherwise communicate the RB set configuration indication state (e.g., a broadcast type indicating the type of sidelink communication to be performed may implicitly indicate the RB set configuration).
[0181] For unicast side link transmission type, if both Tx UE and Rx UE know the RB set configuration, the Rx-centered RB set configuration can be selected. Otherwise, the minimum RB set configuration can be used as the RB set configuration. In some examples, a bit / field may be included in SCI-1 / 2 to indicate between two modes (e.g., minimum RB set configuration or Rx-centered RB set configuration). For broadcast or multicast side link transmission type, if both Tx UE and Rx UE know the RB set configuration, the Tx-centered RB set configuration can be used. Otherwise, the minimum RB set configuration can be used as the RB set configuration. In some aspects, the broadcast type indicator carried in SCI-2 can be used when selecting the RB set configuration based on the indication state (e.g., based on SCI-2). In order to ensure that SCI-2 is received, SCI-2 can be sent in the minimum RB set (e.g., minimum RB set configuration).
[0182] Another option may include the Tx UE configuring and sending or otherwise providing an SCI message to indicate the RB set configuration to the Rx UE. That is, the Tx UE may use SCI-1 and / or SCI-2 to explicitly indicate which of the three RB set configuration modes is being used / selected. In one example, this may include using a two-bit field in SCI-1 / 2 to explicitly indicate which mode (e.g., RB set configuration) the Tx UE applies to sidelink transmission (e.g., when all three modes are supported). Another option may include using a one-bit field in SCI-1 / 2 to explicitly indicate which mode is applied when two modes are supported (e.g., between a minimum RB set configuration and an Rx-centric RB set configuration).
[0183] As discussed above, different UEs may use different sets of RB sets. In the first option and in a Tx-centric RB set configuration scenario, the Tx UE may transmit (e.g., perform sidelink communications) over a set of RB sets within its active BWP. If the Rx UE covers these RB sets in the Tx UE's active BWP (e.g., monitors these RBs), the Rx UE may receive the sidelink transmission. If the Rx UE covers only a subset of the RB sets in the Tx UE's active BWP, reception may be possible, but the RB sets that fall within the Rx UE's active BWP may be received.
[0184] In the second option and for the Rx-centric RB set configuration scenario, the Tx UE may transmit over a set of RB sets within the Rx UE's active BWP (e.g., for a unicast sidelink transmission type to the Rx UE). In this scenario, the Rx UE may receive the sidelink transmission normally (e.g., based on monitoring its own active BWP). If the set of RB sets of the Tx UE and the set of RB sets of the Rx UE are not exactly the same (e.g., may partially overlap but not completely overlap in the frequency domain), the Tx UE may limit the unicast sidelink communication to the set of RB sets that the Rx UE can receive.
[0185] In some examples, the Rx UE may not be aware of the RB set configuration of the Tx UE. If the Tx UE does not restrict the sidelink transmission to the minimum RB set configuration when the RB set configuration is unknown, there may be additional considerations for Rx UE support. For example, the Rx UE may not have received the RB set configuration of the Tx UE. For some subchannels (interlaces), the exact set of RBs covered by the FDRA may be unknown. Therefore, there may be some uncertain RBs (e.g., edge RBs) at either end of the interlace.
[0186] In one option, the Rx UE may ignore these differences (e.g., unknown RB set configuration of the Tx UE) and continue to attempt to decode the sidelink communication using the RB set configuration of the Rx UE. That is, the RX UE may still attempt to decode the sidelink communication using specific assumptions (such as about rate matching), using its own RB set definition / configuration, or some default values. If the RB set configuration does not match, the decoding attempt may fail. Therefore, when the RB set configuration between the Tx UE and the Rx UE does not match, interworking may be a problem.
[0187] In another option, the Tx UE may indicate the RB set configuration in SCI-1. For example, the Tx UE may indicate the starting RB and number of RBs of the RB set in SCI-1, the number of unused RBs on both edges of the interleaving, etc., at the expense of a larger SCI-1 payload. One of several combinations may be (pre)defined (e.g., per subband). After decoding SCI-1, the Rx UE identifies the RB set used for PSSCH transmission, and may therefore perform DMRS-based channel estimation and successfully decode SCI-2. In some aspects, for SCI-2 decoding, the Rx UE may rate match to the entire RB set.
[0188] In another option, the Tx UE may indicate the RB set configuration in the SCI-2. SCI-2 payloads are typically less expensive than SCI-1 payloads. However, the downside is that for SCI-2 decoding, it may not rely on RB set definition / configuration (e.g., the Rx UE may use this SCI-2 that is rate matched to the minimum RB set configuration). In some aspects, there may still be difficulties in two rounds of DMRS channel estimation.
[0189] Aspects of the techniques described herein may also address SCI-1 size alignment considerations. To support interworking, it is preferred that the SCI-1 is decodable without excessive configuration. An optimized SCI-1 design may depend on the RB set configuration (e.g., how many RB sets are there), but variable SCI-1 sizes may interfere with interworking because the Rx UE may assume that the SCI-1 size used for decoding is incorrect.
[0190] Thus, in some examples, the Tx UE may send or otherwise provide an SCI-1 message to the Rx UE that carries or otherwise conveys an indication of the FDRA, and the Rx UE may identify the RB set configuration based on the FDRA indication. That is, for the FDRA field indicated in the SCI-1, the Rx UE may assume the worst case number of RB sets (4 or 5 RB sets may depend on the maximum supported bandwidth of 80 MHz or 100 MHz, respectively). In the case where the Tx UE uses fewer RB sets, even if the sidelink transmission is limited to a single RB set (e.g., in the case of RMSI / discovery signal transmission), the FDRA may use the same structure as the presence of 4 / 5 RB sets, but only conveys an indication that the resource allocation is limited to a single RB set.
[0191] In some examples, aspects of the techniques may include RB set mode switching for sidelink communications. The mode switching may be performed between a minimum RB set configuration 905, a Tx-centric RB set configuration 910, and an Rx-centric RB set configuration 915. Generally, this may include the Tx UE identifying or otherwise determining an updated type of sidelink communication to be performed (e.g., subsequent sidelink communication), and transitioning from the RB set configuration to an updated RB set configuration for subsequent sidelink communications.
[0192] That is, aspects of the technology described herein address situations where a Tx UE can switch between a Tx-centric RB set configuration, an Rx-centric RB set configuration, and a minimum RB set configuration when each mode is supported. For example, a Tx UE can switch between three RB set configuration modes based on the type of broadcast and whether a link-related RB set configuration is established. At the time of initial establishment, both the Tx UE and the Rx UE can adopt a minimum RB set configuration 905, and subsequently communicate using a Tx-centric RB set configuration 910 (e.g., an updated RB set configuration) signaled via an RMSI / SIB / RRC message and an Rx-centric RB set configuration exchanged via an RRC message per link (e.g., per Rx UE). For broadcast / multicast side link communications, the Tx UE can choose to stay in the minimum RB set configuration 905 or switch to the Tx-centric RB set configuration 910. For the next unicast side link transmission, and if a per-link Rx-centric RB set configuration 915 is available, the Tx UE can switch to the Rx-centric RB set configuration 915. Otherwise, the TxUE may fall back to the minimum RB set configuration 905 .
[0193] For the next multicast / broadcast, if the Tx-centric RB set configuration 910 is available for the target Rx UE, the Tx UE may stay in the Tx-centric RB set configuration 910. Otherwise, the Tx UE may fall back to the minimum RB set configuration 905. For unicast side link communication, the Tx UE may choose to keep the minimum RB set configuration 905 or switch to the per-link Rx-centric RB set configuration 915. For the next unicast side link transmission, if the Rx-centric RB set configuration 915 for the target Rx UE is not configured, the Tx UE may fall back to the minimum RB set configuration 905. Otherwise, the Tx UE may keep the minimum RB set configuration 905. For the next multicast side link transmission, if the Tx-centric RB set configuration 910 is available, the Tx UE may switch to the Tx-centric RB set configuration 910. Otherwise, the Tx UE may fall back to the minimum RB set configuration 905.
[0194] Fig.10 A block diagram 1000 of a device 1005 supporting sending or receiving a centralized FDRA according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of various aspects of the UE 115 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include one or more processors, a memory coupled to the one or more processors, and instructions stored in the memory, which may be executed by the one or more processors to enable the one or more processors to perform the RB set configuration mode indication feature discussed herein. Each of these components may communicate with each other (e.g., via one or more buses).
[0195] The receiver 1010 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to transmitting or receiving centralized FDRA). The information may be communicated to other components of the device 1005. The receiver 1010 may utilize a single antenna or a collection of multiple antennas.
[0196] The transmitter 1015 may provide means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to transmitting or receiving a centralized FDRA). In some examples, the transmitter 1015 may be co-located with the receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or a collection of multiple antennas.
[0197] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of a send or receive-centric FDRA as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.
[0198] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured to or otherwise supports means for performing the functions described herein. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).
[0199] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functions of the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.
[0200] In some examples, communication manager 1020 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in conjunction with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.
[0201] According to examples as disclosed herein, the communication manager 1020 can support wireless communications at a UE. For example, the communication manager 1020 can be configured to or otherwise support a means for sending signaling including an indication of an RB set configuration to one or more sidelink UEs, the RB set configuration being based on a type of sidelink communication to be performed and from a set of available RB set configurations including at least a minimum overlapping frequency RB set configuration. The communication manager 1020 can be configured to or otherwise support a means for performing sidelink communications with one or more sidelink UEs according to the RB set configuration.
[0202] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 can support wireless communications at the UE. For example, the communication manager 1020 can be configured to or otherwise support a means for receiving signaling that includes an indication of an RB set configuration from a set of available RB set configurations based on a type of sidelink communication to be performed, the set of available RB set configurations including at least a minimum overlapping frequency RB set configuration. The communication manager 1020 can be configured to or otherwise support a means for performing sidelink communications with a transmitting sidelink UE according to the RB set configuration.
[0203] By including or configuring a communication manager 1020 according to the examples described herein, the device 1005 (e.g., a processor controlling or otherwise coupled to the receiver 1010, the transmitter 1015, the communication manager 1020, or a combination thereof) can support techniques for improved FDRA configuration / interpretation based on Tx-centric RB set configuration, Rx-centric RB set configuration, or minimum RB set configuration.
[0204] Fig.11 A block diagram 1100 of a device 1105 supporting sending or receiving a centralized FDRA according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of various aspects of the device 1005 or UE 115 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include one or more processors, a memory coupled to the one or more processors, and instructions stored in the memory, which may be executed by the one or more processors to enable the one or more processors to perform the RB set configuration mode indication feature discussed herein. Each of these components may communicate with each other (e.g., via one or more buses).
[0205] The receiver 1110 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to transmitting or receiving centralized FDRA). The information may be communicated to other components of the device 1105. The receiver 1110 may utilize a single antenna or a collection of multiple antennas.
[0206] The transmitter 1115 may provide means for transmitting signals generated by other components of the device 1105. For example, the transmitter 1115 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to transmitting or receiving a centralized FDRA). In some examples, the transmitter 1115 may be co-located with the receiver 1110 in a transceiver module. The transmitter 1115 may utilize a single antenna or a collection of multiple antennas.
[0207] Device 1105 or its various components may be examples of components for performing various aspects of sending or receiving central FDRA as described herein. For example, communication manager 1120 may include RB set indication manager 1125, side link communication manager 1130, or any combination thereof. Communication manager 1120 may be an example of various aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to use or otherwise cooperate with receiver 1110, transmitter 1115, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or integrate with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.
[0208] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a UE. The RB set indication manager 1125 may be configured to or otherwise support means for sending signaling including an indication of an RB set configuration to one or more sidelink UEs, the RB set configuration being based on the type of sidelink communication to be performed and from a set of available RB set configurations including at least a minimum overlapping frequency RB set configuration. The sidelink communication manager 1130 may be configured to or otherwise support means for performing sidelink communications with one or more sidelink UEs in accordance with the RB set configuration.
[0209] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1120 can support wireless communications at the UE. The RB set indication manager 1125 can be configured to or otherwise support means for receiving signaling that includes an indication of an RB set configuration from a set of available RB set configurations based on a type of sidelink communication to be performed, the set of available RB set configurations including at least a minimum overlapping frequency RB set configuration. The sidelink communication manager 1130 can be configured to or otherwise support means for performing sidelink communications with a transmitting sidelink UE in accordance with the RB set configuration.
[0210] In some cases, the RB set indication manager 1125 and / or the sidelink communication manager 1130 can each be a processor (e.g., a transceiver processor or a radio processor or a transmitter processor or a receiver processor) or at least a portion of a processor. The processor can be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the features of the RB set indication manager 1125 and / or the sidelink communication manager 1130 discussed herein. The transceiver processor can be co-located with and / or communicate with (e.g., direct the operation of) a transceiver of a device. The radio processor can be co-located with and / or communicate with (e.g., direct the operation of) a radio of a device (e.g., an NR radio, an LTE radio, a Wi-Fi radio). The transmitter processor can be co-located with and / or communicate with (e.g., direct the operation of) a transmitter of a device. The receiver processor can be co-located with and / or communicate with (e.g., direct the operation of) a receiver of a device.
[0211] Fig.12 A block diagram 1200 of a communication manager 1220 supporting a send or receive centralized FDRA according to one or more aspects of the present disclosure is shown. The communication manager 1220 may be an example of aspects of the communication manager 1020, the communication manager 1120, or both as described herein. The communication manager 1220 or its various components may be examples of components for performing aspects of a send or receive centralized FDRA as described herein. For example, the communication manager 1220 may include an RB set indication manager 1225, a side link communication manager 1230, an RB set sub-band manager 1235, a broadcast type manager 1240, an RB set request manager 1245, an RB set change manager 1250, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).
[0212] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a UE. The RB set indication manager 1225 may be configured to or otherwise support means for sending signaling including an indication of an RB set configuration to one or more sidelink UEs, the RB set configuration being based on the type of sidelink communication to be performed and from a set of available RB set configurations including at least a minimum overlapping frequency RB set configuration. The sidelink communication manager 1230 may be configured to or otherwise support means for performing sidelink communications with one or more sidelink UEs in accordance with the RB set configuration.
[0213] In some examples, RB set sub-band manager 1235 may be configured to or otherwise support means for identifying, within a sub-band, RB sets having frequencies that overlap within each RB set configuration in a set of available RB set configurations. In some examples, RB set sub-band manager 1235 may be configured to or otherwise support means for selecting, based on the identification, RB sets for RB set configurations, wherein the minimum overlapping frequency RB set configuration includes RB sets having frequencies that overlap within the sub-band.
[0214] In some examples, performing sidelink communications includes using RB sets to send SCI messages, multicast messages, groupcast messages, RRC messages, or any combination thereof.
[0215] In some examples, RB set sub-band manager 1235 may be configured or otherwise support means for configuring PSCCH for transmission within a set of RBs based on RBs having frequencies that overlap within a sub-band.
[0216] In some examples, RB set sub-band manager 1235 may be configured or otherwise support means for configuring a portion of the PSSCH for sending an SCI message within a set of RBs based on the RBs having frequencies that overlap within a sub-band.
[0217] In some examples, the broadcast type manager 1240 may be configured to or otherwise support means for identifying RB sets of the UE that may be used to send broadcast transmissions, multicast transmissions, or both, wherein the type of the sidelink communication includes the broadcast transmission, the multicast transmission, or both. In some examples, the broadcast type manager 1240 may be configured to or otherwise support means for selecting an RB set for RB set configuration of the UE based on the type of the sidelink communication, wherein the RB set is associated with an Rx-centric RB set configuration in a set of available RB set configurations.
[0218] In some examples, broadcast type manager 1240 may be configured or otherwise support means for identifying a UE's RB set based on the UE's active BWP.
[0219] In some examples, RB set request manager 1245 may be configured or otherwise support means for receiving an indication of a requested RB set configuration from a sidelink UE. In some examples, RB set request manager 1245 may be configured or otherwise support means for selecting the requested RB set configuration as the RB set configuration based on the indication.
[0220] In some examples, to support providing an indication, RB set indication manager 1225 may be configured to or otherwise support means for identifying an RB set configuration indication state for one or more sidelink UEs based on the type of sidelink communication to be performed. In some examples, to support providing an indication, RB set indication manager 1225 may be configured to or otherwise support means for selecting a minimum overlapping frequency RB set configuration as the RB set configuration based on the RB set configuration indication state.
[0221] In some examples, to support providing an indication, RB set indication manager 1225 may be configured or otherwise support means for configuring one or more SCI messages to indicate an RB set configuration, wherein the signaling includes the one or more SCI messages.
[0222] In some examples, RB set change manager 1250 may be configured or otherwise support means for determining an update type of sidelink communication to be performed for subsequent sidelink communication to be performed. In some examples, RB set change manager 1250 may be configured or otherwise support means for transitioning from an RB set configuration to an updated RB set configuration for subsequent sidelink communication based on the update type of the sidelink communication.
[0223] In some examples, the type of sidelink communication performed includes at least one of unicast sidelink communication, broadcast sidelink communication, groupcast sidelink communication, multicast sidelink communication, or a combination thereof.
[0224] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1220 can support wireless communications at the UE. In some examples, the RB set indication manager 1225 can be configured to or otherwise support means for receiving signaling that includes an indication of an RB set configuration from a set of available RB set configurations based on a type of sidelink communication to be performed, the set of available RB set configurations including at least a minimum overlapping frequency RB set configuration. In some examples, the sidelink communication manager 1230 can be configured to or otherwise support means for performing sidelink communications with a transmitting sidelink UE according to the RB set configuration.
[0225] In some examples, the RB set sub-band manager 1235 may be configured to or otherwise support a component for determining, based on the indication, RB sets in the RB set configuration having overlapping frequencies within each RB set configuration in the set of available RB set configurations. In some examples, performing sidelink communications includes using the RB set to receive an SCI message, a multicast message, a groupcast message, an RRC message, or any combination thereof. In some examples, the physical sidelink control channel is configured to transmit within the RB set based on the RB set having overlapping frequencies within the sub-band. In some examples, a portion of the physical sidelink shared channel is configured to transmit an SCI message within the RB set based on the RB set having overlapping frequencies within the sub-band.
[0226] In some examples, RB set sub-band manager 1235 may be configured or otherwise support means for rate matching frequency resources around interlaces across one or more RB sets indicated in an SCI-1 message for an SCI-2 message.
[0227] In some examples, RB set sub-band manager 1235 may be configured or otherwise support means for rate matching frequency resources around a RB set for receiving SCI-1 messages to receive SCI-2 messages.
[0228] In some examples, RB set sub-band manager 1235 may be configured or otherwise support means for rate matching frequency resources around a RB set to receive a PSSCH.
[0229] In some examples, RB set sub-band manager 1235 may be configured or otherwise support means for rate matching frequency resources around an extended RB set after a received signal indicates that the RB set configuration has overlapping frequencies.
[0230] In some examples, the broadcast type manager 1240 may be configured to or otherwise support means for identifying a set of RBs that may be used to transmit a broadcast transmission, a multicast transmission, or both for a transmitting sidelink UE, wherein the type of the sidelink communication includes a broadcast transmission, a multicast transmission, or both. In some examples, the broadcast type manager 1240 may be configured to or otherwise support means for performing sidelink communication using a set of RBs for a RB set configuration of the transmitting sidelink UE based on the type of the sidelink communication, wherein the RB set is associated with a Tx-centric RB set configuration in a set of available RB set configurations. In some examples, the RB set of the transmitting sidelink UE is based on an active BWP of the Tx UE.
[0231] In some examples, to support obtaining the indication, the broadcast type manager 1240 may be configured or otherwise support means for receiving an SCI message indicating an identifier associated with the Tx UE. In some examples, to support obtaining the indication, the broadcast type manager 1240 may be configured or otherwise support means for identifying an RB set configuration based on the identifier.
[0232] In some examples, broadcast type manager 1240 may be configured or otherwise support means for determining that the RB set spans frequency resources outside the configured RB set of the UE. In some examples, broadcast type manager 1240 may be configured or otherwise support means for puncturing frequency resources outside the configured RB set based on the determination.
[0233] In some examples, the RB set request manager 1245 may be configured to or otherwise support a means for sending an indication of a requested RB set configuration to a transmitting side link UE, wherein the RB set configuration includes the requested RB set configuration. In some examples, the RB set configuration is based on an active BWP of the UE. In some examples, the minimum overlapping frequency RB set configuration is selected as the RB set configuration based on the RB set configuration indication state of the UE.
[0234] In some examples, to support obtaining the indication, the RB set indication manager 1225 may be configured to or otherwise support means for receiving one or more SCI messages indicating the RB set configuration. In some examples, the type of side link communication performed includes at least one of unicast side link communication, broadcast side link communication, groupcast side link communication, multicast side link communication, or a combination thereof.
[0235] In some examples, to support obtaining the indication, the RB set indication manager 1225 may be configured as or otherwise support means for receiving an SCI-1 message indicating the FDRA. In some examples, to support obtaining the indication, the RB set indication manager 1225 may be configured as or otherwise support means for identifying the RB set configuration based on the FDRA.
[0236] In some cases, RB set indication manager 1225, sidelink communication manager 1230, RB set sub-band manager 1235, broadcast type manager 1240, RB set request manager 1245, and / or RB set change manager 1250 may each be a processor (e.g., a transceiver processor or a radio processor or a transmitter processor or a receiver processor) or at least a portion of a processor. The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the features of RB set indication manager 1225, sidelink communication manager 1230, RB set sub-band manager 1235, broadcast type manager 1240, RB set request manager 1245, and / or RB set change manager 1250 discussed herein.
[0237] Fig.13 A diagram of a system 1300 including a device 1305 that supports sending or receiving a centralized FDRA according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of a device 1005, a device 1105, or a UE 115 as described herein, or include components thereof. The device 1305 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1305 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1320, an input / output (I / O) controller 1310, a transceiver 1315, an antenna 1325, a memory 1330, a code 1335, and a processor 1340. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1345).
[0238] I / O controller 1310 can manage input and output signals for device 1305. I / O controller 1310 can also manage peripheral devices that are not integrated into device 1305. In some cases, I / O controller 1310 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1310 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 1310 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1310 may be implemented as part of a processor (such as processor 1340). In some cases, a user may interact with device 1305 via I / O controller 1310 or via hardware components controlled by I / O controller 1310.
[0239] In some cases, the device 1305 may include a single antenna 1325. However, in some other cases, the device 1305 may have more than one antenna 1325 that may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1315 may communicate bidirectionally via one or more antennas 1325, wired or wireless links as described herein. For example, the transceiver 1315 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1315 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1325 for transmission; and demodulating packets received from one or more antennas 1325. The transceiver 1315 or the transceiver 1315 and one or more antennas 1325 may be examples of the transmitter 1015, the transmitter 1115, the receiver 1010, the receiver 1110, or any combination thereof or components thereof as described herein.
[0240] Memory 1330 may include random access memory (RAM) and read-only memory (ROM). Memory 1330 may store computer-readable, computer-executable code 1335 including instructions that, when executed by processor 1340, cause device 1305 to perform various functions described herein. Code 1335 may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some cases, code 1335 may not be directly executable by processor 1340, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1330 may also contain, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0241] Processor 1340 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1340 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1340. Processor 1340 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1330) to cause device 1305 to perform various functions (e.g., functions or tasks that support sending or receiving a centralized FDRA). For example, device 1305 or a component of device 1305 may include processor 1340 and memory 1330 coupled to or coupled to processor 1340, and processor 1340 and memory 1330 are configured to perform various functions described herein.
[0242] According to examples as disclosed herein, the communication manager 1320 may support wireless communications at a UE. For example, the communication manager 1320 may be configured to or otherwise support a means for sending signaling including an indication of an RB set configuration to one or more sidelink UEs, the RB set configuration being based on a type of sidelink communication to be performed and from a set of available RB set configurations including at least a minimum overlapping frequency RB set configuration. The communication manager 1320 may be configured to or otherwise support a means for performing sidelink communications with one or more sidelink UEs according to the RB set configuration.
[0243] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1320 can support wireless communications at the UE. For example, the communication manager 1320 can be configured to or otherwise support a means for receiving signaling that includes an indication of an RB set configuration from a set of available RB set configurations based on a type of sidelink communication to be performed, the set of available RB set configurations including at least a minimum overlapping frequency RB set configuration. The communication manager 1320 can be configured to or otherwise support a means for performing sidelink communications with a transmitting sidelink UE according to the RB set configuration.
[0244] By including or configuring the communication manager 1320 according to examples as described herein, the device 1305 may support techniques for improved FDRA configuration / interpretation based on Tx-centric RB set configuration, Rx-centric RB set configuration, or minimum RB set configuration.
[0245] In some examples, the communication manager 1320 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1315, one or more antennas 1325, or any combination thereof. Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the processor 1340, the memory 1330, the code 1335, or any combination thereof. For example, the code 1335 may include instructions that may be executed by the processor 1340 to cause the device 1305 to perform various aspects of a transmit or receive-centric FDRA as described herein, or the processor 1340 and the memory 1330 may be otherwise configured to perform or support such operations.
[0246] Fig.14 1400 is a flowchart illustrating a method 1400 for supporting sending or receiving a centralized FDRA according to one or more aspects of the present disclosure. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 13The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.
[0247] At 1405, the method may include sending signaling to one or more sidelink UEs including an indication of an RB set configuration based on the type of sidelink communication to be performed and from a set of available RB set configurations including at least a minimum overlapping frequency RB set configuration. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Fig.12 The described RB set instructions manager 1225 performs.
[0248] At 1410, the method may include performing sidelink communications with one or more sidelink UEs according to the RB set configuration. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Fig.12 The side link communication manager 1230 described above is used to perform.
[0249] Fig.15 1 is a flowchart illustrating a method 1500 for supporting sending or receiving a centralized FDRA according to one or more aspects of the present disclosure. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 13 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.
[0250] At 1505, the method may include sending signaling to one or more sidelink UEs including an indication of an RB set configuration based on the type of sidelink communication to be performed and from a set of available RB set configurations including at least a minimum overlapping frequency RB set configuration. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig.12 The described RB set instructions manager 1225 performs.
[0251] At 1510, the method may include identifying RB sets within the sub-band that have frequencies that overlap within each of the available RB set configurations. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig.12 The described RB set sub-band manager 1235 is performed.
[0252] At 1515, the method may include selecting an RB set for RB set configuration based on the identification, wherein the minimum overlapping frequency RB set configuration includes RB sets having frequencies that overlap within the sub-band. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Fig.12 The described RB set sub-band manager 1235 is performed.
[0253] At 1520, the method may include performing sidelink communications with one or more sidelink UEs according to the RB set configuration. The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Fig.12 The side link communication manager 1230 described above is used to perform.
[0254] Fig.16 1 shows a flowchart illustrating a method 1600 for supporting sending or receiving a centralized FDRA according to one or more aspects of the present disclosure. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 13 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.
[0255] At 1605, the method may include sending signaling to one or more sidelink UEs including an indication of an RB set configuration based on the type of sidelink communication to be performed and from a set of available RB set configurations including at least a minimum overlapping frequency RB set configuration. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.12 The described RB set instructions manager 1225 performs.
[0256] At 1610, the method may include identifying a set of RBs of the UE that may be used to send a broadcast transmission, a multicast transmission, or both, wherein the type of the sidelink communication includes a broadcast transmission, a multicast transmission, or both. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig.12 The described broadcast type manager 1240 is implemented.
[0257] At 1615, the method may include selecting an RB set for RB set configuration of the UE based on the type of sidelink communication, wherein the RB set is associated with a Tx-centric RB set configuration in the available RB set configurations. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig.12 The described broadcast type manager 1240 is implemented.
[0258] At 1620, the method may include performing sidelink communications with one or more sidelink UEs according to the RB set configuration. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Fig.12 The side link communication manager 1230 described above is used to perform.
[0259] Fig.17 1700 is a flowchart illustrating a method 1700 for supporting sending or receiving a centralized FDRA according to one or more aspects of the present disclosure. The operations of the method 1700 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE or a component thereof as described herein. Figures 1 to 13 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.
[0260] At 1705, the method may include receiving signaling that includes an indication of an RB set configuration from a set of available RB set configurations based on a type of sidelink communication to be performed, the set of available RB set configurations including at least a minimum overlapping frequency RB set configuration. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig.12 The described RB set instructions manager 1225 performs.
[0261] At 1710, the method may include performing sidelink communications with a transmitting sidelink UE according to the RB set configuration. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig.12 The side link communication manager 1230 described above is used to perform.
[0262] The following provides an overview of various aspects of the disclosure:
[0263] Aspect 1: A method for performing wireless communications at a UE, comprising: sending signaling including an indication of an RB set configuration to one or more sidelink UEs, wherein the RB set configuration is based at least in part on a type of sidelink communication to be performed and is from a set of available RB set configurations including at least a minimum overlapping frequency RB set configuration; and performing the sidelink communication with the one or more sidelink UEs according to the RB set configuration.
[0264] Aspect 2: The method according to Aspect 1 also includes: identifying RB sets having overlapping frequencies in each RB set configuration in the available RB set configuration within a sub-band; and selecting the RB set for the RB set configuration based at least in part on the identification, wherein the minimum overlapping frequency RB set configuration includes the RB sets having overlapping frequencies within the sub-band.
[0265] Aspect 3: The method according to aspect 2, wherein performing the sidelink communication includes: using the RB set to send an SCI message, a multicast message, a groupcast message, an RRC message, or any combination thereof.
[0266] Aspect 4: The method according to any one of aspects 2 to 3 further includes: configuring the PSCCH to be used for transmission within the RB set based at least in part on the RB set having the frequency overlapping within the sub-band.
[0267] Aspect 5: The method according to any one of aspects 2 to 4 further includes: configuring a portion of the PSSCH to be used for sending an SCI message within the RB set based at least in part on the RB set having the frequency overlapping within the sub-band.
[0268] Aspect 6: The method according to any one of Aspects 1 to 5 further includes: identifying an RB set of the UE that can be used to send broadcast transmission, multicast transmission, or both, wherein the type of sidelink communication includes the broadcast transmission, the multicast transmission, or both; and selecting the RB set of the UE for the RB set configuration based at least in part on the type of sidelink communication, wherein the RB set is associated with a transmitter-centric RB set configuration in the available RB set configurations.
[0269] Aspect 7: The method according to aspect 6 also includes: identifying the RB set of the UE based at least in part on the active bandwidth portion of the UE.
[0270] Aspect 8: The method according to any one of Aspects 1 to 7 also includes: receiving an indication of a requested RB set configuration from a sidelink UE; and selecting the requested RB set configuration as the RB set configuration based at least in part on the indication.
[0271] Aspect 9: A method according to any one of Aspects 1 to 8, wherein providing the indication includes: identifying an RB set configuration indication state for the one or more side link UEs based at least in part on the type of side link communication to be performed; and selecting the minimum overlapping frequency RB set configuration as the RB set configuration based at least in part on the RB set configuration indication state.
[0272] Aspect 10: The method according to any one of aspects 1 to 9, wherein providing the indication comprises: configuring one or more SCI messages to indicate the RB set configuration, wherein the signaling comprises the one or more SCI messages.
[0273] Aspect 11: The method according to any one of Aspects 1 to 10 further includes: determining an update type of side link communication to be performed for subsequent side link communication to be performed; and transitioning from the RB set configuration to an updated RB set configuration for the subsequent side link communication based at least in part on the update type of the side link communication.
[0274] Aspect 12: A method according to any one of Aspects 1 to 11, wherein the type of side link communication performed includes at least one of unicast side link communication, broadcast side link communication, groupcast side link communication, multicast side link communication, or a combination thereof.
[0275] Aspect 13: A method for performing wireless communications at a UE, comprising: receiving signaling, the signaling including an indication of an RB set configuration from a set of available RB set configurations based at least in part on a type of side link communication to be performed, the set of available RB set configurations including at least a minimum overlapping frequency RB set configuration; and performing the side link communication with a transmitting side link UE according to the RB set configuration.
[0276] Aspect 14: The method according to aspect 13 also includes: determining, based at least in part on the indication, RB sets in the RB set configurations having frequencies overlapping in each of the RB set configurations in the available RB set configurations.
[0277] Aspect 15: The method according to aspect 14, wherein performing the sidelink communication includes: using the RB set to receive an SCI message, a multicast message, a groupcast message, an RRC message, or any combination thereof.
[0278] Aspect 16: The method according to any one of aspects 14 to 15, wherein the PSCCH is configured to be transmitted within the set of RBs based at least in part on the set of RBs having the frequencies overlapping within a sub-band.
[0279] Aspect 17: The method according to any one of aspects 14 to 16, wherein a portion of the PSSCH is configured to send an SCI message within the set of RBs based at least in part on the set of RBs having the frequencies overlapping within a sub-band.
[0280] Aspect 18: The method according to Aspect 17 further comprises: for the SCI-2 message, performing rate matching on frequency resources around the interlaces across one or more RB sets indicated in the SCI-1 message.
[0281] Aspect 19: The method according to any one of Aspects 17 to 18 further includes: performing rate matching on frequency resources around the RB set to receive an SCI two message, wherein the frequency resources are used to receive an SCI one message.
[0282] Aspect 20: The method according to any one of aspects 17 to 19 further includes: performing rate matching on frequency resources around the RB set to receive the PSSCH.
[0283] Aspect 21: The method according to any one of Aspects 14 to 20 further includes: after the received signal indicates that the RB set configuration has overlapping frequencies, performing rate matching on frequency resources around the extended RB set.
[0284] Aspect 22: The method according to any one of Aspects 13 to 21 further includes: identifying an RB set of the transmitting side link UE that can be used to send broadcast transmission, multicast transmission, or both, wherein the type of side link communication includes the broadcast transmission, the multicast transmission, or both; and performing the side link communication using the RB set configured for the RB set of the transmitting side link UE based at least in part on the type of side link communication, wherein the RB set is associated with a transmitter-centric RB set configuration in the available RB set configuration.
[0285] Aspect 23: The method according to aspect 22, wherein the RB set of the transmitting side link UE is based at least in part on the active bandwidth portion of the transmitting side link UE.
[0286] Aspect 24: A method according to any one of Aspects 22 to 23, wherein obtaining the indication includes: receiving an SCI message indicating an identifier associated with the transmitting side link UE; and identifying the RB set configuration based at least in part on the identifier.
[0287] Aspect 25: The method according to any one of Aspects 22 to 24 further includes: determining that the RB set spans frequency resources outside the configured RB set of the UE; and puncturing the frequency resources outside the configured RB set based at least in part on the determination.
[0288] Aspect 26: The method according to any one of Aspects 13 to 25 further includes: sending an indication of a requested RB set configuration to the transmitting side link UE, wherein the RB set configuration includes the requested RB set configuration.
[0289] Aspect 27: The method according to aspect 26, wherein the RB set configuration is based at least in part on the active bandwidth portion of the UE.
[0290] Aspect 28: The method according to any one of aspects 13 to 27, wherein the minimum overlapping frequency RB set configuration is selected as the RB set configuration based at least in part on an RB set configuration indication state of the UE.
[0291] Aspect 29: The method according to any one of aspects 13 to 28, wherein obtaining the indication comprises: receiving one or more SCI messages indicating the RB set configuration.
[0292] Aspect 30: A method according to any one of Aspects 13 to 29, wherein the type of side link communication performed includes at least one of unicast side link communication, broadcast side link communication, groupcast side link communication, multicast side link communication, or a combination thereof.
[0293] Aspect 31: A method according to any one of Aspects 13 to 30, wherein obtaining the indication comprises: receiving an SCI message indicating a frequency domain resource allocation; and identifying the RB set configuration based at least in part on the frequency domain resource allocation.
[0294] Aspect 32: An apparatus for performing wireless communications at a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 12.
[0295] Aspect 33: An apparatus for wireless communication at a UE, comprising at least one component for performing a method according to any one of aspects 1 to 12.
[0296] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 12.
[0297] Aspect 35: An apparatus for performing wireless communications at a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 13 to 31.
[0298] Aspect 36: An apparatus for wireless communication at a UE, comprising at least one means for performing a method according to any one of aspects 13 to 31.
[0299] Aspect 37: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform a method according to any one of aspects 13 to 31.
[0300] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.
[0301] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.
[0302] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.
[0303] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).
[0304] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored on or sent via a computer-readable medium as one or more instructions or codes. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that various parts of the functions are implemented at different physical locations.
[0305] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that promotes the transfer of computer program from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code member and can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure Any other non-transient medium.In addition, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.
[0306] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items introduced by a phrase such as "at least one of..." or "one or more of...") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on".
[0307] The terms "determine" or "determining" encompass a wide variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, etc. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), etc. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.
[0308] In the drawings, similar components or features may have the same reference number. In addition, various components of the same type may be distinguished by following the reference number with a dash and a second reference number to distinguish between the similar components. If only the first reference number is used in the specification, the description may apply to any of the similar components having the same first reference number, regardless of the second or other subsequent reference numbers.
[0309] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The specific embodiments include specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.
[0310] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: sending signaling to one or more sidelink UEs including an indication of a resource block set configuration based at least in part on a type of sidelink communication to be performed and from a set of available resource block set configurations including at least a minimum overlapping frequency resource block set configuration; as well as The sidelink communications with the one or more sidelink UEs are performed according to the resource block set configuration.
2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: identifying resource block sets within a frequency subband having frequencies that overlap within each resource block set configuration in the set of available resource block set configurations; and The resource block set is selected for the resource block set configuration based at least in part on the identification, wherein the minimum overlapping frequency resource block set configuration includes the resource block sets having frequencies overlapping within the frequency subband.
3. The apparatus of claim 2, wherein performing the sidelink communication comprises: The set of resource blocks is used to send a sidelink control information message, a multicast message, a groupcast message, a radio resource control message, or any combination thereof.
4. The apparatus of claim 2, wherein the instructions are further executable by the processor to cause the apparatus to: A physical sidelink control channel is configured for transmission within the set of resource blocks based at least in part on the set of resource blocks having the frequencies overlapping within the sub-band.
5. The apparatus of claim 2, wherein the instructions are further executable by the processor to cause the apparatus to: A portion of a physical sidelink shared channel is configured for transmitting a sidelink control information message within the set of resource blocks based at least in part on the set of resource blocks having the frequencies overlapping within the sub-band.
6. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: identifying a set of resource blocks available for the UE to send a broadcast transmission, a multicast transmission, or both, wherein the type of sidelink communication includes the broadcast transmission, the multicast transmission, or both; and The resource block set for the resource block set configuration of the UE is selected based at least in part on the type of sidelink communication, wherein the resource block set is associated with a transmitter-centric resource block set configuration in the set of available resource block set configurations.
7. The apparatus of claim 6, wherein the instructions are further executable by the processor to cause the apparatus to: The set of resource blocks for the UE is identified based at least in part on an active bandwidth portion of the UE.
8. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: receiving an indication from a sidelink UE requesting a resource block set configuration; and The requested resource block set configuration is selected as the resource block set configuration based at least in part on the indication.
9. The apparatus of claim 1 , wherein the instructions for providing the indication are executable by the processor to cause the apparatus to: identifying a resource block set configuration indication state for the one or more sidelink UEs based at least in part on the type of sidelink communications to be performed; and The minimum overlapping frequency resource block set configuration is selected as the resource block set configuration based at least in part on the resource block set configuration indication state.
10. The apparatus of claim 1, wherein the instructions for providing the indication are executable by the processor to cause the apparatus to: One or more sidelink control information messages are configured to indicate the resource block set configuration, wherein the signaling includes the one or more sidelink control information messages.
11. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: determining, for subsequent sidelink communications to be performed, an update type of sidelink communications to be performed; and Based at least in part on the update type of sidelink communications, transitioning from the resource block set configuration to an updated resource block set configuration for the subsequent sidelink communications.
12. The apparatus of claim 1, wherein the type of sidelink communication performed comprises at least one of a unicast sidelink communication, a broadcast sidelink communication, a groupcast sidelink communication, a multicast sidelink communication, or a combination thereof.
13. The apparatus of claim 1, wherein the minimum overlapping frequency resource block set configuration comprises a numerical number of resource blocks that are shared among the available resource block set configurations.
14. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving signaling including, based at least in part on a type of sidelink communication to be performed, an indication of a resource block set configuration from a set of available resource block set configurations, the set of available resource block set configurations including at least a minimum overlapping frequency resource block set configuration; as well as The sidelink communication with a transmitting sidelink UE is performed according to the resource block set configuration.
15. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: Resource block sets of the resource block set configurations having frequencies that overlap within each of the resource block set configurations in the set of available resource block set configurations are determined based at least in part on the indication.
16. The apparatus of claim 15, wherein performing the sidelink communication comprises: The set of resource blocks is used to receive a sidelink control information message, a multicast message, a groupcast message, a radio resource control message, or any combination thereof.
17. The apparatus of claim 15, wherein a physical sidelink control channel is configured to transmit within the set of resource blocks based at least in part on the set of resource blocks having the frequencies overlapping within a frequency sub-band.
18. The apparatus of claim 15, wherein a portion of a physical sidelink shared channel is configured to send a sidelink control information message within the set of resource blocks based at least in part on the set of resource blocks having the frequencies overlapping within a sub-band.
19. The apparatus of claim 18, wherein the instructions are further executable by the processor to cause the apparatus to: For the sidelink control information two message, rate matching is performed on frequency resources around the interlaces of one or more resource block sets indicated in the sidelink control information one message.
20. The apparatus of claim 18, wherein the instructions are further executable by the processor to cause the apparatus to: Frequency resources around the resource block set are rate matched to receive a sidelink control information two message, wherein the frequency resources are used to receive a sidelink control information one message.
21. The apparatus of claim 18, wherein the instructions are further executable by the processor to cause the apparatus to: Frequency resources around the resource block set are rate matched to receive a physical sidelink shared channel.
22. The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to: After the received signal indicates that the resource block set configuration has overlapping frequencies, frequency resources around the extended resource block set are rate matched.
23. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: identifying a set of resource blocks of the transmitting sidelink UE that can be used to transmit a broadcast transmission, a multicast transmission, or both, wherein the type of sidelink communication includes the broadcast transmission, the multicast transmission, or both; and Based at least in part on the type of sidelink communication, the sidelink communication is performed using the resource block set for the resource block set configuration of the transmitting sidelink UE, wherein the resource block set is associated with a transmitter-centric resource block set configuration in the set of available resource block set configurations.
24. The apparatus of claim 23, wherein the set of resource blocks for the transmitting sidelink UE is based at least in part on an active bandwidth portion of the transmitting sidelink UE.
25. The apparatus of claim 23, wherein the instructions for obtaining the indication are executable by the processor to cause the apparatus to: receiving a sidelink control information message indicating an identifier associated with the transmitting sidelink UE; and The resource block set configuration is identified based at least in part on the identifier.
26. The apparatus of claim 23, wherein the instructions are further executable by the processor to cause the apparatus to: determining that the resource block set configuration spans frequency resources outside the configured resource block set of the UE; and The frequency resources outside of the set of configured resource blocks are punctured based at least in part on the determination.
27. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: An indication of a requested resource block set configuration is sent to the transmitting side link UE, wherein the resource block set configuration includes the requested resource block set configuration.
28. The apparatus of claim 14, wherein the instructions for obtaining the indication are executable by the processor to cause the apparatus to: One or more sidelink control information messages are received indicating the resource block set configuration.
29. A method for wireless communication at a user equipment (UE), the method comprising: sending signaling to one or more sidelink UEs including an indication of a resource block set configuration based at least in part on a type of sidelink communication to be performed and from a set of available resource block set configurations including at least a minimum overlapping frequency resource block set configuration; as well as The sidelink communications with the one or more sidelink UEs are performed according to the resource block set configuration.
30. A method for wireless communication at a user equipment (UE), the method comprising: receiving signaling including, based at least in part on a type of sidelink communication to be performed, an indication of a resource block set configuration from a set of available resource block set configurations, the set of available resource block set configurations including at least a minimum overlapping frequency resource block set configuration; as well as The sidelink communication with a transmitting sidelink UE is performed according to the resource block set configuration.
