Transmission / reception method of terminal in non-terrestrial network, and device supporting same

Abstract

Provided are a method for performing wireless communication, and a device supporting same. The method may comprise the steps in which: a first device obtains an uplink (UL)-prioritizing downlink-uplink (DL-UL) priority rule; and the first device monitors a common search space (CSS) on the basis of the UL-prioritizing DL-UL priority rule. For example, a DL may be prioritized in a time resource in which the CSS was monitored on the basis of the UL-prioritizing DL-UL priority rule.

Description

Method for transmitting and receiving terminals in a non-terrestrial network and device supporting the same

[0001] The present disclosure relates to non-terrestrial networks. More specifically, the present disclosure relates to a method for transmitting and receiving a terminal in a non-terrestrial network and an apparatus supporting the same.

[0002] 5G NR is a successor technology to LTE (long term evolution) and is a new clean-slate type mobile communication system with characteristics such as high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, ranging from low frequency bands below 1 GHz to mid-frequency bands from 1 GHz to 10 GHz, and high frequency (millimeter wave) bands above 24 GHz.

[0003] The 6G (wireless communication) system aims for (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) reduced energy consumption of battery-free IoT (internet of things) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be in four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity, and the 6G system can satisfy requirements such as those shown in Table 1 below. For example, Table 1 may represent an example of the requirements for 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 Fully

[0005] According to one embodiment of the present disclosure, a method may be provided. For example, the method may include the step of a first device obtaining a DL-UL (downlink-uplink) priority rule that prioritizes a UL (uplink); and the step of the first device monitoring a CSS (common search space) based on the DL-UL priority rule that prioritizes the UL. For example, in a time resource where the CSS is monitored based on the DL-UL priority rule that prioritizes the UL, the DL may be prioritized.

[0006] According to one embodiment of the present disclosure, a first device may be provided. For example, the first device may include at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, based on the instructions being executed by the at least one processor, the first device may: obtain a DL-UL (downlink-uplink) priority rule that prioritizes the UL (uplink); and monitor a CSS (common search space) based on the DL-UL priority rule that prioritizes the UL. For example, in a time resource where the CSS is monitored based on the DL-UL priority rule that prioritizes the UL, the DL may be prioritized.

[0007] According to one embodiment of the present disclosure, a processing device (configured to control a first device) may be provided. For example, the processing device may include at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, based on the instructions executed by the at least one processor, the first device may: obtain a DL-UL (downlink-uplink) priority rule that prioritizes the UL (uplink); and monitor a CSS (common search space) based on the DL-UL priority rule that prioritizes the UL. For example, in a time resource where the CSS is monitored based on the DL-UL priority rule that prioritizes the UL, the DL may be prioritized.

[0008] According to one embodiment of the present disclosure, a non-transient computer-readable storage medium recording instructions may be provided. For example, when the instructions are executed, the first device may: obtain a DL-UL (downlink-uplink) priority rule that prioritizes the UL (uplink); and monitor a CSS (common search space) based on the DL-UL priority rule that prioritizes the UL. For example, in a time resource where the CSS is monitored based on the DL-UL priority rule that prioritizes the UL, the DL may be prioritized.

[0009] According to one embodiment of the present disclosure, a method may be provided. For example, the method may include the step of a second device transmitting a DL-UL (downlink-uplink) priority rule that prioritizes a UL (uplink) to a first device; and the step of the second device monitoring a UL from the first device based on the DL-UL priority rule that prioritizes the UL. For example, in a time resource where a CSS is monitored based on the DL-UL priority rule that prioritizes the UL, the DL may be prioritized.

[0010] According to one embodiment of the present disclosure, a second device may be provided. For example, the second device may include at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, based on the instructions being executed by the at least one processor, the second device may: transmit to the first device a DL-UL (downlink-uplink) priority rule that prioritizes the UL (uplink); and monitor the UL from the first device based on the DL-UL priority rule that prioritizes the UL. For example, in a time resource where the CSS is monitored based on the DL-UL priority rule that prioritizes the UL, the DL may be prioritized.

[0011] According to one embodiment of the present disclosure, a processing device (configured to control a second device) may be provided. For example, the processing device may include at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, based on the instructions executed by the at least one processor, the second device may: transmit to the first device a DL-UL (downlink-uplink) priority rule that prioritizes the UL (uplink); and monitor the UL from the first device based on the DL-UL priority rule that prioritizes the UL. For example, in a time resource where the CSS is monitored based on the DL-UL priority rule that prioritizes the UL, the DL may be prioritized.

[0012] According to one embodiment of the present disclosure, a non-transient computer-readable storage medium recording instructions may be provided. For example, when the instructions are executed, the second device may: transmit to the first device a DL-UL (downlink-uplink) priority rule that prioritizes the UL (uplink); and monitor the UL from the first device based on the DL-UL priority rule that prioritizes the UL. For example, in a time resource where the CSS is monitored based on the DL-UL priority rule that prioritizes the UL, the DL may be prioritized.

[0013] FIG. 1 illustrates a communication procedure between devices according to one embodiment of the present disclosure.

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

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

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

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

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

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

[0020] FIG. 8 shows a non-terrestrial network scenario according to one embodiment of the present disclosure.

[0021] FIG. 9 shows a non-terrestrial network scenario according to one embodiment of the present disclosure.

[0022] FIG. 10 shows examples of an NTN access network according to one embodiment of the present disclosure.

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

[0024] FIG. 12 illustrates an example of possible options for an NTN architecture according to one embodiment of the present disclosure.

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

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

[0027] FIG. 15 shows an example of NTN according to one embodiment of the present disclosure.

[0028] FIG. 16 is K according to one embodiment of the present disclosure. offset and K macIt shows an example of.

[0029] FIG. 17 shows examples of UE-specific TA and common TA according to one embodiment of the present disclosure.

[0030] FIG. 18 shows an example of an uplink-downlink timing relationship according to one embodiment of the present disclosure.

[0031] FIG. 19 shows an example of TA mismatch within a beam / cell according to one embodiment of the present disclosure.

[0032] FIG. 20 shows an example of an orbital parameter orbital format according to one embodiment of the present disclosure.

[0033] FIG. 21 shows an HD collision in NTN according to one embodiment of the present disclosure.

[0034] FIG. 22 shows an example of the relationship between a reported TA and an actual TA according to one embodiment of the present disclosure.

[0035] FIG. 23 shows an example of guard time and TA according to one embodiment of the present disclosure.

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

[0037] FIG. 25 illustrates an example related to DL-UL (downlink-uplink) priority rules and CSS exception handling behavior according to one embodiment of the present disclosure.

[0038] FIG. 26 illustrates an example related to DL-UL (downlink-uplink) priority rules and CSS exception handling behavior according to one embodiment of the present disclosure.

[0039] FIG. 27 illustrates a procedure performed by a first device according to one embodiment of the present disclosure.

[0040] FIG. 28 illustrates a procedure performed by a second device according to one embodiment of the present disclosure.

[0041] FIG. 29 shows a communication system (1) according to one embodiment of the present disclosure.

[0042] FIG. 30 shows a wireless device according to one embodiment of the present disclosure.

[0043] FIG. 31 shows a signal processing circuit for a transmission signal according to one embodiment of the present disclosure.

[0044] FIG. 32 shows a wireless device according to one embodiment of the present disclosure.

[0045] FIG. 33 shows a portable device according to one embodiment of the present disclosure.

[0046] In the present disclosure, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in the present disclosure, "A or B" may be interpreted as "A and / or B." For example, in the present disclosure, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0047] A slash ( / ) or a comma used in the present disclosure 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."

[0048] 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 as synonymous with "at least one of A and B."

[0049] Additionally, in the present disclosure, "at least one of A, B and C" may 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" may mean "at least one of A, B and C."

[0050] 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, the "control information" of the present disclosure is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (e.g., PDCCH)," "PDCCH" may be proposed as an example of "control information."

[0051] In the following explanation, 'when, if, in case of' can be replaced with 'based on'.

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

[0053] In the present disclosure, a higher layer parameter may be a parameter that is set for the terminal, pre-set, or pre-defined. For example, a base station or a network may transmit the higher layer parameter to the terminal. For example, the higher layer parameter may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0054] In the present disclosure, "configured or defined" may be interpreted as being configured or pre-configured to a device through pre-defined signaling from a base station or network (e.g., SIB, MAC, RRC, DCI (downlink control information), etc.). In the present disclosure, "configured or defined" may be interpreted as being configured or pre-configured to a device through pre-defined signaling from another device (e.g., MAC, RRC, SCI (sidelink control information), control information signaled between devices, etc.). In the present disclosure, "configured or defined" may be interpreted as being pre-configured to a device.

[0055] In the present disclosure, 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.

[0056] The technology proposed in this 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.

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

[0058] FIG. 1 illustrates a communication procedure between devices 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, suggestions, methods, and / or operations of the embodiments may be omitted.

[0059] Referring to FIG. 1, in step S101, the first device and the second device can perform synchronization. For example, the first device may be a terminal and / or at least one of the devices proposed in the present disclosure. For example, the second device may 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 may perform an initial cell search operation. For example, the first device may detect at least one synchronization signal transmitted according to a rule predefined by the second device. Here, for example, the synchronization signal may include a plurality of synchronization signals (e.g., primary synchronization signal, secondary synchronization signal, etc.) classified according to structure or use. 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., cell identifier).

[0060] In step S103, the first device may obtain system information transmitted by the second device. For example, the system information may include information related to the attributes, characteristics, and / or capabilities of the second device that are necessary 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 the system information prior to receiving the system information. For example, the request and provision of the system information may be performed after a random access procedure described later.

[0061] In step S105, the first device and the second device may perform a random access procedure. For example, the first device may transmit and / or receive at least one message for the random access procedure (e.g., random access preamble, random access response message, etc.) based on information related to the 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 may transmit a preamble (e.g., Msg1) through the random access channel, and the first device may receive a random access response message (e.g., Msg2). The first device may transmit a message (e.g., Msg3) containing 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 may receive a message (e.g., Msg4) for contention resolution and / or connection establishment. For example, Msg1 and Msg3 can be transmitted and received as a single message (e.g., MsgA), and / or Msg2 and Msg4 can be transmitted and received as a single message (e.g., MsgB).

[0062] 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 controlling the connection (e.g., a radio resource control (RRC) layer), a layer handling mapping between a logical channel and a transmission channel (e.g., a media access control (MAC) layer), and a layer handling a physical channel (e.g., a physical (PHY) layer). For example, the first device and the second device may perform at least one of signaling to establish a connection, signaling to determine settings related to communication, and / or signaling to indicate allocated resources. For example, the control information may be signaled / transmitted through 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.

[0063] 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 data based on signaling of control information and transmit and / or receive it. 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, antenna-specific waveform demodulation, signal placement considering layer mapping, constellation demapping, descrambling, and / or channel decoding.

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

[0065] FIG. 2 illustrates a radio protocol architecture according to one 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 said embodiment may be omitted. For example, FIG. 2(a) may represent a radio protocol stack in the user plane for uplink communication or downlink communication, and FIG. 2(b) may represent a radio protocol stack in the control plane for uplink communication or downlink communication. For example, FIG. 2(c) may represent a radio protocol stack in the user plane for device-to-device communication, and FIG. 2(d) may represent a radio protocol stack in the control plane for device-to-device communication.

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

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

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

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

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

[0071] For example, the establishment of an RB can mean the process of defining the characteristics of the wireless protocol layer and channel to provide specific services, and setting each specific parameter and method of operation. For example, an RB can be divided into two types: an SRB (signaling radio bearer) and a DRB (data radio bearer). For example, an SRB can be used as a channel to transmit RRC messages in the control plane, and a DRB can be used as a channel to transmit user data in the user plane.

[0072] For example, if an RRC connection is established between the RRC layer of the terminal and the RRC layer of the base station, the terminal is in the RRC_CONNECTED state, and if not, it may be in the RRC_IDLE state. For example, in the case of NR, an additional RRC_INACTIVE state is defined, and a terminal in the RRC_INACTIVE state maintains a connection with the core network while releasing the connection with the base station.

[0073] For example, a downlink transmission channel may include at least one of a broadcast channel (BCH) that transmits system information and / or a shared channel (SCH) that transmits user traffic or control messages. For example, traffic or control messages for a downlink multicast or broadcast service may be transmitted via a downlink SCH or via a separate multicast channel (MCH). Meanwhile, an uplink transmission channel may include at least one of a random access channel (RACH) that transmits initial control messages and / or a shared channel (SCH) that transmits user traffic or control messages. For example, a logical channel located above the 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).

[0074] FIG. 3 shows the structure of a wireless frame according to one 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.

[0075] Referring to FIG. 3, radio frames may be used, for example, 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 contain 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 by subcarrier spacing (SCS). For example, each slot may contain 12 or 14 OFDM(A) symbols according to a cyclic prefix (CP).

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

[0077] Table 2 below shows the number of symbols per slot (N) according to 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.

[0078] CP Type SCS (15*2 u )N slot symb N frame,u slot N subframe,u slotNormal CP 15kHz (u=0) 1410 130kHz (u=1) 1420 260kHz (u=2) 1440 4120kHz (u=3) 1480 8240kHz (u=4) 14160 16 Extended CP 60kHz (u=2) 1240 4

[0079] For example, OFDM(A) numerology (e.g., SCS, CP length, etc.) may be configured differently among multiple cells merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., subframe, slot, or TTI (transmit time interval)) composed of the same number of symbols may be configured differently among the merged cells. For example, in the present disclosure, time resources such as subframes, slots, TTI, etc. may be referred to as time units.

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

[0081] FIG. 4 shows a slot structure of a frame according to one 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, suggestions, methods, and / or operations of the embodiments may be omitted.

[0082] 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 a single numerology (e.g., SCS, CP length, etc.). For example, a carrier may include up to N BWPs (where N is a positive integer). For example, data communication may be performed through an active BWP. For example, each element may be referred to as a resource element (RE) in a resource grid and may be mapped to a single complex symbol.

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

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

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

[0086] Referring to FIG. 5, for example, a common resource block (CRB) may be a numbered carrier resource block from one end of the 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 the resource block grid.

[0087] For example, BWP is point A, offset from point A (N start BWP ) and bandwidth (N size BWP It can be set by ). For example, point A may be an external reference point of the PRB of a carrier where the subcarrier 0 of all numerologies (e.g., all numerologies supported by the network in that carrier) are aligned. For example, offset may be the PRB interval between the lowest subcarrier in a given numerology and point A. For example, bandwidth may be the number of PRBs in a given numerology.

[0088] FIG. 6 illustrates a communication structure that can be provided in a 6G system according to one 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 said embodiments may be omitted.

[0089] As core implementation technologies for 6G systems, technologies such as artificial intelligence (AI), THz (Terahertz) communication, optical wireless technology, free space optical transmission (FSO) backhaul networks, large-scale 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.

[0090] - Artificial Intelligence: Introducing AI into communications can streamline and enhance real-time data transmission. AI can determine how complex target tasks are performed using numerous analyses. For example, AI can increase efficiency and reduce processing latency. Time-consuming tasks such as handover, network selection, and resource scheduling can be performed instantly using AI. AI can also play a significant role in M2M, machine-to-human, and human-to-machine communication. Furthermore, AI can enable rapid communication in Brain-Computer Interfaces (BCI). 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.

[0091] - THz Communication: Data transmission rates can be increased by expanding bandwidth. This can be achieved by using sub-THz communication with wide bandwidth and applying advanced large-scale MIMO technology. THz waves, also known as sub-millimeter radiation, generally refer to a frequency band between 0.1 THz and 10 THz with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz-300 GHz band range (Sub-THz band) is considered the primary portion of the THz band for cellular communication. Adding the Sub-THz band to the mmWave band increases 6G cellular communication capacity. Among the defined THz bands, the 300 GHz-3 THz band is located in the far-infrared (IR) frequency band. Although the 300 GHz-3 THz band is part of the optical band, it lies at the boundary of the optical band and immediately following the RF band. Therefore, this 300 GHz-3 THz band exhibits similarities to RF. Key characteristics of THz communication include (i) widely available bandwidth to support very high data transmission rates, and (ii) high path loss occurring at high frequencies (highly directional antennas are indispensable). The narrow beam width generated by highly directional antennas reduces interference. The small wavelength of THz signals allows a much larger number of antenna elements to be integrated into devices and BSs operating in this band. This enables the use of advanced adaptive array technologies that can overcome range limitations.

[0092] - Large-scale MIMO technology

[0093] - Hologram beamforming (HBF)

[0094] - Optical wireless technology

[0095] - Free Space Optical Transmission Backhaul Network (FSO backhaul network)

[0096] - Quantum communication

[0097] - Cell-free communication

[0098] - Integration of wireless information and power transmission

[0099] - Integration of wireless communication and sensing

[0100] - Integrated access and backhaul network

[0101] - Big data analysis

[0102] - Reconfigurable intelligent metasurface

[0103] - Metaverse

[0104] - blockchain

[0105] - 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 may include UAM, RAM, UAS, and UAVs (uncrewed aerial vehicles).

[0106] - Autonomous driving (self-driving): V2X (vehicle to everything), a core element of building autonomous driving infrastructure, refers to technologies that enable vehicles to communicate and share with various elements on the road to perform autonomous driving, such as wireless communication between vehicles (vehicle to vehicle, V2V) and between vehicles and infrastructure (vehicle to infrastructure, V2I).

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

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

[0109] - Reconfigurable Intelligent Surface (RIS): An RIS can be used to manipulate and enhance signal propagation in a wireless communication environment. For example, an 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 instance, an RIS can improve signal reception by controlling the path, phase, and / or strength of the propagating signal. For instance, power consumption can be very low because power is consumed only for controlling the phase and amplitude of the small antennas. For instance, since an RIS can be reconfigured to suit various environments, it can meet diverse communication requirements and operate effectively in dynamic network environments.

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

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

[0112] FIG. 8 illustrates a non-terrestrial network scenario according to one embodiment of the present disclosure. FIG. 9 illustrates a non-terrestrial network scenario according to one embodiment of the present disclosure. The embodiments of FIG. 8 and 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.

[0113] FIG. 8 illustrates a non-terrestrial network scenario based on a transparent payload, and FIG. 9 illustrates a non-terrestrial network scenario based on a regenerative payload. For example, a non-terrestrial network may generally include the following elements.

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

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

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

[0117] - A satellite (or UAS platform) capable of implementing transparent or regenerated (including onboard processing) payloads. For example, the satellite (or UAS platform) can generate multiple beams across a given service area, typically defined by a line of sight. For example, the beam footprint may typically be elliptical. For example, the line of sight of the satellite (or UAS platform) may vary depending on the onboard antenna diagram and the minimum elevation angle. For example, for a transparent payload, radio frequency filtering, frequency conversion, and amplification may be performed. Thus, the repeating waveform signal in the payload may not be altered. For example, for a regenerated payload, radio frequency filtering, frequency conversion, and amplification, as well as demodulation / decoding, switching and / or routing, and coding / modulation may be performed. This can effectively be equivalent to equipping the satellite (or UAS platform) with all base station functions.

[0118] - Optionally, Inter-satellite Link (ISL)

[0119] - User equipment can be serviced by a satellite (or UAS platform) within the target service area.

[0120] FIG. 10 illustrates examples of an NTN access network according to one embodiment of the present disclosure. FIG. 10(a) illustrates an example of a transparent payload according to one embodiment of the present disclosure. FIG. 10(b) illustrates an example of a regenerated payload according to one embodiment of the present disclosure. An 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 said embodiments may be omitted.

[0121] Referring to FIG. 10(a), for example, the satellite / HAPS can perform only the role of a simple repeater, receive uplink signals from the UE and transmit them to the Gateway, and relay downlink signals generated at the Gateway back to the UE. Here, for example, communication between the UE and the satellite can use NR radio frequency f1, and communication between the satellite and the Gateway can use NR radio frequency f2. For example, the actual 5G radio access network (e.g., 5G RAN) function is deployed at the Gateway or ground base station (e.g., gNB) located on the ground and can be coupled with the 5G core network (e.g., 5G CN). Thus, for example, the satellite can operate as a simple transponder structure that transparently transmits signals at the physical layer level without performing separate signal processing functions. For example, the transparent payload of FIG. 10(a) may be related to the transparent payload of FIG. 8. For example, the transparent payload of Fig. 10(a) may be related to the NTN architecture discussed in 3GPP Rel-17 and Rel-18.

[0122] Referring to FIG. 10(b), for example, the satellite / HAPS itself may be equipped with 5G RAN functions and may possess payload processing capabilities that include base station functions, rather than being a simple repeater. For example, communication between the UE and the satellite may use NR radio frequency f1, and communication between the satellite and the gateway may use NR radio frequency f2. Here, for example, the gateway is connected to a 5G core network (e.g., 5G CN), and since the satellite can directly provide RAN functions to the UE, it can replace or supplement a ground base station (e.g., gNB). For example, since the satellite has a structure that transmits NR signals after receiving, demodulating, and processing them, rather than simply relaying them, more intelligent wireless resource control and quality of service management are possible. For example, the regeneration payload in FIG. 10(b) may be related to the regeneration payload in FIG. 9. For example, the replay payload of Fig. 10 (b) may be related to the NTN architecture that can be discussed in 3GPP Rel-19 and thereafter.

[0123] FIG. 11 illustrates an example of possible options for an NTN architecture according to one 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 said embodiment may be omitted.

[0124] Referring to FIG. 11, an NTN may be disclosed that features an access network servicing UEs based, for example, a ground-based gNB (satellite hub or gateway level) and a satellite / aerial carrying a bent pipe payload. In FIG. 11, for example, the satellite or aerial may relay “satellite-friendly” NR signals between the gNB and the UEs in a transparent manner. For example, the UE may communicate with the satellite via a radio interface (e.g., Uu), and the satellite may transmit the signal to a ground base station (e.g., gNB). For example, the gNB may perform the role of a 5G radio access network (e.g., RAN) and may be connected to a 5G / 6G core (e.g., 5GC / 6GC) via an NG interface (e.g., NGc, NGu). For example, 5GC / 6GC can be connected to an external data network through the N6 interface. Therefore, for example, in this structure, a satellite can extend the wireless section to mediate the connection between the UE and the ground base station, and subsequent procedures can operate in the same way as the existing 5G structure. For example, the NTN architecture of FIG. 11 can be related to the transparent payload of FIG. 10 (a).

[0125] FIG. 12 illustrates an example of possible options for an NTN architecture according to one embodiment of the present disclosure. The embodiment of FIG. 12 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiment may be omitted.

[0126] Referring to FIG. 12, an NTN may be disclosed that features an access network for servicing UEs based on, for example, a satellite / aerial equipped with a gNB. In FIG. 12, for example, the satellite or aerial may include all or part of a gNB for generating / receiving “satellite-friendly” NR signals for transmitting and receiving with UEs. For example, this may require sufficient on-board processing power to deploy gNB or relay node functions. For example, a UE may communicate with the satellite via a radio interface (e.g., Uu), and the satellite may transmit the signal to a ground base station (e.g., gNB). For example, the gNB can perform the role of a 5G wireless access network (e.g., RAN) and can be connected to a 5G / 6G core (e.g., 5GC / 6GC) via an NG interface (e.g., NGc, NGu). For example, the 5GC / 6GC can be connected to an external data network via an N6 interface. Thus, for example, in this structure, a satellite can extend the wireless section to mediate the connection between the UE and the ground base station, and subsequent procedures can operate in the same way as the existing 5G structure. For example, the NTN architecture of FIG. 12 can be related to the replay payload of FIG. 10 (b).

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

[0128] Referring to FIG. 13, for example, in step S1310, the base station can schedule downlink transmissions such as frequency / time resources, a transport layer, a downlink precoder, an MCS, etc. For example, the base station can determine a beam for the terminal's PDSCH transmission through the operations described above.

[0129] For example, in step S1320, the terminal can receive downlink control information (DCI: Downlink Control Information) for downlink scheduling (e.g., including scheduling information of the PDSCH) from the base station on the PDCCH.

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

[0131] For example, the number of DMRS ports can be scheduled according to each state indicated in the antenna port(s) field, and SU (Single-user) / MU (Multi-user) transmission scheduling can also be performed.

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

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

[0134] For example, if the terminal detects a PDCCH containing DCI format 1_0 or 1_1, it can decode the PDCCH according to instructions from the corresponding DCI.

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

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

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

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

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

[0140] For example, if P' is determined to be either {2 or 4}, the Precoding Resource Block Group (PRG) can be divided into P' consecutive PRBs. For example, the actual number of consecutive PRBs within each PRG can be one or more. For example, the UE may assume that the same precoding is applied to consecutive downlink PRBs within the PRG.

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

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

[0143] Referring to FIG. 14, for example, in step S1410, the base station can schedule uplink transmissions such as frequency / time resources, transport layer, uplink precoder, MCS, etc. For example, the base station can determine a beam for the terminal's PUSCH transmission through the operations described above.

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

[0145] For example, DCI format 0_0 or 0_1 may be used for uplink scheduling, and in particular, DCI format 0_1 ​​may include the following information: DCI format identifier, UL / SUL (Supplementary uplink) indicator, Bandwidth part indicator, Frequency domain resource assignment, Time domain resource assignment, Frequency hopping flag, Modulation and coding scheme (MCS), SRS resource indicator (SRI), Precoding information and number of layers, Antenna port(s), SRS request, DMRS sequence initialization, UL-SCH (Uplink Shared Channel) indicator

[0146] For example, the SRS resource indicator field may indicate SRS resources configured within the SRS resource set associated with the upper-level parameter 'usage'. For instance, 'spatialRelationInfo' can be set for each SRS resource, and its value can be one of {CRI, SSB, SRI}.

[0147] For example, in step S1430, the terminal can transmit uplink data to the base station over PUSCH.

[0148] For example, if the terminal detects a PDCCH containing DCI format 0_0 or 0_1, it can transmit the corresponding PUSCH according to the instructions given by the DCI.

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

[0150] i) For example, when the upper layer parameter 'txConfig' is set to 'codebook', the terminal can be configured for codebook-based transmission. For example, when the upper layer parameter 'txConfig' is set to 'nonCodebook', the terminal can 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, if PUSCH is scheduled by DCI format 0_0, the PUSCH transmission may be based on a single antenna port.

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

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

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

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

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

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

[0157] For example, parameters related to MEO (Medium Earth orbit) may be as follows. For example, the altitude of MEO (Medium Earth orbit) may be 7,000–25,000 km. For example, the beam footprint size of MEO (Medium Earth orbit) may be 100–1,500 km. For example, the maximum propagation delay of MEO (Medium Earth orbit) may be 95.19 msec (for MEO-10000).

[0158] For example, parameters related to the GEO (Geo-stationary Earth orbit) may be as follows. For example, the altitude of the GEO (Geo-stationary Earth orbit) may be 35,786 km. For example, the beam footprint size of the GEO (Geo-stationary Earth orbit) may be 200-3,500 km. For example, the satellite velocity of the GEO (Geo-stationary Earth orbit) may be 3.1 km / sec (negligible). For example, the maximum propagation delay of the GEO (Geo-stationary Earth orbit) may be 541.46 msec.

[0159] For example, to effectively operate an NTN with a very long RTT, the scheduling offset is class This can be introduced.

[0160] FIG. 16 is K according to one embodiment of the present disclosure. offset and K macExamples of are shown. The embodiment of FIG. 16 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0161] Referring to Fig. 16, for example, class Examples of can be presented. For example, service link RTT can be the RTT between the terminal and the satellite. For example, feeder link RTT can be the RTT between the satellite and the base station. For example, common TA can be the TA between the satellite and the RP. For example, can be an offset value representing the RTT of the uplink time synchronization reference point (RP). For example, can mean the sum of the service link RTT and the common TA (if indicated). For example, may be an offset value representing the RTT between the RP and the gNB. For example, the feeder link RTT is the common TA (if indicated) and It can mean the sum of.

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

[0163] Referring to FIG. 17, terminal-specific TA can be acquired to compensate for transmission delays on the service link, and common TA can be acquired to compensate for transmission delays between the RP (reference point) and the satellite.

[0164] For example, in an NTN-based communication system, a terminal can calculate a TA based on the terminal's GNSS (global navigation satellite system) capabilities (e.g., terminal location) and orbit-related upper-layer parameters transmitted from the base station, and this is a terminal-specific TA ( It can be referred to as ). For example, if orbit-related upper-layer parameters are not received from the base station, the terminal-specific TA may be set to 0. For example, common TA parameters, which are upper-layer parameters transmitted from the base station (e.g., , , and / or TA obtained based on ) common TA( It can be referred to as ). For example, if common TA parameters are not transmitted from the base station, the common TA can be set to 0. Accordingly, for example, in an NTN-based communication system, the total TA value (TTA) is “ It can be obtained as ”. For example, can refer to the TA offset value provided to the terminal per serving cell, and can mean a value obtained based on the timing advance command.

[0165] Referring to FIG. 17, for example, in Rel-17 NTN, the terminal can calculate the TA itself based on the terminal's GNSS capability and base station guidance information (e.g., ephemeris information), which can be designated as a terminal-specific (UE-specific) TA. For example, a TA calculated based on common TA parameters indicated by the base station can be designated as a common TA, and the final TA based thereon can be based on FIG. 18 and the description related to FIG. 18.

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

[0167] Referring to FIG. 18, the uplink frame number i for the transmission from the UE is before the start of the corresponding downlink frame from the UE You can start here

[0168] - and ...can be given in Section 4.2 of TS 38.213, and This may be excluded for msgA transmissions on PUSCH that are to be used;

[0169] - It can be derived from the upper-level parameters ta-Common, ta-CommonDrift, and ta-CommonDriftVariant if indicated, and otherwise It could be;

[0170] - is calculated by the UE based on UE position and serving-satellite-orbit-related upper-layer parameters if indicated, and otherwise It could be.

[0171] For example, there may be TA misalignment.

[0172] For example, in NR NTN, a TA mismatch may occur if the gNB does not receive a TA report, if the existing TA report is outdated, or if the granularity of the TA report is insufficient. For example, if the UE does not perform any TA reporting, the gNB [uses] several key scheduling variables (e.g., , Since ) cannot be configured, the above scenario (e.g., no TA reporting) may not be considered a feasible scenario. Therefore, assuming that the UE performs TA reporting, the magnitude of TA mismatch caused by TA reporting obsolescence and / or TA reporting granularity may need to be addressed. For example, if the UE performs TA reporting on NR NTN, TA discrepancies may occur primarily due to outdated TA reporting and / or coarse TA reporting granularity. For example, to support HD-FDD (e)RedCap UE, issues regarding quantitative-level TA misalignment between the gNB and the UE may need to be addressed.

[0173] Meanwhile, differences resulting from outdated TA reporting may occur when the UE location changes, and may occur proportionally to RTT differences depending on the UE location within the cell (e.g., the difference between the minimum TA and the maximum TA).

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

[0175] Referring to Fig. 19, for example, assuming an LEO of 600 km, a beam size of 50 km, and a target elevation angle of 30 degrees, the difference between the shortest RTT (minimum TA) and the longest RTT (maximum TA) can be within about 300 µs, which corresponds to about 4 to 5 OFDM symbols using a 15 kHz SCS.

[0176] For example, assuming an LEO of 600 km, a beam size of 50 km, and a target elevation angle of 30 degrees, the difference between the shortest RTT (minimum TA) and the longest RTT (maximum TA) is within approximately 300 µs, which corresponds to about 4 to 5 OFDM symbols with a 15 kHz SCS. For example, considering that the TA reported granularity of NTN is 1 ms (e.g., 14 OFDM symbols using a 15 kHz SCS), in the LEO example, the main cause of the TA discrepancy may be the TA reported granularity rather than the old TA reported. For example, for an LEO of 600 km, a beam size of 50 km, and a target elevation angle of 30 degrees, the difference between the minimum TA and the maximum TA may be smaller than the TA reported granularity (e.g., 1 ms). For example, in the case of HD-FDD (e)RedCap UE support, issues regarding the enhanced TA reporting mechanism, particularly TA reporting granularity, may need to be addressed.

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

[0178] When comparing the timing advances of NTN and TN due to satellite movement, the timing advance of the service link between the satellite and the UE can be estimated by the UE itself. For example, the gNB can obtain the TA value through TA reporting, but due to the current 1ms granularity reported by the TA, the gNB cannot obtain the exact TA used by the UE, and the UE side cannot know when or which transmission will collide. For example, since the rule for when a DL reception collides with a UL transmission is intended to avoid collisions through gNB scheduling, the NTN gNB may experience difficulties in determining whether the UE is in an uplink slot or a downlink slot.

[0179] For example, the terminal may receive satellite orbit information via system information and / or RRC signaling. For example, satellite orbit information may be implemented / supported in a position and velocity state vector orbit format, and / or an orbital parameter orbit format. For example, the position and velocity state vector orbit format may consist of less than 17 bytes (e.g., 132 bits). For example, the field size for position (x, y, z)(m) may be 78 bits, and velocity (v x , v y , v z The field size for )(m / s) can be 54 bits. For example, the orbital parameter orbital format can be composed of less than 21 bytes (e.g., 164 bits).

[0180] FIG. 20 illustrates an example of an orbital parameter orbital format according to one embodiment of the present disclosure. The embodiment of FIG. 20 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0181] Referring to FIG. 20, information related to the orbital parameter orbit format (e.g., ephemeral information) includes the semi-major axis "α" (e.g., 33 bits) [m], the eccentricity "e" (in an elliptical satellite orbit, 0 <e<1) (예를 들어, 20 비트), 근점 편각(argument of periapsis) "ω"(예를 들어, 28 비트) [rad], 승교점 경도(longitude of ascending node) "Ω" (예를 들어, 28 비트) [rad], (궤도) 경사(inclination) "i" (예를 들어, 27 비트) [rad], 및 / 또는 평균 근점 이각(mean anomaly) "M0" = 에포크 t0[JD]에서 M(t0) (예를 들어, 28 비트) [rad] 중 적어도 어느 하나를 포함할 수 있다.

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

[0183] Referring to Fig. 21, the TA value reported by the UE may be 4ms. For example, the actual TA value may be 4ms. For example, the actual TA value may be 3ms. For example, the actual TA value may be 5ms.

[0184] For example, assuming the TA value reported by the UE is 4ms and the SCS is 15kHz, UE-specific If the gNB schedules based on the reported values ​​set in these four slots, the UE can operate well. For example, the actual TA value could be 4ms. However, as the satellite moves, the distance between the satellite and the UE constantly changes, which may cause the TA value actually used by the UE to increase or decrease. For example, the actual TA value could be 3ms. For example, the actual TA value could be 5ms. For example, if the gNB still schedules according to the old reported value, a crash may occur on the UE side, as filled with black in Fig. 21, where the blank space may indicate that scheduling is not taking place.

[0185] In FIG. 21, the actual TA is shown as 3ms, 4ms, and 5ms, but is not limited thereto. In FIG. 21, the reported TA is shown as 4ms, but is not limited thereto.

[0186] For example, according to an embodiment of the present disclosure, a half-duplex operation may include the following.

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

[0188] For example, if the PDCCH reception by the terminal includes two PDCCH candidates, the end of the PDCCH candidate of the two may be the end of the PDCCH reception.

[0189] For example, the HD-UE may not expect a dedicated higher layer parameter for setting reception for a set of symbols and a DCI format detection for scheduling transmission for any symbol in the set of symbols.

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

[0191] For example, in PUCCH, PUSCH configured by the upper layer versus CSI-RS, PDSCH indicated by the DCI format,

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

[0193] For example, SRS configured by the upper layer vs. CSI-RS and PDSCH indicated by the DCI format

[0194] For example, from the last symbol of the PDCCH reception for the DCI format Without canceling the SRS transmission within the specified period, the SRS transmission of the remaining symbols can be canceled.

[0195] for example, silver It may be the PUSCH preparation time for UE processing function 1 [Refer to TS 38.214] assuming and It may be the smallest SCS setting between the SCS setting of PDCCH carrying the DCI format and the SCS settings of SRS, PUCCH, and PUSCH.

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

[0197] For example, in PUSCH, PUCCH configured by the higher layer vs. the indicated presence of an SSB within the DL BWP by ssb-PositionInBurst in SIB1 or in ServingCellConfigCommon or by NonCellDefiningSSB,

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

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

[0200] For example, in Higher layer configured SRS vs. ssb-PositionInBurst in SIB1 or in ServingCellConfigCommon or by NonCellDefiningSSB,

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

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

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

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

[0205] For example, in SRS vs. SIB1 or in ServingCellConfigCommon or by NonCellDefiningSSB, the presence of an SSB within the DL BWP is indicated by ssb-PositionInBurst in SIB1 or in ServingCellConfigCommon or by NonCellDefiningSSB,

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

[0207] For example, in the reception of PDCCH, PDSCH, CSI-RS, and DL PRS, indicated presence of SSB within the DL BWP by ssb-PositionInBurst in SIB1 or in ServingCellConfigCommon or by NonCellDefiningSSB,

[0208] - For example, if symbol durations overlap, it can be left to the UE implementation.

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

[0210] For example, in the present disclosure, "specific threshold" may mean a threshold that is predefined or (pre-)set by an upper layer (including the application layer) of a network, base station, or terminal. For example, in the present disclosure, "specific set value" may mean a value that is predefined or (pre-)set by an upper layer (including the application layer) of a network, base station, or terminal. For example, in the present disclosure, "set by the network / base station" may mean an action in which a base station sets to a UE (pre-) through upper layer RRC signaling, sets / signals to a UE through MAC CE, or signals to a UE through DCI.

[0211] Recently, active research has been conducted in the field of mobile communications on non-terrestrial (NTN) networks that utilize satellites, drones, and other devices as network nodes. For example, satellites in NTN can be broadly classified into GSO satellites, which possess a geosynchronous orbit (GSO), and NGSO satellites, which do not possess a geosynchronous orbit (non-GSO). Additionally, satellites can be classified into low earth orbit (LEO), medium earth orbit (MEO), and high earth orbit (HEO) based on their altitude. In the field of mobile communications, LEO-based NTN support methods, which offer relatively lower costs and higher data transmission rates, are primarily being researched. However, LEO satellites are NGSO satellites and are characterized by very high speeds required to maintain their orbits due to their very close proximity to the Earth's surface. Therefore, to provide services to ground terminals via LEO satellites, it is necessary to overcome Doppler shifts caused by high relative velocities and / or significant time delays associated with high altitudes.

[0212] Recently, active research is being conducted in the field of mobile communications on non-terrestrial networks (NTNs) that utilize satellites, drones, and the like as network nodes. For example, satellites in NTNs can be broadly classified into GSO satellites, which have a geosynchronous orbit (GSO), and NGSO satellites, which do not have a geosynchronous orbit (non-GSO, NGSO). For example, satellites in NTNs can also be classified into low earth orbit (LEO), medium earth orbit (MEO), and high earth orbit (HEO) depending on their altitude. Here, for example, in the field of mobile communications, LEO-based NTN support methods that offer relatively low costs and high data transmission rates are primarily being researched. Here, for example, the aforementioned satellite-based non-terrestrial network may have channel characteristics such as large path attenuation and / or long time delay and / or large Doppler shift due to high altitude and / or high relative velocity.

[0213] For example, in the telecommunications field, the introduction of non-terrestrial networks (NTNs) utilizing satellites as network nodes is being actively discussed recently. For example, satellites supporting the above NTN can be classified according to their flight orbits and characteristics, such as GEO, MEO, and LEO, and generally have the characteristic of having very high altitudes. For example, the above NTN can service Reduced Capability (RedCap) terminals and / or Enhanced Reduced Capability (eRedCap) terminals that support half-duplex frequency division duplexing (HD-FDD) transmission methods. For example, terminals supporting the above half-duplex transmission method cannot perform DL reception and UL transmission simultaneously; therefore, rules for base station (or network) and / or terminal operations (e.g., DL / UL collision handling rules) may need to be defined when the time of DL reception and the time of UL transmission overlap on the time axis and / or collide. For example, a DL / UL collision handling rule for a terminal operating in half-duplex transmission mode in the above NTN may be defined by considering issues such as information that must be prioritized in the NTN and / or TA discrepancies between the base station and the terminal due to the application of terminal autonomous (UE autonomous) TA (Timing Advance) in the NTN. In the present disclosure, a transmission method and apparatus for a terminal operating in half-duplex transmission mode in the NTN may be proposed in terms of DL / UL collision handling rules.

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

[0215] The propagation delay of the service link in NTN is calculated by the terminal, and since the base station does not know this, the base station cannot accurately know the terminal's actual TA. The base station can roughly estimate the terminal's TA based on the TA reported by the terminal.

[0216] In a wireless communication system, a DL-UL (downlink-uplink) priority rule that prioritizes UL (uplink) can be configured. However, when monitoring the CSS (common search space) in an HD-FDD environment or a half-duplex operation environment, a conflict may occur between the UL priority rule and DL monitoring.

[0217] Furthermore, when supporting RedCap UEs in a non-terrestrial network (NTN) environment, base stations may find it difficult to accurately estimate the UE's timing advance (TA), and the timing boundary between DL and UL becomes uncertain, which can further increase the possibility of DL-UL collisions. In such environments, it is necessary to handle DL-UL collisions more conservatively and reliably.

[0218] In particular, the UE may not be able to immediately determine the existence of DCI and the collision determination result in the CSS, and the determination of the existence / absence of DCI and the related collision handling decision may not be completed immediately within the slot, but may only be determined after at least that slot. As a result, even though it may superficially appear sufficient to process only the symbol section occupied by the CSS as DL, in practice, a problem may arise where it is difficult to determine whether to initiate UL within that slot.

[0219] In addition, if the interval after CSS monitoring is defined as a UL, the base station must determine that UL transmission is possible in that interval and perform UL reception and detection. However, if the UE is unable to actually initiate the UL due to processing delays or other reasons, the base station performs unnecessary monitoring and reception operations for ULs that are not actually reached, which increases the network burden.

[0220] One embodiment of the present disclosure has the technical objective of i) stably handling collisions between CSS monitoring and UL transmission in an environment where a DL-UL priority rule prioritizing UL is configured, ii) resolving the problem of difficulty in immediately determining whether to initiate a UL within a slot due to the delay in confirming DCI processing of the UE, iii) reducing the burden of unnecessarily performing UL reception and detection for ULs that the base station does not actually reach, and iv) handling DL-UL collisions consistently and predictably even in cases where TA uncertainty exists, such as in an NTN environment.

[0221] To this end, according to one embodiment of the present disclosure, for example, a DL-UL priority rule that prioritizes UL is obtained, and CSS is monitored based on said rule, but DL may be prioritized in time resources where CSS is monitored despite the rule prioritizing UL being configured. For example, said time resources may be slots, and accordingly, the entire slot where CSS is monitored may be processed with DL priority. Or, for example, said time resources may be POs (paging occasions), and DL may be prioritized in relation to CSS monitoring in POs. For example, by including DL priority not only in the first time resource where CSS is monitored but also in the second time resource adjacent to said time resource, it may be configured to absorb the DCI processing confirmation delay period of the UE.

[0222] The proposed method(s) of the present disclosure are described below as examples of non-terrestrial networks, but the proposed method(s) of the present disclosure can be extended and applied to terrestrial networks as well.

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

[0224] Referring to FIG. 22, the reported TA and the actual TA may differ. For example, a guard time may be defined. For example, the time difference between the terminal's actual TA and the reported TA may be the guard time. As illustrated in FIG. 22, the propagation delay of the service link in the NTN is calculated by the terminal, and since the base station is unaware of this, the base station cannot accurately know the terminal's actual TA.

[0225] [Proposed Method #01] When a base station (or network) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to half-duplex transmission mode, the base station (or network) and / or terminal can determine whether there is a DL / UL collision based on GT (Guard Time) and / or UL TA (Uplink Time Advance) assumptions for DL ​​transmission resources and UL transmission resources using one or more of the following methods.

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

[0227] (1) A. Option 1

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

[0229] (1) A. ii. A terminal may determine that there is a DL / UL collision if it is located within GT between a DL transmission resource and a UL transmission resource (assuming the application of the second TA).

[0230] (1) B. Option 2

[0231] (1) B. i. A base station may determine that there is a DL / UL collision if there is a DL transmission resource and a UL transmission resource (assuming the first TA is applied) within GT.

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

[0233] (2) The base station and the terminal can apply the same UL TA assumption.

[0234] (2) A. Option 1

[0235] (2) A. i. A base station may determine that there is a DL / UL collision if there is a GT between a DL transmission resource and a UL transmission resource (assuming the application of the third TA).

[0236] (2) A. ii. If the terminal is located within GT between the DL transmission resource and the UL transmission resource (assuming the application of the third TA), it can determine that there is a DL / UL collision.

[0237] (2) B. Option 2

[0238] (2) B. i. A base station may determine that there is a DL / UL collision if there is a GT between a DL transmission resource and a UL transmission resource (assuming the application of the third TA).

[0239] (2) B. ii. The terminal may determine that there is a DL / UL collision if there is an overlap (in the time axis) between the DL transmission resource and the UL transmission resource (assuming the application of the third TA).

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

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

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

[0243] Here, for example, the third TA may mean a UL TA that the base station (or network) and the terminal can equally calculate / derive based on a (pre-) agreement / definition / setting between the base station (or network) and the terminal. For example, the third TA may be a (public) TA or a TA that the terminal reported (most recently) to the base station (or network).

[0244] Here, for example, the above GT may be a value that the base station (or network) (pre-)agrees / defines with the terminal or sets / instructs the terminal.

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

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

[0247] For example, let us assume that in a non-terrestrial network according to one embodiment of the present disclosure, a base station (or network) services a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, for example, when the terminal operates in a half-duplex transmission mode, it cannot perform DL reception and UL transmission simultaneously, and if the timing of DL reception and the timing of UL transmission conflict, the terminal may prioritize DL reception and / or UL transmission according to a DL / UL collision handling rule pre-agreed upon / set with the base station.

[0248] Here, for example, in the uplink of a non-terrestrial network, the terminal may apply a (shared) 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 (shared) TA may be a value mutually recognized through shared parameters and calculation formulas between the base station (or network) and the terminal, and the (UE) TA may be a value that is voluntarily adjusted by the terminal and is unknown to the base station (or network). Here, for example, the TA that the base station (or network) expects / predicts for the terminal (first TA) and the TA that the terminal actually applies (second TA) may have different values.

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

[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 base station (or network) and / or the terminal can determine whether there is a DL / UL collision based on GT (Guard Time) and / or UL TA (Uplink Time Advance) assumptions regarding a DL transmission resource and a UL transmission resource. For example, the base station may determine that there is a DL / UL collision if the DL transmission resource and the UL transmission resource (assuming the application of a third TA) are within the GT, and the terminal may determine that there is a DL / UL collision if the DL transmission resource and the UL transmission resource (assuming the application of a third TA) are located within the GT. Here, for example, the third TA may refer to a UL TA that the base station (or network) and the terminal can calculate / derive in the same way based on a (pre-)agreement / definition / setting between the base station (or network) and the terminal. For example, the third TA may be a (public) TA or a TA that the terminal reported (most recently) to the base station (or network). Here, for example, the GT may be a value that the base station (or network) (pre-)agreed / defines with the terminal or sets / instructs the terminal. For example, the GT may be configured to include a minimum / maximum TA range that the terminal's (UE) TA may have.

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

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

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

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

[0255] According to the proposed method of the present disclosure, there is an advantage in matching the mutual (expected) transmission and reception timing by performing the same DL / UL collision determination and / or DL / UL collision handling rules even when the recognized TA values ​​between the base station (or network) and the terminal in a non-terrestrial network are different. Here, for example, if the proposed method is not supported, a problem may occur in which transmission resources are unnecessarily consumed as the base station (or network) and / or terminal perform transmission and / or reception at an unexpected time.

[0256] The above [Proposed Plan #01] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0257] [Proposed Method #02] When a base station (or network) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, the base station (or network) and / or terminal may select DL transmission resource(s) and / or UL transmission resource(s) (hereinafter referred to as the first resource set) to which DL / UL collision determination and / or DL / UL collision handling rules are applied, using one or more of the following methods.

[0258] (1) A first set of resources can be determined based on the UL transmission resource (hereinafter Resource A).

[0259] (1) A. Option 1

[0260] (1) A. i. T relative to the time of transmission of resource A PROC,2 DL transport resource(s) (dynamically scheduled and / or semi-statically configured) and / or UL transport resource(s) (dynamically scheduled and / or semi-statically configured) up to the previous point in time

[0261] (1) B. Option 2

[0262] (1) B. i. T relative to the time of transmission of resource A PROC,2 Resource A and / or transmission resource(s) that could (potentially) conflict with Resource A among the DL transmission resource(s) (dynamically scheduled and / or semi-statically configured) and / or UL transmission resource(s) (dynamically scheduled and / or semi-statically configured) up to the previous point in time

[0263] (1) C. Option 3

[0264] (1) C. i. T relative to the time of transmission of resource A PROC,2 Resource A and / or transmission resource(s) that could (potentially) conflict with Resource A among the DL transmission resource(s) (dynamically scheduled and / or semi-statically set) and / or UL transmission resource(s) (dynamically scheduled and / or semi-statically set) up to the previous point in time may be selected as the initial second set of resources.

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

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

[0267] (2) A first set of resources can be determined based on a dynamically scheduled resource (hereinafter resource B).

[0268] (2) A. Option 1

[0269] (2) A. i. DL transport resource(s) (dynamically scheduled and / or semi-statically configured) and / or UL transport resource(s) (dynamically scheduled and / or semi-statically configured) up to the point when resource B is scheduled

[0270] (2) B. Option 2

[0271] (2) B. i. Resource B and (potentially) colliding with Resource B among the DL transmission resource(s) (dynamically scheduled and / or semi-statically configured) and / or UL transmission resource(s) (dynamically scheduled and / or semi-statically configured) up to the point when Resource B is scheduled

[0272] (2) C. Option 3

[0273] (2) C. i. Up until the point in time when resource B is scheduled, among the DL transmission resource(s) (dynamically scheduled and / or semi-statically set) and / or UL transmission resource(s) (dynamically scheduled and / or semi-statically set), resource B and / or transmission resource(s) that may (potentially) conflict with resource B may be selected as the initial second set of resources.

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

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

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

[0277] Here, for example, the above T PROC,2 This may refer to the processing time required by the terminal for uplink transmission.

[0278] Here, for example, the terminal can perform the first method starting from the UL transmission resource that has an earlier transmission time in the time axis.

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

[0280] Here, for example, DL / UL collision determination and / or DL / UL collision handling rules can be applied to the active transmission resources among the semi-statically configured transmission resources.

[0281] For example, let us assume that in a non-terrestrial network according to one embodiment of the present disclosure, a base station (or network) services a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, for example, when the terminal operates in a half-duplex transmission mode, it cannot perform DL reception and UL transmission simultaneously, and if the timing of DL reception and the timing of UL transmission conflict, the terminal may prioritize DL reception and / or UL transmission according to a DL / UL collision handling rule pre-agreed upon / set with the base station.

[0282] Here, for example, in the uplink of a non-terrestrial network, the terminal may apply a (shared) 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 (shared) TA may be a value mutually recognized through shared parameters and calculation formulas between the base station (or network) and the terminal, and the (UE) TA may be a value that is voluntarily adjusted by the terminal and is unknown to the base station (or network). Here, for example, the TA that the base station (or network) expects / predicts for the terminal (first TA) and the TA that the terminal actually applies (second TA) may have different values.

[0283] Here, for example, to resolve a recognition discrepancy between the base station (or network) and the terminal regarding the above TA, (potential) DL / UL collision resource(s) can be determined by considering the variable range of the (UE) TA. For example, the base station (or network) and / or terminal may determine that a DL transmission resource and a UL transmission resource existing within a certain GT (Guard Time) are potentially capable of colliding when assuming a specific UL TA. Here, for example, the base station (or network) and / or terminal may pre-select the DL transmission resource(s) and / or UL transmission resource(s) to determine whether a DL / UL collision occurs, and then determine whether a DL / UL collision occurs based on the (candidate) DL / UL transmission resource(s) assuming a UL TA and / or GT.

[0284] Accordingly, the present disclosure proposes a method in which, when a base station (or network) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, the base station (or network) and / or the terminal selects DL transmission resource(s) and / or UL transmission resource(s) (hereinafter referred to as the first resource set) to determine whether a DL / UL collision has occurred by one or more of the following methods. For example, the first resource set may be determined based on a (specific) UL transmission resource. For example, the terminal, relative to the transmission time of the (specific) UL transmission resource, T PROC,2Up to a previous point in time, all and / or part of the DL transmission resource(s) (dynamically scheduled and / or semi-statically set) and / or UL transmission resource(s) (dynamically scheduled and / or semi-statically set) may be designated as a first resource set, and a DL / UL collision between transmission resource(s) within the first resource set may be determined. Alternatively, for example, the first resource set may be determined based on dynamically scheduled resources. For example, the terminal may designate all and / or part of the DL transmission resource(s) (dynamically scheduled and / or semi-statically set) and / or UL transmission resource(s) (dynamically scheduled and / or semi-statically set) up to the point in time when the transmission resource is scheduled as a first resource set, and a DL / UL collision between transmission resource(s) within the first resource set may be determined. Here, for example, based on a (specific) transmission resource, the reference resource and / or transmission resource(s) that may (potentially) collide with the reference resource may be designated as an (initial) first resource set. Here, for example, if there are transmission resource(s) that may (potentially) collide with the first resource set, the terminal may update the first resource set to include said transmission resource(s).

[0285] According to the proposed method of the present disclosure above, when a base station (or network) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, they can equally recognize whether a DL / UL collision is determined and / or the target transmission resource(s) to which the DL / UL collision handling rules are to be applied. Through this, the base station (or network) and / or terminal have the advantage of matching the (expected) transmission and reception timings by equally performing the determination of whether a DL / UL collision is determined and / or the DL / UL collision handling rules. Here, for example, if the proposed method is not supported, a problem may occur in which transmission resources are unnecessarily consumed as the base station (or network) and / or terminal perform transmission and / or reception at an unexpected time.

[0286] The above [Proposed Plan #02] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0287] [Proposed Method #03] When a base station (or network) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, and when there are multiple DL transmission resource(s) and / or UL transmission resource(s) to which the base station (or network) and / or terminal determine whether there is a DL / UL collision and / or apply DL / UL collision handling rules, the base station (or network) and / or terminal can perform the determination of whether there is a DL / UL collision and / or apply DL / UL collision handling rules in one or more of the following ways.

[0288] (1) Determine whether there is a DL / UL collision based on priority and / or order information and / or perform DL / UL collision handling rules

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

[0290] (2) Determining whether there is a DL / UL collision based on the time axis order of the transmission resource and / or performing DL / UL collision handling rules

[0291] (2) A. For example, the terminal may determine whether there is a DL / UL collision for each transmission resource and / or perform a DL / UL collision handling rule in the order of transmission times (in the time axis) preceding each transmission resource for the DL / UL transmission resource(s).

[0292] (3) Determine whether there is a DL / UL collision based on the scheduling order and / or perform DL / UL collision handling rules

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

[0294] (4) Determine whether there is a sequence-based DL / UL conflict between dynamically scheduled resources and semi-statically configured resources and / or perform DL / UL conflict handling rules

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

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

[0297] Here, for example, the above priority and / or order information may be (pre-)agreed between the base station (or network) and the terminal, or the base station (or network) may set / instruct the terminal.

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

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

[0300] Here, for example, when the terminal applies the DL / UL collision handling rule according to the above sequence, the DL / UL transmission resources that were omitted from receiving / transmitting in the preceding process may not be considered as valid transmission resources in the subsequent process. For example, the invalid transmission resource(s) may be excluded from the DL / UL collision determination target.

[0301] Here, for example, the proposed method may be applied to a plurality of (dynamically scheduled and / or semi-statically set) DL transmission resource(s) and / or a plurality of (dynamically scheduled and / or semi-statically set) UL transmission resource(s).

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

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

[0304] Here, for example, DL / UL collision determination and / or DL / UL collision handling rules can be applied to the active transmission resources among the semi-statically configured transmission resources.

[0305] For example, let us assume that in a non-terrestrial network according to one embodiment of the present disclosure, a base station (or network) services a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, for example, when the terminal operates in a half-duplex transmission mode, it cannot perform DL reception and UL transmission simultaneously, and if the timing of DL reception and the timing of UL transmission conflict, the terminal may prioritize DL reception and / or UL transmission according to a DL / UL collision handling rule pre-agreed upon / set with the base station.

[0306] Here, for example, in the uplink of a non-terrestrial network, the terminal may apply a (shared) 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 (shared) TA may be a value mutually recognized through shared parameters and calculation formulas between the base station (or network) and the terminal, and the (UE) TA may be a value that is voluntarily adjusted by the terminal and is unknown to the base station (or network). Here, for example, the TA that the base station (or network) expects / predicts for the terminal (first TA) and the TA that the terminal actually applies (second TA) may have different values.

[0307] Here, for example, to resolve recognition discrepancies between the base station (or network) and the terminal regarding the above TA, (UE) can determine (potential) DL / UL collision resource(s) by considering the variable range of the TA. For example, the base station (or network) and / or terminal may determine that DL transmission resources and UL transmission resources existing within a certain GT (Guard Time) are potentially capable of colliding when assuming a specific UL TA. Here, for example, when performing the GT-based DL / UL collision determination, since the collision time is given as a time interval proportional to the GT, there may be cases where there are multiple DL transmission resource(s) and / or UL transmission resource(s) for which DL / UL collision determination and / or DL / UL collision handling rules must be applied within the collision interval. Here, for example, if the order of applying DL / UL collision handling rules between the DL / UL transmission resource(s) differs between the base station (or network) and the terminal, correct transmission and reception may not be performed. For example, let us assume that a first transmission resource, a second transmission resource, and a third transmission resource exist in order along the time axis. Here, for example, let us assume that the first transmission resource collides with the second transmission resource, the second transmission resource collides with the third transmission resource, and that the transmission priorities are higher in order. Here, for example, if there are no restrictions on the order in which collision handling rules are applied between a base station (or network) and a terminal, the base station is expected to apply the collision handling rules starting from the first transmission resource, whereas the terminal may apply the collision handling rules starting from the second transmission resource. Here, for example, the base station (or network) may omit the second transmission resource after applying the collision handling rules and transmit / receive only the first and third transmission resources. Here, for example, the terminal may omit the third transmission resource after applying the collision handling rules, then omit the second transmission resource again, and then transmit / receive only the first transmission resource.Therefore, if the order for resolving DL / UL collision handling rules is not determined, cases may occur where the transmission resource(s) expected by the base station (or network) and the terminal are different, as in the example above.

[0308] Accordingly, the present disclosure proposes a method in which, when a base station (or network) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, and when there are multiple DL transmission resource(s) and / or UL transmission resource(s) to which the base station (or network) and / or the terminal apply DL / UL collision determination and / or DL / UL collision handling rules, the base station (or network) and / or the terminal perform DL / UL collision determination and / or DL / UL collision handling rules for each transmission resource according to a mutually agreed (pre)convention and / or established / instructed order. For example, the terminal may perform DL / UL collision determination and / or DL / UL collision handling rules based on priority and / or order information. For example, the terminal may perform DL / UL collision determination and / or DL / UL collision handling rules based on the time axis order of the transmission resources. For example, the terminal may perform DL / UL collision determination and / or DL / UL collision handling rules based on the scheduling order. For example, the terminal may determine whether there is a DL / UL collision and / or perform DL / UL collision handling rules based on the order between dynamic scheduling resources and semi-static configured resources. Here, for example, one or more of the above methods may be applied in combination.

[0309] According to the proposed method of the present disclosure above, when a base station (or network) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to half-duplex transmission mode, the results of applying DL / UL collision determination rules can be recognized identically. Through this, there is an advantage in that the base station (or network) and / or terminal can synchronize the (expected) transmission and reception times with each other. Here, for example, if the proposed method is not supported, a problem may occur in which transmission resources are unnecessarily consumed as the base station (or network) and / or terminal perform transmission and / or reception at an unexpected time.

[0310] The above [Proposed Plan #03] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0311] [Proposed Method #04] When a base station (or network) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to half-duplex transmission mode, the base station (or network) and / or terminal can distinguish steps based on resource type and sequentially perform DL / UL collision determination and / or DL / UL collision handling rules according to the steps.

[0312] For example, the terminal may perform stepwise DL / UL collision determination and / or DL / UL collision handling rules as follows.

[0313] (1) Step 1: Determine whether there is a DL / UL conflict related to semi-statically configured resources and / or apply DL / UL conflict handling rules

[0314] (1) A. For example, a rule to determine whether there is a (DL / UL) collision between a DL transmission resource (set to semi-static) and a UL transmission resource (set to semi-static) and / or a rule to handle the (DL / UL) collision can be applied.

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

[0316] (2) A. For example, a (DL / UL) collision determination and / or (DL / UL) collision handling rule can be applied between a (dynamically scheduled) DL transmission resource and a (semi-statically set and / or dynamically scheduled) UL transmission resource.

[0317] (2) B. For example, a (DL / UL) collision determination and / or (DL / UL) collision handling rule can be applied between a (dynamically scheduled) UL transmission resource and a (semi-statically set and / or dynamically scheduled) DL transmission resource.

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

[0319] Here, for example, the terminal may determine potential (potential) resources based on the resource whenever it detects dynamic scheduling for a dynamically scheduled transmission resource, and apply DL / UL collision handling rules. Here, for example, when the terminal searches for potential (potential) resources, it may target resources that were previously set and / or scheduled relative to the detected dynamic scheduling.

[0320] For example, let us assume that in a non-terrestrial network according to one embodiment of the present disclosure, a base station (or network) services a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, for example, when the terminal operates in a half-duplex transmission mode, it cannot perform DL reception and UL transmission simultaneously, and if the timing of DL reception and the timing of UL transmission conflict, the terminal may prioritize DL reception and / or UL transmission according to a DL / UL collision handling rule pre-agreed upon / set with the base station.

[0321] Here, for example, in the uplink of a non-terrestrial network, the terminal may apply a (shared) 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 (shared) TA may be a value mutually recognized through shared parameters and calculation formulas between the base station (or network) and the terminal, and the (UE) TA may be a value that is voluntarily adjusted by the terminal and is unknown to the base station (or network). Here, for example, the TA that the base station (or network) expects / predicts for the terminal (first TA) and the TA that the terminal actually applies (second TA) may have different values.

[0322] Here, for example, due to reasons such as the application of the above (UE) TA, there may be cases where the base station (or network) in a non-terrestrial network does not know whether there is an actual DL / UL collision at the terminal end. Here, for example, the base station (or network) and / or terminal may inevitably encounter cases(s) that were not expected in conventional DL / UL collision handling rules, for example, cases where a quasi-statically configured DL resource collides with a quasi-statically configured UL resource and / or cases where a dynamically scheduled DL resource collides with a dynamically scheduled UL resource. Therefore, DL / UL collision handling rules for the above cases may also need to be defined. Here, for example, the base station (or network) and the terminal must perform DL / UL collision handling rules by taking into account all semi-statically configured DL transmission resource(s) and / or semi-statically configured UL transmission resource(s) and / or dynamically scheduled DL transmission resource(s) and / or dynamically scheduled DL transmission resource(s), and this can be very complex due to the large number of cases to be considered.

[0323] Accordingly, the present disclosure proposes a method in which, when a base station (or network) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, the base station (or network) and / or terminal distinguish steps based on resource types and sequentially perform a determination of whether a DL / UL collision has occurred and / or a DL / UL collision handling rule according to the steps. In the first step, the base station (or network) and / or terminal can perform a determination of whether a DL / UL collision has occurred and / or a DL / UL collision handling rule related to a semi-statically configured resource. For example, a determination of whether a (DL / UL) collision has occurred and / or a (DL / UL) collision handling rule can be applied between a DL transmission resource (semi-statically configured) and a UL transmission resource (semi-statically configured). Subsequently, in the second step, the base station (or network) and / or terminal can perform a determination of whether a DL / UL collision has occurred and / or a DL / UL collision handling rule related to a dynamically scheduled resource during the second step. For example, a collision determination (DL / UL) and / or (DL / UL) collision handling rule can be applied between a (dynamically scheduled) DL transport resource and a (semi-statically configured and / or dynamically scheduled) UL transport resource. For example, a collision determination (DL / UL) and / or (DL / UL) collision handling rule can be applied between a (dynamically scheduled) UL transport resource and a (semi-statically configured and / or dynamically scheduled) DL transport resource.

[0324] According to the proposed method of the present disclosure above, when a base station (or network) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, the computational process of the base station (or network) and / or terminal can be simplified and the complexity can be reduced.

[0325] The above [Proposed Plan #04] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0326] [Proposed Method #05] When a base station (or network) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, a (potential) UL transmission interval (hereinafter referred to as the first UL transmission interval) that may collide with a (specific) DL transmission resource is derived, and for a UL transmission (e.g., PUSCH and / or PUCCH) to which DM-RS Bundling and / or TDW (Time Domain Window) is applied, the terminal may perform one or more of the following operations.

[0327] (1) Exclude the 1st UL transmission section from the (actual) TDW section

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

[0329] (2) Omission of UL transmission within the first UL transmission interval

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

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

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

[0333] Here, for example, the DM-RS Bundling mentioned above may mean an operation that performs channel estimation by utilizing DM-RS resource(s) between UL repeated transmissions.

[0334] Here, for example, the above TDW may refer to a (time) interval that guarantees the phase continuity and / or power consistency of the signal when the terminal transmits a UL. For example, a base station (or network) and / or a terminal may set / agree on a (nominal) TDW interval for a specific UL transmission, and may interpret the (actual) TDW interval based on the time when an Event occurs within the UL transmission. For example, the interval from the start of the UL transmission until the occurrence of the Event may be interpreted as the (actual) TDW interval, and thereafter, the (actual) TDW interval may be (re)started according to the setting within the remaining (nominal) TDW interval.

[0335] For example, let us assume that in a non-terrestrial network according to one embodiment of the present disclosure, a base station (or network) services a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, for example, when the terminal operates in a half-duplex transmission mode, it cannot perform DL reception and UL transmission simultaneously, and if the timing of DL reception and the timing of UL transmission conflict, the terminal may prioritize DL reception and / or UL transmission according to a DL / UL collision handling rule pre-agreed upon / set with the base station.

[0336] Here, for example, in the uplink of a non-terrestrial network, the terminal may apply a (shared) 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 (shared) TA may be a value mutually recognized through shared parameters and calculation formulas between the base station (or network) and the terminal, and the (UE) TA may be a value that is voluntarily adjusted by the terminal and is unknown to the base station (or network). Here, for example, the TA that the base station (or network) expects / predicts for the terminal (first TA) and the TA that the terminal actually applies (second TA) may have different values.

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

[0338] Accordingly, the present disclosure proposes a method in which, when a base station (or network) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, a (potential) UL transmission interval that may collide with a (specific) DL transmission resource is derived, and the terminal performs one or more of the following operations for UL transmissions (e.g., PUSCH and / or PUCCH) to which DM-RS Bundling and / or TDW (Time Domain Window) is applied. For example, the terminal may exclude the (potential) UL transmission interval from the (actual) TDW interval and / or omit UL transmission within the (potential) UL transmission interval. For example, under a specific TA assumption, the base station (or network) and / or the terminal may determine a UL transmission interval that is within a GT (Guard Time) of a specific DL transmission resource as a (potential) UL transmission interval that may collide. Subsequently, the terminal may omit actual UL transmission for the said (potential) UL transmission interval. Alternatively, the terminal may omit transmission only for UL resources where actual collisions have occurred based on the UL TA derived by itself, while ensuring that the base station (or network) and / or the terminal do not expect phase continuity and / or power consistency within the (potential) UL transmission interval. For example, even if the base station detects actual UL transmission within the (potential) UL transmission interval, it may exclude it from DM-RS bundling targets.

[0339] According to the proposed method of the present disclosure above, when a base station (or network) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to half-duplex transmission mode, it can help the base station (or network) and / or terminal to equally understand the sections where DM-RS Bundling is applicable and / or (actual) TDW sections and / or sections where the phase continuity and / or power consistency of the UL signal is guaranteed. Through this, it is possible to prevent the base station from applying DM-RS Bundling to the wrong sections, thereby preventing the degradation of UL reception performance.

[0340] The above [Proposed Plan #05] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0341] [Proposed Method #06] When a base station (or network) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to half-duplex transmission mode, in the event of a collision between a plurality of DL transmission resource(s) (hereinafter referred to as the first resource group) and a plurality of UL transmission resource(s) (the second resource group), the DL / UL collision handling rules can be performed based on the resource with the highest priority (or the corresponding priority value) in the first resource group and the resource with the highest priority (or the corresponding priority value) in the second resource group.

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

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

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

[0345] For example, let us assume that in a non-terrestrial network according to one embodiment of the present disclosure, a base station (or network) services a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, for example, when the terminal operates in a half-duplex transmission mode, it cannot perform DL reception and UL transmission simultaneously, and if the timing of DL reception and the timing of UL transmission conflict, the terminal may prioritize DL reception and / or UL transmission according to a DL / UL collision handling rule pre-agreed upon / set with the base station.

[0346] Here, for example, in the uplink of a non-terrestrial network, the terminal may apply a (shared) 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 (shared) TA may be a value mutually recognized through shared parameters and calculation formulas between the base station (or network) and the terminal, and the (UE) TA may be a value that is voluntarily adjusted by the terminal and is unknown to the base station (or network). Here, for example, the TA that the base station (or network) expects / predicts for the terminal (first TA) and the TA that the terminal actually applies (second TA) may have different values.

[0347] Here, for example, due to reasons such as the above TA, a case may occur where one DL transmission resource collides with two UL transmission resource(s) or one UL transmission resource collides with two DL transmission resource(s). Here, for example, the terminal may regard the above multiple collision situation as a situation in which DL / UL one-to-one collision situations are mixed and apply DL / UL collision handling rules sequentially. However, when multiple transmission resource(s) collide as above, applying the handling rules for conventional DL / UL one-to-one collisions may be a method that increases the implementation complexity of the terminal. Accordingly, the present disclosure proposes a method for performing DL / UL collision handling rules based on the highest priority resource (or corresponding priority value) within the first resource group and the highest priority resource (or corresponding priority value) within the second resource group when a collision occurs between a plurality of DL transmission resource(s) (hereinafter referred to as the first resource group) and a plurality of UL transmission resource(s) (the second resource group) when a base station (or network) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode. For example, let one semi-statically configured DL transmission resource (the first DL resource) collide with two UL transmission resource(s), and let one of the two UL transmission resources be a dynamically scheduled UL transmission resource (the first UL resource) and the other be a semi-statically configured UL transmission resource (the second UL resource). Here, for example, a dynamically scheduled UL transmission resource may have a higher priority than a semi-statically set UL transmission resource. Therefore, a DL / UL collision handling rule can be applied between the first DL resource and the first UL resource.For example, according to conventional DL / UL collision handling rules, since dynamically scheduled resources have a higher priority than semi-statically configured resources, reception of the first DL resource may be omitted and transmission to the UL transmission resource group (i.e., the first and second UL resources) may be prioritized. According to the proposed method of the present disclosure, in a situation where a terminal must perform collision handling rules between multiple DL resources and multiple UL resources, there is an advantage of simplifying the terminal's DL / UL collision handling rules by applying a representative resource-based DL / UL collision handling rule (with a higher priority) within each resource group.

[0348] The above [Proposed Plan #06] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0349] [Proposed Method #07] When a base station (or network) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to half-duplex transmission mode, one or more of the following DL transmission resource(s) can be determined as colliding DL transmission resource(s) based on a (specific) UL transmission resource (hereinafter referred to as the first resource).

[0350] (1) A DL transmission resource that is dynamically scheduled and has a time resource that overlaps with the first resource

[0351] (1) A. Here, for example, the control signal (e.g., DCI) that schedules the DL transmission resource is from the starting point of the first resource T PROC,2 It may be the case that it was transmitted and / or detected prior to the time. Otherwise, the DL transmission resource may not be determined as a collision resource.

[0352] (2) A DL transmission resource that is semi-statically configured and has a time resource that overlaps with the first resource

[0353] (2) A. Here, for example, a control signal (e.g., DCI) that activates the DL transmission resource is from the starting point of the first resource T PROC,2 It may be the case that it was transmitted and / or detected prior to the time. Otherwise, the DL transmission resource may not be determined as a collision resource.

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

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

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

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

[0358] Here, for example, the above T PROC,2 This may refer to the processing time required by the terminal for uplink transmission and / or control signal detection.

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

[0360] For example, let us assume that in a non-terrestrial network according to one embodiment of the present disclosure, a base station (or network) services a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, for example, when the terminal operates in a half-duplex transmission mode, it cannot perform DL reception and UL transmission simultaneously, and if the timing of DL reception and the timing of UL transmission conflict, the terminal may prioritize DL reception and / or UL transmission according to a DL / UL collision handling rule pre-agreed upon / set with the base station.

[0361] Here, for example, in the uplink of a non-terrestrial network, the terminal may apply a (shared) 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 (shared) TA may be a value mutually recognized through shared parameters and calculation formulas between the base station (or network) and the terminal, and the (UE) TA may be a value that is voluntarily adjusted by the terminal and is unknown to the base station (or network). Here, for example, the TA that the base station (or network) expects / predicts for the terminal (first TA) and the TA that the terminal actually applies (second TA) may have different values.

[0362] Therefore, in non-terrestrial networks, DL / UL collision cases (hereinafter error cases) that conventional base stations (or networks) were expected to avoid (e.g., collisions between dynamically scheduled DL transmission resources and dynamically scheduled UL transmission resources and / or collisions between semi-statically configured DL transmission resources and semi-statically configured UL transmission resources) may occur relatively frequently, and DL / UL collision handling rules for terminals operating in half-duplex transmission mode for said cases may need to be defined. As described above, if DL / UL collision handling rules for conventional error cases are defined, the DL / UL collision handling rules may become complex. For example, conventionally, a semi-statically configured UL transmission resource could only collide with a dynamically scheduled DL transmission resource, and in such cases, dynamic scheduling took precedence; however, if new case(s) are allowed, a semi-statically configured UL transmission resource can collide with a semi-statically scheduled DL transmission resource in addition to a dynamically scheduled DL transmission resource. Here, for example, if collision case(s) are mixed, there must be an agreement between the base station (or network) and the terminal regarding the order of resolving the collision case(s). Otherwise, the transmission and reception resources expected by the base station (or network) and the transmission and reception resources expected by the terminal may differ, preventing normal transmission and reception, and resulting in resource waste.

[0363] For example, thus in the present disclosure, when a base station (or network) and / or a terminal in a non-terrestrial network can perform a DL / UL collision handling rule according to a half-duplex transmission mode, the terminal can determine one or more of the following DL transmission resource(s) as colliding DL transmission resource(s) based on a (specific) UL transmission resource (hereinafter referred to as the first resource).

[0364] (1) A DL transmission resource that is dynamically scheduled and has a time resource that overlaps with the first resource

[0365] (1) A. Here, for example, the control signal (e.g., DCI) that schedules the DL transmission resource is from the starting point of the first resource T PROC,2 It may be the case that it was transmitted and / or detected prior to the time. Otherwise, the DL transmission resource may not be determined as a collision resource.

[0366] (2) A DL transmission resource that is semi-statically configured and has a time resource that overlaps with the first resource

[0367] (2) A. Here, for example, a control signal (e.g., DCI) that activates the DL transmission resource is from the starting point of the first resource T PROC,2 It may be the case that it was transmitted and / or detected prior to the time. Otherwise, the DL transmission resource may not be determined as a collision resource.

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

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

[0370] Here, for example, depending on the transmission type and / or priority information of the UL transmission resource and the DL transmission resource, the terminal processing time may or may not be considered when determining a DL / UL collision. Here, for example, if the UL transmission resource has a higher priority than the DL transmission resource, the processing time may not be considered when determining a DL / UL collision, and if the UL transmission resource has a lower priority than the DL transmission resource, the processing time may be considered when determining a DL / UL collision. For example, when a semi-statically configured UL transmission resource and a semi-statically configured DL transmission resource overlap on the time axis, the terminal may determine a DL / UL collision situation without considering processing time if the UL transmission resource has a higher priority than the DL transmission resource. On the other hand, if the UL transmission resource has a lower priority than the DL transmission resource, the terminal determines that the control signal (e.g., DCI) activating the corresponding DL transmission resource occurs a specific processing time prior to the start point of the UL transmission resource (e.g., T PROC,2 A DL / UL collision situation can be determined only when transmitted and / or detected at ). For example, when a dynamically scheduled UL transmission resource and a dynamically scheduled DL transmission resource overlap on the time axis, the terminal may determine a DL / UL collision situation without considering computation time if the UL transmission resource has a higher priority than the DL transmission resource. On the other hand, if the UL transmission resource has a lower priority than the DL transmission resource, the terminal determines that the control signal (e.g., DCI) scheduling the DL transmission resource is at a specific computation time prior to the start point of the UL transmission resource (e.g., T PROC,2 A DL / UL collision situation can be determined only when transmitted to and / or detected in ).

[0371] According to the proposed method of the present disclosure above, by clarifying the DL / UL collision determination process of the terminal in a situation where various types of collision cases are mixed, the same understanding can be achieved between the base station (or network) and the terminal regarding DL / UL collision determination and / or the application of DL / UL collision handling rules. This supports the correct transmission and reception process and prevents resource waste.

[0372] The above [Proposed Plan #07] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0373] [Proposed Method #08] When a base station (or network) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to half-duplex transmission mode, the terminal can perform DL / UL collision handling rules as follows.

[0374] (1) Step 1: A step of selecting a (specific) UL transmission resource (hereinafter Resource A).

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

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

[0377] (2) Step 2: Determining conflicting DL transmission resource(s) based on Resource A and performing DL / UL collision handling rules (for Resource A).

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

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

[0380] (3) Step 3: A step of repeating Steps 1 and 2 above.

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

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

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

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

[0385] For example, let us assume that in a non-terrestrial network according to one embodiment of the present disclosure, a base station (or network) services a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, for example, when the terminal operates in a half-duplex transmission mode, it cannot perform DL reception and UL transmission simultaneously, and if the timing of DL reception and the timing of UL transmission conflict, the terminal may prioritize DL reception and / or UL transmission according to a DL / UL collision handling rule pre-agreed upon / set with the base station.

[0386] Here, for example, in the uplink of a non-terrestrial network, the terminal may apply a (shared) 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 (shared) TA may be a value mutually recognized through shared parameters and calculation formulas between the base station (or network) and the terminal, and the (UE) TA may be a value that is voluntarily adjusted by the terminal and is unknown to the base station (or network). Here, for example, the TA that the base station (or network) expects / predicts for the terminal (first TA) and the TA that the terminal actually applies (second TA) may have different values.

[0387] Therefore, in non-terrestrial networks, DL / UL collision cases (hereinafter error cases) that conventional base stations (or networks) were expected to avoid (e.g., collisions between dynamically scheduled DL transmission resources and dynamically scheduled UL transmission resources and / or collisions between semi-statically configured DL transmission resources and semi-statically configured UL transmission resources) may occur relatively frequently, and DL / UL collision handling rules for terminals operating in half-duplex transmission mode for said cases may need to be defined. As described above, if DL / UL collision handling rules for conventional error cases are defined, the DL / UL collision handling rules may become complex. For example, conventionally, a semi-statically configured UL transmission resource could only collide with a dynamically scheduled DL transmission resource, and in such cases, dynamic scheduling took precedence; however, if new case(s) are allowed, a semi-statically configured UL transmission resource can collide with a semi-statically scheduled DL transmission resource in addition to a dynamically scheduled DL transmission resource. Here, for example, if collision case(s) are mixed, there must be an agreement between the base station (or network) and the terminal regarding the order of resolving the collision case(s). Otherwise, the transmission and reception resources expected by the base station (or network) and the transmission and reception resources expected by the terminal may differ, preventing normal transmission and reception, and resulting in resource waste.

[0388] 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 perform DL / UL collision handling rules as follows.

[0389] (1) Step 1: A step of selecting a (specific) UL transmission resource (hereinafter Resource A).

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

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

[0392] (2) Step 2: Determining conflicting DL transmission resource(s) based on Resource A and performing DL / UL collision handling rules (for Resource A).

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

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

[0395] (3) Step 3: A step of repeating Steps 1 and 2 above.

[0396] For example, the terminal may select a UL transmission resource (hereinafter referred to as Resource A) that has an earlier transmission time on the time axis among UL transmission resource(s) to which DL / UL collision judgment and / or DL / UL collision handling rules are not applied, and may determine the conflicting DL transmission resource(s) based on Resource A as in [Proposed Method #7] of the present disclosure. Here, for example, if at least one DL transmission resource among the conflicting DL transmission resource(s) has a higher priority than Resource A, the terminal may omit and / or cancel the transmission of Resource A. Otherwise, the terminal may transmit Resource A and not receive the conflicting DL transmission resource(s). Then, the terminal may select the UL transmission resource with the next earlier transmission time among UL transmission resource(s) to which DL / UL collision judgment and / or DL / UL collision handling rules are not applied, and repeat the above process.

[0397] According to the proposed method of the present disclosure above, by clarifying the DL / UL collision determination process of the terminal in a situation where various types of collision cases are mixed, the same understanding can be achieved between the base station (or network) and the terminal regarding DL / UL collision determination and / or the application of DL / UL collision handling rules. This supports the correct transmission and reception process and prevents resource waste.

[0398] The above [Proposed Plan #08] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0399] For example, for (e)RedCap HD-FDD UEs for NTN, it is necessary to review at least the following types. For example, considering the discrepancy between the TA actually used by the UE and the TA assumed by the gNB based on available TA reports, whether to reuse or update existing handling rules for the following types:

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

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

[0402] - Type 3: When a semi-statically configured DL reception conflicts with a semi-statically configured UL transmission

[0403] - Type 4: When a dynamically scheduled DL reception conflicts with a dynamically scheduled UL transmission

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

[0405] - Type 6: When a dynamic or semi-static DL conflicts with a valid RO

[0406] - Type 7: Case where a collision occurs due to a change in transmission direction

[0407] For example, the Timing Advance reporting procedure reports the UE's Timing Advance value (e.g., T) to the gNB in ​​a Non-Ground Network (NTN) or Air-to-Ground Network. TA It is used to provide ).

[0408] For example, RRC controls timing advance reporting by setting the following parameters.

[0409] - offsetThresholdTA

[0410] - timingAdvanceSR

[0411] For example, Timing Advance Report (TAR) must be triggered when one of the following events occurs.

[0412] - When there is a directive from the upper layer to trigger a timing advance report

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

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

[0415] For example, the MAC entity must perform the following.

[0416] 1> If the Timing Advance Reporting Procedure determines that one or more TARs were triggered and not cancelled:

[0417] 2> If the UL-SCH resource is available for a new transmission and, as a result of the logical channel priority, the UL-SCH resource can accommodate the Timing Advance Report MAC CE and its subheader:

[0418] 3> Instruct the Multiplexing and Assembly procedure to generate the timing advance report MAC CE as defined in Section 6.1.3.56.

[0419] 2> Otherwise,

[0420] 3> If timingAdvanceSR is set to an enabled value:

[0421] 4> Trigger a scheduling request.

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

[0423] For example, a single MAC PDU must contain at most one Timing Advance Report MAC CE, even if multiple events trigger Timing Advance Reporting. The Timing Advance Report MAC CE must be generated based on the latest available UE Timing Advance estimate immediately prior to MAC PDU assembly.

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

[0425] Terminals operating in half-duplex transmission mode (HD-FDD) on non-terrestrial networks cannot simultaneously perform downlink (DL) reception and uplink (UL) transmission. As a result, situations may occur where the time of DL reception and the time of UL transmission overlap or collide on the time axis. In particular, once a collision between semi-static resources occurs, it can occur repeatedly until the resources are reset, raising concerns that the Timing Advance (TA) error may persist for a long period.

[0426] In existing technologies, TA reporting is performed at relatively long intervals or triggered by simple offset conditions, so the following problems exist.

[0427] 1. Even if the difference between the TA recognized by the base station (1st TA) and the TA actually applied by the terminal (2nd TA) increases, reporting is delayed, and DL / UL timing synchronization mismatch may persist for a long period.

[0428] 2. Even collisions intentionally scheduled by the base station are included in the reporting targets, which can lead to unnecessary waste of UL transmission resources.

[0429] 3. By applying uniform reporting standards without considering the characteristics of each collision type, unnecessary reporting occurs even for collisions with low reproducibility or those already recognized by the base station.

[0430] Therefore, for some specific collision types among multiple collision types (e.g., collisions between semi-static DL resources and semi-static UL resources), there is a need for a technology that can quickly correct TA discrepancies, reduce unnecessary reporting, and quickly respond to problem situations that the base station has not recognized by triggering TA reporting based on the (consecutive) occurrence count, occurrence rate, or occurrence time of the collision.

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

[0432] Referring to FIG. 24, for example, at step S2410, the first device may obtain information related to a semi-statically configured downlink resource. For example, the first device may receive information related to a semi-statically configured downlink resource from the second device. For example, at step S2420, the first device may obtain information related to a semi-statically configured uplink resource. For example, the first device may receive information related to a semi-statically configured uplink resource from the second device. For example, at step S2430, the first device may perform a timing advance report. For example, the timing advance report may be triggered based on a downlink reception based on information related to the semi-statically configured downlink resource colliding with an uplink transmission based on information related to the semi-statically configured uplink resource. For example, the first device may be a terminal. For example, the second device may be a base station, a network node, or a satellite. For example, the first device and / or the second device may be associated with a non-ground network.

[0433] [Proposed Method #09] When a base station (or network node) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to half-duplex transmission mode, and when there may be multiple collision types for the DL / UL collision, the terminal can trigger a TA report based on the (consecutive) occurrence count and / or ratio and / or time for some specific collision type among the multiple collision types.

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

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

[0436] Here, for example, some of the specific conflict types mentioned above may be conflict types that include semi-static DL resources and / or semi-static UL resources. For example, it may be a conflict type that conflicts between semi-static DL resources and semi-static UL resources.

[0437] Here, for example, some specific types of collisions mentioned above may be (pre)defined and / or set and / or instructed by the base station (or network node) to the terminal.

[0438] For example, let us assume that in a non-terrestrial network according to one embodiment of the present disclosure, a base station (or network) services a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, when the terminal operates in a half-duplex transmission mode, it cannot perform DL reception and UL transmission simultaneously, and if the timing of DL reception and the timing of UL transmission conflict, the terminal may prioritize performing DL reception and / or UL transmission according to a DL / UL collision handling rule pre-agreed upon / set with the base station.

[0439] Here, in the uplink of a non-terrestrial network, the terminal may apply a (shared) TA (Timing Advance) that compensates for the time delay between the feeder link and the satellite, and a (UE) TA that compensates for the time delay between the terminal and the satellite. Here, the (shared) TA may be a value mutually recognized through shared parameters and calculation formulas between the base station (or network) and the terminal, and the (UE) TA may be a value that is voluntarily adjusted by the terminal and is unknown to the base station (or network). Here, the TA that the base station (or network) expects / predicts for the terminal (first TA) and the TA that the terminal actually applies (second TA) may have different values.

[0440] Here, in a non-terrestrial network, a terminal can perform a TA report. However, the TA report may be reported at relatively long intervals, and depending on the threshold setting for the TA report, the actual TA value applied by the terminal may differ significantly from the previously reported TA. Here, if the base station assumes the TA reported by the terminal as the first TA, the difference between it and the second TA actually applied by the terminal may gradually increase. Here, to quickly reduce the difference between the first TA and the second TA, a method may be considered in which the terminal triggers a TA report when a DL / UL collision occurs. Here, if the terminal performs a TA report for any arbitrary DL / UL collision, it may trigger a TA report even for DL / UL collisions intentionally scheduled by the base station (or network node), thereby wasting unnecessary UL resources. Accordingly, in the present disclosure, when a base station (or network node) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, and when there may be multiple collision types for said DL / UL collision, the terminal may trigger a TA report based on the (consecutive) occurrence count and / or ratio and / or time of some specific collision types among said multiple collision types. Here, for example, said specific collision types may be collision types including semi-static DL resources and / or semi-static UL resources. For example, it may be a collision type in which a semi-static DL resource and a semi-static UL resource collide. Here, for example, since a collision between said semi-static DL resources and semi-static UL resources may occur repeatedly in the future until resource reset once a collision occurs, it may be a desirable operation for the terminal to report to the base station regarding the occurrence of said collision.Here, for example, a conflict between a dynamically scheduled DL resource and a dynamically scheduled UL resource may have a long time between occurrences and a low frequency of occurrence once a conflict occurs. Therefore, for the above type of conflict, the action of triggering a TA report may be a reactive measure and may be an action with low effectiveness.

[0441] According to the proposed method of the present disclosure above, when a terminal triggers a TA report based on a DL / UL collision, it is possible to support an effective TA reporting operation for problem situations that the base station has not recognized by not triggering unnecessary TA reports for DL / UL collisions that the base station has already recognized and intentionally scheduled, and / or DL / UL collisions with low reproducibility.

[0442] The above [Proposed Plan #09] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0443] [Proposed Method #10] When a base station (or network node) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to half-duplex transmission mode, the base station (or network node) can inform the terminal whether a specific DL / UL collision is an intended scheduling.

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

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

[0446] For example, let us assume that in a non-terrestrial network according to one embodiment of the present disclosure, a base station (or network) services a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, when the terminal operates in a half-duplex transmission mode, it cannot perform DL reception and UL transmission simultaneously, and if the timing of DL reception and the timing of UL transmission conflict, the terminal may prioritize performing DL reception and / or UL transmission according to a DL / UL collision handling rule pre-agreed upon / set with the base station.

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

[0448] Here, in a non-terrestrial network, a terminal can perform a TA report. However, the TA report may be reported at relatively long intervals, and depending on the threshold setting for the TA report, the actual TA value applied by the terminal may differ significantly from the previously reported TA. Here, if the base station assumes the TA reported by the terminal as the first TA, the difference between it and the second TA actually applied by the terminal may gradually increase. Here, to quickly reduce the difference between the first TA and the second TA, a method may be considered in which the terminal triggers a TA report when a DL / UL collision occurs. Here, if the terminal performs a TA report for any arbitrary DL / UL collision, it may trigger a TA report even for DL / UL collisions intentionally scheduled by the base station (or network node), thereby wasting unnecessary UL resources. Accordingly, in the present disclosure, when a base station (or network node) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, the base station (or network node) may inform the terminal whether a specific DL / UL collision is an intended scheduling. Here, for example, the terminal may trigger a TA report based on the number and / or rate and / or time, etc., of occurrences of DL / UL collisions that were not intentionally scheduled by the base station (or network node).

[0449] According to the proposed method of the present disclosure above, when a terminal triggers a TA report based on a DL / UL collision, it is possible to support an effective TA reporting operation for problem situations that the base station has not recognized by not triggering unnecessary TA reports for DL / UL collisions that the base station has already recognized and intentionally scheduled, and / or DL / UL collisions with low reproducibility.

[0450] The above [Proposed Plan #10] may be applied in combination with other proposed plans(s) to the extent that the proposed operations do not conflict.

[0451] [Proposed Method #11] When a base station (or network node) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to half-duplex transmission mode, the terminal can trigger a TA report based on the (consecutive) occurrence count and / or rate and / or time of at least one of the following events.

[0452] (1) When the TA calculated by the terminal is outside the predicted TA interval and a DL / UL collision occurs

[0453] (2) In the case where a DL / UL collision occurs that does not collide based on the TA within the predicted TA interval, but collides based on the TA calculated by the terminal

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

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

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

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

[0458] Here, for example, the TA calculated by the terminal may mean the UL TA and / or Actual TA used for actual UL transmission at the terminal.

[0459] For example, let us assume that in a non-terrestrial network according to one embodiment of the present disclosure, a base station (or network) services a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, when the terminal operates in a half-duplex transmission mode, it cannot perform DL reception and UL transmission simultaneously, and if the timing of DL reception and the timing of UL transmission conflict, the terminal may prioritize performing DL reception and / or UL transmission according to a DL / UL collision handling rule pre-agreed upon / set with the base station.

[0460] Here, in the uplink of a non-terrestrial network, the terminal may apply a (shared) TA (Timing Advance) that compensates for the time delay between the feeder link and the satellite, and a (UE) TA that compensates for the time delay between the terminal and the satellite. Here, the (shared) TA may be a value mutually recognized through shared parameters and calculation formulas between the base station (or network) and the terminal, and the (UE) TA may be a value that is voluntarily adjusted by the terminal and is unknown to the base station (or network). Here, the TA that the base station (or network) expects / predicts for the terminal (first TA) and the TA that the terminal actually applies (second TA) may have different values.

[0461] Here, in a non-terrestrial network, a terminal can perform a TA report. However, the TA report may be reported at relatively long intervals, and depending on the threshold setting for the TA report, the actual TA value applied by the terminal may differ significantly from the previously reported TA. Here, if the base station assumes the TA reported by the terminal as the first TA, the difference between it and the second TA actually applied by the terminal may gradually increase. Here, to quickly reduce the difference between the first TA and the second TA, a method may be considered in which the terminal triggers a TA report when a DL / UL collision occurs. Here, if the terminal performs a TA report for any arbitrary DL / UL collision, it may trigger a TA report even for DL / UL collisions intentionally scheduled by the base station (or network node), thereby wasting unnecessary UL resources. Accordingly, in the present disclosure, when a base station (or network node) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, the terminal can trigger a TA report based on the (consecutive) occurrence count and / or rate and / or time of at least one of the following events.

[0462] (1) When the TA calculated by the terminal is outside the predicted TA interval and a DL / UL collision occurs

[0463] (2) In the case where a DL / UL collision occurs that does not collide based on the TA within the predicted TA interval, but collides based on the TA calculated by the terminal

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

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

[0466] According to the proposed method of the present disclosure above, when a terminal triggers a TA report based on a DL / UL collision, it is possible to support an effective TA reporting operation for problem situations that the base station has not recognized by not triggering unnecessary TA reports for DL / UL collisions that the base station has already recognized and intentionally scheduled, and / or DL / UL collisions with low reproducibility.

[0467] The above [Proposed Plan #11] may be applied in combination with other proposed plans(s) to the extent that the proposed operations do not conflict.

[0468] [Proposed Method #12] When a base station (or network node) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to half-duplex transmission mode, and when the terminal can trigger a TA report and / or a TA report purpose SR (Scheduling Request) based on the occurrence of a DL / UL collision, the terminal can transmit the TA report and / or TA report purpose SR to the base station (or network node) by distinguishing it from the conventional TA report and / or TA report purpose SR.

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

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

[0471] For example, let us assume that in a non-terrestrial network according to one embodiment of the present disclosure, a base station (or network) services a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, when the terminal operates in a half-duplex transmission mode, it cannot perform DL reception and UL transmission simultaneously, and if the timing of DL reception and the timing of UL transmission conflict, the terminal may prioritize performing DL reception and / or UL transmission according to a DL / UL collision handling rule pre-agreed upon / set with the base station.

[0472] Here, in the uplink of a non-terrestrial network, the terminal may apply a (shared) TA (Timing Advance) that compensates for the time delay between the feeder link and the satellite, and a (UE) TA that compensates for the time delay between the terminal and the satellite. Here, the (shared) TA may be a value mutually recognized through shared parameters and calculation formulas between the base station (or network) and the terminal, and the (UE) TA may be a value that is voluntarily adjusted by the terminal and is unknown to the base station (or network). Here, the TA that the base station (or network) expects / predicts for the terminal (first TA) and the TA that the terminal actually applies (second TA) may have different values.

[0473] Here, in a non-terrestrial network, a terminal can perform a TA report. However, the TA report may be reported at relatively long intervals, and depending on the threshold setting for the TA report, the actual TA value applied by the terminal may differ significantly from the previously reported TA. Here, if the base station assumes the TA reported by the terminal as the first TA, the difference between it and the second TA actually applied by the terminal may gradually increase. Here, to quickly reduce the difference between the first TA and the second TA, a method may be considered in which the terminal triggers a TA report when a DL / UL collision occurs. Here, if the terminal performs a TA report for any arbitrary DL / UL collision, it may trigger a TA report even for DL / UL collisions intentionally scheduled by the base station (or network node), thereby wasting unnecessary UL resources. Accordingly, in the present disclosure, when a base station (or network node) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, and when the terminal can trigger a TA report and / or a TA report purpose SR (Scheduling Request) based on the occurrence of a DL / UL collision, the terminal can transmit the TA report and / or TA report purpose SR to the base station (or network node) by distinguishing it from a conventional TA report and / or TA report purpose SR.

[0474] According to the proposed method of the present disclosure above, the base station can distinguish between cases where TA reporting is triggered by exceeding the TA threshold setting and cases where TA reporting is triggered due to DL / UL collision detection even though TA is still within the threshold range, and thereby determine whether to allocate UL transmission resources for TA reporting. This has the advantage of enabling efficient management of UL resource allocation for TA reporting.

[0475] The above [Proposed Plan #12] may be applied in combination with other proposed plans(s) to the extent that the proposed operations do not conflict.

[0476] [Proposed Method #13] When a base station (or network node) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to half-duplex transmission mode, the base station may set and / or direct the priority setting between DL transmission and UL transmission for a specific DL / UL collision type through one or more of the following signalings.

[0477] (1) RRC signaling

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

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

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

[0481] Here, for example, the specific DL / UL collision type may be a type in which a dynamically scheduled DL and a dynamically scheduled UL collide and / or a type in which a semi-statically set DL and a semi-statically set UL collide.

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

[0483] Here, for example, in the event of a DL / UL collision, transmissions with higher priority may be supported, while transmissions with lower priority may not be transmitted or received.

[0484] Here, for example, SIB can be system information. Here, for example, SIB can be a system information block.

[0485] For example, let us assume that in a non-terrestrial network according to one embodiment of the present disclosure, a base station (or network) services a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, when the terminal operates in a half-duplex transmission mode, it cannot perform DL reception and UL transmission simultaneously, and if the timing of DL reception and the timing of UL transmission conflict, the terminal may prioritize performing DL reception and / or UL transmission according to a DL / UL collision handling rule pre-agreed upon / set with the base station.

[0486] Here, in the uplink of a non-terrestrial network, the terminal may apply a (shared) TA (Timing Advance) that compensates for the time delay between the feeder link and the satellite, and a (UE) TA that compensates for the time delay between the terminal and the satellite. Here, the (shared) TA may be a value mutually recognized through shared parameters and calculation formulas between the base station (or network) and the terminal, and the (UE) TA may be a value that is voluntarily adjusted by the terminal and is unknown to the base station (or network). Here, the TA that the base station (or network) expects / predicts for the terminal (first TA) and the TA that the terminal actually applies (second TA) may have different values.

[0487] Accordingly, in non-terrestrial networks, DL / UL collision cases (hereinafter error cases) (e.g., collisions between dynamically scheduled DL transmission resources and dynamically scheduled UL transmission resources and / or collisions between semi-statically configured DL transmission resources and semi-statically configured UL transmission resources) that conventional base stations (or networks) were expected to avoid may occur relatively frequently, and DL / UL collision handling rules for a terminal operating in half-duplex transmission mode for said case(s) may need to be defined. Accordingly, when a base station (or network node) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to half-duplex transmission mode, the base station may set and / or indicate the priority setting between DL transmission and UL transmission for a specific DL / UL collision type through one or more of the following signalings.

[0488] (1) RRC signaling

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

[0490] Here, for example, the terminal may apply a default priority setting before receiving the priority information. For example, the default priority setting may be a predefined priority, or a method that prioritizes DL for a specific type of DL / UL collision. Or it may be a predefined priority based on the information contained in the DL / UL transmission. For example, for SIB19, it may be a method that always gives priority to UL. Here, for example, SIB may be system information. Here, for example, SIB may be a system information block.

[0491] According to the proposed method of the present disclosure above, for a specific type of DL / UL collision, the base station (or network node) can clearly set a priority for the terminal, and also supports a default priority before the setting is effective, and has the advantage of clarifying the terminal operation.

[0492] The above [Proposed Plan #13] may be applied in combination with other proposed plans(s) to the extent that the proposed operations do not conflict.

[0493] [Proposed Method #14] In a non-terrestrial network, a base station (or network node) and / or a terminal may support one or more TA reporting methods including a first TA reporting method and a second TA reporting method, and the base station (or network node) may instruct and / or set and / or trigger a first time interval to the terminal, and the terminal may apply the second TA reporting method during the first time interval and apply the first TA reporting method during other time intervals.

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

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

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

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

[0498] (1) A method of triggering TA reporting when the difference between the TA estimated at the terminal and the (recently) reported TA is greater than or equal to the first threshold.

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

[0500] (1) A method of triggering TA reporting when the difference between the TA estimated at the terminal and the (recently) reported TA is greater than or equal to the second threshold.

[0501] (2) A method for triggering a TA report when a collision between DL and UL is detected at the terminal

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

[0503] (4) A method for triggering TA reporting when the difference between the TA estimated at the terminal and the TA calculated based on the (reported) TA drift rate is greater than or equal to a second threshold.

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

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

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

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

[0508] For example, let us assume that in a non-terrestrial network according to one embodiment of the present disclosure, a base station (or network) services a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, when the terminal operates in a half-duplex transmission mode, it cannot perform DL reception and UL transmission simultaneously, and if the timing of DL reception and the timing of UL transmission conflict, the terminal may prioritize performing DL reception and / or UL transmission according to a DL / UL collision handling rule pre-agreed upon / set with the base station.

[0509] Here, in the uplink of a non-terrestrial network, the terminal may apply a (shared) TA (Timing Advance) that compensates for the time delay between the feeder link and the satellite, and a (UE) TA that compensates for the time delay between the terminal and the satellite. Here, the (shared) TA may be a value mutually recognized through shared parameters and calculation formulas between the base station (or network) and the terminal, and the (UE) TA may be a value that is voluntarily adjusted by the terminal and is unknown to the base station (or network). Here, the TA that the base station (or network) expects / predicts for the terminal (first TA) and the TA that the terminal actually applies (second TA) may have different values.

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

[0511] (1) A method of triggering TA reporting when the difference between the TA estimated at the terminal and the (recently) reported TA is greater than or equal to the first threshold.

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

[0513] (1) A method of triggering TA reporting when the difference between the TA estimated at the terminal and the (recently) reported TA is greater than or equal to the second threshold.

[0514] (2) A method for triggering a TA report when a collision between DL and UL is detected at the terminal

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

[0516] (4) A method for triggering TA reporting when the difference between the TA estimated at the terminal and the TA calculated based on the (reported) TA drift rate is greater than or equal to a second threshold.

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

[0518] According to the proposed method of the present disclosure above, an enhanced TA reporting method for mitigating TA discrepancies between a terminal and a base station (or network node) in a non-terrestrial network is supported, and the signaling load can be reduced by adaptively applying the enhanced TA reporting method to time intervals that the base station (or network node) determines are necessary.

[0519] The above [Proposed Plan #14] may be applied in combination with other proposed plans(s) to the extent that the proposed operations do not conflict.

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

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

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

[0523] (1) A method of triggering TA reporting when the difference between the TA estimated at the terminal and the (recently) reported TA is greater than or equal to the first threshold.

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

[0525] (1) A method of triggering TA reporting when the difference between the TA estimated at the terminal and the (recently) reported TA is greater than or equal to the second threshold.

[0526] (2) A method for triggering a TA report when a collision between DL and UL is detected at the terminal

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

[0528] (4) A method for triggering TA reporting when the difference between the TA estimated at the terminal and the TA calculated based on the (reported) TA drift rate is greater than or equal to a second threshold.

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

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

[0531] Here, for example, the second TA reporting method may be a method that utilizes a finer TA reporting granularity and / or a smaller TA offset threshold compared to the first TA reporting method. Here, for example, the terminal may trigger a TA report if the difference between the actual TA and the reported TA is greater than or exceeds the TA offset threshold.

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

[0533] (1) When TA reporting is performed a certain number of times (e.g., N times) or more based on the 2nd TA reporting method

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

[0535] Here, for example, the above-mentioned fixed number of times (e.g., N) and / or fixed time (e.g., T) may be values ​​that the base station (or network node) (pre)defines and / or sets and / or instructs the terminal. For example, N may be 1.

[0536] For example, let us assume that in a non-terrestrial network according to one embodiment of the present disclosure, a base station (or network) services a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, when the terminal operates in a half-duplex transmission mode, it cannot perform DL reception and UL transmission simultaneously, and if the timing of DL reception and the timing of UL transmission conflict, the terminal may prioritize performing DL reception and / or UL transmission according to a DL / UL collision handling rule pre-agreed upon / set with the base station.

[0537] Here, in the uplink of a non-terrestrial network, the terminal may apply a (shared) TA (Timing Advance) that compensates for the time delay between the feeder link and the satellite, and a (UE) TA that compensates for the time delay between the terminal and the satellite. Here, the (shared) TA may be a value mutually recognized through shared parameters and calculation formulas between the base station (or network) and the terminal, and the (UE) TA may be a value that is voluntarily adjusted by the terminal and is unknown to the base station (or network). Here, the TA that the base station (or network) expects / predicts for the terminal (first TA) and the TA that the terminal actually applies (second TA) may have different values.

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

[0539] According to the proposed method of the present disclosure above, an enhanced TA reporting method for mitigating TA discrepancies between a terminal and a base station (or network node) in a non-terrestrial network is supported, and the signaling load can be reduced by adaptively applying the enhanced TA reporting method to time intervals that the base station (or network node) determines are necessary.

[0540] The above [Proposed Plan #14-2] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0541] [Proposed Method #15] When a base station (or network node) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to half-duplex transmission mode, the terminal may not expect a case where a (single) DL (or UL) transmission resource collides with two or more UL (or DL) transmissions (hereinafter referred to as the first case).

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

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

[0544] Here, for example, when the first case above occurs, the terminal determines it to be an error situation and can perform an operation according to the terminal implementation.

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

[0546] Here, for example, the first case above may not include cases where a (single) DL (or UL) transmission resource has the same priority and / or priority rule for two or more conflicting UL (or DL) transmissions.

[0547] For example, let us assume that in a non-terrestrial network according to one embodiment of the present disclosure, a base station (or network) services a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, when the terminal operates in a half-duplex transmission mode, it cannot perform DL reception and UL transmission simultaneously, and if the timing of DL reception and the timing of UL transmission conflict, the terminal may prioritize performing DL reception and / or UL transmission according to a DL / UL collision handling rule pre-agreed upon / set with the base station.

[0548] Here, in the uplink of a non-terrestrial network, the terminal may apply a (shared) TA (Timing Advance) that compensates for the time delay between the feeder link and the satellite, and a (UE) TA that compensates for the time delay between the terminal and the satellite. Here, the (shared) TA may be a value mutually recognized through shared parameters and calculation formulas between the base station (or network) and the terminal, and the (UE) TA may be a value that is voluntarily adjusted by the terminal and is unknown to the base station (or network). Here, the TA that the base station (or network) expects / predicts for the terminal (first TA) and the TA that the terminal actually applies (second TA) may have different values.

[0549] Therefore, in non-terrestrial networks, DL / UL collision cases (hereinafter error cases) that conventional base stations (or networks) were expected to avoid (e.g., collisions between dynamically scheduled DL transmission resources and dynamically scheduled UL transmission resources and / or collisions between semi-statically configured DL transmission resources and semi-statically configured UL transmission resources) may occur relatively frequently, and DL / UL collision handling rules for terminals operating in half-duplex transmission mode for said cases may need to be defined. As described above, if DL / UL collision handling rules for conventional error cases are defined, the DL / UL collision handling rules may become complex. For example, conventionally, a semi-statically configured UL transmission resource could only collide with a dynamically scheduled DL transmission resource, and in such cases, dynamic scheduling took precedence; however, if new case(s) are allowed, a semi-statically configured UL transmission resource can collide with a semi-statically scheduled DL transmission resource in addition to a dynamically scheduled DL transmission resource. Here, if collision case(s) are mixed, there must be an agreement between the base station (or network) and the terminal regarding the order of resolving the collision case(s). Otherwise, normal transmission and reception may not occur because the transmission and reception resources expected by the base station (or network) differ from those expected by the terminal, and resource waste may result from this.

[0550] Accordingly, in the present disclosure, when a base station (or network node) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, the terminal may not expect a case (hereinafter referred to as the first case) in which a (single) DL (or UL) transmission resource collides with two or more UL (or DL) transmissions. Here, for example, the first case may be limited to a case in which a (single) DL (or UL) transmission resource has different priorities and / or priority rules for two or more UL (or DL) transmissions that collide. For example, it may be a case in which a first UL (or DL) transmission resource collides with a first DL (or UL) transmission resource and a second DL (or UL) transmission resource, and the first UL (or DL) transmission resource has a lower priority than the first DL (or UL) transmission resource and a higher priority than the second DL (or UL) transmission resource. For example, the first case above may not include cases where a (single) DL (or UL) transmission resource has the same priority and / or priority rule for two or more UL (or DL) transmissions that collide. Here, for example, when the first case above occurs, the terminal may determine it to be an error situation and perform an operation according to the terminal implementation.

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

[0552] The above [Proposed Plan #15] may be applied in combination with other proposed plans(s) to the extent that the proposed operations do not conflict.

[0553] [Proposed Method #16] When a base station (or network node) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to half-duplex transmission mode, and a (default) DL / UL priority rule (hereinafter referred to as the first priority rule) is defined and / or set, and the terminal receives a PDSCH scheduled based on a specific SS (search space) and / or a specific RNTI (radio network temporary identifier), the terminal may apply a DL / UL priority rule (hereinafter referred to as the second priority rule) different from the first priority rule to the PDSCH, and / or (exceptionally) determine the DL / UL priority according to the terminal implementation.

[0554] For example, the above specific SS may be a Type-0 / 0A / 1 / 2-PDCCH(Type-0 / 0A / 1 / 2-PDCCH(Type-0 / 0A / 1 / 2-PDCCH)) CSS(common search space).

[0555] For example, the specific RNTI mentioned above may be SI-RNTI and / or P-RNTI.

[0556] For example, when the terminal performs monitoring of the specific SS for the purpose of obtaining system information and / or related information, it may not follow the first priority rule. For example, depending on the terminal implementation, PDCCH monitoring for obtaining system information and / or related information may be performed at the specific SS.

[0557] For example, in a non-terrestrial network according to one embodiment of the present disclosure, it may be assumed that a base station (or network) services a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, for example, when the terminal operates in a half-duplex transmission mode, it cannot perform DL reception and UL transmission simultaneously, and if the timing of DL reception and the timing of UL transmission conflict, the terminal may prioritize performing DL reception and / or UL transmission according to a DL / UL collision handling rule pre-agreed upon / set with the base station.

[0558] 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 mutually recognized through shared parameters and calculation formulas between the base station (or network) and the terminal, while the (UE) TA may be a value that is voluntarily adjusted by the terminal and is unknown to the base station (or network). Here, for example, the TA that the base station (or network) expects / predicts for the terminal (first TA) and the TA that the terminal actually applies (second TA) may have different values.

[0559] Accordingly, for example, in a non-terrestrial network, DL / UL collision(s) (hereinafter error case(s)) (e.g., collisions between dynamically scheduled DL transmission resources and dynamically scheduled UL transmission resources and / or collisions between semi-statically configured DL transmission resources and semi-statically configured UL transmission resources) that conventional base stations (or networks) are expected to avoid may occur relatively frequently, and it is necessary to define DL / UL collision handling rules for a terminal operating in half-duplex transmission mode for said case(s).

[0560] Here, for example, a DL / UL priority rule (hereinafter referred to as the first priority rule) that prioritizes DL or UL may be defined. Here, for example, a specific DL transmission needs to be handled as an exception to the first priority rule. For example, the specific DL transmission may be a PDCCH and / or PDSCH associated with system information. Accordingly, in the present disclosure, for example, when a base station (or network node) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, and a (default) DL / UL priority rule (hereinafter referred to as the first priority rule) is defined and / or set, and the terminal receives a PDSCH scheduled based on a specific SS (search space) and / or a specific RNTI (radio network temporary identifier), the terminal may apply a DL / UL priority rule (hereinafter referred to as the second priority rule) different from the first priority rule to the PDSCH and / or (exceptionally) determine the DL / UL priority according to the terminal implementation.

[0561] For example, in the event of a conflict between a dynamic DL and a dynamic UL, the transmission of the UL (or DL) may be prioritized by a default priority rule, and the network may override the existing priority rule through signaling such as RRC so that the DL (or UL) takes precedence over the UL (or DL) (in a specific interval). Here, for example, the terminal may not follow the above priority rule for a PDSCH scheduled with a specific SS and / or a specific RNTI, and may prioritize the DL or UL according to the terminal implementation. For example, the specific SS may be a Type-0 / 0A / 1 / 2-PDCCH CSS. For example, the RNTI may be an SI-RNTI and / or a P-RNTI.

[0562] According to the proposed method of the present disclosure above, for example, a base station (or network node) and / or a terminal may allow the application of a DL / UL priority rule that takes precedence within the section where the transmission is expected / anticipated for a specific type of DL transmission, thereby ensuring the reception of important DL transmissions while reducing the impact on UL transmissions.

[0563] As a variation of the above proposed method, for example, when a base station (or network node) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to half-duplex transmission mode, and when a (default) DL / UL priority rule (hereinafter referred to as the first priority rule) is defined and / or set, and the terminal can receive a PDSCH based on a specific SS (search space) (e.g., Type-0 / 0A / 1 / 2 common search space) (for obtaining system information, etc.), the terminal may apply a DL / UL priority rule (hereinafter referred to as the second priority rule) different from the first priority rule to one or more of the following (specific) PDSCH types, and / or (exceptionally) determine the DL / UL priority according to the terminal implementation.

[0564] (1) PDSCH associated with system information

[0565] A. For example, it could be a PDSCH received within the SI (system information) window.

[0566] (2) PDSCH scheduled based on a specific RNTI

[0567] A. For example, the specific RNTI mentioned above may include SI-RNTI, P-RNTI, RA-RNTI, TC-RNTI, etc.

[0568] (3) PDSCH scheduled based on RNTI other than a specific RNTI

[0569] A. For example, the specific RNTI mentioned above may be a C-RNTI.

[0570] Here, for example, among the PDSCHs received based on the specific SS (search space) (e.g., Type-0 / 0A / 1 / 2 common search space), if one is not included in the PDSCH type, a first priority rule may be applied.

[0571] The above [Proposed Plan #16] may be applied in combination with other proposed plans(s) to the extent that the proposed operations do not conflict.

[0572] [Proposed Method #17] When a base station (or network node) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to half-duplex transmission mode, the base station (or network node) may explicitly and / or implicitly set and / or instruct the terminal regarding the validity time and / or expiration time of a (specific) DL / UL inter-priority rule (hereinafter referred to as the first priority rule), and the terminal may apply the (default) DL / UL inter-priority rule when the validity of the first priority rule expires.

[0573] Here, for example, the priority rule between the DL / UL mentioned above may be a rule that prioritizes either the DL or the UL.

[0574] Here, for example, the first priority rule may be set / instructed through an upper layer signal (e.g., RRC) and / or MAC CE and / or (group common) DCI.

[0575] Here, for example, the start time of the first priority rule may be implicitly determined by the time when the associated signaling is received.

[0576] Here, for example, information regarding the validity period and / or end time may be provided in the form of a timer.

[0577] For example, in a non-terrestrial network according to one embodiment of the present disclosure, it may be assumed that a base station (or network) services a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, for example, when the terminal operates in a half-duplex transmission mode, it cannot perform DL reception and UL transmission simultaneously, and if the timing of DL reception and the timing of UL transmission conflict, the terminal may prioritize performing DL reception and / or UL transmission according to a DL / UL collision handling rule pre-agreed upon / set with the base station.

[0578] 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 mutually recognized through shared parameters and calculation formulas between the base station (or network) and the terminal, while the (UE) TA may be a value that is voluntarily adjusted by the terminal and is unknown to the base station (or network). Here, for example, the TA that the base station (or network) expects / predicts for the terminal (first TA) and the TA that the terminal actually applies (second TA) may have different values.

[0579] Accordingly, for example, in a non-terrestrial network, DL / UL collision(s) (hereinafter error case(s)) (e.g., collisions between dynamically scheduled DL transmission resources and dynamically scheduled UL transmission resources and / or collisions between semi-statically configured DL transmission resources and semi-statically configured UL transmission resources) that conventional base stations (or networks) are expected to avoid may occur relatively frequently, and it is necessary to define DL / UL collision handling rules for a terminal operating in half-duplex transmission mode for said case(s).

[0580] Here, for example, the priority between DL and UL preferred by a base station (or network node) may vary depending on the physical channel and / or message and / or transmission type. Here, for example, the base station may prioritize DL or UL through signaling, etc. Here, for example, if the base station prioritizes UL, information regarding how long the rule prioritizing UL continues needs to be provided to the terminal. For example, if such information is not provided, the terminal may not properly receive the DL signal from the base station and may not be able to return to the priority rule prioritizing DL. Accordingly, in the present disclosure, for example, when a base station (or network node) and / or a terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, the base station (or network node) may explicitly and / or implicitly set and / or instruct the terminal regarding information on the validity time and / or expiration time for a (specific) DL / UL inter-priority rule (hereinafter referred to as the first priority rule), and the terminal may apply the (default) DL / UL inter-priority rule when the validity of the first priority rule expires.

[0581] If the proposed method of the present disclosure is followed, for example, when a base station can prioritize DL or UL, the priority rule may be not perpetual but expired, thereby ensuring a rollback to the default priority rule.

[0582] The above [Proposed Plan #17] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0583] FIG. 25 illustrates an example relating to a DL-UL (downlink-uplink) priority rule and CSS exception handling behavior according to one embodiment of the present disclosure. The embodiment of FIG. 25 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or behaviors of said embodiments may be omitted.

[0584] Referring to FIG. 25, for example, when a base station (or network node) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, and when a (default) DL / UL priority rule (hereinafter the first priority rule) can be defined and / or set, when the terminal receives (and / or monitors) a (specific) SS (search space) (hereinafter the first SS) and / or a (specific) PDCCH (hereinafter the first PDCCH), the terminal may support one or more of the following DL / UL collision handling schemes for the time resource in which the first SS and / or the first PDCCH was received (and / or monitored). Here, for example, the time resource monitored on the CSS may be L symbols (e.g., in units of symbols). Here, for example, CSS may be at least one of type-0 PDCCH CSS, type-0A PDCCH CSS, type-1 PDCCH CSS, or type-2 PDCCH CSS. Here, for example, L symbol may be 3 symbol. Here, for example, L symbol may be the first resource. Here, for example, the part of slot 1 excluding L symbol may be the second resource.

[0585] In a wireless communication system, a DL-UL (downlink-uplink) priority rule that prioritizes UL (uplink) can be configured. However, when monitoring the CSS (common search space) in an HD-FDD environment or a half-duplex operation environment, a conflict may occur between the UL priority rule and DL monitoring.

[0586] Furthermore, when supporting RedCap UEs in a non-terrestrial network (NTN) environment, base stations may find it difficult to accurately estimate the UE's timing advance (TA), and the timing boundary between DL and UL becomes uncertain, which can further increase the possibility of DL-UL collisions. In such environments, it is necessary to handle DL-UL collisions more conservatively and reliably.

[0587] In particular, the UE may not be able to immediately determine the existence of DCI and the collision determination result in the CSS, and the determination of the existence / absence of DCI and the related collision handling decision may not be completed immediately within the slot, but may only be determined after at least that slot. As a result, even though it may superficially appear sufficient to process only the symbol section occupied by the CSS as DL, in practice, a problem may arise where it is difficult to determine whether to initiate UL within that slot.

[0588] In addition, if the interval after CSS monitoring is defined as a UL, the base station must determine that UL transmission is possible in that interval and perform UL reception and detection. However, if the UE is unable to actually initiate the UL due to processing delays or other reasons, the base station performs unnecessary monitoring and reception operations for ULs that are not actually reached, which increases the network burden.

[0589] One embodiment of the present disclosure has the technical objective of i) stably handling collisions between CSS monitoring and UL transmission in an environment where a DL-UL priority rule prioritizing UL is configured, ii) resolving the problem of difficulty in immediately determining whether to initiate a UL within a slot due to the delay in confirming DCI processing of the UE, iii) reducing the burden of unnecessarily performing UL reception and detection for ULs that the base station does not actually reach, and iv) handling DL-UL collisions consistently and predictably even in cases where TA uncertainty exists, such as in an NTN environment.

[0590] FIG. 26 illustrates an example relating to a DL-UL (downlink-uplink) priority rule and CSS exception handling behavior according to one embodiment of the present disclosure. The embodiment of FIG. 26 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or behaviors of said embodiments may be omitted.

[0591] Referring to FIG. 26, for example, when a base station (or network node) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, and when a (default) DL / UL priority rule (hereinafter referred to as the first priority rule) can be defined and / or set, when the terminal receives (and / or monitors) a (specific) SS (search space) (hereinafter referred to as the first SS) and / or a (specific) PDCCH (hereinafter referred to as the first PDCCH), the terminal may support one or more of the following DL / UL collision handling schemes for the time resource in which the first SS and / or the first PDCCH was received (and / or monitored). Here, for example, the time resource monitored on the CSS may be L symbols (e.g., in units of symbols). Here, for example, CSS may be at least one of type-0 PDCCH CSS, type-0A PDCCH CSS, type-1 PDCCH CSS, or type-2 PDCCH CSS. Here, for example, L symbol may be 3 symbol. Here, for example, L symbol may be the first resource. Here, for example, the part of slot 1 excluding L symbol may be the second resource.

[0592] According to one embodiment of the present disclosure, for example, a DL-UL priority rule that prioritizes UL is obtained, and CSS is monitored based on said rule, but DL may be prioritized in time resources where CSS is monitored despite the rule prioritizing UL being configured. For example, said time resources may be slots, and accordingly, the entire slot where CSS is monitored may be processed with DL priority. Or, for example, said time resources may be POs (paging occasions), and DL may be prioritized in relation to CSS monitoring in POs. For example, by including DL priority not only in the first time resource where CSS is monitored but also in the second time resource adjacent to said time resource, it may be configured to absorb the DCI processing confirmation delay period of the UE.

[0593] According to the present disclosure, the following effects can be obtained.

[0594] First, even if the UE cannot immediately determine the presence / absence of DCI in CSS and the collision handling decision within the slot, the ambiguity of the UE's behavior can be eliminated by prioritizing the time resource containing CSS monitoring as DL.

[0595] Second, it can reduce the unnecessary burden of UL reception and detection on the base station that occurs when the section after CSS is maintained as UL.

[0596] Third, even in cases where TA uncertainty exists, such as in an NTN environment, system stability and procedural consistency can be improved by conservatively handling DL-UL conflicts.

[0597] Fourth, by providing a DL-UL collision handling structure that simultaneously considers UE processing delay and network reception burden, reliability and predictability at the system level can be improved.

[0598] [Proposed Method #18] When a base station (or network node) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to half-duplex transmission mode, and when a (default) DL / UL priority rule (hereinafter referred to as the first priority rule) can be defined and / or set, when the terminal receives (and / or monitors) a (specific) (common) SS (search space) (hereinafter referred to as the first SS) according to an exception handling action (that does not follow the first priority rule), the terminal may allow an exception handling action (that does not follow the first priority rule) for a PDSCH (hereinafter referred to as the first PDSCH) scheduled as a PDCCH in the first SS and / or another (specific) (common) SS (search space) (hereinafter referred to as the second SS) (other than the first SS) at the time resource in which the first SS was received (and / or monitored).

[0599] For example, the first SS and / or the second SS may be one or more of the Type-0 / 0A / 1 / 2-PDCCH(Type-0 / 0A / 1 / 2-PDCCH(Type-0 / 0A / 1 / 2-PDCCH)) CSS (common search space).

[0600] For example, the above time resource may refer to a slot and / or a paging occasion (PO).

[0601] For example, the above exception handling operation may mean an operation that prioritizes DL or UL depending on the terminal implementation.

[0602] For example, the above-mentioned first PDSCH may mean a PDSCH scheduled within the same time resource (and / or slot) as the first SS and / or second SS.

[0603] For example, in a non-terrestrial network according to one embodiment of the present disclosure, it may be assumed that a base station (or network) services a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, for example, when the terminal operates in a half-duplex transmission mode, it cannot perform DL reception and UL transmission simultaneously, and if the timing of DL reception and the timing of UL transmission conflict, the terminal may prioritize performing DL reception and / or UL transmission according to a DL / UL collision handling rule pre-agreed upon / set with the base station.

[0604] 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 mutually recognized through shared parameters and calculation formulas between the base station (or network) and the terminal, while the (UE) TA may be a value that is voluntarily adjusted by the terminal and is unknown to the base station (or network). Here, for example, the TA that the base station (or network) expects / predicts for the terminal (first TA) and the TA that the terminal actually applies (second TA) may have different values.

[0605] Accordingly, for example, in a non-terrestrial network, DL / UL collision(s) (hereinafter error case(s)) (e.g., collisions between dynamically scheduled DL transmission resources and dynamically scheduled UL transmission resources and / or collisions between semi-statically configured DL transmission resources and semi-statically configured UL transmission resources) that conventional base stations (or networks) are expected to avoid may occur relatively frequently, and it is necessary to define DL / UL collision handling rules for a terminal operating in half-duplex transmission mode for said case(s).

[0606] Here, for example, a DL / UL priority rule (hereinafter referred to as the first priority rule) that prioritizes DL or UL may be predefined and / or set. Here, for example, a specific DL reception needs to be handled as an exception to the first priority rule. For example, the specific DL reception may be a specific SS (search space) (hereinafter referred to as the first SS) related to system information and / or system information changes. For example, the first SS may be a Type 2-PDCCH CSS (common search space). Here, for example, the terminal may receive (and / or monitor) not only the first SS but also another specific SS (search space) (hereinafter referred to as the second SS) for the time resource (and / or slot) that received (and / or monitored) the first SS. Here, for example, the terminal may also apply an exception handling action (not following the first priority rule) to a PDSCH scheduled as a PDCCH within the first SS and / or second SS (hereinafter the first PDSCH). Here, for example, the reason for allowing an exception handling action for the first PDSCH may be to match the terminal action with the exception handling action for the first SS and / or second SS, or because it is difficult to apply a different priority rule to the first PDSCH due to the processing time for the first SS and / or second SS.

[0607] In particular, the UE may not be able to immediately determine the existence of DCI and the collision determination result in the CSS, and the determination of the existence / absence of DCI and the related collision handling decision may not be completed immediately within the slot, but may only be determined after at least that slot. As a result, even though it may superficially appear sufficient to process only the symbol section occupied by the CSS as DL, in practice, a problem may arise where it is difficult to determine whether to initiate UL within that slot.

[0608] In addition, if the interval after CSS monitoring is defined as a UL, the base station must determine that UL transmission is possible in that interval and perform UL reception and detection. However, if the UE is unable to actually initiate the UL due to processing delays or other reasons, the base station performs unnecessary monitoring and reception operations for ULs that are not actually reached, which increases the network burden.

[0609] According to the proposed method of the present disclosure above, for example, a base station (or network node) and / or a terminal may allow the application of a DL / UL priority rule that takes precedence within the section where the transmission is expected / anticipated for a specific type of DL transmission, thereby ensuring the reception of important DL transmissions while reducing the impact on UL transmissions. Additionally, for example, the terminal's exception handling behavior may be matched and / or aligned with the PDCCH and / or PDSCH to reduce terminal complexity.

[0610] According to the present disclosure, the following effects can be obtained.

[0611] First, even if the UE cannot immediately determine the presence / absence of DCI in CSS and the collision handling decision within the slot, the ambiguity of the UE's behavior can be eliminated by prioritizing the time resource containing CSS monitoring as DL.

[0612] Second, it can reduce the unnecessary burden of UL reception and detection on the base station that occurs when the section after CSS is maintained as UL.

[0613] Third, even in cases where TA uncertainty exists, such as in an NTN environment, system stability and procedural consistency can be improved by conservatively handling DL-UL conflicts.

[0614] Fourth, by providing a DL-UL collision handling structure that simultaneously considers UE processing delay and network reception burden, reliability and predictability at the system level can be improved.

[0615] The above [Proposed Plan #18] may be applied in combination with other proposed plans(s) to the extent that the proposed operations do not conflict.

[0616] [Proposed Method #19] When a base station (or network node) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to half-duplex transmission mode, and when a (default) DL / UL priority rule (hereinafter referred to as the first priority rule) can be defined and / or set, when the terminal receives (and / or monitors) a (specific) SS (search space) (hereinafter referred to as the first SS) and / or a (specific) PDCCH (hereinafter referred to as the first PDCCH), the terminal may support one or more of the following DL / UL collision handling methods for the time resources at which the first SS and / or the first PDCCH were received (and / or monitored).

[0617] (1) Allow DL priority and / or exception handling behavior for transmissions (within the relevant time resources).

[0618] (2) Allow exception handling operations for the PDSCH scheduled with the first SS and / or first PDCCH (within the relevant time resource).

[0619] For example, the above time resource may refer to a slot and / or a paging occasion (PO).

[0620] For example, the above exception handling operation may mean an operation that prioritizes DL or UL depending on the terminal implementation.

[0621] For example, in a non-terrestrial network according to one embodiment of the present disclosure, it may be assumed that a base station (or network) services a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, for example, when the terminal operates in a half-duplex transmission mode, it cannot perform DL reception and UL transmission simultaneously, and if the timing of DL reception and the timing of UL transmission conflict, the terminal may prioritize performing DL reception and / or UL transmission according to a DL / UL collision handling rule pre-agreed upon / set with the base station.

[0622] 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 mutually recognized through shared parameters and calculation formulas between the base station (or network) and the terminal, while the (UE) TA may be a value that is voluntarily adjusted by the terminal and is unknown to the base station (or network). Here, for example, the TA that the base station (or network) expects / predicts for the terminal (first TA) and the TA that the terminal actually applies (second TA) may have different values.

[0623] Accordingly, for example, in a non-terrestrial network, DL / UL collision(s) (hereinafter error case(s)) (e.g., collisions between dynamically scheduled DL transmission resources and dynamically scheduled UL transmission resources and / or collisions between semi-statically configured DL transmission resources and semi-statically configured UL transmission resources) that conventional base stations (or networks) are expected to avoid may occur relatively frequently, and it is necessary to define DL / UL collision handling rules for a terminal operating in half-duplex transmission mode for said case(s).

[0624] Here, for example, a DL / UL priority rule (hereinafter referred to as the first priority rule) that prioritizes DL or UL may be predefined and / or set. Here, for example, a specific DL reception needs to be handled as an exception to the first priority rule. For example, the specific DL reception handled as an exception may be a (specific) SS (search space) (hereinafter referred to as the first SS) and / or a (specific) PDCCH (hereinafter referred to as the first PDCCH). Here, for example, the terminal may prioritize DL or allow exception handling actions for a time resource (and / or slot) that has received (and / or monitored) the first SS and / or the first PDCCH. Here, for example, the reason for allowing exception handling actions for the time resource (and / or slot) may be to match and / or align the terminal action with the exception handling action for the first SS and / or the first PDCCH, or because it is difficult to apply different priority rules within the time resource (and / or slot) due to the processing time for the first SS and / or the first PDCCH.

[0625] In particular, the UE may not be able to immediately determine the existence of DCI and the collision determination result in the CSS, and the determination of the existence / absence of DCI and the related collision handling decision may not be completed immediately within the slot, but may only be determined after at least that slot. As a result, even though it may superficially appear sufficient to process only the symbol section occupied by the CSS as DL, in practice, a problem may arise where it is difficult to determine whether to initiate UL within that slot.

[0626] In addition, if the interval after CSS monitoring is defined as a UL, the base station must determine that UL transmission is possible in that interval and perform UL reception and detection. However, if the UE is unable to actually initiate the UL due to processing delays or other reasons, the base station performs unnecessary monitoring and reception operations for ULs that are not actually reached, which increases the network burden.

[0627] According to the proposed method of the present disclosure above, for example, a base station (or network node) and / or a terminal may allow the application of a DL / UL priority rule that takes precedence within the section where the transmission is expected / anticipated for a specific type of DL transmission, thereby ensuring the reception of important DL transmissions while reducing the impact on UL transmissions. Additionally, for example, the terminal's exception handling behavior may be matched and / or aligned with the PDCCH and / or PDSCH to reduce terminal complexity.

[0628] According to the present disclosure, the following effects can be obtained.

[0629] First, even if the UE cannot immediately determine the presence / absence of DCI in CSS and the collision handling decision within the slot, the ambiguity of the UE's behavior can be eliminated by prioritizing the time resource containing CSS monitoring as DL.

[0630] Second, it can reduce the unnecessary burden of UL reception and detection on the base station that occurs when the section after CSS is maintained as UL.

[0631] Third, even in cases where TA uncertainty exists, such as in an NTN environment, system stability and procedural consistency can be improved by conservatively handling DL-UL conflicts.

[0632] Fourth, by providing a DL-UL collision handling structure that simultaneously considers UE processing delay and network reception burden, reliability and predictability at the system level can be improved.

[0633] The above [Proposed Plan #19] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0634] [Proposed Plan #20] When a base station (or network node) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to half-duplex transmission mode,

[0635] When a (default and / or configured) DL / UL priority rule (hereinafter referred to as the 1st priority rule) can be (pre)defined and / or configured,

[0636] If the above terminal receives (and / or monitors) a (specific) (common) SS (search space) (hereinafter referred to as the 1st SS) in accordance with an exception handling operation (that does not follow the above 1st priority rule),

[0637] If the terminal detects the first SS and / or a (specific) PDCCH (and / or DCI format) (hereinafter the first PDCCH) within the time resource and / or frequency resource (e.g., slot and / or CORESET) where the terminal received (and / or monitored) the first SS and / or another (specific) (UE-specific) SS (search space) (hereinafter the second SS) (other than the first SS),

[0638] For a (specific) PDSCH (hereinafter referred to as the 1st PDSCH) scheduled to the 1st PDCCH, an exception handling operation (that does not follow the 1st priority rule) may be allowed (by the base station (or network node) and / or terminal).

[0639] Here, for example, the first SS may be a Type-0 / 0A / 1 / 2-PDCCH(Type-0 / 0A / 1 / 2-PDCCH(Type-0 / 0A / 1 / 2-PDCCH)) CSS(common search space).

[0640] Here, for example, the second SS may be a USS (UE-specific search space).

[0641] Here, for example, the above CORESET (control resource set) may refer to physical resources and / or parameter(s) for PDCCH (physical downlink control channel) and / or DCI (downlink control information) transmission.

[0642] Here, for example, the first PDCCH may mean a PDCCH and / or DCI in which a cyclic redundancy check (CRC) applied to a DCI format is scrambled with a (specific) RNTI.

[0643] Here, for example, exception handling for the first PDSCH may be allowed only for a (specific) time resource. For example, exception handling may be allowed only when the first PDSCH is scheduled within the same time resource (and / or slot) as the first SS and / or the second SS.

[0644] Here, for example, the above exception handling operation may mean an operation that prioritizes DL or UL depending on the terminal implementation.

[0645] For example, in a non-terrestrial network according to one embodiment of the present disclosure, it may be assumed that a base station (or network) services a terminal operating in a half-duplex transmission mode based on the non-terrestrial network. Here, for example, when the terminal operates in a half-duplex transmission mode, it cannot perform DL reception and UL transmission simultaneously, and if the timing of DL reception and the timing of UL transmission conflict, the terminal may prioritize performing DL reception and / or UL transmission according to a DL / UL collision handling rule pre-agreed upon / set with the base station.

[0646] 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 mutually recognized through shared parameters and calculation formulas between the base station (or network) and the terminal, while the (UE) TA may be a value that is voluntarily adjusted by the terminal and is unknown to the base station (or network). Here, for example, the TA that the base station (or network) expects / predicts for the terminal (first TA) and the TA that the terminal actually applies (second TA) may have different values.

[0647] Accordingly, for example, in a non-terrestrial network, DL / UL collision(s) (hereinafter error case(s)) (e.g., collisions between dynamically scheduled DL transmission resources and dynamically scheduled UL transmission resources and / or collisions between semi-statically configured DL transmission resources and semi-statically configured UL transmission resources) that conventional base stations (or networks) are expected to avoid may occur relatively frequently, and it is necessary to define DL / UL collision handling rules for a terminal operating in half-duplex transmission mode for said case(s).

[0648] Here, for example, a DL / UL priority rule (hereinafter referred to as the first priority rule) that prioritizes DL or UL may be predefined and / or set. Here, for example, a specific DL reception needs to be handled as an exception to the first priority rule. For example, the specific DL reception may be a specific SS (search space) (hereinafter referred to as the first SS) related to system information and / or system information change and / or initial connection. For example, the first SS may be a Type-0 / 0A / 1 / 2 Type-0 / 0A / 1 / 2-PDCCH CSS (common search space). Here, for example, the terminal may receive (and / or monitor) not only the first SS but also another specific SS (search space) (hereinafter referred to as the second SS) for the time resource (and / or slot) at which the first SS was received (and / or monitored). Here, for example, the terminal may also apply an exception handling action (not following the first priority rule) to a PDSCH (hereinafter the first PDSCH) scheduled as a PDCCH within the first SS and / or the second SS. Here, for example, the reason for allowing an exception handling action for the first PDSCH may be to align the terminal action with the exception handling action for the first SS and / or the second SS, or because it is difficult to apply a different priority rule to the first PDSCH due to the processing time for the first SS and / or the second SS. Here, for example, the second SS may include a USS (UE-specific search space).

[0649] In particular, the UE may not be able to immediately determine the existence of DCI and the collision determination result in the CSS, and the determination of the existence / absence of DCI and the related collision handling decision may not be completed immediately within the slot, but may only be determined after at least that slot. As a result, even though it may superficially appear sufficient to process only the symbol section occupied by the CSS as DL, in practice, a problem may arise where it is difficult to determine whether to initiate UL within that slot.

[0650] In addition, if the interval after CSS monitoring is defined as a UL, the base station must determine that UL transmission is possible in that interval and perform UL reception and detection. However, if the UE is unable to actually initiate the UL due to processing delays or other reasons, the base station performs unnecessary monitoring and reception operations for ULs that are not actually reached, which increases the network burden.

[0651] Accordingly, in the present disclosure, for example, when a base station (or network node) and / or terminal in a non-terrestrial network can perform DL / UL collision handling rules according to a half-duplex transmission mode, and when a (default and / or configured) DL / UL priority rule (hereinafter referred to as the first priority rule) can be (pre)defined and / or configured, and when the terminal receives (and / or monitors) a (specific) (common) SS (search space) (hereinafter referred to as the first SS) according to an exception handling operation (not following the first priority rule), the (specific) PDCCH (and / or DCI format) (hereinafter referred to as the first) within the time resource and / or frequency resource (e.g., slot and / or CORESET) where the terminal received (and / or monitored) the first SS and / or another (specific) (UE-specific) SS (search space) (hereinafter referred to as the second SS) (other than the first SS) When a PDCCH is detected, an exception handling operation (that does not follow the first priority rule) for a (specific) PDSCH (hereinafter the first PDSCH) scheduled to the first PDCCH may be allowed (by the base station (or network node) and / or terminal).

[0652] According to the proposed method of the present disclosure above, for example, a base station (or network node) and / or a terminal may allow the application of a DL / UL priority rule that takes precedence within the section where the transmission is expected / anticipated for a specific type of DL transmission, thereby ensuring the reception of important DL transmissions while reducing the impact on UL transmissions. Additionally, for example, the terminal's exception handling behavior may be matched and / or aligned with the PDCCH and / or PDSCH to reduce terminal complexity.

[0653] According to the present disclosure, the following effects can be obtained.

[0654] First, even if the UE cannot immediately determine the presence / absence of DCI in CSS and the collision handling decision within the slot, the ambiguity of the UE's behavior can be eliminated by prioritizing the time resource containing CSS monitoring as DL.

[0655] Second, it can reduce the unnecessary burden of UL reception and detection on the base station that occurs when the section after CSS is maintained as UL.

[0656] Third, even in cases where TA uncertainty exists, such as in an NTN environment, system stability and procedural consistency can be improved by conservatively handling DL-UL conflicts.

[0657] Fourth, by providing a DL-UL collision handling structure that simultaneously considers UE processing delay and network reception burden, reliability and predictability at the system level can be improved.

[0658] The above [Proposed Plan #20] may be applied in combination with other proposed plans within the scope where the proposed operations do not conflict.

[0659] Although the embodiments of the present disclosure are described as examples of non-ground networks, they can be extended to ground networks as well.

[0660] Combinations of various embodiments of the present disclosure may be applied differently depending on the payload type of the satellite (e.g., regenerative payload or transparent payload).

[0661] Combinations of various embodiments of the present disclosure may be applied differently to the type of non-geostational network node (e.g., GEO (geostationary earth orbit), NGEO (non-geostationary earth orbit), LEO (low earth orbit), MEO (medium earth orbit), HASP (high altitude satellite platform), drone) or altitude or fixed beam footprint or cell-moving beam footprint.

[0662] For example, in the embodiments of the present disclosure, the TDD setting and utilization are not limited to the TDD band, and can be extended to the FDD band and / or a combination of specific DL band and / or UL band.

[0663] For example, in an embodiment of the present disclosure, a base station or network node may be a satellite. For example, a base station or network node may be associated with a transparent payload. For example, a base station or network node may be associated with a regenerated payload.

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

[0665] Various embodiments of the present disclosure may be applied differently depending on the link type (DL, UL, SL) and / or the data type (SIB, group cast, unicast) and / or the search space type (CSS (common search space), USS (UE-specific search space)) where the scheduling PDCCH is detected and / or the base station node type and / or altitude and / or whether there is a power constraint. For example, a combination of various embodiments of the present disclosure may be applied only when involved in SIB transmission.

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

[0667] For example, in the present disclosure, "specific threshold" may mean a threshold that is predefined or (pre-)set by an upper layer (including the application layer) of a network, base station, or terminal. For example, in the present disclosure, "specific set value" may mean a value that is predefined or (pre-)set by an upper layer (including the application layer) of a network, base station, or terminal. For example, in the present disclosure, "set by the network / base station" may mean an action in which a base station sets to a UE (pre-) through upper layer RRC signaling, sets / signals to a UE through MAC CE, or signals to a UE through DCI.

[0668] For example, in this disclosure, various names are exemplary and may be replaced or considered as other names performing the same or similar functions based on the content described in each step (regardless of the name).

[0669] FIG. 27 illustrates a procedure performed by a first device according to one embodiment of the present disclosure. The embodiment of FIG. 27 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiments may be omitted.

[0670] Referring to FIG. 27, in step S2710, the first device can obtain a DL-UL (downlink-uplink) priority rule that prioritizes the UL (uplink). In step S2720, the first device can monitor the CSS (common search space) based on the DL-UL priority rule that prioritizes the UL. For example, in a time resource where the CSS is monitored based on the DL-UL priority rule that prioritizes the UL, the DL may be prioritized.

[0671] For example, the time resource monitored by the CSS based on the DL-UL priority rule that prioritizes the UL may be a slot.

[0672] For example, the time resource monitored by the CSS based on the DL-UL priority rule that prioritizes the UL may be a PO (paging occasion).

[0673] For example, the time resource monitored by the CSS based on the DL-UL priority rule that prioritizes the UL may include a first time resource that is a time resource monitored on the CSS based on the DL-UL priority rule that prioritizes the UL, and a second time resource that is a resource adjacent to the time resource monitored on the CSS within the slot based on the DL-UL priority rule that prioritizes the UL.

[0674] For example, regardless of whether DCI (downlink control information) is detected in the CSS in the second time resource, DL may be prioritized in the second time resource, which is a resource adjacent to the time resource monitored on the CSS within the slot, based on the DL-UL priority rule that prioritizes the UL.

[0675] For example, the first time resource, which is a time resource monitored on the CSS based on the DL-UL priority rule that prioritizes the UL, may be a time resource monitored on a control resource set (core set) based on the DL-UL priority rule that prioritizes the UL.

[0676] For example, the second time resource, which is the resource adjacent to the time resource monitored on the CSS within the slot based on the DL-UL priority rule that prioritizes the UL, may be a time resource monitored on a PDSCH (physical downlink shared channel) scheduled by the CSS based on the DL-UL priority rule that prioritizes the UL.

[0677] For example, based on the DL-UL priority rule that prioritizes the UL, in the second time resource which is the resource adjacent to the time resource monitored on the CSS within the slot, DL may be prioritized for at least one of the PDSCH scheduled by the CSS, the PDSCH scheduled by another CSS, or the PDSCH scheduled by the USS (UE-specific (user equipment-specific) search space).

[0678] For example, the above CSS may be at least one of type-0 PDCCH CSS, type-0A PDCCH CSS, type-1 PDCCH CSS, or type-2 PDCCH CSS.

[0679] For example, the first device above may only support half-duplex FDD operation.

[0680] For example, the first device may be a RedCap UE (user equipment) or an enhanced RedCap UE. For example, the RedCap UE or the enhanced RedCap UE may only support the half-duplex FDD operation.

[0681] For example, in the time resources where the CSS is monitored based on the DL-UL priority rule that prioritizes the UL, the DL may be prioritized based on the fact that the CSS is associated with at least one of SI-RNTI (system information-radio network temporary identifier) ​​or P-RNTI (paging-radio network temporary identifier (P-RNTI).

[0682] For example, the first device may obtain a valid time for the DL-UL priority rule that prioritizes the UL. For example, after the expiration of the valid time, DL may be prioritized or UL may be prioritized based on the default DL-UL priority rule.

[0683] The proposed method above may be applied to a device according to various embodiments of the present disclosure. For example, a processor (102) of a first device (100) may obtain a DL-UL (downlink-uplink) priority rule that prioritizes a UL (uplink) (for example, the processor (102) of the first device (100) may control a transceiver (106) to obtain a DL-UL (downlink-uplink) priority rule that prioritizes a UL (uplink)). For example, the processor (102) of the first device (100) may monitor a CSS (common search space) based on the DL-UL priority rule that prioritizes the UL (for example, the processor (102) of the first device (100) may control a transceiver (106) to monitor a CSS (common search space) based on the DL-UL priority rule that prioritizes the UL). For example, based on the DL-UL priority rule that prioritizes the UL, in the time resources where the CSS is monitored, DL may be prioritized.

[0684] According to one embodiment of the present disclosure, a first device may be provided. For example, the first device may include at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, based on the instructions being executed by the at least one processor, the first device may: obtain a DL-UL (downlink-uplink) priority rule that prioritizes the UL (uplink); and monitor a CSS (common search space) based on the DL-UL priority rule that prioritizes the UL. For example, in a time resource where the CSS is monitored based on the DL-UL priority rule that prioritizes the UL, the DL may be prioritized.

[0685] For example, the time resource monitored by the CSS based on the DL-UL priority rule that prioritizes the UL may be a slot.

[0686] For example, the time resource monitored by the CSS based on the DL-UL priority rule that prioritizes the UL may be a PO (paging occasion).

[0687] For example, the time resource monitored by the CSS based on the DL-UL priority rule that prioritizes the UL may include a first time resource that is a time resource monitored on the CSS based on the DL-UL priority rule that prioritizes the UL, and a second time resource that is a resource adjacent to the time resource monitored on the CSS within the slot based on the DL-UL priority rule that prioritizes the UL.

[0688] For example, regardless of whether DCI (downlink control information) is detected in the CSS in the second time resource, DL may be prioritized in the second time resource, which is a resource adjacent to the time resource monitored on the CSS within the slot, based on the DL-UL priority rule that prioritizes the UL.

[0689] For example, the first time resource, which is a time resource monitored on the CSS based on the DL-UL priority rule that prioritizes the UL, may be a time resource monitored on a control resource set (core set) based on the DL-UL priority rule that prioritizes the UL.

[0690] For example, the second time resource, which is the resource adjacent to the time resource monitored on the CSS within the slot based on the DL-UL priority rule that prioritizes the UL, may be a time resource monitored on a PDSCH (physical downlink shared channel) scheduled by the CSS based on the DL-UL priority rule that prioritizes the UL.

[0691] For example, based on the DL-UL priority rule that prioritizes the UL, in the second time resource which is the resource adjacent to the time resource monitored on the CSS within the slot, DL may be prioritized for at least one of the PDSCH scheduled by the CSS, the PDSCH scheduled by another CSS, or the PDSCH scheduled by the USS (UE-specific (user equipment-specific) search space).

[0692] For example, the above CSS may be at least one of type-0 PDCCH CSS, type-0A PDCCH CSS, type-1 PDCCH CSS, or type-2 PDCCH CSS.

[0693] For example, the first device above may only support half-duplex FDD operation.

[0694] For example, the first device may be a RedCap UE (user equipment) or an enhanced RedCap UE. For example, the RedCap UE or the enhanced RedCap UE may only support the half-duplex FDD operation.

[0695] For example, in the time resources where the CSS is monitored based on the DL-UL priority rule that prioritizes the UL, the DL may be prioritized based on the fact that the CSS is associated with at least one of SI-RNTI (system information-radio network temporary identifier) ​​or P-RNTI (paging-radio network temporary identifier (P-RNTI).

[0696] For example, the first device may obtain a valid time for the DL-UL priority rule that prioritizes the UL. For example, after the expiration of the valid time, DL may be prioritized or UL may be prioritized based on the default DL-UL priority rule.

[0697] According to one embodiment of the present disclosure, a processing device (configured to control a first device) may be provided. For example, the processing device may include at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, based on the instructions executed by the at least one processor, the first device may: obtain a DL-UL (downlink-uplink) priority rule that prioritizes the UL (uplink); and monitor a CSS (common search space) based on the DL-UL priority rule that prioritizes the UL. For example, in a time resource where the CSS is monitored based on the DL-UL priority rule that prioritizes the UL, the DL may be prioritized.

[0698] According to one embodiment of the present disclosure, a non-transient computer-readable storage medium recording instructions may be provided. For example, when the instructions are executed, the first device may: obtain a DL-UL (downlink-uplink) priority rule that prioritizes the UL (uplink); and monitor a CSS (common search space) based on the DL-UL priority rule that prioritizes the UL. For example, in a time resource where the CSS is monitored based on the DL-UL priority rule that prioritizes the UL, the DL may be prioritized.

[0699] FIG. 28 illustrates a procedure performed by a second device according to one embodiment of the present disclosure. The embodiment of FIG. 28 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of said embodiments may be omitted.

[0700] Referring to FIG. 28, in step S2810, the second device may transmit a DL-UL (downlink-uplink) priority rule that prioritizes the UL (uplink) to the first device. In step S2820, the second device may monitor the UL from the first device based on the DL-UL priority rule that prioritizes the UL. For example, in a time resource where CSS is monitored based on the DL-UL priority rule that prioritizes the UL, the DL may be prioritized.

[0701] For example, the time resource monitored by the CSS based on the DL-UL priority rule that prioritizes the UL may be a slot.

[0702] For example, the time resource monitored by the CSS based on the DL-UL priority rule that prioritizes the UL may be a PO (paging occasion).

[0703] For example, the time resource monitored by the CSS based on the DL-UL priority rule that prioritizes the UL may include a first time resource that is a time resource monitored on the CSS based on the DL-UL priority rule that prioritizes the UL, and a second time resource that is a resource adjacent to the time resource monitored on the CSS within the slot based on the DL-UL priority rule that prioritizes the UL.

[0704] For example, regardless of whether DCI (downlink control information) is detected in the CSS in the second time resource, DL may be prioritized in the second time resource, which is a resource adjacent to the time resource monitored on the CSS within the slot, based on the DL-UL priority rule that prioritizes the UL.

[0705] For example, the first time resource, which is a time resource monitored on the CSS based on the DL-UL priority rule that prioritizes the UL, may be a time resource monitored on a control resource set (core set) based on the DL-UL priority rule that prioritizes the UL.

[0706] For example, the second time resource, which is the resource adjacent to the time resource monitored on the CSS within the slot based on the DL-UL priority rule that prioritizes the UL, may be a time resource monitored on a PDSCH (physical downlink shared channel) scheduled by the CSS based on the DL-UL priority rule that prioritizes the UL.

[0707] For example, based on the DL-UL priority rule that prioritizes the UL, in the second time resource which is the resource adjacent to the time resource monitored on the CSS within the slot, DL may be prioritized for at least one of the PDSCH scheduled by the CSS, the PDSCH scheduled by another CSS, or the PDSCH scheduled by the USS (UE-specific (user equipment-specific) search space).

[0708] For example, the above CSS may be at least one of type-0 PDCCH CSS, type-0A PDCCH CSS, type-1 PDCCH CSS, or type-2 PDCCH CSS.

[0709] For example, the first device above may only support half-duplex FDD operation.

[0710] For example, the first device may be a RedCap UE (user equipment) or an enhanced RedCap UE. For example, the RedCap UE or the enhanced RedCap UE may only support the half-duplex FDD operation.

[0711] For example, in the time resources where the CSS is monitored based on the DL-UL priority rule that prioritizes the UL, the DL may be prioritized based on the fact that the CSS is associated with at least one of SI-RNTI (system information-radio network temporary identifier) ​​or P-RNTI (paging-radio network temporary identifier (P-RNTI).

[0712] For example, the second device may transmit to the first device the validity period for the DL-UL priority rule that prioritizes the UL. For example, after the validity period expires, DL may be prioritized or UL may be prioritized based on the default DL-UL priority rule.

[0713] The proposed method above may be applied to a device according to various embodiments of the present disclosure. For example, a processor (202) of a second device (200) may transmit a DL-UL (downlink-uplink) priority rule that prioritizes a UL (uplink) to a first device (for example, the processor (202) of the second device (200) may control a transceiver (206) to transmit a DL-UL (downlink-uplink) priority rule that prioritizes a UL (uplink) to the first device). For example, the processor (202) of the second device (200) may monitor a UL from the first device based on the DL-UL priority rule that prioritizes the UL (for example, the processor (202) of the second device (200) may control a transceiver (206) to monitor a UL from the first device based on the DL-UL priority rule that prioritizes the UL). For example, in time resources where CSS is monitored based on the DL-UL priority rule that prioritizes the UL, DL may be prioritized.

[0714] According to one embodiment of the present disclosure, a second device may be provided. For example, the second device may include at least one transceiver; at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, based on the instructions being executed by the at least one processor, the second device may: transmit to the first device a DL-UL (downlink-uplink) priority rule that prioritizes the UL (uplink); and monitor the UL from the first device based on the DL-UL priority rule that prioritizes the UL. For example, in a time resource where the CSS is monitored based on the DL-UL priority rule that prioritizes the UL, the DL may be prioritized.

[0715] For example, the time resource monitored by the CSS based on the DL-UL priority rule that prioritizes the UL may be a slot.

[0716] For example, the time resource monitored by the CSS based on the DL-UL priority rule that prioritizes the UL may be a PO (paging occasion).

[0717] For example, the time resource monitored by the CSS based on the DL-UL priority rule that prioritizes the UL may include a first time resource that is a time resource monitored on the CSS based on the DL-UL priority rule that prioritizes the UL, and a second time resource that is a resource adjacent to the time resource monitored on the CSS within the slot based on the DL-UL priority rule that prioritizes the UL.

[0718] For example, regardless of whether DCI (downlink control information) is detected in the CSS in the second time resource, DL may be prioritized in the second time resource, which is a resource adjacent to the time resource monitored on the CSS within the slot, based on the DL-UL priority rule that prioritizes the UL.

[0719] For example, the first time resource, which is a time resource monitored on the CSS based on the DL-UL priority rule that prioritizes the UL, may be a time resource monitored on a control resource set (core set) based on the DL-UL priority rule that prioritizes the UL.

[0720] For example, the second time resource, which is the resource adjacent to the time resource monitored on the CSS within the slot based on the DL-UL priority rule that prioritizes the UL, may be a time resource monitored on a PDSCH (physical downlink shared channel) scheduled by the CSS based on the DL-UL priority rule that prioritizes the UL.

[0721] For example, based on the DL-UL priority rule that prioritizes the UL, in the second time resource which is the resource adjacent to the time resource monitored on the CSS within the slot, DL may be prioritized for at least one of the PDSCH scheduled by the CSS, the PDSCH scheduled by another CSS, or the PDSCH scheduled by the USS (UE-specific (user equipment-specific) search space).

[0722] For example, the above CSS may be at least one of type-0 PDCCH CSS, type-0A PDCCH CSS, type-1 PDCCH CSS, or type-2 PDCCH CSS.

[0723] For example, the first device above may only support half-duplex FDD operation.

[0724] For example, the first device may be a RedCap UE (user equipment) or an enhanced RedCap UE. For example, the RedCap UE or the enhanced RedCap UE may only support the half-duplex FDD operation.

[0725] For example, in the time resources where the CSS is monitored based on the DL-UL priority rule that prioritizes the UL, the DL may be prioritized based on the fact that the CSS is associated with at least one of SI-RNTI (system information-radio network temporary identifier) ​​or P-RNTI (paging-radio network temporary identifier (P-RNTI).

[0726] For example, the second device may transmit to the first device the validity period for the DL-UL priority rule that prioritizes the UL. For example, after the validity period expires, DL may be prioritized or UL may be prioritized based on the default DL-UL priority rule.

[0727] According to one embodiment of the present disclosure, a processing device (configured to control a second device) may be provided. For example, the processing device may include at least one processor; and at least one memory connected to the at least one processor and storing instructions. For example, based on the instructions executed by the at least one processor, the second device may: transmit to the first device a DL-UL (downlink-uplink) priority rule that prioritizes the UL (uplink); and monitor the UL from the first device based on the DL-UL priority rule that prioritizes the UL. For example, in a time resource where the CSS is monitored based on the DL-UL priority rule that prioritizes the UL, the DL may be prioritized.

[0728] According to one embodiment of the present disclosure, a non-transient computer-readable storage medium recording instructions may be provided. For example, when the instructions are executed, the second device may: transmit to the first device a DL-UL (downlink-uplink) priority rule that prioritizes the UL (uplink); and monitor the UL from the first device based on the DL-UL priority rule that prioritizes the UL. For example, in a time resource where the CSS is monitored based on the DL-UL priority rule that prioritizes the UL, the DL may be prioritized.

[0729] According to one embodiment of the present disclosure, for example, a DL-UL priority rule that prioritizes UL is obtained, and CSS is monitored based on said rule, but DL may be prioritized in time resources where CSS is monitored despite the rule prioritizing UL being configured. For example, said time resources may be slots, and accordingly, the entire slot where CSS is monitored may be processed with DL priority. Or, for example, said time resources may be POs (paging occasions), and DL may be prioritized in relation to CSS monitoring in POs. For example, by including DL priority not only in the first time resource where CSS is monitored but also in the second time resource adjacent to said time resource, it may be configured to absorb the DCI processing confirmation delay period of the UE.

[0730] According to the present disclosure, the following effects can be obtained.

[0731] First, even if the UE cannot immediately determine the presence / absence of DCI in CSS and the collision handling decision within the slot, the ambiguity of the UE's behavior can be eliminated by prioritizing the time resource containing CSS monitoring as DL.

[0732] Second, it can reduce the unnecessary burden of UL reception and detection on the base station that occurs when the section after CSS is maintained as UL.

[0733] Third, even in cases where TA uncertainty exists, such as in an NTN environment, system stability and procedural consistency can be improved by conservatively handling DL-UL conflicts.

[0734] Fourth, by providing a DL-UL collision handling structure that simultaneously considers UE processing delay and network reception burden, reliability and predictability at the system level can be improved.

[0735] Various embodiments of the present disclosure may be combined with one another. For example, various embodiments of the present disclosure may be combined with one another, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the various embodiments may be omitted.

[0736] The present disclosure describes a 5G wireless communication system as an example. This can be similarly applied and used in 6G wireless communication systems, etc.

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

[0738] The following describes an apparatus to which various embodiments of the present disclosure may be applied.

[0739] Although not limited to, the various descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document may be applied to various fields requiring wireless communication / connection (e.g., 5G, 6G, etc.) between devices.

[0740] Examples are provided in more detail below with reference to the drawings. In the following drawings and descriptions, the same reference numerals may represent the same or corresponding hardware blocks, software blocks, or function blocks unless otherwise described.

[0741] FIG. 29 shows a communication system (1) according to one embodiment of the present disclosure. The embodiment of FIG. 29 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods and / or operations of the embodiments may be omitted.

[0742] Referring to FIG. 29, 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 wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution), 6G, etc.) and may be referred to as a communication / wireless / 5G / 6G 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 Thing) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with wireless communication functions, an autonomous vehicle, a vehicle capable of performing inter-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., Advanced Air Mobility). The XR device includes 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, digital signage, a vehicle, a robot, etc. The portable device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch, smart glasses), a computer (e.g., a laptop, 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 be implemented as a wireless device, and a specific wireless device (200a) may operate as a base station / network node to other wireless devices.

[0743] Here, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present disclosure may include LTE, NR, and 6G, as well as NB-IoT (Narrowband Internet of Things) for low-power communication. In this case, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally, or generally, the wireless communication technology implemented in the wireless devices (100a to 100f) of the present disclosure may perform communication based on LTE-M technology. In this case, for example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the names mentioned above. Additionally or generally, wireless communication technology implemented in the wireless devices (100a to 100f) of the present disclosure may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) for low-power communication, and is not limited to the names mentioned above. As an example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.

[0744] Wireless devices (100a to 100f) can be connected to a network (300) through a base station (200). Artificial Intelligence (AI) technology may be applied to the wireless devices (100a to 100f), and wireless devices (100a to 100f) can be connected to an AI server (400) through 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, or a 6G network. Wireless devices (100a to 100f) may communicate with each other through the base station (200) / network (300), but they may 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). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0745] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base station (200) and base station (200) / base station (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR, 6G, etc.), such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and inter-base station communication (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 / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on various proposals of the present disclosure, at least some of the following may be performed: 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.), resource allocation processes, etc.

[0746] FIG. 30 shows a wireless device according to one embodiment of the present disclosure. The embodiment of FIG. 30 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods and / or operations of the embodiments may be omitted.

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

[0748] The first wireless device (100) includes one or more processors (102) and one or more memories (104), and may additionally include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memory (104) and / or transceivers (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or sequences of operation disclosed in this document. For example, the processor (102) may process information within the memory (104) to generate a first information / signal and then transmit a wireless signal containing the first information / signal through the transceiver (106). Additionally, the processor (102) may receive a wireless signal containing a second information / signal through the transceiver (106) and then store information obtained from the 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 store software code containing instructions for performing some or all of the processes controlled by the processor (102) or for performing the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement 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 through one or more antennas (108). The transceiver (106) may include a transmitter and / or receiver. The transceiver (106) may be combined with an RF (Radio Frequency) unit. In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0749] The second wireless device (200) includes one or more processors (202) and one or more memories (204), and may additionally include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memory (204) and / or transceivers (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or sequences of operation disclosed in this document. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and then transmit a wireless signal containing the third information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and then store information obtained from the signal processing of the fourth information / signal in the memory (204). Memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, memory (204) may store software code containing instructions for performing some or all of the processes controlled by the processor (202) or for performing the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document. Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals through one or more antennas (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeable with an RF unit. In this disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0750] For example, the transceiver (106, 206) may include not only a circuit that directly generates and transmits a wireless signal, but also a circuit that modulates and reflects (backscatters) the incident wireless signal.

[0751] Hereinafter, 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 Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation 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 flowcharts of operation disclosed in this document. One or more processors (102, 202) may generate a signal (e.g., baseband signal) containing a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this document and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this document.

[0752] One or more processors (102, 202) may be referred to as a controller, microcontroller, microprocessor, or 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 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. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be contained in one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.

[0753] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories (104, 204) may be composed of ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0754] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc., of this document to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts, etc., disclosed in this document from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and receive wireless signals. For example, one or more processors (102, 202) may 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 connected to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document through 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 the received wireless signal / channel, etc. from an RF band signal to a baseband signal in order to process the received user data, control information, wireless signal / channel, etc. using one or more processors (102, 202).One or more transceivers (106, 206) can convert user data, control information, wireless signals / channels, etc. processed using one or more processors (102, 202) from baseband signals to RF band signals. To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters.

[0755] FIG. 31 shows a signal processing circuit for a transmission signal according to one embodiment of the present disclosure. The embodiment of FIG. 31 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.

[0756] Referring to FIG. 31, 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 operation / function of FIG. 31 may be performed in the processor (102, 202) and / o...

Claims

1. Regarding the method, The first device obtains a DL-UL (downlink-uplink) priority rule that prioritizes UL (uplink); and The first device comprises the step of monitoring the common search space (CSS) based on the DL-UL priority rule that prioritizes the UL; wherein A method in which DL is prioritized in a time resource where the CSS is monitored, based on the DL-UL priority rule that prioritizes the UL.

2. In Paragraph 1, A method in which the time resource monitored by the CSS based on the DL-UL priority rule prioritizing the UL is a slot.

3. In Paragraph 1, A method in which the time resource monitored by the CSS based on the DL-UL priority rule prioritizing the UL is a PO (paging occasion).

4. In Paragraph 2, A method comprising: a time resource monitored by the CSS based on the DL-UL priority rule prioritizing the UL, a first time resource monitored on the CSS based on the DL-UL priority rule prioritizing the UL, and a second time resource adjacent to the time resource monitored on the CSS within the slot based on the DL-UL priority rule prioritizing the UL.

5. In Paragraph 4, A method in which DL is prioritized in the second time resource, which is a resource adjacent to the time resource monitored on the CSS within the slot, based on the DL-UL priority rule that prioritizes the UL, regardless of whether DCI (downlink control information) is detected in the CSS in the second time resource.

6. In Paragraph 4, A method in which the first time resource, which is a time resource monitored on the CSS based on the DL-UL priority rule that prioritizes the UL, is a time resource monitored on a control resource set (core set) based on the DL-UL priority rule that prioritizes the UL.

7. In Paragraph 4, A method in which the second time resource, which is the resource adjacent to the time resource monitored on the CSS within the slot based on the DL-UL priority rule prioritizing the UL, is the time resource monitored on the PDSCH (physical downlink shared channel) scheduled by the CSS based on the DL-UL priority rule prioritizing the UL.

8. In Paragraph 7, A method in which DL is prioritized for at least one of a PDSCH scheduled by the CSS, a PDSCH scheduled by another CSS, or a PDSCH scheduled by a USS (UE-specific (user equipment-specific) search space) in the second time resource, which is the resource adjacent to the time resource monitored on the CSS within the slot, based on the DL-UL priority rule prioritizing the UL.

9. In Paragraph 4, The above CSS is at least one of type-0 PDCCH CSS, type-0A PDCCH CSS, type-1 PDCCH CSS, or type-2 PDCCH CSS, a method.

10. In Paragraph 4, The above-mentioned first device supports only half-duplex FDD operation, method.

11. In Paragraph 10, The first device above is a Redcap UE (user equipment) or an enhanced Redcap UE, and The above RedCap UE or enhanced RedCap UE supports only the above half-duplex FDD operation, method.

12. In Paragraph 1, A method in which the DL is prioritized based on the DL-UL priority rule prioritizing the UL, in the time resource where the CSS is monitored, the CSS is associated with at least one of SI-RNTI (system information-radio network temporary identifier) ​​or P-RNTI (paging-radio network temporary identifier (P-RNTI)).

13. In Paragraph 1, The first device further comprises the step of obtaining a valid time for the DL-UL priority rule that prioritizes the UL; wherein A method in which DL takes precedence or UL takes precedence based on a default DL-UL priority rule after the expiration of the above validity period.

14. In the first device, At least one transmitter / receiver; At least one processor; and The first device comprises at least one memory connected to the at least one processor and storing instructions, wherein the instructions are executed by the at least one processor: To obtain a DL-UL (downlink-uplink) priority rule that prioritizes UL (uplink); and Monitor the common search space (CSS) based on the DL-UL priority rule that prioritizes the UL, A first device in which DL is prioritized in a time resource where the CSS is monitored based on the DL-UL priority rule that prioritizes the UL.

15. In a processing device, At least one processor; and The first device comprises at least one memory connected to the at least one processor and storing instructions, wherein the instructions are executed by the at least one processor: To obtain a DL-UL (downlink-uplink) priority rule that prioritizes UL (uplink); and Monitor the common search space (CSS) based on the DL-UL priority rule that prioritizes the UL, A processing device in which DL is prioritized in a time resource where the CSS is monitored, based on the DL-UL priority rule that prioritizes the UL.

16. A non-transient computer-readable storage medium that records instructions, When executed, the above instructions cause the first device: To obtain a DL-UL (downlink-uplink) priority rule that prioritizes UL (uplink); and Monitor the common search space (CSS) based on the DL-UL priority rule that prioritizes the UL, A non-transient computer-readable storage medium in which DL is prioritized in a time resource where the CSS is monitored based on the DL-UL priority rule that prioritizes the UL.

17. Regarding the method, The step of the second device transmitting to the first device a DL-UL (downlink-uplink) priority rule that prioritizes UL (uplink); and The second device monitors the UL from the first device based on the DL-UL priority rule that prioritizes the UL; wherein A method in which DL takes precedence in a time resource where CSS is monitored based on the above DL-UL priority rule that takes precedence over the above UL.

18. In the second device, At least one transmitter / receiver; At least one processor; and The second device comprises at least one memory connected to the at least one processor and storing instructions, wherein the instructions are executed by the at least one processor: To transmit a DL-UL (downlink-uplink) priority rule that prioritizes UL (uplink) to the first device; and Monitor the UL from the first device based on the DL-UL priority rule that prioritizes the UL, wherein A second device in which DL is prioritized in a time resource where CSS is monitored based on the DL-UL priority rule that prioritizes the UL.

19. In a processing device, At least one processor; and A second device comprising at least one memory connected to the at least one processor and storing instructions, wherein the instructions are executed by the at least one processor: To transmit a DL-UL (downlink-uplink) priority rule that prioritizes UL (uplink) to the first device; and Monitor the UL from the first device based on the DL-UL priority rule that prioritizes the UL, wherein A processing device in which DL is prioritized in a time resource where CSS is monitored based on the above DL-UL priority rule that prioritizes the above UL.

20. A non-transient computer-readable storage medium that records instructions, When executed, the above commands cause the second device: To transmit a DL-UL (downlink-uplink) priority rule that prioritizes UL (uplink) to the first device; and Monitor the UL from the first device based on the DL-UL priority rule that prioritizes the UL, wherein A non-transient computer-readable storage medium in which DL takes precedence in a time resource where CSS is monitored based on the above DL-UL priority rule that takes precedence over the above UL.

Images