Method and apparatus for carrying out communication in wireless communication system

Abstract

Provided are a method by which an apparatus carries out wireless communication and an apparatus supporting same. The method may comprise the steps of: a first apparatus acquiring information related to a semi-statically configured downlink resource; the first apparatus acquiring information related to a semi-statically configured uplink resource; and the first apparatus triggering a timing advance report. For example, the timing advance report may be triggered on the basis that downlink reception based on the information related to the semi-statically configured downlink resource collides with uplink transmission based on the information related to the semi-statically configured uplink resource.

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] According to one embodiment of the present disclosure, a method may be provided. For example, the method may include: a step of a first device obtaining information related to a semi-statically configured downlink resource; a step of the first device obtaining information related to a semi-statically configured uplink resource; and a step of the first device triggering a timing advance report. For example, the timing advance report may be triggered based on a collision between a downlink reception based on the information related to the semi-statically configured downlink resource and an uplink transmission based on the information related to the semi-statically configured uplink resource.

[0006] According to one embodiment of the present disclosure, a first device may be provided. For example, the first 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, when executed by the at least one processor, may cause the first device to: obtain information related to a semi-statically configured downlink resource; obtain information related to a semi-statically configured uplink resource; and trigger a timing advance report. For example, the timing advance report may be triggered based on a collision between a downlink reception based on information related to the semi-statically configured downlink resource and an uplink transmission based on information related to the semi-statically configured uplink resource.

[0007] According to one embodiment of the present disclosure, a processing device (configured to control a first 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 first device to: obtain information related to a semi-statically configured downlink resource; obtain information related to a semi-statically configured uplink resource; and trigger a timing advance report. For example, the timing advance report may be triggered based on a collision between a downlink reception based on information related to the semi-statically configured downlink resource and an uplink transmission based on information related to the semi-statically configured uplink resource.

[0008] 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 first device to: obtain information related to a semi-statically configured downlink resource; obtain information related to a semi-statically configured uplink resource; and trigger a timing advance report. For example, the timing advance report may be triggered based on a collision between a downlink reception based on the information related to the semi-statically configured downlink resource and an uplink transmission based on the information related to the semi-statically configured uplink resource.

[0009] According to one embodiment of the present disclosure, a method may be provided. For example, the method may include: a step of a second device transmitting, to a first device, information related to a semi-statically configured downlink resource; a step of the second device transmitting, to the first device, information related to a semi-statically configured uplink resource; and a step of the second device receiving, from the first device, a timing advance report. For example, the timing advance report may be triggered based on a collision between a downlink transmission based on information related to the semi-statically configured downlink resource and an uplink reception based on information related to the semi-statically configured uplink resource.

[0010] According to one embodiment of the present disclosure, a second device may be provided. For example, the second 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 second device to: transmit, to a first device, information related to a semi-statically configured downlink resource; transmit, to the first device, information related to a semi-statically configured uplink resource; and receive, from the first device, a timing advance report. For example, the timing advance report may be triggered based on a collision between a downlink transmission based on information related to the semi-statically configured downlink resource and an uplink reception based on information related to the semi-statically configured uplink resource.

[0011] According to one embodiment of the present disclosure, a processing device (configured to control a second 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 second device to: transmit, to a first device, information related to a semi-statically configured downlink resource; transmit, to the first device, information related to a semi-statically configured uplink resource; and receive, from the first device, a timing advance report. For example, the timing advance report may be triggered based on a collision between a downlink transmission based on information related to the semi-statically configured downlink resource and an uplink reception based on information related to the semi-statically configured uplink resource.

[0012] 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 second device to: transmit, to a first device, information related to a semi-statically configured downlink resource; transmit, to the first device, information related to a semi-statically configured uplink resource; and receive, from the first device, a timing advance report. For example, the timing advance report may be triggered based on a collision between a downlink transmission based on the information related to the semi-statically configured downlink resource and an uplink reception based on the information related to the semi-statically configured uplink resource.

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

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

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

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

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

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

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

[0020] FIGS. 8A and 8B illustrate a non-terrestrial network scenario according to one embodiment of the present disclosure.

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

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

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

[0024] FIG. 12 shows examples of K_offset and K_mac according to one embodiment of the present disclosure.

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

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

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

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

[0029] FIG. 17 illustrates an example of a relationship between reported TA and actual TA according to one embodiment of the present disclosure.

[0030] FIG. 18 illustrates an example of guard time and TA according to one embodiment of the present disclosure.

[0031] FIG. 19 illustrates a procedure for performing communication based on uplink timing advance and uplink downlink settings according to one embodiment of the present disclosure.

[0032] FIG. 20 illustrates a method for a first device to perform wireless communication according to one embodiment of the present disclosure.

[0033] FIG. 21 illustrates a method for a second device to perform wireless communication according to one embodiment of the present disclosure.

[0034] Fig. 22 shows a communication system (1) according to one embodiment of the present disclosure.

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

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

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

[0038] FIG. 26 illustrates a mobile device 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 (e.g., 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, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[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., the channel used, whether it is 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 before 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 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted. 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 forwarding of user data, header compression, and ciphering. For example, the functions of the PDCP layer in the control plane may include 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 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[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 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[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 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted. 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 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[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] - Blockchain

[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 various 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, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[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] Figures 8a and 8b illustrate a non-terrestrial network scenario according to an embodiment of the present disclosure. The embodiments of Figures 8a and 8b may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0106] Figure 8a illustrates a non-terrestrial network scenario based on a transparent payload, and Figure 8b illustrates a non-terrestrial network scenario based on a regenerative payload. For example, a non-terrestrial network may typically include the following elements:

[0107] - One or more satellite gateways connecting non-terrestrial networks to public data networks.

[0108] - Feeder link or wireless link between the satellite gateway and the satellite (or UAS platform).

[0109] - Service link or wireless link between user equipment and satellite (or UAS platform)

[0110] - A satellite (or UAS platform) capable of implementing transparent or regenerative (including onboard processing) payloads. For example, a satellite (or UAS platform) may generate multiple beams over a given service area, typically bounded by a field of view. For example, the beam footprint may be typically elliptical in shape. For example, the field of view of the satellite (or UAS platform) may vary depending on the onboard antenna diagram and minimum elevation angle. For example, for transparent payloads, radio frequency filtering, frequency conversion, and amplification may be performed. Therefore, the repetitive waveform signal in the payload may remain unchanged. For example, for regenerative payloads, radio frequency filtering, frequency conversion, and amplification, as well as demodulation / decoding, switching and / or routing, and coding / modulation may be performed. This may effectively be equivalent to onboarding all base station functions onto the satellite (or UAS platform).

[0111] - Optionally, inter-satellite link (ISL)

[0112] - User equipment can be serviced by satellites (or UAS platforms) within the target service area.

[0113] FIG. 9 illustrates a procedure for downlink 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, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

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

[0115] For example, in step S920, 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.

[0116] 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.

[0117] 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.

[0118] 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.

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

[0120] 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.

[0121] 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'.

[0122] 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.

[0123] 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.

[0124] 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}.

[0125] 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.

[0126] 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.

[0127] 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.

[0128] FIG. 10 illustrates a procedure for uplink transmission and reception according to an embodiment of the present disclosure. The embodiment of FIG. 10 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0129] Referring to FIG. 10, for example, in step S1010, 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.

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

[0131] 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.

[0132] 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}.

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

[0134] 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.

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

[0136] 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.

[0137] 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).

[0138] 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).

[0139] FIG. 11 illustrates an example of an NTN according to an embodiment of the present disclosure. The embodiment of FIG. 11 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0140] Referring to Fig. 11, 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).

[0141] 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.

[0142] 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).

[0143] 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).

[0144] 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.

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

[0146] FIG. 12 illustrates examples of K_offset and K_mac according to one embodiment of the present disclosure. The embodiment of FIG. 12 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0147] Referring to FIG. 12, 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 the RTT of an uplink time synchronization reference point (RP). For example, K_offset can be the sum of the service link RTT and the common TA (if indicated). For example, K_mac can be an offset value indicating the 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.

[0148] FIG. 13 illustrates examples of UE-specific TAs and common TAs according to one embodiment of the present disclosure. The embodiment of FIG. 13 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0149] Referring to FIG. 13, 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. 14 and the description related to FIG. 14.

[0150] FIG. 14 illustrates an example of an uplink-downlink timing relationship according to an embodiment of the present disclosure. The embodiment of FIG. 14 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0151] Referring to Figure 14, 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

[0152] - 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;

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

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

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

[0156] 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.

[0157] 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).

[0158] FIG. 15 illustrates an example of TA mismatch within a beam / cell, according to an embodiment of the present disclosure. The embodiment of FIG. 15 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0159] Referring to FIG. 15, 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.

[0160] 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.

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

[0162] 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.

[0163] FIG. 16 illustrates an HD collision in an NTN according to an embodiment of the present disclosure. The embodiment of FIG. 16 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0164] Referring to Figure 16, 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.

[0165] 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 16, where the blank space may indicate that scheduling is not being performed.

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

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

[0168] 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.

[0169] 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.

[0170] 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.

[0171] 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.

[0172] 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,

[0173] - 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.

[0174] 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)

[0175] 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.

[0176] for example, silver may be the PUSCH preparation time for UE processing capability 1 [see TS 38.214] assuming and It may 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.

[0177] 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.

[0178] 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,

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

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

[0181] 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,

[0182] - 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.

[0183] - 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.

[0184] 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,

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

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

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

[0188] 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,

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

[0190] - 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).

[0191] 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.

[0192] In a non-terrestrial network (NTN) using half-duplex transmission mode, a UE cannot perform uplink (UL) transmission and downlink (DL) reception simultaneously. If the UL transmission timing and DL reception timing conflict, the UE can prioritize one operation over the other according to the conflict handling rules agreed upon in advance with the network. In a non-terrestrial network scenario, two types of Timing Advance (TA) are used: a common TA (shared between the network and the UE) that compensates for the time delay between the feeder link and the satellite, and a UE-specific TA (autonomously adjusted by the UE and opaque to the network) that compensates for the time delay between the UE and the satellite. A mismatch between the TA expected by the network and the TA applied by the UE can lead to different perceptions of the timing of conflicts between uplink and downlink resources, which can lead to unintended collisions or inefficient resource usage.

[0193] Since the propagation delay of the service link in NTN is calculated by the terminal and is unknown to the base station, the base station cannot accurately determine the terminal's actual TA. The base station can roughly estimate the terminal's TA based on the TA reported by the terminal.

[0194] FIG. 17 illustrates an example of a relationship between a reported TA and an actual TA, according to an embodiment of the present disclosure. The embodiment of FIG. 17 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0195] Referring to Figure 17, the reported TA and the actual TA may differ. For example, a guard time may be defined. For example, the time difference between the actual TA of a terminal and the reported TA may be within the guard time. As illustrated in Figure 17, the propagation delay of the service link in the NTN is calculated by the terminal, and the base station is unaware of this, so the base station cannot accurately determine the terminal's actual TA.

[0196] [Proposal #01] 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, the base station (or network) and / or the terminal can determine whether a DL / UL collision occurs by one or more of the following methods based on GT (Guard Time) and / or UL TA (Uplink Time Advance) assumptions for DL ​​transmission resources and UL transmission resources.

[0197] (1) For example, the assumption that the base station and terminal are independent UL TAs can be applied.

[0198] (1) A. Option 1

[0199] (1) A. i. A base station can determine a DL / UL collision if there is a GT between a DL transmission resource and an UL transmission resource (assuming the first TA is applied).

[0200] (1) A. ii. A terminal can determine a DL / UL collision if it is located within the GT between a DL transmission resource and a UL transmission resource (assuming the second TA is applied).

[0201] (1) B. Option 2

[0202] (1) B. i. The base station can determine a DL / UL collision if there is a GT between the DL transmission resource and the UL transmission resource (assuming the first TA is applied).

[0203] (1) B. ii. The terminal may determine a DL / UL collision if there is overlap (in the time axis) between DL transmission resources and UL transmission resources (assuming application of the second TA).

[0204] (2) The same UL TA assumption can be applied to the base station and terminal.

[0205] (2) A. Option 1

[0206] (2) A. i. The base station can determine a DL / UL collision if there is a GT between the DL transmission resource and the UL transmission resource (assuming the 3rd TA is applied).

[0207] (2) A. ii. A terminal can determine a DL / UL collision if it is located within the GT between a DL transmission resource and a UL transmission resource (assuming the 3rd TA is applied).

[0208] (2) B. Option 2

[0209] (2) B. i. The base station can determine a DL / UL collision if there is a GT between the DL transmission resource and the UL transmission resource (assuming the 3rd TA is applied).

[0210] (2) B. ii. The terminal may determine a DL / UL collision if there is overlap (in the time axis) between DL transmission resources and UL transmission resources (assuming application of the 3rd TA).

[0211] Here, for example, the base station (or network) can set / instruct the terminal as to which of the above methods(s) to use to determine whether there is a collision between DL / UL.

[0212] Here, for example, the first TA may be a value that the base station (or network) expects / expects as the UL TA at the terminal end.

[0213] Here, for example, the second TA may mean a UL TA measured / calculated / derived by the terminal.

[0214] Here, for example, the third TA may refer to a UL TA that can be equally calculated / derived by the base station (or network) and the terminal based on a (preliminary) agreement / definition / configuration between the base station (or network) and the terminal. For example, the third TA may be a (public) TA or a TA that the terminal (most recently) reported to the base station (or network).

[0215] Here, for example, the GT may be a value that the base station (or network) (preliminarily) agrees / defines with the terminal or sets / instructs to the terminal.

[0216] Here, for example, the GT may be set / indicated per cell and / or per (satellite) beam footprint and / or per terminal. For example, the GT information may be provided as system information such as SIB (System Information Block) 19.

[0217] Here, for example, the terminal can perform a GT and / or UL TA assumption-based DL / UL collision determination process for all UL transmission resources to which the OCC (Orthogonal Cover Code) is applied, for resources to which the OCC is applied. For example, the GT can be applied to the start and / or end points of all UL transmission resources to which the OCC is applied, and resources that collide with the entire UL transmission section including the GT can be searched for.

[0218] For example, in a non-terrestrial network according to one embodiment of the present disclosure, assume that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, for example, 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 can 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.

[0219] Here, for example, in the uplink of a 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. Here, for example, the (common) TA can be 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 can be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). Here, for example, 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 can have different values.

[0220] Here, for example, due to reasons such as application of the above (UE) TA, there may be cases where the mutual recognition of DL / UL conflicting resources between the base station (or network) and the terminal in the 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.

[0221] Therefore, in the present disclosure, 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 (or network) and / or the terminal can determine whether there is a DL / UL collision based on a GT (Guard Time) and / or UL TA (Uplink Time Advance) assumption for a DL transmission resource and an UL transmission resource. For example, the base station can determine a DL / UL collision if the DL transmission resource and the UL transmission resource (assuming the third TA is applied) are located within the GT, and the terminal can determine a DL / UL collision if the DL transmission resource and the UL transmission resource (assuming the third TA is applied) are located within the GT. Here, for example, the third TA may mean a UL TA that the base station (or network) and the terminal can equally calculate / derive based on a (pre-) agreement / definition / setting between the base station (or network) and the terminal. For example, the third TA may be a (public) TA or a TA that the terminal has (most recently) reported to the base station (or network). Here, for example, the GT may be a value that the base station (or network) has (preliminarily) agreed upon / defined with the terminal or set / instructed to the terminal. For example, the GT may be set to include the minimum / maximum TA range that the terminal's (UE) TA may have.

[0222] FIG. 18 illustrates an example of a guard time and TA according to an embodiment of the present disclosure. The embodiment of FIG. 18 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0223] Referring to FIG. 18, for example, [UL - Reported TA] may precede [DL], and [UL - Reported TA] may not overlap with [DL]. For example, [UL - Reported TA] may not overlap with [DL], but the time difference between [UL - Reported TA] and [DL] may be within the guard time. For example, if the time difference between [UL - Reported TA] and [DL] is within the guard time, it may be determined as a DL / UL collision. For example, the terminal may determine a DL / UL collision if the time difference between [UL - Reported TA] and [DL] is within the guard time. For example, the base station may determine a DL / UL collision if the time difference between [UL - Reported TA] and [DL] is within the guard time.

[0224] For example, [DL] may precede [UL - Reported TA], and [DL] and [UL - Reported TA] may not overlap. For example, [DL] may not overlap [UL - Reported TA], but the time difference between [DL] and [UL - Reported TA] may be within the guard time. For example, if the time difference between [DL] and [UL - Reported TA] is within the guard time, it may be determined as a DL / UL collision. For example, the terminal may determine a DL / UL collision if the time difference between [DL] and [UL - Reported TA] is within the guard time. For example, the base station may determine a DL / UL collision if the time difference between [DL] and [UL - Reported TA] is within the guard time.

[0225] The present disclosure effectively resolves UL / DL collision issues and timing mismatches that may arise due to differences in perception of Timing Advance (TA) between a base station and a UE in a non-terrestrial network environment. The present disclosure effectively resolves timing mismatches and UL / DL resource collision issues that arise due to differences in perception of Timing Advance (TA) between a UE and a network in a non-terrestrial network environment. Specifically, by utilizing a guard time (GT) and mutually recognized TAs (e.g., reported TAs), the present disclosure enables both the network and the UE to consistently determine collisions between uplink and downlink resources. This consistency ensures synchronized transmission and reception timing, thereby preventing unexpected resource collisions and significantly improving resource efficiency and system reliability.

[0226] According to the proposed method of the present disclosure, even when the TA values ​​recognized between a base station (or network) and a terminal in a non-terrestrial network are different, there is an advantage in that the DL / UL collision determination and / or DL / UL collision handling rules are performed in the same manner to align the (expected) transmission and reception times between them. Here, for example, if the proposed method is not supported, a problem may arise where the base station (or network) and / or the terminal performs transmission and / or reception at unexpected times, resulting in unnecessary consumption of transmission resources.

[0227] The above [Proposal #01] can be applied in combination with other proposed methods(s) to the extent that the proposed actions do not conflict.

[0228] [Proposal #02] 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, the base station (or network) and / or the terminal can select DL transmission resource(s) and / or UL transmission resource(s) (hereinafter, a first resource set) to determine whether there is a DL / UL collision and / or to apply the DL / UL collision handling rules by one or more of the following methods.

[0229] (1) A first resource set can be determined based on UL transmission resources (hereinafter referred to as resource A).

[0230] (1) A. Option 1

[0231] (1) A. i. DL transmission resource(s) (dynamically scheduled and / or semi-statically set) and / or UL transmission resource(s) (dynamically scheduled and / or semi-statically set) up to a point in time prior to T_PROC,2 relative to the transmission time of resource A.

[0232] (1) B. Option 2

[0233] (1) B. i. Up to a point in time prior to T_PROC,2 compared to the transmission time of resource A, among the (dynamically scheduled and / or semi-statically configured) DL transmission resource(s) and / or the (dynamically scheduled and / or semi-statically configured) UL transmission resource(s), resource A and / or transmission resource(s) that can (potentially) collide with resource A.

[0234] (1) C. Option 3

[0235] (1) C. i. Up to a point in time T_PROC,2 prior to the transmission time of resource A, among the (dynamically scheduled and / or semi-statically set) DL transmission resource(s) and / or the (dynamically scheduled and / or semi-statically set) UL transmission resource(s), resource A and / or transmission resource(s) that can (potentially) collide with resource A may be selected as the initial second resource set.

[0236] (1) C. ii. If there are transmission resource(s) that can (potentially) collide with the second resource set, the second resource set may be updated to include the transmission resource(s).

[0237] (1) C. iii. The second resource set of the last version that is no longer updated can be utilized as the first resource set.

[0238] (2) A first resource set can be determined based on dynamically scheduled resources (hereinafter referred to as resource B).

[0239] (2) A. Option 1

[0240] (2) A. i. DL transmission resource(s) (dynamically scheduled and / or semi-statically set) and / or UL transmission resource(s) (dynamically scheduled and / or semi-statically set) until the time when resource B is scheduled.

[0241] (2) B. Option 2

[0242] (2) B. i. Up to the time when resource B is scheduled, among the DL transmission resource(s) (dynamically scheduled and / or semi-statically set) and / or UL transmission resource(s) (dynamically scheduled and / or semi-statically set), resource B and transmission resource(s) that can (potentially) collide with resource B.

[0243] (2) C. Option 3

[0244] (2) C. i. Until the time when resource B is scheduled, among the DL transmission resource(s) (dynamically scheduled and / or semi-statically set) and / or the UL transmission resource(s) (dynamically scheduled and / or semi-statically set), resource B and / or transmission resource(s) that can (potentially) collide with resource B may be selected as the initial second resource set.

[0245] (2) C. ii. If there are transmission resource(s) that can (potentially) collide with the second resource set, the second resource set may be updated to include the transmission resource(s).

[0246] (2) C. iii. The second resource set of the last version that is no longer updated can be utilized as the first resource set.

[0247] Here, for example, the base station (or network) can set and / or instruct the terminal which of the above method(s) to perform.

[0248] Here, for example, the above T_PROC,2 may mean the processing time required by the terminal for uplink transmission.

[0249] Here, for example, the terminal can perform the first method starting from the UL transmission resource whose transmission time point is earlier on the time axis.

[0250] Here, for example, the DL transmission resource(s) and / or UL transmission resource(s) by which the base station (or network) and / or terminal determines whether there is a DL / UL collision may be limited to the transmission resource(s) within a given (specific) time interval based on the reference point in time.

[0251] Here, for example, among the above-mentioned semi-statically set transmission resources, it is possible to determine whether there is a DL / UL collision and / or apply DL / UL collision handling rules to activated transmission resources.

[0252] For example, in a non-terrestrial network according to one embodiment of the present disclosure, assume that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, for example, 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 can 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.

[0253] Here, for example, in the uplink of a 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. Here, for example, the (common) TA can be 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 can be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). Here, for example, 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 can have different values.

[0254] Here, for example, in order to resolve the mismatch in perception between the base station (or network) and the terminal for the TA, the (potential) DL / UL collision resource(s) can be determined by considering the variable range of the (UE) TA. For example, the base station (or network) and / or the terminal can determine that, when assuming a specific UL TA, DL transmission resources and UL transmission resources existing within a certain GT (Guard Time) can potentially collide. Here, for example, the base station (or network) and / or the terminal can pre-select DL transmission resource(s) and / or UL transmission resource(s) for determining whether there is a DL / UL collision, and then determine whether there is a DL / UL collision based on the UL TA assumption and / or GT for the (candidate) DL / UL transmission resource(s).

[0255] Therefore, in the present disclosure, 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, a method is proposed in which the base station (or network) and / or the terminal selects DL transmission resource(s) and / or UL transmission resource(s) (hereinafter, referred to as a first resource set) for determining whether there is a DL / UL collision by one or more of the following methods. For example, the first resource set may be determined based on a (specific) UL transmission resource. For example, the terminal may designate all and / or part of the (dynamically scheduled and / or semi-statically set) DL transmission resource(s) and / or the (dynamically scheduled and / or semi-statically set) UL transmission resource(s) as the first resource set up to a time point prior to T_PROC,2 relative to the transmission time point of the (specific) UL transmission resource, and determine whether there is a DL / UL collision between transmission resource(s) within the first resource set. Alternatively, for example, the first resource set may be determined based on dynamically scheduled resources. For example, the terminal may determine all and / or part of the (dynamically scheduled and / or semi-statically configured) DL transmission resource(s) and / or the (dynamically scheduled and / or semi-statically configured) UL transmission resource(s) as the first resource set until the time at which the transmission resources are scheduled, and determine whether there is a DL / UL collision between the transmission resource(s) within the first resource set. Here, for example, based on a (specific) transmission resource, the reference resource and / or transmission resource(s) that may (potentially) collide with the reference resource may be determined as the (initial) first resource set. Here, for example, if there are transmission resource(s) that may (potentially) collide with the first resource set, the terminal may update the first resource set to include the corresponding transmission resource(s).

[0256] According to the proposed method of 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, they can equally recognize whether there is a DL / UL collision and / or the target transmission resource(s) to which the DL / UL collision handling rules are to be applied. Through this, there is an advantage in that the base station (or network) and / or the terminal identically performs the DL / UL collision determination and / or the DL / UL collision handling rules, thereby synchronizing the (expected) transmission and reception times therebetween. Here, for example, if the proposed method is not supported, a problem may arise in which the base station (or network) and / or the terminal performs transmission and / or reception at unexpected times, resulting in unnecessary consumption of transmission resources.

[0257] The above [Proposal #02] can be applied in combination with other proposed methods(s) to the extent that the proposed actions do not conflict.

[0258] [Proposal #03] 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, and when there are multiple DL transmission resource(s) and / or UL transmission resource(s) to which the base station (or network) and / or the terminal determines whether there is a DL / UL collision and / or applies the DL / UL collision handling rules, the base station (or network) and / or the terminal can determine whether there is a DL / UL collision and / or perform the DL / UL collision handling rules by one or more of the following methods.

[0259] (1) Determining whether there is a DL / UL conflict based on priority and / or order information and / or executing DL / UL conflict handling rules.

[0260] (1) A. For example, the terminal may determine whether there is a DL / UL collision and / or perform DL / UL collision handling rules for each transmission resource in descending order of priority and / or order information for the DL / UL transmission resource(s).

[0261] (2) Determining whether there is a DL / UL collision based on the time axis order of transmission resources and / or executing DL / UL collision handling rules.

[0262] (2) A. For example, the terminal can determine whether there is a DL / UL collision and / or perform DL / UL collision handling rules for each transmission resource in the order of transmission time (on the time axis) for the DL / UL transmission resource(s).

[0263] (3) Determining whether there is a DL / UL conflict based on the scheduling order and / or executing DL / UL conflict handling rules.

[0264] (3) A. For example, the terminal may determine whether there is a DL / UL collision and / or perform DL / UL collision handling rules for each transmission resource according to the scheduling order and / or its reverse order for the DL / UL transmission resource(s).

[0265] (4) Determine whether there is a sequence-based DL / UL conflict between dynamic scheduling resources and quasi-statically configured resources and / or perform DL / UL conflict handling rules.

[0266] (4) A. For example, the terminal may determine whether there is a DL / UL collision and / or perform DL / UL collision handling rules for each transmission resource according to the order of the dynamically scheduled resources and the next semi-statically set resources and / or its reverse order for the DL / UL transmission resource(s).

[0267] Here, for example, the base station (or network) can set and / or instruct the terminal which of the above method(s) to perform.

[0268] Here, for example, the priority and / or order information may be (in advance) agreed upon between the base station (or network) and the terminal, or the base station (or network) may set / instruct the terminal.

[0269] Here, for example, the priority and / or order information may include priority and / or order information that prioritizes (dynamically scheduled and / or semi-statically configured) DL transmission resources over (dynamically scheduled and / or semi-statically configured) UL transmission resources and / or priority and / or order information that prioritizes (dynamically scheduled and / or semi-statically configured) UL transmission resources over (dynamically scheduled and / or semi-statically configured) DL transmission resources.

[0270] Here, for example, when the terminal determines whether there is a DL / UL collision and / or performs a DL / UL collision handling rule for a (specific) transmission resource (hereinafter, a first resource), the terminal can determine whether there is a DL / UL collision between (potential) transmission resources (hereinafter, a second resource) that may collide based on the first resource, and then, when a collision occurs, perform a terminal operation according to the DL / UL collision handling rule.

[0271] Here, for example, when the terminal applies the DL / UL collision handling rules according to the above order, DL / UL transmission resources omitted from reception / transmission in the previous process may not be considered as valid transmission resources in the subsequent process. For example, the invalid transmission resource(s) may be excluded from the DL / UL collision determination target.

[0272] Here, for example, the proposed scheme can be applied to multiple (dynamically scheduled and / or semi-statically configured) DL transmission resource(s) and / or multiple (dynamically scheduled and / or semi-statically configured) UL transmission resource(s).

[0273] Here, for example, the case where there are multiple DL transmission resource(s) and / or UL transmission resource(s) to which DL / UL collision handling rules are applied may include a case where there are multiple combination(s) of DL transmission resources and UL transmission resources determined to be DL / UL collisions, and at least one DL transmission resource and / or UL transmission resource is shared between different combinations.

[0274] Here, for example, the method for determining whether there is a DL / UL collision and / or executing the DL / UL collision handling rule may be applied differently depending on the combination of target DL transmission resource(s) and / or UL transmission resource(s). For example, the method applied to the combination (dynamically scheduled first DL transmission resource, semi-statically configured second UL transmission resource, dynamically scheduled third DL transmission resource) may be different from the method applied to the combination (semi-statically configured first DL transmission resource, dynamically scheduled second UL transmission resource, semi-statically configured third DL transmission resource).

[0275] Here, for example, among the above-mentioned semi-statically set transmission resources, it is possible to determine whether there is a DL / UL collision and / or apply DL / UL collision handling rules to activated transmission resources.

[0276] For example, in a non-terrestrial network according to one embodiment of the present disclosure, assume that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, for example, 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 can 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.

[0277] Here, for example, in the uplink of a 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. Here, for example, the (common) TA can be 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 can be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). Here, for example, 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 can have different values.

[0278] Here, for example, in order to resolve the mismatch in perception between the base station (or network) and the terminal for the TA, the (potential) DL / UL collision resource(s) can be determined by considering the variable range of the (UE) TA. For example, the base station (or network) and / or the terminal can determine that, assuming a specific UL TA, DL transmission resources and UL transmission resources existing within a certain GT (Guard Time) can potentially collide. Here, for example, when the GT-based DL / UL collision determination is performed, since the collision time is given as a time interval proportional to the GT, there may be a case where there are multiple DL transmission resource(s) and / or UL transmission resource(s) to which the DL / UL collision determination and / or the DL / UL collision handling rule must be applied within the collision interval. Here, for example, if the order of applying the DL / UL collision handling rule between the DL / UL transmission resource(s) is different between the base station (or network) and the terminal, correct transmission and reception may not be performed. For example, suppose there are a first transmission resource, a second transmission resource, and a third transmission resource in order on the time axis. Here, for example, suppose that the first transmission resource collides with the second transmission resource, and the second transmission resource collides with the third transmission resource, and that they have higher transmission priorities in that order. Here, for example, if there is no restriction on the order in which the collision handling rules are applied between the base station (or network) and the terminal, the base station is expected to apply the collision handling rules starting from the first transmission resource, while the terminal may apply the collision handling rules starting from the second transmission resource. Here, for example, the base station (or network) may omit the second transmission resource after applying the collision handling rules, and transmit / receive only the first and third transmission resources. Here, for example, the terminal may omit the third transmission resource after applying the collision handling rules, and then omit the second transmission resource again, and then transmit / receive only the first transmission resource.Therefore, if the order of resolving DL / UL collision handling rules is not determined, there may be cases where the transmission resource(s) expected by the base station (or network) and the terminal are different, as in the example above.

[0279] 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, when there are multiple DL transmission resource(s) and / or UL transmission resource(s) to which the base station (or network) and / or the terminal determines whether there is a DL / UL collision and / or applies the DL / UL collision handling rules, a method is proposed in which the base station (or network) and / or the terminal determines whether there is a DL / UL collision and / or performs the DL / UL collision handling rules for each transmission resource according to a (pre-)promised and / or set / indicated order between each other. For example, the terminal can determine whether there is a DL / UL collision and / or perform the DL / UL collision handling rules based on priority and / or order information. For example, the terminal can determine whether there is a DL / UL collision and / or perform the DL / UL collision handling rules based on a time axis order of transmission resources. For example, the terminal can determine whether there is a DL / UL collision and / or perform the DL / UL collision handling rules based on a scheduling order. For example, a terminal may determine whether there is a DL / UL conflict and / or perform DL / UL conflict handling rules based on the order between dynamically scheduled resources and semi-statically configured resources. Here, for example, one or more of the above methods may be applied in combination.

[0280] According to the proposed method of 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, the application results of the DL / UL collision determination rules can be recognized identically. This has the advantage of allowing the base station (or network) and / or the terminal to synchronize their (expected) transmission and reception times. Here, for example, if the proposed method is not supported, a problem may arise where the base station (or network) and / or the terminal performs transmission and / or reception at unexpected times, resulting in unnecessary consumption of transmission resources.

[0281] The above [Proposal #03] can be applied in combination with other proposed methods(s) to the extent that the proposed actions do not conflict.

[0282] [Proposal #04] 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, the base station (or network) and / or the terminal can differentiate stages based on resource types, and sequentially perform DL / UL collision determination and / or DL / UL collision handling rules according to the stages.

[0283] For example, the terminal may perform step-by-step DL / UL collision determination and / or DL / UL collision handling rules as follows.

[0284] (1) Step 1: Determine whether there is a DL / UL conflict related to a semi-statically set resource and / or apply DL / UL conflict handling rules.

[0285] (1) A. For example, it is possible to determine whether there is a (DL / UL) collision between (quasi-statically set) DL transmission resources and (quasi-statically set) UL transmission resources and / or apply (DL / UL) collision handling rules.

[0286] (2) Step 2: Determine whether there is a DL / UL conflict related to dynamically scheduled resources and / or apply DL / UL conflict handling rules.

[0287] (2) A. For example, it is possible to determine whether there is a (DL / UL) collision between (dynamically scheduled) DL transmission resources and (quasi-statically set and / or dynamically scheduled) UL transmission resources and / or to apply (DL / UL) collision handling rules.

[0288] (2) B. For example, it is possible to determine whether there is a (DL / UL) collision between (dynamically scheduled) UL transmission resources and (quasi-statically set and / or dynamically scheduled) DL transmission resources and / or apply (DL / UL) collision handling rules.

[0289] Here, for example, the resource type may include whether it is a (semi-statically set) resource and / or a (dynamically scheduled) resource.

[0290] Here, for example, the terminal may determine a conflicting (potential) resource based on the resource whenever dynamic scheduling is detected for a dynamically scheduled transmission resource and apply DL / UL conflict handling rules. Here, for example, when searching for a conflicting (potential) resource, the terminal may search for previously set and / or scheduled resources in comparison to the detected dynamic scheduling.

[0291] For example, in a non-terrestrial network according to one embodiment of the present disclosure, assume that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, for example, 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 can 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.

[0292] Here, for example, in the uplink of a 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. Here, for example, the (common) TA can be 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 can be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). Here, for example, 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 can have different values.

[0293] Here, for example, due to reasons such as application of the (UE) TA, there may be cases where the base station (or network) in the non-terrestrial network does not know whether there is an actual DL / UL collision at the terminal end. Here, for example, the base station (or network) and / or the terminal may inevitably encounter case(s) that were not expected in the conventional DL / UL collision handling rules, for example, a collision between a semi-statically configured DL resource and a semi-statically configured UL resource and / or a collision between a dynamically scheduled DL resource and a dynamically scheduled UL resource. Therefore, DL / UL collision handling rules for the above cases may also need to be defined. Here, for example, the base station (or network) and the terminal must perform DL / UL collision handling rules considering both the semi-statically configured DL transmission resource(s) and / or the semi-statically configured UL transmission resource(s) and / or the dynamically scheduled DL transmission resource(s) and / or the dynamically scheduled DL transmission resource(s), which may result in a very large number of cases to consider and may become complex.

[0294] Therefore, in the present disclosure, when a base station (or network) 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 is proposed in which the base station (or network) and / or the terminal divides the steps based on the resource type, and sequentially performs DL / UL collision determination and / or DL / UL collision handling rules according to the steps. In the first step, the base station (or network) and / or the terminal can perform DL / UL collision determination and / or DL / UL collision handling rules related to semi-statically configured resources. For example, the (DL / UL) collision determination and / or (DL / UL) collision handling rules can be applied between (semi-statically configured) DL transmission resources and (semi-statically configured) UL transmission resources. Thereafter, in the second step, the base station (or network) and / or the terminal can perform DL / UL collision determination and / or DL / UL collision handling rules related to dynamically scheduled resources in the second step process. For example, it is possible to determine whether there is a (DL / UL) collision between (dynamically scheduled) DL transmission resources and (quasi-statically configured and / or dynamically scheduled) UL transmission resources and / or to apply (DL / UL) collision handling rules. For example, it is possible to determine whether there is a (DL / UL) collision between (dynamically scheduled) UL transmission resources and (quasi-statically configured and / or dynamically scheduled) DL transmission resources and / or to apply (DL / UL) collision handling rules.

[0295] According to the proposed method of 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, the operation process of the base station (or network) and / or the terminal can be simplified and the complexity can be expected to be reduced.

[0296] The above [Proposal #04] can be applied in combination with other proposed methods as long as the proposed actions do not conflict.

[0297] [Proposal #05] 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 (potential) UL transmission interval (hereinafter referred to as a first UL transmission interval) that may collide with a (specific) DL transmission resource is derived, and the terminal can perform one or more of the following actions for UL transmission (e.g., PUSCH and / or PUCCH) to which DM-RS Bundling and / or TDW (Time Domain Window) are applied.

[0298] (1) Exclude the first UL transmission section from the (actual) TDW section.

[0299] (1) A. For example, a terminal may regard a (potential) UL transmission interval as an Event interval and may not guarantee phase continuity and / or power consistency of the signal within the Event interval.

[0300] (2) Omission of UL transmission within the first UL transmission section

[0301] (2) A. For example, the terminal may omit PUSCH and / or PUCCH transmission within the (potential) UL transmission interval.

[0302] Here, for example, the base station (or network) can set and / or instruct the terminal to perform which of the above operation(s).

[0303] Here, for example, a (potential) UL transmission interval that may collide with the (specific) DL transmission resource can be derived based on GT (Guard Time) and / or UL TA (Uplink Time Advance) assumptions. For example, a base station (or network) and / or a terminal, when assuming the application of a specific TA, can determine a UL transmission interval located within the GT and the (specific) DL transmission resource as a (potential) UL transmission interval that may collide. Here, for example, the GT can be a value that the base station (or network) (in advance) agrees / defines with the terminal or sets / instructs to the terminal.

[0304] Here, for example, the DM-RS Bundling may mean an operation of performing channel estimation by utilizing DM-RS resource(s) between UL repeated transmissions.

[0305] Here, for example, the TDW may mean a (time) interval in which the terminal guarantees phase continuity and / or power consistency of the 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.

[0306] For example, in a non-terrestrial network according to one embodiment of the present disclosure, assume that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, for example, 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 can 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.

[0307] Here, for example, in the uplink of a 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. Here, for example, the (common) TA can be 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 can be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). Here, for example, 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 can have different values.

[0308] Here, for example, the terminal can guarantee the phase continuity and / or power consistency of the signal for a specific UL transmission that supports DM-RS Bundling and / or TDW configuration. Here, for example, the terminal may no longer guarantee the phase continuity and / or power consistency when receiving any DL within the UL transmission interval. Here, for example, in the non-terrestrial network, the base station may not be able to accurately determine the DL reception time within the UL transmission interval of the terminal due to the application of the (UE) TA, etc., and thus it may be difficult to determine the time when the phase continuity and / or power consistency characteristics within the UL transmission interval are broken. This may cause difficulties for the base station in selecting a DM-RS Bundling target and may degrade uplink reception performance.

[0309] 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 is proposed in which a (potential) UL transmission section that may collide with a (specific) DL transmission resource is derived, and the terminal performs one or more of the following actions for a UL transmission (e.g., PUSCH and / or PUCCH) to which DM-RS Bundling and / or TDW (Time Domain Window) are applied. For example, the terminal may exclude the (potential) UL transmission section from the (actual) TDW section and / or omit UL transmission within the (potential) UL transmission section. For example, the base station (or network) and / or the terminal may determine a UL transmission section that is within a GT (Guard Time) and a specific DL transmission resource as a (potential) UL transmission section that may collide. Thereafter, the terminal may actually omit UL transmission for the (potential) UL transmission section. Alternatively, the terminal may omit transmission of only the UL resources where an actual collision has occurred based on the UL TA derived by the terminal, but may ensure that the base station (or network) and / or the terminal do not expect phase continuity and / or power consistency within the (potential) UL transmission interval. For example, the base station may exclude an actual UL transmission within the (potential) UL transmission interval from being a target for DM-RS bundling even if it is detected.

[0310] According to the proposed method of 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, it can help the base station (or network) and / or the terminal to equally understand the section to which DM-RS Bundling is applicable and / or the (actual) TDW section and / or the section in which the phase continuity and / or power consistency of the UL signal are guaranteed. This has the effect of preventing UL reception performance degradation by preventing the case in advance where the base station applies DM-RS Bundling to an incorrect section.

[0311] The above [Proposal #05] can be applied in combination with other proposed methods as long as the proposed actions do not conflict.

[0312] [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 a half-duplex transmission mode, in case of a collision between multiple DL transmission resource(s) (hereinafter, a first resource group) and multiple UL transmission resource(s) (hereinafter, a second resource group), the DL / UL collision handling rules can be performed based on a resource (or its priority value) with the highest priority in the first resource group and a resource (or its priority value) with the highest priority in the second resource group.

[0313] Here, for example, the base station (or network) can set and / or instruct the terminal whether to perform the above operation.

[0314] Here, for example, there may be one or more transmission resources within the first and / or second resource groups.

[0315] Here, for example, the DL / UL collision handling rule may mean a rule for the operation of a base station (or network) and / or terminal when a DL reception time and a UL transmission time overlap and / or collide on the time axis.

[0316] For example, in a non-terrestrial network according to one embodiment of the present disclosure, assume that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, for example, 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 can 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.

[0317] Here, for example, in the uplink of a 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. Here, for example, the (common) TA can be 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 can be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). Here, for example, 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 can have different values.

[0318] Here, for example, due to the above TA or other reasons, a single DL transmission resource may collide with two UL transmission resource(s), or a single UL transmission resource may collide with two DL transmission resource(s). Here, for example, the terminal may regard the multiple collision situation as a mixed situation of DL / UL one-to-one collisions, and sequentially apply DL / UL collision handling rules. However, when multiple transmission resource(s) collide as described above, applying the handling rules for conventional DL / UL one-to-one collisions may increase the implementation complexity of the terminal. 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, in case of a collision between a plurality of DL transmission resource(s) (hereinafter, a first resource group) and a plurality of UL transmission resource(s) (hereinafter, a second resource group), a method is proposed to perform DL / UL collision handling rules based on a resource (or a corresponding priority value) having the highest priority within the first resource group and a resource (or a corresponding priority value) having the highest priority within the second resource group. For example, let us assume that one semi-statically configured DL transmission resource (the first DL resource) collides with two UL transmission resource(s), one of the two UL transmission resources being a dynamically scheduled UL transmission resource (the first UL resource) and the other being a semi-statically configured UL transmission resource (the second UL resource). Here, for example, the dynamically scheduled UL transmission resource may have a higher priority than the semi-statically configured UL transmission resource. Therefore, DL / UL collision handling rules can be applied between the first DL resource and the first UL resource.For example, according to the conventional DL / UL conflict handling rules, since dynamically scheduled resources have a higher priority than semi-statically configured resources, reception of the first DL resource may be omitted and transmission for the UL transmission resource group (i.e., the first and second UL resources) may be prioritized. According to the proposed method of the present disclosure, in a situation where a terminal must perform conflict handling rules between a plurality of DL resources and a plurality of UL resources, there is an advantage in simplifying the DL / UL conflict handling rules of the terminal by applying the DL / UL conflict handling rules based on the representative resource (with a higher priority) within each resource group.

[0319] The above [Proposal #06] can be applied in combination with other proposed methods(s) to the extent that the proposed actions do not conflict.

[0320] [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, one or more of the following DL transmission resource(s) can be determined as a colliding DL transmission resource(s) based on a (specific) UL transmission resource (hereinafter referred to as a first resource).

[0321] (1) DL transmission resources that are dynamically scheduled and have time resources that overlap with the first resource.

[0322] (1) A. Here, for example, the control signal (e.g., DCI) that scheduled the DL transmission resource may be transmitted and / or detected T_PROC,2 hours prior to the start point of the first resource. Otherwise, the DL transmission resource may not be determined as a conflicting resource.

[0323] (2) DL transmission resources that are set semi-statically and have time resources that overlap with the first resource.

[0324] (2) A. Here, for example, the control signal (e.g., DCI) that activates the DL transmission resource may be transmitted and / or detected T_PROC,2 hours prior to the start point of the first resource. Otherwise, the DL transmission resource may not be determined as a conflicting resource.

[0325] (2) B. Here, for example, whether the DL transmission resource is activated may or may not be considered (when determining DL / UL conflicts and / or applying DL / UL conflict handling rules) depending on the priority between the first resource and the corresponding DL transmission resource. For example, if the priority of the first resource is high, whether the DL transmission resource is activated may not be considered. Otherwise, whether the DL transmission resource is activated may be considered.

[0326] Here, for example, the base station (or network) can set and / or instruct the terminal whether to perform the above operation.

[0327] Here, for example, the DL / UL collision handling rule may mean a rule for the operation of a base station (or network) and / or terminal when a DL reception time and a UL transmission time overlap and / or collide on the time axis.

[0328] Here, for example, the priority between the DL transmission resource(s) and / or UL transmission resource(s) may be information that is (preliminarily) agreed upon and / or set between the base station (or network) and the terminal.

[0329] Here, for example, the above T_PROC,2 may mean the processing time required by the terminal for uplink transmission and / or control signal detection.

[0330] Here, for example, the terminal may skip and / or cancel the transmission of the first resource if at least one of the conflicting DL transmission resource(s) has a higher priority than the first resource. Otherwise, the terminal may transmit the first resource and not receive the conflicting DL transmission resource(s).

[0331] For example, in a non-terrestrial network according to one embodiment of the present disclosure, assume that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, for example, 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 can 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.

[0332] Here, for example, in the uplink of a 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. Here, for example, the (common) TA can be 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 can be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). Here, for example, 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 can have different values.

[0333] Therefore, in non-terrestrial networks, 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. As described above, if DL / UL collision handling rules for conventional error cases are defined, the DL / UL collision handling rules may become complicated. For example, in the past, semi-statically configured UL transmission resources could only collide with dynamically scheduled DL transmission resources, and in such cases, dynamic scheduling was given priority. However, when new cases are allowed, semi-statically configured UL transmission resources can collide with semi-statically scheduled DL transmission resources in addition to dynamically scheduled DL transmission resources. Here, for example, when conflict cases are mixed, there must be an agreement on the order in which conflict cases are resolved between the base station (or network) and the terminal. If not, the transmission and reception resources expected by the base station (or network) and the transmission and reception resources expected by the terminal may differ, preventing normal transmission and reception, which may result in resource waste.

[0334] For example, 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, the terminal can determine one or more of the following DL transmission resource(s) as the colliding DL transmission resource(s) based on a (specific) UL transmission resource (hereinafter, the first resource).

[0335] (1) DL transmission resources that are dynamically scheduled and have time resources that overlap with the first resource.

[0336] (1) A. Here, for example, the control signal (e.g., DCI) that scheduled the DL transmission resource may be transmitted and / or detected T_PROC,2 hours prior to the start point of the first resource. Otherwise, the DL transmission resource may not be determined as a conflicting resource.

[0337] (2) DL transmission resources that are set semi-statically and have time resources that overlap with the first resource.

[0338] (2) A. Here, for example, the control signal (e.g., DCI) that activates the DL transmission resource may be transmitted and / or detected T_PROC,2 hours prior to the start point of the first resource. Otherwise, the DL transmission resource may not be determined as a conflicting resource.

[0339] (2) B. Here, for example, whether the DL transmission resource is activated may or may not be considered depending on the priority between the first resource and the corresponding DL transmission resource. For example, if the first resource has a high priority, whether the DL transmission resource is activated may not be considered. Otherwise, whether the DL transmission resource is activated may be considered.

[0340] Here, for example, the terminal may skip and / or cancel the transmission of the first resource if at least one of the conflicting DL transmission resource(s) has a higher priority than the first resource. Otherwise, the terminal may transmit the first resource and not receive the conflicting DL transmission resource(s).

[0341] Here, for example, depending on the transmission type and / or priority information of the UL transmission resource and the DL transmission resource, the terminal processing time may or may not be considered when determining a DL / UL collision. Here, for example, if the UL transmission resource has a higher priority than the DL transmission resource, the processing time may not be considered when determining a DL / UL collision, and if the UL transmission resource has a lower priority than the DL transmission resource, the processing time may be considered when determining a DL / UL collision. For example, when a semi-statically configured UL transmission resource and a semi-statically configured DL transmission resource overlap on the time axis, the terminal may determine a DL / UL collision situation without considering the processing time if the UL transmission resource has a higher priority than the DL transmission resource. On the other hand, if the UL transmission resource has a lower priority than the DL transmission resource, the terminal can determine that a DL / UL collision situation exists only if a control signal (e.g., DCI) for activating the DL transmission resource is transmitted and / or detected before a specific operation time (e.g., T_PROC,2) from the start point of the UL transmission resource. For example, when a dynamically scheduled UL transmission resource and a dynamically scheduled DL transmission resource overlap on the time axis, the terminal can determine that a DL / UL collision situation exists without considering the operation time if the UL transmission resource has a higher priority than the DL transmission resource. On the other hand, if the UL transmission resource has a lower priority than the DL transmission resource, the terminal can determine that a DL / UL collision situation exists only if a control signal (e.g., DCI) for scheduling the DL transmission resource is transmitted and / or detected before a specific operation time (e.g., T_PROC,2) from the start point of the UL transmission resource.

[0342] By clarifying the DL / UL collision determination process of a terminal in situations where multiple types of collision cases coexist, the base station (or network) and the terminal can achieve a common understanding regarding the DL / UL collision determination and / or the application of DL / UL collision handling rules. This supports proper transmission and reception processes and prevents resource waste.

[0343] The above [Proposal #07] can be applied in combination with other proposed methods(s) as long as the proposed actions do not conflict.

[0344] [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, the terminal can perform the DL / UL collision handling rules as follows.

[0345] (1) Step 1: Step of selecting a (specific) UL transmission resource (hereinafter referred to as resource A)

[0346] (1) A. Here, for example, the resource A may be the UL transmission resource with the earliest transmission time among the UL transmission resource(s) (for which DL / UL collision handling rules are not performed).

[0347] (1) B. Here, for example, the resource A may be the UL transmission resource with the highest priority among the UL transmission resource(s) (for which DL / UL collision handling rules are not performed).

[0348] (2) Step 2: Step of determining conflicting DL transmission resource(s) based on resource A and step of executing DL / UL conflict handling rules (for resource A)

[0349] (2) A. Here, for example, the terminal can determine the conflicting DL transmission resource(s) as in [Proposal #07].

[0350] (2) B. Here, for example, the terminal may skip and / or cancel transmission of resource A if at least one of the conflicting DL transmission resource(s) has a higher priority than resource A. Otherwise, the terminal may transmit resource A and not receive the conflicting DL transmission resource(s).

[0351] (3) Step 3: Step of repeating steps 1 and 2 above.

[0352] Here, for example, the base station (or network) can set and / or instruct the terminal whether to perform the above operation.

[0353] Here, for example, there may be one or more transmission resources within the first and / or second resource groups.

[0354] Here, for example, the DL / UL collision handling rule may mean a rule for the operation of a base station (or network) and / or terminal when a DL reception time and a UL transmission time overlap and / or collide on the time axis.

[0355] Here, for example, the priority between the DL transmission resource(s) and / or UL transmission resource(s) may be information that is (preliminarily) agreed upon and / or set between the base station (or network) and the terminal.

[0356] For example, in a non-terrestrial network according to one embodiment of the present disclosure, assume that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, for example, 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 can 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.

[0357] Here, for example, in the uplink of a 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. Here, for example, the (common) TA can be 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 can be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). Here, for example, 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 can have different values.

[0358] Therefore, in non-terrestrial networks, 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. As described above, if DL / UL collision handling rules for conventional error cases are defined, the DL / UL collision handling rules may become complicated. For example, in the past, semi-statically configured UL transmission resources could only collide with dynamically scheduled DL transmission resources, and in such cases, dynamic scheduling was given priority. However, when new cases are allowed, semi-statically configured UL transmission resources can collide with semi-statically scheduled DL transmission resources in addition to dynamically scheduled DL transmission resources. Here, for example, when conflict cases are mixed, there must be an agreement on the order in which conflict cases are resolved between the base station (or network) and the terminal. If not, the transmission and reception resources expected by the base station (or network) and the transmission and reception resources expected by the terminal may differ, preventing normal transmission and reception, which may result in resource waste.

[0359] 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, the terminal can perform the DL / UL collision handling rules as follows.

[0360] (1) Step 1: Step of selecting a (specific) UL transmission resource (hereinafter referred to as resource A)

[0361] (1) A. Here, for example, the resource A may be the UL transmission resource with the earliest transmission time among the UL transmission resource(s) (for which DL / UL collision handling rules are not performed).

[0362] (1) B. Here, for example, the resource A may be the UL transmission resource with the highest priority among the UL transmission resource(s) (for which DL / UL collision handling rules are not performed).

[0363] (2) Step 2: Step of determining conflicting DL transmission resource(s) based on resource A and step of executing DL / UL conflict handling rules (for resource A)

[0364] (2) A. Here, for example, the terminal can determine the conflicting DL transmission resource(s) as in the proposed method #07.

[0365] (2) B. Here, for example, the terminal may skip and / or cancel transmission of resource A if at least one of the conflicting DL transmission resource(s) has a higher priority than resource A. Otherwise, the terminal may transmit resource A and not receive the conflicting DL transmission resource(s).

[0366] (3) Step 3: Step of repeating steps 1 and 2 above.

[0367] For example, the terminal may select a UL transmission resource (hereinafter referred to as resource A) having an earlier transmission time on the time axis among the UL transmission resource(s) to which DL / UL collision determination and / or DL / UL collision handling rule is not applied, and may determine the colliding DL transmission resource(s) based on the resource A as in [Proposal #7] of the present disclosure. Here, for example, the terminal may omit and / or cancel transmission of resource A if at least one or more DL transmission resources among the colliding DL transmission resource(s) have a higher priority than resource A. Otherwise, the terminal may transmit resource A and not receive the colliding DL transmission resource(s). Then, the terminal may select the next UL transmission resource having an earlier transmission time among the UL transmission resource(s) to which DL / UL collision determination and / or DL / UL collision handling rule is not applied, and repeat the above process.

[0368] By clarifying the DL / UL collision determination process of a terminal in situations where multiple types of collision cases coexist, the base station (or network) and the terminal can achieve a common understanding regarding the DL / UL collision determination and / or the application of DL / UL collision handling rules. This supports proper transmission and reception processes and prevents resource waste.

[0369] The above [Proposal #08] can be applied in combination with other proposed methods(s) to the extent that the proposed actions do not conflict.

[0370] For example, for (e)RedCap HD-FDD UEs for NTN, at least the following types need to be considered: For example, given the discrepancy between the TA actually used by the UE and the TA assumed by the gNB based on available TA reports, whether to reuse or update existing handling rules for the following types:

[0371] - Type 1: When dynamically scheduled DL reception conflicts with a semi-statically scheduled UL transmission.

[0372] - Type 2: When a semi-statically configured DL reception conflicts with a dynamically scheduled UL transmission.

[0373] - Type 3: When a DL reception that is set to semi-statically collides with a UL transmission that is set to semi-statically.

[0374] - Type 4: When dynamically scheduled DL reception conflicts with dynamically scheduled UL transmission.

[0375] - Type 5: When the configured SSB conflicts with a dynamically scheduled or configured UL transmission.

[0376] - Type 6: When a dynamic or quasi-static DL collides with a valid RO.

[0377] - Type 7: When a collision occurs due to a change in transmission direction

[0378] For example, the Timing Advance reporting procedure is used to report the UE's timing advance value (e.g., T) to the gNB in ​​a non-terrestrial network (NTN) or air-to-ground network. TA ) is used to provide.

[0379] For example, RRC controls timing advance reporting by setting the following parameters:

[0380] - offsetThresholdTA

[0381] - timingAdvanceSR

[0382] For example, a Timing Advance Report (TAR) should be triggered when one of the following events occurs:

[0383] - When there is an instruction from a higher layer to trigger a timing advance report.

[0384] - When offsetThresholdTA is set in the upper layer and the UE has not previously reported a timing advance value to the current serving cell.

[0385] - If the difference between the currently estimated timing advance value and the last reported timing advance value is greater than or equal to offsetThresholdTA (if offsetThresholdTA is set).

[0386] For example, a MAC entity must:

[0387] 1> If the Timing Advance Reporting procedure determines that one or more TARs have been triggered and not cancelled:

[0388] 2> If UL-SCH resources are available for a new transmission and the logical channel priority results indicate that the UL-SCH resources can accommodate the Timing Advance Report MAC CE and its subheaders:

[0389] 3> Instructs the Multiplexing and Assembly procedure to generate a Timing Advance Report MAC CE as defined in Section 6.1.3.56.

[0390] 2> Otherwise,

[0391] 3> If timingAdvanceSR is set to enabled:

[0392] 4> Trigger a scheduling request.

[0393] For example, note: UL-SCH resources are considered available when the MAC entity configures, receives, or determines an uplink grant. Even if the MAC entity determines that UL-SCH resources are available at a given point in time, this does not necessarily mean that the UL-SCH resources are actually available at that point in time.

[0394] For example, a single MAC PDU must contain at most one timing advance reporting MAC CE, even if multiple events trigger timing advance reporting. The timing advance reporting MAC CE must be generated based on the latest UE timing advance estimate available immediately prior to MAC PDU assembly.

[0395] For example, all triggered timing advance reports must be canceled if the corresponding MAC PDU is transmitted and contains a timing advance report MAC CE.

[0396] Terminals operating in half-duplex transmission mode (HD-FDD) in non-terrestrial networks cannot simultaneously perform downlink (DL) reception and uplink (UL) transmission. This can lead to overlapping or conflicting timing between DL reception and UL transmission. In particular, once collisions occur between semi-static resources, they can recur repeatedly until resources are reconfigured, potentially leading to long-term Timing Advance (TA) errors.

[0397] In existing technologies, TA reporting is performed in relatively long cycles or triggered by simple threshold (offset) conditions, which has the following problems:

[0398] 1. If the difference between the TA recognized by the base station (first TA) and the TA actually applied by the terminal (second TA) increases, reporting may be delayed, and DL / UL timing synchronization mismatch may persist for a long period of time.

[0399] 2. Collisions intentionally scheduled by the base station may be included in the reporting target, resulting in unnecessary waste of UL transmission resources.

[0400] 3. By applying uniform reporting standards without considering the characteristics of each type of collision, unnecessary reports are generated even for collisions that have a low probability of reproducibility or that have already been recognized by the base station.

[0401] Therefore, for some specific types of collisions among multiple types of collisions (e.g., collisions between quasi-static DL resources and quasi-static UL resources), a technology is required that can quickly correct TA mismatches, reduce unnecessary reports, and quickly respond to problem situations that the base station is not aware of by triggering TA reporting based on the number of (consecutive) occurrences of collisions, the occurrence rate, or the occurrence time.

[0402] FIG. 19 illustrates a procedure for performing communication based on uplink timing advance and uplink / downlink settings according to one embodiment of the present disclosure. The embodiment of FIG. 16 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0403] For example, in step S1910, the first device may obtain information related to a semi-statically configured downlink resource. For example, the first device may receive information related to a semi-statically configured downlink resource from a second device. For example, in step S1920, the first device may obtain information related to a semi-statically configured uplink resource. For example, the first device may receive information related to a semi-statically configured uplink resource from a second device. For example, in step S1930, the first device may perform a timing advance report. For example, the timing advance report may be triggered based on a collision between a downlink reception based on information related to the semi-statically configured downlink resource and an uplink transmission based on information related to the semi-statically configured uplink resource. For example, the first device may be a terminal. For example, the second device may be a base station, a network node, or a satellite. For example, the first device and / or the second device may be associated with a non-terrestrial network.

[0404] [Proposal #09] 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 there may be multiple collision types for the DL / UL collision, the terminal can trigger a TA report based on the (consecutive) occurrence count and / or ratio and / or time for some specific collision types among the multiple collision types.

[0405] Here, for example, the base station (or network) can set and / or instruct the terminal whether to perform the above operation.

[0406] Here, for example, the DL / UL collision handling rule may mean a rule for the operation of a base station (or network) and / or terminal when a DL reception time and a UL transmission time overlap and / or collide on the time axis.

[0407] Here, for example, the above-mentioned specific conflict type may be a conflict type involving a quasi-static DL resource and / or a quasi-static UL resource. For example, it may be a conflict type between a quasi-static DL resource and a quasi-static UL resource.

[0408] Here, for example, some specific collision types may be (pre-)defined and / or set and / or instructed by the base station (or network node) to the terminal.

[0409] For example, in a non-terrestrial network according to one embodiment of the present disclosure, assume that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, when the terminal operates in the 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 can 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.

[0410] Here, 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. Here, the (common) TA can be 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 can be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). Here, 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 can have different values.

[0411] Here, in a non-terrestrial network, a terminal can perform TA reporting. However, the TA reporting may be reported at a relatively long cycle, and furthermore, the TA value actually applied by the terminal may differ significantly from the previously reported TA depending on the threshold setting for TA reporting. Here, if the base station assumes the TA reported by the terminal as the first TA, the difference with the second TA actually applied by the terminal may gradually increase. Here, in order to quickly reduce the difference between the first TA and the second TA, a method in which the terminal triggers a TA reporting when a DL / UL collision occurs may be considered. Here, if the terminal reports a TA for any DL / UL collision, the base station (or network node) may also trigger a TA reporting for a DL / UL collision that it has intentionally scheduled, which may unnecessarily waste UL resources. Therefore, in the present disclosure, when a base station (or network node) and / or a terminal in a non-terrestrial network can perform a DL / UL collision handling rule according to a half-duplex transmission mode, and there may be multiple collision types for the DL / UL collision, the terminal can trigger a TA report based on the (continuous) occurrence number and / or ratio and / or time for some specific collision types among the multiple collision types. Here, for example, the some specific collision types may be collision types including quasi-static DL resources and / or quasi-static UL resources. For example, it may be a collision type that collides between quasi-static DL resources and quasi-static UL resources. Here, for example, since a collision between the quasi-static DL resources and quasi-static UL resources may repeatedly occur in the future until resource reconfiguration once the collision occurs, it may be a desirable action for the terminal to report the presence or absence of the collision to the base station.Here, for example, a conflict between a dynamically scheduled DL resource and a dynamically scheduled UL resource may have a long recurrence time and a low frequency of occurrence once the conflict occurs. Therefore, for this type of conflict, triggering a TA report may be a post-event measure and may be ineffective.

[0412] According to the proposed method of the present disclosure, when a terminal triggers a TA report based on a DL / UL collision, an effective TA reporting operation can be supported for a problem situation that the base station is not aware of by not triggering unnecessary TA reports for DL / UL collisions that the base station has already recognized and intentionally scheduled and / or DL / UL collisions that have a low probability of recurrence.

[0413] The above [Proposal #09] can be applied in combination with other proposed methods as long as the proposed actions do not conflict.

[0414] [Proposal #10] 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 half-duplex transmission mode, the base station (or network node) can inform the terminal whether or not scheduling is intended for a specific DL / UL collision.

[0415] Here, for example, the base station (or network) can set and / or instruct the terminal whether to perform the above operation.

[0416] Here, for example, the DL / UL collision handling rule may mean a rule for the operation of a base station (or network) and / or terminal when a DL reception time and a UL transmission time overlap and / or collide on the time axis.

[0417] For example, in a non-terrestrial network according to one embodiment of the present disclosure, assume that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, when the terminal operates in the 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 can 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.

[0418] Here, 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. Here, the (common) TA can be 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 can be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). Here, 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 can have different values.

[0419] Here, in a non-terrestrial network, a terminal can perform TA reporting. However, the TA reporting may be reported at a relatively long cycle, and furthermore, the TA value actually applied by the terminal may differ significantly from the previously reported TA depending on the threshold setting for TA reporting. Here, if the base station assumes the TA reported by the terminal as the first TA, the difference with the second TA actually applied by the terminal may gradually increase. Here, in order to quickly reduce the difference between the first TA and the second TA, a method in which the terminal triggers a TA reporting when a DL / UL collision occurs may be considered. Here, if the terminal reports a TA for any DL / UL collision, the base station (or network node) may also trigger a TA reporting for a DL / UL collision that it has intentionally scheduled, which may unnecessarily waste UL resources. 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, the base station (or network node) can inform the terminal whether a specific DL / UL collision is an intended scheduling. Here, for example, the terminal can trigger a TA report based on the number of occurrences and / or the rate and / or the time for a DL / UL collision that the base station (or network node) did not intentionally schedule.

[0420] According to the proposed method of the present disclosure, when a terminal triggers a TA report based on a DL / UL collision, an effective TA reporting operation can be supported for a problem situation that the base station is not aware of by not triggering unnecessary TA reports for DL / UL collisions that the base station has already recognized and intentionally scheduled and / or DL / UL collisions that have a low probability of recurrence.

[0421] The above [Proposal #10] can be applied in combination with other proposed methods as long as the proposed actions do not conflict.

[0422] [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 half-duplex transmission mode, the terminal can trigger TA reporting based on the (consecutive) occurrence count and / or rate and / or time of at least one of the following events:

[0423] (1) When the TA calculated by the terminal exceeds the predicted TA interval and a DL / UL collision occurs.

[0424] (2) When a DL / UL collision occurs based on the TA criteria calculated by the terminal, but does not occur based on the TA criteria within the predicted TA interval.

[0425] (3) When a DL / UL collision occurs that does not occur based on the TA reported by the terminal, but does occur based on the TA calculated by the terminal.

[0426] Here, for example, the base station (or network) can set and / or instruct the terminal whether to perform the above operation.

[0427] Here, for example, the DL / UL collision handling rule may mean a rule for the operation of a base station (or network) and / or terminal when a DL reception time and a UL transmission time overlap and / or collide on the time axis.

[0428] Here, for example, the predicted TA interval may be information that the base station (or network node) (in advance) defines and / or sets and / or instructs the terminal.

[0429] Here, for example, the TA calculated by the terminal may mean the UL TA and / or Actual TA utilized for actual UL transmission in the terminal.

[0430] For example, in a non-terrestrial network according to one embodiment of the present disclosure, assume that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, when the terminal operates in the 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 can 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.

[0431] Here, 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. Here, the (common) TA can be 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 can be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). Here, 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 can have different values.

[0432] Here, in a non-terrestrial network, a terminal can perform TA reporting. However, the TA reporting may be reported at a relatively long cycle, and furthermore, the TA value actually applied by the terminal may differ significantly from the previously reported TA depending on the threshold setting for TA reporting. Here, if the base station assumes the TA reported by the terminal as the first TA, the difference with the second TA actually applied by the terminal may gradually increase. Here, in order to quickly reduce the difference between the first TA and the second TA, a method in which the terminal triggers a TA reporting when a DL / UL collision occurs may be considered. Here, if the terminal reports a TA for any DL / UL collision, the base station (or network node) may also trigger a TA reporting for a DL / UL collision that it has intentionally scheduled, which may unnecessarily waste UL resources. 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, the terminal can trigger a TA report based on the (consecutive) occurrence number and / or rate and / or time of at least one of the following events.

[0433] (1) When the TA calculated by the terminal exceeds the predicted TA interval and a DL / UL collision occurs.

[0434] (2) When a DL / UL collision occurs based on the TA criteria calculated by the terminal, but does not occur based on the TA criteria within the predicted TA interval.

[0435] (3) When a DL / UL collision occurs that does not occur based on the TA reported by the terminal, but does occur based on the TA calculated by the terminal.

[0436] For example, a base station (or network node) can apply the TA value most recently reported by the terminal when determining a DL / UL collision. Therefore, when a terminal detects a DL / UL collision, if the DL / UL collision occurs based on the most recently reported TA value, it can be assumed that the DL / UL resource is intentionally scheduled by the base station (or network node). On the other hand, if a DL / UL collision occurs that does not occur based on the TA most recently reported by the terminal, but does occur based on the TA calculated by the terminal, the terminal can regard the DL / UL collision as an unintended DL / UL collision by the base station and an event for triggering a TA report.

[0437] According to the proposed method of the present disclosure, when a terminal triggers a TA report based on a DL / UL collision, an effective TA reporting operation can be supported for a problem situation that the base station is not aware of by not triggering unnecessary TA reports for DL / UL collisions that the base station has already recognized and intentionally scheduled and / or DL / UL collisions that have a low probability of recurrence.

[0438] The above [Proposal #11] can be applied in combination with other proposed methods as long as the proposed actions do not conflict.

[0439] [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, and when the terminal can trigger a TA report and / or a TA report purpose SR (Scheduling Request) based on the occurrence of a DL / UL collision, the terminal can transmit the TA report and / or the TA report purpose SR to the base station (or network node) separately from the conventional TA report and / or the TA report purpose SR.

[0440] Here, for example, the base station (or network) can set and / or instruct the terminal whether to perform the above operation.

[0441] Here, for example, the DL / UL collision handling rule may mean a rule for the operation of a base station (or network) and / or terminal when a DL reception time and a UL transmission time overlap and / or collide on the time axis.

[0442] For example, in a non-terrestrial network according to one embodiment of the present disclosure, assume that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, when the terminal operates in the 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 can 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.

[0443] Here, 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. Here, the (common) TA can be 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 can be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). Here, 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 can have different values.

[0444] Here, in a non-terrestrial network, a terminal can perform TA reporting. However, the TA reporting may be reported at a relatively long cycle, and furthermore, the TA value actually applied by the terminal may differ significantly from the previously reported TA depending on the threshold setting for TA reporting. Here, if the base station assumes the TA reported by the terminal as the first TA, the difference with the second TA actually applied by the terminal may gradually increase. Here, in order to quickly reduce the difference between the first TA and the second TA, a method in which the terminal triggers a TA reporting when a DL / UL collision occurs may be considered. Here, if the terminal reports a TA for any DL / UL collision, the base station (or network node) may also trigger a TA reporting for a DL / UL collision that it has intentionally scheduled, which may unnecessarily waste UL resources. 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, and when the terminal can trigger a TA report and / or a TA report purpose SR (Scheduling Request) based on the occurrence of a DL / UL collision, the terminal can transmit the TA report and / or the TA report purpose SR to the base station (or network node) separately from a conventional TA report and / or a TA report purpose SR.

[0445] According to the proposed method of the present disclosure, the base station can distinguish between cases where a TA report is triggered when the TA threshold setting is exceeded and cases where a TA report is triggered due to DL / UL collision detection while the TA is still within the threshold range, and can determine whether to allocate UL transmission resources for TA reporting. This has the advantage of efficiently managing UL resource allocation for TA reporting.

[0446] The above [Proposal #12] can be applied in combination with other proposed methods as long as the proposed actions do not conflict.

[0447] [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, the base station can set and / or indicate priority settings between DL transmission and UL transmission for a specific DL / UL collision type through one or more of the following signaling.

[0448] (1) RRC signaling

[0449] (2) SIB (e.g., SIB19)

[0450] Here, for example, the base station (or network) can set and / or instruct the terminal whether to perform the above operation.

[0451] Here, for example, the DL / UL collision handling rule may mean a rule for the operation of a base station (or network) and / or terminal when a DL reception time and a UL transmission time overlap and / or collide on the time axis.

[0452] Here, for example, the specific DL / UL conflict type may be a type in which a dynamically scheduled DL and a dynamically scheduled UL conflict and / or a type in which a semi-statically configured DL conflicts with a semi-statically configured UL.

[0453] Here, for example, the terminal may apply a default priority setting if a specific collision type occurs before the priority information is set. For example, the default priority setting may be a predefined priority, and may be a method that (always) gives priority to DL or UL for a specific type of DL / UL collision. Alternatively, the default priority may be a predefined priority based on information contained in the DL / UL transmission. For example, for SIB19, it may always give priority to UL.

[0454] Here, for example, in the event of a DL / UL collision, a high priority transmission may be supported, and a low priority transmission may not be transmitted or received.

[0455] Here, for example, SIB may be system information. Here, for example, SIB may be a system information block.

[0456] For example, in a non-terrestrial network according to one embodiment of the present disclosure, assume that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, when the terminal operates in the 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 can 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] Here, 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. Here, the (common) TA can be 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 can be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). Here, 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 can have different values.

[0458] Therefore, in a non-terrestrial network, DL / UL collision case(s) (hereinafter, 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 a conventional base station (or network) is expected to avoid may occur relatively frequently, and DL / UL collision handling rules of a terminal operating in a half-duplex transmission mode for the above case(s) may need to be defined. Therefore, the present disclosure provides that 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, the base station can set and / or indicate priority setting between DL transmission and UL transmission for a specific DL / UL collision type through one or more of the following signaling.

[0459] (1) RRC signaling

[0460] (2) SIB (e.g., SIB19)

[0461] Here, for example, the terminal may apply a default priority setting before receiving the priority information. For example, the default priority setting may be a predefined priority, and may be a method for prioritizing DL for a specific type of DL / UL collision. Alternatively, the default priority may be a predefined priority based on information contained in the DL / UL transmission. For example, for SIB19, it may always prioritize UL. Here, for example, the SIB may be system information. Here, for example, the SIB may be a system information block.

[0462] According to the proposed method of the present disclosure, a base station (or network node) can clearly set priorities for terminals for specific types of DL / UL collisions, and also supports default priorities before the settings become effective, which has the advantage of clarifying terminal operations.

[0463] The above [Proposal #13] can be applied in combination with other proposed methods as long as the proposed actions do not conflict.

[0464] [Proposal #14] In a non-terrestrial network, a base station (or network node) and / or a terminal may support one or more TA reporting schemes including a first TA reporting scheme and a second TA reporting scheme, and the base station (or network node) may instruct and / or set and / or trigger a first time interval to the terminal, and the terminal may apply the second TA reporting scheme in the first time interval, and may apply the first TA reporting scheme in other time intervals.

[0465] Here, for example, the TA reporting method may include a TA reporting trigger and / or a TA reporting transmission format and / or a TA reporting transmission resource.

[0466] Here, for example, the first time interval may be a time interval during which the base station (or network node) is activated and / or deactivated. Here, for example, the activation and / or deactivation may be indicated via a MAC Control Element (CE) and / or DCI, etc. Here, for example, the time at which the activation and / or deactivation is applied may be determined based on the time of receiving feedback on MAC Control Element (CE) and / or DCI-based data.

[0467] Here, for example, the first time interval may be a time interval during which a timer triggered by a base station (or network node) is valid. Here, for example, the trigger may be indicated via a MAC Control Element (CE) and / or DCI, etc. Here, for example, the time point at which the trigger and / or timer are applied may be determined based on the time point at which feedback for MAC Control Element (CE) and / or DCI-based data is received. For example, the terminal may implicitly interpret reception of a PDCCH (related to downlink data and / or uplink data scheduling) as activation / triggering of the first time interval by the base station (or network node).

[0468] Here, for example, the first TA reporting method may include one or more of the following methods.

[0469] (1) A method of triggering a TA report when the difference between the TA estimated from the terminal and the (recently) reported TA is greater than the first threshold.

[0470] Here, for example, the second TA reporting method may include one or more of the following methods.

[0471] (1) A method of triggering a TA report when the difference between the TA estimated from the terminal and the (recently) reported TA is greater than the second threshold.

[0472] (2) Method for triggering TA reporting when a collision between DL and UL is detected at the terminal.

[0473] (3) A method of reporting TA drift rate together with TA report from the terminal.

[0474] (4) A method of triggering a TA report when the difference between the TA estimated at the terminal and the TA calculated based on the (reported) TA drift rate is greater than the second threshold.

[0475] Here, for example, the base station (or network node) may set and / or instruct the terminal as to whether to apply the first TA reporting method and / or the second TA reporting method. For example, only the first TA reporting method may be set and / or instructed to the terminal.

[0476] Here, for example, when the terminal implicitly interprets the reception of a PDCCH (related to downlink data and / or uplink data scheduling) as activation / triggering of the first time interval by the base station (or network node), the base station (or network node) may set and / or indicate information about a PDCCH that can be interpreted as the activation / trigger.

[0477] Here, for example, the length of the first time interval activated / triggered by the downlink data scheduling related PDCCH and the length of the first time interval activated / triggered by the uplink data scheduling related PDCCH may be the same or different.

[0478] Here, for example, the second threshold value may be set to a smaller value than the first threshold value.

[0479] For example, in a non-terrestrial network according to one embodiment of the present disclosure, assume that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, when the terminal operates in the 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 can 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.

[0480] Here, 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. Here, the (common) TA can be 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 can be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). Here, 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 can have different values.

[0481] Here, in order to alleviate the degree of TA mismatch between the base station (or network node) and the terminal, it is necessary to strengthen the TA reporting method. However, the strengthened TA reporting method may not always be necessary, and may be necessary when a collision may occur between DL / UL. Therefore, the present disclosure provides that in a non-terrestrial network, a base station (or network node) and / or a terminal may support one or more TA reporting methods including a first TA reporting method and a second TA reporting method, and the base station (or network node) may instruct and / or configure and / or trigger a first time interval to the terminal, and the terminal may apply the second TA reporting method in the first time interval, and apply the first TA reporting method in other time intervals. For example, the first time interval may refer to a time interval that the base station (or network node) configures and / or instructs the terminal via MAC CE and / or DCI. Here, for example, the terminal may apply an enhanced TA reporting method (hereinafter referred to as the second TA reporting method) within the first time interval, and may apply a conventional TA reporting method (hereinafter referred to as the first TA reporting method) outside the first time interval. For example, the first TA reporting method may include one or more of the following TA reporting methods.

[0482] (1) A method of triggering a TA report when the difference between the TA estimated from the terminal and the (recently) reported TA is greater than the first threshold.

[0483] For example, the second TA reporting method may include one or more of the following TA reporting methods.

[0484] (1) A method of triggering a TA report when the difference between the TA estimated from the terminal and the (recently) reported TA is greater than the second threshold.

[0485] (2) Method for triggering TA reporting when a collision between DL and UL is detected at the terminal.

[0486] (3) A method of reporting TA drift rate together with TA report from the terminal.

[0487] (4) A method of triggering a TA report when the difference between the TA estimated at the terminal and the TA calculated based on the (reported) TA drift rate is greater than the second threshold.

[0488] Here, for example, the base station (or network node) may set and / or instruct the terminal as to whether to apply the first TA reporting method and / or the second TA reporting method. For example, only the first TA reporting method may be set and / or instructed to the terminal.

[0489] According to the proposed method of the present disclosure, an enhanced TA reporting method is supported to alleviate TA mismatch between a terminal and a base station (or network node) in a non-terrestrial network, and the signaling load can be reduced by adaptively applying the enhanced TA reporting method to a time period determined by the base station (or network node) as necessary.

[0490] The above [Proposal #14] can be applied in combination with other proposed methods as long as the proposed actions do not conflict.

[0491] [Proposal #14-2] In a non-terrestrial network, a base station (or network node) and / or a terminal may support one or more TA reporting methods including a first TA reporting method and a second TA reporting method, and the terminal may select and apply a (specific) TA reporting method among the first TA reporting method and the second TA reporting method based on whether a (specific) DL / UL collision type occurs.

[0492] Here, for example, the TA reporting method may include a TA reporting trigger and / or a TA reporting transmission format and / or a TA reporting transmission resource.

[0493] Here, for example, the first TA reporting method may include one or more of the following methods.

[0494] (1) A method of triggering a TA report when the difference between the TA estimated from the terminal and the (recently) reported TA is greater than the first threshold.

[0495] Here, for example, the second TA reporting method may include one or more of the following methods.

[0496] (1) A method of triggering a TA report when the difference between the TA estimated from the terminal and the (recently) reported TA is greater than the second threshold.

[0497] (2) Method for triggering TA reporting when a collision between DL and UL is detected at the terminal.

[0498] (3) A method of reporting TA drift rate together with TA report from the terminal.

[0499] (4) A method of triggering a TA report when the difference between the TA estimated at the terminal and the TA calculated based on the (reported) TA drift rate is greater than the second threshold.

[0500] Here, for example, the base station (or network node) may set and / or instruct the terminal as to whether to apply the first TA reporting method and / or the second TA reporting method. For example, only the first TA reporting method may be set and / or instructed to the terminal.

[0501] Here, for example, the second threshold value may be set and / or defined as a value smaller than the first threshold value. Alternatively, the first threshold value and the second threshold value may be values ​​that are set and / or defined independently of each other.

[0502] Here, for example, the second TA reporting method may utilize a finer TA reporting granularity and / or a smaller TA offset threshold compared to the first TA reporting method. Here, for example, the terminal may trigger TA reporting if the difference between the actual TA and the reported TA is equal to or exceeds the TA offset threshold.

[0503] Here, for example, the terminal may operate in the first TA reporting mode and then switch to the second TA reporting mode based on whether a (specific) DL / UL collision type occurs. Here, for example, the terminal may revert from the second TA reporting mode to the first TA reporting mode if one or more of the following conditions are satisfied.

[0504] (1) If TA reporting is performed more than a certain number of times (e.g., N times) based on the second TA reporting method.

[0505] (2) If a certain period of time (e.g., during T) has elapsed since the start of the 2nd TA reporting method

[0506] Here, for example, the predetermined number of times (e.g., N) and / or predetermined time (e.g., T) may be values ​​that the base station (or network node) (in advance) defines and / or sets and / or instructs the terminal. For example, N may be 1.

[0507] For example, in a non-terrestrial network according to one embodiment of the present disclosure, assume that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, when the terminal operates in the 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 can 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.

[0508] Here, 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. Here, the (common) TA can be 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 can be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). Here, 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 can have different values.

[0509] Here, in order to alleviate the degree of TA mismatch between the base station (or network node) and the terminal, it is necessary to strengthen the TA reporting method. However, the strengthened TA reporting method may not always be necessary, and may be necessary when a DL / UL collision may occur. Therefore, in the present disclosure, in a non-terrestrial network, a base station (or network node) and / or a terminal can support one or more TA reporting methods including a first TA reporting method and a second TA reporting method, and the terminal can select and apply a (specific) TA reporting method among the first TA reporting method and the second TA reporting method based on whether a (specific) DL / UL collision type occurs. For example, the terminal may normally perform TA reporting according to the first TA reporting method, but may perform TA reporting according to the second TA reporting method if the occurrence of a (specific) DL / UL collision type is detected a certain number of times or more. For example, the first TA reporting method may be a method that triggers a TA report when the difference between the TA estimated by the terminal and the (recently) reported TA is greater than or equal to a first threshold, and the second TA reporting method may be a method that triggers a TA report when the difference between the TA estimated by the terminal and the (recently) reported TA is greater than or equal to a second threshold. Here, for example, the second threshold value may be set to a value smaller than the first threshold value. Here, for example, the base station (or network node) may set and / or instruct the terminal whether to apply the first TA reporting method and / or the second TA reporting method. For example, only the first TA reporting method may be set and / or instructed to the terminal.

[0510] According to the proposed method of the present disclosure, an enhanced TA reporting method is supported to alleviate TA mismatch between a terminal and a base station (or network node) in a non-terrestrial network, and the signaling load can be reduced by adaptively applying the enhanced TA reporting method to a time period determined by the base station (or network node) as necessary.

[0511] The above [Proposal #14-2] can be applied in combination with other proposed methods(s) to the extent that the proposed actions do not conflict.

[0512] [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, the terminal may not expect a case (hereinafter, Case 1) where a (single) DL (or UL) transmission resource collides with two or more UL (or DL) transmissions.

[0513] Here, for example, the base station (or network) can set and / or instruct the terminal whether to perform the above operation.

[0514] Here, for example, the DL / UL collision handling rule may mean a rule for the operation of a base station (or network) and / or terminal when a DL reception time and a UL transmission time overlap and / or collide on the time axis.

[0515] Here, for example, when the first case occurs, the terminal may determine that it is an error situation and perform an operation according to the terminal implementation.

[0516] Here, for example, the first case may be limited to a case where two or more UL (or DL) transmissions collide with a (single) DL (or UL) transmission resource and have different priorities and / or priority rules. For example, it may be a case where a first UL (or DL) transmission resource collides with a first DL (or UL) transmission resource and a second DL (or UL) transmission resource, and the first UL (or DL) transmission resource has a lower priority than the first DL (or UL) transmission resource and a higher priority than the second DL (or UL) transmission resource.

[0517] Here, for example, the first case may not include a case where two or more UL (or DL) transmissions collide with a (single) DL (or UL) transmission resource and have the same priority and / or priority rules.

[0518] For example, in a non-terrestrial network according to one embodiment of the present disclosure, assume that a base station (or network) serves a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, when the terminal operates in the 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 can 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.

[0519] Here, 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. Here, the (common) TA can be 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 can be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). Here, 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 can have different values.

[0520] Therefore, in non-terrestrial networks, 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. As described above, if DL / UL collision handling rules for conventional error cases are defined, the DL / UL collision handling rules may become complicated. For example, in the past, semi-statically configured UL transmission resources could only collide with dynamically scheduled DL transmission resources, and in such cases, dynamic scheduling was given priority. However, when new cases are allowed, semi-statically configured UL transmission resources can collide with semi-statically scheduled DL transmission resources in addition to dynamically scheduled DL transmission resources. Here, in the case where conflict cases are mixed, there must be an agreement on the order in which conflict cases are resolved between the base station (or network) and the terminal. If not, the transmission and reception resources expected by the base station (or network) and the transmission and reception resources expected by the terminal may differ, preventing normal transmission and reception, which may result in resource waste.

[0521] 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, the terminal may not expect a case (hereinafter referred to as the first case) where a (single) DL (or UL) transmission resource collides with two or more UL (or DL) transmissions. Here, for example, the first case may be limited to a case where a (single) DL (or UL) transmission resource has different priorities and / or priority rules for two or more colliding UL (or DL) transmissions. For example, it may be a case where a first UL (or DL) transmission resource collides with a first DL (or UL) transmission resource and a second DL (or UL) transmission resource, and the first UL (or DL) transmission resource has a lower priority than the first DL (or UL) transmission resource and a higher priority than the second DL (or UL) transmission resource. For example, the first case above may not include a case where two or more UL (or DL) transmissions collide with a (single) DL (or UL) transmission resource and have the same priority and / or priority rules. Here, for example, when the first case occurs, the terminal may determine that it is an error situation and perform an action according to the terminal implementation.

[0522] According to the proposed method of the present disclosure, there is an advantage in that it facilitates application and / or understanding of DL / UL collision handling rules between a base station (or network node) and a terminal by not expecting multiple DL / UL collisions to which different DL / UL priority rules are applied from a terminal perspective.

[0523] The above [Proposal #15] can be applied in combination with other proposed methods as long as the proposed actions do not conflict.

[0524] For example, in embodiments of the present disclosure, the base station or network node may be a satellite. For example, the base station or network node may be a transparent satellite. For example, the base station or network node may be a regenerative satellite.

[0525] The combination of embodiments of the present disclosure may operate in conjunction with each other.

[0526] Various embodiments of the present disclosure may be applied differently depending on the link type (DL, UL, SL), and / or the data type (SIB, groupcast, unicast), and / or the search space type in which the scheduling PDCCH is detected (common search space (CSS), UE-specific search space (USS)), and / or the base station node type, and / or the altitude, and / or the presence or absence of power constraints. For example, a combination of various embodiments of the present disclosure may be applied only when related to SIB transmission.

[0527] For example, the timing advance reported in an embodiment of the present disclosure may be a previously reported timing advance. For example, the TA reported in an embodiment of the present disclosure may be a previously reported TA. For example, in an embodiment of the present disclosure, the SIB may be used in place of system information.

[0528] FIG. 20 illustrates a method for a first device to perform wireless communication, according to an embodiment of the present disclosure. The embodiment of FIG. 20 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0529] Referring to FIG. 20, in step S2010, the first device can obtain information related to a semi-statically configured downlink resource. In step S2020, the first device can obtain information related to a semi-statically configured uplink resource. In step S2030, the first device can trigger a timing advance report. For example, the timing advance report can be triggered based on a collision between a downlink reception based on information related to the semi-statically configured downlink resource and an uplink transmission based on information related to the semi-statically configured uplink resource.

[0530] For example, the timing advance report may be triggered based on the number of occurrences of the collision being greater than or equal to a threshold.

[0531] For example, the number of collisions may be the number of consecutive occurrences of the collisions.

[0532] For example, the type of collision may be set by the base station or the network.

[0533] For example, the first device may obtain information regarding whether the collision is an intended scheduling conflict. For example, the timing advance report may be triggered based on a collision between a downlink reception associated with information regarding the semi-statically configured downlink resources and an uplink transmission associated with information regarding the semi-statically configured uplink resources, and based on whether the collision is an unintended scheduling conflict.

[0534] For example, the first device may obtain information related to a predicted timing advance interval. For example, the first device may calculate a timing advance. For example, the timing advance report may be triggered based on whether the uplink and downlink do not collide based on the predicted timing advance interval, and whether they collide based on the calculated timing advance.

[0535] For example, the first device may calculate a timing advance. For example, the timing advance report may be triggered based on a non-conflict based on a (previously) reported timing advance, and based on a conflict based on the calculated timing advance.

[0536] For example, the timing advance report may be included in a second timing advance report related to a collision between downlink and uplink. For example, information related to the second timing advance report may be transmitted separately from information related to the first timing advance report that is not related to a collision between downlink and uplink.

[0537] For example, system information can be system information.

[0538] For example, the system information may be SIB19 (system information block 19).

[0539] For example, information related to the timing advance report may include a timing advance drift rate.

[0540] For example, information related to the first timing advance report that is not related to the collision between the uplinks may be transmitted based on a difference between the estimated timing advance of the first device and the (previously) reported timing advance being greater than or equal to a threshold.

[0541] For example, information related to a second timing advance report related to a collision between the downlink and uplink may be transmitted based on the collision being detected between the downlink and uplink by the first device.

[0542] For example, it may not be expected that the first device, based on a single downlink resource colliding with two or more uplink resources, or based on a single uplink resource colliding with two or more DL transmission resources, would have different priority rules applied to each of the two or more collisions.

[0543] For example, it may not be expected that the first device, based on a single downlink resource colliding with two or more uplink resources, or based on a single uplink resource colliding with two or more DL transmission resources, would have different priorities applied to each of the two or more collisions.

[0544] The above proposed method can be applied to devices according to various embodiments of the present disclosure. First, the processor (102) of the first device (100) can obtain information related to a semi-statically configured downlink resource (for example, the processor (102) of the first device (100) can control the transceiver (106) to obtain information related to a semi-statically configured downlink resource). Then, the processor (102) of the first device (100) can obtain information related to a semi-statically configured uplink resource (for example, the processor (102) of the first device (100) can control the transceiver (106) to obtain information related to a semi-statically configured uplink resource). And, the processor (102) of the first device (100) can trigger a timing advance report (e.g., the processor (102) of the first device (100) can control the transceiver (106) to trigger the timing advance report). For example, the timing advance report can be triggered based on a downlink reception based on information associated with the semi-statically configured downlink resources colliding with an uplink transmission based on information associated with the semi-statically configured uplink resources.

[0545] According to one embodiment of the present disclosure, a first device may be provided. For example, the first 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, when executed by the at least one processor, may cause the first device to: obtain information related to a semi-statically configured downlink resource; obtain information related to a semi-statically configured uplink resource; and trigger a timing advance report. For example, the timing advance report may be triggered based on a collision between a downlink reception based on information related to the semi-statically configured downlink resource and an uplink transmission based on information related to the semi-statically configured uplink resource.

[0546] For example, the timing advance report may be triggered based on the number of occurrences of the collision being greater than or equal to a threshold.

[0547] For example, the number of collisions may be the number of consecutive occurrences of the collisions.

[0548] For example, the type of collision may be set by the base station or the network.

[0549] For example, the first device may obtain information regarding whether the collision is an intended scheduling conflict. For example, the timing advance report may be triggered based on a collision between a downlink reception associated with information regarding the semi-statically configured downlink resources and an uplink transmission associated with information regarding the semi-statically configured uplink resources, and based on whether the collision is an unintended scheduling conflict.

[0550] For example, the first device may obtain information related to a predicted timing advance interval. For example, the first device may calculate a timing advance. For example, the timing advance report may be triggered based on whether the uplink and downlink do not collide based on the predicted timing advance interval, and whether they collide based on the calculated timing advance.

[0551] For example, the first device may calculate a timing advance. For example, the timing advance report may be triggered based on a non-conflict based on a (previously) reported timing advance, and based on a conflict based on the calculated timing advance.

[0552] For example, the timing advance report may be included in a second timing advance report related to a collision between downlink and uplink. For example, information related to the second timing advance report may be transmitted separately from information related to the first timing advance report that is not related to a collision between downlink and uplink.

[0553] For example, system information can be system information.

[0554] For example, the system information may be SIB19 (system information block 19).

[0555] For example, information related to the timing advance report may include a timing advance drift rate.

[0556] For example, information related to the first timing advance report that is not related to the collision between the uplinks may be transmitted based on a difference between the estimated timing advance of the first device and the (previously) reported timing advance being greater than or equal to a threshold.

[0557] For example, information related to a second timing advance report related to a collision between the downlink and uplink may be transmitted based on the collision being detected between the downlink and uplink by the first device.

[0558] For example, it may not be expected that the first device, based on a single downlink resource colliding with two or more uplink resources, or based on a single uplink resource colliding with two or more DL transmission resources, would have different priority rules applied to each of the two or more collisions.

[0559] For example, it may not be expected that the first device, based on a single downlink resource colliding with two or more uplink resources, or based on a single uplink resource colliding with two or more DL transmission resources, would have different priorities applied to each of the two or more collisions.

[0560] According to one embodiment of the present disclosure, a processing device (configured to control a first 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 first device to: obtain information related to a semi-statically configured downlink resource; obtain information related to a semi-statically configured uplink resource; and trigger a timing advance report. For example, the timing advance report may be triggered based on a collision between a downlink reception based on information related to the semi-statically configured downlink resource and an uplink transmission based on information related to the semi-statically configured uplink resource.

[0561] 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 first device to: obtain information related to a semi-statically configured downlink resource; obtain information related to a semi-statically configured uplink resource; and trigger a timing advance report. For example, the timing advance report may be triggered based on a collision between a downlink reception based on the information related to the semi-statically configured downlink resource and an uplink transmission based on the information related to the semi-statically configured uplink resource.

[0562] FIG. 21 illustrates a method for a second device to perform wireless communication according to an embodiment of the present disclosure. The embodiment of FIG. 21 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0563] Referring to FIG. 21, in step S2110, the second device may transmit information related to a semi-statically configured downlink resource to the first device. In step S2120, the second device may transmit information related to a semi-statically configured uplink resource to the first device. In step S2130, the second device may receive a timing advance report from the first device. For example, the timing advance report may be triggered based on a conflict between a downlink transmission based on information related to the semi-statically configured downlink resource and an uplink reception based on information related to the semi-statically configured uplink resource.

[0564] For example, the timing advance report may be triggered based on the number of occurrences of the collision being greater than or equal to a threshold.

[0565] For example, the number of collisions may be the number of consecutive occurrences of the collisions.

[0566] For example, the type of collision may be set by the base station or the network.

[0567] For example, the second device may transmit information regarding whether the collision is an intended scheduling conflict. For example, the timing advance report may be triggered based on a downlink reception associated with information regarding the semi-statically configured downlink resources colliding with an uplink transmission associated with information regarding the semi-statically configured uplink resources, and based on the collision being an unintended scheduling conflict.

[0568] For example, the second device may transmit information related to a predicted timing advance interval. For example, the timing advance may be calculated. For example, the timing advance report may be triggered based on whether the uplink and downlink do not collide based on the predicted timing advance interval, and whether they collide based on the calculated timing advance.

[0569] For example, timing advances can be calculated. For example, the timing advance report can be triggered based on non-conflicts based on (previously) reported timing advances, and based on conflicts based on calculated timing advances.

[0570] For example, the timing advance report may be included in a second timing advance report related to a collision between downlink and uplink. For example, information related to the second timing advance report may be received separately from information related to the first timing advance report that is not related to a collision between downlink and uplink.

[0571] For example, system information can be system information.

[0572] For example, the system information may be SIB19 (system information block 19).

[0573] For example, information related to the timing advance report may include a timing advance drift rate.

[0574] For example, information related to the first timing advance report that is not related to the collision between the uplinks may be transmitted based on a difference between the estimated timing advance of the first device and the (previously) reported timing advance being greater than or equal to a threshold.

[0575] For example, information related to a second timing advance report related to a collision between the downlink and uplink may be transmitted based on the collision being detected between the downlink and uplink by the first device.

[0576] For example, based on a single downlink resource colliding with two or more uplink resources, or based on a single uplink resource colliding with two or more DL transmission resources, it may not be expected that different priority rules are applied to each of the two or more conflicts.

[0577] For example, based on a single downlink resource colliding with two or more uplink resources, or based on a single uplink resource colliding with two or more DL transmission resources, it may not be expected that different priorities would be applied to each of the two or more conflicts.

[0578] The above proposed method can be applied to devices according to various embodiments of the present disclosure. First, the processor (202) of the second device (200) can transmit information related to a semi-statically configured downlink resource to the first device (for example, the processor (202) of the second device (200) can control the transceiver (206) to transmit information related to a semi-statically configured downlink resource). Then, the processor (202) of the second device (200) can transmit information related to a semi-statically configured uplink resource to the first device (for example, the processor (202) of the second device (200) can control the transceiver (206) to transmit information related to a semi-statically configured uplink resource to the first device). And, the processor (202) of the second device (200) can receive a timing advance report from the first device (e.g., the processor (202) of the second device (200) can control the transceiver (206) to receive the timing advance report from the first device). For example, the timing advance report can be triggered based on a downlink transmission based on information related to the semi-statically configured downlink resources colliding with an uplink reception based on information related to the semi-statically configured uplink resources.

[0579] According to one embodiment of the present disclosure, a second device may be provided. For example, the second 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 second device to: transmit, to a first device, information related to a semi-statically configured downlink resource; transmit, to the first device, information related to a semi-statically configured uplink resource; and receive, from the first device, a timing advance report. For example, the timing advance report may be triggered based on a collision between a downlink transmission based on information related to the semi-statically configured downlink resource and an uplink reception based on information related to the semi-statically configured uplink resource.

[0580] For example, the timing advance report may be triggered based on the number of occurrences of the collision being greater than or equal to a threshold.

[0581] For example, the number of collisions may be the number of consecutive occurrences of the collisions.

[0582] For example, the type of collision may be set by the base station or the network.

[0583] For example, the second device may transmit information regarding whether the collision is an intended scheduling conflict. For example, the timing advance report may be triggered based on a downlink reception associated with information regarding the semi-statically configured downlink resources colliding with an uplink transmission associated with information regarding the semi-statically configured uplink resources, and based on the collision being an unintended scheduling conflict.

[0584] For example, the second device may transmit information related to a predicted timing advance interval. For example, the timing advance may be calculated. For example, the timing advance report may be triggered based on whether the uplink and downlink do not collide based on the predicted timing advance interval, and whether they collide based on the calculated timing advance.

[0585] For example, timing advances can be calculated. For example, the timing advance report can be triggered based on non-conflicts based on (previously) reported timing advances, and based on conflicts based on calculated timing advances.

[0586] For example, the timing advance report may be included in a second timing advance report related to a collision between downlink and uplink. For example, information related to the second timing advance report may be received separately from information related to the first timing advance report that is not related to a collision between downlink and uplink.

[0587] For example, system information can be system information.

[0588] For example, the system information may be SIB19 (system information block 19).

[0589] For example, information related to the timing advance report may include a timing advance drift rate.

[0590] For example, information related to the first timing advance report that is not related to the collision between the uplinks may be transmitted based on a difference between the estimated timing advance of the first device and the (previously) reported timing advance being greater than or equal to a threshold.

[0591] For example, information related to a second timing advance report related to a collision between the downlink and uplink may be transmitted based on the collision being detected between the downlink and uplink by the first device.

[0592] For example, based on a single downlink resource colliding with two or more uplink resources, or based on a single uplink resource colliding with two or more DL transmission resources, it may not be expected that different priority rules are applied to each of the two or more conflicts.

[0593] For example, based on a single downlink resource colliding with two or more uplink resources, or based on a single uplink resource colliding with two or more DL transmission resources, it may not be expected that different priorities would be applied to each of the two or more conflicts.

[0594] According to one embodiment of the present disclosure, a processing device (configured to control a second 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 second device to: transmit, to a first device, information related to a semi-statically configured downlink resource; transmit, to the first device, information related to a semi-statically configured uplink resource; and receive, from the first device, a timing advance report. For example, the timing advance report may be triggered based on a collision between a downlink transmission based on information related to the semi-statically configured downlink resource and an uplink reception based on information related to the semi-statically configured uplink resource.

[0595] 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 second device to: transmit, to a first device, information related to a semi-statically configured downlink resource; transmit, to the first device, information related to a semi-statically configured uplink resource; and receive, from the first device, a timing advance report. For example, the timing advance report may be triggered based on a collision between a downlink transmission based on the information related to the semi-statically configured downlink resource and an uplink reception based on the information related to the semi-statically configured uplink resource.

[0596] According to the present disclosure, a terminal can trigger a TA report based on the number of (consecutive) collision occurrences, the occurrence rate, or the occurrence time for a specific collision type among multiple collision types according to DL / UL collision handling rules. Accordingly, the following effects can be achieved.

[0597] 1. Early correction of TA error: The difference between the first and second TAs can be quickly reduced to improve DL / UL timing synchronization accuracy.

[0598] 2. Improved UL resource efficiency: Prevents waste of UL transmission resources by omitting reports for collisions that are intentionally scheduled by the base station or collisions with low probability of recurrence.

[0599] 3. Rapid recognition of problem situations: By reporting only collision situations that the base station is unaware of, the base station can identify and respond to problems early.

[0600] 4. Scalability of reporting policy: More sophisticated TA reporting policies can be implemented by combining with other conditions, such as base station intent determination and comparison results between predicted TA and calculated TA.

[0601] The various embodiments of the present disclosure may be combined with each other, and some descriptions, functions, procedures, proposals, methods and / or operations of the various embodiments may be omitted.

[0602] 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).

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

[0604] 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.

[0605] 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.

[0606] Fig. 22 illustrates a communication system (1) according to one embodiment of the present disclosure. The embodiment of Fig. 22 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0607] Referring to FIG. 22, 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.

[0608] 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.

[0609] 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).

[0610] 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.

[0611] FIG. 23 illustrates a wireless device according to an embodiment of the present disclosure. The embodiment of FIG. 23 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0612] Referring to FIG. 23, 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. 22.

[0613] 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.

[0614] 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.

[0615] 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.

[0616] 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 executed 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.

[0617] 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.

[0618] 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.

[0619] FIG. 24 illustrates a signal processing circuit for a transmission signal according to an embodiment of the present disclosure. The embodiment of FIG. 24 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0620] Referring to FIG. 24, 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. 24 may be performed in the processor (102, 202) and / or the transceiver (106, 206) of FIG. 23. The hardware elements of FIG. 24 may be implemented in the processor (102, 202) and / or the transceiver (106, 206) of FIG. 23. For example, blocks 1010 to 1060 may be implemented in the processor (102, 202) of FIG. 23. Additionally, blocks 1010 to 1050 may be implemented in the processor (102, 202) of FIG. 23, and block 1060 may be implemented in the transceiver (106, 206) of FIG. 23.

[0621] The codeword can be converted into a wireless signal through the signal processing circuit (1000) of FIG. 24. 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).

[0622] 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.

[0623] 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.

[0624] 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. 24. For example, a wireless device (e.g., 100, 200 of FIG. 23) 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.

[0625] Figure 25 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 22). The embodiment of Figure 25 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0626] Referring to FIG. 25, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 23 and may be composed of various elements, components, 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. 23. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 23. 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).

[0627] 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. 22, 100a), a vehicle (Fig. 22, 100b-1, 100b-2), an XR device (Fig. 22, 100c), a portable device (Fig. 22, 100d), a home appliance (Fig. 22, 100e), an IoT device (Fig. 22, 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. 22, 400), a base station (Fig. 22, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0628] In FIG. 25, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected 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.

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

[0630] FIG. 26 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. 26 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0631] Referring to FIG. 26, 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. 25, respectively.

[0632] 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.

[0633] 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).

Claims

1. In the method, A step in which a first device acquires information related to a semi-statically set downlink resource; The first device obtains information related to a semi-statically set uplink resource; and The first device comprises a step of triggering a timing advance report; A method wherein the timing advance report is triggered based on a collision between a downlink reception based on information related to the semi-statically configured downlink resources and an uplink transmission based on information related to the semi-statically configured uplink resources.

2. In paragraph 1, The above timing advance report is triggered based on the number of occurrences of the above collision being greater than or equal to a threshold value.

3. In paragraph 2, The number of the above collisions is the number of consecutive occurrences of the above collisions, 4. In paragraph 1, The type of the above collision is set by the base station or the network, 5. In paragraph 1, The first device further comprises a step of obtaining information related to whether the collision is an intended scheduling; The timing advance report is triggered based on a collision between a downlink reception related to information related to the semi-statically configured downlink resources and an uplink transmission related to information related to the semi-statically configured uplink resources, and based on the collision being an unintended scheduling.

6. In paragraph 1, The first device obtains information related to the predicted timing advance section; and The first device further comprises a step of calculating a timing advance; A method wherein the above timing advance report is triggered based on the uplink and downlink not colliding based on the predicted timing advance interval and colliding based on the calculated timing advance.

7. In paragraph 1, The first device further comprises a step of calculating a timing advance; A method wherein the above timing advance report is triggered based on a non-conflict based on a previously reported timing advance and based on a conflict based on a calculated timing advance.

8. In paragraph 1, The above timing advance report is included in a second timing advance report related to a collision between downlink and uplink, and A method wherein information related to the second timing advance report is transmitted separately from information related to the first timing advance report related to a collision between the downlink and the uplink.

9. In paragraph 1, A method in which information regarding whether to prioritize the downlink reception or the uplink transmission related to the above collision is received via system information.

10. In paragraph 1, The above system information is SIB19 (system information block 19), the method.

11. In paragraph 8, Information related to the first timing advance report that is not related to the collision between the uplinks is transmitted based on a difference between the estimated timing advance of the first device and the reported timing advance being greater than or equal to a threshold, and A method wherein information related to a second timing advance report related to a collision between the downlink and uplink is transmitted based on the collision being detected between the downlink and uplink by the first device.

12. In paragraph 1, A method further comprising a step of not expecting that priority rules applied to each of the two or more collisions are different, based on the first device colliding with a single downlink resource and two or more uplink resources, or based on the single uplink resource colliding with two or more DL transmission resources.

13. In paragraph 1, A method further comprising: a step of not expecting that the priorities applied to each of the two or more collisions are different, based on the first device colliding with two or more uplink resources or based on the single uplink resource colliding with two or more DL transmission resources; 14. In the first 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 first device causes: Obtain information related to semi-statically configured downlink resources; Obtain information related to uplink resources that are set semi-statically; and Trigger the timing advance report, A first device, wherein the timing advance report is triggered based on a collision between downlink reception based on information related to the semi-statically configured downlink resources and uplink transmission based on information related to the semi-statically configured uplink resources.

15. In the processing 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 first device causes: Obtain information related to semi-statically configured downlink resources; Obtain information related to uplink resources that are set semi-statically; and Trigger the timing advance report, A processing device wherein the timing advance report is triggered based on a collision between downlink reception based on information related to the semi-statically configured downlink resources and uplink transmission based on information related to the semi-statically configured uplink resources.

16. A non-transitory computer-readable storage medium that records commands, The above commands, when executed, cause the first device to: Obtain information related to semi-statically configured downlink resources; Obtain information related to uplink resources that are set semi-statically; and Trigger the timing advance report, A non-transitory computer-readable storage medium in which the timing advance report is triggered based on a collision between a downlink reception based on information related to the semi-statically configured downlink resources and an uplink transmission based on information related to the semi-statically configured uplink resources.

17. In the method, A step in which a second device transmits, to a first device, information related to a semi-statically set downlink resource; A step in which the second device transmits information related to a semi-statically set uplink resource to the first device; and The second device comprises a step of receiving a timing advance report from the first device; A method wherein the timing advance report is triggered based on a collision between a downlink transmission based on information related to the semi-statically configured downlink resources and an uplink reception based on information related to the semi-statically configured uplink resources.

18. In the second 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 second device causes: To cause the first device to transmit information related to the semi-statically configured downlink resources; To transmit information related to uplink resources set semi-statically to the first device; and To receive a timing advance report from the first device, A second device, wherein the timing advance report is triggered based on a collision between a downlink transmission based on information related to the semi-statically configured downlink resources and an uplink reception based on information related to the semi-statically configured uplink resources.

19. In the processing 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 second device causes: To cause the first device to transmit information related to the semi-statically configured downlink resources; To transmit information related to uplink resources set semi-statically to the first device; and To receive a timing advance report from the first device, A processing device wherein the timing advance report is triggered based on a collision between a downlink transmission based on information related to the semi-statically configured downlink resources and an uplink reception based on information related to the semi-statically configured uplink resources.

20. A non-transitory computer-readable storage medium that records commands, The above commands, when executed, cause the second device to: To cause the first device to transmit information related to the semi-statically configured downlink resources; To transmit information related to uplink resources set semi-statically to the first device; and To receive a timing advance report from the first device, A non-transitory computer-readable storage medium in which the timing advance report is triggered based on a collision between a downlink transmission based on information related to the semi-statically configured downlink resources and an uplink reception based on information related to the semi-statically configured uplink resources.

Images