Method and apparatus for performing communication in wireless communication system

WO2025188167A8PCT designated stage Publication Date: 2025-10-02LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2025/099606
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-10-31
Filing Date
2025-03-06
Publication Date
2025-10-02

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in efficiently managing conflicts between downlink reception and uplink transmission during change time intervals, particularly in advanced systems like 6G, which require high data rates, low latency, and reliable connectivity.

Method used

A method and device are provided to prioritize downlink reception over uplink transmission during change time intervals based on information related to a common search space, ensuring seamless communication by managing conflicts between downlink and uplink operations.

Benefits of technology

This approach enhances communication efficiency by prioritizing downlink reception, thereby maintaining system stability and reliability in 6G wireless systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2025099606_02102025_PF_FP_ABST
    Figure KR2025099606_02102025_PF_FP_ABST
Patent Text Reader

Abstract

Provided are a method by which an apparatus performs wireless communication, and an apparatus supporting same. The method may comprise the steps of: acquiring information related to a common search space; and monitoring system information change information in a change time period. For example, on the basis that the information related to the common search space is provided to the apparatus and on the basis that downlink reception related to the system information change information collides with uplink transmission in the change time period, monitoring for the downlink reception can be prioritized in the change time period.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for performing communication in a wireless communication system

[0001] The present disclosure relates to a wireless communication system.

[0002] 5G NR, the successor to LTE (long-term evolution), is a new clean-slate mobile communications system characterized by high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, from low-frequency bands below 1 GHz, mid-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz.

[0003] The 6G (wireless communication) system aims to achieve (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) low energy consumption for battery-free Internet of Things (IoT) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be divided into four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity, and the 6G system can satisfy the requirements as shown in Table 1 below. For example, Table 1 can represent an example of the requirements of a 6G system.

[0004] Maximum data rate per device: 1 Tbps, E2E latency: 1 ms, Maximum spectral efficiency: 100 bps / Hz, Mobility support: Up to 1000 km / hr, Satellite integration: Fully AI, Fully autonomous driving, Fully XR, Fully haptic communication

[0005] The present disclosure provides a device and method for effectively providing services in a wireless communication system. In particular, the present disclosure provides a method and device for communication.

[0006] According to one embodiment of the present disclosure, a method may be provided. For example, the method may include: obtaining information related to a common search space; and monitoring system information change information during a change time interval. For example, based on the information related to the common search space being provided to a device and based on the fact that downlink reception related to the system information change information conflicts with uplink transmission during the change time interval, monitoring for downlink reception may be prioritized during the change time interval.

[0007] According to one embodiment of the present disclosure, a device may be provided. For example, the device may include at least one transceiver; at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the device to: obtain information related to a common search space; and monitor system information change information during a change time interval. For example, based on the information related to the common search space being provided to the device and based on the fact that downlink reception related to the system information change information conflicts with uplink transmission during the change time interval, monitoring for the downlink reception may be prioritized during the change time interval.

[0008] According to one embodiment of the present disclosure, a processing device configured to control a device may be provided. For example, the processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the device to: acquire information related to a common search space; and monitor system information change information during a change time interval. For example, based on the information related to the common search space being provided to the device and based on the fact that downlink reception related to the system information change information conflicts with uplink transmission during the change time interval, monitoring for downlink reception may be prioritized during the change time interval.

[0009] According to one embodiment of the present disclosure, a non-transitory computer-readable storage medium having instructions recorded thereon may be provided. For example, the instructions, when executed, may cause a device to: obtain information related to a common search space; and monitor system information change information during a change time interval. For example, based on the information related to the common search space being provided to the device and based on the fact that downlink reception related to the system information change information conflicts with uplink transmission during the change time interval, monitoring for downlink reception may be prioritized during the change time interval.

[0010] According to one embodiment of the present disclosure, a method may be provided. For example, the method may include: transmitting information related to a common search space; and transmitting system information change information during a change time interval. For example, based on the information related to the common search space being provided to a device and based on the fact that downlink reception related to the system information change information conflicts with uplink transmission during the change time interval, monitoring for the downlink reception may be prioritized during the change time interval.

[0011] According to one embodiment of the present disclosure, a base station may be provided. For example, the base station may include at least one transceiver; at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the base station to: transmit information related to a common search space; and transmit system information change information during a change time interval. For example, based on the information related to the common search space being provided to a device and based on the fact that downlink reception related to the system information change information conflicts with uplink transmission during the change time interval, monitoring for the downlink reception may be prioritized during the change time interval.

[0012] According to one embodiment of the present disclosure, a processing device configured to control a base station may be provided. For example, the processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the base station to: transmit information related to a common search space; and transmit system information change information during a change time interval. For example, based on the information related to the common search space being provided to the device and based on the fact that downlink reception related to the system information change information conflicts with uplink transmission during the change time interval, monitoring for the downlink reception may be prioritized during the change time interval.

[0013] According to one embodiment of the present disclosure, a non-transitory computer-readable storage medium having instructions recorded thereon may be provided. For example, the instructions, when executed, may cause a base station to: transmit information related to a common search space; and transmit system information change information during a change time interval. For example, based on the information related to the common search space being provided to the device and based on the fact that downlink reception related to the system information change information conflicts with uplink transmission during the change time interval, monitoring for the downlink reception may be prioritized during the change time interval.

[0014] The present disclosure can provide a device and method capable of effectively providing services in a wireless communication system. For example, communication can be performed efficiently through the embodiments proposed in the present disclosure.

[0015] Figure 1 illustrates a device-to-device communication procedure according to one embodiment of the present disclosure.

[0016] FIG. 2 illustrates a radio protocol architecture according to one embodiment of the present disclosure.

[0017] FIG. 3 illustrates the structure of a wireless frame according to one embodiment of the present disclosure.

[0018] FIG. 4 illustrates a slot structure of a frame according to one embodiment of the present disclosure.

[0019] FIG. 5 illustrates an example of a BWP according to one embodiment of the present disclosure.

[0020] FIG. 6 illustrates a communication structure that can be provided in a 6G system according to one embodiment of the present disclosure.

[0021] FIG. 7 illustrates an example of a communication scenario based on a 6G system according to one embodiment of the present disclosure.

[0022] FIG. 8 illustrates a procedure for downlink transmission and reception according to one embodiment of the present disclosure.

[0023] FIG. 9 illustrates a procedure for uplink transmission and reception according to one embodiment of the present disclosure.

[0024] FIG. 10 illustrates an example of an NTN according to one embodiment of the present disclosure.

[0025] FIG. 11 illustrates examples of K_offset and K_mac according to one embodiment of the present disclosure.

[0026] FIG. 12 illustrates an example of a UE-specific TA and a common TA according to one embodiment of the present disclosure.

[0027] FIG. 13 illustrates an example of an uplink-downlink timing relationship according to one embodiment of the present disclosure.

[0028] FIG. 14 illustrates an example of TA mismatch within a beam / cell according to one embodiment of the present disclosure.

[0029] FIG. 15 illustrates an HD collision in NTN according to one embodiment of the present disclosure.

[0030] FIG. 16 illustrates an example related to priority rules according to one embodiment of the present disclosure.

[0031] FIG. 17 illustrates a method by which a device performs wireless communication according to one embodiment of the present disclosure.

[0032] FIG. 18 illustrates a method for a base station to perform wireless communication according to one embodiment of the present disclosure.

[0033] FIG. 19 illustrates a communication system (1) according to one embodiment of the present disclosure.

[0034] FIG. 20 illustrates a wireless device according to an embodiment of the present disclosure.

[0035] FIG. 21 illustrates a signal processing circuit for a transmission signal according to one embodiment of the present disclosure.

[0036] FIG. 22 illustrates a wireless device according to an embodiment of the present disclosure.

[0037] FIG. 23 illustrates a mobile device according to one embodiment of the present disclosure.

[0038] FIG. 24 illustrates a vehicle or autonomous vehicle according to one embodiment of the present disclosure.

[0039] In this disclosure, "A or B" can mean "only A," "only B," or "both A and B." In other words, "A or B" in this disclosure can be interpreted as "A and / or B." For example, "A, B or C" in this disclosure can mean "only A," "only B," "only C," or "any combination of A, B and C."

[0040] As used herein, a slash ( / ) or a comma may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B, or C."

[0041] In the present disclosure, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in the present disclosure, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

[0042] Additionally, in the present disclosure, “at least one of A, B and C” can mean “only A,” “only B,” “only C,” or “any combination of A, B and C.” Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C.”

[0043] Additionally, parentheses used in the present disclosure may mean "for example." Specifically, when indicated as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information." In other words, "control information" in the present disclosure is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information."

[0044] In the following explanation, ‘when, if, in case of’ can be replaced with ‘based on’.

[0045] Technical features individually described in one drawing in this disclosure may be implemented individually or simultaneously.

[0046] In the present disclosure, higher layer parameters may be parameters set for the terminal, preset, or predefined. For example, a base station or network may transmit higher layer parameters to the terminal. For example, the higher layer parameters may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0047] In the present disclosure, "setting or defining" may be interpreted as being set or preset to a device through predefined signaling (e.g., SIB, MAC, RRC, DCI (downlink control information), etc.) from a base station or a network. In the present disclosure, "setting or defining" may be interpreted as being set or preset to a device through predefined signaling (e.g., MAC, RRC, SCI (sidelink control information), device-to-device signaling control information, etc.) from another device. In the present disclosure, "setting or defining" may be interpreted as being set or preset to a device.

[0048] In the present disclosure, a user equipment (UE) may refer to a device, a portable device, a wireless device, etc. In the present disclosure, a base station (BS) may refer to a radio access network (RAN) node, a non-terrestrial network (NTN) cell / node, a transmission reception point (TRP), a network, an integrated access and backhaul (IAB) node, a device, a portable device, a wireless device, etc.

[0049] The technology proposed in the present disclosure can be used in various wireless communication systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (evolved UTRA), LTE (long term evolution), and 5G NR.

[0050] The technology proposed in this disclosure can be implemented with 6G wireless technology and applied to various 6G systems. For example, 6G systems can have key factors such as enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), massive machine-type communication (mMTC), artificial intelligence (AI) integrated communication, tactile internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.

[0051] FIG. 1 illustrates a device-to-device communication procedure according to one embodiment of the present disclosure. The embodiment of FIG. 1 may be combined with various embodiments of the present disclosure.

[0052] Referring to FIG. 1, in step S101, a first device and a second device can perform synchronization. For example, the first device can be a terminal and / or at least one of the devices proposed in the present disclosure. For example, the second device can be a base station, a network, a RAN node, an NTN node / cell, a TRP, a terminal and / or at least one of the devices proposed in the present disclosure. For example, the first device can perform an initial cell search operation. For example, the first device can detect at least one synchronization signal transmitted by the second device according to a predefined rule. Here, for example, the synchronization signal can include a plurality of synchronization signals classified according to a structure or purpose (e.g., a primary synchronization signal, a secondary synchronization signal, etc.). Through this, the first device can identify the boundaries of the frame, subframe, time unit, slot, and / or symbol of the second device, and the first device can obtain information about the second device (e.g., a cell identifier).

[0053] In step S103, the first device can obtain system information transmitted by the second device. For example, the system information may include information related to the properties, characteristics, and / or capabilities of the second device required to connect to the second device and use the service. For example, the system information may be classified according to content (e.g., whether it is essential for connection), transmission structure (e.g., channel used, whether provided on-demand), etc. For example, the system information may be classified into a master information block (MIB) and a system information block (SIB). For example, if necessary, the first device may transmit a signal requesting system information prior to receiving the system information. For example, the request and provision of system information may be performed after a random access procedure described below.

[0054] In step S105, the first device and the second device can perform a random access procedure. For example, the first device can transmit and / or receive at least one message (e.g., a random access preamble, a random access response message, etc.) for the random access procedure based on information related to a random access channel of the second device obtained through system information (e.g., channel location, channel structure, structure of supported preamble, etc.). For example, the first device can transmit a preamble (e.g., Msg1) through the random access channel, the first device can receive a random access response message (e.g., Msg2), the first device can transmit a message (e.g., Msg3) including information related to the first device (e.g., identification information) to the second device using scheduling information included in the random access response message, and the first device can receive a message (e.g., Msg4) for contention resolution and / or connection establishment. For example, Msg1 and Msg3 can be sent and received as one message (e.g., MsgA), and / or Msg2 and Msg4 can be sent and received as one message (e.g., MsgB).

[0055] In step S107, the first device and the second device may perform signaling of control information. Here, for example, the control information may be defined in various layers, such as a layer that controls a connection (e.g., a radio resource control (RRC) layer), a layer that handles mapping between logical channels and transport channels (e.g., a media access control (MAC) layer), a layer that handles physical channels (e.g., a physical (PHY) layer), etc. For example, the first device and the second device may perform at least one of signaling for establishing a connection, signaling for determining settings related to communication, and / or signaling for indicating allocated resources. For example, the control information may be signaled / transmitted via a control channel. For example, the control information and / or the control channel may be used to schedule at least one of data, a data channel (e.g., a shared channel), and / or control information on the data channel.

[0056] In step S109, the first device and the second device may transmit and / or receive data. For example, the first device and the second device may process, transmit, and / or receive data based on signaling of control information. For example, when transmitting data, the first device or the second device may perform at least one of channel encoding, rate matching, scrambling, constellation mapping, layer mapping, waveform modulation, antenna mapping, and / or resource mapping on the information bits. For example, when receiving data, the first device or the second device may perform at least one of signal extraction from resources, waveform demodulation for each antenna, signal arrangement considering layer mapping, constellation demapping, descrambling, and / or channel decoding.

[0057] For example, the layers of a radio interface protocol between a first device and a second device can be divided into L1 (layer 1), L2 (layer 2), L3 (layer 3), etc. For example, a physical layer belonging to the first layer can provide an information transfer service using a physical channel, and an RRC (radio resource control) layer located in the third layer can play a role in controlling radio resources between the first device and the second device. For this purpose, for example, the RRC layer can exchange RRC messages between the first device and the second device.

[0058] FIG. 2 illustrates a radio protocol architecture according to an embodiment of the present disclosure. The embodiment of FIG. 2 can be combined with various embodiments of the present disclosure. For example, (a) of FIG. 2 may illustrate a radio protocol stack of a user plane for uplink communication or downlink communication, and (b) of FIG. 2 may illustrate a radio protocol stack of a control plane for uplink communication or downlink communication. For example, (c) of FIG. 2 may illustrate a radio protocol stack of a user plane for device-to-device communication, and (d) of FIG. 2 may illustrate a radio protocol stack of a control plane for device-to-device communication.

[0059] For example, the physical layer can provide information transmission services to upper layers using physical channels. For example, the physical layer can be connected to the upper layer, the medium access control (MAC) layer, through a transport channel. For example, data can be transmitted between the MAC layer and the physical layer through the transport channel. For example, transport channels can be classified according to how and with what characteristics data is transmitted over the wireless interface. For example, data can be transmitted between different physical layers, for example, between the physical layers of a first device and a second device, through a physical channel. For example, the physical channel can be modulated using an orthogonal frequency division multiplexing (OFDM) scheme, and time and frequency can be utilized as radio resources.

[0060] For example, the MAC layer can provide services to the upper layer, the radio link control (RLC) layer, through logical channels. For example, the MAC layer can provide a mapping function from multiple logical channels to multiple transport channels. For example, the MAC layer can provide a logical channel multiplexing function by mapping multiple logical channels to a single transport channel. For example, the MAC sublayer can provide data transmission services on logical channels.

[0061] For example, the RLC layer can perform concatenation, segmentation, and reassembly of RLC service data units (SDUs). For example, to guarantee the various quality of service (QoS) required by radio bearers (RBs), the RLC layer can provide three operating modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). For example, AM RLC can provide error correction through automatic repeat request (ARQ).

[0062] For example, the RRC (radio resource control) layer can be defined only in the control plane. For example, the RRC layer can be responsible for controlling logical channels, transport channels, and physical channels in relation to the configuration, re-configuration, and release of radio bearers. For example, an RB can mean a logical path provided by a first layer (e.g., a physical layer) and a second layer (e.g., a MAC layer, an RLC layer, a PDCP (packet data convergence protocol) layer, a SDAP (service data adaptation protocol) layer, etc.) for data transmission between a first device and a second device.

[0063] For example, the functions of the PDCP layer in the user plane may include the forwarding of user data, header compression, and ciphering. For example, the functions of the PDCP layer in the control plane may include the forwarding of control plane data and ciphering / integrity protection.

[0064] For example, establishing an RB can refer to the process of defining the characteristics of the radio protocol layer and channel to provide a specific service, and setting specific parameters and operating methods for each. For example, RBs can be divided into two types: signaling radio bearers (SRBs) and data radio bearers (DRBs). For example, SRBs can be used as a channel to transmit RRC messages in the control plane, while DRBs can be used as a channel to transmit user data in the user plane.

[0065] For example, if an RRC connection is established between the RRC layer of the terminal and the RRC layer of the base station, the terminal will be in the RRC_CONNECTED state, and if not, it may be in the RRC_IDLE state. For example, in the case of NR, the RRC_INACTIVE state is additionally defined, and a terminal in the RRC_INACTIVE state can release the connection with the base station while maintaining the connection with the core network.

[0066] For example, a downlink transmission channel may include at least one of a broadcast channel (BCH) for transmitting system information, and / or a downlink shared channel (SCH) for transmitting user traffic or control messages. For example, traffic or control messages of a downlink multicast or broadcast service may be transmitted through the downlink SCH, or may be transmitted through a separate downlink multicast channel (MCH). Meanwhile, an uplink transmission channel may include at least one of a random access channel (RACH) for transmitting initial control messages, and / or an uplink shared channel (SCH) for transmitting user traffic or control messages. For example, a logical channel located above a transmission channel and mapped to the transmission channel may include at least one of a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH), and / or a multicast traffic channel (MTCH).

[0067] FIG. 3 illustrates the structure of a wireless frame according to an embodiment of the present disclosure. The embodiment of FIG. 3 can be combined with various embodiments of the present disclosure.

[0068] Referring to FIG. 3, for example, a radio frame may be used in uplink transmission, downlink transmission, and / or device-to-device transmission. For example, a radio frame may have a length of 10 ms and may be defined as two 5 ms half-frames (HF). For example, a half-frame may include five 1 ms subframes (SF). For example, a subframe may be divided into one or more slots, and the number of slots within a subframe may be determined according to a subcarrier spacing (SCS). For example, each slot may include 12 or 14 OFDM (A) symbols, depending on a cyclic prefix (CP).

[0069] For example, when normal CP is used, each slot can contain 14 symbols. For example, when extended CP is used, each slot can contain 12 symbols. Here, for example, the symbols can contain OFDM symbols (or CP-OFDM symbols), SC-FDMA (single carrier-FDMA) symbols (or DFT-s-OFDM (Discrete Fourier Transform-spread-OFDM) symbols).

[0070] Table 2 below shows the number of symbols per slot (N) depending on the SCS setting (u) when normal CP or extended CP is used. slot symb ), number of slots per frame (N frame,u slot ) and the number of slots per subframe (N subframe,u slot ) is an example.

[0071] CP type SCS (15*2 u )N slot symb N frame,u slot N subframe,u slotNormal CP15kHz (u=0)1410130kHz (u=1)1420260kHz (u=2)14404120kHz (u=3)14808240kHz (u=4)1416016Extended CP60kHz (u=2)12404

[0072] For example, OFDM(A) numerology (e.g., SCS, CP length, etc.) may be set differently between multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of time resources (e.g., subframes, slots, or transmit time intervals (TTIs)) composed of the same number of symbols may be set differently between the merged cells. For example, in the present disclosure, time resources such as subframes, slots, TTIs, etc. may be referred to as time units.

[0073] For example, multiple numerologies, or SCSs, may be supported to support various services. For example, a 15 kHz SCS may support wide areas in traditional cellular bands, while a 30 kHz / 60 kHz SCS may support dense urban areas, lower latency, and wider carrier bandwidth. For example, a 60 kHz or higher SCS may support bandwidths greater than 24.25 GHz to overcome phase noise.

[0074] FIG. 4 illustrates a slot structure of a frame according to an embodiment of the present disclosure. The embodiment of FIG. 4 can be combined with various embodiments of the present disclosure.

[0075] Referring to FIG. 4, for example, a slot may include multiple symbols in the time domain. For example, a carrier may include multiple subcarriers in the frequency domain. For example, a resource block (RB) may be defined as multiple consecutive subcarriers in the frequency domain. For example, a bandwidth part (BWP) may be defined as multiple consecutive (P)RBs ((physical) resource blocks) in the frequency domain, and may correspond to one numerology (e.g., SCS, CP length, etc.). For example, a carrier may include at most N BWPs (where N is a positive integer). For example, data communication may be performed through an activated BWP. For example, each element may be referred to as a resource element (RE) in the resource grid, and one complex symbol may be mapped to it.

[0076] For example, a BWP may be a contiguous set of PRBs in a given numerology. For example, a PRB may be selected from a contiguous subset of common resource blocks (CRBs) for a given numerology on a given carrier.

[0077] For example, the BWP may be at least one of an active BWP, an initial BWP, and / or a default BWP. For example, the UE may not monitor the downlink radio link quality in a DL BWP other than the active DL BWP on the PCell (primary cell). For example, the UE may not receive a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), or a channel state information-reference signal (CSI-RS) (except for radio resource management (RRM)) outside of the active DL BWP. For example, the UE may not trigger channel state information (CSI) reporting for an inactive DL BWP. For example, the UE may not transmit a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) outside of the active UL BWP. For example, for downlink, the initial BWP can be given as a set of consecutive resource blocks (RBs) for the remaining minimum system information (RMSI) CORESET (control resource set) (set by the physical broadcast channel (PBCH)). For uplink, for example, the initial BWP can be given by the system information block (SIB) for the random access procedure. For example, the default BWP can be set by a higher layer. For example, the initial value of the default BWP can be the initial DL BWP.For energy saving, if a terminal does not detect DCI (downlink control information) for a certain period of time, the terminal may switch its active BWP to a default BWP.

[0078] FIG. 5 illustrates an example of a BWP according to an embodiment of the present disclosure. The embodiment of FIG. 5 can be combined with various embodiments of the present disclosure. In the embodiment of FIG. 5, it is assumed that there are three BWPs.

[0079] Referring to FIG. 5, for example, a common resource block (CRB) may be a carrier resource block numbered from one end of a carrier band to the other, and a PRB may be a numbered resource block within each BWP. For example, point A may indicate a common reference point for a resource block grid.

[0080] For example, BWP is point A, offset from point A (N start BWP ) and bandwidth (N size BWP ) can be set by. For example, point A can be an outer reference point of the PRB of a carrier where subcarrier 0 of all numerologies (e.g., all numerologies supported by the network on that carrier) aligns. For example, the offset can be the PRB spacing between the lowest subcarrier in a given numerology and point A. For example, the bandwidth can be the number of PRBs in a given numerology.

[0081] FIG. 6 illustrates a communication structure that can be provided in a 6G system according to an embodiment of the present disclosure. The embodiment of FIG. 6 can be combined with various embodiments of the present disclosure.

[0082] As core implementation technologies of the 6G system, technologies such as artificial intelligence (AI), THz (terahertz) communication, optical wireless technology, free-space optical transmission (FSO) backhaul networks, massive MIMO (multiple input multiple output) technology, blockchain, 3D networking, quantum communication, unmanned aerial vehicles, cell-free communication, wireless information and energy transfer (WIET), integration of sensing and communication, integration of access backhaul networks, holographic beamforming, big data analysis, and large intelligent surface (LIS) can be adopted.

[0083] - Artificial Intelligence: Incorporating AI into communications can streamline and improve real-time data transmission. AI can use numerous analytics to determine how complex target tasks should be performed. For example, AI can increase efficiency and reduce processing delays. Time-consuming tasks such as handovers, network selection, and resource scheduling can be performed instantly using AI. AI can also play a crucial role in machine-to-machine (M2M), machine-to-human, and human-to-machine communications. AI can also facilitate rapid communication in brain-computer interfaces (BCIs). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

[0084] - THz communication (terahertz communication): Data rates can be increased by increasing the bandwidth. This can be achieved by using sub-THz communication with wide bandwidths and applying advanced massive MIMO technology. THz waves, also known as sub-millimeter waves, typically refer to the frequency range between 0.1 THz and 10 THz, with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz to 300 GHz band (sub-THz band) is considered a key part of the THz spectrum for cellular communications. Adding the sub-THz band to the mmWave band will increase the capacity of 6G cellular communications. Among the defined THz bands, 300 GHz to 3 THz lies in the far infrared (IR) frequency band. While part of the optical band, the 300 GHz to 3 THz band lies at the boundary of the optical band, immediately following the RF band. Therefore, this 300 GHz to 3 THz band exhibits similarities to RF. Key characteristics of THz communications include (i) the widely available bandwidth to support very high data rates and (ii) the high path loss that occurs at high frequencies (requiring highly directional antennas). The narrow beamwidths generated by highly directional antennas reduce interference. The small wavelength of THz signals allows for a significantly larger number of antenna elements to be integrated into devices and base stations operating in this band. This enables the use of advanced adaptive array technologies to overcome range limitations.

[0085] - Large-scale MIMO technology

[0086] - Hologram beamforming (HBF)

[0087] - Optical wireless technology

[0088] - Free-space optical transmission backhaul network (FSO backhaul network)

[0089] - Quantum communication

[0090] - Cell-free communication

[0091] - Integration of wireless information and power transmission

[0092] - Integration of wireless communication and sensing

[0093] - Integrated access and backhaul network

[0094] - Big data analysis

[0095] - Reconfigurable intelligent surface

[0096] - metaverse

[0097] - Block chain

[0098] Advanced Air Mobility (AAM): AAM can be a broad concept encompassing urban air mobility (UAM), regional air mobility (RAM), and uncrewed aerial systems (UAS). For example, AAM can include UAM, RAM, UAS, and uncrewed aerial vehicles (UAVs).

[0099] - Autonomous driving (self-driving): V2X (vehicle to everything), a key element in building autonomous driving infrastructure, can be a technology that allows cars to communicate and share with various elements on the road for autonomous driving, such as vehicle to vehicle (V2V) wireless communication and vehicle to infrastructure (V2I) wireless communication.

[0100] Non-terrestrial network (NTN): NTN can refer to a network or network segment that utilizes radio frequency (RF) resources mounted on satellites (or UAS platforms). NTN services may be considered to secure wider coverage or provide wireless communication services in locations where the installation of wireless communication base stations is difficult.

[0101] - Integrated sensing and communication (ISAC): Wireless sensing is a technology that uses radio frequencies to determine the instantaneous linear velocity, angle, distance (range), etc. of an object, thereby obtaining information about the characteristics of the environment and / or objects within the environment.

[0102] - Reconfigurable intelligent surface (RIS): RIS can be used to manipulate and enhance signal propagation in wireless communication environments. For example, a RIS can be composed of many small antennas, or metasurfaces, arranged on a surface, each of which can actively control the phase, amplitude, polarization, etc. of the reflected signal. For example, a RIS can improve signal reception by controlling the path, phase, and / or intensity of the propagating signal. For example, in the case of a RIS, power consumption can be very low because power is consumed only for controlling the phase and amplitude of the small antennas. For example, because a RIS can be reconfigured to suit different environments, it can meet diverse communication requirements and operate effectively in dynamic network environments.

[0103] FIG. 7 illustrates an example of a communication scenario based on a 6G system, according to an embodiment of the present disclosure. The embodiment of FIG. 7 may be combined with various embodiments of the present disclosure.

[0104] Referring to FIG. 7, NTN communication can be performed based on satellite networks, high-altitude platform stations (HAPS) as international mobile telecommunications (IMT) base stations (BS), and terminals capable of aerial communication (e.g., AAMs). For example, to improve coverage, etc., devices such as satellite networks, HIBS, and terminals capable of aerial communication (e.g., AAMs) can act as relays. For example, an AAM can communicate with a base station, a satellite network, etc., and / or an AAM can communicate directly with a terminal, another AAM, etc.

[0105] FIG. 8 illustrates a procedure for downlink transmission and reception according to an embodiment of the present disclosure. The embodiment of FIG. 8 may be combined with various embodiments of the present disclosure.

[0106] Referring to FIG. 8, for example, in step S801, the base station can schedule downlink transmissions such as frequency / time resources, transmission layers, downlink precoder, MCS, etc. For example, the base station can determine a beam for PDSCH transmission of the terminal through the operations described above.

[0107] For example, in step S802, the terminal can receive downlink control information (DCI) for downlink scheduling (e.g., including scheduling information of PDSCH) from the base station on the PDCCH.

[0108] For example, DCI format 1_0 or 1_1 may be used for downlink scheduling, and in particular, DCI format 1_1 may include the following information: Identifier for DCI formats, Bandwidth part indicator, Frequency domain resource assignment, Time domain resource assignment, PRB bundling size indicator, Rate matching indicator, ZP CSI-RS trigger, Antenna port(s), Transmission configuration indication (TCI), SRS request, DMRS (Demodulation Reference Signal) sequence initialization.

[0109] For example, depending on each state indicated in the Antenna port(s) field, a number of DMRS ports can be scheduled, and also single-user (SU) / multi-user (MU) transmission scheduling can be possible.

[0110] For example, the TCI field consists of 3 bits, and QCL for DMRS can be dynamically indicated by indicating up to 8 TCI states depending on the TCI field value.

[0111] For example, in step S803, the terminal can receive downlink data from the base station on the PDSCH.

[0112] For example, if a terminal detects a PDCCH including DCI format 1_0 or 1_1, it can decode the PDSCH according to instructions by the corresponding DCI.

[0113] For example, when a terminal receives a PDSCH scheduled by DCI format 1, the terminal may set a DMRS configuration type by a higher layer parameter 'dmrs-Type', and the DMRS type may be used to receive the PDSCH. For example, the terminal may set a maximum number of DMRA symbols to be front-loaded for the PDSCH by a higher layer parameter 'maxLength'.

[0114] For example, for DMRS configuration type 1, if a terminal is scheduled with a single codeword and is assigned an antenna port mapped with an index of {2, 9, 10, 11, or 30}, or if a terminal is scheduled with two codewords, the terminal can assume that all remaining orthogonal antenna ports are not associated with a PDSCH transmission to another terminal.

[0115] For example, for DMRS configuration type 2, if a terminal is scheduled with a single codeword and is assigned an antenna port mapped with an index of {2, 10, or 23}, or if a terminal is scheduled with two codewords, the terminal can assume that all remaining orthogonal antenna ports are not associated with a PDSCH transmission to another terminal.

[0116] For example, when a terminal receives a PDSCH, a precoding granularity P' can be assumed to be a consecutive resource block in the frequency domain. For example, P' can correspond to one of the values ​​{2, 4, wideband}.

[0117] For example, if P' is determined to be wideband, the terminal does not expect to be scheduled with non-contiguous PRBs, and the terminal can assume that the same precoding is applied to the allocated resources.

[0118] For example, if P' is determined to be one of {2, 4}, a precoding resource block group (PRG) can be divided into P' consecutive PRBs. For example, the actual number of consecutive PRBs within each PRG can be one or more. For example, a UE can assume that the same precoding is applied to consecutive downlink PRBs within a PRG.

[0119] For example, in order for a terminal to determine the modulation order, target code rate, and transport block size within a PDSCH, the terminal may first read a 5-bit MCD field within the DCI to determine the modulation order and target code rate. Then, the terminal may read a redundancy version field within the DCI to determine the redundancy version. Then, the terminal may determine the transport block size using the number of layers and the total number of allocated PRBs before rate matching.

[0120] FIG. 9 illustrates a procedure for uplink transmission and reception according to an embodiment of the present disclosure. The embodiment of FIG. 9 may be combined with various embodiments of the present disclosure.

[0121] Referring to FIG. 9, for example, in step S901, the base station may schedule uplink transmissions such as frequency / time resources, transmission layers, uplink precoder, MCS, etc. For example, the base station may determine a beam for PUSCH transmission of the terminal through the operations described above.

[0122] For example, in step S902, the terminal may receive DCI for uplink scheduling (e.g., including scheduling information of PUSCH) from the base station on the PDCCH.

[0123] For example, DCI format 0_0 or 0_1 may be used for uplink scheduling, and in particular, DCI format 0_1 ​​may include the following information: DCI format identifier, UL / SUL (Supplementary uplink) indicator, UL / SUL indicator, bandwidth part indicator, frequency domain resource assignment, time domain resource assignment, frequency hopping flag, modulation and coding scheme (MCS), SRS resource indicator (SRI), precoding information and number of layers, antenna port(s), SRS request, DMRS sequence initialization, UL-SCH (Uplink Shared Channel) indicator.

[0124] For example, SRS resources configured within a set of SRS resources associated with the upper layer parameter 'usage' can be indicated by the SRS resource indicator field. For example, 'spatialRelationInfo' can be configured for each SRS resource, and its value can be one of {CRI, SSB, SRI}.

[0125] For example, in step S903, the terminal may transmit uplink data to the base station on PUSCH.

[0126] For example, if a terminal detects a PDCCH including DCI format 0_0 or 0_1, it can transmit the corresponding PUSCH according to the instructions of the corresponding DCI.

[0127] For example, two transmission schemes (e.g., codebook-based transmission for PUSCH transmission and non-codebook-based transmission for PUSCH transmission) may be supported:

[0128] i) For example, when the upper layer parameter 'txConfig' is set to 'codebook', the terminal may be configured for codebook-based transmission. For example, when the upper layer parameter 'txConfig' is set to 'nonCodebook', the terminal may be configured for non-codebook-based transmission. For example, if the upper layer parameter 'txConfig' is not set, the terminal may not expect to be scheduled by DCI format 0_1. For example, when PUSCH is scheduled by DCI format 0_0, PUSCH transmission may be based on a single antenna port.

[0129] For example, in case of codebook-based transmission, PUSCH can be scheduled in DCI format 0_0, DCI format 0_1, or semi-statically. For example, if this PUSCH is scheduled by DCI format 0_1, the UE can determine the PUSCH transmission precoder based on the SRI, the transmit precoding matrix indicator (TPMI), and the transmission rank from the DCI, as given by the SRS resource indicator field and the precoding information and number of layers field. For example, the TPMI is used to indicate the precoder to be applied across antenna ports, and may correspond to the SRS resource selected by the SRI when multiple SRS resources are configured. For example, if a single SRS resource is configured, the TPMI is used to indicate the precoder to be applied across antenna ports, and may correspond to the single SRS resource. For example, a transmit precoder may be selected from an uplink codebook having the same number of antenna ports as the upper layer parameter 'nrofSRS-Ports'. For example, when a terminal sets an upper layer with 'codebook' as the parameter 'txConfig', the terminal may be configured with at least one SRS resource. For example, an SRI indicated in slot n is associated with the most recent transmission of the SRS resource identified by the SRI, wherein the SRS resource may precede the PDCCH carrying the SRI (e.g., slot n).

[0130] ii) For example, in case of non-codebook based transmission, PUSCH can be scheduled in DCI format 0_0, DCI format 0_1, or semi-statically. For example, when multiple SRS resources are configured, the UE can determine the PUSCH precoder and transmission rank based on the wideband SRI, where the SRI can be given by the SRS resource indicator in the DCI or by the higher layer parameter 'srs-ResourceIndicator'. For example, the UE uses one or multiple SRS resources for SRS transmission, where the number of SRS resources can be configured for simultaneous transmission within the same RB based on the UE capability. For example, only one SRS port can be configured for each SRS resource. For example, only one SRS resource can be configured with the higher layer parameter 'usage' set to 'nonCodebook'. For example, the maximum number of SRS resources that can be configured for non-codebook based uplink transmission may be 4. For example, the SRI indicated in slot n is associated with the most recent transmission of the SRS resource identified by the SRI, where the SRS transmission may precede the PDCCH carrying the SRI (e.g., slot n).

[0131] FIG. 10 illustrates an example of an NTN according to one embodiment of the present disclosure. The embodiment of FIG. 10 may be combined with various embodiments of the present disclosure.

[0132] Referring to Fig. 10, examples according to NTN platform types can be shown. For example, examples according to NTN platform types can be HAPS (High-Altitude Platform Station), LEO (Low Earth orbit), MEO (Medium Earth orbit), or GEO (Geo-stationary Earth orbit).

[0133] For example, parameters related to a High-Altitude Platform Station (HAPS) may be as follows: For example, the altitude of the High-Altitude Platform Station (HAPS) may be 20 km. For example, the beam footprint size of the High-Altitude Platform Station (HAPS) may be 5-200 km.

[0134] For example, parameters related to LEO (Low Earth orbit) can be as follows. For example, the altitude of LEO (Low Earth orbit) can be 300-1500 km. For example, the beam footprint size of LEO (Low Earth orbit) can be 100-1000 km. For example, the satellite speed in LEO (Low Earth orbit) can be 7.56 km / sec (for LEO-600). For example, the maximum propagation delay in LEO (Low Earth orbit) can be 25.77 msec (for LEO-600).

[0135] For example, parameters related to MEO (Medium Earth orbit) can be as follows. For example, the altitude of MEO (Medium Earth orbit) can be 7000-25000 km. For example, the beam footprint size of MEO (Medium Earth orbit) can be 100-1500 km. For example, the maximum propagation delay of MEO (Medium Earth orbit) can be 95.19 msec (for MEO-10000).

[0136] For example, the parameters related to Geo-stationary Earth orbit (GEO) can be as follows. For example, the altitude of Geo-stationary Earth orbit (GEO) can be 35786 km. For example, the beam footprint size of Geo-stationary Earth orbit (GEO) can be 200-3500 km. For example, the satellite speed of Geo-stationary Earth orbit (GEO) can be 3.1 km / sec (negligible). For example, the maximum propagation delay of Geo-stationary Earth orbit (GEO) can be 541.46 msec.

[0137] For example, to effectively operate NTN with very long RTT, scheduling offsets K_offset and K_mac can be introduced.

[0138] FIG. 11 illustrates examples of K_offset and K_mac according to one embodiment of the present disclosure. The embodiment of FIG. 11 can be combined with various embodiments of the present disclosure.

[0139] Referring to FIG. 11, examples of K_offset and K_mac can be shown. For example, a service link RTT can be an RTT between a terminal and a satellite. For example, a feeder link RTT can be an RTT between a satellite and a base station. For example, a common TA can be a TA between a satellite and a RP. For example, K_offset can be an offset value indicating an RTT of an uplink time synchronization reference point (RP). For example, K_offset can mean the sum of the service link RTT and the common TA (if indicated). For example, K_mac can be an offset value indicating an RTT between an RP and a gNB. For example, the feeder link RTT could mean the sum of the common TA (if indicated) and K_mac.

[0140] FIG. 12 illustrates examples of UE-specific TAs and common TAs according to one embodiment of the present disclosure. The embodiment of FIG. 12 can be combined with various embodiments of the present disclosure.

[0141] Referring to FIG. 12, for example, in Rel-17 NTN, a UE can calculate a TA on its own based on its GNSS capability and base station indication information (e.g., ephemeris information), which can be referred to as a UE-specific TA. For example, a TA calculated based on common TA parameters indicated by a base station can be referred to as a common TA, and the final TA based on this can be based on FIG. 13 and the description related to FIG. 13.

[0142] FIG. 13 illustrates an example of an uplink-downlink timing relationship according to an embodiment of the present disclosure. The embodiment of FIG. 13 may be combined with various embodiments of the present disclosure.

[0143] Referring to Figure 13, the uplink frame number i for transmission from the UE is the number of frames before the start of the corresponding downlink frame at the UE. You can start here

[0144] - and can be given in clause 4.2 of TS 38.213, This may be excluded for msgA transmission on PUSCH that should be used;

[0145] - If indicated, it can be derived from the upper-layer parameters TACommon, TACommonDrift, and TACommonDriftVariation, otherwise It could be;

[0146] - If indicated, the UE position and serving-satellite-orbit-related upper-layer parameters can be computed by the UE, otherwise It could be.

[0147] For example, there may be a TA misalignment.

[0148] For example, in NR NTN, TA mismatch may occur if the gNB does not receive TA reports, if the existing TA reports are outdated, or if the TA reporting granularity is not sufficiently granular. For example, if the UE does not perform TA reporting at all, the above scenario (e.g., no TA reporting) may not be considered a feasible scenario, since the gNB cannot set some key scheduling variables (e.g., K_(cell,offset), K_(UE,offset)). Therefore, assuming that the UE performs TA reporting, the magnitude of the TA mismatch due to TA report aging and / or TA report granularity may need to be addressed. For example, if the UE performs TA reporting in NR NTN, TA mismatch may occur primarily due to outdated TA reports and / or coarse TA report granularity. For example, for HD-FDD (e)RedCap UE support, the issue of quantitative level TA misalignment between gNB and UE may need to be addressed.

[0149] Meanwhile, differences due to old TA reports may occur when the UE location changes, and may occur proportionally to RTT differences that depend on the UE location within the cell (e.g., difference between minimum TA and maximum TA).

[0150] FIG. 14 illustrates an example of TA mismatch within a beam / cell according to an embodiment of the present disclosure. The embodiment of FIG. 14 can be combined with various embodiments of the present disclosure.

[0151] Referring to FIG. 14, for example, assuming LEO 600 km, beam size 50 km, and target elevation angle 30 degrees, the difference between the shortest RTT (minimum TA) and the longest RTT (maximum TA) can be within about 300 us, which can correspond to about 4 to 5 OFDM symbols using 15 kHz SCS.

[0152] For example, assuming LEO 600 km, beam size 50 km, and target elevation angle 30 degrees, the difference between the shortest RTT (min TA) and the longest RTT (max TA) is within about 300 μs, which can correspond to about 4 to 5 OFDM symbols with 15 kHz SCS. For example, considering that the TA reporting granularity of NTN is 1 ms (e.g., 14 OFDM symbols using 15 kHz SCS), in the LEO example, the main cause of TA mismatch may be the TA reporting granularity, not the stale TA reports. For example, for LEO 600 km, beam size 50 km, and target elevation angle 30 degrees, the difference between the min TA and the max TA may be less than the TA reporting granularity (e.g., 1 ms). For example, for HD-FDD (e)RedCap UE support, improved TA reporting mechanisms, especially TA reporting granularity issues, may need to be addressed.

[0153] For example, there may be a DL / UL conflict under TA misalignment.

[0154] When comparing the timing advance of NTN and TN due to satellite movement, the timing advance of the service link between the satellite and the UE can be estimated by the UE itself. For example, the gNB can obtain the TA value through TA reporting. However, due to the current 1 ms granularity of TA reporting, the gNB cannot obtain the exact TA used by the UE, and it cannot determine when and which transmissions on the UE side will collide. For example, since the rule for when DL reception collides with UL transmission is to avoid collisions through gNB scheduling, the gNB in ​​the NTN may have difficulty determining whether the UE is in an uplink or downlink slot.

[0155] FIG. 15 illustrates an HD collision in an NTN according to an embodiment of the present disclosure. The embodiment of FIG. 15 may be combined with various embodiments of the present disclosure.

[0156] Referring to Figure 15, the TA value reported by the UE may be 4 ms. For example, the actual TA value may be 4 ms. For example, the actual TA value may be 3 ms. For example, the actual TA value may be 5 ms.

[0157] For example, if the TA value reported by the UE is 4 ms and the gNB schedules based on the reported value with the UE-specific k_offset set to 4 slots assuming an SCS of 15 kHz, the UE may function properly. For example, the actual TA value may be 4 ms. However, as the satellite moves, the distance between the satellite and the UE constantly changes, which may cause the TA value actually used by the UE to increase or decrease. For example, the actual TA value may be 3 ms. For example, the actual TA value may be 5 ms. For example, if the gNB still schedules based on the old reported value, a collision may occur on the UE side, as shown in the black filled in Figure 15, where the blank space may indicate that scheduling is not being performed.

[0158] In Fig. 15, the actual TA is shown as 3 ms, 4 ms, and 5 ms, but is not limited thereto. In Fig. 15, the reported TA is shown as 4 ms, but is not limited thereto.

[0159] For example, according to embodiments of the present disclosure, half-duplex operation may include:

[0160] For example, an HD-UE may not expect to detect a DCI format that schedules reception for a set of symbols and a DCI format that schedules transmission on any symbol in the set of symbols.

[0161] For example, if PDCCH reception by a terminal includes two PDCCH candidates, the end of the PDCCH candidate that is later among the two may be the end of PDCCH reception.

[0162] For example, an HD-UE may not expect dedicated higher layer parameters that configure reception for a set of symbols and DCI format detection that schedules transmission on any symbol in the set of symbols.

[0163] For example, reception of a DL PRS in a set of symbols (PDCCH, PDSCH, CSI-RS) configured by a higher layer may be performed when a DCI format indicating PUSCH, PUCCH, PRACH, or SRS transmission is not detected for at least one symbol in the set of symbols.

[0164] For example, in the case of PUCCH, PUSCH (Higher layer configured PUCCH, PUSCH) set by the upper layer vs. CSI-RS, PDSCH (DCI format indicated CSI-RS), PDSCH indicated by the DCI format,

[0165] - For example, from the last symbol of PDCCH reception for DCI format If there are first symbols of UL transmission within, the terminal may not cancel the UL transmission. For example, it may cancel otherwise.

[0166] For example, SRS configured by a higher layer (Higher layer configured SRS) vs. CSI-RS, PDSCH indicated by DCI format (DCI format indicated CSI-RS, PDSCH)

[0167] For example, from the last symbol of PDCCH reception for DCI format The SRS transmission of the remaining remaining symbols can be canceled without canceling the SRS transmission within the symbol.

[0168] for example, silver may be the PUSCH preparation time for UE processing capability 1 [see TS 38.214] assuming and It can be the smallest SCS setting between the SCS setting of the PDCCH carrying the DCI format and the SCS setting of the SRS, PUCCH, and PUSCH ( may be the PUSCH preparation time for UE processing capability 1 [Refer to TS 38.214] assuming and corresponds to the smallest SCS configuration between the SCS configuration of the PDCCH carrying the DCI format and the SCS configuration of the SRS, PUCCH, PUSCH).

[0169] For example, one may not expect simultaneous reception of a Type-0 / 0A / 1 / 2-PDCCH CSS set configuration in a set of symbols and a dedicated higher later parameter configuring transmission in the set of symbols.

[0170] For example, in a PUSCH, PUCCH (Higher layer configured PUSCH, PUCCH) vs. SIB1 or ServingCellConfigCommon or in a DL BWP indicated by ssb-PositionInBurst or by NonCellDefiningSSB,

[0171] - For example, if the TX-RX switching time period is not guaranteed before the next earliest SSB, PUSCH and PUCCH may not be transmitted.

[0172] - For example, if the RX-TX switching time period is not guaranteed after the previous latest SSB, PUSCH and PUCCH may not be transmitted.

[0173] For example, in a Higher layer configured SRS vs. SIB1 or in ServingCellConfigCommon or by NonCellDefiningSSB, the presence of SSB within the DL BWP is indicated by ssb-PositionInBurst in SIB1 or in ServingCellConfigCommon or by NonCellDefiningSSB,

[0174] - For example, the SRS of a symbol that is not before the TX-RX switching time period from the next earliest SSB may not be transmitted.

[0175] - For example, the SRS of a symbol that is not after the RX-TX switching time period from the previous latest SSB may not be transmitted.

[0176] For example, in PDCCH order based PRACH, PUSCH, PUCCH vs. SIB1 or ServingCellConfigCommon where the presence of SSB within the DL BWP is indicated by ssb-PositionInBurst or by NonCellDefiningSSB,

[0177] - For example, if any symbol of the symbol duration of SSB overlaps with UL transmission, UL may not be transmitted.

[0178] For example, in the indicated presence of SSB within the DL BWP by ssb-PositionInBurst in SIB1 or in ServingCellConfigCommon or by NonCellDefiningSSB,

[0179] - For example, SRS may not be transmitted during the symbol duration of SSB.

[0180] For example, in a Higher layer triggered PRACH or MsgA PUSCH vs. indicated presence of SSB within the DL BWP by ssb-PositionInBurst in SIB1 or in ServingCellConfigCommon or by NonCellDefiningSSB, in a Reception of PDCCH, PDSCH, CSI-RS, DL PRS, indicated presence of SSB within the DL BWP by ssb-PositionInBurst in SIB1 or in ServingCellConfigCommon or by NonCellDefiningSSB,

[0181] - For example, if symbol durations overlap, it can be left to the UE implementation (Up to UE implementation).

[0182] - For example, if the TX-RX or RX-TX switching period is not guaranteed, it can be left to the UE implementation (Up to UE implementation).

[0183] For example, in the field of communications, the introduction of a non-terrestrial network (NTN) that utilizes satellites as network nodes is being actively discussed. For example, satellites supporting the NTN can be classified according to their flight orbits and characteristics, such as GEO, MEO, and LEO, and generally have very high satellite altitudes. For example, the NTN can serve Reduced Capability (RedCap) terminals and / or Enhanced Reduced Capability (eRedCap) terminals that support half duplex frequency division duplexing (HD-FDD) transmission. For example, terminals supporting the half-duplex transmission method cannot perform DL reception and UL transmission simultaneously, and therefore, rules for base station (or network) and / or terminal operations when the DL reception time and the UL transmission time overlap and / or collide on the time axis (hereinafter, DL / UL collision handling rules) may need to be defined. For example, a DL / UL collision handling rule for a terminal operating in a half-duplex transmission mode in the NTN may need to be defined in consideration of issues such as information that should be prioritized in the NTN and / or TA mismatch between the base station and the terminal due to UE autonomous TA (Timing Advance) application in the NTN. In the present disclosure, a transmission method and device for a terminal operating in a half-duplex transmission mode in an NTN may be proposed from the perspective of the DL / UL collision handling rule.

[0184] For example, proposal #01 can be proposed.

[0185] For example, according to Proposal #01, when a base station (or network) provides vehicle / satellite related information including vehicle and / or satellite movement path / orbit information (e.g., Ephemeris) to terminal(s) as system information, a method may be proposed in which a half-duplex terminal applies DL / UL collision handling rules differently when receiving the system information according to a specific timer value and / or a specific time interval.

[0186] For example, a half-duplex terminal may apply different DL / UL collision handling rules upon receiving the above system information depending on a specific timer value and / or a specific time interval as follows.

[0187] (1) For example, if the remaining time of the specific timer exceeds / is greater than a specific reference value (or is within the specific time interval)

[0188] A. For example, the reception of the above system information may be regarded as a typical downlink reception that is dynamically and / or semi-statically directed and / or set, and the DL / UL collision handling rules for that case (hereinafter, the first DL / UL collision handling rules) may be applied.

[0189] (2) For example, if the remaining time of the specific timer is less than / below a specific reference value (or outside the specific time interval),

[0190] (2) A. For example, the reception of the above system information may be regarded as a special downlink reception, and a second DL / UL collision handling rule different from the first DL / UL collision handling rule may be applied.

[0191] (2) B. For example, the terminal may prioritize the reception of the system information over (all and / or part of) dynamically and / or semi-statically directed and / or configured uplink transmissions. For example, when following the first DL / UL collision handling rule, uplink transmission(s) that had a higher priority than the system information may be changed to have a lower priority than the system information when applying the second DL / UL collision handling rule. For example, in Proposal #01 or the present disclosure, the terminal may cancel and / or omit DL reception and / or UL transmissions that have lower priorities.

[0192] For example, in Proposal #01 or the present disclosure, the system information may include SIB19 (System Block 19) and / or SIB22 (System Block 22).

[0193] For example, in Proposal #01 or the present disclosure, the system information may include satellite and / or AAM and / or drone and / or HAPS (High Altitude Platform Station) related information (or SIB including the same).

[0194] For example, in Proposal #01 or the present disclosure, the specific timer may mean an uplink synchronization validity related timer and / or a timer separate from T430 and / or T430.

[0195] For example, in Proposal #01 or the present disclosure, the specific time interval may be a time interval starting from Epoch Time during which the specific timer (e.g., T430) is greater than a specific reference value.

[0196] For example, in Proposal #01 or the present disclosure, the half-duplex terminal may have DL / UL collision handling rules for DL / UL collisions.

[0197] For example, in Proposal #01 or the present disclosure, the general uplink and / or downlink may mean that it does not have a different priority than other uplinks and / or downlinks.

[0198] For example, in Proposal #01 or the present disclosure, the specific reference value may be a value set / instructed by the base station (or network) to the terminal. For example, in Proposal #01 or the present disclosure, if the terminal does not receive a setting / instruction for the specific reference value, the terminal may apply the second DL / UL collision handling rule.

[0199] For example, in Proposal #01 or the present disclosure, the base station (or network) can directly configure / instruct the terminal to apply either the first DL / UL collision handling rule or the second DL / UL collision handling rule to the system information. For example, if the base station (or network) configures / instructs the application of the second DL / UL collision handling rule to the system information, the second DL / UL collision handling rule can always be applied, regardless of a specific timer value and / or a specific time interval.

[0200] For example, in Proposal #01 or the present disclosure, DL / UL collision handling rules may be applied based on a potential time interval (e.g., SI window) during which the system information may be transmitted. For example, the fact that the base station and / or terminal prioritize receiving the system information may be synonymous with prioritizing the SI window interval for the system information.

[0201] For example, in a non-terrestrial network according to an embodiment of the present disclosure, it may be assumed that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. For example, in Proposal #01 or the present disclosure, if the terminal operates in a half-duplex transmission mode, DL reception and UL transmission cannot be performed simultaneously, and if the DL reception time and the UL transmission time collide, the terminal may perform DL reception and / or UL transmission with priority according to a DL / UL collision handling rule agreed upon / set in advance with the base station, or may determine it as an error case depending on the terminal implementation.

[0202] For example, in Proposal #01 or the present disclosure, the base station (or network) may provide orbit information of an aircraft and / or satellite included in a non-terrestrial network to the terminal as system information. For example, the system information may be transmitted through SIB19 and / or SIB22. For example, in Proposal #01 or the present disclosure, the terminal may perform time axis and / or frequency axis pre-compensation by utilizing path and / or orbit information (e.g., Ephemeris) of the aircraft and / or satellite during uplink transmission. For example, therefore, the process by which the terminal acquires the system information related to the aircraft and / or satellite may be an important process that must precede in order to support non-terrestrial network-based uplink communication. For example, therefore, the system information related to the aircraft and / or satellite may need to be received with a higher priority compared to other general downlink transmissions. For example, if the terminal is a half-duplex terminal, the base station and / or the half-duplex terminal may pre-agree / define / set DL / UL collision handling rules to give priority to receiving the aircraft and / or satellite related system information.

[0203] For example, in Proposal #01 or the present disclosure, the DL / UL collision handling rule for the system information may be applied differently depending on the validity period of the system information. For example, a timer indicating the validity of the vehicle and / or satellite-related system information may exist, and the timer may be started each time the system information is received. For example, in Proposal #01 or the present disclosure, immediately after the half-duplex terminal receives the vehicle and / or satellite-related system information, since valid system information has already been secured, the system information may be regarded as a general downlink reception, and the DL / UL collision handling rule for that case (hereinafter, the first DL / UL collision handling rule) may be applied. For example, on the other hand, if the timer value is low, the validity of the vehicle and / or satellite-related system information may expire quickly, and therefore, unlike the first DL / UL collision handling rule, it may be desirable to give priority to the reception of the system information over other (all and / or part) uplink transmissions.

[0204] For example, therefore, the present disclosure may propose a method for allowing a half-duplex terminal to apply different DL / UL collision handling rules upon receiving the system information, when a base station (or network) provides aircraft / satellite-related information including flight path / orbit information (e.g., Ephemeris) of the aircraft and / or satellite to the terminal(s) as system information, depending on a specific timer value and / or a specific time interval. For example, the half-duplex terminal may apply different DL / UL collision handling rules upon receiving the system information, depending on a specific timer value and / or a specific time interval, as follows.

[0205] (1) For example, if the remaining time of the specific timer exceeds / is greater than a specific reference value (or is within the specific time interval),

[0206] (1) A. For example, the reception of the above system information may be regarded as a typical downlink reception that is dynamically and / or semi-statically directed and / or set, and the DL / UL collision handling rule for that case (hereinafter, the first DL / UL collision handling rule) may be applied.

[0207] (2) For example, if the remaining time of the specific timer is less than / below a specific reference value (or outside the specific time interval),

[0208] (2) A. For example, the reception of the above system information may be regarded as a special downlink reception, and a second DL / UL collision handling rule different from the first DL / UL collision handling rule may be applied.

[0209] (2) B. For example, the terminal may prioritize the reception of the system information over (all and / or part of) dynamically and / or semi-statically directed and / or configured uplink transmissions. For example, when following the first DL / UL collision handling rule, uplink transmission(s) that had a higher priority than the system information may be changed to have a lower priority than the system information when applying the second DL / UL collision handling rule. For example, in Proposal #01 or the present disclosure, the terminal may cancel and / or omit DL reception and / or UL transmissions that have lower priorities.

[0210] For example, according to the present disclosure (e.g., Proposal #01), the base station (or network) has the advantage of being able to control the priority according to the remaining validity time of the vehicle and / or satellite related system information, thereby enabling more efficient operation of the resources of the half-duplex terminal.

[0211] For example, the above proposed method #01 can be applied in combination with other proposed method(s) to the extent that the operations of the present disclosure do not conflict.

[0212] For example, proposal #02 can be proposed.

[0213] For example, according to Proposal #02, when a base station (or network) provides vehicle / satellite-related information including vehicle and / or satellite movement path / orbit information (e.g., Ephemeris) as system information to terminal(s), a method may be proposed in which a half-duplex terminal applies different DL / UL collision handling rules upon receiving the system information depending on the scheduling type (for the system information).

[0214] For example, a half-duplex terminal may apply different DL / UL collision handling rules upon receiving the system information, depending on the scheduling type (for the system information).

[0215] (1) In case of unicast method (or non-periodic transmission),

[0216] (1) A. The above system information reception is regarded as a general downlink reception that is dynamically and / or semi-statically directed and / or set, and the DL / UL collision handling rule (hereinafter referred to as the first DL / UL collision handling rule) in that case may be applied.

[0217] (2) In case of broadcast method (or periodic transmission),

[0218] (2) A. The reception of the above system information is regarded as a special downlink reception, and a second DL / UL collision handling rule different from the first DL / UL collision handling rule may be applied.

[0219] (2) B. For example, the terminal may prioritize the reception of the system information over (all and / or part of) dynamically and / or semi-statically directed and / or configured uplink transmissions. For example, when following the first DL / UL collision handling rule, uplink transmission(s) that had a higher priority than the system information may be changed to have a lower priority than the system information when applying the second DL / UL collision handling rule. For example, in Proposal #02 or the present disclosure, the terminal may cancel and / or omit DL reception and / or UL transmissions that have lower priorities.

[0220] For example, in Proposal #02 or the present disclosure, the system information may include SIB19 (System Block 19) and / or SIB22 (System Block 22).

[0221] For example, in Proposal #02 or the present disclosure, the system information may include satellite and / or AAM and / or drone and / or HAPS (High Altitude Platform Station) related information (or SIB including the same).

[0222] For example, in Proposal #02 or the present disclosure, the scheduling type may include unicast and / or broadcast and / or periodic transmission and / or non-periodic transmission. For example, a broadcast method may mean a method in which transmission is periodically performed through set / instructed resources.

[0223] For example, in Proposal #02 or the present disclosure, the scheduling type may include (scheduling) DCI type (e.g., whether Fallback DCI and / or Non-fallback DCI) and / or (scheduling) Search Space / CORESET type and / or whether DG PUSCH SKIPPING is enabled and / or whether CG PUSCH SKIPPING is enabled and / or whether actual PUSCH transmission is performed.

[0224] For example, in Proposal #02 or the present disclosure, the half-duplex terminal may have DL / UL collision handling rules for DL / UL collisions.

[0225] For example, in Proposal #02 or the present disclosure, the general uplink and / or downlink may mean that it does not have a different priority than other uplinks and / or downlinks.

[0226] For example, in Proposal #02 or the present disclosure, the base station (or network) can directly set / instruct the terminal to apply either the first DL / UL collision handling rule or the second DL / UL collision handling rule to the system information. For example, if the base station (or network) sets / instructs the application of the second DL / UL collision handling rule to the system information, the second DL / UL collision handling rule can always be applied, regardless of a specific timer value and / or a specific time interval.

[0227] For example, in Proposal #02 or the present disclosure, DL / UL collision handling rules may be applied based on a potential time interval (e.g., SI window) in which the system information may be transmitted. For example, the fact that the base station and / or the terminal prioritize receiving the system information may be synonymous with prioritizing the SI window interval for the system information. For example, in Proposal #02 or the present disclosure, the SI window interval may be a resource interval linked to a Synchronization Signal Block (SSB) observed when the terminal acquires MIB (Master Block Information).

[0228] For example, in a non-terrestrial network according to an embodiment of the present disclosure, it may be assumed that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. For example, in Proposal #02 or the present disclosure, if the terminal operates in a half-duplex transmission mode, DL reception and UL transmission cannot be performed simultaneously, and if the DL reception time and the UL transmission time collide, the terminal may perform DL reception and / or UL transmission with priority according to a DL / UL collision handling rule agreed upon / set in advance with the base station, or may determine it as an error case depending on the terminal implementation.

[0229] For example, in Proposal #02 or the present disclosure, the base station (or network) may provide orbit information of an aircraft and / or satellite included in a non-terrestrial network to the terminal as system information. For example, the system information may be transmitted through SIB19 and / or SIB22. For example, in Proposal #02 or the present disclosure, the terminal may perform time axis and / or frequency axis pre-compensation by utilizing path and / or orbit information (e.g., Ephemeris) of the aircraft and / or satellite during uplink transmission. For example, therefore, the process by which the terminal acquires the system information related to the aircraft and / or satellite may be an important process that must precede in order to support non-terrestrial network-based uplink communication. For example, therefore, the system information related to the aircraft and / or satellite may need to be received with a higher priority compared to other general downlink transmissions. For example, if the terminal is a half-duplex terminal, the base station and / or the half-duplex terminal may pre-agree / define / set DL / UL collision handling rules to give priority to receiving the aircraft and / or satellite related system information.

[0230] For example, in Proposal #02 or the present disclosure, the DL / UL collision handling rule for the system information may be applied differently depending on the scheduling type of the system information. For example, if the system information is transmitted terminal-specifically in a unicast manner, it is regarded as a general downlink reception and the DL / UL collision handling rule for that case (hereinafter, the first DL / UL collision handling rule) is applied, and if it is transmitted in a broadcast manner within a periodically given SI window, a DL / UL collision handling rule (hereinafter, the second DL / UL collision handling rule) that gives priority to reception compared to other (all and / or part) uplink transmissions, unlike the first DL / UL collision handling rule, may be applied. For example, therefore, in the present disclosure, when a base station (or network) provides vehicle / satellite-related information including movement path / orbit information (e.g., Ephemeris) of a vehicle and / or satellite to terminal(s) as system information, a method may be proposed in which a half-duplex terminal applies different DL / UL collision handling rules upon receiving the system information depending on a scheduling type (for the system information). For example, a half-duplex terminal may apply different DL / UL collision handling rules upon receiving the system information depending on a scheduling type (for the system information) as follows.

[0231] (1) For example, in case of unicast mode (or non-periodic transmission),

[0232] (1) A. For example, the reception of the above system information may be regarded as a typical downlink reception that is dynamically and / or semi-statically directed and / or set, and the DL / UL collision handling rule for that case (hereinafter, the first DL / UL collision handling rule) may be applied.

[0233] (2) For example, in the case of broadcast mode (or periodic transmission),

[0234] (2) A. For example, the reception of the above system information may be regarded as a special downlink reception, and a second DL / UL collision handling rule different from the first DL / UL collision handling rule may be applied.

[0235] (2) B. For example, the terminal may prioritize the reception of the system information over (all and / or part of) dynamically and / or semi-statically directed and / or configured uplink transmissions. For example, when following the first DL / UL collision handling rule, uplink transmission(s) that had a higher priority than the system information may be changed to have a lower priority than the system information when applying the second DL / UL collision handling rule. For example, in Proposal #02 or the present disclosure, the terminal may cancel and / or omit DL reception and / or UL transmissions that have lower priorities.

[0236] For example, according to the present disclosure (e.g., Proposal #02), the base station (or network) has the advantage of being able to control the priority according to the scheduling type of the aircraft and / or satellite related system information, thereby enabling more efficient operation of the resources of the half-duplex terminal.

[0237] For example, the above proposed method #02 can be applied in combination with other proposed method(s) to the extent that the operations of the present disclosure do not conflict.

[0238] For example, proposal #03 can be proposed.

[0239] For example, according to Proposal #03, when a base station (or network) in a non-terrestrial network can instruct / configure whether to support SR (Scheduling Request) trigger by TA report (e.g., SR triggered by a TA report) to a terminal, a method can be proposed to apply different DL / UL collision handling rules during SR transmission channel and / or SR transmission depending on whether the SR trigger by TA report is instructed / configured.

[0240] For example, a half-duplex terminal may apply different DL / UL collision handling rules for the SR transmission channel and / or SR transmission depending on whether the SR trigger is indicated / set by the above TA report.

[0241] (1) For example, if the SR trigger by TA report is not indicated / set,

[0242] (1) A. For example, the above SR transmission channel and / or SR transmission may be regarded as a general uplink transmission that is dynamically and / or semi-statically directed and / or set, and the DL / UL collision handling rule (hereinafter referred to as the first DL / UL collision handling rule) in that case may be applied.

[0243] (2) For example, if an SR trigger is indicated / set by a TA report.

[0244] (2) A. For example, the SR transmission channel and / or SR transmission may be regarded as a special uplink reception, and a second DL / UL collision handling rule different from the first DL / UL collision handling rule may be applied.

[0245] (2) B. For example, the terminal may prioritize the SR transport channel and / or SR transmission over (all and / or part of) downlink receptions that are dynamically and / or semi-statically directed and / or configured. For example, when following the first DL / UL collision handling rule, downlink reception(s) that had a higher priority than the SR transport channel and / or SR transmission may be changed to have a lower priority than the SR transport channel and / or SR transmission when applying the second DL / UL collision handling rule. For example, in Proposal #03 or the present disclosure, the terminal may cancel and / or omit DL receptions and / or UL transmissions that have lower priorities.

[0246] For example, in Proposal #03 or the present disclosure, the system information may mean SIB19 (System Block 19).

[0247] For example, in Proposal #03 or the present disclosure, the scheduling type may include Unicast and / or Broadcast.

[0248] For example, in Proposal #03 or the present disclosure, the half-duplex terminal may have DL / UL collision handling rules for DL / UL collisions.

[0249] For example, in Proposal #03 or the present disclosure, the general uplink and / or downlink may mean that the priority is not different from that of other uplinks and / or downlinks.

[0250] For example, in Proposal #03 or the present disclosure, the base station (or network) can directly configure / instruct the terminal to apply either the first DL / UL collision handling rule or the second DL / UL collision handling rule for the SR transport channel and / or SR transmission. For example, if the base station (or network) configures / instructs the application of the second DL / UL collision handling rule for the SR transport channel and / or SR transmission, the second DL / UL collision handling rule can always be applied, regardless of whether an SR trigger is instructed / configured by a TA report.

[0251] For example, in a non-terrestrial network according to an embodiment of the present disclosure, it may be assumed that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. For example, in Proposal #03 or the present disclosure, if the terminal operates in a half-duplex transmission mode, DL reception and UL transmission cannot be performed simultaneously, and if the DL reception time and the UL transmission time collide, the terminal may perform DL reception and / or UL transmission with priority according to a DL / UL collision handling rule agreed upon / set in advance with the base station, or may determine it as an error case depending on the terminal implementation.

[0252] For example, in Proposal #03 or the present disclosure, in the NTN system, a terminal can report a TA to a base station (or a network), and the base station (or the network) can allow the terminal to trigger an SR (Scheduling Request) for the TA report. For example, if the terminal requires a TA report and there is no given UL grant, the terminal can trigger an SR to request uplink resource allocation. For example, in Proposal #03 or the present disclosure, the SR transmission by the TA report is important information for uplink synchronization of satellite communication, and thus may need to be given priority over other transmissions. For example, if the terminal is a half-duplex terminal, the base station and / or the half-duplex terminal can pre-agree / define / set a DL / UL collision handling rule to give priority to the SR transmission by the TA report and / or the SR transmission channel.

[0253] For example, in Proposal #03 or the present disclosure, the DL / UL collision handling rule for the SR transmission and / or SR transport channel may be applied differently depending on whether the SR trigger by the TA report is indicated / set. For example, if the SR trigger by the TA report is not indicated / set, the SR transmission and / or SR transport channel may be regarded as a general uplink transmission, and the DL / UL collision handling rule for that case (hereinafter, the first DL / UL collision handling rule) may be applied. For example, on the other hand, if the SR trigger by the TA report is indicated / set, a different DL / UL collision handling rule (hereinafter, the second DL / UL collision handling rule) that gives priority to the SR transmission and / or SR transport channel over other (all and / or part) downlink receptions, unlike the first DL / UL collision handling rule, may be applied. For example, therefore, in the present disclosure, when a base station (or network) in a non-terrestrial network can instruct / configure whether to support SR (Scheduling Request) trigger by TA report (e.g., SR triggered by a TA report) to a terminal, a method may be proposed to apply different DL / UL collision handling rules to an SR transmission channel and / or at the time of SR transmission depending on whether the SR trigger by the TA report is instructed / configured. For example, a half-duplex terminal can apply different DL / UL collision handling rules to an SR transmission channel and / or at the time of SR transmission depending on whether the SR trigger by the TA report is instructed / configured as follows.

[0254] (1) For example, if the SR trigger by TA report is not indicated / set,

[0255] (1) A. For example, the above SR transmission channel and / or SR transmission may be regarded as a general uplink transmission that is dynamically and / or semi-statically directed and / or set, and the DL / UL collision handling rule (hereinafter referred to as the first DL / UL collision handling rule) in that case may be applied.

[0256] (2) For example, if an SR trigger is indicated / set by a TA report,

[0257] (2) A. For example, the SR transmission channel and / or SR transmission may be regarded as a special uplink reception, and a second DL / UL collision handling rule different from the first DL / UL collision handling rule may be applied.

[0258] (2) B. For example, the terminal may prioritize the SR transport channel and / or SR transmission over (all and / or part of) downlink receptions that are dynamically and / or semi-statically directed and / or configured. For example, when following the first DL / UL collision handling rule, downlink reception(s) that had a higher priority than the SR transport channel and / or SR transmission may be changed to have a lower priority than the SR transport channel and / or SR transmission when applying the second DL / UL collision handling rule. For example, in Proposal #03 or the present disclosure, the terminal may cancel and / or omit DL receptions and / or UL transmissions that have lower priorities.

[0259] For example, according to the present disclosure (e.g., Proposal #03), the base station (or network) can control the half-duplex terminal to give priority to SR transmission and / or SR transmission channel for TA reporting over other downlink reception, thereby ensuring stability of the uplink of the half-duplex terminal in a non-terrestrial network.

[0260] For example, the above proposed method #03 can be applied in combination with other proposed method(s) to the extent that the operations of the present disclosure do not conflict.

[0261] For example, proposal #04 can be proposed.

[0262] For example, according to Proposal #04, when a base station (or network) and / or a terminal in a non-terrestrial network performs DL / UL collision handling rules and / or valid UL symbol / slot determination / counting according to a half-duplex transmission mode, a method may be proposed in which the base station (or network) and / or the terminal interprets a UL transmission section (hereinafter, the first section) that overlaps with a specific DL reception section in one of the following ways.

[0263] (1) For example, plan 1

[0264] (1) A. For example, starting point: UL transmission point with the same time index as the DL reception interval starting point + common TA - first offset

[0265] (1) B. For example, the end point: the UL transmission point with the same time index as the DL reception section end point + common TA + second offset

[0266] (2) For example, plan 2

[0267] (2) A. For example, starting point: UL transmission point with the same time index as the DL reception interval start point + (latest) reported TA - 3rd offset

[0268] (2) B. For example, the end point: the UL transmission point with the same time index as the end point of the DL reception interval + (latest) reported TA + the 4th offset.

[0269] (3) For example, plan 3

[0270] (3) A. For example, starting point: UL transmission point with the same time index as the DL reception section start point - 5th offset

[0271] (3) B. For example, the end point: the UL transmission point with the same time index as the DL reception section end point + the 6th offset

[0272] For example, in Proposal #04 or the present disclosure, the terminal may mean a half-duplex terminal.

[0273] For example, in Proposal #04 or the present disclosure, the DL reception may mean SSB reception, in which case the DL reception period may include a TX-RX conversion time and / or an RX-TX conversion time.

[0274] For example, in the proposed scheme #04 or the present disclosure, the first and / or second offset may be a value (pre-)promised and / or a value (pre-)set by the base station (or network) and the terminal.

[0275] For example, in Proposal #04 or the present disclosure, the third and / or fourth offsets may be values ​​(preliminarily) agreed upon and / or (preliminarily) set by the base station (or network) and the terminal. For example, in Proposal #04 or the present disclosure, the third and / or fourth offsets may be threshold values ​​(or values ​​modified based thereon) for TA reporting.

[0276] For example, in Proposal #04 or the present disclosure, the fifth and / or sixth offsets may be values ​​(preliminarily) agreed upon and / or (preliminarily) set by the base station (or network) and the terminal. For example, in Proposal #04 or the present disclosure, the fifth and / or sixth offsets may correspond to minimum TA and / or maximum TA values ​​determined according to the beam radius.

[0277] For example, in Proposal #04 or the present disclosure, the TA report may mean a TA report during the initial connection process and / or a TA report in CONNECTED MODE.

[0278] For example, in Proposal #04 or the present disclosure, the base station (or network) and / or terminal may perform DL / UL collision handling rules and / or valid UL symbol / slot determination / counting based on the overlapping UL transmission interval.

[0279] For example, in Proposal #04 or the present disclosure, the overlapping UL transmission intervals can be utilized for calculating time to check whether UL transmission is canceled and / or determining a UL transmission interval to cancel transmission.

[0280] For example, in Proposal #04 or the present disclosure, the base station (or network) can set / instruct the terminal which of the above scheme(s) to apply.

[0281] For example, in the proposal method #04 or the present disclosure, the common TA may mean a TA (Timing Advanced) value based on an RP (Reference Point) of the NTN, and the base station (or network) may transmit the common TA-related parameters to the terminal, and the terminal may calculate the common TA based on the parameter(s).

[0282] For example, in Proposal #04 or the present disclosure, the terminal may follow the method of the proposed method for valid UL symbol / slot determination / counting, but may omit UL transmission in a second section outside the first section if the UL transmission section (hereinafter referred to as the second section) that overlaps the specific DL reception section is different when reflecting the actual TA. For example, valid UL symbol / slot determination / counting may be based on the first section, but actual UL transmission may refer to the second section.

[0283] For example, in Proposal #04 or the present disclosure, the first and / or second and / or third and / or fourth and / or fifth and / or sixth offset may be determined / set based on the minimum / maximum TA value per satellite footprint and / or beam footprint.

[0284] For example, in Proposal #04 or the present disclosure, some and / or all of the (time) parameters for calculating the UL transmission interval may be applied after being quantized on a symbol-by-symbol basis and / or a symbol-by-symbol group basis and / or a slot basis.

[0285] For example, in a non-terrestrial network according to an embodiment of the present disclosure, it may be assumed that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. For example, in Proposal #04 or the present disclosure, if the terminal operates in a half-duplex transmission mode, DL reception and UL transmission cannot be performed simultaneously, and if the DL reception time and the UL transmission time collide, the terminal may perform DL reception and / or UL transmission with priority according to a DL / UL collision handling rule agreed upon / set in advance with the base station, or may determine it as an error case depending on the terminal implementation.

[0286] For example, in Proposal #04 or the present disclosure, a base station (or network) and / or a half-duplex terminal can prioritize a specific DL reception and promise not to transmit UL transmission that overlaps with the DL reception. For example, the DL reception can be a SSB (Synchronization Signal Block). For example, in Proposal #04 or the present disclosure, the terminal can determine that UL transmission is invalid in the entire section including the SSB section and the TX-RX Gap and / or RX-TX Gap before and after the section. For example, in Proposal #04 or the present disclosure, in the case of an NTN system, the terminal can apply a common TA based on an RP (Reference Point) of the NTN and / or a UE-specific TA (hereinafter referred to as UE TA) that the terminal autonomously applies. For example, in Proposal #04 or the present disclosure, the UE TA may correspond to several slots in an NTN environment with a large RTT, but may have characteristics unknown to the base station (or the network). For example, a difference may occur between the TA value assumed by the base station for the terminal and the TA value actually applied by the terminal, and the base station may not know how the terminal will interpret the UL transmission section overlapping with the SSB. For example, in Proposal #04 or the present disclosure, the above problem may affect not only the DL / UL collision handling rule but also when the terminal performs determination / counting for valid UL symbols / slots.

[0287] For example, therefore, in the present disclosure, when a base station (or network) and / or a terminal in a non-terrestrial network performs DL / UL collision handling rules and / or valid UL symbol / slot determination / counting according to a half-duplex transmission mode, a method may be proposed in which the base station (or network) and / or the terminal interprets a UL transmission section (hereinafter, a first section) that overlaps with a specific DL reception section in one of the following ways.

[0288] (1) For example, plan 1

[0289] (1) A. For example, starting point: UL transmission point with the same time index as the DL reception interval starting point + common TA - first offset

[0290] (1) B. For example, the end point: the UL transmission point with the same time index as the DL reception section end point + common TA + second offset

[0291] (2) For example, plan 2

[0292] (2) A. For example, starting point: UL transmission point with the same time index as the DL reception interval start point + (latest) reported TA - 3rd offset

[0293] (2) B. For example, the end point: the UL transmission point with the same time index as the end point of the DL reception interval + (latest) reported TA + the 4th offset.

[0294] (3) For example, plan 3

[0295] (3) A. For example, starting point: UL transmission point with the same time index as the DL reception section start point - 5th offset

[0296] (3) B. For example, the end point: the UL transmission point with the same time index as the DL reception section end point + the 6th offset

[0297] For example, according to the present disclosure (e.g., Proposal #04), since the overlapping UL transmission intervals for a specific DL reception interval are derived by applying pre-arranged / configured offset(s) based on a reference point (e.g., common TA and / or (latest) reported TA) known to the base station (or network) and the terminal, there is an advantage that the base station (or network) and the terminal can have the same understanding / interpretation of DL / UL collision handling rules and / or valid UL symbol / slot determination / counting. For example, it can support efficient resource management considering transmission resources that the base station (or network) and / or the terminal are canceled / omitted.

[0298] For example, the above proposed method #04 can be applied in combination with other proposed method(s) to the extent that the operations of the present disclosure do not conflict.

[0299] For example, proposal #05 can be proposed.

[0300] For example, according to Proposal #05, when a base station (or network) and / or a terminal in a non-terrestrial network performs DL / UL collision handling rules and / or valid UL symbol / slot determination / counting according to a half-duplex transmission mode, a method may be proposed in which the base station (or network) and / or the terminal interprets a DL reception interval that overlaps a specific UL transmission interval in one of the following ways.

[0301] (1) For example, plan 1

[0302] (1) A. For example, starting point: UL transmission interval starting point and DL reception point with the same time index - common TA - first offset

[0303] (1) B. For example, the end point: the DL reception point with the same time index as the UL transmission interval end point - common TA + second offset

[0304] (2) For example, plan 2

[0305] (2) A. For example, starting point: UL transmission interval starting point and DL reception point with same time index - (latest) reported TA - 3rd offset

[0306] (2) B. For example, the end point: the DL reception point with the same time index as the UL transmission interval end point - (latest) reported TA + 4th offset.

[0307] (3) For example, plan 3

[0308] (3) A. For example, starting point: DL reception point with the same time index as the UL transmission interval starting point - 5th offset

[0309] (3) B. For example, the end point: the DL reception point with the same time index as the UL transmission interval end point + the 6th offset.

[0310] For example, in Proposal #05 or the present disclosure, the terminal may mean a half-duplex terminal.

[0311] For example, in Proposal #05 or the present disclosure, the DL reception may mean SSB reception, in which case the DL reception period may include a TX-RX conversion time and / or an RX-TX conversion time.

[0312] For example, in the proposal #05 or the present disclosure, the first and / or second offset may be a value (pre-)promised and / or (pre-)set by the base station (or network) to the terminal.

[0313] For example, in Proposal #05 or the present disclosure, the third and / or fourth offsets may be values ​​(preliminarily) agreed upon and / or (preliminarily) set by the base station (or network) and the terminal. For example, in Proposal #05 or the present disclosure, the third and / or fourth offsets may be threshold values ​​(or values ​​modified based thereon) for TA reporting.

[0314] For example, in Proposal #05 or the present disclosure, the fifth and / or sixth offset may be a value (preliminarily) agreed upon and / or a value (preliminarily) set by the base station (or network) and the terminal. For example, in Proposal #05 or the present disclosure, the fifth and / or sixth offset may correspond to a minimum TA and / or a maximum TA value determined according to a beam radius.

[0315] For example, in Proposal #05 or the present disclosure, the TA report may mean a TA report during the initial connection process and / or a TA report in CONNECTED MODE.

[0316] For example, in Proposal #05 or the present disclosure, the base station (or network) and / or terminal may perform DL / UL collision handling rules and / or valid UL symbol / slot determination / counting based on the overlapping UL reception interval.

[0317] For example, in Proposal #05 or the present disclosure, the base station (or network) and / or terminal may perform DL / UL collision handling rules and / or valid UL symbol / slot determination / counting based on the overlapping DL reception interval.

[0318] For example, in Proposal #05 or the present disclosure, the overlapping DL reception interval can be utilized for calculating the time to check whether UL transmission is canceled and / or determining the UL transmission interval to be canceled.

[0319] For example, in Proposal #05 or the present disclosure, the base station (or network) can set / instruct the terminal which of the above scheme(s) to apply.

[0320] For example, in the proposal method #05 or the present disclosure, the common TA may mean a TA (Timing Advanced) value based on an RP (Reference Point) of the NTN, and the base station (or network) may transmit the common TA-related parameters to the terminal, and the terminal may calculate the common TA based on the parameter(s).

[0321] For example, in Proposal #05 or the present disclosure, the first and / or second and / or third and / or fourth and / or fifth and / or sixth offset may be determined / set based on the minimum / maximum TA value per satellite footprint and / or beam footprint.

[0322] For example, in Proposal #05 or the present disclosure, some and / or all of the (time) parameters for calculating the DL reception interval may be applied after being quantized on a symbol-by-symbol basis and / or a symbol-by-symbol group basis and / or a slot basis.

[0323] For example, in a non-terrestrial network according to an embodiment of the present disclosure, it may be assumed that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. For example, in Proposal #05 or the present disclosure, if the terminal operates in a half-duplex transmission mode, DL reception and UL transmission cannot be performed simultaneously, and if the DL reception time and the UL transmission time collide, the terminal may perform DL reception and / or UL transmission with priority according to a DL / UL collision handling rule agreed upon / set in advance with the base station, or may determine it as an error case depending on the terminal implementation.

[0324] For example, in Proposal #05 or the present disclosure, the base station (or network) and / or the half-duplex terminal can prioritize a specific UL transmission and promise not to receive some DL that overlaps with the UL transmission. For example, the UL transmission can be a dynamically scheduled PUSCH, and the DL reception can be a semi-statically configured PDSCH. For example, in Proposal #05 or the present disclosure, the terminal can determine that DL reception is not valid in the UL transmission interval. For example, in Proposal #05 or the present disclosure, in the case of an NTN system, the terminal can apply a common TA based on an RP (Reference Point) of the NTN and / or a UE-specific TA (hereinafter referred to as UE TA) that the terminal autonomously applies. For example, in Proposal #05 or the present disclosure, the UE TA can correspond to several slots in an NTN environment with a large RTT, but has a characteristic that the base station (or network) cannot know. For example, a difference may occur between the TA value assumed by the base station for the terminal and the TA value actually applied by the terminal, and a problem may arise where the base station does not know how the terminal will interpret the DL reception interval that overlaps the UL transmission interval. For example, in Proposal #05 or the present disclosure, the above problem may affect not only the DL / UL collision handling rule but also when the terminal performs determination / counting for valid UL symbols / slots.

[0325] For example, therefore, in the present disclosure, when a base station (or network) and / or a terminal in a non-terrestrial network performs DL / UL collision handling rules and / or valid UL symbol / slot determination / counting according to a half-duplex transmission mode, a method may be proposed in which the base station (or network) and / or the terminal interprets a DL reception interval overlapping with a specific UL transmission interval in one of the following ways.

[0326] (1) For example, plan 1

[0327] (1) A. For example, starting point: UL transmission interval starting point and DL reception point with the same time index - common TA - first offset

[0328] (1) B. For example, the end point: the DL reception point with the same time index as the UL transmission interval end point - common TA + second offset

[0329] (2) For example, plan 2

[0330] (2) A. For example, starting point: UL transmission interval starting point and DL reception point with same time index - (latest) reported TA - 3rd offset

[0331] (2) B. For example, the end point: the DL reception point with the same time index as the UL transmission interval end point - (latest) reported TA + 4th offset.

[0332] (3) For example, plan 3

[0333] (3) A. For example, starting point: DL reception point with the same time index as the UL transmission interval starting point - 5th offset

[0334] (3) B. For example, the end point: the DL reception point with the same time index as the UL transmission interval end point + the 6th offset.

[0335] For example, according to the present disclosure (e.g., Proposal #05), since a DL reception interval overlapping a specific UL transmission interval is derived by applying pre-arranged / configured offset(s) based on a reference point (e.g., common TA and / or (latest) reported TA) known to the base station (or network) and the terminal, there is an advantage that the base station (or network) and / or the terminal can have the same understanding / interpretation of DL / UL collision handling rules and / or valid UL symbol / slot determination / counting. For example, it can support efficient resource management considering transmission resources that are canceled / omitted by the base station (or network) and / or the terminal.

[0336] For example, the above proposed method #05 can be applied in combination with other proposed method(s) to the extent that the operations of the present disclosure do not conflict.

[0337] For example, proposal #06 can be proposed.

[0338] For example, according to Proposal #06, when a base station (or network) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to half-duplex transmission mode, a scheme may be proposed in which the base station and / or the terminal prioritizes UL transmission for TA (Timing Advance) report over other (specific) DL reception.

[0339] For example, in Proposal #06 or the present disclosure, the TA report may include one or more of the following:

[0340] (1) For example, TA reporting during the RRC setup / resume / re-establishment process.

[0341] (1) A. For example, the terminal may transmit a TA report to the base station through MAC CE in MSG3 (e.g., RAR (Random Access Response) based UL scheduling transmission) during the initial connection process.

[0342] (2) For example, TA reporting during the handover process

[0343] (2) A. For example, the terminal can transmit a TA report to the base station through MAC CE in the RRC Configuration Complete message during the handover process.

[0344] (3) For example, TA reporting by trigger

[0345] (3) A. For example, the terminal may transmit a TA report to the base station via MAC CE when a TA report is triggered due to a (specific) event.

[0346] For example, in Proposal #06 or the present disclosure, the half-duplex terminal may have DL / UL collision handling rules for DL / UL collisions.

[0347] For example, in Proposal #06 or the present disclosure, the (specific) DL reception may mean PDSCH reception and / or PDCCH reception. For example, it may mean PDSCH reception and / or PDCCH reception for data scheduling.

[0348] For example, in Proposal #06 or the present disclosure, the base station sets / instructs / promises to the terminal information related to time resources and / or time intervals for prioritizing UL transmission for TA reporting over other (specific) DL receptions, and the terminal can prioritize UL transmission for TA reporting over other (specific) DL receptions in the time resources and / or time intervals. For example, the base station can set / instruct / promise to the terminal a (dedicated) UL transmission resource for TA reporting, and the terminal can prioritize UL transmission in the (dedicated) UL transmission resource for TA reporting over (specific) DL receptions. For example, the base station can set / instruct / promise to the terminal a timer and / or time interval for TA reporting, and the terminal can prioritize UL transmission over (specific) DL reception before and / or within the time interval of the timer for TA reporting expiration.

[0349] For example, in Proposal #06 or the present disclosure, the base station (or network) can set / instruct the terminal to apply a DL / UL collision handling rule for the TA report. For example, the terminal can be set to apply a DL / UL collision handling rule that gives priority to the TA report over other specific DL receptions (the first DL / UL collision handling rule), or to apply a DL / UL collision handling rule that assumes the TA report as a general UL transmission (the second DL / UL collision handling rule).

[0350] For example, in a non-terrestrial network according to an embodiment of the present disclosure, it may be assumed that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. For example, in Proposal #06 or the present disclosure, if the terminal operates in a half-duplex transmission mode, DL reception and UL transmission cannot be performed simultaneously, and if the DL reception time and the UL transmission time collide, the terminal may perform DL reception and / or UL transmission with priority according to a DL / UL collision handling rule agreed upon / set in advance with the base station, or may determine it as an error case depending on the terminal implementation.

[0351] For example, in Proposal #06 or the present disclosure, a terminal operating in a non-terrestrial network can report a UE TA value that can be pre-compensated by itself to a base station (or network). For example, the terminal can transmit the TA report to the base station (or network) via MAC CE. For example, in Proposal #06 or the present disclosure, the TA report can be important information for the base station to estimate the RTT (hereinafter referred to as K_offset) between an RP (Reference Point) and the terminal, and the K_offset can be reflected in various scheduling timings. For example, the terminal can increase the uplink transmission timing by adding K_offset to the conventional transmission timing. For example, in Proposal #06 or the present disclosure, if the K_offset is not applied for a sufficiently long time, the transmission timing of the corresponding UL scheduling may occur earlier than the time at which the terminal receives the UL scheduling instruction from the base station (or network), and in such a case, UL transmission may be impossible. For example, the TA report may need to be treated as important information in a non-terrestrial network, and its transmission may need to be guaranteed to have a high priority when applying the DL / UL collision handling rules of a semi-mobile terminal. For example, the present disclosure may propose a method for a terminal to prioritize UL transmission for a TA (Timing Advance) report over other (specific) DL reception when a base station (or network) and / or a terminal performs DL / UL collision handling rules according to a half-duplex transmission mode in a non-terrestrial network. For example, the (specific) DL reception may mean general DL reception.

[0352] For example, according to the present disclosure (e.g., Proposal #06), there is an advantage in that it can support correct RTT calculation and scheduling timing setting by alleviating cases where TA reporting of a half-duplex terminal is omitted in a non-terrestrial network and by possibly supporting the forwarding of TA reporting to a base station (or network).

[0353] For example, the above proposed method #06 can be applied in combination with other proposed method(s) to the extent that the operations of the present disclosure do not conflict.

[0354] For example, proposal #07 can be proposed.

[0355] For example, according to Proposal #07, when a base station (or network) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, a method may be proposed in which the base station and / or the terminal apply DL / UL collision handling rules differently according to the HARQ feedback enable / disable setting for DL ​​reception and / or the HARQ mode A / mode B setting for UL transmission.

[0356] For example, a half-duplex terminal may apply different DL / UL collision handling rules depending on the HARQ feedback enable / disable setting for DL ​​reception and / or the HARQ mode A / mode B setting for UL transmission as follows.

[0357] (1) For example, Scheme 1: Scheme that prioritizes (HARQ feedback disabled) DL reception and / or (HARQ mode B) UL transmission over (HARQ feedback enabled) DL reception and / or (HARQ mode A) UL transmission.

[0358] (2) For example, Scheme 2: Scheme that prioritizes (HARQ feedback enabled) DL reception and / or (HARQ mode A) UL transmission over (HARQ feedback disabled) DL reception and / or (HARQ mode B) UL transmission

[0359] For example, in Proposal #07 or the present disclosure, the half-duplex terminal may have DL / UL collision handling rules for DL / UL collisions.

[0360] For example, in Proposal #07 or the present disclosure, the DL reception and / or UL transmission may be dynamically scheduled and / or semi-statically configured DL reception and / or UL transmission.

[0361] For example, in the proposal #07 or the present disclosure, if the HARQ feedback is enabled, HARQ feedback and / or DL ​​retransmission may be performed, and if the HARQ feedback is disabled, HARQ feedback and / or DL ​​retransmission may not be performed.

[0362] For example, in the proposed scheme #07 or the present disclosure, in the case of HARQ mode A, UL retransmission may be performed, and in the case of HARQ mode B, UL retransmission may not be performed.

[0363] For example, in a non-terrestrial network according to an embodiment of the present disclosure, it may be assumed that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. For example, in Proposal #07 or the present disclosure, if the terminal operates in a half-duplex transmission mode, DL reception and UL transmission cannot be performed simultaneously, and if the DL reception time and the UL transmission time collide, the terminal may perform DL reception and / or UL transmission with priority according to a DL / UL collision handling rule agreed upon / set in advance with the base station, or may determine it as an error case depending on the terminal implementation.

[0364] For example, in Proposal #07 or the present disclosure, a non-terrestrial network may need to operate a large number of HARQ (Hybrid ARQ) process(es) due to high RTT (Round Trip Time) delay at high altitudes. For example, in Proposal #07 or the present disclosure, if the number of HARQs is greatly increased, it may be difficult for the base station and / or the terminal to support all of the HARQ process(es), so HARQ feedback may be disabled and / or HARQ mode B may be set for some of the HARQ process(es). For example, in Proposal #07 or the present disclosure, for the HARQ process(es) set to HARQ feedback disabled and / or HARQ mode B as described above, the impact of some transmissions being dropped and / or omitted may be greater than when HARQ feedback is enabled and / or HARQ mode B is set. For example, when a terminal applies a DL / UL collision handling rule according to a half-duplex mode, it may be desirable to give priority to DL reception and / or UL transmission set to HARQ feedback disable and / or HARQ mode B. For example, the present disclosure may propose a method in which, when a base station (or network) and / or a terminal in a non-terrestrial network can perform a DL / UL collision handling rule according to a half-duplex transmission mode, the base station and / or the terminal apply the DL / UL collision handling rule differently according to a HARQ feedback enable / disable setting for DL ​​reception and / or a HARQ mode A / mode B setting for UL transmission.For example, a half-duplex terminal may apply different DL / UL collision handling rules depending on the HARQ feedback enable / disable setting for DL ​​reception and / or the HARQ mode A / mode B setting for UL transmission as follows.

[0365] (1) For example, Scheme 1: Scheme that prioritizes (HARQ feedback disabled) DL reception and / or (HARQ mode B) UL transmission over (HARQ feedback enabled) DL reception and / or (HARQ mode A) UL transmission.

[0366] (2) For example, Scheme 2: Scheme that prioritizes (HARQ feedback enabled) DL reception and / or (HARQ mode A) UL transmission over (HARQ feedback disabled) DL reception and / or (HARQ mode B) UL transmission

[0367] For example, according to the present disclosure (e.g., Proposal #07), there is an advantage in that the system performance degradation due to DL and / or UL transmission omission can be mitigated by first protecting the HARQ process, which is relatively vulnerable to transmission omission, when applying the DL / UL collision handling rule of a half-duplex terminal.

[0368] For example, the above proposed method #07 can be applied in combination with other proposed method(s) to the extent that the operations of the present disclosure do not conflict.

[0369] For example, proposal #08 can be proposed.

[0370] For example, according to the proposal #08, when a base station (or network) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, a method may be proposed in which the base station and / or the terminal assume a virtual UL transmission interval (hereinafter referred to as a second transmission interval) having a start time when a first TA is assumed to be applied and an end time when a second TA is assumed to be applied for a (specific) UL transmission interval (hereinafter referred to as a first transmission interval), and performs the DL / UL collision handling rules based on the second transmission interval.

[0371] For example, in Proposal #08 or the present disclosure, the first TA and / or the second TA may be configured as a (common) TA and / or a time offset.

[0372] For example, in the proposal method #08 or the present disclosure, the first TA and / or the second TA can be recognized as the same value between the base station and the terminal.

[0373] For example, in Proposal #08 or the present disclosure, the time offset can be set / instructed by the base station (or network) to the terminal.

[0374] For example, in Proposal #08 or the present disclosure, when the terminal applies the actual TA (of the terminal) to the (specific) UL transmission interval, the terminal may omit part and / or all of the UL transmissions that fall outside the second transmission interval.

[0375] For example, in the proposal #08 or the present disclosure, the second transmission interval can be used for calculating a time to check whether UL transmission is canceled and / or determining a UL transmission interval to be canceled.

[0376] For example, in a non-terrestrial network according to an embodiment of the present disclosure, it may be assumed that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. For example, in Proposal #08 or the present disclosure, if the terminal operates in a half-duplex transmission mode, DL reception and UL transmission cannot be performed simultaneously, and if the DL reception time and the UL transmission time collide, the terminal may perform DL reception and / or UL transmission with priority according to a DL / UL collision handling rule agreed upon / set in advance with the base station, or may determine it as an error case depending on the terminal implementation.

[0377] For example, in the case of the NTN system in Proposal #08 or the present disclosure, the terminal can apply a common TA based on the RP (Reference Point) of the NTN and / or a UE-specific TA (hereinafter referred to as UE TA) that the terminal autonomously applies. For example, in the Proposal #08 or the present disclosure, the UE TA may correspond to several slots in an NTN environment with a large RTT, but may have characteristics that the base station (or network) cannot know. For example, therefore, a difference may occur between the TA value that the base station assumes for the terminal and the TA value that the terminal actually applies, and a problem may arise in which it is not known how to interpret the DL reception interval that overlaps the UL transmission interval. For example, in the Proposal #08 or the present disclosure, the above problem may affect not only the DL / UL collision handling rule but also when the terminal performs determination / counting for valid UL symbols / slots. For example, therefore, in the present disclosure, when a base station (or network) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, a method may be proposed in which the base station and / or the terminal assume a virtual UL transmission interval (hereinafter, a second transmission interval) having a start time when a first TA is applied and an end time when a second TA is applied for a (specific) UL transmission interval (hereinafter, a first transmission interval), and performs the DL / UL collision handling rules based on the second transmission interval.

[0378] For example, according to the present disclosure (e.g., Proposal #08), since the base station and the terminal can perform DL / UL collision handling rules based on the first TA and / or the second TA having the same understanding, there may be an advantage in that the DL / UL collision understanding between them becomes consistent and transmission and reception operations can be made clear.

[0379] For example, in Proposal #08 or the present disclosure, when the terminal applies the actual TA (of the terminal) to the (specific) UL transmission interval, the terminal may omit part and / or all of the UL transmissions that fall outside the second transmission interval.

[0380] For example, the above proposed scheme #08 can be applied in combination with other proposed scheme(s) to the extent that the operations of the present disclosure do not conflict.

[0381] For example, proposal #09 can be proposed.

[0382] For example, according to Proposal #09, a method may be proposed in which a terminal in a non-terrestrial network reports TA information in a predictable form to a base station (or network), and triggers TA reporting by utilizing a TA actual value and / or a previous TA value (based on the TA report) and / or a TA predicted value (based on the TA report).

[0383] For example, (in a non-terrestrial network) a terminal reports one or more of the following information to the base station (or network) as TA information:

[0384] (1) For example, TA value (at the reference point) (hereinafter referred to as first information)

[0385] (2) For example, information for predicting TA (at a future point in time) (e.g., TA change rate, etc.) (hereinafter referred to as second information)

[0386] For example, a TA report trigger can be triggered by utilizing one or more of the following conditions:

[0387] (1) For example, if the difference between the (actual) TA value (at the current point in time) and the TA value (at the previous point in time) (based on the first information) is greater than the first threshold,

[0388] (2) For example, if the difference between the (actual) TA value (at the current point in time) and the (predicted) TA value (at the current point in time) (based on the first information and / or the second information) is greater than or equal to the second threshold,

[0389] For example, in Proposal #09 or the present disclosure, the reference point may be the TA reporting point.

[0390] For example, in Proposal #09 or the present disclosure, the TA information may include UE-specific TA (e.g., UE-specific TA) information and / or (common) TA information set / indicated by the base station (or network).

[0391] For example, in Proposal #09 or the present disclosure, the information for TA prediction may have a limited validity period. For example, the terminal may report a timer value that ensures the validity of the information for TA prediction, and the terminal and / or base station (or network) may interpret that the information for TA prediction is no longer valid when the timer expires.

[0392] For example, in Proposal #09 or the present disclosure, the base station (or network) can configure which of the above methods the terminal applies TA information reporting and / or TA reporting trigger conditions.

[0393] For example, in Proposal #09 or the present disclosure, the (actual) TA may mean the TA expected / calculated by the terminal.

[0394] For example, in the proposed scheme #09 or the present disclosure, the TA prediction value can be calculated based on the first information and / or the second information and / or the (pre-arranged and / or set) formula (between the base station and the terminal).

[0395] For example, in Proposal #09 or the present disclosure, the base station (or network) may set the first threshold value and the second threshold value to the same parameter and / or may set them independently.

[0396] For example, in a non-terrestrial network according to an embodiment of the present disclosure, it may be assumed that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. For example, in Proposal #09 or the present disclosure, if the terminal operates in a half-duplex transmission mode, DL reception and UL transmission cannot be performed simultaneously, and if the DL reception time and the UL transmission time collide, the terminal may give priority to DL reception and / or UL transmission according to a DL / UL collision handling rule agreed upon / set in advance with the base station.

[0397] For example, in the proposal #09 or the present disclosure, in the uplink of the non-terrestrial network, the terminal can apply a (common) TA (Timing Advance) that compensates for the time delay between the feeder link and the satellite, and a (UE) TA that compensates for the time delay between the terminal and the satellite. For example, in the proposal #09 or the present disclosure, the (common) TA is a value that is mutually recognized in common between the base station (or network) and the terminal through parameters and calculation formulas shared between the base station (or network), and the (UE) TA may be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network) end. For example, in the proposal #09 or the present disclosure, the TA (first TA) that the base station (or network) expects / predicts for the terminal and the TA (second TA) that the terminal actually applies may have different values.

[0398] For example, in Proposal #09 or the present disclosure, a non-terrestrial network may support a function in which a terminal can report (UE) TA to a base station (or network). For example, in Proposal #09 or the present disclosure, the (UE) TA reported by the terminal may change from the reporting time depending on the relative movement of the terminal and / or the satellite. For example, therefore, when a terminal reports TA information, a method may be considered in which the terminal reports both a TA value (at a reference time) and information for predicting TA (at a future time) (e.g., TA shift information).

[0399] For example, the present disclosure may propose a method of performing a TA reporting trigger by utilizing the information when the terminal reports TA information in a form that can be predicted at a future point in time. For example, the terminal may report one or more of the following information to the base station as TA information:

[0400] (1) For example, TA value (at the reference point) (hereinafter referred to as first information)

[0401] (2) For example, information for predicting TA (at a future point in time) (e.g., TA change rate, etc.) (hereinafter referred to as second information)

[0402] For example, the terminal may then trigger a TA report by utilizing one or more of the following conditions:

[0403] (1) For example, if the difference between the (actual) TA value (at the current point in time) and the TA value (at the previous point in time) (based on the first information) is greater than the first threshold.

[0404] (2) For example, if the difference between the (actual) TA value (at the current point in time) and the (predicted) TA value (at the current point in time) (based on the first information and / or the second information) is greater than or equal to the second threshold.

[0405] For example, when the terminal reports the second information, the terminal may perform a TA reporting trigger based on the second condition. For example, since the terminal performs a TA report when the difference between the TA value reported at a past point in time and the current TA is greater than a certain level in the past, frequent TA reporting and signaling load may occur when the threshold value for TA reporting is set low. For example, on the other hand, according to the proposed method of the present disclosure, since TA reporting is performed when the difference between the predicted TA value for a future point in time and the current TA is greater than a certain level, even if the threshold value for TA reporting is set low, the TA reporting and signaling load may not be relatively large. For example, there is an advantage of reducing the TA reporting and signaling load while increasing the accuracy of TA reporting.

[0406] For example, according to the present disclosure (e.g., Proposal #09), there is an advantage of increasing the accuracy of TA reporting while reducing the TA reporting and signaling load.

[0407] For example, the above proposed method #09 can be applied in combination with other proposed method(s) to the extent that the operations of the present disclosure do not conflict.

[0408] For example, proposal #10 could be proposed.

[0409] For example, according to Proposal #10, a method may be proposed in which a terminal in a non-terrestrial network reports TA information in a predictable form to a base station (or network), and DL / UL collision resource determination is performed by utilizing the TA actual value and / or the previous TA value (based on the TA report) and / or the TA predicted value (based on the TA report).

[0410] For example, (in a non-terrestrial network) a terminal reports one or more of the following information as TA information to a base station (or network):

[0411] (1) For example, TA value (at the reference point) (hereinafter referred to as first information)

[0412] (2) For example, information for predicting TA (at a future point in time) (e.g., TA change rate, etc.) (hereinafter referred to as second information)

[0413] For example, a method for determining DL / UL collision resources by using one or more of the following methods may be proposed.

[0414] (1) For example, when applying the TA value (at the present time), a method can be proposed to determine overlapping DL / UL resources (within a specific time gap) (on the time axis) as DL / UL conflict resources.

[0415] (2) For example, when applying the TA value (at a previous point in time) (based on the first information), a method can be proposed to determine overlapping DL / UL resources (within a specific time gap) (on the time axis) as DL / UL conflict resources.

[0416] (3) For example, when applying a TA prediction value (at the present time) (based on first information and / or second information), a method may be proposed to determine overlapping DL / UL resources (within a specific time gap) (on the time axis) as DL / UL conflicting resources.

[0417] For example, in Proposal #10 or the present disclosure, the reference point may be the TA reporting point.

[0418] For example, in Proposal #10 or the present disclosure, the TA information may include UE-specific TA (e.g., UE-specific TA) information and / or (common) TA information set / indicated by the base station (or network).

[0419] For example, in Proposal #10 or the present disclosure, the information for TA prediction may have a limited validity period. For example, the terminal may report a timer value that ensures the validity of the information for TA prediction, and the terminal and / or base station (or network) may interpret that the information for TA prediction is no longer valid when the timer expires.

[0420] For example, in Proposal #10 or the present disclosure, the base station (or network) can configure in which of the above methods the terminal performs TA information reporting and / or DL / UL collision resource determination.

[0421] For example, in Proposal #10 or the present disclosure, the DL / UL collision resources can be utilized for valid slot / symbol count and / or DM-RS bundling interval (e.g., TDW) and / or DL ​​reception skipping and / or UL transmission skipping (due to DL / UL collision).

[0422] For example, in the proposed method #10 or the present disclosure, the time gap may be information that is (pre-)promised and / or (pre-)set between the base station (or network) and the terminal.

[0423] For example, in Proposal #10 or the present disclosure, the DM-RS bundling may mean an operation of performing channel estimation by utilizing DM-RS resource(s) between UL repeated transmissions.

[0424] For example, in the proposal #10 or the present disclosure, the TDW may mean a (time) interval during which the terminal guarantees phase continuity and / or power consistency of a signal during UL transmission. For example, the base station (or network) and / or the terminal may set / promise a (nominal) TDW interval for a specific UL transmission, and may interpret the (actual) TDW interval based on the time at which an event occurs within the UL transmission. For example, the interval from the start time of UL transmission until the occurrence of the event may be interpreted as the (actual) TDW interval, and thereafter, the (actual) TDW interval may be (re)started according to the setting within the remaining (nominal) TDW interval.

[0425] For example, in the proposed scheme #10 or the present disclosure, the TA prediction value can be calculated based on the first information and / or the second information and / or the (pre-arranged and / or established) formula (between the base station and the terminal).

[0426] For example, in a non-terrestrial network according to an embodiment of the present disclosure, it may be assumed that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. For example, in Proposal #10 or the present disclosure, if the terminal operates in a half-duplex transmission mode, DL reception and UL transmission cannot be performed simultaneously, and if the DL reception time and the UL transmission time collide, the terminal may give priority to DL reception and / or UL transmission according to a DL / UL collision handling rule agreed upon / set in advance with the base station.

[0427] For example, in the proposal #10 or the present disclosure, in the uplink of a non-terrestrial network, a (common) TA (Timing Advance) that compensates for the time delay between a feeder link and a satellite and a (UE) TA that compensates for the time delay between the terminal and a satellite can be applied. For example, in the proposal #10 or the present disclosure, the (common) TA is a value that is mutually recognized in common between a base station (or a network) and a terminal through parameters and calculation formulas shared between the base station (or a network) and the terminal, and the (UE) TA may be a value that the terminal voluntarily adjusts and that is unknown to the base station (or the network). For example, in the proposal #10 or the present disclosure, a TA (first TA) that a base station (or a network) expects / predicts for a terminal and a TA (second TA) that the terminal actually applies may have different values.

[0428] For example, in Proposal #10 or the present disclosure, due to reasons such as application of the (UE) TA, there may be cases where the mutual recognition of DL / UL conflicting resources between a base station (or network) and a terminal in a non-terrestrial network differs. For example, when determining a UL resource / slot that conflicts with a specific DL resource / slot, there may be cases where the location of the UL resource / slot determined to conflict with the DL resource / slot differs by several slots between the base station (or network) and the terminal.

[0429] For example, in Proposal #10 or the present disclosure, a non-terrestrial network may support a function that allows a terminal to report (UE) TA to a base station (or network). For example, in Proposal #10 or the present disclosure, the (UE) TA reported by the terminal may change from the reporting time depending on the relative movement of the terminal and / or the satellite. For example, therefore, when a terminal reports TA information, a method may be considered in which the TA value (at a reference time) and information for predicting TA (at a future time) (e.g., TA shift information) are reported together.

[0430] For example, the present disclosure proposes a method for performing DL / UL collision determination by utilizing TA information reported by a terminal in a form that can be predicted at a future point in time. For example, the terminal reports one or more of the following information to the base station as TA information:

[0431] (1) For example, TA value (at the reference point) (hereinafter referred to as first information)

[0432] (2) For example, information for predicting TA (at a future point in time) (e.g., TA change rate, etc.) (hereinafter referred to as second information)

[0433] For example, the terminal may then use one or more of the following methods to determine DL / UL conflict resources:

[0434] (1) For example, when applying the TA value (at the present time), a method can be proposed to determine overlapping DL / UL resources (within a specific time gap) (on the time axis) as DL / UL conflict resources.

[0435] (2) For example, when applying the TA value (at a previous point in time) (based on the first information), a method can be proposed to determine overlapping DL / UL resources (within a specific time gap) (on the time axis) as DL / UL conflict resources.

[0436] (3) For example, when applying a TA prediction value (at the present time) (based on first information and / or second information), a method may be proposed to determine overlapping DL / UL resources (within a specific time gap) (on the time axis) as DL / UL conflicting resources.

[0437] For example, the terminal can first determine the resources overlapping in the time axis based on the current TA as DL / UL collision resources (hereinafter referred to as first DL / UL collision resources). For example, if the terminal reports the second information, the resources overlapping in the time axis when the TA is applied based on the second information can be determined as additional DL / UL collision resources (hereinafter referred to as second DL / UL collision resources). For example, in Proposal #10 or the present disclosure, the terminal can utilize the first and / or second DL / UL collision resources for determining the effective slot / symbol count and / or DM-RS bundling interval (e.g., TDW) and / or DL ​​reception omission and / or UL transmission omission (due to DL / UL collision). For example, in Proposal #10 or the present disclosure, the second DL / UL collision resources can be utilized when the base station and the terminal must have the same awareness, for example, for determining the effective slot / symbol count and / or TDW. For example, this has the advantage of supporting correct transmission and reception operations between the base station and the terminal.

[0438] For example, according to the present disclosure (e.g., Proposal #10), there is an advantage in that correct transmission and reception operations between a base station and a terminal can be supported.

[0439] For example, the above proposed scheme #10 can be applied in combination with other proposed scheme(s) to the extent that the operations of the present disclosure do not conflict.

[0440] For example, proposal #11 can be proposed.

[0441] For example, according to Proposal #11, when a base station (or network node) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, a scheme may be proposed in which the base station (or network node) and / or the terminal applies different priorities of TA (Timing Advance) reports depending on the trigger type.

[0442] For example, in Proposal #11 or the present disclosure, the DL / UL conflict handling rules may include DL / UL priority rules.

[0443] For example, in Proposal #11 or the present disclosure, the terminal may prioritize UL transmission for TA reporting triggered based on a DL / UL collision event over other (specific) DL reception.

[0444] For example, in Proposal #11 or the present disclosure, the terminal may prioritize UL transmission for TA reporting triggered by an instruction from a base station (or network node) over other (specific) DL reception.

[0445] For example, in Proposal #11 or the present disclosure, the base station (or network node) can set / instruct the terminal to set / instruct the DL / UL priority rules of TA reporting by trigger type.

[0446] For example, in a non-terrestrial network according to an embodiment of the present disclosure, it may be assumed that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. For example, in Proposal #11 or the present disclosure, if the terminal operates in a half-duplex transmission mode, DL reception and UL transmission cannot be performed simultaneously, and if the DL reception time and the UL transmission time collide, the terminal may give priority to DL reception and / or UL transmission according to a DL / UL collision handling rule agreed upon / set in advance with the base station.

[0447] For example, in the proposal #11 or the present disclosure, in the uplink of a non-terrestrial network, a terminal can apply a (common) TA (Timing Advance) that compensates for the time delay between a feeder link and a satellite, and a (UE) TA that compensates for the time delay between the terminal and a satellite. For example, in the proposal #11 or the present disclosure, the (common) TA is a value that is mutually recognized through parameters and calculation formulas shared between the base station (or network) and the terminal, and the (UE) TA may be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network) end. For example, in the proposal #11 or the present disclosure, the TA (first TA) that the base station (or network) expects / predicts for the terminal and the TA (second TA) that the terminal actually applies may have different values.

[0448] For example, in a non-terrestrial network, DL / UL collision case(s) (hereinafter referred to as error cases) (e.g., collision between dynamically scheduled DL transmission resources and dynamically scheduled UL transmission resources and / or collision between semi-statically configured DL transmission resources and semi-statically configured UL transmission resources) that conventional base stations (or networks) are expected to avoid may occur relatively frequently, and DL / UL collision handling rules for a terminal operating in a half-duplex transmission mode for the above case(s) may need to be defined.

[0449] For example, in Proposal #11 or the present disclosure, in order to help the base station recognize a DL / UL collision situation at the terminal end, the terminal can trigger a TA report based on a DL / UL collision event. For example, in Proposal #11 or the present disclosure, the TA report triggered by the DL / UL collision event may have a higher priority than a conventional TA threshold-based TA report trigger. For example, in Proposal #11 or the present disclosure, a higher priority rule and / or a separate DL / UL collision handling rule may need to be applied to the TA report triggered by the DL / UL collision event compared to a conventional TA report. For example, transmission of the collision-based TA report may always be given priority over DL transmission. For example, therefore, in the present disclosure, when a base station (or network node) and / or a terminal can perform DL / UL collision handling rules according to a half-duplex transmission mode in a non-terrestrial network, a method may be proposed in which the base station (or network node) and / or the terminal applies different priorities of TA (Timing Advance) reporting according to a trigger type. For example, in Proposal #11 or the present disclosure, the terminal may prioritize UL transmission for TA reporting triggered based on a DL / UL collision event over other (specific) DL reception. For example, in Proposal #11 or the present disclosure, the terminal may prioritize UL transmission for TA reporting triggered by an instruction of the base station (or network node) over other (specific) DL reception. For example, in Proposal #11 or the present disclosure, the base station (or network node) may set / instruct the terminal to set / instruct DL / UL priority rules for TA reporting according to a trigger type.

[0450] For example, according to the present disclosure (e.g., Proposal #11), a base station (or network node) can control a terminal to prioritize a terminal report related to a DL / UL collision situation over other downlink receptions, thereby enabling the base station (or network node) to support rapid detection and response to a DL / UL collision situation.

[0451] For example, the above proposed scheme #11 can be applied in combination with other proposed scheme(s) to the extent that the operations of the present disclosure do not conflict.

[0452] For example, proposal #12 can be proposed.

[0453] For example, according to Proposal #12, when a base station (or network node) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, a scheme may be proposed in which the base station (or network node) and / or the terminal prioritizes DL / UL collision event-based TA (Timing Advance) reporting and / or UL transmission for DL / UL collision event reporting over other (specific) DL reception.

[0454] For example, in Proposal #12 or the present disclosure, the DL / UL conflict handling rules may include DL / UL priority rules.

[0455] For example, in Proposal #12 or the present disclosure, the base station (or network node) may set / instruct the terminal to perform DL / UL collision event-based TA (Timing Advance) reporting and / or DL / UL priority rules to be applied to DL / UL collision event reporting.

[0456] For example, in a non-terrestrial network according to an embodiment of the present disclosure, it may be assumed that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. For example, in Proposal #12 or the present disclosure, if the terminal operates in a half-duplex transmission mode, DL reception and UL transmission cannot be performed simultaneously, and if the DL reception time and the UL transmission time collide, the terminal may give priority to DL reception and / or UL transmission according to a DL / UL collision handling rule agreed upon / set in advance with the base station.

[0457] For example, in Proposal #12 or the present disclosure, in the uplink of a non-terrestrial network, a terminal can apply a (common) TA (Timing Advance) that compensates for the time delay between a feeder link and a satellite, and a (UE) TA that compensates for the time delay between the terminal and a satellite. For example, in Proposal #12 or the present disclosure, the (common) TA is a value that is mutually recognized through parameters and calculation formulas shared between the base station (or network) and the terminal, and the (UE) TA may be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network) end. For example, in Proposal #12 or the present disclosure, a TA (first TA) that the base station (or network) expects / predicts for the terminal and a TA (second TA) that the terminal actually applies may have different values.

[0458] For example, in a non-terrestrial network, DL / UL collision case(s) (hereinafter referred to as error cases) (e.g., collision between dynamically scheduled DL transmission resources and dynamically scheduled UL transmission resources and / or collision between semi-statically configured DL transmission resources and semi-statically configured UL transmission resources) that conventional base stations (or networks) are expected to avoid may occur relatively frequently, and DL / UL collision handling rules for a terminal operating in a half-duplex transmission mode for the above case(s) may need to be defined.

[0459] For example, in Proposal #12 or the present disclosure, in order to help the base station recognize a DL / UL collision situation at the terminal end, the terminal can perform TA reporting and / or collision reporting based on the DL / UL collision event. For example, in Proposal #12 or the present disclosure, the DL / UL collision-related terminal reporting can have a higher priority than other downlink transmissions. For example, the transmission of the DL / UL collision-related terminal reporting can always be given priority over DL transmissions. For example, therefore, in the present disclosure, when the base station (or network node) and / or the terminal can perform DL / UL collision handling rules according to the half-duplex transmission mode in a non-terrestrial network, a scheme can be proposed in which the base station (or network node) and / or the terminal gives priority to UL transmission for DL / UL collision event-based TA (Timing Advance) reporting and / or DL / UL collision event reporting over other (specific) DL receptions. For example, in Proposal #12 or the present disclosure, the base station (or network node) may set / instruct the terminal to perform DL / UL collision event-based TA (Timing Advance) reporting and / or DL / UL priority rules to be applied to DL / UL collision event reporting.

[0460] For example, according to the present disclosure (e.g., Proposal #12), a base station (or network node) can control a terminal to prioritize a terminal report related to a DL / UL collision situation over other downlink receptions, thereby enabling the base station (or network node) to support rapid detection and response to a DL / UL collision situation.

[0461] For example, the above proposed scheme #12 can be applied in combination with other proposed scheme(s) to the extent that the operations of the present disclosure do not conflict.

[0462] For example, proposal #13 can be proposed.

[0463] For example, according to Proposal #13, when a base station (or network node) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, and when the base station (or network node) and / or the terminal can perform transmission skipping for DL / UL resources where a collision has occurred, a method may be proposed in which the base station (or network node) sets / indicates resource unit information for the transmission skipping.

[0464] For example, in Proposal #13 or the present disclosure, the DL / UL conflict handling rules may include DL / UL priority rules.

[0465] For example, in the proposal method #13 or the present disclosure, the base station (or network node) may set the unit for transmission omission as a repetition transmission unit and / or a slot unit and / or a symbol unit when DL transmission omission and / or UL transmission omission due to DL / UL collision occurs to the terminal.

[0466] For example, in a non-terrestrial network according to an embodiment of the present disclosure, it may be assumed that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. For example, in Proposal #13 or the present disclosure, if the terminal operates in a half-duplex transmission mode, DL reception and UL transmission cannot be performed simultaneously, and if the DL reception time and the UL transmission time collide, the terminal may give priority to DL reception and / or UL transmission according to a DL / UL collision handling rule agreed upon / set in advance with the base station.

[0467] For example, in Proposal #13 or the present disclosure, in the uplink of a non-terrestrial network, a terminal can apply a (common) TA (Timing Advance) that compensates for the time delay between a feeder link and a satellite, and a (UE) TA that compensates for the time delay between the terminal and a satellite. For example, in Proposal #13 or the present disclosure, the (common) TA is a value that is mutually recognized through parameters and calculation formulas shared between the base station (or network) and the terminal, and the (UE) TA may be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network) end. For example, in Proposal #13 or the present disclosure, a TA (first TA) that the base station (or network) expects / predicts for the terminal and a TA (second TA) that the terminal actually applies may have different values.

[0468] For example, in a non-terrestrial network, DL / UL collision case(s) (hereinafter referred to as error cases) (e.g., collision between dynamically scheduled DL transmission resources and dynamically scheduled UL transmission resources and / or collision between semi-statically configured DL transmission resources and semi-statically configured UL transmission resources) that conventional base stations (or networks) are expected to avoid may occur relatively frequently, and DL / UL collision handling rules for a terminal operating in a half-duplex transmission mode for the above case(s) may need to be defined.

[0469] For example, in Proposal #13 or the present disclosure, the DL / UL collision handling rule may be a rule that prioritizes DL or UL transmission, and may omit some or all of the DL or UL transmission. For example, in Proposal #13 or the present disclosure, the base station (or network node) may set / instruct the terminal to have resource unit information for the transmission omission. For example, if symbol-based TA control and sophisticated DL / UL collision management are supported in a non-terrestrial network, the base station (or network node) may allow the terminal to omit symbol-based transmission. For example, on the other hand, if only slot-based TA control is possible in a non-terrestrial network, the base station (or network node) may not allow the terminal to omit symbol-based transmission, and may be configured to perform transmission omission in units of slots or entire repeated transmissions.

[0470] For example, according to the present disclosure (e.g., Proposal #13), a base station (or network node) can control resource units for which a terminal performs transmission skipping in the event of a DL / UL collision, thereby improving efficiency in terms of resource utilization in the event of a DL / UL collision.

[0471] For example, the above proposed scheme #13 can be applied in combination with other proposed scheme(s) to the extent that the operations of the present disclosure do not conflict.

[0472] For example, in the mobile communications field, Non-Terrestrial Networks (NTNs), which utilize satellites as network nodes, are being actively discussed. Satellites used in NTN environments can be categorized into geostationary (GEO), medium Earth orbit (MEO), and low Earth orbit (LEO) satellites based on their orbital altitude and characteristics. Compared to ground-based networks, they are characterized by very high altitudes and long propagation delays.

[0473] For example, in such NTN environments, if a terminal supports half-duplex transmission, downlink (DL) reception and uplink (UL) transmission cannot be performed simultaneously. Therefore, if the timing of DL reception and UL transmission overlap in time, a collision may occur. For example, if a terminal is scheduled to receive important system information (e.g., system information change history) or control signals via DL and UL transmission is scheduled at the same time, a collision may result in the terminal not being able to properly receive the system information or the UL transmission being delayed.

[0474] For example, existing methods have been proposed to allow terminals or networks to arbitrarily resolve DL / UL collisions, or to selectively perform DL or UL transmission based on certain priority rules. However, if these methods fail to sufficiently consider NTN-specific limitations, such as high satellite altitudes, long propagation delays, and terminal-autonomous Timing Advance (TA) implementation, system performance and link reliability may deteriorate. Therefore, for terminals supporting half-duplex transmission in NTN environments, a technical solution is required that effectively handles DL / UL collisions to ensure stable reception of critical system information while simultaneously enabling efficient UL transmission.

[0475] For example, proposal #14 can be proposed.

[0476] For example, according to Proposal #14, when a base station (or network node) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, a method may be proposed to apply DL / UL collision handling rules differently depending on whether system information is being acquired and / or whether a change in system information falls within a time interval (or a specific sub-interval of that time interval) that is indicated / announced.

[0477] For example, in Proposal #14 or the present disclosure, the DL / UL conflict handling rules may include DL / UL priority rules.

[0478] For example, in Proposal #14 or the present disclosure, the time period in which a change of the system information is indicated / announced may mean a Modification time period in which a SI change (Modification) is indicated.

[0479] For example, in Proposal #14 or the present disclosure, prior to acquisition of the system information, a (specific) DL transmission may be given priority over a (specific) UL transmission. For example, the (specific) DL transmission may include a Type0 / 0A-PDCCH CSS (Common Search Space) type.

[0480] For example, in Proposal #14 or the present disclosure, a (specific) DL transmission may be given priority over a (specific) UL transmission within a time interval in which a change in the system information is indicated / announced. For example, the (specific) DL transmission may include a Type0 / 0A-PDCCH CSS (Common Search Space) type.

[0481] For example, in Proposal #14 or the present disclosure, a (specific) DL transmission may not be prioritized over a (specific) UL transmission outside of a time interval in which a change in the system information is indicated / announced. For example, the (specific) DL transmission may include a Type0 / 0A-PDCCH CSS (Common Search Space) type.

[0482] For example, in Proposal #14 or the present disclosure, the base station (or network node) may (in advance) promise / set / instruct the terminal about information about a specific sub-interval of the time interval in which a change in the system information is indicated / announced.

[0483] For example, in Proposal #14 or the present disclosure, the terminal may be a terminal in RRC_CONNECTED. For example, in Proposal #14 or the present disclosure, if an RRC connection is established between the RRC layer of the terminal and the RRC layer of the base station, the terminal may be in the RRC_CONNECTED state, and if not, the terminal may be in the RRC_IDLE state. For example, in the case of NR, the RRC_INACTIVE state is additionally defined, and a terminal in the RRC_INACTIVE state may maintain a connection with the core network while releasing the connection with the base station.

[0484] For example, in a non-terrestrial network according to an embodiment of the present disclosure, it may be assumed that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. For example, in Proposal #14 or the present disclosure, if the terminal operates in a half-duplex transmission mode, DL reception and UL transmission cannot be performed simultaneously, and if the DL reception time and the UL transmission time collide, the terminal may give priority to DL reception and / or UL transmission according to a DL / UL collision handling rule agreed upon / set in advance with the base station.

[0485] For example, in Proposal #14 or the present disclosure, in the uplink of a non-terrestrial network, a (common) TA (Timing Advance) that compensates for the time delay between a feeder link and a satellite and a (UE) TA that compensates for the time delay between the terminal and a satellite can be applied. For example, in Proposal #14 or the present disclosure, the (common) TA is a value that is mutually recognized through parameters and calculation formulas shared between the base station (or network) and the terminal, and the (UE) TA may be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network) end. For example, in Proposal #14 or the present disclosure, a TA (first TA) that the base station (or network) expects / predicts for the terminal and a TA (second TA) that the terminal actually applies may have different values.

[0486] For example, in a non-terrestrial network, DL / UL collision case(s) (hereinafter referred to as error cases) (e.g., collision between dynamically scheduled DL transmission resources and dynamically scheduled UL transmission resources and / or collision between semi-statically configured DL transmission resources and semi-statically configured UL transmission resources) that conventional base stations (or networks) are expected to avoid may occur relatively frequently, and DL / UL collision handling rules for a terminal operating in a half-duplex transmission mode for the above case(s) may need to be defined.

[0487] For example, in Proposal #14 or the present disclosure, a specific type of DL transmission can be predicted in terms of the time point and / or time interval during which reception of the DL transmission is expected. For example, in the case of receiving system information, the terminal can prioritize DL reception until the system information is acquired at least once. For example, in Proposal #14 or the present disclosure, after the terminal acquires the system information, the terminal can attempt to receive the system information only when the system information has changed. For example, the terminal can attempt to receive the system information within the time interval in which the base station (or network node) instructs / announces a change in the system information. For example, therefore, in the present disclosure, when the base station (or network node) and / or the terminal can perform DL / UL collision handling rules according to the half-duplex transmission mode in a non-terrestrial network, a method can be proposed in which the DL / UL collision handling rules are applied differently depending on whether the system information is acquired and / or whether the change in the system information falls within the instructed / announced time interval (or a specific sub-interval of the time interval). For example, reception of Type0 / 0A-PDCCH CSS may be prioritized over UL transmission within a Modification time period (or its sub-resources) in which SI modification is expected. For example, the UE may always prioritize reception of all or part of Type2-PDCCH CSS resources over UL. For example, in the above case, the UE may stably receive SI modification information from Type2-PDCCH CSS resources, and the priority of Type0 / 0A-PDCCH CSS may be maintained higher than UL transmission only within a Modification time period (or its sub-resources) in which SI modification is expected.For example, Type0 / 0A-PDCCH CSS may not have a high priority outside the Modification time period (or its sub-resources) where SI modification is expected (e.g., for a terminal that has already acquired system information).

[0488] For example, in Proposal #14 or the present disclosure, the terminal may be a terminal in RRC_CONNECTED. For example, in Proposal #14 or the present disclosure, if an RRC connection is established between the RRC layer of the terminal and the RRC layer of the base station, the terminal may be in the RRC_CONNECTED state, and if not, the terminal may be in the RRC_IDLE state. For example, in the case of NR, the RRC_INACTIVE state is additionally defined, and a terminal in the RRC_INACTIVE state may maintain a connection with the core network while releasing the connection with the base station.

[0489] For example, there may be a case where a (semi-statically configured) DL reception conflicts with a (semi-statically configured) UL transmission.

[0490] For example, for a Rel-19 HD-FDD (e)Redcap UE in RRC-Connected mode, in the case where a (semi-statically configured) DL reception collides with a (semi-statically configured) UL transmission, the collision handling with Type-0 / 0A / 1 / 2-PDCCH CSS in RRC-Connected mode may depend on the UE implementation whether to prioritize UL or DL ​​using the constraints of the following notes (e.g., Case 1).

[0491] For example, note: Terminals must adhere to the following existing procedures:

[0492] For example, an RRC-Connected terminal shall monitor SI change indications in every paging opportunity at least once per Modification time period to monitor paging on an active BWP if a common search space including pagingSearchSpace, searchSpaceSIB1 and searchSpaceOtherSystemInformation is provided to the terminal.

[0493] For example, for a Rel-19 HD-FDD (e)Redcap UE in RRC-Connected mode, in the case where a (semi-statically configured) DL reception collides with a (semi-statically configured) UL transmission, the default priority rule for the case where a (semi-statically configured) DL reception collides with a (semi-statically configured) UL transmission in RRC-Connected mode in the first case and in other cases (e.g., case 2) may be that the DL takes precedence.

[0494] For example, the network may indicate that UL is preferred over DL for Case 2 above.

[0495] For example, this can be signaled by RRC configuration.

[0496] FIG. 16 illustrates an example of a priority rule according to an embodiment of the present disclosure. The embodiment of FIG. 16 may be combined with various embodiments of the present disclosure.

[0497] For example, the priority rule may vary depending on whether the device has been provided with information about the common search space. For example, if the device has not been provided with information about the common search space, the second priority rule may apply.

[0498] For example, a second priority rule may be one that prioritizes DL reception over UL transmission. For example, the second priority rule may indicate that DL is prioritized. For example, in the second priority rule, the network may indicate that UL is prioritized over DL. This may be signaled, for example, by an RRC configuration. For example, the second priority rule may be different from the first priority rule. For example, the second priority rule may be a priority rule related to a case where (semi-statically configured) DL reception conflicts with (semi-statically configured) UL transmission.

[0499] For example, if a device is provided with information regarding a common search space, it may need to determine whether the device is in a change time interval. For example, the change time interval may include at least one subinterval. For example, at least one subinterval may be at least one paging opportunity.

[0500] For example, if a device is provided with information regarding a common search space, the priority rule may vary depending on whether the device is in a change time interval. For example, the change time interval may include at least one subinterval. For example, at least one subinterval may be at least one paging opportunity. For example, if the device is not in a change time interval, a second priority rule may apply.

[0501] For example, a second priority rule may be one that prioritizes DL reception over UL transmission. For example, the second priority rule may indicate that DL is prioritized. For example, in the second priority rule, the network may indicate that UL is prioritized over DL. This may be signaled, for example, by an RRC configuration. For example, the second priority rule may be different from the first priority rule. For example, the second priority rule may be a priority rule related to a case where (semi-statically configured) DL reception conflicts with (semi-statically configured) UL transmission.

[0502] For example, if the device is provided with information regarding the common search space, the first priority rule may apply if the device is in a change time interval.

[0503] For example, a first priority rule may be that if information related to a common search space is provided to the terminal, the terminal must monitor for SI change indications in all paging opportunities at least once per Modification period to monitor paging. For example, a first priority rule may be that an RRC-Connected terminal must monitor for SI change indications in all paging opportunities at least once per Modification period to monitor paging on an active BWP if the terminal is provided with a common search space containing pagingSearchSpace, searchSpaceSIB1, and searchSpaceOtherSystemInformation. For example, a first priority rule may be a priority rule related to a case where a (semi-statically configured) DL reception conflicts with a (semi-statically configured) UL transmission.

[0504] For example, according to the present disclosure (e.g., Proposal #14), a base station (or network node) and / or a terminal may allow application of DL / UL priority rules that give priority to a specific type of DL transmission within the expected / anticipated interval of the transmission, thereby ensuring reception of important DL transmissions while reducing the impact on UL transmissions.

[0505] For example, by prioritizing downlink reception for system information changes over scheduled uplink transmissions during a modification period, terminals operating in a non-terrestrial network (NTN) environment supporting half-duplex transmission can obtain critical system information changes reliably and without interruption. This ensures that even if downlink reception and uplink transmission collide, the terminal's ability to track and respond to system information changes is not impaired. As a result, communication continuity and overall link reliability can be improved even in NTN environments where essential system information changes are at high risk due to constraints such as satellite altitude, propagation delay, and half-duplex. For example, this collision handling mechanism allows terminals to maintain accurate network parameters while minimizing the need for additional signaling overhead or repeated transmissions, thereby further improving efficiency and user experience.

[0506] For example, the above proposed scheme #14 can be applied in combination with other proposed scheme(s) to the extent that the operations of the present disclosure do not conflict.

[0507] For example, proposal #15 can be proposed.

[0508] For example, according to Proposal #15, when a base station (or network node) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, a scheme may be proposed in which the base station (or network node) and / or the terminal applies the DL / UL collision handling rules differently for (a specific DL transmission and / or a specific UL transmission) depending on whether a specific timer (remaining) value and / or a specific time interval are included.

[0509] For example, in Proposal #15 or the present disclosure, the DL / UL conflict handling rules may include DL / UL priority rules.

[0510] For example, in Proposal #15 or the present disclosure, the starting point of the specific timer may be determined based on the reception point of specific (system) information and / or an instruction / configuration value of the base station (or network node). For example, the base station (or network node) may instruct / configure the terminal with the (start) reference point of the specific timer.

[0511] For example, in Proposal #15 or the present disclosure, the specific timer may mean an uplink synchronization validity related timer and / or a timer separate from T430 and / or T430.

[0512] For example, in Proposal #15 or the present disclosure, the specific timer may refer to a DRX and / or DTX operation related timer applied at a base station (or network node) and / or a terminal.

[0513] For example, in Proposal #15 or the present disclosure, the specific time interval may include a RAR window and / or a contention resolution window applied to a base station (or network node) and / or a terminal. For example, in a non-terrestrial network according to an embodiment of the present disclosure, it may be assumed that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. For example, in Proposal #15 or the present disclosure, when the terminal operates in a half-duplex transmission mode, DL reception and UL transmission cannot be performed simultaneously, and when the DL reception time and the UL transmission time collide, the terminal may give priority to DL reception and / or UL transmission according to a DL / UL collision handling rule prearranged / set with the base station.

[0514] For example, in Proposal #15 or the present disclosure, in the uplink of a non-terrestrial network, a terminal can apply a (common) TA (Timing Advance) that compensates for the time delay between a feeder link and a satellite, and a (UE) TA that compensates for the time delay between the terminal and a satellite. For example, in Proposal #15 or the present disclosure, the (common) TA is a value that is mutually recognized through parameters and calculation formulas shared between the base station (or network) and the terminal, and the (UE) TA may be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network) end. For example, in Proposal #15 or the present disclosure, a TA (first TA) that the base station (or network) expects / predicts for the terminal and a TA (second TA) that the terminal actually applies may have different values.

[0515] For example, in a non-terrestrial network, DL / UL collision case(s) (hereinafter referred to as error cases) (e.g., collision between dynamically scheduled DL transmission resources and dynamically scheduled UL transmission resources and / or collision between semi-statically configured DL transmission resources and semi-statically configured UL transmission resources) that conventional base stations (or networks) are expected to avoid may occur relatively frequently, and DL / UL collision handling rules for a terminal operating in a half-duplex transmission mode for the above case(s) may need to be defined.

[0516] For example, in Proposal #15 or the present disclosure, a specific type of DL transmission can be predicted for the time and / or time interval at which reception of the DL transmission is expected. For example, in the case of RAR (Msg2) and Contention Resolution information (Msg4), reception can be expected in the RAR Window and the Contention Resolution Window, respectively. For example, therefore, the terminal can prioritize a (specific) DL transmission related to Msg2 (e.g., Type1-PDCCH CSS) over an UL transmission within the RAR Window, and can prioritize a (specific) DL transmission related to Msg4 over an UL transmission within the Contention Resolution Window. For example, in the case of SIB19, reception of SIB19 by the terminal can be expected based on the value of the uplink synchronization validity timer (hereinafter referred to as T430). For example, if the T430 length is less than or equal to a certain threshold value, the terminal may be expected to attempt to receive SIB19, and if it is greater than or equal to the threshold value, the terminal may not be expected to attempt to receive SIB19. For example, therefore, if the T430 length is less than or equal to a certain threshold value, the terminal may prioritize SIB19-related (specific) DL transmission over UL transmission, and if it is greater than or equal to the certain threshold value, the terminal may not prioritize SIB19-related (specific) DL transmission over UL transmission. For example, in Proposal #15 or the present disclosure, the threshold value may be a value that the base station (or network node) sets to the terminal. For example, in Proposal #15 or the present disclosure, the T430 is configured to start when the conventional terminal receives SIB19, but the base station and the terminal may need to have the same awareness of the timer value in order to determine the DL / UL priority.For example, when utilizing the T430 timer value for the purpose of DL / UL priority determination, the DL / UL priority rule can be applied based on the remaining timer value compared to the (start) reference point of the timer instructed / set by the base station (or network node) to the terminal. For example, therefore, in the present disclosure, when the base station (or network node) and / or the terminal in a non-terrestrial network can perform the DL / UL collision handling rule according to the half-duplex transmission mode, a method can be proposed in which the base station (or network node) and / or the terminal applies the DL / UL collision handling rule differently for (a specific DL transmission and / or a specific UL transmission) depending on whether a specific timer (remaining) value and / or a specific time interval are included.

[0517] For example, according to the present disclosure (e.g., Proposal #15), a base station (or network node) and / or a terminal may allow application of DL / UL priority rules that give priority to a specific type of DL transmission within the interval in which the transmission is expected / expected, thereby ensuring reception of important DL transmissions while reducing the impact on UL transmissions.

[0518] For example, there is an advantage in that reception of emergency / critical information such as system information and / or PWS can be guaranteed even in situations where DL / UL collisions may occur.

[0519] For example, the above proposed scheme #15 can be applied in combination with other proposed scheme(s) to the extent that the operations of the present disclosure do not conflict.

[0520] For example, proposal #16 can be proposed.

[0521] For example, according to Proposal #16, when a base station (or network node) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, a scheme may be proposed in which the base station (or network node) and / or the terminal prioritizes reception of all and / or part of Type2-PDCCH CSS resources over UL transmission.

[0522] For example, in Proposal #16 or the present disclosure, the base station (or network node) may set / instruct (some) Type 2-PDCCH CSS resource information to which the high priority will be applied to the terminal.

[0523] For example, in a non-terrestrial network according to an embodiment of the present disclosure, it may be assumed that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. For example, in Proposal #16 or the present disclosure, if the terminal operates in a half-duplex transmission mode, DL reception and UL transmission cannot be performed simultaneously, and if the DL reception time and the UL transmission time collide, the terminal may give priority to DL reception and / or UL transmission according to a DL / UL collision handling rule agreed upon / set in advance with the base station.

[0524] For example, in the proposal #16 or the present disclosure, in the uplink of a non-terrestrial network, a terminal can apply a (common) TA (Timing Advance) that compensates for the time delay between a feeder link and a satellite, and a (UE) TA that compensates for the time delay between the terminal and a satellite. For example, in the proposal #16 or the present disclosure, the (common) TA is a value that is mutually recognized through parameters and calculation formulas shared between the base station (or network) and the terminal, and the (UE) TA may be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network) end. For example, in the proposal #16 or the present disclosure, a TA (first TA) that the base station (or network) expects / predicts for the terminal and a TA (second TA) that the terminal actually applies may have different values.

[0525] For example, in a non-terrestrial network, DL / UL collision case(s) (hereinafter referred to as error cases) (e.g., collision between dynamically scheduled DL transmission resources and dynamically scheduled UL transmission resources and / or collision between semi-statically configured DL transmission resources and semi-statically configured UL transmission resources) that conventional base stations (or networks) are expected to avoid may occur relatively frequently, and DL / UL collision handling rules for a terminal operating in a half-duplex transmission mode for the above case(s) may need to be defined.

[0526] For example, in Proposal #16 or the present disclosure, Type2-PDCCH CSS may be a resource for transmitting emergency and important information such as whether system information has changed and / or PWS (Public Warning System). For example, therefore, in the present disclosure, when a base station (or network node) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, a scheme may be proposed in which the base station (or network node) and / or the terminal prioritizes reception of all and / or part of Type2-PDCCH CSS resources over UL transmission. For example, in Proposal #16 or the present disclosure, the base station (or network node) may configure / instruct (part of) Type 2-PDCCH CSS resource information to which the terminal will apply the high priority.

[0527] For example, according to the present disclosure (e.g., Proposal #16), there is an advantage in that a base station (or network node) and / or a terminal can be guaranteed to receive emergency / critical information such as system information and / or PWS even in a situation where DL / UL collision may occur.

[0528] For example, the above proposed scheme #16 can be applied in combination with other proposed scheme(s) to the extent that the operations of the present disclosure do not conflict.

[0529] FIG. 17 illustrates a method for a device to perform wireless communication according to an embodiment of the present disclosure. The embodiment of FIG. 17 may be combined with various embodiments of the present disclosure.

[0530] Referring to FIG. 17, for example, in step S1710, the device may acquire information related to a common search space. For example, in step S1720, the device may monitor system information change information in a change time interval. For example, based on the fact that the device is provided with information related to the common search space and based on the fact that downlink reception related to the system information change information conflicts with uplink transmission in the change time interval, monitoring for the downlink reception may be prioritized in the change time interval.

[0531] For example, based on the information related to the common search space being provided to the device, and based on the downlink reception related to the system information change information colliding with the uplink transmission in the change time interval, the downlink reception may be given priority in the change time interval.

[0532] For example, the device may obtain information associated with the change time interval, which includes information associated with at least one paging opportunity. For example, based on the information associated with the common search space being provided to the device, and based on the downlink reception associated with the system information change information colliding with the uplink transmission in the change time interval, the downlink reception may be prioritized in the at least one paging opportunity in the change time interval.

[0533] For example, the device may establish a radio resource control connection with a base station. For example, based on the device being in a radio resource control connection associated with the establishment of the radio resource control connection, based on the information associated with the common search space being provided to the device, and based on the downlink reception associated with the system information change information colliding with the uplink transmission in the change time interval, the monitoring for the downlink reception may be prioritized in the change time interval.

[0534] For example, the priority rule for collision of the downlink reception and the uplink transmission related to the system information change information in the change time interval may be different from the priority rule for collision of the downlink reception and the uplink transmission outside the change time interval.

[0535] For example, based on the information related to the common search space being provided to the device, and based on the downlink reception and the uplink transmission related to the system information change information colliding in the change time interval, monitoring for the downlink reception may be prioritized at least once in the change time interval.

[0536] For example, the collision of the above downlink reception and uplink transmission may be a collision of a semi-statically set downlink reception and a semi-statically set uplink transmission.

[0537] For example, the device may be a half-duplex device for a non-terrestrial network. For example, based on the fact that the device is a half-duplex device for the non-terrestrial network, based on the information related to the common search space being provided to the device, and based on the change time interval associated with the system information change information in the change time interval, the monitoring for the downlink reception may be prioritized.

[0538] For example, based on the device being provided with information related to the common search space associated with the type 0-physical downlink control channel common search space, and based on the downlink reception associated with the system information change information colliding with the uplink transmission in the change time interval, the monitoring for the downlink reception may be prioritized in the change time interval.

[0539] For example, based on the fact that the device is provided with information related to the common search space associated with the Type 0A-physical downlink control channel common search space, and based on the fact that the downlink reception associated with the system information change information in the change time interval collides with the uplink transmission, the monitoring for the downlink reception in the change time interval may be prioritized.

[0540] For example, based on the fact that the device is provided with information related to the common search space associated with the type 2-physical downlink control channel common search space, and based on the fact that the downlink reception associated with the system information change information in the change time interval collides with the uplink transmission, the monitoring for the downlink reception in the change time interval may be prioritized.

[0541] For example, the uplink transmission may be prioritized based on a collision between the downlink reception and the reporting of information related to timing advances outside of the change time interval, or an uplink transmission associated with at least one of a trigger for a scheduling request for reporting information related to timing advances. For example, the reporting of information related to timing advances may include at least one of a reporting of information related to timing advances associated with radio resource control, a reporting of information related to timing advances associated with handover, or a reporting of information related to timing advances due to a trigger. For example, the reporting of information related to timing advances associated with radio resource control may include a reporting of information related to timing advances associated with at least one of radio resource control setup, radio resource control resumption, or radio resource control reconfiguration. For example, the reporting of information related to timing advances due to a trigger may include a reporting of information related to timing advances due to a trigger based on a collision of downlink and uplink.

[0542] For example, the device can report at least one of information related to a first timing advance and information for predicting a second timing advance. For example, the device can trigger reporting of a third timing advance based on at least one of information related to an actual timing advance and information for predicting the first timing advance and the second timing advance. For example, the device can determine collision of downlink and uplink based on at least one of information related to the third timing advance and information for predicting the first timing advance and the second timing advance.

[0543] The proposed method can be applied to devices according to various embodiments of the present disclosure. For example, first, the processor (102) of the device (100) can acquire information related to a common search space. For example, the processor (102) of the device (100) can monitor system information change information during a change time interval. For example, based on the fact that the device is provided with information related to the common search space and based on the fact that downlink reception related to the system information change information conflicts with uplink transmission during the change time interval, monitoring for the downlink reception can be prioritized during the change time interval.

[0544] According to one embodiment of the present disclosure, a device may be provided. For example, the device may include at least one transceiver; at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the device to: obtain information related to a common search space; and monitor system information change information during a change time interval. For example, based on the information related to the common search space being provided to the device and based on the fact that downlink reception related to the system information change information conflicts with uplink transmission during the change time interval, monitoring for the downlink reception may be prioritized during the change time interval.

[0545] According to one embodiment of the present disclosure, a processing device configured to control a device may be provided. For example, the processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the device to: acquire information related to a common search space; and monitor system information change information during a change time interval. For example, based on the information related to the common search space being provided to the device and based on the fact that downlink reception related to the system information change information conflicts with uplink transmission during the change time interval, monitoring for downlink reception may be prioritized during the change time interval.

[0546] According to one embodiment of the present disclosure, a non-transitory computer-readable storage medium having instructions recorded thereon may be provided. For example, the instructions, when executed, may cause a device to: obtain information related to a common search space; and monitor system information change information during a change time interval. For example, based on the information related to the common search space being provided to the device and based on the fact that downlink reception related to the system information change information conflicts with uplink transmission during the change time interval, monitoring for downlink reception may be prioritized during the change time interval.

[0547] FIG. 18 illustrates a method for a base station to perform wireless communication according to an embodiment of the present disclosure. The embodiment of FIG. 18 may be combined with various embodiments of the present disclosure.

[0548] Referring to FIG. 18, for example, in step S1810, the base station may transmit information related to a common search space. In step S1820, the base station may transmit system information change information in a change time interval. For example, based on the fact that information related to the common search space is provided to the device and based on the fact that downlink reception related to the system information change information conflicts with uplink transmission in the change time interval, monitoring for the downlink reception may be prioritized in the change time interval.

[0549] For example, based on the information related to the common search space being provided to the device, and based on the downlink reception related to the system information change information colliding with the uplink transmission in the change time interval, the downlink reception may be given priority in the change time interval.

[0550] For example, the base station may transmit information associated with the change time interval, including information associated with at least one paging opportunity. For example, based on the information associated with the common search space being provided to the device and based on the downlink reception associated with the system information change information conflicting with the uplink transmission in the change time interval, the downlink reception may be prioritized in the at least one paging opportunity in the change time interval.

[0551] For example, the base station may establish a radio resource control connection with the device. For example, based on the device being in a radio resource control connection associated with the establishment of the radio resource control connection, based on the information associated with the common search space being provided to the device, and based on the downlink reception associated with the system information change information colliding with the uplink transmission in the change time interval, the monitoring for the downlink reception may be prioritized in the change time interval.

[0552] For example, the priority rule for collision of the downlink reception and the uplink transmission related to the system information change information in the change time interval may be different from the priority rule for collision of the downlink reception and the uplink transmission outside the change time interval.

[0553] For example, based on the information related to the common search space being provided to the device, and based on the downlink reception and the uplink transmission related to the system information change information colliding in the change time interval, monitoring for the downlink reception may be prioritized at least once in the change time interval.

[0554] For example, the collision of the above downlink reception and uplink transmission may be a collision of a semi-statically set downlink reception and a semi-statically set uplink transmission.

[0555] For example, the device may be a half-duplex device for a non-terrestrial network. For example, based on the fact that the device is a half-duplex device for the non-terrestrial network, based on the information related to the common search space being provided to the device, and based on the change time interval associated with the system information change information in the change time interval, the monitoring for the downlink reception may be prioritized.

[0556] For example, based on the device being provided with information related to the common search space associated with the type 0-physical downlink control channel common search space, and based on the downlink reception associated with the system information change information colliding with the uplink transmission in the change time interval, the monitoring for the downlink reception may be prioritized in the change time interval.

[0557] For example, based on the fact that the device is provided with information related to the common search space associated with the Type 0A-physical downlink control channel common search space, and based on the fact that the downlink reception associated with the system information change information in the change time interval collides with the uplink transmission, the monitoring for the downlink reception in the change time interval may be prioritized.

[0558] For example, based on the fact that the device is provided with information related to the common search space associated with the type 2-physical downlink control channel common search space, and based on the fact that the downlink reception associated with the system information change information in the change time interval collides with the uplink transmission, the monitoring for the downlink reception in the change time interval may be prioritized.

[0559] For example, the uplink transmission may be prioritized based on a collision between the downlink reception and the reporting of information related to timing advances outside of the change time interval, or an uplink transmission associated with at least one of a trigger for a scheduling request for reporting information related to timing advances. For example, the reporting of information related to timing advances may include at least one of a reporting of information related to timing advances associated with radio resource control, a reporting of information related to timing advances associated with handover, or a reporting of information related to timing advances due to a trigger. For example, the reporting of information related to timing advances associated with radio resource control may include a reporting of information related to timing advances associated with at least one of radio resource control setup, radio resource control resumption, or radio resource control reconfiguration. For example, the reporting of information related to timing advances due to a trigger may include a reporting of information related to timing advances due to a trigger based on a collision of downlink and uplink.

[0560] For example, the base station can receive a report of at least one of information related to a first timing advance and information for predicting a second timing advance. For example, based on at least one of a third timing advance related to an actual timing advance and information for predicting the first timing advance and the second timing advance, reporting of the third timing advance can be triggered. For example, based on at least one of the third timing advance related to the actual timing advance and information for predicting the first timing advance and the second timing advance, collision of downlink and uplink can be determined.

[0561] The proposed method can be applied to devices according to various embodiments of the present disclosure. For example, first, the processor (202) of the base station (200) can control the transceiver (206) to transmit information related to a common search space. For example, and then, the processor (202) of the base station (200) can control the transceiver (206) to transmit system information change information during a change time interval. For example, based on the information related to the common search space being provided to the device and based on the fact that downlink reception related to the system information change information conflicts with uplink transmission during the change time interval, monitoring for the downlink reception can be prioritized during the change time interval.

[0562] According to one embodiment of the present disclosure, a base station may be provided. For example, the base station may include at least one transceiver; at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the base station to: transmit information related to a common search space; and transmit system information change information during a change time interval. For example, based on the information related to the common search space being provided to a device and based on the fact that downlink reception related to the system information change information conflicts with uplink transmission during the change time interval, monitoring for the downlink reception may be prioritized during the change time interval.

[0563] According to one embodiment of the present disclosure, a processing device configured to control a base station may be provided. For example, the processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the base station to: transmit information related to a common search space; and transmit system information change information during a change time interval. For example, based on the information related to the common search space being provided to the device and based on the fact that downlink reception related to the system information change information conflicts with uplink transmission during the change time interval, monitoring for the downlink reception may be prioritized during the change time interval.

[0564] According to one embodiment of the present disclosure, a non-transitory computer-readable storage medium having instructions recorded thereon may be provided. For example, the instructions, when executed, may cause a base station to: transmit information related to a common search space; and transmit system information change information during a change time interval. For example, based on the information related to the common search space being provided to the device and based on the fact that downlink reception related to the system information change information conflicts with uplink transmission during the change time interval, monitoring for the downlink reception may be prioritized during the change time interval.

[0565] The various embodiments of the present disclosure may be combined with each other.

[0566] The above proposed method can be applied to the device described below. First, the processor (202) of the receiving terminal can set at least one partial bandwidth (e.g., BWP; bandwidth part). Then, the processor (202) of the receiving terminal can control the transceiver (206) of the receiving terminal to receive a physical channel related to terminal-to-terminal communication (e.g., SL communication) and / or a reference signal related to terminal-to-terminal communication (e.g., SL communication) from the transmitting terminal on at least one partial bandwidth (e.g., BWP).

[0567] Below, a description is given of devices to which various embodiments of the present disclosure can be applied.

[0568] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in this document may be applied to various fields requiring wireless communication / connectivity (e.g., 5G) between devices.

[0569] Hereinafter, more specific examples will be provided with reference to the drawings. In the drawings / descriptions below, the same drawing reference numerals may represent identical or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise described.

[0570] FIG. 19 illustrates a communication system (1) according to one embodiment of the present disclosure. The embodiment of FIG. 19 can be combined with various embodiments of the present disclosure.

[0571] Referring to FIG. 19, a communication system (1) to which various embodiments of the present disclosure are applied includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone) and / or an Aerial Vehicle (AV) (e.g., an Advanced Air Mobility (AAM)). The XR device may include an Augmented Reality (AR) / Virtual Reality (VR) / Mixed Reality (MR) device, and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, etc. The portable device may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), a computer (e.g., a laptop, etc.), etc. The home appliance may include a TV, a refrigerator, a washing machine, etc. The IoT device may include a sensor, a smart meter, etc. For example, a base station and a network may also be implemented as a wireless device, and a specific wireless device (200a) may operate as a base station / network node to other wireless devices.

[0572] Here, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present specification may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present specification may perform communication based on LTE-M technology. At this time, 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 can be implemented 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 above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present specification can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create personal area networks (PAN) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0573] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). Artificial Intelligence (AI) technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, etc. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). In addition, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0574] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base stations (200), and base stations (200) / base stations (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication (150a), sidelink communication (150b) (or, D2D communication), and communication between base stations (150c) (e.g., relay, IAB (Integrated Access Backhaul). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present disclosure.

[0575] FIG. 20 illustrates a wireless device according to an embodiment of the present disclosure. The embodiment of FIG. 20 may be combined with various embodiments of the present disclosure.

[0576] Referring to FIG. 20, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals via various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} can correspond to {the wireless device (100x), the base station (200)} and / or {the wireless device (100x), the wireless device (100x)} of FIG. 19.

[0577] A 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) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). Furthermore, the processor (102) may receive a wireless signal including second information / signal via the transceiver (106), and then store information obtained from signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present disclosure, a wireless device may also mean a communication modem / circuit / chip.

[0578] A 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) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). In addition, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present disclosure, a wireless device may also mean a communication modem / circuit / chip.

[0579] Hereinafter, the hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement 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 Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed herein, and provide the signals 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 obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0580] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software configured to perform 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 operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0581] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0582] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of this document, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled 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, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein, via one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0583] FIG. 21 illustrates a signal processing circuit for a transmission signal according to an embodiment of the present disclosure. The embodiment of FIG. 21 can be combined with various embodiments of the present disclosure.

[0584] Referring to FIG. 21, the signal processing circuit (1000) may include a scrambler (1010), a modulator (1020), a layer mapper (1030), a precoder (1040), a resource mapper (1050), and a signal generator (1060). Although not limited thereto, the operations / functions of FIG. 21 may be performed in the processor (102, 202) and / or the transceiver (106, 206) of FIG. 20. The hardware elements of FIG. 21 may be implemented in the processor (102, 202) and / or the transceiver (106, 206) of FIG. 20. For example, blocks 1010 to 1060 may be implemented in the processor (102, 202) of FIG. 20. Additionally, blocks 1010 to 1050 may be implemented in the processor (102, 202) of FIG. 20, and block 1060 may be implemented in the transceiver (106, 206) of FIG. 20.

[0585] The codeword can be converted into a wireless signal through the signal processing circuit (1000) of FIG. 21. Here, the codeword is an encoded bit sequence of an information block. The information block may include a transport block (e.g., an UL-SCH transport block, a DL-SCH transport block). The wireless signal may be transmitted through various physical channels (e.g., a PUSCH or a PDSCH).

[0586] Specifically, the codeword can be converted into a bit sequence scrambled by a scrambler (1010). The scramble sequence used for scrambling is generated based on an initialization value, and the initialization value may include ID information of the wireless device, etc. The scrambled bit sequence can be modulated into a modulation symbol sequence by a modulator (1020). The modulation method may include pi / 2-BPSK (pi / 2-Binary Phase Shift Keying), m-PSK (m-Phase Shift Keying), m-QAM (m-Quadrature Amplitude Modulation), etc. The complex modulation symbol sequence can be mapped to one or more transmission layers by a layer mapper (1030). The modulation symbols of each transmission layer can be mapped to the corresponding antenna port(s) by a precoder (1040) (precoding). The output z of the precoder (1040) can be obtained by multiplying the output y of the layer mapper (1030) by a precoding matrix W of N*M. Here, N is the number of antenna ports, and M is the number of transmission layers. Here, the precoder (1040) can perform precoding after performing transform precoding (e.g., DFT transform) on complex modulation symbols. In addition, the precoder (1040) can perform precoding without performing transform precoding.

[0587] The resource mapper (1050) can map modulation symbols of each antenna port to time-frequency resources. The time-frequency resources can include multiple symbols (e.g., CP-OFDMA symbols, DFT-s-OFDMA symbols) in the time domain and multiple subcarriers in the frequency domain. The signal generator (1060) generates a wireless signal from the mapped modulation symbols, and the generated wireless signal can be transmitted to another device through each antenna. To this end, the signal generator (1060) can include an Inverse Fast Fourier Transform (IFFT) module, a Cyclic Prefix (CP) inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, etc.

[0588] The signal processing process for receiving signals in a wireless device can be configured in reverse order of the signal processing process (1010 to 1060) of FIG. 21. For example, a wireless device (e.g., 100, 200 of FIG. 20) can receive wireless signals from the outside through an antenna port / transceiver. The received wireless signals can be converted into baseband signals through a signal restorer. For this purpose, the signal restorer can include a frequency downlink converter, an analog-to-digital converter (ADC), a CP remover, and a fast Fourier transform (FFT) module. Thereafter, the baseband signal can be restored to a codeword through a resource demapper process, a postcoding process, a demodulation process, and a descrambling process. The codewords can be restored to the original information blocks through decoding. Accordingly, a signal processing circuit (not shown) for a received signal may include a signal restorer, a resource de-mapper, a postcoder, a demodulator, a de-scrambler, and a decoder.

[0589] Figure 22 illustrates a wireless device according to an embodiment of the present disclosure. The wireless device may be implemented in various forms depending on the use case / service (see Figure 19). The embodiment of Figure 22 may be combined with various embodiments of the present disclosure.

[0590] Referring to FIG. 22, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 20 and may be composed of various elements, components, units / units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and an additional element (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 20. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 20. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and the additional elements (140) and controls the overall operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit (130). In addition, the control unit (120) may transmit information stored in the memory unit (130) to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit (130).

[0591] The additional element (140) may be configured in various ways depending on the type of the wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 19, 100a), a vehicle (Fig. 19, 100b-1, 100b-2), an XR device (Fig. 19, 100c), a portable device (Fig. 19, 100d), a home appliance (Fig. 19, 100e), an IoT device (Fig. 19, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, an AI server / device (Fig. 19, 400), a base station (Fig. 19, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0592] In FIG. 22, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be interconnected entirely via a wired interface, or at least some may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and the first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit / part, and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed of one or more processor sets. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of a random access memory (RAM), a dynamic RAM (DRAM), a read only memory (ROM), a flash memory, a volatile memory, a non-volatile memory, and / or a combination thereof.

[0593] Below, the implementation example of Fig. 22 is described in more detail with reference to the drawings.

[0594] FIG. 23 illustrates a mobile device according to an embodiment of the present disclosure. The mobile device may include a smartphone, a smart pad, a wearable device (e.g., a smartwatch, smartglasses), or a portable computer (e.g., a laptop, etc.). The mobile device may be referred to as a Mobile Station (MS), a User Terminal (UT), a Mobile Subscriber Station (MSS), a Subscriber Station (SS), an Advanced Mobile Station (AMS), or a Wireless Terminal (WT). The embodiment of FIG. 23 may be combined with various embodiments of the present disclosure.

[0595] Referring to FIG. 23, the portable device (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a memory unit (130), a power supply unit (140a), an interface unit (140b), and an input / output unit (140c). The antenna unit (108) may be configured as a part of the communication unit (110). Blocks 110 to 130 / 140a to 140c correspond to blocks 110 to 130 / 140 of FIG. 22, respectively.

[0596] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with other wireless devices and base stations. The control unit (120) can control components of the mobile device (100) to perform various operations. The control unit (120) can include an AP (Application Processor). The memory unit (130) can store data / parameters / programs / codes / commands required for operating the mobile device (100). In addition, the memory unit (130) can store input / output data / information, etc. The power supply unit (140a) supplies power to the mobile device (100) and can include a wired / wireless charging circuit, a battery, etc. The interface unit (140b) can support connection between the mobile device (100) and other external devices. The interface unit (140b) can include various ports (e.g., audio input / output ports, video input / output ports) for connection with external devices. The input / output unit (140c) can input or output video information / signals, audio information / signals, data, and / or information input from a user. The input / output unit (140c) may include a camera, a microphone, a user input unit, a display unit (140d), a speaker, and / or a haptic module.

[0597] For example, in the case of data communication, the input / output unit (140c) obtains information / signals (e.g., touch, text, voice, image, video) input by the user, and the obtained information / signals can be stored in the memory unit (130). The communication unit (110) converts the information / signals stored in the memory into wireless signals, and can directly transmit the converted wireless signals to other wireless devices or to a base station. In addition, the communication unit (110) can receive wireless signals from other wireless devices or base stations, and then restore the received wireless signals to the original information / signals. The restored information / signals can be stored in the memory unit (130) and then output in various forms (e.g., text, voice, image, video, haptic) through the input / output unit (140c).

[0598] Figure 24 illustrates a vehicle or autonomous vehicle according to one embodiment of the present disclosure. The vehicle or autonomous vehicle may be implemented as a mobile robot, a car, a train, a manned or unmanned aerial vehicle (AV), a ship, or the like. The embodiment of Figure 24 may be combined with various embodiments of the present disclosure.

[0599] Referring to FIG. 24, a vehicle or autonomous vehicle (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a driving unit (140a), a power supply unit (140b), a sensor unit (140c), and an autonomous driving unit (140d). The antenna unit (108) may be configured as a part of the communication unit (110). Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 of FIG. 22, respectively.

[0600] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with external devices such as other vehicles, base stations (e.g., base stations, road side units, etc.), and servers. The control unit (120) can control elements of the vehicle or autonomous vehicle (100) to perform various operations. The control unit (120) can include an ECU (Electronic Control Unit). The drive unit (140a) can drive the vehicle or autonomous vehicle (100) on the ground. The drive unit (140a) can include an engine, a motor, a power train, wheels, brakes, a steering device, etc. The power supply unit (140b) supplies power to the vehicle or autonomous vehicle (100) and can include a wired / wireless charging circuit, a battery, etc. The sensor unit (140c) can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit (140c) may include an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an incline sensor, a weight detection sensor, a heading sensor, a position module, a vehicle forward / backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illuminance sensor, a pedal position sensor, etc. The autonomous driving unit (140d) may implement a technology for maintaining a driving lane, a technology for automatically controlling speed such as adaptive cruise control, a technology for automatically driving along a set path, a technology for automatically setting a path and driving when a destination is set, etc.

[0601] For example, the communication unit (110) can receive map data, traffic information data, etc. from an external server. The autonomous driving unit (140d) can generate an autonomous driving route and driving plan based on the acquired data. The control unit (120) can control the drive unit (140a) so that the vehicle or autonomous vehicle (100) moves along the autonomous driving route according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit (110) can irregularly / periodically acquire the latest traffic information data from an external server and can acquire surrounding traffic information data from surrounding vehicles. In addition, during autonomous driving, the sensor unit (140c) can acquire vehicle status and surrounding environment information. The autonomous driving unit (140d) can update the autonomous driving route and driving plan based on newly acquired data / information. The communication unit (110) can transmit information regarding the vehicle location, autonomous driving route, driving plan, etc. to the external server. External servers can predict traffic information data in advance using AI technology or other technologies based on information collected from vehicles or autonomous vehicles, and provide the predicted traffic information data to the vehicles or autonomous vehicles.

[0602] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined and implemented as a device, and the technical features of the device claims of this specification may be combined and implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a method.

Claims

1. In the method, A step of obtaining information related to a common search space; and A step of monitoring system information change information in a change time interval; including; A method in which monitoring for the downlink reception is given priority in the change time interval based on the information related to the common search space being provided to the device and based on the downlink reception related to the system information change information colliding with the uplink transmission in the change time interval.

2. In paragraph 1, A method wherein the downlink reception is given priority in the change time interval based on the information related to the common search space being provided to the device and based on the downlink reception related to the system information change information colliding with the uplink transmission in the change time interval.

3. In the first paragraph, the step of monitoring the system information change information in the change time section is, A step of obtaining information related to at least one paging opportunity associated with the above change time interval; further comprising: A method in which the downlink reception is given priority in the at least one paging opportunity in the change time interval, based on the information related to the common search space being provided to the device, and based on the downlink reception related to the system information change information colliding with the uplink transmission in the change time interval.

4. In paragraph 1, A step of establishing a base station and a radio resource control connection; including: A method wherein the monitoring for the downlink reception is given priority in the change time interval based on the fact that the device is in a radio resource control connection associated with the establishment of the radio resource control connection, based on the fact that the device is provided with the information associated with the common search space, and based on the fact that the downlink reception associated with the system information change information in the change time interval conflicts with the uplink transmission.

5. In paragraph 1, A method in which the priority rule for collision of the downlink reception and the uplink transmission related to the system information change information in the above change time interval is different from the priority rule for collision of the downlink reception and the uplink transmission outside the above change time interval.

6. In paragraph 1, A method wherein monitoring for the downlink reception is prioritized at least once in the change time interval based on the information related to the common search space being provided to the device and based on the downlink reception and the uplink transmission related to the system information change information colliding in the change time interval.

7. In paragraph 1, A method wherein the collision of the above downlink reception and uplink transmission is a collision of a semi-statically set downlink reception and a semi-statically set uplink transmission.

8. In paragraph 1, The above device is a half-duplex device for non-terrestrial networks, and A method wherein the monitoring for the downlink reception is given priority in the change time interval related to the system information change information, based on the fact that the device is the half-duplex device for the non-terrestrial network, based on the information related to the common search space being provided to the device, and based on the fact that the information related to the common search space is provided to the device, and based on the fact that the information related to the system information change information is provided in the change time interval.

9. In paragraph 1, A method wherein the monitoring for the downlink reception is given priority in the change time interval based on the information related to the common search space associated with the type 0-physical downlink control channel common search space being provided to the device, and based on the downlink reception associated with the system information change information colliding with the uplink transmission in the change time interval.

10. In paragraph 1, A method wherein the monitoring for the downlink reception is given priority in the change time interval based on the information related to the common search space associated with the type 0A-physical downlink control channel common search space being provided to the device, and based on the downlink reception associated with the system information change information colliding with the uplink transmission in the change time interval.

11. In paragraph 1, A method wherein the monitoring for the downlink reception is given priority in the change time interval based on the information related to the common search space associated with the type 2-physical downlink control channel common search space being provided to the device, and based on the downlink reception associated with the system information change information colliding with the uplink transmission in the change time interval.

12. In paragraph 5, Based on a conflict between the uplink transmission related to at least one of the reporting of information related to the downlink reception and timing advance or the trigger of the scheduling request for reporting of information related to the timing advance outside the above change time interval, the uplink transmission is given priority, The reporting of information related to the timing advance includes at least one of reporting of information related to timing advance related to radio resource control, reporting of information related to timing advance related to handover, or reporting of information related to timing advance due to a trigger. The reporting of the information related to the timing advance associated with the radio resource control includes reporting of information related to the timing advance associated with at least one of radio resource control setup, radio resource control resumption, or radio resource control reset, and A method for reporting information related to timing advance due to the above trigger, wherein the reporting includes reporting information related to timing advance due to a trigger based on collision of downlink and uplink.

13. In paragraph 1, A step of reporting at least one of information related to a first timing advance and information for predicting a second timing advance; and A step of triggering reporting of a third timing advance based on at least one of information for predicting a third timing advance related to an actual timing advance and the first timing advance and the second timing advance; or A method further comprising: a step of determining a collision of downlink and uplink based on at least one of information for predicting the third timing advance and the first timing advance and the second timing advance related to the actual timing advance.

14. In the device, At least one transmitter / receiver; at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said device causes: Obtain information related to a common search space; and Monitor system information change information during the change time interval. A device, wherein monitoring for the downlink reception is given priority in the change time interval based on the information related to the common search space being provided to the device and based on the downlink reception related to the system information change information colliding with the uplink transmission in the change time interval.

15. In a processing device set to control a device, at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said device causes: Obtain information related to a common search space; and Monitor system information change information during the change time interval. A processing device, wherein monitoring for the downlink reception is given priority in the change time interval based on the information related to the common search space being provided to the device and based on the downlink reception related to the system information change information colliding with the uplink transmission in the change time interval.

16. A non-transitory computer-readable storage medium that records commands, The above commands, when executed, cause the device to: Obtain information related to a common search space; and Monitor system information change information during the change time interval. A non-transitory computer-readable storage medium, wherein monitoring for the downlink reception is given priority in the change time interval based on the information related to the common search space being provided to the device and based on the downlink reception related to the system information change information colliding with the uplink transmission in the change time interval.

17. In the method, a step of transmitting information related to a common search space; and A step of transmitting system information change information in a change time interval; including; A method in which monitoring for the downlink reception is given priority in the change time interval based on the information related to the common search space being provided to the device and based on the downlink reception related to the system information change information colliding with the uplink transmission in the change time interval.

18. At the base station, At least one transmitter / receiver; at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said base station: Transmitting information related to a common search space; and Transmit system information change information during the change time interval. A base station, wherein monitoring for the downlink reception is given priority in the change time interval based on the information related to the common search space being provided to the device and based on the downlink reception related to the system information change information colliding with the uplink transmission in the change time interval.

19. In a processing device set to control a base station, at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said base station: Transmitting information related to a common search space; and Transmit system information change information during the change time interval. A processing device, wherein monitoring for the downlink reception is given priority in the change time interval based on the information related to the common search space being provided to the device and based on the downlink reception related to the system information change information colliding with the uplink transmission in the change time interval.

20. A non-transitory computer-readable storage medium that records commands, The above commands, when executed, cause the base station to: Transmitting information related to a common search space; and Transmit system information change information during the change time interval. A non-transitory computer-readable storage medium, wherein monitoring for the downlink reception is given priority in the change time interval based on the information related to the common search space being provided to the device and based on the downlink reception related to the system information change information colliding with the uplink transmission in the change time interval.