Method and device for supporting half-duplex transmission mode in non-terrestrial network

Abstract

Provided are a method by which a device performs wireless communication, and a device supporting same. The device may: obtain information related to a first offset; obtain information related to a second offset; receive information related to a transmission resource; and determine a transmission interval that conflicts with the transmission resource. For example, the transmission interval may start before the first offset and end after the second offset from a reference resource related to the transmission resource.

Description

Method and device for supporting half-duplex transmission mode in non-terrestrial networks

[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: obtaining information related to a first offset; obtaining information related to a second offset; receiving information related to a transmission resource; and determining a transmission interval that conflicts with the transmission resource. For example, the transmission interval may start before the first offset and end after the second offset from a reference resource related to the transmission resource.

[0006] According to one embodiment of the present disclosure, a device may be provided. For example, the device may include at least one transceiver; at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, when executed by the at least one processor, may cause the device to: obtain information related to a first offset; obtain information related to a second offset; receive information related to a transmission resource; and determine a transmission interval that conflicts with the transmission resource. For example, the transmission interval may start before the first offset and end after the second offset from a reference resource related to the transmission resource.

[0007] According to one embodiment of the present disclosure, a processing device configured to control a device may be provided. For example, the processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the device to: obtain information related to a first offset; obtain information related to a second offset; receive information related to a transmission resource; and determine a transmission interval that conflicts with the transmission resource. For example, the transmission interval may start before the first offset and end after the second offset from a reference resource related to the transmission 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 device to: obtain information related to a first offset; obtain information related to a second offset; receive information related to a transmission resource; and determine a transmission interval that conflicts with the transmission resource. For example, the transmission interval may start before the first offset and end after the second offset from a reference resource related to the transmission resource.

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

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

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

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

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

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

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

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

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

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

[0019] FIG. 11 illustrates an example of a common TA (timing advance) and a terminal-specific TA according to one embodiment of the present disclosure.

[0020] Figure 12 shows an example of a collision due to TA mismatch.

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

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

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

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

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

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

[0027] FIG. 19 illustrates a mobile device according to an embodiment of the present disclosure.

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

[0029] 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."

[0030] 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."

[0031] 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.”

[0032] 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.”

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0058] 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), single carrier-FDMA (SC-FDMA) symbols (or Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) symbols).

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

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

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

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

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

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

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

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

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

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

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

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

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

[0072] - 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 key 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.

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

[0074] - Large-scale MIMO technology

[0075] - Hologram beamforming (HBF)

[0076] - Optical wireless technology

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

[0078] - Quantum communication

[0079] - Cell-free communication

[0080] - Integration of wireless information and power transmission

[0081] - Integration of wireless communication and sensing

[0082] - Integrated access and backhaul network

[0083] - Big data analysis

[0084] - Reconfigurable intelligent surface

[0085] - metaverse

[0086] - Block chain

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

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

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

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

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

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

[0093] 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), terminals capable of aerial communication (e.g., AAM), etc. For example, to improve coverage, etc., devices such as satellite networks, HIBS, terminals capable of aerial communication (e.g., AAM), etc. can act as relays. For example, AAMs can communicate with base stations, satellite networks, etc., and / or AAMs can communicate directly with terminals, other AAMs, etc.

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

[0095] 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:

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

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

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

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

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

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

[0102] FIG. 9 illustrates a procedure for performing 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.

[0103] Referring to FIG. 9, in step S910, the base station may schedule downlink transmission, such as frequency / time resources, transmission layers, downlink precoder, modulation and coding scheme (MCS), etc. For example, the base station may determine a beam for PDSCH transmission to the terminal.

[0104] In step S920, the terminal can receive DCI for downlink scheduling (e.g., including scheduling information of PDSCH) from the base station on the PDCCH.

[0105] For example, DCI format 1_0 or 1_1 may be used for downlink scheduling. For example, 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, zero power (ZP) CSI-RS trigger, antenna port(s), transmission configuration indication (TCI), sounding reference signal (SRS) request, demodulation reference signal (DMRS) sequence initialization.

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

[0107] For example, the TCI field can consist of 3 bits, and quasi co-location (QCL) for DMRS can be dynamically indicated by indicating up to 8 TCI states depending on the TCI field value.

[0108] In step S930, the terminal can receive downlink data from the base station on the PDSCH.

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

[0110] FIG. 10 illustrates a procedure for performing 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.

[0111] Referring to FIG. 10, in step S1010, the base station may schedule uplink transmission, such as frequency / time resources, transmission layers, uplink precoder, modulation and coding scheme (MCS), etc. For example, the base station may determine a beam for the terminal to transmit PUSCH.

[0112] In step S1020, the terminal can receive DCI for uplink scheduling (e.g., including scheduling information of PUSCH) from the base station on the PDCCH.

[0113] For example, DCI format 0_0 or 0_1 may be used for uplink scheduling. For example, DCI format 0_1 ​​may include the following information: identifier for DCI formats, supplementary uplink (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, and uplink shared channel (UL-SCH) indicator.

[0114] For example, the SRS resources configured within the SRS resource set 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}.

[0115] In step S1030, the terminal can transmit uplink data to the base station on PUSCH.

[0116] For example, if a terminal detects a PDCCH including DCI format 0_0 or 0_1, the terminal can transmit the corresponding PUSCH according to the instructions of the corresponding DCI. For example, two transmission methods, codebook-based transmission and non-codebook-based transmission, can be supported for PUSCH transmission.

[0117] For example, when the upper layer parameter 'txConfig' is set to 'codebook', the terminal may be configured for codebook-based transmission. On the other hand, 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, the PUSCH transmission may be based on a single antenna port.

[0118] FIG. 11 illustrates an example of a common timing advance (TA) and a terminal-specific TA 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.

[0119] Referring to FIG. 11, a terminal-specific TA can be acquired to compensate for transmission delay for a service link, and a common TA can be acquired to compensate for transmission delay between a reference point (RP) and a satellite.

[0120] For example, in an NTN-based communication system, a terminal can calculate a TA based on the terminal's global navigation satellite system (GNSS) capability (e.g., terminal position) and orbit-related upper layer parameters transmitted from a base station, and this is called a terminal-specific TA (N UE TA,adj ) can be referred to as a common TA. For example, if orbit-related upper layer parameters are not received from the base station, the terminal-specific TA can be set to 0. For example, a TA obtained based on common TA parameters (e.g., TACommon, TACommonDrift, and / or TACommonDriftVariation), which are upper layer parameters transmitted from the base station, can be referred to as a common TA (N common TA,adj ) can be referred to as a common TA parameter. For example, if the common TA parameter is not transmitted from the base station, the common TA can be set to 0. Accordingly, for example, in an NTN-based communication system, the overall TA value (T TA ) is "(N TA + N TA,offset + N common TA,adj + N UE TA,adj )*T c " can be obtained as, for example, N TA,offset may mean the TA offset value provided to the terminal for each serving cell, and N TA may mean a value obtained based on a timing advance command.

[0121] In embodiments of the present disclosure, the semi-duplex operation may include the following operations.

[0122] For example, a half-duplex (HD)-UE may not expect to detect a DCI format that schedules reception on a set of symbols and a DCI format that schedules transmission on any symbol in the set of symbols.

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

[0124] For example, an HD-UE may not expect to detect a DCI format that schedules transmission on any symbol in the set of symbols and a dedicated higher layer parameter that configures reception on a set of symbols.

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

[0126] For example, for PUCCH, PUSCH with higher layer configuration versus DCI format indicated CSI-RS, PDSCH, T from the last symbol of PDCCH reception for DCI format proc,2 If there is a first symbol of UL transmission within, the terminal may not cancel the UL transmission; otherwise, the terminal may cancel the UL transmission.

[0127] For example, for the upper layer configured SRS vs. DCI format indicated CSI-RS, PDSCH, T from the last symbol of PDCCH reception for the DCI format proc,2 SRS transmissions within this period may not be canceled, and SRS transmissions of the remaining remaining symbols may be canceled.

[0128] For example, T proc,2 is d 2,1Assuming =1, it can be a PUSCH preparation time for UE processing capability 1, and μ can correspond to the SCS setting of the PDCCH carrying the DCI format and the smallest SCS setting among the SCS settings of the SRS, PUCCH, and PUSCH.

[0129] For example, simultaneous reception of dedicated upper layer parameters configuring a set of Type-0 / 0A / 1 / 2-PDCCH CSS sets and transmissions on a set of symbols may not be expected.

[0130] For example, in case of presence of SSBs indicated in DL BWP by higher layer configured PUSCH, PUCCH vs. NonCellDefiningSSB or by ServingCellConfigCommon or ssb-PositionInBurst in SIB1, PUSCH, PUCCH transmissions may be omitted if TX-RX switching time period is not guaranteed before the next earliest SSB, and / or PUSCH, PUCCH transmissions may be omitted if RX-TX switching time period is not guaranteed after the previous latest SSB.

[0131] For example, in the case of the presence of an SSB in a DL BWP indicated by a higher layer configured SRS vs. NonCellDefiningSSB or by ServingCellConfigCommon or by ssb-PositionInBurst in SIB1, the SRS of a symbol that is not before the TX-RX switching time period from the next earliest SSB may not be transmitted, and / or the SRS of a symbol that is not after the RX-TX switching time period from the previous latest SSB may not be transmitted.

[0132] For example, in case of presence of SSB in DL BWP indicated by NonCellDefiningSSB in PDCCH order based PRACH, PUSCH, PUCCH or ServingCellConfigCommon or ssb-PositionInBurst in SIB1, if any symbol of the symbol duration of SSB overlaps with UL transmission, the UL transmission may be omitted.

[0133] For example, in case of the presence of SSB in DL BWP indicated by SRS to NonCellDefiningSSB or by ServingCellConfigCommon or by ssb-PositionInBurst in SIB1, SRS may not be transmitted in the symbol duration of SSB.

[0134] For example, in case of reception of higher layer triggered PRACH or MsgA PUSCH versus PDCCH, PDSCH, CSI-RS, DL PRS, presence of SSB indicated by NonCellDefiningSSB or in ServingCellConfigCommon or in DL BWP by ssb-PositionInBurst in SIB1, if symbol duration overlaps, it may be UE implementation, and if TX-RX or RX-TX switching period is not guaranteed, it may be UE implementation.

[0135] Recently, in the field of communications, the introduction of a non-terrestrial network (NTN) that utilizes satellites as network nodes is being actively discussed. Satellites that support the NTN can be classified according to their flight orbits and characteristics, such as geostationary earth orbit (GEO), medium earth orbit (MEO), and low earth orbit (LEO), and generally have very high satellite altitudes. Here, the NTN can service a reduced capability (RedCap) terminal and / or an enhanced reduced capability (eRedCap) terminal that supports a half-duplex frequency division duplexing (HD-FDD) transmission scheme. Here, a terminal that supports the half-duplex transmission scheme cannot perform DL reception and UL transmission simultaneously, and therefore, it is necessary to define rules for the 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). Here, the DL / UL collision handling rule for a terminal operating in a half-duplex transmission mode in the NTN needs 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.

[0136] For example, in NTN communication, since the propagation delay is large and variable, it may be difficult for the base station to determine the exact TA of the terminal, and / or if the terminal autonomously applies the TA, the terminal may perform transmission in a time interval other than the uplink time interval (e.g., uplink slot, uplink subframe, uplink TTI, etc.) expected by the base station. In this case, for example, if the uplink transmission overlaps with the downlink time interval, a collision may occur. Fig. 12 shows an example of a collision due to TA mismatch. Referring to Fig. 12, if the TAs match between the terminal and the base station, the uplink transmission by the terminal in time interval #A may not collide with the downlink time interval of the base station. On the other hand, if the TAs do not match between the terminal and the base station, the uplink transmission by the terminal in time interval #B may collide with the downlink time interval of the base station (e.g., time interval #C in Fig. 12).

[0137] Hereinafter, in the present disclosure, from the viewpoint of DL / UL collision handling rules, a transmission method of a terminal operating in a half-duplex transmission mode in NTN and a device supporting the same are proposed.

[0138] [Selecting DL / UL Conflict Resource Determination Criteria]

[0139] [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, when the base station (or network) and / or the terminal recognizes a colliding DL / UL resource, the colliding DL / UL resource can be recognized in one or more of the following ways according to a (pre-)configured and / or agreed upon method between the base station (or network) and the terminal.

[0140] (1) First method: A (potential) UL transmission interval that may collide (assuming a TA (timing advance) corresponding to a specific range) can be derived based on DL. For example, for the specific DL resource / slot, a (potential) UL transmission interval that may collide (assuming a TA corresponding to a specific range) may mean a UL resource interval that starts at a time point / symbol to which a first (time) offset is applied compared to a UL resource / slot (hereinafter, a reference UL resource / slot) having the same time index as the DL resource / slot, and ends at a time point / symbol to which a second (time) offset is applied compared to the reference UL resource / slot.

[0141] (2) Second method: A (potential) DL transmission interval that may collide (assuming a TA (timing advance) corresponding to a specific range) can be derived based on UL. For example, for the specific UL resource / slot, a (potential) DL transmission interval that may collide (assuming a TA corresponding to a specific range) may mean a DL resource interval that starts at a time point / symbol that is ahead of a DL resource / slot (hereinafter, a reference DL resource / slot) having the same time index as the UL resource / slot by a first (time) offset, and ends at a time point / symbol that is behind the reference UL resource / slot by a second (time) offset.

[0142] Here, for example, the first (time) offset and / or the second (time) offset may be a (pre-)agreed and / or set value between the base station (or network) and the terminal. Here, for example, the first (time) offset and / or the second (time) offset may be composed of one or more elements, one of which may include a (common) TA.

[0143] For example, in a non-terrestrial network according to an 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.

[0144] 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 is a value that is mutually recognized through parameters and calculation formulas shared between the base station (or network) and the terminal, and the (UE) TA may be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). 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 may have different values.

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

[0146] Accordingly, 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 the base station (or network) and / or the terminal recognize a colliding DL / UL resource, the colliding DL / UL resource can be recognized by assuming a TA corresponding to a specific range according to a (pre-)configured and / or (pre-)promised manner between the base station (or network) and the terminal. For example, when the base station (or network) and / or the terminal determines a UL resource / slot that may collide with a (specific) DL resource / slot, the base station (or network) and / or the terminal can recognize a UL resource section that starts at a time point / symbol to which a first (time) offset is applied relative to a UL resource / slot (hereinafter, a reference UL resource / slot) having the same time index as the (specific) DL resource / slot, and ends at a time point / symbol to which a second (time) offset is applied relative to the reference UL resource / slot, as a potential collision section. Alternatively, for example, when a base station (or network) and / or a terminal determines a DL resource / slot that may collide with a (specific) UL resource / slot, the base station (or network) and / or the terminal may recognize a DL resource section that starts at a time point / symbol to which a first (time) offset is applied compared to a DL resource / slot (hereinafter, a reference DL resource / slot) having the same time index as the (specific) UL resource / slot, and ends at a time point / symbol to which a second (time) offset is applied compared to the reference DL resource / slot, as a potential collision section.

[0147] The proposed method of the present disclosure has the advantage of enabling a common understanding of (potential) DL / UL collision resource(s) even when the TA values ​​recognized by the base station (or network) and the terminal in a non-terrestrial network are different. This allows the base station (or network) and the terminal to have the same understanding and / or expectations regarding the target and / or result of the DL / UL collision rule.

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

[0149] [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, when the base station (or network) configures / indicates a (dynamically scheduled and / or semi-statically configured) DL (or UL) resource to the terminal, whether the DL (or UL) resource is a resource to be prioritized over the (dynamically scheduled and / or semi-statically configured) UL (or DL) resource can also be configured / indicated. Here, for example, the DL resource can include a PDCCH and / or a PDSCH and / or a CSI-RS. Here, for example, the UL resource can include a PUCCH and / or a PUSCH and / or an SRS and / or a PRACH.

[0150] 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 may perform DL reception and / or UL transmission with priority according to a DL / UL collision handling rule agreed upon / set in advance with the base station, or may determine it as an error case depending on the terminal implementation.

[0151] Here, for example, in the uplink of a non-terrestrial network, the terminal may 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 is a value that is mutually recognized through parameters and calculation formulas shared between the base station (or network) and the terminal, and the (UE) TA may be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). 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 may have different values, which may result in cases where mutual recognition of DL / UL collision resources is different.

[0152] Here, for example, due to the application of the above (UE) TA, a DL / UL collision may occur between a base station (or network) and a terminal in a non-terrestrial network, even in cases where scheduling could have been avoided in the past. For example, according to the conventional DL / UL collision handling rule, if a dynamically scheduled DL reception and a dynamically scheduled UL transmission collide, the terminal expects the base station (or network) to not create such a situation and regards it as an error case. However, in a non-terrestrial network, the base station (or network) cannot accurately know the DL / UL collision resources from the terminal's perspective, and thus the above situation may occur.

[0153] Accordingly, 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 the base station (or network) configures / indicates a (dynamically scheduled and / or semi-statically configured) DL (or UL) resource to the terminal, whether the DL (or UL) resource is a resource to be prioritized over the (dynamically scheduled and / or semi-statically configured) UL (or DL) resource can also be configured / indicated.

[0154] According to the proposed method of the present disclosure, when an unintended DL / UL collision occurs due to differences in the TA values ​​recognized between a base station (or network) and a terminal in a non-terrestrial network, there is an advantage in that reception / transmission of one of DL and UL can be given priority based on the same understanding according to a (pre-) agreement and / or (pre-)set method between the base station (or network) and the terminal.

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

[0156] [Determining Priority Between DL / UL Conflicting Resources]

[0157] [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, the terminal can derive a collision-prone (potential) UL transmission interval (hereinafter, the first UL collision interval) (assuming a timing advance (TA) corresponding to a specific range) for a configured and / or scheduled DL reception resource / slot (hereinafter, the first DL transmission) (e.g., PDSCH). In this case, for example, if there is at least one configured and / or scheduled UL transmission resource / slot (hereinafter, the first UL transmission) within the first UL collision interval, the terminal can determine which transmission will be given priority between the first DL transmission and the first UL transmission(s) (within the first UL collision interval) as follows.

[0158] (1) If at least one first UL transmission and / or all first UL transmissions (within the first UL collision period) have a higher priority than the first DL transmission, the first UL transmission may be given priority (within the first UL collision period).

[0159] (2) In other cases, the first DL transmission may be given priority.

[0160] Here, for example, for the first DL transmission and the first UL transmission, there can only be cases where one has a higher or lower priority than the other. Here, for example, for the specific DL resource / slot, a (potential) UL transmission interval that can collide (assuming a TA corresponding to a specific range) may mean a UL resource interval that starts at a time point / symbol to which a first (time) offset is applied compared to a UL resource / slot (hereinafter, a reference UL resource / slot) having the same time index as the DL resource / slot, and ends at a time point / symbol to which a second (time) offset is applied compared to the reference UL resource / slot. Here, for example, the first (time) offset and / or the second (time) offset may be a value that is (pre-)agreed and / or set between the base station (or network) and the terminal. Here, for example, the first (time) offset and / or the second (time) offset may be composed of one or more elements, one of which may include a (common) TA. Here, for example, the priority may be based on a (pre-) agreement and / or (pre-)configuration between the base station (or network) and the terminal. Here, for example, the base station (or network) may (pre-) agree and / or configure / instruct the terminal as to whether to perform the operation and / or which operation to perform.

[0161] 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 may perform DL reception and / or UL transmission with priority according to a DL / UL collision handling rule agreed upon / set in advance with the base station, or may determine it as an error case depending on the terminal implementation.

[0162] Here, for example, in the uplink of a non-terrestrial network, the terminal may 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 is a value that is mutually recognized through parameters and calculation formulas shared between the base station (or network) and the terminal, and the (UE) TA may be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). 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 may have different values, which may result in cases where mutual recognition of DL / UL collision resources is different.

[0163] Here, for example, due to the application of the (UE) TA, etc., the base station (or network) and / or the terminal in the non-terrestrial network can recognize a series of UL resource / slot(s) that may collide with (a specific) DL resource / slot. For example, the terminal can derive a (potential) UL transmission interval (hereinafter, the first UL collision interval) that may collide (assuming a TA (timing advance) corresponding to a specific range) with respect to the configured and / or scheduled DL reception resource / slot (hereinafter, the first DL transmission) (e.g., PDSCH). Here, in order to support correct signal transmission and reception operation considering, for example, a half-duplex transmission mode, it is necessary to have a mutual agreement between the base station (or network) and / or the terminal on which transmission to give priority between the first DL transmission and the first UL transmission(s) (within the first UL collision interval).

[0164] Accordingly, in the present disclosure, if there is at least one UL transmission resource / slot (hereinafter referred to as the first UL transmission) set and / or scheduled within the first UL collision period, the terminal can determine which transmission to give priority to among the first DL transmission and the first UL transmission(s) (within the first UL collision period) as follows.

[0165] (1) If at least one first UL transmission and / or all first UL transmissions (within the first UL collision period) have a higher priority than the first DL transmission, the first UL transmission may be given priority (within the first UL collision period).

[0166] (2) In other cases, the first DL transmission may be given priority.

[0167] According to the proposed method of the present disclosure, when a base station (or network) and a terminal in a non-terrestrial network mutually recognize a UL transmission section that is potentially collided with a (specific) DL transmission section by reflecting TA uncertainty, there is an advantage in that the terminal's half-duplex mode operation can be smoothly supported based on a clear agreement on which transmission between the DL transmission and the UL transmission section to give priority to.

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

[0169] [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 terminal can derive a collision-prone (potential) DL transmission interval (hereinafter referred to as a first DL collision interval) (assuming a timing advance (TA) corresponding to a specific range) for a configured and / or scheduled UL transmission resource / slot (hereinafter referred to as a first UL transmission) (e.g., PUSCH). In this case, for example, if there is at least one configured and / or scheduled DL reception resource / slot (hereinafter referred to as a first DL transmission) within the first DL collision interval, the terminal can determine which transmission will be given priority between the first UL transmission and the first DL transmission(s) (within the first DL collision interval) as follows.

[0170] (1) If at least one 1st DL transmission and / or all 1st DL transmissions (within the 1st DL collision period) have a higher priority than the 1st UL transmission, the 1st DL transmission may be given priority (within the 1st DL collision period).

[0171] (2) In other cases, the first UL transmission may be given priority.

[0172] Here, for example, for the first DL transmission and the first UL transmission, there can only be cases where one has a higher or lower priority than the other. Here, for example, for the specific UL resource / slot, a (potential) DL transmission interval that can collide (assuming a TA corresponding to a specific range) may mean a DL resource interval that starts at a time point / symbol that is ahead of a DL resource / slot (hereinafter, a reference DL resource / slot) having the same time index as the UL resource / slot by a first (time) offset, and ends at a time point / symbol that is behind the reference UL resource / slot by a second (time) offset. Here, for example, the first (time) offset and / or the second (time) offset may be a value that is (pre-)agreed and / or set between the base station (or network) and the terminal. Here, for example, the first (time) offset and / or the second (time) offset may be composed of one or more elements, one of which may include a (common) TA. Here, for example, the priority may be based on a (pre-) agreement and / or (pre-)configuration between the base station (or network) and the terminal. Here, for example, the base station (or network) may (pre-) agree and / or configure / instruct the terminal as to whether to perform the operation and / or which operation to perform.

[0173] 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 may perform DL reception and / or UL transmission with priority according to a DL / UL collision handling rule agreed upon / set in advance with the base station, or may determine it as an error case depending on the terminal implementation.

[0174] Here, for example, in the uplink of a non-terrestrial network, the terminal may 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 is a value that is mutually recognized through parameters and calculation formulas shared between the base station (or network) and the terminal, and the (UE) TA may be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). 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 may have different values, which may result in cases where mutual recognition of DL / UL collision resources is different.

[0175] Here, for example, due to the application of the (UE) TA, etc., the base station (or network) and / or the terminal in the non-terrestrial network can recognize a series of DL resource / slot(s) that may collide with (a specific) UL resource / slot. For example, the terminal can derive a (potential) DL transmission interval (hereinafter, the first DL collision interval) that may collide (assuming a TA (Timing Advance) corresponding to a specific range) with respect to the configured and / or scheduled UL reception resource / slot (hereinafter, the first UL transmission) (e.g., PUSCH). Here, in order to support a correct signal transmission / reception operation considering, for example, a half-duplex transmission mode, it is necessary that there is a mutual agreement between the base station (or network) and / or the terminal on which transmission to give priority between the first UL transmission and the first DL transmission(s) (within the first DL collision interval).

[0176] Accordingly, in the present disclosure, if there is at least one DL reception resource / slot (hereinafter referred to as the first DL transmission) set and / or scheduled within the first DL collision period, the terminal can determine which transmission to give priority to among the first UL transmission and the first DL transmission(s) (within the first DL collision period) as follows.

[0177] (1) If at least one 1st DL transmission and / or all 1st DL transmissions (within the 1st DL collision period) have a higher priority than the 1st UL transmission, the 1st DL transmission may be given priority (within the 1st DL collision period).

[0178] (2) In other cases, the first UL transmission may be given priority.

[0179] According to the proposed method of the present disclosure, when a base station (or network) and a terminal in a non-terrestrial network mutually recognize a DL transmission section that is potentially collided with a (specific) UL transmission section by reflecting TA uncertainty, there is an advantage in that the terminal's half-duplex mode operation can be smoothly supported based on a clear agreement on which transmission between the DL transmission and the UL transmission section to give priority to.

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

[0181] [DL reception priority]

[0182] [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, the terminal can derive a collision-prone (potential) UL transmission interval (hereinafter, the first UL collision interval) (assuming a timing advance (TA) corresponding to a specific range) for a configured and / or scheduled DL reception resource / slot (hereinafter, the first DL transmission) (e.g., PDSCH). In this case, for example, if there is at least one configured and / or scheduled UL transmission resource / slot (hereinafter, the first UL transmission) within the first UL collision interval, the terminal can perform one or more of the following operations.

[0183] (1) First movement

[0184] For example, for a (specific) first UL transmission (within the first UL collision window) with the earliest transmission time and / or scheduling time, if the time interval between the end time / symbol of reception of configuration information and / or scheduling information for the first DL transmission (hereinafter, the first time point) and the start time / symbol of transmission of the first UL transmission (hereinafter, the second time point) is equal to or greater than T_PROC,2, the terminal may perform and / or expect (partial and / or complete) skipping of the first UL transmission (within the first UL collision window), and / or the terminal may perform and / or expect reception of the first DL transmission.

[0185] For example, if the above case does not apply, the terminal may not perform and / or expect (some and / or all) first UL transmission skipping (within the first UL collision period), and / or the terminal may not perform and / or expect first DL transmission reception.

[0186] (2) Second movement

[0187] For example, for at least one first UL transmission (within the first UL collision window), if the time interval between the end time / symbol of reception of configuration information and / or scheduling information for the first DL transmission (hereinafter, the first time point) and the start time / symbol of transmission of the first UL transmission (hereinafter, the second time point) is equal to or greater than T_PROC,2, the terminal may perform and / or expect (some and / or all) of the first UL transmissions (within the first UL collision window), and / or the terminal may perform and / or expect the reception of the first DL transmissions.

[0188] For example, if the above case does not apply, the terminal may not perform and / or expect (some and / or all) first UL transmission skipping (within the first UL collision period), and / or the terminal may not perform and / or expect first DL transmission reception.

[0189] (3) Third movement

[0190] For example, for all (within the first UL collision window) first UL transmissions, if the time interval between the end time / symbol of reception of configuration information and / or scheduling information for the first DL transmission (hereinafter referred to as the first time point) and the start time / symbol of transmission of the first UL transmission (hereinafter referred to as the second time point) is equal to or greater than T_PROC,2, the terminal may perform and / or expect (some and / or all) first UL transmission skipping (within the first UL collision window), and / or the terminal may perform and / or expect first DL transmission reception.

[0191] For example, if the above case does not apply, the terminal may not perform and / or expect (some and / or all) first UL transmission skipping (within the first UL collision period), and / or the terminal may not perform and / or expect first DL transmission reception.

[0192] (4) 4th movement

[0193] For example, the terminal may perform and / or expect to skip (some and / or all) the first UL transmission (within the first UL collision window), and / or the terminal may perform and / or expect to receive the first DL transmission.

[0194] Here, for example, for the specific DL resource / slot, a colliding (potential) UL transmission interval (assuming a TA corresponding to a specific range) may mean a UL resource interval whose starting point is a time point / symbol to which a first (time) offset is applied compared to a UL resource / slot (hereinafter, a reference UL resource / slot) having the same time index as the DL resource / slot, and whose ending point is a time point / symbol to which a second (time) offset is applied compared to the reference UL resource / slot. Here, for example, the first (time) offset and / or the second (time) offset may be a value (in advance) agreed upon and / or set between the base station (or the network) and the terminal. Here, for example, the first (time) offset and / or the second (time) offset may be composed of one or more elements, one of which may include a (common) TA. Here, for example, the T_PROC,2 may refer to the processing time required for the terminal to prepare and / or cancel UL transmission. Here, for example, the operation may be an operation when giving priority to the first DL transmission over the first UL transmission (within the first UL collision period). Here, for example, the base station (or network) may (in advance) promise and / or set / instruct the terminal whether to perform the operation and / or which operation to perform.

[0195] 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 may perform DL reception and / or UL transmission with priority according to a DL / UL collision handling rule agreed upon / set in advance with the base station, or may determine it as an error case depending on the terminal implementation.

[0196] Here, for example, in the uplink of a non-terrestrial network, the terminal may 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 is a value that is mutually recognized through parameters and calculation formulas shared between the base station (or network) and the terminal, and the (UE) TA may be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). 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 may have different values, which may result in cases where mutual recognition of DL / UL collision resources is different.

[0197] Here, for example, due to the application of the (UE) TA, etc., the base station (or network) and / or the terminal in the non-terrestrial network may recognize a series of UL resource / slot(s) that may collide with (specific) DL resources / slots. For example, the terminal may derive a (potential) UL transmission interval (hereinafter, the first UL collision interval) that may collide (assuming a TA (timing advance) corresponding to a specific range) with respect to the configured and / or scheduled DL reception resource / slot (hereinafter, the first DL transmission) (e.g., PDSCH). Here, for example, depending on the characteristics of the message and / or the scheduling type, etc., there may occur a case where the first DL transmission is given priority over the first UL transmission (within the first UL collision interval).

[0198] Accordingly, 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 derive a collision-prone (potential) UL transmission interval (hereinafter, the first UL collision interval) (assuming a timing advance (TA) corresponding to a specific range) for a configured and / or scheduled DL reception resource / slot (hereinafter, the first DL transmission) (e.g., PDSCH). In this case, for example, if there is at least one configured and / or scheduled UL transmission resource / slot (hereinafter, the first UL transmission) within the first UL collision interval, the terminal can perform one or more of the following operations.

[0199] (1) First movement

[0200] For example, for a (specific) first UL transmission (within the first UL collision window) with the earliest transmission time and / or scheduling time, if the time interval between the end time / symbol of reception of configuration information and / or scheduling information for the first DL transmission (hereinafter, the first time point) and the start time / symbol of transmission of the first UL transmission (hereinafter, the second time point) is equal to or greater than T_PROC,2, the terminal may perform and / or expect (partial and / or complete) skipping of the first UL transmission (within the first UL collision window), and / or the terminal may perform and / or expect reception of the first DL transmission.

[0201] For example, if the above case does not apply, the terminal may not perform and / or expect (some and / or all) first UL transmission skipping (within the first UL collision period), and / or the terminal may not perform and / or expect first DL transmission reception.

[0202] (2) Second movement

[0203] For example, for at least one first UL transmission (within the first UL collision window), if the time interval between the end time / symbol of reception of configuration information and / or scheduling information for the first DL transmission (hereinafter, the first time point) and the start time / symbol of transmission of the first UL transmission (hereinafter, the second time point) is equal to or greater than T_PROC,2, the terminal may perform and / or expect (some and / or all) of the first UL transmissions (within the first UL collision window), and / or the terminal may perform and / or expect the reception of the first DL transmissions.

[0204] For example, if the above case does not apply, the terminal may not perform and / or expect (some and / or all) first UL transmission skipping (within the first UL collision period), and / or the terminal may not perform and / or expect first DL transmission reception.

[0205] (3) Third movement

[0206] For example, for all (within the first UL collision window) first UL transmissions, if the time interval between the end time / symbol of reception of configuration information and / or scheduling information for the first DL transmission (hereinafter referred to as the first time point) and the start time / symbol of transmission of the first UL transmission (hereinafter referred to as the second time point) is equal to or greater than T_PROC,2, the terminal may perform and / or expect (some and / or all) first UL transmission skipping (within the first UL collision window), and / or the terminal may perform and / or expect first DL transmission reception.

[0207] For example, if the above case does not apply, the terminal may not perform and / or expect (some and / or all) first UL transmission skipping (within the first UL collision period), and / or the terminal may not perform and / or expect first DL transmission reception.

[0208] (4) 4th movement

[0209] For example, the terminal may perform and / or expect to skip (some and / or all) the first UL transmission (within the first UL collision window), and / or the terminal may perform and / or expect to receive the first DL transmission.

[0210] According to the proposed method of the present disclosure, when a base station (or network) and a terminal in a non-terrestrial network derive a potentially colliding UL transmission section for a (specific) DL transmission by reflecting TA uncertainty and want to give priority to the (specific) DL transmission, there is an advantage in that the terminal can perform DL reception priority by considering the potentially colliding UL transmission section and / or the computation time (e.g., T_PROC,2) required to prepare / cancel UL transmission. As a result, a correct signal transmission / reception process can be performed under the same understanding between the base station (or network) and the terminal in a DL / UL collision situation.

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

[0212] [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, the terminal can derive a collision-prone (potential) DL transmission interval (hereinafter, the first DL collision interval) (assuming a timing advance (TA) corresponding to a specific range) for a configured and / or scheduled UL transmission resource / slot (hereinafter, the first UL transmission) (e.g., PUSCH). In this case, for example, if there is at least one configured and / or scheduled DL reception resource / slot (hereinafter, the first DL transmission) within the first DL collision interval, the terminal can perform one or more of the following operations.

[0213] (1) First movement

[0214] For example, for a (specific) first DL transmission (within the first DL collision window) with the earliest transmission time and / or scheduling time, if the time interval between the end time / symbol of reception of configuration information and / or scheduling information for the first DL transmission (hereinafter, the first time point) and the start time / symbol of transmission of the first UL transmission (hereinafter, the second time point) is equal to or greater than T_PROC,2, the terminal may perform and / or expect UL transmission skipping for the first UL transmission, and / or the terminal may perform and / or expect reception of (partial and / or entire) first DL transmission (within the first DL collision window).

[0215] For example, if the above case does not apply, the terminal may not perform and / or expect transmission skipping for the first UL transmission, and / or the terminal may not perform and / or expect reception of (some and / or all) the first DL transmission (within the first DL collision period).

[0216] (2) Second movement

[0217] For example, for at least one first DL transmission (within the first DL collision window), if the time interval between the end time / symbol of reception of configuration information and / or scheduling information for the first DL transmission (hereinafter, the first time point) and the start time / symbol of transmission of the first UL transmission (hereinafter, the second time point) is equal to or greater than T_PROC,2, the terminal may perform and / or expect UL transmission skipping for the first UL transmission, and / or the terminal may perform and / or expect reception of (partial and / or entire) first DL transmission (within the first DL collision window).

[0218] For example, if the above case does not apply, the terminal may not perform and / or expect transmission skipping for the first UL transmission, and / or the terminal may not perform and / or expect reception of (some and / or all) the first DL transmission (within the first DL collision period).

[0219] (3) Third movement

[0220] For example, for all (within the first DL collision window) first DL transmissions, if the time interval between the end time / symbol of reception of configuration information and / or scheduling information for the first DL transmission (hereinafter, the first time point) and the start time / symbol of transmission of the first UL transmission (hereinafter, the second time point) is equal to or greater than T_PROC,2, the terminal may perform and / or expect UL transmission skipping for the first UL transmission, and / or the terminal may perform and / or expect reception of (partial and / or all) first DL transmissions (within the first DL collision window).

[0221] For example, if the above case does not apply, the terminal may not perform and / or expect transmission skipping for the first UL transmission, and / or the terminal may not perform and / or expect reception of (some and / or all) the first DL transmission (within the first DL collision period).

[0222] (4) 4th movement

[0223] For example, the terminal may perform and / or expect UL transmission skipping for the first UL transmission, and the terminal may perform and / or expect reception of (some and / or all) the first DL transmission (within the first DL collision window).

[0224] Here, for example, for the specific UL resource / slot, a colliding (potential) DL transmission interval (assuming a TA corresponding to a specific range) may mean a DL resource interval whose starting point is a time point / symbol that is ahead of a DL resource / slot (hereinafter, a reference DL resource / slot) having the same time index as the UL resource / slot by a first (time) offset, and whose ending point is a time point / symbol that is behind the reference UL resource / slot by a second (time) offset. Here, for example, the first (time) offset and / or the second (time) offset may be a value that is (pre-)agreed and / or set between the base station (or the network) and the terminal. Here, for example, the first (time) offset and / or the second (time) offset may be composed of one or more elements, one of which may include a (common) TA. Here, for example, the T_PROC,2 may refer to the processing time required for the terminal to prepare and / or cancel UL transmission. Here, for example, the operation may be an operation when giving priority to the first DL transmission over the first UL transmission (within the first DL collision period). Here, for example, the base station (or network) may (in advance) promise and / or set / instruct the terminal whether to perform the operation and / or which operation to perform.

[0225] 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 may perform DL reception and / or UL transmission with priority according to a DL / UL collision handling rule agreed upon / set in advance with the base station, or may determine it as an error case depending on the terminal implementation.

[0226] Here, for example, in the uplink of a non-terrestrial network, the terminal may 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 is a value that is mutually recognized through parameters and calculation formulas shared between the base station (or network) and the terminal, and the (UE) TA may be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). 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 may have different values, which may result in cases where mutual recognition of DL / UL collision resources is different.

[0227] Here, for example, due to the application of the (UE) TA, etc., the base station (or network) and / or the terminal in the non-terrestrial network may recognize a series of DL resource / slot(s) that may collide with (specific) UL resources / slots. For example, the terminal may derive a (potential) DL transmission interval (hereinafter, the first DL collision interval) that may collide (assuming a TA (timing advance) corresponding to a specific range) with respect to the configured and / or scheduled UL reception resource / slot (hereinafter, the first UL transmission) (e.g., PUSCH). Here, for example, depending on the characteristics of the message and / or the scheduling type, etc., there may occur a case where the first DL transmission (within the first DL collision interval) is given priority over the first UL transmission.

[0228] Accordingly, 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 derive a collision-prone (potential) DL transmission interval (hereinafter, the first DL collision interval) (assuming a timing advance (TA) corresponding to a specific range) for a configured and / or scheduled UL transmission resource / slot (hereinafter, the first UL transmission) (e.g., PUSCH). In this case, for example, if there is at least one configured and / or scheduled DL reception resource / slot (hereinafter, the first DL transmission) within the first DL collision interval, the terminal can perform one or more of the following operations.

[0229] (1) First movement

[0230] For example, for a (specific) first DL transmission (within the first DL collision window) with the earliest transmission time and / or scheduling time, if the time interval between the end time / symbol of reception of configuration information and / or scheduling information for the first DL transmission (hereinafter, the first time point) and the start time / symbol of transmission of the first UL transmission (hereinafter, the second time point) is equal to or greater than T_PROC,2, the terminal may perform and / or expect UL transmission skipping for the first UL transmission, and / or the terminal may perform and / or expect reception of (partial and / or entire) first DL transmission (within the first DL collision window).

[0231] For example, if the above case does not apply, the terminal may not perform and / or expect transmission skipping for the first UL transmission, and / or the terminal may not perform and / or expect reception of (some and / or all) the first DL transmission (within the first DL collision period).

[0232] (2) Second movement

[0233] For example, for at least one first DL transmission (within the first DL collision window), if the time interval between the end time / symbol of reception of configuration information and / or scheduling information for the first DL transmission (hereinafter, the first time point) and the start time / symbol of transmission of the first UL transmission (hereinafter, the second time point) is equal to or greater than T_PROC,2, the terminal may perform and / or expect UL transmission skipping for the first UL transmission, and / or the terminal may perform and / or expect reception of (partial and / or entire) first DL transmission (within the first DL collision window).

[0234] For example, if the above case does not apply, the terminal may not perform and / or expect transmission skipping for the first UL transmission, and / or the terminal may not perform and / or expect reception of (some and / or all) the first DL transmission (within the first DL collision period).

[0235] (3) Third movement

[0236] For example, for all (within the first DL collision window) first DL transmissions, if the time interval between the end time / symbol of reception of configuration information and / or scheduling information for the first DL transmission (hereinafter, the first time point) and the start time / symbol of transmission of the first UL transmission (hereinafter, the second time point) is equal to or greater than T_PROC,2, the terminal may perform and / or expect UL transmission skipping for the first UL transmission, and / or the terminal may perform and / or expect reception of (partial and / or all) first DL transmissions (within the first DL collision window).

[0237] For example, if the above case does not apply, the terminal may not perform and / or expect transmission skipping for the first UL transmission, and / or the terminal may not perform and / or expect reception of (some and / or all) the first DL transmission (within the first DL collision period).

[0238] (4) 4th movement

[0239] For example, the terminal may perform and / or expect UL transmission skipping for the first UL transmission, and / or the terminal may perform and / or expect reception of (partial and / or entire) the first DL transmission (within the first DL collision window).

[0240] According to the proposed method of the present disclosure, when a base station (or network) and a terminal in a non-terrestrial network derive a potentially colliding DL transmission section for a (specific) UL transmission by reflecting TA uncertainty and want to give priority to the DL transmission section, there is an advantage in that the terminal can perform DL reception priority by considering the computation time (e.g., T_PROC,2) required to prepare / cancel the potentially colliding DL transmission section and / or UL transmission. As a result, a correct signal transmission / reception process can be performed under the same understanding between the base station (or network) and the terminal in a DL / UL collision situation.

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

[0242] [UL transmission priority]

[0243] [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, the terminal can derive a collision-prone (potential) UL transmission interval (hereinafter, the first UL collision interval) (assuming a timing advance (TA) corresponding to a specific range) for a configured and / or scheduled DL reception resource / slot (hereinafter, the first DL transmission) (e.g., PDSCH). In this case, for example, if there is at least one configured and / or scheduled UL transmission resource / slot (hereinafter, the first UL transmission) within the first UL collision interval, the terminal can perform one or more of the following operations.

[0244] (1) First movement

[0245] For example, the terminal may perform and / or expect (some and / or all) of the first UL transmissions (within the first UL collision window), and / or the terminal may not perform and / or expect to receive the first DL transmissions.

[0246] Here, for example, for the specific DL resource / slot, a colliding (potential) UL transmission interval (assuming a TA corresponding to a specific range) may mean a UL resource interval whose starting point is a time point / symbol to which a first (time) offset is applied compared to a UL resource / slot (hereinafter, a reference UL resource / slot) having the same time index as the DL resource / slot, and whose ending point is a time point / symbol to which a second (time) offset is applied compared to the reference UL resource / slot. Here, for example, the first (time) offset and / or the second (time) offset may be a value (in advance) agreed upon and / or set between the base station (or the network) and the terminal. Here, for example, the first (time) offset and / or the second (time) offset may be composed of one or more elements, one of which may include a (common) TA. Here, for example, the above operation may be an operation when giving priority to the first UL transmission over the first DL transmission (within the first UL collision period). Here, for example, the base station (or network) may (in advance) promise and / or set / instruct the terminal as to whether to perform the above operation and / or which operation to perform.

[0247] 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 may perform DL reception and / or UL transmission with priority according to a DL / UL collision handling rule agreed upon / set in advance with the base station, or may determine it as an error case depending on the terminal implementation.

[0248] Here, for example, in the uplink of a non-terrestrial network, the terminal may 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 is a value that is mutually recognized through parameters and calculation formulas shared between the base station (or network) and the terminal, and the (UE) TA may be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). 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 may have different values, which may result in cases where mutual recognition of DL / UL collision resources is different.

[0249] Here, for example, due to the application of the (UE) TA, etc., the base station (or network) and / or the terminal in the non-terrestrial network may recognize a series of UL resource / slot(s) that may collide with (specific) DL resources / slots. For example, the terminal may derive a (potential) UL transmission interval (hereinafter, the first UL collision interval) that may collide (assuming a TA (timing advance) corresponding to a specific range) with respect to the configured and / or scheduled DL reception resource / slot (hereinafter, the first DL transmission) (e.g., PDSCH). Here, for example, depending on the characteristics of the message and / or the scheduling type, etc., there may occur a case where the first UL transmission (within the first UL collision interval) is given priority over the first DL transmission.

[0250] Accordingly, 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 derive a collision-prone (potential) UL transmission interval (hereinafter, the first UL collision interval) (assuming a timing advance (TA) corresponding to a specific range) for a configured and / or scheduled DL reception resource / slot (hereinafter, the first DL transmission) (e.g., PDSCH). In this case, for example, if there is at least one configured and / or scheduled UL transmission resource / slot (hereinafter, the first UL transmission) within the first UL collision interval, the terminal can perform one or more of the following operations.

[0251] (1) First movement

[0252] For example, the terminal may perform and / or expect (some and / or all) of the first UL transmissions (within the first UL collision window), and / or the terminal may not perform and / or expect to receive the first DL transmissions.

[0253] According to the proposed method of the present disclosure, when a base station (or network) and a terminal in a non-terrestrial network derive a potentially colliding UL transmission section for a (specific) DL transmission by reflecting TA uncertainty and want to prioritize the UL transmission section, there is an advantage in that the terminal can perform UL transmission priority by considering the potentially colliding UL transmission section. This allows the base station (or network) and the terminal to perform a correct signal transmission and reception process under the same understanding in a DL / UL collision situation.

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

[0255] [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 derive a collision-prone (potential) DL transmission interval (hereinafter, the first DL collision interval) (assuming a timing advance (TA) corresponding to a specific range) for a configured and / or scheduled UL transmission resource / slot (hereinafter, the first UL transmission) (e.g., PUSCH). In this case, for example, if there is at least one configured and / or scheduled DL reception resource / slot (hereinafter, the first DL transmission) within the first DL collision interval, the terminal can perform one or more of the following operations.

[0256] (1) First movement

[0257] For example, the terminal may perform and / or expect a first UL transmission, and / or the terminal may not perform and / or expect to receive (some and / or all) the first DL transmission (within the first DL collision window).

[0258] Here, for example, for the specific UL resource / slot, a colliding (potential) DL transmission interval (assuming a TA corresponding to a specific range) may mean a DL resource interval whose starting point is a time point / symbol that is ahead of a DL resource / slot (hereinafter, a reference DL resource / slot) having the same time index as the UL resource / slot by a first (time) offset, and whose ending point is a time point / symbol that is behind the reference UL resource / slot by a second (time) offset. Here, for example, the first (time) offset and / or the second (time) offset may be a value that is (pre-)agreed and / or set between the base station (or the network) and the terminal. Here, for example, the first (time) offset and / or the second (time) offset may be composed of one or more elements, one of which may include a (common) TA. Here, for example, the operation may be an operation when giving priority to the first UL transmission over the first DL transmission (within the first DL collision period). Here, for example, the base station (or network) may (in advance) promise and / or set / instruct the terminal as to whether to perform the operation and / or which operation to perform.

[0259] 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 may perform DL reception and / or UL transmission with priority according to a DL / UL collision handling rule agreed upon / set in advance with the base station, or may determine it as an error case depending on the terminal implementation.

[0260] Here, for example, in the uplink of a non-terrestrial network, the terminal may 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 is a value that is mutually recognized through parameters and calculation formulas shared between the base station (or network) and the terminal, and the (UE) TA may be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). 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 may have different values, which may result in cases where mutual recognition of DL / UL collision resources is different.

[0261] Here, for example, due to the application of the (UE) TA, etc., the base station (or network) and / or the terminal in the non-terrestrial network may recognize a series of DL resource / slot(s) that may collide with (a specific) UL resource / slot. For example, the terminal may derive a (potential) DL transmission interval (hereinafter, the first DL collision interval) that may collide (assuming a TA (timing advance) corresponding to a specific range) with respect to the configured and / or scheduled UL reception resource / slot (hereinafter, the first UL transmission) (e.g., PUSCH). Here, for example, depending on the characteristics of the message and / or the scheduling type, etc., there may occur a case where the first UL transmission is given priority over the first DL transmission (within the first DL collision interval).

[0262] Accordingly, 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 derive a collision-prone (potential) DL transmission interval (hereinafter, the first DL collision interval) (assuming a timing advance (TA) corresponding to a specific range) for a configured and / or scheduled UL transmission resource / slot (hereinafter, the first UL transmission) (e.g., PUSCH). In this case, for example, if there is at least one configured and / or scheduled DL reception resource / slot (hereinafter, the first DL transmission) within the first DL collision interval, the terminal can perform one or more of the following operations.

[0263] (1) First movement

[0264] For example, the terminal may perform and / or expect a first UL transmission, and / or the terminal may not perform and / or expect to receive (some and / or all) the first DL transmission (within the first DL collision window).

[0265] According to the proposed method of the present disclosure, in a non-terrestrial network, when a base station (or network) and a terminal derive a potentially colliding DL transmission section for a (specific) UL transmission by reflecting TA uncertainty and want to prioritize the UL transmission, there is an advantage in that the terminal can perform UL transmission priority by considering the potentially colliding DL transmission section. This allows the base station (or network) and the terminal to perform a correct signal transmission and reception process under the same understanding in a DL / UL collision situation.

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

[0267] [Exception handling behavior]

[0268] [Proposal #09] 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) can set / instruct the terminal to have an (expected) TA range (hereinafter referred to as a first TA range). In this case, the terminal can apply different DL / UL collision handling rules when the TA (hereinafter referred to as a second TA) it has calculated is within the first TA range and when it is not. For example, the terminal can calculate the TA when data to be transmitted is generated in the buffer and / or when transmission is scheduled. For example, the terminal can apply the DL / UL collision handling rules as follows.

[0269] (1) If the second TA exists within the scope of the first TA

[0270] DL / UL conflict resource determination and conflict handling rules are applied based on the 1st TA scope.

[0271] (2) If the second TA does not exist within the scope of the first TA.

[0272] A. Option 1: Determine DL / UL conflict resources based on the second TA and apply conflict handling rules.

[0273] B. Option 2: Omit transmissions for UL resources (dynamically scheduled and / or semi-statically configured).

[0274] Here, for example, (specific) uplink physical channels / resources that have been (preliminarily) agreed upon / established between the base station (or network) and the terminal may be excluded from the UL transmission omission target. Here, for example, the base station (or network) may (preliminarily) agree upon and / or establish / instruct the terminal as to whether or not to perform the operation and / or which operation to perform.

[0275] 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 may perform DL reception and / or UL transmission with priority according to a DL / UL collision handling rule agreed upon / set in advance with the base station, or may determine it as an error case depending on the terminal implementation.

[0276] Here, for example, in the uplink of a non-terrestrial network, the terminal may 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 is a value that is mutually recognized through parameters and calculation formulas shared between the base station (or network) and the terminal, and the (UE) TA may be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). 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 may have different values, which may result in cases where mutual recognition of DL / UL collision resources is different.

[0277] Here, for example, in a non-terrestrial network, a base station (or network) and a terminal may (in advance) agree upon and / or set an (expected) TA range (hereinafter, referred to as the first TA range) between each other, and when performing DL / UL collision handling rules according to a half-duplex transmission mode, DL / UL collision resource determination and collision handling rules may be applied based on the first TA range. Here, for example, if the actual TA (hereinafter, referred to as the second TA) calculated by the terminal is outside the first TA range, there may be cases where the DL / UL collision resource determinations between the base station (or network) and the terminal are different from each other. In this case, the terminal may omit UL transmission (until a TA report) or determine whether to perform UL transmission after determining DL / UL collision resources based on its second TA in a BE (best effort) manner.

[0278] According to the proposed method of the present disclosure, when a base station (or network) and a terminal in a non-terrestrial network apply DL / UL collision handling rules based on a TA range, reflecting TA uncertainty, exception handling for terminal operations in cases where the actual TA falls outside the TA range can be supported. This has the advantage of clarifying terminal operations in the above-described exceptional circumstances.

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

[0280] [Proposal #10] 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) can set / indicate an (expected) TA range (hereinafter, the first TA range) to the terminal. In this case, for example, if the TA calculated by the terminal (hereinafter, the second TA) is outside the TA range, the terminal can perform one or more of the following actions.

[0281] (1) TA mismatch event reporting

[0282] (2) SR transmission for TA reporting

[0283] (3) TA Report Trigger and / or TA Report

[0284] Here, for example, the base station (or network) may (preliminarily) promise and / or set / instruct the terminal to perform the above operation. Here, for example, the TA mismatch event report may include a report on an event in which the second TA is outside the range of the first TA.

[0285] 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 may perform DL reception and / or UL transmission with priority according to a DL / UL collision handling rule agreed upon / set in advance with the base station, or may determine it as an error case depending on the terminal implementation.

[0286] Here, for example, in the uplink of a non-terrestrial network, the terminal may 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 is a value that is mutually recognized through parameters and calculation formulas shared between the base station (or network) and the terminal, and the (UE) TA may be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). 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 may have different values, which may result in cases where mutual recognition of DL / UL collision resources is different.

[0287] Here, for example, in a non-terrestrial network, a base station (or network) can (pre-)promise and / or set / instruct information about an (expected) TA range (hereinafter, the first TA range) to a terminal operating in a half-duplex mode. Here, for example, the base station (or network) and / or the terminal can recognize (potential) DL / UL collision resources in the same manner, assuming the first TA range. Here, for example, if the TA (hereinafter, the second TA) calculated by the terminal is out of the first TA range set / instructed by the base station (or network), the DL / UL collision resource recognition method between the base station (or network) and the terminal based on the first TA range may no longer be valid. Here, for example, the terminal may need to quickly report the situation to the base station (or network). For example, the terminal may report the event itself, or may naturally perform an SR transmission for TA reporting and / or a TA reporting tree and / or a TA reporting operation according to the occurrence of the event.

[0288] According to the proposed method of the present disclosure, when a base station (or network) and a terminal manage DL / UL collision resources based on an (expected) TA range reflecting TA uncertainty in a non-terrestrial network, there is an advantage of supporting rapid situational awareness at the base station (or network) level in the case where the actual TA of the terminal is outside the (expected) TA range. Through this, the base station (or network) can update the (expected) TA range again to equally understand the (potential) DL / UL collision resources between the base station (or network) and the terminal, and support performing the correct transmission / reception process accordingly.

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

[0290] [Proposal #11] 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, if a collision occurs between a dynamically scheduled transmission (hereinafter referred to as a first transmission) and a semi-statically configured transmission (hereinafter referred to as a second transmission), the priorities between the first transmission and the second transmission may be applied differently depending on the order between the scheduling for the first transmission and the activation setting / indication / timing for the second transmission. For example, the terminal may apply the priorities as follows.

[0291] (1) If activation for the second transmission is set / instructed / started prior to scheduling for the first transmission, the first transmission / reception may be given priority.

[0292] (2) If activation for the second transmission is set / instructed / started after scheduling for the first transmission, the second transmission / reception may be given priority.

[0293] Here, for example, the base station (or network) can (pre-)promise and / or set / instruct the terminal whether to perform the above operation. Here, for example, the base station (or network) can (pre-)promise and / or (pre-)set to the terminal priority information between the first transmission and the second transmission to be applied according to the order between the scheduling for the first transmission and the activation trigger for the second transmission. Here, for example, the first transmission and the second transmission can be DL transmission and UL transmission, or UL transmission and DL transmission, respectively.

[0294] 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 may perform DL reception and / or UL transmission with priority according to a DL / UL collision handling rule agreed upon / set in advance with the base station, or may determine it as an error case depending on the terminal implementation.

[0295] 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 is a value that is mutually recognized through parameters and calculation formulas shared between the base station (or network) and the terminal, and the (UE) TA may be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network) end. Here, for example, the (common) TA and / or the (UE) TA may have a very large value. For example, in the case of a LEO satellite, considering an RTT (round trip time) delay of about several tens of milliseconds, the total TA size may correspond to about several tens of slot(s). Here, the base station (or network) may set an additional offset (hereinafter referred to as K_offset) to the timing when scheduling the uplink in consideration of the TA.

[0296] Here, for example, according to the conventional DL / UL collision handling rule according to the half-duplex transmission mode, a dynamically scheduled transmission resource (hereinafter, the first transmission resource) may be given priority over a semi-statically configured transmission resource (hereinafter, the second transmission resource). Here, for example, the DL / UL collision handling rule may be based on the assumption that the base station (or the network) already knows of the existence of the semi-statically configured second transmission resource. Here, for example, considering that the uplink scheduling timing (e.g., K_offset) may be very long in the non-terrestrial network, unlike the conventional case, activation for the second transmission resource may be set / instructed after the first transmission resource is dynamically scheduled.

[0297] Accordingly, 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, if a collision occurs between a dynamically scheduled UL transmission (hereinafter referred to as a first UL transmission) and a semi-statically configured DL transmission (hereinafter referred to as a first DL transmission), different priorities may be applied between the first UL transmission and the first DL transmission depending on the order between the scheduling of the first UL transmission and the activation trigger for the first DL transmission. For example, the terminal may give priority to the first UL transmission if the activation of the first DL transmission is set / indicated before the scheduling of the first UL transmission, and may give priority to the first DL transmission if the activation of the first DL transmission is set / indicated after the scheduling of the first UL transmission.

[0298] According to the proposed method of the present disclosure, collision handling rules can be defined between dynamically scheduled transmissions and semi-statically configured transmissions, taking into account the relatively long uplink scheduling timing in non-terrestrial networks. Specifically, this has the advantage of allowing the base station (or network) to prioritize more preferred / intended transmissions by comparing the scheduling timing with the activation time for semi-statically configured resources.

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

[0300] [Proposal #12] In a non-terrestrial network, when a base station (or network) and / or a terminal can perform DL / UL collision handling rules according to a half-duplex transmission mode, for UL transmission (e.g., PUSCH and / or PUCCH) to which DM-RS bundling and / or time domain window (TDW) is applied, the base station (or network) may promise / configure / instruct the terminal to give priority to the UL transmission over other (specific) DL reception, or promise / configure / instruct not to perform (specific) DL reception during the UL transmission. Here, for example, SSB reception may be excluded from the (specific) DL reception. Here, for example, the DM-RS bundling may mean an operation of performing channel estimation by utilizing DM-RS resource(s) between repeated UL transmissions. Here, for example, the TDW may mean a (time) interval during which the terminal guarantees phase continuity and / or power consistency.

[0301] 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 may perform DL reception and / or UL transmission with priority according to a DL / UL collision handling rule agreed upon / set in advance with the base station, or may determine it as an error case depending on the terminal implementation.

[0302] Here, for example, in the uplink of a non-terrestrial network, the terminal may 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 is a value that is mutually recognized through parameters and calculation formulas shared between the base station (or network) and the terminal, and the (UE) TA may be a value that the terminal voluntarily adjusts and that is unknown to the base station (or network). 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 may have different values, which may result in cases where mutual recognition of DL / UL collision resources is different.

[0303] Here, for example, considering the wide coverage area of ​​the non-terrestrial network, the terminal may support a DM-RS bundling function that utilizes the DM-RS resource(s) between repeated transmissions in the joint channel estimation process for the entire repeated transmission during uplink transmission. Here, for example, the terminal may support a time domain window (TDW), which is a period that ensures phase continuity and / or power consistency from a signal transmission perspective. Here, for example, when the terminal receives DL, etc. within the uplink transmission period, the terminal may not be able to maintain phase continuity and / or power consistency, and thus the (actual) TDW may end at the point where the UL transmission and DL reception collide. Here, for example, due to (UE) TA, etc., in the non-terrestrial network, the base station (or network) may not be able to accurately determine the point in time when the UL transmission and DL reception collide from the terminal's perspective, and as a result, the (actual) TDW period may be recognized differently between the base station (or network) and the terminal. In the above case, the base station (or network) may perform joint channel estimation by utilizing DM-RSs within the wrong section, which may result in degradation of uplink reception performance.

[0304] Accordingly, 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, for UL transmission (e.g., PUSCH and / or PUCCH) to which DM-RS bundling and / or time domain window (TDW) are applied, the base station (or network) can promise / configure / instruct the terminal to give priority to the UL transmission over other (specific) DL reception, or promise / configure / instruct not to receive the (specific) DL during the UL transmission.

[0305] According to the proposed method of the present disclosure, there is an effect of preventing possible TDW fragmentation from occurring for UL transmissions to which DM-RS bundling and / or TDW is applied, thereby preventing cases where a base station (or network) incorrectly recognizes the (actual) TDW section of a terminal from occurring.

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

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

[0308] Referring to FIG. 13, in step S1310, the device may obtain information related to a first offset. In step S1320, the device may obtain information related to a second offset. In step S1330, the device may receive information related to a transmission resource. In step S1340, the device may determine a transmission interval that conflicts with the transmission resource. For example, the transmission interval may start before the first offset and end after the second offset from a reference resource related to the transmission resource.

[0309] Additionally, for example, the device may receive information about whether the transmission resource is a priority resource.

[0310] For example, the transmission resource may be a resource for downlink transmission. For example, the reference resource may be a resource for uplink transmission having the same time index as the transmission resource. For example, based on the priority of at least one uplink transmission within the transmission interval being higher than the priority of the downlink transmission, the uplink transmission may be prioritized over the downlink transmission within the transmission interval. For example, based on (i) the downlink transmission being prioritized over the uplink transmission, and (ii) the time interval between the reception of configuration information or scheduling information for the downlink transmission and the fastest uplink transmission within the transmission interval being greater than or equal to the processing time, the uplink transmission may be omitted within the transmission interval. For example, based on (i) the downlink transmission being prioritized over the uplink transmission, and (ii) the time interval between the reception of configuration information or scheduling information for the downlink transmission and the fastest uplink transmission within the transmission interval being less than the processing time, the uplink transmission may be performed within the transmission interval.

[0311] For example, the transmission resource may be a resource for uplink transmission. For example, the reference resource may be a resource for downlink transmission having the same time index as the transmission resource. For example, based on the priority of at least one downlink transmission within the transmission interval being higher than the priority of the uplink transmission, the downlink transmission may be prioritized over the uplink transmission within the transmission interval. For example, based on (i) the downlink transmission being prioritized over the uplink transmission, and (ii) the time interval between the uplink transmission and the reception of configuration information or scheduling information for the fastest downlink transmission within the transmission interval being greater than or equal to the processing time, the uplink transmission may be omitted within the transmission interval. For example, based on (i) the downlink transmission being prioritized over the uplink transmission, and (ii) the time interval between the uplink transmission and the reception of configuration information or scheduling information for the fastest downlink transmission within the transmission interval being less than the processing time, the uplink transmission may be performed within the transmission interval.

[0312] Additionally, for example, the device may receive information related to a timing advance range. Additionally, for example, the device may determine a timing advance. For example, a priority rule for conflicts between uplink and downlink may be applied differently based on whether the timing advance is within the timing advance range. For example, if a default priority rule is defined, if the timing advance is outside the timing advance range, the established priority rule may be released, and the default priority rule may be automatically applied. For example, if a default priority rule is defined, if the timing advance is within the timing advance range, the established priority rule may be applied. For example, based on whether the timing advance is within the timing advance range, a determination of whether a conflict exists between uplink and downlink may be performed based on the timing advance range. For example, based on whether the timing advance is outside the timing advance range, a determination as to whether there is a collision between the uplink and downlink can be performed based on the timing advance.

[0313] The proposed method can be applied to devices according to various embodiments of the present disclosure. First, the processor (102) of the device (100) can obtain information related to a first offset. Then, the processor (102) of the device (100) can obtain information related to a second offset. Then, the processor (102) of the device (100) can control the transceiver (106) to receive information related to a transmission resource. Then, the processor (102) of the device (100) can determine a transmission interval that conflicts with the transmission resource. For example, the transmission interval can start before the first offset and end after the second offset from a reference resource related to the transmission resource.

[0314] According to one embodiment of the present disclosure, a device may be provided. For example, the device may include at least one transceiver; at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, when executed by the at least one processor, may cause the device to: obtain information related to a first offset; obtain information related to a second offset; receive information related to a transmission resource; and determine a transmission interval that conflicts with the transmission resource. For example, the transmission interval may start before the first offset and end after the second offset from a reference resource related to the transmission resource.

[0315] According to one embodiment of the present disclosure, a processing device configured to control a device may be provided. For example, the processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the device to: obtain information related to a first offset; obtain information related to a second offset; receive information related to a transmission resource; and determine a transmission interval that conflicts with the transmission resource. For example, the transmission interval may start before the first offset and end after the second offset from a reference resource related to the transmission resource.

[0316] According to one embodiment of the present disclosure, a non-transitory computer-readable storage medium having instructions recorded thereon may be provided. For example, the instructions, when executed, may cause a device to: obtain information related to a first offset; obtain information related to a second offset; receive information related to a transmission resource; and determine a transmission interval that conflicts with the transmission resource. For example, the transmission interval may start before the first offset and end after the second offset from a reference resource related to the transmission resource.

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

[0318] Referring to FIG. 14, in step S1410, the base station may obtain information related to the first offset. In step S1420, the base station may obtain information related to the second offset. In step S1430, the base station may transmit information related to a transmission resource. In step S1440, the base station may determine a transmission interval that conflicts with the transmission resource. For example, the transmission interval may start before the first offset and end after the second offset from a reference resource related to the transmission resource.

[0319] Additionally, for example, the base station may transmit information about whether the transmission resource is a priority resource.

[0320] For example, the transmission resource may be a resource for downlink transmission. For example, the reference resource may be a resource for uplink transmission having the same time index as the transmission resource. For example, based on the priority of at least one uplink transmission within the transmission interval being higher than the priority of the downlink transmission, the uplink transmission may be prioritized over the downlink transmission within the transmission interval. For example, based on (i) the downlink transmission being prioritized over the uplink transmission, and (ii) the time interval between the reception of configuration information or scheduling information for the downlink transmission and the fastest uplink transmission within the transmission interval being greater than or equal to the processing time, the uplink transmission may be omitted within the transmission interval. For example, based on (i) the downlink transmission being prioritized over the uplink transmission, and (ii) the time interval between the reception of configuration information or scheduling information for the downlink transmission and the fastest uplink transmission within the transmission interval being less than the processing time, the uplink transmission may be performed within the transmission interval.

[0321] For example, the transmission resource may be a resource for uplink transmission. For example, the reference resource may be a resource for downlink transmission having the same time index as the transmission resource. For example, based on the priority of at least one downlink transmission within the transmission interval being higher than the priority of the uplink transmission, the downlink transmission may be prioritized over the uplink transmission within the transmission interval. For example, based on (i) the downlink transmission being prioritized over the uplink transmission, and (ii) the time interval between the uplink transmission and the reception of configuration information or scheduling information for the fastest downlink transmission within the transmission interval being greater than or equal to the processing time, the uplink transmission may be omitted within the transmission interval. For example, based on (i) the downlink transmission being prioritized over the uplink transmission, and (ii) the time interval between the uplink transmission and the reception of configuration information or scheduling information for the fastest downlink transmission within the transmission interval being less than the processing time, the uplink transmission may be performed within the transmission interval.

[0322] Additionally, for example, the base station may transmit information related to the timing advance range. For example, prioritization rules for uplink and downlink collisions may be applied differently based on whether the timing advance determined by the device is within the timing advance range. For example, if a default prioritization rule is defined, if the timing advance is outside the timing advance range, the established prioritization rule may be released, and the default prioritization rule may be automatically applied. For example, if a default prioritization rule is defined, if the timing advance is within the timing advance range, the established prioritization rule may be applied. For example, based on whether the timing advance determined by the device is within the timing advance range, the determination of whether there is a collision between the uplink and downlink may be performed based on the timing advance range. For example, based on whether the timing advance determined by the device is outside the timing advance range, a determination as to whether there is a collision between the uplink and downlink can be performed based on the timing advance.

[0323] The proposed method can be applied to devices according to various embodiments of the present disclosure. First, the processor (202) of the base station (200) can obtain information related to a first offset. Then, the processor (202) of the base station (200) can obtain information related to a second offset. Then, the processor (202) of the base station (200) can control the transceiver (206) to transmit information related to a transmission resource. Then, the processor (202) of the base station (200) can determine a transmission interval that conflicts with the transmission resource. For example, the transmission interval can start before the first offset and end after the second offset from a reference resource related to the transmission resource.

[0324] According to one embodiment of the present disclosure, a base station may be provided. For example, the base station may include at least one transceiver; at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the base station to: obtain information related to a first offset; obtain information related to a second offset; transmit information related to a transmission resource; and determine a transmission interval that conflicts with the transmission resource. For example, the transmission interval may start before the first offset and end after the second offset from a reference resource related to the transmission resource.

[0325] According to one embodiment of the present disclosure, a processing device configured to control a base station may be provided. For example, the processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions. For example, the instructions, based on execution by the at least one processor, may cause the base station to: obtain information related to a first offset; obtain information related to a second offset; transmit information related to a transmission resource; and determine a transmission interval that conflicts with the transmission resource. For example, the transmission interval may start before the first offset and end after the second offset from a reference resource related to the transmission resource.

[0326] According to one embodiment of the present disclosure, a non-transitory computer-readable storage medium having instructions recorded thereon may be provided. For example, the instructions, when executed, may cause a base station to: obtain information related to a first offset; obtain information related to a second offset; transmit information related to a transmission resource; and determine a transmission interval that conflicts with the transmission resource. For example, the transmission interval may start before the first offset and end after the second offset from a reference resource related to the transmission resource.

[0327] According to various embodiments of the present disclosure, even when the TA values ​​recognized between a base station (or network) and a terminal in a non-terrestrial network differ, the understanding of (potential) DL / UL collision resource(s) can be aligned. This allows for efficient prioritization procedures for DL / UL collisions in a non-terrestrial network.

[0328] 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 embodiments may be omitted.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0351] Figure 18 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 15). The embodiment of Figure 18 may be combined with various embodiments of the present disclosure.

[0352] Referring to FIG. 18, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 16 and may be composed of various elements, components, units / units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional elements (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. 16. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 16. 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).

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

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

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

[0356] FIG. 19 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. 19 may be combined with various embodiments of the present disclosure.

[0357] Referring to FIG. 19, 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. 18, respectively.

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

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

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

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

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

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

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

Claims

1. In the method, A step of obtaining information related to the first offset; Step of obtaining information related to the second offset; A step of receiving information related to a transmission resource; and A step of determining a transmission section that conflicts with the above transmission resource; including: A method wherein the transmission interval starts before the first offset and ends after the second offset from a reference resource related to the transmission resource.

2. In paragraph 1, A method further comprising: receiving information on whether the above transmission resource is a priority resource; 3. In paragraph 1, A method wherein the above transmission resources are resources for downlink transmission.

4. In paragraph 3, A method wherein the above reference resource is a resource for uplink transmission having the same time index as the above transmission resource.

5. In paragraph 3, A method in which uplink transmission is given priority over downlink transmission within the transmission interval based on the priority of at least one uplink transmission within the transmission interval being higher than the priority of the downlink transmission.

6. In paragraph 3, A method wherein (i) the downlink transmission is given priority over the uplink transmission, and (ii) the uplink transmission is omitted within the transmission interval based on a time interval between the reception of configuration information or scheduling information for the downlink transmission and the fastest uplink transmission within the transmission interval being greater than or equal to the processing time.

7. In paragraph 3, A method wherein (i) the downlink transmission is given priority over the uplink transmission, and (ii) the uplink transmission is performed within the transmission interval based on a time interval between the reception of configuration information or scheduling information for the downlink transmission and the fastest uplink transmission within the transmission interval being less than a processing time.

8. In paragraph 1, A method wherein the above transmission resources are resources for uplink transmission.

9. In paragraph 8, A method wherein the above reference resource is a resource for downlink transmission having the same time index as the above transmission resource.

10. In paragraph 8, A method in which downlink transmission is given priority over uplink transmission within the transmission interval based on the priority of at least one downlink transmission within the transmission interval being higher than the priority of the uplink transmission.

11. In paragraph 8, A method wherein (i) downlink transmission is given priority over said uplink transmission, and (ii) said uplink transmission is omitted within said transmission interval based on a time interval between said uplink transmission and the reception of configuration information or scheduling information for the fastest downlink transmission within said transmission interval being greater than or equal to a processing time.

12. In paragraph 8, A method wherein (i) downlink transmission is given priority over the uplink transmission, and (ii) the uplink transmission is performed within the transmission interval based on a time interval between the uplink transmission and the reception of configuration information or scheduling information for the fastest downlink transmission within the transmission interval being less than a processing time.

13. In paragraph 1, A step of receiving information related to a timing advance range; and A step of determining a timing advance; further comprising: A method wherein priority rules for collisions between uplink and downlink are applied differently based on whether the timing advance is within the timing advance range.

14. In the device, At least one transmitter / receiver; at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said device causes: Obtain information related to the first offset; Obtain information related to the second offset; To receive information related to transmission resources; and Determine the transmission section that conflicts with the above transmission resource, A device wherein the transmission interval starts before the first offset and ends after the second offset from a reference resource related to the transmission resource.

15. In a processing device set to control a device, at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said device causes: Obtain information related to the first offset; Obtain information related to the second offset; To receive information related to transmission resources; and Determine the transmission section that conflicts with the above transmission resource, A processing device wherein the transmission interval starts before the first offset and ends after the second offset from the reference resource associated with the transmission resource.

16. A non-transitory computer-readable storage medium that records commands, The above commands, when executed, cause the device to: Obtain information related to the first offset; Obtain information related to the second offset; To receive information related to transmission resources; and Determine the transmission section that conflicts with the above transmission resource, A non-transitory computer-readable storage medium, wherein the transmission interval starts before the first offset and ends after the second offset from the reference resource associated with the transmission resource.

17. In the method, A step of obtaining information related to the first offset; Step of obtaining information related to the second offset; A step of transmitting information related to a transmission resource; and A step of determining a transmission section that conflicts with the above transmission resource; including: A method wherein the transmission interval starts before the first offset and ends after the second offset from a reference resource related to the transmission resource.

18. At the base station, At least one transmitter / receiver; at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said base station: Obtain information related to the first offset; Obtain information related to the second offset; To transmit information related to the transmission resource; and Determine the transmission section that conflicts with the above transmission resource, A base station, wherein the transmission interval starts before the first offset and ends after the second offset from the reference resource related to the transmission resource.

19. In a processing device set to control a base station, at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said base station: Obtain information related to the first offset; Obtain information related to the second offset; To transmit information related to the transmission resource; and Determine the transmission section that conflicts with the above transmission resource, A processing device wherein the transmission interval starts before the first offset and ends after the second offset from the reference resource associated with the transmission resource.

20. A non-transitory computer-readable storage medium that records commands, The above commands, when executed, cause the base station to: Obtain information related to the first offset; Obtain information related to the second offset; To transmit information related to the transmission resource; and Determine the transmission section that conflicts with the above transmission resource, A non-transitory computer-readable storage medium, wherein the transmission interval starts before the first offset and ends after the second offset from the reference resource associated with the transmission resource.

Images