Method and apparatus for uplink transmission to a transmission / reception point with reduced functionality

Abstract

A method, system and apparatus for performing uplink transmission to a transmission / reception point with reduced functionality in a wireless communication system are provided, wherein the method includes receiving a physical downlink control channel command from a first transmission / reception point of a serving cell, wherein a field in the physical downlink control channel command indicates an association between a physical random access channel transmission and the first transmission / reception point with downlink and uplink functionality or an association between the physical random access channel transmission and a second transmission / reception point of the serving cell that does not have downlink functionality or has reduced downlink functionality, and performing a physical random access channel transmission in response to the physical downlink control channel command, wherein a transmission power of the physical random access channel transmission is determined based on the field.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 542,484, filed on October 4, 2023, which is incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to wireless communication networks, and more particularly to methods and apparatus for uplink transmissions to transmit / receive points with reduced functionality in a wireless communication system. Background Art

[0004] With the rapid growth of the demand for transmitting large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks that communicate using Internet Protocol (IP) packets. This IP packet communication can provide IP-bearing voice, multimedia, multicast and on-demand communication services for users of mobile communication devices.

[0005] An exemplary network structure is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The E-UTRAN system can provide high data throughput to enable the above-mentioned IP-borne voice and multimedia services. Currently, the 3GPP standards organization is discussing new radio technologies for the next generation (e.g., 5G). Therefore, changes to the current body of 3GPP standards are currently being submitted and considered to evolve and complete the 3GPP standards. Summary of the invention

[0006] A method, system and apparatus for performing uplink transmission to a transmission / reception point with reduced functionality in a wireless communication system are provided, wherein the method includes receiving a physical downlink control channel (PDCCH) command from a first transmission / reception point (TRP) of a serving cell, wherein a field in the PDCCH command indicates an association between a physical random access channel (PRACH) transmission and a first TRP with downlink (DL) and uplink (UL) functionality or an association between the PRACH transmission and a second TRP of the serving cell that does not have DL functionality or has reduced DL functionality, and performing the PRACH transmission in response to the PDCCH command, wherein a transmission power of the PRACH transmission is determined based on the field.

[0007] In various embodiments, a method for a UE in a wireless communication system includes receiving a PDCCH command from a first TRP of a serving cell, wherein a field in the PDCCH command is related to a PRACH transmission initiated by the PDCCH command to the first TRP having DL and UL functionality or to a second TRP of the serving cell that does not have DL functionality or has reduced DL functionality, and performing a PRACH transmission in response to the PDCCH command, wherein a transmission power of the PRACH transmission is determined based on the field.

[0008] In various embodiments, a method for a UE in a wireless communication system includes receiving one or more DL signals indicating a first transmission configuration indicator (TCI) state and a second TCI state, receiving a PDCCH command in a serving cell via the first TCI state, wherein a field in the PDCCH command indicates an association between a PRACH transmission and the first TCI state or an association between the PRACH transmission and the second TCI state, and performing a PRACH transmission in response to the PDCCH command, wherein a transmission power of the PRACH transmission is determined based on the field. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 The drawings show a wireless communication system according to an embodiment of the present invention.

[0010] Figure 2 is a block diagram of a transmitter system (also referred to as an access network) and a receiver system (also referred to as a user equipment or UE) according to an embodiment of the present invention.

[0011] Figure 3 is a functional block diagram of a communication system according to an embodiment of the present invention.

[0012] Figure 4 According to an embodiment of the present invention Figure 3 Functional block diagram of the program code.

[0013] Figure 5 It is from 3GPP TS 38.321, V17.5.0 (2023-06) Figure 6 .1.3.47-1: Unified TCI state activation / deactivation of MAC CE reappearance.

[0014] Figure 6 It is from 3GPP TS 38.321, V17.5.0 (2023-06) Figure 6 .1.3.15-1: Reproduction of TCI status indication for UE-specific PDCCH MAC CE.

[0015] Figure 7is an example figure according to an embodiment of the present invention, which shows that for UL-only TRP, TRP1 and TRP2 are both intra-cell TRPs (i.e., TRP1 and TRP2 are in the same serving cell), and the UE can receive DL from TRP1 (e.g., DL) while transmitting UL to TRP2 (e.g., UL2).

[0016] Figure 8 is a flowchart of a method of a UE according to an embodiment of the present invention, which includes receiving a configuration of an uplink-only transmission / reception point from a network node and receiving a PDCCH order from the network node, and performing PRACH transmission in response to the PDCCH order.

[0017] Fig. 9 It is a flowchart of a method of a UE according to an embodiment of the present invention, which includes receiving a PDCCH command from a first TRP of a serving cell, wherein a field in the PDCCH command indicates an association between a PRACH transmission and the first TRP having DL and UL functionality or an association between the PRACH transmission and a second TRP of the serving cell that does not have DL functionality or has reduced DL functionality, and performing PRACH transmission in response to the PDCCH command, wherein the transmission power of the PRACH transmission is determined based on the field.

[0018] Fig.10 It is a flowchart of a method of a UE according to an embodiment of the present invention, which includes receiving a PDCCH command from a first TRP of a serving cell, wherein a field in the PDCCH command is related to a PRACH transmission initiated by the PDCCH command to the first TRP having DL and UL functionality or to a second TRP of the serving cell that does not have DL functionality or has reduced DL functionality, and performing PRACH transmission in response to the PDCCH command, wherein the transmission power of the PRACH transmission is determined based on the field.

[0019] Fig.11 The present invention is a flowchart of a method for a UE, which includes receiving one or more DL signals indicating a first TCI state and a second TCI state, receiving a PDCCH command in a serving cell via the first TCI state, wherein a field in the PDCCH command indicates an association between a PRACH transmission and the first TCI state or an association between the PRACH transmission and the second TCI state, and performing a PRACH transmission in response to the PDCCH command, wherein a transmission power of the PRACH transmission is determined based on the field. DETAILED DESCRIPTION

[0020] The present invention described herein may be applied to or implemented in the exemplary wireless communication systems and devices described below. In addition, the present invention is mainly described in the context of the 3GPP architecture reference model. However, it should be understood that with the help of the disclosed information, those skilled in the art can easily adapt and use and implement aspects of the present invention in the 3GPP2 network architecture as well as other network architectures.

[0021] The exemplary wireless communication systems and devices described below employ wireless communication systems that support broadcast services. Wireless communication systems are widely deployed to provide various types of communications, such as voice, data, etc. These systems can be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP Long Term Evolution (LTE) radio access, 3GPP Long Term Evolution Advanced (LTE-A) radio access, 3GPP2 Ultra Mobile Broadband (UMB), WiMax, 3GPP New Radio (NR), or some other modulation technology.

[0022] In particular, the exemplary wireless communication systems and devices described below may be designed to support one or more standards, such as those provided by a consortium named "3rd Generation Partnership Project" referred to herein as 3GPP, including: [1] 3GPP TS 38.331, V17.5.0 (2023-06), 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) Protocol Specification (Release 17); [2] 3GPP TS 38.321, V17.5.0 (2023-06), 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) Protocol Specification (Release 17); [3] 3GPP TS 38.214, V17.6.0 (2023-06), 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical Layer Procedures for Data (Release 17); [4] 3GPP TS 3GPP TS 38.213, V17.6.0 (2023-06), 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 17); and [5] 3GPP TS 38.212, V17.5.0 (2023-03), 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Multiplexing and channel coding (Release 17). The standards and documents listed above are hereby expressly and completely incorporated herein by reference in their entirety.

[0023] Figure 1 1 shows a multiple access wireless communication system according to an embodiment of the present invention. An access network 100 (AN) includes multiple antenna groups, one including 104 and 106, another including 108 and 110, and another including 112 and 114. Figure 1 , only two antennas are shown for each antenna group, however, more or fewer antennas may be utilized for each antenna group. Access terminal (AT) 116 communicates with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 via forward link 120 and receive information from AT 116 via reverse link 118. AT 122 communicates with antennas 106 and 108, where antennas 106 and 108 transmit information to AT 122 via forward link 126 and receive information from AT 122 via reverse link 124. In an FDD system, communication links 118, 120, 124, and 126 may use different frequencies for communication. For example, forward link 120 may use a different frequency than the frequency used by reverse link 118.

[0024] Each group of antennas and / or the area in which they are designed to communicate is often referred to as a sector of the access network. In an embodiment, the antenna groups are each designed to communicate with access terminals in a sector of the area covered by the access network 100.

[0025] In communicating via forward links 120 and 126, the transmit antennas of access network 100 may utilize beamforming in order to improve the signal-to-noise ratio of the forward links for the different access terminals 116 and 122. Additionally, an access network transmitting to access terminals randomly dispersed throughout its coverage area using beamforming may cause less interference to access terminals in neighboring cells than an access network transmitting to all of its access terminals via a single antenna.

[0026] AN can be a fixed station or base station for communicating with a terminal, and can also be referred to as an access point, Node B, base station, enhanced base station, eNodeB or some other term. AT can also be referred to as user equipment (UE), a wireless communication device, a terminal, an access terminal or some other term.

[0027] Figure 2 2 is a simplified block diagram of an embodiment of a transmitter system 210 (also referred to as an access network) and a receiver system 250 (also referred to as an access terminal (AT) or user equipment (UE)) in a MIMO system 200. At the transmitter system 210, traffic data for a number of data streams is provided from a data source 212 to a transmit (TX) data processor 214.

[0028] In one embodiment, each data stream is transmitted through a respective transmit antenna.TX data processor 214 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.

[0029] The coded data for each data stream may be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data for each data stream are then modulated (e.g., symbol mapped) based on a particular modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for the data stream to provide modulation symbols. Instructions executed by processor 230 may determine the data rate, coding, and modulation for each data stream. Memory 232 is coupled to processor 230.

[0030] The modulation symbols for all data streams are then provided to a TX MIMO processor 220, which may further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then converts the N T The modulation symbol stream is provided to N T transmitters (TMTR) 222a through 222t. In certain embodiments, TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

[0031] Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (eg, amplifies, filters, and up-converts) the analog signals to provide a modulated signal suitable for transmission via a MIMO channel. T The antennas 224a to 224t transmit the N signals from the transmitters 222a to 222t. T a modulated signal.

[0032] At the receiver system 250, N R The transmitted modulated signals are received by each antenna 252a through 252r and the received signal from each antenna 252 is provided to a respective receiver (RCVR) 254a through 254r. Each receiver 254 conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding “received” symbol stream.

[0033] RX data processor 260 then extracts the N R The receiver 254 receives and processes N R received symbol streams to provide N T The RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing by the RX data processor 260 is complementary to the processing performed by the TX MIMO processor 220 and the TX data processor 214 at the transmitter system 210.

[0034] Processor 270 periodically determines which pre-coding matrix to use (discussed below). Processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.

[0035] The reverse link message may include various types of information about the communication link and / or the received data stream. The reverse link message is then processed by the TX data processor 238 (which also receives traffic data for a number of data streams from the data source 236), modulated by the modulator 280, conditioned by the transmitters 254a to 254r, and transmitted back to the transmitter system 210.

[0036] At the transmitter system 210, the modulated signal from the receiver system 250 is received by the antenna 224, conditioned by the receiver 222, demodulated by the demodulator 240, and processed by the RX data processor 242 to extract the reverse link message transmitted by the receiver system 250. The processor 230 then determines which precoding matrix to use to determine the beamforming weights and then processes the extracted message.

[0037] The memory 232 may be used to temporarily store some buffer / calculated data from 240 or 242 via the processor 230, store some buffer data from 212, or store some specific program codes. Also, the memory 272 may be used to temporarily store some buffer / calculated data from 260 via the processor 270, store some buffer data from 236, or store some specific program codes.

[0038] Go to Figure 3 , this figure shows an alternative simplified functional block diagram of a communication device according to one embodiment of the present invention. Figure 3 As shown, the communication device 300 in the wireless communication system can be used to implement Figure 1 UE (or AT) 116 and 122 in, and the wireless communication system is preferably an NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, a program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 through the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive a signal input by a user through the input device 302 (e.g., a keyboard or a keypad), and can output images and sounds through the output device 304 (e.g., a monitor or a speaker). The transceiver 314 is used to receive and transmit wireless signals, pass the received signal to the control circuit 306, and wirelessly output the signal generated by the control circuit 306.

[0039] Figure 4 According to one embodiment of the present invention, Figure 34. In this embodiment, program code 312 includes application layer 400, layer 3 portion 402, and layer 2 portion 404, and is coupled to layer 1 portion 406. Layer 3 portion 402 typically performs radio resource control. Layer 2 portion 404 typically performs link control. Layer 1 portion 406 typically performs physical connectivity.

[0040] For LTE, LTE-A or NR systems, the layer 2 portion 404 may include a radio link control (RLC) layer and a medium access control (MAC) layer. The layer 3 portion 402 may include a radio resource control (RRC) layer.

[0041] Any two or more of the following paragraphs, (sub) bullet points, points, actions or claims described in each invention paragraph or section may be logically, reasonably and appropriately combined to form a particular method.

[0042] Any sentence, paragraph, (sub) bullet, key point, action or claim described in each of the following invention paragraphs or sections can be implemented independently and individually to form a specific method or device. Dependencies such as "based on", "more specifically", "example" and the like in the following disclosure of the present invention are only one possible embodiment that does not limit a specific method or device.

[0043] In [1] 3GPP TS 38.331, V17.5.0 (2023-06), the RRC parameters related to the present disclosure are quoted below:

[0044] -TCI-State

[0045] IE TCI-State associates one or two DL reference signals with the corresponding quasi-colocation (QCL) type.

[0046] TCI-State Information Element

[0047]

[0048]

[0049]

[0050] -TCI-UL-StateIE TCI-UL-State indicates TCI state information for UL transmission. TCI-UL-State information element

[0051]

[0052]

[0053] -RACH-ConfigDedicatedIERACH-ConfigDedicated is used to specify dedicated random access parameters. RACH-ConfigDedicated information element

[0054]

[0055]

[0056]

[0057]

[0058]

[0059] -RACH-ConfigGeneric

[0060] IERACH-ConfigGeneric is used to specify random access parameters both for regular random access and for beam failure recovery.

[0061] RACH-ConfigGeneric Information Element

[0062]

[0063]

[0064] --TAG-RACH-CONFIGGENERIC-STOP--ASN1 STOP

[0065]

[0066]

[0067]

[0068] -ControlResourceSet

[0069] IE ControlResourceSet is used to configure the time / frequency control resource set (CORESET) in which to search for downlink control information (see TS 38.213

[13] , clause 10.1). For UEs that do not support multipleCORESETs in FR1, in order to receive MBS multicast in a CFR within the UE's active BWP, if no CORESET is configured in PDCCH-ConfigMulticast, then a CORESET other than CORESET#0 configured in the UE's active BWP for scheduling unicast may be used to schedule MBS multicast, and the CORESET is expected to be fully contained within the CFR, and the parameters configured in the CORESET are expected to be supported by the UE for MBS multicast.

[0070] ControlResourceSet Information Element

[0071] --ASN1START

[0072] --TAG-CONTROLRESOURCESET-START

[0073]

[0074]

[0075]

[0076] --TAG-CONTROLRESOURCESET-STOP--ASN1 STOP

[0077]

[0078]

[0079]

[0080] -SearchSpace

[0081] IE SearchSpace defines how / where to search for PDCCH candidates. Each search space is associated with a ControlResourceSet. For the scheduled SCell in case of cross-carrier scheduling, all optional fields except nrofCandidates do not exist (regardless of their existence conditions). For the scheduled SpCell in case of cross-carrier scheduling, if the search space is linked to another search space in the scheduling SCell, all optional fields of this search space in the scheduled SpCell do not exist (regardless of their existence conditions), except nrofCandidates.

[0082] SearchSpace Information Element

[0083] --ASN1START

[0084] --TAG-SEARCHSPACE-START

[0085]

[0086]

[0087]

[0088]

[0089]

[0090]

[0091]

[0092]

[0093] In [2] 3GPP TS 38.321, V17.5.0 (2023-06), the relevant paragraphs and MACCE are quoted below:

[0094] 6.1.3.47 Unified TCI status activation / deactivation of MAC CE

[0095] The unified TCI state activation / deactivation MAC CE is identified by a MAC subheader with the eLCID as specified in Table 6.2.1-1b. It has a variable size consisting of the following fields:

[0096] - Serving Cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of the field is 5 bits. If the indicated serving cell is configured as part of simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3 or simultaneousU-TCI-UpdateList4 as specified in TS 38.331 [5], then this MAC CE applies to all serving cells in the set simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3 or simultaneousU-TCI-UpdateList4, respectively;

[0097] - BWP ID: This field indicates the DL BWP applied by the MAC CE as the code point of the DCI Bandwidth Part Indicator field as specified in TS 38.212 [9]. The length of the BWP ID field is 2 bits;

[0098] -BWP ID: This field indicates the UL BWP applied by the MAC CE as the code point of the DCI bandwidth part indicator field as specified in TS 38.212 [9]. If the value of unifiedTCI-StateType in the serving cell indicated by the serving cell ID is joint, this field is considered reserved. The length of the BWP ID field is 2 bits;

[0099] -P i : This field indicates whether each TCI code point has multiple TCI states or a single TCI state. i The P field is set to 1, which indicates that the i-th TCI code point contains both the DL TCI state and the UL TCI state. i The field is set to 0, which indicates that the i-th TCI codepoint contains only DL / Joint TCI state or UL TCI state. The codepoint to which the TCI state is mapped is determined by its ordinal position among all TCI State ID fields;

[0100] -D / U: This field indicates whether the TCI State ID in the same octet is used for the joint / downlink or uplink TCI state. If this field is set to 1, the TCI State ID in the same octet is used for the joint / downlink. If this field is set to 0, the TCI State ID in the same octet is used for the uplink;

[0101] -TCI State ID: This field indicates the TCI state identified by TCI-StateId as specified in TS 38.331 [5]. If D / U is set to 1, the 7-bit length TCI State ID, i.e., TCI-StateId, as specified in TS 38.331 [5] is used. If D / U is set to 0, the most significant bit of the TCI State ID is considered a reserved bit and the remaining 6 bits indicate the TCI-UL-State-Id as specified in TS 38.331 [5]. The maximum number of activated TCI states is 16;

[0102] -R: Reserved bit, set to 0.

[0103] Figure 5 It is from 3GPP TS 38.321, V17.5.0 (2023-06) Figure 6 .1.3.47-1: Unified TCI state activation / deactivation of MAC CE reappearance.

[0104] 6.1.3.15 TCI status indication for UE-specific PDCCH MAC CE

[0105] The TCI status indication for the UE-specific PDCCH MAC CE is identified by a MAC subheader with an LCID as specified in Table 6.2.1-1. It has a fixed size of 16 bits with the following fields:

[0106] - Serving Cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of the field is 5 bits. If the indicated serving cell is configured as part of simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2 as specified in TS 38.331 [5], then this MAC CE applies to all serving cells in a set of simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2, respectively;

[0107] - CORESET ID: This field indicates the control resource set identified by ControlResourceSetId as specified in TS 38.331 [5], indicating its TCI status. In the case where the value of the field is 0, the field refers to the control resource set that has been configured by controlResourceSetZero as specified in TS 38.331 [5]. The length of the field is 4 bits;

[0108] -TCI State ID: This field indicates the TCI state applicable to the control resource set identified by the CORESET ID field, identified by the TCI-StateId as specified in TS 38.331 [5]. If the field of CORESET ID is set to 0, this field indicates the TCI-StateId of the TCI state among the first 64 TCI states configured by the tci-StatesToAddModList and tci-StatesToReleaseList in the PDSCH-Config in the active BWP or by the dl-OrJoint-TCI-State-ToAddModList and dl-OrJoint-TCI-State-ToReleaseList in the PDSCH-Config in the active BWP or the reference BWP. If the field of CORESET ID is set to a value other than 0, this field indicates the TCI-StateId that has been configured by the tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList in the controlResourceSet identified by the indicated CORESET ID. The length of the field is 7 bits.

[0109] Figure 6 It is from 3GPP TS 38.321, V17.5.0 (2023-06) Figure 6 .1.3.15-1: Reproduction of TCI status indication for UE-specific PDCCH MAC CE.

[0110] In [3] 3GPP TS 38.214, V17.6.0 (2023-06), the following is provided:

[0111] 5.1.5 Quasi-co-location of antenna ports

[0112] The UE may be configured with a list of up to M TCI-State configurations within the higher layer parameter PDSCH-Config to decode the PDSCH based on a detected PDCCH with DCI intended for the UE and a given serving cell, where M depends on the UE capability maxNumberConfiguredTCIstatesPerCC. Each TCI-State contains parameters for configuring a quasi-co-location relationship between one or two downlink reference signals and the DM-RS ports of the PDSCH, the DM-RS ports of the PDCCH, or the CSI-RS ports of the CSI-RS resources. The quasi-co-location relationship is configured by the higher layer parameter qcl-Type1 for the first DL RS and the higher layer parameter qcl-Type2 for the second DL RS (if configured). In the case of two DL RSs, the QCL type will be different, regardless of whether the reference is to the same DL RS or different DL RSs. The quasi-co-location type corresponding to each DL RS is given by the higher layer parameter qcl-Type in QCL-Info and can take one of the following values:

[0113] - 'Type A': {Doppler shift, Doppler spread, average delay, delay spread}

[0114] - 'Type B': {Doppler shift, Doppler spread}

[0115] - 'Type C': {Doppler shift, average delay}

[0116] - 'Type D': {Spatial Rx Parameters}

[0117] The UE may be configured with a list of up to 128 TCI-State configurations within the higher layer parameter dl-OrJointTCI-StateList in PDSCH-Config for providing quasi-co-located reference signals for the DM-RS of the PDSCH and the DM-RS of the PDCCH in a CC, for CSI-RS, and, where applicable, for determining the UL TX spatial filter for PUSCH and PUCCH resources and SRS in the CC based on dynamic grants and configured grants.

[0118] If the TCI-State or TCI-UL-State configuration does not exist in the BWP of the CC, the UE may apply the TCI-State or TCI-UL-State configuration from the reference BWP of the reference CC. If the UE is configured with dl-OrJointTCI-StateList or ul-TCI-StateList in any CC in the band, the UE is not expected to be configured with tci-StatesToAddModList, SpatialRelationInfo or PUCCH-SpatialRelationInfo in CCs in the same band, except SpatialRelationInfoPos. The UE may assume that when the UE is configured with tci-StatesToAddModList in any CC in the CC list configured by simultaneousTCI-UpdateList1-r16, simultaneousTCI-UpdateList2-r16, simultaneousSpatial-UpdatedList1-r16 or simultaneousSpatial-UpdatedList2-r16, the UE is not configured with dl-OrJointTCI-StateList or ul-TCI-StateList in any CC in the same frequency band in the CC list.

[0119] The UE receives an activation command as described in clause 6.1.3.14 of [10, TS 38.321] or 6.1.3.47 of [10, TS 38.321] for mapping up to 8 TCI states and / or TCI state pairs to codepoints of the DCI field 'Transmission Configuration Indication' for one or a set of CC / DL BWPs and (if applicable) for one or a set of CC / UL BWPs, wherein one TCI state is used for a DL channel / signal and / or one TCI state is used for a UL channel / signal. When a set of TCI state IDs is activated for a CC / DL BWP set and (if applicable) for a CC / UL BWP set, wherein the applicable list of CCs is determined by the CCs indicated in the activation command, the same set of TCI state IDs applies for all DL and / or UL BWPs in the indicated CCs. If the activation command maps the TCI-State and / or TCI-UL-State to only one TCI code point, once the indicated mapping for the one single TCI code point is applied as described in [11, TS38.133], the UE shall apply the indicated TCI-State and / or TCI-UL-State to one CC / DL BWP or a set thereof, and, if applicable, to one CC / UL BWP or a set thereof.

[0120] When the bwp-id or cell of the QCL-TypeA / D source RS in the QCL-Info of the TCI state is not configured, the UE assumes that the QCL-TypeA / D source RS is configured in the CC / DL BWP in which the TCI state is applicable.

[0121] When tci-PresentInDCI is set to 'enabled' or tci-PresentDCI-1-2 is configured for CORESET, a UE configured with a dl-OrJointTCI-StateList with an activated TCI-State or a ul-TCI-StateList with an activated TCI-UL-State receives DCI format 1_1 / 1_2, which provides the indicated TCI-State and / or TCI-UL-State of one CC or all CCs in the same CC list configured by simultaneousU-TCI-UpdateList1-r17, simultaneousU-TCI-UpdateList2-r17, simultaneousU-TCI-UpdateList3-r17, simultaneousU-TCI-UpdateList4-r17. DCI format 1_1 / 1_2 may or may not have (if applicable) a DL assignment. If DCI format 1_1 / 1_2 / no DL assignment, the UE may assume the following:

[0122] -CS-RNTI is used to scramble the CRC of the DCI

[0123] - Set the values ​​of the following DCI fields as follows:

[0124] -RV=all '1'

[0125] -MCS=all '1'

[0126] -NDI=0

[0127] - Set to all '0' for FDRA type 0, or set to all '1' for FDRA type 1, or set to all '0' for dynamicSwitch (same as in Table 10.2-4 of [6, TS 38.213]).

[0128] After the UE receives an initial higher layer configuration of dl-OrJointTCI-StateList with more than one TCI-State and before applying the indicated TCI state from the configured TCI state:

[0129] - The UE assumes that the DM-RS of the PDSCH and the DMR-S of the PDCCH and the CSI-RS to which the indicated TCI state is applied are quasi-co-located with the SS / PBCH block identified by the UE during the initial access procedure

[0130] After the UE receives an initial higher layer configuration of a dl-OrJointTCI-StateList with more than one TCI-State or a ul-TCI-StateList with more than one TCI-UL-State and before applying the indicated TCI state from the configured TCI state:

[0131] - The UE assumes, if applicable, that the UL TX spatial filters for PUSCH and PUCCH based on dynamic grants and configured grants, and for SRS to which the indicated TCI state is applied, are the same as the UL TX spatial filters used for PUSCH transmissions scheduled by the RAR UL grant during the initial access procedure

[0132] After the UE receives a higher layer configuration of dl-OrJointTCI-StateList with more than one TCI-State as part of the reconfiguration procedure with synchronization as described in [12, TS 38.331], and before applying the indicated TCI from the configured TCI state:

[0133] - The UE assumes that the DM-RS of the PDSCH and the DM-RS of the PDCCH, and the CSI-RS to which the indicated TCI state is applied, are quasi-co-located with the SS / PBCH blocks or the CSI-RS resources identified by the UE during the random access procedure initiated with the synchronized reconfiguration procedure as described in [12, TS 38.331].

[0134] After the UE receives a higher layer configuration of dl-OrJointTCI-StateList with more than one TCI-State or more than one TCI-UL-State as part of the reconfiguration procedure with synchronization as described in [12, TS 38.331], and before applying the indicated TCI from the configured TCI state:

[0135] - The UE assumes, if applicable, that the UL TX spatial filters for PUSCH and PUCCH based on dynamic grants and configured grants, and for SRS for which the indicated TCI state is applied, are the same as the UL TX spatial filters used for PUSCH transmissions scheduled by the RAR UL grant during the initial access procedure initiated by the reconfiguration procedure with synchronization as described in [12, TS 38.331].

[0136] If the UE receives a higher layer configuration of dl-OrJointTCI-StateList with a single TCI-State that can be used as the indicated TCI state, the UE obtains the QCL assumption from the configured TCI states for the DM-RS for the PDSCH and the DM-RS for the PDCCH, and the CSI-RS to which the indicated TCI state is applied.

[0137] If the UE receives a higher layer configuration of a dl-OrJointTCI-StateList with a single TCI-State or a ul-TCI-StateList with a single TCI-UL-State that can be used as the indicated TCI state, the UE determines the UL TX spatial filter (if applicable) from the configured TCI states of PUSCH and PUCCH based on the dynamic grant and configured grant, and the SRS to which the indicated TCI state is applied.

[0138] When a UE configured with dl-OrJointTCI-StateList is to transmit a PUCCH with positive HARQ-ACK or a PUSCH with positive HARQ-ACK corresponding to a DCI carrying a TCI state indication and without DL assignment or corresponding to a PDSCH scheduled by a DCI carrying a TCI state indication, and if the indicated TCI state is different from the previously indicated one, the indicated TCI-State and / or TCI-UL-State shall apply starting from the first slot at least beamAppTime symbols after the last symbol of the PUCCH or PUSCH. Both the first slot and beamAppTime symbols are determined over the active BWP, where the minimum SCS among the BWPs of the CC applies the indicated TCI-State or TCI-UL-State active at the end of the PUCCH or PUSCH carrying positive HARQ-ACK.

[0139] If the UE is configured with a pdsch-TimeDomainAllocationListForMultiPDSCH where one or more rows contain multiple SLIVs for PDSCH on the DL BWP of the serving cell, and the UE is receiving a DCI carrying a TCI-State indication and without a DL assignment, the UE does not expect the number of SLIVs indicated by the DCI in the rows of the pdsch-TimeDomainAllocationListForMultiPDSCH to be more than one.

[0140] If the UE is configured with SSB-MTC-AdditionalPCI and PDCCH-Config containing two different values ​​of coresetPoolIndex in ControlResourceSet, the UE receives an activation command for the CORESET associated with each coresetPoolIndex, as described in clause 6.1.3.14 of [10, TS 38.321] to map up to 8 TCI states to the codepoint of the DCI field 'Transmission Configuration Indication' in one CC / DL BWP. When a set of TCI state IDs is activated for a coresetPoolIndex, the activated TCI state corresponding to one coresetPoolIndex is associated with the serving cell physical cell ID, and the activated TCI state corresponding to another coresetPoolIndex may be associated with another physical cell ID.

[0141] When the UE supports two TCI states in the code point of the DCI field 'Transmission Configuration Indication', the UE may receive an activation command as described in clause 6.1.3.24 of [10, TS 38.321], the activation command being used to map up to 8 combinations of one or two TCI states to the code point of the DCI field 'Transmission Configuration Indication'. The UE is not expected to receive more than 8 TCI states in the activation command.

[0142] When the DCI field 'Transmission Configuration Indication' is present in DCI format 1_2 and when the number of code points S in the DCI field 'Transmission Configuration Indication' of DCI format 1_2 is less than the number of TCI code points activated by the activation command, as described in clauses 6.1.3.14 and 6.1.3.24 of [10, TS38.321], only the first S activated code points are applied to DCI format 1_2.

[0143] When the UE is to transmit a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH carrying the activation command, the indicated mapping between the TCI states and the code points of the DCI field 'Transmission Configuration Indication' shall be from , where μ is the SCS configuration for PUCCH, and μ Kmac is k with value 0 for frequency range 1 mac The subcarrier spacing configuration is k mac Supplied by K-Mac, or if K-Mac is not provided, k mac= 0. If tci-PresentInDCI is set to 'enabled' or tci-PresentDCI-1-2 is configured as CORESET for scheduling PDSCH, and the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than timeDurationForQCL (if applicable), then after the UE receives the initial higher layer configuration of the TCI state and before the reception of the activation command, the UE may assume that the DM-RS ports of the PDSCH of the serving cell are quasi-co-located with the SS / PBCH blocks determined in the initial access procedure with respect to the qcl-Type set to 'Type A' and, if applicable, also with respect to the qcl-Type set to 'Type D'.

[0144] If the UE is configured with the higher layer parameter tci-PresentInDCI set to 'enabled' for the CORESET for scheduling PDSCH, the UE assumes that the TCI field is present in DCI format 1_1 of the PDCCH transmitted on the CORESET. If the UE is configured with the higher layer parameter tci-PresentDCI-1-2 for the CORESET for scheduling PDSCH, the UE assumes that the TCI field is present in DCI format 1_2 of the PDCCH transmitted on the CORESET with the DCI field size indicated by tci-PresentDCI-1-2. If the UE is configured with the higher layer parameter tci-PresentInDCI set to 'enabled' for the CORESET for scheduling multicast PDSCH, the UE assumes that the TCI field is present in DCI format 4_2 of the PDCCH transmitted on the CORESET. If PDSCH is scheduled via a DCI format in which the TCI field is absent, and the time offset between the reception of the DL DCI and the corresponding PDSCH of the serving cell is equal to or greater than a threshold timeDurationForQCL (if applicable), where the threshold is based on reported UE capabilities [13, TS 38.306], for the purpose of determining PDSCH antenna port quasi-co-location, the UE assumes that the TCI state or QCL assumption used for PDSCH is the same as the TCI state or QCL assumption applied by the CORESET for PDCCH transmissions within the active BWP of the serving cell (whichever is the other).

[0145] When the UE is configured with both sfnSchemePdcch and sfnSchemePdsch scheduled by DCI format 1_0 or DCI format 1_1 / 1_2, if the time offset between the reception of the DL DCI and the corresponding PDSCH of the serving cell is equal to or greater than the threshold timeDurationForQCL (if applicable), then:

[0146] - If the UE supports sfn-DefaultDL-BeamSetup-r17 for DCI scheduling without TCI field, the UE assumes that the TCI state or QCL assumption for PDSCH is the same as the TCI state or QCL assumption applied by the CORESET for reception of DL DCI within the active BWP of the serving cell, regardless of the number of active TCI states of the CORESET. If the UE does not support sfn-SchemeA-DynamicSwitching-r17 or sfn-SchemeB-DynamicSwitching-r17, the UE shall be activated with a CORESET with two TCI states.

[0147] - Otherwise if the UE does not support sfn-DefaultDL-BeamSetup-r17 for DCI scheduling without TCI field, the UE shall expect the TCI field to be present when scheduled by DCI format 1_1 / 1_2.

[0148] When the UE is configured with sfnSchemePdsch and sfnSchemePdcch is not configured, when scheduled by DCI format 1_1 / 1_2, if the time offset between the reception of the DL DCI and the corresponding PDSCH of the serving cell is equal to or greater than the threshold timeDurationForQCL (if applicable), the UE shall expect the TCI field to be present.

[0149] For PDSCH scheduled by DCI formats 1_0, 1_1, 1_2, when the UE is configured with sfnSchemePdcch set to 'sfnSchemeA' and sfnSchemePdsch is not configured, and no TCI code point with two TCI states is present in the activation command, and if the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than the threshold timeDurationForQCL (if applicable) and the CORESET scheduling the PDSCH is indicated with two TCI states, the UE assumes that the TCI state or QCL assumption used for the PDSCH is the same as the first TCI state or QCL assumption applied for the CORESET transmitted for the PDCCH within the active BWP for the serving cell.

[0150] If the PDSCH is scheduled by a DCI format in which the TCI field is present, then the TCI field in the DCI in the scheduling component carrier points to an activated TCI state in the scheduled component carrier or DL ​​BWP, and the UE shall use the TCI-State based on the value of the 'Transmission Configuration Indication' field in the detected PDCCH with DCI for determining the PDSCH antenna port quasi-co-location. If the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than the threshold timeDurationForQCL, the UE may assume that the DM-RS ports of the PDSCH of the serving cell are quasi-co-located with the RS in the TCI state relative to the QCL type parameter given by the indicated TCI state, where the threshold is based on the reported UE capabilities [13, TS 38.306]. For single-slot PDSCH, the indicated TCI state shall be based on the activated TCI state in the slot with the scheduled PDSCH. For multi-slot PDSCH or the UE is configured with the higher layer parameter pdsch-TimeDomainAllocationListForMultiPDSCH, the indicated TCI state shall be based on the activated TCI state in the first slot with scheduled PDSCH, and the UE shall expect the activated TCI state to be the same across slots with scheduled PDSCH. When the UE is configured with a CORESET associated with a search space set for cross-carrier scheduling and the UE is not configured with enableDefaultBeamForCCS, the UE expects tci-PresentInDCI to be set to 'enabled' or tci-PresentDCI-1-2 to be configured for the CORESET, and if one or more of the TCI states configured for serving cells scheduled by the search space set contains qcl-Type set to 'Type D', then the UE expects the time offset between the reception of a detected PDCCH in the search space set and the corresponding PDSCH to be greater than or equal to the threshold timeDurationForQCL.

[0151] Independent of the configuration of tci-PresentInDCI and tci-PresentDCI-1-2 in RRC connected mode, if the UE is not provided with dl-OrJointTCI-StateList-r17, and if the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL and at least one configured TCI state of the serving cell for the scheduled PDSCH contains qcl-Type set to 'typeD', then

[0152] - The UE may assume that the DM-RS ports of the PDSCH of the serving cell are quasi-co-located with the RS relative to the QCL parameters of the PDCCH quasi-co-location indication for the CORESET associated with the monitoring search space with the lowest controlResourceSetId in the latest slot in which one or more CORESETs within the active BWP of the serving cell were monitored by the UE. In this case, if qcl-Type is set to 'typeD' of the PDSCH DM-RS different from the PDCCH DM-RS it overlaps in at least one symbol, the UE is expected to prioritize the reception of the PDCCH associated with the CORESET. This also applies to the intra-band CA case (when the PDSCH and the CORESET are in different component carriers).

[0153] - if the UE is configured with enableDefaultTCI-StatePerCoresetPoolIndex and the UE is configured with a higher layer parameter PDCCH-Config containing two different values ​​for coresetPoolIndex in different ControlResourceSets,

[0154] -The UE may assume that the DM-RS ports of the PDSCH associated with the value of coresetPoolIndex of the serving cell are quasi-co-located with the RS with respect to the QCL parameters of the PDCCH quasi-co-location indication for the CORESET associated with the monitoring search space with the lowest controlResourceSetId among the CORESETs configured with the same coresetPoolIndex value as the PDCCH scheduling the PDSCH in the latest slot, where one or more CORESETs associated with the same coresetPoolIndex value as the PDCCH scheduling the PDSCH within the active BWP of the serving cell are monitored by the UE. In this case, if the 'QCL type D' of the PDSCH DM-RS is different from the PDCCH DM-RS that it overlaps in at least one symbol and they are associated with the same value of coresetPoolIndex, the UE is expected to prioritize the reception of the PDCCH associated with the CORESET. This also applies to the intra-band CA case (when the PDSCH and the CORESET are in different component carriers).

[0155] - If the UE is configured with enableTwoDefaultTCI-States and at least one TCI codepoint indicates two TCI states, the UE may assume that the DM-RS port of the PDSCH or PDSCH transmission opportunity of the serving cell is quasi-co-located with the RS with respect to the QCL parameter associated with the TCI state corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states. When the UE is configured with the higher layer parameter repetitionScheme set to 'tdmSchemeA' or is configured with the higher layer parameter repetitionNumber, and the offset between the reception of the DL DCI and the first PDSCH transmission opportunity is less than the threshold timeDurationForQCL, the mapping of TCI states to PDSCH transmission opportunities is determined according to clause 5.1.2.1 by replacing the indicated TCI state with the TCI state corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states, based on the activated TCI states in the timeslot with the first PDSCH transmission opportunity. In this case, if the 'QCL Type D' in the two TCI states corresponding to the lowest code point among the TCI code points containing two different TCI states is different from the 'QCL Type D' of the PDCCH DM-RS with which they overlap in at least one symbol, then the UE is expected to prioritize the reception of the PDCCH associated with the CORESET. This also applies to the intra-band CA case (when the PDSCH and CORESET are in different component carriers)

[0156] - If the UE is not configured with sfnSchemePdsch, and the UE is configured with sfnSchemePdcch set to 'sfnSchemeA' and there is no TCI codepoint with two TCI states in the activation command and the CORESET with the lowest ID in the latest slot is indicated with two TCI states, then the UE may assume that the DM-RS ports of the PDSCH of the serving cell are quasi-co-located with the RS with respect to the QCL parameters associated with the first of the two TCI states indicated for the CORESET. In this case, if qcl-Type is set to 'Type D' for the PDSCH DM-RS to be different from the PDCCH DM-RS it overlaps in at least one symbol, then the UE is expected to prioritize the reception of the PDCCH associated with said CORESET with a single active TCI state. This also applies to intra-band CA cases (when the PDSCH and CORESET are in different component carriers).

[0157] - In all the above cases, if the configured TCI state of the serving cell for the scheduled PDSCH is not configured with qcl-Type set to 'Type D', the UE shall derive other QCL assumptions from the indicated TCI state for its scheduled PDSCH, regardless of the time offset between the reception of the DL DCI and the corresponding PDSCH.

[0158] Independent of the configuration of tci-PresentInDCI and tci-PresentDCI-1-2 in RRC connected mode, if the UE is provided with dl-OrJointTCI-StateList-r17, and if the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL and at least one configured TCI state of the serving cell for the scheduled PDSCH contains a qcl-Type set to 'typeD', regardless of the configuration of followUnifiedTCI-State,

[0159] - If the indicated TCI state is associated with the PCI of the serving cell, the indicated TCI state is applied to PDSCH reception.

[0160] - If the indicated TCI state is associated with a different PCI than that of the serving cell, the UE may assume that the DM-RS ports of the PDSCH of the serving cell are quasi-co-located with the RS with respect to the QCL parameters of the PDCCH quasi-co-location indication for the CORESET associated with the monitored search space with the lowest controlResourceSetId in the latest slot in which the UE monitored one or more CORESETs within the active BWP of the serving cell. In the CA case, if the 'QCL Type D' of the PDSCH DM-RS from the corresponding CCs in the band are different in the slot, the QCL Type D assumption of the PDSCH DM-RS in the CC with the lowest CC ID in the band is applied to all PDSCH DM-RS in the CCs in the band. In this case, if the qcl-Type of the PDSCH DM-RS set to 'Type D' is different from the type of the PDCCH DM-RS they overlap in at least one symbol, the UE is expected to prioritize the reception of the PDCCH associated with the CORESET. This also applies to the intra-band CA case (when PDSCH and CORESET are in different component carriers).

[0161] If the PDCCH carrying the scheduling DCI is received on one component carrier, and the PDSCH scheduled by the DCI is on another component carrier:

[0162] -timeDurationForQCL is determined based on the subcarrier spacing of the scheduled PDSCH. PDCCH <μ PDSCH , then the additional timing delay Added to timeDurationForQCL, where d is defined in 5.2.1.5.1a-1, otherwise d is zero;

[0163] -When the UE is configured with enableDefaultBeamForCCS, if the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL, or if the TCI field is not present in the DL DCI, the UE obtains its QCL assumption for the scheduled PDSCH from the activated TCI state with the lowest ID of the PDSCH in the active BWP applicable to the scheduled cell.

[0164] As described in [13, TS 38.306], a UE that has indicated the capability beamCorrespondenceWithoutUL-BeamSweeping set to 'Supported' may determine the spatial domain filter to be used while performing the applicable channel access procedure described in [16, TS 37.213] prior to UL transmission on the channel as follows:

[0165] - if the UE is indicated with an SRI corresponding to a UL transmission, the UE may use the same spatial domain filter as the spatial domain transmit filter associated with the indicated SRI,

[0166] - if the UE is configured with SRS-spatialRelationInfo for UL transmission, the UE may use the same spatial domain filter as the spatial domain filter associated with the referenceSignal in the corresponding SRS-spatialRelationInfo,

[0167] - If the UE is configured with a TCI-State in the dl-OrJointTCI-StateList or a TCI-UL-State in the ul-TCI-StateList, the UE may use the same spatial domain receive filters as the spatial domain receive filters that the UE may use to receive DL reference signals associated with the indicated TCI state.

[0168] When a PDCCH reception includes two PDCCHs from two corresponding search space sets, as described in clause 10.1 of [6, TS 38.213], for the purpose of determining the time offset between the reception of the DL DCI and the corresponding PDSCH, the PDCCH candidate that ends later in time is used. When a PDCCH reception includes two PDCCH candidates from two corresponding search space sets, as described in clause 10.1 of [6, TS 38.213], for the configuration of tci-PresentInDCI or tci-PresentDCI-1-2, the UE expects the same configuration in the first and second CORESETs associated with the two PDCCH candidates; and if the PDSCH is scheduled by a DCI format without the presence of the TCI field and if the scheduling offset is equal to or greater than timeDurationForQCL (if applicable), the PDSCH QCL assumption is based on the CORESET with the lower ID among the first and second CORESETs associated with the two PDCCH candidates.

[0169] For periodic CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, the UE shall expect the TCI-State to indicate one of the following quasi co-location types:

[0170] - 'Type C' with SS / PBCH blocks and, where applicable, 'Type D' with the same SS / PBCH blocks, where the PCI of the SS / PBCH blocks may be different from the PCI of the serving cell. The UE may assume that the center frequency, SCS, SFN offset of the SS / PBCH blocks from the serving cell and the SS / PBCH blocks with a different PCI from the serving cell are the same, or

[0171] - 'Type C' with SS / PBCH blocks and, where applicable, 'Type D' with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, where the PCI of the SS / PBCH blocks may be different from the PCI of the serving cell. The UE may assume that the center frequency, SCS, SFN offset are the same for the SS / PBCH blocks from the serving cell and for SS / PBCH blocks with a different PCI from the serving cell.

[0172] For periodic / semi-persistent CSI-RS, if the UE is configured with dl-OrJointTCI-StateList, the UE may assume that the indicated TCI-State does not apply.

[0173] For non-periodic CSI-RS resources in NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info, the UE shall expect the TCI-State indication to have a qcl-Type set to 'Type A' for the periodic CSI-RS resources in NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info, and, when applicable, a qcl-Type set to 'Type D' for the same periodic CSI-RS resources.

[0174] For CSI-RS resources in NZP-CSI-RS-ResourceSet for which the higher layer parameter trs-Info is not configured and the higher layer parameter repetition is not configured, the UE shall expect the TCI-State to indicate one of the following quasi co-location types:

[0175] - 'Type A' with a CSI-RS resource configured in NZP-CSI-RS-ResourceSet with the higher layer parameter trs-Info, and, where applicable, 'Type D' with the same CSI-RS resource, or

[0176] - 'Type A' with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info, and 'Type D' with SS / PBCH blocks where applicable, where the PCI of the SS / PBCH blocks may be different from the PCI of the serving cell. The UE may assume that the center frequency, SCS, SFN offset are the same for the SS / PBCH blocks from the serving cell and for the SS / PBCH blocks with a different PCI from the serving cell, or

[0177] - 'Type A' with CSI-RS resources configured in NZP-CSI-RS-ResourceSet with the higher layer parameter trs-Info and, where applicable, 'Type D' with CSI-RS resources configured in NZP-CSI-RS-ResourceSet with the higher layer parameter repetition, or

[0178] - 'Type B' with CSI-RS resources configured in NZP-CSI-RS-ResourceSet with higher layer parameter trs-Info when 'Type D' is not applicable.

[0179] For CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, the UE shall expect the TCI-State to indicate one of the following quasi co-location types:

[0180] - 'Type A' with a CSI-RS resource configured in NZP-CSI-RS-ResourceSet with the higher layer parameter trs-Info, and, where applicable, 'Type D' with the same CSI-RS resource, or

[0181] - 'Type A' with CSI-RS resources configured in NZP-CSI-RS-ResourceSet with the higher layer parameter trs-Info and, where applicable, 'Type D' with CSI-RS resources configured in NZP-CSI-RS-ResourceSet with the higher layer parameter repetition, or

[0182] - 'Type C' with SS / PBCH blocks, and 'Type D' with the same SS / PBCH blocks when applicable, the reference RS may additionally be a SS / PBCH block with a PCI different from that of the serving cell. The UE may assume that the center frequency, SCS, SFN offset of the SS / PBCH blocks from the serving cell and the SS / PBCH blocks with a PCI different from that of the serving cell are the same.

[0183] For the DM-RS of the PDCCH, if the UE is not configured with dl-OrJointTCI-StateList, the UE shall expect the TCI-State to indicate one of the following quasi co-location types:

[0184] - 'Type A' with a CSI-RS resource configured in NZP-CSI-RS-ResourceSet with the higher layer parameter trs-Info, and, where applicable, 'Type D' with the same CSI-RS resource, or

[0185] - 'Type A' with CSI-RS resources configured in NZP-CSI-RS-ResourceSet with the higher layer parameter trs-Info and, where applicable, 'Type D' with CSI-RS resources configured in NZP-CSI-RS-ResourceSet with the higher layer parameter repetition, or

[0186] - 'Type A' with a CSI-RS resource in the NZP-CSI-RS-ResourceSet for which the higher layer parameter trs-Info is not configured and the higher layer parameter repetition is not configured, and, when applicable, 'Type D' with the same CSI-RS resource.

[0187] When the UE is configured with sfnSchemePdcch set to 'sfnSchemeA' and the CORESET is activated with two TCI states, the UE shall assume that the DM-RS ports of the PDCCH in the CORESET are quasi-co-located with the DL-RS of the two TCI states. When the UE is configured with sfnSchemePdcch set to 'sfnSchemeB' and the CORESET is activated with two TCI states, the UE shall assume that the DM-RS ports of the PDCCH are quasi-co-located with the DL-RS of the two TCI states, except for the quasi-co-location parameters {Doppler shift, Doppler spread} of the second indicated TCI state.

[0188] For the DM-RS of PDSCH, if the UE is not configured with dl-OrJointTCI-StateList, the UE shall expect the TCI-State to indicate one of the following quasi co-location types:

[0189] - 'Type A' with a CSI-RS resource configured in NZP-CSI-RS-ResourceSet with the higher layer parameter trs-Info, and, where applicable, 'Type D' with the same CSI-RS resource, or

[0190] - 'Type A' with CSI-RS resources configured in NZP-CSI-RS-ResourceSet with the higher layer parameter trs-Info and, where applicable, 'Type D' with CSI-RS resources configured in NZP-CSI-RS-ResourceSet with the higher layer parameter repetition, or

[0191] - 'Type A' with a CSI-RS resource in the NZP-CSI-RS-ResourceSet for which the higher layer parameter trs-Info is not configured and the higher layer parameter repetition is not configured, and, when applicable, 'Type D' with the same CSI-RS resource.

[0192] For the DM-RS of the PDCCH, if the UE is configured with dl-OrJointTCI-StateList, the UE shall expect the indicated TCI-State to indicate one of the following quasi co-location types:

[0193] - 'Type A' with a CSI-RS resource configured in NZP-CSI-RS-ResourceSet with the higher layer parameter trs-Info, and, where applicable, 'Type D' with the same CSI-RS resource, or

[0194] - 'Type A' with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, when applicable, 'Type D' with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition.

[0195] For DM-RS of PDSCH, if the UE is configured with dl-OrJointTCI-StateList, the UE shall expect the indicated TCI-State to indicate one of the following quasi co-location types:

[0196] - 'Type A' with a CSI-RS resource configured in NZP-CSI-RS-ResourceSet with the higher layer parameter trs-Info, and, where applicable, 'Type D' with the same CSI-RS resource, or

[0197] - 'Type A' with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info and, when applicable, 'Type D' with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition.

[0198] When the UE is configured with sfnSchemePdsch set to 'sfnSchemeA' and the UE is indicated with two TCI states in the code point of the DCI field 'Transmission Configuration Indication' in the DCI that schedules the PDSCH, the UE shall assume that the DM-RS ports of the PDSCH are quasi-co-located with the DL-RS of the two TCI states. When the UE is configured with sfnSchemePdsch set to 'sfnSchemeB' and the UE is indicated with two TCI states in the code point of the DCI field 'Transmission Configuration Indication' in the DCI that schedules the PDSCH, the UE shall assume that the DM-RS ports of the PDSCH are quasi-co-located with the DL-RS of the two TCI states, except for the quasi-co-location parameters {Doppler shift, Doppler spread} of the second indicated TCI state.

[0199] In [4] 3GPP TS 38.213, V17.6.0 (2023-06), the following is provided:

[0200] 6 Link Recovery Procedure

[0201] For each BWP of the serving cell, the UE can be provided with a set of periodic CSI-RS resource configuration indices via failureDetectionResourcesToAddModList and a set of periodic CSI-RS resource configuration indices and / or SS / PBCH block indices are provided through candidateBeamRSList or candidateBeamRSListExt or candidateBeamRSSCellList for radio link quality measurement on the BWP of the serving cell Alternative to collection and For each BWP of the serving cell, the UE may be provided with two corresponding sets of periodic CSI-RS resource configuration indices through failureDetectionSet1 and failureDetectionSet2 which may be activated by MAC CE [11TS 38.321] and And two corresponding sets of periodic CSI-RS resource configuration indexes and / or SS / PBCH block indexes are provided through candidateBeamRS-List and candidateBeamRS-List2 respectively used for radio link quality measurement on the BWP of the serving cell and gather With Collection Related and collection With Collection Associated.

[0202] If the UE is not provided with failureDetectionResourcesToAddModList for the BWP for the serving cell Then the UE determines the set Contains a periodic CSI-RS resource configuration index that has the same value as the RS index in the RS set indicated by the TCI-State of the corresponding CORESET used by the UE to monitor the PDCCH. and Then the UE determines the set and Contains a periodic CSI-RS resource configuration index having the same value as an RS index in the RS set indicated by the TCI-State for the first and second CORESETs used by the UE to monitor the PDCCH, respectively, where the UE is provided with two coresetPoolIndex values ​​of 0 and 1 for the first and second CORESETs, or is not provided with a coresetPoolIndex value for the first CORESET and is provided with a coresetPoolIndex value of 1 for the second CORESET, respectively. If there are two RS indices in the TCI state, the set or or Contains RS indices configured with qcl-Type set to 'Type D' for the corresponding TCI state. If the CORESET used by the UE to monitor PDCCH contains two TCI states and the UE is provided with sfnSchemePdcch set to 'sfnSchemeA' or 'sfnSchemeB', then the set Contains RS indices in the RS set associated with the two TCI states.

[0203] UE expected set Contains at most two RS indices. If the UE is provided or Then the UE expected set or Collection Contains at most N BFD-RS-resourcesPerSetPerBWP as indicated by maxBFD-RS-resourcesPerSetPerBWP BFD RS index. If the UE is not provided or And if the number of active TCI states for PDCCH reception in the first or second CORESET is greater than N BFD , then UE determines the set or Contains a periodic CSI-RS resource configuration index having the same value as an RS index in an RS set associated with an active TCI state for PDCCH reception in a first or second CORESET corresponding to a search space set in ascending order of PDCCH monitoring periodicity. If more than one first or second CORESET corresponds to a search space set with the same monitoring periodicity, the UE determines the order of the first or second CORESETs according to descending order of the CORESET index.

[0204] If UE

[0205] - coresetPoolIndex is not provided or the first CORESET on the active DL BWP for the serving cell is provided with a coresetPoolIndex with value 0,

[0206] - the second CORESET on the active DL BWP for the serving cell is provided with a coresetPoolIndex with a value of 1, and

[0207] -Provided by SSB-MTCAdditionalPCI

[0208] SS / PBCH block indices associated with physical cell identities other than those provided by physCellId in ServingCellConfigCommon may be provided in or In the set, and corresponding or A set is associated with the physical cell identity.

[0209] UE expected set or or The single-port RS in UE expected set or or A single-port or two-port CSI-RS with a frequency density equal to 1 or 3 REs per RB. out，LR and Q in，LR They correspond to [10, TS 38.133] for Q out The preset value of rlmInSyncOutOfSyncThreshold described and the value provided by rsrp-ThresholdSSB or rsrp-ThresholdBFR.

[0210] Physical layer in UE UE comparison Q out，LR According to the resource configuration collection or Evaluate the radio link quality. The UE shall evaluate the radio link quality based only on the SS / PBCH blocks on the PCell or PSCell or periodic CSI-RS resource configuration that is quasi-co-located with the DM-RS received by the UE as described in [6, TS 38.214]. in，LR The threshold is applied to the L1-RSRP measurement obtained from the SS / PBCH block. After scaling the corresponding CSI-RS received power by the value provided by powerControlOffsetSS, the UE sets Q in，LRThe threshold is applied to the L1-RSRP measurement value obtained for the CSI-RS resource.

[0211] In non-DRX mode operation, the physical layer in the UE provides a set of parameters to the higher layers that the UE uses to evaluate the quality of the radio link. In or Collection or When the radio link quality of all corresponding resource configurations in out，LR The physical layer periodically informs higher layers when the radio link quality is better than the threshold Q out，LR The periodicity is a set of or The maximum value between the shortest periodicity among the SS / PBCH blocks on the PCell or PSCell and / or periodic CSI-RS configuration in the DRX mode and 2 milliseconds. In DRX mode operation, the physical layer provides the higher layer with a periodicity determined as described in [10, TS 38.133] when the radio link quality is better than the threshold Q out，LR Poor instructions.

[0212] For PCell or PSCell, upon request from higher layers, the UE provides higher layers with or or The periodic CSI-RS configuration index and / or SS / PBCH block index, and greater than or equal to Q in，LR The corresponding L1-RSRP measurement value of the threshold.

[0213] For SCell, upon request from higher layers, the UE indicates to higher layers whether there is a corresponding L1-RSRP measurement value from the set or or At least one periodic CSI-RS configuration index or SS / PBCH block index is greater than or equal to Q in，LR threshold, and provide a value greater than or equal to Q in，LR Thresholds from the set or or The periodic CSI-RS configuration index and / or SS / PBCH block index and corresponding L1-RSRP measurement value (if any).

[0214] For a PCell or PSCell, the UE may be provided with a CORESET via a link to the search space set provided by recoverySearchSpaceId, as described in clause 10.1, for monitoring PDCCH in the CORESET. If the UE is provided with recoverySearchSpaceId, the UE is not expected to be provided with another search space set for monitoring PDCCH in the CORESET associated with the search space set provided by recoverySearchSpaceId.

[0215] For PCell or PSCell, the configuration for PRACH transmission may be provided to the UE via PRACH-ResourceDedicatedBFR as described in clause 8.1. For PRACH transmission in slot n and according to the periodic CSI-RS resource configuration or and the index q provided by higher layers new The associated SS / PBCH block associated antenna port quasi-co-location parameters [11, TS38.321], the UE monitors the PDCCH in the search space set provided by recoverySearchSpaceId for detecting the failure from slot n+4+2 within the window configured by BeamFailureRecoveryConfig μ ·k mac Start with a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI, where μ is the SCS configuration for PRACH transmission and k mac is the number of time slots provided by kmac [12, TS 38.331], or k if kmac is not provided mac = 0. For PDCCH monitoring and corresponding PDSCH reception in the search space set provided by recoverySearchSpaceId, the UE assumes that the antenna port quasi-co-location parameter and index q newThe associated antenna port quasi-co-location parameters are the same until the UE receives an activation from a higher layer for the TCI state or any of the parameters tci-StatesPDCCH-ToAddList and / or tci-StatesPDCCH-ToReleaseList. After the UE detects a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI in the search space set provided by recoverySearchSpaceId, the UE continues to monitor PDCCH candidates in the search space set provided by recoverySearchSpaceId until the UE receives a MAC CE activation command for the TCI state or tci-StatesPDCCH-ToAddList and / or tci-StatesPDCCH-ToReleaseList.

[0216] For PCell or PSCell, after 28 symbols from the last symbol of the first PDCCH reception in the search space set provided by recoverySearchSpaceId (where the UE detects a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI) and before the UE receives an activation command [11, TS38.321] for PUCCH-SpatialRelationInfo or PUCCH-SpatialRelationInfo provided for PUCCH resources, the UE transmits PUCCH on the same cell as the PRACH transmission using the following

[0217] -Same spatial filter as last PRACH transmission

[0218] - power determined as described in clause 7.2.1, where q u =0,q d =q new And l = 0

[0219] For PCell or PSCell and for the set and After 28 symbols starting from the last symbol of the first PDCCH reception in the search space set provided by recoverySearchSpaceId where the UE detects a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI, the UE assumes and matches the index q for PDCCH monitoring in CORESET with index 0. new The associated antenna port quasi co-location parameters are the same antenna port quasi co-location parameters.

[0220] If the UE is provided with a dl-OrJointTCI-StateList or ul-TCI-StateList [6, TS 38.214] indicating a unified TCI state for a PCell or PSCell, then after 28 symbols from the last symbol of the first PDCCH reception in the search space set provided by recoverySearchSpaceId where the UE detected a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI, the UE

[0221] - If SSB-MTC-AdditionalPCI is not provided, PDCCH is monitored in all CORESETs and the sum and corresponding index q are used new (if any) associated antenna port quasi-co-location parameters with the same antenna port quasi-co-location parameters PDSCH and aperiodic CSI-RS resources are received in a CSI-RS resource set with the same indicated TCI state for PDCCH and PDSCH

[0222] - For the last PRACH transmission using the following parameters for determining the corresponding power as described in clauses 7.1.1, 7.2.1 and 7.3.1, transmit PUSCH, PUCCH and SRS using the same spatial domain filter with the same indicated TCI state for PUSCH and PUCCH

[0223] - RS index q used to obtain downlink path loss estimate d =q new

[0224] - P provided by p0AlphaSetforPUSCH associated with the minimum value of ul-powercontrolId for PCell or PSCell O_UE_PUSCH，b，f，c (j), α b，f，c (j) and the value of PUSCH power control adjustment state l

[0225] - P provided by p0AlphaSetforPUCCH associated with the minimum value of ul-powercontrolId for PCell or PSCell O_PUCCH，b，f，c (q u ) and the value of PUCCH power control adjustment state l

[0226] - P provided by p0AlphaSetforSRS associated with the minimum value of ul-powercontrolId for PCell or PSCell O_SRS，b，f，c (q s ), αSRS，b，f，c (q s ) and the value of SRS power control adjustment state l

[0227] For the remainder of this clause, if a PDCCH reception includes two PDCCH candidates from two linked search space sets based on searchSpaceLinkingId, as described in clause 10.1, then the last symbol of the PDCCH reception is the last symbol of the later ending PDCCH candidate. The PDCCH reception also includes the two PDCCH candidates when the UE does not need to monitor one of the two PDCCH candidates, as described in clauses 10 (except clause 10.4), 11.1, 11.1.1 and 17.2.

[0228] For PCell or PSCell, if the BFR MAC CE [11, TS 38.321] is provided in Msg3 or MsgA of the contention based random access procedure and if the PUCCH resource has PUCCH-SpatialRelationInfo, then after 28 symbols from the last symbol of PDCCH reception that determined the completion of the contention based random access procedure as described in clause 5.1.4a or clause 5.1.5 of [11, TS 38.321], the UE transmits PUCCH on the same cell as the PRACH transmission using the following

[0229] -Same spatial filter as last PRACH transmission

[0230] - power determined as described in clause 7.2.1, where q u =0,q d =q new and l = 0, where q new is the SS / PBCH block index selected for the last PRACH transmission.

[0231] If the UE is provided with a dl-OrJointTCI-StateList or ul-TCI-StateList indicating a unified TCI state for a PCell or PSCell, and the UE provides a BFRMAC CE in Msg3 or MsgA of a contention-based random access procedure, then 28 symbols after the last symbol of PDCCH reception for which completion of the contention-based random access procedure is determined as described in [11, TS 38.321], the UE

[0232] - If SSB-MTC-AdditionalPCI is not provided, PDCCH is monitored in all CORESETs and the sum and corresponding index q are used new(if any) associated antenna port quasi-co-location parameters with the same antenna port quasi-co-location parameters PDSCH and aperiodic CSI-RS resources are received in a CSI-RS resource set with the same indicated TCI state for PDCCH and PDSCH

[0233] - For the last PRACH transmission using the following parameters for determining the corresponding power as described in clauses 7.1.1, 7.2.1 and 7.3.1, transmit PUSCH, PUCCH and SRS using the same spatial domain filter with the same indicated TCI state for said PUSCH and PUCCH

[0234] - RS index q used to obtain downlink path loss estimate d =q new

[0235] - P provided by p0AlphaSetforPUSCH associated with the minimum value of ul-powercontrolId for PCell or PSCell O_UE_PUSCH，b，f，c (j), α b，f，c (j) and the value of PUSCH power control adjustment state l

[0236] - P provided by p0AlphaSetforPUCCH associated with the minimum value of ul-powercontrolId for PCell or PSCell O_PUCCH，b，f，c (q u ) and the value of PUCCH power control adjustment state l

[0237] - P provided by p0AlphaSetforSRS associated with the minimum value of ul-powercontrolId for PCell or PSCell O_SRS，b，f，c (q s ), α sRs , b, f, c (q s ) and the value of SRS power control adjustment state l

[0238] The UE may be provided with a configuration for PUCCH transmission with a Link Recovery Request (LRR) as described in clause 9.2.4 by the schedulingRequestID-BFR-SCell for the UE to transmit PUCCH [11, TS 38.321]. and and with the collection and If the UE is associated with the first configuration, the UE may be provided with a first configuration for PUCCH transmission with LRR by schedulingRequestID-BFR, and if the UE provides twoLRRcapability, the UE may be provided with a second configuration for PUCCH transmission with LRR by schedulingRequestID-BFR2. If the UE is provided with only the first configuration, the UE shall or Transmitting PUCCH with LRR. If the UE is provided with both the first configuration and the second configuration, the UE transmits the PUCCH with the set using the first configuration associated with a PUCCH with LRR and transmitted using a second configuration and set Associated PUCCH with LRR [11, TS 38.321].

[0239] The UE may be used for at least out，LR The first PUSCH MAC CE index of the corresponding SCell with poor radio link quality provides q for the corresponding SCell. new An indication of the presence of, and an index q for the periodic CSI-RS configuration or for the SS / PBCH block provided by a higher layer as described in [11, TS38.321] for the corresponding SCell new , if present. After 28 symbols from the last symbol received of a PDCCH with a DCI format scheduling a PUSCH transmission with the same HARQ process number as the transmission of the first PUSCH and with a switched NDI field value, the UE

[0240] - Use the sum and the corresponding index q new (if any) Associated antenna port quasi co-location parameters Same antenna port quasi co-location parameters Monitor PDCCH in all CORESETs on the Scell ​​indicated by MAC CE

[0241] - Use the same protocol as described in clause 9.2.2 for periodic CSI-RS or SS / PBCH block reception as corresponding to q new The PUCCH is transmitted on the PUCCH-SCell using the same spatial domain filter as that of the PUCCH (if any), and using the power determined as described in clause 7.2.1, where q u =0,q d =q new And l = 0, the premise is

[0242] - The UE is provided with the PUCCH-SpatialRelationInfo for the PUCCH,

[0243] - PUCCH with LRR is not transmitted on PCell or PSCell or is transmitted on PCell or PSCell, and

[0244] -PUCCH-SCell is included in the SCell indicated by MAC-CE

[0245] The SCS configuration for the 28 symbols is the minimum of the SCS configuration of the active DL BWP for PDCCH reception and the SCS configuration of the active DL BWP of the at least one SCell.

[0246] If the UE is provided with a dl-OrJointTCI-StateList or ul-TCI-StateList indicating a unified TCI state, then 28 symbols after the last symbol received from a PDCCH with a DCI format scheduling a PUSCH transmission with the same HARQ process number as the transmission of the first PUSCH and with a switched NDI field value, the UE

[0247] - If SSB-MTC-AdditionalPCI is not provided, PDCCH is monitored in all CORESETs on the SCell indicated by the MAC CE and the sum and the corresponding index q are used new (If present) Associated antenna port quasi co-location parameters Antenna port quasi co-location parameters with the same parameters receive PDSCH and aperiodic CSI-RS resources in the CSI-RS resource set

[0248] - Use and correspond to q new Transmit PUSCH, PUCCH and SRS using the same spatial domain filter with the same indicated TCI state for PUSCH and PUCCH (if any) and using the following parameters for determining corresponding powers as described in clauses 7.1.1, 7.2.1 and 7.3.1

[0249] - RS index q used to obtain downlink path loss estimate d =q new

[0250] - P provided by p0AlphaSetforPUSCH associated with the minimum value of ul-powercontrolId for the corresponding SCell O_UE_PUSCH，b，f，c (j), α b，f，c (j) and the value of PUSCH power control adjustment state l

[0251] - P provided by p0AlphaSetforPUCCH associated with the minimum value of ul-powercontrolId for the corresponding SCell O_PUCCH，b，f，c (q u ) and the value of PUCCH power control adjustment state l

[0252] - P provided by p0AlphaSetforSRS associated with the minimum value of ul-powercontrolId for the corresponding SCell O_SRS，b，f，c (q s ), α SRS , b, f, c(q s ) and the value of SRS power control adjustment state l

[0253] If there is a set and and with the collection and associated with at least one serving cell, the UE can and / or have and Q out，LR The second PUSCH MAC CE index of at least one cell with poor radio link quality provides those and / or The index of q new The presence of and from the serving cell and / or corresponding sets and / or The index q new (if any) an indication of the presence of.

[0254] For the collection and and with the collection and Related and with Q out，LR poor radio link quality for a serving cell, the UE assumes antenna port quasi co-location parameters 28 symbols after the last symbol received of the first PDCCH with a DCI format scheduling a PUSCH transmission with the same HARQ process number for the transmission of a second PUSCH and with a switched NDI field value

[0255] - For the first CORESET, corresponding to Q new (if any),

[0256] - For the second CORESET, corresponding to the Q new(if present)

[0257] The SCS configuration for the 28 symbols is the smallest of the SCS configuration of the active DL BWP for PDCCH reception and the SCS configuration of the active DL BWP of the serving cell.

[0258] …

[0259] 7.4 Physical Random Access Channel

[0260] The UE determines the transmit power P for the physical random access channel (PRACH) on the active ULBWP b of carrier f of serving cell c based on the DL RS for serving cell c in transmit opportunity i. PRACH,b,f,c (i)

[0261] P PRACHb,,f,c (i) = min{P CMAX,f,c (i),P PRACHt,arget,f,c +PL b,f,c}[dBm],

[0262] Where P CMAX,f,c (i) is the UE configured maximum output power defined in [8-1, TS 38.101-1], [8-2, TS 38.101-2] and [8-3, TS 38.101-3] for carrier f of serving cell c in transmission opportunity i, P PRACH,target,f,c is the PRACH target received power PREAMBLE_RECEIVED_TARGET_POWER provided by higher layers [11, TS 38.321] for carrier f of serving cell c, and PL b,f,c is the path loss of the active UL BWP b for carrier f based on the DL RS associated with the PRACH transmission on the active DL BWP of serving cell c and is calculated by the UE in dB as referenceSignalPower in dBm - higher layer filtered RSRP, where RSRP is defined in [7, TS 38.215] and higher layer filter configurations are defined in [12, TS 38.331]. If the active DL BWP is the initial DL BWP and is used for SS / PBCH blocks and CORESET multiplexing mode 2 or 3 as described in clause 13, the UE determines the PL based on the SS / PBCH blocks associated with the PRACH transmission b,f,c .

[0263] If the PRACH transmission from the UE is not in response to the UE detecting a PDCCH order, or in response to the UE detecting a PDCCH order triggering a contention-based random access procedure, or with an index q corresponding thereto newIn association with the link recovery procedure associated with a SS / PBCH block, as described in clause 6, the referenceSignalPower is provided by the ss-PBCH-BlockPower.

[0264] If the PRACH transmission from the UE is in response to the UE's detection of a PDCCH order triggering a contention-free random access procedure and the DM-RS of the PDCCH order is dependent on its quasi-co-located DL RS as described in clause 10.1, then the referenceSignalPower is provided by ss-PBCH-BlockPower, or if the UE is configured for resources for periodic CSI-RS reception or the PRACH transmission is associated with a link recovery procedure, where the corresponding index q new In association with a periodic CSI-RS configuration as described in clause 6, the referenceSignalPower is derived from the ss-PBCH-BlockPower and powerControlOffsetSS, where powerControlOffsetSS provides an offset of the CSI-RS transmit power relative to the SS / PBCH block transmit power [6, TS 38.214]. If powerControlOffsetSS is not provided to the UE, the UE assumes an offset of 0 dB. If the active TCI state of the PDCCH providing the PDCCH command contains two RSs, the UE expects one RS to be configured with qcl-Type set to 'Type D' and the UE uses that one RS when applying the value provided by powerControlOffsetSS.

[0265] If, within the random access response window, as described in clause 8.2, the UE does not receive a random access response containing a preamble identifier corresponding to a preamble sequence transmitted by the UE, the UE determines the transmit power for subsequent PRACH transmissions (if any) as described in [11, TS 38.321].

[0266] If the UE changes the spatial domain transmit filter before PRACH retransmission, Layer 1 informs higher layers to suspend the power ramp counter as described in [11, TS 38.321].

[0267] If the UE does not transmit PRACH in a transmit opportunity due to power allocation for PUSCH / PUCCH / PRACH / SRS transmission as described in clause 7.5, or due to power allocation in EN-DC or NE-DC or NR-DC operation, or due to slot format determination as described in clause 11.1, or due to PUSCH / PUCCH / PRACH / SRS transmission opportunities being in the same slot or a smaller gap between PRACH transmission and PUSCH / PUCCH / SRS transmission as described in clause 8.1, or due to DAPS operation as described in clause 15, or due to HD-UE operation in paired spectrum as described in clause 17.2, then layer 1 notifies higher layers to suspend the corresponding power ramp counter. If the UE transmits PRACH in a transmit opportunity with reduced power due to power allocation for PUSCH / PUCCH / PRACH / SRS transmission as described in clause 7.5, or due to power allocation in EN-DC or NE-DC or NR-DC operation, then layer 1 may notify higher layers to suspend the corresponding power ramp counter.

[0268] …

[0269] 8 Random Access Procedure

[0270] Before initiating the physical random access procedure, Layer 1 receives a set of SS / PBCH block indices from higher layers and provides a corresponding set of RSRP measurement values ​​to the higher layers.

[0271] Prior to initiation of the physical random access procedure, Layer 1 may receive an indication from a higher layer to perform a Type 1 random access procedure as described in clauses 8.1 to 8.4 or a Type 2 random access procedure as described in clauses 8.1 to 8.2A.

[0272] Before initiating the physical random access procedure, Layer 1 receives the following information from higher layers:

[0273] - Configuration of physical random access channel (PRACH) transmission parameters (PRACH preamble format, time resources, and frequency resources used for PRACH transmission).

[0274] - Parameters used to determine the root sequence and its cyclic shift in the PRACH preamble sequence set (index of the logical root sequence table, cyclic shift (N CS ) and the collection type (unrestricted, restricted collection A, or restricted collection B).

[0275] From the physical layer perspective, the Type 1 L1 random access procedure includes the transmission of a random access preamble (Msg1) in PRACH, a random access response (RAR) message (Msg2) with PDCCH / PDSCH, and, when applicable, the transmission of a PUSCH scheduled by the RAR UL grant and a PDSCH for contention resolution.

[0276] From the physical layer perspective, the Type 2 L1 random access procedure includes the transmission of a random access preamble and PUSCH (MsgA) in PRACH and the reception of a RAR message (MsgB) with PDCCH / PDSCH, and, when applicable, the transmission of PUSCH scheduled by a fallback RAR UL grant and PDSCH for contention resolution.

[0277] If the random access procedure is initiated by a PDCCH order to the UE, the PRACH transmission has the same SCS as a PRACH transmission initiated by higher layers.

[0278] If the UE is configured with two UL carriers for the serving cell and the UE detects a PDCCH order, the UE uses the UL / SUL indicator field value from the detected PDCCH order to determine the UL carrier to use for the corresponding PRACH transmission.

[0279] 8.1 Random Access Preamble

[0280] The physical random access procedure is triggered following a request for PRACH transmission by higher layers or a PDCCH order. The configuration by higher layers for PRACH transmission contains the following:

[0281] - Configuration for PRACH transmission [4, TS 38.211].

[0282] -Preamble index, preamble SCS, P PRACH，目标 , corresponding to RA-RNTI, and PRACH resources.

[0283] The selected PRACH format is used on the indicated PRACH resource with a transmit power P as described in clause 7.4. PRACH，b ,f, c (i) Transmitting PRACH.

[0284] For the Type 1 random access procedure, the number N of SS / PBCH block indices associated with one PRACH opportunity and the number R of contention-based preambles per valid PRACH opportunity per SS / PBCH block index are provided to the UE via ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0285] For Type 2 random access procedure with co-configuration of PRACH opportunities with Type 1 random access procedure, the UE is provided with the number N SS / PBCH block indices associated with one PRACH opportunity via ssb-perRACH-OccasionAndCB-PreamblesPerSSB and the number Q contention-based preambles per valid PRACH opportunity per SS / PBCH block index via msgA-CB-PreamblesPerSSB-PerSharedRO. For UEs provided with the PRACH mask index via msgA-SSB-SharedRO-MaskIndex according to [11, TS 38.321], PRACH transmissions may be on a subset of PRACH opportunities associated with the same SS / PBCH block index within the SSB-RO mapping cycle.

[0286] For a Type 2 random access procedure with a separate configuration of PRACH opportunities from a Type 1 random access procedure, the UE is provided with the number N SS / PBCH block indices associated with one PRACH opportunity and the number R contention-based preambles per valid PRACH opportunity per SS / PBCH block index via msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB when provided; otherwise, via ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0287] For the random access procedure associated with the feature combination indicated by FeatureCombinationPreambles, the UE is provided with the number N SS / PBCH block indices associated with one PRACH opportunity via ssb-perRACH-OccasionAndCB-PreamblesPerSSB or msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB when provided and the number S contention-based preambles per valid PRACH opportunity per SS / PBCH block index via startPreambleForThisPartition and numberOfPreamblesPerSSB-ForThisPartition. For UEs provided with the PRACH mask index via ssb-SharedRO-MaskIndex according to [11, TS 38.321], PRACH transmissions may be on a subset of PRACH opportunities associated with the same SS / PBCH block index within the SSB-RO mapping cycle.

[0288] For a Type 1 random access procedure, or for a Type 2 random access procedure with a configuration of PRACH opportunities separate from a Type 1 random access procedure, if N < 1, then one SS / PBCH block index is mapped to 1 / N consecutive valid PRACH opportunities, and the R contention-based preambles with consecutive indices associated with the SS / PBCH block index per valid PRACH opportunity start from preamble index 0. If N ≥ 1, then the R contention-based preambles with consecutive indices associated with the SS / PBCH block index n per valid PRACH opportunity, 0 ≤ n ≤ N-1, start from preamble index Start, where Provided by totalNumberOfRA-Preambles for a Type 1 random access procedure, or provided by msgA-TotalNumberOfRA-Preambles for a Type 2 random access procedure with a configuration of PRACH opportunities separate from the Type 1 random access procedure, and is an integer multiple of N.

[0289] For a type 2 random access procedure with a configuration of PRACH opportunities common to a type 1 random access procedure, if N < 1, then one SS / PBCH block index is mapped to 1 / N consecutive valid PRACH opportunities, and Q contention-based preambles with consecutive indices associated with the SS / PBCH blocks per valid PRACH opportunity start from preamble index R. If N ≥ 1, then Q contention-based preambles with consecutive indices associated with the SS / PBCH block index n per valid PRACH opportunity, 0 ≤ n ≤ N-1, start from preamble index R. Start, where Provided by totalNumberOfRA-Preambles for Type 1 Random Access procedure.

[0290] For link recovery, the N SS / PBCH block indices associated with one PRACH opportunity are provided to the UE via ssb-perRACH-Occasion in BeamFailureRecoveryConfig. For the dedicated RACH configuration provided by RACH-ConfigDedicated, if cfra is provided, the N SS / PBCH block indices associated with one PRACH opportunity are provided to the UE via ssb-perRACH-Occasion in occasions. If N<1, then one SS / PBCH block index is mapped to 1 / N consecutive valid PRACH opportunities. If N≥1, then all N consecutive SS / PBCH block indices are associated with one PRACH opportunity.

[0291] The SS / PBCH block indices provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon are mapped to valid PRACH opportunities in the following order, where the parameters are described in [4, TS 38.211].

[0292] - First, in increasing order of preamble index within a single PRACH opportunity

[0293] - Second, in increasing order of frequency resource index for frequency multiplexing PRACH opportunities

[0294] - Third, in increasing order of time resource index for time multiplexing PRACH opportunities within a PRACH slot

[0295] - Fourth, in increasing order of index used for PRACH slots

[0296] The association period used to map SS / PBCH block indices to PRACH opportunities starting from frame 0 is the minimum value in the set determined by the PRACH configuration period according to Table 8.1-1, such that The SS / PBCH block index is mapped to the PRACH opportunity at least once in the associated period, where the UE obtains the value of ssb-PositionsInBurst from SIB1 or ServingCellConfigCommon If an integer number of SS / PBCH block indices to PRACH opportunities are mapped to the associated period after the mapping cycle, there are If a PRACH opportunity or PRACH preamble is associated with a set of SS / PBCH block indices, then no SS / PBCH block index is mapped to the set of PRACH opportunities or PRACH preambles. The association pattern period includes one or more association periods and is determined so that the pattern between PRACH opportunities and SS / PBCH block indices repeats at most every 160 milliseconds. PRACH opportunities that are not associated with SS / PBCH block indices after an integer number of association periods (if any) are not used for PRACH transmission.

[0297] For a PRACH transmission of a UE triggered by a PDCCH order, if the value of the Random Access Preamble Index field is not zero, then the PRACH Mask Index field [5, TS 38.212] indicates the PRACH opportunity for the PRACH transmission, where the PRACH opportunity is associated with the SS / PBCH block index indicated by the SS / PBCH Block Index field of the PDCCH order. If the UE is provided with K via cellSpecificKoffset 小区，偏移 , then the PRACH opportunity is in time slot n+2μ ·K 小区，偏移 After that, where n is assumed to be T TA = 0, and μ is the SCS configuration for PRACH transmission. If the PDCCH reception for the PDCCH command contains two PDCCH candidates from two linked search space sets based on searchSpaceLinkingId, as described in clause 10.1, the last symbol of the PDCCH reception is the last symbol of the PDCCH candidate that ends later. The PDCCH reception also contains the two PDCCH candidates when the UE does not need to monitor one of the two PDCCH candidates, as described in clauses 10 (except clause 10.4), 11.1, 11.1.1 and 17.2.

[0298] For PRACH transmission triggered by higher layers, if ssb-ResourceList is provided, the PRACH mask index is indicated by ra-ssb-OccasionMaskIndex, which indicates the PRACH opportunity used for PRACH transmission, where the PRACH opportunity is associated with the selected SS / PBCH block index.

[0299] The PRACH opportunities are mapped consecutively per corresponding SS / PBCH block index. The index of the PRACH opportunity indicated by the mask index value is reset per mapping cycle of consecutive PRACH opportunities per SS / PBCH block index. The UE selects the PRACH opportunity indicated by the PRACH mask index value for the indicated SS / PBCH block index in the first available mapping cycle for PRACH transmission.

[0300] For the indicated preamble index, the ordering of the PRACH opportunities is

[0301] - First, in increasing order of frequency resource index for frequency multiplexing PRACH opportunities

[0302] - Second, in increasing order of time resource index for time multiplexed PRACH opportunities within a PRACH slot

[0303] - Third, in increasing order of index used for PRACH slots

[0304] For PRACH transmission triggered upon request of a higher layer, if csirs-ResourceList is provided, the value of ra-OccasionList [12, TS 38.331] indicates a list of PRACH opportunities for PRACH transmission, where the PRACH opportunities are associated with the selected CSI-RS index indicated by csi-RS. The index of the PRACH opportunity indicated by ra-OccasionList is reset every association mode period.

[0305] Table 8.1-1: Mapping between PRACH configuration period and SS / PBCH block to PRACH opportunity association period

[0306]

[0307] For paired spectrum or supplemental uplink bands, all PRACH opportunities are valid.

[0308] For the unpaired spectrum,

[0309] - If the UE is not provided with tdd-UL-DL-ConfigurationCommon, then the PRACH opportunity in the PRACH slot is valid if it does not precede an SS / PBCH block in the PRACH slot and is at least N received symbols after the last SS / PBCH block. gap Symbols start, where N gap Provided in Table 8.1-2, and if channelAccessMode="semi-static" is provided, does not overlap with a set of consecutive symbols before the start of the next channel occupancy time in which the UE does not transmit [15, TS 37.213].

[0310] - The candidate SS / PBCH block index of the SS / PBCH block corresponds to the SS / PBCH block index provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon, as described in clause 4.1

[0311] - If the UE is provided with tdd-UL-DL-ConfigurationCommon, then the PRACH opportunities in the PRACH slots are valid provided that

[0312] - it is within the UL symbol, or

[0313] - It does not precede an SS / PBCH block in a PRACH slot and is at least N after the last downlink symbol gap symbols and at least N after the last SS / PBCH block symbol gapSymbols start, where N gap Provided in Table 8.1-2, and if channelAccessMode="semi-static" is provided, does not overlap with a set of consecutive symbols before the start of the next channel occupancy time in which there will not be any transmission, as described in [15, TS 37.213]

[0314] - The candidate SS / PBCH block index of the SS / PBCH block corresponds to the SS / PBCH block index provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon, as described in clause 4.1.

[0315] For preamble format B4 [4, TS 38.211], N gap =0.

[0316] Table 8.1-2: N for different preamble codes SCSμ gap value

[0317]

[0318] If the random access procedure is initiated by a PDCCH order, then if requested by higher layers, the UE transmits PRACH in the selected PRACH opportunity as described in [11, TS 38.321], the time between the last symbol received by the PDCCH order and the first symbol transmitted by the PRACH is greater than or equal to N T , 2+Δ BWPSwitching +Δ Delay +T switch milliseconds, where

[0319] -N T，2 is the duration of N2 symbols corresponding to the PUSCH preparation time for UE processing capability 1 [6, TS 38.214], assuming that μ corresponds to the minimum SCS configuration between the SCS configuration commanded by the PDCCH and the SCS configuration transmitted by the corresponding PRACH

[0320] - If the active UL BWP does not change, then Δ BWPSwitching =0, otherwise Δ BWPSwitching Also defined in [10, TS38.133]

[0321] - For FR1, Δ Delay = 0.5 ms, and for FR2, Δ Delay = 0.25 ms

[0322] -T switch is the switching gap duration as defined in [6, TS 38.214]

[0323] For PRACH transmissions using 1.25 kHz or 5 kHz SCS, the UE determines N2, assuming SCS configuration μ=0.

[0324] For single cell operation or for operation with contiguous carrier aggregation in the same frequency band or for operation with non-contiguous carrier aggregation in the same frequency band if the UE is not provided with intraBandNC-PRACH-simulTx-r17, the UE does not transmit PRACH and PUSCH / PUCCH / SRS in the same slot or does not transmit when the first or last symbol of a PRACH transmission in a first slot is separated from the last or first symbol of a PUSCH / PUCCH / SRS transmission in a second slot by less than N symbols, respectively, relative to the minimum SCS configuration between the SCS configuration for the UL BWP with PRACH and the SCS configuration for the UL BWP with PUSCH / PUCCH / SRS transmission, where N=2 for μ=0 or μ=1, N=4 for μ=2 or μ=3, N=16 for μ=5, N=32 for μ=6, and μ is the SCS configuration for the UL BWP with PRACH and the SCS configuration for the UL BWP with PUSCH / PUCCH / SRS transmission. The minimum SCS configuration between the SCS configurations of the BWP. For a PUSCH transmission with repetition type B, this applies for every actual repetition of the PUSCH transmission [6, TS 38.214].

[0325] …

[0326] 8.2 Random Access Response - Type 1 Random Access Procedure

[0327] …

[0328] If the UE attempts to detect DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order triggering a non-contention random access procedure for the SpCell [11, TS 38.321], the UE may assume that the PDCCH contains DCI format 1_0 and the PDCCH order has the same DM-RS antenna port quasi-co-location characteristic. If the UE attempts to detect DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order triggering a non-contention random access procedure for the secondary cell, the UE may assume that the DM-RS antenna port quasi-co-location characteristic of the CORESET associated with the Type1-PDCCH CSS set used to receive the PDCCH contains DCI format 1_0.

[0329] …

[0330] 10.1 UE Procedure for Determining Physical Downlink Control Channel Assignments

[0331] A set of PDCCH candidates for UE monitoring is defined according to a PDCCH search space set. A search space set can be a CSS set or a USS set. The UE monitors PDCCH candidates in one or more of the following search space sets:

[0332] -Type0-PDCCH CSS set on the primary cell of the MCG, which is configured by the following items

[0333] - for DCI format 1_0 with CRC scrambled by SI-RNTI, pdcch-ConfigSIB1 in the MIB or searchSpaceSIB1 in PDCCH-ConfigCommon or searchSpaceZero in PDCCH-ConfigCommon, or

[0334] - For DCI format 4_0 with CRC scrambled by MCCH-RNTI or G-RNTI for broadcast, searchSpaceZero by providing searchSpaceID=0 for searchSpaceMCCH or searchSpaceMTCH

[0335] - For DCI format 1_0 with CRC scrambled by SI-RNTI on the primary cell of the MCG, the Type0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon

[0336] - For DCI format 4_0 with CRC scrambled by MCCH-RNTI on the primary cell of the MCG or G-RNTI for broadcast, Type0 B-PDCCH CSS set configured by searchSpaceMCCH and searchSpaceMTCH

[0337] - Type1-PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommon for DCI format with CRC scrambled by RA-RNTI, MsgB-RNTI or TC-RNTI on the primary cell

[0338] - For DCI formats with CRC scrambled by C-RNTI or CS-RNTI on the primary cell as described in clause 19.1, the Type 1A-PDCCH CSS set configured by sdt-SearchSpace in PDCCH-ConfigCommon

[0339] - For DCI format 1_0 with CRC scrambled by P-RNTI on the primary cell of the MCG, the Type2-PDCCH CSS set configured by pagingSearchSpace in PDCCH-ConfigCommon

[0340] - For DCI format 2_7 with CRC scrambled by PEI-RNTI on the primary cell of the MCG, the Type2A-PDCCH CSS set configured by pei-SearchSpace in pei-ConfigBWP

[0341] -Type3-PDCCH CSS set, which is configured by the following

[0342] - SearchSpace in PDCCH-Config with searchSpaceType=common for a DCI format with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI or CI-RNTI and by C-RNTI, MCS-C-RNTI, CS-RNTI or PS-RNTI for the primary cell only, or

[0343] -SearchSpace in pdcch-ConfigMulticast for DCI formats with CRC scrambled by G-RNTI or G-CS-RNTI, or

[0344] - for DCI format 4_0 with CRC scrambled by MCCH-RNTI or G-RNTI for broadcast, searchSpaceMCCH and searchSpaceMTCH on the secondary cell, and

[0345] -USS collection, which is configured by

[0346] -SearchSpace in PDCCH-Config with searchSpaceType=ue-Specific for DCI formats with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI, SL-RNTI, SL-CS-RNTI or SL semi-persistent scheduling V-RNTI

[0347] In the following, a DCI format with a CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI is also referred to as a unicast DCI format, a DCI format with a CRC scrambled by G-RNTI or G-CS-RNTI for multicast is also referred to as a multicast DCI format, and a DCI format with a CRC scrambled by MCCH-RNTI or G-RNTI for broadcast scheduling PDSCH reception is also referred to as a broadcast DCI format.

[0348] For DL ​​BWP, if the UE is not provided with searchSpaceSIB1 for Type0-PDCCH CSS set through PDCCH-ConfigCommon, the UE does not monitor PDCCH candidates of Type0-PDCCH CSS set on DL BWP. Type0-PDCCH CSS set is defined by the CCE aggregation level and the number of PDCCH candidates per CCE aggregation level given in Table 10.1-1.

[0349] If the active DL BWP and the initial DL BWP for the UE have the same SCS and the same CP length, and the active DL BWP contains all RBs of the CORESET with index 0, or the active DL BWP is the initial DL BWP, or the active DL BWP contains all RBs of MBS frequency resources provided by cfr-ConfigMCCH-MTCH as described in clause 18, the CORESET configured for Type0-PDCCH CSS set has CORESET index 0 and the Type0-PDCCH CSS set has search space set index 0.

[0350] If the active DL BWP and MBS frequency resources are determined by cfr-ConfigMCCH-MTCH for a UE with the same SCS and the same CP length, or by CORESET with index 0 when cfr-ConfigMCCH-MTCH is not provided and the active DL BWP contains all RBs of the MBS frequency resources, and if the UE is provided with searchSpaceMCCH or searchSpaceMTCH for a Type0B-PDCCH CSS set on the primary cell or a Type3-PDCCH CSS set on the secondary cell, the UE monitors the PDCCH to detect the broadcast DCI format on the active DL BWP as described in clause 18.

[0351] For DL ​​BWP, if the UE is not provided with searchSpaceOtherSystemInformation for Type0A-PDCCH CSS set, the UE does not monitor PDCCH for Type0A-PDCCH CSS set on DL BWP. The CCE aggregation level and the number of PDCCH candidates per CCE aggregation level for Type0A-PDCCH CSS set are given in Table 10.1-1.

[0352] For DL ​​BWP, if the UE is not provided with ra-SearchSpace for Type1-PDCCH CSS set, the UE does not monitor PDCCH for Type1-PDCCH CSS set on DL BWP. If the UE has not been provided with Type3-PDCCH CSS set or Type1A-PDCCH CSS set or USS set, and the UE has received C-RNTI and Type1-PDCCH CSS set has been provided, the UE monitors PDCCH candidates for DCI format 0_0 and DCI format 1_0 with CRC scrambled by C-RNTI in Type1-PDCCH CSS set.

[0353] If the UE is not provided with pagingSearchSpace for Type2-PDCCH CSS set, the UE does not monitor PDCCH for Type2-PDCCH CSS set on DL BWP.The CCE aggregation level and the number of PDCCH candidates per CCE aggregation level for Type2-PDCCH CSS set are given in Table 10.1-1.

[0354] If the UE is not provided with pei-SearchSpace for a Type2A-PDCCH CSS set, the UE does not monitor PDCCH for a Type2A-PDCCH CSS set on the DL BWP. The CCE aggregation level for the Type2A-PDCCH CSS set and the number of PDCCH candidates per CCE aggregation level are given in Table 10.1-1. If the UE is provided with pei-SearchSpace with a value of zero for the Type2A-PDCCH CSS set index, and for SS / PBCH blocks and CORESET multiplexing modes 2 and 3, the UE determines the PDCCH monitoring occasions as described in clause 13, and the CCE aggregation level for the Type2A-PDCCH CSS set and the number of PDCCH candidates per CCE aggregation level are given in Table 10.1-1.

[0355] If the UE is provided with a zero value for searchSpaceID in PDCCH-ConfigCommon for a Type0 / 0A / 2-PDCCH CSS set, or is provided with a zero value for searchSpaceMCCH or searchSpaceMTCH, the UE determines the monitoring occasions for PDCCH candidates for a Type0 / 0A / 2-PDCCH CSS set as described in clause 13, and the UE is provided with a C-RNTI, the UE monitors the PDCCH candidates only at monitoring occasions associated with an SS / PBCH block, where the SS / PBCH block is determined by the most recent of the following:

[0356] - a MAC CE activation command indicating the TCI-State of the active BWP containing the CORESET with index 0, as described in [6, TS 38.214], where the TCI-State contains a CSI-RS that is quasi-co-located with a SS / PBCH block, or

[0357] - A random access procedure not initiated by a PDCCH command that triggers a contention-free random access procedure

[0358] If the UE monitors whether the PDCCH candidates have a DCI format with a CRC scrambled by C-RNTI, and the UE is provided with a non-zero value of searchSpaceID in PDCCH-ConfigCommon for Type0 / 0A / 2-PDCCH CSS set, or monitors whether the PDCCH candidates have a DCI format with a CRC scrambled by MCCH-RNTI or G-RNTI for broadcast, and the UE is provided with non-zero values ​​of searchSpaceMCCH and searchSpaceMTCH in PDCCH-ConfigCommon for Type0 / 0B-PDCCH CSS set, the UE determines the monitoring timing of the PDCCH candidates of the Type0 / 0A / 2-PDCCH CSS set or the Type0 / 0B-PDCCH set, respectively, based on the search space set associated with the value of searchSpaceID.

[0359] If the UE is not provided with a TCI state indicating quasi-co-location information of the DM-RS antenna ports for PDCCH reception in the CORESET, the UE may assume that the DM-RS antenna ports associated with PDCCH reception in the CORESET configured by pdcch-ConfigSIB1 in the MIB, the DM-RS antenna ports associated with the corresponding PDSCH reception, and the corresponding SS / PBCH blocks are quasi-co-located with respect to average gain, quasi-co-location 'Type A' and 'Type D' properties (where applicable [6, TS 38.214]). The value of the DM-RS scrambling sequence initialization is the cell ID. For operation without shared spectrum channel access in FR1 and FR2-1, the SCS is provided by subCarrierSpacingCommon in the MIB. For operation with shared spectrum channel access in FR1 and for operation in FR2-2, the SCS is the same as the SCS of the corresponding SS / PBCH block.

[0360] For single cell operation or for operation with carrier aggregation in the same frequency band, if the DM-RS used for monitoring PDCCH in Type1-PDCCH CSS set is not configured with the same qcl-Type set to 'Type D' property as the DM-RS used for monitoring PDCCH in Type0 / 0A / 0B / 2 / 3-PDCCH CSS set or USS set [6, TS 38.214], and if the PDCCH or the associated PDSCH overlaps with the PDCCH monitored by the UE in Type1-PDCCH CSS set or with the associated PDSCH in at least one symbol, the UE is expected not to monitor the PDCCH in Type0 / 0A / 0B / 2 / 3-PDCCH CSS set or USS set.

[0361] If the UE is provided

[0362] - one or more search space sets corresponding to one or more of searchSpaceZero, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace, and

[0363] -C-RNTI, MCS-C-RNTI or CS-RNTI

[0364] The UE monitors whether the PDCCH candidates have DCI format 0_0 and DCI format 1_0 with CRC scrambled by C-RNTI, MCS-C-RNTI or CS-RNTI in the one or more search space sets in the time slot, and in the time slot the UE monitors whether the PDCCH candidates have at least DCI format 0_0 or DCI format 1_0 with CRC scrambled by SI-RNTI, RA-RNTI, MsgB-RNTI or P-RNTI.

[0365] If the UE is provided

[0366] - one or more search space sets corresponding to one or more of searchSpaceZero, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, pei-SearchSpace, ra-SearchSpace, or the CSS set of PDCCH-Config, and

[0367] -SI-RNTI, P-RNTI, PEI-RNTI, RA-RNTI, MsgB-RNTI, SFI-RNTI, INT-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI

[0368] Then, for an RNTI from any of these RNTIs, the UE is not expected to process information from more than one DCI format with RNTI-scrambled CRC per slot.

[0369] Table 10.1-1: CCE aggregation levels and maximum number of PDCCH candidates per CCE aggregation level for CSS sets configured by searchSpaceSIB1

[0370] CCE aggregation level ●Number of candidates 4 4 ★8 ★2 16 1

[0371] For each DL BWP configured for the UE in the serving cell, the UE may be provided by higher layer signaling with

[0372] -P ≤ 3 CORESETs, provided that coresetPoolIndex is not provided, or if coresetPoolIndex is provided, the value of coresetPoolIndex is the same for all CORESETs

[0373] -P ≤ 5 CORESETs, provided that coresetPoolIndex is not provided for the first CORESET, or is provided for the first CORESET and has the value 0, and is provided for the second CORESET and has the value 1

[0374] For each CORESET, the ControlResourceSet provides the UE with the following:

[0375] - either by controlResourceSetId or by the CORESET index p of controlResourceSetId-v1610, where

[0376] - 0 < p < 12, provided that coresetPoolIndex is not provided, or if coresetPoolIndex is provided, the value of coresetPoolIndex is the same for all CORESETs;

[0377] - 0 < p < 16, if coresetPoolIndex is not provided for the first CORESET, or is provided for the first CORESET and has the value 0, and is provided for the second CORESET and has the value 1;

[0378] - the initialization value of the DM-RS scrambling sequence provided by pdcch-DMRS-ScramblingID;

[0379] - the precoder granularity for several REGs in the frequency domain provided by precoderGranularity, where the UE may assume the use of the same DM-RS precoder;

[0380] - the number of consecutive symbols provided by duration;

[0381] - the set of resource blocks provided by frequencyDomainResources;

[0382] - the CCE to REG mapping parameter provided by cce-REG-MappingType;

[0383] -Antenna port quasi co-location from a set of antenna port quasi co-locations provided by TCI-State, which indicates the quasi co-location information of the DM-RS antenna port for PDCCH reception;

[0384] - Indication of the presence or absence of the Transmission Configuration Indication (TCI) field for DCI formats other than DCI format 1_0 that schedule PDSCH reception or have associated HARQ-ACK information without scheduled PDSCH and provided by PDCCH in CORESETp through tci-PresentInDCI or tci-PresentDCI-1-2.

[0385] When precoderGranularity = allContiguousRBs, the UE does not expect

[0386] - A resource block set configured as a CORESET containing more than four resource block subsets that are not contiguous in frequency

[0387] - Any RE of CORESET overlaps with any RE determined from lte-CRS-ToMatchAround or from LTE-CRS-PatternList or with any RE of SS / PBCH block.

[0388] If the UE is provided with two TCI states indicating quasi co-location information of DM-RS antenna ports for PDCCH reception in a CORESET associated with a Type3-PDCCH CSS set, the UE may assume the quasi co-location information indicated in both of the two TCI states for PDCCH reception in the CORESET.

[0389] For each CORESET in the DL BWP of the serving cell, the corresponding frequencyDomainResources provides a bitmap

[0390] - If CORESET is not associated with any search space set configured with freqMonitorLocations, then the search space set with the starting common RB location is used. of The bits of the bitmap have a one-to-one mapping with non-overlapping groups of 6 consecutive PRBs, wherein if rb-Offset is not provided, the first common RB of the first group of 6 PRBs has a common RB index Or the first common RB of the first group of 6 PRBs has a common RB index in Provided by rb-Offset.

[0391] - If CORESET is associated with at least one search space set configured with freqMonitorLocations, then [6, TS 38.214] The ascending order of the PRB index in each RB set k in the DL BWP bandwidth of RPBs, the first The bits have a one-to-one mapping with non-overlapping groups of 6 consecutive PRBs, where the first common RB of the first group of 6 PRBs has a common RB index And k is indicated by freqMonitorLocations if provided for a search space set, otherwise, k=0. is the number of available PRBs in RB set 0 for DL ​​BWP, and provided by rb-Offset, or if rb-Offset is not provided, then If the UE is provided with the RB set in the DL BWP, the UE expects the RBs of the CORESET to be within the union of the PRBs in the RB set of the DL BWP.

[0392] For a CORESET other than the one with index 0,

[0393] - if the UE has not been provided with configuration of TCI states via tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList for the CORESET, or has been provided with initial configuration of more than one TCI states for the CORESET via tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList but has not received a MAC CE activation command for one of the TCI states as described in [11, TS 38.321], the UE assumes that the DM-RS antenna ports associated with PDCCH reception are quasi-co-located with the SS / PBCH blocks identified by the UE during the initial access procedure, or for the most recently configured granted PUSCH transmission as described in clause 19 for the same HARQ process;

[0394] - If the UE has been provided with the configuration of more than one TCI states via tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList for CORESET as part of the reconfiguration with synchronization procedure as described in [12, TS 38.331], but has not yet received a MAC CE activation command for one of the TCI states as described in [11, TS 38.321], then the UE assumes that the DM-RS antenna port associated with PDCCH reception is quasi-co-located with the SS / PBCH blocks or CSI-RS resources identified by the UE during the random access procedure initiated by the reconfiguration with synchronization procedure as described in [12, TS 38.331].

[0395] For the CORESET with index 0,

[0396] - If the UE is provided with a TCI-State and if followUnifiedTCI-State = 'enabled' for a CORESET, the UE assumes that the DM-RS antenna ports used for PDCCH reception in the CORESET and the DM-RS antenna ports used for PDSCH reception scheduled by the DCI format provided by the PDCCH reception in the CORESET are quasi-co-located with the reference signals provided by the indicated TCI-State [6, TS 38.214]

[0397] - otherwise, the UE assumes that the DM-RS antenna ports used for PDCCH reception in the CORESET are quasi co-located with - said one or more DL RSs configured by TCI state indicated by the MAC CE activation command for the CORESET (if present), or

[0398] - If no MAC CE Activation Command indicating the TCI state for the CORESET was received after the last random access procedure, then the SS / PBCH blocks identified by the UE during the last random access procedure not initiated by a PDCCH command triggering a contention-free random access procedure, or the SS / PBCH blocks identified by the UE during the last configured grant for PUSCH transmission as described in clause 19.

[0399] For a CORESET other than the CORESET with index 0, if the UE is provided with a single TCI state for the CORESET, or if the UE receives a MAC CE activation command providing one or both of the TCI states for the CORESET, then the UE assumes that the DM-RS antenna ports associated with PDCCH reception in the CORESET are quasi-co-located with the one or more DL RS configured by the TCI state. For the CORESET with index 0, the UE expects that the CSI-RS configured with qcl-Type set to 'Type D' in the TCI state indicated by the MAC CE activation command for the CORESET is provided by the SS / PBCH block

[0400] - If the UE receives a MAC CE activation command for one of the TCI states, the UE The activation command is applied in the first time slot after k, where k is the time slot in which the UE shall transmit the PUCCH with the HARQ-ACK information of the PDSCH providing the activation command, μ is the SCS configuration of the PUCCH in the time slot when the activation command is applied, and k mac is the number of time slots for SCS configuration μ=0 provided by kmac, or k if kmac is not provided mac =0.

[0401] If the UE is provided with a TCI-State in dl-OrJointTCI-StateList, then only the DM-RS antenna ports for PDCCH reception in the CORESET other than the CORESET with index 0 associated with the USS set and / or Type3-PDCCH CSS set and the DM-RS antenna ports in the CORESET for PDSCH reception scheduled by the DCI format provided by PDCCH reception are quasi-co-located with the reference signal provided by the indicated TCI-State [6, TS 38.214].

[0402] If the UE is provided with followUnifiedTCI-State for a CORESET other than the CORESET with index 0 that is associated with at least a CSS set other than the Type3-PDCCH CSS set, and if followUnifiedTCI-State is set to enabled, then the DM-RS antenna ports in the CORESET used for PDCCH reception and the DM-RS antenna ports in the CORESET used for PDSCH reception scheduled by the DCI format provided by the PDCCH reception are quasi-co-located with the reference signal provided by the indicated TCI-State.

[0403] If the UE is provided with up to two lists of cells with simultaneous TCI states activated via simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2, the UE applies the quasi-co-location of the antenna ports provided by one or two TCI-States, each having the same activated tci-StateID value, to the CORESET with the same index in all configured DL BWPs of all configured cells in the list determined from the serving cell index, where one or two tci-StateIDs, CORESET index and serving cell index are provided by the MAC CE command.

[0404] For each DL BWP configured for the UE in the serving cell, the UE is provided with S≤10 search space sets by higher layers, where for each of the S search space sets, the UE is provided with the following via SearchSpace:

[0405] -Search space collection index s by searchSpaceId, 0 <s<40

[0406] - Association between search space set s and CORESETp via controlResourceSetId or via controlResourceSetId-v1610

[0407] -k via monitoringSlotPeriodicityAndOffset or via monitoringSlotPeriodicityAndOffset-r17 s The PDCCH monitoring periodicity and o s PDCCH monitoring offset of time slots

[0408] - PDCCH monitoring mode within a slot via monitoringSymbolsWithinSlot, which indicates the first symbol of the CORESET used for PDCCH monitoring within each slot where the UE monitors PDCCH

[0409] - Duration T s <k s , which indicates the number of time slots in which the search space set s exists through duration, or the number of time slots in a continuous time slot group in which the search space set s may exist through duration-r17

[0410] - A bitmap via monitoringSlotsWithinSlotGroup, which applies per group of slots and provides a PDCCH monitoring pattern indicating the slots in the slot group used for PDCCH monitoring

[0411] - The size of the slot group is the same as the size of monitoringSlotsWithinSlotGroup

[0412] - For a Type 1-PDCCH CSS set provided by the ra-SearchSpace in the dedicated RRC signaling, or for a Type 3-PDCCH CSS set, or for a USS set, the PDCCH monitoring mode indicates only consecutive slots in the slot group used for PDCCH monitoring, and for at least one combination indicated by the UE as capable (X s , Y s ), the number of consecutive time slots is not greater than Y s

[0413] - For the Type1-PDCCH CSS set provided by ra-SearchSpace in SIB1, the PDCCH monitoring mode indicates only at most 1 slot in the slot group used for PDCCH monitoring

[0414] - For Type0-PDCCH CSS set or for Type0A-PDCCH CSS set or for Type2-PDCCH CSS set, the PDCCH monitoring mode indicates the slots in the slot group used for PDCCH monitoring, and the slots are not restricted to be consecutive, and the number of those slots is not greater than the size of monitoringSlotsWithinSlotGroup

[0415] - Provide several PDCCH candidates per CCE aggregation level L through aggregationLevel1, aggregationLevel2, aggregationLevel4, aggregationLevel8 and aggregationLevel16 for CCE aggregation level 1, CCE aggregation level 2, CCE aggregation level 4, CCE aggregation level 8 and CCE aggregation level 16 respectively

[0416] - The search space set s is an indication of the CSS set or USS set set by searchSpaceType

[0417] - If the search space set s is a CSS set

[0418] -Indication provided by dci-Format0-0-AndFormat1-0 for monitoring PDCCH candidates for DCI format 0_0 and DCI format 1_0

[0419] - An indication provided by dci-Format2-0 to monitor one or two PDCCH candidates for DCI format 2_0 and corresponding CCE aggregation level, or one PDCCH candidate per RB set when the UE is provided with freqMonitorLocations for the search space set

[0420] -Indication provided by dci-Format2-1 for monitoring PDCCH candidates for DCI format 2_1

[0421] -Indication provided by dci-Format2-2 for monitoring PDCCH candidates for DCI format 2_2

[0422] -Indication provided by dci-Format2-3 for monitoring PDCCH candidates for DCI format 2_3

[0423] -Indication provided by dci-Format2-4 for monitoring PDCCH candidates for DCI format 2_4

[0424] -Indication provided by dci-Format2-6 for monitoring PDCCH candidates for DCI format 2_6

[0425] -Indication provided by dci-Format4-0 for monitoring PDCCH candidates for DCI format 4_0

[0426] - Indication provided by dci-Format4-1 or dci-Format4-2 or dci-Format4-1-AndFormat4-2 to monitor PDCCH candidates for DCI format 4_1 or DCI format 4_2 or both DCI format 4_1 and DCI format 4_2, respectively

[0427] - an indication that the search space set s provided by searchSpaceLinkingId is linked to another search space set provided with the same value of searchSpaceLinkingId

[0428] - If the search space set s is a USS set, the indication provided by dci-Formats to monitor PDCCH candidates for DCI format 0_0 and DCI format 1_0 or for DCI format 0_1 ​​and DCI format 1_1, or the indication provided by dci-FormatsExt to monitor PDCCH candidates for DCI format 0_2 and DCI format 1_2 or for DCI format 0_1, DCI format 1_1, DCI format 0_2, and DCI format 1_2, or the indication provided by dci-FormatsSL to monitor PDCCH candidates for DCI format 0_0 and DCI format 1_0 or for DCI format 0_1 ​​and DCI format 1_1 or for DCI format 3_0 or for DCI format 3_1 or for DCI format 3_0 and DCI format 3_1

[0429] - A bitmap provided by freqMonitorLocations (if provided) to indicate the index of one or more RB sets for search space set s, where the MSB k in the bitmap corresponds to RB set k-1 in the DL BWP. For RB set k indicated in the bitmap, the first PRB in the frequency domain monitoring locations within the RB set is defined by Given, where is the index of the first common RB of RB set k [6, TS 38.214], and provided by rb-Offset, or if rb-Offset is not provided, then For each RB set with a corresponding value of 1 in the bitmap, the frequency domain resource allocation pattern for the monitoring location is based on the first RB in frequencyDomainResources provided by the associated CORESET configuration. Determined by the individual digits.

[0430] If monitoringSymbolsWithinSlot instructs the UE to monitor PDCCH in a subset of up to three consecutive symbols that are the same in each slot, where the UE monitors PDCCH for all search space sets, then the UE is not expected to be configured to use a PDCCH SCS other than 15 kHz if the subset contains at least one symbol after the third symbol.

[0431] The UE does not expect to be provided with the first symbol and several consecutive symbols of the CORESET resulting in PDCCH candidate mapping to symbols of different slots.

[0432] The UE does not expect any two PDCCH monitoring occasions on the active DL BWP in the same CORESET, for the same search space set or for different search space sets, separated by a non-zero number of symbols less than the CORESET duration.

[0433] The UE determines the PDCCH monitoring opportunities on the active DLBWP based on the PDCCH monitoring periodicity, PDCCH monitoring offset and PDCCH monitoring mode within the time slot. If monitoringSlotsWithinSlotGroup is not provided, the UE determines that the PDCCH monitoring opportunities exist in the slot with number n. f The frame has a number [4, TS 38.211], provided that UE from time slot Start monitoring for T s PDCCH candidates in the search space set s of consecutive time slots are not monitored for the next k s -T s PDCCH candidates for search space set s of consecutive time slots. If monitoringSlotsWithinSlotGroup is provided, then for search space set s, the UE determines the PDCCH candidates that satisfy The number n f The frame has a number [4, TS 38.211] The time slot is L s The first time slot in the first group of time slots, and the PDCCH monitoring opportunity exists in T starting from the first group s / L s consecutive time slot groups, where L s is the size of monitoringSlotsWithinSlotGroup. Initially, the UE monitors T according to monitoringSlotsWithinSlotGroup s / L a PDCCH candidates for the search space set s in each of the k consecutive time slot groups, and not monitoring the PDCCH candidates for the next k s -T s PDCCH candidates of the search space set s of consecutive time slots.

[0434] The USS at CCE aggregation level L∈{1, 2, 4, 8, 16} is defined by the PDCCH candidate set for CCE aggregation level L.

[0435] In [5] 3GPP TS 38.212, V17.5.0 (2023-03), the following is provided:

[0436] 7.3.1.1.1 Format 0_0

[0437] DCI format 0_0 is used to schedule PUSCH in one cell.

[0438] The following information is transmitted via DCI format 0_0, where the CRC is scrambled by the C-RNTI or CS-RNTI or MCS-C-RNTI:

[0439] - Identifier for DCI format - 1 bit

[0440] - The value of this bit field is always set to 0, indicating the UL DCI format

[0441] - Frequency domain resource assignment - The number of bits determined as follows:

[0442] - bit, provided that the higher layer parameters useInterlacePUCCH-PUSCH in BWP-UplinkCommon and useInterlacePUCCH-PUSCH in BWP-UplinkDedicated are not configured, where Defined in clause 7.3.1.0

[0443] - For PUSCH frequency hopping of resource allocation type 1:

[0444] - According to clause 6.3 of [6, TS 38.214], N UL_hop The MSB bits are used to indicate the frequency offset, where if the higher layer parameter frequencyHoppingOffsetLists contains two offset values, then N UL_hop = 1, if the higher layer parameter frequencyHoppingOffsetLists contains four offset values, then N UL_hop =2

[0445] - The frequency domain resource allocation is provided according to clause 6.1.2.2.2 of [6, TS 38.214]

[0446] - For non-PUSCH frequency hopping of resource allocation type 1:

[0447] - The frequency domain resource allocation is provided according to clause 6.1.2.2.2 of [6, TS 38.214]

[0448] - If any of the higher layer parameters useInterlacePUCCH-PUSCH in BWP-UplinkCommon and useInterlacePUCCH-PUSCH in BWP-UplinkDedicated is configured - If the subcarrier spacing for the active UL bandwidth part is 30 kHz, the 5+Y bits provide the frequency domain resource allocation according to clause 6.1.2.2.3 of [6, TS 38.214].

[0449] - If the subcarrier spacing for the active UL bandwidth part is 15 kHz, the 6+Y bits provide the frequency domain resource allocation according to clause 6.1.2.2.3 of [6, TS 38.214].

[0450] If DCI format 0_0 is monitored in the UE-specific search space, the value of Y is given by Determine, among which is the number of RB sets contained in the active UL BWP, as defined in clause 7 of [6, TS38.214]. If DCI 0_0 is monitored in the common search space Y=0.

[0451] - Time domain resource assignment - 4 bits, as defined in clause 6.1.2.1 of [6, TS 38.214]

[0452] - Frequency Hopping Flag - 1 bit according to Table 7.3.1.1.1-3, as defined in clause 6.3 of [6, TS 38.214]

[0453] - Modulation and coding scheme - 5 bits, as defined in clause 6.1.4.1 of [6, TS 38.214]

[0454] - New data indicator - 1 bit

[0455] - Redundancy version - 2 bits, as defined in Table 7.3.1.1.1-2

[0456] -HARQ process number - 4 bits

[0457] - TPC command for scheduled PUSCH - 2 bits, as defined in clause 7.1.1 of [5, TS 38.213]

[0458] -ChannelAccess-CPext - 2 bits indicate the combination of channel access type and CP extension as defined in Table 7.3.1.1.1-4 or in Table 7.3.1.1.1-4A when channelAccessMode-r16 = 'semi-static' is provided for operation in a cell with shared spectrum channel access in frequency range 1; 2 bits indicate the channel access type as defined in Table 7.3.1.1.1-4B when ChannelAccessMode2-r17 is provided for operation in a cell in frequency range 2-2; otherwise, 0 bit.

[0459] -Fill in positions as needed

[0460] -UL / SUL indicator - 1 bit for UEs configured with supplementaryUplink in ServingCellConfig in a cell as defined in Table 7.3.1.1.1-1 and the number of bits of DCI format 1_0 before padding is greater than the number of bits of DCI format 0_0 before padding; otherwise 0 bit. The UL / SUL indicator (if present) is located in the last bit position of DCI format 0_0 after the padding bits.

[0461] - If the UL / SUL indicator is present in DCI format 0_0 and the higher-layer parameter pusch-Config is not configured on UL and SUL, the UE ignores the UL / SUL indicator field in DCI format 0_0 and the corresponding PUSCH scheduled by DCI format 0_0 is for the UL or SUL in which the higher-layer parameter pucch-Config is configured;

[0462] - If the UL / SUL indicator does not exist in DCI format 0_0 and pucch-Config is configured, the corresponding PUSCH scheduled by DCI format 0_0 is for UL or SUL in which the higher layer parameter pucch-Config is configured.

[0463] - If the UL / SUL indicator is not present in DCI format 0_0 and pucch-Config is not configured, the corresponding PUSCH scheduled by DCI format 0_0 is used for the uplink on which the latest PRACH is transmitted.

[0464] 7.3.1.2.1 Format 1_0

[0465] DCI format 1_0 is used for scheduling of PDSCH in one DL cell.

[0466] The following information is transmitted via DCI format 1_0, where the CRC is scrambled by the C-RNTI or CS-RNTI or MCS-C-RNTI:

[0467] - Identifier for DCI format - 1 bit

[0468] - The value of this bit field is always set to 1, indicating the DL DCI format

[0469] - Frequency Domain Resource Assignment - bits, of which Given by clause 7.3.1.0

[0470] If the CRC of DCI format 1_0 is scrambled by C-RNTI and the "Frequency Domain Resource Assignment" field is all ones, then DCI format 1_0 is used for random access procedure initiated by PDCCH order, with all remaining fields set as follows:

[0471] - Random Access Preamble Index - 6 bits, according to ra-PreambleIndex in clause 5.1.2 of [8, TS38.321]

[0472] -UL / SUL indicator - 1 bit. If the value of "Random Access Preamble Index" is not all zeros, and if the UE is configured to use supplementaryUplink in ServingCellConfig in the cell, then this field indicates which UL carrier in the cell transmits PRACH according to Table 7.3.1.1.1-1; otherwise, this field is reserved.

[0473] -SS / PBCH Index - 6 bits. If the value of "Random Access Preamble Index" is not all zeros, this field indicates the SS / PBCH that will be used to determine the RACH timing for PRACH transmission; otherwise, this field is reserved.

[0474] -PRACH Mask Index - 4 bits. If the value of "Random Access Preamble Index" is not all zeros, this field indicates the RACH opportunity associated with the SS / PBCH indicated by "SS / PBCH Index" for PRACH transmission according to clause 5.1.1 of [8, TS38.321]; otherwise, this field is reserved.

[0475] - Reserved bits - 12 bits for operation in a cell with shared spectrum channel access in frequency range 1 or when a DCI format is monitored in the common search space for operation in a cell in frequency range 2-2; otherwise 10 bits

[0476] Otherwise, set all remaining fields as follows:

[0477] - Time domain resource assignment - 4 bits, as defined in clause 5.1.2.1 of [6, TS 38.214]

[0478] - VRB to PRB mapping - 1 bit, according to Table 7.3.1.2.2-5

[0479] - Modulation and coding scheme - 5 bits, as defined in clause 5.1.3 of [6, TS 38.214]

[0480] - New data indicator - 1 bit

[0481] - Redundancy version - 2 bits, as defined in Table 7.3.1.1.1-2

[0482] -HARQ process number - 4 bits

[0483] - Downlink Assignment Index - 2 bits, as defined in clause 9.1.3 of [5, TS 38.213], corresponding to DAI

[0484] - TPC command for scheduled PUCCH - 2 bits, as defined in clause 7.2.1 of [5, TS 38.213]

[0485] - PUCCH resource indicator - 3 bits, as defined in clause 9.2.3 of [5, TS 38.213]

[0486] -PDSCH-to-HARQ_feedback timing indicator - 3 bits, as defined in clause 9.2.3 of [5, TS38.213]

[0487] - ChannelAccess-CPext - 2 bits indicate the combination of channel access type and CP extension as defined in Table 7.3.1.1.1-4 or in Table 7.3.1.1.1-4A if channelAccessMode-r16="semi-static" is provided for operation in cells with shared spectrum channel access in frequency range 1; 2 bits indicate the channel access type as defined in Table 7.3.1.1.1-4B if ChannelAccessMode2-r17 is provided for operation in cells in frequency range 2-2; otherwise 0 bits

[0488] - Reserved bits - 2 bits when a DCI format is monitored in a common search space for operation in a cell in frequency range 2-2 and the number of bits for the field 'ChannelAccess-CPext' is 0;

[0489] Otherwise, it is 0.

[0490] In the legacy new radio (NR), the physical random access channel (PRACH) can be triggered by a physical downlink control channel (PDCCH) command. Based on the random access (RA) procedure field being all zero or not zero, contention-free random access (CFRA) (e.g., not all zero) or contention-based random access (CBRA) (all zero). Since the user equipment (UE) selects the synchronization signal (SS) / physical broadcast channel (PBCH) for the CBRA triggered by the PDCCH command, the SS / PBCH field and the PRACH mask index field are both reserved. However, for CFRA triggered by the PDCCH command, the SS / PBCH field will indicate one SS / PBCH, and the PRACH opportunity associated with the one SS / PBCH can be determined. From the perspective of the dedicated random access channel (RACH) configuration, multiple reference signals (RS) (SS / PBCH or channel state information reference signal (CSI-RS)) can be configured, and each RS can be configured with at least one PRACH opportunity (and one preamble index).

[0491] In NR Rel-19, network vendors proposed to deploy only uplink (UL) transmission / reception points (TRPs) for enhanced coverage. Based on this enhanced deployment, downlink (DL) and UL can be associated with different TRPs, and with this deployment, the UE does not need to use too much transmit power to perform UL transmission. For example, for a UL-only TRP, such as Figure 7 As shown, TRP1 and TRP2 are both intra-cell TRPs (i.e., TRP1 and TRP2 are in the same serving cell), and the UE can receive DL from TRP1 (e.g., DL) while transmitting UL to TRP2 (e.g., UL2). TRP2 can act as a UL-only TRP. The UL-only TRP can act as a cost-reducing device. TRP1 and TRP2 can have a backhaul link for communication. In some cases, the UE may perform an initial access procedure on TRP1 including DL and UL1. The initial access procedure may include cell search, synchronization signal and broadcast channel reception, and / or a random access procedure. The UE may perform UL transmission associated with the random access procedure via TRP1. Alternatively, another approach is to use TRP2 to perform UL transmission associated with the random access procedure.

[0492] Considering that DL and UL are associated with different TRPs (in the same serving cell), issues related to UL transmission may need to be addressed. More specifically, timing alignment (including downlink reference timing, and / or initial timing advance (TA) value acquisition), UL transmission power (including open loop power control, closed loop power control and / or path loss RS determination), beams for PRACH to / for UL TRP only.

[0493] In a first example, according to current signaling for a PDCCH command (e.g., downlink control information (DCI) format 1_0), a bit field in the signaling includes a random access preamble index, a UL / supplementary uplink (SUL) indicator, an SS / PBCH index, and a PRACH mask index. The beam used for the PRACH according to the PDCCH command is determined based on the SS / PBCH index, however, there is no DL functionality for a UL-only TRP (i.e., a UL-only TRP does not support DL functionality, including transmitting SS / PBCH).

[0494] In addition, two TA scenarios are proposed not only in using multi-DCI (mDCI) multi-TRP (mTRP) but also in using single DCI (sDCI) mTRP.

[0495] concept

[0496] The concept is to change the beam or associated RS used for PRACH transmission (in the cell) triggered by a PDCCH command (received in the cell) from "SS / PBCH" to "UL RS". The UL RS can be a demodulation reference signal (DMRS), a phase tracking reference signal (PTRS) or a sounding reference signal (SRS). Alternatively, the UL RS should be an SRS. A distinction between this new kind of beam (e.g., SRS) and the traditional kind of beam (e.g., SS / PBCH) may be needed for PRACH transmission triggered by a PDCCH command. Whether the RS field in the PDCCH command is determined / interpreted as "SS / PBCH" or "SRS" is based on which TRP (of the cell) the PDCCH command is associated with (e.g., to which TRP the PRACH will be transmitted). The detailed distinction between PDCCH commands for different TRPs is based on the following content.

[0497] Explicit signaling differentiation can be based on a specific (new) field in the PDCCH order. When this new specific (new) field is set to a first value (e.g., 0), the PDCCH order corresponds to a TRP providing a DL signal (or the beam or associated RS used for the PDCCH order is "SS / PBCH"). When this new specific (new) field is set to a second value (e.g., 1), the PDCCH order corresponds to a UL-only TRP (or the beam or associated RS used for the PDCCH order is "UL RS"). The random access preamble index field in the PDCCH order is not (allowed to) be set to all zeros (e.g., the PDCCH order indicates CFRA) (e.g., if the new specific (new) field is set to 1). When this new specific (new) field is set to a first value, the UE determines the PRACH resources and / or the beam or associated RS used for PRACH via the first dedicated RACH configuration. When this specific (new) field is set to a second value, the UE determines the PRACH resources and / or the beam or associated RS for the PRACH via the second dedicated RACH configuration.

[0498] The first dedicated RACH configuration corresponds to a PRACH resource associated with SS / PBCH or CSI-RS. The first dedicated RACH configuration is associated with a TRP providing a DL signal. The following text using legacy RRC parameters may be the first dedicated RACH configuration.

[0499]

[0500]

[0501] The second dedicated RACH configuration corresponds to a PRACH resource associated with an SRS or UL RS. The second dedicated RACH configuration is associated with only a UL TRP. The second dedicated RACH configuration may contain associated one or more SRS or UL RS. The second dedicated RACH configuration may contain a PRACH opportunity associated with an SRS or UL RS indicated in the second dedicated RACH configuration. The second dedicated RACH configuration may contain a PRACH preamble index associated with an SRS or UL RS indicated in the second dedicated RACH configuration. The following text using legacy radio resource control (RRC) parameters may be a second dedicated RACH configuration (bold and underlined text added).

[0502]

[0503] Based on the specific (new) field, the UE determines to transmit the PRACH based on the first dedicated RACH configuration or the second RACH configuration.

[0504] A specific (new) field may be set / placed earlier than the "RS field" in the PDCCH order. The RS field corresponds to the "SS / PBCH field" or the "SRS field". The new specific (new) field may be set / placed earlier than the "random access preamble index" field. Alternatively, the specific (new) field may be set / placed later than the "random access preamble index" field (but earlier than the "RS field"). When this specific (new) field is set to a first value, the "RS field" is interpreted / determined as the "SS / PBCH" index, and / or the RS field is interpreted / determined as the SS / PBCH field. When this specific (new) field is set to a second value, the "RS field" is interpreted / determined as the "SRS resource" index, and / or the RS field is interpreted / determined as the SRS field. The SRS field indicates an SRS resource index among an SRS resource set. The SRS resource set may be configured or dynamically indicated. Preferably, in some embodiments, the SRS field indicates an SRS resource among multiple SRS resources. Alternatively, when this specific (new) field is set to a first value, the "RS field" is interpreted / determined as an "SS / PBCH" index, and / or the RS field is interpreted / determined as an SS / PBCH field. When this specific (new) field is set to a second value, the "RS field" is interpreted / determined as an "SRS resource set" index and an "SRS resource" index, and / or the RS field is interpreted / determined as an SRS field. This alternative provides additional flexibility for the network node to indicate both an SRS resource set and an SRS resource (within the indicated SRS resource set).

[0505] Preferably, in some embodiments the size of a particular (new) field is one bit and / or a bit-field.

[0506] Preferably, in certain embodiments, whether (the DCI format of) a PDCCH order contains a specific (new) field may be based on RRC configuration and / or configured by a network node.

[0507] Alternatively, the explicit signaling distinction may be based on (whether there is) a second specific (new) field (in the PDCCH order) that directly indicates the SRS resources. The size of the second specific (new) field may be based on the number of SRS resources among multiple SRS resources (e.g., particularly in a RACH dedicated configuration). Preferably, in some embodiments, the size of the second specific (new) field may be further based on a reserved code point for distinction. In this way, a dedicated RACH configuration using SRS may not include parameters for configuring the PRACH timing (e.g., without ra-OccasionList). The SS / PBCH field in the PDCCH command will indicate the PRACH timing associated with this SS / PBCH. The UE transmits PRACH on the PRACH timing using a spatial filter based on the SRS according to the second specific (new) field. Preferably, in some embodiments, the size of the second specific (new) field is more than one bit. Since the second specific (new) field uses reserved bits set to zero, the code point of the second specific (new) field of all zeros corresponds to a PDCCH command for a TRP for providing DL signaling (e.g., or corresponds to a TRP with an RS for a PDCCH command as "SS / PBCH"). On the other hand, the code point of the second specific (new) field that is not all zeros corresponds to a PDCCH for a UL-only TRP (e.g., or corresponds to a TRP with an RS for a PDCCH command as "UL RS"). Preferably, in some embodiments, the code point 1 of the second specific (new) field corresponds to an SRS resource identity (ID) = 0 or the lowest SRS resource or the lowest entry in the SRS resource set.

[0508] Implicit signaling differentiation can be based on a specific control resource set (CORESET) / search space that carries / delivers the PDCCH command. More specifically, a PDCCH command carried / delivered by a specific CORESET / search space corresponds to a PDCCH command for a UL-only TRP. A PDCCH command not carried / delivered by a specific CORESET / search space corresponds to a PDCCH command for a TRP that provides a DL signal. Preferably, in some embodiments, the specific CORESET / search space is configured by a network node. Based on which CORESET / search space carries / delivers the PDCCH command, the UE can determine that the SS / PBCH field (or RS field) in the PDCCH command is determined / interpreted as an SS / PBCH field, or an SRS resource field. Based on which CORESET / search space carries / delivers the PDCCH command, the UE can determine that the SS / PBCH field (or RS field) is determined / interpreted as an SS / PBCH field, or an SRS resource set and an SRS resource field. Based on which CORESET / search space carries / delivers the PDCCH command, the UE can determine which TRP the PDCCH command is associated with. More specifically, based on which CORESET / search space carries / delivers the PDCCH command, the UE can determine which beam the PRACH transmission is based on or is associated with the SS / PBCH or SRS. Preferably, in some embodiments, a specific CORESET / search space is associated with a specific SRS resource set. Preferably, in some embodiments, the SRS resource indicated by the SRS field in the PDCCH command is among the specific SRS resource set. Preferably, in some embodiments, the specific CORESET / search space is not a beam failure recovery (BFR) CORESET or BFR search space (SS). Preferably, in some embodiments, the UE can monitor the specific CORESET / search space (even) when a beam failure does not occur. Preferably, in some embodiments, in addition to the PDCCH that schedules the PDCCH command, the specific CORESET / search space may also include a PDCCH that schedules UL transmissions. Preferably, in some embodiments, the UE does not expect the specific CORESET / search space to not follow the unified transmission configuration indicator (TCI) state. The UE monitors a specific CORESET / search space based on the TCI state activated in the TCI state (de)activation media access control (MAC) control element (CE) for a specific CORESET / search space (which does not follow the beam indication DCI or beam indication MAC CE). Preferably, in some embodiments, the beam indication or beam indication MAC CE is used for UE-specific DL channel / signal reception and / or UE-specific channel / signal transmission. Preferably, in some embodiments, the beam indication MAC CE and the MAC CE for a specific CORESET / search space correspond to different MAC CEs.Alternatively, a specific CORESET is configured to follow the 2nd TCI state. Alternatively, a specific CORESET is configured to follow the 1st and 2nd TCI states (eg, PDCCH in a single frequency network (SFN)). Preferably, in some embodiments,. Figure 7 The PDCCH in the SFN in the scenario may correspond to the CORESET with this configuration, but the UE actually receives the PDCCH in TRP1.

[0509] Alternatively, the implicit signaling distinction may be based on a specific CORESET / search space that carries / delivers the PDCCH command, and the specific CORESET / search space is used to deliver the PDCCH command for providing a TRP for DL ​​signals. A PDCCH command carried / delivered by a specific CORESET / search space corresponds to a TRP that provides DL signals. A PDCCH command carried / delivered by a CORESET / search space other than the specific CORESET / search space corresponds to a UL-only TRP.

[0510] The implicit signaling distinction may be based on whether the CORESET delivering / including / providing the PDCCH command is configured to follow or not follow the 1st TCI state. Preferably, in some embodiments, the PDCCH command received in the CORESET following the 1st TCI state corresponds to the TRP providing the DL signal (e.g., Figure 7 Preferably, in some embodiments, a PDCCH command received in a CORESET that does not follow the 1st TCI state (e.g., follows both, does not follow, follows the 2nd) corresponds to a PDCCH command associated with a UL-only TRP (e.g., Figure 7Preferably, in some embodiments, when the first CORESET is configured to follow the 1st TCI state, the UE will apply the 1st TCI state in the code point of the beam indication MAC CE (e.g., the unified TCI state (de)activation MAC CE) to monitor the first CORESET. Preferably, in some embodiments, when there are more than one code point in the beam indication MAC CE, the code point of the beam indication MAC CE is indicated by the beam indication DCI (which indicates a different code point from the previous beam indication DCI). Preferably, in some embodiments, when there is only one code point in the beam indication MAC CE, the code point of the beam indication MAC CE is the only code point. Preferably, in some embodiments, the second CORESET is configured to follow the 2nd TCI state. The UE monitors the second CORESET via the 2nd TCI state. In this UL-only TRP scenario, the UE expects the 1st TCI state and the 2nd TCI state (as code points of the beam indication MAC CE) to correspond to the same TCI state (e.g., TCI state ID). When the UE receives a beam indication MAC CE including at least one code point having the 1st TCI state and the 2nd TCI state corresponding to the same TCI state ID, the UE considers the UL-only TRP scenario to be determined as multi-TRP operation. Preferably, in some embodiments, the DL functionality of the UL-only TRP is muted and / or the UE does not expect to receive DL signals from the UL-only TRP.

[0511] The implicit signaling distinction can be based on the time pattern or even / odd time slots. More specifically, the PDCCH command received in the odd time slot corresponds to the PDCCH command for the UL-only TRP. The PDCCH command received in the even time slot corresponds to the PDCCH command for the TRP providing the DL signal. Alternatively, the PDCCH command received in the odd time slot corresponds to the TRP providing the DL signal, while the PDCCH command received in the even time slot corresponds to the PDCCH command for the UL-only TRP. Preferably, in some embodiments, the time slot can be replaced by a transmission time interval (TTI).

[0512] Implicit signaling differentiation can be based on whether a UL-only TRP is being added or operating in a mode with communications with a UL-only TRP. When the UE determines or signals to use a UL-only TRP or performs an UL transmission to a UL-only TRP (and receives DL in another TRP), the PDCCH command is determined to be associated with the UL-only TRP. When the UE determines not to use a UL-only TRP or does not signal to use a UL-only TRP or performs an UL transmission to the same TRP as the received DL, the PDCCH command is determined to be associated with the TRP providing the DL signal. Prior to adding the UE or operating in a mode with communications with a UL-only TRP, the UE determines that the PDCCH command is associated with the TRP used to provide the DL signal.

[0513] Implicit signaling differentiation can be based on the DCI format used for PDCCH commands associated with only UL TRPs or PDCCH commands associated with TRPs that provide DL signals. For a first search space configured with a DCI format for monitoring associated with only UL TRPs, a PDCCH command monitored in the first search space is associated with only UL TRPs and / or a PRACH transmission in response to a PDCCH command is associated with only UL TRPs. For a second search space configured with a DCI format for monitoring associated with TRPs that provide DL signals, a PDCCH command monitored in the second search space is associated with a TRP that provides DL signals and / or a PRACH transmission in response to a PDCCH command is associated with a TRP that provides DL signals. The DCI format for scheduling PRACH transmissions associated with a TRP that provides DL signals may be DCI format 1_0. The DCI format for scheduling PRACH transmissions associated with only UL TRPs may not be DCI format 1_0. The DCI format used to schedule PRACH transmission associated with only UL TRP can be DCI format 1_x, or DCI format 0_x, or DCI format 0_0. For example, there is one condition check for DCI format 0_0, which indicates that the PDCCH command frequency domain resource assignment field in DCI format 0_0 is all ones.

[0514] The following is example text (bold and underlined):

[0515] If the CRC of DCI format 0_0 is scrambled by C-RNTI and the "frequency domain resource assignment" field is all ones, then the DCI format Formula 0_0 is used for the random access procedure initiated by the PDCCH order, where all other fields are set as follows:

[0516] - Random Access Preamble Index - 6 bits, according to clause 5.1.2 of [8, TS38.321] PreambleIndex.

[0517] -UL / SUL indicator - 1 bit. If the value of "Random Access Preamble Index" is not all zeros and if the UE is configured If supplementaryUplink in ServingCellConfig is used in the cell, this field is based on the table 7.3.1.1.1-1 indicates which UL carrier in the cell transmits the PRACH; otherwise, this field is reserved.

[0518] -SRS Index - 6 bits. If the value of "Random Access Preamble Index" is not all zeros, then this field indicates the The SRS or SS / PBCH associated with SRS is used to determine the RACH opportunity for PRACH transmission; otherwise, this field is reserved.

[0519] -PRACH Mask Index - 4 bits. If the value of "Random Access Preamble Index" is not all zeros, this field is According to clause 5.1.1 of [8, TS 38.321], the SRS associated with the SRS indicated by the "SRS index" for PRACH transmission is indicated. RACH opportunity; otherwise, this field is reserved.

[0520] - Reserved bit - For operation in a cell with shared spectrum channel access in frequency range 1 or when in use 12 bits when a DCI format is monitored in the common search space operating in a cell in frequency range 2-2; otherwise, 10 bits.

[0521] Implicit signaling differentiation can be based on applying the "TCI state" (field) to replace the "SS / PBCH index" field (in the PDCCH command). Preferably, in some embodiments, this method may require constructing an association between the TCI state and the dedicated RACH configuration (rather than the SS / PBCH index and the dedicated RACH configuration). Preferably, in some embodiments, based on the source RS of the TCI state indicated by the TCI state field in the PDCCH command, the UE can determine the dedicated PRACH configuration or PRACH timing. For example, when the source RS of the TCI state indicated by the TCI field in the PDCCH command corresponds to the SS / PBCH index x, the UE determines the PRACH timing associated with the dedicated PRACH configuration that provides the PRACH timing associated with the SS / PBCH index x. For another example, when the source RS of the TCI state indicated by the TCI field in the PDCCH command corresponds to the SRS index y, the UE determines the PRACH timing associated with the dedicated PRACH configuration that provides the PRACH timing associated with the SRS index y. Alternatively, when the source RS of the TCI state indicated by the TCI field in the PDCCH command corresponds to the SRS index y, the UE determines the PRACH opportunity associated with the dedicated PRACH configuration that provides the PRACH opportunity associated with the SS / PBCH associated with the SRS index y. Based on the TCI state indicated by the TCI field in the PDCCH command, the UE can determine the RACH opportunity (which can be further based on the configuration associated with the dedicated RACH configuration of the TCI state). Based on the source RS associated with the TCI state indicated by the TCI state field in the PDCCH command, the UE can determine whether the beam or spatial filter used for PRACH transmission is associated with the SRS or SS / PBCH (or CSI-RS). When the source RS associated with the TCI state indicated by the TCI state field in the PDCCH command corresponds to the SRS and preferably the SRS is associated with only the UL TRP (for example, using the 2nd TCI state), the UE determines that the PDCCH command is associated with only the UL TRP, and / or the UE determines the PRACH transmission in response to the PDCCH command being associated with the (indicated) TCI state. Based on the indication of the PDCCH order, the UE performs PRACH transmission via the spatial filter associated with the SS / PBCH, SRS, CSI-RS and / or TCI state.

[0522] A PDCCH command with "TCI Status" (field) may trigger a PRACH transmission to a UL-only TRP. A PDCCH command with "TCI Status" (field) may also trigger a PRACH transmission to a TRP providing a DL signal. Alternatively, a PDCCH command with "TCI Status" (field) may not (be allowed to) be used to trigger a PRACH transmission to a TRP providing a DL signal.

[0523] The following is an example of the association between TCI state and dedicated RACH configuration. Preferably, in certain embodiments, the TCI state corresponds to TCI-state or TCI-UL-State (bold and underlined).

[0524] ReferenceSignal (-r17) in qcl-info or TCI-UL-State (-r17) corresponds to the SS / PBCH index, CSI-RS index or SRS index.

[0525]

[0526]

[0527] Preferably, in some embodiments, the UE determines to use only UL TRP based on signaling. Preferably, in some embodiments, the signaling may be DCI, MAC CE or RRC. Preferably, in some embodiments, the signaling may indicate or imply that UL transmission is performed in only UL TRP. Preferably, in some embodiments, in response to the signaling, the UE may determine that the UL transmission will go to only UL TRP. More specifically, the signaling may be a beam indication MAC CE and / or a beam indication DCI. The beam indication MAC CE may include at least one code point having a 1st TCI state and a 2nd TCI state corresponding to the same TCI state. Preferably, in some embodiments, the 1st / 2nd TCI state corresponds to the DL TCI state. Alternatively, a detailed further extended beam indication MAC CE design may indicate the 1st joint TCI state with deactivated UL and / or the 2nd TCI state with deactivated DL. In one example, there are two octets in the MAC CE, wherein each bit in the first octet corresponds to the 1st TRP, and each bit in the second octet corresponds to the 2nd TRP. Preferably, in some embodiments, each bit in the first octet of the two octets indicates that one code point of the TCI field in the DCI corresponds to multiple or single TCI states for the 1st TRP. Preferably, in some embodiments, each bit in the second octet of the two octets indicates that one code point of the TCI field in the DCI corresponds to multiple or single TCI states for the 2nd TRP. For one bit in the first octet of the two octets indicating a single TCI state for one code point of the TCI field in the DCI, the code point indicates a single TCI state for the 1st TRP. Even for a joint TCI state, when one bit in the first octet of the two octets indicates a single TCI state, whether to use the DL / UL of the joint TCI state based on the DL / UL field in the same octet of the joint TCI state. When the DL / UL field in the same octet of the joint TCI state corresponds to DL, there is no UL functionality or the UL of the joint TCI state is deactivated or not activated. When the DL / UL field in the same octet of the joint TCI state corresponds to UL, there is no DL functionality or the DL of the joint TCI state is deactivated or not activated. Similar functionality is reused from each bit in the first octet of the two octets to each bit in the second octet of the two octets.

[0528] Preferably, in some embodiments, the dedicated RACH configuration may be extended. An example may be shown below (bold and underlined words correspond to the extended part). Preferably, in some embodiments, the UE may be configured with one or more dedicated RACH configurations. Preferably, in some embodiments, the PDCCH command triggering PRACH may correspond to a CFRA associated with SS / PBCH or SRS. Preferably, in some embodiments, the distinction between which dedicated PRACH configuration the PDCCH command is associated with may be determined based on the above-mentioned distinction method.

[0529]

[0530]

[0531]

[0532] Alternatively, take Figure 7As an example, when the UE is in an RRC connected state with TRP1, the UE may receive reconfiguration or signaling for information associated with TRP2. The reconfiguration or signaling for information may specify that the first one or more RACH opportunities are associated with SS / PBCH that is not associated with SRS, and the second one or more RACH opportunities are associated with SS / PBCH associated with SRS. The reconfiguration or signaling for information may provide an association between SS / PBCH and SRS. By this method, when the UE receives a PDCCH command (wherein the random access preamble is not all zero), the UE may determine whether the PDCCH command is associated with TRP1 or TRP2 based on whether the SS / PBCH indicated by the SS / PBCH index field is associated with SRS (or based on whether the PRACH opportunity is associated with SRS (SS / PBCH associated therewith)). When the SS / PBCH index field indicates a first SS / PBCH that is not associated with SRS, the UE determines that the PDCCH command is associated with TRP1 (e.g., a TRP providing a DL signal). When the SS / PBCH index field indicates a second SS / PBCH associated with the SRS, the UE determines that the PDCCH command is associated with TRP2 (e.g., UL TRP only). Preferably, in some embodiments, the distinction of which TRP the PDCCH command is associated with may be based on SS / PBCH separation. Preferably, in some embodiments, the SS / PBCH separation may be based on RRC, MAC CE and / or DCI signals. Preferably, in some embodiments, the above is a separation method, and an alternative separation may be based on indicating that the SS / PBCH is associated with TRP1 / TRP2. Alternatively, the separation method may be based on the SS / PBCH being associated with the 1st or 2nd TCI state in the code point in the beam indication MAC CE or in the beam indication DCI. Preferably, in some embodiments, the 1st TCI state may be associated with or implied by TRP1 (e.g., a TRP providing a DL signal). Preferably, in some embodiments, the 2nd TCI state may be associated with or implied by TRP2 (e.g., UL TRP only).

[0533] Preferably, in certain embodiments, throughout the present invention, a PDCCH command (received in a cell) indicates here either a CFRA towards a TRP providing DL signals (of the cell) or a CFRA towards a UL-only TRP.

[0534] See also Figure 8 , with respect to such and other concepts, systems and methods of the present invention, a method 1000 for a UE in a wireless communication system includes receiving a configuration of an uplink-only transmit / receive point from a network node and receiving a PDCCH command from the network node (step 1002), and performing a PRACH transmission in response to the PDCCH command (step 1004).

[0535] Preferably, in certain embodiments, the PDCCH order and the PRACH transmission are on the same serving cell.

[0536] Preferably, in certain embodiments, based on the serving cell for which the UE received the PDCCH order, the UE determines which serving cell the PRACH transmission is in response to.

[0537] Preferably, in some embodiments, the serving cell corresponds to a primary cell (PCell) or a secondary cell (SCell).

[0538] Preferably, in certain embodiments, the UE determines whether the PRACH transmission is associated with SRS or SS / PBCH based on a specific field in the PDCCH order.

[0539] Preferably, in certain embodiments, the UE determines PRACH transmission via a spatial filter associated with SRS or SS / PBCH based on a specific field.

[0540] Preferably, in some embodiments, the UE determines the PRACH opportunity associated with the SRS or SS / PBCH based on a specific field.

[0541] Preferably, in certain embodiments, when the UE receives parameters or signaling or (re)configuration associated with the specific field, the specific field is enabled or exists or is a valid bit field in the PDCCH order.

[0542] Preferably, in certain embodiments, before the UE receives parameters or signaling or (re)configuration associated with the specific field or when the UE does not receive parameters or signaling or (re)configuration associated with the specific field, the specific field is not enabled or does not exist or is not a valid bit field in the PDCCH command.

[0543] Preferably, in certain embodiments, the parameters or signaling or (re)configuration associated with a specific field corresponds to a UL TRP only.

[0544] Preferably, in certain embodiments, the parameter or signaling or (re)configuration associated with the specific field corresponds to an additional SRS power control process, and / or when the UE is configured with two SRS power control processes (for at least one serving cell), the specific field is enabled or exists or is a valid bit field.

[0545] Preferably, in certain embodiments, the UE is configured with two SRS resource sets associated with the same purpose (e.g., non-codebook or codebook), or when at least the UE is configured with two SRS resource sets associated with the same purpose (e.g., non-codebook or codebook), the specific field is enabled or exists or is a valid bit field.

[0546] Preferably, in some embodiments, the specific field indicates information of a (type D) quasi co-located (QCL) source RS or information of a source RS or information of a spatial filter used for PRACH transmission.

[0547] Preferably, in certain embodiments, based on a specific field, the UE determines the source RS or the spatial filter QCL to SRS or SS / PBCH for PRACH transmission.

[0548] Preferably, in certain embodiments, the size of a particular field is one.

[0549] Preferably, in some embodiments, when the specific field indicates a first value (eg, 0), the PDCCH order is associated with the SS / PBCH.

[0550] Preferably, in some embodiments, when the specific field indicates the second value (eg, 1), the PDCCH order is associated with the SRS.

[0551] Preferably, in certain embodiments, the PRACH transmission corresponds to a contention-free PRACH transmission, and / or the random access preamble index field in the PDCCH order indicates non-all zeros.

[0552] Preferably, in certain embodiments, when the random access preamble index field in the PDCCH order indicates not all zeros (e.g., CFRA PRACH), a specific field indicates (type D) information of a quasi co-located source RS or information of a source RS or information of a spatial filter for PRACH transmission.

[0553] Preferably, in certain embodiments, when the random access preamble index field in the PDCCH order indicates all zeros (eg, CBRA PRACH), a specific field is reserved.

[0554] Preferably, in some embodiments, the specific field is placed or set in a bit field earlier than the RS field (eg, SS / PBCH index field or SRS index field).

[0555] Preferably, in some embodiments, based on the indication of the specific field, the UE determines that the RS field in the PDCCH order corresponds to the SS / PBCH index field or the SRS index field.

[0556] Preferably, in some embodiments, the specific field is placed later than the random access preamble index field.

[0557] Preferably, in certain embodiments, the RS field is used to determine the PRACH opportunity for PRACH transmission.

[0558] Preferably, in certain embodiments, the UE receives one or more dedicated PRACH configurations.

[0559] Preferably, in some embodiments, based on the dedicated PRACH configuration, the UE determines or identifies an association between a PRACH opportunity and an RS.

[0560] Preferably, in certain embodiments, the UE determines or identifies the PRACH opportunity for PRACH transmission based on the RS indicated by the RS field in the PDCCCH order.

[0561] Preferably, in some embodiments, the RS corresponds to SS / PBCH, CSI-RS or SRS.

[0562] Preferably, in certain embodiments, the UE receives a DL signal from a first TRP and transmits a UL signal to a second TRP.

[0563] Preferably, in some embodiments, the UE communicates with a service cell including a first TRP and a second TRP.

[0564] Preferably, in certain embodiments, the activated TCI state corresponds to a DL TCI state associated with a first TRP and a UL TCI state associated with a second TRP, and / or the activated TCI state corresponds to the DL functionality and UL functionality of a first joint TCI state and the UL functionality of a second joint TCI state.

[0565] Preferably, in certain embodiments, the UE receives a beam indication MAC CE for activating one or more DL / UL / joint TCI states.

[0566] Preferably, in certain embodiments, the UE receives a beam indication DCI indicating a code point from a beam indication MAC CE, and the TCI state in the code point is determined or regarded as the indicated / used / applied TCI state.

[0567] Preferably, in certain embodiments, the UE determines whether the PRACH transmission is associated with SRS or SS / PBCH based on at least one or any combination of: the DCI format associated with the PDCCH command, which CORESET / search space provides the PDCCH command, the 1st / 2nd TCI state associated with the CORESET providing the PDCCH command, the even / odd TTI associated with the PDCCH command, or the TCI state field in the PDCCH command.

[0568] Preferably, in certain embodiments, the PRACH opportunity (for PRACH transmission in response to a PDCCH order) is determined based on an RS field (eg, SS / PBCH index field or SRS index field) in the PDCCH order.

[0569] Preferably, in certain embodiments, the PRACH opportunity (for PRACH transmission in response to a PDCCH order) is determined based on the TCI field in the PDCCH order.

[0570] Preferably, in certain embodiments, the PRACH opportunity (for PRACH transmission in response to a PDCCH order) may be further determined based on a dedicated PRACH configuration.

[0571] Preferably, in certain embodiments, the spatial filter or beam used to transmit the PRACH is associated with the RS indicated by the RS field in the PDCCH order.

[0572] Preferably, in certain embodiments, the source RS associated with the spatial filter or beam used to transmit the PRACH is determined based on any one or any combination of: a specific field in the PDCCH command, a DCI format used for the PDCCH command, and / or an association between the PRACH opportunity and the SS / PBCH or SRS, and / or a dedicated PRACH configuration, and / or a joint / UL TCI state corresponding to the CORESET used to provide the PDCCH command.

[0573] Preferably, in certain embodiments, the UE performs PRACH transmission on the PRACH opportunity (determined by the second RS) via the spatial filter or beam associated with the first RS.

[0574] Preferably, in some embodiments, the first RS corresponds to SRS, and / or the second RS corresponds to SS / PBCH.

[0575] Preferably, in some embodiments, the first RS and the second RS correspond to SS / PBCH.

[0576] Preferably, in some embodiments, both the first RS and the second RS correspond to SRS.

[0577] Preferably, in certain embodiments, a dedicated PRACH configuration provides an association between a PRACH opportunity and the first RS.

[0578] Preferably, in certain embodiments, a dedicated PRACH configuration provides an association between the PRACH occasions and the second RS.

[0579] Preferably, in some embodiments, when a specific field in the PDCCH order indicates a first value, the first RS corresponds to an SRS.

[0580] Preferably, in some embodiments, when the specific field in the PDCCH order indicates the second value, the first RS corresponds to the SRS.

[0581] Preferably, in some embodiments, when the DCI format used for the PDCCH command corresponds to a DCI format of the first category (eg, DCI format 1_0), the first RS corresponds to SS / PBCH.

[0582] Preferably, in some embodiments, when the DCI format used for the PDCCH command corresponds to the DCI format of the second category (eg, DCI format 0_0), the first RS corresponds to the SRS.

[0583] Preferably, in certain embodiments, when the first CORESET for the PDCCH command is configured to follow the 1st joint TCI state (or the 1st UL TCI state) or is associated with the first TRP, the first RS corresponds to the SS / PBCH.

[0584] Preferably, in certain embodiments, when the second CORESET for the PDCCH command is configured to follow the 2nd joint TCI state (or the 2nd UL TCI state) or to be associated with the second TRP, the first RS corresponds to the SRS.

[0585] Preferably, in certain embodiments, the UE is configured with a first set of SS / PBCH associated with a first TRP and a second set of SS / PBCH associated with a second TRP.

[0586] Preferably, in certain embodiments, when the SS / PBCH index field in the PDCCH command indicates an SS / PBCH in a first set of SS / PBCHs associated with the first TRP, the first RS corresponds to the SS / PBCH.

[0587] Preferably, in certain embodiments, when the SS / PBCH index field in the PDCCH command indicates an SS / PBCH in a second set of SS / PBCHs associated with a second TRP, the first RS corresponds to the SRS.

[0588] Preferably, in some embodiments, when a PDCCH order is received in an even TTI, the first RS corresponds to SS / PBCH.

[0589] Preferably, in some embodiments, when a PDCCH order is received in an odd TTI, the first RS corresponds to an SRS.

[0590] Preferably, in certain embodiments, the association between PRACH opportunities and SS / PBCH or SRS is configured by a dedicated PRACH configuration.

[0591] Preferably, in certain embodiments, the dedicated PRACH configuration configures multiple resources or RSs, which include a first set of RSs associated with a first TRP and a second set of RSs associated with a second TRP.

[0592] Preferably, in certain embodiments, the dedicated PRACH configuration configures one or more PRACH opportunities associated with one resource or one RS from among a plurality of resources or a plurality of RSs.

[0593] Preferably, in certain embodiments, the UE operates in sDCI mTRP.

[0594] Preferably, in certain embodiments, the UE is not configured with a CORESETPoolIndex for any serving cell.

[0595] Preferably, in certain embodiments, the UE is configured with a specific CORESET / search space for PDCCH orders associated with SRS.

[0596] Preferably, in certain embodiments, when the UE receives a PDCCH order in a specific CORESET / search space, the first RS corresponds to the SRS.

[0597] Preferably, in some embodiments, the PDCCH command includes a TCI field, and / or a source RS of a TCI state indicated by the TCI field or a QCL type D source RS of a TCI state indicated by the TCI field corresponds to the first RS (for example, the first RS corresponds to this source RS).

[0598] Preferably, in certain embodiments, when the UE receives parameters / (re)configuration associated with or enabled with UL-only TRP, the PDCCH order includes a TCI field (rather than the SS / PBCH index field).

[0599] Preferably, in certain embodiments, the TCI field in the PDCCH order indicates or provides the RS associated with the dedicated PRACH configuration.

[0600] Preferably, in some embodiments, the TCI field in the PDCCH order indicates or provides the first RS (as a spatial filter for transmitting the PRACH).

[0601] Preferably, in some embodiments, the TCI field in the PDCCH order indicates or provides the second RS (for determining the PRACH opportunity).

[0602] Preferably, in certain embodiments, the PDCCH order includes both the TCI field and the SS / PBCH index field.

[0603] Preferably, in some embodiments, the SS / PBCH field provides a second RS.

[0604] Preferably, in certain embodiments, the TCI field provides the first RS.

[0605] Preferably, in some embodiments, based on that the source RS of the TCI state indicated by the TCI field corresponds to the SS / PBCH or SRS, the UE determines a PRACH opportunity associated with the SS / PBCH or SRS.

[0606] Preferably, in certain embodiments, when the source RS of the TCI state indicated by the TCI field corresponds to the SS / PBCH, the PRACH opportunity is associated with the SS / PBCH in the dedicated / common PRACH configuration.

[0607] Preferably, in certain embodiments, when the source RS of the TCI state indicated by the TCI field corresponds to the SRS, the PRACH opportunity is associated with the SRS in the dedicated PRACH configuration.

[0608] Preferably, in some embodiments, the UE is configured with an SRS resource set associated with an SRS resource in a dedicated PRACH configuration, and / or an SRS resource index in the dedicated PRACH configuration is associated with an SRS resource set.

[0609] Preferably, in some embodiments, when identifying the SRS resources in the dedicated PRACH configuration, the signaling may provide an SRS resource set index and an SRS resource index.

[0610] Preferably, in certain embodiments, the PRACH opportunities associated with the SS / PBCH are determined by a common PRACH configuration.

[0611] Reference now Figure 3 and 4 In one or more embodiments from the perspective of a UE in a wireless communication system, the apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. The CPU 308 may execute the program code 312 to: (i) receive a configuration of an uplink-only transmission / reception point from a network node and receive a PDCCH order from the network node; and (ii) perform a PRACH transmission in response to the PDCCH order. In addition, the CPU 308 may execute the program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

[0612] It should be noted that any of the methods, alternatives, steps, examples and embodiments presented above and herein may be applied independently, individually and / or in combination with multiple methods, alternatives, steps, examples and embodiments.

[0613] See also Fig. 9 , with respect to such and other concepts, systems and methods of the present invention, a method 1010 for a UE in a wireless communication system includes receiving a PDCCH command from a first TRP of a serving cell, wherein a field in the PDCCH command indicates an association between a PRACH transmission and the first TRP having DL and UL functionality or an association between the PRACH transmission and a second TRP of the serving cell that does not have DL functionality or has reduced DL functionality (step 1012), and performing a PRACH transmission in response to the PDCCH command, wherein a transmission power of the PRACH transmission is determined based on the field (step 1014).

[0614] In various embodiments, if the field indicates a first value, the transmit power of the PRACH transmission is determined to be a first transmit power, wherein the PRACH transmission is to a first TRP, and / or if the field indicates a second value, the transmit power of the PRACH transmission is determined to be a second transmit power, wherein the PRACH transmission is to a second TRP, and / or the first transmit power is greater than the second transmit power, and / or the first transmit power is different from the second transmit power.

[0615] In various embodiments, regardless of whether the field indicates a first value or a second value, the UE determines or uses the PL RS associated with the first TRP for determining a path loss estimate to determine a transmit power for a PRACH transmission.

[0616] In various embodiments, the PL RS used to determine a path loss estimate to determine a transmit power for a PRACH transmission is associated with a first TRP, and / or even if the PRACH transmission is transmitted to a second TRP, the UE determines or uses the PL RS associated with the first TRP for determining a path loss estimate to determine a transmit power for the PRACH transmission.

[0617] In various embodiments, the field is enabled or present or is a valid bit field in a PDCCH command when the UE receives a parameter or signaling or configuration or reconfiguration associated with the field, and / or the field is enabled or present or is a valid bit field in a PDCCH command when the UE is configured with at least a second TRP, and / or the parameter or signaling or configuration or reconfiguration associated with the field corresponds to a UL TRP only, and / or the field is reserved when the random access preamble index field in the PDCCH command indicates all zeros.

[0618] In various embodiments, the UE is configured with two SRS power control processes for a serving cell, and / or one of the two SRS power control processes is associated with a first TRP and the other of the two SRS power control processes is associated with a second TRP, and / or when the UE is configured with a serving cell including a UL-only TRP or a TRP with reduced DL functionality, the UE is configured with the two SRS power control processes for the serving cell.

[0619] In various embodiments, the UE does not report the capability to support multiple TRPs based on multiple DCIs, and / or the UE reports the capability to support multiple TRPs based on multiple DCIs.

[0620] In various embodiments, the UE receives one or more CORESET configurations associated with a serving cell, and wherein parameters for configuring CORESETPoolIndex are not present in the one or more CORESET configurations, and / or the UE receives one or more CORESET configurations associated with a serving cell, and wherein parameters for configuring CORESETPoolIndex are not present in the one or more CORESET configurations.

[0621] In various embodiments, the UE performs PRACH transmission to the first TRP or the second TRP based on the field.

[0622] In various embodiments, the UE receives one or more DL signals indicating a first TCI state and a second TCI state, and / or the first TRP means or corresponds to the first TCI state, and / or the second TRP means or corresponds to the second TCI state.

[0623] In various embodiments, if the UE is configured with a joint TCI state mode, the first TCI state and the second TCI state are both or correspond to a joint TCI state, and / or the UE determines that the second TCI state is applied with UL functionality or is applied to one or more UL channels and / or the UE determines that the second TCI state is not applied with DL functionality or is not applied to one or more DL channels, and / or the UE determines that the first TCI state is applied with DL and UL functionality or is applied to one or more UL channels and one or more DL channels.

[0624] Return to reference Figure 3 and 4In one or more embodiments from the perspective of a UE in a wireless communication system, the apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. The CPU 308 may execute the program code 312 to: (i) receive a PDCCH command from a first TRP of a serving cell, wherein a field in the PDCCH command indicates an association between a PRACH transmission and a first TRP having DL and UL functionality or an association between a PRACH transmission and a second TRP of a serving cell having no DL functionality or having reduced DL functionality; and (ii) perform a PRACH transmission in response to the PDCCH command, wherein a transmission power of the PRACH transmission is determined based on the field. In addition, the CPU 308 may execute the program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

[0625] See also Fig.10 , with respect to such and other concepts, systems and methods of the present invention, a method 1020 for a UE in a wireless communication system includes receiving a PDCCH command from a first TRP of a serving cell, wherein a field in the PDCCH command is related to a PRACH transmission initiated by the PDCCH command to the first TRP having DL and UL functionality or a second TRP of the serving cell not having DL functionality or having reduced DL functionality (step 1022), and performing a PRACH transmission in response to the PDCCH command, wherein a transmission power of the PRACH transmission is determined based on the field (step 1024).

[0626] In various embodiments, if the field indicates a first value, the transmit power of the PRACH transmission is determined to be a first transmit power, wherein the PRACH transmission is to a first TRP, and / or if the field indicates a second value, the transmit power of the PRACH transmission is determined to be a second transmit power, wherein the PRACH transmission is to a second TRP, and / or the first transmit power is greater than the second transmit power, and / or the first transmit power is different from the second transmit power.

[0627] In various embodiments, regardless of whether the field indicates a first value or a second value, the UE determines or uses the PL RS associated with the first TRP for determining a path loss estimate to determine a transmit power for a PRACH transmission.

[0628] In various embodiments, the PL RS used to determine a path loss estimate to determine a transmit power for a PRACH transmission is associated with a first TRP, and / or even if the PRACH transmission is transmitted to a second TRP, the UE determines or uses the PL RS associated with the first TRP for determining a path loss estimate to determine a transmit power for the PRACH transmission.

[0629] In various embodiments, the field is enabled or present or is a valid bit field in a PDCCH command when the UE receives a parameter or signaling or configuration or reconfiguration associated with the field, and / or the field is enabled or present or is a valid bit field in a PDCCH command when the UE is configured with at least a second TRP, and / or the parameter or signaling or configuration or reconfiguration associated with the field corresponds to a UL TRP only, and / or the field is reserved when the random access preamble index field in the PDCCH command indicates all zeros.

[0630] In various embodiments, the UE is configured with two SRS power control processes for a serving cell, and / or one of the two SRS power control processes is associated with a first TRP and the other of the two SRS power control processes is associated with a second TRP, and / or when the UE is configured with a serving cell including the UL-only TRP or the TRP with reduced DL functionality, the UE is configured with the two SRS power control processes for the serving cell.

[0631] In various embodiments, the UE does not report the capability to support multiple TRPs based on multiple DCIs, and / or the UE reports the capability to support multiple TRPs based on multiple DCIs.

[0632] In various embodiments, the UE receives one or more CORESET configurations associated with a serving cell, wherein a parameter for configuring CORESETPoolIndex is not present in the one or more CORESET configurations.

[0633] In various embodiments, the UE performs PRACH transmission to the first TRP or the second TRP based on the field.

[0634] In various embodiments, the UE receives one or more DL signals indicating a first TCI state and a second TCI state, and / or a first TRP means or corresponds to the first TCI state, and / or a second TRP means or corresponds to the second TCI state.

[0635] In various embodiments, if the UE is configured with a joint TCI state mode, the first TCI state and the second TCI state are both or correspond to a joint TCI state, and / or the UE determines that the second TCI state is applied with UL functionality or is applied to one or more UL channels and / or the UE determines that the second TCI state is not applied with DL functionality or is not applied to one or more DL channels, and / or the UE determines that the first TCI state is applied with DL and UL functionality or is applied to one or more UL channels and one or more DL channels.

[0636] Return to reference Figure 3 and 4In one or more embodiments from the perspective of a UE in a wireless communication system, the apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. The CPU 308 may execute the program code 312 to: (i) receive a PDCCH command from a first TRP of a serving cell, wherein a field in the PDCCH command is related to a PRACH transmission initiated by the PDCCH command to the first TRP having DL and UL functionality or to a second TRP of a serving cell that does not have DL functionality or has reduced DL functionality; and (ii) perform a PRACH transmission in response to the PDCCH command, wherein a transmission power of the PRACH transmission is determined based on the field. In addition, the CPU 308 may execute the program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

[0637] See also Fig.11 , with respect to such and other concepts, systems and methods of the present invention, a method 1030 for a UE in a wireless communication system includes receiving one or more DL signals indicating a first TCI state and a second TCI state (step 1032), receiving a PDCCH command in a serving cell via the first TCI state, wherein a field in the PDCCH command indicates an association between a PRACH transmission and the first TCI state or an association between the PRACH transmission and the second TCI state (step 1034), and performing a PRACH transmission in response to the PDCCH command, wherein a transmission power of the PRACH transmission is determined based on the field (step 1036).

[0638] In various embodiments, if the field indicates a first value, the transmit power of the PRACH transmission is determined to be a first transmit power, wherein the PRACH transmission is associated with a first TCI state, and / or if the field indicates a second value, the transmit power of the PRACH transmission is determined to be a second transmit power, wherein the PRACH transmission is associated with a second TCI state, and / or the first transmit power is greater than the second transmit power, and / or the first transmit power is different from the second transmit power.

[0639] In various embodiments, regardless of whether the field indicates the first value or the second value, the UE determines or uses the PL RS associated with the first TCI state for determining a path loss estimate to determine the transmit power of the PRACH transmission.

[0640] In various embodiments, the PL RS used to determine the path loss estimate to determine the transmit power of the PRACH transmission is associated with the first TCI state, and / or even if the PRACH transmission is associated with the second TCI state, the UE determines or uses the PL RS associated with the first TCI state for determining the path loss estimate to determine the transmit power of the PRACH transmission.

[0641] In various embodiments, the field is enabled or present or is a valid bit field in a PDCCH order when the UE receives parameters or signaling or configuration or reconfiguration associated with the field, and / or the field is enabled or present or is a valid bit field in a PDCCH order when the UE is configured with at least a second TCI state that applies only to one or more UL channels, and / or the parameters or signaling or configuration or reconfiguration associated with the field correspond to a UL-only TRP, and / or when the random access preamble index field in the PDCCH order indicates all zeros, the field is reserved.

[0642] In various embodiments, the UE is configured with two SRS power control processes for a serving cell, and / or one of the two SRS power control processes is associated with a first TCI state and the other of the two SRS power control processes is associated with a second TCI state, and / or when the UE is configured with a serving cell including a UL-only TRP or a TRP with reduced DL functionality, the UE is configured with the two SRS power control processes for the serving cell.

[0643] In various embodiments, the UE does not report the capability to support multiple TRPs based on multiple DCIs, and / or the UE reports the capability to support multiple TRPs based on multiple DCIs.

[0644] In various embodiments, the UE receives one or more CORESET configurations associated with a serving cell, wherein a parameter for configuring CORESETPoolIndex is not present in the one or more CORESET configurations.

[0645] In various embodiments, the UE performs PRACH transmission via the first TCI state or the second TCI state based on the field, and / or the UE determines transmission power via PRACH transmission using the first TCI state or via the second TCI state based on the field.

[0646] In various embodiments, if the UE is configured with a joint TCI state mode, the first TCI state and the second TCI state are both or correspond to a joint TCI state, and / or the UE determines that the second TCI state is applied with UL functionality or is applied to one or more UL channels and / or the UE determines that the second TCI state is not applied with DL functionality or is not applied to one or more DL channels, and / or the UE determines that the first TCI state is applied with DL and UL functionality or is applied to one or more UL channels and one or more DL channels.

[0647] Return to reference Figure 3 and 4In one or more embodiments from the perspective of a UE in a wireless communication system, the apparatus 300 includes a program code 312 stored in a memory 310 of a transmitter. The CPU 308 may execute the program code 312 to: (i) receive one or more DL signals indicating a first TCI state and a second TCI state; (ii) receive a PDCCH command in a serving cell via the first TCI state, wherein a field in the PDCCH command indicates an association between a PRACH transmission and the first TCI state or an association between a PRACH transmission and the second TCI state; and (iii) perform a PRACH transmission in response to the PDCCH command, wherein a transmission power of the PRACH transmission is determined based on the field. In addition, the CPU 308 may execute the program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

[0648] Any combination of the concepts or teachings above or herein may be fully or partially combined or formed into new embodiments. The disclosed details and embodiments may be used to at least (but not limited to) solve the problems mentioned above and herein.

[0649] It should be noted that any of the methods, alternatives, steps, examples and embodiments presented herein may be applied independently, individually and / or in combination with multiple methods, alternatives, steps, examples and embodiments.

[0650] Various aspects of the present disclosure have been described above. It should be clear that the teachings herein can be implemented in a wide variety of forms, and any specific structure, function, or both disclosed herein are only representative. Based on the teachings herein, it should be understood by those skilled in the art that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in different ways. For example, any number of aspects set forth herein can be used to implement a device or practice method. In addition, by using other structures, functionality, or structures and functionality other than one or more aspects of the aspects set forth herein or different from one or more aspects of the aspects set forth herein, this device can be implemented or this method can be practiced. As an example of some of the above concepts, in some aspects, parallel channels can be established based on pulse repetition frequencies. In some aspects, parallel channels can be established based on pulse positions or offsets. In some aspects, parallel channels can be established based on time hopping sequences. In some aspects, parallel channels can be established based on pulse repetition frequencies, pulse positions or offsets, and time hopping sequences.

[0651] Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0652] Those of ordinary skill in the art will further appreciate that the various illustrative logical blocks, modules, processors, components, circuits, and algorithm steps described in conjunction with the various aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two, which may be designed using source decoding or some other technique), and various forms of programs or design code with instructions (which may be referred to herein as "software" or "software modules" for convenience), or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0653] In addition, the various illustrative logical blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented within or performed by an integrated circuit ("IC"), an access terminal, or an access point. The IC may include a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute code or instructions residing within the IC, outside the IC, or both. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0654] It should be understood that any specific order or hierarchy of steps in any disclosed process is an example of an exemplary method. It should be understood that based on design preferences, the specific order or hierarchy of steps in a process can be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order and are not intended to be limited to the specific order or hierarchy presented.

[0655] The steps of the method or algorithm described in conjunction with the various aspects disclosed herein can be implemented directly with hardware, with a software module executed by a processor, or with a combination of the two. Software modules (e.g., including executable instructions and related data) and other data can reside in a data memory, such as a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of a computer-readable storage medium known in the art. A sample storage medium can be coupled to a machine such as a computer / processor (for convenience, the machine can be referred to as a "processor" in this article) so that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. A sample storage medium can be integrated with a processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user device. In an alternative, the processor and the storage medium can reside in a user device as discrete components. In addition, in some aspects, any suitable computer program product may include a computer-readable medium, and the computer-readable medium includes a code related to one or more of the various aspects of the present disclosure. In some aspects, a computer program product may include packaging materials.

[0656] Although the present invention has been described in conjunction with various aspects and examples, it will be appreciated that the present invention is capable of further modifications. This application is intended to cover any changes, uses or adaptations of the present invention, which generally follow the principles of the present invention and include such deviations from the present disclosure, which are within the scope of known and customary practice in the technical field to which the present invention belongs.

Claims

1. A method for a user device, characterized in that: include: receiving a physical downlink control channel order from a first transmission / reception point of a serving cell, wherein a field in the physical downlink control channel order indicates an association between a physical random access channel transmission and the first transmission / reception point having downlink and uplink functionality or an association between the physical random access channel transmission and a second transmission / reception point of the serving cell having no downlink functionality or having reduced downlink functionality; as well as The physical random access channel transmission is performed in response to the physical downlink control channel command, wherein a transmission power of the physical random access channel transmission is determined based on the field.

2. The method according to claim 1, characterized in that: If the field indicates a first value, the transmit power of the physical random access channel transmission is determined to be a first transmit power, wherein the physical random access channel transmission is to the first transmission / reception point, and / or If the field indicates a second value, the transmit power of the physical random access channel transmission is determined to be a second transmit power, wherein the physical random access channel transmission is to the second transmission / reception point, and / or The first transmission power is greater than the second transmission power, and / or The first transmit power is different from the second transmit power.

3. The method according to claim 2, characterized in that Regardless of whether the field indicates the first value or the second value, the user equipment determines or uses a path loss reference signal associated with the first transmission / reception point for determining a path loss estimate to determine the transmit power of the physical random access channel transmission.

4. The method according to claim 1, characterized in that: A path loss reference signal for determining a path loss estimate to determine said transmit power for said physical random access channel transmission is associated with said first transmission / reception point, and / or Even if the physical random access channel transmission is transmitted to the second transmission / reception point, the user equipment determines or uses the path loss reference signal associated with the first transmission / reception point for determining the path loss estimate to determine the transmission power of the physical random access channel transmission.

5. The method according to claim 1, characterized in that: The field is enabled or exists or is a valid bit field in the physical downlink control channel command when the user equipment receives parameters or signaling or configuration or reconfiguration associated with the field, and / or The field is enabled or exists or is a valid bit field in the physical downlink control channel command when the user equipment is configured with at least the second transmission / reception point, and / or The parameter or the signaling or the configuration or the reconfiguration associated with the field corresponds to an uplink-only transmission / reception point, and / or When the Random Access Preamble Index field in the Physical Downlink Control Channel order indicates all zeros, the field is reserved.

6. The method according to claim 1, characterized in that: The user equipment is configured with two sounding reference signal power control processes for the serving cell, and / or One of the two sounding reference signal power control processes is associated with the first transmission / reception point, and the other of the two sounding reference signal power control processes is associated with the second transmission / reception point, and / or When the user equipment is configured with the serving cell comprising uplink-only transmission / reception points or transmission / reception points with reduced downlink functionality, the user equipment is configured with the two sounding reference signal power control procedures for the serving cell.

7. The method according to claim 1, characterized in that: The user equipment does not report the capability of supporting multiple transmission / reception points based on multiple downlink control information, and / or The user equipment reports a capability of supporting multiple transmission / reception points based on multiple downlink control information, and / or The user equipment receives one or more control resource set configurations associated with the serving cell, and wherein a parameter for configuring CORESETPoolIndex does not exist in the one or more control resource set configurations.

8. The method according to claim 1, characterized in that: The user equipment performs the physical random access channel transmission to the first transmission / reception point or the second transmission / reception point based on the field.

9. The method according to claim 1, characterized in that: The user equipment receives one or more downlink signals indicating a first transmission configuration indicator state and a second transmission configuration indicator state, and / or The first transmission / reception point means or corresponds to the first transmission configuration indicator state, and / or The second transmission / reception point means or corresponds to the second transmission configuration indicator state.

10. The method according to claim 9, characterized in that: If the user equipment is configured with a joint transmission configuration indicator state mode, the first transmission configuration indicator state and the second transmission configuration indicator state are or correspond to a joint transmission configuration indicator state, and / or The user equipment determines that the second transmission configuration indicator state applies uplink functionality or applies to one or more uplink channels, and / or the user equipment determines that the second transmission configuration indicator state does not apply downlink functionality or does not apply to one or more downlink channels, and / or The user equipment determines that the first transmission configuration indicator state applies to downlink and uplink functionality or to one or more uplink channels and one or more downlink channels.

11. A method for a user device, characterized in that: include: receiving one or more downlink signals indicating a first transmit configuration indicator state and a second transmit configuration indicator state; receiving a physical downlink control channel command in a serving cell via the first transmission configuration indicator state, wherein a field in the physical downlink control channel command indicates an association between a physical random access channel transmission and the first transmission configuration indicator state or an association between the physical random access channel transmission and the second transmission configuration indicator state; as well as The physical random access channel transmission is performed in response to the physical downlink control channel command, wherein a transmission power of the physical random access channel transmission is determined based on the field.

12. The method according to claim 11, characterized in that: If the field indicates a first value, the transmit power of the physical random access channel transmission is determined to be a first transmit power, wherein the physical random access channel transmission is associated with the first transmit configuration indicator state, and / or If the field indicates a second value, the transmit power of the physical random access channel transmission is determined to be a second transmit power, wherein the physical random access channel transmission is associated with the second transmit configuration indicator state, and / or The first transmission power is greater than the second transmission power, and / or The first transmit power is different from the second transmit power.

13. The method according to claim 12, characterized in that Regardless of whether the field indicates the first value or the second value, the user equipment determines or uses a path loss reference signal associated with the first transmission configuration indicator state for determining a path loss estimate to determine the transmit power of the physical random access channel transmission.

14. The method according to claim 11, characterized in that: A path loss reference signal for determining a path loss estimate to determine the transmit power for the physical random access channel transmission is associated with the first transmit configuration indicator state, and / or Even if the physical random access channel transmission is associated with the second transmission configuration indicator state, the user equipment determines or uses the path loss reference signal associated with the first transmission configuration indicator state for determining the path loss estimate to determine the transmission power of the physical random access channel transmission.

15. The method according to claim 11, characterized in that: The field is enabled or exists or is a valid bit field in the physical downlink control channel command when the user equipment receives parameters or signaling or configuration or reconfiguration associated with the field, and / or When the user equipment is configured with at least the second transmission configuration indicator state that applies only to one or more uplink channels, the field is enabled or exists or is a valid bit field in the physical downlink control channel command, and / or The parameter or the signaling or the configuration or the reconfiguration associated with the field corresponds to an uplink-only transmission / reception point, and / or When the Random Access Preamble Index field in the Physical Downlink Control Channel order indicates all zeros, the field is reserved.

16. The method according to claim 11, characterized in that: The user equipment is configured with two sounding reference signal power control processes for the serving cell, and / or One of the two sounding reference signal power control processes is associated with the first transmission configuration indicator state and the other of the two sounding reference signal power control processes is associated with the second transmission configuration indicator state, and / or When the user equipment is configured with the serving cell comprising uplink-only transmission / reception points or transmission / reception points with reduced downlink functionality, the user equipment is configured with the two sounding reference signal power control procedures for the serving cell.

17. The method according to claim 11, characterized in that: The user equipment does not report the capability of supporting multiple transmission / reception points based on multiple downlink control information, and / or The user equipment reports a capability of supporting multiple transmission / reception points based on multiple downlink control information.

18. The method according to claim 11, characterized in that The user equipment receives one or more control resource set configurations associated with the serving cell, wherein a parameter for configuring CORESETPoolIndex does not exist in the one or more control resource set configurations.

19. The method according to claim 11, characterized in that: The user equipment performs the physical random access channel transmission via the first transmission configuration indicator state or the second transmission configuration indicator state based on the field, and / or The user equipment determines the transmit power transmitted via the physical random access channel using the first transmit configuration indicator state or via the second transmit configuration indicator state based on the field.

20. The method according to claim 11, characterized in that: If the user equipment is configured with a joint transmission configuration indicator state mode, the first transmission configuration indicator state and the second transmission configuration indicator state are or correspond to a joint transmission configuration indicator state, and / or The user equipment determines that the second transmission configuration indicator state applies uplink functionality or applies to one or more uplink channels, and / or the user equipment determines that the second transmission configuration indicator state does not apply downlink functionality or does not apply to one or more downlink channels, and / or The user equipment determines that the first transmission configuration indicator state applies to downlink and uplink functionality or to one or more uplink channels and one or more downlink channels.

Images