Waveforms for synchronization and beam management of secondary cells

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may obtain synchronization with a primary cell (PCell) of a wireless network. The UE may receive an indication to activate a secondary cell (SCell) of the wireless network. In some embodiments, the UE may receive a reference signal (RS) for the SCell, the reception of the RS for the SCell based at least in part on obtaining synchronization with the PCell, the reception comprising one or more of using a reduced list of candidate beams for initial beam search, or using a reduced time domain range for receiving the RS for the SCell. The UE may communicate via the SCell based at least in part on synchronization with the SCell and using a pair of beams obtained using the RS of the SCell. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. non-provisional patent application No. 18 / 165,048, filed on February 6, 2023, entitled “WAVEFORM FOR SYNCHRONIZATION AND BEAM MANAGEMENT OF A SECONDARY CELL,” which is hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatuses using waveforms for synchronization and beam management of secondary cells. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). 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, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communication for wireless communication devices, such as user equipment (UE) or multiple UEs. The UE may communicate with the network node via downlink and uplink communications. A "downlink" (or "DL") refers to the communication link from the network node to the UE, and an "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via a local link (e.g., a sidelink (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, regional, and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and better integrating with other open standards by using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink and CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink; as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] In order that the above-mentioned features of the present disclosure may be fully understood, a more particular description of the invention briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). It should be noted, however, that the drawings illustrate only certain typical aspects of the present disclosure and are not therefore to be considered limiting of its scope, as the description may admit to other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0008] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0009] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0010] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0011] Figure 4 is a diagram illustrating an example of dual connectivity according to the present disclosure.

[0012] Figure 5 is a diagram illustrating an example of a synchronization signal (SS) hierarchy structure according to the present disclosure.

[0013] Figure 6 is a diagram illustrating an example of a beam management process according to the present disclosure.

[0014] Figure 7 is a diagram illustrating an example of performing communication using a millimeter wave repeater according to the present disclosure.

[0015] Figure 8 is a diagram illustrating an example of communication using a primary cell (PCell) and a secondary cell (SCell) according to the present disclosure.

[0016] Figure 9 is a diagram of an example associated with using a waveform for synchronization and beam management of a secondary cell according to the present disclosure.

[0017] Figure 10 is a diagram of an example associated with a waveform for synchronization and beam management of a secondary cell according to the present disclosure.

[0018] Figure 11 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0019] Figure 12 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.

[0020] Figure 13 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0021] Figure 14 is a diagram of an example apparatus for wireless communications according to the present disclosure. Summary of the Invention

[0022] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include obtaining synchronization with a primary cell (PCell) of a wireless network. The method may include receiving an indication to activate a secondary cell (SCell) of the wireless network. The method may include receiving a reference signal (RS) of the SCell, the reception of the RS of the SCell being based at least in part on obtaining synchronization with the PCell, the reception comprising one or more of the following operations: using a reduced candidate beam list for initial beam search relative to a candidate beam list for initial beam search that is not synchronized with the PCell, or using a reduced time domain range for receiving the RS of the SCell. The method may include obtaining synchronization with the SCell based at least in part on the RS of the SCell. The method may include identifying a beam pair for communicating via the SCell based at least in part on the RS of the SCell. The method may include communicating via the SCell based at least in part on synchronization with the SCell and using the beam pair.

[0023] Some aspects described herein relate to a method for wireless communication performed by a network node. The method may include sending a synchronization RS of a PCell of a wireless network to a UE, the RS of a primary cell being configured to support synchronization with the PCell. The method may include sending an indication to activate an SCell of the wireless network. The method may include sending an RS of the SCell, the RS of the SCell being associated with one or more of the following: a candidate beam list for initial beam search that is reduced relative to a candidate beam list for initial beam search that is not synchronized with the PCell, or a reduced time domain range for sending the RS of the SCell. The method may include communicating via the secondary cell based at least in part on synchronization with the secondary cell.

[0024] Some aspects described herein relate to a UE for wireless communication. The UE may include: a memory; and one or more processors coupled to the memory. The one or more processors may be configured to obtain synchronization with a PCell of a wireless network. The one or more processors may be configured to receive an indication to activate an SCell of the wireless network. The one or more processors may be configured to receive a RS for the SCell, the receiving of the RS for the SCell being based at least in part on obtaining synchronization with the PCell, the receiving comprising one or more of: using a reduced candidate beam list for initial beam search relative to a candidate beam list for initial beam search not synchronized with the PCell, or using a reduced time domain range for receiving the RS for the SCell. The one or more processors may be configured to obtain synchronization with the SCell based at least in part on the RS for the SCell. The one or more processors may be configured to identify a beam pair for communication via the SCell based at least in part on the RS for the SCell. The one or more processors may be configured to communicate via the SCell based at least in part on the synchronization with the SCell and using the beam pair.

[0025] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send a synchronization RS of a PCell of a wireless network to a UE, the RS of a primary cell being configured to support synchronization with the PCell. The one or more processors may be configured to send an indication of activating an SCell of the wireless network. The one or more processors may be configured to send the RS of the SCell, the RS of the SCell being associated with one or more of the following: a candidate beam list for initial beam search that is reduced relative to a candidate beam list for initial beam search that is not synchronized with the PCell, or a reduced time domain range for sending the RS of the SCell. The one or more processors may be configured to communicate via the secondary cell based at least in part on synchronization with the secondary cell.

[0026] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions may cause the UE to acquire synchronization with a PCell of a wireless network. When executed by the one or more processors of the UE, the set of instructions may cause the UE to receive an indication to activate an SCell of the wireless network. When executed by the one or more processors of the UE, the set of instructions may cause the UE to receive a RS for the SCell, where the reception of the RS for the SCell is based at least in part on acquiring synchronization with the PCell, the reception comprising one or more of the following operations: using a reduced candidate beam list for initial beam search relative to a candidate beam list for initial beam search that is not synchronized with the PCell, or using a reduced time domain range for receiving the RS for the SCell. When executed by the one or more processors of the UE, the set of instructions may cause the UE to acquire synchronization with the SCell based at least in part on the RS for the SCell. The instruction set, when executed by one or more processors of the UE, may cause the UE to identify a beam pair for communicating via the SCell based at least in part on the RS of the SCell. The instruction set, when executed by one or more processors of the UE, may cause the UE to communicate via the SCell based at least in part on synchronization with the SCell and using the beam pair.

[0027] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. When executed by one or more processors of the network node, the instruction set may cause the network node to send a synchronization RS for a PCell of a wireless network to a UE, the RS for a primary cell being configured to support synchronization with the PCell. When executed by one or more processors of the network node, the instruction set may cause the network node to send an indication to activate an SCell of the wireless network. When executed by one or more processors of the network node, the instruction set may cause the network node to send an RS for the SCell, the RS for the SCell being associated with one or more of: a reduced candidate beam list for initial beam search relative to a candidate beam list for initial beam search that is not synchronized with the PCell, or a reduced time domain range for transmitting the RS for the SCell. When executed by one or more processors of the network node, the instruction set may cause the network node to communicate via the secondary cell based at least in part on synchronization with the secondary cell.

[0028] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for obtaining synchronization with a PCell of a wireless network. The apparatus may include means for receiving an indication to activate an SCell of the wireless network. The apparatus may include means for receiving a RS for the SCell, wherein the reception of the RS for the SCell is based at least in part on obtaining synchronization with the PCell, the means including one or more of: means for using a reduced candidate beam list for initial beam search relative to a candidate beam list for initial beam search not synchronized with the PCell, or means for using a reduced time domain range for receiving the RS for the SCell. The apparatus may include means for obtaining synchronization with the SCell based at least in part on the RS for the SCell. The apparatus may include means for identifying a beam pair for communicating via the SCell based at least in part on the RS for the SCell. The apparatus may include means for communicating via the SCell based at least in part on the synchronization with the SCell and using the beam pair.

[0029] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for sending a synchronization RS of a PCell of a wireless network to a UE, the RS of a primary cell being configured to support synchronization with the PCell. The apparatus may include a component for sending an indication of activating an SCell of the wireless network. The apparatus may include a component for sending the RS of the SCell, the RS of the SCell being associated with one or more of the following: a candidate beam list for initial beam search that is reduced relative to a candidate beam list for initial beam search that is not synchronized with the PCell, or a reduced time domain range for sending the RS of the SCell. The apparatus may include a component for communicating via the secondary cell based at least in part on synchronization with the secondary cell.

[0030] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices, and / or processing systems as fully described herein with reference to and as illustrated in the accompanying drawings and description.

[0031] The features and technical advantages of the examples according to the present disclosure have been outlined quite broadly above so that the detailed description that follows may be better understood. Additional features and advantages will be described below. The concepts and specific examples disclosed may be readily used as a basis for modifying or designing other structures for achieving the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0032] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporated into the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and compositions. DETAILED DESCRIPTION

[0033] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout the present disclosure. Rather, these aspects are provided so that the present disclosure will be thorough and complete, and will fully convey the scope of protection of the present disclosure to those skilled in the art. It will be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or practice method. Furthermore, the scope of the present disclosure is intended to cover such apparatus or methods implemented using other structures, functionality, or structure and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present claims.

[0034] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0035] Although various aspects may be described herein using terminology generally associated with 5G or New Radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G (e.g., 6G) RATs.

[0036] Figure 1 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (illustrated as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (illustrated as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, meaning that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0037] In some examples, network node 110 is or includes a network node (such as an RU) that communicates with UE 120 via a radio access link. In some examples, network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link. In some examples, network node 110 (such as a converged network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. Network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, an RU, a CU, a mobility element of a network, a core network node, a network element, network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 using any suitable transport network via various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks.

[0038] In some examples, network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​network node 110 and / or a network node subsystem serving that coverage area, depending on the context in which the term is used. Network node 110 may provide communication coverage for a macrocell, a picocell, a femtocell, and / or another type of cell. A macrocell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs 120 with service subscriptions. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 associated with the femtocell (e.g., UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macrocell may be referred to as a macro network node. A network node 110 for a picocell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0039] In some aspects, the term "base station" or "network node" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions, such as those described herein in conjunction with network node 110. In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not another base station function. In this way, a single device may include more than one base station.

[0040] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110 d (e.g., a relay network node) may communicate with a network node 110 a (e.g., a macro network node) and a UE 120 d to facilitate communications between the network node 110 a and the UE 120 d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0041] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0042] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0043] UEs 120 may be dispersed throughout wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0044] Some UEs 120 may be considered machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that can communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. The UE 120 may be included within a housing that houses components of the UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0045] Generally speaking, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. A RAT may be referred to as a radio technology, air interface, etc. A frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0046] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0047] Devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0048] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz–24.25 GHz). The frequency bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation to more than 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz–71 GHz), FR4 (52.6 GHz–114.25 GHz), and FR5 (114.25 GHz–300 GHz). Each of these higher frequency bands falls within the EHF band.

[0049] With the above examples in mind, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a, FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0050] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may acquire synchronization with a primary cell (PCell) of a wireless network; receive an indication to activate a secondary cell (SCell) of the wireless network; receive a reference signal (RS) for the SCell, the reception of the RS for the SCell being based at least in part on acquiring synchronization with the PCell, the reception comprising one or more of: using a reduced candidate beam list for initial beam search relative to a candidate beam list for initial beam search without synchronization with the PCell; or using a reduced time domain range for receiving the RS for the SCell; acquiring synchronization with the SCell based at least in part on the RS for the SCell; identifying a beam pair for communicating via the SCell based at least in part on the RS for the SCell; and communicating via the SCell based at least in part on synchronization with the SCell and using the beam pair. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0051] In some aspects, the network node 110 may include a communication manager 150. As described in greater detail elsewhere herein, the communication manager 150 may: transmit a synchronization RS for a PCell of a wireless network to a UE, the RS for a primary cell being configured to support synchronization with the PCell; transmit an indication to activate an SCell of the wireless network; transmit an RS for the SCell, the RS for the SCell being associated with one or more of: a reduced candidate beam list for initial beam search relative to a candidate beam list for initial beam search that is not synchronized with the PCell, or a reduced time domain range for transmitting the RS for the SCell; and communicate via the secondary cell based at least in part on synchronization with the secondary cell. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0052] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0053] Figure 22 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ≥ 1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ≥ 1). The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 232. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components, such as one or more CUs or one or more DUs, that facilitate direct communication with the UE 120.

[0054] At network node 110, transmit processor 220 may receive data intended for UE 120 (or a set of UEs 120) from data source 212. Transmit processor 220 may select one or more modulation and coding schemes (MCS) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 may process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. Transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input, multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, as applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a through 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or frequency upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit the set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a through 234t).

[0055] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use the demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols, if applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine, among other things, a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter. In some examples, one or more components of the UE 120 may be included in a housing 284.

[0056] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0057] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0058] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI) from the controller / processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, if applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to execute the instructions herein (eg, reference Figures 9 to 14 ) any aspects of any of the methods described.

[0059] At network node 110, uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., a demodulator component (shown as DEMOD) of modem 232), detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include a communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, modem 232 of network node 110 may include a modulator and a demodulator. In some examples, network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute the instructions herein (e.g., reference 242). Figures 9 to 14 ) any aspects of any of the methods described.

[0060] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or the like may perform one or more techniques associated with using waveforms for synchronization and beam management of secondary cells as described in more detail elsewhere herein. Figure 2 Any other component of the may perform or direct e.g. Figure 11 Process 1100, Figure 12 1200 and / or other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 11 Process 1100, Figure 12 The process 1200 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, among other things.

[0061] In some aspects, the UE includes components for obtaining synchronization with a PCell of a wireless network; components for receiving an indication of activating a SCell of the wireless network; components for receiving the RS of the SCell, wherein the reception of the RS of the SCell is based at least in part on obtaining synchronization with the PCell, the components including one or more of the following: components for using a reduced list of candidate beams for initial beam search relative to a list of candidate beams for initial beam search that is not synchronized with the PCell; or components for using a reduced time domain range for receiving the RS of the SCell; components for obtaining synchronization with the SCell based at least in part on the RS of the SCell; components for identifying a beam pair for communicating via the SCell based at least in part on the RS of the SCell; and / or components for communicating via the SCell based at least in part on synchronization with the SCell and using the beam pair. Means for the UE to perform the operations described herein may include, for example, one or more of the communications manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0062] In some aspects, the network node includes: means for transmitting a synchronization RS for a PCell of a wireless network to a UE, the RS for a primary cell being configured to support synchronization with the PCell; means for transmitting an indication of activating an SCell of the wireless network; means for transmitting the RS for the SCell, the RS for the SCell being associated with one or more of: a reduced candidate beam list for initial beam search relative to a candidate beam list for initial beam search without synchronization with the PCell, or a reduced time domain range for transmitting the RS for the SCell; and / or means for communicating via the secondary cell based at least in part on synchronization with the secondary cell. Means for the network node to perform the operations described herein may include, for example, one or more of the following: the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0063] Although Figure 2 The blocks in FIG. 2 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0064] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0065] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of the network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated architecture or a decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also known as an independent base station or a monolithic base station) or a decomposed base station. A "network entity" or a "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs or a combination thereof).

[0066] A converged base station (e.g., a converged network node) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) can be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually spread across one or more other network nodes. The DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among others.

[0067] Base station type operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate scaling of the communication system by separating base station functionality into one or more units that can be deployed separately. A disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Each unit of the disaggregated base station may be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0068] Figure 3 FIG2 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as a near-RT RIC 325 via an E2 link, a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0069] Each of the units (including the CU 310, DU 330, RU 340) and the near-RT RIC 325, the non-RT RIC 315, and the SMO framework 305 may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit, may be configured to communicate with one or more of the other units via the transmission medium. In some examples, each of the units may include a wired interface configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium, and a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) configured to receive signals or transmit signals to one or more of the other units via a wireless transmission medium, or both.

[0070] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among others. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0071] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers, at least in part according to a functional split (such as that defined by 3GPP). In some aspects, the one or more higher PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, and the like. In some aspects, the DU 330 may also host one or more lower PHY layers, such as those implemented by one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0072] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions based on functional split (e.g., functional split defined by 3GPP) (such as lower layer functional split), such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering. In such an architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0073] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements can include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some implementations, the SMO framework 305 can communicate with hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0074] The non-RT RIC 315 can be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or in communication with the near-RT RIC 325 (e.g., via an A1 interface). The near-RT RIC 325 can be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources through data collection and actions via an interface (e.g., via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

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

[0076] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0077] Figure 4 is a diagram illustrating an example 400 of dual connectivity according to the present disclosure. Figure 4 The example shown is for Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA)-NR Dual Connectivity (ENDC) mode. In ENDC mode, the UE 120 communicates using the LTE RAT on a Master Cell Group (MCG), and the UE 120 communicates using the NR RAT on an SCell Group (SCG). However, the aspects described herein may be applicable to ENDC mode (e.g., where the MCG is associated with the LTE RAT and the SCG is associated with the NR RAT), NR-E-UTRA Dual Connectivity (NEDC) mode (e.g., where the MCG is associated with the NR RAT and the SCG is associated with the LTE RAT), NR Dual Connectivity (NRDC) mode (e.g., where the MCG is associated with the NR RAT and the SCG is also associated with the NR RAT), or another dual connectivity mode (e.g., where the MCG is associated with a first RAT and the SCG is associated with one of the first RAT or a second RAT). ENDC mode is sometimes referred to as NR or 5G Non-Standalone (NSA) mode. Thus, as used herein, “dual connectivity mode” may refer to an ENDC mode, a NEDC mode, an NRDC mode, and / or another type of dual connectivity mode.

[0078] like Figure 4As shown, UE 120 can communicate with both an eNB (e.g., 4G network node 110) and a gNB (e.g., 5G network node 110), and the eNB and gNB can communicate (e.g., directly or indirectly) with a 4G / LTE core network (shown as an evolved packet core (EPC) including a mobility management entity (MME), a packet data network gateway (PGW), a serving gateway (SGW), and / or other devices). Figure 4 In the present invention, the PGW and SGW are collectively referred to as P / SGW. In some aspects, the eNB and gNB can be co-located at the same network node 110. In some aspects, the eNB and gNB can be included in different network nodes 110 (e.g., they may not be co-located at the same place).

[0079] like Figure 4 , further shown in FIG, 5G NSA mode, in some aspects, a wireless network permitting operation in 5G NSA mode may permit such operation using an MCG for a first RAT (e.g., an LTE RAT or a 4G RAT) and an SCG for a second RAT (e.g., an NR RAT or a 5G RAT). In this case, the UE 120 may communicate with the eNB via the MCG and may communicate with the gNB via the SCG. In some aspects, the MCG may anchor the network connection between the UE 120 and the 4G / LTE core network (e.g., for mobility, coverage, and / or control plane information), and the SCG may be added as an additional carrier to increase throughput (e.g., for data traffic and / or user plane information). In some aspects, the gNB and the eNB may not communicate user plane information between each other. In some aspects, a UE 120 operating in dual connectivity mode may be concurrently connected to an LTE network node 110 (e.g., an eNB) and an NR network node 110 (e.g., a gNB) (e.g., in the case of ENDC or NEDC), or may be concurrently connected to one or more network nodes 110 using the same RAT (e.g., in the case of NRDC). In some aspects, an MCG may be associated with a first frequency band (e.g., a sub-6 GHz band and / or an FR1 band), and an SCG may be associated with a second frequency band (e.g., a mmWave band and / or an FR2 band).

[0080] The UE 120 may communicate via the MCG and SCG using one or more radio bearers (e.g., data radio bearers (DRBs) and / or signaling radio bearers (SRBs)). For example, the UE 120 may send or receive data via the MCG and / or SCG using one or more DRBs. Similarly, the UE 120 may send or receive control information (e.g., RRC information and / or measurement reports) using one or more SRBs. In some aspects, a radio bearer may be dedicated to a particular cell group (e.g., a radio bearer may be an MCG bearer or an SCG bearer). In some aspects, a radio bearer may be a split radio bearer. A split radio bearer may be split in the uplink and / or downlink. For example, a DRB may be split on the downlink (e.g., the UE 120 may receive downlink information for the MCG or SCG in the DRB) but not split on the uplink (e.g., the uplink may not be split from the primary path to the MCG or SCG such that the UE 120 transmits in the uplink only on the primary path). In some aspects, DRBs can be split from the primary path to the MCG or SCG on the uplink. The DRBs that are split in the uplink can use the primary path to send data until the size of the uplink transmit buffer meets the uplink data split threshold. If the uplink transmit buffer meets the uplink data split threshold, the UE 120 can use the DRBs to send data to the MCG or SCG.

[0081] In some networks, the MCG and the SCG may be associated with different frequency ranges (FRs). For example, the MCG may be associated with FR1 and / or FR2, and the SCG may be associated with FR3, FR4a, FR4 and / or FR5, and so on. The MCG may be associated with one or more bandwidths on a carrier frequency with relatively high coverage and relatively low propagation loss. The SCG may be associated with one or more bandwidths on a carrier frequency with relatively low coverage and relatively high propagation loss. Additionally or alternatively, the bandwidth of the carrier of the MCG or the sum of the bandwidths of the MCG may have a size that is smaller than the bandwidth of the carrier of the SCG or the sum of the bandwidths of the SCG. In this way, the SCG may have a higher throughput capacity than the MCG, and the MCG may have a higher reliability than the SCG.

[0082] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0083] Figure 5 5 is a diagram illustrating an example 500 of a synchronization signal (SS) hierarchy according to the present disclosure. Figure 5As shown in , the SS hierarchy may include an SS burst set 505, which may include multiple SS bursts 510, shown as SS Burst 0 through SS Burst N-1, where N is the maximum number of repetitions of the SS burst 510 that may be sent by one or more network nodes. As further shown in the figure, each SS burst 510 may include one or more SS blocks (SSBs) 515 (shown as SSB 0 through SSB M-1, where M is the maximum number of SSBs 515 that may be carried by the SS burst 510). In some aspects, different SSBs 515 may be beamformed in different manners (e.g., transmitted using different beams) and may be used for cell search, cell acquisition, beam management, and / or beam selection (e.g., as part of an initial network access procedure). The SS burst set 505 may be sent by a wireless node (e.g., network node 110) periodically (such as every X milliseconds), as shown in . Figure 5 In some aspects, the SS burst set 505 may have Figure 5 In some cases, the SS burst set 505 or SS burst 510 may be referred to as a discovery reference signal (DRS) transmission window or an SSB measurement time configuration (SMTC) window.

[0084] In some aspects, an SSB 515 may include resources that carry a PSS 520, an SSS 525, and / or a physical broadcast channel (PBCH) 530. In some aspects, multiple SSBs 515 are included in an SS burst 510 (e.g., utilizing transmission on different beams), and the PSS 520, SSS 525, and / or PBCH 530 may be the same across each SSB 515 of an SS burst 510. In some aspects, a single SSB 515 may be included in an SS burst 510. In some aspects, an SSB 515 may be at least four symbols (e.g., OFDM symbols) in length, with each symbol carrying one or more of: a PSS 520 (e.g., occupying one symbol), an SSS 525 (e.g., occupying one symbol), and / or a PBCH 530 (e.g., occupying two symbols). In some aspects, an SSB 515 may be referred to as an SS / PBCH block.

[0085] In some aspects, the symbols of SSB 515 are continuous, such as Figure 5 . In some aspects, the symbols of the SSB 515 are non-contiguous. Similarly, in some aspects, one or more SSBs 515 of the SS burst 510 may be transmitted in contiguous radio resources (e.g., consecutive symbols) during one or more time slots. Additionally or alternatively, one or more SSBs 515 of the SS burst 510 may be transmitted in non-contiguous radio resources.

[0086] In some aspects, the SS burst 510 may have a burst periodicity, and the SSB 515 of the SS burst 510 may be transmitted by a wireless node (e.g., the network node 110) according to the burst periodicity. In this case, the SSB 515 may repeat during each SS burst 510. In some aspects, the SS burst set 505 may have a burst set periodicity, whereby the SS bursts 510 in the SS burst set 505 are transmitted by the wireless node according to a fixed burst set periodicity. In other words, the SS burst 510 may repeat during each SS burst set 505.

[0087] In some aspects, the SSB 515 may include an SSB index, which may correspond to a beam used to carry the SSB 515. The UE 120 may monitor and / or measure the SSB 515 using different receive (Rx) beams during an initial network access procedure and / or a cell search procedure, etc. Based at least in part on the monitoring and / or measurement, the UE 120 may indicate one or more SSBs 515 having the best signal parameters (e.g., RSRP parameters) to the network node 110 (e.g., directly or via one or more other network nodes). The network node 110 and the UE 120 may use the indicated one or more SSBs 515 to select one or more beams to be used for communication between the network node 110 and the UE 120 (e.g., for a random access channel (RACH) procedure). Additionally or alternatively, the UE 120 may use the SSB 515 and / or the SSB index to determine the cell timing of a cell (e.g., a serving cell) via which the SSB 515 is received.

[0088] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0089] Figure 6 600, 610, and 620 are diagrams illustrating examples of beam management processes according to the present disclosure. Figure 6 As shown, examples 600, 610, and 620 include UE 120 communicating with network node 110 in a wireless network (e.g., wireless network 100). Figure 6 The devices shown are provided as examples, and the wireless network may support communication and beam management between other devices (e.g., between UE 120 and network node 110 or TRP, between mobile terminal nodes and control nodes, between IAB child nodes and IAB parent nodes, and / or between scheduled nodes and scheduling nodes). In some aspects, UE 120 and network node 110 may be in a connected state (e.g., an RRC connected state).

[0090] like Figure 6As shown, example 600 may include a network node 110 (e.g., one or more network node devices such as RU, DU, and / or CU, etc.) and a UE 120, the network node communicating with the UE to perform beam management using RS (e.g., channel state information reference signal (CSI-RS) and / or SSB). Example 600 depicts a first beam management process (e.g., P1 beam management). The first beam management process may be referred to as a beam selection process, an initial beam acquisition process, a beam scanning process, a cell search process, and / or a beam search process. As shown in FIG. Figure 6 As shown in example 600, the RS may be configured to be transmitted from the network node 110 to the UE 120. The RS may be configured to be periodic (e.g., using RRC signaling), semi-persistent (e.g., using MAC control element (MAC-CE) signaling), and / or aperiodic (e.g., using downlink control information (DCI)).

[0091] The first beam management process may include the network node 110 performing beam scanning on multiple transmit (Tx) beams. The network node 110 may use each transmit beam used for beam management to transmit an RS. To enable the UE 120 to perform Rx beam scanning, the network node may use a transmit beam to transmit each RS multiple times (e.g., using repetition) within the same RS resource set, so that the UE 120 can sweep the receive beam in multiple transmission instances. For example, if the network node 110 has a set of N transmit beams and the UE 120 has a set of M receive beams, the RS may be transmitted M times on each of the N transmit beams, so that the UE 120 can receive M instances of the RS per transmit beam. In other words, for each transmit beam of the network node 110, the UE 120 may perform beam scanning on the receive beam of the UE 120. Thus, the first beam management procedure may enable UE 120 to measure RSs on different transmit beams using different receive beams to support selection of a network node 110 transmit beam / UE 120 receive beam pair. UE 120 may report the measurements to network node 110 to enable network node 110 to select one or more beam pairs for communication between network node 110 and UE 120. The RSs in example 600 may include CSI-RSs and / or SSBs for beam management in a manner similar to that described above.

[0092] like Figure 6 As shown, example 610 may include network node 110 and UE 120 communicating to perform beam management using RS. Example 610 depicts a second beam management process (e.g., P2 beam management). This second beam management process may be referred to as a beam refinement process, a network node beam refinement process, a TRP beam refinement process, and / or a transmit beam refinement process. Figure 6 As shown in example 610, RSs may be configured to be transmitted from network node 110 to UE 120. The RSs may be configured to be aperiodic (e.g., using DCI). The second beam management procedure may include network node 110 performing beam scanning on one or more transmit beams. The one or more transmit beams may be a subset of all transmit beams associated with network node 110 (e.g., determined at least in part based on measurements reported by UE 120 in conjunction with the first beam management procedure). Network node 110 may transmit RSs using each of the one or more transmit beams used for beam management. UE 120 may measure each RS using a single (e.g., identical) receive beam (e.g., determined at least in part based on measurements performed in conjunction with the first beam management procedure). The second beam management procedure may enable network node 110 to select an optimal transmit beam based at least in part on RS measurements reported by UE 120 (e.g., measured by UE 120 using a single receive beam). The RS in example 610 may include CSI-RS and / or SSB for beam management in a manner similar to that described above.

[0093] like Figure 6 As shown, example 620 depicts a third beam management process (e.g., P3 beam management). The third beam management process may be referred to as a beam refinement process, a UE beam refinement process, and / or a receive beam refinement process. Figure 6 As shown in example 620, one or more RSs may be configured to be transmitted from network node 110 to UE 120. The RSs may be configured to be non-periodic (e.g., using DCI). The third beam management process may include network node 110 transmitting the one or more RSs using a single transmit beam (e.g., determined at least in part based on measurements reported by UE 120 in conjunction with the first beam management process and / or the second beam management process). To enable UE 120 to perform receive beam scanning, the network node may transmit the RS multiple times (e.g., using repetitions) within the same RS resource set using a transmit beam, such that UE 120 may sweep across one or more receive beams in multiple transmission instances. The one or more receive beams may be a subset of all receive beams associated with UE 120 (e.g., determined at least in part based on measurements performed in conjunction with the first beam management process and / or the second beam management process). The third beam management process may enable network node 110 and / or UE 120 to select the best receive beam based at least in part on reported measurement results received from UE 120 (e.g., reported measurement results of RSs of transmit beams received from the UE using the one or more receive beams). The RS in example 620 may include CSI-RS and / or SSBs for beam management in a manner similar to that described above.

[0094] In some networks, a beam management procedure may be performed when a connection is established with a network on a cell or cell group (or reconnected with the network). In addition, a beam management procedure may be performed when already connected to a network on a cell or cell group. The amount of time the beam management procedure is performed when establishing the connection may be longer than the amount of time the beam management procedure is performed when already connected to the network on the cell or cell group. In some networks, the amount of time the beam management procedure is performed when establishing the connection may not meet the latency requirements of communications intended to be communicated via the cell or cell group. For example, when communicating in dual connectivity mode, the SCG may be inactive in situations where the throughput of the MCG is sufficient for data communicated via the network. When the throughput of the MCG is insufficient, the network may activate the SCG to increase the combined throughput to meet the throughput required for data communicated via the network. However, when the SCG is activated, the UE may need to perform a beam management procedure before being scheduled to carry data. The beam management procedure may require an amount of time that causes the data to fail to meet the latency requirements.

[0095] Failure to meet latency requirements may result in communication errors that may consume computing, power, communication, and / or network resources to detect and correct. Additionally or alternatively, failure to meet latency requirements may not be remedied, depending on the type of data (e.g., for data streams where data becomes useless after expiration).

[0096] As indicated above, Figure 6 is provided as an example of a beam management process. Other examples of beam management processes can be found in the Figure 6 For example, the UE 120 and the network node 110 may perform the third beam management procedure before performing the second beam management procedure, and / or the UE 120 and the network node 110 may perform a similar beam management procedure to select a UE transmit beam.

[0097] Figure 7 is a diagram illustrating an example 700 of communicating using a millimeter wave repeater according to the present disclosure.

[0098] Because millimeter wave communications have higher frequencies and shorter wavelengths than other types of radio waves used for communications (e.g., sub-6 GHz communications), millimeter wave communications may have shorter propagation distances and may be more easily blocked by obstacles than other types of radio waves. For example, wireless communications using sub-6 GHz radio waves may be able to penetrate the walls of a building or structure to provide coverage from a network node 110 using sub-6 GHz radio waves to an area on the opposite side of the wall. However, millimeter waves may not be able to penetrate the same wall (e.g., depending on the thickness of the wall and / or the material from which the wall is constructed). Some of the techniques and apparatus described herein use millimeter wave repeaters (in Figure 7 In an example of a UE 120 comprising a first relay and a second relay, the UE 120 may be configured to increase the coverage area of ​​the network node 110 and / or extend coverage to UEs 120 that do not have line of sight to the network node 110 (e.g., due to obstacles). Figure 7 In the example of UE 120a, UE 120b is included).

[0099] For example, Figure 7 As illustrated in the example of , an obstacle between UE 120b and network node 110 blocks the link between network node 110 and UE 120b or otherwise reduces the quality of the link. Similarly, an obstacle between UE 120b and the first relay blocks the link between the first relay and UE 120b or otherwise reduces the quality of the link. However, there are no obstacles or fewer obstacles between the second relay and UE 120b, and thus, it is possible that the communication between the second relay and UE 120b will have a higher quality than the communication between network node 110 and UE 120b or between the first relay and UE 120b. In addition, the millimeter wave repeater described herein can be a layer 1 millimeter wave repeater or an analog millimeter wave repeater, which is associated with lower cost, less processing, and lower latency than a layer 2 relay or a layer 3 relay.

[0100] A millimeter wave repeater (sometimes referred to herein as a repeater) can perform directional communication by using beamforming to communicate with the network node 110 via a first beam pair (e.g., a backhaul beam pair on a backhaul link with the network node 110) and communicate with the UE 120 via a second beam pair (e.g., an access beam pair on an access link with the UE 120). For example, in example 700, the first relay can communicate with the network node 110 via the first beam pair and can communicate with the UE 120a via the second beam pair. Similarly, the second relay can communicate with the network node 110 via the first beam pair and can communicate with the UE 120a via the second beam pair. A beam pair can refer to a Tx beam used by the first device to transmit and an Rx beam used by the second device to receive information sent by the first device via the Tx beam.

[0101] As shown in reference numeral 705, the network node 110 may use a beam sweeping process to transmit communications over time via multiple beams (e.g., using time division multiplexing (TDM)). As shown in reference numeral 710, the first repeater may receive communications via the Rx beam of the first repeater. As shown in reference numeral 715, the first repeater may relay each communication received via the multiple Tx beams of the first repeater (e.g., using TDM). As used herein, relaying a communication may refer to transmitting the received communication (e.g., after amplifying the received communication) without decoding the received communication and / or without modifying the information carried in the received communication. Alternatively, relaying a received communication may refer to transmitting the received communication after decoding the received communication and / or modifying the information carried in the received communication. In some aspects, a received communication may be relayed using different time resources, different frequency resources, and / or different spatial resources (e.g., a different beam) than the time resources, frequency resources, and / or spatial resources in which the communication was received to transmit the communication. As shown by reference numeral 720, UE 120a may receive the relayed communication. In some aspects, UE 120a may generate a communication to be transmitted to network node 110. UE 120a may then send the communication to a first relay for relaying to network node 110.

[0102] In some aspects, a millimeter wave (mmW) repeater may receive a millimeter wave signal (e.g., an analog millimeter wave signal) from a network node 110, may amplify the millimeter wave signal, and may transmit the amplified millimeter wave signal to one or more UEs 120. In some aspects, the mmW repeater may be an analog mmW repeater, sometimes also referred to as a layer 1 mmW repeater. Additionally or alternatively, the mmW repeater may be a wireless TRP acting as a distributed unit (e.g., of a 5G access node) that wirelessly communicates with a network node 110 acting as a central unit or access node controller (e.g., of a 5G access node). The mmW repeater may receive, amplify, and transmit the analog mmW signal without performing analog-to-digital conversion on the analog mmW signal and / or without performing any digital signal processing on the mmW signal. In this way, latency may be reduced and the cost of producing the mmW repeater may be reduced.

[0103] In some networks, multiple relays may be used in a communication link between a UE and a network node, where the communication link includes two or more hops. The amount of latency between the UE and the network node may be based at least in part on the number of relays (and / or hops) used in the communication link between the UE and the network node and / or the total path length of the communication link. In some networks (such as in dual connectivity networks), different cells or groups of cells may use different paths for the communication link between the UE and the network node. In this way, the amount of latency may be different for different cells or groups of cells.

[0104] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0105] Figure 8 8 is a diagram illustrating an example 800 of communicating using a PCell and an SCell according to the present disclosure. For example, a UE may communicate with a network node using an NSA connection, in which the PCell provides an anchor point and the SCell provides increased throughput capacity when needed. The PCell may be part of a PCell group, and / or the second cell may be part of an SCell group. The PCell may be associated with a first FR and / or a first RAT, and the SCell may be associated with a second FR and / or a second RAT (e.g., where the first and second FRs are different and / or the first and second RATs are different).

[0106] like Figure 8 As shown, the UE and the network node may communicate during PCell active time 805. The PCell active time 805 may include a time during which a communication link is established and connects the UE and the network node.

[0107] During the PCell active time 805, the UE and the network node may also communicate via the SCell during the SCell active time 810. The UE and the network node may communicate via the SCell active time 810 based at least in part on an amount of data for communication meeting a threshold (e.g., exceeding the throughput capacity of the PCell).

[0108] The network node may release the SCell for the SCell inactive time 815. The network node may release the SCell to save computational, power, communication, and network resources. The network node may reactivate the SCell for the SCell active time. For example, the network node may activate the SCell for the SCell active time 820 based at least in part on receiving an increased amount of data for the UE (e.g., from an application server communicating with the UE), where the increased amount of data meets a threshold (e.g., exceeds the throughput capacity of the PCell).

[0109] As indicated above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 The examples described are different.

[0110] In some networks, the SCell may have minimal scope for critical functionality (e.g., relying on the PCell and / or lower frequency band cells for certain functionality). For example, the network node may not send "always on" signals, such as SSBs or other RSs that the UE may use to synchronize with the network node on the SCell. In some networks, the SCell may be active for sporadic and / or short sessions with bursty activity patterns, such as Figure 8 As shown.

[0111] In some networks, SCells (e.g., sub-THz-based SCells) may operate using one or more hops between the UE and network nodes. For example, the one or more hops may traverse one or more power-efficient smart repeaters (repeaters (RPs) and / or APs, etc.) with out-of-band control using PCells.

[0112] A smart repeater (e.g., for sub-THz) may have functional components such as RedCap UE (RC UE) for PCell connections (e.g., for delivering out-of-band control messages, reports, and / or feedback, etc.), wideband analog amplification and forwarding (AF) functionality for data forwarding, and / or dedicated narrowband local SSB and / or synchronous RS transmission and / or reception capabilities on the SCell (e.g., using sub-THz carrier frequencies) for complementary time synchronization and beam refinement processing. The communication link between the UE and the network node may have progressive synchronization across hops, hop-specific synchronization, and beam management sessions with customized synchronization RS and / or SSB microburst scheduling.

[0113] In some networks, both APs and RPs are intelligent repeaters. RPs are involved when an additional repeater is needed to provide a communication link between an AP and a network node (e.g., a base station or RU). APs and RPs may have conceptually the same functionality, but with some differences in hardware and capabilities. APs and RPs may be referred to using different names to identify usage. For example, AP may be used to indicate an intelligent repeater (e.g., a network node and / or wireless communication device) that has a direct connection (e.g., a serving link) to a UE, and RP may be used to indicate an intelligent repeater that has an intermediate link or a direct link (e.g., a donor link) to a network node. As used herein, RP and / or repeater may be used to refer to an AP or RP as described herein.

[0114] As discussed herein, when the SCell or PCell operates with different FRs and / or with different RATs, or with different latencies between the UE and the network node, synchronization with the PCell may not be sufficient for synchronization with the SCell. Based at least in part on the SCell link not being continuously active using an "always on" signal or other synchronization signal when not actively communicating via the SCell, the UE and / or any smart repeaters along the communication link may need to be synchronized before commencing communication to avoid communication errors that may have been caused by timing errors. However, performing a full synchronization process and / or beam management process may consume an amount of time that causes the data to not meet latency requirements. Additionally or alternatively, performing a full synchronization process may unnecessarily consume power resources. In this way, activating the SCell may provide increased throughput capacity, but may result in communication errors when the UE synchronizes with the network node via the SCell.

[0115] In some aspects described herein, a UE and / or a repeater (e.g., a smart repeater, an AP and / or a RP, etc.) may perform synchronization (e.g., time and / or frequency synchronization) with a network node for an SCell, where the synchronization is based at least in part on PCell synchronization.

[0116] For example, a wireless communication device (e.g., a UE and / or a relay) may obtain synchronization with a PCell of a wireless network (e.g., using a RS of a PCell). The wireless communication device may receive an indication of activating an SCell of the wireless network and may receive the RS of the SCell. The wireless communication device may obtain synchronization with the SCell based at least in part on an offset between the RS of the SCell and a reference time of the PCell. The reference time may be based at least in part on synchronization with the PCell. Once synchronized with the SCell, the wireless communication device may communicate via the SCell. By obtaining synchronization with the SCell based at least in part on an offset between the RS of the SCell and the reference time of the PCell, the network may support obtaining synchronization on the SCell (e.g., across all hops) in a reduced amount of time compared to a full synchronization process. Additionally or alternatively, the wireless communication device may save power resources that would otherwise have been consumed by performing a full synchronization process on the SCell.

[0117] Synchronization with the SCell may be based at least in part on using a single-hop (e.g., direct) or multi-hop communication link between the UE and the network node. In some aspects, the multi-hop synchronization process may be established using a gradual synchronization approach in which a first RP is synchronized (e.g., using a synchronization RS sent by the network node to the first RP or sent by the network node using a beam closest to the RP), a second RP is synchronized (e.g., the first RP sends a synchronization RS to the second RP based at least in part on downlink synchronization of the first RP), and so on until the UE is reached and synchronized (e.g., an AP with a direct link to the UE sends a synchronization RS based at least in part on downlink synchronization of the AP).

[0118] In some aspects, for SCells (e.g., sub-THz SCells), a local frequency tracking loop (FTL) or frequency synchronization may not be required. Frequency tracking and / or corresponding parts per million (ppm) errors (ppm_err) based at least in part on the PCell (e.g., PCell connectivity) may be reused and / or projected onto the SCell (e.g., the frequency band of the SCell). In some aspects, frequency tracking and / or ppm errors may be modified and / or offset for application to the SCell.

[0119] In some aspects, the PCell time tracking loop (TTL) and PCell timing can be used as a coarse timing reference for the SCell. In some aspects, no separate TTL is used on the SCell, and only a complementary fine timing estimate (delta timing offset (TO)) relative to the PCell timing is required for SCell time synchronization. Time synchronization for DCI can be performed at least in part based on dedicated synchronization RS (e.g., SSB or other RS) microbursts sent during SCell hop-specific synchronization and / or beam management sessions.

[0120] The SCell time synchronization session (which may also include beam management synchronization) may be scheduled and / or performed by the network node via the PCell. For example, the SCell time synchronization session may be scheduled and / or performed by the network node in the following manners: upon link activation (e.g., an indication of activating the SCell), upon a predefined time period and / or periodicity along a long-term active SCell-based data offload session, and / or as an event-driven synchronization session scheduled during an active data offload session in response to one or more events, etc.

[0121] In some aspects, a time synchronization session may be based at least in part on a synchronization session configuration for the receiving side (and the transmitting side for intermediate hops), which is indicated and / or executed over the PCell link and with reference to the PCell timing. In some aspects, the time synchronization session may use PCell timing information for coarse time synchronization and / or reference to define time search boundaries and / or time uncertainty for the SCell local synchronization session per SCell link activation. A wireless communication device (e.g., a downstream wireless communication device) may estimate the fine timing (e.g., incremental timing offset) of the SCell relative to the configured receive time for the SCell synchronization session based at least in part on the PCell timing, time slots, and / or control signaling time slots. In this way, the wireless communication device may not have an independent TTL on the SCell and may obtain SCell time synchronization based at least in part on the PCell coarse time and the locally estimated relative timing offset. In some aspects, a progressive synchronization approach may be used to establish overall time synchronization per multi-hop link.

[0122] In some aspects, SCell control messages may be signaled on the PCell with reference to a PCell downlink slot index, a PCell symbol within a downlink slot, a PCell downlink slot carrying a control message (e.g., a physical downlink control channel (PDCCH)), a scheduling event on the PCell for the PCell or SCell (e.g., indicated relative to the scheduling and based on the PCell timing), and / or an additional time offset relative to any of the previous references (e.g., as a timing reference for determining and / or applying a timing offset). In some aspects, an additional time offset may be indicated and / or configured for synchronization with the SCell.

[0123] In some aspects, SCell control applications may be provided with relative offsets in SCell time units (e.g., symbols and / or slots) for communications assumed to be scheduled via the SCell. For example, each PCell slot and / or symbol may include multiple SCell slots / symbols, so SCell control information (e.g., scheduling DCI) may indicate the timing of subsequent SCell time units with reference to the PCell time unit. SCell control information may indicate scheduling of synchronization RSs and / or associated receive and / or transmit times, scheduling of SCell data and / or forwarding operations, and / or scheduling of SCell link adaptation (LA) RSs, among other things.

[0124] The SCell control information may be indicated using reference PCell timing based at least in part on an indication of synchronization sent by the wireless communication device (e.g., an "in sync" status bit in uplink control information (UCI) to be indicated by the SCell to the PCell as a response to the synchronization session to indicate a success of the synchronization process (e.g., by measuring whether the channel RSSI is greater than a predefined threshold). In some aspects, once the indication of synchronization is sent (e.g., the "in sync" status bit is turned on), the network node may schedule data periodically and / or at least in part based on events. In some aspects, the synchronization state may be valid until a change in the relative channel delay and / or dominant line-of-sight (LOS) channel path, TTL movement, and / or drift for the PCell between the PCell and the SCell meets a threshold (e.g., which may be related to some abnormal dynamics involving the PCell channel and / or communication link) or a beam switch of the PCell.

[0125] In some aspects, for long-lasting SCell data offloading sessions and / or SCell link activation or duration scenarios, the synchronization session for the SCell may be repeated periodically or semi-periodically according to a certain time threshold duration to update the relative time offset estimate to maintain a negligible time mismatch between the SCell timing and the PCell timing, may be scheduled non-periodically according to the threshold time duration, or may be event-driven, etc.

[0126] Based at least in part on using PCell synchronization for SCell synchronization, the network can support acquiring synchronization on the SCell (e.g., across all hops) in a reduced amount of time and / or can save power resources that might have been used to perform full synchronization using only SCell signals.

[0127] Additionally or alternatively, a progressive synchronization approach supports low-latency and low-power multi-hop link synchronization with smart relays with out-of-band control based on PCell. For example, in a network with one or more relays between a UE and a network node, using PCell-based (e.g., out-of-band for SCell) timing to assist in SCell synchronization, each of the one or more relays can save power resources that would otherwise have been consumed by beneficial synchronization using only SCell signaling.

[0128] Furthermore, using PCell synchronization for SCell synchronization enables faster SCell link activation and deactivation for eligible UEs with low complexity, low power, and low latency penalties, supporting bursty activity modes for improved power efficiency. For example, a wireless communication device can achieve SCell synchronization more quickly than using only SCell signaling. In this way, the use of SCells for intermittent, bursty, and / or high-throughput communications when temporary supplementation of the PCell is needed can be optimized for efficient power resource consumption.

[0129] In some aspects, using PCell synchronization for SCell synchronization can expand a range of use cases and scenarios in which SCells with relatively high FR can be used with reasonable implementation and deployment implications (e.g., with relatively fast SCell link activation and reduced power consumption). In addition, using PCell synchronization for SCell synchronization can accelerate initial high FR (e.g., sub-THz) deployments (e.g., with a strong dependency on lower frequency bands).

[0130] When the RS of the SCell is used to further synchronize the SCell or perform beam management within the SCell when the SCell is activated, the RS can save network resources, computing resources, and power resources compared to the RS that can be used without synchronization via the PCell.

[0131] In some aspects, the network node and the UE may use a reduced list of candidate transmit beams for initial beam search per SCell activation based at least in part on having synchronized on the PCell and having received information associated with synchronization and beam management on the SCell via the PCell. For example, the transmit beam list may be reduced based at least in part on PCell beam association for direct or single-hop UE-gNB links, coarse beam determination based on position and ray tracing for multi-hop link hopping, and / or past beam management reports from fixed infrastructure for hopping and / or links.

[0132] In some aspects, based at least in part on having synchronized on the PCell and receiving information associated with synchronization and beam management on the SCell via the PCell, the network node and the UE may use a relatively small time uncertainty range for time synchronization and / or initial acquisition (Init Acq) search for each SCell activation (e.g., using coarse timing based at least in part on the PCell timing), omit local frequency synchronization or hypothesis search for the SCell (e.g., the frequency for the SCell may be tracked based on the PCell link), and / or omit multiple physical cell identifier (PCI) hypothesis searches based at least in part on the configuration of all N_IDs and PCIs for the SCell on the PCell.

[0133] In some aspects, based at least in part on having synchronized on the PCell and receiving information associated with synchronization and beam management on the SCell via the PCell, the RS for the SCell may omit one or more of the PSS and SSS based at least in part on the need to detect a known sequence RS on one of the beam hypotheses to obtain timing and transmit-receive beam pairs for the SCell. Additionally or alternatively, the network node and the UE may omit Master Information Block (MIB) data signaling on the SCell. For example, only the SCell transmit beam index information may be indicated as part of the synchronization and beam management RS waveform and signaling, while the remaining control information may be provided on the PCell. Accordingly, the PBCH allocation and decoding process may be simplified.

[0134] Based at least in part on using RS for SCell as described, the RS can have reduced complexity, reduced power, and reduced range for initial acquisition for each SCell link activation and / or synchronization and beam management sessions for multi-hop SCell links (e.g., SubThz links).

[0135] In some aspects, the RS for the SCell may include SSB microbursts with the same SSB structure and waveform, where the customized selection of the beam list is localized at the time of each SCell hop and synchronization session scheduling. The customized SSB microburst (e.g., simplified SSB microburst) may have reduced processing by the receiving device (e.g., UE) to derive only a subset of synchronization and beam management parameters (e.g., time synchronization and transmit-receive beam pairs).

[0136] In some aspects, a waveform for RS can be introduced to support SCell synchronization and beam management sessions (e.g., in SubThz), thereby supporting only a subset of synchronization and beam management parameters. In this way, the waveform can reduce the complexity functionality relative to SSB-based Init Ack without using PCell synchronization to support synchronization and beam management at the SCell.

[0137] In some aspects, the RS waveform may include a first component having only the PSS or SSS (e.g., not both) or another narrowband, and being continuous in the frequency domain RS and having a known sequence. For the first component, the known sequence may be defined by a corresponding N_ID, which may be configured (e.g., dynamically) for each SCell link hop (e.g., to the transmitting and receiving nodes involved in a particular synchronization and beam management session) via the PCell.

[0138] The sequence design may include a sufficient number of sequence options (N_ID) to allow different sequences to be used for different simultaneously trained or activated SCell links or hops in adjacent SCell coverage areas or locations. In this way, each SCell (e.g., SubThz-based SCell) coverage area may include multiple SCellAPs providing multiple SCell coverage points, which may include multiple simultaneously activated (e.g., with multiple nodes) SCell multi-hop links that may be established or activated simultaneously (e.g., may require multiple simultaneous synchronization and beam management sessions across all involved hops or nodes).

[0139] In addition to the first component carrying a known sequence, a second component (e.g., carried on a single additional OFDM symbol) can also be used in this waveform to convey transmit beam index information. Once only one specific beam is detected from a transmit beam block (e.g., an RS transmitted via a transmit beam set), the known sequence can allow the UE to derive the location (e.g., exact timing) of the start of the transmit beam block. The transmit beam index or beam ID can be determined for the detected beam for use in beam management reporting and corresponding transmit configuration indicator (TCI) or quasi-co-location (QCL) association.

[0140] In some aspects, for each synchronization and beam management session, each synchronization and beam management RS block may include multiple scanned transmit beams (e.g., configured for a transmitting node such as a network node via a PCell) having a consecutive set of indices. In some aspects, different synchronization and beam management sessions may have different beam lists (e.g., even for the same SCell link hop). In each session, consecutive beam indices may be used, and beam indices from any previous session may be irrelevant to the current synchronization and beam management session. For example, independent beam indices may be used for the same hop across different synchronization and beam management sessions, and only the current or last session may be associated with a per-node beam index covering a consecutive list (e.g., starting at 1) of beam indices that may be associated with different physical beams scanned or used in the current synchronization and beam management session.

[0141] Based at least in part on the use of a relatively low number of scanned transmit beams per session, beam index information may be provided as follows. In the case of synchronization and beam management sessions for SCells, a new control information payload or a modified PBCH / control data payload may carry only beam index information. In this case, a general PBCH (or PBCH-like) structure may be used, modified to use only a single additional OFDM symbol (e.g., as a second component of the RS) that may be included in this new waveform synchronization and beam management RS. The general PBCH structure may have a payload that may be decoded using information derived from the DMRS (e.g., channel estimation). This option may involve a complete PBCH / control payload demodulation and decoding process (e.g., for a single OFDM symbol for PBCH under this option).

[0142] Alternatively, an addressing list of consecutive beam indices can be mapped onto a sequence list. The number of sequences can be large enough to support unique sequences for all scanned transmit beams for each synchronization and beam management session. A specific sequence associated with a specific transmit beam index can be used and sent on an additional OFDM symbol of the synchronization and beam management RS. In some aspects, the sequence can be sent as a SSS, where the purpose of the transmitted SSS sequence is repurposed (e.g., to transmit beam identification instead of N_ID2 for PCI). The SSS supports 336 sequences, which may be sufficient to support the transmit beam index scanned for each synchronization and beam management session. Different subsets of the sequence list can be used on adjacent hops or adjacent SCells to eliminate or reduce possible interference. This option can involve reducing processing complexity on the receiver side.

[0143] In some aspects, the number of transmit beams per synchronization and beam management RS block can be configured and indicated for the corresponding transmitting node for each synchronization and beam management RS session on the PCell. The number of scanned transmit beams, denoted as N, can define the first N SSS-like sequences to be addressed on the receiving node side for beam index determination and detection.

[0144] The sequence option list may include a sufficient number of sequences to account for scenarios with a higher number of scanning transmit beams per session, but based on the configuration used for the number of scanning transmit beams, typically only the first N sequences from the list will be applicable for a particular synchronization and beam management session.

[0145] In some aspects, different hops or SCells may use different sequence subsets for beam index indication (e.g., configured via PCell-based configuration) to reduce the negative impact of any possible interference. In the case where the SCell operates in the Sub-Thz band, cross-link RS interference may be relatively small based at least in part on propagation characteristics in the Sub-Thz band.

[0146] The bandwidth of the RS may be configurable or predefined. In some aspects, the RS waveform may be based only at least in part on (e.g., as an observer from the repeater side) analog processing NB for a wideband signal assumption, while the digital processing capabilities on the repeater side may be used only to support synchronization and beam management RS transmission and reception processes.

[0147] The reduced RS bandwidth may save power on the repeater side associated with digital processing regarding synchronization and beam management sessions, and will also enable higher effective isotropically radiated power for the RS (e.g., to improve the robustness of synchronization and beam management sessions).

[0148] As a configurable option, several repetitions of RS can be sent on consecutive OFDM symbols for the same beam. RS block repetition can be used to support receive beam scanning on the receiving side node (e.g., UE).

[0149] In some aspects, different beams from a single synchronization and beam management RS block can be transmitted on consecutive OFDM symbols from the beginning of each synchronization and beam management RS block repetition until the end of this repetition (e.g., without null symbols or gap symbols). The same receive beam will be reused along a single synchronization and beam management block that includes all scanned transmit beams. Receive beam switching and searching can be performed between or across different repetitions of the RS block.

[0150] Different synchronization and beam management RS block repetitions can be sent using time gaps configurable via the PCell time gap. Time gaps can be used for receive beam switching between RS block repetitions to allow receive beam searching under time uncertainty before timing synchronization is achieved.

[0151] Based at least in part on using the described waveform with reduced content relative to SSB, the UE can activate and acquire the SCell with reduced complexity of the InitAck procedure, reduce the complexity of the session for synchronization and beam management for the SCell, reduce network power consumption, and / or reduce activation latency (e.g., single localization in the time synchronization and beam management session for time synchronization and transmit-receive beam pair determination for each hop), etc. Additionally or alternatively, the waveform can support avoiding SSB scalability issues (e.g., not always turning on a signal with a reserved SSB slot for a smart repeater), and / or can support universal support for multi-hop links with an unlimited number of smart repeaters associated with the same SCell (e.g., to allow for extended range or mesh topologies).

[0152] Figure 9 is a diagram of an example 900 associated with using waveforms for synchronization and beam management of a secondary cell according to the present disclosure. Figure 9 As shown in FIG, a network node (e.g., network node 110, CU, DU, and / or RU) may communicate with a UE (e.g., a mobile terminal (MT) of a wireless communication device and / or relay, etc.). In some aspects, the network node and the UE may be part of a wireless network (e.g., wireless network 100). The UE and the network node may be in a Figure 9 The operations shown are performed after a wireless connection has been established.

[0153] As indicated by reference numeral 905, the network node may send configuration information, and the UE may receive the configuration information. In some aspects, the UE may receive the configuration information via one or more of RRC signaling, one or more MAC CEs, and / or DCI, etc. In some aspects, the configuration information may include an indication of one or more configuration parameters for the UE to select (e.g., known to the UE and / or previously indicated by the network node or other network device) and / or explicit configuration information for the UE to configure the UE, etc.

[0154] In some aspects, the configuration information may indicate that the UE is to send an indication of support for SCell synchronization based at least in part on PCell synchronization. In some aspects, the network node may send the configuration information via the PCell connected to the UE. In some aspects, the PCell may operate using a relatively lower FR than the SCell. The PCell may be part of an MCG.

[0155] In some aspects, the configuration information may indicate the configuration of the RS of the SCell. In some aspects, the configuration may indicate one or more frequency bands or FRs to which the configuration is applicable (eg, applicable to a Sub-Thz SCell).

[0156] The UE may configure itself based at least in part on the configuration information.In some aspects, the UE may be configured to perform one or more operations described herein based at least in part on the configuration information.

[0157] As indicated by reference numeral 910, the UE may send an indication of support for SCell synchronization based at least in part on PCell synchronization, and the network node may receive the indication.In some aspects, the capability report may indicate that the UE supports SCell synchronization based at least in part on PCell synchronization.

[0158] As shown by reference numeral 915, the UE may receive RSs for the PCell and the network node may transmit these RSs. In some aspects, the RSs for the PCell may include SSBs and / or CSI-RSs. In some aspects, the RSs may include other types of RSs, such as DMRSs and / or Tracking Reference Signals (TRSs) within data communications.

[0159] The UE may acquire synchronization with the PCell, as indicated by reference numeral 920. For example, the UE may use the RS of the PCell to synchronize the UE in the time domain and / or in the frequency domain.

[0160] As indicated by reference numeral 925, the UE may receive an indication to activate the SCell, and the network node may send the indication. The SCell may be part of a wireless network associated with the PCell. In some aspects, the SCell may be part of an SCG. In some aspects, the SCell may be associated with a frequency bandwidth higher than that of the PCell. For example, the highest frequency used for the PCell may be lower than the lowest frequency used for the SCell. This may enable the PCell to have higher reliability than the SCell.

[0161] In some aspects, the indication to activate the SCell may include a MAC-CE configured to activate the SCell.The UE may receive the indication to activate the SCell via communication using the PCell.

[0162] As indicated by reference numeral 930, the UE may receive a configuration for synchronization with the SCell, and the network node may send the configuration. For example, the configuration for synchronization with the SCell may indicate one or more parameters for using the reference time of the PCell for synchronization with the SCell. For example, the one or more parameters may indicate whether the SCell will have a time tracking loop (e.g., independent of the PCell) and / or the time during which the SCell will have a time tracking loop. In some aspects, the one or more parameters indicate that resources of the RS of the SCell are to be used for fine timing estimation as a supplement to the coarse timing estimation using the PCell. In some aspects, the one or more parameters may indicate scheduling for synchronization sessions associated with the SCell and / or PCell. In some aspects, the configuration includes an indication of activating the SCell.

[0163] As indicated by reference numeral 935, the UE may receive an indication of a configuration for receiving an RS for an SCell, and the network node may send the indication. In some aspects, the configuration may indicate a reference time of the PCell for synchronization of the SCell. In some aspects, the reference time of the PCell may be based at least in part on a downlink slot index of the PCell, a symbol within a downlink slot of the PCell, a downlink slot index carrying control information associated with the SCell, a scheduling event on the PCell, and / or a time unit offset from any of these by an indicated amount, etc.

[0164] In some aspects, the indication described in conjunction with reference numeral 925, the configuration described in conjunction with reference numeral 930, and / or the indication described in conjunction with reference numeral 935 may be combined into one or two messages.

[0165] As shown in reference numeral 940, the UE may receive the RS for the SCell, and the network node may transmit the RS. In some aspects, the RS for the SCell may be configured based at least in part on synchronization with the PCell. For example, the RS for the SCell may have reduced and / or different content based at least in part on synchronization with the PCell. In some aspects, the configuration of the RS for the SCell may be based at least in part on an indication of the configuration of the RS for the SCell received via the PCell and / or an indication of the configuration within a communication protocol, etc.

[0166] In some aspects, repetition of the RS of the SCell may include transmitting the RS using a set of network node transmit beams (e.g., sequentially using each of the network node transmit beams using TDM). In some aspects, the respective repetitions of the transmit beam set support receive beam scanning of the transmit beam set. For example, each repetition may include the same set of network node transmit beams, which the UE may use to test different UE receive beams to find a beam pair.

[0167] In some aspects, the UE may receive the RS of the SCell using a reduced candidate beam list for initial beam search relative to a candidate beam list for initial beam search that is not synchronized with the PCell (e.g., based at least in part on an indication via the PCell and / or based at least in part on a configuration received via the PCell of a candidate beam list associated with a beam for communicating via the PCell) and / or receive the RS using a reduced time domain range for receiving the RS of the SCell (e.g., based at least in part on having coarse time domain synchronization from synchronization with the PCell).

[0168] In some aspects, the RS of the SCell may not include a PSS associated with a synchronized SSB without a PCell, an SSS associated with a synchronized SSB without a PCell, or one or more elements of a MIB associated with a synchronized SSB without a PCell, etc.

[0169] In some aspects, the RS of the SCell includes a known sequence RS or transmit beam index information for a beam associated with the SCell. The known sequence RS may be transmitted within a unique symbol of the SSS, PSS, or RS. In some aspects, the known sequence may include a sequence selected from a set of candidate sequences that support different sequences for different devices of the wireless network. In some aspects, the different sequences may be associated with corresponding devices of the wireless network, where each device of the wireless network has a unique sequence. In some aspects, the known sequence may be known at least in part based on an indication via the PCell.

[0170] In some aspects, the transmit beam index information may include an indication of the timing of the transmit beam used to transmit the RS of the SCell and / or a transmit beam identifier. In some aspects, the RS may include an indication of the transmit beam index information within the PBCH portion of the RS of the SCell, within a single OFDM symbol, or based at least in part on a selection of a sequence of RS symbols, where the sequence is selected from a set of candidate sequences associated with different transmit beam index information. For example, each candidate sequence may be mapped to different transmit beam index information. In some aspects, the UE may receive an indication of the mapping via the PCell.

[0171] In some aspects, a UE may receive RS for an SCell during a first RS opportunity for the SCell. In some aspects, the first RS opportunity for the SCell may be associated with a first set of transmit beams, and a second RS opportunity for the SCell may be associated with a second set of transmit beams that is different from the first set of transmit beams, and so on.

[0172] In some aspects, the RS of the SCell may be used to support determining a time offset for hops in a communication link between the UE and a network node. In some aspects, the RS of the SCell may include an SSB or another RS ​​type. In some aspects, the UE may receive the RS of the SCell within a time window that is based at least in part on the offset and / or configuration from the SCell.

[0173] In some aspects, the UE may receive the RS for the SCell via an air path that includes multiple hops. For example, the RS for the SCell may be forwarded by a RP and / or AP between the network node and the UE. In some aspects, the RP and / or AP may modify and / or retransmit the RS for the SCell as part of the forwarding. In some aspects, the RP and / or AP may apply a timing offset associated with the RP and / or AP before forwarding the RS for the SCell.

[0174] In some aspects, receiving the RS for the SCell comprises receiving an RS burst (e.g., a transmission that occupies less than all time resources of a time slot or subframe) during a synchronization session or during a beam management session. In some aspects, the synchronization session or beam management session is associated with: a frequency range-specific synchronization session or beam management session, a secondary cell-specific synchronization session or beam management session, and / or a hop-specific synchronization session or beam management session, among others.

[0175] As indicated by reference numeral 945, the UE may obtain synchronization with the SCell based at least in part on an offset from the RS of the SCell and a reference time of the PCell. For example, the UE may use the reference time of the PCell as coarse timing and may refine the timing based at least in part on refining the coarse timing using an offset determined based on the RS of the SCell. The reference time may be based at least in part on synchronization with the PCell. For example, the reference time may rely on synchronization with the PCell to use a time unit (e.g., a time slot or symbol) of the PCell as a reference time.

[0176] In some aspects, the UE may obtain the reference time of the PCell via an indication of a configuration for receiving the RS of the SCell as described in conjunction with reference numeral 935. In some aspects, the UE may obtain the reference time via observation at the UE (e.g., measuring a signal) and / or via out-of-band communication. In some aspects, the reference time of the PCell is based at least in part on the FTL of the PCell and / or the RAN time unit of the PCell.

[0177] In some aspects, obtaining synchronization with the SCell may be based at least in part on a configured periodicity for synchronizing the SCell and / or a triggering event during ongoing communication via the SCell. For example, the UE may be configured with a set of one or more events that may periodically or trigger synchronization of the SCell.

[0178] In some aspects, the network node may acquire synchronization with the UE based at least in part on the UE acquiring synchronization with the network node. In some aspects, the UE may indicate that the UE has acquired synchronization with the network node and the operation may be part of the network node acquiring synchronization with the UE.

[0179] In some aspects, the UE can obtain synchronization with the SCell based at least in part on obtaining frequency synchronization for the SCell via the PCell, obtaining one or more elements of the MIB for the SCell via the PCell (e.g., reducing the number of elements of the MIB to be received via the SCell), using the RS of the SCell to reduce or omit frequency synchronization, and / or decoding the PBCH allocation with reduced complexity relative to the PBCH associated with the SSB without synchronization of the PCell, etc.

[0180] As shown at reference numeral 950, the UE may identify a beam pair for the SCell. In some aspects, the UE may identify the beam pair based at least in part on a beam identifier (e.g., beam ID) indicated within the RS of the SCell. The UE may identify the strongest transmit beam and paired UE receive beam for transmitting the RS of the SCell based at least in part on measuring the RS (e.g., based at least in part on the configuration of the RS for receiving the SCell).

[0181] In some aspects, the UE can identify a beam pair (e.g., a transmit beam used by a network node within a beam pair) based at least in part on decoding transmit beam information based at least in part on a DMRS within one or more OFDM symbols of transmit beam index information, and / or identifying a beam associated with an RS of an SCell based at least in part on the transmit beam information.

[0182] As indicated by reference numeral 955, the UE may send an indication of whether the UE is synchronized with the SCell and / or one or more beams aligned for communication via the SCell, and the network node may receive the indication. In some aspects, the UE may send an indication of synchronization with the SCell via UCI. In some aspects, the indication may be a single bit indication. In some aspects, the network node may schedule communication via the SCell only if the UE indicates synchronization with the SCell. Alternatively, the network node may schedule communication via the SCell only if the UE has not indicated a failure to synchronize with the SCell.

[0183] In some aspects, the indication of whether the UE is synchronized with the SCell applies over a duration that expires based at least in part on: a change in the relative channel delay between the PCell and the SCell, a change in the dominant line-of-sight path for the SCell or PCell, beam switching for the PCell, a change in the TTL meeting a threshold and / or after a configured amount of time, and the like.

[0184] In some aspects, the UE may indicate one or more beams in a beam pair for communication via the SCell based at least in part on the beam identifier of the strongest beam on which the UE receives the RS of the SCell. In some aspects, the UE may send an indication of RSRP or other beam quality metric to the network node to indicate the transmit beams that the network node should use for communication with the UE via the SCell. In some aspects, the UE may not indicate receive beams for reception in communication with the network node.

[0185] As shown in the reference numeral 960, the UE may receive a scheduling message for communicating using the SCell, and the network node may send the scheduling message. In some aspects, the scheduling message may reference timing in the PCell. In some aspects, receiving the scheduling message may include: receiving an indication of a first time unit for the PCell, and receiving an indication of a second time unit for the SCell within the first time unit. For example, the scheduling message may indicate a time slot of the PCell. However, the time slot of the PCell may include multiple time slots of the SCell (e.g., based at least in part on different subcarrier spacings and symbol lengths). In this case, the scheduling message may indicate a second time unit of the SCell to indicate which of the multiple time slots of the SCell is included in the time slot of the PCell that is scheduled for communication via the SCell.

[0186] As indicated by reference numeral 965, the UE and the network node may communicate via the SCell. For example, the network node may transmit data that is not suitable for the throughput of the PCell, and the UE may receive the data. In some aspects, the UE and the network node may communicate via the SCell using one or more beams in a beam pair identified by the UE and / or indicated to the network node.

[0187] The UE may acquire synchronization with the SCell as indicated by reference numeral 965. For example, the UE may resynchronize with the SCell after communicating via the SCell for an amount of time that satisfies a threshold.

[0188] In some aspects, resynchronization with the SCell may be based at least in part on a configured periodicity for synchronizing the SCell and / or a triggering event during ongoing communication via the SCell. For example, the UE may be configured with a set of one or more events that may periodically or trigger resynchronization of the SCell.

[0189] Based at least in part on the use of PCell synchronization for SCell synchronization, the network may support acquiring synchronization on the SCell (e.g., across all hops) in a reduced amount of time. Additionally or alternatively, a progressive synchronization approach supports low latency and low power multi-hop link synchronization with smart repeaters with PCell-based out-of-band control. Furthermore, the use of PCell synchronization for SCell synchronization may support faster SCell link activation and deactivation with low complexity, low power, and low latency penalty for eligible UEs to support bursty activity modes for improved power efficiency. In some aspects, the use of PCell synchronization for SCell synchronization may expand a range of use cases and scenarios in which SCells with relatively high FR may be used with reasonable implementation and deployment implications. Furthermore, the use of PCell synchronization for SCell synchronization may accelerate initial high FR (e.g., sub-THz) deployments (e.g., with a strong dependency on lower frequency bands).

[0190] Based at least in part on using the described waveform with reduced content relative to SSB, the UE can activate and acquire the SCell with reduced complexity of the InitAck procedure, reduce the complexity of the session for synchronization and beam management for the SCell, reduce network power consumption, and / or reduce activation latency (e.g., single localization in the time synchronization and beam management session for time synchronization and transmit-receive beam pair determination for each hop), etc. Additionally or alternatively, the waveform can support avoiding SSB scalability issues (e.g., not always turning on a signal with a reserved SSB slot for a smart repeater), and / or can support universal support for multi-hop links with an unlimited number of smart repeaters associated with the same SCell (e.g., to allow for extended range or mesh topologies).

[0191] As indicated above, Figure 9 are provided as examples. Other examples can be found in the Figure 9 The examples described are different.

[0192] Figure 10 1000 and 1002 are diagrams of examples associated with waveforms for synchronization and beam management of SCells according to the present disclosure. Figure 10 In the context of , a network node (e.g., network node 110, CU, DU, and / or RU) may communicate with a UE (e.g., a wireless communication device and / or MT of a relay, etc.). In some aspects, the network node and the UE may be part of a wireless network (e.g., wireless network 100). The UE and the network node may be part of a wireless network (e.g., wireless network 100). Figure 10 The operations shown in FIG have previously established a wireless connection by PCell. Figure 10 The operations shown in may be associated with establishing a connection via an RS using an SCell, which has reduced content and / or complexity relative to an SSB.

[0193] As shown in examples 1000 and 1002, the RS may include a portion 1004 using transmit beam 1, a portion 1006 using transmit beam 2, and a portion 1008 using transmit beam 3. Each portion 1004, 1006, and 1008 may include a portion for time synchronization (e.g., a PSS or similar synchronization signal) and a portion indicating a beam identifier (e.g., a PBCH or SSS, etc.).

[0194] After transmitting a portion of the RS on the final transmit beam, a time gap 1010 may be used. This allows the UE time to switch its receive component to receive using a different receive beam. For example, RS repetition 1012 may be used to test the UE's receive beam 1, and RS repetition 1014 may be used to test the UE's receive beam 3. Each RS repetition may include the same set of transmit beams that the UE may use to find a beam pair with the UE's receive beam.

[0195] In some aspects, the number of transmit beams can be reduced relative to attempting synchronization with the SCell when the PCell is not yet synchronized. For example, the number of transmit beams can be associated with a set of transmit beams that are in the same or similar directions as the beams used in the PCell for communication between the UE and the network node. In this way, each repetition can have a reduced length, RSs can be transmitted with improved periodicity while maintaining the same overhead cost, and / or RS overhead can be reduced.

[0196] As indicated above, Figure 10 are provided as examples. Other examples can be found in the Figure 10 The examples described are different.

[0197] Figure 11 is a diagram illustrating an example process 1100, performed, for example, by a UE, according to the present disclosure. Example process 1100 is an example in which a UE (eg, UE 120) performs operations associated with using a waveform for synchronization and beam management of an SCell.

[0198] like Figure 11 As shown, in some aspects, process 1100 may include obtaining synchronization with a PCell of a wireless network (block 1110). For example, a UE (e.g., using Figure 13 The receiving component 1302 and / or the communication manager 1306 depicted in can obtain synchronization with the PCell of the wireless network, as described above.

[0199] like Figure 11 As further shown in FIG. 1 , in some aspects, process 1100 may include receiving an indication to activate an SCell of the wireless network (block 1120). For example, a UE (e.g., using Figure 13 The receiving component 1302 and / or the communication manager 1306 depicted in can receive an indication to activate the SCell of the wireless network, as described above.

[0200] like Figure 11As further shown in FIG, in some aspects, process 1100 may include receiving a RS for an SCell, the receiving of the RS for the SCell being based at least in part on obtaining synchronization with the PCell, the receiving including one or more of: using a reduced candidate beam list for initial beam search relative to a candidate beam list for initial beam search without synchronization with the PCell; or using a reduced time domain range for receiving the RS for the SCell (block 1130). For example, a UE (e.g., using Figure 13 The receiving component 1302 and / or the communication manager 1306 depicted in the figure can receive the RS of the SCell, and the reception of the RS of the SCell is at least partially based on obtaining synchronization with the PCell, and the reception includes one or more of the following operations: using a reduced candidate beam list for initial beam search relative to a candidate beam list for initial beam search that is not synchronized with the PCell; or using a reduced time domain range for receiving the RS of the SCell, as described above.

[0201] like Figure 11 As further shown in FIG. 1 , in some aspects, process 1100 may include obtaining synchronization with the SCell based at least in part on the RS of the SCell (block 1140). For example, a UE (e.g., using Figure 13 The receiving component 1302 and / or the communication manager 1306 depicted in can obtain synchronization with the SCell based at least in part on the RS of the SCell, as described above.

[0202] like Figure 11 As further shown in FIG. 1 , in some aspects, process 1100 may include identifying a beam pair for communicating via the SCell based at least in part on the RS of the SCell (block 1150). Figure 13 The communication manager 1306 depicted in can identify beam pairs for communicating via the SCell based at least in part on the RS of the SCell, as described above.

[0203] like Figure 11 As further shown in FIG. 1 , in some aspects, process 1100 may include communicating via the SCell based at least in part on synchronization with the SCell and using a beam pair (block 1160). Figure 13 The receiving component 1302, the sending component 1304 and / or the communication manager 1306 depicted in can communicate via the SCell based at least in part on synchronization with the SCell and using beam pairs, as described above.

[0204] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0205] In a first aspect, the RS of the SCell does not include one or more of the following: a PSS associated with a synchronized SSB without a PCell, an SSS associated with a synchronized SSB without a PCell, or one or more elements of a MIB associated with a synchronized SSB without a PCell.

[0206] In a second aspect, alone or in combination with the first aspect, the RS of the SCell includes one or more of a known sequence RS or transmit beam index information for a beam associated with the SCell.

[0207] In a third aspect, either alone or in combination with one or more of the first and second aspects, the known sequence comprises a sequence selected from a set of candidate sequences supporting different sequences for different devices used in the wireless network, and the known sequence is known at least in part based on an indication via the PCell.

[0208] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the transmit beam index information includes an indication of the timing of the transmit beam of the RS used to transmit the SCell or one or more of the transmit beam identifiers.

[0209] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the transmit beam index information is indicated within one or more of: a PBCH portion of the RS of the SCell, a single orthogonal frequency division multiplexing (OFDM) symbol, or a selection of a sequence of symbols of the RS, the sequence being selected from a set of candidate sequences associated with different transmit beam index information.

[0210] In the sixth aspect, alone or in combination with one or more of the first to fifth aspects, identifying a beam pair includes one or more of the following operations: decoding the transmitted beam information based at least in part on a DMRS within one or more OFDM symbols of the transmitted beam index information, or identifying the beam associated with the RS of the SCell based at least in part on the transmitted beam information.

[0211] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, selection of a sequence is based at least in part on an indication of mapping received via a PCell to indicate transmit beam index information.

[0212] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, obtaining synchronization with the SCell includes one or more of the following operations: obtaining frequency synchronization for the SCell via the PCell, obtaining one or more elements of the MIB for the SCell via the PCell, using the RS of the SCell to reduce or omit frequency synchronization, or decoding the PBCH allocation with reduced complexity relative to the PBCH associated with the SSB without synchronization of the PCell.

[0213] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, reception of the RS of the SCell is associated with a first RS timing of the SCell, wherein the first RS timing of the SCell is associated with a first set of transmit beams, and wherein the second timing of the SCell is associated with a second set of transmit beams that is different from the first set of transmit beams.

[0214] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the configuration of the RS of the SCell is at least partially based on an indication of the configuration of the RS of the SCell received via the PCell or an indication of the configuration within the communication protocol.

[0215] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the RS of the SCell is associated with a repetition of a transmit beam set, and the corresponding repetition of the transmit beam set supports receive beam scanning of the transmit beam set.

[0216] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, a highest frequency used for the PCell is lower than a lowest frequency used for the SCell.

[0217] In a thirteenth aspect, alone or in combination with one or more of aspects one to twelfth, process 1100 includes sending an indication of at least one beam associated with the beam pair, wherein communicating via the SCell using the beam pair is at least partially based on sending an indication of at least one beam associated with the beam pair.

[0218] although Figure 11 Example blocks of process 1100 are shown, but in some aspects, process 1100 may include Figure 11 The blocks may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1100. Additionally or alternatively, two or more blocks of the blocks of process 1100 may be executed in parallel.

[0219] Figure 12is a diagram illustrating an example process 1200, for example, performed by a network node, in accordance with the present disclosure. The example process 1200 is an example in which a network node (eg, network node 110) performs operations associated with waveforms for synchronization and beam management of a secondary cell.

[0220] like Figure 12 As shown in FIG, in some aspects, process 1200 may include sending a synchronized RS of a PCell of a wireless network to a UE, the RS of the primary cell being configured to support synchronization with the PCell (block 1210). For example, a network node (e.g., using Figure 14 The transmitting component 1404 and / or the communication manager 1406 depicted in FIG may transmit a synchronization RS of a PCell of a wireless network to the UE, the RS of the primary cell being configured to support synchronization with the PCell, as described above.

[0221] like Figure 12 As further shown in FIG. 1 , in some aspects, process 1200 may include sending an indication to activate the SCell of the wireless network (block 1220). For example, a network node (e.g., using Figure 14 The sending component 1404 and / or the communication manager 1406 depicted in can send an indication of activating the SCell of the wireless network, as described above.

[0222] like Figure 12 As further shown in FIG. 1 , in some aspects, process 1200 may include transmitting an RS for an SCell, the RS for the SCell being associated with one or more of: a reduced candidate beam list for initial beam search relative to a candidate beam list for initial beam search that is not synchronized with the PCell, or a reduced time domain range for transmitting the RS for the SCell (block 1230). For example, a network node (e.g., using Figure 14 The sending component 1404 and / or the communication manager 1406 depicted in the figure can send the RS of the SCell, and the RS of the SCell is associated with one or more of the following: a reduced candidate beam list for initial beam search relative to a candidate beam list for initial beam search that is not synchronized with the PCell, or a reduced time domain range for sending the RS of the SCell, as described above.

[0223] like Figure 12 As further shown in FIG. 1 , in some aspects, process 1200 may include communicating via a secondary cell based at least in part on synchronization with the secondary cell (block 1240). Figure 14 The receiving component 1402, sending component 1404, and / or communication manager 1406 depicted in FIG can communicate via the secondary cell based at least in part on synchronization with the secondary cell, as described above.

[0224] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0225] In a first aspect, the RS of the SCell does not include one or more of the following: a PSS associated with a synchronized SSB without a PCell, an SSS associated with a synchronized SSB without a PCell, or one or more elements of a MIB associated with a synchronized SSB without a PCell.

[0226] In a second aspect, alone or in combination with the first aspect, the RS of the SCell includes one or more of a known sequence RS and transmit beam index information for a beam associated with the SCell.

[0227] In a third aspect, either alone or in combination with one or more of the first and second aspects, the known sequence comprises a sequence selected from a set of candidate sequences supporting different sequences for different devices used in the wireless network, and the known sequence is known at least in part based on an indication via the PCell.

[0228] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the transmit beam index information includes an indication of the timing of the transmit beam of the RS used to transmit the SCell or one or more of the transmit beam identifiers.

[0229] In the fifth aspect, alone or in combination with one or more of the first to fourth aspects, the transmit beam index information is indicated within one or more of: a PBCH portion of the RS of the SCell, a single OFDM symbol, or a selection of a sequence of symbols of the RS, the sequence being selected from a set of candidate sequences associated with different transmit beam index information.

[0230] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, selection of a sequence is based at least in part on an indication of mapping received via a PCell to indicate transmit beam index information.

[0231] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, the transmission of the RS to the SCell is associated with a first RS timing of the SCell, wherein the first RS timing of the SCell is associated with a first set of transmit beams, and wherein the second timing of the SCell is associated with a second set of transmit beams that is different from the first set of transmit beams.

[0232] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, the configuration of the RS of the SCell is at least partially based on an indication of the configuration of the RS of the SCell received via the PCell or an indication of the configuration within the communication protocol.

[0233] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the RS of the SCell is associated with a repetition of a transmit beam set, and the corresponding repetition of the transmit beam set supports receive beam scanning of the transmit beam set.

[0234] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, a highest frequency used for the PCell is lower than a lowest frequency used for the SCell.

[0235] In an eleventh aspect, alone or in combination with one or more of aspects one to ten, process 1200 includes receiving an indication of at least one beam associated with a beam pair, wherein communicating via the SCell using the beam pair is at least partially based on receiving the indication of at least one beam associated with the beam pair.

[0236] although Figure 12 Example blocks of process 1200 are shown, but in some aspects, process 1200 may include Figure 12 The blocks may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1200. Additionally or alternatively, two or more blocks of the blocks of process 1200 may be executed in parallel.

[0237] Figure 13 1 is a diagram of an example apparatus 1300 for wireless communication according to the present disclosure. Apparatus 1300 may be a UE, or a UE may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302, a sending component 1304, and / or a communication manager 1306, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1306 is a communication manager that is configured to communicate with one another. Figure 1 The described communication manager 140. As shown, the device 1300 can communicate with another device 1308, such as a UE or a network node (such as a CU, DU, RU, or base station), using a receiving component 1302 and a sending component 1304.

[0238] In some aspects, the apparatus 1300 may be configured to perform Figures 9 and 10 Additionally or alternatively, the apparatus 1300 may be configured to perform one or more of the processes described herein, such as Figure 11The process 1100. In some aspects, Figure 13 The apparatus 1300 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Figure 13 One or more of the components shown may be combined Figure 2 In one or more components described herein, the components may be implemented in a manner that is at least partially implemented as software stored in a memory. In addition or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and that can be executed by a controller or processor to perform the function or operation of the component.

[0239] The receiving component 1302 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the device 1308. The receiving component 1302 may provide the received communications to one or more other components of the device 1300. In some aspects, the receiving component 1302 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1300. In some aspects, the receiving component 1302 may include in conjunction with Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0240] The transmitting component 1304 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1308. In some aspects, one or more other components of the apparatus 1300 may generate communications and may provide the generated communications to the transmitting component 1304 for transmission to the apparatus 1308. In some aspects, the transmitting component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the apparatus 1308. In some aspects, the transmitting component 1304 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmitting component 1304 can be co-located with the receiving component 1302 in a transceiver.

[0241] The communications manager 1306 can support the operation of the receiving component 1302 and / or the sending component 1304. For example, the communications manager 1306 can receive information associated with configuring the receipt of communications by the receiving component 1302 and / or the sending of communications by the sending component 1304. Additionally or alternatively, the communications manager 1306 can generate and / or provide control information to the receiving component 1302 and / or the sending component 1304 to control the receipt and / or sending of communications.

[0242] The receiving component 1302 may obtain synchronization with a PCell of a wireless network. The receiving component 1302 may receive an indication to activate an SCell of the wireless network. The receiving component 1302 may receive a RS of the SCell, the receiving of the RS of the SCell being based at least in part on obtaining synchronization with the PCell, the receiving comprising one or more of the following operations: using a reduced candidate beam list for initial beam search relative to a candidate beam list for initial beam search without synchronization with the PCell; or using a reduced time domain range for receiving the RS of the SCell. The receiving component 1302 may obtain synchronization with the SCell based at least in part on the RS of the SCell. The communication manager 1306 may identify a beam pair for communicating via the SCell based at least in part on the RS of the SCell. The receiving component 1302 and / or the transmitting component 1304 may communicate via the SCell based at least in part on synchronization with the SCell and using the beam pair.

[0243] The transmitting component 1304 may transmit an indication of at least one beam associated with the beam pair, wherein communicating via the SCell using the beam pair is based at least in part on transmitting the indication of at least one beam associated with the beam pair.

[0244] Figure 13 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 13 The components shown may include additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 13 Two or more components shown may be implemented in a single component, or Figure 13 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 13 The set of (one or more) components shown in FIG can perform the operations described as being performed by Figure 13 One or more functions performed by another group of components shown in FIG.

[0245] Figure 141 is a diagram of an example apparatus 1400 for wireless communication according to the present disclosure. Apparatus 1400 may be a network node, or a network node may include apparatus 1400. In some aspects, apparatus 1400 includes a receiving component 1402, a sending component 1404, and / or a communication manager 1406, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1406 is a communication manager that is configured to communicate with one another. Figure 1 The described communication manager 150. As shown, the device 1400 can communicate with another device 1408, such as a UE or a network node (such as a CU, DU, RU, or base station), using a receiving component 1402 and a sending component 1404.

[0246] In some aspects, the apparatus 1400 may be configured to perform Figures 9 and 10 Additionally or alternatively, the apparatus 1400 may be configured to perform one or more of the processes described herein, such as Figure 12 The process 1200. In some aspects, Figure 14 The apparatus 1400 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, one or more components of the network node described. Figure 14 One or more of the components shown may be combined Figure 2 In one or more components described herein, the components may be implemented in a manner that is at least partially implemented as software stored in a memory. In addition or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and that can be executed by a controller or processor to perform the function or operation of the component.

[0247] The receiving component 1402 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the device 1408. The receiving component 1402 may provide the received communications to one or more other components of the device 1400. In some aspects, the receiving component 1402 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1400. In some aspects, the receiving component 1402 may include in conjunction with Figure 2One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the receiving component 1402 and / or the transmitting component 1404 may include or be included in a network interface. The network interface may be configured to obtain and / or output signals for the device 1400 via one or more communication links (such as a backhaul link, a midhaul link, and / or a fronthaul link).

[0248] The transmitting component 1404 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1408. In some aspects, one or more other components of the apparatus 1400 may generate communications and may provide the generated communications to the transmitting component 1404 for transmission to the apparatus 1408. In some aspects, the transmitting component 1404 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the apparatus 1408. In some aspects, the transmitting component 1404 may include in conjunction with Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the transmitting component 1404 can be co-located with the receiving component 1402 in a transceiver.

[0249] The communications manager 1406 can support the operation of the receiving component 1402 and / or the sending component 1404. For example, the communications manager 1406 can receive information associated with configuring the receipt of communications by the receiving component 1402 and / or the sending of communications by the sending component 1404. Additionally or alternatively, the communications manager 1406 can generate and / or provide control information to the receiving component 1402 and / or the sending component 1404 to control the receipt and / or sending of communications.

[0250] The transmitting component 1404 may transmit a synchronization RS of the PCell of the wireless network to the UE, the RS of the primary cell being configured to support synchronization with the PCell. The transmitting component 1404 may transmit an indication of activating the SCell of the wireless network. The transmitting component 1404 may transmit the RS of the SCell, the RS of the SCell being associated with one or more of the following: a candidate beam list for initial beam search that is reduced relative to a candidate beam list for initial beam search that is not synchronized with the PCell, or a reduced time domain range for transmitting the RS of the SCell. The receiving component 1402 and / or the transmitting component 1404 may communicate via the secondary cell based at least in part on synchronization with the secondary cell.

[0251] Receiving component 1402 may receive an indication of at least one beam associated with the beam pair, wherein communicating via the SCell using the beam pair is based at least in part on receiving the indication of at least one beam associated with the beam pair.

[0252] Figure 14 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 14 The components shown may include additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 14 Two or more components shown may be implemented in a single component, or Figure 14 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 14 The set of (one or more) components shown in FIG can perform the operations described as being performed by Figure 14 One or more functions performed by another group of components shown in FIG.

[0253] The following provides an overview of some aspects of the disclosure:

[0254] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: obtaining synchronization with a primary cell (PCell) of a wireless network; receiving an indication to activate a secondary cell (SCell) of the wireless network; receiving a reference signal (RS) of the SCell, wherein the reception of the RS of the SCell is based at least in part on obtaining synchronization with the PCell, the reception comprising one or more of the following operations: using a reduced candidate beam list for initial beam search relative to a candidate beam list for initial beam search that is not synchronized with the PCell; or using a reduced time domain range for receiving the RS of the SCell; obtaining synchronization with the SCell based at least in part on the RS of the SCell; identifying a beam pair for communicating via the SCell based at least in part on the RS of the SCell; and communicating via the SCell based at least in part on the synchronization with the SCell and using the beam pair.

[0255] Aspect 2: A method according to Aspect 1, wherein the RS of the SCell does not include one or more of the following: a primary synchronization signal (PSS) associated with a synchronization signal block (SSB) without synchronization of the PCell, a secondary synchronization signal (SSS) associated with an SSB without synchronization of the PCell, or one or more elements of a master information block (MIB) associated with an SSB without synchronization of the PCell.

[0256] Aspect 3: The method according to any one of aspects 1 to 2, wherein the RS of the SCell includes one or more of the following: a known sequence RS or transmit beam index information for a beam associated with the SCell.

[0257] Aspect 4: The method of aspect 3, wherein the known sequence comprises a sequence selected from a set of candidate sequences supporting different sequences for different devices of the wireless network, and wherein the known sequence is known at least in part based on an indication via the PCell.

[0258] Aspect 5: The method according to aspect 3, wherein the transmission beam index information includes one or more of the following: an indication of the timing of the transmission beam of the RS used to transmit the SCell or a transmission beam identifier.

[0259] Aspect 6: A method according to Aspect 3, wherein the transmit beam index information is indicated within one or more of: a physical broadcast channel (PBCH) portion of the RS of the SCell, a single orthogonal frequency division multiplexing (OFDM) symbol, or a selection of a sequence of symbols of the RS, the sequence being selected from a set of candidate sequences associated with different transmit beam index information.

[0260] Aspect 7: A method according to Aspect 6, wherein identifying the beam pair includes one or more of the following operations: decoding the transmit beam information based at least in part on a demodulation reference signal (DMRS) within one or more OFDM symbols of the transmit beam index information, or identifying the beam associated with the RS of the SCell based at least in part on the transmit beam information.

[0261] Aspect 8: The method according to aspect 6, wherein the selection of the sequence is based at least in part on an indication of mapping received via the PCell to indicate the transmit beam index information.

[0262] Aspect 9: A method according to any one of Aspects 1 to 8, wherein obtaining synchronization with the SCell includes one or more of the following operations: obtaining frequency synchronization for the SCell via the PCell, obtaining one or more elements of the MIB for the SCell via the PCell, using the RS of the SCell to reduce or omit frequency synchronization, or decoding a physical broadcast channel (PBCH) associated with a synchronization signal block (SSB) without synchronization of the PCell with a reduced complexity.

[0263] Aspect 10: A method according to any one of Aspects 1 to 9, wherein reception of the RS of the SCell is associated with a first RS timing of the SCell, wherein the first RS timing of the SCell is associated with a first set of transmit beams, and wherein the second timing of the SCell is associated with a second set of transmit beams different from the first set of transmit beams.

[0264] Aspect 11: A method according to any one of Aspects 1 to 10, wherein the configuration of the RS of the SCell is at least partially based on: an indication of the configuration of the RS of the SCell received via the PCell or an indication of the configuration within a communication protocol.

[0265] Aspect 12: The method according to any one of aspects 1 to 11, wherein the RS of the SCell is associated with repetitions of a transmit beam set, and wherein the respective repetitions of the transmit beam set support receive beam scanning of the transmit beam set.

[0266] Aspect 13: The method according to any one of aspects 1 to 12, wherein a highest frequency used for the PCell is lower than a lowest frequency used for the SCell.

[0267] Aspect 14: The method according to any one of Aspects 1 to 13 further includes: sending an indication of at least one beam associated with the beam pair, wherein communicating via the SCell using the beam pair is at least partially based on sending the indication of the at least one beam associated with the beam pair.

[0268] Aspect 15: A method of wireless communication performed by a network node, comprising: sending a synchronization reference signal (RS) of a primary cell (PCell) of a wireless network to a user equipment (UE), the RS of the primary cell being configured to support synchronization with the PCell; sending an indication to activate a secondary cell (SCell) of the wireless network; sending the RS of the SCell, the RS of the SCell being associated with one or more of: a reduced candidate beam list for initial beam search relative to a candidate beam list for initial beam search that is not synchronized with the PCell, or a reduced time domain range for sending the RS of the SCell; and communicating via the secondary cell at least in part based on synchronization with the secondary cell.

[0269] Aspect 16: A method according to Aspect 15, wherein the RS of the SCell does not include one or more of the following: a primary synchronization signal (PSS) associated with a synchronization signal block (SSB) without synchronization of the PCell, a secondary synchronization signal (SSS) associated with an SSB without synchronization of the PCell, or one or more elements of a master information block (MIB) associated with an SSB without synchronization of the PCell.

[0270] Aspect 17: The method according to any one of aspects 15 to 16, wherein the RS of the SCell includes one or more of the following: a known sequence RS and transmit beam index information for a beam associated with the SCell.

[0271] Aspect 18: The method of aspect 17, wherein the known sequence comprises a sequence selected from a set of candidate sequences supporting different sequences for different devices of the wireless network, and wherein the known sequence is known at least in part based on an indication via the PCell.

[0272] Aspect 19: The method according to aspect 17, wherein the transmission beam index information includes one or more of the following: an indication of the timing of the transmission beam of the RS used to transmit the SCell or a transmission beam identifier.

[0273] Aspect 20: A method according to Aspect 17, wherein the transmit beam index information is indicated within one or more of: a physical broadcast channel (PBCH) portion of the RS of the SCell, a single orthogonal frequency division multiplexing (OFDM) symbol, or a selection of a sequence of symbols of the RS, the sequence being selected from a set of candidate sequences associated with different transmit beam index information.

[0274] Aspect 21: The method according to aspect 20, wherein the selection of the sequence is based at least in part on an indication of mapping received via the PCell to indicate the transmit beam index information.

[0275] Aspect 22: A method according to any one of Aspects 15 to 21, wherein the transmission of the RS to the SCell is associated with a first RS timing of the SCell, wherein the first RS timing of the SCell is associated with a first set of transmission beams, and wherein the second timing of the SCell is associated with a second set of transmission beams different from the first set of transmission beams.

[0276] Aspect 23: A method according to any one of Aspects 15 to 22, wherein the configuration of the RS of the SCell is at least partially based on: an indication of the configuration of the RS of the SCell received via the PCell or an indication of the configuration within a communication protocol.

[0277] Aspect 24: The method according to any one of aspects 15 to 23, wherein the RS of the SCell is associated with repetitions of a transmit beam set, wherein the respective repetitions of the transmit beam set support receive beam scanning of the transmit beam set.

[0278] Aspect 25: The method according to any one of aspects 15 to 24, wherein a highest frequency used for the PCell is lower than a lowest frequency used for the SCell.

[0279] Aspect 26: The method according to any one of Aspects 15 to 25 further includes: receiving an indication of at least one beam associated with the beam pair, wherein communicating via the SCell using the beam pair is at least partially based on receiving the indication of the at least one beam associated with the beam pair.

[0280] Aspect 27: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in aspects 1 to 26.

[0281] Aspect 28: An apparatus for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 26.

[0282] Aspect 29: An apparatus for wireless communication, comprising at least one component for performing the method according to one or more of aspects 1 to 26.

[0283] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 26.

[0284] Aspect 31: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 26.

[0285] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the various aspects.

[0286] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of different forms of hardware and / or hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, no reference is made herein to specific software code to describe the operation and behavior of the systems and / or methods, as those skilled in the art will appreciate that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.

[0287] As used herein, "satisfying a threshold" may mean that a value is greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0288] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner not specifically described in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b, or c" is intended to encompass a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination of multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other arrangement of a, b, and c).

[0289] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly described as such. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more projects and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more projects connected with the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "group" and "cluster" are intended to include one or more projects and can be used interchangeably with "one or more". If only want to refer to a project, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to represent "at least partially based on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory and configured to: Acquire synchronization with the primary cell (PCell) of the wireless network; receiving an indication to activate a secondary cell (SCell) of the wireless network; and receiving a reference signal (RS) of the SCell, wherein the receiving of the RS of the SCell is based at least in part on obtaining synchronization with the PCell, the receiving comprising one or more of the following operations: using a reduced candidate beam list for initial beam search relative to a candidate beam list for initial beam search that is not synchronized with the PCell; or using a reduced time domain range for receiving the RS of the SCell; obtaining synchronization with the SCell based at least in part on the RS of the SCell; identifying a beam pair for communicating via the SCell based at least in part on the RS of the SCell; and Communicating via the SCell is performed based at least in part on the synchronization with the SCell and using the beam pair.

2. The UE according to claim 1, wherein the RS of the SCell does not include one or more of the following: a primary synchronization signal (PSS) associated with a synchronization signal block (SSB) without synchronization of the PCell, a Secondary Synchronization Signal (SSS) associated with an SSB that is not synchronized with the PCell, or One or more elements of a master information block (MIB) associated with a SSB without synchronization of the PCell.

3. The UE according to claim 1 , wherein the RS of the SCell comprises one or more of the following: Known sequence RS, or Transmit beam index information for the beam associated with the SCell.

4. The UE of claim 3 , wherein the known sequence comprises a sequence selected from a set of candidate sequences supporting different sequences for different devices of the wireless network, and The known sequence is known at least in part based on an indication via the PCell.

5. The UE according to claim 3, wherein the transmit beam index information comprises one or more of the following: an indication of the timing of the transmit beam of the RS used to transmit the SCell, or Transmit beam identifier.

6. The UE according to claim 3, wherein the transmit beam index information is indicated in one or more of the following: a physical broadcast channel (PBCH) portion of the RS of the SCell, A single Orthogonal Frequency Division Multiplexing (OFDM) symbol, or A sequence of symbols of the RS is selected from a set of candidate sequences associated with different transmit beam index information.

7. The UE of claim 6, wherein to identify the beam pair, the one or more processors are configured to: decoding the transmit beam information based at least in part on a demodulation reference signal (DMRS) within one or more OFDM symbols of the transmit beam index information, or A beam associated with the RS of the SCell is identified based at least in part on the transmit beam information.

8. The UE of claim 6, wherein the selection of the sequence is based at least in part on an indication of mapping received via the PCell to indicate the transmit beam index information.

9. The UE of claim 1 , wherein, to obtain synchronization with the SCell, the one or more processors are configured to: obtaining frequency synchronization for the SCell via the PCell, obtaining one or more elements of the MIB for the SCell via the PCell, and using the RS of the SCell to reduce or omit frequency synchronization, or A physical broadcast channel (PBCH) allocation is decoded with reduced complexity relative to a synchronization signal block (SSB) associated with the PCell.

10. The UE according to claim 1, wherein the reception of the RS of the SCell is associated with a first RS opportunity of the SCell, wherein the first RS opportunity of the SCell is associated with a first set of transmit beams, and The second timing of the SCell is associated with a second set of transmit beams that is different from the first set of transmit beams.

11. The UE according to claim 1 , wherein the configuration of the RS of the SCell is based at least in part on: an indication of the configuration of the RS of the SCell received via the PCell, or An indication of said configuration within a communications protocol.

12. The UE according to claim 1, wherein the RS of the SCell is associated with a repetition of a transmission beam set, and The corresponding repetition of the transmit beam set supports receive beam scanning of the transmit beam set. 13 . The UE according to claim 1 , wherein a highest frequency used for the PCell is lower than a lowest frequency used for the SCell.

14. The UE of claim 1 , wherein the one or more processors are further configured to: sending an indication of at least one beam associated with the beam pair, Wherein communicating via the SCell using the beam pair is based at least in part on sending the indication of the at least one beam associated with the beam pair.

15. A network node for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory and configured to: sending a synchronization reference signal (RS) of a primary cell (PCell) of a wireless network to a user equipment (UE), the RS of the primary cell being configured to support synchronization with the PCell; sending an indication to activate a secondary cell (SCell) of the wireless network; Sending a RS of the SCell, where the RS of the SCell is associated with one or more of the following: a reduced candidate beam list for initial beam search relative to a candidate beam list for initial beam search that is not synchronized with the PCell, or A reduced time domain range for transmitting the RS of the SCell; and Communicating via the secondary cell is based at least in part on synchronization with the secondary cell.

16. The network node according to claim 15, wherein the RS of the SCell does not include one or more of the following: a primary synchronization signal (PSS) associated with a synchronization signal block (SSB) without synchronization of the PCell, a Secondary Synchronization Signal (SSS) associated with an SSB that is not synchronized with the PCell, or One or more elements of a master information block (MIB) associated with a SSB without synchronization of the PCell.

17. The network node according to claim 15, wherein the RS of the SCell comprises one or more of the following: The sequence RS is known, and Transmit beam index information for the beam associated with the SCell.

18. The network node of claim 17, wherein the known sequence comprises a sequence selected from a set of candidate sequences that support different sequences for different devices of the wireless network, and The known sequence is known at least in part based on an indication via the PCell.

19. The network node according to claim 17, wherein the transmit beam index information comprises one or more of the following: an indication of the timing of the transmit beam of the RS used to transmit the SCell, or Transmit beam identifier.

20. The network node of claim 17, wherein the transmit beam index information is indicated in one or more of the following: a physical broadcast channel (PBCH) portion of the RS of the SCell, A single Orthogonal Frequency Division Multiplexing (OFDM) symbol, or A sequence of symbols of the RS is selected from a set of candidate sequences associated with different transmit beam index information.

21. The network node of claim 20, wherein the selection of the sequence is based at least in part on an indication of mapping received via the PCell to indicate the transmit beam index information.

22. The network node according to claim 15, wherein the transmission of the RS for the SCell is associated with a first RS opportunity of the SCell, wherein the first RS opportunity of the SCell is associated with a first set of transmit beams, and The second timing of the SCell is associated with a second set of transmit beams that is different from the first set of transmit beams.

23. The network node of claim 15, wherein configuration of the RS of the SCell is based at least in part on: an indication of the configuration of the RS of the SCell received via the PCell, or An indication of said configuration within a communications protocol.

24. The network node according to claim 15, wherein the RS of the SCell is associated with a repetition of a transmit beam set, The corresponding repetition of the transmit beam set supports receive beam scanning of the transmit beam set.

25. The network node of claim 15, wherein a highest frequency used for the PCell is lower than a lowest frequency used for the SCell.

26. The network node of claim 15, wherein the one or more processors are further configured to: receiving an indication of at least one beam associated with a beam pair identified using the RS, Wherein communicating via the SCell using the beam pair is based at least in part on receiving the indication of the at least one beam associated with the beam pair.

27. A method of wireless communication performed by a user equipment (UE), comprising: Acquire synchronization with the primary cell (PCell) of the wireless network; receiving an indication to activate a secondary cell (SCell) of the wireless network; and receiving a reference signal (RS) of the SCell, wherein the receiving of the RS of the SCell is based at least in part on obtaining synchronization with the PCell, the receiving comprising one or more of the following operations: using a reduced candidate beam list for initial beam search relative to a candidate beam list for initial beam search that is not synchronized with the PCell; or using a reduced time domain range for receiving the RS of the SCell; obtaining synchronization with the SCell based at least in part on the RS of the SCell; identifying a beam pair for communicating via the SCell based at least in part on the RS of the SCell; and Communicating via the SCell is performed based at least in part on the synchronization with the SCell and using the beam pair.

28. The method of claim 27, wherein the RS of the SCell does not include one or more of the following: a primary synchronization signal (PSS) associated with a synchronization signal block (SSB) without synchronization of the PCell, a Secondary Synchronization Signal (SSS) associated with an SSB that is not synchronized with the PCell, or One or more elements of a master information block (MIB) associated with a SSB without synchronization of the PCell.

29. A method of wireless communication performed by a network node, comprising: sending a synchronization reference signal (RS) of a primary cell (PCell) of a wireless network to a user equipment (UE), the RS of the primary cell being configured to support synchronization with the PCell; sending an indication to activate a secondary cell (SCell) of the wireless network; Sending a RS of the SCell, where the RS of the SCell is associated with one or more of the following: a reduced candidate beam list for initial beam search relative to a candidate beam list for initial beam search that is not synchronized with the PCell, or a reduced time domain range for transmitting the RS of the SCell; and Communicating via the secondary cell is based at least in part on synchronization with the secondary cell.

30. The method of claim 29, wherein the RS of the SCell does not include one or more of the following: a primary synchronization signal (PSS) associated with a synchronization signal block (SSB) without synchronization of the PCell, a Secondary Synchronization Signal (SSS) associated with an SSB that is not synchronized with the PCell, or One or more elements of a master information block (MIB) associated with a SSB without synchronization of the PCell.

Images