Method and apparatus for triggering cell handover for inter-cell beam management

Abstract

The present disclosure relates to a 5G communication system or a 6G communication system for supporting higher data rates beyond 4G communication systems such as LTE. Methods and apparatus are provided for inter-cell beam management triggered cell handover. A method of operating a UE includes receiving first information for a first set of DL or joint candidate cell TCI states corresponding to one or more candidate cells; receiving second information for a second set of UL candidate cell TCI states corresponding to the one or more candidate cells; receiving a first MAC-CE for activating a subset of candidate cell TCI states from the first set or the second set; and receiving a second MAC CE including a cell handover command. The cell handover command indicates a candidate cell and at least one candidate cell TCI state in a first set or a second set corresponding to the candidate cell.

Description

Technical Field

[0001] This disclosure generally relates to wireless communication systems, and more specifically, to methods and apparatus for triggering cell handover for inter-cell beam management. Background Technology

[0002] Given the evolution of wireless communication technologies, these technologies have primarily been developed for human-centric services such as voice calls, multimedia services, and data services. With the commercialization of 5G (fifth-generation) communication systems, the number of connected devices is expected to grow exponentially. These will increasingly connect to communication networks. Examples of connected things can include vehicles, robots, drones, home appliances, displays, smart sensors connected to various infrastructures, construction machinery, and factory equipment. Mobile devices are expected to evolve in various form factors, such as augmented reality glasses, virtual reality headsets, and holographic devices. Efforts are underway to develop improved 6G communication systems to provide a wide range of services by connecting hundreds of billions of devices and things in the 6G (sixth-generation) era. For these reasons, 6G communication systems are referred to as "beyond 5G" systems.

[0003] The 6G communication system, which is expected to be commercialized around 2030, will have peak data rates in the trillion (1000 gigabits) bps range and radio latency of less than 100 microseconds, making it 50 times faster than 5G communication systems and with 1 / 10 of their radio latency.

[0004] To achieve such high data rates and ultra-low latency, 6G communication systems have been considered for implementation in the terahertz band (e.g., the 95 GHz to 3 THz band). It is anticipated that technologies capable of ensuring signal transmission distance (i.e., coverage) will become even more critical, as path loss and atmospheric absorption in the terahertz band are more severe than those in the millimeter-wave band introduced in 5G. As key technologies for ensuring coverage, it is necessary to develop radio frequency (RF) components, antennas, novel waveforms with better coverage than orthogonal frequency division multiplexing (OFDM), beamforming and massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, and multi-antenna transmission technologies such as massive MIMO. Furthermore, new technologies for improving the coverage of terahertz band signals have been discussed, such as metamaterial-based lenses and antennas, orbital angular momentum (OAM), and reconfigurable smart surfaces (RIS).

[0005] In addition, to improve spectrum efficiency and overall network performance, the following technologies have been developed for 6G communication systems: full-duplex technology to enable uplink and downlink transmissions to use the same frequency resources simultaneously; network technologies to utilize satellites, high-altitude platform stations (HAPS), etc., in an integrated manner; improved network architectures to support mobile base stations and achieve network operation optimization and automation; dynamic spectrum sharing technology based on spectrum usage prediction via conflict avoidance; the use of artificial intelligence (AI) in wireless communication, improving overall network operation by utilizing AI in the design phase to develop 6G and internalizing end-to-end AI support functions; and next-generation distributed computing technologies to overcome the limitations of UE computing capabilities through ultra-high-performance communication and computing resources (such as mobile edge computing (MEC), cloud, etc.) accessible on the network. Furthermore, by designing new protocols for use in 6G communication systems, the following operations are ongoing: developing mechanisms for achieving hardware-based secure environments and secure data use, developing technologies for maintaining privacy, attempting to enhance connectivity between devices, optimizing networks, promoting the software-defined nature of network entities, and increasing the openness of wireless communication.

[0006] Research and development of 6G communication systems in hyper-connectivity (including human-to-machine (P2M) and machine-to-machine (M2M)) is expected to enable the next hyper-connected experience. Specifically, services such as truly immersive extended reality (XR), high-fidelity mobile holograms, and digital replicas are anticipated to be available through 6G communication systems. Additionally, services such as remote surgery, industrial automation, and emergency response for enhanced security and reliability will be provided through 6G communication systems, enabling these technologies to be applied in various fields such as industry, healthcare, automotive, and home appliances.

[0007] Wireless communication is already one of the most successful innovations in modern history. Recently, the number of users of wireless communication services has exceeded five billion and continues to grow rapidly. The demand for wireless data traffic is increasing rapidly due to the growing popularity of smartphones and other mobile data devices (such as tablets, notebook computers, netbooks, e-book readers, and machine-type devices) among consumers and businesses. To meet the high growth of mobile data services and support new applications and deployments, improvements in radio interface efficiency and coverage are crucial. To meet the increased demand for wireless data services since the deployment of 4G communication systems, and to enable various vertical applications, 5G communication systems have been developed and are currently being deployed. Summary of the Invention

[0008] [Technical Solution]

[0009] This disclosure relates to triggered cell handover for inter-cell beam management.

[0010] In one embodiment, a user equipment (UE) is provided. The UE includes a transceiver configured to receive first information for a first set of downlink (DL) or joint candidate cell transmission configuration indicator (TCI) states corresponding to one or more candidate cells; second information for a second set of uplink (UL) candidate cell TCI states corresponding to one or more candidate cells; a first media access control channel element (MAC-CE) for activating a subset of candidate cell TCI states from the first or second set; and a second MAC-CE including a cell handover command. The cell handover command indicates a candidate cell and at least one candidate cell TCI state corresponding to the candidate cell from the first or second set. The at least one candidate cell TCI state is indicated when activated by the first MAC-CE. The UE also includes a processor operatively coupled to the transceiver. The processor is configured to deactivate a subset of candidate cell TCI states that exclude the activation of the at least one candidate cell TCI state.

[0011] In another embodiment, a base station (BS) is provided. The BS includes a transceiver configured to transmit first information for a first set of DL or joint candidate cell TCI states corresponding to one or more candidate cells, second information for a second set of UL candidate cell TCI states corresponding to one or more candidate cells, a first MAC-CE for activating a subset of candidate cell TCI states from the first or second set, and a second MAC-CE including a cell handover command. The cell handover command indicates a candidate cell and at least one candidate cell TCI state corresponding to the candidate cell from the first or second set. The at least one candidate cell TCI state is indicated when activated by the first MAC-CE. The BS also includes a processor operatively coupled to the transceiver. The processor is configured to deactivate a subset of activated candidate cell TCI states that exclude the at least one candidate cell TCI state.

[0012] In another embodiment, a method for operating a UE is provided. The method includes receiving first information for a first set of DL or joint candidate cell TCI states corresponding to one or more candidate cells; receiving second information for a second set of UL candidate cell TCI states corresponding to one or more candidate cells; receiving a first MAC-CE for activating a subset of candidate cell TCI states from the first or second set; and receiving a second MAC-CE including a cell handover command. The cell handover command indicates a candidate cell and at least one candidate cell TCI state corresponding to the candidate cell from the first or second set. The at least one candidate cell TCI state is indicated when activated by the first MAC-CE. The method further includes deactivating a subset of activated candidate cell TCI states that exclude the at least one candidate cell TCI state.

[0013] Other technical features will be obvious to those skilled in the art based on the following figures, description and claims.

[0014] Before proceeding with the detailed description below, it may be advantageous to define certain words and phrases used throughout this patent document. The term “coupled” and its derivatives refer to any direct or indirect communication between two or more elements, whether or not these elements are physically in contact with each other. The terms “transmit,” “receive,” and “communicate,” and their derivatives include both direct and indirect communication. The terms “comprising” and “including,” and their derivatives, mean including but not limited to. The term “or” is inclusive, meaning and / or. The phrase “associated with,” and its derivatives, mean including, being included in, interconnected with, containing, being contained within, connected to or connected to, coupled to or coupled with, able to communicate with, cooperate with, interleaved, juxtaposed, proximate, bound to or bound to, having, possessing the properties of, having a relationship to or with, etc. The term “controller” means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller may be centralized or distributed, local or remote. When used with a list of items, the phrase "at least one" means that different combinations of one or more of the listed items may be used, and it may be necessary to use only one item from the list. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0015] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media does not include wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media in which data can be permanently stored and media in which data can be stored and later rewritten, such as rewritable optical discs or erasable memory devices.

[0016] Definitions of certain other words and phrases are provided throughout this patent document. Those skilled in the art will understand that, in many cases (if not most), such definitions apply to the prior and future use of the words and phrases defined in this way. Attached Figure Description

[0017] To gain a more complete understanding of this disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like reference numerals denote like parts:

[0018] Figure 1 An example wireless network according to an embodiment of the present disclosure is shown;

[0019] Figure 2 An example gNodeB (gNB) according to an embodiment of this disclosure is shown;

[0020] Figure 3 An example user equipment (UE) according to an embodiment of the present disclosure is shown;

[0021] Figure 4A and 4B An example of a wireless transmission and reception path according to an embodiment of the present disclosure is shown;

[0022] Figure 5A An example of a wireless system according to an embodiment of the present disclosure is shown;

[0023] Figure 5B An example of multi-beam operation according to an embodiment of the present disclosure is shown;

[0024] Figure 6 An example of a transmitter structure for beamforming according to an embodiment of the present disclosure is shown;

[0025] Figure 7 A diagram illustrating an example architecture for inter-cell beam management according to embodiments of the present disclosure is shown;

[0026] Figure 8 A diagram illustrating example high-level signaling according to an embodiment of this disclosure is shown;

[0027] Figure 9 An example of a timeline for inter-cell handover according to an embodiment of the present disclosure is shown;

[0028] Figure 10 An example of a timeline for inter-cell handover according to an embodiment of the present disclosure is shown;

[0029] Figure 11 A diagram illustrating example Transport Configuration Indication (TCI) status / TCI status code points for a serving / candidate cell according to an embodiment of the present disclosure is shown;

[0030] Figure 12 A diagram showing exemplary TCI status / TCI status code points of a serving / candidate cell according to embodiments of this disclosure is provided;

[0031] Figure 13 A diagram showing exemplary TCI status / TCI status code points of a serving / candidate cell according to embodiments of this disclosure is provided;

[0032] Figure 14 A diagram showing exemplary TCI status / TCI status code points of a serving / candidate cell according to embodiments of this disclosure is provided;

[0033] Figure 15 A diagram showing exemplary TCI status / TCI status code points of a serving / candidate cell according to embodiments of this disclosure is provided;

[0034] Figure 16 A diagram illustrating an example MAC CE configuration for TCI state of candidate cells according to an embodiment of the present disclosure is shown;

[0035] Figure 17 A diagram showing an example list of non-zero power (NZP) channel state information reference signal (CSI-RS) resources according to embodiments of the present disclosure;

[0036] Figure 18 A diagram showing an example list of NZP CSI-RS resources according to embodiments of the present disclosure;

[0037] Figure 19A diagram illustrating an example orthogonal frequency division multiplexing (OFDM) waveform according to an embodiment of the present disclosure is shown;

[0038] Figure 20 A diagram of an example Fast Fourier Transform (FFT) window according to an embodiment of the present disclosure is shown;

[0039] Figure 21 A diagram is shown of an example Media Access Control (MAC) Random Access Procedure (RAR) for a Type 1 random access procedure according to an embodiment of the present disclosure;

[0040] Figure 22 A diagram of an example MAC RAR for a Type 2 random access procedure is shown according to an embodiment of the present disclosure;

[0041] Figure 23 A diagram illustrating an example timing advance command MAC CE according to an embodiment of the present disclosure is shown;

[0042] Figure 24 A diagram illustrating an example absolute timing advance command MAC CE according to an embodiment of the present disclosure is shown;

[0043] Figure 25 A flowchart of a random access procedure according to an embodiment of the present disclosure is shown;

[0044] Figure 26 A flowchart of an example two-step random access procedure according to an embodiment of the present disclosure is shown;

[0045] Figure 27 A process for an example RAR according to an embodiment of this disclosure is illustrated;

[0046] Figure 28 A process for an example RAR according to an embodiment of this disclosure is illustrated;

[0047] Figure 29 A process for an example RAR according to an embodiment of this disclosure is illustrated;

[0048] Figure 30 A process for an example RAR according to an embodiment of this disclosure is illustrated;

[0049] Figure 31 A process for an example RAR according to an embodiment of this disclosure is illustrated;

[0050] Figure 32 A process for an example RAR according to an embodiment of this disclosure is illustrated; and

[0051] Figure 33 A procedure for an example RAR is illustrated according to an embodiment of this disclosure. Detailed Implementation

[0052] The following discussion Figure 1-33 The various non-limiting embodiments used to describe the principles of this disclosure in this patent document are for illustrative purposes only and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or device.

[0053] To meet the increased demand for wireless data services since the deployment of 4G communication systems, and to enable various vertical applications, 5G / NR communication systems have been developed and are currently being deployed. 5G / NR communication systems are implemented in higher frequency (mmWave) bands (e.g., 28 GHz or 60 GHz bands) to achieve higher data rates, or in lower frequency bands (such as 6 GHz) to achieve robust coverage and mobility support. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are discussed in 5G / NR communication systems.

[0054] In addition, in 5G / NR communication systems, development is underway to improve system networks based on advanced small cells, cloud radio access networks (RAN) ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), and receiver interference cancellation.

[0055] The discussion of 5G systems and their associated frequency bands is for informational purposes only, as some embodiments of this disclosure can be implemented in 5G systems. However, this disclosure is not limited to 5G systems or their associated frequency bands, and embodiments of this disclosure can be utilized in combination with any frequency band. For example, aspects of this disclosure can also be applied to 5G communication systems, 6G, or even newer deployments using terahertz (THz) frequency bands.

[0056] The following literature and standards descriptions are hereby incorporated in this disclosure by reference, as if fully set forth herein: [1] 3GPP TS 38.211 v17.8.0, “NR; Physical Channels and Modulation”; [2] 3GPP TS 38.212 v17.9.0, “NR; Multiplexing and Channel Coding”; [3] 3GPP TS 38.213 v17.10.0, “NR; Physical Layer Procedures for Control”; [4] 3GPP TS 38.214 v17.10.0, “NR; Physical Layer Procedures for Data”; [5] 3GPP TS 38.321 v17.9.0, “NR; Media Access Control (MAC) Protocol Specification”; [6] 3GPP TS 38.331 v17.9.0, “NR; Radio Resource Control (RRC) Protocol Specification”; [7] 3GPP RP-213565, “Further NR Mobility Enhancements;” and [8] 3GPP RP-213598, “MIMO Evolution for Downlink and Uplink”

[0057] The following Figure 1-3 Various embodiments of communication technologies implemented in wireless communication systems and using orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) are described. Figure 1-3 The description does not imply any physical or architectural limitations on how the different embodiments can be implemented. Different embodiments of this disclosure can be implemented in any suitably arranged communication system.

[0058] Figure 1 An example wireless network 100 according to an embodiment of the present disclosure is shown. Figure 1 The embodiment of the wireless network 100 shown is for illustrative purposes only. Other embodiments of the wireless network 100 may be used without departing from the scope of this disclosure.

[0059] like Figure 1 As shown, the wireless network 100 includes gNB 101 (e.g., a base station, BS), gNB 102, and gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one network 130 (such as the Internet, a proprietary Internet Protocol (IP) network, or other data network).

[0060] gNB 102 provides wireless broadband access to network 130 to a first plurality of user equipments (UEs) within its coverage area 120. The first plurality of UEs includes UE 111, which may be located in a small business; UE 112, which may be located in an enterprise; UE 113, which may be a WiFi hotspot; UE 114, which may be located in a first residence; UE 115, which may be located in a second residence; and UE 116, which may be a mobile device, such as a cellular phone, wireless laptop computer, wireless PDA, etc. gNB 103 provides wireless broadband access to network 130 to a second plurality of UEs within its coverage area 125. The second plurality of UEs includes UE 115 and UE 116. In some embodiments, one or more of gNBs 101-103 may communicate with each other and with UEs 111-116 using 5G / NR, Long Term Evolution (LTE), LTE-A Advanced, WiMAX, WiFi, or other wireless communication technologies.

[0061] Depending on the network type, the term "base station" or "BS" can refer to any component (or set of components) configured to provide wireless access to a network, such as a transmitting point (TP), a transmitting-receiving point (TRP), an enhanced base station (eNodeB or eNB), a 5G / NR base station (gNB), a macro cell, a femtocell, a WiFi access point (AP), or other wirelessly enabled equipment. A base station can provide wireless access according to one or more wireless communication protocols, such as 5G / NR 3rd Generation Partnership Project (3GPP) NR, Long Term Evolution (LTE), LTE-Advanced (LTE-A), High Speed ​​Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. For convenience, the terms "BS" and "TRP" are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. Furthermore, depending on the network type, the term "user equipment" or "UE" can refer to any component such as a "mobile station," "subscriber station," "remote terminal," "wireless terminal," "receiving point," or "user device." For convenience, the terms “user equipment” and “UE” are used in this patent document to refer to a remote wireless device for wireless access to a BS, whether the UE is a mobile device (such as a mobile phone or smartphone) or is generally considered to be a fixed device (such as a desktop computer or vending machine).

[0062] The dashed lines indicate the approximate extent of coverage areas 120 and 125, which are shown as approximately circular for illustrative and explanatory purposes only. It should be clearly understood that coverage areas associated with the gNB (such as coverage areas 120 and 125) may have other shapes, including irregular shapes, depending on the configuration of the gNB and variations in the radio environment associated with natural and man-made obstacles.

[0063] As described in more detail below, one or more of UEs 111-116 include circuitry, programming, or a combination thereof for inter-cell beam management using triggered cell handover. In some embodiments, one or more of BSs 101-103 include circuitry, programming, or a combination thereof to support triggered cell handover for inter-cell beam management.

[0064] although Figure 1 An example of a wireless network is shown, but more can be found on... Figure 1 Various modifications can be made. For example, wireless network 100 can include any number of gNBs and any number of UEs in any suitable arrangement. Furthermore, gNB 101 can communicate directly with any number of UEs and provide these UEs with wireless broadband access to network 130. Similarly, each gNB 102-103 can communicate directly with network 130 and provide UEs with direct wireless broadband access to network 130. Additionally, gNBs 101, 102, and / or 103 can provide access to other or additional external networks (e.g., external telephone networks or other types of data networks).

[0065] Figure 2 An example gNB 102 according to an embodiment of the present disclosure is shown. Figure 2 The embodiment of gNB 102 shown is for illustrative purposes only, and Figure 1 gNBs 101 and 103 can have the same or similar configurations. However, gNBs have a wide variety of configurations, and Figure 2 This disclosure is not intended to limit the scope of any particular implementation of gNB.

[0066] like Figure 2 As shown, gNB 102 includes multiple antennas 205a-205n, multiple transceivers 210a-210n, a controller / processor 225, a memory 230, and a backhaul or network interface 235.

[0067] Transceivers 210a-210n receive incoming radio frequency (RF) signals from antennas 205a-205n, such as signals transmitted by a UE in wireless network 100. Transceivers 210a-210n down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are processed by receive (RX) processing circuitry in transceivers 210a-210n and / or controller / processor 225, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. Controller / processor 225 can further process the baseband signals.

[0068] The transmit (TX) processing circuitry in transceivers 210a-210n and / or controller / processor 225 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from controller / processor 225. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. Transceivers 210a-210n up-convert the baseband or IF signal into an RF signal transmitted via antennas 205a-205n.

[0069] The controller / processor 225 may include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, the controller / processor 225 may control the transceivers 210a-210n to receive uplink (UL) channel signals and transmit downlink (DL) channel signals according to well-known principles. The controller / processor 225 may also support additional functions, such as more advanced wireless communication functions. For example, the controller / processor 225 may support beamforming or directional routing operations, wherein outgoing / incoming signals from / to multiple antennas 205a-205n are weighted differently to effectively guide outgoing signals to a desired direction. The controller / processor 225 may support any of a variety of other functions in the gNB 102.

[0070] The controller / processor 225 is also capable of executing programs and other processes residing in the memory 230, such as supporting triggered cell handover for inter-cell beam management. The controller / processor 225 can move data into or out of the memory 230 as needed for the execution process.

[0071] The controller / processor 225 is also coupled to a backhaul or network interface 235. The backhaul or network interface 235 allows the gNB 102 to communicate with other devices or systems via a backhaul connection or over a network. Interface 235 can support communication via any suitable wired or wireless connection. For example, when the gNB 102 is implemented as part of a cellular communication system (such as a cellular communication system supporting 5G / NR, LTE, or LTE-A), interface 235 can allow the gNB 102 to communicate with other gNBs via a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, interface 235 can allow the gNB 102 to communicate via a wired or wireless local area network or via a wired or wireless connection to a larger network (such as the Internet). Interface 235 includes any suitable architecture supporting communication via wired or wireless connections, such as Ethernet or a transceiver.

[0072] Memory 230 is coupled to controller / processor 225. A portion of memory 230 may include RAM, and another portion of memory 230 may include flash memory or other ROM.

[0073] although Figure 2 An example of gNB 102 is shown, but it is possible to compare it with other models. Figure 2 Various changes can be made. For example, gNB 102 can include any number of Figure 2 Each component shown. Furthermore, Figure 2 The various components can be combined, further subdivided, or omitted, and additional components can be added as needed.

[0074] Figure 3 An example UE 116 according to an embodiment of the present disclosure is shown. Figure 3 The embodiment of UE 116 shown is for illustrative purposes only, and Figure 1 UEs 111-115 can have the same or similar configurations. However, UEs have a wide variety of configurations, and Figure 3 This disclosure is not intended to limit the scope to any particular embodiment of the UE.

[0075] like Figure 3 As shown, UE 116 includes an antenna 305, a transceiver 310, and a microphone 320. UE 116 also includes a speaker 330, a processor 340, an input / output (I / O) interface (IF) 345, an input 350, a display 355, and memory 360. Memory 360 includes an operating system (OS) 361 and one or more applications 362.

[0076] Transceiver 310 receives incoming RF signals transmitted by a gNB of wireless network 100 from antenna 305. Transceiver 310 down-converts the incoming RF signals to generate intermediate frequency (IF) or baseband signals. The IF or baseband signals are processed by RX processing circuitry in transceiver 310 and / or processor 340, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. The RX processing circuitry sends the processed baseband signals to speaker 330 (e.g., for voice data) or to processor 340 (e.g., for web browsing data).

[0077] The TX processing circuitry in transceiver 310 and / or processor 340 receives analog or digital voice data from microphone 320 or other outgoing baseband data (such as network data, email, or interactive video game data) from processor 340. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. Transceiver 310 up-converts the baseband or IF signal into an RF signal transmitted via antenna 305.

[0078] Processor 340 may include one or more processors or other processing devices and executes OS 361 stored in memory 360 to control the overall operation of UE 116. For example, processor 340 may control transceiver 310 to receive DL channel signals and transmit UL channel signals according to well-known principles. In some embodiments, processor 340 includes at least one microprocessor or microcontroller.

[0079] Processor 340 is also capable of executing other processes and programs residing in memory 360. For example, processor 340 may execute processes to utilize and / or identify triggered cell handovers for inter-cell beam management, as described in embodiments of this disclosure. Processor 340 may move data into or out of memory 360 as needed to execute processes. In some embodiments, processor 340 is configured to execute application 362 based on OS 361 or in response to signals received from gNB or operator. Processor 340 is also coupled to I / O interface 345, which provides UE 116 with the ability to connect to other devices, such as laptop computers and handheld computers. I / O interface 345 is the communication path between these accessories and processor 340.

[0080] The processor 340 is also coupled to an input 350 and a display 355. The input 350 includes, for example, a touchscreen, a keypad, etc. The operator of the UE 116 can use the input 350 to input data into the UE 116. The display 355 may be a liquid crystal display, a light-emitting diode display, or other display capable of displaying text and / or at least limited graphics (such as from a website).

[0081] The memory 360 is coupled to the processor 340. A portion of the memory 360 may include random access memory (RAM), and another portion of the memory 360 may include flash memory or other read-only memory (ROM).

[0082] although Figure 3 An example of UE 116 is shown, but it is possible to modify it. Figure 3 Make various changes. For example, Figure 3 The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. As a specific example, processor 340 can be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In another example, transceiver 310 may include any number of transceivers and signal processing chains and can be connected to any number of antennas. Furthermore, although... Figure 3 The UE116 is shown configured as a mobile phone or smartphone, but the UE can be configured to operate as other types of mobile or fixed devices.

[0083] Figure 4A and Figure 4B Examples of wireless transmit and receive paths 400 and 450 according to embodiments of the present disclosure are shown respectively. For example, transmit path 400 may be described as being implemented in a gNB (such as gNB 102), while receive path 450 may be described as being implemented in a UE (such as UE 116). However, it should be understood that receive path 450 may be implemented in a gNB, and transmit path 400 may be implemented in a UE. In some embodiments, transmit path 400 and / or receive path 450 are configured to support triggered cell handover for inter-cell beam management, as described in embodiments of the present disclosure.

[0084] like Figure 4A As shown, the transmit path 400 includes a channel coding and modulation block 205, a serial-to-parallel (S to P) block 410, an N-size inverse fast Fourier transform (IFFT) block 415, a parallel-to-serial (P to S) block 420, a cyclic prefix addition block 425, and an up-converter (UC) 430. The receive path 250 includes a down-converter (DC) 455, a cyclic prefix removal block 460, an S to P block 465, an N-size fast Fourier transform (FFT) block 470, a parallel-to-serial (P to S) block 475, and a channel decoding and demodulation block 480.

[0085] In transmit path 400, channel coding and modulation block 405 receives a set of information bits, applies coding (such as low-density parity-check (LDPC) coding), and modulates the input bits (such as using quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM)) to generate a sequence of frequency-domain modulated symbols. Serial-to-parallel block 410 converts (such as demultiplexes) the serial modulated symbols into parallel data to generate N parallel symbol streams, where N is the IFFT / FFT size used in gNB 102 and UE 116. IFFT block 415 of size N performs an IFFT operation on the N parallel symbol streams to generate a time-domain output signal. Parallel-to-serial block 420 converts (such as multiplexes) the parallel time-domain output symbols from IFFT block 415 of size N to generate a serial time-domain signal. Cyclic prefix addition block 425 inserts a cyclic prefix into the time-domain signal. Upconverter 430 modulates (such as upconverts) the output of cyclic prefix addition block 425 to an RF frequency for transmission via the wireless channel. The signal can also be filtered at the baseband before being switched to the RF frequency.

[0086] like Figure 4B As shown, downconverter 455 downconverts the received signal to the baseband frequency, and cyclic prefix removal block 460 removes the cyclic prefix to generate a serial time-domain baseband signal. Serial-to-parallel block 465 converts the time-domain baseband signal into a parallel time-domain signal. FFT block 470 of size N performs an FFT algorithm to generate N parallel frequency-domain signals. (P to S) block 475 converts the parallel frequency-domain signals into a sequence of modulated data symbols. Channel decoding and demodulation block 480 demodulates and decodes the modulated symbols to recover the original input data stream.

[0087] Each of gNBs 101-103 can implement a transmission path 400 similar to that sent to UEs 111-116 in the downlink, and a reception path 450 similar to that received from UEs 111-116 in the uplink. Similarly, each of UEs 111-116 can implement a transmission path 400 for sending to gNBs 101-103 in the uplink, and a reception path 450 for receiving from gNBs 101-103 in the downlink.

[0088] Figure 4A and 4B Each component in the system can be implemented using only hardware or a combination of hardware and software / firmware. As a specific example, Figure 4A and 4BAt least some components can be implemented in software, while others can be implemented using configurable hardware or a combination of software and configurable hardware. For example, FFT block 470 and IFFT block 415 can be implemented as configurable software algorithms, where the value of size N can be modified depending on the implementation.

[0089] Furthermore, although described as using FFT and IFFT, this is merely illustrative and should not be construed as limiting the scope of this disclosure. Other types of transforms, such as the Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions, may be used. It should be understood that for the DFT and IDFT functions, the value of the variable N can be any integer (e.g., 1, 2, 3, 4, etc.), while for the FFT and IFFT functions, the value of the variable N can be any integer that is a power of 2 (e.g., 1, 2, 4, 8, 16, etc.).

[0090] although Figure 4A and 4B Examples of wireless transmit and receive paths 400 and 450 are shown respectively, but more details can be found on the other side. Figure 4A and 4B Make various changes. For example, you can combine, further subdivide, or omit. Figure 4A and 4B It includes various components and allows for the addition of additional components as needed. Furthermore, Figure 4A and 4B This is intended to illustrate examples of the types of transmit and receive paths that can be used in a wireless network. Any other suitable architecture can be used to support wireless communication in a wireless network.

[0091] like Figure 5A As shown, in the wireless system 500, the beam 501 of device 504 can be characterized by beam direction 502 and beamwidth 503. For example, device 504 (or UE 116) transmits RF energy in the beam direction and within the beamwidth. Device 504 receives RF energy in the beam direction and within the beamwidth. Figure 5A As shown, when point A is within the beamwidth and direction of the beam from device 504, the device at point A 505 can receive from and transmit to device 504. Figure 5A As shown, the device at point B 506 cannot receive from or transmit to device 504 because point B 506 is outside the beamwidth and direction of the beam from device 504. Although for illustrative purposes, Figure 5A A 2D beam is shown, but it will be apparent to those skilled in the art that the beam can be 3D, where the beam direction and beamwidth are defined in space.

[0092] Figure 5BAn example of multi-beam operation 550 according to an embodiment of the present disclosure is shown. For example, multi-beam operation 550 may be... Figure 3 The UE 116 is utilized. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0093] In wireless systems, devices can transmit and / or receive on multiple beams. This is known as "multi-beam operation." (Although for illustrative purposes...) Figure 5B The beam in the image is 2D, but it will be apparent to those skilled in the art that the beam can be 3D, wherein the beam can be sent in any direction in space or received from any direction in space.

[0094] Figure 6 An example of a transmitter structure 600 for beamforming according to an embodiment of the present disclosure is shown. In some embodiments, one or more of gNB 102 or UE 116 include transmitter structure 600. For example, one or more of antenna 205 and its associated system or antenna 305 and its associated system may be included in transmitter structure 600. This example is for illustration only, and other embodiments may be used without departing from the scope of the present disclosure.

[0095] Therefore, embodiments of this disclosure recognize that versions 14 LTE and 15 NR support up to 32 Channel State Indication Reference Signal (CSI-RS) antenna ports, enabling eNBs or gNBs to be equipped with a large number of antenna elements (such as 64 or 128). Multiple antenna elements can then be mapped onto a single CSI-RS port. For millimeter-wave bands, although the number of antenna elements can be larger for a given form factor, hardware constraints (such as the feasibility of mounting a large number of analog-to-digital converters (ADCs) and digital-to-analog converters (DACs) at millimeter-wave frequencies) can limit the number of CSI-RS ports that can correspond to the number of digital precoding ports, such as... Figure 6 As shown. A CSI-RS port can then be mapped to a large number of antenna elements that can be controlled by a set of analog phase shifters 601. A CSI-RS port can then correspond to a subarray that generates a narrow analog beam through analog beamforming 605. This analog beam can be configured to sweep a wider range of angles 620 by changing the phase shifter group across symbols or time slots / subframes. The number of subarrays (equal to the number of RF chains) is the same as the number of CSI-RS ports (NCSI-PORT). Digital beamforming unit 610 performs linear combination across NCSI-PORT analog beams to further increase precoding gain. While the analog beam is wideband (and therefore not frequency-selective), digital precoding can vary across frequency subbands or resource blocks. Receiver operation can be envisioned similarly.

[0096] because Figure 6 The transmitter structure 600 utilizes multiple analog beams for transmission and reception (where, for example, after a training duration performed occasionally or periodically, one or a few analog beams are selected from a large number of analog beams), hence the term "multi-beam operation" is used to refer to this aspect of the entire system. For illustrative purposes, this includes indicating the assigned DL or ULTX beam (also referred to as "beam indication"), measuring at least one reference signal for calculating and performing beam reporting (also referred to as "beam measurement" and "beam reporting," respectively), and receiving DL or UL transmissions via selecting the corresponding RX beam. Figure 6 The system is also suitable for higher frequency bands, such as >52.6 GHz. In this case, the system can use only analog beams. Due to O2 absorption loss near 60 GHz (an additional loss of ~10 dB per 100 m distance), a larger number and narrower analog beams (and therefore a larger number of radiators in the array) are needed to compensate for the additional path loss.

[0097] The text and accompanying drawings are provided by way of example only to aid the reader in understanding this disclosure. They are not intended and should not be construed as limiting the scope of this disclosure in any way. Although certain embodiments and examples have been provided, those skilled in the art will understand based on the disclosure herein that changes can be made to the illustrated embodiments and examples without departing from the scope of this disclosure. The transmitter structure 600 for beamforming is for illustrative purposes only, and other embodiments may be used without departing from the scope of this disclosure.

[0098] In this disclosure, the beam is determined by any of the following:

[0099] TCI states that establish a quasi-co-address (QCL) relationship between a source reference signal (e.g., a synchronization signal block (SSB) and / or CSI-RS) and a target reference signal.

[0100] Establish spatial relationship information associated with source reference signals (such as SSB or CSI-RS or probe reference signal (SRS)).

[0101] In either case, the ID of the source reference signal identifies the beam.

[0102] The TCI status and / or spatial relationship reference RS can determine the spatial Rx filter used to receive downlink channels at the UE, or the spatial TX filter used to transmit uplink channels from the UE; or the spatial Tx filter used to transmit downlink channels from the gNB, or the spatial Rx filter used to receive uplink channels at the gNB.

[0103] Version 17 introduced a unified TCI framework, in which the UE is signaled with a unified, primary, major, or indicated TCI status. A unified, primary, or major TCI status can be one of the following:

[0104] In the case of a joint TCI status indication, where the same beam is used for both the DL and UL channels, the joint TCI status can be used for at least the UE-dedicated DL channel and the UE-dedicated UL channel.

[0105] In the case of separate TCI status indications, where different beams are used for DL ​​and UL channels, the DL TCI status can be used at least for the UE-dedicated DL channel.

[0106] In the case of separate TCI status indications, where different beams are used for DL ​​and UL channels, the UL TCI status can be used at least for the UE-dedicated UL channel.

[0107] The unified (primary, dominant, or indicated) TCI status is the TCI status of UE-dedicated reception on Physical Downlink Shared Channel (PDSCH) / Physical Downlink Control Channel (PDCCH) or Physical Uplink Shared Channel (PUSCH) and Dedicated Physical Uplink Control Channel (PUCCH) resources based on Dynamic Licensing / Configuration Licensing.

[0108] The unified TCI framework applies to intra-cell beamforming, where the TCI state has a source RS directly or indirectly associated with the serving cell's SSB through a quasi-co-location relationship (e.g., spatial relationship) (e.g., the TCI state is associated with the serving cell's TRP). The unified TCI state framework also applies to inter-cell beamforming, where the TCI state may have a source RS directly or indirectly associated with the cell's SSB through a quasi-co-location relationship (e.g., spatial relationship), and the cell has a Physical Cell Identifier (PCI) different from the serving cell's PCI (e.g., the TCI state is associated with the TRP of a cell with a PCI different from the serving cell's PCI). In Release 17, UE-dedicated channels can be received and / or transmitted using TCI states associated with cells having PCIs different from the serving cell's PCI. Common channels can be received and / or transmitted using TCI states associated with the serving cell (e.g., not associated with cells having PCIs different from the serving cell's PCI). Common channels may include:

[0109] Channels carrying system information (such as SIBs) with DL assignments carried by downlink control information (DCI) in PDCCHs, which have cyclic redundancy check (CRC) scrambled by system information radio network temporary identifiers (SI-RNTIs), and are transmitted in the type 0-PDCCH common search space (CSS) set.

[0110] The channel carries other system information with DL allocation, which is carried by DCI in PDCCH with CRC scrambled by SI-RNTI and transmitted in type 0A-PDCCH CSS set.

[0111] A channel carrying a paging or short message with a DL allocation carried by a DCI in a PDCCH, the PDCCH having a CRC scrambled by a paging RNTI (P-RNTI), and transmitted in a type 2-PDCCH CSS set.

[0112] The channel carrying the RACH-related channel, DL allocation or UL grant is carried by the DCI in the PDCCH with CRC scrambled by the Random Access RNTI (RA-RNTI) or Temporary Cell RNTI (TC-RNTI) and is transmitted in the Type 1-PDCCH CSS set.

[0113] Quasi-colocation (QCL) relationships can be quasi-locations with respect to one or more of the following relationships [38.214 [Reference 4] - Section 5.1.5]:

[0114] Type A, {Doppler frequency shift, Doppler spread, average delay, delay spread}

[0115] Type B, {Doppler frequency shift, Doppler spread}

[0116] Type C, {Doppler shift, average delay}

[0117] Type D, {space Rx parameter}

[0118] In addition, quasi-co-location relationships can also provide spatial relationships for UL channels. For example, the DL source reference signal provides information about the spatial domain filters to be used for UL transmission, or the UL source reference signal provides the spatial domain filters to be used for UL transmission, such as the same spatial domain filters used for the UL source reference signal and UL transmission.

[0119] The unified (primary or main) TCI state applies at least to UE-dedicated DL and UL channels. The unified (primary or main) TCI can also be applied to other DL and / or UL channels and / or signals, such as non-UE-dedicated channels and sounding reference signals (SRS).

[0120] In version 18, work item [7] was agreed upon to further enhance mobility in NR. “When a UE moves from the coverage of one cell to another, a serving cell change is required at some point. The current serving cell change is triggered by L3 measurements and completed by reconfiguration triggered by RRC signaling to synchronize changes to the primary cell (PCell) and primary-secondary cell group cell (PSCell), and release the addition of SCells where applicable. Embodiments of this disclosure recognize that each case involves a full L2 (and L1) reset, resulting in longer latency, greater overhead, and longer downtime than beam-switching mobility. The goal of L1 / L2 mobility enhancement is to enable serving cell changes via L1 / L2 signaling to reduce latency, overhead, and downtime” [7]. Allowing seamless changes to the serving cell using L1 / L2 mechanisms reduces handover latency and results in more robust operation (fewer dropped calls). In this disclosure, various embodiments focus on mechanisms for activating and indicating, and deactivating, the TCI state of the serving cell and candidate cells before, during, and after cell handover.

[0121] Figure 7 A diagram is shown of an example architecture 700 for inter-cell beam management according to an embodiment of the present disclosure. For example, the architecture 700 for inter-cell beam management can be derived from... Figure 1 UE 112 and BS 102 within network 100 utilize this. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0122] Release 17 introduces a unified TCI state framework to simplify beam management by reducing latency and overhead associated with beam changes. Release 17 also introduces inter-cell beam management, where UE-dedicated channels can be received on at least the beam associated with a TRP associated with a PCI different from the serving cell's PCI. (Reference) Figure 7 In version 17, when the beam is changed from the TRP of the serving cell to the TRP of a cell with a different PCI than the serving cell, the serving cell remains unchanged. The common channel continues to receive and transmit on the beam associated with the serving cell.

[0123] In version 17, a unified, primary, major, or indicated TCI state is signaled to the UE to indicate the beam the UE will use. RRC signaling configures the version 17 TCI state, where the TCI state can be configured as a DL or joint TCI state using the information element (DLorJoint-TCIState), or as a UL TCI state using the information element (UL-TCIState). MAC signaling can activate one or more TCI code points. When the MAC CE activates a TCI state code point, the UE applies the TCI state associated with the activated code point after the beam application time. When the MAC CE activates more than one TCI code point, further DCI signaling is used to indicate the TCI state code points to the UE. The unified TCI state can be signaled by a DCI format with DL assignment (e.g., a DL-assigned DCI format (e.g., DCI format 1_1 or DCI format 1_2) or a DL-assigned DCI format without DL assignment (e.g., DCI format 1_1 or DCI format 1_2).

[0124] To further enhance mobility, when the beam changes from a first TRP associated with the source serving cell to a second TRP associated with a PCI different from that of the source serving cell, the second TRP can become the target serving cell. In this disclosure, various embodiments focus on mechanisms for activating, indicating, and deactivating the TCI states of serving cells and candidate cells before, during, and after cell handover.

[0125] This disclosure relates to 5G / NR communication systems.

[0126] This disclosure provides design aspects related to dynamic handover of a serving cell from a source serving cell to a candidate cell. The TCI state of the candidate cell is activated before or during the handover and is indicated in the handover command. The TCI state of the serving cell remains in use until the handover command is issued. After the handover command, the TCI state activated for the candidate set can continue to be used until a new TCI state is activated for the new serving cell.

[0127] In this disclosure, various embodiments focus on aspects related to signaling that use the NZP CSI-RS associated with the candidate cell as the source RS for the candidate cell's TCI state prior to cell handover. In this disclosure, the candidate cell TCI state is also referred to as the L1 / L2 triggered mobility (LTM) TCI state.

[0128] Aspects, features, and advantages of this disclosure will become apparent from the following detailed description simply by illustrating several specific embodiments and implementations, including the best mode contemplated for carrying out this disclosure. This disclosure is also capable of having other and different embodiments, and several details thereof may be modified in various obvious ways without departing from the spirit and scope of this disclosure. Therefore, the drawings and description are to be considered illustrative in nature and not restrictive. This disclosure is illustrated in the accompanying figures by way of example rather than limitation.

[0129] In the following text, both Frequency Division Duplex (FDD) and Time Division Duplex (TDD) are considered duplexing methods for DL ​​and UL signaling.

[0130] Although the following exemplary descriptions and embodiments presuppose orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA), this disclosure can be extended to other OFDM-based transmission waveforms or multiple access schemes, such as filtered OFDM (F-OFDM).

[0131] This disclosure provides several components that can be used in combination or together, or that can operate as independent solutions.

[0132] Figure 8 A diagram illustrating an example higher-layer signaling 800 according to an embodiment of the present disclosure is shown. For example, the higher-layer signaling 800 may be provided by… Figure 1 The UE 111 receives this. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0133] In this disclosure, the term "activation" describes an operation in which the UE receives and decodes a signal representing a start time point from the network (or gNB). The start point can be a current or future time slot / subframe or symbol, and its exact location is implicitly or explicitly indicated, or otherwise specified in system operation or configured by a higher layer. Upon successful decoding of the signal, the UE responds according to the indication provided by the signal. The term "deactivation" describes an operation in which the UE receives and decodes a signal representing a stop time point from the network (or gNB). The stop point can be a current or future time slot / subframe or symbol, and its exact location is implicitly or explicitly indicated, or otherwise specified in system operation or configured by a higher layer. Upon successful decoding of the signal, the UE responds according to the indication provided by the signal.

[0134] Terms such as TCI, TCI status, SpatialRelationInfo, target RS, reference RS, and others are for descriptive purposes and are therefore not normative. Other terms referring to the same function may also be used.

[0135] "Reference RS" corresponds to a set of characteristics of DL beams or UL TX beams, such as orientation, precoding / beamforming, number of ports, etc.

[0136] In the following components, the TCI state is used for beam indication. It can refer to the DL TCI state of a downlink channel (e.g., PDCCH and PDSCH), the uplink TCI state of an uplink channel (e.g., PUSCH or PUCCH), the joint TCI state of downlink and uplink channels, or the individual TCI state of uplink and downlink channels. The TCI state can be common across multiple component carriers, or it can be a single TCI state for a component carrier or a set of component carriers. The TCI state can be gNB or UE panel-specific or common across panels. In some examples, the uplink TCI state can be replaced by an SRS resource indicator (SRI).

[0137] In the following example, refer to Figure 7 The UE (e.g., UE 116) is configured / updated with a set of TCI states having N elements via higher-layer RRC signaling. In one example, the DL and joint TCI states are configured by higher-layer parameters, where the number of DL and joint TCI states is... The UL TCI state is configured by the higher-level parameter UL-TCIState, where the number of UL TCI states is... . .

[0138] MAC CE signaling includes M (M) from a set of N TCI states. N) TCI states or subsets of TCI state code points, wherein the code points are signaled in the "Transmission Configuration Indication" field to indicate the DCI state. A code point may include one TCI state (e.g., DL TCI state, UL TCI state, or combined (DL and UL) TCI state). Alternatively, a code point may include two TCI states (e.g., DL TCI state and UL TCI state). L1 control signaling (i.e., downlink control information (DCI)) updates the UE's TCI state, where the DCI includes, for example, a "Transmission Configuration Indication" (beam indicator) field with m bits (making...). The TCI state corresponds to the code point signaled by the MAC CE. The DCI used to indicate the TCI state can be a DL-assigned DCI format with or without DL assignment (e.g., DCI format 1_1 or DCI format 1_2).

[0139] TCI states can be associated with the serving cell's SSB or with an SSB associated with a PCI different from the serving cell's PCI through QCL relationships. QCL relationships with SSBs can be direct QCL relationships, where the source RS of the QCL state (e.g., for QCL type D relationships or spatial relationships) is an SSB. QCL relationships with SSBs can be indirect QCL relationships, where the source RS (e.g., for QCL type D relationships or spatial relationships) can be a reference signal, and the reference signal has an SSB as its source (e.g., for QCL type D relationships or spatial relationships). Indirect QCL relationships with SSBs can involve QCL or spatial relationship chains with more than one reference signal.

[0140] Figure 9 An example of a timeline 900 for inter-cell handover according to an embodiment of the present disclosure is shown. For example, Figure 1 UE 113 may follow the timeline 900 for inter-cell handover. This example is for illustrative purposes only and may be used without departing from the scope of this disclosure.

[0141] Figure 10 An example of a timeline 1000 for inter-cell handover according to an embodiment of the present disclosure is shown. For example, Figure 1 UE 114 may follow timeline 1000 for inter-cell handover. This example is for illustrative purposes only and may be used without departing from the scope of this disclosure.

[0142] Figure 9 and Figure 10 An example of dynamic cell handover is shown. The UE has established communication with a first cell. This cell is referred to as the serving cell. As part of establishing communication with the first cell, a first set of TCI states is configured by higher-layer (e.g., RRC) signaling. The first set of TCI states may include one or more of the following (as described herein):

[0143] List of DL or combined TCI status

[0144] UL TCI Status List

[0145] TCI states can have source RSs for QCL or for spatial relations, where source RSs can be associated with the following:

[0146] The first residential area (i.e., the service area)

[0147] Cells with a PCI different from the first cell (i.e., the serving cell)

[0148] The source RS can be a Synchronization Symbol / Physical Broadcast Channel (SS / PBCH) block or an NZP CSI-RS resource.

[0149] like Figure 9 and Figure 10 As shown, a subset of TCI states from the first set of TCI states can be activated via MAC CE signaling. The activated subset of TCI states consists of code points that can be indicated to the UE in DCI format. The number of activated TCI state code points is M1. Code points may include:

[0150] Joint TCI status for joint (DL and UL) beam indication;

[0151] DL TCI status for individual beam indication;

[0152] UL TCI status for individual beam indication; and / or

[0153] A pair of DL TCI states and UL TCI states for individual beam indication.

[0154] The UE can be indicated with code points from active TCI status code points via DCI format (e.g., DCI format 1_1 or DCI format 1_2, with or without DL allocation).

[0155] Configure Layer 1 / Layer 2 triggered Mobility Transaction (LTM) TCI states for candidate cells. Activate or configure a second set of TCI states for one or more candidate cells. The maximum number of candidate cells for activating or configuring TCI states depends on the UE capability. In one example, the maximum number of candidate cells is one. The second set of TCI states may include one or more of the following:

[0156] The list of candidate cell DL or joint TCI states is called the LTM (L1 / L2 triggered mobility) DL or joint TCI state.

[0157] The list of UL TCI statuses for candidate cells is called the LTM UL TCI status.

[0158] LTM TCI states can have source RSs for QCL or for spatial relationships, where the source RS can be associated with one of the candidate cells. In one example, the source RS can be an SS / PBCH block associated with a candidate cell. For example, the source RS is defined or determined by the SS / PBCH block index and PCI (or PCI index) associated with the candidate cell. In another example, the source RS can be a CSI-RS resource, such as:

[0159] Tracking Reference Signal (TRS) (e.g., CSI-RS configured with TRS information), or

[0160] Configure CSI-RS resources for beam management (e.g., configure duplicate CSI-RS), or

[0161] Configure CSI-RS resources for CSI acquisition (e.g., CSI-RS configured without trs-info and without duplication).

[0162] CSI-RS resources can be associated with candidate cells, as described later in this disclosure.

[0163] refer to Figure 9 MAC CE activates a subset of LTM TCI states. In the case of joint beam indication on candidate cells where LTM TCI states are activated, the activated LTM TCI states include the LTM joint TCI state. In the case of individual beam indication on candidate cells where LTM TCI states are activated, the activated LTM TCI states include the LTM DL TCI state and the LTM UL TCI state. In one example, the LTM TCI states activated by MAC CE are used for J candidate cells, where... In one example, The maximum value is based on the UE capability. In one example, J=1. In one example, the number of active LTM TCI states is M2. In one example, the active LTM TCI states are code points, and the number of code points is M2. In one example, LTM TCI state code points can be:

[0164] LTM joint TCI status for joint (DL and UL) beam indication on candidate cells;

[0165] LTM DL TCI status used for individual beam indication on candidate cells;

[0166] LTM UL TCI status for individual beam indication on candidate cells; and / or

[0167] A pair of DL TCI states and UL TCI states used for individual beam indication on candidate cells.

[0168] Figure 11 A diagram illustrating an exemplary TCI state / TCI state code point 1100 for a serving / candidate cell according to an embodiment of the present disclosure is shown. For example, the TCI state and TCI state code point 1100 can be derived from... Figure 1 This example is used in any of UEs 111-116 (e.g., UE 115). This example is for illustrative purposes only and may be used without departing from the scope of this disclosure.

[0169] Figure 12A diagram illustrating an exemplary TCI state / TCI state code point 1200 for a serving / candidate cell according to an embodiment of the present disclosure is shown. For example, the TCI state and TCI state code point 1200 can be derived from... Figure 1 Any of the UE 111-116 used, for example Figure 3 UE 116. This example is for illustrative purposes only and may be used without departing from the scope of this disclosure.

[0170] In one example, M1 (the active TCI status code point of the serving cell (first cell)) and M2 (the active LTM TCI status or LTM TCI status code point of the candidate cell) are in the same pool, list, or set, such as Figure 11 and Figure 12 As shown, the size is M (for example, In one example, the maximum value of M depends on the UE capability; for example, the maximum value is given by M=8, M=16, or M=4. In another example, the maximum value of M1 depends on the UE capability; for example, the maximum value is given by M1=8 or M1=4. In yet another example, the maximum value of M2 depends on the UE capability; for example, the maximum value is given by M2=8 or M2=4. Figure 12 In this process, the M2 active LTM TCI states or LTM TCI state code points are further divided into separate subsets or sublists for each of the J candidate cells, where ,and It is the number of active LTM TCI states or LTM TCI state code points in cell J, and Alternatively, J can be adjusted to this range. Within. In one example, the maximum number of active TCI states or TCI status code points per cell (e.g. This can depend on the UE's capabilities; for example, the maximum value is given. =4, or =8, =1, or =2. In one example, for joint beam indication =n, and for individual beam indication =2n, where, for example, n=1 or n=2. The active TCI state or TCI state code point can be determined according to... Figure 11 or Figure 12 Indexed sequentially.

[0171] Figure 13 A diagram illustrating an exemplary TCI state and TCI state code point 1300 of a serving / candidate cell according to an embodiment of the present disclosure is provided. For example, the TCI state and TCI state code point 1300 can be derived from... Figure 1This example is used in any of UEs 111-116 (e.g., UE 111). This example is for illustrative purposes only and may be used without departing from the scope of this disclosure.

[0172] In one example, M1 (the active TCI status code point of the serving cell (first cell)) and M2 (the active TCI status or TCI status code point of the candidate cell) are located in separate pools, lists, or sets, such as Figure 13 As shown. In one example, the maximum value of M1 depends on the UE capability; for example, the maximum value is given by M1=8 or M1=4. In one example, the maximum value of M2 depends on the UE capability; for example, the maximum value is given by M2=8 or M2=4. In one example, there exists a value that depends on the UE capability. The maximum size, for example, is given by M=8, M=16, or M=4.

[0173] Figure 14 A diagram illustrating an example TCI state and TCI state code point 1400 for a serving / candidate cell according to an embodiment of the present disclosure is shown. For example, the TCI state and TCI state code point 1400 can be derived from... Figure 1 This example is used in any of UEs 111-116 (e.g., UE 112). This example is for illustrative purposes only and may be used without departing from the scope of this disclosure.

[0174] exist Figure 13 In the variant, refer to Figure 14 For each of the j candidate cells, the M2 active LTM TCI states or LTM TCI state code points are further divided into separate subsets or sublists, where ,and It is the number of active LTM TCI states or LTM TCI state code points in cell j, and Alternatively, j can be adjusted to that range. Within. In one example, the maximum number of active LTM TCI states or LTM TCI state code points per cell (e.g., This can depend on the UE's capabilities; for example, the maximum value is given. =4 or =8, =1 or =2. In one example, for joint beam indication =n, and for individual beam indication =2n, where, for example, n=1 or n=2. (See reference) Figure 14 The active LTM TCI status or LTM TCI status code points of candidate cells can be indexed sequentially.

[0175] Figure 15 A diagram is shown illustrating an example TCI state / TCI state code point 1500 for a serving / candidate cell according to an embodiment of the present disclosure. For example, the TCI state and TCI state code point 1500 can be derived from... Figure 1 This example is used in any of UEs 111-116 (such as UE 113). This example is for illustrative purposes only and may be used without departing from the scope of this disclosure.

[0176] In such Figure 15 shown Figure 13 and Figure 14 In the variant, the M2 active LTM TCI states or LTM TCI state code points are further divided into separate subsets or sublists for each of the J candidate cells, and each has its own pool, list, or set, where, ,and It is the number of active LTM TCI states or LTM TCI state code points in cell j, and Alternatively, j can be adjusted to that range. Within. In one example, the maximum number of active LTM TCI states or LTM TCI state code points per cell (e.g., This can depend on the UE's capabilities; for example, the maximum value is given. =4 or =8, =1 or =2. In one example, for joint beam indication =n, and for individual beam indication =2n, where, for example, n=1 or n=2.

[0177] In one example, refer to Figure 9 After activating the LTM TCI state, the active TCI status code point of the serving cell (e.g., the first cell) is maintained and can be indicated to the UE, for example, using a DCI format (e.g., DCI format 1_1 or DCI format 1_2 with or without DL allocation).

[0178] In the variant example ( Figure 9 (Not shown in the image), after activating the LTM TCI state, the active TCI state code point of the serving cell (e.g., the first cell) becomes deactivated. In one example, deactivation is implicit, i.e., there is no deactivation command; for example, deactivation occurs simultaneously with the LTM TCI state being activated or becoming active. In another example, deactivation occurs at the time the channel transmits the MAC CE activating the LTM TCI state. (For example, the start or end of the channel) after which, Configuration and / or updates can be performed via RRC signaling and / or MAC CE signaling and / or L1 control signaling. In another example, deactivation occurs when the channel (e.g., the start or end of the channel) sends an acknowledgment (e.g., a positive acknowledgment) to the MAC CE to activate the LTM TCI state. After that, among them Configuration and / or updates can be performed via RRC signaling and / or MAC CE signaling and / or L1 control signaling. In one example, deactivation occurs from the time the LTM TCI state is activated or becomes activated. After that, among them Configuration and / or updates can be performed via RRC signaling and / or MAC CE signaling and / or L1 control signaling.

[0179] In another example, deactivation is explicit, meaning there is a signal (e.g., MAC CE or DCI format) to deactivate the active TCI status code point of the serving cell (e.g., the first cell). In one example, a deactivation signal is sent to the UE after activating the LTM TCI status.

[0180] In one example, refer to Figure 9 The system sends a cell handover command to the UE (e.g., in MAC CE). In the case of a joint beam indication for the candidate cell, the cell handover command includes the LTM joint TCI state of the candidate cell; or in the case of a separate beam indication for the candidate cell, the cell handover command includes a pair of LTM DL TCI states and LTM ULTCI states of the candidate cell. The LTM joint TCI state or LTM DL TCI state and LTM UL TCI state are derived from the active LTM TCI state. In one example, the indication of the LTM joint TCI state or LTM DL TCI state or LTM UL TCI state can be based on the index of the corresponding TCI state in the RRC configuration list of the LTM DL or joint TCI state or UL TCI state. In another example, the indication of the LTM joint TCI state or LTM DL TCI state or LTM UL TCI state can be based on an index in the set of active LTM TCI states. For example, the index is based on the order of the active set or list of LTM TCI states. For example, the first active LTM TCI state in a set or list has index 0, the second active LTM TCI state in a set or list has index 1, and so on.

[0181] In one example, the indication of an LTM combined TCI state, LTM DL TCI state, or LTM UL TCI state can be based on an index in the set of active LTM TCI state code points. For example, the index or code point is based on the order of LTM TCI state code points in the active set or list of LTM TCI state code points. For example, the first active LTM TCI state code point in the set or list has an index of 0, the second active LTM TCI state code point in the set or list has an index of 1, and so on.

[0182] For simplicity, the LTM TCI status or LTM TCI status code point in the cell handover command can refer to the LTM joint TCI status of the candidate cell when the candidate cell is indicated by a joint beam, or refer to a pair of LTM DL TCI status and LTM UL TCI status of the candidate cell when the candidate cell is indicated by a separate beam.

[0183] In one example, the active LTM TCI state or LTM TCI state code point is globally indexed in candidate cells with an active LTM TCI state. In another example, the active LTM TCI state or LTM TCI state code point is individually indexed on each candidate cell with an active TCI state. For example, a cell handover command may include a candidate cell ID and the index or ID of the LTM TCI state or TCI state code point within that cell.

[0184] In one example, the configured (e.g., RRC-configured) LTM TCI state is globally indexed across candidate cells that have a configured (e.g., RRC-configured) LTM TCI state. In another example, the active LTM TCI state is individually indexed on each candidate cell that has a configured (e.g., RRC-configured) TCI state. For example, a cell handover command or a MACCE LTM TCI state activation command may include a candidate cell ID and the index or ID of the LTM TCI state within that cell.

[0185] In one example, refer to Figure 10The cell handover command is sent to the UE (e.g., in MAC CE). In the case of joint beam indication of the candidate cell, the cell handover command includes the LTM joint TCI state of the candidate cell; or in the case of individual beam indication of the candidate cell, the cell handover command includes a pair of LTM DL TCI states and LTM UL TCI states of the candidate cell. Prior to the cell handover command, the LTM joint TCI state or the LTM DL TCI state and the LTM ULTCI state are not activated. The cell handover command both activates and indicates the LTM TCI state. Indication of the LTM TCI state refers to using the TCI state for UE transmission and reception, for example, to determine QCL attributes and / or spatial filters. In one example, the activation and indication of the LTM joint TCI state or the LTM DL TCI state or the LTM UL TCI state can be based on the index of the corresponding TCI state in the RRC configuration list of the LTM DL or joint TCI state or the ULTCI state. In one example, the configured (e.g., RRC-configured) LTM TCI state is globally indexed across candidate cells that have a configured (e.g., RRC-configured) LTM TCI state. In another example, the active LTM TCI state is individually indexed on each candidate cell that has a configured (e.g., RRC-configured) TCI state. For example, a cell handover command or a MAC CE LTM TCI state activation command may include a candidate cell ID and the index or ID of the LTM TCI state within that cell.

[0186] Figure 16 A diagram illustrates an example MAC CE configuration 1600 for TCI state of a candidate cell according to an embodiment of the present disclosure. For example, the MAC CE configuration 1600 for TCI state can be provided by… Figure 1 The UE 111 implementation is described above. This example is for illustrative purposes only, and other embodiments may be used without departing from the scope of this disclosure.

[0187] In one example, when indicated in the cell handover command (e.g., Figure 9 ) or activation and indication (e.g., Figure 10 When the UE is in LTM TCI state or TCI state code point, it will remain in that state for a period of time. Then the LTM TCI state is applied. In one example, Measurements are taken from the channel carrying the MAC CE with cell handover commands (e.g., the start or end of the channel). In one example, Measurements are taken from the channel (e.g., the start or end of the channel) carrying acknowledgments (e.g., affirmative Ack) to MAC CEs carrying cell handover commands. For example, refer to Figure 16 ,time This is from the end of the channel carrying the acknowledgment to the MACCE containing the cell handover command. In this example, The value can depend on whether the TCI state is indicated (e.g., Figure 9 ) or is activated and indicated (e.g., Figure 10 For example, depending on the scenario, it can be provided via RRC signaling and / or MAC CE signaling and / or L1 control signaling. Configure and / or update two values. In this example, The value and TCI status are indicated (e.g., Figure 9 ) or is activated and indicated (e.g., Figure 10 This is unrelated; for example, it can be done via RRC signaling and / or MAC CE signaling and / or L1 control signaling. Configure and / or update a value.

[0188] In one example, if the TCI state has been activated before the cell handover command, the beam application time... yes Each time slot.

[0189] In one example, if the TCI state has not been activated before the cell handover command, then The value is determined by RAN4. Based on the current RAN4 specification, when the source RS of the TCI state is SSB, the beam application time... It may be given by (see Clause 8.10.3 of TS 38.133): ,in:

[0190] When the target TCI status is not in the activity list.

[0191] It is the time from when the MAC CE with the cell handover command is decoded to when the first SSB is transmitted.

[0192] ms.

[0193] In one example, the UE determines whether to apply joint beam indication or individual beam indication to a candidate cell based on the following:

[0194] A flag or indication used for the RRC configuration of each candidate cell, indicating whether the candidate cell uses joint beam indication or individual beam indication.

[0195] The RRC configuration provides a common flag or indication for candidate cells, indicating whether the candidate cell uses joint beam indication or individual beam indication.

[0196] The flags in the cell handover command indicate whether the candidate cell uses joint beam indication or individual beam indication.

[0197] If the UE is configured with DL or joint TCI state for candidate cells, it uses joint beam indication. If the UE is configured with both DL or joint TCI state and UL TCI state for candidate cells, it uses separate beam indication.

[0198] If the UE is in the active DL or joint TCI state of the candidate cell, it uses joint beam indication. If the UE is in the active DL or joint TCI and UL TCI state of the candidate cell, it uses separate beam indication.

[0199] If in the cell handover command (for example, such as...) Figure 9 As shown, if the UE is indicated with a TCI state (e.g., LTM joint TCI state), it uses a joint beam indication. If a pair of TCI states (e.g., LTM DL TCI state and LTM UL TCI state) are indicated to the UE in the cell handover command, the UE uses a separate beam indication.

[0200] If in the cell handover command (for example, such as...) Figure 10 As shown), if the UE is activated and indicated with a TCI state (e.g., LTM joint TCI state), it uses a joint beam indication. If the UE is activated and indicated with a pair of TCI states in the cell handover command (e.g., LTM DL TCI state and LTM UL TCI state), the UE uses a separate beam indication.

[0201] In one example, refer to Figure 9 and Figure 10 Following a cell handover command, the active TCI status code point of the serving cell (e.g., the first cell) changes to deactivated. In one example, deactivation is implicit, i.e., no deactivation command is issued. For example, deactivation occurs simultaneously with the LTM TCI status indicated in the applied cell handover command. In another example, deactivation occurs during the transmission of the MAC CE with the cell handover command on the channel. (For example, the start or end of the channel) after which, Configuration and / or updates can be performed via RRC signaling and / or MAC CE signaling and / or L1 control signaling. In another example, deactivation occurs when an acknowledgment (e.g., a positive acknowledgment) is sent to the MAC CE via a cell handover command at the time the channel (e.g., the start or end of the channel) is activated. After that, among them Configuration and / or updates can be made via RRC signaling and / or MAC CE signaling and / or L1 control signaling. In one example, deactivation occurs from the time the LTM TCI state is applied. After that, among them Configuration and / or updates can be performed via RRC signaling and / or MAC CE signaling and / or L1 control signaling.

[0202] In another example, deactivation is explicit, meaning there is a signal (e.g., MAC CE or DCI format) for deactivating the active TCI status code point of the serving cell (e.g., the first cell). In one example, the deactivation signal is sent to the UE after the LTM TCI status in the applied cell handover command. In another example, the deactivation signal is sent to the UE after the cell handover command is acknowledged (e.g., positive ack).

[0203] In one example, refer to Figure 9 Following a cell handover command, the active LTM TCI state or TCI state code point of the candidate cell continues to be used. In one example, the DCI format (e.g., DCI format 1_1 or DCI format 1_2 with or without DL assignment) can indicate one of the active LTM TCI states or LTM TCI state code points.

[0204] In one example ( Figure 9 (Not shown in the image), after a cell handover command, the active LTM TCI state or LTMTCI state code point becomes deactivated (in one example, in addition to the LTM TCI state indicated in the cell handover command; in another example, in addition to the active LTM TCI state or LTMTCI state code point of the candidate cell for the TCI indicated in the cell handover command). In one example, deactivation is implicit, i.e., no deactivation command exists. For example, deactivation occurs simultaneously with the application of the LTM TCI state indicated in the cell handover command. In another example, deactivation occurs during the transmission of the MAC CE with the cell handover command on the channel. (For example, the start or end of the channel) after which, Configuration and / or updates can be performed via RRC signaling and / or MAC CE signaling and / or L1 control signaling. In another example, deactivation occurs when an acknowledgment (e.g., a positive acknowledgment) is sent to the MAC CE via a cell handover command at the time the channel (e.g., the start or end of the channel) is activated. After that, among them Configuration and / or updates can be made via RRC signaling and / or MAC CE signaling and / or L1 control signaling. In one example, deactivation occurs from the time the LTM TCI state is applied. After that, among them Configuration and / or updates can be performed via RRC signaling and / or MAC CE signaling and / or L1 control signaling.

[0205] In another example, deactivation is explicit; that is, there is a signal (e.g., MAC CE or DCI format) that deactivates the active LTM TCI state or LTM TCI state code point (in one example, in addition to the LTM TCI state indicated in the cell handover command). In one example, the deactivation signal is sent to the UE (e.g., UE 116) after the LTM TCI state in the cell handover command is applied. In another example, the deactivation signal is sent to the UE after the cell handover command is acknowledged (e.g., positive ack).

[0206] In one example, after a cell handover to a candidate cell (e.g., referred to as the second cell or the new serving cell), the network (e.g., network 130) may send a MAC CE to the UE to activate the TCI state of the second cell. The third set of TCI states is configured by higher-layer (e.g., RRC) signaling of the second cell. The third set of TCI states may include one or more of the following (as described herein):

[0207] List of DL or combined TCI status

[0208] UL TCI Status List

[0209] In one example, the third set of TCI states for the second cell is a superset of the LTM TCI states (the second set of TCI states) configured for the second cell (e.g., as a candidate cell). The LTM TCI states (the second set of TCI states) configured for the candidate cell (the second cell) are a subset of the third set of TCI states configured for the second cell (e.g., used after cell handover as described in this disclosure). This allows the continued use of LTM TCI states after cell handover, which can reduce UE complexity. In one example, the same TCI states in the second and third sets (e.g., having the same source RS and QCL / spatial relationship type) have the same TCI state ID. In another example, the same TCI states in the second and third sets (e.g., having the same source RS and QCL / spatial relationship type) may have different TCI state IDs.

[0210] In one example, the third set of TCI states for the second cell is equivalent to the set of LTM TCI states (second set TCI states) configured for the second cell (e.g., as a candidate cell). In one example, the same TCI states in the second and third sets (e.g., having the same source RS and QCL / spatial relationship type) have the same TCI state ID. In one example, the same TCI states in the second and third sets (e.g., having the same source RS and QCL / spatial relationship type) may have different TCI state IDs.

[0211] In one example, the third set of TCI states for the second cell is a subset of the LTM TCI states (second set of TCI states) configured for the second cell (e.g., as a candidate cell). In one example, the same TCI states in the second and third sets (e.g., having the same source RS and QCL / spatial relationship type) have the same TCI state ID. In one example, the same TCI states in the second and third sets (e.g., having the same source RS and QCL / spatial relationship type) may have different TCI state IDs.

[0212] Set A is a superset of set B when all elements of set B are also elements of set A. Set A is equivalent to set B when all elements of set A are also elements of set B, and vice versa. Set A is a subset of set B when all elements of set A are also elements of set B.

[0213] In one example, the third set of TCI states can be configured for the second cell before the cell handover command is sent to the UE.

[0214] TCI states can have source RSs for QCL or for spatial relations, where source RSs can be associated with the following:

[0215] The second residential area (i.e., the new service area)

[0216] Cells with a different PCI than the second cell (i.e., the new serving cell).

[0217] The source RS can be an SS / PBCH block or an NZP CSI-RS resource.

[0218] refer to Figure 9 and Figure 10 A subset of TCI states from the third set of TCI states can be activated via MAC CE signaling. The activated subset of TCI states consists of code points that can be indicated to the UE in DCI format. The number of activated TCI state code points is M1. Code points may include:

[0219] Joint TCI status for joint (DL and UL) beam indication;

[0220] DL TCI status for individual beam indication;

[0221] UL TCI status for individual beam indication; and / or

[0222] A pair of DL TCI states and UL TCI states for individual beam indication;

[0223] The active TCI status code point from the second cell can be indicated to the UE via DCI format (e.g., DCI format 1_1 or DCI format 1_2, with or without DL allocation).

[0224] In one example ( Figure 9 In the example shown (not shown), after the MAC CE activates the TCI status code point of the second cell, the activated TCI status code point of the serving cell (e.g., the first cell) becomes deactivated. In one example, deactivation is implicit, i.e., there is no deactivation command. For example, deactivation occurs simultaneously with the activation of the TCI status code point of the second cell. In another example, deactivation occurs at the time the channel transmits the MAC CE that activates the TCI status code point of the second cell. (e.g., the start or end of the channel) after which, Configuration and / or updates can be made via RRC signaling and / or MAC CE signaling and / or L1 control signaling. In another example, deactivation occurs at the time when the channel (e.g., the start or end of the channel) transmits an acknowledgment (e.g., a positive acknowledgment) to the TCI status code point for MAC CE activation of the second cell. After that, among them Configuration and / or updates can be performed via RRC signaling and / or MAC CE signaling and / or L1 control signaling. In one example, deactivation occurs from the time of activation of the TCI state of the second cell. After that, among them Configuration and / or updates can be performed via RRC signaling and / or MACCE signaling and / or L1 control signaling.

[0225] In another example, deactivation is explicit, meaning there is a signal (e.g., MAC CE or DCI format) to deactivate the active TCI status code point of the serving cell (e.g., the first cell). In one example, a deactivation signal is sent to the UE after activating the TCI status of the second cell. In another example, a deactivation signal is sent to the UE after acknowledging (e.g., positive ack) the MAC CE that activates the TCI status code point of the second cell.

[0226] In one example, refer to Figure 9 After the MAC CE activates the TCI status code of the second cell, the activated LTM TCI status code becomes deactivated (in one example, except for the TCI status indicated in the cell handover command). In one example, deactivation is implicit, i.e., there is no deactivation command. For example, deactivation occurs simultaneously with the activation of the TCI status code of the second cell. In another example, deactivation occurs at the time the channel transmits the MAC CE activating the TCI status code of the second cell. (e.g., the start or end of the channel) after which, Configuration and / or updates can be made via RRC signaling and / or MAC CE signaling and / or L1 control signaling. In another example, deactivation occurs at the time when the channel (e.g., the start or end of the channel) transmits an acknowledgment (e.g., a positive acknowledgment) to the TCI status code point for MAC CE activation of the second cell. After that, among them Configuration and / or updates can be performed via RRC signaling and / or MAC CE signaling and / or L1 control signaling. In one example, deactivation occurs from the time of activation of the TCI state of the second cell. After that, among them Configuration and / or updates can be performed via RRC signaling and / or MAC CE signaling and / or L1 control signaling.

[0227] In another example, deactivation is explicit, i.e., there is a signal (e.g., MAC CE or DCI format) that deactivates the active LTM TCI state or LTM TCI state code point (in one example, besides the TCI state indicated in the cell handover command). In one example, a deactivation signal is sent to the UE after activating the TCI state of the second cell. In one example, a deactivation signal is sent to the UE after acknowledging (e.g., positive ack) the MAC CE activating the TCI state code point of the second cell.

[0228] In one example ( Figure 9 (Not shown in the image) After the first time DCI format indicates the TCI status code point of the second cell, the active TCI status code point of the serving cell (e.g., the first cell) becomes deactivated. In one example, deactivation is implicit, i.e., there is no deactivation command. For example, deactivation occurs simultaneously with the application of the indicated TCI status code point of the second cell. In another example, deactivation occurs during the transmission of a channel (e.g., the start or end of the channel) having the DCI format for the indicated TCI status code point of the second cell. After that, among them Configuration and / or updates can be made via RRC signaling and / or MAC CE signaling and / or L1 control signaling. In another example, deactivation occurs at the time when the channel (e.g., the start or end of the channel) conveys an acknowledgment (e.g., a positive acknowledgment) in DCI format to the TCI status code point of the indicated second cell. After that, among them Configuration and / or updates can be made via RRC signaling and / or MAC CE signaling and / or L1 control signaling. In one example, deactivation occurs from the time the TCI state of the second cell is applied. After that, among them Configuration and / or updates can be performed via RRC signaling and / or MAC CE signaling and / or L1 control signaling.

[0229] In another example, deactivation is explicit, meaning there is a signal (e.g., MAC CE or DCI format) indicating the active TCI status code point of the serving cell (e.g., the first cell) for deactivation. In one example, the deactivation signal is sent to the UE after the TCI status of the second cell is applied. In another example, the deactivation signal is sent to the UE after the DCI format indicating the TCI status code point of the second cell is acknowledged (e.g., positive ack).

[0230] In one example ( Figure 9 (Not shown in the image) After the first time-of-use DCI format indicates the TCI status code point of the second cell, the active LTM TCI state or LTM TCI status code point becomes deactivated. In one example, deactivation is implicit, i.e., there is no deactivation command; for example, deactivation occurs simultaneously with the application of the indicated TCI status code point of the second cell. In another example, deactivation occurs at the time when the channel (e.g., the start or end of the channel) with the DCI format for the indicated TCI status code point of the second cell is communicated. After that, among them Configuration and / or updates can be made via RRC signaling and / or MAC CE signaling and / or L1 control signaling. In another example, deactivation occurs at the time when the channel (e.g., the start or end of the channel) conveys an acknowledgment (e.g., a positive acknowledgment) in DCI format to the TCI status code point of the indicated second cell. After that, among them Configuration and / or updates can be made via RRC signaling and / or MAC CE signaling and / or L1 control signaling. In one example, deactivation occurs from the time the TCI state of the second cell is applied. After that, among them Configuration and / or updates can be performed via RRC signaling and / or MAC CE signaling and / or L1 control signaling.

[0231] In another example, deactivation is explicit, meaning there is a signal (e.g., MAC CE or DCI format) indicating the activation of the LTM TCI state or LTM TCI state code point. In one example, the deactivation signal is sent to the UE after the TCI state of the second cell is applied. In another example, the deactivation signal is sent to the UE after the DCI format indicating the TCI state code point of the second cell is acknowledged (e.g., positive ack).

[0232] exist Figure 9 and Figure 10 In a variant of the example, the third set of TCI states for the second cell includes:

[0233] Includes a DL or a combined list of TCI states; and / or

[0234] Includes a list of UL TCI states with a TCI state.

[0235] After a time T elapses following the cell handover command, for example, the time T from the end of the confirmation (e.g., affirmative Ack) of the MAC CE carrying the cell handover command, the UE applies a combined TCI state or a DL TCI state and / or a UL TCI state.

[0236] exist Figure 9 and Figure 10 In a variant of the example, the UE activates the code point set of the second cell from the third set of TCI states.

[0237] In one example, the set of active TCI state code points includes a code point (e.g., for a combined TCI state, or for a pair of DL and UL TCI states).

[0238] In one example, the TCI state code points activated by this set include one code point for the DL TCI state and one code point for the UL TCI state.

[0239] After MAC CE activation, apply the TCI status code point, TCI status, and

[0240] In one example, the active TCI status code point of the serving cell (e.g., the first cell) becomes deactivated as described in this article.

[0241] In one example, an active LTM TCI state or LTM TCI status code point becomes deactivated after the example described in this article.

[0242] In one example, when the UE supports NZP CSI-RS resources (e.g., tracking reference signals) as the source RS for the LTM TCI state of the candidate cell, the NZP CSI-RS resources are configured with LTM TCI states for quasi-co-location information.

[0243] In TS 38.331 [Reference 6], NZP-CSI-RS resource IE

[0244] NZP-CSI-RS-Resource ::= SEQUENCE {

[0245] nzp-CSI-RS-ResourceId NZP-CSI-RS-ResourceId,

[0246] resourceMapping CSI-RS-ResourceMapping,

[0247] powerControlOffset INTEGER (-8..15),

[0248] powerControlOffsetSS ENUMERATED{db-3, db0, db3, db6}OPTIONAL,-- Need R

[0249] scramblingID ScramblingId,

[0250] periodicityAndOffset CSI-ResourcePeriodicityAndOffsetOPTIONAL,-- Cond PeriodicOrSemiPersistent

[0251] qcl-InfoPeriodicCSI-RS TCI-StateIdOPTIONAL,--Cond Periodic ...

[0253] }

[0254] In one example, the TCI State ID can be the TCI-StateId of the serving cell as described herein. In another example, the TCI State ID can be the LTM-tci-StateId of the LTM candidate cell as described herein.

[0255] Figure 17According to embodiments of this disclosure, a diagram of an exemplary list 1700 of NZP CSI-RS resources is shown. For example, the list of NZP CSI-RS resources 1700 can be generated by… Figure 1 References to any of UEs 111-116 (such as UE 112). This example is for illustrative purposes only, and other embodiments may be used without departing from the scope of this disclosure.

[0256] In one example, refer to Figure 17 There exists a pool or list of NZP CSI-RS resources, where the qcl-info for some CSI-RS resources is provided by TCI-StateId, and the qcl-info for others is provided by LTM-tci-StateId. For example, qcl-InfoPeriodicCSI-RS can be given by the following formula:

[0257] qcl-InfoPeriodicCSI-RS CHOICE {

[0258] TCI-StateId,

[0259] LTM-tci-StateId

[0260] },

[0261] Figure 18 A diagram illustrates an example list of NZP CSI-RS resources 1800 according to an embodiment of this disclosure. For example, the list of NZP CSI-RS resources 1800 can be generated by… Figure 1 References to any of UEs 111-116 (such as UE 113). This example is for illustrative purposes only, and other embodiments may be used without departing from the scope of this disclosure.

[0262] In one example, refer to Figure 18 There are two pools or lists of NZP CSI-RS resources, where the qcl-info for NZP CSI-RS resources in the first pool or list is provided by TCI-StateId, and the qcl-info for NZPCSI-RS resources in the second pool or list is provided by LTM-tci-StateId.

[0263] exist Figure 17 In a variant of the example, there are multiple pools or lists of NZPCSI-RS resources with qcl-info provided by LTM-tci-StateId, where each candidate cell has a pool or list of NZP CSI-RS resources.

[0264] In one example, the LTM TCI state has a source RS for quasi-co-location or spatial relationships, and the source RS can be:

[0265] The SS / PBCH block (SSB) of the candidate cell is determined by the PCI index of the candidate cell and the SSB index within the SSB of the candidate cell; and / or

[0266] It has NZP CSI-RS resources with qcl-info provided by LTM-tci-StateId.

[0267] In one example, the UE is configured with a list of cells that apply the same TCI state. This cell list is applied to the first serving cell prior to the cell handover command.

[0268] In one example, the UE receives the configuration of candidate cells, where for each candidate cell, the UE is configured with a list of cells that apply the same TCI state.

[0269] In another example, for candidate cells, the UE uses the same list of cells configured for the serving cell.

[0270] The UE receives a cell handover command to switch to one of the candidate cells. In one example, after the cell handover, the UE applies the LTM TCI state to the cell that is in the same list as the candidate cell.

[0271] In one example, a cell handover command may include a flag indicating whether the TCI state indicated in the cell handover command (and activated if applicable) is applied only to candidate cells or to additional cells determined by the configured cell list of TCI states applied.

[0272] In one embodiment, the UE determines the transmit power of the uplink transmission on the candidate cell after cell handover.

[0273] In one example, the PUSCH transmit power is given by (TS 38.213 [Reference 3] Clause 7.1.1):

[0274] dBm.

[0275] In one example, the PUCCH transmit power is given by (TS 38.213 [Reference 3] Clause 7.2.1):

[0276] dBm.

[0277] In one example, the SRS transmit power is given by (TS 38.213 [Reference 3] Clause 7.3.1):

[0278] dBm.

[0279] In one example, to determine the transmit power according to the equation described in this article, the following parameters can be used:

[0280] Path loss reference signal, for example, used for ; and / or

[0281] Power control parameters of each of PUSCH, PUCCH, and SRS , and closed-loop index

[0282] In one example, the LTM TCI state includes (e.g., configured) a path loss reference signal ID; for example, the LTM TCI state could be a joint TCI state or a UL TCI state. In one example, the path loss reference signal ID could be the ID of a reference signal (e.g., a CSI-RS or SS block) used for PUSCH, PUCCH, and SRS path loss estimation. In one example, this field refers to an element in a list configured for a candidate cell, where the joint or UL TCI state is applied by the UE. In one example, the path loss reference signal could be the SS / PBCH block of the candidate cell (e.g., determined by the candidate cell index and the candidate cell's SSB index). In one example, the path loss reference signal could be an NZP CSI-RS associated with a candidate cell as described herein. In one example, the NZP CSI-RS is a periodic RS.

[0283] In one example, the path loss reference signal ID is not included (e.g., not configured) in the LTM TCI state, and the UE may use a source reference signal for QCL or spatial relationships as the path loss reference signal in the LTM TCI state (e.g., joint or UL TCI state). In one example, the path loss reference signal may be the SS / PBCH block of the candidate cell (e.g., determined by the candidate cell index and the SSB index of that candidate cell). In one example, the path loss reference signal may be the NZP CSI-RS associated with the candidate cell as described herein. In one example, the NZP CSI-RS is a periodic RS.

[0284] In one example, the mobility (LTM) TCI state triggered by L1 / L2 (e.g., joint or UL TCI state) includes Uplink-powerControlId.

[0285] In one example, Uplink-powerControlId refers to P0AlphaSetForPUSCH, P0AlphaSetForPUCCH, and P0AlphaSetForSRS for PUSCH, PUCCH, and SRS, where each of P0AlphaSetForPUSCH, P0AlphaSetForPUCCH, and P0AlphaSetForSRS includes:

[0286] p0 INTEGER (-16..15)OPTIONAL, -- Need R

[0287] alpha AlphaOPTIONAL, -- Need S

[0288] closedLoopIndex ENUMERATED { i0, i1}

[0289] In the variant example, α is not included, and α equals 1.

[0290] In the variant example, closedLoopIndex is not included, and the index of closedLoop is 10.

[0291] In the variant example, closedLoopIndex is not included, and closed-loop power control is not used.

[0292] In one example, Uplink-powerControlId refers to the common P0AlphaSet used for PUSCH, PUCCH, and SRS, where P0AlphaSet includes:

[0293] p0 INTEGER (-16..15)OPTIONAL, -- Need R

[0294] alpha AlphaOPTIONAL, -- Need S

[0295] closedLoopIndex ENUMERATED { i0, i1}

[0296] In the variant example, α is not included, and α equals 1.

[0297] In the variant example, α is not included, and α equals 0.

[0298] In the variant example, closedLoopIndex is not included, and the index of closedLoop is i0.

[0299] In the variant example, closedLoopIndex is not included, and closed-loop power control is not used.

[0300] In one example, the LMT TCI state (e.g., combined or UL TCI state) does not include the Uplink-powerControlId. Uplink power control parameters can be configured by RRC and / or MAC CE.

[0301] In one example, UL power control parameters can be configured individually for each of PUSCH, PUCCH, and / or SRS.

[0302] In one example, the UL power control parameters are common to PUSCH, PUCCH, and SRS.

[0303] In one example, the power control parameters include p0, α, and closedLoopIndex.

[0304] In one example, α is not configured, and α equals 1.

[0305] In one example, α is not configured, and α equals 0.

[0306] In one example, closedLoopIndex is not configured, and closedLoopIndex is i0.

[0307] In one example, closedLoopIndex is not configured, and closed-loop power control is not used.

[0308] In one example, the LMT TCI state (e.g., combined or UL TCI state) does not include the Uplink-powerControlId. The uplink power control parameters are not configured by higher layers.

[0309] In one example, p0 is 0.

[0310] In one example, α is 1.

[0311] In one example, α is 0.

[0312] In one example, closedLoopIndex is i0.

[0313] In one example, closed-loop power control is not used.

[0314] In one example, the transmit power is determined based on the latest Physical Random Access Channel (PRACH) transmit power on the candidate cell for uplink transmission (e.g., using PDCCH commands). In another example, the transmit power for PUSCH... :in It features the latest PRACH transmission power, and It is an offset that can be configured by higher layers (e.g., RRC signaling and / or MAC CE signaling). As shown in the equations described herein. In one example, similar equations can be used for PUCCH and SRS. In one example, separate configurations are provided for each of PUSCH, PUCCH, and SRS. In one example, the same configuration is used for PUSCH, PUCCH, and / or SRS. In one example, α is 1. In another example, α is 0. In one example, closedLoopIndex is i0. In one example, closed-loop power control is not used. In one example, the path loss RS can be a reference signal used for path loss estimation by the corresponding PRACH transmission.

[0315] The time unit for DL ​​and UL signaling on a cell is a symbol. A symbol belongs to a time slot that includes multiple symbols (such as 14 symbols). A time slot can also be used as a time unit. A bandwidth (BW) unit is called a resource block (RB). An RB includes multiple subcarriers (SCs). For example, a time slot can have a duration of one millisecond, and an RB can have a bandwidth of 180 kHz and include 12 SCs with an interval of 15 kHz between SCs. As another example, a time slot can have a duration of 0.25 milliseconds and include 14 symbols, and an RB can have a BW of 720 kHz and include 12 SCs with an SC interval of 60 kHz. An RB in a symbol of a time slot is called a physical RB (PRB) and includes multiple resource elements (REs). A time slot can be a full DL time slot, a full UL time slot, or a hybrid time slot similar to a special subframe in a Time Division Duplex (TDD) system (see also Reference 1).

[0316] Figure 19 A diagram illustrating an example OFDM waveform 1900 according to an embodiment of the present disclosure is shown. For example, OFDM waveform 1900 can be derived from... Figure 1 Any of UEs 111-116 may be used. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0317] Figure 20 A diagram illustrating an example FFT window 2000 according to an embodiment of the present disclosure is shown. For example, the FFT window 2000 may be... Figure 3 UE 116 or Figure 2 The gNB 102 is utilized. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0318] refer to Figure 19 NR uses cyclic prefix (CP)-OFDM and discrete Fourier transform-spread-orthogonal frequency division multiplexing (DTF-s-OFDM) waveforms for uplink transmission [1], namely for the physical uplink shared channel (PUSCH) and physical uplink control channel (PUCCH). Both waveforms include a (cyclic prefix) CP appended to the front of each symbol. The CP is the last few samples of the OFDM symbol appended to the front of the symbol. The base station estimates the round-trip time between the UE and the base station. For example, this can be initially estimated using the PRACH channel during random access. The base station signals a time advance (TA) command to advance the uplink transmission time of the UE, for example, by the duration of the round-trip delay, so that the uplink transmission from the UE and the n-TimingAdvanceOffset (e.g., PUSCH or PUCCH) arrive aligned with the base station reference timing, such as Figure 20 As shown. Each user is synchronized to the same reference time; this maintains orthogonality among users. Reference Figure 20 The start time of symbol n for user 0, for example, symbol n may correspond to symbol zero of a radio frame, and is precisely aligned with the base station's reference time. For user 1, the start time of symbol n is slightly delayed from the base station's reference time. For user 2, the start time of symbol n is delayed more than the base station's reference time. This could be due to timing alignment errors, for example. For user 3, the start time of symbol n is advanced by a significant amount of time from the base station's reference time, which could also be due to timing alignment errors, for example.

[0319] The first stage of an NR baseband receiver is CP removal, followed by a Fast Fourier Transform (FFT) operator, which transforms the OFDM symbols from the time domain to the frequency domain. (Reference) Figure 20 An example of an FFT window is shown. In this example, the FFT window for symbol n begins at CP / 2 after the base station's reference time, where CP is the duration of the cyclic prefix, and the duration of the FFT window is large enough to include the samples required for the FFT operation. Note that in this example, since the FFT window begins in the middle of CP rather than at the end of CP, a time adjustment of CP / 2 can be performed in the frequency domain (after the FFT) to compensate for the CP / 2 offset. If the user's misalignment is within the CP range, i.e., for Figure 20 The example shown, within the range of [-CP / 2, CP / 2], then only... Within the CP range, user i's signal is cyclically delayed. For example, user 1 was delayed. Therefore, within the FFT window of symbol n, the sample belongs to symbol n. In this case, there is no inter-symbol interference. The delay is within the CP range. It is converted into a phasor after FFT and can be easily estimated and compensated. (Reference) Figure 20 ,if If the value is greater than the CP range, inter-symbol interference may occur for users 2 and 3. For user 2, This exceeds CP / 2, therefore, within the FFT window of symbol n, there are samples from symbol n-1, causing inter-symbol interference and thus reducing performance. For user 3, Since the value is less than -CP / 2, there are samples from symbol n+1 in the FFT window of symbol n, causing inter-symbol interference and thus reducing performance.

[0320] When a UE (e.g., UE 116) communicates with multiple TRPs, the distance between the UE and each TRP can be different. If the UE uses a common UL transmission time to send to a TRP, the UE's reception may be aligned with the reception reference time of one TRP, but misaligned with the reception reference times of other TRPs (beyond the CP), resulting in inter-symbol interference and orthogonality loss at other TRPs. One way to avoid this problem is to allow multiple UL transmission times from the UE, where each transmission time corresponds to a TRP.

[0321] The TA of the second TRP can be determined based on a measurement of the differential DL propagation delay of the reference signals from the first TRP and the second TRP at the UE. The TA of the second TRP can also be determined based on a random access procedure toward the second TRP. Further details are as set forth in U.S. Patent Application No. 18 / 177,744 ('744 application), filed March 2, 2023, which is incorporated herein by reference in its entirety.

[0322] One or two TA values ​​can be signaled to the UE. The UE determines the UL transmission time toward each TA based on the one or two signaled TA values. The UE can determine the UL transmission timing to use based on the TCI state of the UL transmission (e.g., beam) and its association with the TAG ID or the TA location within the TAG. Further details are described in U.S. Patent Application No. 18 / 177,753 ('753 application), filed March 2, 2023, the entire contents of which are incorporated herein by reference.

[0323] The unified (primary, dominant, or indicative) TCI state is the UE-dedicated reception TCI state on PDSCH / PDCCH and CSI-RS, where, when conforming to the unified TCI state, the TCI state provides reference signals for quasi-co-addressing of DMRS for PDSCH and PDCCH in CC and CSI-RS. The unified (primary, dominant, or indicative) TCI state is the UE-dedicated reception TCI state on PUSCH and PUCCH resources based on dynamic granting / configuration granting and SRS, where the TCI state, when conforming to the unified TCI state, provides UL TX spatial filtering for PUSCH and PUCCH resources based on dynamic granting and configuration granting in CC and SRS.

[0324] The unified TCI framework applies to intra-cell beam management, where the TCI state has a source RS that is directly or indirectly associated with the serving cell's SSB through quasi-colocation (e.g., spatial relationship). The unified TCI state framework also applies to inter-cell beam management, where the TCI state may have a source RS that is directly or indirectly associated with the cell's SSB through quasi-colocation (e.g., spatial relationship), and the cell's PCI differs from the serving cell's PCI.

[0325] Quasi-colocation (QCL) relationships can be quasi-locations with respect to one or more of the following relationships [38.214 [Reference 4] - Section 5.1.5]:

[0326] Type A, {Doppler frequency shift, Doppler spread, average delay, delay spread}

[0327] Type B, {Doppler frequency shift, Doppler spread}

[0328] Type C, {Doppler shift, average delay}

[0329] Type D, {space Rx parameter}

[0330] The UL or combined TCI state can also provide spatial relationships of the UL channel. For example, the DL source reference signal provides information about the spatial domain filter to be used for UL transmission, or the UL source reference signal provides the spatial domain filter to be used for UL transmission, such as the same spatial domain filter used for the UL source reference signal and the UL transmission.

[0331] The unified (primary, dominant, or indicator) TCI state applies at least to UE-dedicated DL and UL channels. The unified (primary or dominant) TCI can also be applied to other DL and / or UL channels and / or signals, such as non-UE-dedicated channels, CSI_RS, and sounding reference signals (SRS).

[0332] Figure 21A diagram is shown of an example MAC RAR 2100 for a Type 1 random access procedure according to an embodiment of the present disclosure. For example, the MAC RAR 2100 for a Type 1 random access procedure can be... Figure 1 Any of UEs 111-116 (such as UE 114) receives this. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0333] In NR, round-trip time can be indicated by the following formula:

[0334] The Random Access Response (RAR) of a Type 1 Random Access Procedure or the MSGB response of a Type 2 Random Access Procedure signals a 12-bit "Timing Advance Command" value, ranging from 0 to 3846. (in ,in and TA offset in units of ) Calculated as

[0335]

[0336] in, It is the subcarrier spacing configuration.

[0337] refer to Figure 21 MAC RAR (for Type 1 random access procedures) includes a 12-bit timing advance command (38.321 [Reference 5]). Figure 6 2.3-1).

[0338] refer to Figure 21 The rollback RAR (for Type 2 random access procedures) used when the MSGA PRACH is successfully received but the MSGA PUSCH is not correctly decoded includes a 12-bit timing advance command (38.321 [Reference 5]). Figure 6 .2.3a-1).

[0339] Figure 22 A diagram of an example MAC RAR 2200 for a Type 2 random access procedure is shown according to an embodiment of the present disclosure. For example, the MAC RAR 2200 for a Type 2 random access procedure may be provided by… Figure 1 The UE 111-116 (such as UE 115) receives the data. This example is for illustrative purposes only, and other embodiments may be used without departing from the scope of this disclosure.

[0340] refer to Figure 22The successful RAR (for Type 2 random access procedures) used when the MSGA PRACH is successfully received and the MSGA PUSCH is correctly decoded includes a 12-bit timing advance command. (38.321 [Reference 5]) Figure 6 .2.3a-2).

[0341] The timing advance command can also be indicated by the timing advance MAC (Item 6.1.3.4 of TS 38.321 [Reference 5]), where The value can be changed by the "Timing Advance Command" in the MAC CE. For example, the Timing Advance MAC CE indicates a value in the range of 0, 1, ..., 63 (e.g., a 6-bit value). The value of "Timed Advance Command". (in ,in and Updates (new) in units of ) Value relative to the previous (old) The value is given by the following formula:

[0342]

[0343] in, It is the subcarrier spacing configuration.

[0344] Figure 23 A diagram of an example timing advance command MAC CE 2300 according to an embodiment of the present disclosure is shown. For example, the timing advance command MAC CE 2300 may be generated by... Figure 1 Any of UE 111-116 (such as Figure 3 The UE 116) shall be complied with. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0345] refer to Figure 23 The timing advance command (MAC CE) includes a 6-bit timing advance command (38.321 [Reference 5]). Figure 6 .1.3.4-1). It also includes the associated TAG-ID. Absolute timing advance can also be indicated by the absolute timing advance MAC (Item 6.1.3.4a of TS 38.321 [Reference 5]), where the signaled value is a 12-bit "timing advance command" ( ).by (in ,in and TA offset in units of ) Calculated as

[0346]

[0347] in, It is the subcarrier spacing configuration.

[0348] Figure 24 A diagram is shown of an example absolute timing advance command MAC CE 2400 according to an embodiment of the present disclosure. For example, Figure 1 Any of UE 111-116 (such as Figure 3 The UE 116 can comply with the absolute timing advance command MAC CE2400. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0349] refer to Figure 24 The absolute timing advance command (MAC CE) includes a 12-bit timing advance command (38.321 [Reference 5]). Figure 6 (1.3.4a-1). It also includes the associated TAG-ID.

[0350] NR supports four different sequence lengths for random access preamble sequences:

[0351] The sequence length of 839 is used with subcarrier spacings of 1.25 kHz and 5 kHz, with either an unrestricted or restricted set.

[0352] The sequence length 139 is used with subcarrier spacings of 15 kHz, 30 kHz, 60 kHz and 120 kHz, with an unlimited set.

[0353] The sequence length is 571, used with a subcarrier spacing of 30 kHz, and has an unrestricted set.

[0354] The sequence length of 1151 is used in conjunction with a subcarrier spacing of 15 kHz, and has an unrestricted set.

[0355] The RACH preamble is transmitted in a PRACH timing (RO). Depending on the preamble sequence length, the subcarrier spacing of the preamble, the subcarrier spacing of the PUSCH in the UL bandwidth portion (BWP), and the preamble format, each RO determines the time and frequency resources for transmitting the preamble, the resources allocated to the RO in the frequency domain (e.g., the number of PRBs), and the resources allocated to the RO in the time domain (e.g., the number of OFDMA symbols or time slots). Multiple PRACH timings can be FDMed within a single timing instance. This is provided by the higher-layer parameter msg1-FDM. The timing instance of the PRACH timing is determined by the higher-layer parameter prach-ConfigurationIndex and Tables 6.3.3.2-2, 6.3.3.2-3, and 6.3.3.2-4 of TS 38.211 [Reference 1].

[0356] SSBs are associated with ROs. The number of SSBs associated with a RO can be provided by high-level parameters such as ssb-perRACH-OccasionAndCB-PreamblesPerSSB and ssb-perRACH-Occasion. The number of SSBs per RO can be {1 / 8, 1 / 4, 1 / 2, 1, 2, 4, 8, 16}. When the number of SSBs per RO is less than 1, multiple ROs are associated with the same SSB. The SS / PBCH block indexes provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon are mapped to valid PRACH timings in the following order [38, 213][Reference 3]:

[0357] First, within a single PRACH timing, the ascending order of the preamble index.

[0358] Second, sort the frequency resource index in ascending order according to the frequency reuse PRACH timing.

[0359] Third, the time resource indexes are in ascending order according to the time multiplexing PRACH timing within the PRACH time slot.

[0360] Fourth, follow the ascending order of the PRACH slot index.

[0361] The association period starts from frame 0 and is used to map the SS / PBCH block index to the PRACH timing.

[0362] Figure 25 A flowchart 2500 of an example two-step random access procedure according to an embodiment of the present disclosure is shown. For example, Figure 1 Any of UE 111-116 (such as Figure 3UE 116 and BS (such as BS 103) can follow the flowchart 2500 of the Example 2-step random access procedure. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0363] The random access procedure can be initiated by the PDCCH command, the MAC entity, or the RRC.

[0364] There are two types of random access procedures: Type 1 random access procedure and Type 2 random access procedure.

[0365] Type 1 random access procedure, also known as the four-step random access procedure (4-step RACH), such as Figure 25 As shown:

[0366] In 2510, the UE sends a random access preamble, also known as Msg1, to the gNB. The gNB (e.g., gNB 102) attempts to receive and detect the preamble.

[0367] In 2520, when the gNB receives the preamble, it sends a Random Access Response (RAR), also known as Msg2, to the UE. This response includes a Time Adjustment (TA) command and fields such as uplink grant for subsequent PUSCH transmissions.

[0368] In 2530, after receiving the RAR, the UE sends a PUSCH transmission authorized and scheduled by the RAR, and performs time adjustment based on the TA received in the RAR. The Msg3 or PUSCH authorized and scheduled by the RAR UL may include an RRC reconfiguration complete message.

[0369] In 2540, when the gNB receives the RRC reconfiguration complete message, it allocates downlink and uplink resources to the UE for transmission in the downlink PDSCH transmission.

[0370] After the final step, the UE can continue to receive and send data services.

[0371] Type 1 random access procedure (4-step RACH) can be either contention-based random access (CBRA) or contention-free random access (CFRA). The CFRA procedure ends after the random access response. The following message is not part of the random access procedure. For CFRA, in 2505, the gNB indicates to the UE the preamble to be used.

[0372] Figure 26 A flowchart 2600 of an example two-step random access procedure according to an embodiment of the present disclosure is shown. For example, Figure 1Any of the UEs 111-116 (such as UE 113) and BSs (such as BS 102) can follow the flowchart 2600 of the Example 2-step random access procedure. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0373] refer to Figure 26 Version 16 introduced a new random access procedure, Type 2 random access procedure, also known as the 2-step random access procedure (2-step RACH), which in version 2610 combines the preamble and PUSCH transmissions into a single transmission from the UE to the gNB, referred to as MsgA. Similarly, in version 2620, the RAR and PDSCH transmissions (e.g., Msg4) are combined into a single downlink transmission from the gNB to the UE, referred to as MsgB.

[0374] Type 2 random access procedures can be either contention-based random access (CBRA) or contention-free random access (CFRA). For CFRA, in 2605, the gNB indicates to the UE the preamble and PUSCH to be used.

[0375] The random access procedure can be triggered by a PDCCH command. The PDCCH command is triggered by DCI format 1_0 with a CRC scrambled by C-RNTI, and the "Frequency Domain Resource Allocation" field is set to 1. The fields of DCI format 1_0 carrying the PDCCH command are described in Table 1 as follows:

[0376] Table 1

[0377]

[0378] If the "Random Access Preamble Index" is not zero, the PDCCH command triggers a contention-free random access preamble, where the PRACH timing is determined based on the "SS / PBCH Index" indicated in the PDCCH command and the "PRACH Mask Index" indicated in the PRACH timing associated with the SS / PBCH indicated by the "SS / PBCH Index". The "Random Access Preamble Index" indicates the preamble index to be used in the PRACH timing. If a PRACH transmission from the UE responds to the UE detecting a PDCCH command that triggers a contention-free random access procedure, the preamble can be sent based on the SSB of the DL RS co-located with the DMRS of the PDCCH command.

[0379] If the UE attempts to detect DCI format 1_0 [TS 38.321][Reference 5] with a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH command that triggers a contention-free random access procedure for the SpCell, the UE may expect the PDCCH, including DCI format 1_0 and the PDCCH command, to have the same DMRS antenna port quasi-co-addressable properties. When a PDSCH scheduled using RA-RNTI is received in response to a random access procedure triggered by a PDCCH command that triggers a contention-free random access procedure for the SpCell [TS 38.321][Reference 5], the UE may expect the DMRS port of the received PDCCH command and the DMRS port of the corresponding PDSCH scheduled using RA-RNTI to be quasi-co-addressable with the same SS / PBCH block or CSI-RS in terms of Doppler shift, Doppler spread, average delay, delay spread, and spatial RX parameters (if applicable).

[0380] If the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH command that triggers a contention-free random access procedure for the secondary cell, the UE may expect the DMRS antenna port quasi-co-address attribute of the CORESET associated with the type 1-PDCCH CSS set to receive the PDCCH including DCI format 1_0.

[0381] If the "Random Access Preamble Index" is zero, the PDCCH command triggers a contention-based random access procedure. If a PRACH transmission from the UE responds to the UE detecting a PDCCH command that triggers a contention-based random access procedure, the UE can determine the SSB for the preamble transmission and select the preamble in the PRACH context corresponding to the SSB. If the UE attempts to detect a DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH command that triggers a contention-free random access procedure, the UE can expect the DMRS antenna port quasi-co-address attributes of the PDCCH and PDSCH to be the same as the SS / PBCH block or CSI-RS resource used by the UE for PRACH association.

[0382] Embodiments of this disclosure provide a scheme for determining multiple TAs (e.g., two TAs) using a random access procedure for inter-cell and intra-cell multi-TRP scenarios. The random access procedure can be a contention-free random access (CFRA) procedure triggered by a PDCCH command.

[0383] Embodiments of this disclosure provide aspects related to determining the power of the PRACH when a PDCCH command triggers the transmission of a preamble to a TRP different from the TRP that sent the PDCCH command.

[0384] The UE can communicate with a network (e.g., network 130) through two or more spatial relationship filters (referred to herein as beams) for transmission and reception. The beams are determined by TCI states, such as the joint TCI state of the UL and DL beams, or the DL TCI state of the DL beam or the UL TCI state of the UL beam. A beam can be associated with a single TRP. Alternatively, a beam can be associated with multiple (two or more) TRPs, where the TRPs can have the same Physical Cell Identifier (PCI) (i.e., transmit SSBs associated with the same PCI), or they can have different PCIs (i.e., transmit SSBs associated with different PCIs). The round-trip propagation delay or round-trip propagation time (RTT) on each beam can be different. This could be due, for example, to different reflections and / or different propagation paths due to different distances between the UE and the TRPs. As described herein, a UL signal from the UE should arrive at each TRP at a reference time for each TRP; therefore, transmissions on each beam (e.g., to the corresponding TRP) will have different transmission times and thus different TA values ​​to arrive at the corresponding TRP at the reference time for that TRP. In this disclosure, various embodiments provide schemes for determining multiple TAs (e.g., two TAs) using a random access procedure for inter-cell and multi-TRP scenarios. The random access procedure can be a contention-free random access (CFRA) procedure triggered by a PDCCH command.

[0385] Various embodiments provide aspects related to determining the power of the PRACH when a PDCCH command triggers the transmission of a preamble to a different TRP than the TRP that sent the PDCCH command. The power is determined based on a path loss reference signal (PL-RS) used to measure the PL between the TRP and the UE. In this disclosure, various embodiments investigate how the PL-RS is determined. Various embodiments also investigate aspects related to determining the cell's TAG-ID.

[0386] This disclosure relates to 5G / NR communication systems.

[0387] This disclosure provides design aspects relating to determining multiple access control (TA) (e.g., 2 TA) using a random access procedure, wherein the random access procedure may be triggered by a PDCCH command or by a higher layer (e.g., by the UE), and the random access procedure may be a contention-free random access (CFRA) procedure, providing the following aspects:

[0388] Quasi-co-address information (e.g., TCI status) for the PDCCH demodulation reference signal (DMRS) used in PDCCH commands.

[0389] Resources used for preamble transmission.

[0390] Spatial relationship and / or power of preamble transmission

[0391] Quasi-co-location information (e.g., TCI status) used for RAR PDCCH DMRS

[0392] The search space set up for RAR.

[0393] Various embodiments also provide aspects related to determining the cell TAG-ID.

[0394] In this disclosure, RRC signaling (e.g., through the configuration of RRC signaling) includes the following: public RRC signaling, which may be RRC signaling based on a System Information Block (SIB) (e.g., SIB1 or other SIBs) or RRC-specific signaling sent to a specific UE.

[0395] In the examples disclosed herein, the UE can communicate with the network using, for example, different beams associated with the TRP. Different beams can be used at different times (e.g., switching from one beam to another), or they can be used simultaneously (e.g., simultaneously receiving from the network on multiple beams or simultaneously transmitting to the network on multiple beams). In the former example, two or more TAs can be active in the UE, but depending on the beam used for UL transmission, only one TA is used at a time. In the latter, two or more TAs can be active in the UE. When the UE transmits simultaneously on multiple UL beams, more than one TA is used simultaneously.

[0396] In one example, the UE communicates with the same TRP on two or more different beams. Different beams have different round-trip times. For example, the different round-trip times may be due to different reflections.

[0397] In another example, the UE communicates with two or more different TRPs that have the same Physical Cell Identity (PCI). The UE uses at least one beam to communicate with each TRP. The cycle delay to each TRP can be different. The TRPs can be synchronous or asynchronous. This is an example of multiple TAs within a cell (e.g., 2 TAs in the case of 2 TRPs).

[0398] In another example, the UE communicates with two or more different TRPs that have the same or different Physical Cell Identity (PCI). The UE uses at least one beam to communicate with each TRP. The cyclic delay to each TRP can be different. The TRPs can be synchronous or asynchronous. This is an example of inter-cell multiple TAs (e.g., 2 TAs in the case of 2 TRPs) when at least one TRP has a different PCI from the others.

[0399] In one example, the first TRP is associated with the first coresetpoolIndex (e.g., coresetpoolIndex 0). The second TRP is associated with the second coresetpoolIndex (e.g., coresetpoolIndex 1).

[0400] In one example, the first TRP is associated with the first group of SSBs. The second TRP is associated with the second group of SSBs.

[0401] In one example, the first TRP is associated with (or with) the PCI of the serving cell. The second TRP is associated with (or with) a cell that has a different PCI than the serving cell. This is, for example, an inter-cell multiple TRP operation.

[0402] In one example, the first TRP is associated with (or related to) the PCI of the first cell. The second TRP is associated with (or related to) the PCI of the second cell. This is an example of an inter-cell multi-TRP operation.

[0403] In one example, the first TRP and the second TRP are associated with the serving cell. This is, for example, an intra-cell multiple TRP operation.

[0404] In one example, the first TRP and the second TRP are associated with a cell. This is, for example, a multi-TRP operation within a cell.

[0405] Figure 27 A process 2700 for an example RAR according to an embodiment of the present disclosure is illustrated. For example, process 2700 may be performed by... Figure 1 Any of UE 111-116 (such as Figure 3 The UE 116 and BS (such as BS 103) are followed. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0406] The process begins at 2710, when the gNB sends a PDCCH command to the UE. At 2720, the UE sends a PRACH preamble to the gNB. At 2730, the gNB sends a RAR to the UE.

[0407] In one example, the PDCCH command triggers a contention-free random access procedure for inter-cell or intra-cell multi-TRP scenarios to determine the TA.

[0408] refer to Figure 27 This illustrates an example of a CFRA process triggered by a PDCCH command. The following aspects are provided:

[0409] TRP, beam, and / or quasi-co-address attributes used to send PDCCH commands.

[0410] The resources used for preamble transmission include PRACH timing and preamble index.

[0411] Spatial filters and / or transmit power are used for transmitting the preamble.

[0412] Quasi-co-addressing for random access responses.

[0413] In one example, the PDCCH command is sent from a TRP associated with the serving cell. For example, the TCI state of the PDCCH command includes one or more source RSs (e.g., QCL type D and / or QCL type A), and one or more source RSs are associated with the SSB of the serving cell (e.g., via QCL relationship). In this example, the PDCCH command (transmitted from the serving cell's TRP) triggers a preamble sent to either the serving cell's TRP or a non-serving cell's TRP. The PDCCH command may trigger a preamble sent to a TRP different from the TRP of the PDCCH command. For example, the spatial filter and / or transmit power of the preamble may be based on the SSB of a cell (or TRP) different from the cell (or TRP) of the PDCCH command. In one example, the PDCCH command includes a triggered RACH procedure with the PCI of the cell associated with it (i.e., the preamble is sent there), and the spatial transmit filter and / or power of the transmitted preamble is based on the SSB associated with that cell. The PCI of a cell can be (1) the PCI of the serving cell (e.g., when the PCI index in the PDCCH command is 0), or (2) the additional PCIIndex of another cell (e.g., the value of additional PCIIndex-r17 based on SSB-MTC-AdditionalPCI-r17). In one example, the PCI field has a size of N bits, where In one example, maxNrofAdditionalPCI=7, and N=3 bits. In another example, if the PCI field is 0, this indicates the serving cell; otherwise, the PCI indicates the additional PCI index of a non-serving cell. In yet another example, the PDCCH command includes a flag indicating whether the preamble is triggered for the serving cell or another cell (e.g., one of the cells corresponding to the additionalPCIIndex). In one example, the flag may indicate whether the PRACH is the same TRP as the PDCCH or a different TRP, as described in this disclosure.

[0414] In one example, the SSB used to determine the transmit power of the preamble is configured, activated, or indicated as PL-RS before the transmission of the PDCCH command. In one example, the UE (e.g., UE 116) is aware of the SSB when the PDCCH command is triggered. In one example, the time between the configuration, activation, or indication of the SSB as PL-RS and the timing of the PDCCH is... In one example, The measurement is made from the channel (start or end) of the PL-RS, which is communicated with the configuration, activation, or indication of the SSB. In another example, the channel is affirmatively acknowledged. In one example, From the channel (start or end) that communicates Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) to the channel measurement that communicates SSB as a configuration, activation, or indication of PL-RS. In another example, HARQ-ACK is a positive acknowledgment (ACK). In yet another example, HARQ-ACK can be either a positive acknowledgment (ACK) or a negative acknowledgment (NACK).

[0415] In one example, for instance, Measurements from the channel transmitting HARQ-ACK:

[0416]

[0417] In one example, for instance, Measured from the channel that communicates the configuration, activation, or indication of the SSB to the PL-RS:

[0418]

[0419] in, It is used for subcarrier spacing. The number of time slots in each subframe.

[0420] If the UE does not maintain the SSB configured as PL-RS, then NM=1; otherwise, NM=0.

[0421] In one example, an SSB configured as PL-RS is considered not maintained. In another example, an SSB configured as PL-RS is considered maintained.

[0422] It is the periodicity of the SSB configured as PL-RS.

[0423] It is the HARQ delay between the transmission channel and the receipt of HARQ-ACK feedback.

[0424] In one example, the SSB configured, activated, or indicated as PL-RS is known at the time of configuration, activation, or indication.

[0425] In one example, the SSB configured, activated, or indicated as PL-RS is unknown at the time of configuration, activation, or indication. To know the SSB, exist An additional delay τ is added to the base. Wherein, This includes additional Rx time for beam refinement as described in TS 38.133.

[0426] As described in TS 38.133: A path loss reference signal (e.g., SSB) is known if the following conditions are met during the time period between the last transmission of the RS resource used for the L1-RSRP measurement report and the completion of the path loss reference signal handover, wherein the RS resource is the target path loss reference signal or QCLed with the target path loss reference signal (with type D).

[0427] Receive path loss reference signal switching command within 1280 ms after the last transmission of RS resources used for beam reporting or measurement.

[0428] The UE has sent at least one L1-RSRP report for the target path loss reference signal before the path loss reference signal switching command.

[0429] The target path loss reference signal remains detectable during the path loss reference signal switching period.

[0430] Signal-to-noise ratio (SNR) of the target path loss reference signal -3dB.

[0431] The SSB associated with the target path loss reference signal remains detectable during the path loss reference signal switching period.

[0432] SNR of associated SSB -3dB.

[0433] Otherwise, the path loss reference signal is unknown.

[0434] In one example, when the UE measures (e.g., the SSB of the serving cell, or a cell with a different PCI than the serving cell), the UE can determine the path loss associated with the SSB. The UE can then use the transmit power determined based on the path loss associated with the SSB to transmit the PRACH preamble associated with the SSB.

[0435] In one example, when the UE measures (e.g., the SSB of the serving cell, or a cell with a PCI different from the serving PCI), the UE can determine the path loss associated with the SSB. The UE can then use the transmit power determined based on the path loss associated with the SSB to transmit the PRACH preamble associated with the SSB. A cell with a PCI associated with the SSB may not have an active TCI state (e.g., an inactive PCI or an additional PCI).

[0436] In one example, when the UE measures an SSB (e.g., that of the serving cell or a cell with a PCI different from the serving PCI), the UE can determine the path loss associated with the SSB. The UE can then use the transmit power determined based on the path loss associated with the SSB to transmit the PRACH preamble associated with the SSB. Cells with a PCI associated with the SSB have an active TCI state (e.g., active PCI or additional PCI).

[0437] In one example, when the UE measures (e.g., the SSB of the serving cell, or a cell with a different PCI than the serving cell), the UE can determine the path loss associated with the SSB. The UE can then use the transmit power determined based on the path loss associated with the SSB to transmit the PRACH preamble associated with the SSB. The SSB is associated with an active TCI state (e.g., a TCI state with a source RS that is directly or indirectly associated with the SSB (e.g., QCLed).

[0438] In one example, the UE capability can determine whether the SSB used for path loss measurement is associated with a cell that is one of the following:

[0439] The cell has an active TCI status (e.g., active PCI or additional PCI).

[0440] The unit may not have an active TCI state.

[0441] In one example, if the UE can determine the path loss from the SSB associated with a cell that has a PCI (e.g., provided by additionalPCIIndex), and that cell has no active TCI state or TCI state code point (e.g., additionalPCIIndex is inactive), then the PRACH can be triggered to the cell with the inactive additionalPCIIndex. Otherwise, if the UE cannot determine the path loss from the SSB associated with a cell that has a PCI (e.g., provided by additionalPCIIndex), and that cell has no active TCI state or TCI state code point (e.g., additionalPCIIndex is inactive), then the PRACH is triggered to the cell with an active additionalPCIIndex (e.g., with an active TCI state or TCI state code point). In one example, this can be based on UE capabilities.

[0442] In the following examples, the SSB is associated with the TCI state if one or more of the following occur:

[0443] SSB is the source RS for QCL relations or spatial relations used in TCI states.

[0444] SSB is the PL-RS (path loss RS) of the TCI state.

[0445] SSB is the source of QCL relations or spatial relations for TCI states.

[0446] SSB is the QCL source or spatial relation source of PL-RS in TCI state.

[0447] SSB is the PL-RS of the source RS for QCL relations or spatial relations of TCI states.

[0448] SSB is the PL-RS of the TCI state PL-RS.

[0449] An SSB can be a QCL source or spatial relation source through multiple (e.g., chains) TCI states or quasi-co-addressable relationships. For example, a TCI state has a PL-RS. In one example, CSI-RS1 is a PL-RS, and CSI-RS1 has an SSB as its source RS. In another example, CSI-RS1 is a PL-RS, CSI-RS1 has CSI-RS2 as its source RS, and CSI-RS2 has an SSB as its source RS. In yet another example, CSI-RS1 is a PL-RS, CSI-RS1 has CSI-RS2 as its source RS, CSI-RS2 has CSI-RS3 as its source RS, and CSI-RS3 has an SSB as its source RS, and so on. These are examples of TCI states (or PL-RS) associated with an SSB.

[0450] In the following examples, the TCI state can be the uplink TCI state in the case of a single beam indication, or the joint TCI state in the case of a joint beam indication.

[0451] In one example, a PDCCH command is sent from a first TRP, and a PRACH preamble is sent to a second TRP. In one example, the first and second TRPs are in the same cell (e.g., intra-cell). In another example, the first TRP is in the first cell, and the second TRP is in the second cell (e.g., inter-cell). The PDCCH command includes an SSB index. In one example, the SSB index is associated with an active TCI state (e.g., a TCI state activated by MAC CE). This association can be as described herein. In one example, PL-RS is the SSB indicated in the PDCCH command.

[0452] In one example, a PDCCH command is sent from a first TRP, and a PRACH preamble is sent to a second TRP. In one example, the first and second TRPs are in the same cell (e.g., intra-cell). In another example, the first TRP is in the first cell, and the second TRP is in the second cell (e.g., inter-cell). The PDCCH command includes an SSB index. In one example, the SSB index is associated with an active TCI state (e.g., a TCI state activated by MAC CE). This association can be as described herein. In one example, PL-RS is an SSB associated with an activated TCI state having the same TAG ID as the activated TCI state, which is associated with the SSB indicated in the PDCCH command.

[0453] In one example, a PDCCH command is sent from a first TRP, and a PRACH preamble is sent to a second TRP. In one example, the first and second TRPs are in the same cell (e.g., intra-cell). In another example, the first TRP is in a first cell, and the second TRP is in a second cell (e.g., inter-cell). The PDCCH command includes an SSB index. In one example, the SSB index is associated with an active TCI state (e.g., a TCI state activated by MAC CE). This association can be as described herein. In one example, PL-RS is an SSB associated with an indicated TCI state having the same TAG ID as the active TCI state associated with the SSB indicated in the PDCCH command. The indicated TCI state can be a TCI state applied by the UE for transmission on the uplink channel and / or reception on the DL channel. The indicated TCI state can be a TCI state that has been signaled to the UE via code points in the "Transmission Configuration Indicator" field of the DCI format.

[0454] In one example, a PDCCH command is sent from a first TRP, and a PRACH preamble is sent to a second TRP. In one example, the first and second TRPs are in the same cell (e.g., intra-cell). In another example, the first TRP is in the first cell, and the second TRP is in the second cell (e.g., inter-cell). The PDCCH command includes an SSB index. In one example, the SSB index is associated with an active TCI state (e.g., a TCI state activated by MAC CE). This association can be as described herein. In one example, PL-RS is an SSB associated with the first active TCI state in the list of TCI states activated by MAC CE, having the same TAG ID as the active TCI state associated with the SSB indicated in the PDCCH command.

[0455] In one example, a PDCCH command is sent from a first TRP, and a PRACH preamble is sent to a second TRP. In one example, the first and second TRPs are in the same cell (e.g., intra-cell). In another example, the first TRP is in the first cell, and the second TRP is in the second cell (e.g., inter-cell). The PDCCH command includes an SSB index. In one example, the SSB index is associated with a configured TCI state (e.g., a TCI state configured by RRC). This association can be as described herein. In one example, PL-RS is the SSB indicated in the PDCCH command.

[0456] In one example, a PDCCH command is sent from a first TRP, and a PRACH preamble is sent to a second TRP. In one example, the first and second TRPs are in the same cell (e.g., intra-cell). In another example, the first TRP is in the first cell, and the second TRP is in the second cell (e.g., inter-cell). The PDCCH command includes an SSB index. In one example, the SSB index is associated with a configured TCI state (e.g., a TCI state configured by RRC). This association can be as described herein. In one example, PL-RS is an SSB associated with an activated TCI state that has the same TAG ID as a configured TCI state associated with the SSB indicated in the PDCCH command.

[0457] In one example, a PDCCH command is sent from a first TRP, and a PRACH preamble is sent to a second TRP. In one example, the first and second TRPs are in the same cell (e.g., intra-cell). In another example, the first TRP is in the first cell, and the second TRP is in the second cell (e.g., inter-cell). The PDCCH command includes an SSB index. In one example, the SSB index is associated with a configured TCI state (e.g., a TCI state configured by RRC). This association can be as described herein. In one example, PL-RS is an SSB associated with a configured TCI state that has the same TAG ID as the configured TCI state associated with the SSB indicated in the PDCCH command.

[0458] In one example, a PDCCH command is sent from a first TRP, and a PRACH preamble is sent to a second TRP. In one example, the first and second TRPs are in the same cell (e.g., intra-cell). In another example, the first TRP is in a first cell, and the second TRP is in a second cell (e.g., inter-cell). The PDCCH command includes an SSB index. In one example, the SSB index is associated with a configured TCI state (e.g., a TCI state configured by RRC). This association can be as described herein. In one example, the PL-RS is an SSB associated with an indicated TCI state having the same TAG ID as the configured TCI state associated with the SSB indicated in the PDCCH command. The indicated TCI state can be a TCI state applied by the UE for transmission on the uplink channel and / or reception on the DL channel. The indicated TCI state can be a TCI state that has been signaled to the UE via the code point in the "Transmission Configuration Indicator" field of the DCI format.

[0459] In one example, a PDCCH command is sent from a first TRP, and a PRACH preamble is sent to a second TRP. In one example, the first and second TRPs are in the same cell (e.g., intra-cell). In another example, the first TRP is in the first cell, and the second TRP is in the second cell (e.g., inter-cell). The PDCCH command includes an SSB index. In one example, the SSB index is associated with a configured TCI state (e.g., a TCI state configured by RRC). This association can be as described herein. In one example, PL-RS is an SSB associated with the first active TCI state in the list of TCI states activated by the MAC CE, having the same TAG ID as the configured TCI state associated with the SSB indicated in the PDCCH command.

[0460] In one example, a PDCCH command is sent from a first TRP, and a PRACH preamble is sent to a second TRP. In one example, the first and second TRPs are in the same cell (e.g., intra-cell). In another example, the first TRP is in the first cell, and the second TRP is in the second cell (e.g., inter-cell). The PDCCH command includes an SSB index. In one example, the SSB index is associated with a configured TCI state (e.g., a TCI state configured by RRC). This association can be as described herein. In one example, PL-RS is an SSB associated with the first configured TCI state in the list of TCI states configured by RRC, which has the same TAG ID as the configured TCI state associated with the SSB indicated in the PDCCH command.

[0461] In one example, a PDCCH command is sent from the first TRP, and a PRACH preamble is sent to the second TRP. In one example, the first and second TRPs are in the same cell (e.g., intra-cell). In another example, the first TRP is in the first cell, and the second TRP is in the second cell (e.g., inter-cell). The PDCCH command includes an SSB index. In one example, PL-RS is the SSB indicated in the PDCCH command.

[0462] In one example, a PDCCH command is sent from a first TRP, and a PRACH preamble is sent to a second TRP. In one example, the first and second TRPs are in the same cell (e.g., intra-cell). In another example, the first TRP is in the first cell, and the second TRP is in the second cell (e.g., inter-cell). The PDCCH command includes an SSB index. In one example, PL-RS is an SSB associated with an activated TCI state, which has the same TAG ID as the TCI state associated with the SSB indicated in the PDCCH command.

[0463] In one example, a PDCCH command is sent from a first TRP, and a PRACH preamble is sent to a second TRP. In one example, the first and second TRPs are in the same cell (e.g., intra-cell). In another example, the first TRP is in the first cell, and the second TRP is in the second cell (e.g., inter-cell). The PDCCH command includes an SSB index. In one example, PL-RS is an SSB associated with a configured TCI state, which has the same TAG ID as the TCI state associated with the SSB indicated in the PDCCH command.

[0464] In one example, a PDCCH command is sent from the first TRP, and a PRACH preamble is sent to the second TRP. In one example, the first TRP and the second TRP are in the same cell (e.g., intra-cell). In another example, the first TRP is in the first cell, and the second TRP is in the second cell (e.g., inter-cell). The PDCCH command includes an SSB index. In one example, PL-RS is an SSB associated with an indicated TCI state having the same TAG ID as the TCI state associated with the SSB indicated in the PDCCH command. The indicated TCI state can be a TCI state applied by the UE for transmission on the uplink channel and / or reception on the DL channel. The indicated TCI state can be a TCI state that has been signaled to the UE via the code point in the "Transmission Configuration Indicator" field of the DCI format.

[0465] In one example, a PDCCH command is sent from the first TRP, and a PRACH preamble is sent to the second TRP. In one example, the first and second TRPs are in the same cell (e.g., intra-cell). In another example, the first TRP is in the first cell, and the second TRP is in the second cell (e.g., inter-cell). The PDCCH command includes an SSB index. In one example, PL-RS is an SSB associated with the first active TCI state in the list of active TCI states for MAC CE, having the same TAG ID as the TCI state associated with the SSB indicated in the PDCCH command.

[0466] In one example, a PDCCH command is sent from the first TRP, and a PRACH preamble is sent to the second TRP. In one example, the first and second TRPs are in the same cell (e.g., intra-cell). In another example, the first TRP is in the first cell, and the second TRP is in the second cell (e.g., inter-cell). The PDCCH command includes an SSB index. In one example, PL-RS is an SSB associated with the first configured TCI state in the TCI state list configured by RRC, having the same TAG ID as the TCI state associated with the SSB indicated in the PDCCH command.

[0467] In one example, a PDCCH command is sent from a first TRP, and a PRACH preamble is sent to a second TRP. In one example, the first and second TRPs are in the same cell (e.g., intra-cell). In another example, the first TRP is in a first cell, and the second TRP is in a second cell (e.g., inter-cell). The PDCCH command includes an SSB index. In one example, the SSB index is associated with an indicated TCI state. This association can be as described herein. In one example, PL-RS is the SSB indicated in the PDCCH command. The indicated TCI state can be a TCI state applied by the UE for transmission on the uplink channel and / or reception on the DL channel. The indicated TCI state can be a TCI state that has been signaled to the UE via the code point in the "Transmission Configuration Indicator" field of the DCI format.

[0468] In one example, a PDCCH command is sent from the first TRP, and a PRACH preamble is sent to the second TRP. The network (e.g., network 130) can configure the UE to use the indicated SSB as the PL-RS for determining the PRACH power or to use the SSB following one of the examples described herein to determine the PRACH.

[0469] In one example, a PDCCH command is sent from the first TRP, and a PRACH preamble is sent to the second TRP. The network can configure the UE to use the indicated SSB as the PL-RS for determining PRACH power, or to use the SSB associated with the indicated TCI state, which has the same TAG ID as the TCI state (e.g., an active TCI state or a configured TCI state) associated with the SSB indicated in the PDCCH command.

[0470] In one example, a PDCCH command is sent from the first TRP, and a PRACH preamble is sent to the second TRP. The UE may indicate to the network (e.g., via capability signaling) whether it has the capability to use the SSB indicated in the PDCCH command as the PL-RS (e.g., following one of the examples described herein).

[0471] In one example, a PDCCH command is sent from the first TRP, and a PRACH preamble is sent to the second TRP. The UE may (e.g., via capability signaling) indicate to the network whether it has the capability to use the SSB indicated in the PDCCH command as a PL-RS or to use an SSB associated with an indicated TCI state having the same TAG ID as the TCI state (e.g., an active TCI state or a configured TCI state) associated with the SSB indicated in the PDCCH command.

[0472] In one example, the PDCCH command is sent from a TRP associated with the serving cell or a cell configured with an additional PCIIndex. For example, the TCI state of the PDCCH command includes one or more source RSs (e.g., having QCL type D and / or QCL type A), and these one or more source RSs are associated with the SSB of the serving cell or the SSB of the cell configured with an additional PCIIndex (e.g., via QCL relationship). The following sub-examples are provided in this embodiment.

[0473] In one sub-example, the PDCCH command is sent from a TRP of one cell, and it triggers a preamble that can be sent to a TRP of another cell, for example, the spatial filter and / or transmit power of the preamble may be based on the SSB of a cell (or TRP) different from the cell (or TRP) to which the PDCCH command originates. In one example, the PDCCH command includes the PCI of the cell to which the triggered RACH procedure is associated (i.e., the preamble is sent), and the spatial transmit filter and / or power of the transmitted preamble is based on the SSB associated with that cell. The PCI of the cell may be (1) the PCI of the serving cell (e.g., when the PCI index in the PDCCH command is 0), or (2) the additional PCIIndex of another cell (e.g., the value of additional PCIIndex-r17 based on SSB-MTC-AdditionalPCI-r17). In one example, the PCI field has a size of N bits, where In one example, maxNrofAdditionalPCI=7, and N=3 bits. In another example, if the PCI field is 0, this indicates the serving cell. Otherwise, the PCI indicates the additional PCI index of a non-serving cell. In another example, the PDCCH command includes a flag (or indicator) indicating whether the preamble is triggered for the serving cell or another cell (e.g., one of the cells corresponding to the additionalPCIIndex). For example, the other cell could be a cell other than the serving cell that has an active TCI state.

[0474] In one sub-example, the PDCCH command is sent to the cell's TRP, and it triggers a preamble sent to the same cell's TRP (e.g., the same TRP used for the PDCCH command). For example, the spatial filter and / or transmit power of the preamble can be based on the SSB of the cell (or TRP) of the PDCCH command.

[0475] In one sub-example, if the PDCCH command is triggered from a TRP associated with the serving cell (e.g., the TCI state of the PDCCH command has a QCL directly or indirectly with the source RS of the serving cell), the PRACH preamble can be sent to either the serving cell or a non-serving cell, as described herein. If the PDCCH command is triggered from a TRP associated with a cell having a PCI different from that of the serving cell (e.g., the TCI state of the PDCCH command has a QCL directly or indirectly with the source RS of the cell having a PCI different from that of the serving cell), the PRACH preamble can be sent to the cell having a PCI different from that of the serving cell.

[0476] In one sub-example, if the PDCCH command is triggered from a TRP associated with the serving cell (e.g., the TCI state of the PDCCH command has a QCL directly or indirectly with the source RS of the serving cell), the PRACH preamble can be sent to either the serving cell or a non-serving cell, as described herein. If the PDCCH command is triggered from a TRP associated with a cell having a PCI different from that of the serving cell (e.g., the TCI state of the PDCCH command has a QCL directly or indirectly with the source RS of the cell having a PCI different from that of the serving cell), the PRACH preamble can be sent to the cell having a PCI different from that of the serving cell (e.g., sent to a non-serving cell).

[0477] In one example, the SSB used to determine the transmit power of the preamble is configured, activated, or indicated as PL-RS before the transmission of the PDCCH command, as described herein.

[0478] The resources used for the preamble are determined by the PRACH timing and the preamble index within the PRACH timing. The preamble index can be indicated by the PDCCH command. The PRACH timing is determined based on the SSB or CSI-RS resources associated with the preamble, using the described association pattern. In version 15, the association pattern is defined only for the SSB of the serving cell. However, in the case of multiple TRPs between cells, there is an SSB associated with the serving cell and an SSB associated with the cell corresponding to the additional PCIIndex. Therefore, one example is to define a new PRACH configuration to cover the SSB of the serving cell and the SSB on the cell corresponding to the additional PCIIndex. In the case of multiple TRPs within a cell, there is an SSB associated with the first TRP and an SSB associated with the second TRP.

[0479] In one example, the new PRACH configuration can be used to transmit preambles associated with the serving cell and the cell corresponding to the additional PCIIndex.

[0480] In one example, the new PRACH configuration can be used to transmit the preamble associated with the cell corresponding to the additional PCIIndex. The PRACH configuration in NR version 15 can be used to transmit the preamble associated with the serving cell.

[0481] In one example, the new PRACH configuration can be used to transmit the preamble associated with the cell corresponding to the additional PCIIndex. Higher-layer parameters (e.g., via RRC configuration and / or MAC CE configuration) can indicate whether the preamble associated with the serving cell is transmitted using (1) the new PRACH configuration or (2) the PRACH configuration of NR version 15.

[0482] In one example, the new PRACH configuration can be used to transmit the preamble associated with the cell corresponding to the additional PCIIndex. Indicators (e.g., flags) in the PDCCH command can indicate whether the preamble associated with the serving cell is transmitted using (1) the new PRACH configuration or (2) the PRACH configuration of NR version 15.

[0483] In one example, a separate PRACH configuration is provided for each additional PCIIndex. The PRACH configuration associated with an additional PCIIndex can be used to transmit the preamble associated with the cell corresponding to the additional PCIIndex. The PRACH configuration in NR version 15 can be used to transmit the preamble associated with the serving cell.

[0484] The following example can be evaluated for the new PRACH configuration.

[0485] This association is based on PCI-SSB pairs, meaning that each PCI-SSB pair is associated with an RO.

[0486] This association is based on SSB, where SSB is a superset of the SSB index configured across cells as provided by ssb-PositionsInBurst. In one example, "All Cells" includes the serving cell and the cell corresponding to the additionalPCIIndex. In another example, "All Cells" includes the cell corresponding to the additionalPCIIndex.

[0487] In one example, the SSB of the cell corresponding to the additionalPCIIndex is the configured additionalPCIIndex. Up to seven configured additionalPCIIndex can exist, determined by maxNrofAdditionalPCI-r17=7. In another example, the SSB of the cell corresponding to the additionalPCIIndex is the cell with an active TCI state, where a cell is considered to have an active TCI state if the source RS of the active TCI state is associated with the cell's SSB via quasi-co-addressing. An active TCI state is a TCI state activated by the MAC CE, as described in Clauses 5.18.23 and 6.1.3.47 of TS38.321 [Reference 5]. In one example, an active TCI state (or TCI state code point or active spatial relation) can be associated with the serving cell and another cell corresponding to the additionalPCIIndex. In one example, the active TCI state (or TCI status code point or active spatial relationship) can be associated with the serving cell and one or more other cells corresponding to the additional PCIIndex. Therefore, the following example is provided for the association between PRACH timing and SSB in a new RACH configuration.

[0488] This association is based on the SSB of the serving cell and the SSB of the cell corresponding to the configured additionalPCIIndex.

[0489] This association is based on the SSB of the serving cell and the SSB of the cell with a MAC CE activated TCI state corresponding to the configured additionalPCIIndex.

[0490] This association is based on the SSB of the cell corresponding to the configured additionalPCIIndex.

[0491] This association is based on the SSB of a cell with a MAC CE activated TCI state corresponding to the configured additionalPCIIndex.

[0492] In one example, the UE (e.g., UE 116) is configured with a new PRACH configuration. For example, the new RACH-ConfigGeneric and / or RACH-ConfigDedicated are used for inter-cell multi-TRP, for example.

[0493] The UE is configured with an additional PCI and an SSB associated with the additional PCI. For example, the UE may be configured with a CSI-SSB-ResourceSet, which includes a list of additional PCI indices given by servingAdditionalPCIList.

[0494] CSI-SSB-ResourceSet ::= SEQUENCE {

[0495] csi-SSB-ResourceSetId CSI-SSB-ResourceSetId,

[0496] csi-SSB-ResourceList SEQUENCE (SIZE(1..maxNrofCSI-SSB-ResourcePerSet)) OF SSB-Index,

[0497] ..., [[

[0499] servingAdditionalPCIList-r17 SEQUENCE (SIZE(1..maxNrofCSI-SSB-ResourcePerSet)) OF ServingAdditionalPCIIndex-r17 OPTIONAL -- Need R ]]

[0501] }

[0502] Here, `maxNrofCSI-SSB-ResourcePerSet` is 64, and `servingAdditionalPCIList` indicates the Physical Cell ID (PCI) of the SSB in `csi-SSB-ResourceList`. If present, this list has the same number of entries as `csi-SSB-ResourceList`. The first entry in the list indicates the PCI value used for the first entry in `csi-SSB-ResourceList`, the second entry indicates the PCI value used for the second entry in `csi-SSB-ResourceList`, and so on. For each entry, the following applies:

[0503] If the value is zero, then the PCI is the PCI that defines the serving cell of this CSI-SSB-ResourceSet.

[0504] Otherwise, the value is taken as additionalPCIIndex-r17 of SSB-MTC-AdditionalPCI-r17 in ServingCellConfig additionalPCIList-r17, and the PCI is additionalPCI-r17 of that SSB-MTC-AdditionalPCI-r17.

[0505] SSB-MTC-AdditionalPCI-r17 ::= SEQUENCE {

[0506] additionalPCIIndex-r17 AdditionalPCIIndex-r17,

[0507] additional PCI-r17 PhysCellId,

[0508] periodicity-r17 ENUMERATED { ms5, ms10, ms20,ms40, ms80, ms160, spare2,spare1},

[0509] ssb-PositionsInBurst-r17 CHOICE {

[0510] shortBitmap BIT STRING (SIZE (4)),

[0511] mediumBitmap BIT STRING (SIZE (8)),

[0512] longBitmap BIT STRING (SIZE (64))

[0513] },

[0514] ss-PBCH-BlockPower-r17 INTEGER (-60..50)

[0515] }

[0516] In this bitmap, AdditionalPCIIndex-r17 ::= INTEGER(1..maxNrofAdditionalPCI-r17), maxNrofAdditionalPCI is 7, and ssb-PositionsInBurst indicates the temporal position of the SS block transmitted in a half-frame containing SS / PBCH blocks. The first / leftmost bit corresponds to SS / PBCH block index 0, the second bit corresponds to SS / PBCH block index 1, and so on. A value of 0 in the bitmap indicates that the corresponding SS / PBCH block is not transmitted, while a value of 1 indicates that the corresponding SS / PBCH block is transmitted.

[0517] For the association of SSBs with ROs in the new PRACH configuration, the number of SSBs to be associated with ROs is given in the following example.

[0518] In one example, the number of SSBs to be associated with an RO is obtained from the CSI-SSB-ResourceSet based on the SSB indices in the list csi-SSB-ResourceList associated with the additional PCIs given by servingAdditionalPCIList (i.e., excluding SSBs associated with the serving cell (which have zero values ​​in their corresponding entries in servingAdditionalPCIList)). The order of SSB-to-RO association can be based on the order of the SSBs in the csi-SSB-ResourceList associated with the additional PCIs. In a variant of this example, only the SSBs of cells with a TCI state that has MACCE active are evaluated.

[0519] In one example, the number of SSBs to be associated with RO is the sum of the number of SSBs configured for each AdditionalPCIIndex, obtained from the corresponding SSB-PositionsInBurst. Let... It refers to the total number of SSBs associated with the PRACH timing.

[0520]

[0521] in, This can be obtained from ssb-PositionsInBurst corresponding to SSB-MTC-AdditionalPCI. For example, the value of a digital bit in the bitmap is equal to 1. The association order between SSB and RO can be based on:

[0522] First, the order of the SSBs in the corresponding SSB-PositionsInBurst bitmap; and / or

[0523] The order of the configured AdditionalPCIIndex, for example, as provided in ServingCellConfig.

[0524] ServingCellConfig-> mimoParam-r17->additionalPCI-ToAddModList-r17SEQUENCE (SIZE(1..maxNrofAdditionalPCI-r17)) OF SSB-MTC-AdditionalPCI-r17

[0525] Alternatively, the order of AdditionalPCIIndex can be an ascending (or descending) order of AdditionalPCIIndex. For example, first the SSB associated with AdditionalPCIIndex 1 (if configured), then the SSB associated with AdditionalPCIIndex 2 (if configured), and so on. In a variant of this example, only the SSBs of cells with TCI states that have MAC CE activation are evaluated.

[0526] In one example, the number of SSBs to be associated with an RO is obtained from the CSI-SSB-ResourceSet based on the SSB indexes associated with the serving cell PCI or the additional PCI given by the servingAdditionalPCIList in the csi-SSB-ResourceList. The order of SSB-to-RO association can be based on the order of the SSBs in the csi-SSB-ResourceList. In a variant of this example, only the SSBs of cells with a TCI state that has MAC CE activation are evaluated.

[0527] In one example, the number of SSBs associated with RO is the sum of the number of SSBs configured for the serving cell, obtained from ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon, and for each AdditionalPCIIndex, it is obtained from the corresponding ssb-PositionsInBurst. Let It refers to the total number of SSBs associated with the PRACH timing.

[0528] in, It can be obtained from ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon. This can be obtained from ssb-PositionsInBurst corresponding to SSB-MTC-AdditionalPCI. For example, the value of a digital bit in the bitmap is equal to 1. The association order of SSB and RO can be based on:

[0529] First, the order of the SSBs in the corresponding SSB-PositionsInBurst bitmap; and / or

[0530] Second, the SSB of the serving cell, followed by the configured AdditionalPCIIndex, in the following order, for example, as provided in ServingCellConfig.

[0531] ServingCellConfig-> mimoParam-r17->additionalPCI-ToAddModList-r17SEQUENCE (SIZE(1..maxNrofAdditionalPCI-r17)) OF SSB-MTC-AdditionalPCI-r17

[0532] Alternatively, the order of AdditionalPCIIndex can be an ascending (or descending) order of AdditionalPCIIndex. For example, first the SSB associated with the serving cell, then the SSB associated with AdditionalPCIIndex 1 (if configured), then the SSB associated with AdditionalPCIIndex 2 (if configured), and so on. In a variant of this example, only the SSBs of cells with a TCI state that has MAC CE active are evaluated.

[0533] In one example, each AdditionalPCIIndex has an associated ssb-PositionsInBurst provided by SSB-MTC-AdditionalPCI, which corresponds to the bits of the ssb-PositionsInBurst of the cell of the AdditionalPCIIndex. Figure 1It performs an OR operation, that is, creates a superset of the union of the SSBs used in the cell corresponding to AdditionalPCIIndex. This can be obtained from the resulting superset (the result of the OR operation described herein). The association order from SSB to RO can be based on the order of SSBs in the resulting SSB superset. In a variant of this example, only the SSBs of cells with TCI states that have MAC CE activation are evaluated.

[0534] In one example, each AdditionalPCIIndex has, as included in the associated ssb-PositionsInBurst, SIB1, or ServingCellConfigCommon provided by SSB-MTC-AdditionalPCI, (1) the bit map of the ssb-PositionsInBurst of the cell corresponding to the AdditionalPCIIndex and (2) the bit map of the ssb-PositionsInBurst of the serving cell. Figure 1 It performs an OR operation, that is, it produces a superset of the union of the SSBs used in the cell and the serving cell corresponding to AdditionalPCIIndex. This can be obtained from the resulting superset (the result of the OR operation described herein). The association order from SSB to RO can be based on the order of SSBs in the resulting SSB superset. In a variant of this example, only the SSBs of cells with TCI states that have MAC CE activation are evaluated.

[0535] In one example, for The ssb-PositionsInBurst of the serving cell, included in SIB1 or ServingCellConfigCommon, is provided. The association order of ssb to RO can be based on the order of ssbs in the ssb-PositionsInBurst of the serving cell. For RACH preambles triggered by PDCCH commands, PDCCH provides resources for transmitting the preamble (i.e., preamble index and PRACH timing). PRACH timing can be based on the SSB of the serving cell. The SSB used to determine the spatial filter and / or power of the preamble can be determined based on the SSB of the additional indication in the PDCCH command or the quasi-co-address attribute of the DMRS used for the PDCCH command.

[0536] In one example, the SSB used to determine the transmit power of the preamble is configured, activated, or indicated as PL-RS before the transmission of the PDCCH command, as described herein.

[0537] In one example, no new PRACH configuration exists; the version-15 PRACH configuration can be used to send a PDCCH command triggering a preamble to the serving cell or a cell associated with an additional PCIIndex. For a RACH preamble triggered by a PDCCH command, the PDCCH provides resources for transmitting the preamble (i.e., the preamble index and PRACH timing). The PRACH timing can be based on the serving cell's SSB. The SSB used to determine the spatial filter and / or power of the preamble can be determined based on additional indications in the PDCCH command or the SSB of the quasi-co-location attribute of the DMRS used for the PDCCH command.

[0538] In one example, the SSB used to determine the transmit power of the preamble is configured, activated, or indicated as PL-RS before the transmission of the PDCCH command, as described in this disclosure.

[0539] In one example, the PDCCH command includes at least (1) a random access preamble index, (2) an SS / PBCH index, (3) a PRACH mask index, and (4) a PCI index or PCI flag, which can identify the PRACH preamble and the PRACH timing to be used for preamble transmission.

[0540] In one example, PCIIndex could be:

[0541] If the value is zero, then the PCI is the PCI that defines the serving cell of this CSI-SSB-ResourceSet. In this example, the PCI determines the PRACH timing used to transmit the preamble (e.g., as described in the example presented herein).

[0542] Using another value corresponding to additionalPCIIndex-r17 in SSB-MTC-AdditionalPCI-r17 within additionalPCIList-r17 in ServingCellConfig, then PCI is AdditionalPCI-r17 within that SSB-MTC-AdditionalPCI-r17. In this example, PCI determines the PRACH timing used for transmitting the preamble (e.g., as described in the example herein).

[0543] PCIIndex is not included in the PDCCH command. In this case, the timing of the PRACH for transmitting the preamble is determined regardless of PCIIndex (e.g., according to one or more examples described herein).

[0544] In another example, PCIIndex could be:

[0545] Using the value corresponding to additionalPCIIndex-r17 in SSB-MTC-AdditionalPCI-r17 within additionalPCIList-r17 in ServingCellConfig, the PCI is AdditionalPCI-r17 within that SSB-MTC-AdditionalPCI-r17. In this example, the PCI determines the PRACH timing used for transmitting the preamble (e.g., as described in the example herein). In one example, if PCIIndex is 0, this corresponds to a cell triggered by a PDCCH command. In another example, if PCIIndex is 0, this corresponds to the serving cell.

[0546] PCIIndex is not included in the PDCCH command. In this case, the timing of the PRACH for transmitting the preamble is determined regardless of PCIIndex (e.g., according to one or more examples described herein).

[0547] In one example, the PCI flag could be:

[0548] If the value is zero, then the PCI is the PCI that defines the serving cell of the CSI-SSB-ResourceSet. This could, for example, correspond to the first TAG ID (e.g., TAG ID 0).

[0549] If the value is 1, the UE selects the PCI corresponding to additionalPCIIndex-r17 in SSB-MTC-AdditionalPCI-r17 of additionalPCIList-r17 in ServingCellConfig. For example, selection can be based on a cell with an active TCI state (or TCI state code point or active spatial relationship). In another example, selection can be based on RRC configuration and / or MAC CE signaling and / or L1 control signaling; for example, the network can signal to the UE the additionalPCIIndex corresponding to a PCI flag with a value of 1. This could, for example, correspond to a second TAG ID (e.g., TAG ID 1).

[0550] In one example, the PCI flag could be:

[0551] For the first RRC configuration and / or MAC CE signaling and / or L1 control signaling, the value of additionalPCIIndex is zero. This could, for example, correspond to the first TAG ID (e.g., TAG ID 0).

[0552] For a second RRC configuration and / or a signaling MAC CE and / or a signaling L1 control, the value of additionalPCIIndex is 1. This could, for example, correspond to a second TAG ID (e.g., TAG ID 1).

[0553] In one example, if PCIflag is zero, or PCIIndex is zero, the PDCCH command follows the common PDCCH command line as described in Table 1.

[0554] In one example, the PDCCH command has the PDCCH format shown in Table 2.

[0555] Table 2

[0556]

[0557] In one example, the PDCCH command has the PDCCH format shown in Table 3.

[0558] Table 3

[0559]

[0560] For description A, see the following example. In one example, if the PCI index or PCI flag is zero:

[0561] If the "Random Access Preamble Index" is non-zero, this field indicates the preamble index to be sent for CFRA-based PDCCH commands.

[0562] If the "Random Access Preamble Index" is zero, this field indicates a CBRA-based PDCCH command.

[0563] In one example, if the PCI index or PCI flag is non-zero:

[0564] If the "Random Access Preamble Index" is non-zero, this field indicates the preamble index to be sent for CFRA-based PDCCH commands.

[0565] If the "Random Access Preamble Index" is zero, this field indicates a CBRA-based PDCCH command.

[0566] In one example, if the PCI index or PCI flag is non-zero:

[0567] The field “Random Access Preamble Index” indicates the preamble index to be sent for CFRA-based PDCCH commands.

[0568] In one example, if the PCI index or PCI flag is non-zero:

[0569] If the "Random Access Preamble Index" is non-zero, this field indicates the preamble index to be sent for CFRA-based PDCCH commands.

[0570] The field "Random Access Preamble Index" with a value of zero is reserved or not supported.

[0571] For description B, see the following example.

[0572] In one example, if the PCI index or PCI flag is zero:

[0573] If the "Random Access Preamble Index" is not zero, then the "SS / PBCH Index" indicates the SSB index used for RO association; otherwise, the "SS / PBCH Index" is retained.

[0574] In one example, if the PCI index or PCI flag is non-zero:

[0575] If the "Random Access Preamble Index" is not zero, then the "SS / PBCH Index" indicates the SSB index used for RO association and determining the preamble transmit power and preamble space filter; otherwise, the "SS / PBCH Index" is retained.

[0576] In one example, if the PCI index or PCI flag is non-zero:

[0577] The “SS / PBCH index” indicates the SSB index used for RO association and determining the preamble transmit power and the preamble space filter.

[0578] For description C, see the following examples.

[0579] In one example, if the PCI index or PCI flag is zero:

[0580] If the "Random Access Preamble Index" is not zero, then the "PRACH Mask Index" indicates the use of RO; otherwise, the "PRACH Mask Index" is retained.

[0581] In one example, if the PCI index or PCI flag is non-zero:

[0582] If the "Random Access Preamble Index" is not zero, then the "PRACH Mask Index" indicates the use of RO; otherwise, the "PRACH Mask Index" is retained.

[0583] In one example, if the PCI index or PCI flag is non-zero:

[0584] The “PRACH mask index” indicates the RO used.

[0585] For description D, see the following example.

[0586] In one example, if the PCI flag is 0, a PRACH transmission is sent to the same TRP that sent the PDCCH command.

[0587] In one example, if the PCI flag is 0, a PRACH transmission is sent to the serving cell.

[0588] In one example, a PDCCH command with a PCI flag value of 0 is sent from the serving cell.

[0589] In one example, a PDCCH command with a PCI flag value of 0 can be sent from either the serving cell or a non-serving cell (e.g., an inter-cell PDCCH command).

[0590] In one example, the PCI flag could be the TAG ID flag.

[0591] In one example, a network (e.g., network 130) can signal the additional PCIIndex of the TRP corresponding to a PCI flag with a value of 1 via RRC configuration and / or MAC CE signaling and / or L1 control signaling.

[0592] In one example, the network can send the first additional PCIIndex of the TRP corresponding to a PCI flag with a value of 0 and the second additional PCIIndex of the TRP corresponding to a PCI flag with a value of 1 via RRC configuration and / or MAC CE signaling and / or L1 control signaling.

[0593] In one example, the second TRP for a PCI flag with a value of 1 can be associated with a cell that has an active TCI status (or TCI status code point or active spatial relationship).

[0594] In one example, if the PCI flag is 0, the typical behavior in Table 1 is followed.

[0595] For description E, see the following examples.

[0596] In one example, if the PCI index is 0, a PRACH transmission is sent to the same TRP that sent the PDCCH command.

[0597] In one example, if the PCI index is 0, a PRACH transmission is sent to the serving cell.

[0598] In one example, a PDCCH command with a PCI index of 0 is sent from the serving cell.

[0599] In one example, a PDCCH command with a PCI index of 0 can be sent from either the serving cell or a non-serving cell (e.g., an inter-cell PDCCH command).

[0600] In one example, if the PDCCH command comes from the serving cell:

[0601] If the PCI index is 0, a PRACH transmission is sent to the serving cell (e.g., following typical behavior, where the SSB used to determine the PRACH transmission power is the SSB of the QCL used for the PDCCH command, or the SSB used to determine the PRACH transmission is the SSB indicated in the PDCCH command).

[0602] If the PCI index is non-zero (e.g., indicating cell A), a PRACH transmission is sent to cell A (e.g., the SSB used to determine the PRACH transmission power is the SSB indicated in the PDCCH command for cell A).

[0603] In one example, if the PDCCH command comes from cell A, which has a PCI different from that of the serving cell:

[0604] If the PCI index is 0, a PRACH transmission is sent to the serving cell (e.g., where the SSB used to determine the PRACH transmission power is the SSB of the QCL used for the PDCCH command, or the SSB used to determine the PRACH transmission is the SSB indicated in the PDCCH command).

[0605] If the PCI index indicates cell A, then one of the following:

[0606] A PRACH transmission is sent to cell A, and the SSB used to determine the PRACH transmission power is the SSB indicated in the PDCCH command for cell A.

[0607] A PRACH transmission is sent to cell A, and the SSB used to determine the PRACH transmission power is the SSB of the QCL used for the PDCCH command.

[0608] If the PCI index is non-zero and different from the PCI index of cell A (e.g., indicating cell B), then a PRACH transmission is sent to cell A, and the SSB used to determine the PRACH transmission power is the SSB indicated in the PDCCH command for cell B.

[0609] In one example, if the PDCCH command comes from cell A, which has a PCI different from that of the serving cell:

[0610] The PCI index is 0. A PRACH transmission is sent to cell A. In one example, the SSB used to determine the PRACH transmit power is the SSB of the QCL used for the PDCCH command (e.g., similar to a typical PDCCH command). In another example, the SSB used to determine the PRACH transmit power is the SSB indicated in the PDCCH command for cell A.

[0611] In this example, a PDCCH command from the serving cell can trigger a PRACH transmission toward the serving cell or a cell with a PCI different from that of the serving cell. A PDCCH command from cell A, which has a PCI different from that of the serving cell, can trigger a PRACH transmission toward cell A.

[0612] In one example, if the PDCCH command comes from cell A, which has a PCI different from that of the serving cell:

[0613] The PCI index is the PCI index of cell A. The PRACH transmission is sent to cell A. In one example, the SSB used to determine the PRACH transmit power is the SSB of the QCL used for the PDCCH command (e.g., similar to a typical PDCCH command). In another example, the SSB used to determine the PRACH transmit power is the SSB indicated in the PDCCH command for cell A.

[0614] In this example, a PDCCH command from the serving cell can trigger a PRACH transmission toward the serving cell or a cell with a PCI different from that of the serving cell. A PDCCH command from cell A, which has a PCI different from that of the serving cell, can trigger a PRACH transmission toward cell A.

[0615] In one example, PCI index 0 can correspond to the first TAG ID (e.g., TAG ID 0), and a non-zero PCI index can correspond to the second TAG ID (e.g., TAG ID 1).

[0616] In one example, the first PCI index may correspond to a first TAG ID (e.g., TAG ID 0), and the second PCI index may correspond to a second TAG ID (e.g., TAG ID 1). In one example, the network may configure the first PCI index and / or the second PCI index via RRC configuration and / or MAC CE signaling and / or L1 control signaling.

[0617] In one example, the PCI field has a size of N bits, where In one example, maxNrofAdditionalPCI=7, and N=3 bits. In another example, if the PCI field is 0, this indicates the serving cell; otherwise, the PCI indicates an additional PCI index for a non-serving cell.

[0618] In one example, if the PCI index is 0, the typical behavior in Table 1 is followed.

[0619] In one example, a new flag can be added to the PDCCH command.

[0620] If the flag is "0", then the typical PDCCH command line as described in Table 1 is followed.

[0621] If the flag is "1", the new behavior is followed. For example:

[0622] The PCI index or PCI flag is included in the PDCCH command.

[0623] If the "Random Access Preamble Index" is not zero, then the "SS / PBCH Index" indicates the SSB index used for RO association and determining the preamble transmit power and the preamble spatial filter; otherwise, the "SS / PBCH Index" is retained. Alternatively, the "SS / PBCH Index" indicates the SSB index used for RO association and determining the preamble transmit power and the preamble spatial filter.

[0624] If the "Random Access Preamble Index" is not zero, then the "PRACH Mask Index" indicates the use of the RO; otherwise, the "PRACH Mask Index" is retained. Alternatively, the "PRACH Mask Index" indicates the RO used.

[0625] In one example, the SSB used to determine the transmit power of the preamble is configured, activated, or indicated as PL-RS before the transmission of the PDCCH command, as described in this disclosure.

[0626] Figure 28 A process 2800 for an example RAR according to an embodiment of the present disclosure is illustrated. For example, process 2800 may be performed by... Figure 1 Any of UEs 111-116 (such as UE 111) and BSs (such as BS 102) shall comply. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0627] The process begins at 2810, where the gNB (e.g., gNB 102) sends a PDCCH command to the UE, indicating the SSB and PCI for transmitting the preamble. At 2820, the UE sends a PRACH preamble to the gNB, where the spatial transmission and / or power of the preamble are determined based on the indicated SSB and PCI. At 2830, the gNB sends a RAR to the UE.

[0628] In one example, refer to Figure 28 The preamble is transmitted using a spatial filter and / or power determined based on (1) the SS / PBCH index and (2) the PCIIndex included in (or indicated by) the PDCCH command. The following variants can be evaluated for this example:

[0629] Variant 1: The same SS / PBCH index is used for (1) determining the PRACH timing for transmitting the preamble, and (2) determining the spatial filter and / or power of the preamble. For example, as shown in Table 3.

[0630] Variant 2: The PDCCH command includes two SS / PBCH indices; (1) one for determining the PRACH timing for transmitting the preamble, and (2) the other for determining the power of the spatial filter and / or the preamble. For example, as shown in Table 4.

[0631] Table 4

[0632]

[0633] For description F, see the following example. In one example, if the PCI index or PCI flag is zero:

[0634] If the "Random Access Preamble Index" is not zero, then the "SS / PBCH Index" indicates the SSB index used for RO association; otherwise, the "SS / PBCH Index" is retained.

[0635] In one example, if the PCI index or PCI flag is non-zero:

[0636] If the "Random Access Preamble Index" is not zero, then the "SS / PBCH Index" indicates the SSB index used for RO association; otherwise, the "SS / PBCH Index" is retained.

[0637] In one example, if the PCI index or PCI flag is non-zero:

[0638] The “SS / PBCH index” indicates the SSB index used for RO association.

[0639] For a description of G, see the following examples.

[0640] In one example, if the PCI index or PCI flag is zero:

[0641] The field “SS / PBCH index 2” is reserved.

[0642] In one example, if the PCI index or PCI flag is non-zero:

[0643] If the "Random Access Preamble Index" is not zero, then "SS / PBCH Index 2" indicates the SSB index used to determine the preamble transmit power and the preamble space filter; otherwise, the "SS / PBCH Index" is retained.

[0644] In one example, if the PCI index or PCI flag is non-zero:

[0645] The “SS / PBCH index” indicates the SSB index used to determine the preamble transmit power and the preamble space filter.

[0646] In one example, a new flag can be added to the PDCCH command.

[0647] If the flag is "0", then the typical PDCCH command line as described in Table 1 is followed.

[0648] If the flag is "1", the new behavior is followed. For example:

[0649] The PCI index or PCI flag is included in the PDCCH command.

[0650] If the "Random Access Preamble Index" is not zero, then the "SS / PBCH Index" indicates the SSB index used for RO association; otherwise, the "SS / PBCH Index" is retained. Alternatively, the "SS / PBCH Index" indicates the SSB index used for RO association.

[0651] A new field, “SS / PBCH Index 2”, is added to the PDCCH command. If the “Random Access Preamble Index” is not zero, then “SS / PBCH Index 2” indicates the SSB index used to determine the preamble transmit power and the preamble space filter; otherwise, the “SS / PBCH Index” is retained. Alternatively, the “SS / PBCH Index” indicates the SSB index used to determine the preamble transmit power and the preamble space filter.

[0652] If the "Random Access Preamble Index" is not zero, then the "PRACH Mask Index" indicates the use of the RO; otherwise, the "PRACH Mask Index" is retained. Alternatively, the "PRACH Mask Index" indicates the RO used.

[0653] In one example, the SSB used to determine the transmit power of the preamble is configured, activated, or indicated as PL-RS before the transmission of the PDCCH command, as described in this disclosure.

[0654] In one example, refer to Figure 28 The preamble is transmitted using a spatial filter and / or power determined based on (1) the SS / PBCH index and (2) the PCI flags included in (or indicated by) the PDCCH command. The following variants can be evaluated for this example:

[0655] Variant 1: The same SS / PBCH index is used for (1) determining the PRACH timing for transmitting the preamble, and (2) determining the spatial filter and / or power of the preamble. For example, as shown in Table 2.

[0656] Variant 2: The PDCCH command includes two SS / PBCH indices; (1) one for determining the PRACH timing for transmitting the preamble, and (2) the other for determining the power of the spatial filter and / or the preamble. For example, as shown in Table 5.

[0657] In one example, the SSB used to determine the transmit power of the preamble is configured, activated, or indicated as PL-RS before the transmission of the PDCCH command, as described in this disclosure.

[0658] Table 5

[0659]

[0660] In one example, the PCI flag could be:

[0661] If the value is zero, then the PCI is the PCI that defines the serving cell of the CSI-SSB-ResourceSet.

[0662] If the value is 1, the UE (e.g., UE 116) selects the PCI corresponding to the additionalPCIIndex-r17 of SSB-MTC-AdditionalPCI-r17 in the additionalPCIList-r17 in ServingCellConfig. For example, the selection can be based on a cell with an active TCI state (or TCI state code point or active spatial relationship).

[0663] In one example, refer to Figure 29The preamble is transmitted using spatial filters and / or power determined based on SSB or CSI-RS resources, which are source RSs or quasi-co-located source RSs with the PDCCH DMRS of the PDCCH command. The SSB or CSI-RS may be associated with the serving cell or with a cell corresponding to the additional PCIIndex.

[0664] In one example, the SSB or CSI-RS used to determine the transmit power of the preamble is configured, activated, or indicated as PL-RS before the transmission of the PDCCH command, as described in this disclosure.

[0665] Figure 29 A process 2900 for an example RAR according to an embodiment of the present disclosure is shown. For example, process 2900 may be performed by... Figure 1 Any of UEs 111-116 (such as UE 112) and BSs (such as BS 103) shall comply. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0666] The process begins at 2910, when the gNB sends a PDCCH command to the UE. At 2920, the UE sends a PRACH preamble to the gNB, where the spatial transmission and / or power of the preamble are determined based on the source RS of the quasi-co-address attributes used for the PDCCH command DMRS. At 2930, the gNB sends a RAR to the UE.

[0667] In one example, refer to Figure 29 The preamble is transmitted using spatial filters and / or power determined based on SSB or CSI-RS resources, which are source RSs or quasi-co-located source RSs with the PDCCH DMRS of the PDCCH command. The SSB or CSI-RS can be associated with a cell corresponding to the additional PCIIndex.

[0668] In one example, the SSB or CSI-RS used to determine the transmit power of the preamble is configured, activated, or indicated as PL-RS before the transmission of the PDCCH command, as described in this disclosure.

[0669] Figure 30 A process 3000 for an example RAR according to an embodiment of the present disclosure is illustrated. For example, process 3000 may be... Figure 1 Any of UEs 111-116 (such as UE 113) and BSs (such as BS 102) shall comply. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0670] The process begins at 3010, where the gNB sends a PDCCH command to the UE indicating the code point or spatial relationship of the active TCI state. At 3020, the UE sends a PRACH preamble to the gNB, where the spatial transmission and / or power of the preamble is determined based on the source RS of the TCI state or spatial relationship of the indicated code point. At 3030, the gNB sends a RAR to the UE.

[0671] In one example, refer to Figure 30 The preamble is transmitted using a spatial filter and / or power determined based on the SS / PBCH index or CSI-RS resource, where the SS / PBCH index or CSI-RS resource is the source RS for a quasi-co-addressable (e.g., type D QCL or type A QCL) TCI state activated by MAC CE, and the activated MAC CE TCI state code point (or TCI state or TCI state ID) is included in (or indicated by) the PDCCH command. The active TCI state code point corresponds to a TCI state activated by MAC CE, as described in Clauses 5.18.23 and 6.1.3.47 of TS 38.321 [Reference 5]. In a variant, the SSB index is used to determine the spatial filter and / or power of the transmitted preamble, where the SSB index is the root source RS for the TCI state code point (or TCI state or TCI state ID) included in (or indicated by) the PDCCH command. The root RS is a direct or indirect RS that provides QCL information or spatial relationship information for a TCI status code point (or TCI status or TCI status ID). A direct RS is when the RS is the source RS of the TCI status code point (or TCI status or TCI status ID), while an indirect RS is when the RS provides QCL information or spatial relationship information to the source RS of the TCI status code point (or TCI status or TCI status ID).

[0672] In one example, the SSB or CSI-RS used to determine the transmit power of the preamble is configured, activated, or indicated as PL-RS before the transmission of the PDCCH command, as described in this disclosure.

[0673] In one example, refer to Figure 30The preamble is transmitted using spatial filters and / or power determined based on the SS / PBCH index or CSI-RS resource, where the SS / PBCH index or CSI-RS resource is the source RS for the spatial relation used for MAC CE activation, and the activated MAC CE spatial relation (or spatial relation code point or spatial relation ID) is included in (or indicated by) the PDCCH command. In a variant, the SSB index is used to determine the spatial filters and / or power of the transmitted preamble, where the SSB index is the root source RS for the spatial relation (or spatial relation code point or spatial relation ID) included in (or indicated by) the PDCCH command. The root source RS is a direct or indirect RS for QCL information or spatial relation information for the spatial relation (or spatial relation code point or spatial relation ID). A direct RS is when the RS is the source RS for the spatial relation (or spatial relation code point or spatial relation ID). An indirect RS is when the RS provides QCL information or spatial relation information for the source RS of the spatial relation (or spatial relation code point or spatial relation ID).

[0674] In one example, the SSB or CSI-RS used to determine the transmit power of the preamble is configured, activated, or indicated as PL-RS before the transmission of the PDCCH command, as described in this disclosure.

[0675] Figure 31 A process 3100 for an example RAR according to an embodiment of the present disclosure is illustrated. For example, process 3100 may be performed by... Figure 1 Any of UEs 111-116 (such as UE 114) and BSs (such as BS 103) shall comply. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0676] The process begins at 3110, where the gNB sends a PDCCH command to the UE. At 3120, the UE sends a PRACH preamble to the gNB. At 3130, the gNB sends a RAR to the UE, where the DMRS of the PDCCH in the RAR and the DMRS of the PDCCH command have the same source RS for quasi-co-address attributes.

[0677] Figure 32 A process 3200 for an example RAR is illustrated according to an embodiment of the present disclosure. For example, the process 3200 for an example RAR may be provided by... Figure 1 Any of UEs 111-116 (such as UE 115) and BSs (such as BS 102) shall comply. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0678] The process begins at 3210, where the gNB (e.g., gNB 102) sends an indicated SSB to the UE for preamble transmission. At 3220, the gNB sends a PDCCH command to the UE indicating the SSB and PCI for preamble transmission. At 3230, the UE sends a RACH preamble to the gNB, where the spatial transmission and / or power of the preamble are determined based on the indicated SSB and PCI. At 3240, the gNB sends a RAR to the UE, where the SSB source RS of the DMRS for the PDCCH used in the RAR is used for quasi-co-address attributes.

[0679] In one example, the random access response to the preamble is sent in a PDCCH with a CRC scrambled by RA-RNTI.

[0680] In one example, refer to Figure 31 The DMRS antenna port of the RAR's PDCCH has the same antenna port quasi-co-address attribute as the DMRS antenna port of the PDCCH command.

[0681] In one example, refer to Figure 32 The DMRS antenna port of the RAR's PDCCH is quasi-co-located with the SSB and CSI-RS resources used to determine the space filter and / or power of the preamble transmission.

[0682] In one example, the DMRS antenna port of the RAR's PDCCH is quasi-co-located with the SSB and CSI-RS resources used to determine the association between the preamble transmission and the RO.

[0683] In one example, the DMRS antenna port of the RAR's PDCCH is co-located with the SSB quasi-co-located as indicated by the "SS / PBCH index" in the PDCCH command.

[0684] In one example, the DMRS antenna port of the RAR's PDCCH is co-located with the SSB quasi-co-located as indicated in the PDCCH command via the "SS / PBCH index" and PCI flag or PCI index.

[0685] In one example, the DMRS antenna port of the RAR's PDCCH is co-located with the SSB quasi-co-located as indicated by "SS / PBCH index 2" in the PDCCH command.

[0686] In one example, the DMRS antenna port of the RAR's PDCCH is co-located with the SSB quasi-co-located as indicated in the PDCCH command by "SS / PBCH index 2" and the PCI flag or PCI index.

[0687] In one example, the DMRS antenna port of the RAR's PDCCH is associated with a CORESET quasi-co-located set of the same type of 1-PDCCH common search space (CSS) (e.g., the source RS based on the TCI state of the CORESET).

[0688] In one example, if a PDCCH command is associated with a cell having a PCI different from that of the serving cell (e.g., the TCI state of the PDCCH command is associated with a cell or SSB having a PCI different from that of the serving cell), then the DMRS antenna port of the RAR's PDCCH is associated with a CORESET quasi-co-addressable set of the same type of 1-PDCCH common search space (CSS) (e.g., the source RS based on the TCI state of the CORESET). If a PDCCH command is associated with a serving cell (e.g., the TCI state of the PDCCH command is associated with the serving cell or the serving cell's SSB), then the DMRS antenna port of the RAR's PDCCH has the same antenna port quasi-co-addressable properties as the DMRS antenna port of the PDCCH command.

[0689] In one example, the DMRS antenna port of the RAR's PDCCH is quasi-co-located with the CORESET quasi-co-located with the search space (USS) set that varies from UE to UE (e.g., the source RS based on the TCI state of the CORESET).

[0690] In one example, the RAR's PDCCH is sent in the Type 1-PDCCH CSS set associated with the serving cell.

[0691] In one example, the RAR's PDCCH is transmitted in a Type 1-PDCCH CSS set associated with a cell, where the cell is the cell associated with the preamble transmission. The cell can be the serving cell or a cell of the additional PCIndex. In this example, the UE can be configured with multiple Type 1-PDCCHCSS sets for both the serving cell and the additional PCIndex.

[0692] In one example, the PDCCH is transmitted in a Type 1-PDCCH CSS set associated with a cell, where the cell is the cell associated with the preamble transmission. The cell can be the serving cell or a cell of the additional PCIndex. In this example, the UE can be configured with two Type 1-PDCCH CSS sets: a first Type 1-PDCCH CSS for the serving cell and a second Type 1-PDCCH CSS for any cell of the additional PCIndex.

[0693] In one example, the PDCCH of the RAR is sent in the USS set.

[0694] In one example, the PDCCH for RAR is sent in the same search space set as the PDCCH command.

[0695] In one example, if the PCI flag or PCI index or TAG ID / index in the PDCCH command is 0, or if a flag is added in the PDCCH command to indicate new behavior and the flag is set to 0, then the DMRS antenna port of the RAR's PDCCH has the same antenna port quasi-co-addressable attributes as the DMRS antenna port of the PDCCH in the PDCCH command; otherwise (if the PCI flag or PCI index or TAG ID / index in the PDCCH command is non-zero), the DMRS antenna port of the RAR's PDCCH is quasi-co-addressable with the SSB and CSI-RS resources used to determine the space filter and / or power of the preamble transmission.

[0696] In one example, if the PCI flag, PCI index, or TAG ID / index in the PDCCH command is 0, or if a flag is added in the PDCCH command to indicate new behavior and the flag is set to 0, then the DMRS antenna port of the RAR's PDCCH has the same antenna port quasi-co-addressable attribute as the DMRS antenna port of the PDCCH in the PDCCH command; otherwise (if the PCI flag, PCI index, or TAG ID / index in the PDCCH command is non-zero), the DMRS antenna port of the RAR's PDCCH is quasi-co-addressable with the SSB indicated by one of the following:

[0697] SS / PBCH Index

[0698] SS / PBCH index and PCI flag or PCI index.

[0699] SS / PBCH Index 2

[0700] SS / PBCH index 2 and PCI flag or PCI index.

[0701] In one example, the DMRS antenna port of the RAR's PDSCH has the same antenna port quasi-co-addressability as the DMRS antenna port of the RAR's PDCCH. The antenna port quasi-co-addressability as the DMRS antenna port of the RAR's PDCCH can be based on one or more examples described herein.

[0702] In one example, the DCI format of the PDCCH of RAR or MsgB includes a TAG ID or TAG flag. For example, this could be a 1-bit flag where "0" is used for the first TAG ID and "1" is used for the second TAG ID. The TAG ID can be a timed TAG ID communicated by RAR or MgsB.

[0703] In one example, the MAC CE of the RAR or MsgB includes a TAG ID or TAG flag. For example, this could be a 1-bit flag where "0" is used for the first TAG ID and "1" is used for the second TAG ID. The TAG ID can be a timed TAG ID communicated by the RAR or MgsB.

[0704] In one example, the timing advance communicated by the RAR or MgsB can be determined based on the PDCCH command that triggers the PRACH preamble transmission associated with the RAR (e.g., the PCI flag or index in the PDCCH command, or the cell in which the PDCCH command is sent, or the cell in which the PDCCH command triggers the preamble transmission).

[0705] In one example, the timing advance communicated by RAR or MgsB can be determined based on the SSB or CSI-RS used for the transmission of the PRACH preamble (e.g., one set of SSBs or CSI-RS is associated with a first TAG ID, and a second set of SSBs or CSI-RS is associated with a second TAG ID).

[0706] In one example, the timing advance communicated by RAR or MgsB can be determined based on the SSB or CSI-RS used to determine the RO of the PRACH preamble (e.g., one set of SSBs or CSI-RS is associated with the first TAG ID, and a second set of SSBs or CSI-RS is associated with the second TAG ID).

[0707] In one example, the SSB or CSI-RS used to determine the transmit power of the preamble in the example described herein is configured or activated or indicated as PL-RS before the transmission of the PDCCH command, as described in this disclosure.

[0708] In one example, in a cross-TRP trigger scenario, a preamble is sent to the TRP of a cell other than the one sending the PDCCH command. In this case, additional signaling is required to determine the TRP to which the PRACH is being sent. For this purpose, a new field can be included in the PDCCH command. This new field could be:

[0709] The PRACH in the PDCCH command is a one-bit flag (e.g., the PCI flag) indicating whether it is sent to the serving cell or another non-serving cell. For example, a non-serving cell could be a cell with an active TCI state; and / or

[0710] SSB-MTC-AdditionalPCI-r17 includes a 3-bit field that indicates the cell ID (e.g., PCI index), such as identifying AdditionalPCIIndex-r17 (values ​​from 1 to 7). A value of 0 can indicate the serving cell.

[0711] In one example, for a multi-cell multi-TRP operation based on multiple DCI with two TA enhancements, for the CFRAPDCCH command, an additional flag or field is included in the PDCCH command to identify the cell to which the PDCCH command is sent.

[0712] In one example, for multi-DCI-based multi-TRP operation with two TA enhancements, the PDCCH command includes an additional flag or field to identify the TRP to which the PRACH command was sent. In one example, if the flag or field is set to zero, the PRACH is sent to the same TRP as the one that sent the PDCCH command. If the flag or field is 1, the PRACH is sent to a different TRP than the one that sent the PDCCH command. In a variant example, the function associated with one or zero can be reversed. In another example, if the flag is set to zero, the PRACH is sent to the first TRP (e.g., the TRP associated with the first coresetpoolIndex (e.g., coresetpoolIndex 0), or the TRP associated with the first group of SSBs). If the flag is set to 1, the PRACH is sent to the second TRP (e.g., the TRP associated with the second coresetpoolIndex (e.g., coresetpoolIndex 1), or the TRP associated with the second group of SSBs). In the variant example, the function associated with 1 or 0 can be reversed.

[0713] In one example, if the PCI flag, or the field indicating a PDCCH command, has a value of 0, the PDCCH command operates according to the typical behavior described herein. If the PCI flag in the PDCCH command has a non-zero value, this indicates a PDCCH command with PRACH sent to a cell other than the cell that triggered the PDCCH command. In this case,

[0714] The “Random Access Preamble Index” field indicates the preamble transmitted toward another cell via PRACH.

[0715] The “UL / SUL Indicator” field indicates whether the PRACH preamble is transmitted on a UL carrier or on a SUL carrier in another cell.

[0716] The “SS / PBCH Index” field indicates the SSB index determined by the cell based on the PCI flag / PCI index to determine the RO used for PRACH preamble transmission toward the cell. The indicated SSB index of the cell can also be used to determine the PRACH preamble transmission power. That is, this field is used for PRACH RO association and transmission power.

[0717] The “PRACH Mask Index” field determines the RO used for PRACH preamble transmission toward the cell indicated by the PCI flag / PCI index.

[0718] In one example, for a multi-DCI-based multi-TRP operation with two TA enhancements, the CFRA PDCCH command is as follows:

[0719] If the PCI field PCI flag or field is zero, the PDCCH command follows typical behavior.

[0720] If the PCI field, PCI flag, or field indicates PRACH transmission toward a cell and / or TRP other than the cell and / or TRP that triggered the PDCCH command, the remaining fields in the PDCCH command are used to determine the preamble index and RO of the PRACH preamble transmitted toward other cells. The "SS / PBCH Index" field is used to determine the transmission power of the PRACH preamble toward other cells.

[0721] In one example, the QCL of the RAR and the corresponding PDSCH PDCCH DMRS can follow the QCL of the PDCCH command PDCCH DMRS. The Type 1 PDCCH CSS (Common Search Space) set configured for the serving cell can be used for PDCCH monitoring timing of the RAR.

[0722] In one example, the QCL of the RAR's PDCCH DMRS can be determined based on the SSB used for preamble transmission. In this case, the Type 1 PDCCH CSS set configured for the serving cell can also be used for the timing of RAR's PDCCH monitoring.

[0723] The TAG ID can be determined based on the PCI flag or PCI index of the PDCCH command. For example, if the PCI flag or field is zero, it can correspond to one TAG ID, and if the PCI flag is not zero, it can correspond to another TAG ID.

[0724] In one example, for a multi-TRP operation based on inter-cell multi-DCI with two TA enhancements, the type 1 PDCCH CSS configured for the serving cell can be used for the PDCCH monitoring timing of RAR for the CFRAPDCCH command.

[0725] If a PDCCH command is sent to the serving cell, the UE can expect that the PDCCH and PDCCH commands, which include the RAR DCI format 1_0 and the corresponding PDSCH, have the same DMRS antenna port quasi-co-address characteristics.

[0726] If a PDCCH command is sent toward a non-serving cell, the UE can expect a PDCCH of DCI format 1_0 including RAR and a corresponding PDSCH with the same antenna port quasi-co-address characteristics as the SSB used for PRACH preamble transmission.

[0727] In one example, for a multi-TRP operation based on inter-cell multi-DCI with two TA enhancements, the TAG ID is determined based on the PCI flag or PCI index of the PDCCH command for the CFRAPDCCH command.

[0728] In one example, for a multi-TRP operation based on intra-cell multiple DCI with two TA enhancements, the TAG ID is determined based on the PCI flag or PCI index of the PDCCH command for the CFRAPDCCH command.

[0729] In one example, for a multi-TRP operation based on intra-cell multiple DCI with two TA enhancements, a RACH procedure toward the same TRP is triggered by a CFRA PDCCH command sent by one TRP.

[0730] The preamble is transmitted using a spatial filter and power determined based on SSB resources, which are the source RS of the PDCCH DMRS of the PDCCH command.

[0731] In one example, for a multi-TRP operation based on intra-cell multiple DCI with two TA enhancements, the TAG ID is determined for the CFRAPDCCH command based on the PDCCH command or the TCI state of the TRP from which the PDCCH command was sent.

[0732] In one example, for an intra-cell scenario, the RAR is sent from the TRP that sends the PDCCH command. The QCL of the RAR's PDCCH and the corresponding PDSCH can follow the QCL of the PDCCH command. The Type 1 PDCCH CSS configured for the serving cell can be used for PDCCH monitoring of the RAR.

[0733] In one example, for multi-TRP operations based on inter-cell or intra-cell multiple DCI with two TA enhancements, the Type 1 PDCCH CSS configured for the serving cell can be used for PDCCH monitoring timing of the RAR for the CFRA PDCCH command. The UE can expect that the PDCCH including the RAR DCI format 1_0 and the corresponding PDSCH and PDCCH commands have the same DMRS antenna port quasi-co-address attributes.

[0734] In one example, if a PDCCH command is associated with a cell having a PCI different from that of the serving cell (e.g., the TCI state of the PDCCH command is associated with a cell or SSB having a PCI different from that of the serving cell), then the DMRS antenna ports of the RAR's PDCCH and / or PDSCH are associated with the CORESET quasi-co-addressable set of the same type of 1-PDCCH common search space (CSS) (e.g., the source RS based on the TCI state of the CORESET). If a PDCCH command is associated with a serving cell (e.g., the TCI state of the PDCCH command is associated with the serving cell or the serving cell's SSB), then the DMRS antenna ports of the RAR's PDCCH and / or PDSCH have the same antenna port quasi-co-addressable properties as the DMRS antenna ports of the PDCCH command.

[0735] In one example, as described herein, the SSB or CSI-RS used to determine the transmit power of the preamble is configured or activated or indicated as PL-RS prior to the transmission of the PDCCH command, as described in this disclosure.

[0736] Figure 33 A process 3300 for an example RAR is illustrated according to an embodiment of the present disclosure. For example, the process 3300 for an example RAR may be provided by... Figure 1 Any of UEs 111-116 (such as UE 111) and BSs (such as BS 103) shall comply. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0737] The process begins at 3310, where the gNB sends a random access preamble allocation to the UE. At 3320, the UE sends a PRACH preamble to the gNB, and at 3300, the gNB sends a RAR to the UE.

[0738] In one example, a higher layer triggers a contention-free random (CFRA) access procedure for inter-cell or intra-cell multi-TRP scenarios to determine the TA.

[0739] refer to Figure 33 This illustrates the CFRA process triggered at a higher level. The following aspects are provided:

[0740] Resources used for preamble transmission, including PRACH timing and preamble index.

[0741] Spatial filters and / or transmit power are used for transmitting the preamble.

[0742] Quasi-co-addressing for random access responses.

[0743] The resources used for the preamble are determined by the PRACH timing and the preamble index within the PRACH timing. The preamble index can be indicated by a higher layer (e.g., Figure 33 (RA preamble allocation in the context of the code). The PRACH timing is determined based on the SSB or CSI-RS resources associated with the preamble, according to the described association pattern. In version 15, the association pattern is defined only for the SSB of the serving cell. However, in the case of multiple TRPs between cells, there is an SSB associated with the serving cell and an SSB associated with the cell corresponding to the additional PCIIndex. Therefore, one example is defining a new PRACH configuration to cover both the serving cell SSB and the SSB on the cell corresponding to the additional PCIIndex. In the case of multiple TRPs within a cell, there is an SSB associated with the first TRP and an SSB associated with the second TRP.

[0744] In one example, the new PRACH configuration can be used to transmit preambles associated with the serving cell and the cell corresponding to the additional PCIIndex.

[0745] In one example, the new PRACH configuration can be used to transmit the preamble associated with the cell corresponding to the additional PCIIndex. The PRACH configuration in NR version 15 can be used to transmit the preamble associated with the serving cell.

[0746] In one example, the new PRACH configuration can be used to transmit the preamble associated with the cell corresponding to the additional PCIIndex. Higher-layer parameters (e.g., via RRC configuration and / or MAC CE configuration) can indicate whether the preamble associated with the serving cell is transmitted using (1) the new PRACH configuration or (2) the PRACH configuration of NR version 15.

[0747] In one example, a separate PRACH configuration is provided for each additional PCIIndex. The PRACH configuration associated with an additional PCIIndex can be used to transmit the preamble associated with the cell corresponding to the additional PCIIndex. The PRACH configuration in NR version 15 can be used to transmit the preamble associated with the serving cell.

[0748] The following example can be evaluated for the new PRACH configuration.

[0749] This association is based on PCI-SSB pairs, that is, each PCI-SSB pair is associated with an RO; and / or

[0750] This association is based on the SSB of additionalPCIIndex, where the SSB is provided by ssb-PositionsInBurst of SSB-MTC-AdditionalPCI-r17.

[0751] In one example, the UE (e.g., UE 116) determines the PCI and / or SSB for transmitting the contention-free random access preamble. For example, the PCI can be determined based on the active TCI status code point (or TCI status or TCI status ID) and / or the active spatial relationship. In one example, let X1 be the set of PCIs associated with the TCI status code points active with the MAC CE. For example, as described in sections 5.18.23 and 6.1.3.47 of TS38.321 [Reference 5], the UE selects (or determines) PCI Y1 from the set X1, and the UE further selects (or determines) the SSB index Z1 associated with PCI Y1. The UE uses the SSB index Z1 to determine the spatial filter and / or power for the preamble transmission. In one example, X2 is a set of PCIs associated with spatial relation information activated by MAC CE. The UE selects (or determines) PCI Y2 from set X2. The UE further selects (or determines) the SSB index Z2 associated with PCI Y2. The UE uses SSB index Z2 to determine the spatial filter and / or power for preamble transmission. The UE transmits the preamble with higher-layer indication at the PRACH timing corresponding to Z1 / Y1 or Z2 / Y2.

[0752] In one example, an active TCI state (or TCI state code point or active spatial relationship) can be associated with the serving cell and one or more other cells corresponding to the additional PCIIndex.

[0753] In one example, the SSB or CSI-RS used to determine the transmit power of the preamble is configured, activated, or indicated as PL-RS before the transmission of the PDCCH command, as described in this disclosure.

[0754] In one example, the UE is configured with a new PRACH configuration. For example, the new RACH-ConfigGeneric and / or RACH-ConfigDedicated are used for inter-cell multi-TRP.

[0755] The UE is configured with an additional PCI and an SSB associated with the additional PCI. For example, the UE may be configured with a CSI-SSB-ResourceSet, which includes a list of additional PCI indices given by servingAdditionalPCIList.

[0756] CSI-SSB-ResourceSet ::= SEQUENCE {

[0757] csi-SSB-ResourceSetId CSI-SSB-ResourceSetId,

[0758] csi-SSB-ResourceList SEQUENCE (SIZE(1..maxNrofCSI-SSB-ResourcePerSet)) OF SSB-Index,

[0759] ..., [[

[0761] servingAdditionalPCIList-r17 SEQUENCE (SIZE(1..maxNrofCSI-SSB-ResourcePerSet)) OF ServingAdditionalPCIIndex-r17 OPTIONAL -- Need R ]]

[0763] }

[0764] Here, `maxNrofCSI-SSB-ResourcePerSet` is 64, and `servingAdditionalPCIList` indicates the Physical Cell ID (PCI) of the SSB in `csi-SSB-ResourceList`. If present, this list has the same number of entries as `csi-SSB-ResourceList`. The first entry in the list indicates the PCI value used for the first entry in `csi-SSB-ResourceList`, the second entry indicates the PCI value used for the second entry in `csi-SSB-ResourceList`, and so on. For each entry, the following applies:

[0765] If the value is zero, then the PCI is the PCI that defines the serving cell of this CSI-SSB-ResourceSet.

[0766] Otherwise, the value is taken as additionalPCIIndex-r17 of SSB-MTC-AdditionalPCI-r17 in ServingCellConfig additionalPCIList-r17, and the PCI is additionalPCI-r17 of that SSB-MTC-AdditionalPCI-r17.

[0767] SSB-MTC-AdditionalPCI-r17 ::= SEQUENCE {

[0768] additionalPCIIndex-r17 AdditionalPCIIndex-r17,

[0769] additional PCI-r17 PhysCellId,

[0770] periodicity-r17 ENUMERATED { ms5, ms10, ms20,ms40, ms80, ms160, spare2,spare1},

[0771] ssb-PositionsInBurst-r17 CHOICE {

[0772] shortBitmap BIT STRING (SIZE (4)),

[0773] mediumBitmap BIT STRING (SIZE (8)),

[0774] longBitmap BIT STRING (SIZE (64))

[0775] },

[0776] ss-PBCH-BlockPower-r17 INTEGER (-60..50)

[0777] }

[0778] In this context, AdditionalPCIIndex-r17 ::= INTEGER(1..maxNrofAdditionalPCI-r17), where maxNrofAdditionalPCI is 7, and ssb-PositionsInBurst indicates the temporal position of the SS block transmitted in a half-frame containing SS / PBCH blocks. The first / leftmost bit corresponds to SS / PBCH block index 0, the second bit corresponds to SS / PBCH block index 1, and so on. A value of 0 in the bitmap indicates that the corresponding SS / PBCH block is not transmitted, while a value of 1 indicates that the corresponding SS / PBCH block is transmitted.

[0779] For the association of SSBs with ROs in the new PRACH configuration, the number of SSBs to be associated with ROs is given in the following example.

[0780] In one example, the number of SSBs to be associated with an RO is obtained from the CSI-SSB-ResourceSet based on the SSB indices in the list csi-SSB-ResourceList associated with the additional PCIs given by servingAdditionalPCIList (i.e., excluding SSBs associated with the serving cell (which have zero values ​​in their corresponding entries in servingAdditionalPCIList)). The order of SSB-to-RO association can be based on the order of the SSBs in the csi-SSB-ResourceList associated with the additional PCIs. In a variant of this example, only the SSBs of cells with a TCI state that has MACCE active are evaluated.

[0781] In one example, the number of SSBs to be associated with RO is the sum of the number of SSBs configured for each AdditionalPCIIndex, obtained from the corresponding SSB-PositionsInBurst. Let... It refers to the total number of SSBs associated with the PRACH timing.

[0782]

[0783] in This can be obtained from ssb-PositionsInBurst corresponding to SSB-MTC-AdditionalPCI. For example, the value of a digital bit in the bitmap is equal to 1. The association order of SSB and RO can be based on:

[0784] First, the order of the SSBs in the corresponding SSB-PositionsInBurst bitmap; and / or

[0785] - The order of the configured AdditionalPCIIndex, such as that provided in ServingCellConfig.

[0786] ServingCellConfig-> mimoParam-r17->additionalPCI-ToAddModList-r17SEQUENCE (SIZE(1..maxNrofAdditionalPCI-r17)) OF SSB-MTC-AdditionalPCI-r17

[0787] Alternatively, the order of AdditionalPCIIndex can be an ascending (or descending) order of AdditionalPCIIndex. For example, first the SSB associated with AdditionalPCIIndex 1 (if configured), then the SSB associated with AdditionalPCIIndex 2 (if configured), and so on. In a variant of this example, only the SSBs of cells with TCI states that have MAC CE activation are evaluated.

[0788] In one example, the number of SSBs to be associated with an RO is obtained from the CSI-SSB-ResourceSet based on the SSB indexes associated with the serving cell PCI or the additional PCI given by the servingAdditionalPCIList in the csi-SSB-ResourceList. The order of SSB-to-RO association can be based on the order of the SSBs in the csi-SSB-ResourceList. In a variant of this example, only the SSBs of cells with a TCI state that has MAC CE activation are evaluated.

[0789] In one example, the number of SSBs associated with RO is the sum of the number of SSBs configured for the serving cell, obtained from ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon, and for each AdditionalPCIIndex, it is obtained from the corresponding ssb-PositionsInBurst. Let It is an SSB that is associated with the timing of PRACH.

[0790]

[0791] in It can be obtained from ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon. This can be obtained from ssb-PositionsInBurst corresponding to SSB-MTC-AdditionalPCI. For example, the value of a digital bit in the bitmap is equal to 1. The association order of SSB and RO can be based on:

[0792] First, the order of the SSBs in the corresponding SSB-PositionsInBurst bitmap; and / or

[0793] Second, the SSB of the serving cell, followed by the configured AdditionalPCIIndex, in that order, such as those provided in ServingCellConfig.

[0794] ServingCellConfig-> mimoParam-r17->additionalPCI-ToAddModList-r17SEQUENCE (SIZE(1..maxNrofAdditionalPCI-r17)) OF SSB-MTC-AdditionalPCI-r17

[0795] Alternatively, the order of AdditionalPCIIndex can be an ascending (or descending) order of AdditionalPCIIndex. For example, first the SSB associated with the serving cell, then the SSB associated with AdditionalPCIIndex 1 (if configured), then the SSB associated with AdditionalPCIIndex 2 (if configured), and so on. In a variant of this example, only the SSBs of cells with a TCI state that has MAC CE active are evaluated.

[0796] In one example, the preamble is transmitted using a spatial filter and / or power determined based on the PCI and SSB indices (e.g., as described in one or more examples herein). As described herein, the RO for CFRA preamble transmission can also be determined based on the PCI and SSB indices.

[0797] In one example, the SSB used to determine the transmit power of the preamble is configured, activated, or indicated as PL-RS before the transmission of the PDCCH command, as described in this disclosure.

[0798] In one example, the random access response to the preamble is sent in a PDCCH with a CRC scrambled by RA-RNTI.

[0799] In one example, the RAR's PDCCH is sent in the Type 1-PDCCH Common Search Space (CSS) set associated with the serving cell.

[0800] In one example, the RAR's PDCCH is transmitted in a Type 1-PDCCH CSS set associated with a cell, where the cell is the cell associated with the preamble transmission. The cell can be the serving cell or a cell of the additional PCIndex. In this example, the UE can be configured with multiple Type 1-PDCCHCSS sets for both the serving cell and the additional PCIndex.

[0801] In one example, the PDCCH is transmitted in a Type 1-PDCCH CSS set associated with a cell, where the cell is the cell associated with the preamble transmission. The cell can be the serving cell or a cell of the additional PCIndex. In this example, the UE can be configured with two Type 1-PDCCH CSS sets: a first Type 1-PDCCH CSS for the serving cell and a second Type 1-PDCCH CSS for any cell of the additional PCIndex.

[0802] In one example, the PDCCH of the RAR is sent in the USS set.

[0803] In one example, the DMRS antenna port of the RAR's PDCCH is quasi-co-located with the SSB or CSI-RS resource used to determine the spatial filter and / or power of the preamble transmission.

[0804] In one example, the DMRS antenna port of the RAR's PDCCH is quasi-co-located with the SSB or CSI-RS resource used to determine the association between the preamble transmission and the RO.

[0805] In one example, the DMRS antenna port of the RAR's PDCCH is associated with a CORESET quasi-co-located set of type 1-PDCCH CSS (e.g., the source RS based on the CORESET's TCI state).

[0806] In one example, if a PDCCH command is associated with a cell having a PCI different from that of the serving cell (e.g., the TCI state of the PDCCH command is associated with a cell or SSB having a PCI different from that of the serving cell), then the DMRS antenna port of the RAR's PDCCH is associated with a CORESET quasi-co-addressable set of the same type of 1-PDCCH common search space (CSS) (e.g., the source RS based on the TCI state of the CORESET). If a PDCCH command is associated with a serving cell (e.g., the TCI state of the PDCCH command is associated with the serving cell or the serving cell's SSB), then the DMRS antenna port of the RAR's PDCCH has the same antenna port quasi-co-addressable properties as the DMRS antenna port of the PDCCH command.

[0807] In one example, the DMRS antenna port of the RAR's PDCCH is quasi-co-located with the CORESET associated with the USS set (e.g., the source RS based on the CORESET's TCI state).

[0808] In one example, the DMRS antenna port of the RAR's PDSCH has the same antenna port quasi-co-addressability as the DMRS antenna port of the RAR's PDCCH. The antenna port quasi-co-addressability as the DMRS antenna port of the RAR's PDCCH can be based on the previous example.

[0809] In one example, the DCI format of the PDCCH of RAR or MsgB includes a TAG ID or TAG flag. For example, this could be a 1-bit flag where "0" is used for the first TAG ID and "1" is used for the second TAG ID. The TAG ID can be a timed TAG ID communicated by RAR or MgsB.

[0810] In one example, the MAC CE of the RAR or MsgB includes a TAG ID or TAG flag. For example, this could be a 1-bit flag where "0" is used for the first TAG ID and "1" is used for the second TAG ID. The TAG ID can be a timed TAG ID communicated by the RAR or MgsB.

[0811] In one example, the timing advance communicated by RAR or MgsB can be determined based on the SSB or CSI-RS used for the transmission of the PRACH preamble (e.g., one set of SSBs or CSI-RS is associated with a first TAG ID, and a second set of SSBs or CSI-RS is associated with a second TAG ID).

[0812] In one example, the timing advance communicated by RAR or MgsB can be determined based on the SSB or CSI-RS used to determine the RO of the PRACH preamble (e.g., one set of SSBs or CSI-RS is associated with the first TAG ID, and a second set of SSBs or CSI-RS is associated with the second TAG ID).

[0813] In one example, as described herein, the SSB or CSI-RS used to determine the transmit power of the preamble is configured or activated or indicated as PL-RS prior to the transmission of the PDCCH command, as described in this disclosure.

[0814] In one example, the UE configures a list of DL or JointTCI states via the parameter dl-OrJointTCI-StateList in PDSCH-Config. In another example, the UE configures a unifiedTCI-StateRef in PDSCH-Configured, which provides the serving cell and BWP for the configuration defining the DL or JointTCI states. In yet another example, the UE configures a list of UL TCI states via the parameter ul-TCI-StateList in BWP-UplinkDedicated. And in yet another example, the UE configures a unifiedTCI-StateRef in BWP-UplinkDedicated, which provides the serving cell and BWP for the configuration defining the DL or JointTCI states.

[0815] In one example, the DL or combined TCI status includes one or two QCL information fields, which are defined as follows:

[0816] QCL-Info ::= SEQUENCE {

[0817] cell ServCellIndexOPTIONAL,--Need R

[0818] bwp-Id BWP-IdOPTIONAL, -- Cond CSI-RS-Indicated

[0819] referenceSignal CHOICE {

[0820] csi-rs NZP-CSI-RS-ResourceId,

[0821] ssb SSB-Index

[0822] },

[0823] qcl-Type ENUMERATED {typeA, typeB, typeC,typeD}, ...

[0825] }

[0826] The cell is defined as the serving cell of the UE in which referenceSignal is configured. If this field does not exist, referenceSignal is configured in the serving cell where the UE applies TCI state. RS can be located on a serving cell other than the serving cell where the UE applies TCI-State, only if qcl-type is configured as type C or type D. If referenceSignal is set to csi-rs and unifiedTCI-StateType is configured, both cell and bwp-Id are present or both are absent. See Clause 5.1.5 of TS 38.214 [Reference 4]

[19] .

[0827] In one example, the TCI state (e.g., DL or combined TCI state) includes TAG_ID.

[0828] In one example, TAG_ID refers to the cell determined based on the "Cell" IE in the QCL-Info. In one example, if the TCI state has two QCL-Info fields, the "Cell" IE of the QCL-Info field with type -D is used to determine the cell referred to by TAG-ID. In a variant example, if the TCI state has two QCL-Info fields, the "Cell" IE of the QCL-Info field with type A is used to determine the cell referred to by TAG-ID. If the TCI state has two QCL-Info fields, the "Cell" IE of the first QCL-Info field is used to determine the cell referred to by TAG-ID. In one example, as described herein, the "Cell" IE of the QCL-Info field is used to determine the cell of TAG-ID (if configured); otherwise, the UE applies the serving cell of the TCI state to determine the cell of TAG-ID.

[0829] In one example, TAG_ID refers to a cell determined based on the cell configuration DL or joint TCI status list as described in this article.

[0830] In one example, TAG_ID refers to a cell determined based on the applied DL or joint TCI status.

[0831] In one example, the UL TCI status is defined by the following formula:

[0832] TCI-UL-State-r17 ::= SEQUENCE {

[0833] tci-UL-StateId-r17 TCI-UL-StateId-r17,

[0834] servingCellId-r17 ServCellIndexOPTIONAL,--Need R

[0835] bwp-Id-r17 BWP-IdOPTIONAL,-- Cond CSI-RSorSRS-Indicated

[0836] referenceSignal-r17 CHOICE {

[0837] ssb-Index-r17 SSB-Index,

[0838] csi-RS-Index-r17 NZP-CSI-RS-ResourceId,

[0839] srs-r17 SRS-ResourceId

[0840] },

[0841] additionalPCI-r17 AdditionalPCIIndex-r17OPTIONAL,-- Need R

[0842] ul-powerControl-r17 Uplink-powerControlId-r17OPTIONAL,--Need R

[0843] pathlossReferenceRS-Id-r17 PathlossReferenceRS-Id-r17OPTIONAL,-- Cond Mandatory ...

[0845] }

[0846] The `servingCellIndex` field is defined as the serving cell of the UE where the `referenceSignal` is configured. If this field does not exist, the `referenceSignal` is configured in the serving cell where the UE applies TCI-UL-State.

[0847] In one example, the TCI status (e.g., UL TCI status) includes TAG_ID.

[0848] In one example, TAG_ID refers to the cell determined based on the "servingCellIndex" IE in TCI-UL-State. In another example, if servingCellId is configured, the TAG ID is determined based on servingCellId. Otherwise, the TAG ID is based on the serving cell for which the UE applies TCI-UL-State.

[0849] In one example, TAG_ID refers to a cell determined based on a cell configured with a UL TCI status list as described in this article.

[0850] In one example, TAG_ID refers to the cell determined based on the cell status of the applied UL TCI.

[0851] The flowcharts above illustrate example methods that can be implemented according to the principles of this disclosure, and various modifications can be made to the methods shown in the flowcharts herein. For example, although shown as a series of steps, the individual steps in each diagram may overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, steps may be omitted or replaced with other steps.

[0852] Any of the above-described variant embodiments can be used independently or in combination with at least one other variant embodiment. Although the accompanying drawings illustrate different examples of user equipment, various changes can be made to the drawings. For example, the user equipment can include any number of each component in any suitable arrangement. Generally, the drawings do not limit the scope of this disclosure to any particular configuration. Furthermore, while the drawings illustrate operating environments in which various user equipment features disclosed in this patent document can be used, these features can be used in any other suitable system.

[0853] Although this disclosure has been described using exemplary embodiments, various changes and modifications may be suggested to those skilled in the art. This disclosure is intended to cover such changes and modifications that fall within the scope of the appended claims. Nothing described in this application should be construed as implying that any particular element, step, or function is an essential element that must be included within the scope of the claims. The scope of the patent subject matter is defined by the claims.

Claims

1. A user equipment (UE), comprising: The transceiver is configured as follows: Receive first information for a first set of downlink (DL) or joint candidate cell transmission configuration indicator (TCI) states corresponding to one or more candidate cells. Receive second information for a second set of uplink (UL) candidate cell TCI states corresponding to the one or more candidate cells. Receive a first Media Access Control Channel Element (MAC-CE) for activating a subset of the TCI states of candidate cells from a first set or a second set, and Receive a second MAC CE including the cell handover command, wherein: The cell handover command indicates (1) the candidate cell and (2) the TCI status of at least one candidate cell from a first set or a second set corresponding to the candidate cell, and When the TCI state of the at least one candidate cell is activated by the first MAC-CE, the TCI state of the at least one candidate cell is indicated; and A processor, operatively coupled to the transceiver, is configured to deactivate a subset of active candidate cell TCI states that exclude the at least one candidate cell TCI state.

2. The UE according to claim 1, wherein, When the TCI state of at least one candidate cell is not activated by the first MAC CE, the cell handover command is activated and indicates the TCI state of the at least one candidate cell.

3. The UE according to claim 1, wherein, The source reference signal (RS) for the TCI state of at least one candidate cell is: The synchronization signal / physical broadcast channel (SS / PBCH) block of the candidate cell, or The tracking reference signal (TRS) of the candidate cell.

4. The UE according to claim 1, wherein, The third information includes parameters used to indicate the joint or individual TCI state corresponding to the one or more candidate cells.

5. The UE according to claim 1, wherein: The transceiver is also configured to receive: The set of DL or joint TCI states of the candidate cells, and The set of UL TCI states of the candidate cells, The DL or joint TCI states from the set of DL or joint TCI states and the DL or joint candidate cell TCI states corresponding to the candidate cells have the same TCI state identifier and quasi-co-location type, and The UL TCI states from the set of UL TCI states and the UL candidate cell TCI states corresponding to the candidate cells have the same TCI state identifier and spatial relationship reference signal (RS).

6. The UE according to claim 1, wherein, The transceiver is also configured to receive: A list of path loss reference signals (PL-RS) for candidate cells from the one or more candidate cells, and The at least one candidate cell TCI state includes PL-RS from the list of PL-RS.

7. The UE according to claim 1, wherein: The transceiver is also configured to receive physical downlink control channel (PDCCH) commands from the first cell. The PDCCH command includes a synchronization signal / physical broadcast channel (SS / PBCH) block index. The SS / PBCH block index is the path loss reference signal (PL-RS) for the active TCI state. The processor is also configured to use the SS / PBCH block index as the PL-RS for transmitting the Physical Random Access Channel (PRACH) to the second cell, and The transceiver is also configured to send PRACH to the second cell.

8. A base station (BS), comprising: The transceiver is configured as follows: Send first information for a first set of downlink (DL) or joint candidate cell transmission configuration indicator (TCI) states corresponding to one or more candidate cells. Send second information for a second set of uplink (UL) candidate cell TCI states corresponding to the one or more candidate cells. Send the first Media Access Control Channel Element (MAC-CE) for activating a subset of the TCI states of candidate cells from the first or second set, and Send a second MAC CE including the cell handover command, where: The cell handover command indicates (1) the candidate cell and (2) the TCI status of at least one candidate cell from a first set or a second set corresponding to the candidate cell, and When the TCI state of the at least one candidate cell is activated by the first MAC-CE, the TCI state of the at least one candidate cell is indicated; and A processor, operatively coupled to the transceiver, is configured to deactivate a subset of active candidate cell TCI states that exclude the at least one candidate cell TCI state.

9. The BS according to claim 8, wherein, When the TCI state of at least one candidate cell is not activated by the first MAC CE, the cell handover command is activated and indicates the TCI state of the at least one candidate cell.

10. The BS according to claim 8, wherein, The source reference signal (RS) for the TCI state of at least one candidate cell is: The synchronization signal / physical broadcast channel (SS / PBCH) block of the candidate cell, or The tracking reference signal (TRS) of the candidate cell.

11. The BS according to claim 8, wherein, The third information includes parameters used to indicate the joint or individual TCI state corresponding to the one or more candidate cells.

12. The BS according to claim 8, wherein, The transceiver is also configured to transmit: The set of DL or joint TCI states of the candidate cells, and The set of UL TCI states of the candidate cells, The DL or joint TCI states from the set of DL or joint TCI states and the DL or joint candidate cell TCI states corresponding to the candidate cells have the same TCI state identifier and quasi-co-location type, and The UL TCI states from the set of UL TCI states and the UL candidate cell TCI states corresponding to the candidate cells have the same TCI state identifier and spatial relationship reference signal (RS).

13. The BS according to claim 8, wherein, The transceiver is also configured to transmit: A list of path loss reference signals (PL-RS) for candidate cells from the one or more candidate cells, and The at least one candidate cell TCI state includes PL-RS from the list of PL-RS.

14. The BS according to claim 8, wherein: The transceiver is also configured to send physical downlink control channel (PDCCH) commands from the first cell. The PDCCH command includes a synchronization signal / physical broadcast channel (SS / PBCH) block index. The SS / PBCH block index is the path loss reference signal (PL-RS) for the active TCI state. Among them, the SS / PBCH block index is the PL-RS used for the Physical Random Access Channel (PRACH) to the second cell, and The transceiver is also configured to receive PRACH on the second cell.

15. A method of operating a user equipment (UE), the method comprising: Receive first information for a first set of downlink (DL) or joint candidate cell transmission configuration indicator (TCI) states corresponding to one or more candidate cells; Receive second information for a second set of uplink UL candidate cell TCI states corresponding to the one or more candidate cells; Receive a first Media Access Control Channel Element (MAC-CE) for activating a subset of the TCI states of candidate cells from a first set or a second set. Receive a second MAC CE including the cell handover command, wherein: The cell handover command indicates (1) the candidate cell and (2) the TCI status of at least one candidate cell from a first set or a second set corresponding to the candidate cell, and When the TCI state of the at least one candidate cell is activated by the first MAC-CE, the TCI state of the at least one candidate cell is indicated, and Deactivate a subset of the activated candidate cell TCI states that exclude the at least one candidate cell TCI state.

Images