Secondary cell synchronization

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a wireless communication device may obtain synchronization with a primary cell of a wireless network. The wireless communication device may receive an indication to activate a secondary cell of the wireless network. The wireless communication device may receive a reference signal (RS) of the secondary cell. The wireless communication device may obtain synchronization with the secondary cell based at least in part on an offset between the RS of the secondary cell and a reference time of the primary cell, the reference time based at least in part on the synchronization with the primary cell. The wireless communication device may communicate via the secondary cell based at least in part on the synchronization with the secondary cell. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Patent Application No. 17 / 933,303, filed on September 19, 2022, entitled “SECONDARY CELL SYNCHRONIZATION” and assigned to the assignee of this patent application. The disclosure of the prior application is considered a part of this patent application and is incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for secondary cell synchronization. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth or 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 communications for wireless communication devices, such as user equipment (UE) or multiple UEs. The UE may communicate with the network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0006] The above 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, region, 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 spectral efficiency, reducing costs, improving services, utilizing new spectrum, and better integrating with other open standards by using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink, 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. Summary of the invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a wireless communication device. 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 method may include obtaining 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 being based at least in part on the synchronization with the PCell. The method may include communicating via the SCell based at least in part on the synchronization with the SCell.

[0008] Some aspects described herein relate to a method of 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 the PCell being configured to support synchronization with the PCell. The method may include sending an indication of activating an SCell of the wireless network. The method may include sending an RS of the SCell, the RS of the SCell being configured to support synchronization of the UE 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 being based at least in part on the synchronization with the PCell. The method may include communicating via the SCell based at least in part on the synchronization with the SCell.

[0009] Some aspects described herein relate to a wireless communication device for wireless communication. The wireless communication device 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 of activating an SCell of the wireless network. The one or more processors may be configured to receive an RS of the SCell. The one or more processors may be configured to 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 being based at least in part on the synchronization with the PCell. The one or more processors may be configured to communicate via the SCell based at least in part on the synchronization with the SCell.

[0010] 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, and the RS of the PCell is 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 an RS of the SCell, and the RS of the SCell is configured to support synchronization of the UE with the SCell based at least in part on an offset between the RS of the SCell and a reference time of the PCell, and the reference time is based at least in part on the synchronization with the PCell. The one or more processors may be configured to communicate via the SCell based at least in part on the synchronization with the SCell.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a wireless communication device. The instruction set, when executed by one or more processors of the wireless communication device, may enable the wireless communication device to obtain synchronization with a PCell of a wireless network. The instruction set, when executed by one or more processors of the wireless communication device, may enable the wireless communication device to receive an indication of activating an SCell of the wireless network. The instruction set, when executed by one or more processors of the wireless communication device, may enable the wireless communication device to receive the RS of the SCell. The instruction set, when executed by one or more processors of the wireless communication device, may enable the wireless communication device to 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 being based at least in part on the synchronization with the PCell. The instruction set, when executed by one or more processors of the wireless communication device, may enable the wireless communication device to communicate via the SCell based at least in part on the synchronization with the SCell.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to send a synchronization RS of a PCell of a wireless network to a UE, the RS of the PCell being configured to support synchronization with the PCell. The instruction set, when executed by one or more processors of the network node, may cause the network node to send an indication of activating the SCell of the wireless network. The instruction set, when executed by one or more processors of the network node, may cause the network node to send an RS of the SCell, the RS of the SCell being configured to support synchronization of the UE 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 being based at least in part on the synchronization with the PCell. The instruction set, when executed by one or more processors of the network node, may cause the network node to communicate via the SCell based at least in part on the synchronization with the SCell.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for obtaining synchronization with a PCell of a wireless network. The apparatus may include components for receiving an indication of activating an SCell of the wireless network. The apparatus may include components for receiving a RS of the SCell. The apparatus may include components for obtaining 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 being based at least in part on the synchronization with the PCell. The apparatus may include components for communicating via the SCell based at least in part on the synchronization with the SCell.

[0014] 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 the PCell 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 an RS of the SCell, the RS of the SCell being configured to support synchronization of the UE 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 being based at least in part on the synchronization with the PCell. The apparatus may include a component for communicating via the SCell based at least in part on the synchronization with the SCell.

[0015] 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 the drawings and description and as illustrated in the drawings and description.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose 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.

[0017] 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 non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices 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 devices incorporating 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 for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in a variety of devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0020] 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.

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

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

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

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

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

[0026] 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.

[0027] Fig. 9 is a diagram of an example associated with SCell synchronization according to the present disclosure.

[0028] Fig.10 is a diagram of an example associated with SCell synchronization according to the present disclosure.

[0029] Fig.11 is a diagram illustrating an example process performed, for example, by a wireless communication device according to the present disclosure.

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

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

[0032] Fig.14 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0033] The 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 interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should 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 it is 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 a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functionality, or structures 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 claim.

[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, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such 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 applied to other RATs, such as 3G RAT, 4G RAT, and / or 5G and beyond (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 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown 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, which means 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). For another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means 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, the network node 110 is or includes a network node (such as an RU) that communicates with the UE 120 via a radio access link. In some examples, the 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, the 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, the network node 110 (such as an aggregated 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. For example, the network node 110 may include 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, a RU, a CU, a mobility element of a network, a core network node, a network element, a 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 via various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

[0038] In some examples, the 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 ​​the network node 110 and / or a network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell 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. The 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 the 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 the network node 110. In some aspects, the term "base station" or "network node" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a number of 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 repeat the execution of 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] 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., network node 110 or UE 120) and transmit transmissions of data to a downstream node (e.g., UE 120 or 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, a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communications between the network node 110a and the UE 120d. 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, or the like.

[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, or 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] UE 120 may be dispersed throughout the 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 smart phone), 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 a 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, an 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 as 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 may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included in a housing that houses components of 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, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0045] In general, 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. RAT may be referred to as a radio technology or air interface, etc. Frequency may be referred to as a carrier or 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) may communicate directly (e.g., without using network node 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocol (e.g., may include vehicle-to-vehicle (V2V) protocol, vehicle-to-infrastructure (V2I) protocol, or vehicle-to-pedestrian (V2P) protocol) and / or mesh network. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0047] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., according to frequency or wavelength. For example, the 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 to 7.125 GHz) and FR2 (24.25 GHz to 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 "below 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 to 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 bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz to 24.25 GHz). The frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend the features of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0049] Considering the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 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. In addition, unless otherwise explicitly 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 or 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 (FR).

[0050] In some aspects, a wireless communication device (e.g., a network node 110 or a UE 120) may include a communication manager 140 or 150. As described in more detail elsewhere herein, the communication manager 140 or 150 may obtain 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) of the SCell; 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 being based at least in part on the synchronization with the PCell; and communicate via the SCell based at least in part on the synchronization with the SCell. Additionally or alternatively, the communication manager 140 or 150 may perform one or more other operations described herein.

[0051] In some aspects, the network node may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send a synchronization RS of a PCell of a wireless network to a UE, the RS of the PCell being configured to support synchronization with the PCell; send an indication to activate a SCell of the wireless network; send an RS of the SCell, the RS of the SCell being configured to support synchronization of the UE 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 being based at least in part on the synchronization with the PCell; and communicate via the SCell based at least in part on the synchronization with the SCell. 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 2 2 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 to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. 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 a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0054] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a group of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The 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., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where 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 to 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 further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0055] At the UE 120, a group of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a group of received signals (e.g., R received signals) to a group of modems 254 (e.g., R modems) (shown as modems 254a to 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 a 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 where 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 the 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 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, among other things. In some examples, one or more components of the UE 120 may be included in a housing.

[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 groups of antenna elements, and / or one or more antenna arrays, etc. An antenna panel, antenna group, group of antenna elements, and / or antenna array may include one or more antenna elements (in a single housing or multiple housings), a group of coplanar antenna elements, a group 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, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). 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, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent 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 perform the functions described herein (eg, reference Figures 9 to 14 ) any aspects of any of the methods described herein.

[0059] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the 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 perform operations described herein (e.g., with reference to Figures 9 to 14 ) any aspects of any of the methods described herein.

[0060] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other components of the SCell may perform one or more techniques associated with SCell synchronization, as described in more detail elsewhere herein. In some aspects, the wireless communication device described herein is a network node 110 (e.g., a relay node, a forwarding node, or a relay, etc.), is included in the network node 110, or includes Figure 2 In some aspects, the wireless communication device described herein is a UE 120, is included in a UE 120, or includes Figure 2 One or more components of UE 120 are shown.

[0061] For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Fig.11 Process 1100, Fig.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 that stores one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, conversion, and / or interpretation), may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Fig.11 Process 1100, Fig.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, etc.

[0062] Although Figure 2 The blocks in the 2000 and 2010 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.

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

[0064] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform 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. "Network entity" or "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).

[0065] An aggregated base station (e.g., an aggregated network node) may 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) may 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 distributed 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), and the like.

[0066] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed 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 the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed 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. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0067] Figure 33 is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated 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 disaggregated control units, such as a near-RT RIC 325 via an E2 link, or 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.

[0068] Each of these units (including CU 310, DU 330, RU 340) and near-RT RIC 325, non-RTRIC 315 and SMO framework 305) may include or be coupled to one or more interfaces, which are configured to receive or send signals, data or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these 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 a transmission medium. In some examples, each of these units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, and the wireless interface may include a receiver, a transmitter or a transceiver (such as an RF transceiver), which is configured to receive signals or send signals to one or more of the other units via a wireless transmission medium, or both.

[0069] 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, etc. Each control function may be implemented using an interface that is 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 specific 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 CU310 may be implemented to communicate with the DU 330 for network control and signaling.

[0070] 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 high physical (PHY) layers, at least in part according to a functional split (such as a functional split defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may further host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0071] 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 (such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc.) based on a functional split such as a lower layer functional split (e.g., a functional split defined by 3GPP). 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 specific implementations, real-time and non-real-time aspects of control plane communications 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).

[0072] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an 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 an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an 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.

[0073] The non-RT RIC 315 may 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 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as 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.

[0074] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function 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 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

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

[0076] Figure 4 is a diagram illustrating an example 400 of dual connectivity according to the present disclosure. Figure 4The example shown is for Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA)-NR Dual Connectivity (ENDC) mode. In ENDC mode, UE 120 communicates using LTE RAT on a Master Cell Group (MCG), and UE 120 communicates using NR RAT on a SCell Group (SCG). However, the various 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 the first RAT and the SCG is associated with one of the first RAT or the 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.

[0077] like Figure 4 As shown, UE 120 may communicate with both eNBs (e.g., 4G network node 110) and gNBs (e.g., 5G network node 110), and the eNBs and gNBs may communicate 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) (e.g., directly or indirectly). Figure 4 In the present invention, PGW and SGW are collectively referred to as P / SGW. In some aspects, the eNB and gNB may be co-located at the same network node 110. In some aspects, the eNB and gNB may be included in different network nodes 110 (eg, may not be co-located).

[0078] like Figure 4As further shown, in some aspects, a wireless network that permits operation in 5G NSA mode may permit such operation using an MCG for a first RAT (e.g., LTE RAT or 4G RAT) and an SCG for a second RAT (e.g., NR RAT or 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 base station 110 (e.g., an eNB) and an NR base station 110 (e.g., a gNB) (e.g., in the case of ENDC or NEDC), or may be concurrently connected to one or more base stations 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 a FR1 band), and an SCG may be associated with a second frequency band (e.g., a mmWave band and / or a FR2 band).

[0079] 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 specific 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, the DRB may be split on the uplink from the primary path to the MCG or SCG. The DRB that is split in the uplink may 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 may use the DRB to send data to the MCG or SCG.

[0080] In some networks, the MCG and the SCG may be associated with different 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, etc. 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 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.

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

[0082] Figure 5 is a diagram illustrating an example 500 of a synchronization signal (SS) hierarchy according to the present disclosure. Figure 5 As shown, 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, 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), such as Figure 5 In some aspects, the SS burst set 505 may have a fixed or dynamic length (which may be 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.

[0083] In some aspects, the 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 transmissions 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, the 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, the SSB 515 may be referred to as an SS / PBCH block.

[0084] In some aspects, the symbols of SSB 515 are consecutive, 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 sent 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 sent in non-contiguous radio resources.

[0085] In some aspects, the SS burst 510 may have a burst periodicity, and the SSB 515 of the SS burst 510 may be sent by a wireless node (e.g., 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 sent 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.

[0086] 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 cell timing for a cell (e.g., a serving cell) via which the SSB 515 is received.

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

[0088] 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 a UE 120 communicating with a network node 110 in a wireless network (eg, 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 node and control node, between IAB child node and IAB parent node, and / or between scheduled node and scheduling node). In some aspects, UE 120 and network node 110 may be in a connected state (e.g., RRC connected state).

[0089] like Figure 6 As 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. Figure 6As shown in example 600, the RS may be configured to be sent 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)).

[0090] 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. In order 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 transmit 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 process 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 measurement results 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 RS in example 600 may include CSI-RS and / or SSB for beam management in a similar manner as described above.

[0091] 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 procedure (e.g., P2 beam management). The second beam management procedure may be referred to as a beam refinement procedure, a network node beam refinement procedure, a TRP beam refinement procedure, and / or a transmit beam refinement procedure. Figure 6As shown in example 610, the RS may be configured to be transmitted from the network node 110 to the UE 120. The RS may be configured to be non-periodic (e.g., using DCI). The second beam management process may include the 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 the network node 110 (e.g., determined at least in part based on the measurement results reported by the UE 120 in conjunction with the first beam management process). The network node 110 may transmit the RS using each of the one or more transmit beams used for beam management. The UE 120 may measure each RS using a single (e.g., the same) receive beam (e.g., determined at least in part based on the measurement performed in conjunction with the first beam management process). The second beam management process may enable the network node 110 to select the best transmit beam based at least in part on the measurement results of the RS reported by the UE 120 (e.g., measured by the UE 120 using a single receive beam). The RS in example 610 may include CSI-RS and / or SSB for beam management in a similar manner as described above.

[0092] 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 sent from the network node 110 to the UE 120. The RS may be configured to be non-periodic (e.g., using DCI). The third beam management process may include the network node 110 sending the one or more RSs using a single transmit beam (e.g., determined at least in part based on measurement results reported by the UE 120 in conjunction with the first beam management process and / or the second beam management process). In order to enable the UE 120 to perform receive beam scanning, the network node may use the transmit beam to send the RS multiple times (e.g., using repetitions) within the same RS resource set, so that the UE 120 can 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 the 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 the network node 110 and / or the UE 120 to select the best receive beam based at least in part on reported measurements received from the UE 120 (e.g., reported measurements of RSs of transmit beams received from the UE using the one or more receive beams). The RSs in example 620 may include CSI-RS and / or SSBs for beam management in a similar manner as described above.

[0093] In some networks, a beam management process may be performed when a connection is established with a network on a cell or cell group (or reconnected with the network). Additionally, a beam management process may be performed when already connected to a network on a cell or cell group. The amount of time to perform the beam management process when establishing the connection may be longer than the amount of time to perform the beam management process when already connected to the network on the cell or cell group. In some networks, the amount of time to perform the beam management process 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 a situation 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, thereby meeting the throughput required for data communicated via the network. However, when the SCG is activated, the UE may need to perform a beam management process before being scheduled to carry data. The beam management process may require an amount of time that causes the data to fail to meet the latency requirements.

[0094] 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).

[0095] As indicated above, Figure 6 is provided as an example of a beam management process. Other examples of beam management processes may be found with respect to 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.

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

[0097] 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 house or building to provide coverage to areas on the opposite side of the wall from a network node 110 that uses sub-6 GHz radio waves to communicate. 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 that makes up the wall). Some techniques and devices described herein use millimeter wave repeaters (in Figure 7 In an example of a first relay and a second relay, the network node 110 may be used to increase the coverage area of ​​the network node 110 and / or to extend the coverage to UEs 120 that do not have line of sight to the network node 110 (eg, due to obstacles). Figure 7 In the example of , it includes UE 120a and UE 120b).

[0098] 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 repeater blocks the link between the first repeater and UE 120b or otherwise reduces the quality of the link. However, there are no obstacles or fewer obstacles between the second repeater and UE 120b, and therefore, it is possible that the communication between the second repeater and UE 120b will have a higher quality than the communication between network node 110 and UE 120b or between the first repeater 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 repeater or a layer 3 repeater.

[0099] A millimeter wave repeater (sometimes referred to herein as a repeater) may perform directional communication by using beamforming to communicate with a network node 110 via a first beam pair (e.g., a backhaul beam pair on a backhaul link with the network node 110) and to communicate with a 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, a first repeater may communicate with the network node 110 via a first beam pair and may communicate with a UE 120a via a second beam pair. Similarly, a second repeater may communicate with the network node 110 via a first beam pair and may communicate with a UE 120a via a second beam pair. A beam pair may refer to a Tx beam used by a first device for transmission and an Rx beam used by a second device for receiving information sent by the first device via the Tx beam.

[0100] As shown by reference numeral 705, the network node 110 may use a beam scanning process to send communications over time via multiple beams (e.g., using time division multiplexing (TDM)). As shown by reference numeral 710, the first repeater may receive communications via the Rx beam of the first repeater. As shown by reference numeral 715, the first repeater may relay each communication received via multiple Tx beams of the first repeater (e.g., using TDM). As used herein, relaying a communication may refer to sending 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 the received communication may refer to sending the received communication after decoding the received communication and / or modifying the information carried in the received communication. In some aspects, the received communication may be relayed using different time resources, different frequency resources, and / or different spatial resources (e.g., different beams) than the time resources, frequency resources, and / or spatial resources in which the communication was received to send 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 sent to network node 110. UE 120a may then send the communication to the first relay for relaying to network node 110.

[0101] 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 send the amplified millimeter wave signal to one or more UEs 120 (e.g., shown as UE 120f). 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 an analog mmW signal without performing analog-to-digital conversion of 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.

[0102] In some networks, multiple relays may be used in a communication link between a UE and a network node, the communication link comprising 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 a dual connectivity network), 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.

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

[0104] Figure 8 800 is a diagram illustrating an example of communicating using a PCell and a 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 a 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 FR and the second FR are different and / or the first RAT and the second RAT are different).

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

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

[0107] The network node may release the SCell for the SCell inactive time 815. The network node may release the SCell to save computation, 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), wherein the increased amount of data meets a threshold (e.g., exceeds the throughput capacity of the PCell).

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

[0109] 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 some functionality). For example, the network node may not send "always on" signals, such as SSB or other RS ​​that the UE can use to synchronize with the network node on the SCell. In some networks, the SCell may be active for sporadic and / or short duration sessions with bursty activity patterns, such as Figure 8 As shown.

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

[0111] Smart repeaters (e.g., for sub-THz) may have functional parts such as RedCap UE (RC UE) for PCell connectivity (e.g., to deliver out-of-band control messages, reports and / or feedback, etc.), wideband analog amplification and forwarding (AF) functionality for data forwarding, dedicated narrowband local SSB for complementary time synchronization and beam refinement processing and / or synchronized RS transmission and / or reception capabilities on SCell (e.g., using sub-THz carrier frequencies). 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 synchronized RS and / or SSB microburst scheduling.

[0112] In some networks, both AP and RP are intelligent repeaters. 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), an RP is involved. AP and RP may have the same functionality in concept, but have some differences in hardware and capabilities. AP and RP may be referred to by different names to identify usage. For example, AP may be used to indicate an intelligent repeater (e.g., a network node and / or a wireless communication device) with a direct connection (e.g., a service link) to a UE, and RP may be used to indicate an intelligent repeater with 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.

[0113] As discussed herein, when the SCell or PCell operates with different FRs and / or with different RATs or with different delays 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 fact that the SCell link does not utilize an "always on" signal or other synchronization signal to remain active when not actively communicating via the SCell, the UE and / or any smart repeater along the communication link may need to be synchronized before starting communication to avoid communication errors that may have been caused by timing errors. However, performing a full synchronization process and / or a beam management process may consume an amount of time that causes the data to fail to meet the delay 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 cause communication errors when the UE synchronizes with the network node via the SCell.

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

[0115] 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 an RS of a PCell). The wireless communication device may receive an indication of activating an SCell of a wireless network, and may receive an 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 a 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 may have been consumed by performing a full synchronization process on the SCell.

[0116] 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 progressive 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 having a direct link with the UE sends a synchronization RS based at least in part on downlink synchronization of the AP).

[0117] 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 to apply to the SCell.

[0118] In some aspects, the PCell time tracking loop (TTL) and PCell timing may be used as a coarse timing reference for the SCell. In some aspects, a separate TTL is not 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 may 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.

[0119] 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 manner: according to link activation (e.g., an indication of activating the SCell), according to a predefined time period and / or periodicity along a long-term persistent 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.

[0120] In some aspects, a time synchronization session may be based at least in part on a synchronization session configuration for a receiving side (and a transmitting side for intermediate hops), which is indicated and / or executed via a PCell link and with reference to PCell timing. In some aspects, a time synchronization session may use PCell timing information for coarse time synchronization and / or reference to define a time search boundary and / or time uncertainty for a SCell local synchronization session in accordance with 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 reception time for the SCell synchronization session based at least in part on PCell timing, time slots, and / or control signaling time slots. In this way, a wireless communication device may not have an independent TTL on the SCell, and may obtain SCell time synchronization based at least in part on PCell coarse time and a relative timing offset estimated locally. In some aspects, a progressive synchronization approach may be used to establish overall time synchronization for each multi-hop link.

[0121] 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.

[0122] In some aspects, a relative offset in a SCell time unit (e.g., symbol and / or time slot) may be provided to an SCell control application for communications that are assumed to be scheduled via the SCell. For example, each PCell time slot and / or symbol may include multiple SCell time 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. The 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, etc.

[0123] 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 successful 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 before the 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., this may be related to some abnormal dynamics involving the PCell channel and / or communication link) or the beam switching of the PCell.

[0124] 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.

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

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

[0127] In addition, using PCell synchronization for SCell synchronization can support faster SCell link activation and deactivation for eligible UEs with low complexity, low power and low latency penalties to support burst activity mode to improve power efficiency. For example, a wireless communication device can obtain synchronization of the SCell faster than using only SCell signaling. In this way, the use of SCell for intermittent, burst and / or high throughput communications when temporary supplementation of PCell is required can be optimized for efficiency of power resource consumption.

[0128] 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 strong reliance on lower frequency bands).

[0129] Fig. 9 9 is a diagram of an example 900 associated with SCell synchronization according to the present disclosure. Fig. 9As shown, a network node (e.g., network node 110, CU, DU, and / or RU) may communicate with a wireless communication device (WCD) (e.g., UE 120, network node 110 such as RP, AP, and / or forwarding node). In some aspects, the network node and the wireless communication device may be part of a wireless network (e.g., wireless network 100). The network node and the wireless communication device may be in a Fig. 9 The operations shown are performed with a wireless connection already established.

[0130] As indicated by reference numeral 905, the network node may send configuration information, and the wireless communication device may receive the configuration information. In some aspects, the wireless communication device 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 selection by the wireless communication device (e.g., known to the wireless communication device and / or previously indicated by the network node or other network device) and / or explicit configuration information for the wireless communication device to use to configure the wireless communication device, etc.

[0131] In some aspects, the configuration information may indicate that the wireless communication device is to send an indication of support for SCell synchronization based at least in part on PCell synchronization.

[0132] In some aspects, the network node may send the configuration information via a PCell connected to the wireless communication device. In some aspects, the PCell may operate using a relatively lower FR compared to the SCell. The PCell may be part of an MCG.

[0133] 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.

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

[0135] As shown by reference numeral 915, the wireless communication device may receive the RS of the PCell and the network node may send the RS of the PCell. In some aspects, the RS of the PCell may include SSB and / or CSI-RS. In some aspects, the RS may include other types of RS, such as DMRS and / or tracking reference signal (TRS) within data communication.

[0136] As indicated by reference numeral 920, the wireless communication device may obtain synchronization with the PCell. For example, the wireless communication device may use the RS of the PCell to synchronize the wireless communication device in the time domain and / or the frequency domain.

[0137] As shown by reference numeral 925, the wireless communication device may receive an indication to activate the SCell, and the network node may send an indication to activate the SCell. The SCell may be part of a wireless network associated with the PCell. In some aspects, the SCell may be part of the SCG. In some aspects, the SCell may be associated with a frequency bandwidth higher than the frequency bandwidth of the PCell. This may allow the PCell to have higher reliability than the SCell.

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

[0139] As shown by reference numeral 930, a wireless communication device may receive a configuration for synchronization with a SCell, and a network node may send a configuration for synchronization with a SCell. For example, the configuration for synchronization with a SCell may indicate one or more parameters for using a reference time of a 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.

[0140] As indicated by reference numeral 935, the wireless communication device may receive an indication of a reference time of the PCell for synchronization of the SCell, and the network node may send an indication of 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 by an indicated amount from any of these items, and the like.

[0141] 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.

[0142] As shown in reference numeral 940, the wireless communication device may receive the RS of the SCell, and the network node may send the RS of the SCell. In some aspects, the RS of the SCell may be used to support determining a time offset of a jump of a communication link between the wireless communication device and the network node. In some aspects, the RS of the SCell may include SSB or another RS ​​type. In some aspects, the wireless communication device may receive the RS of the SCell within a time window that is at least partially based on an offset and / or configuration with the SCell.

[0143] In some aspects, the wireless communication device may receive the RS of the SCell via an air path including multiple hops. For example, the RS of the SCell may be forwarded by an RP and / or AP between a network node and the wireless communication device. In some aspects, the RP and / or AP may modify and / or resend the RS of 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 of the SCell.

[0144] In some aspects, receiving the RS of the SCell includes receiving an RS burst received during a synchronization session or received during a beam management session (e.g., a transmission that occupies less time resources than all time resources of a time slot or subframe). 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 specific synchronization session or beam management session, or a hop specific specific synchronization session or beam management session, and the like.

[0145] As indicated by reference numeral 945, the wireless communication device 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 wireless communication device may use the reference time of the PCell as a 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.

[0146] In some aspects, the wireless communication device may obtain the reference time of the PCell via an indication of the reference time as described in conjunction with reference numeral 935. In some aspects, the wireless communication device may obtain the reference time via observation at the wireless communication device (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.

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

[0148] In some aspects, the network node may acquire synchronization with the wireless communication device based at least in part on the wireless communication device acquiring synchronization with the network node. In some aspects, the wireless communication device may indicate that the wireless communication device has acquired synchronization with the network node and the process may be part of the network node acquiring synchronization with the wireless communication device.

[0149] As shown by reference numeral 950, the wireless communication device may send an indication of whether the wireless communication device is synchronized with the SCell, and the network node may receive an indication of whether the wireless communication device is synchronized with the SCell. For example, the wireless communication device may send an indication of whether the wireless communication device is synchronized with the SCell via the 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 when the wireless communication device indicates synchronization with the SCell. Alternatively, the network node may schedule communication via the SCell only when the wireless communication device has not yet indicated a failure to synchronize with the SCell.

[0150] In some aspects, the indication of whether a wireless communication device is synchronized with a SCell applies within a time duration that expires based at least in part on one or more of: 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, a beam switch for the PCell, a change in the TTL to satisfy a threshold and / or after a configured amount of time, and the like.

[0151] As shown by reference numeral 955, a wireless communication device may receive a scheduling message for communication using an SCell, and a network node may send and receive a scheduling message for communication using an SCell. 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 time slot of the multiple time slots of the SCell is included in the time slot of the PCell, which time slot of the PCell is scheduled for communication via the SCell.

[0152] As indicated by reference numeral 960, the wireless communication device and the network node may communicate via the second cell. For example, the network node may transmit data that is not suitable for the throughput of the PCell, and the wireless communication device may receive data that is not suitable for the throughput of the PCell.

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

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

[0155] Based at least in part on the use of 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. Additionally or alternatively, the progressive synchronization approach supports low latency and low power multi-hop link synchronization with smart repeaters with PCell-based out-of-band control. In addition, the use of PCell synchronization for SCell synchronization can support faster SCell link activation and deactivation with low complexity, low power, and low latency penalties for qualified wireless communication devices to support burst activity modes to improve power efficiency. In some aspects, the use of PCell synchronization for SCell synchronization can expand a range of use cases and scenarios in which SCells with relatively high FRs can be used with reasonable specific implementation and deployment implications. In addition, the use of PCell synchronization for SCell synchronization can accelerate initial high FR (e.g., sub-THz) deployments (e.g., with a strong reliance on lower frequency bands).

[0156] As indicated above, Fig. 9 are provided as examples. Other examples can be found in relation to Fig. 9 The examples described are different.

[0157] Fig.10 1 is a diagram of an example 1000 associated with SCell synchronization according to the present disclosure. Fig.10 As shown, a network node (e.g., network node 110, CU, DU, and / or RU) may communicate with one or more wireless communication devices (e.g., UE 120, RP, AP, and / or forwarding node). In some aspects, the network node and the one or more wireless communication devices may be part of a wireless network (e.g., wireless network 100). The one or more wireless communication devices and the network node may be in a Fig.10 The illustrated operations are preceded by an established wireless connection.In some aspects, one or more wireless communication devices and network nodes may have established synchronization with a PCell for communication.

[0158] like Fig.10 As shown, the network node, RP, AP, and UE may have a time grid 1005. As shown in the time grid 1005, the network node may initiate both PCell communication and SCell communication in a substantially synchronized manner. However, the PCell communication and the SCell communication may arrive at one or more wireless communication devices at different times (e.g., in a non-synchronized manner). For example, at the RP, a time offset of T1 separates the reception of the PCell communication and the SCell communication. Similarly, a time offset of T2 separates the reception of the PCell communication and the SCell communication at the AP, and a time offset of T2 separates the reception of the PCell communication and the SCell communication at the UE.

[0159] In some aspects, the network node and one or more wireless communication devices may be synchronized on PCell downlink timing (tracked using local PCell receive downlink timing, which may be used as a coarse or initial timing reference for the SCell). In some aspects, ppm offsets may be tracked. For example, the SCell frequency offset may be corrected and / or known, and the sampling rate may be adjusted to avoid cumulative time drift (e.g., assuming the same phase-locked loop (PLL) where the PCell and SCell use the same clock, a reference for the PCell and SCell, and a quasi-static channel where UE mobility meets a threshold for the PCell and SCell).

[0160] In some aspects, PCell and SCell (e.g., sub-THz) propagation may travel via different channels (e.g., for AP and UE) and may have a relative time offset. For example, PCell downlink local receive timing may be shifted relative to the PCell local receive timing grid. This relative time offset may be estimated and / or tracked by the SCell downlink synchronization process during an active traffic offload session.

[0161] like Fig.10 As shown, the network node, RP, AP, and UE may communicate RS 1010 to obtain synchronization. For example, the network node may send RS to the RP for the RP to estimate the time offset T1 between the PCell and the SCell. The RP may send RS to the AP with the offset T1 between the RS of the PCell and the RS of the SCell. The AP may determine the offset T2 between the PCell and the SCell. The AP may send RS to the UE with the offset T2 between the PCell and the SCell. The UE may determine the offset T3 between the PCell and the SCell based at least in part on the RS from the AP.

[0162] In some aspects, T1 may be estimated based at least in part on the selected network node SSB.The SCell time grid may be synchronized at the RP side by SCell reception (downlink) being the time of PCell reception plus or minus T1.

[0163] In some aspects, T2 may be estimated based at least in part on the selected RP SSB.The SCell time grid may be synchronized at the AP side by the time of SCell reception (downlink) being the time of AP reception of the PCell plus or minus T2.

[0164] In some aspects, T3 may be estimated based at least in part on the selected AP SSB.The SCell time grid may be synchronized at the UE side by the time of SCell reception (downlink) being the time of UE reception of the PCell plus or minus T3.

[0165] like Fig.10 As shown, the network nodes, RP, AP, and UE may communicate data via PCell and SCell 1015. In some aspects, each of the RP, AP, and UE may apply T1, T2, or T3, respectively, as a timing offset relative to the PCell for receiving data via the SCell.

[0166] As indicated above, Fig.10 are provided as examples. Other examples can be found in relation to Fig.10 The examples described are different.

[0167] Fig.11 is a diagram illustrating an example process 1100, for example, performed by a wireless communication device according to the present disclosure. The example process 1100 is an example in which a wireless communication device (eg, UE 120 or network node 110) performs operations associated with SCell synchronization.

[0168] like Fig.11 As shown, in some aspects, process 1100 may include obtaining synchronization with a PCell of a wireless network (block 1110). For example, the wireless communication device (e.g., using Fig.13 The depicted communication manager 140 or 150 and / or communication manager 1308) may obtain synchronization with a PCell of a wireless network, as described above.

[0169] like Fig.11 As further shown, in some aspects, process 1100 may include receiving an indication to activate an SCell of the wireless network (block 1120). For example, the wireless communication device (eg, using Fig.13 The depicted communications manager 140 or 150 and / or receiving component 1302) can receive an indication to activate a SCell for the wireless network, as described above.

[0170] like Fig.11 As further shown, in some aspects, process 1100 may include receiving a RS for the SCell (block 1130). For example, the wireless communication device (eg, using Fig.13 The depicted communication manager 140 or 150 and / or receiving component 1302) can receive the RS for the SCell, as described above.

[0171] like Fig.11As further shown, in some aspects, process 1100 may include obtaining 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 being based at least in part on the synchronization with the PCell (block 1140). Fig.13 The depicted communication manager 140 or 150 and / or communication manager 1308) 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 being based at least in part on the synchronization with the PCell, as described above.

[0172] like Fig.11 As further shown, in some aspects, process 1100 may include communicating via the SCell based at least in part on the synchronization with the SCell (block 1150). Fig.13 The depicted communication manager 140 or 150 and / or receiving component 1302, sending component 1304, and / or communication manager 1308) can communicate via the SCell based at least in part on the synchronization with the SCell, as described above.

[0173] 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.

[0174] In a first aspect, the PCell is associated with a first frequency bandwidth that is lower than a frequency bandwidth of the SCell.

[0175] In a second aspect, alone or in combination with the first aspect, receiving the RS of the SCell includes receiving the RS of the SCell via an air path including a plurality of hops.

[0176] In a third aspect, alone or in combination with one or more of the first and second aspects, the reference time of the PCell is based at least in part on a frequency tracking loop of the PCell or a radio access network time unit of the PCell.

[0177] In a fourth aspect, alone or in combination with one or more of the first to third aspects, receiving the RS of the SCell includes one or more of the following: receiving an RS burst received during a synchronization session, or receiving an RS burst received during a beam management session.

[0178] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the synchronization session or the beam management session is associated with: a frequency range-specific synchronization session or beam management session, a secondary cell-specific specific synchronization session or beam management session, or a jump-specific specific synchronization session or beam management session.

[0179] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, process 1100 includes sending, via the PCell, a configuration for the synchronization with the SCell.

[0180] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the configuration schedules the RS of the SCell, or wherein the configuration includes the indication to activate the SCell.

[0181] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, obtaining the synchronization with the SCell is based at least in part on a configured periodicity of synchronizing the SCell or a triggering event during ongoing communication via the SCell.

[0182] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, process 1100 includes receiving an indication of the reference time for the PCell.

[0183] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the reference time of the PCell is based at least in part on one or more of the following: a downlink time slot index of the PCell, a symbol within a downlink time slot of the PCell, a downlink time slot index carrying control information associated with the SCell, a scheduling event on the PCell, or a time unit offset by an indicated amount from any of the above.

[0184] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, communicating via the SCell includes: receiving a scheduling message for communication using the SCell, the scheduling message referring to the timing in the PCell, and wherein receiving the scheduling message includes: receiving an indication of a first time unit of the PCell, and receiving an indication of a second time unit of the SCell within the first time unit.

[0185] In a twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, process 1100 includes sending an indication of whether the wireless communication device is synchronized with the SCell.

[0186] In the thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the indication indicates that the wireless communication device is synchronized with the SCell, and wherein communication via the SCell is at least partially based on sending the indication that the wireless communication device is synchronized with the SCell.

[0187] In a fourteenth aspect, either alone or in combination with one or more of aspects one to thirteen, the indication of whether the wireless communication device is synchronized with the SCell applies over a time duration that expires based at least in part on one or more of: 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 the PCell, a beam switch for the PCell, or a change in the timing tracking loop that satisfies a threshold.

[0188] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the wireless communication device includes a UE or a forwarding node.

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

[0190] Fig.12 is a diagram illustrating an example process 1200 performed, for example, 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 SCell synchronization.

[0191] like Fig.12 As shown, in some aspects, process 1200 may include sending a synchronization RS of a PCell of a wireless network to a UE, the RS of the PCell being configured to support synchronization with the PCell (block 1210). For example, the network node (eg, using Fig.14 The depicted communication manager 150 and / or transmitting component 1404) can transmit to the UE a synchronization RS of a PCell of a wireless network, the RS of the PCell being configured to support synchronization with the PCell, as described above.

[0192] like Fig.12 As further shown, in some aspects, process 1200 may include sending an indication to activate the SCell of the wireless network (block 1220). For example, the network node (eg, using Fig.14The depicted communications manager 150 and / or transmitting component 1404 can transmit an indication to activate the SCell of the wireless network, as described above.

[0193] like Fig.12 As further shown, in some aspects, process 1200 may include sending a RS for the SCell, the RS for the SCell being configured to support synchronization of the UE with the SCell based at least in part on an offset between the RS for the SCell and a reference time for the PCell, the reference time being based at least in part on the synchronization with the PCell (block 1230). For example, the network node (e.g., using Fig.14 The depicted communication manager 150 and / or sending component 1404) may send the RS of the SCell, and the RS of the SCell is configured to support synchronization of the UE with the SCell based at least in part on an offset between the RS of the SCell and a reference time of the PCell, and the reference time is at least in part based on the synchronization with the PCell, as described above.

[0194] like Fig.12 As further shown, in some aspects, process 1200 may include communicating via the SCell based at least in part on the synchronization with the SCell (block 1240). For example, the network node (eg, using Fig.14 The depicted communication manager 150 and / or receiving component 1402, sending component 1404, and / or communication manager 1408) can communicate via the SCell based at least in part on the synchronization with the SCell, as described above.

[0195] 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.

[0196] In a first aspect, the PCell is associated with a first frequency bandwidth that is lower than a frequency bandwidth of the SCell.

[0197] In a second aspect, alone or in combination with the first aspect, transmitting the RS of the SCell includes: transmitting the RS of the SCell via an air path including a plurality of hops.

[0198] In a third aspect, alone or in combination with one or more of the first and second aspects, the reference time of the PCell is based at least in part on a frequency tracking loop of the PCell or a radio access network time unit of the PCell.

[0199] In a fourth aspect, alone or in combination with one or more of the first to third aspects, sending the RS of the SCell includes one or more of the following: sending an RS burst sent during a synchronization session, or sending an RS burst sent during a beam management session.

[0200] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the synchronization session or the beam management session is associated with: a frequency range-specific synchronization session or beam management session, a secondary cell-specific specific synchronization session or beam management session, or a jump-specific specific synchronization session or beam management session.

[0201] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, process 1200 includes sending, via the PCell, a configuration for the synchronization with the SCell.

[0202] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the configuration schedules the RS of the SCell, or wherein the configuration includes the indication to activate the SCell.

[0203] In an eighth aspect, either alone or in combination with one or more of aspects one to seven, the RS of the SCell is configured to support synchronization of the UE with the SCell based at least in part on a configured periodicity for synchronizing the SCell or a triggering event during ongoing communication via the SCell.

[0204] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, process 1200 includes sending an indication of the reference time for the PCell.

[0205] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the reference time of the PCell is based at least in part on one or more of the following: a downlink time slot index of the PCell, a symbol within a downlink time slot of the PCell, a downlink time slot index carrying control information associated with the SCell, a scheduling event on the PCell, or a time unit offset by an indicated amount from any of the above.

[0206] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, communicating via the SCell includes: sending a scheduling message for communication using the SCell, the scheduling message referring to the timing in the PCell, and wherein sending the scheduling message includes: sending an indication of a first time unit of the PCell, and sending an indication of a second time unit of the SCell within the first time unit.

[0207] In a twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, process 1200 includes receiving an indication of whether the wireless communication device is synchronized with the SCell.

[0208] In the thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the indication indicates that the wireless communication device is synchronized with the SCell, and wherein communication via the SCell is at least partially based on receiving the indication that the wireless communication device is synchronized with the SCell.

[0209] In a fourteenth aspect, either alone or in combination with one or more of aspects one to thirteen, the indication of whether the wireless communication device is synchronized with the SCell applies over a time duration that expires based at least in part on one or more of: 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 the PCell, a beam switch for the PCell, or a change in the timing tracking loop that satisfies a threshold.

[0210] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the wireless communication device includes a UE or a forwarding node.

[0211] although Fig.12 An example block diagram of process 1200 is shown, but in some aspects, process 1200 may include Fig.12 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1200 may be performed in parallel.

[0212] Fig.13 1 is a diagram of an example apparatus 1300 for wireless communication according to the present disclosure. Apparatus 1300 may be a wireless communication device, or a wireless communication device may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302 and a transmitting component 1304, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a base station, or another wireless communication device) using receiving component 1302 and transmitting component 1304. As further shown, apparatus 1300 may include a communication manager 1308 (e.g., communication manager 140 or 150).

[0213] In some aspects, the apparatus 1300 may be configured to perform Figures 9 and 10Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as Fig.11 The process 1100. In some aspects, Fig.13 The device 1300 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.13 One or more of the components shown may be combined with Figure 2 Additionally 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 codes that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0214] The receiving component 1302 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1306. 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 combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the wireless communication device.

[0215] Transmit component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1306. In some aspects, one or more other components of device 1300 may generate communications and may provide the generated communications to transmit component 1304 for transmission to device 1306. In some aspects, transmit 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 device 1306. In some aspects, transmit 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 wireless communication device. In some aspects, the transmit component 1304 can be co-located with the receive component 1302 in a transceiver.

[0216] The communication manager 1308 may obtain synchronization with the PCell of the wireless network. The receiving component 1302 may receive an indication of activating the SCell of the wireless network. The receiving component 1302 may receive the RS of the SCell. The communication manager 1308 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 being based at least in part on synchronization with the PCell. The receiving component 1302, the sending component 1304, and / or the communication manager 1308 may communicate via the SCell based at least in part on synchronization with the SCell.

[0217] The receiving component 1302 can receive, via the PCell, a configuration for synchronization with the SCell.

[0218] Receiving component 1302 can receive an indication of a reference time for a PCell.

[0219] The sending component 1304 can send an indication of whether the wireless communication device is synchronized with the SCell.

[0220] Fig.13 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.13 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.13 Two or more components shown may be implemented in a single component, or Fig.13 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.13 The illustrated set (one or more) of components executable is described as being comprised of Fig.13 Another group of components shown performs one or more functions.

[0221] Fig.14 1 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 and a transmitting component 1404, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1400 may communicate with another apparatus 1406 (such as a UE, a base station, or another wireless communication device) using receiving component 1402 and transmitting component 1404. As further shown, apparatus 1400 may include a communication manager 1408 (e.g., communication manager 150).

[0222] In some aspects, the apparatus 1400 may be configured to perform Figures 9 and 10Additionally or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as Fig.12 The process 1200. In some aspects, Fig.14 The device 1400 and / or one or more components shown may include a combination of Figure 2 One or more components of the network node. Additionally or alternatively, Fig.14 One or more of the components shown may be combined with Figure 2 Additionally 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 codes that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0223] The receiving component 1402 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1406. 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 combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the network node.

[0224] Transmit component 1404 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1406. In some aspects, one or more other components of device 1400 may generate communications and may provide the generated communications to transmit component 1404 for transmission to device 1406. In some aspects, transmit 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 device 1406. In some aspects, transmit component 1404 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the network node. In some aspects, the transmit component 1404 can be co-located with the receive component 1402 in a transceiver.

[0225] The sending component 1404 may send a synchronization RS of a PCell of a wireless network to the UE, the RS of the PCell being configured to support synchronization with the PCell. The sending component 1404 may send an indication of activating the SCell of the wireless network. The sending component 1404 may send an RS of the SCell, the RS of the SCell being configured to support synchronization of the UE 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 being based at least in part on synchronization with the PCell. The receiving component 1402, the sending component 1404, and / or the communication manager 1408 may communicate via the SCell based at least in part on synchronization with the SCell.

[0226] The sending component 1404 can send the configuration for synchronization with the SCell via the PCell.

[0227] Transmitting component 1404 can receive an indication of a reference time for the PCell.

[0228] Receiving component 1402 can receive an indication of whether the wireless communication device is synchronized with the SCell.

[0229] Fig.14 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.14 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.14 Two or more components shown may be implemented in a single component, or Fig.14 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.14 The illustrated set (one or more) of components executable is described as being comprised of Fig.14 Another group of components shown performs one or more functions.

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

[0231] Aspect 1: A wireless communication method performed by a wireless communication device, the method comprising: obtaining synchronization with a primary cell of a wireless network; receiving an indication to activate a secondary cell of the wireless network; receiving a reference signal (RS) of the secondary cell; obtaining synchronization with the secondary cell based at least in part on an offset between the RS of the secondary cell and a reference time of the primary cell, the reference time being based at least in part on the synchronization with the primary cell; and communicating via the secondary cell based at least in part on the synchronization with the secondary cell.

[0232] Aspect 2: The method according to aspect 1, wherein the primary cell is associated with a first frequency bandwidth, and the first frequency bandwidth is lower than the frequency bandwidth of the secondary cell.

[0233] Aspect 3: The method according to any one of aspects 1 to 2, wherein receiving the RS of the secondary cell comprises: receiving the RS of the secondary cell via an air path including a plurality of hops.

[0234] Aspect 4: The method according to any one of aspects 1 to 3, wherein the reference time of the primary cell is based at least in part on: a frequency tracking loop of the primary cell or a radio access network time unit of the primary cell.

[0235] Aspect 5: The method according to any one of Aspects 1 to 4, wherein receiving the RS of the secondary cell comprises one or more of the following: receiving an RS burst received during a synchronization session, or receiving an RS burst received during a beam management session.

[0236] Aspect 6: A method according to Aspect 5, wherein the synchronization session or the beam management session is associated with: a frequency range-specific synchronization session or beam management session, a secondary cell-specific specific synchronization session or beam management session, or a jump-specific specific synchronization session or beam management session.

[0237] Aspect 7: According to the method according to any one of aspects 1 to 6, the method further includes: receiving, via the primary cell, a configuration for the synchronization with the secondary cell.

[0238] Aspect 8: The method according to aspect 7, wherein the configuration schedules the RS of the secondary cell, or wherein the configuration includes the indication of activating the secondary cell.

[0239] Aspect 9: The method according to any one of aspects 1 to 8, wherein obtaining the synchronization with the secondary cell is based at least in part on: a configured periodicity of synchronizing the secondary cell or a triggering event during ongoing communication via the secondary cell.

[0240] Aspect 10: According to the method according to any one of aspects 1 to 9, the method also includes: receiving an indication of the reference time of the primary cell.

[0241] Aspect 11: A method according to Aspect 10, wherein the reference time of the primary cell is based at least in part on one or more of the following items: a downlink time slot index of the primary cell, a symbol within a downlink time slot of the primary cell, a downlink time slot index carrying control information associated with the secondary cell, a scheduling event on the primary cell, or a time unit offset by an indicated amount from any of the above items.

[0242] Aspect 12: A method according to any one of Aspects 1 to 11, wherein communicating via the secondary cell includes: receiving a scheduling message for communication using the secondary cell, the scheduling message referring to the timing in the primary cell, and wherein receiving the scheduling message includes: receiving an indication of a first time unit of the primary cell, and receiving an indication of a second time unit of the secondary cell within the first time unit.

[0243] Aspect 13: According to the method according to any one of aspects 1 to 12, the method further comprises: sending an indication of whether the wireless communication device is synchronized with the secondary cell.

[0244] Aspect 14: The method according to aspect 13, wherein the indication indicates that the wireless communication device is synchronized with the secondary cell, and wherein communicating via the secondary cell is based at least in part on sending the indication that the wireless communication device is synchronized with the secondary cell.

[0245] Aspect 15: A method according to any one of Aspects 13 to 14, wherein the indication of whether the wireless communication device is synchronized with the secondary cell is applicable within a time duration that expires based at least in part on one or more of the following: a change in the relative channel delay between the primary cell and the secondary cell, a change in the dominant line-of-sight path for the secondary cell or the primary cell, a beam switch for the primary cell, or a change in the timing tracking loop that meets a threshold.

[0246] Aspect 16: The method according to any one of aspects 1 to 15, wherein the wireless communication device comprises: a user equipment (UE) or a forwarding node.

[0247] Aspect 17: A method of wireless communication performed by a network node, the method comprising: sending a synchronization reference signal (RS) of a primary cell of a wireless network to a user equipment (UE), the RS of the primary cell being configured to support synchronization with the primary cell; sending an indication to activate a secondary cell of the wireless network; sending a reference signal (RS) of the secondary cell, the RS of the secondary cell being configured to support synchronization of the UE with the secondary cell based at least in part on an offset between the RS of the secondary cell and a reference time of the primary cell, the reference time being at least in part based on the synchronization with the primary cell; and communicating via the secondary cell based at least in part on the synchronization with the secondary cell.

[0248] Aspect 18: The method according to aspect 17, wherein the primary cell is associated with a first frequency bandwidth, and the first frequency bandwidth is lower than the frequency bandwidth of the secondary cell.

[0249] Aspect 19: The method according to any one of aspects 17 to 18, wherein transmitting the RS of the secondary cell comprises: transmitting the RS of the secondary cell via an air path including a plurality of hops.

[0250] Aspect 20: The method according to any one of aspects 17 to 19, wherein the reference time of the primary cell is based at least in part on: a frequency tracking loop of the primary cell or a radio access network time unit of the primary cell.

[0251] Aspect 21: A method according to any one of Aspects 17 to 20, wherein sending the RS of the secondary cell comprises one or more of the following: sending an RS burst sent during a synchronization session, or sending an RS burst sent during a beam management session.

[0252] Aspect 22: A method according to Aspect 21, wherein the synchronization session or the beam management session is associated with: a frequency range-specific synchronization session or beam management session, a secondary cell-specific specific synchronization session or beam management session, or a jump-specific specific synchronization session or beam management session.

[0253] Aspect 23: According to the method according to any one of aspects 17 to 22, the method further includes: sending, via the primary cell, a configuration for the synchronization with the secondary cell.

[0254] Aspect 24: The method according to aspect 23, wherein the configuration schedules the RS of the secondary cell, or wherein the configuration includes the indication of activating the secondary cell.

[0255] Aspect 25: A method according to any one of Aspects 17 to 24, wherein the RS of the secondary cell is configured to support synchronization of the UE with the secondary cell based at least in part on: a configured periodicity of synchronizing the secondary cell or a triggering event during ongoing communication via the secondary cell.

[0256] Aspect 26: According to the method according to any one of aspects 17 to 25, the method also includes: sending an indication of the reference time of the primary cell.

[0257] Aspect 27: A method according to Aspect 26, wherein the reference time of the primary cell is based at least in part on one or more of the following items: a downlink time slot index of the primary cell, a symbol within a downlink time slot of the primary cell, a downlink time slot index carrying control information associated with the secondary cell, a scheduling event on the primary cell, or a time unit offset by an indicated amount from any of the above items.

[0258] Aspect 28: A method according to any one of Aspects 17 to 27, wherein communicating via the secondary cell includes: sending a scheduling message for communication using the secondary cell, the scheduling message references the timing in the primary cell, and wherein sending the scheduling message includes: sending an indication of a first time unit of the primary cell, and sending an indication of a second time unit of the secondary cell within the first time unit.

[0259] Aspect 29: The method according to any one of aspects 17 to 28, the method further comprising: receiving an indication of whether the wireless communication device is synchronized with the secondary cell.

[0260] Aspect 30: The method according to aspect 29, wherein the indication indicates that the wireless communication device is synchronized with the secondary cell, and wherein communicating via the secondary cell is based at least in part on receiving the indication that the wireless communication device is synchronized with the secondary cell.

[0261] Aspect 31: A method according to any one of Aspects 29 to 30, wherein the indication of whether the wireless communication device is synchronized with the secondary cell is applicable within a time duration that expires based at least in part on one or more of the following: a change in the relative channel delay between the primary cell and the secondary cell, a change in the dominant line-of-sight path for the secondary cell or the primary cell, a beam switch for the primary cell, or a change in the timing tracking loop that meets a threshold.

[0262] Aspect 32: The method according to any one of aspects 17 to 31, wherein the wireless communication device comprises: a user equipment (UE) or a forwarding node.

[0263] Aspect 33: An apparatus for performing wireless communications at a device, the apparatus 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 32.

[0264] Aspect 34: A device for wireless communication, the device 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 32.

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

[0266] Aspect 36: 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 32.

[0267] Aspect 37: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, 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 32.

[0268] 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 these aspects.

[0269] 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, executables, 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 clear that the systems and / or methods described herein can be implemented by different forms of hardware and / or a combination of 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, there is no reference to specific software codes herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method at least in part based on the description herein.

[0270] 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, or not equal to a threshold, etc., depending on the context.

[0271] 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 each aspect. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of each aspect includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the 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 cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with 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 ordering of a, b and c).

[0272] Any element, action or instruction used herein should not be interpreted as critical or necessary unless clearly stated. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more items and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms are used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "an element having" A may also have B). In addition, the phrase "based on" is intended to mean "based at least in part 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 expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A wireless communication device for wireless communication, the wireless communication device comprising: Memory; and one or more processors coupled to the memory and configured to: Acquiring synchronization with a primary cell of a wireless network; receiving an indication to activate a secondary cell of the wireless network; receiving a reference signal (RS) of the secondary cell; obtaining synchronization with the secondary cell based at least in part on an offset between the RS of the secondary cell and a reference time of the primary cell, the reference time being based at least in part on the synchronization with the primary cell; as well as Communicating via the secondary cell is performed based at least in part on the synchronization with the secondary cell. 2 . The wireless communication device of claim 1 , wherein the primary cell is associated with a first frequency bandwidth that is lower than a frequency bandwidth of the secondary cell.

3. The wireless communication device according to claim 1, wherein in order to receive the RS of the secondary cell, the one or more processors are configured to: The RS of the secondary cell is received via an air path including a plurality of hops.

4. The wireless communication device of claim 1 , wherein the reference time of the primary cell is based at least in part on: The frequency tracking loop of the primary cell, or A radio access network time unit of the primary cell.

5. The wireless communication device of claim 1 , wherein in order to receive the RS of the secondary cell, the one or more processors are configured to: Receive RS bursts received during a synchronization session, or Receive RS bursts received during a beam management session.

6. The wireless communication device of claim 5, wherein the synchronization session or the beam management session is associated with: frequency range specific synchronization sessions or beam management sessions, A specific synchronization session or beam management session specific to the secondary cell, or Jump to a specific synchronization session or beam management session.

7. The wireless communication device of claim 1 , wherein the one or more processors are further configured to: A configuration for the synchronization with the secondary cell is received via the primary cell.

8. The wireless communication device according to claim 7, wherein the configuration schedules the RS of the secondary cell, or The configuration includes the indication for activating the secondary cell.

9. The wireless communication device of claim 1 , wherein the one or more processors are configured to obtain the synchronization with the secondary cell based at least in part on: Synchronize the configured periodicity of the secondary cell, or A triggering event during ongoing communication via the secondary cell.

10. The wireless communication device of claim 1, wherein the one or more processors are further configured to: An indication of the reference time of the primary cell is received.

11. The wireless communication device of claim 10, wherein the reference time of the primary cell is based at least in part on one or more of: The downlink timeslot index of the primary cell, symbols in the downlink time slot of the primary cell, a downlink time slot index, the downlink time slot index carrying control information associated with the secondary cell, a scheduling event on the primary cell, or A time unit offset by an indicated amount from any of the above items.

12. The wireless communication device of claim 1 , wherein to communicate via the secondary cell, the one or more processors are configured to: receive a scheduling message for communication using the secondary cell, the scheduling message references timing in the primary cell, and Wherein, in order to receive the scheduling message, the one or more processors are configured to: receiving an indication of a first time unit of the primary cell, and An indication of a second time unit of the secondary cell within the first time unit is received.

13. The wireless communication device of claim 1 , wherein the one or more processors are further configured to: An indication of whether the wireless communication device is synchronized with the secondary cell is sent.

14. The wireless communication device of claim 13, wherein the indication indicates that the wireless communication device is synchronized with the secondary cell, and Wherein communicating via the secondary cell is based at least in part on sending the indication that the wireless communication device is synchronized with the secondary cell.

15. The wireless communication device of claim 13, wherein the indication of whether the wireless communication device is synchronized with the secondary cell is applicable for a duration of time that expires based at least in part on one or more of: a change in the relative channel delay between the primary cell and the secondary cell, a change in the dominant line-of-sight path for the secondary cell or the primary cell, beam switching for the primary cell, or The timing of meeting the threshold tracks the change of the loop.

16. The wireless communication device of claim 1, wherein the wireless communication device comprises: User Equipment (UE), or Forwarding node.

17. A network node for wireless communication, the network node comprising: Memory; and one or more processors coupled to the memory and configured to: sending a synchronization reference signal (RS) of a primary cell of a wireless network to a user equipment (UE), the RS of the primary cell being configured to support synchronization with the primary cell; sending an indication to activate a secondary cell of the wireless network; sending a RS of the secondary cell, the RS of the secondary cell being configured to support synchronization of a UE with the secondary cell based at least in part on an offset between the RS of the secondary cell and a reference time of the primary cell, the reference time being based at least in part on the synchronization with the primary cell; as well as Communicating via the secondary cell is performed based at least in part on the synchronization with the secondary cell.

18. The network node of claim 17, wherein the reference time of the primary cell is based at least in part on: The frequency tracking loop of the primary cell, or A radio access network time unit of the primary cell.

19. The network node of claim 17, wherein the one or more processors are further configured to: Configuration for the synchronization with the secondary cell is sent via the primary cell.

20. The network node according to claim 19, wherein the configuration schedules the RS of the secondary cell, or The configuration includes the indication for activating the secondary cell.

21. The network node of claim 17, wherein the RS of the secondary cell is configured to support synchronization of a UE with the secondary cell based at least in part on: Synchronize the configured periodicity of the secondary cell, or A triggering event during ongoing communication via the secondary cell.

22. The network node of claim 17, wherein the one or more processors are further configured to: Sending an indication of the reference time of the primary cell.

23. The network node of claim 22, wherein the reference time of the primary cell is based at least in part on one or more of: The downlink timeslot index of the primary cell, symbols in the downlink time slot of the primary cell, a downlink time slot index, the downlink time slot index carrying control information associated with the secondary cell, a scheduling event on the primary cell, or A time unit offset by an indicated amount from any of the above items.

24. The network node of claim 17, wherein for communicating via the secondary cell, the one or more processors are configured to send a scheduling message for communication using the secondary cell, the scheduling message references timing in the primary cell, and Wherein, in order to send the scheduling message, the one or more processors are configured to: sending an indication of a first time unit of the primary cell, and An indication of a second time unit of the secondary cell within the first time unit is sent.

25. The network node of claim 17, wherein the one or more processors are further configured to: An indication of whether the wireless communication device is synchronized with the secondary cell is received.

26. The network node of claim 25, wherein the indication indicates that the wireless communication device is synchronized with the secondary cell, and Wherein communicating via the secondary cell is based at least in part on receiving the indication that the wireless communication device is synchronized with the secondary cell.

27. The network node of claim 26, wherein the indication of whether the wireless communication device is synchronized with the secondary cell is applicable for a duration of time that expires based at least in part on one or more of: a change in the relative channel delay between the primary cell and the secondary cell, a change in the dominant line-of-sight path for the secondary cell or the primary cell, beam switching for the primary cell, or The timing of meeting the threshold tracks the change of the loop.

28. A method of wireless communication performed by a wireless communication device, the method comprising: Acquiring synchronization with a primary cell of a wireless network; receiving an indication to activate a secondary cell of the wireless network; receiving a reference signal (RS) of the secondary cell; obtaining synchronization with the secondary cell based at least in part on an offset between the RS of the secondary cell and a reference time of the primary cell, the reference time being based at least in part on the synchronization with the primary cell; as well as Communicating via the secondary cell is performed based at least in part on the synchronization with the secondary cell.

29. The method of claim 28, wherein the reference time of the primary cell is based at least in part on: The frequency tracking loop of the primary cell, or A radio access network time unit of the primary cell.

30. A method of wireless communication performed by a network node, the method comprising: sending a synchronization reference signal (RS) of a primary cell of a wireless network to a user equipment (UE), the RS of the primary cell being configured to support synchronization with the primary cell; sending an indication to activate a secondary cell of the wireless network; sending a RS of the secondary cell, the RS of the secondary cell being configured to support synchronization of a UE with the secondary cell based at least in part on an offset between the RS of the secondary cell and a reference time of the primary cell, the reference time being based at least in part on the synchronization with the primary cell; as well as Communicating via the secondary cell is performed based at least in part on the synchronization with the secondary cell.

Images