User equipment, base station and method for beam indication of network controlled repeaters

Abstract

A network controlled repeater (NCR) device is described that communicates with a user equipment (UE) and a base station device. The NCR apparatus may include a receiving circuit configured to: receive a radio resource control (RRC) message including first information indicating a first list of transmit configuration indicator (TCI) states for beams associated with a backhaul link and / or a C-link; receiving an RRC message including second information for indicating a second list of transmit configuration indicator (TCI) states for beams associated with the access link; receiving a first medium access control (MAC) control element (CE) message including third information; and receiving a second medium access control (MAC) control element (CE) message including fourth information. The apparatus may also include a transmission circuit configured to transmit a physical downlink control channel (PDCCH) carried by the access link according to the second TCI state.

Description

Technical Field

[0001] The present disclosure generally relates to communication systems and, more particularly, to user equipment, base stations, and methods for beam pointing of a Network Controlled Relay (NCR). Background Art

[0002] To meet consumer demands and improve portability and convenience, wireless communication devices have become smaller and more powerful. Consumers have become dependent on wireless communication devices and expect reliable service, expanded coverage, and enhanced functionality. A wireless communication system can provide communication for multiple wireless communication devices, each of which can be served by a base station. A base station is a device that communicates with wireless communication devices.

[0003] With the development of wireless communication devices, people have been seeking ways to improve communication capacity, speed, flexibility and / or efficiency. However, improving communication capacity, speed, flexibility and / or efficiency may bring certain problems.

[0004] For example, a wireless communication device may use a communication structure to communicate with one or more devices. However, the communication structure used may only provide limited flexibility and / or efficiency. As illustrated in this discussion, systems and methods for improving communication flexibility and / or efficiency may be advantageous. Summary of the Invention

[0005] In one example, a network controlled relay (NCR) device that communicates with a user equipment (UE) and a base station device, the network controlled relay (NCR) device comprising: a receiving circuit configured to: receive a radio resource control (RRC) message comprising first information, the first information being used to indicate a first list of transmission configuration indicator (TCI) states for beams associated with a backhaul link and / or a C-link; receive an RRC message comprising second information, the second information being used to indicate a second list of transmission configuration indicator (TCI) states for beams associated with an access link; receive a first medium access control (MAC) control element (CE) message comprising third information, the third information being used to indicate a second list of transmission configuration indicator (TCI) states for beams associated with an access link; and receive a first medium access control (MAC) control element (CE) message comprising third information. Information is used to indicate a first TCI state of a physical downlink control channel (PDCCH) carried by the backhaul link and / or the C-link in the first list; receiving a second medium access control (MAC) control element (CE) message including fourth information, the fourth information being used to indicate a second TCI state of a physical downlink control channel (PDCCH) carried by the access link in the second list; and receiving a physical downlink control channel (PDCCH) carried by the backhaul link and / or the C-link according to the first TCI state; a transmitting circuit, the transmitting circuit being configured to: transmit a physical downlink control channel (PDCCH) carried by the access link according to the second TCI state.

[0006] In one example, a base station device that communicates with a user equipment (UE) and a network controlled relay (NCR) device includes: a transmitting circuit configured to: transmit a radio resource control (RRC) message including first information indicating a first list of transmit configuration indicator (TCI) states for beams associated with a backhaul link and / or a C-link; transmit an RRC message including second information indicating a second list of transmit configuration indicator (TCI) states for beams associated with an access link; and transmit a first medium access message including third information. The method further comprises transmitting a medium access control (MAC) control element (CE) message including third information for indicating a first TCI state of a physical downlink control channel (PDCCH) carried by the backhaul link and / or the C-link in the first list; transmitting a second medium access control (MAC) control element (CE) message including fourth information for indicating a second TCI state of a physical downlink control channel (PDCCH) carried by the access link in the second list; and transmitting a physical downlink control channel (PDCCH) carried by the backhaul link and / or the C-link according to the first TCI state.

[0007] In one example, a user equipment (UE) that communicates with a network controlled repeater (NCR) device and a base station device includes: a receiving circuit configured to: receive an RRC message including second information, the second information being used to indicate a second list of transmission configuration indicator (TCI) states for a beam associated with an access link; receive a second medium access control (MAC) control element (CE) message including fourth information, the fourth information being used to indicate a second TCI state in the second list for a physical downlink control channel (PDCCH) carried by the access link; and receive a physical downlink control channel (PDCCH) carried by the access link according to the second TCI state. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 is a block diagram illustrating one specific implementation of one or more gNode Bs (gNBs) and one or more user equipments (UEs) in which systems and methods for transmitting signals may be implemented. Figure 2 Examples of multiple parameter sets are shown. Figure 3 is a diagram illustrating one example of a resource grid and resource blocks. Figure 4 An example of a resource area is shown. Figure 5 Examples of beamforming and quasi-collocated (QCL) types are illustrated. Figure 5 Examples of beamforming and quasi-collocated (QCL) types are illustrated. Figure 7 is a flow chart illustrating an example of a method for joint beam management. Figure 8 is a flow chart illustrating an example of a method for joint beam management. Figure 9 Various components that may be utilized in a UE are illustrated. Figure 10 Illustrate various components that can be used in gNB. Figure 11 is a block diagram illustrating one specific implementation of a UE in which one or more of the systems and / or methods described herein may be implemented. Figure 12 is a block diagram illustrating one specific implementation of a gNB in ​​which one or more of the systems and / or methods described herein may be implemented. Figure 13 is a block diagram illustrating a specific implementation of a gNB. Figure 14 is a block diagram illustrating one specific implementation of a UE. Figure 15 is an example of a block diagram of a conceptual model of a network controlled repeater (NCR). Figure 16 is a flowchart illustrating an example of a method for a UE to perform beam management with respect to inter-cell mobility. Figure 17 is a flowchart illustrating an example of a method for a base station to perform beam management with respect to inter-cell mobility. Figure 18 is a flowchart illustrating an example of a method for a UE to perform beam indication regarding inter-cell mobility for a PDSCH. Figure 19 This is a flowchart illustrating an example of a method for a base station to perform beam indication regarding inter-cell mobility on a PDSCH. Figure 20 is a flowchart illustrating an example of a method for a UE to perform beam indication regarding inter-cell mobility with respect to a PDCCH. Figure 21 This is a flowchart illustrating an example of a method for a base station to perform beam indication regarding inter-cell mobility with respect to a PDCCH. DETAILED DESCRIPTION

[0009] The present invention describes a network controlled relay (NCR) device that communicates with a user equipment (UE) and a base station device. The NCR device may include a receiving circuit configured to: receive a radio resource control (RRC) message including first information, the first information being used to indicate a first list of transmission configuration indicator (TCI) states for beams associated with a backhaul link and / or a C-link; receive an RRC message including second information, the second information being used to indicate a second list of transmission configuration indicator (TCI) states for beams associated with an access link; receive a first medium access control (MAC) control element (CE) message including third information, the third information being used to indicate a first TCI state for a physical downlink control channel (PDCCH) carried by the backhaul link and / or the C-link in the first list; receive a second medium access control (MAC) control element (CE) message including fourth information, the fourth information being used to indicate a second TCI state for a physical downlink control channel (PDCCH) carried by the access link in the second list; and receive a physical downlink control channel (PDCCH) carried by the backhaul link and / or the C-link according to the first TCI state. The NCR device may further include a transmitting circuit configured to transmit a physical downlink control channel (PDCCH) carried by the access link according to the second TCI state.

[0010] The present invention describes a base station apparatus that communicates with a user equipment (UE) and a network controlled relay (NCR) apparatus. The device may include a transmitting circuit configured to: transmit a radio resource control (RRC) message including first information, the first information being used to indicate a first list of transmission configuration indicator (TCI) states for beams associated with a backhaul link and / or a C-link; transmit an RRC message including second information, the second information being used to indicate a second list of transmission configuration indicator (TCI) states for beams associated with an access link; transmit a first medium access control (MAC) control element (CE) message including third information, the third information being used to indicate a first TCI state for a physical downlink control channel (PDCCH) carried by the backhaul link and / or the C-link in the first list; transmit a second medium access control (MAC) control element (CE) message including fourth information, the fourth information being used to indicate a second TCI state for a physical downlink control channel (PDCCH) carried by the access link in the second list; and transmit a physical downlink control channel (PDCCH) carried by the backhaul link and / or the C-link according to the first TCI state.

[0011] The present invention describes a user equipment (UE) that communicates with a network controlled relay (NCR) device and a base station device. The UE may include a receiving circuit configured to: receive an RRC message including second information indicating a second list of transmit configuration indicator (TCI) states for a beam associated with an access link; receive a second medium access control (MAC) control element (CE) message including fourth information indicating a second TCI state for a physical downlink control channel (PDCCH) carried by the access link in the second list; and receive the physical downlink control channel (PDCCH) carried by the access link according to the second TCI state.

[0012] The 3rd Generation Partnership Project (also known as "3GPP") is a collaborative agreement that develops globally applicable technical specifications and technical reports for third and fourth generation wireless communication systems. 3GPP develops specifications for next generation mobile networks, systems, and devices.

[0013] 3GPP Long Term Evolution (LTE) is the name given to a project to improve the Universal Mobile Telecommunications System (UMTS) mobile phone or device standard to cope with future needs. In one aspect, UMTS has been modified to provide support and specifications for Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).

[0014] At least some aspects of the systems and methods disclosed herein may be described in conjunction with 3GPP LTE, LTE-Advanced (LTE-A), LTE-Advanced Pro, and other standards (e.g., 3GPP Releases 8, 9, 10, 11, 12, 13, 14, 15, and / or 16). However, the scope of the present disclosure should not be limited in this respect. At least some aspects of the systems and methods disclosed herein may be used in other types of wireless communication systems.

[0015] A wireless communication device may be an electronic device that transmits voice and / or data to a base station, which in turn may communicate with a network of devices (e.g., a public switched telephone network (PSTN), the Internet, etc.). When describing the systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, UE, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, mobile device, etc. Examples of wireless communication devices include cellular phones, smartphones, personal digital assistants (PDAs), laptops, netbooks, e-readers, wireless modems, etc. In 3GPP specifications, wireless communication devices are generally referred to as UEs. However, since the scope of the present disclosure should not be limited to 3GPP standards, the terms "UE" and "wireless communication device" may be used interchangeably herein to represent the more general term "wireless communication device." A UE may also be more generally referred to as a terminal device.

[0016] In 3GPP specifications, a base station is often referred to as a Node B, an evolved Node B (eNB), a home-enhanced or evolved Node B (HeNB), a gNode B (gNB), or some other similar term. Because the scope of this disclosure should not be limited to 3GPP standards, the terms "base station," "Node B," "eNB," "gNB," and "HeNB" are used interchangeably herein to refer to the more general term "base station." Furthermore, the term "base station" may be used to refer to an access point. An access point can be an electronic device that provides wireless communication devices with access to a network (e.g., a local area network (LAN), the Internet, etc.). The term "communication device" may be used to refer to a wireless communication device and / or a base station. A gNB may also be more generally referred to as a base station device.

[0017] It should be noted that, as used herein, a "cell" can be any communication channel designated by standardization or regulatory authorities for use with International Mobile Telecommunications-Advanced (IMT-Advanced) or IMT-2020, as well as all or a subset thereof, and adopted by 3GPP as a licensed or unlicensed band (e.g., a frequency band) for communication between an eNB or gNB and a UE. It should also be noted that, in the general description of E-UTRA and E-UTRAN, as used herein, a "cell" can be defined as "a combination of downlink resources and, optionally, uplink resources." The link between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources can be indicated in system information transmitted on the downlink resources.

[0018] The fifth generation communication system, referred to as NR (New Radio Technology) by 3GPP, envisions the use of time / frequency / space resources to enable services such as eMBB (enhanced Mobile Broadband) transmission, URLLC (Ultra-Reliable and Low-Latency Communication) transmission, and mMTC (Massive Machine Type Communication) transmission. Furthermore, in NR, one or more bandwidth parts (BWPs) in a serving cell and / or for one or more serving cells may be designated (e.g., configured) for transmission of different services. A user equipment (UE) may receive downlink (DL) signals and / or transmit uplink signals in the BWPs of one or more serving cells.

[0019] In order for services to efficiently use time, frequency, and / or space resources, it would be useful to be able to effectively control downlink and / or uplink transmissions. Therefore, a process for effectively controlling downlink and / or uplink transmissions should be designed. Therefore, a detailed design of the process for downlink and / or uplink transmissions may be beneficial.

[0020] Various examples of the systems and methods disclosed herein will now be described with reference to the accompanying drawings, wherein like reference numerals may indicate functionally similar elements. The systems and methods generally described and illustrated in the drawings herein can be arranged and designed in a variety of different specific implementations. Therefore, the following more detailed description of several specific implementations presented in the drawings is not intended to limit the scope of the claims, but is merely representative of the systems and methods.

[0021] Figure 1is a block diagram illustrating one implementation of one or more gNBs 160 and one or more UEs 102 in which systems and methods for transmitting signals (and / or joint beam management) may be implemented. The one or more UEs 102 communicate with the one or more gNBs 160 using one or more physical antennas 122a-n. For example, the UE 102 transmits electromagnetic signals to the gNB 160 and receives electromagnetic signals from the gNB 160 using one or more physical antennas 122a-n. The gNB 160 communicates with the UE 102 using one or more physical antennas 180a-n. In some implementations, the terms "base station," "eNB," and / or "gNB" may refer to and / or be replaced by the term "transmit receive point (TRP)." For example, in some implementations, in conjunction with Figure 1 The gNB 160 described may be a TRP.

[0022] UE 102 and gNB 160 may communicate with each other using one or more channels and / or one or more signals 119, 121. For example, UE 102 may transmit information or data to gNB 160 using one or more uplink channels 121. Examples of uplink channels 121 include physical shared channels (e.g., PUSCH (Physical Uplink Shared Channel)) and / or physical control channels (e.g., PUCCH (Physical Uplink Control Channel)). For example, one or more gNBs 160 may also transmit information or data to one or more UEs 102 using one or more downlink channels 119. Examples of downlink channels 119 include physical shared channels (e.g., PDSCH (Physical Downlink Shared Channel)) and / or physical control channels (PDCCH (Physical Downlink Control Channel)). Other types of channels and / or signals may also be used.

[0023] Each of the one or more UEs 102 may include one or more transceivers 118, one or more demodulators 114, one or more decoders 108, one or more encoders 150, one or more modulators 154, a data buffer 104, and a UE operations module 124. For example, one or more receive paths and / or transmit paths may be implemented in the UE 102. For convenience, only a single transceiver 118, decoder 108, demodulator 114, encoder 150, and modulator 154 are illustrated in the UE 102, but multiple parallel elements (e.g., multiple transceivers 118, decoders 108, demodulators 114, encoders 150, and modulators 154) may be implemented.

[0024] The transceiver 118 may include one or more receivers 120 and one or more transmitters 158. The one or more receivers 120 may receive signals from the gNB 160 using one or more antennas 122a-n. For example, the receiver 120 may receive and downconvert a signal to produce one or more received signals 116. The one or more received signals 116 may be provided to the demodulator 114. The one or more transmitters 158 may transmit signals to the gNB 160 using one or more physical antennas 122a-n. For example, the one or more transmitters 158 may upconvert and transmit the one or more modulated signals 156.

[0025] The demodulator 114 may demodulate one or more received signals 116 to generate one or more demodulated signals 112. The one or more demodulated signals 112 may be provided to the decoder 108. The UE 102 may use the decoder 108 to decode the signal. The decoder 108 may generate a decoded signal 110, which may include the UE-decoded signal 106 (also referred to as the first UE-decoded signal 106). For example, the first UE-decoded signal 106 may include received payload data, which may be stored in the data buffer 104. Another signal included in the decoded signal 110 (also referred to as the second UE-decoded signal 110) may include overhead data and / or control data. For example, the second UE-decoded signal 110 may provide data that the UE operations module 124 may use to perform one or more operations.

[0026] Generally speaking, the UE operations module 124 may enable the UE 102 to communicate with one or more gNBs 160. The UE operations module 124 may include a UE scheduling module 126.

[0027] The UE scheduling module 126 may perform downlink reception and uplink transmission. Downlink reception includes reception of data, reception of downlink control information, and / or reception of downlink reference signals. In addition, uplink transmission includes transmission of data, transmission of uplink control information, and / or transmission of uplink reference signals.

[0028] Furthermore, in carrier aggregation (CA), gNB 160 and UE 102 may communicate with each other using one or more serving cells. Here, the one or more serving cells may include a primary cell and one or more secondary cells. For example, gNB 160 may transmit information using an RRC message to configure one or more secondary cells to form a serving cell set together with the primary cell. That is, the serving cell set may include one primary cell and one or more secondary cells. Here, the primary cell may be always activated. Furthermore, gNB 160 may activate one or more secondary cells within the configured secondary cells. Here, in the downlink, the carrier corresponding to the primary cell may be a downlink primary component carrier (i.e., DL PCC), and the carrier corresponding to the secondary cell may be a downlink secondary component carrier (i.e., DL SCC). Furthermore, in the uplink, the carrier corresponding to the primary cell may be an uplink primary component carrier (i.e., UL PCC), and the carrier corresponding to the secondary cell may be an uplink secondary component carrier (i.e., UL SCC).

[0029] In a radio communication system, physical channels (uplink physical channels and / or downlink physical channels) may be defined. The physical channels (uplink physical channels and / or downlink physical channels) may be used to transmit information delivered from a higher layer.

[0030] For example, in the uplink, a PRACH (Physical Random Access Channel) may be defined. In some methods, the PRACH (e.g., a random access procedure) may be used for an initial access connection establishment procedure, a handover procedure, a connection reestablishment procedure, timing adjustment (e.g., for synchronization of uplink transmissions, for UL synchronization), and / or for requesting uplink shared channel (UL-SCH) resources (e.g., uplink physical shared channel (PSCH) (e.g., PUSCH) resources).

[0031] In another example, a physical uplink control channel (PUCCH) may be defined. The PUCCH may be used to transmit uplink control information (UCI). The UCI may include a hybrid automatic repeat request acknowledgement (HARQ-ACK), channel state information (CSI), and / or a scheduling request (SR). The HARQ-ACK is used to indicate a positive acknowledgement (ACK) or negative acknowledgement (NACK) of downlink data (e.g., a transport block, a medium access control protocol data unit (MAC PDU), and / or a downlink shared channel (DL-SCH)). The CSI is used to indicate the state of a downlink channel (e.g., a downlink signal). In addition, the SR is used to request resources for uplink data (e.g., a transport block, a MAC PDU, and / or an uplink shared channel (UL-SCH)).

[0032] Here, DL-SCH and / or UL-SCH may be transport channels used in the MAC layer. Furthermore, a transport block (TB) and / or a MAC PDU may be defined as a unit of a transport channel used in the MAC layer. A transport block may be defined as a unit of data delivered from the MAC layer to the physical layer. The MAC layer may deliver a transport block to the physical layer (e.g., the MAC layer delivers data as a transport block to the physical layer). In the physical layer, a transport block may be mapped to one or more codewords.

[0033] In the downlink, a physical downlink control channel (PDCCH) may be defined. The PDCCH may be used to transmit downlink control information (DCI). Here, more than one DCI format may be defined for DCI transmission on the PDCCH. That is, fields may be defined in the DCI format and mapped to information bits (e.g., DCI bits).

[0034] Additionally or alternatively, a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH) may be defined. For example, when a PDSCH (e.g., PDSCH resources) is scheduled using a DCI format for the downlink, the UE 102 may receive downlink data on the scheduled PDSCH (e.g., PDSCH resources). Additionally or alternatively, when a PUSCH (e.g., PUSCH resources) is scheduled using a DCI format for the downlink, the UE 102 may transmit uplink data on the scheduled PUSCH (e.g., PUSCH resources). For example, the PDSCH may be used to transmit downlink data (e.g., DL-SCH, downlink transport blocks). Additionally or alternatively, the PUSCH may be used to transmit uplink data (e.g., UL-SCH, uplink transport blocks).

[0035] Furthermore, the PDSCH and / or PUSCH may be used to transmit information from higher layers (e.g., the radio resource control (RRC) layer and / or the MAC layer). For example, the PDSCH (e.g., from gNB 160 to UE 102) and / or the PUSCH (e.g., from UE 102 to gNB 160) may be used to transmit RRC messages (RRC signals). Additionally or alternatively, the PDSCH (e.g., from gNB 160 to UE 102) and / or the PUSCH (e.g., from UE 102 to gNB 160) may be used to transmit MAC control elements (MAC CEs). Herein, RRC messages and / or MAC CEs are also referred to as higher layer signals.

[0036] In some methods, a physical broadcast channel (PBCH) may be defined. For example, the PBCH may be used to broadcast a Master Information Block (MIB). Here, system information may be divided into the MIB and multiple System Information Blocks (SIBs). For example, the MIB may be used to carry minimum system information. Additionally or alternatively, the SIB may be used to carry system information messages.

[0037] In some methods, a synchronization signal (SS) may be defined in the downlink. The SS may be used to acquire time and / or frequency synchronization with a cell. Additionally or alternatively, the SS may be used to detect the physical layer cell ID of the cell. The SS may include a primary SS and a secondary SS.

[0038] An SS / PBCH block can be defined as a set of a primary SS, a secondary SS, and a PBCH. In the time domain, an SS / PBCH block can consist of four OFDM symbols, which are numbered in ascending order from 0 to 3 within the SS / PBCH block. The PSS, SSS, and PBCH with associated demodulation reference signals (DMRS) are mapped to the symbols. One or more SS / PBCH blocks can be mapped within a certain duration (e.g., 5 milliseconds).

[0039] In addition, the SS / PBCH block can be used for beam measurement, radio resource management (RRM) measurement, and radio link control (RLM) measurement. Specifically, the secondary synchronization signal (SSS) can be used for measurement.

[0040] In uplink radio communications, UL RSs may be used as uplink physical signals. Additionally or alternatively, in downlink radio communications, DL RSs may be used as downlink physical signals. Uplink physical signals and / or downlink physical signals may not be used to transmit information provided by higher layers, but may be used by the physical layer.

[0041] Here, for simplicity of description, in some implementations, it may be assumed that the downlink physical channels and / or downlink physical signals described herein are included in downlink signals (e.g., DL signals). In addition or alternatively, for simplicity of description, in some implementations, it may be assumed that the uplink physical channels and / or uplink physical signals described herein are included in uplink signals (i.e., UL signals).

[0042] The UE operations module 124 may provide information 148 to one or more receivers 120. For example, the UE operations module 124 may inform a receiver 120 when to receive a retransmission.

[0043] UE operations module 124 may provide information 138 to demodulator 114. For example, UE operations module 124 may inform demodulator 114 of the modulation pattern expected for transmissions from gNB 160.

[0044] The UE operations module 124 may provide information 136 to the decoder 108. For example, the UE operations module 124 may inform the decoder 108 of the coding to be expected for the transmission from the gNB 160.

[0045] The UE operation module 124 may provide information 142 to the encoder 150. The information 142 may include data to be encoded and / or instructions for encoding. For example, the UE operation module 124 may instruct the encoder 150 to encode the transmit data 146 and / or other information 142. The other information 142 may include PDSCH HARQ-ACK information.

[0046] The encoder 150 may encode transmit data 146 and / or other information 142 provided by the UE operations module 124. For example, encoding the data 146 and / or other information 142 may involve error detection and / or correction coding, mapping the data to spatial, time, and / or frequency resources for transmission, multiplexing, etc. The encoder 150 may provide the encoded data 152 to a modulator 154.

[0047] UE operations module 124 may provide information 144 to modulator 154. For example, UE operations module 124 may inform modulator 154 of the modulation type (e.g., constellation mapping) to be used for transmission to gNB 160. Modulator 154 may modulate coded data 152 to provide one or more modulated signals 156 to one or more transmitters 158.

[0048] UE operations module 124 may provide information 140 to one or more transmitters 158. The information 140 may include instructions for one or more transmitters 158. For example, UE operations module 124 may instruct one or more transmitters 158 when to transmit signals to gNB 160. For example, one or more transmitters 158 may transmit during a UL subframe. One or more transmitters 158 may upconvert the modulated signal 156 and transmit the modulated signal to one or more gNB 160.

[0049] Each of the one or more gNBs 160 may include one or more transceivers 176, one or more demodulators 172, one or more decoders 166, one or more encoders 109, one or more modulators 113, a data buffer 162, and a gNB operations module 182. For example, one or more receive paths and / or transmit paths may be implemented in the gNB 160. For convenience, only a single transceiver 176, decoder 166, demodulator 172, encoder 109, and modulator 113 are illustrated in the gNB 160, but multiple parallel elements (e.g., multiple transceivers 176, decoders 166, demodulators 172, encoders 109, and modulators 113) may be implemented.

[0050] The transceiver 176 may include one or more receivers 178 and one or more transmitters 117. The one or more receivers 178 may receive signals from the UE 102 using one or more physical antennas 180a-n. For example, the receiver 178 may receive and downconvert a signal to produce one or more received signals 174. The one or more received signals 174 may be provided to the demodulator 172. The one or more transmitters 117 may transmit signals to the UE 102 using one or more physical antennas 180a-n. For example, the one or more transmitters 117 may upconvert and transmit one or more modulated signals 115.

[0051] The demodulator 172 may demodulate one or more received signals 174 to produce one or more demodulated signals 170. The one or more demodulated signals 170 may be provided to the decoder 166. The gNB 160 may use the decoder 166 to decode the signals. The decoder 166 may generate one or more decoded signals 164, 168. For example, the signal 164 decoded by the first gNB may include received payload data, which may be stored in the data buffer 162. The signal 168 decoded by the second gNB may include overhead data and / or control data. For example, the signal 168 decoded by the second gNB may provide data (e.g., PDSCH HARQ-ACK information) that the gNB operations module 182 may use to perform one or more operations.

[0052] Generally speaking, the gNB operations module 182 may enable the gNB 160 to communicate with one or more UEs 102. The gNB operations module 182 may include one or more gNB scheduling modules in a gNB scheduling module 194. The gNB scheduling module 194 may perform scheduling of downlink and / or uplink transmissions as described herein.

[0053] The gNB operations module 182 may provide information 188 to the demodulator 172. For example, the gNB operations module 182 may inform the demodulator 172 of the modulation pattern expected for transmissions from the UE 102.

[0054] The gNB operations module 182 may provide information 186 to the decoder 166. For example, the gNB operations module 182 may inform the decoder 166 of the encoding to be expected for transmissions from the UE 102.

[0055] gNB operations module 182 may provide information 101 to encoder 109. Information 101 may include data to be encoded and / or instructions for encoding. For example, gNB operations module 182 may instruct encoder 109 to encode information 101, including transmit data 105.

[0056] Encoder 109 may encode transmit data 105 and / or other information included in information 101 provided by gNB operations module 182. For example, encoding transmit data 105 and / or other information included in information 101 may involve error detection and / or correction coding, mapping data to spatial, time, and / or frequency resources for transmission, multiplexing, etc. Encoder 109 may provide encoded data 111 to modulator 113. Transmit data 105 may include network data to be relayed to UE 102.

[0057] The gNB operations module 182 may provide information 103 to the modulator 113. The information 103 may include instructions for the modulator 113. For example, the gNB operations module 182 may inform the modulator 113 of the modulation type (e.g., constellation mapping) to be used for transmission to the UE 102. The modulator 113 may modulate the coded data 111 to provide one or more modulated signals 115 to one or more transmitters 117.

[0058] The gNB operations module 182 may provide information 192 to the one or more transmitters 117. The information 192 may include instructions for the one or more transmitters 117. For example, the gNB operations module 182 may instruct the one or more transmitters 117 when (and when not) to transmit a signal to the UE 102. The one or more transmitters 117 may upconvert the modulated signal 115 and transmit the modulated signal to the one or more UEs 102.

[0059] It should be noted that DL subframes may be transmitted from the gNB 160 to one or more UEs 102, and UL subframes may be transmitted from one or more UEs 102 to the gNB 160. In addition, both the gNB 160 and one or more UEs 102 may transmit data in standard special subframes.

[0060] It should also be noted that one or more of the elements or components thereof included in the eNB 160 and the UE 102 may be implemented in hardware. For example, one or more of these elements or components may be implemented as a chip, a circuit, a hardware component, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in hardware and / or performed using hardware. For example, one or more of the methods described herein may be implemented in and / or implemented using a chipset, an application specific integrated circuit (ASIC), a large-scale integrated circuit (LSI), or an integrated circuit, etc.

[0061] Figure 2 An example of multiple parameters 201 is shown. Figure 2 As shown, multiple parameters 201 (e.g., multiple subcarrier spacings) may be supported. For example, μ (e.g., subcarrier space configuration) and cyclic prefix (e.g., μ and cyclic prefix of a carrier bandwidth portion) may be configured by higher layer parameters (e.g., RRC messages) for downlink and / or uplink. Here, 15 kHz may be a reference parameter 201. For example, REs of the reference parameter 201 may be defined as having a subcarrier spacing of 15 kHz in the frequency domain and a 2048Ts+CP length (e.g., 160Ts or 144Ts) in the time domain, where Ts represents a baseband sampling time unit defined as 1 / (15000*2048) seconds.

[0062] Additionally or alternatively, the number of OFDM symbols per slot may be determined based on μ (eg, subcarrier spatial configuration). Here, for example, time slot configuration 0 (eg, the number 203 of OFDM symbols per time slot may be 14).

[0063] Figure 3 is a diagram illustrating one example of a resource grid 301 and resource blocks 391 (eg, for downlink and / or uplink). Figure 3 The illustrated resource grid 301 and resource block 391 may be used in some implementations of the systems and methods disclosed herein.

[0064] exist Figure 3 In the example, a subframe 369 may include Symbols 387. Additionally or alternatively, a resource block 391 may include multiple resource elements (REs) 389. Here, in the downlink, an OFDM access scheme with a cyclic prefix (CP) may be employed, which may also be referred to as CP-OFDM. A downlink radio frame may include multiple pairs of downlink resource blocks (RBs) 391, which are also referred to as physical resource blocks (PRBs). A downlink RB pair is a unit for allocating downlink radio resources defined by a predetermined bandwidth (RB bandwidth) and time slot. A downlink RB pair may include two downlink RBs 391 that are consecutive in the time domain. Additionally or alternatively, a downlink RB 391 may include twelve subcarriers in the frequency domain and seven (for normal CP) or six (for extended CP) OFDM symbols in the time domain. The region defined by one subcarrier in the frequency domain and one OFDM symbol in the time domain is called a resource element (RE) 389 and is uniquely identified by an index pair (k, l), where k and l are indices in the frequency domain and time domain, respectively.

[0065] In addition or alternatively, in the uplink, in addition to CP-OFDM, a single-carrier frequency division multiple access (SC-FDMA) access scheme may be adopted, which is also called discrete Fourier transform spread OFDM (DFT-S-OFDM). An uplink radio frame may include multiple pairs of uplink resource blocks 391. An uplink RB pair is a unit for allocating uplink radio resources defined by a predetermined bandwidth (RB bandwidth) and time slot. An uplink RB pair may include two uplink RBs 391 that are consecutive in the time domain. An uplink RB may include twelve subcarriers in the frequency domain and seven (for normal CP) or six (for extended CP) OFDM / DFT-S-OFDM symbols in the time domain. The region defined by one subcarrier in the frequency domain and one OFDM / DFT-S-OFDM symbol in the time domain is called a resource element (RE) 389 and is uniquely identified by an index pair (k, l) in a time slot, where k and l are indices in the frequency domain and time domain, respectively.

[0066] Each element in the resource grid 301 (eg, antenna port p) and subcarrier configuration p is referred to as a resource element 389 and is uniquely identified by an index pair (k, l), where k=0, ..., is an index in the frequency domain, and 1 refers to the symbol position in the time domain. The resource element (k, l) 389 on antenna port p and subcarrier spacing configuration μ is denoted as (k, l) p, μ. The physical resource block 391 is defined as The physical resource block 391 is from 0 to Number. Physical resource block number n in the frequency domain PRBThe relationship between the resource element (k, l) is given by given.

[0067] In NR, the following reference signals can be defined: NZP CSI-RS (Non-Zero Power Channel State Information Reference Signal) ZP CSI-RS (Zero Power Channel State Information Reference Signal) DMRS (Demodulation Reference Signal) SRS (Sounding Reference Signal)

[0068] NZP CSI-RS can be used for channel tracking (e.g., synchronization), CSI measurements (including channel and interference measurements), and / or beamforming performance measurements. NZP CSI-RS can be transmitted in the downlink (gNB to UE). NZP CSI-RS can be transmitted aperiodically, semi-persistently, or periodically. Furthermore, NZP CSI-RS can be used for radio resource management (RRM) and radio link control (RLM) measurements.

[0069] The ZP CSI-RS can be used for interference measurement and is transmitted in the downlink (gNB to UE). The ZP CSI-RS can be transmitted aperiodically, semi-persistently, or periodically.

[0070] DMRS can be used for demodulation of downlink (gNB to UE), uplink (UE to gNB), and sidelink (UE to UE).

[0071] SRS can be used for channel sounding and beam management. SRS can be transmitted in the uplink (UE to gNB).

[0072] In some methods, DCI may be used. The following DCI formats may be defined: DCI format 0_0 DCI format 0_1 DCI format 0_2 DCI format 1_0 DCI format 1_1 DCI format 1_2 DCI format 2_0 DCI format 2_1 DCI format 2_2 DC format 2_3 DCI format 2_4 DCI format 2_5 DCI format 2_6 DCI format 3_0 DCI format 3_1

[0073] DCI format 1_0 can be used for PUSCH scheduling in one cell. DCI can be transmitted using DCI format 0_0, which has a cyclic redundancy check (CRC) scrambled by the cell radio network temporary identifier (C-RNTI) or the configured scheduling RNTI (CS-RNTI) or the modulation and coding scheme - cell RNTI (MCS-C-RNTI).

[0074] DCI format 0_1 ​​can be used for scheduling one or more PUSCHs in a cell or for indicating configured grant downlink feedback information (CG-DFI) to the UE. DCI can be transmitted using DCI format 0_1, which has a CRC scrambled by C-RNTI, CS-RNTI, semi-persistent channel state information (SP-CSI-RNTI), or MCS-C-RNTI. DCI format 0_2 can be used for CSI requests (e.g., aperiodic CSI reporting or semi-persistent CSI requests). DCI format 0_2 can be used for SRS requests (e.g., aperiodic SRS transmission).

[0075] DCI format 0_2 can be used for PUSCH scheduling in a cell. DCI can be transmitted using DCI format 0_2, which has a CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI. DCI format 0_2 can be used to schedule PUSCH with high priority and / or low latency (e.g., URLLC). DCI format 0_2 can be used for CSI requests (e.g., aperiodic CSI reporting or semi-persistent CSI requests). DCI format 0_2 can be used for SRS requests (e.g., aperiodic SRS transmission).

[0076] In addition, for example, the DCI included in DCI format 0_Y (Y=0, 1, 2, ...) may be a BWP indicator (e.g., for PUSCH). In addition or alternatively, the DCI included in DCI format 0_Y may be a frequency domain resource allocation (e.g., for PUSCH). In addition or alternatively, the DCI included in DCI format 0_Y may be a time domain resource allocation (e.g., for PUSCH). In addition or alternatively, the DCI included in DCI format 0_Y may be a modulation and coding scheme (e.g., for PUSCH). In addition or alternatively, the DCI included in DCI format 0_Y may be a new data indicator. In addition or alternatively, the DCI included in DCI format 0_Y may be a TPC command for a scheduled PUSCH. In addition or alternatively, the DCI included in DCI format 0_Y may be a CSI request for requesting a CSI report. Additionally or alternatively, as described below, the DCI included in DCI format 0_Y may be information indicating the index of the configuration of the configured grant. Additionally or alternatively, the DCI included in DCI format 0_Y may be a priority indication (e.g., for PUSCH transmission and / or for PUSCH reception).

[0077] DCI format 1_0 can be used for PDSCH scheduling in one DL cell. DCI is transmitted using DCI format 1_0, which has a CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI. DCI format 1_0 can be used for a random access procedure initiated by a PDCCH command. In addition or alternatively, DCI can be transmitted using DCI format 1_0, which has a CRC scrambled by a system information RNTI (SI-RNTI), and the DCI can be used for system information transmission and / or reception. In addition or alternatively, DCI can be transmitted using DCI format 1_0, which has a CRC scrambled by a random access RNTI (RA-RNTI) for a random access response (RAR) (e.g., Msg 2) or msgB-RNTI for a 2-step RACH. Additionally or alternatively, DCI may be transmitted with DCI format 1_0, which has a CRC scrambled by a temporary cell RNTI (TC-RNTI), and may be used for msg3 transmission by UE 102 .

[0078] DCI format 1_1 can be used for PDSCH scheduling in one cell. DCI can be transmitted using DCI format 1_1, which has a CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI. DCI format 1_1 can be used for SRS requests (e.g., aperiodic SRS transmission).

[0079] DCI format 1_2 can be used for PDSCH scheduling in a cell. DCI can be transmitted using DCI format 1_2, which has a CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI. DCI format 1_2 can be used to schedule PDSCH with high priority and / or low latency (e.g., URLLC). DCI format 1_2 can be used for SRS requests (e.g., aperiodic SRS transmission).

[0080] In addition, for example, the DCI included in DCI format 1_X may be a BWP indicator (e.g., for PDSCH). In addition or alternatively, the DCI included in DCI format 1_X may be a frequency domain resource allocation (e.g., for PDSCH). In addition or alternatively, the DCI included in DCI format 1_X may be a time domain resource allocation (e.g., for PDSCH). In addition or alternatively, the DCI included in DCI format 1_X may be a modulation and coding scheme (e.g., for PDSCH). In addition or alternatively, the DCI included in DCI format 1_X may be a new data indicator. In addition or alternatively, the DCI included in DCI format 1_X may be a TPC command for a scheduled PUCCH. In addition or alternatively, the DCI included in DCI format 1_X may be a CSI request for requesting (e.g., triggering) the transmission of CSI (e.g., a CSI report (e.g., an aperiodic CSI report)). Additionally or alternatively, the DCI included in DCI format 1_X may be a PUCCH resource indicator. Additionally or alternatively, the DCI included in DCI format 1_X may be a PDSCH-to-HARQ feedback timing indicator. Additionally or alternatively, the DCI included in DCI format 1_X may be a priority indication (e.g., for PDSCH transmission and / or for PDSCH reception). Additionally or alternatively, the DCI included in DCI format 1_X may be a priority indication (e.g., for HARQ-ACK transmission of PDSCH and / or for HARQ-ACK reception of PDSCH).

[0081] DCI format 2_0 can be used to signal the slot format, channel occupancy time (COT) duration for unlicensed band operation, available resource block (RB) sets, and search space group switching. DCI can be transmitted using DCI format 2_0, which has a CRC scrambled by the slot format indicator RNTI (SFI-RNTI).

[0082] DCI format 2_1 may be used to inform the UE that physical resource blocks (PRBs) and orthogonal frequency division multiplexing (OFDM) symbols may be assumed to be not intended for the UE's transmission. DCI is transmitted using DCI format 2_1, which has a CRC scrambled by the interrupt transmission RNTI (INT-RNTI).

[0083] DCI format 2_2 can be used to transmit transmit power control (TPC) commands for PUCCH and PUSCH. The following information is transmitted using DCI format 2_2, which has a CRC scrambled by TPC-PUSCH-RNTI or TPC-PUCCH-RNTI. In the case where the CRC is scrambled by TPC-PUSCH-RNTI, the indicated one or more TPC commands may apply to the TPC cycle of PUSCH. In the case where the CRC is scrambled by TPC-PUCCH-RNTI, the indicated one or more TPC commands may apply to the TPC cycle of PUCCH.

[0084] DCI format 2_3 can be used to transmit a set of TPC commands for SRS transmission by one or more UEs. Along with the TPC commands, an SRS request can also be transmitted. DCI can be transmitted using DCI format 2_3, which has a CRC scrambled by TPC-SRS-RNTI.

[0085] DCI format 2_4 can be used to inform the UE to cancel the PRBs and OFDM symbols in which the corresponding UL transmission is transmitted. DCI can be transmitted using DCI format 2_4, which has a CRC scrambled by a cancellation indication RNTI (CI-RNTI).

[0086] DCI format 2_5 can be used to notify the availability of soft resources for integrated access and backhaul (IAB) operation. DCI can be transmitted using DCI format 2_5, which has a CRC scrambled by the availability indication RNTI (AI-RNTI).

[0087] DCI format 2_6 can be used to inform one or more UEs of power saving information outside of discontinuous reception (DRX) active time. DCI can be transmitted with the help of DCI format 2_6, which has a CRC scrambled by the power saving RNTI (PS-RNTI).

[0088] DCI format 3_0 can be used to schedule the NR physical sidelink control channel (PSCCH) and the NR physical sidelink shared channel (PSSCH) in a cell. DCI can be transmitted using DCI format 3_0, which has a CRC scrambled by the sidelink RNTI (SL-RNTI) or the sidelink configured scheduling RNTI (SL-CS-RNTI). This can be used for vehicle-to-everything (V2X) operations for NR V2X UEs.

[0089] DCI format 3_1 can be used for scheduling LTE PSCCH and LTE PSSCH in a cell. The following information DCI is transmitted using DCI format 3_1, which has a CRC scrambled by SL-L-CS-RNTI. This can be used for LTE V2X operation for LTE V2X UEs.

[0090] UE 102 may monitor one or more DCI formats in a common search space set (CSS) and / or a UE-specific search space set (USS). The set of PDCCH candidates to be monitored by the UE may be defined according to a PDCCH search space set. A search space set may be a CSS set or a USS set. UE 102 may monitor PDCCH candidates in one or more of the following search space sets. The search space may be defined by a PDCCH configuration in the RRC layer.

[0091] Type0-PDCCH CSS set can be set via pdcch-ConfigSIB 1 in MIB or via PDCCH-ConfigCommon searchSpaceSIB 1 in PDCCH-ConfigCommon or searchSpaceZero in PDCCH-ConfigCommon for DCI format configuration of CRC scrambled by SI-RNTI on the primary cell of MCG, Type0A-PDCCH CSS set can be configured via searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for DCI formats with CRC scrambled by SI-RNTI on the primary cell of the MCG, Type 1-PDCCH CSS set can be configured via ra-SearchSpace in PDCCH-ConfigCommon for DCI formats with CRC scrambled by RA-RNTI or TC-RNTI on the primary cell, Type2-PDCCH CSS set can be targeted by pagingSearchSpace in PDCCH-ConfigCommon DCI format configuration of the CRC scrambled by the P-RNTI on the primary cell of the MCG, Type3-PDCCH CSS set can be used to target the INT-RNTI, DCI format configuration with CRC scrambled by SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, or PS-RNTI (and for primary cell only, with CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI), where searchSpaceType=common, and / or The USS set can be targeted by the SearchSpace in PDCCH-Config with C-RNTI, MCS-C-RNTI, DCI with CRC scrambled by SP-CSI-RNTI, CS-RNTI, SL-RNTI, SL-CS-RNTI, or SL-L-CS-RNTI Format configuration, where searchSpaceType=ue-Specific.

[0092] UE 102 may monitor a candidate set of PDCCHs in one or more control resource sets (e.g., CORESETs) on the active DL bandwidth part (BWP) on each activated serving cell according to a corresponding search space set. A CORESET may be configured from gNB 160 to UE 102, and a CSS set and a USS set may be defined in the configured CORESET. One or more CORESETs may be configured in the RRC layer.

[0093] Figure 4 An example of a resource region (e.g., a downlink resource region) is shown. One or more PRB 491 sets 401 (e.g., a control resource set (i.e., CORESET)) can be configured for DL ​​control channel monitoring (e.g., PDCCH monitoring). For example, a CORESET is a set 401 of PRBs 491 in the frequency domain and / or time domain, within which a UE 102 attempts to decode DCI (e.g., DCI format, PDCCH). In the case where the PRBs 491 may or may not be frequency-contiguous and / or time-contiguous, the UE 102 can be configured with one or more control resource sets (e.g., CORESETs), and one DCI message can be mapped within one control resource set. In the frequency domain, a PRB 491 is the resource unit size of a DL control channel (which may or may not include a DM-RS).

[0094] Figure 5 Examples of beamforming and quasi-collocated (QCL) types are illustrated. Figure 5 The gNB 560 and the UE 502 are illustrated. The gNB 560 may be about Figure 1 The example of gNB 160 is described. UE 502 may be about Figure 1 An example of UE 102 is shown. In NR, gNB 560 and UE 502 can perform beamforming by using multiple antenna elements. Beamforming is achieved by using directional antennas or applying a phase shift to each antenna element, thereby achieving high electric field strength in a specific spatial direction. Here, beamforming or beamforming can be rephrased as "spatial domain transmit filter" or "spatial domain filter." In the downlink, the gNB 560 may apply transmit beamforming and transmit DL channels and / or DL ​​signals, and the UE 502 may also apply receive beamforming and receive DL channels and / or DL ​​signals.

[0095] In the uplink, UE 502 may apply transmit beamforming and transmit UL channels and / or UL signals, and gNB 560 may also apply receive beamforming and receive UL channels and / or UL signals.

[0096] The beam correspondence can be defined based on the UE capability. The beam correspondence can be defined based on the following: In the downlink, the UE 502 may determine transmit beamforming for UL channels and / or UL signals based on receive beamforming for DL ​​channels and / or DL ​​signals. In the uplink, the gNB 560 may determine the DL channel based on the receive beamforming for the UL channel and / or UL signal. Transmit beamforming of channels and / or DL ​​signals.

[0097] Beam management may be performed to adaptively switch, refine, or operate beamforming. For beam management, NZP-CSI-RS and SRS may be used to measure channel quality in the downlink and uplink, respectively. Specifically, in the downlink, gNB 560 may transmit one or more NZP CSI-RSs. UE 502 may measure these one or more NZP CSI-RSs. Furthermore, UE 502 may change beamforming to receive each NZP CSI-RS. UE 502 may identify which combination of gNB-side transmit beamforming corresponds to the UE-side receive beamforming for the NZP CSI-RS. In the uplink, UE 502 may transmit one or more SRSs. gNB 560 may measure these one or more SRSs. Furthermore, gNB 560 may change receive beamforming to receive each SRS. gNB 560 may identify which combination of gNB-side transmit beamforming corresponds to the gNB-side receive beamforming for the SRS.

[0098] To maintain a transmit beam and receive link for communication between gNB 560 and UE 502, a quasi-co-location (QCL) assumption can be defined. Two antenna ports are said to be quasi-co-located if the large-scale properties of the channel over which the symbols on one antenna port are transmitted are inferred from the channel over which the symbols on the other antenna port are transmitted. The large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and / or spatial Rx parameters. The following QCL types can be defined: QCL Type A (“QCL-Type A”): {Doppler shift, Doppler spread, average delay, delay spread} QCL Type B (“QCL-TypeB”): {Doppler shift, Doppler spread} QCL Type C (“QCL-Type C”): {Doppler shift, average delay} QCL Type D (“QCL-TypeD”) {Spatial Rx parameters}

[0099] QCL type D is related to beam management. For example, two NZP CSI-RS resources are configured for UE 502, and NZP CSI-RS resource #1 and NZP CSI-RS resource #2 are used for beam #1 and beam #2, respectively. On the UE side, Rx beam #1 is used for the reception of NZP CSI-RS #1, and Rx beam #2 is used for the reception of NZP CSI-RS #2 for beam management. Here, NZP CSI-RS resource #1 and NZP CSI-RS resource #2 refer to Tx beam #1 and Tx beam #2, respectively. The QCL type D assumption can be used for PDCCH and PDSCH and DL signal reception. When UE 502 receives PDCCH using the QCL type D assumption with NZP CSI-RS #1, UE 502 can use Rx beam #2 for PDCCH reception.

[0100] To this end, the gNB 560 may configure a Transmit Configuration Indication (TCI) state to the UE 502. The TCI state may include: One or more reference resource indexes; and / or • The QCL type of each index in the one or more reference resource indexes.

[0101] For example, if the TCI state includes QCL type D and NZP CSI-RS #1 and is indicated to the UE 502, the UE 502 may apply Rx beam #1 to the reception of the PDCCH, PDSCH, and / or DL ​​signals. In other words, the UE 502 may determine the reception beam to be used for the reception of the PDCCH, PDSCH, and / or DL ​​signals by using the TCI state.

[0102] Figure 6 An example of a TCI state is shown. Seven TCI states can be configured, and one of the configured TCI states can be used to receive PDCCH, PDSCH, and / or DL ​​signals. For example, if gNB 560 indicates TCI state #1, UE 502 can assume that the PDCCH, PDSCH, and / or DL ​​signals are quasi-colocated with the NZP CSI-RS corresponding to NZP CSI-RS resource #1. When UE 502 receives the NZP CSI-RS corresponding to NZP CSI-RS resource #1, UE 502 can determine to use a receive beam.

[0103] Next, how to indicate a TCI state from gNB 560 to UE 502. In an RRC message, N TCI states can be configured by the RRC message. gNB 560 can indicate one of the configured TCI states via DCI (e.g., DCI format 1_1 or DCI format 1_2). Alternatively or in addition, gNB 560 can indicate one of the configured TCI states via a MAC CE. Alternatively or in addition, the MAC CE selects more than one TCI state from the configured TCI states, and the DCI indicates one of the more than one TCI states activated by the MAC CE.

[0104] Here, an example of configuring a common beam for PDCCH and PDSCH is described. As an example, a gNB (e.g., gNB 160 and / or gNB 560) may transmit information for configuring a common beam configuration for PDCCH and PDSCH to a UE (e.g., UE 102 and / or UE 502). As used herein, "common beam" may refer to a shared beam or a shared beam (e.g., a beam common to multiple channels). Information for configuring the common beam for PDCCH and PDSCH may be transmitted via RRC signaling. When a gNB (e.g., gNB 160 and / or gNB 560) configures a common beam for PDCCH and PDSCH, a MAC CE may activate a TCI state, and the UE (e.g., UE 102 and / or UE 502) may receive the PDCCH and PDSCH based on the activated TCI state. For example, a UE (e.g., UE 102 and / or UE 502) may receive a PDCCH and a PDSCH using the same receive beam as used to receive a reference signal in an activated TCI state. A common beam configuration may be configured such that the same receive beam is used to receive one or more PDCCHs and / or one or more PDSCHs. A common beam may be defined as a common TCI or a common QCL.

[0105] Alternatively or in addition, when a UE (e.g., UE 102 and / or UE 502) is configured with DL carrier aggregation (e.g., more than one DL serving cell is configured), a common beam (e.g., one TCI state) may be applied to receive the PDCCH and / or PDSCH for one or more of the configured serving cells. For example, when two DL serving cells (cell #1 and cell #2) and a common beam configuration are configured for a UE (e.g., UE 102 and / or UE 502) and the common beam configuration is applied to cell #1 and cell #2, the UE may receive the PDCCH on cell #1 and the PDCCH on cell #2 based on the TCI state activated by the MAC CE or indicated by the DCI. For example, the UE may receive the PDCCH on cell #1 and the PDCCH on cell #2 using the same receive beam as the reference signal included in the TCI state activated by the MAC CE or indicated by the DCI. The TCI state may be indicated by the TCI field in DCI format 1_1 or DCI format 1_2. The reference signal may correspond to QCL type D.

[0106] As an example, when a UE (e.g., UE 102 and / or UE 502) receives information for configuring a common beam configuration for two DL serving cells (cell #1 and cell #2), UE 102 may receive the PDCCH on cell #1 and the PDCCH on cell #2 based on the activated TCI state or the TCI state indicated by the DCI. For example, the UE may receive the PDSCH on cell #1 and the PDSCH on cell #2 using the same receive beam as the reference signal included in the TCI state activated by the MAC CE or indicated by the DCI. The TCI state may be indicated by the TCI field in the DCI format. The TCI state may be activated by the MAC CE.

[0107] Alternatively or in addition, when more than one DL serving cell is configured, the serving cell group may be configured to apply a common beam to receive multiple PDCCHs and / or multiple PDSCHs on cells within the serving cell group. The more than one DL serving cell may include a primary cell (PCell) or a primary secondary cell (SPCell) and one or more DL secondary cells (SCells). Configuring one or more SCells can be rephrased as configuring more than one serving cell.

[0108] Alternatively or in addition, the common beam configuration may be configured separately for each physical channel. For example, a configuration for configuring a common beam configuration for the PDCCH and a configuration for configuring a common beam configuration for the PDSCH may be configured for a serving cell group. Alternatively or in addition, the common beam configuration may include a combination of one or more downlink channels and downlink serving cell / downlink serving cell index information for configuring a common beam configuration for the PDCCH, and / or information for configuring a common beam configuration for the PDSCH may be configured in the RRC.

[0109] The common beam configuration for the PDSCH may be included in the PDSCH configuration (PDSCH-Config or PDSCH-ConfigCommon). The common beam configuration for the PDCCH may be included in the PDCCH configuration (PDCCH-Config or PDCCH-ConfigCommon).

[0110] The TCI state set for the PDSCH can be configured in the RRC, and the TCI state set for the PDCCH can be configured as a subset of the TCI state set for the PDSCH. For the PDCCH TCI state, one TCI state from the configured TCI states for the PDCCH can be activated by a MAC CE. For the PDSCH, one or more TCI states from the configured TCI states for the PDCCH can be activated by a MAC CE. If more than one TCI state is activated, the TCI field in the DCI scheduling the PDSCH can indicate a TCI state for PDSCH reception. If the TCI field is configured, the UE 102 can receive the PDSCH based on the TCI value of the TCI field in the DCI. The UE 102 can receive the same receive beam for the PDSCH as for the reference signal included in the indicated TCI state corresponding to the value of the TCI field in the DCI (e.g., DCI format 1_1 or DCI format 1_2).

[0111] As another example, a UE (e.g., UE 102 and / or UE 502) may receive information for configuring a common beam configuration and information for configuring one or more secondary cells, and may receive PDSCH #1 on cell #1 (e.g., PCell) and PDSCH #2 on cell #2 (e.g., SCell). The information for configuring the common beam configuration may indicate whether the same spatial domain filter is used for reception of PDSCH #1 and PDSCH #2. For example, a gNB (e.g., gNB 160 and / or gNB 560) may transmit information for configuring a common beam configuration and information for configuring one or more secondary cells, and may transmit PDSCH #1 on cell #1 (e.g., PCell) and PDSCH #2 on cell #2 (e.g., SCell). The information for configuring the common beam configuration may indicate whether a single TCI state is applied to PDSCH #1 and PDSCH #2.

[0112] An example of a common beam configuration for an uplink signal or channel (e.g., uplink common TCI) is described. When the common beam configuration is configured, UE 102 may apply the same transmit beam for both PUSCH and PUCCH. For example, a UE (e.g., UE 102 and / or UE 502) may be configured with a common beam configuration for PUSCH and PUCCH. In addition or alternatively, when multiple uplink serving cells are configured (e.g., UL CA), the common beam configuration may be applied to PUSCH and / or PUCCH for one or more uplink serving cells. For example, when two uplink serving cells (cell #1 and cell #2) are configured and the common beam configuration is configured to a UE (e.g., UE 102 and / or UE 502), the UE may apply the same transmit beam for PUSCH on cell #1 and cell #2 as the transmit beam used for PUSCH on cell #1.

[0113] In addition or alternatively, the spatial domain filter (e.g., transmit beam) used for the PUSCH may be associated with the spatial domain filter used for the SRS resource. The UE (e.g., UE 102 and / or UE 502) may be configured with information about the spatial domain filter via the RRC parameter SRS-SpatialRelationInfo. In the parameter SRS-SpatialRelationInfo, the spatial domain filter used for the SRS resource may be associated with the SS / PBCH block, NZP CSI-RS, and / or SRS resource configured via information received in the RRC layer. The parameter SRS-SpatialRelationInfo may include a serving cell index. For each SRS resource configuration, one or more parameters SRS-SpatialRelationInfo may be included. The transmit beam (e.g., spatial domain filter) used for the PUSCH may be determined based on the transmit beam of the SRS resource configured via RRC. The UE (e.g., UE 102 and / or UE 502) may apply the same spatial domain transmit filter for the PUSCH as the spatial domain transmit filter for the configured SRS resource. The UE (e.g., UE 102 and / or UE 502) may apply the same spatial domain transmit filter for the PUSCH as the spatial domain transmit filter for the activated SRS resources. The UE (e.g., UE 102 and / or UE 502) may apply the same spatial domain transmit filter for the PUSCH as the spatial domain transmit filter for the SRS resources indicated by the DCI (e.g., DCI format 0_1 ​​or DCI format 0_2). The SRI field in the DCI may indicate the spatial domain filter for PUSCH transmission and / or PUCCH transmission. The DCI that schedules the PDSCH (e.g., DCI format 1_0, 1_1, or 1_2) may be used to determine the reception of the PDSCH, PUSCH, and / or PUCCH. The DCI that schedules the PUSCH (e.g., DCI format 0_0, 0_1, or 0_2) may be used to determine the reception of the PUSCH, PDSCH, and / or PUCCH.

[0114] Common beam configurations can be configured separately for uplink signals / channels and downlink signals / channels. For example, a common beam configuration for PDCCH / PDSCH and a common beam configuration for PUSCH / PUCCH can be configured.

[0115] This example illustrates a case where UE 102 has beam-matching capabilities (e.g., common beams for DL ​​and UL). When a UE (e.g., UE 102 and / or UE 502) has beam-matching capabilities, the UE can infer or estimate the transmit beam from the receive beam used for downlink channels and / or signals.

[0116] As an example, a gNB (gNB 160 and / or gNB 560) may transmit information for configuring a common beam configuration (e.g., a UE may receive the information for configuring the common beam configuration). When a UE (e.g., UE 102 and / or UE 502) receives the information for configuring the common beam configuration, the UE may use the same spatial filter for transmission of PUSCH, PUCCH, and / or uplink signals as used for reception of PDCCH, PDSCH, and / or downlink signals. For example, if a common beam configuration is configured for a UE (e.g., UE 102 and / or UE 502), the UE may apply the same spatial filter for transmission of PUCCH or PUSCH as used for reception of PDCCH.

[0117] Additionally or alternatively, common beam configurations may be configured individually based on channel and signal combinations. For example, a first common beam configuration may indicate a common spatial domain filter for a combination of a receive beam for the PDCCH on cell #1, a receive beam for the PDSCH on cell #1, and a transmit beam for the PUCCH on cell #1. A second common beam configuration may include a receive beam for the PDSCH on cell #1, a transmit beam for the PDSCH on cell #2, and a transmit beam for the PUCCH on cell #1.

[0118] Additionally or alternatively, a common beam configuration may be configured to apply spatial domain filters to all channels and signals for DL ​​and UL on one or more cells.

[0119] Additionally or alternatively, each TCI state may include a downlink signal (e.g., SS / PBCH block or NZP CSI-RS) or an uplink signal (e.g., SRS resource). If the TCI state includes an uplink signal, the same spatial domain filter as that used for transmission corresponding to the indicated SRS resource may be used.

[0120] As mentioned above, the description includes examples of UE specific implementations where a MAC CE or DCI indicates a TCI state to change the spatial domain filter for a downlink channel / signal and / or an uplink channel / signal.

[0121] As another example, a gNB (e.g., gNB 160 and / or gNB 560) may indicate a TCI state that includes DL TCI and UL spatial relationship information (e.g., a joint indication of DL and UL beams). For example, each TCI state may include: 1) one or more combinations of downlink reference signals and corresponding QCL types (A, B, C, or D) for DL ​​receive beams; and / or 2) spatial relationship of PUSCH or PUCCH. The spatial relationship of PUSCH may be associated with each SRS resource. The spatial relationship of PUCCH may be configured via RRC, activated via MAC CE, or indicated via DCI.

[0122] Additionally or alternatively, the RRC information may indicate one or more combinations of DL TCI states and UL spatial relation parameters. Each combination may include one or more (M) DL TCI states and one or more (N) UL spatial relation parameters. Each DL TCI state may include one or more DL reference signals (e.g., SS / PBCH block index and / or NZP-CSI-RS index) and a corresponding QCL type. Each UL spatial relation parameter may include one or more reference signals (e.g., SS / PBCH block index, NZP CSI-RS index, and / or SRS resource index). The UL spatial relation parameter may be referred to as UL TCI. A MAC CE may activate one DL TCI and one UL TCI.

[0123] When the TCI field in the DCI is not configured, the combination of DL TCI and UL TCI corresponding to the TCI state for the PDCCH can be applied to the reception of the PDCCH, the scheduled PDSCH, and the transmission of the PUSCH. The combination of DL TCI and UL TCI can be configured for each CORESET configuration. If the duration between the PDSCH and the scheduled PDSCH is less than the configured threshold (timeDurationQCL) in the RRC, the combination of DL TCI and UL TCI can be the combination of DL TCI and UL TCI associated with the monitored search space with the lowest CORESETID.

[0124] The configuration of joint TCI can indicate one or more combinations, and each combination can include a downlink transmission configuration indication (TCI) and an uplink transmission configuration indication (TCI). Information about the presence of the TCI field in the DCI scheduling and the duration threshold (e.g., timeDurationQCL) between the PDCCH and PDSCH can be configured.

[0125] If the TCI field is present by configuring the presence of the TCI field and the duration between the PDCCH and the PDSCH is equal to or greater than the duration threshold, the UE (e.g., UE 102 and / or UE 502) may transmit PUSCH or PUCCH based on the TCI state corresponding to the value of the TCI field in the DCI.

[0126] If the TCI field is present by configuring the presence of the TCI field and the duration between the PDCCH and the PDSCH is equal to or greater than the duration threshold, the UE (e.g., UE 102 and / or UE 502) may transmit PUSCH or PUCCH based on a combination of DL TCI and UL TCI corresponding to the value of the TCI field in the DCI.

[0127] If the TCI field is not present, either by configuration of the presence of the TCI field or by no configuration of the presence of the TCI field, and the duration between the PDCCH and the PDSCH is equal to or greater than the duration threshold, the UE (e.g., UE 102 and / or UE 502) may transmit a PUSCH or PUCCH based on a combination of the DL TCI and the UL TCI corresponding to the control resource set (CORESET) for the PDCCH.

[0128] If the duration between the PDCCH and the PDSCH is less than the duration threshold, the UE (e.g., UE 102 and / or UE 502) may transmit a PUSCH or PUCCH based on a combination of the DL TCI and the UL TCI corresponding to the control resource set (CORESET) in which the monitored search space has the lowest index among the CORESET indices.

[0129] In the above description, "DL TCI" may be information on reception of PDSCH, PDCCH and / or downlink reference signal, and "UL TCI" may be information on transmission of PUSCH, PUCCH and / or uplink reference signal.

[0130] In the above description, "A is configured for the UE" (e.g., UE 102 and / or UE 502) may mean that the gNB (e.g., gNB 160 and / or gNB 560) transmits information for configuring A in RRC and the UE receives the information for configuring A in RRC. "The UE is configured with A" may mean that the gNB (e.g., gNB 160 and / or gNB 560) transmits information for configuring A in RRC and the UE (e.g., UE 102 and / or UE 502) receives the information for configuring A in RRC. In some examples, one or more of the above implementations may also apply a semi-persistent PDSCH or a grant for configuration of a PUSCH.

[0131] Figure 7 7 is a flowchart illustrating an example of a method 700 for joint beam management. A UE (e.g., UE 102 and / or UE 502) may receive (702) first information, second information, and / or third information. The UE may receive (704) a PDCCH and a PDSCH. The UE may transmit a PUCCH. The first information may indicate one or more combinations. Each combination may include a downlink TCI and an uplink TCI. The second information may indicate whether the presence of a TCI field in a DCI carried by the PDCCH is configured. The third information may indicate a duration threshold between the PDCCH and the PDSCH. When the TCI field in the DCI is present and the duration between the PDCCH and the PDSCH is equal to or greater than the duration threshold, the PUCCH may be transmitted based on a first combination corresponding to the TCI field in the DCI. When the TCI field in the DCI is not present and the duration between the PDCCH and the PDSCH is equal to or greater than the duration threshold, the PUCCH may be transmitted based on a second combination corresponding to a CORESET of the PDCCH. In case that the duration between the PDCCH and the PDSCH is less than the duration threshold, the PUCCH may be transmitted based on a third combination corresponding to a CORESET in which a monitored search space has a lowest index among the CORESET indices.

[0132] Figure 8800 is a flowchart illustrating an example of a method 800 for joint beam management. A base station device (e.g., gNB 160 and / or gNB 560) may transmit (802) first information, second information, and / or third information. The base station device may transmit (804) a PDCCH and a PDSCH. The base station may receive (806) a PUCCH. The first information may indicate one or more combinations. Each combination may include a downlink time-based access (TCI) and an uplink time-based access (TCI). The second information may indicate whether a TCI field in a DCI carried by the PDCCH is configured. The third information may indicate a duration threshold between the PDCCH and the PDSCH. If the TCI field in the DCI is present and the duration between the PDCCH and the PDSCH is equal to or greater than the duration threshold, the PUCCH may be received based on a first combination corresponding to the TCI field in the DCI. If the TCI field in the DCI is not present and the duration between the PDCCH and the PDSCH is equal to or greater than the duration threshold, the PUCCH may be received based on a second combination corresponding to a control resource set (CORESET) of the PDCCH. In case that the duration between the PDCCH and the PDSCH is less than the duration threshold, the PUCCH may be received based on a third combination corresponding to a CORESET in which a monitored search space has a lowest index among the CORESET indices.

[0133] Figure 9 9 illustrates various components that may be used in UE 902. Figure 9 The UE 902 described may be configured in accordance with Figure 1 UE 102 described and / or in combination Figure 5 UE 502 described herein may be implemented. UE 902 includes a processor 903 that controls the operation of UE 902. Processor 903 may also be referred to as a central processing unit (CPU). Memory 905 (which may include read-only memory (ROM), random access memory (RAM), a combination of these two memories, or any type of device that can store information) provides instructions 907a and data 909a to processor 903. A portion of memory 905 may also include non-volatile random access memory (NVRAM). Instructions 907b and data 909b may also reside in processor 903. The instructions 907b and / or data 909b loaded into processor 903 may also include instructions 907a and / or data 909a from memory 905, which are loaded for execution or processing by processor 903. Instructions 907b may be executed by processor 903 to implement one or more of the methods described herein.

[0134] The UE 902 may also include a housing that houses one or more transmitters 958 and one or more receivers 920 to allow for transmission and reception of data. The transmitters 958 and receivers 920 may be combined into one or more transceivers 918. One or more antennas 922a-n are attached to the housing and electrically coupled to the transceiver 918.

[0135] The various components of the UE 902 are coupled together via a bus system 911 (which may include a power bus, a control signal bus, and a status signal bus in addition to a data bus). However, for the sake of clarity, the various buses are not shown in FIG. Figure 9 911. The UE 902 may further include a digital signal processor (DSP) 913 for processing signals. The UE 902 may further include a communication interface 915 that provides a user with access rights to functions of the UE 902. Figure 9 The illustrated UE 902 is a functional block diagram rather than a listing of specific components.

[0136] Figure 10 Illustrate various components that can be utilized in gNB 1060. Figure 10 The gNB 1060 described may be configured in accordance with Figure 1 The gNB 160 described and / or in combination Figure 5 The gNB 1060 described herein may be implemented using the gNB 560. The gNB 1060 includes a processor 1003 that controls the operation of the gNB 1060. The processor 1003 may also be referred to as a central processing unit (CPU). Memory 1005 (which may include read-only memory (ROM), random access memory (RAM), a combination of both, or any other type of device capable of storing information) provides instructions 1007a and data 1009a to the processor 1003. A portion of the memory 1005 may also include non-volatile random access memory (NVRAM). Instructions 1007b and data 1009b may also reside in the processor 1003. The instructions 1007b and / or data 1009b loaded into the processor 1003 may also include instructions 1007a and / or data 1009a from the memory 1005, which are loaded for execution or processing by the processor 1003. The instructions 1007b may be executed by the processor 1003 to implement one or more of the methods described herein.

[0137] The gNB 1060 may also include a housing that houses one or more transmitters 1017 and one or more receivers 1078 to allow for transmission and reception of data. The transmitters 1017 and receivers 1078 may be combined into one or more transceivers 1076. One or more antennas 1080a-n are attached to the housing and electrically coupled to the transceivers 1076.

[0138] The various components of the gNB 1060 are coupled together via the bus system 1011 (which may include a power bus, a control signal bus, and a status signal bus in addition to the data bus). However, for the sake of clarity, the various buses are not shown in the figure. Figure 10 1060 is illustrated as bus system 1011. gNB 1060 may also include a digital signal processor (DSP) 1013 for processing signals. gNB 1060 may also include a communication interface 1015 that provides users with access rights to the functions of gNB 1060. Figure 10 The illustrated gNB 1060 is a functional block diagram rather than a listing of specific components.

[0139] Figure 11 1 is a block diagram illustrating one specific implementation of a UE 1102 in which one or more of the systems and / or methods described herein may be implemented. The UE 1102 includes a transmitting device 1158, a receiving device 1120, and a control device 1124. The transmitting device 1158, the receiving device 1120, and the control device 1124 may be configured to perform a combination of the above. Figure 1 One or more of the functions described above. Figure 9 Illustrated Figure 11 Various other structures can be implemented to achieve Figure 1 For example, the DSP may be implemented by software.

[0140] Figure 12 is a block diagram illustrating one specific implementation of a gNB 1260 in which one or more of the systems and / or methods described herein may be implemented. The gNB 1260 includes a transmitting device 1217, a receiving device 1278, and a control device 1282. The transmitting device 1217, the receiving device 1278, and the control device 1282 may be configured to perform a combination of the above. Figure 1 One or more of the functions described above. Figure 10 Illustrated Figure 12 Various other structures can be implemented to achieve Figure 1 For example, the DSP may be implemented by software.

[0141] Figure 13 is a block diagram illustrating a specific implementation of gNB 1360. gNB 1360 may be combined with Figure 1 gNB160 described and / or in combination Figure 5An example of a gNB 560 is depicted. The gNB 1360 may include a higher layer processor 1323, a DL transmitter 1325, a UL receiver 1333, and one or more antennas 1331. The DL transmitter 1325 may include a PDCCH transmitter 1327 and a PDSCH transmitter 1329. The UL receiver 1333 may include a PUCCH receiver 1335 and a PUSCH receiver 1337.

[0142] The higher layer processor 1323 manages the behavior of the physical layer (UL transmitter and DL receiver) and provides higher layer parameters to the physical layer. The higher layer processor 1323 can obtain transport blocks from the physical layer. The higher layer processor 1323 can send and receive higher layer messages, such as RRC messages and MAC messages, to / from the higher layers of the UE. The higher layer processor 1323 can provide transport blocks to the PDSCH transmitter and provide transmission parameters related to the transport blocks to the PDCCH transmitter.

[0143] The DL transmitter 1325 may multiplex downlink physical channels and downlink physical signals (including reserved signals) and transmit them via the transmit antenna 1331. The UL receiver 1333 may receive and demultiplex the multiplexed uplink physical channels and uplink physical signals via the receive antenna 1331. The PUCCH receiver 1335 may provide UCI to the higher layer processor 1323. The PUSCH receiver 1337 may provide the received transport block to the higher layer processor 1323.

[0144] Figure 14 is a block diagram illustrating one specific implementation of UE 1402. UE 1402 may be a combination of Figure 1 UE 102 and / or in combination with Figure 5 UE 1402 may include a higher layer processor 1423, a UL transmitter 1451, a DL receiver 1443, and one or more antennas 1431. The UL transmitter 1451 may include a PUCCH transmitter 1453 and a PUSCH transmitter 1455. The DL receiver 1443 may include a PDCCH receiver 1445 and a PDSCH receiver 1447.

[0145] The higher layer processor 1423 manages the behavior of the physical layer (DL transmitter and UL receiver) and provides higher layer parameters to the physical layer. The higher layer processor 1423 can obtain transport blocks from the physical layer. The higher layer processor 1423 can send and receive higher layer messages, such as RRC messages and MAC messages, to and from the higher layers of the UE. The higher layer processor 1423 can provide transport blocks to the PUSCH transmitter and provide UCI to the PUCCH transmitter 1453.

[0146] The DL receiver 1443 may receive and demultiplex the multiplexed downlink physical channel and the downlink physical signal via the reception antenna 1431. The PDCCH receiver 1445 may provide DCI to the higher layer processor 1423. The PDSCH receiver 1447 may provide the received transport block to the higher layer processor 1423.

[0147] This article describes a network-controlled repeater (NCR). Coverage is a fundamental aspect of cellular network deployment. Mobile operators rely on different types of network nodes to provide coverage in their deployments. Deployment of conventional full-stack cells is an option, but it may not always be possible (e.g., no backhaul available) or economically viable. Therefore, new types of network nodes have been considered to increase mobile operators' flexibility in their network deployments. For example, integrated access and backhaul (IAB) was introduced in Rel-16 and enhanced in Rel-17 as a new type of network node that does not require a wired backhaul. Another type of network node is the RF repeater, which simply amplifies and forwards any signals it receives. RF repeaters are widely deployed in 2G, 3G, and 4G to supplement the coverage provided by conventional full-stack cells. In Rel-17, RAN4 specifies RF and EMC requirements for such RF repeaters for NR targeting both FR1 and FR2. While RF repeaters offer a cost-effective means of extending network coverage, they have their limitations. RF repeaters simply perform amplification and forwarding operations without considering various factors that can improve performance. Such factors may include information about semi-static and / or dynamic downlink / uplink configurations, adaptive transmitter / receiver spatial beamforming, on-off status, and more. Network-controlled repeaters are an enhancement over traditional RF repeaters, with the ability to receive and process side control information from the network. This side control information allows network-controlled repeaters to perform their amplification and forwarding operations more efficiently. Potential benefits may include mitigation of unnecessary noise amplification, transmission and reception with better spatial directionality, and simplified network integration.

[0148] Figure 15 is an example of a block diagram of a conceptual model of a network controlled repeater (NCR). This document describes the modeling of a network controlled repeater. The network controlled repeater 1528 is as follows: Figure 15The NCR-MT 1521 is modeled as a functional entity that communicates with the gNB 1560 via a control link 1519 (C-link) to exchange information (e.g., at least side control information related to the control of the NCR-Fwd 1522). The C-link 1519 is based on the NRUu interface. The NCR-Fwd 1522 is defined as a functional entity for amplifying and forwarding UL / DL RF signals between the gNB 1560 and the UE 1524 via the backhaul link 1520 and the access link 1523. The behavior of the NCR-Fwd 1522 is controlled based on the side control information received from the gNB 1560. Furthermore, at least one of the NCR-MT's carriers must be within the set of carriers forwarded by the NCR-Fwd 1522 in the same frequency range. And NCR-MT 1521 and NCR-Fwd 1522 operating in the same carrier can be prioritized for research. As a baseline, it is expected that C-link 1519 and backhaul link 1520 (at least when NCR-MT 1521 and NCR-Fwd 1522 operate in the same carrier) will experience the same large-scale channel characteristics, namely, channel characteristics of Type A and Type D (if applicable). Control link 1519 can transmit PDCCH and / or PDSCH with (NCR-specific) RNTI. Backhaul link 1520 can be defined as a resource.

[0149] For backhaul link 1520 and C-link 1519, both fixed beams and adaptive beams (FFS: a mechanism for indicating and determining beams) may be considered for both C-link 1519 and backhaul link 1520 at NCR 1528. Fixed beams refer to situations where the beams used for both C-link 1519 and backhaul link 1520 at NCR 1528 cannot be changed. Whether fixed beams or adaptive beams are supported may be a UE capability. Capability signaling may include parameters indicating whether UE 1524 supports fixed beams and / or adaptive beams for backhaul link 1520 and C-link 1519 of NCR 1528. Whether fixed beams and / or adaptive beams are applied / used / implemented for the backhaul link 1520 and C-link 1519 of the NCR 1528 may be configured / indicated through common / dedicated / UE-specific RRC messages / signaling and / or SI, and / or indicated through L2 signaling (e.g., MAC CE) and / or L1 signaling (e.g., DCI, PDCCH), and / or provided / determined in the specification. The configuration of fixed beams and / or adaptive beams for the backhaul link 1520 and C-link 1519 of the NCR 1528 may be configured / indicated through common / dedicated / UE-specific RRC messages / signaling and / or SI, and / or indicated through L2 signaling (e.g., MAC CE) and / or L1 signaling (e.g., DCI, PDCCH), and / or provided / determined in the specification. The indication of fixed beams and / or adaptive beams for the backhaul link 1520 and C-link 1519 of the NCR 1528 may be configured / indicated via common / dedicated / UE-specific RRC messages / signaling and / or SI, and / or indicated via L2 signaling (e.g., MAC CE) and / or L1 signaling (e.g., DCI, PDCCH), and / or provided / determined in the specification. For example, the beam set for the C-link 1519 and / or backhaul link 1520 may be configured via RRC messages / signaling, and the beams used by the C-link 1519 and / or backhaul link 1520 may be indicated via MAC messages / signaling (e.g., MAC CE). In another example, the beam set used for the C-link 1519 and / or the backhaul link 1520 may be configured via RRC messaging / signaling, and a subset of beams (from the set) used for the C-link 1519 and / or the backhaul link 1520 may be indicated / activated via MAC messaging / signaling (e.g., MAC CE), and then the beams (from the subset) used by the C-link 1519 and / or the backhaul link 1520 may be indicated via L1 messaging / signaling (e.g., PDCCH, DCI).

[0150] The maximum number of beams associated with the backhaul link 1520 of the NCR 1528 may be a UE capability. Capability signaling (e.g., csi-ReportFramework, csi-ReportFrameworkExt-NCR) may include a parameter (e.g., maxNumberBeams-NCR-backhaul) indicating the maximum number of beams associated with the backhaul link 1520 of the NCR 1528. Whether the maximum number of beams associated with the backhaul link 1520 of the NCR 1528 is applied / used / implemented and / or the maximum value of supported beams associated with the backhaul link 1520 of the NCR 1528 may be configured / indicated through common / dedicated / UE-specific RRC messages / signaling and / or SI, and / or indicated through L2 signaling (e.g., MAC CE) and / or L1 signaling (e.g., DCI, PDCCH), and / or provided / determined in the specification.

[0151] The maximum number of beams associated with the C-link 1519 of the NCR 1528 may be a UE capability. Capability signaling (e.g., csi-ReportFramework, csi-ReportFrameworkExt-NCR) may include a parameter (e.g., maxNumberBeams-NCR-control) indicating the maximum number of beams associated with the C-link 1519 of the NCR 1528. Whether the maximum number of beams associated with the C-link 1519 of the NCR 1528 is applied / used / implemented and / or the maximum value of supported beams associated with the C-link 1519 of the NCR 1528 may be configured / indicated via common / dedicated / UE-specific RRC messages / signaling and / or SI, and / or indicated via L2 signaling (e.g., MAC CE) and / or L1 signaling (e.g., DCI, PDCCH), and / or provided / determined in the specification.

[0152] As a baseline, if the carriers of the NCR-MT are within the set of carriers forwarded by NCR-Fwd 1522, the TCI state of the beam used for backhaul link 1520 at NCR-Fwd 1522 is assumed to be the same as the TCI state of C-link 1519 (FFS: an additional indication from gNB 1560 to determine the beam used for backhaul link 1520 at NCR-Fwd 1522 or implicitly determine the beam used for backhaul link 1520 at NCR-Fwd 1522). The same assumption of beam correspondence is applied to the DL / UL of backhaul link 1520 at NCR-Fwd 1522 as the DL / UL of C-link 1519 at NCR-MT 1521. In yet another design, C-link 1519 and backhaul link 1520 may use different TCI states and / or beams. Whether to support the same TCI state (beam) or different TCI states for the C-link 1519 and the backhaul link 1520 may be a UE capability. Capability signaling may include parameters indicating whether the UE 1524 supports the same TCI state (beam) or different TCI states for the C-link 1519 and the backhaul link 1520 of the NCR 1528. Whether the same TCI state (beam) or different TCI states are applied / used / implemented for the C-link 1519 and the backhaul link 1520 of the NCR 1528 may be configured / indicated via common / dedicated / UE-specific RRC messages / signaling and / or SI, and / or indicated via L2 signaling (e.g., MAC CE) and / or L1 signaling (e.g., DCI, PDCCH), and / or provided / determined in the specification. The configuration of the same state (beam) or different TCI states for the C-link 1519 and the backhaul link 1520 for the NCR 1528 may be configured / indicated through common / dedicated / UE-specific RRC messages / signaling and / or SI, and / or indicated through L2 signaling (e.g., MAC CE) and / or L1 signaling (e.g., DCI, PDCCH), and / or provided / determined in the specification. The indication of the same state (beam) or different TCI states for the C-link 1519 and the backhaul link 1520 for the NCR 1528 may be configured / indicated through common / dedicated / UE-specific RRC messages / signaling and / or SI, and / or indicated through L2 signaling (e.g., MAC CE) and / or L1 signaling (e.g., DCI, PDCCH), and / or provided / determined in the specification. For example, the beam set used for the C-link 1519 and / or the backhaul link 1520 may be configured via RRC messaging / signaling, and the beam used by the C-link 1519 and / or the backhaul link 1520 may be indicated via MAC messaging / signaling (e.g., MAC CE).In another example, the beam set used for the C-link 1519 and / or the backhaul link 1520 may be configured via RRC messaging / signaling, and a subset of beams (from the set) used for the C-link 1519 and / or the backhaul link 1520 may be indicated / activated via MAC messaging / signaling (e.g., MAC CE), and then the beams (from the subset) used by the C-link 1519 and / or the backhaul link 1520 may be indicated via L1 messaging / signaling (e.g., PDCCH, DCI).

[0153] For the access link 1523, beam information is beneficial and is recommended as side control information of the network-controlled relay to control the behavior of the NCR at least for the access link 1523. The beam correspondence is assumed for the DL / UL of the access link at NCR-Fwd 1522. In the access link beam indication, the access link beam can be indicated by the beam index (associated with the corresponding time domain resource of the beam) and / or the index of the source RS (for example, an indicator similar to TCI). For the beam of the access link 1523 used in NCR-Fwd1522, both dynamic indication and semi-static indication can be considered. Whether to support the access link beam indication implemented by the beam index and / or the index of the source RS may be a UE capability. The capability signaling may include a parameter indicating whether the UE supports the access link beam indication implemented by the beam index and / or the index of the source RS. Whether to apply / use / implement the access link beam indication achieved by the beam index and / or the index of the source RS may be configured / indicated by a common / dedicated / UE-specific RRC message / signaling and / or SI, and / or indicated by L2 signaling (e.g., MAC CE) and / or L1 signaling (e.g., DCI, PDCCH), and / or provided / determined in the specification. The configuration of the access link beam indication achieved by the beam index and / or the index of the source RS may be configured / indicated by a common / dedicated / UE-specific RRC message / signaling and / or SI, and / or indicated by L2 signaling (e.g., MAC CE) and / or L1 signaling (e.g., DCI, PDCCH), and / or provided / determined in the specification. The indication of the beams used for the access link 1523 of the NCR 1528 may be configured / indicated via common / dedicated / UE-specific RRC messaging / signaling and / or SI, and / or indicated via L2 signaling (e.g., MAC CE) and / or L1 signaling (e.g., DCI, PDCCH), and / or provided / determined in the specification. For example, the beam set used for the access link 1523 may be configured via RRC messaging / signaling, and the beams used by the access link 1523 may be indicated via MAC messaging / signaling (e.g., MAC CE). In another example, the beam set used for the access link 1523 may be configured via RRC messaging / signaling, and a subset of beams used for the access link (from the set) may be indicated / activated via MAC messaging / signaling (e.g., MAC CE), and then the beams used by the access link 1523 (from the subset) may be indicated via L1 messaging / signaling (e.g., PDCCH, DCI).

[0154] The maximum number of beams associated with access link 1523 (e.g., the maximum total number of beams associated with access links for all UEs) may be a UE capability. Capability signaling (e.g., csi-ReportFramework, csi-ReportFrameworkExt-NCR) may include a parameter indicating the maximum number of beams associated with access link 1523 (e.g., maxNumberBeams-accesslink-ForNCR). Whether the maximum number of beams associated with access link 1523 for NCR 1528 and / or the maximum value of supported beams associated with access link 1523 is applied / used / implemented may be configured / indicated via common / dedicated / UE-specific RRC messages / signaling and / or SI, and / or indicated via L2 signaling (e.g., MAC CE) and / or L1 signaling (e.g., DCI, PDCCH), and / or provided / determined in the specification.

[0155] The maximum number of beams associated with the access link 1523 for the NCR UE (e.g., the maximum number of beams associated with the access link for the NCR UE (per NCR UE)) may be a UE capability. Capability signaling (e.g., csi-ReportFramework, csi-ReportFrameworkExt-NCR) may include a parameter indicating the maximum number of beams associated with the access link 1523 for the NCR UE (e.g., maxNumberBeams-PerUEaccesslink-ForNCR). Whether the maximum number of beams associated with the access link for the NCR UE and / or the maximum value of supported beams associated with the access link 1523 for the NCR UE is applied / used / implemented may be configured / indicated via common / dedicated / UE-specific RRC messages / signaling and / or SI, and / or indicated via L2 signaling (e.g., MAC CE) and / or L1 signaling (e.g., DCI, PDCCH), and / or provided / determined in the specification.

[0156] The beam indication for NCR 1528 may include TCI (TCI-like) state configuration, TCI (TCI-like) state / list / table configuration, MAC-CE-based TCI (TCI-like) state activation and / or DCI-based beam indication for C-link and / or backhaul link and / or access link.

[0157] IE TCI state associates one or two DL reference signals with the corresponding quasi co-location (QCL) type. An example of the TCI state information element is shown in Listing 1. ServCellIndex is the serving cell index (which may be an RRC configured with the serving cell configuration (included in the RRC message / signaling for the serving cell configuration)). BWP-Id is the BWP ID (which may be an RRC configured with the BWP configuration (included in the RRC message / signaling for the BWP configuration)) and indicates the DL BWP in which the RS is located. NZP-CSI-RS-ResourceId is the NZP CSI RS resource ID (which may be an RRC configured with the NZP CSIRS resource configuration (included in the RRC message / signaling for the NZP CSI RS resource configuration)). SSB index is the SSB index (which may be an RRC configured with the SSB configuration (included in the RRC message / signaling for the SSB configuration)).

[0158] List 1

[0159] The TCI state of the beam associated with the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 can be configured as the updated / modified IE TCI state. An example of the TCI state information element supporting the beam associated with the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 is shown in Listing 2. Which link (C-link 1519 and / or the backhaul link 1520 and / or the access link 1523) is associated with the TCI state configuration can be indicated by the parameter link. Assuming that the TCI state for the beam of the backhaul link 1520 at the NCR-Fwd 1522 is the same as the TCI state of the C-link 1519, the TCI state configuration for the C-link 1519 or the TCI state configuration for the backhaul link 1520 is provided / needed. NZP-CSI-RS-NCR-ResourceId is an NZP CSI RS resource ID (which may be RRC configured using NZP CSI RS resource configuration within the C-link 1519 and / or backhaul link 1520 and / or access link 1523 (included in RRC message / signaling for NZP CSI RS resource configuration within the C-link 1519 and / or backhaul link 1520 and / or access link 1523)). SSB-NCR-Index is an SSB index (which may be RRC configured using SSB configuration within the C-link 1519 and / or backhaul link 1520 and / or access link 1523 (included in RRC message / signaling for SSB configuration within the C-link 1519 and / or backhaul link 1520 and / or access link 1523)).

[0160] List 2

[0161] The TCI status of beams associated with the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 can be individually configured as updated / modified IE TCI status. Examples of TCI status information elements supporting beams associated with the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 are shown in Listings 3, 4, and 5. The same-as-backhaul-link (same-as-c-link) field indicates whether the TCI status of the beam used for the backhaul link 1520 at the NCR-Fwd 1522 is assumed to be the same as the TCI status of the C-link 1519. NZP-CSI-RS-C-Link-ResourceId and / or NZP-CSI-RS-Backhaul-Link-ResourceId and / or NZP-CSI-RS-Access-Link-ResourceId are NZP CSI RS resource IDs (which may be RRC configured with NZP CSI RS resource configuration within the C-link 1519 and / or backhaul link 1520 and / or access link 1523 (included in RRC message / signaling for NZP CSI RS resource configuration within the C-link 1519 and / or backhaul link 1520 and / or access link 1523)). SSB-C-Link-Index and / or SSB-Backhaul-Link-Index and / or SSB-Access-Link-Index are SSB indices (which may be RRC configured using SSB configuration within the C-link 1519 and / or backhaul link 1520 and / or access link 1523 (included in the RRC message / signaling for SSB configuration within the C-link 1519 and / or backhaul link 1520 and / or access link 1523)).

[0162] List 3

[0163] List 4

[0164] List 5

[0165] RRC signaling / messages may provide TCI state / list / table configuration. A TCI state / list / table is a list / set of one or more TCI states. An example of a TCI state / list / table configuration for PDSCH is shown in List 6. The RRC parameter tci-StatesToAddModList is a list of Transmission Configuration Indicator (TCI) states indicating a transmission configuration including a QCL-relationship between DL RSs in an RS Set and PDSCH DMRS ports. An example of a TCI state / list / table configuration for PDCCH is shown in List 7. The RRC parameter tci-StatesPDCCH-ToAddList is a subset of the TCI states defined in the pdsch-Config included in the BWP-DownlinkDedicated, which corresponds to the serving cell or DL ​​BWP to which the ControlResourceSet belongs. They are used to provide a QCL relationship between the DL RSs in one RS Set (TCI-State) and the PDCCH DMRS ports.

[0166] List 6

[0167] List 7

[0168] In the case where the TCI status for the beam associated with the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 is introduced / configured / existed, the RRC signaling / message may provide a TCI status / list / table configuration including the TCI status for the beam associated with the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523. The TCI status / list / table may include the TCI status for the beam associated with the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523. For example, the RRC parameter tci-StatesToAddModList is a list of transmission configuration indicator (TCI) states, which includes TCI states (e.g., TCI-State, TCI-State-C-Link, TCI-State-Backhaul-Link, TCI-State-Access-Link, TCI-StateId) for beams associated with the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523. The RRC parameter tci-StatesPDCCH-ToAddList is a list of transmission configuration indicator (TCI) states, which includes TCI states (e.g., TCI-State, TCI-State-C-Link, TCI-State-Backhaul-Link, TCI-State-Access-Link, TCI-StateId) for beams associated with the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523.

[0169] When TCI states for beams associated with C-link 1519 and / or backhaul link 1520 and / or access link 1523 are introduced / configured / exist, RRC signaling / messages may provide separate / different TCI state / list / table configurations including TCI states for beams associated with C-link 1519 and / or backhaul link 1520 and / or access link 1523. That is, the TCI states for beams associated with C-link 1519 and / or backhaul link 1520 and / or access link 1523 may be configured in different TCI states / lists / tables. A first TCI state / list / table may include TCI states for beams associated with C-link 1519, and / or a second TCI state / list / table may include TCI states for beams associated with backhaul link 1520, and / or a third TCI state / list / table may include TCI states for beams associated with access link 1523. For example, the RRC parameter tci-StatesToAddModList-C-Link is a list of TCI states including the transmission configuration indicator (TCI) states (e.g., TCI-State, TCI-State-C-Link, TCI-StateId) for the beam associated with the C-link 1519, and the RRC parameter tci-StatesToAddModList-Backhaul-Link is a list of TCI states including the transmission configuration indicator (TCI) states (e.g., TCI-State, TCI-State-Backhaul-Link, TCI-StateId) for the beam associated with the backhaul link, and the RRC parameter tci-StatesToAddModList-Access-Link is a list of TCI states including the transmission configuration indicator (TCI) states (e.g., TCI-State, TCI-State-Access-Link, TCI-StateId) for the beam associated with the access link 1523.The RRC parameter tci-StatesPDCCH-ToAddList-C-Link is a list of TCI states including the transmission configuration indicator (TCI) states (e.g., TCI-State, TCI-State-C-Link, TCI-StateId) for the beam associated with the C-link 1519, and the RRC parameter tci-StatesPDCCH-ToAddList-Backhaul-Link is a list of TCI states including the transmission configuration indicator (TCI) states (e.g., TCI-State, TCI-State-Backhaul-Link, TCI-StateId) for the beam associated with the backhaul link 1520, and the RRC parameter tci-StatesPDCCH-ToAddList-Access-Link is a list of TCI states including the transmission configuration indicator (TCI) states (e.g., TCI-State, TCI-State-Access-Link, TCI-StateId) for the beam associated with the access link 1523. Listing 8 shows an example of a TCI state / list / table configuration for a PDSCH supporting beams associated with the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523. Listing 9 shows an example of a TCI state / list / table configuration for a PDCCH supporting beams associated with the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523. The RRC parameter tci-StatesToAddModList-C-Link and / or the RRC parameter tci-StatesToAddModList-Backhaul-Link and / or the RRC parameter tci-StatesToAddModList-Access-Link can be configured in the same PDSCH configuration (RRC message / signaling, IE). The RRC parameter tci-StatesToAddModList-C-Link and / or the RRC parameter tci-StatesToAddModList-Backhaul-Link and / or the RRC parameter tci-StatesToAddModList-Access-Link may be configured with separate / different PDSCH configurations (RRC message / signaling, IE).The RRC parameter tci-StatesPDCCH-ToAddModList-C-Link and / or the RRC parameter tci-StatesPDCCH-ToAddModList-Backhaul-Link and / or the RRC parameter tci-StatesPDCCH-ToAddModList-Access-Link can be configured with the same PDCCH / CORESET configuration (RRC message / signaling, IE). The RRC parameter tci-StatesPDCCH-ToAddModList-C-Link and / or the RRC parameter tci-StatesPDCCH-ToAddModList-Backhaul-Link and / or the RRC parameter tci-StatesPDCCH-ToAddModList-Access-Link can be configured with separate / different PDCCH / CORESET configurations (RRC message / signaling, IE). Assuming that the TCI state of the beam used for the backhaul link 1520 at NCR-Fwd 1522 is the same as the TCI state of the C-link 1519, one TCI state / list / table configuration is used / configured / provided for both the C-link 1519 and the backhaul link 1520.

[0170] List 8

[0171] List 9

[0172] The network may activate and deactivate the configured TCI state for the PDSCH of a serving cell or a set of serving cells by sending a TCI state activation / deactivation for a UE-specific PDSCH MAC CE. The network may activate and deactivate the configured TCI state for the code point of the DCI transmission configuration indication field of the PDSCH of a serving cell by sending the described enhanced TCI state activation / deactivation for a UE-specific PDSCH MAC CE. The configured TCI state for the PDSCH is initially deactivated at the time of configuration and after switching. If the MAC entity receives a TCI state activation / deactivation for a UE-specific PDSCH MAC CE on the serving cell, the MAC entity shall indicate information about the TCI state activation / deactivation for the UE-specific PDSCH MAC CE to the lower layers. If the MAC entity receives enhanced TCI state activation / deactivation for UE-specific PDSCH MAC CE on the serving cell, the MAC entity shall indicate information about the enhanced TCI state activation / deactivation for the UE-specific PDSCH MAC CE to the lower layers.

[0173] In the case where the TCI state for the beam associated with the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 is introduced / configured / existed, the network may activate and deactivate the configured TCI state for the PDSCH of the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 by sending a TCI state activation / deactivation for a UE-specific PDSCH MAC CE. In the case where the TCI state for the beam associated with the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 is configured in a TCI state / list / table, the network may activate and deactivate the configured TCI state for the PDSCH of the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 by sending a joint / single TCI state activation / deactivation for a UE-specific PDSCH MAC CE. In the case where the TCI states for beams associated with the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 are configured in separate / different TCI states / lists / tables, the network can activate and deactivate the configured TCI states for the PDSCH of the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 by sending a separate TCI state activation / deactivation for the UE-specific PDSCH MAC CE. The network can support the simultaneous activation of TCI states for more than one access link. The network can activate and deactivate the configured TCI states for the PDSCH of the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 by sending a separate TCI state activation / deactivation for the UE-specific PDSCH MAC CE. If the MAC entity receives TCI state activation / deactivation for a UE-specific PDSCH MAC CE on the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523, the MAC entity shall indicate information about the TCI state activation / deactivation for the UE-specific PDSCH MAC CE to the lower layers. If the MAC entity receives enhanced TCI state activation / deactivation for a UE-specific PDSCH MAC CE on the C-link and / or the backhaul link and / or the access link, the MAC entity shall indicate information about the enhanced TCI state activation / deactivation for the UE-specific PDSCH MAC CE to the lower layers.

[0174] The network may indicate the TCI status for PDCCH reception for a serving cell or a CORESET of a serving cell set by sending a TCI status indication for a UE-specific PDCCH MAC CE. If the MAC entity receives a TCI status indication for a UE-specific PDCCH MAC CE on a serving cell, the MAC entity shall indicate information about the TCI status indication for the UE-specific PDCCH MAC CE to lower layers.

[0175] In the case where the TCI state for the beam associated with the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 is introduced / configured / existed, the network may indicate the TCI state for PDCCH reception of the CORESET for the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 by transmitting a TCI state indication for a UE-specific PDCCH MAC CE. In the case where the TCI state for the beam associated with the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 is configured in a TCI state / list / table, the network may activate and deactivate the configured TCI state for the PDCCH of the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 by transmitting a joint / single TCI state activation / deactivation for a UE-specific PDCCH MAC CE. In the case where the TCI states for beams associated with the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 are configured in separate / different TCI states / lists / tables, the network can activate and deactivate the configured TCI states for the PDCCHs of the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 by sending a separate TCI state activation / deactivation for a UE-specific PDCCH MAC CE. The network can support the simultaneous activation of TCI states for more than one access link. The network can activate and deactivate the configured TCI states for the PDCCHs of the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 by sending a separate TCI state activation / deactivation for a UE-specific PDCCH MAC CE. If the MAC entity receives a TCI status indication for a UE-specific PDCCH MAC CE on the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523, the MAC entity shall indicate information about the TCI status indication for the UE-specific PDCCH MAC CE to the lower layers.

[0176] In the case where the TCI state for the beam associated with the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 is introduced / configured / existed, the network may indicate the TCI state for PDSCH reception of the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 by sending a TCI state indication for a UE-specific PDSCH MAC CE. In the case where the TCI state for the beam associated with the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 is configured in a TCI state / list / table, the network may activate and deactivate the configured TCI state for the PDSCH of the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 by sending a joint / single TCI state activation / deactivation for a UE-specific PDSCH MAC CE. In the case where the TCI states for beams associated with the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 are configured in separate / different TCI states / lists / tables, the network can activate and deactivate the configured TCI states for the PDSCH of the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 by sending a separate TCI state activation / deactivation for the UE-specific PDSCH MAC CE. The network can support the simultaneous activation of TCI states for more than one access link. The network can activate and deactivate the configured TCI states for the PDCCH of the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523 by sending a separate TCI state activation / deactivation for the UE-specific PDSCH MAC CE. If the MAC entity receives a TCI status indication for a UE-specific PDSCH MAC CE on the C-link 1519 and / or the backhaul link 1520 and / or the access link 1523, the MAC entity shall indicate information about the TCI status indication for the UE-specific PDSCH MAC CE to the lower layers.

[0177] DCI-based beam indication is supported. The DCI field transmission configuration indication is used to indicate one of the TCI states activated by the MAC CE mentioned above. The set of activated TCI states may include TCI states for beams associated with the C-link 1519, the backhaul link 1520, and / or the access link 1523.

[0178] In the case where the activated TCI states for beams associated with C-link 1519 and / or backhaul link 1520 and / or access link 1523 are included in different sets for DCI-based beam indications. This document describes how to distinguish the DCI-based beam indications from the activated TCI states for beams associated with C-link 1519 and / or backhaul link 1520 and / or access link 1523. As mentioned above, there may be two TCI lists / tables. The first TCI list / table is a list of TCI states including the transmit configuration indicator (TCI) states for beams associated with backhaul link 1520, and the second TCI list / table is a list of TCI states including the transmit configuration indicator (TCI) states for beams associated with access link 1523. The first set of activated TCI states (the set of activated TCI states for beams associated with the backhaul link 1520) may be activated from a first TCI list / table via a MAC CE, and the second set of activated TCI states (the set of activated TCI states for beams associated with the access link 1523) may be activated from a second TCI list / table via a MAC CE.

[0179] Whether the first set of activated TCI states or the second set of activated TCI states is used for DCI-based beam indication may depend on a radio network temporary identifier (RNTI). For example, if the UE 1524 detects a PDCCH carrying a DCI format with a CRC scrambled by a first RNTI, a DCI field in the DCI format transmits a configuration indication for indicating one TCI state from the first set of activated TCI states. If the UE 1524 detects a PDCCH carrying a DCI format with a CRC scrambled by a second RNTI, a DCI field in the DCI format transmits a configuration indication for indicating one TCI state from the second set of activated TCI states.

[0180] Whether the first set of activated TCI states or the second set of activated TCI states is used for DCI-based beam indication may depend on the DCI format. For example, if the UE 1524 detects a PDCCH carrying a first DCI format, the DCI field in the first DCI format transmits a configuration indication for indicating a TCI state from the first set of activated TCI states. If the UE 1524 detects a PDCCH carrying a second DCI format, the DCI field in the second DCI format transmits a configuration indication for indicating a TCI state from the second set of activated TCI states.

[0181] Whether the first set of activated TCI states or the second set of activated TCI states is used for DCI-based beam indication may depend on the CORESET. For example, if the UE 1524 detects a PDCCH carrying a DCI format in the first CORESET, the DCI field in the DCI format transmits a configuration indication for indicating a TCI state from the first set of activated TCI states. If the UE 1524 detects a PDCCH carrying a DCI format in the second CORESET, the DCI field in the DCI format transmits a configuration indication for indicating a TCI state from the second set of activated TCI states.

[0182] Whether the first set of activated TCI states or the second set of activated TCI states is used for DCI-based beam indication may depend on the search space. For example, if the UE 1524 detects a PDCCH carrying a DCI format in the first search space, the DCI field in the DCI format transmits a configuration indication for indicating a TCI state from the first set of activated TCI states. If the UE 1524 detects a PDCCH carrying a DCI format in the second search space, the DCI field in the DCI format transmits a configuration indication for indicating a TCI state from the second set of activated TCI states.

[0183] Whether the first set of activated TCI states or the second set of activated TCI states is used for DCI-based beam indication may depend on a DCI field. The DCI field may be newly introduced or reused from an existing DCI field. For example, if UE 1524 detects a PDCCH carrying a DCI format and a DCI field set to a first value, the DCI field in the DCI format transmits a configuration indication for indicating one TCI state from the first set of activated TCI states. If UE 1524 detects a PDCCH carrying a DCI format and a DCI field set to a second value, the DCI field in the DCI format transmits a configuration indication for indicating one TCI state from the second set of activated TCI states.

[0184] In yet another design, the DCI field transmission configuration indication may be used to jointly indicate the TCI status of the C-link and / or the backhaul link and / or the access link.

[0185] The capability signaling / messages mentioned in the present disclosure may be configured / indicated via public / dedicated / UE-specific RRC messages / signaling and / or SI, and / or indicated via L2 signaling (e.g., MAC CE) and / or L1 signaling (e.g., DCI, PDCCH), and / or provided / determined in the specification.

[0186] Figure 16 16 is a flow chart illustrating an example of a method 1600 for a UE to perform beam management with respect to inter-cell mobility. The UE may receive (1602) a radio resource control (RRC) message including first information indicating that multi-beam measurement / reporting enhancement for inter-cell mobility centered around L1 / L2 and inter-cell mTRP are enabled. The UE may receive (1604) an RRC message including second information indicating a maximum total number (K) of beams associated with all corresponding non-serving cells reported in a single channel state information (CSI) reporting instance. The UE may transmit (1606) a CSI report to a base station.

[0187] Figure 17 1700 is a flow chart illustrating an example of a method 1700 for a base station to perform beam management with respect to inter-cell mobility. The base station may transmit (1702) a radio resource control (RRC) message including first information indicating that multi-beam measurement / reporting enhancement for inter-cell mobility centered around L1 / L2 and inter-cell mTRP are enabled. The base station may transmit (1704) an RRC message including second information indicating a maximum total number (K) of beams associated with all corresponding non-serving cells reported in a single channel state information (CSI) reporting instance. The base station may receive (1706) a CSI report from a UE.

[0188] Figure 18 18 is a flowchart illustrating an example of a method 1800 for a UE to perform beam indication for inter-cell mobility with respect to a PDSCH. The UE may receive (1802) a radio resource control (RRC) message including first information indicating a first list of transmit configuration indicator (TCI) states for beams associated with a non-serving cell. The UE may receive (1704) an RRC message including second information indicating a second list of transmit configuration indicator (TCI) states for beams associated with a serving cell. In addition, the UE may receive (1806) a first medium access control (MAC) control element (CE) message including third information for activating a first TCI state set from the first list. The UE may receive (1808) a second medium access control (MAC) control element (CE) message including fourth information including information for activating a second TCI state set from the second list. The UE may receive (1810) a physical downlink control channel (PDCCH) carrying downlink control information (DCI) indicating a TCI state for a physical downlink shared channel (PDSCH) in a first set or a second set.

[0189] Figure 1919. The present invention is a flow chart illustrating an example of a method 1900 for a base station to perform beam indication for PDSCH regarding inter-cell mobility. The base station may transmit (1902) a radio resource control (RRC) message including first information indicating a first list of transmit configuration indicator (TCI) states for beams associated with non-serving cells. The base station may transmit (1904) an RRC message including second information indicating a second list of transmit configuration indicator (TCI) states for beams associated with a serving cell. In addition, the base station may transmit (1906) a first medium access control (MAC) control element (CE) message including third information for activating a first set of TCI states from the first list. The base station may transmit (1908) a second medium access control (MAC) control element (CE) message including fourth information including information for activating a second set of TCI states from the second list. The base station may transmit (1910) a physical downlink control channel (PDCCH) carrying downlink control information (DCI) indicating a TCI state for a physical downlink shared channel (PDSCH) in a first set or a second set.

[0190] Figure 20 The present invention is a flowchart illustrating an example of a method 2000 for a UE to perform beam indication for a PDCCH regarding inter-cell mobility. The UE may receive (2002) a radio resource control (RRC) message including first information indicating a first list of transmit configuration indicator (TCI) states for beams associated with a non-serving cell. The UE may receive (2004) an RRC message including second information indicating a second list of transmit configuration indicator (TCI) states for beams associated with a serving cell. In addition, the UE may receive (2006) a first medium access control (MAC) control element (CE) message including third information indicating a first TCI state for a physical downlink control channel (PDCCH) in the first list. The UE may receive (2008) a second medium access control (MAC) control element (CE) message including fourth information indicating a second TCI state for a physical downlink control channel (PDCCH) in the second list.

[0191] Figure 21The present invention is a flowchart illustrating an example of a method 2100 for a base station to perform beam indication for a PDCCH regarding inter-cell mobility. The base station may transmit (2102) a radio resource control (RRC) message including first information indicating a first list of transmit configuration indicator (TCI) states for beams associated with a non-serving cell. The base station may transmit (2104) an RRC message including second information indicating a second list of transmit configuration indicator (TCI) states for beams associated with a serving cell. In addition, the base station may transmit (2106) a first medium access control (MAC) control element (CE) message including third information indicating a first TCI state for a physical downlink control channel (PDCCH) in the first list. The base station may transmit (2108) a second medium access control (MAC) control element (CE) message including fourth information indicating a second TCI state for a physical downlink control channel (PDCCH) in the second list.

[0192] The term "computer-readable medium" refers to any available medium that can be accessed by a computer or processor. As used herein, the term "computer-readable medium" may refer to a non-transitory and tangible computer-readable medium and / or processor-readable medium. By way of example, and not limitation, computer-readable or processor-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer or processor. Disks and optical disks, as used herein, include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Optical disks, where disks typically reproduce data magnetically, optical disks use lasers to reproduce data optically.

[0193] It should be noted that one or more of the methods described herein may be implemented in hardware and / or performed using hardware. For example, one or more of the methods described herein may be implemented in a chipset, an application specific integrated circuit (ASIC), a large-scale integrated circuit (LSI), or an integrated circuit, and / or implemented using ...

[0194] Each method disclosed herein includes one or more steps or actions for implementing the method. These method steps and / or actions may be interchangeable with one another and / or combined into a single step without departing from the scope of the claims. In other words, unless a specific order of steps or actions is required for the correct operation of the method, the order and / or use of specific steps and / or actions may be modified without departing from the scope of the claims.

[0195] It is to be understood that the claims are not limited to the precise configuration and components illustrated above, and that various modifications, changes and variations may be made in the arrangement, operation and details of the systems, methods, and apparatus described herein without departing from the scope of the claims.

[0196] The program running on the gNB 160 or UE 102 according to the systems and methods described herein controls the CPU, etc., to implement the functions according to the systems and methods (a program that causes the computer to operate). Information processed by these devices is then temporarily stored in RAM while being processed. This information is then stored in various ROMs or HDDs and read by the CPU for modification or writing whenever necessary. Possible recording media on which the program is stored include semiconductors (e.g., ROMs, nonvolatile memory cards, etc.), optical storage media (e.g., DVDs, MOs, MDs, CDs, BDs, etc.), and magnetic storage media (e.g., magnetic tapes, floppy disks, etc.). In some cases, the functions according to the systems and methods described herein are implemented by executing the loaded program. Alternatively, the functions according to the systems and methods are implemented based on instructions from the program in conjunction with an operating system or other application programs.

[0197] Furthermore, if the program is commercially available, it can be distributed stored on a portable recording medium, or it can be transmitted to a server computer connected via a network such as the Internet. In this case, the storage device in the server computer is also included. Furthermore, some or all of the gNB 160 and UE 102 according to the systems and methods described herein can be implemented as LSIs, which are typical integrated circuits. Each functional block of the gNB 160 and UE 102 can be individually built into a chip, and some or all functional blocks can be integrated into a chip. Furthermore, integrated circuit technology is not limited to LSIs, and integrated circuits for functional blocks can be implemented using dedicated circuits or general-purpose processors. Furthermore, if integrated circuit technology that replaces LSIs emerges as semiconductor technology continues to advance, integrated circuits using such technology can also be used.

[0198] In addition, each functional block or various features of the base station equipment and terminal equipment used in each of the above-mentioned embodiments can be realized or executed by circuit (typically an integrated circuit or multiple integrated circuits). The circuit designed to perform the function described in this specification may include a general-purpose processor, a digital signal processor (DSP), a dedicated or general-purpose integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices or discrete hardware components or a combination thereof. The general-purpose processor can be a microprocessor, or alternatively, the processor can be a conventional processor, a controller, a microcontroller or a state machine. The general-purpose processor or every kind of circuit described herein can be configured by a digital circuit, or can be configured by an analog circuit. In addition, when the technology of the integrated circuit replacing current integrated circuit occurs due to the progress of semiconductor technology, it is also possible to use the integrated circuit produced by this technology.

[0199] As used herein, the term "and / or" should be interpreted as meaning one or more items. For example, the phrase "A, B, and / or C" should be interpreted as meaning any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. As used herein, the phrase "at least one" should be interpreted as meaning one or more items. For example, the phrase "at least one of A, B, and C" or the phrase "at least one of A, B, or C" should be interpreted as meaning any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. As used herein, the phrase "one or more" should be understood to refer to one or more items. For example, the phrase "one or more of A, B, and C" or the phrase "one or more of A, B, or C" should be interpreted to mean any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. <Cross Reference>

[0200] This nonprovisional application claims priority under 35 U.S.C. 119 to provisional application 63 / 391,438, filed on July 22, 2022, the entire contents of which are hereby incorporated by reference.

Claims

1. A network controlled relay (NCR) device communicating with a user equipment (UE) and a base station device, the network controlled relay (NCR) device comprising: A receiving circuit, wherein the receiving circuit is configured to: receiving a radio resource control (RRC) message including first information indicating a first list of transmit configuration indicator (TCI) states for beams associated with a backhaul link and / or a C-link; receiving an RRC message including second information indicating a second list of transmit configuration indicator (TCI) states for a beam associated with an access link; Receiving a first medium access control (MAC) control element (CE) message including third information indicating a first TCI state in the first list for a physical downlink control channel (PDCCH) carried by the backhaul link and / or the C-link; receiving a second medium access control (MAC) control element (CE) message including fourth information indicating a second TCI state in the second list for a physical downlink control channel (PDCCH) carried by the access link; as well as receiving a physical downlink control channel (PDCCH) carried by the backhaul link and / or the C-link according to the first TCI state; A transmitting circuit, wherein the transmitting circuit is configured as follows: A physical downlink control channel (PDCCH) carried by the access link is transmitted according to the second TCI state.

2. A base station device for communicating with a user equipment (UE) and a network controlled relay (NCR) device, the base station device comprising: A transmitting circuit, wherein the transmitting circuit is configured as follows: transmitting a radio resource control (RRC) message including first information indicating a first list of transmit configuration indicator (TCI) states for beams associated with a backhaul link and / or a C-link; transmitting an RRC message including second information indicating a second list of transmit configuration indicator (TCI) states for a beam associated with the access link; transmitting a first medium access control (MAC) control element (CE) message including third information for indicating a first TCI state in the first list for a physical downlink control channel (PDCCH) carried by the backhaul link and / or the C-link; transmitting a second medium access control (MAC) control element (CE) message including fourth information, the fourth information being used to indicate a second TCI state in the second list for a physical downlink control channel (PDCCH) carried by the access link; as well as A physical downlink control channel (PDCCH) carried by the backhaul link and / or the C-link is transmitted according to the first TCI state.

3. A user equipment (UE) for communicating with a network controlled repeater (NCR) device and a base station device, the user equipment (UE) comprising: A receiving circuit, wherein the receiving circuit is configured to: receiving an RRC message including second information indicating a second list of transmit configuration indicator (TCI) states for a beam associated with an access link; receiving a second medium access control (MAC) control element (CE) message including fourth information indicating a second TCI state in the second list for a physical downlink control channel (PDCCH) carried by the access link; and A physical downlink control channel (PDCCH) carried by the access link is received according to the second TCI state.

Images