Uplink transmission or reception method and apparatus in a wireless communication system

Abstract

A method and apparatus for uplink transmission or uplink reception in a wireless communication system are disclosed. A method according to one embodiment of the present disclosure may include the steps of: receiving first information from a first network node by a terminal, relating to one or more of the SSB (synchronization signal / physical broadcast channel block) or reference signals (RS) of the first network node; transmitting a random access preamble to a second network node by the terminal based on the first information; and receiving a random access response (RAR) from the second network node by the terminal in response to the random access preamble. The RAR may include second information relating to a timing advance (TA) to the second network node.

Description

[Technical Field]

[0001] This disclosure relates to wireless communication systems, and more particularly to methods and apparatus for uplink transmission or uplink reception in wireless communication systems. [Background technology]

[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, mobile communication systems have expanded beyond voice to include data services, and currently, the explosive increase in traffic is causing resource shortages. Furthermore, users are demanding faster services, so more advanced mobile communication systems are desired.

[0003] The requirements for next-generation mobile communication systems are broad, including the ability to handle explosive data traffic, a dramatic increase in transmission rates per user, acceptance of a significantly increased number of connected devices, extremely low end-to-end latency, and support for high energy efficiency. To this end, various technologies such as dual connectivity, massive multiple input / output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking are being researched. [Overview of the project] [Problems that the invention aims to solve]

[0004] The technical problem addressed by this disclosure is to provide a method and apparatus for uplink transmission at a terminal or uplink reception at a base station in a network including an uplink receiving point.

[0005] A further technical challenge of this disclosure is to provide a method and apparatus for obtaining a timing advance for an uplink reception point at a terminal or for a base station to provide a timing advance for an uplink reception point at a terminal.

[0006] The technical challenges addressed in this disclosure are not limited to those mentioned above, and other technical challenges not mentioned will be clearly understood by those with ordinary skill in the art to which this disclosure pertains from the following description. [Means for solving the problem]

[0007] A method relating to one aspect of the present disclosure may include the steps of: receiving first information from a first network node by a terminal, relating to one or more of the SSB (synchronization signal / physical broadcast channel block) or reference signals (RS) of the first network node; transmitting a random access preamble to a second network node by the terminal based on the first information; and receiving a random access response (RAR) from the first network node by the terminal in response to the random access preamble. The RAR may include (may include; configure; construct; set up; encompass; include; contain; may have; may be equipped with) second information relating to a timing advance (TA) to the second network node.

[0008] A further aspect of the present disclosure may include the steps of: transmitting first information relating to one or more of the SSB (synchronization signal / physical broadcast channel block) or reference signals (RS) of the first network node to a terminal by the first network node; and transmitting a random access response (RAR) to the terminal by the first network node in response to a random access preamble transmitted to the second network node by the terminal based on the first information. The RAR may include second information relating to a timing advance (TA) to the second network node. [Effects of the Invention]

[0009] According to this disclosure, a method and apparatus for uplink transmission by a terminal or uplink reception by a base station in a network including an uplink receiving point can be provided.

[0010] According to this disclosure, a method and apparatus can be provided for obtaining a timing advance for an uplink reception point on a terminal or for a base station to provide a timing advance for an uplink reception point on a terminal.

[0011] The effects derived from this disclosure are not limited to those mentioned above, and any other effects not mentioned above will be clearly understood by a person with ordinary skill in the art to which this disclosure pertains from the following description. [Brief explanation of the drawing]

[0012] The accompanying drawings, included as part of the detailed description to aid in understanding this disclosure, provide examples relating to this disclosure and illustrate the technical features of this disclosure together with the detailed description.

[0013] [Figure 1] This figure illustrates the structure of a wireless communication system to which this disclosure can be applied. [Figure 2]This figure illustrates a frame structure in a wireless communication system to which this disclosure can be applied. [Figure 3] This figure illustrates a resource grid in a wireless communication system to which this disclosure can be applied. [Figure 4] This figure illustrates a physical resource block in a wireless communication system to which this disclosure can be applied. [Figure 5] This figure illustrates a slot structure in a wireless communication system to which this disclosure can be applied. [Figure 6] This figure illustrates physical channels used in wireless communication systems to which this disclosure can be applied, and general signal transmission and reception methods using them. [Figure 7] This diagram illustrates the uplink-downlink timing relationship in a wireless communication system to which this disclosure can be applied. [Figure 8] This figure illustrates a MAC CE for random access response in a wireless communication system to which this disclosure can be applied. [Figure 9] This figure illustrates a timing advance instruction MAC CE in a wireless communication system to which this disclosure can be applied. [Figure 10] This figure illustrates the operation of a terminal according to one embodiment of the present disclosure. [Figure 11] This figure illustrates the operation of a base station according to one embodiment of the present disclosure. [Figure 12] This is a block diagram of a wireless communication device according to one embodiment of the present disclosure. [Modes for carrying out the invention]

[0014] Preferred embodiments relating to this disclosure will be described in detail below with reference to the accompanying drawings. The detailed description disclosed below, together with the accompanying drawings, is intended to illustrate exemplary embodiments of this disclosure and is not intended to represent the only possible embodiments of this disclosure. The detailed description below includes specific details to provide a complete understanding of this disclosure. However, those skilled in the art will understand that this disclosure is implementable without such specific details.

[0015] In some cases, to avoid ambiguity of the concepts in this disclosure, known structures and devices may be omitted, or they may be shown in the form of block diagrams focusing on the core function of each structure and device.

[0016] In this disclosure, when one component is “connected,” “joined,” or “linked” to another component, this may include not only direct connections but also indirect connections between them where other components exist. Also, in this disclosure, the terms “includes” or “have” identify the presence of the referred features, stages, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, stages, operations, elements, components and / or groups thereof.

[0017] In this disclosure, terms such as “first,” “second,” etc., are used solely to distinguish one component from another and are not used to limit the components, nor do they limit the order or importance of the components unless specifically mentioned. Therefore, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0018] The terms used in this disclosure are for illustrative purposes relating to specific embodiments and are not intended to limit the scope of the claims. As used in the description of the embodiments and in the attached claims, the singular forms are intended to include the plural forms unless otherwise specified in the context. The terms “and / or” used in this disclosure may refer to one of the related enumerated items, or to any and all possible combinations of two or more of them. In this disclosure, “ / ” between words has the same meaning as “and / or” unless otherwise specified.

[0019] This disclosure describes a wireless communication network or wireless communication system, where operations performed in the wireless communication network may occur in the process of a device (e.g., a base station) controlling the network and transmitting or receiving signals, or in the process of a terminal connected to the wireless network transmitting or receiving signals to or from the network.

[0020] In this disclosure, transmitting or receiving a channel includes transmitting or receiving information or signals on that channel. For example, transmitting a control channel means transmitting control information or signals on the control channel. Similarly, transmitting a data channel means transmitting data information or signals on the data channel.

[0021] In the following, downlink (DL) refers to communication from the base station to the terminal, and uplink (UL) refers to communication from the terminal to the base station. In the downlink, the transmitter may be part of the base station, and the receiver may be part of the terminal. In the uplink, the transmitter may be part of the terminal, and the receiver may be part of the base station. The base station may be referred to as the first communication device, and the terminal as the second communication device. The term Base Station (BS) may be replaced with terms such as fixed station, Node B, eNB (evolved-Node B), gNB (Next Generation Node B), BTS (base transceiver system), Access Point (AP), network (5G network), AI (Artificial Intelligence) system / module, RSU (roadside unit), robot, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. Furthermore, the term "Terminal" may be fixed or mobile, and may be replaced by terms such as UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), MTC (Machine-Type Communication) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, RSU (roadside unit), robot, AI (Artificial Intelligence) module, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, and VR (Virtual Reality) device.

[0022] The following technologies may be used in various wireless connectivity systems such as CDMA, FDMA, TDMA, OFDMA, and SC-FDMA. CDMA may be implemented by wireless technologies such as UTRA (Universal Terrestrial Radio Access) and CDMA2000. TDMA may be implemented by wireless technologies such as GSM (Global System for Mobile communications) / GPRS (General Packet Radio Service) / EDGE (Enhanced Data Rates for GSM Evolution). OFDMA may be implemented by wireless technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (Evolved UTRA). UTRA is part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project: registered trademark: hereinafter the same) LTE (Long Term Evolution) is part of E-UMTS (Evolved UMTS) which uses E-UTRA, and LTE-A (Advanced) / LTE-A pro are advanced versions of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an advanced version of 3GPP LTE / LTE-A / LTE-A pro.

[0023] For clarity, the explanation will be based on 3GPP communication systems (e.g., LTE-A, NR), but the technical concepts of this disclosure are not limited thereto. LTE refers to 3GPP TS (Technical Specification) 36.xxx Release 8 and later technologies. More specifically, LTE technology from 3GPP TS 36.xxx Release 10 onwards is called LTE-A, and LTE technology from 3GPP TS 36.xxx Release 13 onwards is called LTE-A pro. 3GPP NR refers to TS 38.xxx Release 15 and later technologies. LTE / NR may be referred to as a 3GPP system. "xxx" means the standard document detail number. LTE / NR may be referred to as a 3GPP system. For background information, terminology, abbreviations, etc., used in this disclosure, refer to the standard documents published prior to this disclosure. For example, refer to the following documents.

[0024] For 3GPP LTE, you can refer to TS 36.211 (Physical Channels and Modulation), TS 36.212 (Multiplexing and Channel Coding), TS 36.213 (Physical Layer Procedures), TS 36.300 (General Description), and TS 36.331 (Radio Resource Control).

[0025] For 3GPP NR, you can refer to TS 38.211 (Physical Channels and Modulation), TS 38.212 (Multiplexing and Channel Coding), TS 38.213 (Physical Layer Procedures for Control), TS 38.214 (Physical Layer Procedures for Data), TS 38.300 (General Description of NR and NG-RAN (New Generation-Radio Access Network)), and TS 38.331 (Radio Resource Control Protocol Standard).

[0026] Abbreviations of terms used in this disclosure are defined as follows:

[0027] - BM: Beam Management

[0028] - CQI: Channel Quality Indicator

[0029] - CRI: Channel State Information - Reference Signal Resource Indicator

[0030] - CSI: Channel State Information

[0031] - CSI-IM: Channel State Information - Interference Measurement

[0032] - CSI-RS: Channel State Information - Reference Signal

[0033] - DMRS: Demodulation reference signal

[0034] - FDM: Frequency Division Multiplexing

[0035] - FFT: Fast Fourier Transform

[0036] - IFDMA: Interleaved frequency division multiple access

[0037] - IFFT: Inverse Fast Fourier Transform

[0038] - L1-RSRP: Layer 1 reference signal received power

[0039] - L1-RSRQ: Layer 1 reference signal received quality

[0040] - MAC: Medium Access Control

[0041] - NZP: Non-Zero Power

[0042] - OFDM: Orthogonal frequency division multiplexing

[0043] - PDCCH: Physical Downlink Control Channel

[0044] - PDSCH: Physical Downlink Shared Channel

[0045] - PMI: Precoding matrix indicator

[0046] - RE: Resource element

[0047] - RI: Rank indicator

[0048] - RRC: Radio Resource Control

[0049] - RSSI: received signal strength indicator

[0050] - Rx: Reception

[0051] - QCL: quasi co-location

[0052] - SINR: Signal-to-interference and noise ratio

[0053] - SSB (or SS / PBCH block): Synchronization signal block (including primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast channel (PBCH))

[0054] - TDM: time division multiplexing

[0055] - TRP: Transmission and Reception Point

[0056] - TRS: Tracking Reference Signal

[0057] - Tx: transmission

[0058] - UE: User equipment

[0059] - ZP: Zero Power

[0060] General System

[0061] As more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Massive Machine Type Communications (MTC), which connects multiple devices and things to provide various services anytime, anywhere, is also a major consideration in next-generation communications. In addition, communication system design that takes into account reliability and latency-sensitive services / terminals is being discussed. Thus, the introduction of next-generation RATs that consider eMBB (enhanced mobile broadband communication), Mmtc (massive MTC), URLLC (Ultra-Reliable and Low Latency Communication), etc., is being discussed, and for convenience in this disclosure, this technology will be referred to as NR. NR is an expression representing an example of 5G RAT.

[0062] The new RAT system, including NR, uses an OFDM transmission scheme or a similar scheme. The new RAT system may follow OFDM parameters different from those of LTE. Alternatively, the new RAT system may follow the existing LTE / LTE-A numerology but support a larger system bandwidth (e.g., 100 MHz). Alternatively, a single cell may support multiple numerologies; that is, terminals operating with different numerologies may coexist within a single cell.

[0063] Numerology corresponds to a single subcarrier spacing in the frequency domain. Different numerologies can be defined by scaling the reference subcarrier spacing by an integer N.

[0064] Figure 1 illustrates the structure of a wireless communication system to which this disclosure can be applied.

[0065] Referring to Figure 1, the NG-RAN consists of gNBs that provide control plane (RRC) protocol termination for the NG-RA (NG-Radio Access) user plane (i.e., the new AS (access stratum) sublayer / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC / PHY) and UE. The gNBs are interconnected via the Xn interface. The gNBs are also connected to the NGC (New Generation Core) via the NG interface. More specifically, the gNBs are connected to the AMF (Access and Mobility Management Function) via the N2 interface and to the UPF (User Plane Function) via the N3 interface.

[0066] Figure 2 illustrates a frame structure in a wireless communication system to which this disclosure can be applied.

[0067] The NR system can support multiple numerologies, which may be defined by subcarrier spacing and cyclic prefix (CP) overhead. Multiple subcarrier spacings may be derived by scaling the fundamental (reference) subcarrier spacing by an integer N (or μ). Furthermore, even assuming that very low subcarrier spacings are not used at very high carrier frequencies, the numerologies used may be selected independently of the frequency band. The NR system may also support various frame structures based on multiple numerologies.

[0068] The following describes the OFDM numerologies and frame structures that can be considered in the NR system. The multiple OFDM numerologies supported in the NR system may be defined as shown in Table 1 below.

[0069] [Table 1]

[0070] NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services. For example, an SCS of 15kHz supports wide area on traditional cellular bands, an SCS of 30kHz / 60kHz supports dense-urban areas, lower latency, and wider carrier bandwidth, and an SCS of 60kHz or higher supports bandwidths greater than 24.25GHz to overcome phase noise.

[0071] The NR frequency band is defined as a frequency range of two types (FR1 and FR2). FR1 and FR2 may be configured as shown in Table 2 below. Furthermore, FR2 can represent millimeter waves (mmW).

[0072] [Table 2]

[0073] In relation to the frame structure in an NR system, the sizes of various fields in the time domain are T c = 1 / (Δf max ·N f It is expressed as a multiple of the time unit of ). Here, Δf max =480·10 3 It is Hz, Nf =4096. Downlink and uplink transmissions are organized in radio frames each having a duration of T f =1 / (Δf max N f / 100)·T c =10ms. Here, each radio frame consists of 10 subframes each having a duration of T sf =(Δf max N f / 1000)·T c =1ms. In this case, there may be one set of frames for the uplink and one set of frames for the downlink. Further, the transmission in uplink frame number i from a terminal must start before T TA =(N TA +N TA,offset )T c from the start of the corresponding downlink frame at the terminal. For subcarrier spacing configuration μ, slots are numbered in increasing order of n s μ∈{0,...,N slot subframe, μ-1} within a subframe, and numbered in increasing order of n s,f μ∈{0,...,N slot frame, μ-1} within a radio frame. One slot consists of N symb slot consecutive OFDM symbols, where N symb slot is determined by the CP. The start of slot n s μ in a subframe is aligned in time with the start of OFDM symbol n s μN symb slot in the same subframe. Not all terminals can transmit and receive at the same time, which means that not all OFDM symbols in a downlink slot or an uplink slot may be used.

[0074] Table 3 shows the number of OFDM symbols per slot in a general CP (N symb slot ), Number of slots per wireless frame (N slot frame, μ), Number of slots per subframe (N) slot subframe, Table 4 shows the number of OFDM symbols per slot, the number of slots per wireless frame, and the number of slots per subframe in the extended CP.

[0075] [Table 3]

[0076] [Table 4]

[0077] Figure 2 shows an example where μ=2 (SCS is 60kHz). Referring to Table 3, one subframe may contain four slots. The one subframe = {1,2,4} slots shown in Figure 2 is just an example; the number of slots that can be included in one subframe is defined as shown in Table 3 or Table 4. Also, a mini-slot may contain 2, 4, or 7 symbols, or more or fewer symbols.

[0078] In relation to physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, and carrier parts may be considered. The following describes in detail the physical resources that can be considered in an NR system.

[0079] First, in relation to antenna ports, an antenna port is defined such that the channel on which a symbol is carried on an antenna port can be inferred from the channel on which other symbols on the same antenna port are carried. Two antenna ports can be said to be in a QC / QCL (quasi co-located or quasi co-location) relationship if the large-scale property of the channel on which a symbol is carried on one antenna port can be inferred from the channel on which a symbol is carried on another antenna port. Here, the large-scale property includes one or more of the following: delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0080] Figure 3 illustrates a resource grid in a wireless communication system to which this disclosure can be applied.

[0081] Referring to Figure 3, the resource grid is N in the frequency domain. RB μN sc RB This description exemplifies a system where a subframe consists of 14·2μOFDM symbols, and is not limited to this. In an NR system, the transmitted signal is N RB μN sc RB One or more resource grids composed of subcarriers and 2μN symb ( μ ) This is explained by the OFDM symbol, where N RB μ≦N RB max, μ is N RB max,μ represents the maximum transmit bandwidth, which may vary not only numerically but also between the uplink and downlink. In this case, one resource grid may be configured for each μ and antenna port p.

[0082] [Table A]

[0083] Point A acts as the common reference point for the resource block grid and is obtained as follows:

[0084] - The offsetToPointA for the Primary Cell (PCell) downlink indicates the frequency offset between the lowest subcarrier of the lowest resource block overlapping with the SS / PBCH block used by the terminal for initial cell selection and point A. It is expressed in resource block units, assuming a 15kHz subcarrier spacing for FR1 and a 60kHz subcarrier spacing for FR2.

[0085] - absoluteFrequencyPointA indicates the frequency-position of point A as expressed in ARFCN (absolute radio-frequency channel number).

[0086] Common resource blocks are numbered upwards from 0 in the frequency domain relative to the subcarrier spacing setting μ. The center of subcarrier 0 of common resource block 0 relative to the subcarrier spacing setting μ coincides with 'point A'. In the frequency domain, common resource block number n... CRB The relationship between μ and the resource element (k,l) with respect to the subcarrier spacing setting μ is given by Equation 1 below.

[0087]

number

[0088] In Equation 1, k is defined relative to point A such that k=0 corresponds to a subcarrier centered at point A. The physical resource block ranges from 0 to N within the bandwidth part (BWP). BWP,i size, Numbers are assigned up to μ-1, where i is the BWP number. In BWP i, physical resource block n PRB and common resource block n CRB The relationship between them is given by equation 2 below.

[0089]

number

[0090] N BWP,i start, μ is a common resource block where BWP starts relative to common resource block 0.

[0091] Figure 4 illustrates a physical resource block in a wireless communication system to which this disclosure can be applied. Figure 5 illustrates a slot structure in a wireless communication system to which this disclosure can be applied.

[0092] Referring to Figures 4 and 5, a slot contains multiple symbols in the time domain. For example, in a general CP, one slot contains seven symbols, while in an extended CP, one slot contains six symbols.

[0093] A carrier wave contains multiple subcarriers in the frequency domain. An RB (Resource Block) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (Bandwidth Part) is defined as multiple consecutive (physical) resource blocks in the frequency domain and may correspond to a single numerology (e.g., SCS, CP length, etc.). A carrier wave may contain up to N (e.g., 5) BWPs. Data communication takes place over activated BWPs, and only one BWP may be activated for a single terminal. In a resource grid, each element is called a Resource Element (RE) and may be mapped to a single complex symbol.

[0094] An NR system may support up to 400 MHz per component carrier (CC). If a terminal operating on such a wideband CC keeps its radio frequency (RF) chip on for the entire CC at all times, terminal battery consumption may increase. Alternatively, considering various use cases operating within a single wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.), different numerologies (e.g., subcarrier spacing) may be supported for each frequency band within that CC. Alternatively, terminals may have different capabilities for the maximum bandwidth. Taking this into consideration, a base station may instruct terminals to operate only on a portion of the wideband CC's bandwidth rather than the entire bandwidth, and this portion of the bandwidth is conveniently defined as a bandwidth part (BWP). A BWP may consist of consecutive RBs on the frequency axis and may correspond to a single numerology (e.g., subcarrier spacing, CP length, slot / minislot interval).

[0095] On the other hand, a base station can configure multiple BWPs within a single CC configured on a terminal. For example, a PDCCH monitoring slot may be configured with a BWP occupying a relatively small frequency range, while the PDSCH instructed by the PDCCH may be scheduled on a larger BWP. Alternatively, if UEs are concentrated on a particular BWP, other BWPs may be configured on some terminals for load balancing. Or, considering frequency domain inter-cell interference cancellation between adjacent cells, a portion of the spectrum of the total bandwidth may be excluded, and both BWPs may be configured within the same slot. In other words, a base station can configure at least one DL / UL BWP on a terminal associated with a broadband CC. A base station can activate at least one DL / UL BWP configured at a particular time (by L1 signaling, MAC CE (Control Element), or RRC signaling, etc.). Furthermore, the base station can instruct switching to another configured DL / UL BWP (by L1 signaling, MAC CE, or RRC signaling, etc.). Alternatively, it may switch to a designated DL / UL BWP when a timer expires. In this case, the activated DL / UL BWP is defined as the active DL / UL BWP. However, in situations such as when a terminal is in the initial access process or before the RRC connection is set up, the settings for the DL / UL BWP may not be received. In such situations, the DL / UL BWP assumed by the terminal is defined as the initially active DL / UL BWP.

[0096] Figure 6 illustrates physical channels used in wireless communication systems to which this disclosure can be applied, and general signal transmission and reception methods using them.

[0097] In wireless communication systems, a terminal receives information from a base station via the downlink and transmits information to the base station via the uplink. The information transmitted and received between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type and purpose of the information being transmitted and received.

[0098] When a terminal is powered on or enters a new cell, it performs an initial cell search (S601), including synchronizing with the base station. To do this, the terminal receives a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station to synchronize with the base station and obtain information such as the cell identifier (ID). Subsequently, the terminal receives the physical broadcast channel (PBCH) from the base station to obtain intra-cell broadcast information. Meanwhile, during the initial cell search phase, the terminal can receive a downlink reference signal (DL RS) to check the downlink channel status.

[0099] After completing the initial cell search, the terminal receives the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH) via the information carried on the PDCCH, thereby obtaining more specific system information (S602).

[0100] On the other hand, if the terminal is initially connected to a base station or does not have radio resources for signal transmission, it can perform a Random Access Procedure (RACH) with respect to the base station (stages S603 to S606). To do this, the terminal transmits a specific sequence as a preamble on a Physical Random Access Channel (PRACH) (S603 and S605), and can receive a response message to the preamble on the PDCCH and the corresponding PDSCH (S604 and S606). In the case of a conflict-based RACH, a Contention Resolution Procedure can also be performed.

[0101] A terminal that has performed the procedures described above can then perform general uplink / downlink signal transmission procedures, such as receiving PDCCH / PDSCH (S607) and transmitting Physical Uplink Shared Channel (PUSCH) / Physical Uplink Control Channel (PUCCH) (S608). In particular, the terminal receives Downlink Control Information (DCI) via PDCCH. Here, DCI includes control information such as resource allocation information for the terminal, and its format differs depending on its purpose of use.

[0102] On the other hand, control information that a terminal transmits to or receives from a base station on the uplink includes downlink / uplink ACK / NACK (Acknowledgement / Non-Acknowledgement) signals, CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indicator), etc. In the 3GPP LTE system, the terminal can transmit the above-mentioned control information such as CQI / PMI / RI via PUSCH and / or PUCCH.

[0103] Table 5 shows an example of the DCI format in the NR system.

[0104] [Table 5]

[0105] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 can include resource information related to PUSCH scheduling (e.g., UL / SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), Transport Block (TB) related information (e.g., MCS (Modulation Coding and Scheme), NDI (New Data Indicator), RV (Redundancy Version), etc.), HARQ (Hybrid - Automatic Repeat and Request) related information (e.g., process number, DAI (Downlink Assignment Index), PDSCH-HARQ feedback timing, etc.), multiplex antenna related information (e.g., DMRS sequence initialization information, antenna ports, CSI requests, etc.), and power control information (e.g., PUSCH power control, etc.). The control information included in each DCI format may be predefined.

[0106] DCI format 0_0 is used for scheduling PUSCH within a single cell. The information contained in DCI format 0_0 is scrambled using CRC (cyclic redundancy check) by C-RNTI (Cell RNTI: Cell Radio Network Temporary Identifier), CS-RNTI (Configured Scheduling RNTI), or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI) before transmission.

[0107] DCI format 0_1 ​​is used to instruct terminals to schedule one or more pushes in a single cell, or to provide configured grant (CG) downlink feedback information. The information contained in DCI format 0_1 ​​is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI (Semi-Persistent CSI RNTI), or MCS-C-RNTI.

[0108] DCI format 0_2 is used for scheduling pushes within a single cell. The information contained in DCI format 0_2 is CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI before transmission.

[0109] Next, DCI formats 1_0, 1_1, and 1_2 may include resource information related to PDSCH scheduling (e.g., frequency resource allocation, time resource allocation, VRB (virtual resource block)-PRB (physical resource block) mapping, etc.), transmission block (TB) related information (e.g., MCS, NDI, RV, etc.), HARQ related information (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), multiplex antenna related information (e.g., antenna ports, TCI (transmission configuration indicator), SRS (sounding reference signal) requests, etc.), and PUCCH related information (e.g., PUCCH power control, PUCCH resource indicator, etc.), and the control information included in each DCI format may be predefined.

[0110] DCI format 1_0 is used for PDSCH scheduling in a single DL cell. The information contained in DCI format 1_0 is CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI before transmission.

[0111] DCI format 1_1 is used for PDSCH scheduling in a single cell. The information contained in DCI format 1_1 is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0112] DCI format 1_2 is used for PDSCH scheduling in a single cell. The information contained in DCI format 1_2 is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0113] Timing Advance (TA) related operations

[0114] Figure 7 illustrates the uplink-downlink timing relationship in a wireless communication system to which this disclosure can be applied.

[0115] The uplink frame number i for transmission from the UE is T earlier than the start of the corresponding downlink frame (i.e., downlink frame i) in the UE. TA =(N TA +N TA,offset )T c It starts only a little earlier. In other words, the uplink frame starts T later than the corresponding downlink frame. TA It starts just before. Here, N TA,offset This involves sending msgA on PUCH (in this case, N TA Except for =0), the values ​​are given from TS 38.213.

[0116] Below, N TA This document describes how to configure it.

[0117] N TA This may be set i) through a random access response (RAR), or ii) through a timing advance command MAC control element (CE).

[0118] Case 1: How to configure via RAR

[0119] For random access responses or absolute timing advance commands for timing advance groups (TAGs), MAC CE(T) A In ), the timing advance instruction is T A N = index values ​​of 0, 2, ..., 3846 TA Specify the value. Here, the amount of time alignment for a TAG with an SCS of 2μ·15kHz is N TA =T A It is 16·64 / 2μ. TA This is relative to the SCS of the first uplink transmission from the UE after receiving a random access response or an absolute timing advance instruction MAC CE.

[0120] Figure 8 illustrates a MAC CE for random access response in a wireless communication system to which this disclosure can be applied.

[0121] The MAC CE for random access responses (hereinafter referred to as MAC RAR) has a fixed size as shown in Figure 8 and includes the following fields.

[0122] - R: Reserved bit, set to 0;

[0123] - Timing Advance Command: The Timing Advance Command field is an index value T used to control the amount of timing adjustment that a MAC entity should apply. A This instructs the system. The Timing Advance Command field is 12 bits in size.

[0124] - UL Grant: The UL Grant (Uplink Grant) field indicates the resources to be used for the uplink. The size of the UL Grant field is 27 bits.

[0125] - Temporary C-RNTI: The Temporary C-RNTI field is a temporary identifier used by MAC individuals during random access. The size of the Temporary C-RNTI field is 16 bits.

[0126] Case 2: Setting via Timing Advance Instruction (MAC-CE)

[0127] Timing advance instruction for TAG (T A ) is T A The current index values ​​are 0, 1, 2, ..., 63. TA Value (i.e., N TA#old )'s new N TA Value (i.e., N TA#new This instructs adjustment to ). Here, in the case of a 2μ·15kHz SCS, N TA#new =N TA#old +(T A -31)·16·64 / 2μ

[0128] Figure 9 illustrates a timing advance instruction MAC CE in a wireless communication system to which this disclosure can be applied.

[0129] A Timing Advance Command (MAC CE) is identified by a MAC subheader containing a logical channel identity (LCID). A Timing Advance Command (MAC CE) has a fixed size and consists of one octet, as follows:

[0130] - TAG Identifier (TAG ID: TAG Identity): This field indicates the TAG identifier of the addressed TAG. TAGs containing SpCells have TAG identifier 0. This field is 2 bits long.

[0131] - Timing Advance Command: This field is an index value T used to control the amount of timing adjustment that a MAC entity should apply. A This instructs the user to perform a timing advance instruction. The length of the timing advance instruction field is 6 bits.

[0132] This disclosure primarily describes a four-step random access procedure (i.e., the RACH procedure), but does not exclude two-step random access procedures; therefore, this disclosure may also be applied to two-step random access procedures.

[0133] Below, N TA,offset This document describes how to configure the settings.

[0134] Case 1: How to set specific values ​​for each serving cell

[0135] Information elements (IEs) for common serving cell settings (e.g., ServingCellConfigCommon) are used to configure cell-specific parameters for a UE's serving cell. When the UE accesses a cell from an idle state, these IEs include parameters that can generally be obtained from the SSB, master information block (MIB), or SIB. Along with these IEs, the network provides information within dedicated signaling when the UE configures a secondary cell (SCell) or additional cell group (SCG). The network also provides information to the UE for special cells (SpCells) (master cell groups (MCGs) and SCGs) when resynchronizing.

[0136] Table 6 shows an example of ServingCellConfigCommon IE.

[0137] [Table 6] JPEG2026534002000011.jpg14139

[0138] Referring to Table 6, the n-TimingAdvanceOffset field (or parameter) applies to all uplink transmissions on the serving cell. TA,offset This indicates the setting. If this field does not exist, the UE applies the values ​​defined for the duplex mode and frequency range (FR) of the serving cell.

[0139] Case 2: A method of applying predefined values ​​to the serving cell according to the duplex mode and frequency range (FR).

[0140] Table 7 exemplifies N TA,offset values.

[0141] [Table 7]

[0142] Referring to Table 7, the value of N TA,offset is determined according to the frequency range (FR) and band of the cell used for uplink transmission. In a case that is neither an E-UTRA-NR coexistence case nor an NB-IoT-NR coexistence case, and that is a FR1 FDD or TDD band, the value of N TA,offset is 25600. In a FR1 FDD band in an E-UTRA-NR and / or NB-IoT-NR coexistence case, the value of N TA,offset is 0. In a FR1 TDD band in an E-UTRA-NR and / or NB-IoT-NR coexistence case, the value of N TA,offset is 39936. For FR2, the value of N TA,offset is 13792.

[0143] As described above, the UE identifies the value of N based on the n-TimingAdvanceOffset field (or parameter) information TA,offset . However, if the UE is not provided with the n-TimingAdvanceOffset field (or parameter) information, the default value of N TA,offset is set to 25600 for the FR1 band. For multiple UL carriers in the same timing advance group (TAG), the UE expects the same n-TimingAdvanceOffset value for all UL carriers, and the 39936 value of N TA,offset may also be provided for the FDD serving cell.

[0144] The Timing Advance Group (TAG) will be discussed below.

[0145] For cells set by RRC and with UL set, TAG refers to a serving cell group that uses the same timing reference cell and the same timing advance value. The TAG containing the SpCell of a MAC individual is called the Primary TAG (PTAG: Primary Timing Advance Group), while the Secondary TAG (STAG: Secondary Timing Advance Group) refers to other TAGs.

[0146] IE for TAG settings (e.g., TAG-Config) is used to set parameters for time-alignment groups.

[0147] Table 8 shows an example of TAG-Config IE.

[0148] [Table 8]

[0149] Referring to Table 8, the tag-Id field (parameter) indicates the TAG of the SpCell or SCell. This field uniquely identifies the TAG within the scope of the cell group.

[0150] Additionally, the timeAlignmentTimer field (parameter) specifies the time alignment timer value ([ms]) for the TAG that has a tag-Id.

[0151] The maximum number of tags may be determined by the standard or the base station, and may be, for example, 4.

[0152] IE for MAC cell group configuration (e.g., MAC-CellGroupConfig) is used to set MAC parameters for cell groups, including DRX (discontinuous reception).

[0153] Table 9 shows an example of a part of MAC-CellGroupConfig IE.

[0154] [Table 9] JPEG2026534002000015.jpg114159

[0155] Referring to Table 9, the TAG-Config IE may be configured through the tag-Config field within the MAC-CellGroupConfig IE.

[0156] An IE (e.g., CellGroupConfig) for configuring cell groups is used to configure a master cell group (MCG) or a secondary cell group (SCG). A cell group is associated with one MAC unit, an RLC (Radio Link Control) unit, and includes a set of logical channels for a primary cell (SpCell) and one or more secondary cells (SCells).

[0157] Table 10 shows an example of a part of CellGroupConfig IE.

[0158] [Table 10]

[0159] Referring to Table 10, the MAC-CellGroupConfig IE may be configured through the mac-CellGroupConfig field within the CellGroupConfig IE.

[0160] The maximum number of secondary cell groups may be determined by a standard or by the base station, and may be, for example, 3.

[0161] Table 11 illustrates the behavior of individual MACs in maintaining uplink time alignment.

[0162] [Table 11] JPEG2026534002000018.jpg99139

[0163] Uplink transmission to uplink receiving point

[0164] In existing wireless communication systems, the operation of multiplexed TRP (M-TRP) based terminals for uplink transmission and downlink reception, and base stations for uplink reception and downlink transmission is defined. Such M-TRP operation may include single DCI (S-DCI) based M-TRP operation, in which a specific TRP transmits control signals to the terminal, and multiple DCI (M-DCI) based M-TRP operation, in which multiple TRPs all transmit control signals to the terminal. In improved wireless communication systems, one or more uplink receive points (or uplink receive-only points, hereinafter referred to as "UL Rx points") additionally placed in macrocells are discussed for terminal uplink coverage compensation.

[0165] Such UL Rx points may be implemented to perform UL reception only without a DL transmit chain in order to reduce base station installation costs. In this case, since the UL Rx point cannot transmit a DL reference signal (RS), the terminal does not know the DL slot boundary (or reference point) for applying TA to the UL Rx point. Furthermore, since the UL Rx point does not transmit SSB, it is impossible to directly apply existing SSB-based RACH procedures to the RACH procedure for acquiring TA related to the timing of the terminal's UL transmission to the UL Rx point. In addition, in existing wireless communication systems, a path loss reference signal (hereinafter referred to as PL-RS) is set as an open-loop parameter for UL power control, but since the UL Rx point does not perform DL transmission, it is not possible to set the DL RS used as PL-RS at the terminal. Moreover, even if the terminal has the capability for beam correspondence, it is not possible to set the DL RS as the reference RS for the terminal's UL transmit beam for a UL Rx point that does not transmit DL RS, so there is a problem that the terminal must find the optimal UL transmit beam for the UL Rx point through its UL beam management operation.

[0166] The following describes various examples of the methods by which the base station schedules uplink transmissions to a terminal and how the terminal acquires and applies a Terminal Arrangement (TA) when the terminal performs uplink transmissions to multiple Rx points (e.g., macrocells and / or UL Rx points) in a particular CC / BWP.

[0167] In this disclosure, the definition of information / value can mean that the base station and the terminal know the information / value in advance without any signaling / instruction between the base station and the terminal for that information. In this disclosure, the setting of information / value on a terminal can mean that the base station provides the information / value to the terminal through higher layer (e.g., L3) signaling. In this disclosure, the instruction of information / value on a terminal can mean that the base station provides the information / value to the terminal through L2 / L1 signaling such as MAC CE or DCI.

[0168] Furthermore, the scope of this disclosure is not limited by the terms macrocell and UL Rx point in the following description. For example, in this disclosure, macrocell may be used as a term representing a base station or cell that supports both DL and UL transmission / reception, and UL Rx point (or Rx-only point, or UL TRP) may be used as a term representing a base station or cell that supports only UL reception. For example, UL Rx point may correspond to an RRH (radio remote head), or functionally, macrocell may correspond to a CU (central unit) and a DU (distributed unit), or to a DU, and UL Rx point may correspond to a RU (radio unit). It may also be assumed that the macrocell and UL Rx point are connected by an ideal backhaul and that there is little to no delay in information exchange between them.

[0169] Figure 10 is a diagram illustrating the operation of a terminal according to one embodiment of the present disclosure.

[0170] In step S1010, the terminal can receive first information from the first network node relating to the SSB and / or RS of the first network node.

[0171] In step S1020, the terminal can send a random access preamble to the second network node based on the first information.

[0172] The downlink reference timing or pathloss offset for random access preamble transmission may be determined by the terminal based on one or more of the SSB or RS values ​​of the first information. For example, the transmit beam and / or PL-RS of the random access preamble (or PRACH) may be determined based on the SSB / RS values ​​of the first information.

[0173] Such first information may be included in the PDCCH order from the first network node to the terminal. Alternatively, the first information may be provided in advance from the first network node to the terminal via uplink signaling or MAC CE before the terminal receives the PDCCH order related to the random access procedure.

[0174] For example, the first network node may be a macrocell or a TRP (i.e., a network node that supports both DL transmission and UL reception), and the second network node may be a UL Rx point (i.e., a network node that does not support DL transmission but supports UL reception).

[0175] In step S1030, the terminal can receive a Random Access Response (RAR) from the first network node in response to the Random Access Preamble.

[0176] The RAR may include second information related to timing advance (TA) for the second network node.

[0177] The quasi-co-location (QCL) assumption for a PDSCH carrying a RAR and / or a PDCCH scheduling said PDSCH may be based on the SSB of first information provided by the first network. Alternatively, the QCL assumption for a PDSCH carrying a RAR and / or a PDCCH scheduling said PDSCH may be based on the RS of first information and / or on QCL information set for a control resource set (CORESET) associated with a Type-1 common search space (CSS) for a first network node.

[0178] RA-RNTI (random access-RNTI) related to monitoring a PDCCH (or DCI containing scheduling information for said PDSCH) that schedules a PDSCH that carries RAR may be calculated based on one or more of the symbol index, slot index, or frequency domain index of a PRACH opportunity (occasion) or RACH opportunity (RO) based on the SSB of the first information.

[0179] As an addition or alternative, after obtaining a TA for the second network node, the terminal may expect the reference point (or wireless frame boundary) for applying the TA value to be the same as the DL reference point for the first network node; or the terminal may be given a definition / setting / instruction of the difference (or offset) between the DL reference point of the second network node and the DL reference point of the first network node; or the value of the N_TA_offset parameter may be defined / set / instructed separately for the second network node (i.e., in addition to the value of the parameter for the first network node).

[0180] As an addition or alternative, an SRS resource set / SRS resource for the second network node may be configured separately (for example, in addition to the SRS resource set / SRS resource for the first network node). Based on this, a TA instruction (TAC) corresponding to an absolute value or a TAC corresponding to a relative value may be instructed to the terminal via MAC CE in order to correct the TA for the second network node.

[0181] After obtaining a TA for the second network node in this way, the terminal can perform an uplink transmission to the second network node based on the obtained TA.

[0182] The TA acquisition operation of the terminal to the second network node, as described above, may be performed after the terminal has been provided with settings related to the second network node (from the first network node) (i.e., based on those settings). For example, the settings related to the second network node may include information related to the TA settings described above, and / or (after TA acquisition to the second network node) may include settings related to the transmission and reception operations between the first and second network nodes and the terminal.

[0183] For example, distinct time and / or frequency resources may be allocated to the first and second network nodes. Additionally or alternatively, UL channel / signal resources may be configured separately for the first and second network nodes. Additionally or alternatively, power control parameters / TA parameters / beam-related parameters may be configured separately for the first and second network nodes. Additionally or alternatively, different CORESET pool indices may be configured for the first and second network nodes, in which case the terminal can only perform UL transmissions for the CORESET pool indices corresponding to the second network node. Additionally or alternatively, SRS resource sets may be configured separately for the first and second network nodes. Additionally or alternatively, joint / individual TCI states may be configured separately for the first and second network nodes. As an additional or alternative, HARQ process IDs may be set separately for the first and second network nodes, and power control parameters / TA parameters / beam-related parameters may be set separately for each HARQ process ID.

[0184] For example, a first TAG associated with a first network node and a second TAG associated with a second network node may be set for the terminal. In this case, the second information related to the TA included in the RAR in step S1030 may be applied to the second TAG. Also, a first TCI state for the first TAG and a second TCI state for the second TAG may be set / instructed to the terminal. In this case, uplink transmission from the terminal to the second network node may be performed based on the second TCI state. As a further example of the above example, a path loss offset (or reference point) associated with the second TCI state may be applied to random access preamble transmission to the second network node.

[0185] The method illustrated in the example in Figure 10 may be performed by the first wireless device 100 shown in Figure 12, which will be described later. For example, one or more processors 102 of the first wireless device 100 in Figure 12 may be configured to receive first information related to one or more of the SSB or RS of the first network node from the first network node via one or more transceivers 106 by a terminal; transmit a random access preamble to the second network node via one or more transceivers 106 by a terminal based on the first information; and receive a RAR in response to the random access preamble from the first network node via one or more transceivers 106 by a terminal. The RAR may include second information related to the TA for the second network node. One or more memories 104 of the first wireless device 100 may store instructions for performing the method illustrated in Figure 10 or the example described later when executed by one or more processors 102.

[0186] Figure 11 is a diagram illustrating the operation of a base station according to one embodiment of the present disclosure.

[0187] In step S1110, the first network node can transmit first information relating to the SSB and / or RS of the first network node to the terminal.

[0188] In step S1120, the first network node can send a RAR to the terminal in response to the random access preamble sent by the terminal to the second network node based on the first information.

[0189] For example, the connection between the first and second network nodes can be assumed to be an ideal backhaul (i.e., with little to no delay in information exchange between them). This allows the first network node to assume that it knows without delay that the second network node has received a random access preamble from a terminal. For example, if the second network node receives a random access preamble from a terminal, it can notify the first network node of this.

[0190] The specific characteristics of the first information, second information, random access preamble, and RAR are the same as those described with reference to the example in Figure 10, and redundant explanations will be omitted.

[0191] The method illustrated in the example in Figure 11 may be performed by the second wireless device 200 shown in Figure 12, which will be described later. For example, one or more processors 202 of the second wireless device 200 in Figure 12 may be configured to transmit first information related to one or more of the SSB or RS of the first network node to a terminal via one or more transceivers 206 by the first network node; and transmit RAR in response to a random access preamble transmitted to the second network node by the terminal based on the first information via one or more transceivers 206 by the first network node. The RAR may include second information related to the TA for the second network node. One or more memories 204 of the second wireless device 200 may store instructions for performing the method illustrated in Figure 11 or the example described later, when executed by one or more processors 202.

[0192] The following describes various examples of the operational procedures for macrocells and UL Rx points related to this disclosure, as well as the procedures for terminal TA acquisition for UL Rx points.

[0193] Example 1

[0194] This embodiment relates to the operation of macrocells (e.g., first network node) and UL Rx points (e.g., second network node) and terminal operation schemes.

[0195] Between the base station and the terminal, the UL Rx point may operate or be run based on one or more of the following embodiments 1-1 to 1-4.

[0196] Example 1-1

[0197] Macrocells and UL Rx points may be allocated separate frequency-domain resources and / or time-domain resources.

[0198] Example 1-1-1

[0199] Base stations can allocate macrocell uplinks and UL Rx point uplinks to separate frequency resources.

[0200] For example, a base station can configure both a macrocell uplink and a UL Rx point uplink for the same UL BWP and allocate them to independent (or separate) frequency resources within that UL BWP. In the following description, "independent" and "separate" mean distinct from each other, but may be the same or different from each other.

[0201] Alternatively, the base station can configure the macrocell uplink and the UL Rx point uplink for separate UL BWPs. That is, power control, timing advance, uplink beam-related parameters / resources, etc., can be configured independently (or differently) for each separate UL BWP.

[0202] As an additional or alternative, base stations can also utilize specific SUL (supplementary UL) carriers for UL Rx point uplinks.

[0203] This allows power control, timing advance, and uplink beam-related parameters / resources to be set / managed separately for uplink transmission to UL Rx points that are physically located differently from macrocells.

[0204] Example 1-1-2

[0205] The base station can allocate macrocell uplinks and UL Rx point uplinks to different time resources.

[0206] For example, in a downlink / uplink / flexible slot configuration pattern configured via a higher-layer signal such as TDD-UL-DL-ConfigCommon or / and TDD-UL-DL-ConfigDedicated, information indicating that certain uplink slots (and / or flexible slots) are used for macrocells and the remaining slots are used for UL Rx points may be transmitted to the terminal via a higher-layer signal (e.g., RRC or MAC CE). TDD-UL-DL-ConfigCommon or / and TDD-UL-DL-ConfigDedicated may be used for transmitting such information.

[0207] This allows terminals to perform uplink transmissions based on different power control, timing advance, uplink beam-related parameters, etc., for distinct uplink resources, depending on which time resources the base station allocates as uplink resources for which target (i.e., whether the uplink resources are allocated to macrocells or UL Rx points).

[0208] Examples 1-2

[0209] The base station can configure each UL channel / signal (e.g., PRACH, PUCCH, PUSCH, and / or SRS) separately for the UL channel / signal to the macrocell and for the UL Rx point, and can configure {power control, timing advance, uplink beam} related parameters independently (or differently) for each UL channel / signal.

[0210] For example, this embodiment may be applied assuming that the above-described embodiment 1-1 does not apply (i.e., the same frequency / time domain resources are used for the macrocell and the UL Rx point).

[0211] Example 1-2-1

[0212] UL channels / signals for macrocells (e.g., UL channel / signal resources / resource sets) and UL channels / signals for UL Rx points (e.g., UL channel / signal resources / resource sets) may be configured separately.

[0213] For example, PUCCH resources for macrocells and PUCCH resources for UL Rx points may be configured separately.

[0214] As an addition or alternative, separate codebook-based (CB) / non-codebook-based (NCB) SRS resource sets may be configured for macrocells and for UL Rx points. This allows for the distinction between push transmission scheduling for macrocells and push transmission scheduling for UL Rx points based on the SRI (SRS resource indicator) field and / or the code point in the SRI field within the DCI.

[0215] Alternatively, SRS resources / SRS resource sets may be configured separately for each target (e.g., macrocells and UL Rx points), thereby distinguishing between push transmissions to macrocells and push transmissions to UL Rx points.

[0216] As an additional or alternative, CG (configured grant) PUSCH resources may be configured (for example, separately for macrocells and UL Rx points), thereby differentiating the scheduling of CG PUSCH transmissions for macrocells and CG PUSCH transmissions for UL Rx points.

[0217] As an additional or alternative, the PRACH resources for macrocells and the PRACH resources for UL Rx points may be configured independently (or differently).

[0218] Example 1-2-2

[0219] UL channel / signal-related parameters for macrocells (e.g., power control (PC), timing advance (TA), uplink beam-related parameters) and UL channel / signal-related parameters for UL Rx points (e.g., PC, TA, uplink beam-related parameters) may be set independently (or differently). That is, for the same UL channel / signal resource, the values ​​of the PC / TA / beam-related parameters for macrocells and the PC / TA / beam-related parameters for UL Rx points may be set differently from each other.

[0220] For example, multiple (e.g., two) PC / TA / beam-related parameters may be set / instructed for the same PUCCH resource to both the macrocell and the UL Rx point. That is, the terminal can utilize specific parameters from among the multiple uplink transmission parameters depending on whether the transmission target is a macrocell or a UL Rx point. Additionally or alternatively, if the base station is configured / instructed to transmit the resource with the multiple transmission parameters set / instructed to both the macrocell and the UL Rx point simultaneously, the terminal can also utilize each transmission parameter to transmit the resource to both the macrocell and the UL Rx point simultaneously.

[0221] Examples 1-3

[0222] A base station may be configured to associate macrocells and UL Rx points with different CORESET pool indices. This distinguishes PC / TA / beam-related parameters / resources associated with a first CORESET pool index from those associated with a second CORESET pool index, allowing transmission parameters to be set / applied independently (or differently) for each target (i.e., macrocells and UL Rx points). For example, power control, timing advance, and uplink beam-related parameters / resources may be set / managed differently (for each CORESET pool index) for uplink transmission to a UL Rx point that is physically located differently from a macrocell.

[0223] For example, this embodiment may apply when the uplink to a macrocell and the uplink to a UL Rx point are assigned within the same UL BWP.

[0224] Example 1-3-1

[0225] If you configure macrocells and UL Rx points to be associated with different CORESET pool indexes, you may configure the terminal to only send uplinks to the CORESET pool index associated with the UL Rx point.

[0226] For example, in M-DCI-based M-TRP operation, it is possible to configure / instruct only uplink transmissions for a specific CORESET pool index. In this case, similar to the configuration of two CB / NCB SRS resource sets in the M-TRP STxMP (simultaneous transmission across multi-panel) PUSCH transmission scheme, a separate CB / NCB SRS resource set may be configured for the macrocell and a separate CB / NCB SRS resource set for the UL Rx point (i.e., two distinct CB / NCB SRS resource sets are configured for the terminal). This allows for a one-to-one association between the CB / NCB SRS resource set for the macrocell and a specific CORESET pool index (e.g., the first CORESET pool index), and a one-to-one association between the CB / NCB SRS resource set for the UL Rx point and another specific CORESET pool index (e.g., the second CORESET pool index).

[0227] In the UL grant DCI at the time of PUSCH scheduling, the target of uplink transmission (i.e., macro cell or UL Rx point) may differ depending on which SRS resource set of the two SRS resource sets the SRI indication included therein is associated with. Accordingly, power control, timing advance, and uplink beam-related parameters for uplink transmission may be applied differently for each target. Furthermore, when all SRIs associated with the two SRS resource sets (i.e., two SRIs) are indicated by utilizing a plurality of SRI indications via the UL grant DCI, and the base station configures / indicates to transmit PUSCH simultaneously to the macro cell and the UL Rx point, the terminal can transmit the PUSCH simultaneously to the macro cell and the UL Rx point by using respective transmission parameters.

[0228] Also in the case of PUCCH / SRS, power control, timing advance, and uplink beam-related parameters for the macro cell and / or the UL Rx point may be applied during terminal uplink transmission, depending on which one or more CORESET pool indices (or which one or more CB / NCB SRS resource sets) the resource is associated with.

[0229] Example 1-3-2

[0230] In S-DCI-based M-TRP operation, similar to the PUSCH repetition method (assuming, as mentioned above, that the uplink to the macrocell and the uplink to the UL Rx point are allocated within the same UL BWP), the CORESET pool index may not be set, and separate CB / NCB SRS resource sets may be configured for macrocell use and for UL Rx point use. In this case, the two SRS resource sets will have a one-to-one correspondence with a specific PUSCH TO (transmission occasion) group during PUSCH repetition transmissions, so that terminals can perform PUSCH repetition transmissions to macrocells and UL Rx points in response to the base station scheduling PUSCH repetition transmissions.

[0231] For example, in the first TO group, repeated push transmissions may be made to a macrocell, and in the second TO group, repeated push transmissions may be made to a UL Rx point. Here, transmissions to an S-TRP (i.e., either a macrocell or a UL Rx point) may be made by an SRI instruction (or by an SRS resource set indicator field). In each TO group, depending on whether the transmission target is a macrocell or a UL Rx point (or depending on which SRI and TPMI associated with which SRS resource set are indicated), the terminal may utilize specific parameters associated with the target / SRS resource set from among several uplink transmission parameters associated with SRS resource sets (e.g., power control, timing advance, uplink beam-related parameters).

[0232] In the case of PUCCH / SRS, depending on which CB / NCB SRS resource set the resource is associated with, macrocell-specific or UL Rx point-specific power control, timing advance, and uplink beam-related parameters may be applied during terminal uplink transmission.

[0233] Examples 1-4

[0234] A base station can configure macrocells and UL Rx points to be associated with different joint and / or separate (UL) TCI states within a unified TCI framework. In this case, since each of the different joint / separate (UL) TCI states has information related to power control, timing advance, and transmit beam, respectively, the base station may distinguish whether the target of an uplink transmission at a terminal is a macrocell or a UL Rx point depending on which joint / separate (UL) TCI state it utilizes for uplink transmission.

[0235] For example, in an extension of the integrated TCI state for M-TRP operation, the number of receive and transmit common beams may be extended to two for TRP-specific common beam management, and such two designated TCI states (i.e., a joint TCI state and / or a separated UL TCI state) can be applied to uplink transmissions to macrocells and UL Rx points.

[0236] Example 2

[0237] This embodiment relates to a method for acquiring terminal TA (Time Attorney) data for a UL Rx point.

[0238] In the example of Embodiment 1 described above, HARQ process IDs may be defined / set separately for the macrocell and the UL Rx point. Power control, TA, and transmit beam-related parameters for uplink transmission may be applied to the HARQ process ID for the macrocell and the HARQ process ID for the UL Rx point, respectively. Even assuming that the macrocell and the UL Rx point are connected by an ideal backhaul, given the difficulty of actually implementing soft combining of the uplink signals received from the terminals at the macrocell and UL Rx point in the fronthaul stage, it would be appropriate to distinguish the transmit-related parameters for each target through separate HARQ processes.

[0239] As mentioned above, UL Rx points do not have a DL Tx chain to reduce base station installation costs and can only perform UL reception, which means they have the limitation that they cannot transmit DL RS to terminals. Therefore, when a terminal transmits uplink to a UL Rx point, it cannot measure / determine the DL slot boundary (or reference point) for TA application, and there is no SSB transmission from the UL Rx point, so there is no reference information for random access preamble selection and / or random access preamble transmission timing when transmitting RACH / PRACH for TA acquisition, resulting in uncertainty in terminal operation.

[0240] The following describes various examples of this disclosure relating to obtaining timing advance information for a UL Rx point for terminal uplink transmission to the UL Rx point.

[0241] Example 2-1

[0242] This embodiment relates to the definition or configuration of a reference point for applying a corresponding TA value (e.g., the value of the N_TA and / or N_TA,offset parameter) after a terminal acquires a timing advance (TA) for a UL Rx point. The reference point may correspond to the boundary of a downlink radio frame for applying the TA value.

[0243] Example 2-1-1

[0244] The terminal can expect that the reference point of the UL Rx point is the same as the DL reference point of the macro cell. Additionally or alternatively, in the deployment / implementation of the base station, a constraint that the DL reference point of the macro cell and the reference point of the UL Rx point are the same may be applied. In this case, the following reference point definition for a specific cell (e.g., SpCell / SCell) of the terminal may be applied to the UL Rx point.

[0245] For terminal transmission timing, the terminal may have the capability to follow the frame timing change of the reference cell when transmitting PUSCH on a CG (configured grant) resource for SDT (small data transmission) in an RRC connected state or in an RRC inactive state. As described above, uplink frame transmission starts from the reception time point of the first detected path (in time) of the corresponding downlink frame from the reference cell (N TA +N TA,offset )*T cThis may be performed at a previous point in time. For the PTAG serving cell, the terminal may use the SpCell as a reference cell for deriving the transmission timing for the PTAG cell. For the STAG serving cell, the terminal may use any one of the activated SCells as a reference cell for deriving the transmission timing for the STAG cell. The initial transmission timing accuracy and gradual timing adjustment requirements of the terminal may be defined.

[0246] Example 2-1-2

[0247] For defining the reference point of the UL Rx point, an offset value between the DL reference point of the macro cell and the reference point of the UL Rx point may be configured / indicated from the base station to the terminal. This may be applied when there is a reference point difference between the macro cell and the UL Rx point, and an offset value of 0 may be configured / indicated even when there is no difference. When there are multiple UL Rx points associated with one macro cell, the offset value may be separately (or differently) configured / indicated for each of the multiple UL Rx points.

[0248] For example, the offset value may be represented by N of the TA command as described above TA value (here, T A =0, 1, 2, ..., 3846 indicated by an index value), or may be represented by T in the relative TA command as described above A =0, 1, 2, ..., 63 (a multiple thereof).

[0249] As another example, the offset value may be predefined as a specific value (e.g., a positive / negative real number), and any one of the predefined values may be configured / indicated to the terminal as the offset value related to the reference point of the UL Rx point.

[0250] Since DL radio frames do not exist / are not defined in UL Rx points, the reference point for a UL Rx point may be defined as a UL reference point, virtual point, or virtual reference point instead of a DL reference point.

[0251] Example 2-1-3

[0252] For the definition of the reference point of the UL Rx point, N for the UL Rx point TA,offset The value may be defined / set. N for UL Rxpoint TA,offset The parameter is N for macrocells. TA,offset It may be defined / set as a parameter distinct from other parameters. This may apply when there is a difference in reference points between the macrocell and the UL Rx point, or even when there is no difference, it may be the same N as the macrocell. TA,offset The value may be defined / set. If there are multiple UL Rx points associated with one macrocell, N will be defined for each of the multiple UL Rx points. TA,offset The parameter values ​​may be set / specified separately (or differently).

[0253] N for macrocells (i.e., existing) TA,offset The parameters correspond to TDD / FDD bandwidth-specific values ​​and are either predefined or signaled to the terminal by the base station configuration. This is distinct from the N for UL Rx point. TA,offset The parameters may be set by the base station for the terminal and / or predefined.

[0254] In the aforementioned Example 2-1, the base station can signal to the terminal whether any of Examples 2-1-1, 2-1-2, or 2-1-3 applies, depending on whether or not there is a reference point difference between the macrocell and the UL Rx point. For example, in Examples 2-1-2 and 2-1-3, the offset value or N for (multiple) UL Rx points. TA,offset The base station can signal information to the terminal regarding when the value is applied.

[0255] Example 2-2

[0256] This embodiment relates to a method for acquiring a TA for a terminal's UL Rx point and a method for instructing / updating the TA for a UL Rx point. In the following example, for the purpose of managing the TA value for a UL Rx point, the TA value for a UL Rx point may be managed as a TAG different from that of a macrocell, or it may be managed by a predetermined offset value relative to the TA value of a macrocell.

[0257] Example 2-2-1

[0258] Similar to Example 2-1, if a reference point for uplink transmission to a UL Rx point is defined / configured, the terminal can transmit uplink transmissions to the configured / instructed UL Rx point relative to that reference point. In this case, the base station does not need to perform any separate operation for the terminal to acquire the TA. Subsequently, the base station can provide a TA command to the UL Rx point by utilizing absolute / relative TA commands (e.g., MAC CE) to correct the terminal's TA value to the UL Rx point.

[0259] Example 2-2-2

[0260] A terminal can send RACH / PRACH to a UL Rx point. For example, RACH / PRACH may be sent to a UL Rx point based on a PDCCH order. The PDCCH order may be provided to the terminal from the macrocell. After receiving RACH / PRACH at the UL Rx point, the base station can instruct the terminal of the TA value for the UL Rx point through a RAR (e.g., an absolute TA instruction field included in the RAR) sent from the macrocell to the terminal. That is, the RAR in response to the RACH / PRACH sent to the UL Rx point may be received from the macrocell. For example, the RAR may be received through a CORESET associated with type-1CSS (common search space).

[0261] In connection with this, it may be helpful to apply a PL (path loss) offset to PRACH transmitted to a UL Rx point based on the PDCCH order. Based on the PDCCH order, DL reference timing determination for PRACH transmission to a UL Rx point may be based on DL RS as defined beforehand. For example, DL RS such as macrocell SSB and / or CSI-RS may be used for DL ​​reference timing determination to the UL Rx point or applied as PL reference RS. Alternatively, for PL offset indication for PRACH transmission based on the PDCCH order, a PL offset associated with the joint / UL TCI state indicated for the UL Rx point in the integrated TCI framework may be applied to PDCCH order-based PRACH transmission.

[0262] Specifically, since UL Rx points do not transmit SSBs, it is necessary to solve the problem of difficulty in power control and transmit beam information setting for RACH / PRACH transmission. To this end, i) the base station can instruct the terminal to use a specific SSB of the macrocell via PDCCH order, so that the terminal can utilize the RACH / PRACH resources associated with that SSB, and the terminal can apply that SSB as the transmit beam RS and / or PL RS (or PL reference RS) and transmit RACH / PRACH based on it. Or, ii) the base station can instruct the terminal to use a specific SSB of the macrocell via PDCCH order, so that the terminal can utilize the RACH / PRACH resources associated with that SSB, and the transmit beam RS and / or PL RS determined in another manner will be applied instead of the macrocell's SSB, so that the terminal can transmit RACH / PRACH based on it. Or, iii) the terminal can apply the transmit beam RS and / or PL RS determined in another manner without any instruction on the base station's SSB. For example, for RACH / PRACH transmission beams determined by other methods, a beam management SRS transmitted in advance by a terminal may be used as the reference RS for the RACH / PRACH transmission beam.

[0263] Various examples of transmit beam / PL RS application for RACH / PRACH transmissions (e.g., i), ii), and / or iii) described above) may be selectively applied (e.g., switched / controlled) by the base station. For example, when a base station sends a PDCCH order to a terminal that triggers a RACH / PRACH transmission to a UL Rx point, information indicating whether the terminal should transmit RACH / PRACH based on the terminal's received beam to the macrocell's SSB (e.g., example i)) or based on a beam direction different from the terminal's received beam to the macrocell's SSB (e.g., example ii) or iii)) may be included in the DCI corresponding to the PDCCH order.

[0264] The QCL assumptions applied to the reception of a RAR (i.e., a PDCCH / DCI scheduling a PDSCH carrying a RAR, and / or a PDSCH carrying a RAR) in response to a random access preamble after a random access preamble transmission via RACH / PRACH to a UL Rx point may be applied as exemplified below. For example, if a RACH / PRACH transmission is made based on the macrocell's SSB according to example i) above, the indicated macrocell's SSB may be used as the QCL RS for RAR reception. Or, if a RACH / PRACH transmission is made based on the transmit beam RS and / or PL RS determined in another manner according to example ii) or iii) above, the transmit beam RS and / or PL RS may be used as the QCL RS for RAR reception. Additionally or alternatively, the QCL information (or TCI state) set for a CORESET associated with a type-1CSS used for RAR reception (of a macrocell) as described above may be used as the QCL RS for RAR reception.

[0265] When a RAR scheduling PDCCH / DCI is received after a RACH / PRACH has been sent to a cell that supports both DL and UL, the RA-RNTI applicable to monitoring the PDCCH / DCI may be computed based on the RACH occasion (RO), and the PDCCH / DCI may be received based on this identification information. The RA-RNTI for monitoring a RAR scheduling PDCCH / DCI in response to a RACH / PRACH / random access preamble sent to a UL Rx point may be computed by the following example: For example, if a RACH / PRACH transmission is performed / triggered based on a specific SSB of a macrocell, as in example i) or ii) above, the RA-RNTI may be computed based on RO information (e.g., symbol index, slot index, frequency domain index) based on that specific SSB of the macrocell, and the RAR scheduling PDCCH / DCI may be received based on this. Alternatively, as in example iii) above, if the transmission is not based on a specific SSB or if RACH / PRACH transmission is performed, the terminal may calculate a separate RA-RNTI and receive the RAR scheduling PDCCH / DCI based on this.

[0266] The RA-RNTI for a 4-step RACH procedure may be calculated as follows: The RA-RNTI associated with a PRACH opportunity (occasion) in which a random access preamble is sent may be calculated by the formula RA-RNTI = 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id, where s_id is the index of the first OFDM symbol of the PRACH opportunity (0 ≤ s_id < 14). t_id is the index of the first slot of the PRACH opportunity in the system frame (0 ≤ t_id < 80), where the subcarrier spacing for determining t_id may be based on subcarrier spacing setting indices μ (= 0, 1, 2, 3) and μ (= 5, 6). For example, t_id may correspond to the slot index based on 120 kHz subcarrier spacing in the system frame containing the PRACH opportunity. f_id is the index of the PRACH opportunity in the frequency domain (0 ≤ f_id < 8). ul_carrier_id is the index of the UL carrier used for random access preamble transmission, and its value may be 0 for NUL (normal uplink) carriers and 1 for SUL (supplementary uplink) carriers. In the 2-step RACH procedure, the MSGB-RNTI associated with the PRACH opportunity (occasion) for which the random access preamble is transmitted may be calculated by the formula MSGB-RNTI = 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id + 14 × 80 × 8 × 2.

[0267] The example in Example 2-2 may also apply when a terminal sends RACH / PRACH to perform initial access. For example, RACH / PRACH information associated with a UL Rx point (e.g., a higher-level information element RACH-config containing information about RACH resources such as the SSB index, RACH preamble, and RACH opportunity) may be included in a specific SIB (system information block). Based on the information included in the SIB, a terminal can send RACH / PRACH to the UL Rx point when performing the initial access procedure.

[0268] Example 2-2-3

[0269] A separate SRS resource set and / or SRS resources for RACH-like SRS may be configured on the terminal. Based on the reception of RACH-like SRS transmitted by the terminal, the base station can then provide the terminal with a TA command for the UL Rx point, utilizing absolute / relative TA commands (e.g., MAC CE) to correct the TA value for the terminal's UL Rx point. The aforementioned specific SRS resources for RACH-like SRS may consist of N or more symbols and time / frequency domain resources with a bandwidth of X kHz or more (where N and X are positive natural numbers). This allows the base station to solve the problem of inaccurate TA acquisition due to insufficient granularity in existing SRS reception.

[0270] General equipment to which this disclosure applies

[0271] Figure 12 is a block diagram of a wireless communication device according to one embodiment of the present disclosure.

[0272] Referring to Figure 12, the first wireless device 100 and the second wireless device 200 can transmit and receive wireless signals using various wireless connection technologies (e.g., LTE, NR).

[0273] The first wireless device 100 includes one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106 and be configured to embody the descriptions, functions, procedures, suggestions, methods and / or operation sequence diagrams disclosed herein. For example, the processor 102 may process information in the memory 104 to generate first information / signals and then transmit a wireless signal containing the first information / signals from the transceiver 106. Alternatively, the processor 102 may receive a wireless signal containing second information / signals from the transceiver 106 and then store information obtained from signal processing of the second information / signals in the memory 104. The memory 104 may be linked to the processor 102 and can store various information related to the operation of the processor 102. For example, memory 104 may store software code that includes instructions for performing some or all of the processes controlled by processor 102, or for performing the descriptions, functions, procedures, suggestions, methods and / or operation sequence diagrams disclosed in this disclosure. Here, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to embody wireless communication technology (e.g., LTE, NR). Transceiver 106 may be coupled with processor 102 and may transmit and / or receive radio signals via one or more antennas 108. Transceiver 106 may include a transmitter and / or receiver. Transceiver 106 may be replaced with an RF (Radio Frequency) unit. In this disclosure, radio equipment may mean a communication modem / circuit / chip.

[0274] The second wireless device 200 includes one or more processors 202, one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceivers 206 and be configured to embody the descriptions, functions, procedures, suggestions, methods and / or operation sequence diagrams disclosed herein. For example, the processor 202 may process information in the memory 204 to generate third information / signals and then transmit a wireless signal containing the third information / signals from the transceiver 206. Alternatively, the processor 202 may receive a wireless signal containing fourth information / signals from the transceiver 206 and then store information obtained from signal processing of the fourth information / signals in the memory 204. The memory 204 may be linked to the processor 202 and can store various information related to the operation of the processor 202. For example, memory 204 may store software code that includes instructions for performing some or all of the processes controlled by processor 202, or for performing the descriptions, functions, procedures, suggestions, methods and / or operation sequence diagrams disclosed in this disclosure. Here, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to embody wireless communication technology (e.g., LTE, NR). Transceiver 206 may be coupled with processor 202 and can transmit and / or receive radio signals via one or more antennas 208. Transceiver 206 may include a transmitter and / or receiver. Transceiver 206 may be replaced with an RF unit. In this disclosure, wireless equipment may mean a communication modem / circuit / chip.

[0275] The hardware elements of the wireless devices 100,200 will be described in more detail below. However, one or more protocol layers may be embodied by one or more processors 102,202. For example, one or more processors 102,202 may embodied one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors 102,202 may generate one or more PDUs (Protocol Data Units) and / or one or more SDUs (Service Data Units) by means of the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams disclosed in this disclosure. One or more processors 102,202 may generate messages, control information, data or information by means of the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams disclosed in this disclosure. One or more processors 102,202 can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information by means of the functions, procedures, suggestions, and / or methods disclosed in this disclosure and provide them to one or more transceivers 106,206. One or more processors 102,202 can receive signals (e.g., baseband signals) from one or more transceivers 106,206 and can acquire PDUs, SDUs, messages, control information, data, or information by means of the descriptions, functions, procedures, suggestions, methods, and / or operation sequence diagrams disclosed in this disclosure.

[0276] One or more processors 102,202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102,202 may be embodied by hardware, firmware, software, or a combination thereof. For example, one or more ASICs (Application Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processing Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field Programmable Gate Arrays) may be included in one or more processors 102,202. The descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams disclosed in this disclosure may be embodied using firmware or software, and the firmware or software may be embodied to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and / or sequence diagrams disclosed in this disclosure may be contained in one or more processors 102,202 or stored in one or more memories 104,204 and driven by one or more processors 102,202. The descriptions, functions, procedures, suggestions, methods and / or sequence diagrams disclosed in this disclosure may be embodied by firmware or software in the form of code, instructions and / or sets of instructions.

[0277] One or more memories 104,204 may be connected to one or more processors 102,202 and can store various forms of data, signals, messages, information, programs, code, instructions and / or commands. One or more memories 104,204 may consist of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media and / or combinations thereof. One or more memories 104,204 may be located inside and / or outside of one or more processors 102,202. Furthermore, one or more memories 104,204 may be connected to one or more processors 102,202 by various technologies such as wired or wireless connections.

[0278] One or more transceivers 106,206 can transmit user data, control information, radio signals / channels, etc., as referred to in the methods and / or operation sequence diagrams of this disclosure, to one or more other devices. One or more transceivers 106,206 can receive user data, control information, radio signals / channels, etc., as referred to in the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams disclosed in this disclosure, from one or more other devices. For example, one or more transceivers 106,206 may be coupled with one or more processors 102,202 to transmit and receive radio signals. For example, one or more processors 102,202 can control one or more transceivers 106,206 to transmit user data, control information, or radio signals to one or more other devices. Also, one or more processors 102,202 can control one or more transceivers 106,206 to receive user data, control information, or radio signals from one or more other devices. Furthermore, one or more transceivers 106,206 may be connected to one or more antennas 108,208, and one or more transceivers 106,206 may be configured to transmit and receive user data, control information, radio signals / channels, etc., as referred to in the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams disclosed in this disclosure, via one or more antennas 108,208. In this disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106,206 may convert the received user data, control information, radio signals / channels, etc., from RF band signals to baseband signals for processing using one or more processors 102,202. One or more transceivers 106,206 may convert the user data, control information, radio signals / channels, etc., processed by one or more processors 102,202, from baseband signals to RF band signals. To this end, one or more transceivers 106,206 may include (analog) oscillators and / or filters.

[0279] The embodiments described above are combinations of the components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless otherwise explicitly mentioned. Each component or feature may be implemented in a form that does not combine with other components or features. It is also possible to combine some components and / or features to constitute embodiments of the present disclosure. The order of operations described in embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in other embodiments, or replaced by corresponding components or features of other embodiments. It is clear that claims that do not have an explicit reference relationship in the claims may be combined to constitute embodiments, or may be included as new claims by amendment after filing.

[0280] It will be obvious to those skilled in the art that this disclosure can be embodied in other specific forms, provided that the essential features of this disclosure are not deviated from. Therefore, the above-mentioned detailed description should not be constrained in any way and should be considered illustrative. The scope of this disclosure should be determined by a reasonable interpretation of the attached claims, and any modifications within the equivalent scope of this disclosure are included within the scope of this disclosure.

[0281] The scope of this disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that cause an apparatus or computer to perform operations according to the methods of various embodiments, and non-transitory computer-readable medium on which such software or instructions are stored and executable on the apparatus or computer. Instructions available for programming a processing system that performs the features described in this disclosure may be stored on / in a storage medium or computer-readable storage medium, and the features described in this disclosure may be embodied using a computer program product including such storage medium. The storage medium may include, but is not limited to, high-speed random-access memory such as DRAM, SRAM, DDR RAM, or other random-access solid-state memory devices, and may include non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory optionally includes one or more storage devices located remotely from the processor. Memory, or alternatively, non-volatile memory devices within memory, includes non-transitory computer-readable storage medium. The features described in this disclosure may be stored on any one of the machine-readable media and integrated into software and / or firmware that can control the hardware of the processing system and cause the processing system to interact with other mechanisms that utilize the results relating to the embodiments of this disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems and execution environments / containers.

[0282] Here, the wireless communication technologies embodied in the wireless devices 100 and 200 of this disclosure may include, in addition to LTE, NR, and 6G, Narrowband Internet of Things (NB-IoT) for low-power communication. In this case, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be embodied by standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the names mentioned above. Additionally or alternatively, the wireless communication technologies embodied in the wireless devices 100 and 200 of this disclosure may communicate based on LTE-M technology. In this case, for example, LTE-M technology may be an example of LPWAN technology and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be embodied by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the names mentioned above. Additionally or alternatively, wireless communication technologies embodied in the wireless devices 100,200 of this disclosure may include at least one of ZigBee, Bluetooth (registered trademark), and Low Power Wide Area Network (LPWAN), taking low-power communication into consideration, and is not limited to the names mentioned above. As an example, ZigBee technology can generate personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be called by various names.

[0283] [Industrial applicability] Although the method proposed in this disclosure has been described primarily in terms of its application to 3GPP LTE / LTE-A and 5G systems, it is applicable to a variety of other wireless communication systems as well.

[0284] [Claims when filing an international application] [Claim 1] It is a method, The steps include: receiving first information from the first network node via a terminal, relating to one or more of the SSB (synchronization signal / physical broadcast channel block) or the reference signal (RS) of the first network node; The steps include: transmitting a random access preamble to a second network node based on the first information using the aforementioned terminal; The procedure includes the step of receiving a random access response (RAR) from the first network node in response to the random access preamble via the terminal, A method wherein the RAR includes second information related to timing advance (TA) for the second network node. [Claim 2] The method according to claim 1, wherein the downlink reference timing for the random access preamble transmission is based on one or more of the SSB or RS of the first information. [Claim 3] The method according to claim 1, wherein the path loss offset for the random access preamble transmission is based on one or more of the SSB or RS of the first information. [Claim 4] The method according to claim 1, wherein the first information is included in the physical downlink control channel order (PDCCH order) from the first network node to the terminal. [Claim 5] The method according to claim 1, wherein the quasi-co-location (QCL) assumption for one or more physical downlink sharing channels (PDSCHs) that carry the RAR or PDCCHs that schedule the PDSCH is based on the SSB of the first information. [Claim 6] The QCL (quasi co-location) assumption for one or more PDSCHs that transport the RAR or PDCCHs that schedule the PDSCH is: The RS of the first information, or The method according to claim 1, based on one or more QCL pieces of information set for a control resource set (CORESET) associated with a type-1 common search space (CSS) for the first network node. [Claim 7] RA-RNTI (random access-radio network temporary identifier) ​​related to monitoring a PDCCH that schedules a PDSCH that carries the RAR, or monitoring downlink control information (DCI) that includes scheduling information for the PDSCH, The method according to claim 1, calculated based on one or more of the symbol index, slot index, or frequency domain index of the PRACH (physical random access channel) occasions based on the SSB of the first information. [Claim 8] The method according to claim 1, wherein the second information included in the RAR is applied to the second TAG based on the setting of a first timing advance group (TAG) associated with the first network node and a second TAG associated with the second network node for the terminal. [Claim 9] The method according to claim 8, wherein, based on the setting or instruction of a first TCI (transmission configuration indicator) state for the first TAG and a second TCI state for the second TAG to the terminal, an uplink transmission from the terminal to the second network node is performed based on the second TCI state. [Claim 10] The method according to claim 9, wherein the path loss offset associated with the second TCI state is applied to the random access preamble transmission. [Claim 11] The method according to claim 1, wherein, before receiving the first information, the terminal is provided with configuration information for one or more SSBs of the first network node or one or more reference signals (RS) of the first network node. [Claim 12] The aforementioned first network node corresponds to a macrocell, The method according to claim 1, wherein the second network node corresponds to an uplink receiving point. [Claim 13] The method according to claim 12, wherein the uplink receiving point supports uplink reception from one or more terminals, including the terminal, but does not support downlink transmission to the one or more terminals. [Claim 14] It is a device, One or more transceivers, The system comprises one or more processors connected to one or more of the aforementioned transceivers, The one or more processors described above are: The terminal receives first information from the first network node via one or more transceivers, relating to one or more of the SSB (synchronization signal / physical broadcast channel block) or the reference signal (RS) of the first network node. The terminal transmits a random access preamble to the second network node via one or more transceivers based on the first information. The terminal is configured to receive a random access response (RAR) in response to the random access preamble from the first network node via one or more transceivers. The RAR is a device that includes second information related to timing advance (TA) for the second network node. [Claim 15] It is a method, The first network node transmits to a terminal first information relating to one or more of the SSB (synchronization signal / physical broadcast channel block) or the reference signal (RS) of the first network node, The process includes the step of the first network node transmitting a random access response (RAR) to the terminal in response to a random access preamble transmitted by the terminal to the second network node based on the first information, A method wherein the RAR includes second information related to timing advance (TA) for the second network node. [Claim 16] It is a device, One or more transceivers, The system comprises one or more processors connected to one or more of the aforementioned transceivers, The one or more processors described above are: The first network node transmits to the terminal, via one or more transceivers, first information related to one or more of the SSB (synchronization signal / physical broadcast channel block) or the reference signal (RS) of the first network node. The first network node is configured to send a random access response (RAR) to the terminal via one or more transceivers in response to a random access preamble sent by the terminal to the second network node based on the first information. The RAR is a device that includes second information related to timing advance (TA) for the second network node. [Claim 17] A processing device, One or more processors, A processing device comprising: one or more computer memories operably connected to the one or more processors, and storing instructions for performing the method according to any one of claims 1 to 11, based on being executed by the one or more processors. [Claim 18] One or more non-transitory computer-readable media that are executed by one or more processors and store one or more instructions that control the process to perform the method described in any one of claims 1 to 11.

Claims

1. It is a method, The steps include: receiving first information from the first network node via a terminal, relating to one or more of the SSB (synchronization signal / physical broadcast channel block) or the reference signal (RS) of the first network node; The steps include: transmitting a random access preamble to a second network node based on the first information using the aforementioned terminal; The procedure includes the step of receiving a random access response (RAR) in response to the random access preamble from the first network node via the terminal, A method wherein the RAR includes second information related to timing advance (TA) for the second network node.

2. The method according to claim 1, wherein the downlink reference timing for the random access preamble transmission is based on one or more of the SSB or RS of the first information.

3. The method according to claim 1, wherein the path loss offset for the random access preamble transmission is based on one or more of the SSB or RS of the first information.

4. The method according to claim 1, wherein the first information is included in the physical downlink control channel order (PDCCH order) from the first network node to the terminal.

5. The method according to claim 1, wherein the QCL (quasi coordination) assumption for one or more physical downlink sharing channels (PDSCH) that carry the RAR or PDCCHs that schedule the PDSCH is based on the SSB of the first information.

6. The QCL (quasi coordination) assumption for one or more of the PDSCHs that transport the RAR or the PDCCHs that schedule the PDSCH is: The RS of the first information, or The method according to claim 1, based on one or more QCL pieces of information set for a control resource set (CORESET) associated with a Type-1 Common Search Space (CSS) for the first network node.

7. RA-RNTI (random access-radio network temporary identifier), which relates to monitoring a PDCCH that schedules a PDSCH that carries the RAR, or monitoring downlink control information (DCI) that includes scheduling information for the PDSCH, The method according to claim 1, calculated based on one or more symbol indexes, slot indexes, or frequency domain indexes of PRACH (physical random access channel) opportunities (occasions) based on the SSB of the first information.

8. The method according to claim 1, wherein the second information included in the RAR is applied to the second TAG based on the setting of a first timing advance group (TAG) associated with the first network node and a second TAG associated with the second network node for the terminal.

9. The method according to claim 8, wherein, based on the setting or instruction of a first TCI (transmission configuration indicator) state for the first TAG and a second TCI state for the second TAG to the terminal, an uplink transmission from the terminal to the second network node is performed based on the second TCI state.

10. The method according to claim 9, wherein the path loss offset associated with the second TCI state is applied to the random access preamble transmission.

11. The method according to claim 1, wherein, before receiving the first information, setting information for one or more SSBs of the first network node or one or more reference signals (RSs) of the first network node is provided to the terminal.

12. The first network node corresponds to a macrocell, The method according to claim 1, wherein the second network node corresponds to an uplink receiving point.

13. The method according to claim 12, wherein the uplink receiving point supports uplink reception from one or more terminals, including the terminal, but does not support downlink transmission to the one or more terminals.

14. It is a device, One or more transceivers, The system comprises one or more processors connected to one or more of the aforementioned transceivers, The one or more processors described above are: The terminal receives first information from the first network node via one or more transceivers, relating to one or more of the SSB (synchronization signal / physical broadcast channel block) or the reference signal (RS) of the first network node. The terminal transmits a random access preamble to the second network node via one or more transceivers based on the first information. The terminal is configured to receive a random access response (RAR) in response to the random access preamble from the first network node via one or more transceivers. The RAR includes a device that includes second information related to timing advance (TA) for the second network node.

15. It is a method, The first network node transmits to a terminal first information relating to one or more of the SSB (synchronization signal / physical broadcast channel block) or the reference signal (RS) of the first network node, The process includes the step of transmitting a random access response (RAR) from the first network node to the terminal in response to a random access preamble transmitted by the terminal to the second network node based on the first information, A method wherein the RAR includes second information related to timing advance (TA) for the second network node.

16. It is a device, One or more transceivers, The system comprises one or more processors connected to one or more of the aforementioned transceivers, The one or more processors described above are: The first network node transmits to the terminal, via one or more transceivers, first information related to one or more of the SSB (synchronization signal / physical broadcast channel block) or the reference signal (RS) of the first network node, The first network node is configured to send a random access response (RAR) to the terminal via one or more transceivers in response to a random access preamble transmitted by the terminal to the second network node based on the first information. The RAR includes a device that includes second information related to timing advance (TA) for the second network node.

17. A processing device, One or more processors, A processing device comprising: one or more computer memories operably connected to one or more processors, which store instructions for performing the method according to any one of claims 1 to 11, based on that they are executed by the one or more processors.

18. One or more non-transitory computer-readable media that are executed by one or more processors and store one or more instructions that control the method according to any one of claims 1 to 11.

Images