Identification of reduced-capability user equipment for sidelink communications

Abstract

Example aspects include an apparatus and method for wireless communication by a reduced capability user equipment (RedCap UE) in a network, including transmitting, to a non-RedCap UE, an indication indicating that the RedCap UE is a RedCap UE device. The aspects also include performing sidelink communications with the non-RedCap UE in accordance with capabilities of the RedCap UE.

Description

Technical Field

[0001] The aspects described generally relate to wireless communication systems, and more specifically to the identification of user equipment (RedCap UE) that provides reduced capabilities for side link communication. Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0003] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the municipal, national, regional, and even global levels. An example of a telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Mobile Broadband Evolution (CMB) initiative released by the 3rd Generation Partnership Project (3GPP) to meet new requirements related to latency, reliability, security, scalability (e.g., the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. Various aspects of wireless communication can include direct communication between devices, such as in sidelink, vehicle-to-vehicle (V2V), vehicle-to-everything (V2X), and / or device-to-device (D2D) communications. Further improvements are needed in sidelink technologies, V2X technologies, V2V technologies, and / or D2D technologies. These improvements can also be applied to other multiple access technologies and telecommunications standards that employ these technologies. Summary of the Invention

[0004] The following is a brief overview of one or more aspects to provide a basic understanding of them. This overview is not a general description of all anticipated aspects, nor is it intended to identify key or important elements of all aspects, nor to depict the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0005] One example aspect includes a method for wireless communication by a first user equipment (UE), comprising sending an indication to a second UE of a UE type for sidelink communication. The method further includes performing sidelink communication with the second UE based on the indicated UE type.

[0006] Another example aspect includes an apparatus for wireless communication by a first user equipment (UE), comprising a memory and a processor communicatively coupled to the memory. The processor is configured to send an indication to a second UE of a UE type for sidelink communication. The processor is also configured to perform sidelink communication with the second UE based on the indicated UE type.

[0007] Another example aspect includes an apparatus for wireless communication by a first user equipment (UE), including a unit for transmitting an indication to a second UE of a UE type for sidelink communication. The apparatus also includes a unit for performing sidelink communication with the second UE according to the indicated UE type.

[0008] Another example includes a non-transitory computer-readable medium comprising stored instructions for wireless communication by a first user equipment (UE), the stored instructions being processor-executable to send an indication to a second UE of a UE type for sidelink communication. The instructions are also executable to perform sidelink communication with the second UE according to the indicated UE type.

[0009] To achieve the foregoing and related objectives, the one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and drawings illustrate specific illustrative features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of the aspects can be employed, and this description is intended to include all such aspects and their equivalents. Attached Figure Description

[0010] Figure 1 This is a diagram illustrating examples of wireless communication systems and access networks according to various aspects of this disclosure.

[0011] Figure 2A This is a diagram illustrating an example of the first frame of various aspects according to this disclosure.

[0012] Figure 2B This is a diagram illustrating an example of a downlink channel within a subframe according to various aspects of this disclosure.

[0013] Figure 2C This is a diagram illustrating an example of the second frame according to various aspects of this disclosure.

[0014] Figure 2D This is a diagram illustrating an example of an uplink channel within a subframe according to various aspects of this disclosure.

[0015] Figure 3 Example aspects of the side link time slot structure according to various aspects of this disclosure are shown.

[0016] Figure 4 This is a diagram illustrating examples of hardware components of a base station and user equipment (UE) in an access network according to various aspects of this disclosure.

[0017] Figure 5 This is a diagram illustrating other example aspects of the side link time slot structure according to various aspects of this disclosure.

[0018] Figure 6 This is a diagram illustrating examples of narrowband bandwidth resources and broadband bandwidth resources according to various aspects of this disclosure.

[0019] Figure 7 This is a diagram illustrating the first message flow between a RedCap UE and a non-RedCap UE according to various aspects of this disclosure.

[0020] Figure 8 This is a diagram illustrating examples of PSBCH content according to various aspects of this disclosure.

[0021] Figure 9 This is a diagram illustrating the second message flow between a RedCap UE and a non-RedCap UE according to various aspects of this disclosure.

[0022] Figure 10 This is a diagram illustrating a third message flow between a RedCap UE and a non-RedCap UE according to various aspects of this disclosure.

[0023] Figure 11 This is a diagram illustrating the fourth message flow between RedCap UE and non-RedCap UE according to various aspects of this disclosure.

[0024] Figure 12 This is a diagram illustrating an example set of resource blocks according to various aspects of this disclosure.

[0025] Figure 13 The mapping between RedCap UE type indication and sequence cyclic shift value is shown according to various aspects of this disclosure.

[0026] Figure 14This is a diagram illustrating the fifth message flow between RedCap UE and non-RedCap UE according to various aspects of this disclosure.

[0027] Figure 15 This is a diagram illustrating an example apparatus according to various aspects of this disclosure.

[0028] Figure 16 This is a flowchart of a method for wireless communication to be performed by a UE in accordance with various aspects of this disclosure.

[0029] Figure 17 This is a flowchart of the first additional or optional step of a wireless communication method to be performed by the UE in accordance with various aspects of this disclosure.

[0030] Figure 18 This is a flowchart of a second additional or optional step in a wireless communication method to be performed by a UE in accordance with various aspects of this disclosure.

[0031] Figure 19 This is a flowchart of a third additional or optional step in a wireless communication method to be performed by the UE in accordance with various aspects of this disclosure. Detailed Implementation

[0032] The specific embodiments described below with reference to the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configuration in which the concepts described herein can be practiced. The specific embodiments include detailed descriptions to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0033] User equipment (UE) in a wireless communication system may include capability-reduced (RedCap) UE devices. In some aspects, RedCap UEs may have reduced capabilities, reduced complexity, and / or reduced costs compared to conventional or non-RedCap UEs. For example, the capability reduction of RedCap UE devices compared to non-RedCap UE devices may include, but is not limited to, smaller bandwidth capabilities, fewer receiving antennas, relaxed processing requirements, and less frequent monitoring of the control channel. RedCap UE devices can be used in devices such as wearable devices (e.g., smartwatches, rings, etc.), industrial wireless sensors, and / or surveillance cameras. That is, RedCap UE devices can be used in applications that require extended battery life and / or infrequent transmission of small amounts of data.

[0034] In wireless communication systems, non-RedCap UEs can perform sidelink communication, vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication, and / or device-to-device (D2D) communication with RedCap UEs. RedCap UEs may have lower capabilities (e.g., bandwidth capabilities) compared to non-RedCap UEs. If or when a non-RedCap UE communicates with a RedCap UE based on parameters associated with the non-RedCap UE, the RedCap UE may not be able to properly send and / or receive information. Therefore, non-RedCap UEs may need to identify the RedCap UE type in order to properly configure sidelink transmission resources. However, legacy communication systems do not support: RedCap UEs indicating their RedCap UE type to non-RedCap UEs. In such legacy systems, non-RedCap UEs may be unable to perform sidelink communication with RedCap UEs.

[0035] The aspects presented in this paper provide multiple ways for RedCap UEs to indicate their RedCap UE type to non-RedCap UEs. Such indications allow non-RedCap UEs to configure appropriate transmission parameters to perform sidelink communication. Furthermore, the aspects presented in this paper can reduce the complexity and latency of wireless communication systems.

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

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

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

[0039] Figure 1 This is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also known as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)).

[0040] In a particular aspect, UE 104 may include a sidelink identification component 198 configured to send an indication of the type of UE for sidelink communication and to perform sidelink communication based on the indicated UE type.

[0041] Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femtocells, picocells, and microcells. Base station 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). Base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a second backhaul link 184. In addition to other functions, base station 102 may perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and device tracking, RAN information management (RIM), paging, location, and delivery of warning messages. Base station 102 may communicate with each other directly or indirectly (e.g., via EPC 160 or core network 190) via a third backhaul link 134 (e.g., X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless.

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

[0043] A specific UE 104 can communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 can use DL / UL WWAN spectrum. The D2D communication link 158 can use one or more sideline channels, such as the Physical Sideline Broadcast Channel (PSBCH), Physical Sideline Discovery Channel (PSDCH), Physical Sideline Shared Channel (PSSCH), and Physical Sideline Control Channel (PSCCH). D2D communication can be conducted through various wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

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

[0045] Both small cell 102' and large cell (e.g., macro base station) base station 102 can include evolved Node B (eNB), g Node B (gNB) or other types of base stations. Some base stations, such as gNB 180, can operate in one or more frequency bands within the electromagnetic spectrum.

[0046] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating frequency bands have been identified as the frequency range names FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). The frequencies between FR1 and FR2 are generally referred to as the mid-band frequencies. Although a portion of FR1 is greater than 6GHz, FR1 is often referred to (interchangeably) as the “Sub-6 GHz” band in various documents and articles. Similar naming issues sometimes arise regarding FR2, although it differs from the Ultra High Frequency (EHF) band (30GHz–300GHz) defined by the International Telecommunication Union (ITU) as the “millimeter wave” (mmW) band, FR2 is often referred to (interchangeably) as the “millimeter wave” band in documents and articles.

[0047] Considering the foregoing, unless otherwise specified, it should be understood that the term "sub-6GHz" as used herein can broadly refer to frequencies that are less than 6GHz, within FR1, or may include intermediate frequency band frequencies. Furthermore, unless otherwise specified, it should be understood that the term "millimeter wave" as used herein can broadly refer to frequencies that may include intermediate frequency band frequencies, within FR2, or within the EHF band. Communication using the mmW radio band has extremely high path loss and short range. The mmW base station 180 can utilize beamforming 182 with the UE 104 to compensate for path loss and short range.

[0048] Base station 180 can transmit beamformed signals to UE 104 in one or more transmission directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182”. UE 104 may also transmit beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beamforming to determine the optimal receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions of base station 180 may be the same or different. The transmit and receive directions of UE 104 may be the same or different. Although beamformed signals are shown between UE 104 and base stations 102 / 180, aspects of beamforming can be similarly applied by UE 104 or RSU 107 to communicate with another UE 104 or RSU 107, such as sidelink-based communication, V2X communication, V2V communication, or D2D communication.

[0049] EPC 160 may include 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 Packet Data Network (PDN) Gateway 172. MME 162 can communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All 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. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. The BM-SC 170 can provide functions for MBMS user service provisioning and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and schedule MBMS transmissions. The MBMS gateway 168 can allocate MBMS services to base station 102 belonging to a Multicast-Broadcast Single Frequency Network (MBSFN) area belonging to a broadcast-specific service, and can be responsible for session management (start / stop) and collecting billing information related to eMBMS.

[0050] Core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UDP) 195. AMF 192 can communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between UE 104 and core network 190. Typically, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted via UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP service 197. IP service 197 may include the Internet, intranet, IP Multimedia Subsystem (IMS), Packet Switched (PS) Streaming (PSS) service, and / or other IP services.

[0051] Base stations may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), Transmitter Receiver Point (TRP), or any other suitable term. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / brakes, displays, or any other similar functional devices. Some UE 104 devices may be referred to as IoT devices (e.g., parking timers, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client, or any other suitable term.

[0052] Some wireless communication networks may include vehicle-based communication devices that can communicate from vehicle to vehicle (V2V), from vehicle to infrastructure (V2I) (e.g., from a vehicle-based communication device to a road infrastructure node such as a roadside unit (RSU), from vehicle to network (V2N) (e.g., from a vehicle-based communication device to one or more network nodes such as a base station), and / or combinations thereof, and / or communicate with other devices, which can be collectively referred to as vehicle-to-everything (V2X) communication. See again Figure 1In certain aspects, UE 104 (e.g., a vehicle user equipment (VUE) or other UE making the transmission) can be configured to send messages directly to another UE 104. Communication can be based on sidelink / V2V / V2X / V2I or other D2D communication, such as Proximity Services (ProSe). Sidelink, V2V, V2X, V2I, and / or D2D communication can also be sent and received by other transmitting and receiving devices such as Roadside Unit (RSU) 107. Various aspects of the communication can be based on PC5 or sidelink communication, for example, as combined with... Figure 3 The example described in [the document / reference] is as follows.

[0053] While the following description provides examples for sidelink / V2X / D2D communication related to 5G NR, the concepts described herein are applicable to other similar fields such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0054] Reference Figures 2A to 2D These diagrams illustrate network elements (e.g., base station 102, UE 104) that can be used in wireless communication systems, as described above. Figure 1 Examples of different resources for communication between access networks 100. Resources can be time-based, frequency-based, or a combination of both.

[0055] Figure 2A Figure 200 shows an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 shows an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 shows an example of a second subframe within a 5G NR frame structure. Figure 2D Figure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD), where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL, or it can be Time Division Duplex (TDD), where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL. Figure 2A , 2CIn the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (primarily DL), where D is DL, U is UL, and F is flexible for use between DL / UL, and subframe 3 is configured with slot format 1 (with all UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE configures the slot format via the received Slot Format Indicator (SFI) (dynamically via DL Control Information (DCI) or semi-statically / statically via Radio Resource Control (RRC) signaling). Note that the following description also applies to 5G NR frame structures that are TDD.

[0056] Other wireless communication technologies may have different frame structures and / or different channels. A frame (e.g., 10 milliseconds) can be divided into 10 subframes of equal size (e.g., 1 millisecond). Each subframe may include one or more time slots. Subframes may also include mini-time slots, which may contain 7, 4, or 2 symbols. Depending on the time slot configuration, each time slot may contain 7 or 14 symbols. For time slot configuration 0, each time slot may contain 14 symbols, and for time slot configuration 1, each time slot may contain 7 symbols. Symbols on the DL can be Cyclic Prefix (CP) OFDM (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the time slot configuration and digital scheme. For slot configuration 0, different digital schemes μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different digital schemes 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Correspondingly, for slot configuration 0 and digital scheme μ, there are 14 symbols / slot and 2... μ Each time slot / subframe. Subcarrier spacing and symbol length / duration are functions of the digital scheme. Subcarrier spacing can be equal to 2. μ *15kHz, where μ is the digital scheme from 0 to 4. Therefore, digital scheme μ = 0 has a subcarrier spacing of 15kHz, and digital scheme μ = 4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely proportional to the subcarrier spacing. Figure 2A-2DExamples are provided for slot configuration 0 with 14 symbols per slot and digital scheme μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, one or more different bandwidth portions (BWPs) of frequency division multiplexing can exist (see...). Figure 2B Each BWP may have a specific numerical scheme.

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

[0058] like Figure 2A As shown, some REs carry reference (pilot) signals (RS) for the UE. RSs may include demodulation RS (DM-RS) for channel estimation at the UE (indicated as R for a particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS). RSs may also include beam measurement RS (BRS), beam refinement RS (BRS), and phase tracking RS (PT-RS).

[0059] Figure 2BExamples of various DL channels within a subframe of a frame are shown. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE groups (REGs), each REG comprising 12 consecutive REs in the OFDM symbols of an RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during PDCCH monitoring occasions on a CORESET, where PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can reside at larger and / or lower frequencies across the channel bandwidth. The Primary Synchronization Signal (PSS) can be within symbol 2 of a specific subframe of the frame. UE 104 uses the PSS to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) can be within symbol 4 of a specific subframe of the frame. The UE uses the SSS to determine the physical layer cell identification group number and radio frame timing. 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 DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Block (SIB)), and paging messages.

[0060] like Figure 2C As shown, some REs carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DM-RS configurations are possible). The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first one or two symbols preceding the PUSCH. The PUCCH DM-RS can be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and the specific PUCCH format used. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the combs. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0061] Figure 2DExamples of various UL channels within a subframe of a frame are shown. The PUCCH can be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) ACK / NACK feedback. The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0062] Figure 3 Example figures 300 and 310 are shown, illustrating an example time slot structure that can be used for wireless communication between UE 104A and UE 104B, for example, for sidelink communication. The time slot structure can be within a 5G / NR frame structure. Although the following description may focus on 5G NR, the concepts described herein are applicable to other similar domains such as LTE, LTE-A, CDMA, GSM, and other wireless technologies. This is merely an example; other wireless communication technologies may have different frame structures and / or different channels. A frame (10 milliseconds) can be divided into 10 subframes (1 milliseconds) of equal size. Each subframe may include one or more time slots. Subframes may also include mini-time slots, which may include 7, 4, or 2 symbols. Depending on the time slot configuration, each time slot may include 7 or 14 symbols. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. Figure 300 illustrates a single-slot transmission, which may correspond to a transmission time interval (TTI) of 0.5 milliseconds. Figure 310 illustrates an example of two-slot aggregation, for example, the aggregation of two 0.5-millisecond TTIs. Figure 300 illustrates a single resource block (RB), while Figure 310 illustrates N RBs. In Figure 310, the 10 RBs used for control are merely an example. The number of RBs may vary.

[0063] A resource grid can be used to represent frame structure. Each time slot includes a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme. Figure 3 As shown, some REs may include control information, for example, along with the demodulation RS (DMRS). Figure 3 The illustration also shows that the symbols may include CSI-RS. Figure 3The symbols indicated for use in DMRS or CSI-RS include DMRSREs or CSI-RS REs. These symbols may also include REs that include data. For example, if the number of ports used for DMR or CSI-RS is 1, and comb 2 mode is used for DMR / CSI-RS, half of the REs may include RSs, and the other half may include data. CSI-RS resources can begin at any symbol in a time slot and can occupy 1, 2, or 4 symbols, depending on the number of ports configured. CSI-RS can be periodic, semi-persistent, or aperiodic (e.g., DCI-triggered). For time / frequency tracking, CSI-RS can be periodic or aperiodic. CSI-RS can be transmitted in bursts of two or four symbols, distributed across one or two time slots. Control information may include sidelink control information (SCI). As described herein, at least one symbol may be used for feedback. Symbols before and / or after feedback may be used for the turnaround period between receiving data and transmitting feedback. Although symbol 12 is shown in relation to data, it can be a gap symbol used to implement a turnaround period for feedback in symbol 13. Another symbol (e.g., at the end of a time slot) can be used as a gap. This gap allows the device to switch from operating as a transmitting device to preparing to operate as a receiving device (e.g., in a later time slot). As shown, data can be transmitted in the remaining RE. The data can include the data message described herein. The position of any of the SCI symbol, feedback symbol, and LBT symbol can differ. Figure 3 The example shown illustrates how multiple time slots can be aggregated together. Figure 3 An example aggregation of two time slots is also shown. The number of time slot aggregations can also be greater than two. When time slots are aggregated, the symbols used for feedback and / or the slot symbols can be different from those used for a single time slot. Although feedback is not shown for the aggregation example, symbols in multi-time slot aggregations can also be assigned for feedback, as shown in the single-time slot example.

[0064] Figure 4This is a block diagram 400 showing, for example, communication between a first wireless communication device 410 and a second wireless communication device 450 via a sidelink / V2V / V2X / D2D communication. Device 410 may include a transmitting device that communicates with a receiving device (e.g., device 450) via a sidelink / V2V / V2X / D2D communication. This communication may be based on, for example, a sidelink. Transmitting device 410 may include a non-RedCap UE, RSU, etc. Receiving device may include a RedCap UE, RSU, etc. Packets may be provided to a controller / processor 475 that can implement Layer 3 and Layer 2 functions. Layer 3 may include a Radio Resource Control (RRC) layer, and Layer 2 may include a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Media Access Control (MAC) layer.

[0065] Transmit (TX) processor 416 and receive (RX) processor 470 can implement Layer 1 functions associated with various signal processing functions. Layer 1, which may include a physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 416 can process the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM streams can be spatially precoded to produce multiple spatial streams. The channel estimate from channel estimator 474 can be used to determine coding and modulation schemes, as well as for spatial processing. The channel estimate can be derived based on reference signals transmitted by UE 450 and / or channel condition feedback. Each spatial stream can then be provided to different antennas 420 via separate transmitters 418TX. Each transmitter 418TX can modulate an RF carrier with the corresponding spatial stream for transmission.

[0066] At device 450, each receiver 454RX can receive signals via its respective antenna 452. Each receiver 454RX can recover information modulated onto the RF carrier and can provide that information to the receive (RX) processor 456. The TX processor 468 and RX processor 456 can implement Layer 1 functions associated with various signal processing functions. The RX processor 456 can perform spatial processing on the information to recover any spatial streams destined for device 450. If multiple spatial streams are destined for device 450, or when multiple spatial streams are destined for device 450, the multiple spatial streams can be combined by the RX processor 456 into a single OFDM symbol stream. The RX processor 456 can then use a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal can include a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier can be recovered and demodulated by determining the most probable signal constellation point transmitted by device 410. These soft decisions can be based on channel estimates calculated by the channel estimator 458. The soft decision can then be decoded and deinterleaved to recover the data and control signals initially transmitted by device 410 on the physical channel. The data and control signals can then be provided to a controller / processor 459 capable of implementing Layer 3 and Layer 2 functions.

[0067] Controller / processor 459 may be associated with memory 460, which stores program code and data. Memory 460 may be referred to as a computer-readable medium. Controller / processor 459 can provide demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels. Controller / processor 459 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0068] Similar to the functions described in conjunction with the transmissions performed by device 410, controller / processor 459 can provide RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with upper-layer PDU transmission, error correction via ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MACSDUs to TBs, demultiplexing of MAC SDUs from TBs, reporting of scheduling information, error correction via HARQ, priority processing, and logical channel priority allocation.

[0069] The channel estimate derived by channel estimator 458 from the reference signal transmitted by device 410 or feedback can be used by TX processor 468 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial stream generated by TX processor 468 can be provided to different antennas 452 via separate transmitters 454TX. Each transmitter 454TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0070] Transmission can be processed at device 410 in a manner similar to that described for the receiver function at device 450. Each receiver 418RX can receive signals via its corresponding antenna 420. Each receiver 418RX can recover information modulated onto the RF carrier and can provide that information to the RX processor 470.

[0071] Controller / processor 475 may be associated with memory 476, which stores program code and data. Memory 476 may be referred to as a computer-readable medium. Controller / processor 475 can provide demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels. Controller / processor 475 may also be responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0072] At UE 450, at least one of the TX processor 468, RX processor 456, and controller / processor 459 can be configured to perform operations related to... Figure 1 The side link identification component 198 is related to various aspects.

[0073] Wireless communication systems can be configured to share available system resources and provide various telecommunications services (e.g., telephone, video, data, messaging, broadcasting, etc.) based on multiple access technologies that support communication with multiple users (such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and TD-SCDMA systems). In many cases, common protocols that facilitate communication with wireless devices are adopted across various telecommunications standards. For example, communication methods associated with eMBB, mMTC, and URLLC can be incorporated into the 5G NR telecommunications standard, while others can be incorporated into the 4G LTE standard. Since mobile broadband technology is part of continuous evolution, further improvements to mobile broadband remain useful for the continued development of such technologies.

[0074] In some aspects, there may be use cases in wireless communication systems where peak capabilities of the UE are not required (e.g., eMBB, URLLC). Therefore, it may be desirable for the UE to be scalable and / or deployable in an efficient and / or cost-effective manner. For example, peak throughput, latency, and / or reliability requirements for the UE can be relaxed in exchange for efficiency (e.g., power consumption and system overhead) and / or cost reduction. Examples of such UEs (e.g., RedCap UEs, also known as New Radio (NR) - Lightweight UEs) can include wearable devices (e.g., smartwatches), industrial wireless sensor network (IWSN) devices, security devices (e.g., surveillance cameras), etc. When compared to non-RedCap UE devices, the reduced capabilities of RedCap UEs can include, but are not limited to, smaller bandwidth capabilities, fewer receive antennas, relaxed processing requirements, and less frequent monitoring of the control channel.

[0075] Wireless communication devices (e.g., UE 104A, UE 104B) in a wireless communication system can perform communication based on NR-side walkways (e.g., V2V, V2X, direct D2D links). NR-side walkway communication can support at least one of the following types of operations: broadcast operation, multicast operation, and unicast operation. Broadcast operation can include data transmission from a first device to all devices. Multicast operation can include data transmission from a first device to a group of multiple devices (e.g., a multicast group). Unicast operation can include data transmission from a first device to a second device. During a unicast operation, a communication link can be established between the first device and the second device. For example, the communication link can include an NR-side walkway communication link.

[0076] NR sidelink communication can utilize resources from transmit and / or receive resource pools allocated for sidelink communication. These resource pools may have already been allocated by network devices (e.g., gNBs). In some aspects, the minimum resource allocation unit may include a subchannel in the frequency domain and a timeslot in the time domain. A subchannel may include several consecutive RBs (e.g., 10, 15, 20, 25, 50, 75, 100 PRBs). The size of the subchannel can be configured by higher layers.

[0077] In some aspects, the PSCCH and PSSCH can be transmitted within the same side link time slot. For example, the PSCCH can be configured to span a predetermined number of PRBs (e.g., 10, 12, 15, 20, 25) and can be limited to a single subchannel. Alternatively or additionally, the PSSCH can be configured to span one or more subchannels based on the SCI information transmitted in the PSSCH. PSSCH transmission can include one or two layers of transmission and can support various modulation schemes, such as QPSK, 16-QAM, 64-QAM, and 256-QAM. In other aspects, the Physical Side Link Feedback Channel (PSFCH) can be further transmitted in the side link time slot. The PSFCH can include two OFDM symbols. For example, the first OFDM symbol of the PSFCH can be a repetition of the second OFDM symbol of the PSFCH. Such a scenario can facilitate automatic gain control (AGC) settings. Alternatively or additionally, gap symbols can be transmitted after the PSFCH symbols.

[0078] Sidelink communication can be configured with multiple transmit resource pools and / or multiple receive resource pools. Each resource pool can define a subset of available subframes and / or resource blocks for sidelink transmission or reception. Alternatively or additionally, each resource pool can define PSCCH configuration, PSSCH configuration, PSFCH configuration, subchannel quantity, subchannel size, starting resource block, sensing configuration, power control configuration, etc.

[0079] The sidelink resource pool can be configured statically or semi-statically (e.g., using Layer 3 messages). In some aspects, if or when the UE determines that it wants to use sidelink communication to send data, the UE can dynamically select one or more transmission resources from the transmission resource pool. For example, the UE can determine one or more transmission resources based at least on the transmission mode configuration. That is, in a first transmission mode, the UE can determine one or more transmission resources based on an indication received from a network device (e.g., gNB). Alternatively or additionally, in a second transmission mode, the UE can determine one or more transmission resources according to predetermined rules.

[0080] Reference Figure 5 Figures 500 and 510 show examples of different time slot structures that can be used for side link communication between network elements (e.g., UE 104A, UE 104B). Figure 5 The time slot structure described in [the document] is similar in many ways to the one referenced above. Figure 3 The described time slot structure may include additional features not mentioned above. Figures 500 and 510 show examples of various side link channels within a subframe of a frame.

[0081] For example, as shown in Figure 500, the first symbol in a time slot can be allocated for Automatic Gain Control (AGC). In some aspects, the first two symbols (not shown) in a time slot can be allocated for AGC. The PSCCH can carry control information such as SCI, and the associated PSCCH can carry side link data. The last symbol in a time slot can be used as a gap. This gap allows the device to switch from operating as a transmitting device to preparing to operate as a receiving device, for example, in a subsequent time slot.

[0082] Alternatively or additionally, the side link time slot structure may include a PSFCH, as shown in Figure 510. The PSFCH may carry HARQ feedback information (e.g., ACK / NACK feedback).

[0083] In some respects, RedCap UEs may have reduced capabilities compared to non-RedCap UEs. For example, a RedCap UE may operate on a narrow bandwidth (e.g., 20 MHz or optional 40 MHz for FR1, and 100 MHz for FR2). In another example, a RedCap UE may have a reduced number of receive branches or antennas (e.g., one or two). In yet another example, a RedCap UE may have a reduced number of MIMO spatial layers (e.g., one or two) and / or a reduced maximum modulation order (e.g., 64-QAM). Therefore, a non-RedCap UE attempting to communicate with a RedCap UE using sidelink communication may require indication of its UE type (e.g., RedCap UE, non-RedCap UE) to configure appropriate PSSCH transmission parameters. For example, the scheduled bandwidth for PSSCH transmission should not exceed the maximum UE bandwidth capability associated with the indicated UE type (e.g., 20 MHz or optional 40 MHz for RedCap UE, and 100 MHz for FR2). In another example, the number of MIMO spatial layers used for PSSCH transmission should not exceed the maximum number of MIMO spatial layers supported by the indicated UE type (e.g., one or two for a RedCap UE). In yet another example, the assigned PSSCH resources should be within the frequency range associated with the indicated UE type. That is, the assigned PSSCH resources should be within the narrow bandwidth resources used for RedCap UEs.

[0084] For example, such as Figure 6As shown, RedCap UE 104 can operate within the narrow resource bandwidth 610. That is, RedCap UE 104A can assign and / or utilize transmission resources 612-614 (e.g., PSSCH) falling within the narrow resource bandwidth 610. Alternatively or additionally, nonRedCap UE 104B can operate within the wide resource bandwidth 620. That is, nonRedCap UE 104B can assign and / or utilize transmission resources 622-626 (e.g., PSSCH) falling within the wide resource bandwidth 620. Therefore, nonRedCap UE 104B may not be able to utilize transmission resources (e.g., 622 and 626) falling outside the narrow resource bandwidth 620 to perform sidelink communication with RedCap UE 104A. Instead, nonRedCap UE 104B may need to utilize transmission resources (e.g., 624) falling within the narrow resource bandwidth 620 to perform sidelink communication with RedCap UE 104A. Therefore, there is a need for RedCap UE 104A to indicate the RedCap UE type to non-RedCap UE 104B. Such an indication would allow non-RedCap UE 104B to configure appropriate transmission parameters to perform sidelink communication with RedCap UE 104A.

[0085] Figure 7 This is a diagram illustrating a first message flow between a RedCap UE and a non-RedCap UE, including an indication of the RedCap UE type. For example, schematic diagram 700 shows a message flow in which RedCap UE 104A indicates the RedCap UE type to non-RedCap UE 104B. In step 710, RedCap UE 104A may send an advance indication of the RedCap UE type during a sidelink SSB (SL-SSB) transmission. For example, RedCap UE 104A may send an SL-SSB that includes the indication of the RedCap UE type. The indication of the RedCap UE type may be sent via the PSBCH. In some aspects, one or more reserved bits of the PSBCH payload may be reinterpreted as an indication of the RedCap UE type, such as... Figure 8 As shown. For example, one or more reserved bits can indicate that RedCap UE 104A is a RedCap UE.

[0086] Reference Figure 8The PSBCH payload may include a Direct Frame Number (DFN) field. For example, the DFN field may include 10 bits of the PSBCH payload. The PSBCH payload may also include an indication of TDD configuration. This indication may indicate system-wide information, such as TDD-UL-DL configuration, potential SL slots, etc. For example, this indication may include 12 bits of the PSBCH payload. The PSBCH payload may also include a slot index field. The slot index field may include 7 bits of the PSBCH payload. The PSBCH payload may also include an in-coverage indicator field. For example, the in-coverage indicator field may include 1 bit of the PSBCH payload. The PSBCH payload may also include one or more reserved bits. For example, the PSBCH payload may include 2 reserved bits. In some aspects, one or more reserved bits of the PSBCH payload may be reinterpreted as an indication of RedCap UE type. The PSBCH payload may also include a Cyclic Redundancy Check (CRC) field. The CRC field may include 24 bits of the PSBCH payload.

[0087] Further reference Figure 7 Alternatively or additionally, RedCap UE 104A and non-RedCap UE 104B may perform PC5 (e.g., sidelink) RRC communication. PC5-RRC communication may be performed to establish a PC5 (e.g., sidelink) link between RedCap UE 104A and non-RedCap UE 104B. PC5-RRC communication may include capability negotiation between RedCap UE 104A and non-RedCap UE 104B, at least in part based on prior indication of the RedCap UE type. That is, as part of capability negotiation, RedCap UE 104A may provide non-RedCap UE 104B with additional RedCap UE type and / or capability information. In some aspects, RedCap UE 104A and non-RedCap UE 104B may reuse conventional PC5-RRC signaling to exchange capability information. In other respects, RedCap UE 104A and non-RedCap UE 104B can add new fields to the legacy PC5-RRC signaling to indicate RedCap UE type and / or capability information.

[0088] In step 720, non-RedCap UE 104B can request capability information from RedCap UE 104A. That is, non-RedCap UE 104B can send a UECapabilityEnquirySidelink message requesting capability information to RedCap UE 104A. In step 730, RedCap UE 104A can respond to the request by reporting the capability information requested by non-RedCap UE 104B. For example, RedCap UE 104A can send a UECapabilityInformationSidelink message to non-RedCap UE 104B to provide the requested capability information. The reported capability information may include maximum bandwidth information, the number of receive branches or antennas, the number of MIMO spatial layers, the maximum modulation order, etc. RedCap UE 104A and non-RedCap UE 104B can establish a PC5 (e.g., sidelink) link based on the reported capability information.

[0089] Figure 9 This is a diagram illustrating a second message flow between a RedCap UE and a non-RedCap UE, including an indication of the RedCap UE type. For example, schematic diagram 900 shows a message flow during the transmission of a discovery signal, instructing a non-RedCap UE 104B to indicate the RedCap UE type. The indication of the RedCap UE type may include an indication that RedCap UE 104A is a RedCap UE. Alternatively or additionally, the indication of the RedCap UE may include capability information of RedCap UE 104A.

[0090] In step 910, RedCap UE 104A may send a presence announcement. For example, as part of the discovery process, RedCap UE 104A may send a presence announcement to its neighboring devices. The presence announcement may include an indication of RedCap UE type information. In some aspects, the presence announcement may include a Global Synchronization Signal (GSS) and / or a Reference Broadcast Synchronization (RBS) signal. In other aspects, the presence announcement may be sent on the PSCCH or the PSSCH.

[0091] In step 920, the non-RedCap UE 104B can monitor discovery signals sent by neighboring devices. That is, the non-RedCap UE 104B can monitor the PSCCH and / or PSSCH in response to presence announcements from RedCap UE 104A. In step 930, the non-RedCap UE 104B can send a connection request to RedCap UE 104A based at least on the indication of RedCap UE type included in the presence announcement. For example, the non-RedCap UE 104B can determine whether to establish a sidelink communication link with RedCap UE 104A based at least on the presence announcement and the included indication of RedCap UE type. In step 940, RedCap UE 104A and non-RedCap UE 104B can use the sidelink communication link to perform sidelink communication. For example, RedCap UE 104A and non-RedCap UE 104B can exchange data and / or control signal transmissions on one or more side link channels (e.g., PSCCH, PSSCH).

[0092] Figure 10 This is a diagram illustrating a third message flow between a RedCap UE and a non-RedCap UE, including an indication of the RedCap UE type. For example, schematic diagram 1000 shows a message flow during data communication transmission where RedCap UE 104A indicates the RedCap UE type to non-RedCap UE 104B.

[0093] In step 1010, the non-RedCap UE 104B can send data communications to neighboring devices (e.g., RedCap UE 104A, non-RedCap UE 104C). In some aspects, the data communications can be sent on a physical side link channel (e.g., PSSCH). For example, the data communications can include multicast transmissions. That is, the non-RedCap UE 104B can send data communications without using a communication link (e.g., a side link) configured between the non-RedCap UE 104B and the recipient of the data communications (e.g., RedCap UE 104A, non-RedCap UE 104C). Therefore, the transmission parameters of the data communications may be incompatible with RedCap UE 104A, and RedCap UE 104A may not be able to receive and / or decode the data communications. For example, the frequency range of the resources (e.g., PSSCH) used by RedCap UE 104A for data communications may be outside the bandwidth of RedCap UE 104A.

[0094] As shown in step 1020, at least based on data communication transmission, RedCap UE 104A can send an indication of RedCap UE type to non-RedCap UE 104B. The indication of RedCap UE type may include an indication that RedCap UE 104A is a RedCap UE. Alternatively or additionally, the RedCap UE indication may include capability information of RedCap UE 104A. For example, capability information may indicate the Layer 1 capabilities of RedCap UE 104A, including but not limited to maximum bandwidth, maximum modulation order, and the number of MIMO spatial layers. In some aspects, RedCap UE 104A may use a conventional physical channel (e.g., PSFCH) to send the indication of RedCap UE type. In other aspects, such as... Figure 12 As shown, RedCap UE 104A can use a new physical channel to send indications of the RedCap UE type. The new physical channel (e.g., Figure 12 The resource 1210) can have similar characteristics to a traditional PSFCH (e.g., Figure 12 The time slot structure of resource 1220. That is, the new physical channel may include two OFDM symbols. In some aspects, the first OFDM symbol of the new physical channel may be a repetition of the second OFDM symbol of the new physical channel. Alternatively or additionally, the new physical channel may also include gap symbols.

[0095] In some aspects, non-RedCap UE 104B can dynamically enable or disable the transmission of RedCap UE type indications. For example, non-RedCap UE 104B can send control information (e.g., SCI format 1, SCI format 2) for scheduling PSSCH transmissions, indicating whether RedCap UE type indications need to be sent. In other aspects, RedCap UE 104A can send RedCap UE type indications with HARQ ACK / NACK feedback information. If or when the transmission of RedCap UE type indications is enabled, in addition to HARQ ACK / NACK feedback information, RedCap UE 104A can also report RedCap UE 104A capability information.

[0096] Reference Figure 11Non-RedCap UE 104B can send data communications to neighboring devices (e.g., RedCap UE 104A, non-RedCap UE 104C). In step 1110, the data communication may indicate that RedCap UE type indication is enabled. Non-RedCap UE 104C and RedCap UE 104A can respond to the data communication with feedback information (e.g., HARQ-ACK) in steps 1120 and 1130, respectively. Based at least on the data communication transmission and the indication that the transmission of RedCap UE type indication is enabled, the transmission of feedback information from RedCap UE 104A in step 1130 may further include an indication that RedCap UE 104A is a RedCap UE. Alternatively or additionally, the RedCap UE indication may include capability information of RedCap UE 104A.

[0097] Further reference Figure 12 RedCap UE 104A can use resources other than those used for sending feedback information (e.g., resource 1220) (e.g., resource 1210) to send RedCap UE type indications. In some aspects, RedCap UE 104A can determine the resources used for sending RedCap UE type indications based on a mapping of attributes associated with the sidelink physical channel (i.e., PSSCH). For example, the mapping can be based on the starting subchannel and timeslot number of the PSSCH. Alternatively or additionally, the mapping can be based on the source ID and / or destination ID of the sidelink communication link.

[0098] Alternatively or additionally, RedCap UE 104A may use different sequence cyclic shift values ​​to transmit the RedCap UE type indication. In some aspects, the transmitted sequence cyclic shift value can provide an indication of the RedCap UE type. That is, the cyclic shift sequence selected by RedCap UE 104A can be used as an indication of the RedCap UE type. For example, RedCap UE 104A may determine the sequence cyclic shift value based at least on the mapping between the RedCap UE type indication and the sequence cyclic shift value. (See reference...) Figure 13This diagram illustrates examples of different mapping relationships that RedCap UEs can use to select sequence cyclic shift values, at least based on RedCap UE type indications. Each mapping relationship can associate one or more capabilities of a RedCap UE with one or more sequence cyclic shift values. In some aspects, the number of possible combinations of indicated RedCap UE capabilities can correspond to the amount of sequence cyclic shift values. For example, two different sequence cyclic shift values ​​can be used to indicate two possible MIMO layer configurations for a RedCap UE.

[0099] In some aspects, the first mapping relationship 1310 may associate the maximum number of MIMO spatial layers of the RedCap UE with one or more sequence cyclic shift values. For example, a first sequence cyclic shift value (e.g., 0) may be associated with a RedCap UE that includes a maximum of one (1) MIMO layers. That is, RedCap UE 104A may be selected as a sequence cyclic shift value of zero (0) to indicate to non-RedCap UE 104B that RedCap UE 104A includes a maximum of one (1) MIMO layers. Alternatively or additionally, a second sequence cyclic shift value (e.g., 6) may be associated with a RedCap UE that includes a maximum of two (2) MIMO spatial layers. That is, RedCap UE 104A may be selected as a sequence cyclic shift value of six (6) to indicate to non-RedCap UE 104B that RedCap UE 104A includes a maximum of two (2) MIMO spatial layers.

[0100] In other respects, the second mapping relationship 1320 can associate the maximum number of MIMO spatial layers of the RedCap UE and the maximum bandwidth of the RedCap UE with one or more sequence cyclic shift values. For example, a first sequence cyclic shift value (e.g., 0) can be associated with a RedCap UE that includes a maximum of one (1) MIMO layer and a maximum bandwidth of 20 MHz. That is, RedCap UE 104A can be selected as a sequence cyclic shift value of zero (0) to indicate to non-RedCap UE 104B that RedCap UE 104A includes a maximum of one (1) MIMO layer and a maximum bandwidth of 20 MHz. In another example, a second sequence cyclic shift value (e.g., 3) can be associated with a RedCap UE that includes a maximum of one (1) MIMO layer and a maximum bandwidth of 40 MHz. That is, RedCap UE 104A can be selected as a sequence cyclic shift value of three (3) to indicate to non-RedCap UE 104B that RedCap UE 104A includes a maximum of one (1) MIMO layer and a maximum bandwidth of 40 MHz. In yet another example, a third sequence cyclic shift value (e.g., 6) can be associated with a RedCap UE that includes a maximum of two (2) MIMO spatial layers and a maximum bandwidth of 20 MHz. That is, RedCap UE 104A can be selected as a sequence cyclic shift value of six (6) to indicate to non-RedCap UE 104B that RedCap UE 104A includes a maximum of two (2) MIMO spatial layers and a maximum bandwidth of 20 MHz. In yet another example, a fourth sequence cyclic shift value (e.g., 9) can be associated with a RedCap UE that includes a maximum of two (2) MIMO spatial layers and a maximum bandwidth of 40 MHz. That is, RedCap UE 104A can be selected as a sequence cyclic shift value of nine (9) to indicate to non-RedCap UE 104B that RedCap UE 104A includes a maximum of two (2) MIMO spatial layers and a maximum bandwidth of 40 MHz.

[0101] In other respects, the third mapping relation 1330 can associate the maximum number of MIMO spatial layers and HARQ feedback indication of a RedCap UE with one or more sequential cyclic shift values. For example, a first sequential cyclic shift value (e.g., 0) can be associated with a RedCap UE that includes a maximum of one (1) MIMO layer and a HARQ-ACK indication. That is, RedCap UE 104A can be selected as a sequential cyclic shift value of zero (0) to indicate to non-RedCap UE 104B that RedCap UE 104A includes a maximum of one (1) MIMO layer and a HARQ-ACK indication. In another example, a second sequential cyclic shift value (e.g., 6) can be associated with a RedCap UE that includes a maximum of one (1) MIMO layer and a HARQ-NACK indication. That is, RedCap UE 104A can be selected as a sequential cyclic shift value of six (6) to indicate to non-RedCap UE 104B that RedCap UE 104A includes a maximum of one (1) MIMO layer and a HARQ-NACK indication. In yet another example, a third sequence cyclic shift value (e.g., 3) can be associated with a RedCap UE that includes a maximum of two (2) MIMO spatial layers and a HARQ-ACK indication. That is, RedCap UE 104A can be selected as a three (3) sequence cyclic shift value to indicate to non-RedCap UE 104B that RedCap UE 104A includes a maximum of two (2) MIMO spatial layers and a HARQ-ACK indication. In yet another example, a fourth sequence cyclic shift value (e.g., 9) can be associated with a RedCap UE that includes a maximum of two (2) MIMO spatial layers and a HARQ-NACK indication. That is, RedCap UE 104A can be selected as a nine (9) sequence cyclic shift value to indicate to non-RedCap UE 104B that RedCap UE 104A includes a maximum of two (2) MIMO spatial layers and a HARQ-NACK indication.

[0102] Figure 14This is a diagram illustrating a fifth message flow between a RedCap UE and a non-RedCap UE, including an indication of the RedCap UE type. For example, schematic diagram 1400 shows a message flow during data communication transmission where RedCap UE 104A, via a network device (e.g., base station 180), indicates the RedCap UE type to a non-RedCap UE 104B. The indication of the RedCap UE type may include an indication that RedCap UE 104A is a RedCap UE. In some aspects, the RedCap UE indication may include capability information of RedCap UE 104A. Alternatively or additionally, the RedCap UE indication may include identification information of RedCap UE 104A and / or identification information of non-RedCap UE 104B.

[0103] In step 1410, the non-RedCap UE 104B can send data communications to neighboring devices (e.g., RedCap UE 104A, non-RedCap UE 104C). In some aspects, the data communications can be sent on a physical side link channel (e.g., PSSCH). For example, the data communications can include multicast transmissions. That is, the non-RedCap UE 104B can send data communications without using a communication link (e.g., a side link) configured between the non-RedCap UE 104B and the recipient of the data communications (e.g., RedCap UE 104A, non-RedCap UE 104C). Therefore, the transmission parameters of the data communications may be incompatible with RedCap UE 104A, and RedCap UE 104A may not be able to receive and / or decode the data communications. For example, the frequency range of the resources (e.g., PSSCH) used by RedCap UE 104A for data communications may be outside the bandwidth of RedCap UE 104A.

[0104] As shown in step 1420, at least based on data communication transmissions, RedCap UE 104A may request network device 180 (e.g., gNB) to forward one or more physical layer capabilities of RedCap UE 104A to non-RedCap UE 104B. That is, RedCap UE 104 may send an indication of RedCap UE type to network device 180 (e.g., gNB). For example, in response to a failure to decode a data communication transmission, RedCap UE 104A may send an indication of RedCap UE type. The indication of RedCap UE type may include an indication that RedCap UE 104A is a RedCap UE. In some aspects, the indication of RedCap UE may include capability information of RedCap UE 104A. For example, capability information may indicate the Layer 1 capabilities of RedCap UE 104, including but not limited to maximum bandwidth, maximum modulation order, and the number of MIMO spatial layers. Alternatively or additionally, the indication for a RedCap UE may include identification information for RedCap UE 104A and / or identification information for non-RedCap UE 104B. For example, the identification information may include at least one of a MAC layer identifier, an RLC layer identifier, a PDCP layer identifier, a NAS layer identifier, an IP layer identifier, and an application layer identifier. In another example, the identification information may also include a mapping between identification information and a Cell Radio Network Temporary Identifier (C-RNTI).

[0105] In step 1430, network device 180 may send a RedCap UE type indication from RedCap UE 104A to non-RedCap UE 104B. In some aspects, network device 180 may send identification information of RedCap UE 104A. Non-RedCap UE 104B may reconfigure transmission parameters for subsequent data communication transmissions based at least on the RedCap UE type indication received from network device 180. For example, non-RedCap UE 104B may use the reconfigured transmission parameters to send another data communication to a neighboring device (e.g., RedCap UE 104A, non-RedCap UE 104C).

[0106] Figure 15 This is a block diagram of an example device 1500 for wireless communication. Device 1500 may be a RedCap UE (e.g., Figure 1 UE 104 Figure 4 Equipment 450 Figure 6-7The RedCap UE (104A) of 9-11, 14, or the RedCap UE may include device 1500. In some aspects, device 1500 includes a receiving component 1502 configured to receive sidelink communication from another device (e.g., device 1508), a communication manager 1504 configured to perform sidelink communication, and a transmitting component 1506 configured to send sidelink communication to device 1508, and the receiving component 1502, communication manager 1504, and transmitting component 1506 can communicate with each other (e.g., via one or more buses or electrical connections). As shown, device 1500 can use the receiving component 1502 and the transmitting component 1506 to communicate with another device 1508 (such as a non-RedCap UE, a base station, or another wireless communication device).

[0107] In some respects, device 1500 can be configured to perform the functions described herein. Figure 5-14 One or more operations described herein. Alternatively or additionally, the device 1500 may be configured to perform one or more processes described herein, such as... Figure 16-19 Method 1600. In some aspects, apparatus 1500 may include the above-described combination. Figure 1 and 4 One or more components of the UE described.

[0108] Receiver 1502 may receive communications from device 1508, such as reference signals, control information, data communications, or combinations thereof. Receiver 1502 may provide the received communications to one or more other components of device 1500, such as communication manager 1504. In some aspects, receiver 1502 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding), and may provide the processed signal to one or more other components. In some aspects, receiver 1502 may include the above-described combinations... Figure 1 and 4 The described UE includes one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0109] Transmitting component 1506 can send communications, such as reference signals, control information, data communications, or combinations thereof, to device 1508. In some aspects, communication manager 1504 can generate communications and send the generated communications to transmitting component 1506 for transmission to device 1508. In some aspects, transmitting component 1506 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on ​​the generated communications and send the processed signal to device 1508. In other aspects, transmitting component 1506 can include the above-described combinations. Figure 1 and 4 The described UE includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 1506 may be located in a transceiver or transceiver assembly with the receive component 1502.

[0110] Communication manager 1504 can send an indication to device 1508 of a UE type for sidelink communication, and can perform sidelink communication with device 1508 based on the indicated UE type. For example, communication manager 1504 can send an SSB including an indication of a UE type for sidelink communication. In another example, communication manager 1504 can send UE capability information indicating at least one reduced capability of device 1500 in response to a UE capability request. In yet another example, communication manager 1504 can send a discovery message including an indication of a UE type for sidelink communication. Alternatively or additionally, communication manager 1504 can send an indication of a UE type for sidelink communication via PSFCH. In some aspects, communication manager 1504 can include the above-mentioned combinations Figure 1 and 4 The described UE's controller / processor, memory, or a combination thereof.

[0111] In some aspects, the communication manager 1504 may include a set of components, such as a sending component 1510, an execution component 1512, a receiving component 1514, or a combination thereof. Alternatively, this set of components may be separate from and distinct from the communication manager 1504. In some aspects, one or more components of this set of components may include those combined as described above. Figure 1 and 4 The described UE's controller / processor, memory, or a combination thereof, or a combination thereof. Figure 1 and 4The described UE is implemented within a controller / processor, memory, or a combination thereof. Alternatively or additionally, one or more components of this group of components may be implemented at least partially as software stored in memory. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0112] The transmitting component 1510 may transmit to the device 1508 an indication of the UE type used for sidelink communication. The indication of the UE type may include an indication of whether the device 1508 is a RedCap UE. In some aspects, the indication of the UE type may include capability information of the device 1508. For example, capability information may indicate the Layer 1 capabilities of the device 1508, including but not limited to maximum bandwidth, maximum modulation order, and the number of MIMO spatial layers. Alternatively or additionally, the indication of the UE type may include identification information of the device 1508.

[0113] Execution component 1512 may perform sidelink communication with device 1508 according to the indicated UE type. For example, as part of the sidelink communication, execution component 1512 may send data and / or control information to device 1508 via sidelink physical channels (e.g., PSCCH, PSSCH, PSFCH). Alternatively or additionally, as part of the sidelink communication, execution component 1512 may receive data and / or control information from device 1508 via sidelink physical channels (e.g., PSCCH, PSSCH, PSFCH). In some aspects, execution component 1512 may request device 1508 to forward one or more physical layer capabilities of device 1500 to another device.

[0114] The receiving component 1514 can receive requests from the device 1508. For example, the receiving component 1514 can receive a UE capability request from the device 1508. In another example, the receiving component 1514 can receive a connection request from the device 1508 in response to a discovery message.

[0115] Reference Figures 16-19 In operation, the first UE 450 can execute the wireless communication method 1600. Method 1600 can be executed by the first UE 450 (which may include memory 460 and may be a component of the entire first UE 450 or UE 104, such as a side-link identification component 198, TX processor 468, RX processor 456, or controller / processor 459). Method 1600 can also be executed by the UE-side-link identification component 198 communicating with the second UE 410.

[0116] exist Figure 16At block 1602, method 1600 includes sending an indication to the second UE indicating the UE type for lateral link communication. For example, in one aspect, the first UE 450, the lateral link identification component 198, and / or the sending component 1510 may be configured to, or may include, units for sending an indication to the second UE 410 indicating the UE type for lateral link communication.

[0117] For example, the transmission at block 1602 may include transmitting a sidelink SSB (SL-SSB) that includes an indication of the UE type used for sidelink communication. In some aspects, the SL-SSB may be transmitted on the PSBCH. In other aspects, one or more reserved bits of the PSBCH payload may be reinterpreted as an indication of the UE type used for sidelink communication.

[0118] In some optional or additional aspects, the transmission at block 1602 may include sending a discovery message (e.g., a presence notice) to a neighboring device of the first UE 450 (e.g., the second UE 410, device 1508) as part of the discovery process. The discovery message may include an indication of the UE type used for lateral link communication. Additionally or alternatively, the discovery message may include GSS and / or RBS signals. In other aspects, the discovery message may be transmitted on the PSCCH or on the PSSCH.

[0119] In some optional or additional aspects, the indication of the UE type used for side link communication may designate the first UE 450 as a RedCap UE device.

[0120] Furthermore, for example, the transmission at block 1602 can be performed to provide the second UE 410 with an indication of the UE type used for sidelink communication. Such an indication allows the second UE 410 to configure appropriate transmission parameters to perform sidelink communication with the first UE 450. Therefore, the aspects proposed herein can reduce the complexity and latency of wireless communication systems.

[0121] In block 1604, method 1600 may include performing sidelink communication with a second UE based on the indicated UE type. For example, in one aspect, the first UE 450, sidelink identification component 198, and / or execution component 1512 may be configured to, or may include, units for performing sidelink communication with the second UE 410 based on the indicated UE type.

[0122] For example, the execution at block 1604 may include establishing a sidelink (e.g., PC5, V2V, V2X) between the first UE 450 and the second UE 410 according to the indicated UE type. The execution at block 1604 may include the first UE 450 and the second UE 410 exchanging data and / or control signal transmissions on one or more sidelink channels (e.g., PSCCH, PSSCH).

[0123] In some optional or additional aspects, the execution at box 1604 may include receiving a connection request from the second UE 410 in response to a discovery message.

[0124] Furthermore, for example, the execution at block 1604 can be performed to establish a sidelink communication channel between the first UE 450 and the second UE 410 without the need for a base station. Therefore, the aspects proposed herein can reduce the complexity and power consumption of wireless communication systems.

[0125] Reference Figure 17 In an optional or additional aspect, in block 1702, method 1600 may further include receiving a UE capability request from a second UE. For example, in one aspect, the first UE 450, the sidelink identification component 198, and / or the receiving component 1514 may be configured to, or may include, elements for receiving a UE capability request from the second UE 410.

[0126] For example, receiving information at box 1702 may include a request from the second UE 410 to the first UE 450 for additional RedCap UE type and / or capability information as part of capability negotiation for establishing a sidelink communication link. In some aspects, the first UE 450 and the second UE 410 may reuse conventional PC5-RRC signaling to exchange capability information (e.g., UECapabilityEnquirySidelink). In other aspects, the first UE 450 and the second UE 410 may add new fields to the conventional PC5-RRC signaling to indicate RedCap UE type and / or capability information.

[0127] Furthermore, for example, the reception at block 1702 can be performed to negotiate the capabilities between the second UE 410 and the first UE 450, at least based on additional capability information of the first UE 450. Such negotiation allows the second UE 410 to configure appropriate transmission parameters to perform sidelink communication with the first UE 450. Therefore, the aspects proposed herein can reduce the complexity and latency of wireless communication systems.

[0128] In this additional or optional aspect, in block 1704, the transmission in block 1602 may include transmitting UE capability information indicating at least one reduced capability of the first UE to the second UE in response to a UE capability request. For example, in one aspect, the first UE 450, the sidelink identification component 198, and / or the transmission component 1510 may be configured to, or may include, units for transmitting UE capability information indicating at least one reduced capability of the first UE 450 to the second UE 410 in response to a UE capability request.

[0129] For example, the transmission at box 1704 may include reporting UE capability information requested by the second UE 410. For example, the first UE 450 may send a UECapabilityInformationSidelink message to the second UE 410 providing the requested capability information. The reported capability information may include bandwidth information, the number of receive branches or antennas, the number of MIMO spatial layers, the maximum modulation order, etc.

[0130] In addition, for example, the transmission at box 1704 can be performed to negotiate the capabilities between the second UE 410 and the first UE 450 based at least on additional capability information of the first UE 450.

[0131] Reference Figure 18 In another optional or additional aspect, in block 1802, method 1600 may further include receiving data communication from the second UE via PSSCH. For example, in one aspect, the first UE 450, the sidelink identification component 198, and / or the receiving component 1514 may be configured to, or may include, units for receiving data communication from the second UE 410 via PSSCH.

[0132] For example, receiving at block 1802 may include receiving data communication that the second UE 410 has sent to a neighboring device (e.g., the first UE 450). For example, the data communication may include multicast transmission. That is, the second UE 410 may send data communication without using a communication link (e.g., a side link) configured between the second UE 410 and the recipient of the data communication (e.g., the first UE 450).

[0133] In addition, for example, the receiving function at block 1802 can be performed to receive data communication sent by the second UE 410.

[0134] In this additional or alternative aspect, in block 1804, the transmission in block 1602 may include transmitting an indication via PSFCH of the UE type for sidelink communication. For example, in one aspect, the first UE 450, the sidelink identification component 198, and / or the transmission component 1510 may be configured to, or may include, elements for transmitting an indication via PSFCH of the UE type for sidelink communication.

[0135] For example, the transmission at block 1804 may include an indication from the first UE 450 to the second UE 410 of the UE type used for sidelink communication. This indication may include information about whether the first UE 450 is a RedCap UE. Alternatively or additionally, the indication of the UE type used for sidelink communication may include capability information of the first UE 450. For example, the capability information may indicate the Layer 1 capabilities of the first UE 450, including but not limited to maximum bandwidth, maximum modulation order, and the number of MIMO spatial layers.

[0136] In another example, the transmission at box 1804 may include determining from the PSFCH resources an indication of the UE type for sidelink communication to be transmitted via the PSFCH. The PSFCH resources may be determined based on at least one of the starting subchannel of the PSSCH, the slot index of the PSSRCH, the source identifier of the sidelink communication link, the destination identifier of the sidelink communication link, and combinations thereof.

[0137] In another example, the transmission at box 1804 may include transmitting HARQ feedback information (e.g., HARQ-ACK, HARQ-NACK) for data communication via the PSFCH. In some aspects, the PSFCH resources used for transmitting HARQ feedback information may be configured separately from the PSFCH resources used to indicate the UE type for sidelink communication.

[0138] In another example, the transmission at box 1804 may include accessing the mapping between multiple cyclic shift sequences associated with the PSFCH and one or more physical layer capabilities of the first UE 450. The one or more physical layer capabilities of the first UE 450 may include at least one of a maximum modulation order, the amount of MIMO spatial layers, and combinations thereof.

[0139] Furthermore, for example, the transmission at block 1804 can be performed to allow the second UE 410 to configure appropriate transmission parameters to perform sidelink communication with the first UE 450. Therefore, the aspects proposed herein can reduce the complexity and latency of wireless communication systems.

[0140] Reference Figure 19In another optional or additional aspect, in block 1902, method 1600 may further include receiving first data communication from a second UE via PSSCH. For example, in one aspect, the first UE 450, the sidelink identification component 198, and / or the receiving component 1514 may be configured to, or may include, elements for receiving the first data communication from the second UE 410 via PSSCH.

[0141] For example, receiving at block 1902 may include receiving data communication that the second UE 410 has sent to a neighboring device (e.g., the first UE 450). For example, the data communication may include multicast transmission. That is, the second UE 410 may send data communication without using a communication link (e.g., a side link) configured between the second UE 410 and the recipient of the data communication (e.g., the first UE 450).

[0142] In addition, for example, the receiving function at block 1902 can be performed to receive data communication sent by the second UE 410.

[0143] In another or alternative aspect, in block 1904, the transmission in block 1602 may include: in response to a failure to decode the first data communication, sending a request to the network device for forwarding one or more physical layer capabilities of the first UE to the second UE, wherein the request includes a first identifier of the first UE and a second identifier of the second UE. For example, in one aspect, the first UE 450, the sidelink identification component 198, and / or the transmission component 1510 may be configured to, or may include, a unit for sending a request to the network device 180 in response to a failure to decode the first data communication for forwarding one or more physical layer capabilities of the first UE 450 to the second UE 410, wherein the request includes a first identifier of the first UE 450 and a second identifier of the second UE 410.

[0144] For example, the transmission at block 1904 may include sending an indication to network device 180 of a UE type for sidelink communication. This indication may include an indication that the first UE 450 is a RedCap UE. In some aspects, the indication of the UE type for sidelink communication may include capability information of the first UE 450. For example, the capability information may indicate the Layer 1 capabilities of the first UE 450, including but not limited to maximum bandwidth, maximum modulation order, and the number of MIMO spatial layers. Alternatively or additionally, the indication of the UE type for sidelink communication may include identification information of the first UE 450 and / or identification information of the second UE 410. For example, the identification information may include at least one of a MAC layer identifier, an RLC layer identifier, a PDCP layer identifier, a NAS layer identifier, an IP layer identifier, and an application layer identifier. In another example, the identification information may also include a mapping between identification information and C-RNTI.

[0145] In another example, the transmission at box 1904 could cause network device 180 to send an indication to second UE 410 of the UE type for side link communication from first UE 450.

[0146] Furthermore, for example, the transmission at block 1904 can be performed to provide the second UE 410 with an indication of the UE type for sidelink communication. Such an indication allows the second UE 410 to configure appropriate transmission parameters to perform sidelink communication with the first UE 450. Therefore, the aspects proposed herein can reduce the complexity and latency of wireless communication systems.

[0147] In another or alternative aspect, in block 1906, method 1600 may further include receiving second data communication configured according to one or more physical layer capabilities of the first UE from the second UE. For example, in one aspect, the first UE 450, the sidelink identification component 198, and / or the receiving component 1514 may be configured to, or may include, units for receiving second data communication configured according to one or more physical layer capabilities of the first UE 450 from the second UE 410.

[0148] For example, receiving at block 1906 may include reconfiguring transmission parameters for subsequent sidelink communication with the first UE 450 by the second UE 410, at least based on an indication of the UE type indicating the sidelink communication for the first UE 450.

[0149] In addition, for example, the receiving function at block 1906 can be performed to receive a second data communication sent by the second UE 410.

[0150] Implementation examples are described in the following numbered clauses:

[0151] 1. A method for wireless communication by a first user equipment (UE), comprising:

[0152] Send an indication to the second UE indicating the UE type used for sidelink communication; and

[0153] Perform side link communication with the second UE according to the indicated UE type.

[0154] 2. The method described according to Clause 1, wherein:

[0155] The first UE is a capability-reduced UE (RedCap UE) device;

[0156] The second UE is a non-RedCap UE device; and

[0157] The indication of the UE type includes indicating the first UE as the RedCap UE device.

[0158] 3. The method according to Clause 1 or Clause 2, wherein sending the instruction includes:

[0159] A synchronization signal block (SSB) is sent to the second UE, the synchronization signal block including an indication of the UE type used for the side link communication.

[0160] 4. The method according to any one of clauses 1-3 further includes:

[0161] Receive UE capability request from the second UE; and

[0162] Sending the indication includes: in response to the UE capability request, sending UE capability information to the second UE indicating at least one reduced capability of the first UE.

[0163] 5. The method according to any one of clauses 1-4, wherein:

[0164] Sending the indication includes sending a discovery message to the second UE, the discovery message including the indication of the UE type for the sidelink communication; and

[0165] The method also includes receiving a connection request from the second UE in response to the discovery message.

[0166] 6. The method according to any one of clauses 1-5 further includes:

[0167] Receive data communication from the second UE via the Physical Side Link Shared Channel (PSSCH); and

[0168] Sending the indication includes sending the indication for the UE type used for the side link communication via the Physical Side Link Feedback Channel (PSFCH).

[0169] 7. The method according to Clause 6, wherein sending the instruction via the PSFCH comprises:

[0170] The resources for transmitting the indication of the UE type for the side link communication via the PSFCH are determined from the PSFCH resources based on at least one of the following:

[0171] The starting sub-channel of the PSSCH;

[0172] The time slot index of the PSSCH;

[0173] Source identifier of the side link communication link;

[0174] The destination identifier of the sidelink communication link; and

[0175] Its combination.

[0176] 8. The method described pursuant to Clause 6 or Clause 7 further includes:

[0177] The PSFCH sends a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback for the data communication, wherein the first PSFCH resource for sending the HARQ-ACK feedback is configured separately from the second PSFCH resource for indicating the UE type for the sidelink communication.

[0178] 9. The method according to any one of clauses 6-8 further includes:

[0179] Receive from the second UE sidelink control information (SCI) enabling the indication of the UE type for the sidelink communication, the SCI scheduling the data communication; and

[0180] Sending the instruction includes sending one or more physical layer capabilities of the first UE via the PSSCH.

[0181] 10. The method according to any one of clauses 6-8, wherein sending the instruction comprises:

[0182] Access the mapping relationship between multiple cyclic shift sequences associated with the PSFCH and one or more physical layer capabilities of the first UE.

[0183] 11. The method according to Clause 10, wherein the one or more physical layer capabilities of the first UE include at least one of the following:

[0184] Maximum bandwidth information;

[0185] Maximum modulation order;

[0186] The amount of multiple-input multiple-output (MIMO) spatial layer; and

[0187] Its combination.

[0188] 12. The method according to any one of clauses 1 to 11 further includes:

[0189] The first data communication is received from the second UE via the physical side link shared channel (PSSCH);

[0190] Sending the instruction includes: in response to a failure to decode the first data communication, sending a request to the network device for forwarding one or more physical layer capabilities of the first UE to the second UE, the request including a first identifier of the first UE and a second identifier of the second UE; and

[0191] Receive second data communication from the second UE, configured according to the one or more physical layer capabilities of the first UE.

[0192] 13. The method according to Clause 12, wherein the first identifier and the second identifier include at least one of a Media Access Control (MAC) layer identifier, a Radio Link Control (RLC) layer identifier, a Packet Data Convergence Control (PDCP) layer identifier, a Non-Access Stratum (NAS) layer identifier, an Internet Protocol (IP) layer identifier, an application layer identifier, and a mapping between the first identifier and the second identifier and a Cell Radio Network Temporary Identifier (C-RNTI).

[0193] 14. An apparatus for wireless communication by a first user equipment (UE), comprising:

[0194] Memory; and

[0195] A processor, which is communicatively coupled to the memory and configured to:

[0196] Send an indication to the second UE indicating the UE type used for sidelink communication; and

[0197] Perform side link communication with the second UE according to the indicated UE type.

[0198] 15. The apparatus according to Clause 14, wherein:

[0199] The first UE is a capability-reduced UE (RedCap UE) device;

[0200] The second UE is a non-RedCap UE device; and

[0201] The indication of the UE type includes indicating the first UE as the RedCap UE device.

[0202] 16. The apparatus according to Clause 14 or Clause 15, wherein sending the instruction comprises:

[0203] A synchronization signal block (SSB) is sent to the second UE, the synchronization signal block including an indication of the UE type used for the side link communication.

[0204] 17. The apparatus according to any one of clauses 14-16, wherein the processor is further configured to:

[0205] Receive UE capability request from the second UE; and

[0206] Sending the indication includes: in response to the UE capability request, sending UE capability information to the second UE indicating at least one reduced capability of the first UE.

[0207] 18. The apparatus according to any one of clauses 14-17, wherein:

[0208] Sending the indication includes sending a discovery message to the second UE, the discovery message including the indication of the UE type for the sidelink communication; and

[0209] The processor is also configured to receive a connection request from the second UE in response to the discovery message.

[0210] 19. The apparatus according to any one of clauses 14-19, wherein the processor is further configured to:

[0211] Receive data communication from the second UE via the Physical Side Link Shared Channel (PSSCH); and

[0212] Sending the indication includes sending the indication for the UE type used for the side link communication via the Physical Side Link Feedback Channel (PSFCH).

[0213] 20. The apparatus according to Clause 19, wherein sending the instruction via the PSFCH comprises:

[0214] The resources for transmitting the indication of the UE type for the side link communication via the PSFCH are determined from the PSFCH resources based on at least one of the following:

[0215] The starting sub-channel of the PSSCH;

[0216] The time slot index of the PSSCH;

[0217] Source identifier of the side link communication link;

[0218] The destination identifier of the sidelink communication link; and

[0219] Its combination.

[0220] 21. The apparatus according to Clause 19 or Clause 20, wherein the processor is further configured to:

[0221] The PSFCH sends a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback for the data communication, wherein the first PSFCH resource for sending the HARQ-ACK feedback is configured separately from the second PSFCH resource for indicating the UE type for the sidelink communication.

[0222] 22. The apparatus according to any one of clauses 19-21, wherein the processor is further configured to:

[0223] Receive from the second UE sidelink control information (SCI) enabling the indication of the UE type for the sidelink communication, the SCI scheduling the data communication; and

[0224] Sending the instruction includes sending one or more physical layer capabilities of the first UE via the PSSCH.

[0225] 23. The apparatus according to any one of clauses 19-22, wherein sending the instruction comprises:

[0226] Access the mapping relationship between multiple cyclic shift sequences associated with the PSFCH and one or more physical layer capabilities of the first UE.

[0227] 24. The apparatus according to clause 23, wherein the one or more physical layer capabilities of the first UE include at least one of the following:

[0228] Maximum bandwidth information;

[0229] Maximum modulation order;

[0230] The amount of multiple-input multiple-output (MIMO) spatial layer; and

[0231] Its combination.

[0232] 25. The apparatus according to any one of clauses 14-24, wherein the processor is further configured to:

[0233] The first data communication is received from the second UE via the physical side link shared channel (PSSCH);

[0234] Sending the instruction includes: in response to a failure to decode the first data communication, sending a request to the network device for forwarding one or more physical layer capabilities of the first UE to the second UE, the request including a first identifier of the first UE and a second identifier of the second UE; and

[0235] Receive second data communication from the second UE, configured according to the one or more physical layer capabilities of the first UE.

[0236] 26. The apparatus according to Clause 25, wherein the first identifier and the second identifier include at least one of a Media Access Control (MAC) layer identifier, a Radio Link Control (RLC) layer identifier, a Packet Data Convergence Control (PDCP) layer identifier, a Non-Access Stratum (NAS) layer identifier, an Internet Protocol (IP) layer identifier, an application layer identifier, and a mapping between the first identifier and the second identifier and a Cell Radio Network Temporary Identifier (C-RNTI).

[0237] 27. An apparatus for wireless communication by a first user equipment (UE), comprising:

[0238] A unit for sending an indication to the second UE of the UE type used for sidelink communication; and

[0239] A unit for performing side link communication with the second UE according to the indicated UE type.

[0240] 28. The apparatus according to Clause 27, wherein:

[0241] The first UE is a capability-reduced UE (RedCap UE) device;

[0242] The second UE is a non-RedCap UE device; and

[0243] The indication of the UE type includes indicating the first UE as the RedCap UE device.

[0244] 29. The apparatus according to clause 27 or clause 28, wherein the unit for transmitting the instruction comprises:

[0245] A unit for sending a synchronization signal block (SSB) to the second UE, the synchronization signal block including an indication of the UE type for the side link communication.

[0246] 30. The apparatus according to any one of clauses 27-29 further comprises:

[0247] A unit for receiving a UE capability request from the second UE; and

[0248] The unit for sending the indication includes: a unit that, in response to the UE capability request, sends UE capability information indicating at least one reduced capability of the first UE to the second UE.

[0249] 31. The apparatus according to any one of clauses 27-30, wherein:

[0250] The method for sending the indication includes a unit for sending a discovery message to the second UE, the discovery message including the indication of the UE type for the sidelink communication; and

[0251] The device also includes a unit that receives a connection request from the second UE in response to the discovery message.

[0252] 32. The apparatus according to any one of clauses 27-31 further comprises:

[0253] A unit for receiving data communication from the second UE via the Physical Side Link Shared Channel (PSSCH); and

[0254] The unit for sending the indication includes a unit for sending the indication for the UE type used for the side link communication via the Physical Side Link Feedback Channel (PSFCH).

[0255] 33. The apparatus according to clause 32, wherein the unit for transmitting the instruction via the PSFCH comprises:

[0256] A unit for determining from PSFCH resources, based on at least one of the following, the resources for transmitting via the PSFCH the indication of the UE type for the side link communication:

[0257] The starting sub-channel of the PSSCH;

[0258] The time slot index of the PSSCH;

[0259] Source identifier of the side link communication link;

[0260] The destination identifier of the sidelink communication link; and

[0261] Its combination.

[0262] 34. The apparatus according to clause 32 or clause 33 further includes:

[0263] A unit for sending a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback for the data communication via the PSFCH, wherein a first PSFCH resource for sending the HARQ-ACK feedback is configured separately from a second PSFCH resource for indicating the UE type for the sidelink communication.

[0264] 35. The apparatus according to any one of clauses 32-34 further comprises:

[0265] A unit for receiving from the second UE sidelink control information (SCI) that enables indication of the UE type for the sidelink communication, the SCI scheduling the data communication; and

[0266] The unit for sending the indication includes a unit for sending one or more physical layer capabilities of the first UE via the PSSCH.

[0267] 36. The apparatus according to any one of clauses 32-35, wherein the unit for transmitting the instruction comprises:

[0268] A unit for accessing the mapping relationship between multiple cyclic shift sequences associated with the PSFCH and one or more physical layer capabilities of the first UE.

[0269] 37. The apparatus according to clause 36, wherein the one or more physical layer capabilities of the first UE include at least one of the following:

[0270] Maximum bandwidth information;

[0271] Maximum modulation order;

[0272] The amount of multiple-input multiple-output (MIMO) spatial layer; and

[0273] Its combination.

[0274] 38. The apparatus according to any one of clauses 27-37 further comprises:

[0275] A unit for receiving first data communication from the second UE via the physical side link shared channel (PSSCH);

[0276] The unit for sending the indication includes: a unit for sending a request to a network device, in response to a failure to decode the first data communication, for forwarding one or more physical layer capabilities of the first UE to the second UE, the request including a first identifier of the first UE and a second identifier of the second UE; and

[0277] A unit for receiving second data communication configured according to one or more physical layer capabilities of the first UE from the second UE.

[0278] 39. The apparatus according to Clause 39, wherein the first identifier and the second identifier include at least one of a Media Access Control (MAC) layer identifier, a Radio Link Control (RLC) layer identifier, a Packet Data Convergence Control (PDCP) layer identifier, a Non-Access Stratum (NAS) layer identifier, an Internet Protocol (IP) layer identifier, an application layer identifier, and a mapping between the first identifier and the second identifier and a Cell Radio Network Temporary Identifier (C-RNTI).

[0279] 40. A non-transitory computer-readable medium comprising stored instructions executable by a processor for wireless communication by a first user equipment (UE) for the following operations:

[0280] Send an indication to the second UE indicating the UE type used for sidelink communication; and

[0281] Perform side link communication with the second UE according to the indicated UE type.

[0282] 41. The non-transitory computer-readable medium as described in Clause 40, wherein:

[0283] The first UE is a capability-reduced UE (RedCap UE) device;

[0284] The second UE is a non-RedCap UE device; and

[0285] The indication of the UE type includes indicating the first UE as the RedCap UE device.

[0286] 42. A non-transitory computer-readable medium pursuant to Clause 40 or Clause 41, wherein the instructions for transmitting the indication include further instructions for:

[0287] A synchronization signal block (SSB) is sent to the second UE, the synchronization signal block including an indication of the UE type used for the side link communication.

[0288] 43. The non-transitory computer-readable medium according to any one of clauses 40-42 further includes instructions for operating as follows:

[0289] Receive UE capability request from the second UE; and

[0290] The instruction for sending the indication includes: a further instruction for sending UE capability information indicating at least one reduced capability of the first UE to the second UE in response to the UE capability request.

[0291] 44. A non-transitory computer-readable medium according to any one of clauses 40-43, wherein:

[0292] The instruction for sending the indication includes further instructions for sending a discovery message to the second UE, the discovery message including the indication of the UE type for the sidelink communication; and

[0293] The non-transitory computer-readable medium also includes instructions for receiving a connection request from the second UE in response to the discovery message.

[0294] 45. The non-transitory computer-readable medium according to any one of clauses 40-44 further includes instructions for operating as follows:

[0295] Instructions for receiving data communication from the second UE via the Physical Side Link Shared Channel (PSSCH); and

[0296] The instructions for sending the indication include further instructions for sending the indication via the Physical Side Link Feedback Channel (PSFCH) indicating the type of UE used for the side link communication.

[0297] 46. ​​The non-transitory computer-readable medium according to clause 45, wherein the instructions for transmitting the indication via the PSFCH include:

[0298] Further instructions for determining from the PSFCH resources, based on at least one of the following, the resources for transmitting the indication of the UE type for the side link communication via the PSFCH:

[0299] The starting sub-channel of the PSSCH;

[0300] The time slot index of the PSSCH;

[0301] Source identifier of the side link communication link;

[0302] The destination identifier of the sidelink communication link; and

[0303] Its combination.

[0304] 47. The non-transitory computer-readable medium pursuant to Clause 45 or Clause 46 further includes instructions for operating as follows:

[0305] The PSFCH sends a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback for the data communication, wherein the first PSFCH resource for sending the HARQ-ACK feedback is configured separately from the second PSFCH resource for indicating the UE type for the sidelink communication.

[0306] 48. The non-transitory computer-readable medium according to any one of clauses 45-47 further includes instructions for operating as follows:

[0307] Receive from the second UE sidelink control information (SCI) enabling the indication of the UE type for the sidelink communication, the SCI scheduling the data communication; and

[0308] The instructions for sending the indication include further instructions for sending one or more physical layer capabilities of the first UE via the PSSCH.

[0309] 49. A non-transitory computer-readable medium according to any one of clauses 45-48, wherein the instructions for transmitting the indication include further instructions for:

[0310] Access the mapping relationship between multiple cyclic shift sequences associated with the PSFCH and one or more physical layer capabilities of the first UE.

[0311] 50. A non-transitory computer-readable medium as described in Clause 49, wherein the one or more physical layer capabilities of the first UE include at least one of the following:

[0312] Maximum bandwidth information;

[0313] Maximum modulation order;

[0314] The amount of multiple-input multiple-output (MIMO) spatial layer; and

[0315] Its combination.

[0316] 51. The non-transitory computer-readable medium according to any one of clauses 40-50 further includes instructions for operating as follows:

[0317] The first data communication is received from the second UE via the physical side link shared channel (PSSCH);

[0318] The instruction for sending the indication includes: a further instruction to the network device, in response to a failure to decode the first data communication, to request the forwarding of one or more physical layer capabilities of the first UE to the second UE, the request including a first identifier of the first UE and a second identifier of the second UE; and

[0319] Receive second data communication from the second UE, configured according to the one or more physical layer capabilities of the first UE.

[0320] 52. The non-transitory computer-readable medium as described in section 51, wherein the first identifier and the second identifier include at least one of a Media Access Control (MAC) layer identifier, a Radio Link Control (RLC) layer identifier, a Packet Data Convergence Control (PDCP) layer identifier, a Non-Access Stratum (NAS) layer identifier, an Internet Protocol (IP) layer identifier, an application layer identifier, and a mapping between the first identifier and the second identifier and a Cell Radio Network Temporary Identifier (C-RNTI).

[0321] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowchart is illustrative of an exemplary manner. Based on design preferences, it should be understood that the specific order or hierarchy of the boxes in the process / flowchart can be rearranged. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of the various boxes in an exemplary order and are not intended to limit one to the specific order or hierarchy presented.

[0322] While illustrative aspects and / or embodiments have been discussed above, it should be noted that various changes and modifications may be made herein without departing from the scope of the aspects and / or embodiments as defined in the appended claims. Furthermore, although elements of the described aspects and / or embodiments may be described or claimed in the singular form, the plural form may be considered unless expressly limited by the singular form. Moreover, all or part of any aspect and / or embodiment may be used in conjunction with all or part of any other aspect and / or embodiment unless otherwise stated.

[0323] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be consistent with the full scope of the language claims, wherein elements referenced in the singular are not intended to mean “one and only one” (unless specifically stated otherwise), but rather “one or more.” Terms such as “if,” “when,” and “at the time of” should be interpreted as “under the condition of”, rather than implying a direct temporal relationship or reaction. That is, these phrases (e.g., “when”) do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply mean that if a condition is met, then the action will occur, but there is no specific or immediate time limit for the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous to other aspects. Unless specifically stated otherwise, the term “some” means one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure are known to or will subsequently be known to those skilled in the art, are expressly incorporated herein by reference, and are intended to be covered by the claims. Moreover, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. The terms “module,” “mechanism,” “element,” and “device” may not replace the word “unit.” Therefore, no claim can be made that an element should be interpreted as a functional module unless the element is explicitly described using the phrase “unit for…”.

Claims

1. A method for wireless communication by a first user equipment (UE), comprising: The first data communication is received from the second UE via the physical side crosslink shared channel (PSSCH); Sending an indication to the second UE of the UE type for sidelink communication, wherein sending the indication includes: in response to a failure to decode the first data communication, sending a request to the network device for forwarding one or more physical layer capabilities of the first UE to the second UE, the request including a first identifier of the first UE and a second identifier of the second UE; Perform side-link communication with the second UE according to the indicated UE type; and Receive second data communication from the second UE, configured according to the one or more physical layer capabilities of the first UE.

2. The method according to claim 1, wherein: The first UE is a capability-reduced UE (RedCap UE) device; The second UE is a non-RedCap UE device; and The indication of the UE type includes indicating the first UE as the RedCap UE device.

3. The method according to claim 1, wherein, Sending the instruction also includes: A synchronization signal block (SSB) is sent to the second UE, the synchronization signal block (SSB) including the indication of the UE type for the side link communication.

4. The method according to claim 1, further comprising: Receive UE capability request from the second UE; as well as Sending the indication includes: in response to the UE capability request, sending UE capability information to the second UE indicating at least one reduced capability of the first UE.

5. The method according to claim 1, wherein: Sending the indication further includes sending a discovery message to the second UE, the discovery message including the indication of the UE type for the sidelink communication; and The method further includes receiving a connection request from the second UE in response to the discovery message.

6. The method according to claim 1, further comprising: Data communication is received from the second UE via the Physical Side Link Shared Channel (PSSCH); as well as Sending the indication further includes sending the indication for the UE type used for the side link communication via the Physical Side Link Feedback Channel (PSFCH).

7. The method according to claim 6, wherein, Sending the instruction via the PSFCH includes: The resources for transmitting the indication of the UE type for the side link communication via the PSFCH are determined from the PSFCH resources based on at least one of the following: The starting sub-channel of the PSSCH; The time slot index of the PSSCH; Source identifier of the side link communication link; The destination identifier of the sidelink communication link; and Its combination.

8. The method according to claim 6, further comprising: The PSFCH sends a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback for the data communication, wherein the first PSFCH resource for sending the HARQ-ACK feedback is configured separately from the second PSFCH resource for indicating the UE type for the sidelink communication.

9. The method according to claim 6, further comprising: Receive from the second UE sidelink control information (SCI) that enables the UE type to be indicated for the sidelink communication, the SCI scheduling the data communication; as well as Sending the instruction also includes sending one or more physical layer capabilities of the first UE via the PSSCH.

10. The method according to claim 6, wherein, Sending the instruction also includes: Access the mapping relationship between multiple cyclic shift sequences associated with the PSFCH and one or more physical layer capabilities of the first UE.

11. The method according to claim 10, wherein, The one or more physical layer capabilities of the first UE include at least one of the following: Maximum bandwidth information; Maximum modulation order; The amount of multiple-input multiple-output (MIMO) spatial layer; and Its combination.

12. The method according to claim 1, wherein, The first identifier and the second identifier include at least one of the following: a Media Access Control (MAC) layer identifier, a Radio Link Control (RLC) layer identifier, a Packet Data Convergence Control (PDCP) layer identifier, a Non-Access Stratum (NAS) layer identifier, an Internet Protocol (IP) layer identifier, an application layer identifier, and a mapping between the first identifier and the second identifier and a Cell Radio Network Temporary Identifier (C-RNTI).

13. An apparatus for wireless communication by a first user equipment (UE), comprising: Memory; as well as A processor, which is communicatively coupled to the memory and configured to: The first data communication is received from the second UE via the physical side crosslink shared channel (PSSCH); Sending an indication to the second UE of the UE type for sidelink communication, wherein sending the indication includes: in response to a failure to decode the first data communication, sending a request to the network device for forwarding one or more physical layer capabilities of the first UE to the second UE, the request including a first identifier of the first UE and a second identifier of the second UE; Perform side-link communication with the second UE according to the indicated UE type; and Receive second data communication from the second UE, configured according to the one or more physical layer capabilities of the first UE.

14. The apparatus according to claim 13, wherein: The first UE is a capability-reduced UE (RedCap UE) device; The second UE is a non-RedCap UE device; and The indication of the UE type includes indicating the first UE as the RedCap UE device.

15. The apparatus according to claim 13, wherein, Sending the instruction also includes: A synchronization signal block (SSB) is sent to the second UE, the synchronization signal block (SSB) including the indication of the UE type for the side link communication.

16. The apparatus according to claim 13, wherein, The processor is also configured to: Receive UE capability request from the second UE; as well as Sending the indication further includes: in response to the UE capability request, sending UE capability information to the second UE indicating at least one reduced capability of the first UE.

17. The apparatus according to claim 13, wherein: Sending the indication further includes sending a discovery message to the second UE, the discovery message including the indication of the UE type for the sidelink communication; and The processor is also configured to receive a connection request from the second UE in response to the discovery message.

18. The apparatus according to claim 13, wherein, The processor is also configured to: Receive data communication from the second UE via the Physical Side Link Shared Channel (PSSCH); and Sending the indication further includes sending the indication for the UE type used for the side link communication via the Physical Side Link Feedback Channel (PSFCH).

19. The apparatus according to claim 18, wherein, Sending the instruction via the PSFCH includes: The resources for transmitting the indication of the UE type for the side link communication via the PSFCH are determined from the PSFCH resources based on at least one of the following: The starting sub-channel of the PSSCH; The time slot index of the PSSCH; Source identifier of the side link communication link; The destination identifier of the sidelink communication link; and Its combination.

20. The apparatus according to claim 18, wherein, The processor is also configured to: The PSFCH sends a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback for the data communication, wherein the first PSFCH resource for sending the HARQ-ACK feedback is configured separately from the second PSFCH resource for indicating the UE type for the sidelink communication.

21. The apparatus according to claim 18, wherein, The processor is also configured to: Receive from the second UE sidelink control information (SCI) that enables the UE type to be indicated for the sidelink communication, the SCI scheduling the data communication; as well as Sending the instruction includes sending one or more physical layer capabilities of the first UE via the PSSCH.

22. The apparatus according to claim 18, wherein, Sending the instruction also includes: Access the mapping relationship between multiple cyclic shift sequences associated with the PSFCH and one or more physical layer capabilities of the first UE.

23. The apparatus according to claim 22, wherein, The one or more physical layer capabilities of the first UE include at least one of the following: Maximum bandwidth information; Maximum modulation order; The amount of multiple-input multiple-output (MIMO) spatial layer; and Its combination.

24. The apparatus according to claim 13, wherein, The first identifier and the second identifier include at least one of the following: a Media Access Control (MAC) layer identifier, a Radio Link Control (RLC) layer identifier, a Packet Data Convergence Control (PDCP) layer identifier, a Non-Access Stratum (NAS) layer identifier, an Internet Protocol (IP) layer identifier, an application layer identifier, and a mapping between the first identifier and the second identifier and a Cell Radio Network Temporary Identifier (C-RNTI).

25. An apparatus for wireless communication by a first user equipment (UE), comprising: A unit for receiving first data communication from a second UE via the physical side link shared channel (PSSCH); A unit for sending an indication to a second UE indicating the type of UE used for sidelink communication, wherein the unit for sending the indication includes: a unit for sending a request to a network device for forwarding one or more physical layer capabilities of the first UE to the second UE in response to a failure to decode the first data communication, the request including a first identifier of the first UE and a second identifier of the second UE; A unit for performing side-link communication with the second UE according to the indicated UE type; and A unit for receiving second data communication configured according to one or more physical layer capabilities of the first UE from the second UE.

26. A non-transitory computer-readable medium comprising stored instructions executable by a processor to perform the method according to any one of claims 1 to 12 for wireless communication by a first user equipment (UE).

Images