Systems and methods for wireless sidelink carrier aggregation communications

Abstract

Systems and methods for wireless sidelink carrier aggregation communications are provided. Systems, methods, and devices for wireless sidelink operation may include a first device including a transceiver and one or more processors configured to establish a sidelink connection with a second UE via the transceiver. The first UE may determine to operate in a carrier aggregation mode to communicate via a sidelink connection. The first UE may operate a sidelink connection according to a set of predefined parameters for each component carrier (CC) in response to determining to operate in a carrier aggregation mode.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of and priority to U.S. application No. 63 / 531,917, filed on August 10, 2023, and U.S. patent application No. 18 / 768,433, filed on July 10, 2024, the contents of which are incorporated herein by reference in their entirety. Technical Field

[0003] The present disclosure generally relates to wireless communications between multiple devices, including but not limited to systems and methods for wireless sidelink (SL) carrier aggregation communications. Background Art

[0004] Augmented reality (AR), virtual reality (VR) and mixed reality (MR) are becoming more and more common, and these technologies are supported on a wider range of platforms and devices. Some AR / VR / MR devices or wearable devices can communicate with other devices in the environment via corresponding sidelink communication channels. Summary of the invention

[0005] In one aspect, the present disclosure relates to a method. The method may include establishing, by a first user equipment (UE), a sidelink connection with a second UE. The method may include determining, by the first UE, to operate in a carrier aggregation mode to communicate via the sidelink connection. The method may include operating, by the first UE, the sidelink connection according to a set of predefined parameters in response to determining to operate in a carrier aggregation mode.

[0006] In some embodiments, the set of predefined parameters includes a selected SCS value selected from a plurality of sub-carrier spacing (SCS) values. In some embodiments, operating the sidelink connection includes modifying the size of a resource block (RB) size according to the SCS value. In some embodiments, operating the sidelink connection includes selecting a maximum transmission bandwidth according to the SCS value. In some embodiments, the maximum transmission bandwidth is selected according to the SCS value and the channel bandwidth corresponding to the sidelink connection. In some embodiments, operating the sidelink connection includes selecting a minimum guard band according to the SCS value. In some embodiments, the minimum guard band is selected according to the SCS value and the channel bandwidth corresponding to the sidelink connection. In some embodiments, the set of predefined parameters includes a reference measurement channel (RMC) configuration corresponding to an adjacent channel selectivity (ACS) configuration. In some embodiments, the first UE includes at least one of a first UE of a first pedestrian or a first UE of a first vehicle, and the second UE includes at least one of a second UE of a second pedestrian or a second UE of a second vehicle. In some embodiments, the method includes sending a signal indicating operation in a carrier aggregation mode to the second UE by the first UE.

[0007] In another aspect, the present disclosure relates to a first user equipment (UE) comprising a wireless transceiver and one or more processors configured to establish a sidelink connection with a second UE via the wireless transceiver. The one or more processors may be configured to determine to operate in a carrier aggregation mode to communicate via the sidelink connection. The one or more processors may be configured to operate the sidelink connection according to a set of predefined parameters in response to determining to operate in the carrier aggregation mode.

[0008] In some embodiments, the set of predefined parameters includes a selected subcarrier spacing (SCS) value selected from a plurality of SCS values. In some embodiments, operating the sidelink connection includes modifying the size of a resource block (RB) size based on the SCS value. In some embodiments, operating the sidelink connection includes selecting a maximum transmission bandwidth based on the SCS value. In some embodiments, the maximum transmission bandwidth is selected based on the SCS value and a channel bandwidth corresponding to the sidelink connection. In some embodiments, operating the sidelink connection includes selecting a minimum guard band based on the SCS value. In some embodiments, the minimum guard band is selected based on the SCS value and a channel bandwidth corresponding to the sidelink connection. In some embodiments, the set of predefined parameters includes a reference measurement channel (RMC) configuration corresponding to an adjacent channel selectivity (ACS) configuration. In some embodiments, the first UE includes at least one of a first UE of a first pedestrian or a first UE of a first vehicle, and the second UE includes at least one of a second UE of a second pedestrian or a second UE of a second vehicle.

[0009] In yet another aspect, the present disclosure relates to a first user equipment (UE) comprising a wireless transceiver and one or more processors configured to establish a sidelink connection with a second UE via the wireless transceiver. The one or more processors may be configured to receive an indication from the second UE to operate in a carrier aggregation mode to communicate via the sidelink connection. The one or more processors may be configured to operate the sidelink connection according to a set of predefined parameters in response to determining to operate in the carrier aggregation mode. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The accompanying drawings are not intended to be drawn to scale. Like reference numbers and names in the various drawings indicate like elements. For clarity, not every component is labeled in every drawing.

[0011] Figure 1 is a schematic diagram of an example wireless communication system according to an example implementation of the present disclosure.

[0012] Figure 2 is a schematic diagram of a console and a head wearable display for presenting augmented reality or virtual reality according to an example embodiment of the present disclosure.

[0013] Figure 3 is a schematic diagram of a head wearable display according to an exemplary embodiment of the present disclosure.

[0014] Figure 4 is a block diagram of a computing environment according to an example implementation of the present disclosure.

[0015] Figure 5is a block diagram of a system for wireless sidelink carrier aggregation communication according to an example embodiment of the present disclosure.

[0016] Figure 6 is a flow chart illustrating an example method for wireless sidelink carrier aggregation communications according to an example embodiment of the present disclosure. DETAILED DESCRIPTION

[0017] Before turning to the drawings that show certain embodiments in detail, it should be understood that the present disclosure is not limited to the details or methods set forth in the specification or shown in the drawings. It should also be understood that the terminology used herein is for descriptive purposes only and should not be considered as limiting.

[0018] Figure 1 An example wireless communication system 100 is shown. The wireless communication system 100 may include a base station 110 (also referred to as a "wireless communication node 110" or "station 110") and one or more user equipment (UE) 120 (also referred to as a "wireless communication device 120" or "terminal device 120"). The base station 110 and the UE 120 may communicate via wireless communication links 130A, 130B, 130N. The wireless communication link 130 may be a cellular communication link that complies with third generation mobile communication technology (3G), fourth generation mobile communication technology (4G), fifth generation mobile communication technology (5G), or other cellular communication protocols or Wi-Fi communication protocols. In one example, the wireless communication link 130 supports, employs, or is based on orthogonal frequency division multiple access (OFDMA). In one aspect, the UE 120 is located within a geographical boundary relative to the base station 110 and may communicate with or through the base station 110. In some embodiments, the wireless communication system 100 includes more than one wireless communication link. Figure 1 More components, fewer components, or including components shown in Figure 1 For example, the wireless communication system 100 may include components other than Figure 1 One or more additional base stations 110 other than the base station 110 shown in FIG.

[0019] In some embodiments, UE 120 may be a user device, such as a mobile phone, a smart phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, a wearable computing device, etc. Each UE 120 may communicate with a base station 110 via a corresponding communication link 130. For example, UE 120 may send data to base station 110 via wireless communication link 130, and receive data from base station 110 via wireless communication link 130. Example data may include audio data, image data, text, etc. Communication or data transmission by UE 120 to base station 110 may be referred to as uplink communication. Communication or data reception by UE 120 from base station 110 may be referred to as downlink communication. In some embodiments, UE 120A includes a wireless interface 122, a processor 124, a memory device (also referred to as memory) 126, and one or more antennas 128. These components may be implemented as hardware, software, firmware, or a combination thereof. In some embodiments, UE 120A includes more than one embodiment. Figure 1 More components, fewer components, or including components shown in Figure 1 For example, UE 120 may include an electronic display and / or input device. For example, UE 120 may include in addition to Figure 1 Additional antennas 128 and wireless interfaces 122 beyond the antennas 128 and wireless interfaces 122 shown in FIG.

[0020] Antenna 128 can be a component that receives radio frequency (RF) signals and / or sends RF signals through a wireless medium. The RF signal can be at a frequency between 200 megahertz (MHz) and 100 gigahertz (GHz). The RF signal can have a data packet, symbol or frame corresponding to the data used for communication. Antenna 128 can be a dipole antenna, a patch antenna, a loop antenna, or any suitable antenna for wireless communication. In one aspect, a single antenna 128 is used to both send and receive RF signals. In one aspect, different antennas 128 are used to send and receive RF signals. In one aspect, multiple antennas 128 are used to support multiple-input, multiple-out (MIMO) communications.

[0021] The wireless interface 122 includes or is implemented as a transceiver for sending and receiving RF signals through a wireless medium. The wireless interface 122 can communicate with the wireless interface 112 of the base station 110 through a wireless communication link 130A. In one configuration, the wireless interface 122 is coupled to one or more antennas 128. In one aspect, the wireless interface 122 can receive an RF signal at an RF frequency received by the antenna 128, and down-convert the RF signal to a baseband frequency (e.g., 0 GHz to 1 GHz). The wireless interface 122 can provide a down-converted signal to the processor 124. In one aspect, the wireless interface 122 can receive a baseband signal transmitted at a baseband frequency from the processor 124, and up-convert the baseband signal to generate an RF signal. The wireless interface 122 can send an RF signal through the antenna 128.

[0022] The processor 124 is a component for processing data. The processor 124 can be implemented as a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a logic circuit, etc. The processor 124 can obtain instructions from the memory device 126 and execute the instructions. In one aspect, the processor 124 can receive down-converted data at a baseband frequency from the wireless interface 122, and decode or process the down-converted data. For example, the processor 124 can generate audio data or image data based on the down-converted data, and present the audio indicated by the audio data and / or the image indicated by the image data to the user of the UE 120A. In one aspect, the processor 124 can generate or obtain data transmitted at a baseband frequency, and encode or process the data. For example, the processor 124 can encode or process image data or audio data at a baseband frequency, and provide the encoded or processed data to the wireless interface 122 for transmission.

[0023] The memory device 126 is a component that stores data. The memory device 126 can be implemented as a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a register, a hard disk, a removable disk, a compact disc read-only memory (CD-ROM), or any device capable of storing data. The memory device 126 can be implemented as a non-transitory computer-readable medium that stores the following instructions: the instructions can be executed by the processor 124 to perform various functions of the UE 120A disclosed herein. In some embodiments, the memory device 126 and the processor 124 are integrated into a single component.

[0024] In some embodiments, each of UEs 120B ... 120N includes similar components of UE 120A for communicating with base station 110. Therefore, for the sake of brevity, detailed descriptions of repeated parts thereof are omitted herein.

[0025] In some embodiments, the base station 110 may be an evolved node B (eNB), a serving eNB, a target eNB, a femto station, or a pico station. The base station 110 may be communicatively coupled to another base station 110 or other communication device via a wireless communication link and / or a wired communication link. The base station 110 may receive data (or RF signals) from the UE 120 in an uplink communication. Additionally or alternatively, the base station 110 may provide data to another UE 120, another base station, or another communication device. Thus, the base station 110 allows communication between multiple UEs 120 associated with the base station 110, or allows communication between other multiple UEs associated with different base stations. In some embodiments, the base station 110 includes a wireless interface 112, a processor 114, a memory device (also referred to as a memory) 116, and one or more antennas 118. These components may be implemented as hardware, software, firmware, or a combination thereof. In some embodiments, the base station 110 includes more than one embodiment of the present invention. Figure 1 More components, fewer components, or including components shown in Figure 1 For example, base station 110 may include an electronic display and / or an input device. For example, base station 110 may include an electronic display and / or an input device. Figure 1An additional antenna 118 and wireless interface 112 are provided in addition to the antenna 118 and wireless interface 112 shown in FIG.

[0026] Antenna 118 may be a component that receives radio frequency (RF) signals and / or transmits RF signals through a wireless medium. Antenna 118 may be a dipole antenna, a patch antenna, a loop antenna, or any suitable antenna for wireless communication. In one aspect, a single antenna 118 is used to both transmit and receive RF signals. In one aspect, different antennas 118 are utilized to transmit and receive RF signals. In one aspect, multiple antennas 128 are utilized to support multiple-input multiple-output (MIMO) communications.

[0027] The wireless interface 112 includes or is implemented as a transceiver for sending and receiving RF signals through a wireless medium. The wireless interface 112 can communicate with the wireless interface 122 of the UE 120 through a wireless communication link 130. In one configuration, the wireless interface 112 is coupled to one or more antennas 118. In one aspect, the wireless interface 112 can receive an RF signal at an RF frequency received by the antenna 118, and down-convert the RF signal to a baseband frequency (e.g., 0 GHz to 1 GHz). The wireless interface 112 can provide the processor 114 with a down-converted signal. In one aspect, the wireless interface 122 can receive a baseband signal transmitted at a baseband frequency from the processor 114, and up-convert the baseband signal to generate an RF signal. The wireless interface 112 can send an RF signal through the antenna 118.

[0028] Processor 114 is a component for processing data. Processor 114 can be implemented as FPGA, ASIC, logic circuit, etc. Processor 114 can obtain instructions from memory device 116 and execute the instructions. In one aspect, processor 114 can receive down-converted data at baseband frequency from wireless interface 112, and decode or process the down-converted data. For example, processor 114 can generate audio data or image data based on down-converted data. In one aspect, processor 114 can generate or obtain data for transmission at baseband frequency, and encode or process the data. For example, processor 114 can encode or process image data or audio data at baseband frequency, and provide encoded or processed data to wireless interface 112 for transmission. In one aspect, processor 114 can set, assign, schedule or allocate communication resources for different UE120. For example, processor 114 can set different modulation schemes, time slots, channels, frequency bands, etc. for each UE 120 to avoid interference. The processor 114 may generate data (or an uplink configuration grant (UL CG)) indicating the configuration of communication resources and provide the data (or UL CG) to the wireless interface 112 for transmission to the UE 120 .

[0029] The memory device 116 is a component that stores data. The memory device 116 may be implemented as a RAM, flash memory, ROM, EPROM, EEPROM, registers, a hard disk, a removable disk, a CD-ROM, or any device capable of storing data. The memory device 116 may be implemented as a non-transitory computer-readable medium that stores instructions that can be executed by the processor 114 to perform various functions of the base station 110 disclosed herein. In some embodiments, the memory device 116 and the processor 114 are integrated into a single component.

[0030] In some embodiments, the communication between the base station 110 and the UE 120 is based on one or more layers of the Open Systems Interconnection (OSI) model. The OSI model may include multiple layers, including: a physical layer; a medium access control (MAC) layer; a radio link control (RLC) layer; a packet data convergence protocol (PDCP) layer; a radio resource control (RRC) layer; a non-access stratum (NAS) layer or an Internet Protocol (IP) layer; and other layers.

[0031] Figure 2is a block diagram of an example artificial reality system environment 200. In some embodiments, the artificial reality system environment 200 includes a HWD 250 worn by a user, and a console 210 that provides artificial reality (e.g., augmented reality, virtual reality, mixed reality) content to the HWD 250. Each of the HWD 250 and the console 210 may be a separate UE 120. The HWD 250 may be referred to as, include, or be a part of a head mounted display (HMD), a head mounted device (HMD), a head wearable device (HWD), a head worn display (HWD), or a head worn device (HWD). The HWD 250 may detect the position and / or orientation of the HWD 250, and the shape, position and / or orientation of the body / hand / face of the user, and provide the detected position and / or orientation of the HWD 250, and / or tracking information indicating the shape, position and / or orientation of the body / hand / face to the console 210. The console 210 may generate image data indicating an artificial reality image based on the following items, and send the image data to the HWD 250 for presentation. In some embodiments, the artificial reality system environment 200 includes more than Figure 2 More components, fewer components, or including components shown in Figure 2 In some embodiments, the functionality of one or more components in the artificial reality system environment 200 may be distributed among the components in a manner different from that described herein. For example, some functions of the console 210 may be performed by the HWD 250. For example, some functions of the HWD 250 may be performed by the console 210. In some embodiments, the console 210 is integrated as part of the HWD 250.

[0032] In some embodiments, HWD 250 is an electronic component that can be worn by a user and can present or provide an artificial reality experience to the user. HWD 250 can render one or more images, videos, audio, or some combination thereof to provide an artificial reality experience to the user. In some embodiments, audio is presented via an external device (e.g., a speaker and / or headphones) that receives audio information from HWD 250, console 210, or both and presents audio based on the audio information. In some embodiments, HWD 250 includes a sensor 255, a wireless interface 265, a processor 270, an electronic display 275, a lens 280, and a compensator 285. These components can operate together to detect the position of HWD 250 and the gaze direction of the user wearing HWD 250, and render an image of a field of view corresponding to the detected position and / or orientation of HWD 250 within an artificial reality. In other embodiments, HWD 250 includes a sensor 255, a wireless interface 265, a processor 270, an electronic display 275, a lens 280, and a compensator 285. These components can operate together to detect the position of HWD 250 and the gaze direction of the user wearing HWD 250, and render an image of a field of view corresponding to the detected position and / or orientation of HWD 250 within an artificial reality. In other embodiments, HWD 250 includes a sensor 255, a wireless interface 265, a processor 270, an electronic display 275, a lens 280, and a compensator 285. Figure 2 The components shown may be more components, fewer components, or include components similar to those shown. Figure 2 The components shown in the figure are different components.

[0033] In some embodiments, sensor 255 includes an electronic component or a combination of an electronic component and a software component that detects the position and orientation of HWD 250. Examples of sensor 255 may include: one or more imaging sensors, one or more accelerometers, one or more gyroscopes, one or more magnetometers, or another suitable type of sensor that detects motion and / or position. For example, one or more accelerometers may measure translational motion (e.g., forward / backward, upward / downward, left / right), and one or more gyroscopes may measure rotational motion (e.g., pitch, yaw, roll). In some embodiments, sensor 255 detects translational motion and rotational motion, and determines the orientation and position of HWD 250. In one aspect, sensor 255 may detect translational motion and rotational motion relative to the previous orientation and position of HWD 250, and determines the new orientation and / or position of HWD 250 by accumulating or integrating the detected translational motion and / or rotational motion. For example, assuming that HWD 250 is facing a direction 25 degrees from a reference direction, sensor 255 may determine that HWD 250 is now facing or facing a direction 45 degrees from the reference direction in response to detecting that HWD 250 has turned 20 degrees. For another example, assuming that HWD 250 is located two feet away from a reference point in a first direction, sensor 255 may determine that HWD 250 is now located at the vector product of two feet in the first direction and three feet in the second direction in response to detecting that HWD 250 has moved three feet in the second direction.

[0034] In some embodiments, the sensor 255 includes an eye tracker. These eye trackers may include electronic components, or a combination of electronic components and software components, that determine the gaze direction of the user of the HWD 250. In some embodiments, the HWD 250, the console 210, or a combination thereof may generate image data for artificial reality in conjunction with the gaze direction of the user of the HWD 250. In some embodiments, the plurality of eye trackers include two eye trackers, each of which captures an image of a corresponding eye and determines the gaze direction of the eye. In one example, the eye tracker determines the angular rotation of the eye, the translation of the eye, the torsion change of the eye, and / or the change in the shape of the eye based on the captured eye image, and determines the relative gaze direction relative to the HWD 250 based on the determined angular rotation of the eye, the translation of the eye, and the torsion change of the eye. In one method, the eye tracker may illuminate or project a predetermined reference pattern or structured pattern on a portion of the eye, and capture an image of the eye to analyze the pattern projected on the portion of the eye to determine the relative gaze direction of the eye relative to the HWD 250. In some embodiments, the eye tracker determines the user's gaze direction in combination with the orientation of HWD 250 and the relative gaze direction relative to HWD 250. For example, assuming that HWD 250 is oriented in a direction 30 degrees from a reference direction, and the relative gaze direction of HWD 250 relative to HWD 250 is -10 degrees (or 350 degrees), the eye tracker can determine that the user's gaze direction is 20 degrees from the reference direction. In some embodiments, the user of HWD 250 can configure HWD 250 (e.g., via user settings) to enable or disable the eye tracker. In some embodiments, the user of HWD 250 is prompted to enable or disable the eye tracker.

[0035] In some embodiments, the wireless interface 265 includes electronic components, or a combination of electronic components and software components, that communicate with the console 210. The wireless interface 265 may be or correspond to the wireless interface 122. The wireless interface 265 may communicate with the wireless interface 215 of the console 210 via a wireless communication link via the base station 110. Through the communication link, the wireless interface 265 may transmit data indicating the determined position and / or orientation of the HWD 250 and / or the determined user gaze direction to the console 210. In addition, through the communication link, the wireless interface 265 may receive image data indicating or corresponding to an image to be rendered and additional data associated with the image from the console 210.

[0036] In some embodiments, the processor 270 includes an electronic component, or a combination of electronic components and software components, that generates one or more images for display (e.g., according to a change in the field of view of the space of the artificial reality). In some embodiments, the processor 270 is implemented as a part of the processor 124, or is communicatively coupled to the processor 124. In some embodiments, the processor 270 is implemented as a processor (or a graphical processing unit (GPU)) that executes multiple instructions to perform various functions described herein. The processor 270 can receive image data describing an artificial reality image to be rendered, and additional data associated with the image through the wireless interface 265, and the processor 270 can render the image for display through the electronic display 275. In some embodiments, the image data from the console 210 can be encoded, and the processor 270 can decode the image data to render the image. In some embodiments, the processor 270 receives object information and depth information located in the additional data from the console 210, the object information indicating a virtual object in the artificial reality space, and the depth information indicating the depth of the virtual object (or the distance from the HWD 250). In one aspect, the processor 270 may perform shading, reprojection, and / or blending based on the artificial reality image from the console 210, object information, depth information, and / or updated sensor measurements from the sensor 255 to update the artificial reality image to correspond to the updated position and / or orientation of the HWD 250. Assuming that the user turns his head after the initial sensor measurements, the processor 270 may generate a small portion (e.g., 10%) of the image corresponding to the updated field of view within the artificial reality based on the updated sensor measurements and append the portion to the image in the image data from the console 210 by reprojection, rather than reconstructing the entire image in response to the updated sensor measurements. The processor 270 may perform shading and / or blending on the additional edges. Thus, the processor 270 may generate an image of the artificial reality without reconstructing the image of the artificial reality based on the updated sensor measurements.

[0037] In some embodiments, the electronic display 275 is an electronic component that displays an image. The electronic display 275 may be, for example, a liquid crystal display or an organic light emitting diode display. The electronic display 275 may be a transparent display that allows the user to see through. In some embodiments, when the user wears the HWD 250, the electronic display 275 is located near the user's eyes (e.g., less than 3 inches). In one aspect, the electronic display 275 emits light or projects light toward the user's eyes according to the image generated by the processor 270.

[0038] In some embodiments, lens 280 is a mechanical component that changes the light received from electronic display 275. Lens 280 can magnify the light from electronic display 275 and correct the optical errors associated with the light. Lens 280 can be a Fresnel lens, a convex lens, a concave lens, a filter, or any suitable optical component that changes the light from electronic display 275. Although electronic display 275 is very close to both eyes, light from electronic display 275 can still pass through lens 280 to the pupil so that the user can see the image displayed by electronic display 275.

[0039] In some embodiments, compensator 285 includes electronic components, or a combination of electronic components and software components, that perform compensation to compensate for any distortion or aberration. In one aspect, lens 280 introduces optical aberrations (e.g., chromatic aberration), pincushion distortion, barrel distortion, etc. Compensator 285 can determine compensation (e.g., pre-distortion) to be applied to the image to be rendered from processor 270 to compensate for the distortion caused by lens 280, and apply the determined compensation to the image from processor 270. Compensator 285 can provide the pre-distorted image to electronic display 275.

[0040] In some embodiments, the console 210 is an electronic component or a combination of an electronic component and a software component that provides content to be rendered to the HWD 250. In one aspect, the console 210 includes a wireless interface 215 and a processor 230. These components can operate together to determine the visual field of artificial reality corresponding to the position of the HWD 250 and the gaze direction of the user of the HWD 250 (e.g., the user's field of view (FOV)), and can generate image data indicating an artificial reality image corresponding to the determined visual field. In addition, these components can operate together to generate additional data associated with the image. Additional data can be information associated with presenting or rendering artificial reality in addition to the artificial reality image. Examples of additional data include hand model data, mapping information (or simultaneous localization and mapping (SLAM) data) for converting the position and orientation of the HWD 250 in the physical space to the virtual space, eye tracking data, motion vector information, depth information, edge information, object information, etc. The console 210 may provide image data and additional data to the HWD 250 for use in presenting artificial reality. Figure 2 More components, fewer components, or including components shown in Figure 2 In some embodiments, console 210 is integrated as a part of HWD 250.

[0041] In some embodiments, the wireless interface 215 is an electronic component, or a combination of an electronic component and a software component, that communicates with the HWD 250. The wireless interface 215 may be or correspond to the wireless interface 122. The wireless interface 215 may be a corresponding component of the wireless interface 265 to communicate via a communication link (e.g., a wireless communication link). The wireless interface 215 may receive data from the HWD 250 via the communication link, the data indicating the determined position and / or orientation of the HWD 250, and / or the determined user gaze direction. In addition, via the communication link, the wireless interface 215 may transmit image data describing the image to be rendered and additional data associated with the image of the artificial reality to the HWD 250.

[0042] The processor 230 may include or correspond to a component that generates content to be rendered based on the position and / or orientation of the HWD 250. In some embodiments, the processor 230 is implemented as a part of the processor 124 or is communicatively coupled to the processor 124. In some embodiments, the processor 230 may be combined with the gaze direction of the user of the HWD 250. In one aspect, the processor 230 determines the view of the artificial reality based on the position and / or orientation of the HWD 250. For example, the processor 230 maps the position of the HWD 250 in the physical space to a position within the artificial reality space, and determines the view of the artificial reality space along the direction corresponding to the mapped orientation from the position in the mapped artificial reality space. The processor 230 may generate image data of an image describing the view of the determined artificial reality space, and transmit the image data to the HWD 250 via the wireless interface 215. In some embodiments, the processor 230 may generate additional data associated with the image (the additional data may include motion vector information, depth information, edge information, object information, hand model data, etc.), and transmit the additional data together with the image data to the HWD 250 through the wireless interface 215. The processor 230 may encode the image data describing the image, and may transmit the encoded data to the HWD 250. In some embodiments, the processor 230 generates image data periodically (e.g., every 11 milliseconds (ms)) and provides the image data to the HWD 250.

[0043] In one aspect, the process of detecting the position of the HWD 250 and the gaze direction of the user wearing the HWD 250 and rendering the image to the user should be performed within one frame time (e.g., 11ms or 16ms). The delay between the movement of the user wearing the HWD 250 and the image displayed corresponding to the user's movement may cause jitter, which may cause motion sickness and may reduce the user experience. In one aspect, the HWD 250 and the console 210 can prioritize the communication of AR / VR so that the delay between the movement of the user wearing the HWD 250 and the image displayed corresponding to the user's movement can be presented within one frame time (e.g., 11ms or 16ms) to provide a seamless experience.

[0044] Figure 3 2 is a schematic diagram of HWD 250 according to an exemplary embodiment. In some embodiments, HWD 250 includes a front rigid body 305 and a belt 310. Front rigid body 305 includes: electronic display 275 ( Figure 3 Not shown), lens 280 ( Figure 3 ), sensor 255, wireless interface 265, and processor 270. Figure 3 In the illustrated embodiment, the wireless interface 265, processor 270, and sensor 255 are located within the front rigid body 305 and may not be visible to the outside. Figure 3 For example, the wireless interface 265, the processor 270 and / or the sensor 255 may be located in a different configuration than that shown in FIG. Figure 3 The positions shown in the figure are different positions.

[0045] Various operations described herein may be implemented on a computer system. Figure 4 A block diagram of a representative computing system 414 that can be used to implement the present disclosure is shown. In some embodiments, the base station 110, the UE 120, the console 210, and the HWD 250 can be implemented by the computing system 414. The computing system 414 can be implemented, for example, as a consumer device, such as a smartphone, other mobile phones, tablet computers, wearable computing devices (e.g., smart watches, glasses, head wearable displays), desktop computers, laptop computers; or can be implemented using distributed computing devices. The computing system 414 can be implemented to provide VR experience, AR experience, MR experience. In some embodiments, the computing system 414 may include traditional computer components, such as a processor unit 416, a storage device 418, a network interface 420, a user input device 422, and a user output device 424.

[0046] The network interface 420 can provide a connection to a wide area network (e.g., the Internet) to which a wide area network (WAN) interface of the remote server system is also connected. The network interface 420 can include a wired interface (e.g., Ethernet) and / or a wireless interface that implements various radio frequency (RF) data communication standards, such as Wi-Fi, Bluetooth, or cellular data network standards (e.g., 3G, 4G, 5G, 60GHz, Long Term Evolution (LTE), etc.).

[0047] The network interface 420 may include a transceiver to allow the computing system 414 to send data to a remote device using a transmitter and to receive data from a remote device using a receiver. The transceiver may be configured to support such transmission / reception: the transmission / reception supports industrial standards for implementing two-way communication. An antenna may be attached to the transceiver housing and electrically coupled to the transceiver. Additionally or alternatively, a multi-antenna array may be electrically coupled to the transceiver so that multiple beams pointing in different directions can facilitate sending and / or receiving data.

[0048] The transmitter may be configured to wirelessly transmit a frame, time slot, or symbol generated by the processor unit 416. Similarly, the receiver may be configured to receive a frame, time slot, or symbol, and the processor unit 416 may be configured to process the frame. For example, the processor unit 416 may be configured to determine the type of frame and process the frame and / or fields of the frame accordingly.

[0049] User input device 422 may include any device (or devices) via which a user may provide signals to computing system 414; computing system 414 may interpret these signals as indicating a particular user request or information. User input device 422 may include any or all of the following: a keyboard; a touch pad; a touch screen; a mouse or other pointing device; a scroll wheel; a click wheel; a dial; a button; a switch; a keypad; a microphone; and a sensor (e.g., a motion sensor, an eye tracking sensor, etc.), etc.

[0050] User output device 424 may include any device via which computing system 414 can provide information to a user. For example, user output device 424 may include a display for displaying images generated by computing system 414 or delivered to computing system 314. The display may be combined with various image generation technologies and supporting electronic devices (e.g., digital-to-analog converters or analog-to-digital converters, or signal processors, etc.), such as liquid crystal displays (LCDs), light-emitting diodes (LEDs) including organic light-emitting diodes (OLEDs), projection systems, or cathode ray tubes (CRTs), etc. Devices that act as both input devices and output devices, such as touch screens, may be used. User output device 424 may be provided in addition to or in place of a display. Examples include indicator lights, speakers, tactile "display" devices, and printers, etc.

[0051] Some embodiments include electronic components storing computer program instructions in computer-readable storage media (e.g., non-transient computer-readable media), such as microprocessors, storage devices, and memory. Many of the multiple features described in this specification may be implemented as a process: the process is specified as a set of program instructions encoded on a computer-readable storage medium. These program instructions, when executed by one or more processors, cause the processor to perform the various operations indicated in these program instructions. Examples of program instructions or computer codes include machine codes and files, which are generated, for example, by a compiler, and the files include high-level codes executed by a computer, electronic component, or microprocessor using an interpreter. Through suitable programming, the processor unit 416 can provide various functions for the computing system 414, including any of the following: functions described herein as being executed by a server or client, or other functions associated with a message management service.

[0052] It will be understood that computing system 414 is illustrative and various variations and modifications may be made. The computer system used in conjunction with the present disclosure may have other capabilities not explicitly described herein. In addition, although computing system 414 is described with reference to specific blocks, it should be understood that these blocks are defined for the convenience of description and are not intended to imply a specific physical arrangement structure of component parts. For example, different blocks may be located in the same facility, in the same server rack, or on the same motherboard. In addition, these blocks do not have to correspond to physically different components. Each block may be configured to perform various operations, such as by programming a processor or providing an appropriate and suitable control circuit, and various blocks may or may not be reconfigurable, depending on how to obtain the initial configuration. Embodiments of the present disclosure may be implemented in a variety of devices, including electronic devices implemented using any combination of circuits and software.

[0053] The disclosure herein relates to systems and methods for performing sidelink (SL) carrier aggregation (SL-CA) communications. Sidelink operations may be described in various standard requests to support sidelink carrier aggregation (CA) in an intelligent transportation system (ITS) spectrum. For example, some embodiments may include support for LTE SL-CA features (e.g., SL carrier (re)selection, synchronization of aggregated carriers, power control for synchronous SL transmission, packet duplication, etc.) for new radio (NR). However, multiple subcarrier spacing values ​​may be supported in various spectrums (e.g., spectrum at frequency range (FR) 1). Such subcarrier spacing values ​​for SL-CA may include, for example, 15 kilohertz (kHz), 30kHz, and / or 60kHz at a 5G NR system. In addition, in a 5G NR system, spectrum utility (SU) to accommodate larger resource block (RB) sizes in certain channel bandwidths (BW) is increased from a 4G LTE system. In addition, some embodiments may include updating the SL initial access mechanism using a merged SL synchronization signal block (S-SSB), where the merged S-SSB is based on a sidelink synchronization channel (SLSS) and a SL broadcast channel (S-PBCH) for 5G NR SL operations. In addition, some embodiments may include a restricted SL time slot structure that supports a physical sidelink control channel (PSCCH) / physical sidelink shared channel (PSSCH) multiplexing method. Based on these improvements, certain enhancements to reference measurement results and / or other parameters may be achieved. According to the systems and methods described herein, the present solution may define specific SL parameters / features for RF requirements (especially for SL-CA operations).

[0054] In various embodiments, a first wireless communication device or a first user equipment (UE) may establish a sidelink connection with a second UE. The first UE may determine to operate in a carrier aggregation (CA) mode to communicate via the sidelink connection. The first UE may operate the sidelink connection according to a set of predefined parameters in response to determining to operate in CA mode. According to various embodiments of the present solution, the systems and methods described herein may meet various RF requirements for SL-CA operation while accommodating additional multiple subcarrier spacing values ​​and meeting increased spectrum utilization (e.g., in 5G NR) and other updated items.

[0055] Reference now Figure 5 , depicted is a block diagram of a system 500 for wireless sidelink carrier aggregation communications according to an example embodiment of the present disclosure. The system 500 may include a first device 502 and a second device 504. In various embodiments, the first device 502 and the second device 504 may be configured to establish or maintain a sidelink (SL) connection (in Figure 5 The first device 502 may be configured to determine to operate in a carrier aggregation (CA) mode to communicate via a SL connection. The first device 502 (and the second device 504) may be configured to operate the SL connection according to a set of predefined parameters in response to determining to operate in the SL-CA mode.

[0056] The first device 502 and the second device 504 may be similar to the above-mentioned devices, components, elements or hardware. In various embodiments, the first device 502 and / or the second device 504 may be a lightweight (reduced capability, RedCap) device. For example, the first device 502 may be a wearable device. In some embodiments, the first device 502 and the second device 504 may be or include a device that provides an extended reality (extended reality, XR) environment to the user. For example, the first device 502 may be a head wearable device, and the second device 504 may be a console. In some embodiments, the first device 502 may be a device of one user, and the second device 504 may be a device of another user. For example, the first device 502 may be a device corresponding to a vehicle (e.g., a car, a bicycle, a motorcycle, a bus), and the second device 504 may be a device of a user (e.g., a pedestrian). In addition, in some embodiments, the first device 502 may be a device corresponding to a vehicle, and the second device 504 may be a device corresponding to another vehicle.

[0057] The first device 502 and the second device 504 may include one or more processors 506 and a memory 508. The one or more processors 506 may be similar to: Figure 1Processors 114, 124 in; Figure 2 and Figure 3 One or more processors 230, 270; and / or Figure 4 The processor unit 416 in. The memory 508 may be similar to: Figure 1 Memory 116, 126 in; and / or Figure 4 The first device 502 and the second device 504 may include a wireless interface 510, which may be similar to Figures 1 to 3 The wireless interface 112, 122, 215, 265 and / or Figure 4 The network interface 420 in.

[0058] The first device 502 and the second device 504 may include one or more processing engines 512. The one or more processing engines 512 may be or include any device, component, element or hardware designed or configured to perform various functions of the device. Although the one or more processing engines 512 are shown as being implemented on the corresponding devices 502, 504, in various embodiments, the one or more processing engines 512 may be or include the hardware of the wireless interface 510. The one or more processing engines 512 may include a connection manager 514 and a parameter controller 516. Although these two one or more processing engines 512 are shown and described, in various embodiments, additional processing engines 512 may be implemented at the devices 502, 504 and / or in the wireless interface 510. In addition, in various embodiments, one or more processing engines 512 may be combined with another processing engine 512. Additionally or alternatively, a processing engine 512 may be divided into multiple processing engines 512.

[0059] The devices 502, 504 may include a connection manager 514. The connection manager 514 may be or include any device, component, element, or hardware that is designed or configured to establish, generate, maintain, or otherwise manage various connections (e.g., wireless connections) with one or more endpoints or nodes. In some embodiments, the connection manager 514 may be configured to manage a sidelink connection between the first device 502 and the second device, and to manage an uplink / downlink (e.g., non-sidelink) cellular connection between the respective devices 502, 504 and the base station 110. In this regard, the connection manager 514 may be configured to manage device-to-device connections and device-to-network (or device-to-base station) connections.

[0060] The connection manager 514 may be configured to generate, create, or otherwise establish a sidelink (SL) connection between the first device 502 and the second device 504. In some embodiments, the connection manager 514 may be configured to establish a SL connection by performing device discovery and proximity detection. For example, the connection manager 514 of the first device 502 may be configured to broadcast a discovery signal (e.g., via the wireless interface 510), and the connection manager 514 of the second device 504 may be configured to detect the discovery signal from the first device 502. The connection manager 514 may be configured to determine the proximity between the devices 502 and 504 (e.g., based on the signal strength of the discovery signal sent by the first device 502 and received by the second device 504 in the above example). The connection manager 514 may be configured to perform various additional steps (e.g., permission and identity authentication) that may be required to establish a SL connection.

[0061] The connection manager 514 may be configured to determine the resources allocated for the SL connection. For example, the connection manager 514 may be configured to determine the resources allocated by the base station 110 or the core network for the sidelink connection. In some embodiments, the allocated resources may be or include a specific frequency or frequency range, a specific time slot, etc. In some embodiments, the allocated resources may include frequencies in an unlicensed band, which includes an ITS spectrum. For example, the unlicensed band may be an ITS spectrum (5855 MHz to 5925 MHz) or include n46 (5150 MHz to 5925 MHz), n96 (5925 MHz to 7125 MHz), and n102 (5925 MHz to 6425 MHz). In some examples, the unlicensed band may include a higher unlicensed frequency range between 5.925 gigahertz (GHz) and 7.125 GHz. The connection manager 514 may be configured to receive allocated resources from the base station 110 or the core network, the allocated resources including a specific frequency or frequency range in which to establish a SL connection between the first device 502 and the second device 504 .

[0062] The connection manager 514 may be configured to generate, maintain, or otherwise establish a SL connection based on the allocated resources (e.g., from a base station or core network). In some embodiments, the connection manager 514 may be configured to establish a SL connection in an unlicensed band. For example, where the allocated resources include a specific frequency or frequency band within an unlicensed band, the connection manager 514 may be configured to establish a SL connection in the unlicensed band.

[0063] In some embodiments, the connection manager 514 may be configured to establish a SL connection as a SL unlicensed (SL-unlicensed, SL-U) connection and / or a SL carrier aggregation (SL-CA) connection. A SL-U connection may be or include a SL connection within an unlicensed band (e.g., n46, n96, and n102). A SL-CA connection may be or include a SL connection that combines (or aggregates) multiple bands (or carriers) into a single data channel in an unlicensed band. The connection manager 514 may be configured to establish a SL connection as a SL-U / SL-CA connection based on allocated resources from the base station 110 and / or the core network.

[0064] In some embodiments, the connection manager 514 may be configured to establish and maintain / manage SL connections and other cellular (e.g., non-sidelink) connections. For example, the connection manager 514 may be configured to establish and maintain one or more cellular connections with the base station 110. The connection manager 514 may be configured to establish a cellular connection with the base station 110 in a manner similar to the wireless communication link 130 described above. In some embodiments, the process by which the connection manager 514 establishes a cellular connection with the base station 110 may be similar to establishing an SL connection. For example, the connection manager 514 may be configured to receive a signal broadcast by the base station 110 and establish a connection based on the allocated resources from the base station 110. In some embodiments, the connection manager 514 may be configured to establish a cellular connection in a licensed band. For example, the base station 110 and / or the core network may allocate resources (e.g., a frequency band or one or more channels) in a licensed band for a cellular connection between the devices 502, 504 and the base station 110. The connection manager 514 may be configured to establish and / or maintain a cellular connection (e.g., maintain a cellular connection in a licensed band) based on the allocated resources.

[0065] In some embodiments, the connection manager 514 may be configured to establish, maintain or otherwise coordinate multiple connections. For example, the connection manager 514 may be configured to coordinate the SL connection between the first device 502 and the second device 504, and the cellular connection between the corresponding devices 502, 504 and the base station 110. The connection manager 514 may be configured to coordinate these connections by operating, utilizing or otherwise using each connection together (e.g., in parallel). For example, the connection manager 514 may be configured to transmit various signals / data packets / protocol data units (PDUs) via corresponding connections in different frequencies or time periods. In this regard, in various instances, the connection manager 514 may be configured to utilize a cellular connection to send data to one or more remote sources via the base station 110 and / or receive data from one or more remote sources, and may utilize a SL connection to send and / or receive data between devices 502, 504 (e.g., relatively locally).

[0066] The parameter controller 516 may be designed or configured to select, identify, control or otherwise determine parameters to be used for the SL connection between the first device 502 and the second device 504. In some embodiments, as described above, in the case where the connection manager 514 determines to establish a SL-CA connection between the first device 502 and the second device 504, the parameter controller 516 may be configured to identify, determine or otherwise select a set of predefined parameters in which the SL connection is operated in response to a determination to operate in CA mode. For example, the parameter controller 516 may be configured to select a set of predefined parameters associated with the CA mode in response to a determination to operate in CA mode. The parameter controller 516 may be configured to select predefined parameters for each component carrier (CC) in response to a determination to operate in CA mode. In other words, the predefined parameters for the SL connection may include predefined parameters for each CC.

[0067] In some embodiments, the parameter controller 516 can be configured to select parameters to be tested for verifying compliance / operational settings, etc. related to the SL connection. For example, the first device 502 can be tested for SL operation before the first device 502 is deployed. The parameter controller 516 can be configured to select various parameters for operating the SL connection during the testing phase and before deployment, where the selection of these parameters can be similar to the selection described herein as part of the deployment. Therefore, in various instances in which the first device 502 determines to operate in CA mode (e.g., as part of testing), the first device 502 can be configured to select predefined parameters for testing the operation of the first device 502 in CA mode. In other words, the parameter controller 516 can be configured to select the parameters described herein for verifying / evaluating / testing the operation of the first device 502 in SL CA mode (e.g., transmitter operation and / or receiver operation of the SL CA UE) before deployment. When the first device 502 is deployed, the first device 502 can operate the SL connection according to preconfigured and tested parameters (e.g., parameters used to meet its own transmission / reception parameters or requirements, and / or coexistence parameters or requirements).

[0068] The parameter controller 516 may be configured to select a subcarrier spacing (SCS) value for operating a SL connection in CA mode. The parameter controller 516 may be configured to select an SCS value from a plurality of SCS values, such as 15 kilohertz (kHz), 30 kHz, and 60 kHz. In some embodiments, the parameter controller 516 may be configured to select an SCS value based on allocated resources for the SL connection (e.g., from the base station 110).

[0069] The parameter controller 516 may be configured to select, identify, configure, or otherwise determine a channel bandwidth to be used for the SL connection. In some embodiments, the parameter controller 516 may be configured to determine the channel bandwidth based on the allocated bandwidth from the base station 110. The parameter controller 516 may be configured to request the allocated bandwidth for the SL connection (e.g., based on an application or resource being executed on the device, based on a preconfigured requested allocated resource for the SL connection, etc.). The parameter controller 516 may be configured to determine the channel bandwidth from a plurality of available channel bandwidths, such as (but not limited to) 3 megahertz (MHz), 5 MHz, 10 MHz, 15 MHz, 20 MHz, 25 MHz, 30 MHz, 35 MHz, 40 MHz, 45 MHz, 50 MHz, 60 MHz, 70 MHz, 80 MHz, 90 MHz, and / or 100 MHz. In particular, in some embodiments, channel bandwidths (CBW) of up to 70 MHz in the ITS spectrum may be supported.

[0070] The parameter controller 516 may be configured to select, identify, configure, or otherwise determine the maximum transmission bandwidth configuration N for a resource block. RB In some embodiments, the parameter controller 516 may be configured to determine the maximum transmission bandwidth configuration based on or in accordance with the selected subcarrier spacing and / or channel bandwidth. For example, the parameter controller 516 may be configured to determine the maximum transmission bandwidth configuration by cross-referencing the selected subcarrier spacing and channel bandwidth with a data structure identifying the corresponding maximum transmission bandwidth configuration. The data structure may be maintained locally at the first device 502 and / or stored remotely and accessible by the first device 502. An example of such a data structure is included in Table 1 below.

[0071]

[0072] Table 1. Maximum transmission bandwidth configuration

[0073] The parameter controller 516 may be configured to select, identify, configure, or otherwise determine the minimum guard band. In some embodiments, the parameter controller 516 may be configured to determine the minimum guard band based on or according to the selected subcarrier spacing and / or channel bandwidth. The parameter controller 516 may be configured to determine the minimum guard band according to the channel bandwidth, the maximum transmission bandwidth configuration, and the subcarrier spacing. For example, the parameter controller 516 may be configured to calculate the minimum guard band using the following equation 1, where BW 信道 is the channel bandwidth, N RB is the maximum transmission bandwidth configuration, and SCS is the subcarrier spacing, and where GB 信道is the minimum guard band (in kHz):

[0074]

[0075] In some embodiments, similar to determining the maximum transmission bandwidth configuration, the parameter controller 516 can be configured to determine the minimum guard band by cross-referencing the selected subcarrier spacing and channel bandwidth with a data structure identifying the corresponding minimum guard band. The data structure can be maintained locally at the first device 502 and / or stored remotely and accessible by the first device 502. An example of such a data structure is included in Table 2, where an example minimum guard band is shown as calculated for a channel bandwidth between 20 MHz and 50 MHz (e.g., using Formula 1 above).

[0076]

[0077]

[0078] Table 2. Minimum guard bands

[0079] Note that some minimum guard bands may not be applicable at certain combinations of channel bandwidth and SCS value. For example, for a channel bandwidth greater than or equal to 60 MHz, the minimum guard band may not be applicable at an SCS value of 15 kHz; for a channel bandwidth of 3 MHz, the minimum guard band may not be applicable at an SCS value of 30 kHz; or for a channel bandwidth less than 10 MHz, the minimum guard band may not be applicable at an SCS value of 60 kHz.

[0080] The parameter controller 516 may be configured to determine other parameters for operating the SL channel in response to determining to operate in the NR SL CA mode. For example, the parameter controller 516 may be configured to determine one or more predefined or preconfigured parameters (e.g., a maximum input level of the first device 502) according to the SL-CA bandwidth category. In some embodiments, the maximum input level may be preconfigured and tested for compliance according to the formula set forth in Table 3 below, where 10log 10 (Value) Rounded to the nearest 0.5 decibel (dB).

[0081]

[0082] Table 3. Maximum input levels of SL-CA

[0083] The parameter controller 516 may be configured to determine one or more pre-configured and tested parameters to comply with adjacent channel selectivity (ACS) values / settings / configurations / requirements. For example, the ACS values ​​may be pre-configured and tested according to the following Tables 4 to 6, depending on the various input parameters described therein (e.g., whether the carrier aggregation is an intra-band carrier aggregation according to the power level of the interference source).

[0084] SL CA Bandwidth Category Rx parameters unit B ACS dB 20.0

[0085] Table 4 ACS of SL-CA

[0086]

[0087]

[0088] Table 5 is for ACS with in-band SL-CA, case 1.

[0089]

[0090] Table 6. ACS for in-band SL-CA, case 2.

[0091] The parameter controller 516 may be configured to operate the SL connection according to various preconfigured and tested in-band blocking parameters. For example, (e.g., in instances where the SL connection is used for in-band continuous operation) the in-band blocking parameters may be tested and preconfigured according to the following Tables 7 and 8 to comply with transmit (TX) / RX requirements / settings / configurations, and / or to coexist with other legacy protocols or signaling.

[0092]

[0093] Table 7. In-band blocking parameters for in-band SL-CA.

[0094]

[0095] Table 8. In-band blocking parameters for in-band continuous SL-CA.

[0096] The parameter controller 516 may be configured to operate the SL connection according to various preconfigured and tested out-of-band blocking parameters. For example, (e.g., in instances where the SL connection is used for in-band continuous operation) the out-of-band blocking parameters may be tested and preconfigured according to the following Tables 9 and 10 to comply with various operating parameters / configurations / settings for TX / RX on the SL connection, and / or to coexist with legacy communications or signaling.

[0097]

[0098] Table 9. Out-of-band blocking parameters for in-band SL-CA.

[0099]

[0100] Table 10. Out-of-band blocking parameters for in-band continuous SL-CA.

[0101] The parameter controller 516 may be configured to operate the SL connection according to various pre-configured and tested spurious response parameters. For example, the spurious response parameters may be pre-configured and tested according to the following Tables 11 and 12 to meet TX / RX requirements and coexistence requirements.

[0102]

[0103] Table 11. Spurious response parameters for in-band continuous SL-CA.

[0104]

[0105] Table 12. Spurious response parameters for in-band continuous SL-CA.

[0106] The parameter controller 516 can be configured to operate the SL connection according to various pre-configured and tested wideband intermodulation. For example, similar to the above parameters, wideband intermodulation parameters can be tested and pre-configured according to the following Table 13 to meet coexistence compliance and TX / RX operation configuration.

[0107]

[0108] Table 13. Wideband intermodulation parameters for in-band continuous SL-CA.

[0109] When determining one or more parameters for operating the SL connection in CA mode, the wireless interface 510 may be configured to control, transmit, configure, or otherwise operate the SL connection according to the parameters selected / determined / preconfigured / tested by the parameter controller 516. For example, the wireless interface 510 may be configured to operate the SL connection based on or according to the selected / determined / predetermined parameters including a maximum transmission bandwidth configuration, a minimum guard band, a maximum input level, an ACS configuration and corresponding parameters, an in-band blocking parameter, an out-of-band blocking parameter, a spurious response parameter, and / or a wideband intermodulation parameter.

[0110] In some embodiments, in response to determining to operate in CA mode, the wireless interface 510 (e.g., of the first device 502) may be configured to transmit, convey, send, or otherwise provide a signal / message / indication to the second device 504. The indication may be configured, for example, to indicate to the second device 504 that it is operating in CA mode. In some embodiments, the indication may indicate parameters for operating a SL connection in CA mode. In this regard, the first device 502 may be a master device that indicates parameters to the second device 504, which may be a slave device. In some embodiments, the indication may indicate various information related to information such as allocated resources / channels, so that the second device 504 may be configured to independently derive parameters for operating a SL connection in CA mode.

[0111] Reference now Figure 6 , depicted is a flowchart illustrating an example method 600 for wireless sidelink carrier aggregation communication according to an example embodiment of the present disclosure. The method 600 may be referred to above. Figures 1 to 5 Implementation, execution or otherwise realization of the device, component, element or hardware described herein, such as a first device 502 (or primary device / user equipment (UE) 502) and / or a second device 504 (or secondary device / UE 504). As a brief overview, the method 600 may begin at step 602, where the first UE 502 establishes a sidelink connection. At step 604, the first UE 502 may determine to operate in carrier aggregation mode. At step 606, the first UE 502 may determine parameters. At step 608, the first UE 502 may send an indication to the second UE 504. At step 610, the second UE 504 may determine to operate in carrier aggregation mode. At step 612, the second UE 504 may determine parameters. At step 614, the first UE 502 (and the second UE 504) may operate the sidelink connection.

[0112] In step 602, the first UE establishes a sidelink connection. In some embodiments, the first UE may generate, create, or otherwise establish a SL connection between the first UE and the second UE. The first UE may establish a SL connection between the first UE and the second UE to exchange, send, receive, or otherwise share data / information / data packets / messages / transmissions between the first device and the second device (e.g., locally). At this point, the SL connection may be a device-to-device (D2D) connection. The first UE may establish a SL connection in response to a message / beacon / frame / signal broadcast by one of the first UE and the second UE. For example, one of the devices may send a discovery signal or a communication signal by broadcasting an advertising signal (e.g., a physical random access channel (PRACH) signal) to nearby devices. Another device may receive or otherwise detect the discovery / communication signal, and the devices may establish a SL connection in response to the discovery / communication signal.

[0113] The first UE can establish a SL connection based on the resources allocated by the core network. For example, as part of establishing the SL connection, the core network can allocate certain resources (e.g., certain frequency bands or frequency ranges, time slot scheduling, etc.) to the device for operating / managing / maintaining / establishing the SL connection. The first UE can establish a SL connection between the first UE and the second UE based on the allocated resources. For example, the core network can allocate resources in an unlicensed band, allocate resources across multiple bands (e.g., for carrier aggregation), etc. The first device can establish a SL connection based on the allocated resources. Continuing with the above example, the first device can establish the SL connection as an unlicensed SL connection (e.g., SL-U connection) and / or a carrier aggregation SL connection (e.g., SL-CA connection) based on the allocated resources from the core network.

[0114] In step 604, the first UE may determine to operate in carrier aggregation mode. In some embodiments, the first UE may determine to operate in carrier aggregation mode to communicate via a SL connection. The first UE may determine to operate in carrier aggregation mode based on or according to resources allocated by the network. As described above, as part of establishing a SL connection, the core network may allocate certain resources to the SL connection across multiple frequency bands, such as certain resources in an unlicensed frequency band. The first device may determine to operate in carrier aggregation mode based on the resources allocated by the core network. For example, where the core network allocates resources across multiple frequency bands, the first device may determine to operate in carrier aggregation mode (e.g., to aggregate multiple channels across different frequency bands for the SL connection).

[0115] In step 606, the first UE may determine parameters. In some embodiments, the first UE may determine a set of predefined parameters for operating in carrier aggregation mode. The first UE may determine the set of predefined parameters in response to determining to operate in carrier aggregation mode. In some embodiments, the first UE may determine the set of predefined parameters based on resources allocated by the core network. The set of predefined parameters may include a selected SCS value (e.g., from a plurality of subcarrier spacing (SCS) values). In some embodiments, the first UE may determine, identify, or otherwise select corresponding parameters (e.g., resource block size, maximum transmission bandwidth, minimum guard band, etc.) based on or according to the selected SCS value. In some embodiments, the first UE may determine, identify, or otherwise select parameters for operating a SL connection in carrier aggregation mode based on, according to, and / or using the information included in Tables 1 to 13.

[0116] In step 608, the first UE may send an indication. In some embodiments, the first UE may transmit, send, convey, or otherwise provide an indication to the second UE. The first UE may provide an indication to the second UE to indicate that the second UE is to operate a SL connection in carrier aggregation mode. In some embodiments, the first UE may provide an indication to the second UE via a SL connection. In some embodiments, the first UE may provide an indication to the second UE via out-of-band signaling (e.g., via Bluetooth signaling, near field communication signaling, local area network (LAN) signaling, or any other non-SL signaling). The first UE may provide an indication in response to determining to operate in carrier aggregation mode, in response to determining parameters, etc.

[0117] In step 610, the second UE may determine to operate in carrier aggregation mode. The second UE may determine to operate in carrier aggregation mode based on or according to an indication (e.g., sent in step 608). For example, the second UE may receive an indication from the first UE, wherein the indication indicates operation in carrier aggregation mode, and the second UE may determine to operate in carrier aggregation mode according to the indication. In some embodiments, the second UE may determine to operate in carrier aggregation mode in a manner similar to the first UE. For example, the second UE may determine to operate in carrier aggregation mode based on resources allocated for the SL connection (e.g., the resources may be notified to the second UE by the core network, may be identified in an indication received from the first UE, etc.).

[0118] In step 612, the second UE may determine parameters. In some embodiments, the second UE may determine parameters (e.g., predefined parameters) for operating the SL connection. Similar to determining to operate in carrier aggregation mode, the second UE may determine the parameters based on information included in the indication (e.g., the parameters themselves, and information that the second UE can use to independently derive / determine the parameters, etc.). In step 614, the UE may operate the SL connection. In some embodiments, the first UE and the second UE may operate the SL connection according to the parameters determined in steps 606 and 612. The first UE and the second UE may operate the SL according to these parameters by controlling the following items for signaling on the SL connection between the first UE and the second UE: signaling / transmitting or receiving power; transmission bandwidth; guard band; input level; adjacent channel selectivity and parameters; in-band / out-of-band blocking parameters; spurious response parameters; and / or wideband intermodulation parameters. In other words, the UE may operate the SL connection, for example, by sending or receiving SL signals using carrier aggregation according to predetermined / predefined parameters.

[0119] Now that some illustrative embodiments have been described, it is apparent that the foregoing, which has been presented by way of example, is illustrative and not restrictive. Specifically, although many of the examples presented herein relate to specific combinations of method actions or system elements, these actions and these elements may be combined in other ways to achieve the same purpose. The actions, elements, and features discussed in conjunction with one embodiment are not intended to be excluded from similar roles in other embodiments.

[0120] The hardware and multiple data processing components for implementing the various processes, operations, illustrative logic, logic blocks, modules and circuits described in conjunction with the multiple embodiments disclosed herein can be implemented or executed using the following components designed to perform the functions described herein: a general-purpose single-chip processor or a general-purpose multi-chip processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof. A general-purpose processor may be a microprocessor, or may be any conventional processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration. In some embodiments, specific processes and methods may be performed by circuits dedicated to a given function. A memory (e.g., a memory, a memory unit, a storage device, etc.) may include one or more devices (e.g., RAM, ROM, flash memory, hard disk storage, etc.) for storing data and / or computer code for completing or facilitating the various processes, various layers and various modules described in this disclosure. The memory may be or may include volatile memory or non-volatile memory, and may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. According to an exemplary embodiment, the memory is communicatively connected to the processor via the processing circuit and includes computer code for executing (e.g., by the processing circuit and / or the processor) one or more processes described herein.

[0121] The present disclosure contemplates methods, systems, and program products on any machine-readable medium for completing various operations. The various embodiments of the present disclosure may be implemented using existing computer processors, or by a dedicated computer processor for a suitable system combined for this or other purposes, or by a hard-wired system. The various embodiments within the scope of the present disclosure include program products, which include machine-readable media for carrying or storing machine-executable instructions or data structures thereon. Such machine-readable media may be any available medium that can be accessed by a general-purpose computer or a special-purpose computer or other machine with a processor. As an example, such machine-readable media may include RAM, ROM, EPROM, EEPROM, or other optical disk storage, disk storage, or other magnetic storage device, or any other medium that can be used to carry or store program codes in the form of desired machine-executable instructions or data structures, and can be accessed by a general-purpose computer or a special-purpose computer or other machine with a processor. The above combinations are also included in the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data that cause a general-purpose computer, a special-purpose computer, or a special-purpose processing machine to perform a specific function or group of functions.

[0122] The words and terms used herein are for descriptive purposes and should not be considered limiting. The use of "comprising," "including," "having," "containing," "involving," "characterized by," "characterized by," and variations thereof herein is meant to encompass the items listed thereafter, their equivalents and additional items, and to include alternative embodiments consisting exclusively of the items listed thereafter. In one embodiment, the systems and methods described herein include one, each combination of more than one of the described elements, acts, or components, or all of them.

[0123] Any reference to an embodiment or element or action of the system and method mentioned in the singular herein may also encompass an embodiment including a plurality of these elements, and any plural reference to any embodiment or element or action herein may also encompass an embodiment including only a single element. References in the singular or plural form are not intended to limit the currently disclosed systems or methods, their components, actions or elements to a single or multiple configurations. References to any action or element based on any information, action or element may include an embodiment in which the action or element is based at least in part on any information, action or element.

[0124] Any embodiment disclosed herein may be combined with any other embodiment or example, and references to "an embodiment," "some embodiments," "an embodiment," etc. are not necessarily mutually exclusive, but are intended to indicate that a particular feature, structure, or characteristic described in conjunction with the embodiment may be included in at least one embodiment or example. These terms as used herein do not necessarily all refer to the same embodiment. Any embodiment may be combined, inclusively or exclusively, with any other embodiment in any manner consistent with the various aspects and embodiments disclosed herein.

[0125] Where technical features in the drawings, detailed description or any claims are followed by reference numerals, these reference numerals have been included to increase the intelligibility of the drawings, detailed description and claims. Therefore, these reference numerals or their absence do not have any limiting effect on the scope of any claim element.

[0126] Without departing from the features of the present invention, the systems and methods described herein may be implemented in other specific forms. Unless otherwise expressly noted, references to "approximately," "about," "substantially," or other degree terms include changes of plus or minus 10% (+ / -10%) from a given measurement, unit, or range. The coupled elements may be electrically coupled, mechanically coupled, or physically coupled to each other directly or through intermediate elements. Therefore, the scope of the systems and methods described herein is indicated by the appended claims rather than the preceding description, and changes within the meaning and scope of the equivalents of the claims are included therein.

[0127] The term "coupled" and variations thereof include two members being directly or indirectly connected to one another. Such connection may be constant (e.g., permanent or fixed) or movable (e.g., removable or releasable). Such connection may be achieved by the two members being directly coupled to one another or coupled to one another, by the two members being coupled to one another using a separate intermediate member, and by any additional intermediate member being coupled to one another, or by the two members being coupled to one another using an intermediate member that is integrally formed as a single, unitary body with one of the two members. If "coupled" or variations thereof are modified by additional terms (e.g., directly coupled), the general definition of "coupled" provided above is modified by the plain language meaning of the additional terms (e.g., "directly coupled" means that the two members are connected without any separate intermediate member), resulting in a narrower definition than the general definition of "coupled" provided above. Such coupling may be mechanical, electrical, or fluidic.

[0128] References to "or" may be interpreted as inclusive, such that any term described using "or" may mean single, more than one, and any one of all described terms. References to "at least one of 'A' and 'B'" may include only 'A', only 'B', and both 'A' and 'B'. Such references used in conjunction with "including" or other public terms may include additional items.

[0129] Without departing substantially from the teachings and advantages of the subject matter disclosed herein, modifications may be made to the elements and actions described, such as changes in the size, dimensions, structure, shape and proportion of the various elements, parameter values, mounting arrangement structures, use of materials, colors, orientations. For example, an element shown as being integrally formed may be composed of multiple parts or elements, the positions of these elements may be reversed or otherwise changed, and the nature or number or position of discrete elements may be altered or varied. Other substitutions, modifications, changes and omissions may also be made to the design, operating conditions and arrangements of the disclosed elements and operations without departing from the scope of the present disclosure.

[0130] References herein to the positions of elements (e.g., "top," "bottom," "above," "below") are only used to describe the orientation of the various elements in the drawings. According to other example embodiments, the orientation of the various elements may be different, and such variations are intended to be encompassed by the present disclosure.

Claims

1. A method comprising: The first user equipment UE establishes a sidelink connection with the second UE; determining, by the first UE, to operate in a carrier aggregation mode to communicate via the sidelink connection; as well as The sidelink connection is operated according to a set of predefined parameters per component carrier CC by the first UE in response to determining to operate in the carrier aggregation mode.

2. The method according to claim 1, wherein: The set of predefined parameters includes a selected SCS value selected from a plurality of subcarrier spacing SCS values.

3. The method according to claim 2, wherein: Operating the sidelink connection includes modifying a size of a resource block (RB) size according to the SCS value.

4. The method according to claim 2, wherein: Operating the sidelink connection includes selecting a maximum transmission bandwidth based on the SCS value.

5. The method according to claim 4, wherein: The maximum transmission bandwidth is selected based on the SCS value and the channel bandwidth corresponding to the sidelink connection.

6. The method according to claim 2, wherein: Operating the sidelink connection includes selecting a minimum guard band based on the SCS value.

7. The method according to claim 6, wherein: The minimum guard band is selected based on the SCS value and the channel bandwidth corresponding to the sidelink connection.

8. The method according to claim 1, wherein: The set of predefined parameters includes a reference measurement channel configuration corresponding to an adjacent channel selective ACS configuration.

9. The method according to claim 1, wherein: The first UE includes at least one of a first UE of a first pedestrian or a first UE of a first vehicle, and the second UE includes at least one of a second UE of a second pedestrian or a second UE of a second vehicle.

10. The method according to claim 1, further comprising: A signal indicating operation in the carrier aggregation mode is sent by the first UE to the second UE.

11. A first user equipment UE, comprising: Wireless transceiver; as well as One or more processors configured to: establishing a sidelink connection with a second UE via the wireless transceiver; determining to operate in a carrier aggregation mode to communicate via the sidelink connection; as well as In response to determining to operate in the carrier aggregation mode, the sidelink connection is operated according to a set of predefined parameters for each component carrier CC.

12. The first UE according to claim 11, wherein: The set of predefined parameters includes a selected SCS value selected from a plurality of subcarrier spacing SCS values.

13. The first UE according to claim 12, wherein: Operating the sidelink connection includes modifying a size of a resource block (RB) size according to the SCS value.

14. The first UE according to claim 12, wherein: Operating the sidelink connection includes selecting a maximum transmission bandwidth based on the SCS value.

15. The first UE according to claim 14, wherein: The maximum transmission bandwidth is selected based on the SCS value and the channel bandwidth corresponding to the sidelink connection.

16. The first UE according to claim 12, wherein: Operating the sidelink connection includes selecting a minimum guard band based on the SCS value.

17. The first UE according to claim 16, wherein: The minimum guard band is selected based on the SCS value and the channel bandwidth corresponding to the sidelink connection.

18. The first UE according to claim 11, wherein: The set of predefined parameters includes a reference measurement channel configuration corresponding to an adjacent channel selective ACS configuration.

19. The first UE according to claim 11, wherein: The first UE includes at least one of a first UE of a first pedestrian or a first UE of a first vehicle, and the second UE includes at least one of a second UE of a second pedestrian or a second UE of a second vehicle.

20. A first user equipment UE, comprising: Wireless transceiver; as well as One or more processors configured to: establishing a sidelink connection with a second UE via the wireless transceiver; receiving an indication from the second UE to operate in a carrier aggregation mode to communicate via the sidelink connection; as well as In response to determining to operate in the carrier aggregation mode, the sidelink connection is operated according to a set of predefined parameters for each component carrier CC.

Images