Allocating additional PRB to sidelink communications in order to meet OCB threshold

Abstract

Certain aspects of the present disclosure provide techniques for determining transport block sizes for sidelink communications. In one example, a method for wireless communication by a user equipment includes determining that an occupied channel bandwidth (OCB) threshold for sidelink communication is not satisfied based on an initial allocation of physical resource blocks (PRBs) in one or more sub-channels that do not overlap with a guard band within a resource pool for sidelink communication; allocating one or more additional PRBs from the resource pool to the sidelink communication so as to meet an OCB threshold, where the one or more additional PRSs include at least one of: all partial sub-channel PRBs in the sub-channels in the resource pool that overlap with the guard band portion; or all boundary PRBs of sub-channels within the resource pool but not allocated to the resource pool.

Description

[0001] introduction Technical Field

[0002] Various aspects of this disclosure relate to wireless communication, and more specifically to techniques for determining transport block size for sidelink communication.

[0003] Related technical descriptions

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, broadcasting, or other similar services. These wireless communication systems may employ multiple access technologies that enable communication with multiple users by sharing available wireless communication system resources.

[0005] Despite significant technological advancements in wireless communication systems over the years, challenges remain. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and receivers. Therefore, there is a continuous expectation for improving the technical performance of wireless communication systems, including, for example: improving communication speed and data carrying capacity; improving the efficiency of shared communication media; reducing the power used by transmitters and receivers during communication; improving the reliability of wireless communication; avoiding redundant transmission and / or reception and related processing; improving the coverage area of ​​wireless communication; increasing the number and types of devices that can access the wireless communication system; increasing the ability of different types of devices to communicate with each other; and increasing the number and types of available wireless communication media. Therefore, there is a need for further improvements to wireless communication systems to overcome the aforementioned technical challenges and other obstacles. Summary of the Invention

[0006] One aspect provides a method for wireless communication by a user equipment (UE). The method includes: determining an occupied channel bandwidth (OCB) threshold for the sidelink communication that is not met based on an initial allocation of physical resource blocks (PRBs) in one or more sub-channels that do not overlap with the guard band within a resource pool for sidelink communication; and allocating one or more additional PRBs from the resource pool to the sidelink communication to meet the OCB threshold, wherein the one or more additional PRBs include at least one of: all partial sub-channel PRBs in sub-channels that partially overlap with the guard band within the resource pool; or all boundary PRBs in sub-channels within the resource pool but not allocated to the resource pool.

[0007] On the other hand, a method for wireless communication by a UE is provided. The method includes: receiving sidelink communication using at least one of: all partial subchannel PRBs in a subchannel that partially overlaps with the guard band in the resource pool; or all boundary PRBs in a subchannel within the resource pool but not allocated to the resource pool; determining a transport block size for the sidelink communication; and decoding the sidelink communication based on the transport block size.

[0008] Other aspects provide: one or more means operable to, configured to, or otherwise adapted to perform any part of any method described herein (e.g., such that performance can be implemented by only one means or in a distributed manner across multiple means); one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of one or more means, cause the one or more means to perform any part of any method described herein (e.g., such that instructions can be included in only one computer-readable medium or in a distributed manner across multiple computer-readable media, such that instructions can be executed by only one processor or by multiple processors in a distributed manner, such that...). Each of the one or more means may include one or more processors, and / or enable execution to be performed by only one means or in a distributed manner across multiple means; one or more computer program products embodied on one or more computer-readable storage media, the computer-readable storage media including code for performing any part of any method described herein (e.g., enabling the code to be stored in only one computer-readable medium or in a distributed manner across computer-readable media); and / or one or more means including one or more components for performing any part of any method described herein (e.g., enabling execution to be performed by only one means or by multiple means in a distributed manner). By way of example, an means may include a processing system, a device having a processing system, or a processing system cooperating via one or more networks.

[0009] For illustrative purposes, the following description and figures illustrate certain features. Attached Figure Description

[0010] The accompanying drawings depict certain features of the various aspects described herein and should not be considered as limiting the scope of this disclosure.

[0011] Figure 1 An example wireless communication network is depicted.

[0012] Figure 2 An example decomposed base station architecture is described.

[0013] Figure 3Various aspects of the example base station and example user equipment (UE) are described.

[0014] Figure 4A , Figure 4B , Figure 4C and Figure 4D Various example aspects of data structures used in wireless communication networks are described.

[0015] Figure 5 An example of a resource pool that can be used for sidelink communication is depicted.

[0016] Figure 6 This is a first example illustrating how to determine the total number of PRBs allocated for sidelink communication.

[0017] Figure 7 A second example illustrates how to determine the total number of PRBs allocated for sidelink communication.

[0018] Figure 8 A third example illustrates how to determine the total number of PRBs allocated for sidelink communication.

[0019] Figure 9 A fourth example illustrates how to determine the total number of PRBs allocated for sidelink communication.

[0020] Figure 10 The fifth example illustrates how to determine the total number of PRBs allocated for sidelink communication.

[0021] Figure 11A and Figure 11B The sixth example illustrates how to determine the total number of PRBs allocated for sidelink communication.

[0022] Figure 12 A method for wireless communication is described.

[0023] Figure 13 Another method for wireless communication is described.

[0024] Figure 14 Various aspects of the example communication device are described. Detailed Implementation

[0025] Various aspects of this disclosure provide apparatus, methods, processing systems, and computer-readable media for determining the transport block size for sidelink communication.

[0026] A transport block is a block of data transmitted over the air interface from a transmitter-side wireless communication device to a receiver-side wireless communication device. Specifically, a transport block can include data packets passed between the Media Access Control (MAC) layer and the Physical (PHY) layer of the radio protocol stack. At the transmitter-side wireless communication device, data packets can be passed down from the MAC layer to the PHY layer. At the receiver-side wireless communication device, data packets can be passed up from the PHY layer to the MAC layer. For the receiver-side wireless communication device to decode the transport block received in the signal from the transmitter-side wireless communication device, the receiver-side wireless communication device needs to determine the size of the transport block, also known as the Transport Block Size (TBS).

[0027] Sidelink communication typically involves using a resource pool with multiple subchannels to (e.g., without network intermediaries) directly communicate transport blocks from a transmitter user equipment (UE) to a receiver UE, each of which comprises a number of physical resource blocks (PRBs) corresponding to the configuration of time and frequency resources. The number of PRBs configured for a subchannel within the resource pool can be referred to as the subchannel size. The resource pool may further have one or more sets of resource blocks comprising PRBs. In some cases, the resource pool may also include boundary PRBs not associated with the subchannels, for example, when the subchannel size is not equally divided into the number of PRBs within the resource pool. In some sidelink implementations, the smallest allocatable unit for sidelink communication is the subchannel, and therefore the TBS for sidelink communication is typically a function of the number of subchannels allocated to sidelink communication and the number of PRBs associated with each allocated subchannel, etc.

[0028] When multiple sidelink communications are performed within contiguous resource blocks in a resource pool, guard bands are conventionally used to avoid interference between sidelink communications. Guard bands can be defined to overlap with one or more subchannels. Because (as described above) the smallest allocatable unit for communication in a sidelink is traditionally a subchannel, a guard band overlapping a portion of a subchannel can render all PRBs (including PRBs in the non-overlapping portions of the subchannel—since non-overlapping PRBs cannot be allocated individually) unavailable for that subchannel. This raises several technical problems. For example, wasting non-overlapping PRB resources in subchannels that partially overlap with the guard band reduces spectrum utilization and increases latency. Furthermore, wasting non-overlapping PRB resources may result in failure to meet the Occupied Channel Bandwidth (OCB) threshold (or requirement) for accessing the spectrum.

[0029] OCB thresholds typically refer to a portion of the frequency spectrum that a wireless communication system should use when transmitting data, and may include the bandwidth used for information signals as well as the bandwidth required for modulation, filtering, and other signal processing functions. OCB thresholds can be established, for example, to ensure efficient use of the frequency spectrum and that different wireless systems can coexist without interfering with each other. In some cases, OCB thresholds can be defined relative to the nominal bandwidth of a given frequency band. For example, an OCB threshold might require that 80% of the nominal bandwidth of a given frequency band be used when accessing the frequency band for purposes such as sidelink transmissions and other unlicensed uses. When the OCB requirement for the allocated bandwidth is not met, intended sidelink communication can be completely blocked.

[0030] The aspects described herein provide a technical solution to the aforementioned technical problem by utilizing PRBs in sub-channels that partially overlap with the guard band and / or PRBs (e.g., boundary PRBs) within the resource pool that are not associated with the sub-channels. For example, according to the aspects described herein, a UE can be configured to: determine, based on an initial allocation of PRBs in one or more sub-channels that do not overlap with the guard band within the resource pool for sidelink communication, that an OCB threshold for sidelink communication is not met; and based on this determination, allocate one or more additional PRBs from the resource pool to sidelink communication to meet the OCB threshold, wherein the one or more additional PRBs include at least one of the following: all partial sub-channel PRBs in sub-channels that partially overlap with the guard band within the resource pool; or all boundary PRBs in sub-channels within the resource pool but not allocated to the resource pool. These aspects have the beneficial technical effects of improving spectral efficiency by utilizing more PRBs within a given resource pool and reducing latency by transmitting more data within a given resource pool. In addition to these beneficial technical effects, a UE implementing the aspects described herein can overcome power spectral density (PSD) limitations by utilizing more bandwidth within the resource pool.

[0031] Conventional methods for determining TBS may not function correctly when utilizing additional PRBs within the resource pool (such as some aspects described herein). Another aspect described herein provides a technical solution to this problem by adapting TBS determination to account for the use of additional PRBs (such as PRBs in boundary PRBs not associated with subchannels) in sidelink communication. This results in a beneficial technical effect, as the transmitter UE can utilize more bandwidth while the receiver UE can still correctly determine the TBS for successful decoding of sidelink transmissions.

[0032] An introduction to wireless communication networks

[0033] The techniques and methods described herein can be used in a variety of wireless communication networks. While aspects may be described herein using terms commonly associated with 3G, 4G, and / or 5G wireless technologies, aspects of this disclosure are equally applicable to other communication systems and standards not explicitly mentioned herein.

[0034] Figure 1 An example of a wireless communication network 100 in which the aspects described herein can be implemented is depicted.

[0035] Generally, wireless communication network 100 includes various network entities (optionally, network elements or network nodes). Network entities are typically communication devices and / or communication functions performed by communication devices (e.g., user equipment (UE), base station (BS), components of the BS, servers, etc.). Since such communication devices are part of wireless communication network 100 and facilitate wireless communication, they may be referred to as wireless communication devices. For example, various functions of the network and various devices associated with and interacting with the network may be considered network entities. Furthermore, wireless communication network 100 includes terrestrial and non-terrestrial aspects. The terrestrial aspect includes ground-based network entities (e.g., BS 102), and the non-terrestrial aspect includes satellite 140 and aircraft 145, which may include onboard network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and UEs.

[0036] In the depicted example, wireless communication network 100 includes BS 102, UE 104 and one or more core networks (such as Evolved Packet Core (EPC) 160 and 5G Core (5GC) network 190) that interoperate to provide communication services over various communication links, including wired and wireless links.

[0037] Figure 1 Various example UE 104s are described, which may more generally include: cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players, cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, Internet of Things (IoT) devices, always-on (AON) devices, edge processing devices, or other similar devices. UE 104 may also be more generally referred to as mobile devices, wireless devices, stations, mobile stations, subscriber stations, mobile subscriber stations, mobile units, subscriber units, wireless units, remote units, remote devices, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, and others.

[0038] BS 102 communicates wirelessly with UE 104 via communication link 120 (e.g., transmitting or receiving signals to or from UE 104). Communication link 120 between BS 102 and UE 104 may include uplink (UL) transmission (also referred to as reverse link) from UE 104 to BS 102 and / or downlink (DL) transmission (also referred to as forward link) transmission from BS 102 to UE 104. In various aspects, communication link 120 may utilize multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity.

[0039] BS 102 may typically include: NodeB, enhanced NodeB (eNB), next-generation enhanced NodeB (ng-eNB), next-generation NodeB (gNB or gNodeB), access point, transceiver base station, radio base station, radio transceiver, transceiver functionality, transmit / receive point, and / or others. Each of BS 102 provides communication coverage for a corresponding coverage area 110, which may sometimes be referred to as a cell, and in some cases may overlap (e.g., a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of a macro cell). For example, BS may provide communication coverage for macro cells (covering a relatively large geographic area), pico cells (covering a relatively small geographic area, such as a stadium), femtocells (covering a relatively small geographic area (e.g., a home)), and / or other types of cells.

[0040] Although BS 102 is described as a single communication device in various aspects, it can be implemented in a variety of configurations. For example, one or more components of the base station can be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, to name a few. In another example, various aspects of the base station can be virtualized. More generally, a base station (e.g., BS 102) can include components located at a single physical location or components located at various physical locations. In examples where the base station includes components located at various physical locations, the various components can each perform functions, such that the various components collectively achieve functionality similar to a base station located at a single physical location. In some aspects, a base station including components located at various physical locations can be referred to as a decomposed radio access network architecture (such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture). Figure 2 An example decomposed base station architecture is depicted and described.

[0041] Different BSs 102 within the wireless communication network 100 can also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G). For example, a BS 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) can interface with 5GC 190 via a second backhaul link 184. BSs 102 can communicate directly or indirectly with each other (e.g., via EPC 160 or 5GC 190) on a third backhaul link 134 (e.g., X2 interface), which can be wired or wireless.

[0042] Wireless communication network 100 can subdivide the electromagnetic spectrum into various categories, bands, channels, or other characteristics. In some aspects, subdivision is provided based on wavelength and frequency, where frequency may also be referred to as carrier, subcarrier, channel, frequency modulation, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 410MHz-7125MHz, which is often (interchangeably) referred to as “sub-6GHz”. Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250MHz-52,600MHz, which is sometimes (interchangeably) referred to as “millimeter wave” (“mmW” or “mmWave”). Base stations configured to communicate using mmWave / near mmWave radio bands (e.g., mmWave base stations such as BS 180) can utilize beamforming (e.g., 182) with UEs (e.g., 104) to improve path loss and range.

[0043] The communication link 120 between BS 102 and, for example, UE 104 can be via one or more carriers, which may have different bandwidths (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz and / or other MHz) and may be aggregated in various ways. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL).

[0044] Compared to lower-frequency communication, communication using higher frequency bands may have higher path loss and shorter range. Therefore, some base stations (e.g., Figure 1The beamforming 182 of the BS 180 (180) with the UE 104 can be used to improve path loss and range. For example, the BS 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, the BS 180 may transmit beamformed signals to the UE 104 in one or more transmit directions 182''. The UE 104 may receive beamformed signals from the BS 180 in one or more receive directions 182''. The UE 104 may also transmit beamformed signals to the BS 180 in one or more transmit directions 182''. The BS 180 may also receive beamformed signals from the UE 104 in one or more receive directions 182''. The BS 180 and UE 104 may then perform beamforming training to determine the optimal receive and transmit directions for each of the BS 180 and UE 104. It is worth noting that the transmit and receive directions of the BS 180 may be the same or different. Similarly, the transmission and reception directions of UE 104 may or may not be the same.

[0045] The wireless communication network 100 also includes a Wi-Fi AP 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, unlicensed spectrum in 2.4 GHz and / or 5 GHz.

[0046] Some UEs 104 may use device-to-device (D2D) communication links 158 to communicate with each other. The D2D communication link 158 may use one or more sidelink channels, such as physical sidelink broadcast channel (PSBCH), physical sidelink discovery channel (PSDCH), physical sidelink shared channel (PSSCH), physical sidelink control channel (PSCCH), and / or physical sidelink feedback channel (PSFCH).

[0047] EPC 160 may include various functional components, including: Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and / or Packet Data Network (PDN) Gateway 172, as in the illustrated example. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connectivity management.

[0048] Generally, user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP service 176, which may include, for example, the Internet, intranet, IP Multimedia Subsystem (IMS), packet-switched (PS) streaming service, and / or other IP services.

[0049] The BM-SC 170 provides functionality for MBMS user service dispatch and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, can be used to authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and / or can be used to schedule MBMS transmissions. The MBMS gateway 168 can be used to distribute MBMS services to BS 102 belonging to a Broadcast-Specific Service Single Frequency Network (MBSFN) area, and / or can be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0050] 5GC 190 may include various functional components, including: Access and Mobility Management Function (AMF) 192, other AMFs 193, Session Management Function (SMF) 194, and User Plane Function (UPF) 195. AMF 192 can communicate with Unified Data Management (UDM) 196.

[0051] AMF 192 is the control node that handles signaling between UE 104 and 5GC 190. AMF 192 provides services such as Quality of Service (QoS) flow and session management.

[0052] Internet Protocol (IP) packets are transmitted via UPF 195, which connects to IP service 197 and provides the UE with IP address allocation and other functions for 5GC 190. IP service 197 may include, for example, the Internet, intranet, IMS, PS streaming service, and / or other IP services.

[0053] In various aspects, to give a few examples, network entities or network nodes can be implemented as aggregated base stations, decomposed base stations, components of base stations, integrated access and backhaul (IAB) nodes, relay nodes, and sidelink nodes.

[0054] Figure 2An example decomposed base station 200 architecture is depicted. The decomposed base station 200 architecture may include one or more central units (CUs) 210, which may communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 through one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) framework 205, or both. CUs 210 may communicate with one or more distributed units (DUs) 230 via corresponding midhaul links (such as F1 interfaces). DUs 230 may communicate with one or more radio units (RUs) 240 via corresponding fronthaul links. RUs 240 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, UE 104 may be served simultaneously by multiple RUs 240.

[0055] Each unit in a cell (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO frame 205) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each unit in the cell, or an associated processor or controller providing instructions to the unit's communication interface, may be configured to communicate with one or more other units via a transmission medium. For example, these units may include a wired interface configured to receive signals or transmit signals to one or more other units via a wired transmission medium. Additionally or alternatively, the unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive signals on a wireless transmission medium or transmit signals to one or more other units, or both.

[0056] In some aspects, CU 210 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by CU 210. CU 210 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP)), control plane functions (e.g., Central Unit-Control Plane (CU-CP)), or combinations thereof. In some implementations, CU 210 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, CU-UP units can communicate bidirectionally with CU-CP units via an interface such as an E1 interface. CU 210 can be implemented to communicate with DU 230 for network control and signaling purposes, as needed.

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

[0058] Lower-layer functionality can be implemented by one or more RU 240s. In some deployments, an RU240 controlled by a DU 230 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both, at least in part based on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UE 104s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration enables the implementation of the DU 230 and CU 210 in cloud-based RAN architectures such as vRAN architectures.

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

[0060] The non-RT RIC 215 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 225. The non-RT RIC 215 can be coupled to or communicate with the near-RT RIC 225, such as via an A1 interface. The near-RT RIC 225 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via data collection and actions through an interface such as an E2 interface connecting one or more CU 210s, one or more DU 230s, or both, and O-eNBs to the near-RT RIC 225.

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

[0062] Figure 3 Various aspects of examples BS 102 and UE 104 are described.

[0063] Generally, BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-334t (collectively referred to as 334), transceivers 332a-332t (collectively referred to as 332) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., data source 312) and the wireless reception of data (e.g., data sink 339). For example, BS 102 can transmit and receive data between BS 102 and UE 104. BS 102 includes a controller / processor 340 that can be configured to implement the various functions described herein related to wireless communication.

[0064] Generally, UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-352r (collectively referred to as 352), transceivers 354a-354r (collectively referred to as 354) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., retrieved from data source 362) and the wireless reception of data (e.g., provided to data sink 360). UE 104 includes a controller / processor 380 that can be configured to implement the various functions described herein related to wireless communication.

[0065] Regarding example downlink transmission, BS 102 includes a transmission processor 320 that can receive data from data source 312 and control information from controller / processor 340. This control information may be for a Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid Automatic Repeat Request (HARQ) Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Group Common PDCCH (GC PDCCH), and / or others. In some examples, this data may be for a Physical Downlink Shared Channel (PDSCH).

[0066] The transmitter processor 320 can process (e.g., encode and symbol map) data and control information to obtain data symbols and control symbols, respectively. The transmitter processor 320 can also generate reference symbols (such as those for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS)).

[0067] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, and / or reference symbols where applicable, and can provide the output symbol stream to the modulators (MODs) in transceivers 332a-332t. Each modulator in transceivers 332a-332t can process its corresponding output symbol stream to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signal from the modulators in transceivers 332a-332t can be transmitted via antennas 334a-334t respectively.

[0068] To receive downlink transmissions, UE 104 includes antennas 352a-352r that receive downlink signals from BS 102 and provide the received signals to demodulators (DEMODs) in transceivers 354a-354r respectively. Each demodulator in transceivers 354a-354r can adjust (e.g., filter, amplify, down-convert, and digitize) the corresponding received signal to obtain an input sample. Each demodulator can further process the input sample to obtain the received symbols.

[0069] The RX MIMO detector 356 acquires received symbols from all demodulators in transceivers 354a-354r, performs MIMO detection on the received symbols where applicable, and provides the detected symbols. The receive processor 358 processes (e.g., demodulates, deinterleaves, and decodes) the detected symbols, provides the decoded data for UE 104 to data sink 360, and provides the decoded control information to controller / processor 380.

[0070] Regarding example uplink transmission, UE 104 also includes a transmit processor 364 that receives and processes data from data source 362 (e.g., for PUSCH) and control information from controller / processor 380 (e.g., for Physical Uplink Control Channel (PUCCH)). Transmit processor 364 may also generate reference symbols for reference signals (e.g., for Sounding Reference Signal (SRS)). Symbols from transmit processor 364 may be pre-decoded by TX MIMO processor 366, where applicable, further processed by modulators in transceivers 354a-354r (e.g., for SC-FDM), and transmitted to BS 102.

[0071] At BS 102, uplink signals from UE 104 can be received by antennas 334a-334t, processed by demodulators in transceivers 332a-332t, detected where applicable by RX MIMO detector 336, and further processed by receiver processor 338 to obtain decoded data and control information transmitted by UE 104. Receiver processor 338 can provide the decoded data to data sink 339 and the decoded control information to controller / processor 340.

[0072] Memory 342 and memory 382 can store data and program code for BS 102 and UE 104, respectively.

[0073] Scheduler 344 can schedule UE to transmit data on the downlink and / or uplink.

[0074] In various respects, BS 102 can be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" can refer to various mechanisms that output data, such as from data source 312, scheduler 344, memory 342, transmit processor 320, controller / processor 340, TX MIMO processor 330, transceiver 332a-332t, antenna 334a-334t, and / or other aspects described herein. Similarly, "receiving" can refer to various mechanisms that acquire data, such as from antenna 334a-334t, transceiver 332a-332t, RX MIMO detector 336, controller / processor 340, receive processor 338, scheduler 344, memory 342, and / or other aspects described herein.

[0075] In various respects, UE 104 can also be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms that output data, such as from data source 362, memory 382, ​​transmit processor 364, controller / processor 380, TX MIMO processor 366, transceiver 354a-354t, antenna 352a-352t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms that acquire data, such as from antenna 352a-352t, transceiver 354a-354t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, ​​and / or other aspects described herein.

[0076] In some respects, the processor can be configured to perform various operations (such as those associated with the methods described herein) and to send (output) data to or receive data from another interface configured to send or receive data, respectively.

[0077] Figure 4A , Figure 4B , Figure 4C and Figure 4D Describes the use of wireless communication networks (such as Figure 1 All aspects of the data structure of the wireless communication network 100.

[0078] Specifically, Figure 4A Figure 400 is an example of the first subframe within a 5G (e.g., 5G NR) frame structure. Figure 4B Figure 430 illustrates an example of a DL channel within a 5G subframe. Figure 4C Figure 450 illustrates an example of the second subframe within a 5G frame structure, and Figure 4DFigure 480 illustrates an example of a UL channel within a 5G subframe.

[0079] Wireless communication systems can utilize Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems can also support half-duplex operation using Time Division Duplex (TDD). OFDM and Single-Carrier Frequency Division Multiplexing (SC-FDM) will (e.g., as...) Figure 4B and Figure 4D The system bandwidth (as depicted in the text) is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0080] Wireless communication frame structures can be frequency division duplex (FDD), where for a specific set of subcarriers, subframes within that set are dedicated to either deep (DL) or ultra-low (UL). Wireless communication frame structures can also be time division duplex (TDD), where for a specific set of subcarriers, subframes within that set are dedicated to both DL and UL.

[0081] exist Figure 4A and Figure 4C In this example, the wireless communication frame structure is TDD, where D stands for DL, U for UL, and X is flexibly used between DL and UL. The UE can configure the time slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). In the depicted example, a 10ms frame is divided into 10 equal-sized 1ms subframes. Each subframe may include one or more time slots. In some examples, each time slot may include 7 or 14 symbols, depending on the time slot format. Subframes may also include micro-slots, which typically have fewer symbols than the entire time slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0082] In some respects, the number of slots within a subframe is based on the slot configuration and parameter set. For example, for slot configuration 0, different parameter sets (μ) 0 to 5 allow for 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow for 2, 4, and 8 slots per subframe, respectively. Therefore, for slot configuration 0 and parameter set μ, there are 14 symbols / slot and 2µ slots / subframe. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to... kHz, where μ is the parameter set from 0 to 5. Thus, the parameter set... It has a subcarrier spacing of 15 kHz and a parameter set It has a subcarrier spacing of 480 kHz. The symbol length / duration is negatively correlated with the subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D It provides slot configuration 0 with 14 symbols per slot and parameter set with 4 slots per subframe. Example: The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0083] like Figure 4A , Figure 4B , Figure 4C and Figure 4D As depicted, the resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)) extending for, for example, 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0084] like Figure 4A As illustrated in the example, some REs in the RE carry information for the UE (e.g., Figure 1 and Figure 3 The reference (pilot) signal (RS) for the UE (104) may include a demodulation RS (DMRS) and / or a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).

[0085] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0086] The Primary Synchronization Signal (PSS) can be located within symbol 2 of a specific subframe of the frame. The PSS is generated by the UE (e.g., Figure 1 and Figure 3 104) is used to determine subframe / symbol timing and physical layer identifier.

[0087] The secondary synchronization signal (SSS) can be located in symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identifier group number and radio frame timing.

[0088] Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block. The MIB provides the System Frame Number (SFN) and the number of Restricted Frames (RBs) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information (such as System Information Blocks (SIBs)) not transmitted via the PBCH, and / or paging messages.

[0089] like Figure 4C As illustrated, some REs in the REs carry DMRS for channel estimation at the base station (indicated as R for a particular configuration, but other DMRS configurations are possible). The UE may transmit DMRS for PUCCH and DMRS for PUSCH. PUSCH DMRS may be transmitted, for example, in the first or second symbol preceding the PUSCH. PUCCH DMRS may be transmitted in different configurations depending on whether a short or long PUCCH is being transmitted and depending on the specific PUCCH format used. UE104 may transmit a Sounding Reference Signal (SRS). SRS may be transmitted, for example, in the last symbol of a subframe. SRS may have a comb structure, and the UE may transmit SRS on one of the comb structures within that comb structure. SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0090] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCI.

[0091] Various factors related to using unallocated physical resource blocks for sidelink communication in order to meet the occupied channel bandwidth threshold. aspect

[0092] Figure 5 Describes what can be used, such as in the above text relative to Figure 1 and Figure 3 An example of resource pool 502 describing sidelink communication between two UEs.

[0093] Resource pool 502 includes a first resource block set 504A and a second resource block set 504B separated by a guard band 506 (e.g., an intra-cell guard band). Resource pool 502 also includes eight sub-channels (indexed 0 to 7), each of which in this example comprises 10 physical resource blocks (PRBs). In other examples, different numbers of sub-channels and different numbers of PRBs per sub-channel may be used.

[0094] exist Figure 5 In the example, subchannel mapping begins with the first PRB of resource pool 502 and continues sequentially within resource pool 502 according to the subchannel size (e.g., which may be defined by the number of PRBs within each subchannel). Therefore, the first subchannel (subchannel 0) is aligned with the first boundary (leftmost) of resource pool 502. However, because the subchannel size may not always be evenly divided across the resource pool size, some PRBs within resource pool 502 may not be mapped to subchannels. For example, resource pool 502 includes a “boundary PRB” 510, which is not mapped to a subchannel (not associated with a subchannel).

[0095] When subchannels are allocated for sidelink transmission, the smallest resource allocation granularity can be the subchannel. Therefore, if a subchannel is allocated for sidelink communication, all PRBs within that subchannel are also allocated for sidelink communication. This means that when a subchannel overlapping with the guard band is allocated for sidelink communication, the PRBs within the guard band are also allocated for sidelink communication. Therefore, subchannels overlapping with the guard band are typically not used at all. While PRB-level resource allocation is possible, this can incur significant signaling overhead.

[0096] exist Figure 5 In the example, guard band 506 separates the first resource block set 504A and the second resource block set 504B, and partially overlaps with sub-channels 3 and 4. Guard bands such as 506 are typically used to separate narrow frequency ranges of two wider frequency ranges (e.g., the first resource block set 504A and the second resource block set 504B), allowing simultaneous transmission over a wider frequency range without co-interference. It is noteworthy that guard band 506 reserves some PRBs (Programmable Resource Blocks) in the partially overlapping sub-channels 3 and 4 that are technically usable for data transmission, as these are not within the guard band itself, but rather due to the aforementioned resource allocation granularity. The PRBs within the sub-channels partially overlapping with guard band 506 that are technically usable for data transmission are referred to as “partial sub-channel PRBs” 508A and 508B.

[0097] It is worth noting that if some sub-channels PRB 508A and 508B and boundary PRB 510 are not used for data transmission, the Occupied Channel Bandwidth (OCB) threshold (alternatively referred to as the bandwidth occupancy threshold) for resource pool 502 may not be met, and data transmission may be delayed. More generally, if some sub-channels PRB 508A and 508B and boundary PRB 510 are not used—even if the OCB threshold is met—data transmission resources are still wasted, which reduces spectral efficiency and increases latency—two technical problems of conventional sidelink resource allocation methods.

[0098] Therefore, the aspects described herein relate to utilizing a portion of the sub-channels PRBs 508A and 508B and / or the boundary PRB 510 (collectively referred to as "unallocated" or "unmapped" PRBs or "residual" PRBs) within resource pool 502. These aspects have the beneficial technical effects of improving spectral efficiency by utilizing more PRBs within a given resource pool and reducing latency by transmitting more data within a given resource pool. Thus, the aspects described herein provide a technical solution to the technical problem of satisfying the OCB threshold while observing the guard band within the resource pool.

[0099] Specifically, in some aspects described herein, a UE (e.g., a sidelink UE) can be configured to use the boundary PRB and / or some subchannel PRB for sidelink communication (e.g., for sidelink transmission and reception) if the OCB threshold cannot be met without using the boundary PRB and / or some subchannel PRB.

[0100] In one respect, the boundary PRB (e.g., 510) can be connected to adjacent sub-channels (e.g., Figure 5 Subchannel 7 in the example is associated with, or considered as, an independent subchannel for which the subchannel size (e.g., in PRBs) is smaller than the nominal subchannel size. For example, boundary PRB 510 can be mapped to subchannel 8 (not depicted) and comprises six PRBs, whereas in this example, the nominal subchannel size for subchannels 0 through 7 is ten PRBs.

[0101] Considering that the Physical Sidelink Control Channel (PSCCH) is transmitted in the lowest sub-channel among the sub-channels allocated to the PSSCH, if the lowest sub-channel only includes a portion of the sub-channel PRBs, the available PRBs for the PSCCH may be smaller compared to the complete sub-channel, which will degrade PSCCH decoding performance. Furthermore, if the UE punctures resource elements in the PRBs of the lowest sub-channels overlapping with the guard band, a portion of the control information may be lost, further reducing PSCCH reliability. To mitigate the impact on PSCCH transmission when boundary PRBs and / or partial sub-channel PRBs are used for sidelink transmission, boundary PRBs and / or partial sub-channel PRBs associated with larger (or higher) sub-channel indices can be assigned a higher priority than boundary PRBs or partial sub-channel PRBs associated with smaller (or lower) sub-channel indices. Generally, unallocated or residual PRBs (e.g., boundary and / or partial sub-channel PRBs) can then be allocated to sidelink transmission in descending order of their associated sub-channel indices until the OCB threshold is met. This increases the chance that the starting subchannel used for transmission is a complete subchannel (e.g., subchannel 5) rather than a partial subchannel (e.g., subchannel 4).

[0102] The OCB threshold can typically be defined relative to the allocated RB set. For example, if only one RB set is allocated (e.g., RB set 0), then the PSSCH must occupy at least the threshold amount of resources in RB set 0 (e.g., 80% of the resources). Similarly, if two RB sets are allocated (e.g., RB sets 0 and 1), then the PSSCH must occupy at least 80% of the resources in RB sets 0 and 1. Here, we assume the OCB threshold for resource block set 504B is 32 PRBs. Transmissions mapped only to the complete subchannels 5-7 will have only 30 PRBs compared to the threshold. According to the aspects described herein, the PRB associated with the highest subchannel index (here, boundary PRB 510) can be allocated to the transmission to satisfy the OCB threshold. Therefore, in this example, two PRBs from boundary PRB 510 can be allocated to the transmission so that the OCB threshold is satisfied.

[0103] Various aspects related to determining the transport block size when utilizing boundary and partial sub-channel PRB .

[0104] When unallocated or residual PRBs in the resource pool, such as partial sub-channel PRBs and boundary PRBs, are used for sidelink communication (such as those mentioned above relative to...), Figure 5 When described, the conventional method for determining the Transport Block Size (TBS) can be adapted to take into account any additional PRB.

[0105] Typically, to determine the TBS used for sidelink communication, the UE can first determine the number of resource elements (REs) within a time slot, and then determine the total number of REs allocated for the Physical Sidelink Shared Channel (PSSCH). In one example, the UE determines the total number of REs allocated for the PSSCH based on the following:

[0106]

[0107] in It is the number of REs allocated for PSSCH within the PRB. It is the total number of PRBs allocated for PSSCH. This is the total number of REs occupied by the Physical Side Link Control Channel (PSCCH) and the PSCCH Demodulation Reference Signal (DMRS), and It is the number of decoded modulation symbols generated for Level 2 SCI transmission (before replication for Level 2), such as those described in Section 8.1.3.2 of 3GPP TS 38.214 v17.2.0.

[0108] The various aspects described in this article are based on, for example, relative to Figures 6 to 11B To determine the total amount of PRB allocated in more detail ( This is to account for unallocated or residual PRBs in sidelink communication. The total number of allocated PRBs can then be used to determine the TBS used for sidelink communication.

[0109] Figure 6 This describes how to determine the total number of PRBs allocated for sidelink communication. The first example is where the nominal subchannel size is (pre-)configured.

[0110] In this example, data for sidelink transmission on the PSSCH is allocated to subchannels 0-3 within resource block set 604A of resource pool 602, and subchannel 3 overlaps with guard band 606. Since only RB set 0 604A is allocated to the PSSCH, the PRBs of subchannel 3, which overlaps with guard band 606, may not be used for the PSSCH. Only a portion of the PRBs of subchannel 3 are used for the PSSCH. Note that subchannel 4 also overlaps with guard band 606, but it is not allocated for PSSCH transmission.

[0111] here, The nominal subchannel size is determined based on the nominal subchannel size, which can be pre-configured or signaled by the network entity or peer UE (e.g., via PC5-RRC signaling). For example, here the nominal subchannel size is 25 PRBs, and therefore... .

[0112] For subchannel 3 that overlaps with guard band 606, the transmitting UE can perform rate matching based on the full subchannel size including the PRBs that overlap with guard band 606, rather than solely on the PRBs that do not overlap with guard band 606. However, since guard band 606 should not be used for transmission in this example, the transmitting UE can puncture the transmission of PRB 608 that overlaps with guard band 606. In this context, puncturing refers to reducing redundancy in transmitted data by removing the decoded bits of the REs mapped to PRB 608 that overlaps with guard band 606. Punching can be used in conjunction with error correction codes to add redundancy to data while selectively removing punctured data. Therefore, the total amount of data that needs to be transmitted can be reduced while still maintaining a high level of error correction capability.

[0113] Figure 7 This describes how to determine the total number of PRBs allocated for sidelink communication. The second example is that a reference subchannel size is pre-configured for the resource pool.

[0114] In this example, data for the first sidelink transmission (PSSCH 1) is allocated to sub-channels 2 and 3 within resource block set 704A of resource pool 702. Since only RB set 0 704A is allocated to PSSCH 1, the PRB of sub-channel 3, which overlaps with guard band 706, may not be used for PSSCH 1. Only a portion of the PRB of sub-channel 3 is used for PSSCH 1. In the second example, data for the second sidelink transmission (PSSCH 2) is allocated to sub-channels 5 and 6 within resource block set 704B of resource pool 702. Here, sub-channels 3 and 4 overlap with guard band 706.

[0115] here, It can be based on the reference subchannel size instead of... Figure 6 The reference subchannel size is determined in the example. In some respects, the reference subchannel size can be configured, for example, according to a resource pool such as resource pool 702 (pre-configured). In some respects, a reference subchannel size for a resource pool can be reused, or a new reference subchannel size can be configured for a resource pool.

[0116] In this example, The number of subchannels determined to be allocated to sidelink transmissions (e.g., PSSCH or PSCCH) is multiplied by the reference subchannel size. For example, given a reference subchannel size of 25 PRBs per subchannel, this would be for PSSCH 1 (occupying subchannels 2 and 3) and PSSCH 2 (occupying subchannels 5 and 6). .

[0117] In some respects, to avoid needing to significantly increase the decoding rate, thresholds can be (pre-)configured so that only when the number of partial sub-channel PRBs exceeds the threshold can partial sub-channel PRBs be used for PSSCH transmission. For example, sub-channel 3 has 20 partial sub-channel PRBs, which is greater than the example threshold of 15, while sub-channel 4 has only 2 partial sub-channel PRBs, which is less than the example threshold of 15. Therefore, sub-channel 3 is assigned to PSSCH 1, while sub-channel 4 is not assigned to either PSSCH 1 or PSSCH 2.

[0118] Figure 8 This describes how to determine the total number of PRBs allocated for sidelink communication. A third example of this approach involves determining the reference subchannel size based on the minimum number of PRBs that do not overlap with the guard band among multiple assigned subchannels.

[0119] In this example, similar to Figure 7 In the example, data for first sidelink transmission (PSSCH 1) is allocated to sub-channels 2 and 3 within resource block set 804A of resource pool 802. Since only RB set 0 804A is allocated to PSSCH 1, the PRB of sub-channel 3, which overlaps with guard band 806, may not be used for PSSCH 1. Only a portion of the PRB of sub-channel 3 is used for PSSCH. In the second example, data for second sidelink transmission (PSSCH 2) is allocated to sub-channels 5 and 6 within resource block set 804B of resource pool 802. Here, sub-channels 3 and 4 overlap with guard band 806.

[0120] here, The reference subchannel size is determined based on the minimum number of PRBs that do not overlap with guard band 806 across multiple allocated subchannels. For example, for resource block set 804A, the minimum number of PRBs that do not overlap with guard band 806 is 20 in subchannel 3, and therefore for PSSCH 1 (occupying subchannels 2 and 3), the reference subchannel size is 20 PRBs per subchannel. Therefore, for PSSCH 1, Although the sub-channel allocation is the same, this is different from Figure 7 The examples are different. For PSSCH 2 (occupying sub-channels 5 and 6), the minimum number of PRBs that do not overlap with guard band 806 is 25, therefore Note that, with Figure 7 Compared to the previous example, this configuration may result in a lower decoding rate.

[0121] Figure 9 This describes how to determine the total number of PRBs allocated for sidelink communication. The fourth example is that the reference subchannel size is determined based on the weighted number of PRBs among the multiple assigned subchannels.

[0122] In this example, data for sidelink transmission (PSSCH) is allocated to sub-channels 2 and 3 within resource block set 904A of resource pool 902. Here, sub-channels 3 and 4 overlap with guard band 906. Since only RB set 0 904A is allocated to PSSCH, the PRBs of sub-channel 3, which overlaps with guard band 906, may not be used for PSSCH. Only a portion of the PRBs of sub-channel 3 are used for PSSCH.

[0123] here, The reference subchannel size is determined based on the weighted number of PRBs among the multiple allocated subchannels.

[0124] For example, the weighted quantity of PRB can be determined as follows:

[0125] ,

[0126] floor ),or

[0127] ceil( ),

[0128] in It is the weight associated with the sub-channels that do not overlap with guard band 906. This is the number of sub-channels that do not overlap with guard band 906. These are the weights associated with the sub-channels that overlap with guard band 906. It is the number of sub-channels that overlap with guard band 906. It is the number of partial subchannel PRBs of the i-th subchannel overlapping with guard band 906, and floor is the largest integer less than or equal to x that takes a real number x as input (sometimes by...). The instruction is given to the function that outputs x, and ceil is the smallest integer greater than or equal to x (sometimes indicated by...). Functions that indicate (instructions). In various aspects, and It can be predefined or configured. For example, if we consider the average weighted number of PRBs, = = .

[0129] Therefore, the total number of PRBs ( This can be determined as the number of sub-channels allocated to sidelink communication (PSSCH in this example) multiplied by a reference sub-channel size, where the reference sub-channel size is based on the weights described above. For example, let here... = =½, (Refer to sub-channel 2) (Refer to sub-channel 3) ,but = Or when using the floor function Or when using the ceil function .

[0130] Figure 10 This describes how to determine the total number of PRBs allocated for sidelink communication. The fifth example, in which the reference subchannel size is defined only for subchannels that overlap with the guard band.

[0131] In this example, data used for sidelink transmission (PSSCH) is allocated to sub-channels 2 to 4 within resource block sets 1004A and 1004B of resource pool 1002. Here, sub-channels 3 and 4 overlap with guard band 1006. Since both RB set 01004A and RB set 11004B are allocated to PSSCH, the intra-cell guard band 1006 between them can be used for PSSCH.

[0132] In this example, for the sub-channel that does not overlap with guard band 1006 (here, sub-channel 2), the method used to determine... The pre-configured sub-channel size associated with, for example, resource pool 1002. For sub-channels overlapping with guard band 1006 (here, sub-channels 3 and 4), the reference sub-channel size is determined based on, for example, the minimum, maximum, or average number of PRBs outside guard band 1006 in one or more sub-channels overlapping with guard band 1006.

[0133] Therefore, here The number of sub-channels allocated that do not overlap with guard band 1006 can be determined by multiplying the configured sub-channel size by adding the number of sub-channels allocated that overlap with guard band 1006 by multiplying the reference sub-channel size (e.g., based on the minimum, maximum, or average number of PRBs as described above).

[0134] For example, subchannel 2, which does not overlap with guard band 1006, has 25 configured PRBs. Subchannel 3, which overlaps with guard band 1006, has 20 PRBs that do not overlap with guard band 1006. Subchannel 4, which also overlaps with guard band 1006, has 2 PRBs that do not overlap with guard band 1006. Therefore, the reference subchannel size is based on: a minimum of two PRBs outside guard band 1006 (associated with subchannel 4); a maximum of twenty PRBs outside guard band 1006 (associated with subchannel 3); and an average of eleven PRBs outside guard band 1006 (associated with subchannels 3 and 4). Therefore, The maximum measure is 25+20+20=65, the minimum measure is 25+2+2=29, or the average measure is 25+11+11=47.

[0135] Figure 11A and Figure 11B This describes how to determine the total number of PRBs allocated for sidelink communication. The sixth example is in which the reference subchannel size is dynamically indicated by the transmitting UE.

[0136] exist Figure 11A In this configuration, data from the same transmitting UE used for sidelink transmissions (PSSCH 1 and PSSCH 2) is allocated to sub-channels 2 to 4 within resource block sets 1104A and 1104B of resource pool 1102, with PSSCH allocated to sub-channels 1 and 3 and PSSCH 2 allocated to sub-channel 4. Sub-channels 3 and 4 overlap with guard band 1106. Since both RB sets 1004A and 1004B are allocated to transmissions from the same UE 104, guard band 1106 can be used. For PSSCH 1, the PRB in sub-channel 3 that overlaps with guard band 1106 can be used. For PSSCH 2, the PRB in sub-channel 4 that overlaps with guard band 1106 can be used.

[0137] In this example, the transmitting UE indicates whether a partial or full subchannel size should be used as the reference subchannel size for subchannels overlapping with guard band 1106. It is noteworthy that when PSSCH 1 and PSSCH 2 are transmitted by the same transmitting UE, there is no interference issue between PSSCH 1 and PSSCH 2, therefore all PRBs can be used, including those overlapping with guard band 1106. In other words, the transmitting UE can indicate that the full subchannel size should be used as the reference subchannel size even for subchannels overlapping with guard band 1106.

[0138] Therefore, in Figure 11AIn the example, where PSSCH 1 and PSSCH 2 are transmitted by the same transmitting UE, the transmitting UE can instruct the full subchannels to be used for subchannels 3 and 4 respectively, and therefore reference subchannel size 25 is used for subchannels 3 and 4, and The number of sub-channels allocated that do not overlap with guard band 1106 can be determined by multiplying the configured sub-channel size by the number of sub-channels allocated that overlap with guard band 1106 by multiplying the indicated reference sub-channel size. In this case, the number of PRBs corresponding to the allocation of PSSCH 1 is... And the number of PRBs corresponding to the allocation of PSSCH 2 is .

[0139] exist Figure 11B In the example, where the transmitting UE transmits PSSCH only in subchannels 2 and 3, since only RB set 1104A is allocated to PSSCH, the PRB overlapping with guard band 1106 in subchannel 3 can be omitted, and the transmitting UE can indicate that a portion of the subchannel is used for subchannel 3. Therefore, for subchannel 3, a reference subchannel size 20 (e.g., a portion of the subchannel size) is considered, and in this case... It can be determined as =45.

[0140] Example operations performed by user equipment

[0141] Figure 12 It shows the use of UE (such as Figure 1 and Figure 3 Method 1200 for wireless communication of UE 104.

[0142] Method 1200 begins at step 1205, where the initial allocation of PRBs in one or more sub-channels that do not overlap with the guard band within the resource pool for sidelink communication determines the OCB threshold that is not met for sidelink communication.

[0143] Then, method 1200 proceeds to step 1210, wherein one or more additional PRBs are allocated from the resource pool to the sidelink communication to satisfy the OCB threshold, wherein the one or more additional PRBs include at least one of the following: all partial subchannel PRBs in the subchannels that partially overlap with the guard band in the resource pool; or all boundary PRBs in the subchannels that are within the resource pool but not allocated to the resource pool.

[0144] In one respect, in order to allocate one or more additional PRBs for sidelink communication, the UE allocates any available boundary PRBs before allocating any available partial subchannel PRBs.

[0145] In one aspect, in order to allocate one or more additional PRBs for sidelink communication, the UE allocates any available PRB with a higher subchannel index before allocating any available PRB with a lower subchannel index.

[0146] In one aspect, method 1200 further includes associating a boundary PRB within a resource pool with a subchannel within the resource pool that has the highest subchannel index.

[0147] In one aspect, method 1200 further includes associating a boundary PRB within the resource pool with a new subchannel, the new subchannel comprising a smaller number of PRBs compared to the configured subchannel size of all other subchannels in the resource pool.

[0148] In one aspect, method 1200 further includes: determining the transport block size for PRB-based initial allocation and sidelink communication of one or more additional PRBs, based at least in part on a pre-configured nominal subchannel size.

[0149] In one aspect, method 1200 further includes performing rate matching on a given subchannel based on all PRBs that overlap with the guard band in a given subchannel that are assigned to sidelink communication and overlap with the guard band.

[0150] In one aspect, method 1200 further includes punching sidelink communication in any PRB that overlaps with the guard band.

[0151] In one aspect, method 1200 further includes: determining the transport block size for PRB-based initial allocation and sidelink communication of one or more additional PRBs, at least in part based on the reference subchannel size.

[0152] In one respect, the reference subchannel size is pre-configured for the resource pool.

[0153] In one respect, the total number of PRBs for transport blocks used for sidelink communication is equal to the number of subchannels allocated to sidelink communication multiplied by the number of PRBs associated with the reference subchannel size.

[0154] In one aspect, method 1200 further includes: allocating partial subchannel PRBs to one or more additional PRBs based on the fact that the number of partial subchannel PRBs is greater than a threshold.

[0155] In one aspect, method 1200 further includes determining a reference subchannel size based on the minimum number of PRBs that do not overlap with the guard band in the subchannels allocated to sidelink communication.

[0156] In one aspect, method 1200 further includes: determining a reference subchannel size based on a weighting function, the weighting function including a first weight associated with a subchannel assigned to sidelink communication and not overlapping with the guard band and a second weight associated with a subchannel assigned to sidelink communication and overlapping with the guard band.

[0157] In one respect, the weighting function is , It is the first weight. It is the second weight. It is the number of sub-channels allocated to sidelink communication that do not overlap with the guard band. It is the number of sub-channels allocated to sidelink communication and overlapping with the guard band. It is the number of partial subchannel PRBs of the i-th subchannel that overlap with the guard band.

[0158] In one aspect, method 1200 further includes rounding the output value of the weighting function to either the nearest integer value lower than the output value or the nearest integer value higher than the output value before determining the reference subchannel size.

[0159] In one respect, and It is pre-configured.

[0160] In one respect, = = .

[0161] In one aspect, method 1200 further includes: only for subchannels allocated to sidelink communication and overlapping with the guard band; and determining a reference subchannel size based on one of: the minimum number of partial subchannel PRBs overlapping with the guard band in the subchannels allocated to sidelink communication; the maximum number of partial subchannel PRBs overlapping with the guard band in the subchannels allocated to sidelink communication; or the average number of partial subchannel PRBs overlapping with the guard band in the subchannels allocated to sidelink communication.

[0162] In one aspect, method 1200 further includes determining the transport block size based on a reference subchannel size allocated to sidelink communication and overlapping with the guard band, and a pre-configured subchannel size associated with a resource pool for subchannels allocated to sidelink communication and not overlapping with the guard band.

[0163] In one aspect, the total number of PRBs for transport blocks used for sidelink communication is equal to the number of subchannels allocated to sidelink communication and overlapping with the guard band multiplied by the number of PRBs associated with the reference subchannel size plus the number of subchannels allocated to sidelink communication and not overlapping with the guard band multiplied by the number of PRBs associated with the pre-configured subchannel size.

[0164] In one aspect, method 1200 further includes transmitting an indication of a reference subchannel size to user equipment intended to receive sidelink communications.

[0165] In one aspect, the indication only applies to subchannels that overlap with the guard band and are assigned to sidelink communication, indicating whether a portion of the subchannel or the entire subchannel is used as the reference subchannel size.

[0166] In one aspect, the total number of PRBs for transport blocks used for sidelink communication is equal to the number of subchannels allocated to sidelink communication and overlapping with the guard band multiplied by the number of PRBs associated with the reference subchannel size plus the number of subchannels allocated to sidelink communication and not overlapping with the guard band multiplied by the number of PRBs associated with the pre-configured subchannel size.

[0167] In some respects, sidelink communication includes one or both of PSCCH communication and PSSCH communication.

[0168] In one aspect, method 1200 further includes: performing sidelink communication using an initial allocation of a PRB and one or more additional PRBs.

[0169] In one aspect, method 1200 or any aspect thereof may be made by means of a device (such as...) Figure 14 The communication device 1400 performs the operation, and the device includes various components operable to, configured to, or adapted to perform the method 1200. The communication device 1400 is described in more detail below.

[0170] Generally, without explicit instruction from the transmitter UE or receiver UE, the various aspects of method 1200 described above can be performed by the transmitter UE or receiver UE. For example, the transmitter UE can perform aspects of method 1200 to prepare and transmit sidelink communication, and the receiver UE can perform aspects of method 1200 to receive and decode sidelink communication.

[0171] It should be noted that Figure 12 This is merely one example of a method, and other methods that include fewer, additional, or alternative steps may also be consistent with this disclosure.

[0172] Figure 13 It shows the use of UE (such as Figure 1and Figure 3 Method 1300 for wireless communication of UE 104.

[0173] Method 1300 begins at step 1305, wherein sidelink communication is received using at least one of the following: all partial subchannel PRBs in subchannels that partially overlap with the guard band in the resource pool; or all boundary PRBs in subchannels that are within the resource pool but not allocated to the resource pool.

[0174] Then, method 1300 proceeds to step 1310, where the transport block size for sidelink communication is determined.

[0175] Then, method 1300 proceeds to step 1315, where the sidelink communication is decoded based on the transport block size.

[0176] In one aspect, method 1300 further includes receiving an indication of the size of a reference subchannel to a UE intended to receive sidelink communication.

[0177] In one aspect, method 1300 further includes: determining the transport block size for PRB-based initial allocation and sidelink communication of one or more additional PRBs, at least in part based on the reference subchannel size.

[0178] In one aspect, method 1300 or any aspect thereof may be made by means of a device (such as...) Figure 14 The communication device 1400 performs the operation, and the device includes various components operable to, configured to, or adapted to perform the method 1300. The communication device 1400 is described in more detail below.

[0179] It should be noted that Figure 13 This is merely one example of a method, and other methods that include fewer, additional, or alternative steps may also be consistent with this disclosure.

[0180] Example communication device

[0181] Figure 14 Various aspects of the example communication device 1400 are described. In some aspects, the communication device 1400 is user equipment, such as those described above relative to... Figure 1 and Figure 3 The UE 104 described.

[0182] Communication device 1400 includes a processing system 1402 coupled to a transceiver 1446 (e.g., a transmitter and / or receiver). Transceiver 1446 is configured to transmit and receive signals for communication device 1400 via antenna 1448, such as various signals as described herein. Processing system 1402 may be configured to perform processing functions of communication device 1400, including processing signals received by and / or to be transmitted by communication device 1400.

[0183] Processing system 1402 includes one or more processors 1404. In various aspects, the one or more processors 1404 may represent one or more of a receive processor 358, a transmit processor 364, a TX MIMO processor 366, and / or a controller / processor 380, as relative to... Figure 3 As described. One or more processors 1404 are coupled to a computer-readable medium / memory 1424 via a bus 1444. In some aspects, the computer-readable medium / memory 1424 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1404, enable the one or more processors 1404 to execute and cause the one or more processors to perform actions related to... Figure 12 The described method 1200 or any aspect thereof, including regarding Figure 12 Any additional steps or sub-steps described; and relative to Figure 13 The described method 1300 or any aspect thereof, including regarding Figure 13 Any additional steps or sub-steps described. Note that references to processors performing the functions of communication device 1400 may include one or more processors, such as performing the functions of communication device 1400 in a distributed manner.

[0184] In the depicted example, computer-readable medium / memory 1424 stores code 1426 for determination, code 1428 for allocation, code 1430 for execution, code 1432 for punching, code 1434 for rounding, code 1436 for transmission, code 1438 for reception, code 1440 for decoding, and code 1442 for association. Processing of codes 1426 to 1442 enables communication device 1400 to execute and allows the communication device to perform relative to Figure 12 The described method 1200 or any aspect thereof; and relative to Figure 13 The method described 1300 or any aspect thereof.

[0185] One or more processors 1404 include circuitry configured to implement (e.g., execute) code stored in computer-readable medium / memory 1424, including circuitry 1406 for determining, circuitry 1408 for allocating, circuitry 1410 for executing, circuitry 1412 for punching, circuitry 1414 for rounding, circuitry 1416 for transmitting, circuitry 1418 for receiving, circuitry 1420 for decoding, and circuitry 1422 for associating. Processing using the circuitry 1406 to 1422 for determining can enable the communication device 1400 to execute and allow the communication device to perform relative to Figure 12 The described method 1200 or any aspect thereof; and relative to Figure 13 The method described 1300 or any aspect thereof.

[0186] More generally, components used for communication, sending, transmitting, or outputting for transmission may include Figure 3 The UE104 illustrated includes a transceiver 354, an antenna 352, a transmit processor 364, a TX MIMO processor 366, and / or a controller / processor 380. Figure 14 The transceiver 1446 and / or antenna 1448 of the communication device 1400, and / or Figure 14 One or more processors 1404 of the communication device 1400. Components for communicating, receiving, or acquiring may include... Figure 3 The UE 104 illustrated includes a transceiver 354, an antenna 352, a receiver processor 358, and / or a controller / processor 380. Figure 14 The transceiver 1446 and / or antenna 1448 of the communication device 1400, and / or Figure 14 One or more processors 1404 of the communication device 1400 in the middle.

[0187] Example Terms

[0188] Specific implementation examples are described in the following numbered clauses:

[0189] Clause 1: A method for wireless communication by a UE, the method comprising: determining an OCB threshold not satisfied for said sidelink communication based on an initial allocation of PRBs in one or more subchannels that do not overlap with the guard band within a resource pool for sidelink communication; allocating one or more additional PRBs from the resource pool to the sidelink communication to satisfy the OCB threshold, wherein said one or more additional PRBs include at least one of: all partial subchannel PRBs in subchannels that partially overlap with the guard band in the resource pool; or all boundary PRBs in subchannels within the resource pool but not allocated to the resource pool.

[0190] Clause 2: The method according to Clause 1, wherein in order to allocate the one or more additional PRBs to the sidelink communication, the UE allocates any available boundary PRBs before allocating any available partial subchannel PRBs.

[0191] Clause 3: The method according to Clause 2, wherein, in order to allocate the one or more additional PRBs to the sidelink communication, the UE allocates any available PRB with a higher subchannel index before allocating any available PRB with a lower subchannel index.

[0192] Clause 4: The method according to any one of Clauses 1 to 3 further comprises: associating the boundary PRB within the resource pool with the subchannel within the resource pool that has the highest subchannel index.

[0193] Clause 5: The method according to any one of Clauses 1 to 4 further comprises: associating a boundary PRB within the resource pool with a new subchannel, the new subchannel comprising a smaller number of PRBs compared to the subchannel size configured for all other subchannels in the resource pool.

[0194] Clause 6: The method according to any one of Clauses 1 to 5 further comprises: determining, at least in part, the transport block size for the PRB-based initial allocation and the sidelink communication of the one or more additional PRBs based on a pre-configured nominal subchannel size.

[0195] Clause 7: The method according to Clause 6 further comprises: performing rate matching on the given subchannel based on all PRBs that overlap with the guard band in the given subchannel that are assigned to the sidelink communication and overlap with the guard band.

[0196] Clause 8: The method described in Clause 6 further includes: punching the side link communication in any PRB that overlaps with the guard band.

[0197] Clause 9: The method according to any one of Clauses 1 to 8 further comprises: determining, at least in part, the transport block size for the sidelink communication based on the initial allocation of the PRB and the one or more additional PRBs, based on a reference subchannel size.

[0198] Clause 10: The method according to Clause 9, wherein the reference subchannel size is pre-configured for the resource pool.

[0199] Clause 11: The method according to Clause 9, wherein the total number of PRBs for the transport blocks used for the sidelink communication is equal to the number of subchannels allocated to the sidelink communication multiplied by the number of PRBs associated with the reference subchannel size.

[0200] Clause 12: The method according to Clause 9 further includes: allocating the partial subchannel PRBs to the one or more additional PRBs based on the number of partial subchannel PRBs being greater than a threshold.

[0201] Clause 13: The method according to Clause 11 further comprises: determining the reference subchannel size based on the minimum number of PRBs that do not overlap with the guard band in the subchannels allocated to the sidelink communication.

[0202] Clause 14: The method according to Clause 11 further comprises: determining the reference subchannel size based on a weighting function, the weighting function including a first weight associated with a subchannel assigned to the sidelink communication and not overlapping with the guard band and a second weight associated with a subchannel assigned to the sidelink communication and overlapping with the guard band.

[0203] Clause 15: The method described in Clause 14, wherein: the weighting function is , It is the first weight. It is the second weight. It is the number of sub-channels allocated to the sidelink communication that do not overlap with the guard band. It is the number of sub-channels allocated to the sidelink communication and overlapping with the guard band. It is the number of partial subchannel PRBs of the i-th subchannel that overlap with the guard band.

[0204] Clause 16: The method according to Clause 15 further comprises: rounding the output value of the weighting function to either the nearest integer value lower than the output value or the nearest integer value higher than the output value before determining the reference subchannel size.

[0205] Clause 17: The method described in accordance with Clause 15, wherein and It is pre-configured.

[0206] Clause 18: The method described in accordance with Clause 15, wherein = = .

[0207] Clause 19: The method according to Clause 9 further comprises: only for subchannels allocated to the sidelink communication and overlapping with the guard band; and determining the reference subchannel size based on one of: the minimum number of partial subchannel PRBs overlapping with the guard band in the subchannels allocated to the sidelink communication; the maximum number of partial subchannel PRBs overlapping with the guard band in the subchannels allocated to the sidelink communication; or the average number of partial subchannel PRBs overlapping with the guard band in the subchannels allocated to the sidelink communication.

[0208] Clause 20: The method according to Clause 19 further comprises: determining the transport block size based on the reference subchannel size of the subchannels allocated to the sidelink communication and overlapping with the guard band and the pre-configured subchannel size of the subchannels allocated to the sidelink communication and not overlapping with the guard band, which is associated with the resource pool.

[0209] Clause 21: The method according to Clause 20, wherein the total number of PRBs for the transport block used for the sidelink communication is equal to the number of subchannels allocated to the sidelink communication and overlapping with the guard band multiplied by the number of PRBs associated with the reference subchannel size plus the number of subchannels allocated to the sidelink communication and not overlapping with the guard band multiplied by the number of PRBs associated with the pre-configured subchannel size.

[0210] Clause 22: The method according to Clause 9 further includes: transmitting an indication of the size of the reference subchannel to a user equipment intended to receive the sidelink communication.

[0211] Clause 23: The method according to Clause 22, wherein the indication is only for subchannels allocated to the sidelink communication that overlap with the guard band, indicating whether a portion of the subchannel or the entire subchannel is used as the reference subchannel size.

[0212] Clause 24: The method according to Clause 22, wherein the total number of PRBs for the transport blocks used for the sidelink communication is equal to the number of subchannels allocated to the sidelink communication and overlapping with the guard band multiplied by the number of PRBs associated with the reference subchannel size plus the number of subchannels allocated to the sidelink communication and not overlapping with the guard band multiplied by the number of PRBs associated with the pre-configured subchannel size.

[0213] Clause 25: The method according to any one of Clauses 1 to 24, wherein the sidelink communication includes one or both of PSCCH communication and PSSCH communication.

[0214] Clause 26: The method according to any one of Clauses 1 to 25, the method further comprising: using the initial allocation of the PRB and the one or more additional PRBs to perform the sidelink communication.

[0215] Clause 27: A method for wireless communication by a UE, the method comprising: receiving sidelink communication using at least one of: all partial subchannel PRBs in a subchannel that partially overlaps with a guard band in a resource pool; or all boundary PRBs in a subchannel that is in the resource pool but not allocated to the resource pool; determining a transport block size for the sidelink communication; and decoding the sidelink communication based on the transport block size.

[0216] Clause 28: The method according to Clause 27 further comprises: receiving an indication of the reference subchannel size to a user equipment intended to receive the sidelink communication; and determining, at least in part, a transport block size for the sidelink communication based on the reference subchannel size for the initial allocation based on the PRB and the one or more additional PRBs.

[0217] Clause 29: One or more means comprising: a memory including executable instructions; and one or more processors configured to execute the executable instructions and cause the one or more means to: perform the method according to any one of Clauses 1 to 28.

[0218] Clause 30: One or more apparatuses, said apparatus including components for performing the method according to any one of Clauses 1 to 28.

[0219] Clause 31: One or more non-transitory computer-readable media, the non-transitory computer-readable media comprising: executable instructions that, when executed by one or more processors of one or more devices, cause the one or more devices to perform the method according to any one of Clauses 1 to 28.

[0220] Clause 32: One or more computer program products embodied on one or more computer-readable storage media, said computer-readable storage media comprising: code for performing the methods described pursuant to any one of Clauses 1-28.

[0221] Additional Notes

[0222] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, the function and arrangement of the elements discussed may be changed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in the various examples. For example, the described methods may be performed in a different order than described, and various actions may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Additionally, the scope of this disclosure is intended to cover such apparatuses or methods practiced using other structures, functionalities, or structures and functionalities that complement or replace the various aspects of this disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims.

[0223] The various exemplary logic blocks, modules, and circuits described in this disclosure can be implemented or executed using a general-purpose processor, digital signal processor (DSP), ASIC, field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic device, discrete hardware component, or any combination thereof designed to perform the functions described herein. While the general-purpose processor may be a microprocessor, in alternative embodiments, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, a system-on-a-chip (SoC), or any other such configuration.

[0224] As used in this article, the phrase “at least one of” in a list of items refers to any combination of those items (including single members). For example, “at least one of a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0225] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" can include calculation, operation, processing, deduction, investigation, lookup (e.g., searching in a table, database, or other data structure), assertion, and so on. Additionally, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), and so on. Furthermore, "determine" can include parsing, selecting, picking, building, and so on.

[0226] As used herein, unless otherwise stated, “coupled to” and “coupled with” generally encompass both direct and indirect coupling (e.g., including intermediate aspects of coupling). For example, stating that a processor is coupled to memory allows for direct coupling or coupling via an intermediate aspect such as a bus.

[0227] The methods disclosed herein include one or more actions for implementing the methods. These actions may be interchanged without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of a particular action may be modified without departing from the scope of the claims. Furthermore, the various operations of the methods described above may be performed by any suitable component capable of performing the corresponding function. This component may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors.

[0228] The following claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language of the claims. Within the claims, unless specifically stated otherwise, reference to the singular form of an element is not intended to mean "one and only one," but rather "one or more." Unless otherwise specifically stated, the term "some" refers to one or more. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are now or hereafter known to those skilled in the art are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly stated in the claims.

Claims

1. A user equipment configured for wireless communication and comprising: The memory includes processor-executable instructions; and one or more processors, said one or more processors being configured to execute processor-executable instructions and equip the user: The initial allocation of physical resource blocks (PRBs) in one or more sub-channels that do not overlap with the guard band within the resource pool used for sidelink communication determines the occupied channel bandwidth (OCB) threshold that is not met for said sidelink communication. One or more additional PRBs are allocated from the resource pool to the sidelink communication in order to satisfy the OCB threshold. The one or more additional PRS mentioned above include at least one of the following: All partial subchannels (PRBs) in the subchannels that partially overlap with the guard band in the resource pool; or All boundary PRBs of sub-channels within the resource pool but not allocated to the resource pool.

2. The user equipment of claim 1, wherein, in order to allocate the one or more additional PRBs to the sidelink communication, the one or more processors are configured to execute processor-executable instructions and further cause the user equipment to: allocate any available boundary PRBs before allocating any available partial subchannel PRBs.

3. The user equipment of claim 2, wherein, in order to allocate the one or more additional PRBs to the sidelink communication, the one or more processors are configured to execute processor-executable instructions and further cause the user equipment to: allocate any available PRB with a higher subchannel index before allocating any available PRB with a lower subchannel index.

4. The user equipment of claim 1, wherein the one or more processors are further configured to execute processor-executable instructions and cause the user equipment to: associate a boundary PRB within the resource pool with a subchannel within the resource pool having the highest subchannel index.

5. The user equipment of claim 1, wherein the one or more processors are further configured to execute processor-executable instructions and cause the user equipment to: associate a boundary PRB within the resource pool with a new subchannel, the new subchannel comprising a smaller number of PRBs compared to the subchannel size of all other subchannels configured in the resource pool.

6. The user equipment of claim 1, wherein the one or more processors are further configured to execute processor-executable instructions and cause the user equipment to: determine, at least in part, a transport block size for the PRB-based initial allocation and the sidelink communication of the one or more additional PRBs based on a pre-configured nominal subchannel size.

7. The user equipment of claim 6, wherein the one or more processors are further configured to execute processor-executable instructions and cause the user equipment to: perform rate matching on the given subchannel based on all PRBs overlapping the guard band in the given subchannel assigned to the sidelink communication and overlapping the guard band.

8. The user equipment of claim 6, wherein the one or more processors are further configured to execute processor-executable instructions and cause the user equipment to: punch the sidelink communication in any PRB overlapping the guard band.

9. The user equipment of claim 1, wherein the one or more processors are further configured to execute processor-executable instructions and cause the user equipment to: determine, at least in part, the transport block size for the PRB-based initial allocation and the sidelink communication of the one or more additional PRBs based on the reference subchannel size.

10. The user equipment of claim 9, wherein the reference subchannel size is pre-configured for the resource pool.

11. The user equipment of claim 9, wherein the total number of PRBs for the transport blocks used for the sidelink communication is equal to the number of subchannels allocated to the sidelink communication multiplied by the number of PRBs associated with the reference subchannel size.

12. The user equipment of claim 9, wherein the one or more processors are further configured to execute processor-executable instructions and cause the user equipment to: allocate the partial subchannel PRBs to the one or more additional PRBs based on the number of partial subchannel PRBs being greater than a threshold.

13. The user equipment of claim 11, wherein the one or more processors are further configured to execute processor-executable instructions and cause the user equipment to: determine the reference subchannel size based on the minimum number of PRBs that do not overlap with the guard band in the subchannels allocated to the sidelink communication.

14. The user equipment of claim 11, wherein the one or more processors are further configured to execute processor-executable instructions and cause the user equipment to: determine the reference subchannel size based on a weighting function, the weighting function including a first weight associated with a subchannel allocated to the sidelink communication and not overlapping with the guard band and a second weight associated with a subchannel allocated to the sidelink communication and overlapping with the guard band.

15. The user equipment according to claim 14, wherein: The weighting function is , It is the first weight. It is the second weight. It is the number of sub-channels allocated to the sidelink communication that do not overlap with the guard band. It is the number of sub-channels allocated to the sidelink communication and overlapping with the guard band. It is the number of partial subchannel PRBs of the i-th subchannel that overlap with the guard band.

16. The user equipment of claim 15, wherein the one or more processors are further configured to execute processor-executable instructions and cause the user equipment to: round the output value of the weighting function to one of the nearest integer value lower than the output value or the nearest integer value higher than the output value before determining the reference subchannel size.

17. The user equipment according to claim 15, wherein and It is pre-configured.

18. The user equipment according to claim 15, wherein = = .

19. The user equipment of claim 9, wherein the one or more processors are further configured to execute processor-executable instructions and cause the user equipment to: Only for sub-channels allocated to the sidelink communication and overlapping with the guard band; and The reference subchannel size is determined based on one of the following: The minimum number of PRBs in the sub-channels that overlap with the guard band in the sub-channels allocated to the side link communication; The maximum number of PRBs in the sub-channels that overlap with the guard band among the sub-channels allocated to the sidelink communication; or The average number of PRBs in the sub-channels that overlap with the guard band in the sub-channels allocated to the side link communication.

20. The user equipment of claim 19, wherein the one or more processors are further configured to execute processor-executable instructions and cause the user equipment to: determine the transport block size based on the reference subchannel size of a subchannel allocated to the sidelink communication and overlapping with the guard band and the pre-configured subchannel size of a subchannel allocated to the sidelink communication and not overlapping with the guard band and associated with the resource pool.

21. The user equipment of claim 20, wherein the total number of PRBs for the transport blocks used for the sidelink communication is equal to the number of subchannels allocated to the sidelink communication and overlapping with the guard band multiplied by the number of PRBs associated with the reference subchannel size plus the number of subchannels allocated to the sidelink communication and not overlapping with the guard band multiplied by the number of PRBs associated with a pre-configured subchannel size.

22. The user equipment of claim 9, wherein the one or more processors are further configured to execute processor-executable instructions and cause the user equipment to: transmit an indication of the reference subchannel size to a user equipment intended to receive the sidelink communication.

23. The user equipment of claim 22, wherein the indication is only for subchannels allocated to the sidelink communication that overlap with the guard band, indicating whether a portion of the subchannel or the entire subchannel is used as the reference subchannel size.

24. The user equipment of claim 22, wherein the total number of PRBs for the transport blocks used for the sidelink communication is equal to the number of subchannels allocated to the sidelink communication and overlapping with the guard band multiplied by the number of PRBs associated with the reference subchannel size plus the number of subchannels allocated to the sidelink communication and not overlapping with the guard band multiplied by the number of PRBs associated with the pre-configured subchannel size.

25. The user equipment of claim 1, wherein the sidelink communication includes one or both of physical sidelink control channel (PSCCH) communication and physical sidelink shared channel (PSSCH) communication.

26. The user equipment of claim 1, wherein the one or more processors are further configured to execute processor-executable instructions and cause the user equipment to perform the sidelink communication using the initial allocation of the PRB and the one or more additional PRBs.

27. A user equipment configured for wireless communication and comprising: The memory includes processor-executable instructions; and a processor, the processor being configured to execute processor-executable instructions and equip the user: Use at least one of the following to receive sidelink communication: All partial subchannels (PRBs) in the subchannels that partially overlap with the guard band in the resource pool; or All boundary PRBs of sub-channels within the resource pool but not allocated to the resource pool; Determine the transport block size used for the sidelink communication; and The sidelink communication is decoded based on the transport block size.

28. The user equipment of claim 27, wherein the one or more processors are further configured to execute processor-executable instructions and cause the user equipment to: The indication of the reference subchannel size is received by user equipment intended to receive the sidelink communication; and The transport block size for the PRB-based initial allocation and the sidelink communication of the one or more additional PRBs is determined at least in part based on the reference subchannel size.

29. A method for wireless communication by a user equipment, the method comprising: The initial allocation of PRBs in one or more sub-channels that do not overlap with the guard band within the resource pool used for sidelink communication determines whether the occupied channel bandwidth (OCB) threshold for said sidelink communication is not met. as well as One or more additional PRBs are allocated from the resource pool to the sidelink communication in order to satisfy the OCB threshold. The one or more additional PRS mentioned above include at least one of the following: All partial subchannels (PRBs) in the subchannels that partially overlap with the guard band in the resource pool; or All boundary PRBs of sub-channels within the resource pool but not allocated to the resource pool.

30. A method for wireless communication by a user equipment, the method comprising: Use at least one of the following to receive sidelink communication: All partial subchannel physical resource blocks (PRBs) in the subchannels that partially overlap with the guard band in the resource pool; or All boundary PRBs of sub-channels within the resource pool but not allocated to the resource pool; Determine the transport block size used for the sidelink communication; and The sidelink communication is decoded based on the transport block size.

Images