Method and device for supporting reduced capability terminal in communication system

Abstract

Disclosed are a method and device for supporting a reduced capability terminal in a communication system. A method performed by a UE comprises the steps of: receiving, from a base station, first configuration information about uplink communication and second configuration information about downlink communication; selecting one communication among the uplink communication and the downlink communication on the basis of a collision between the uplink communication and the downlink communication in at least one symbol; and performing the selected one communication with the base station on the basis of the configuration information about the selected one communication.

Description

Method and device for supporting low-spec terminals in a communication system

[0001] The present disclosure relates to communication technology, and more particularly, to technology for supporting low-spec terminals in a communication system.

[0002] Communication systems can be designed considering various scenarios, service requirements, and potential system compatibility. In 5G communication systems (e.g., new radio (NR) communication systems) and / or beyond 5G communication systems (e.g., 6G communication systems), both terrestrial network (TN) and non-terrestrial network (NTN) communication are being discussed. It is expected that TN and / or NTN communication will be implemented. NTN communication may be implemented using satellites and / or aircraft. NTN communication may be implemented based on a different method than TN communication.

[0003] In a communication system supporting TN communication and / or NTN communication, terminals with various functions may exist. The terminals may have different communication performances and / or different requirements. Among reduced capability terminals, some reduced capability terminals may only perform one of downlink (DL) reception and uplink (UL) transmission operations in the same time interval even in a paired spectrum environment supporting frequency division duplex (FDD). In other words, some reduced capability terminals may be half duplex (HD)-FDD UEs. An HD-FDD UE may only perform one of DL reception and UL transmission operations in the same time interval. For an HD-FDD UE existing in a TN, terminal operations (e.g., collision handling operations) may be supported when DL reception and UL transmission collide. In NTN, propagation delays of tens of milliseconds or more can exist in the service link between the terminal and the satellite, and in the feeder link between the satellite and the ground station. Methods to improve existing collision handling operations by taking these propagation delays into account may be necessary.

[0004] The purpose of the present disclosure to solve the above problems is to provide a method and device for supporting a reduced capability terminal in a communication system supporting TN (terrestrial network) communication and / or NTN (non-terrestrial network) communication.

[0005] A method of a UE (user equipment) according to embodiments of the present disclosure for achieving the above object includes: receiving first configuration information of uplink communication and second configuration information of downlink communication from a base station; selecting one of the uplink communication and the downlink communication based on whether the uplink communication and the downlink communication collide in at least one symbol; and performing the selected one communication with the base station based on configuration information for the selected one communication.

[0006] The method of the UE may further include the step of transmitting information indicating that the UE has a collision handling capability between the uplink communication and the downlink communication to the base station; and the step of receiving information indicating a priority rule from the base station based on the UE having the collision handling capability, wherein one of the uplink communication and the downlink communication may be selected based on the priority rule.

[0007] Based on the fact that the UE does not have a collision handling capability between the uplink communication and the downlink communication, the UE may not expect to receive from the base station the first configuration information and the second configuration information for each of the uplink communication and the downlink communication that collide in the at least one symbol.

[0008] Based on the UE having a collision handling capability between the uplink communication and the downlink communication, the first configuration information and the second configuration information for each of the uplink communication and the downlink communication colliding in the at least one symbol can be received from the base station.

[0009] Based on a priority rule indicating that the uplink communication is given priority, which is received from the base station, the uplink communication may be selected among the uplink communication and the downlink communication.

[0010] Based on the fact that a priority rule indicating that the uplink communication is given priority is not received from the base station, the downlink communication may be selected among the uplink communication and the downlink communication.

[0011] The first configuration information of the above uplink communication may be configuration information of semi-static uplink communication, and the second configuration information of the above downlink communication may be configuration information of semi-static downlink communication.

[0012] The first configuration information of the above uplink communication may be DCI (downlink control information) or MAC (medium access control) CE (control element) indicating dynamic uplink communication, and the second configuration information of the above downlink communication may be DCI or MAC CE indicating dynamic downlink communication.

[0013] The UE may support HD (half duplex)-FDD (frequency division duplex), the UE may operate in an NTN (non-terrestrial network) serving cell, and the operating state of the UE may be an RRC (radio resource control) connected state or an RRC inactive state.

[0014] A method of a base station according to embodiments of the present disclosure for achieving the above object includes the steps of transmitting first configuration information of uplink communication and second configuration information of downlink communication to a UE (user equipment); and performing one of the uplink communication and the downlink communication with the UE based on a collision between the uplink communication and the downlink communication in at least one symbol, wherein the one communication is selected by the UE, and the UE supports HD (half duplex)-FDD (frequency division duplex).

[0015] The method of the base station may further include the step of receiving information from the UE indicating that the UE has a collision handling capability between the uplink communication and the downlink communication; and the step of transmitting information indicating a priority rule to the UE based on the UE having the collision handling capability, wherein one of the uplink communication and the downlink communication may be selected based on the priority rule.

[0016] Based on the fact that the UE does not have a collision handling capability between the uplink communication and the downlink communication, the base station may not transmit the first configuration information and the second configuration information for each of the uplink communication and the downlink communication that collide in the at least one symbol to the UE.

[0017] Based on the UE having a collision handling capability between the uplink communication and the downlink communication, the base station can transmit the first configuration information and the second configuration information for each of the uplink communication and the downlink communication colliding in the at least one symbol to the UE.

[0018] Based on the fact that the base station has transmitted to the UE a priority rule indicating that the uplink communication is given priority, the uplink communication may be selected among the uplink communication and the downlink communication.

[0019] Based on the fact that the base station has not transmitted to the UE a priority rule indicating that the uplink communication is given priority, the downlink communication may be selected among the uplink communication and the downlink communication.

[0020] The first configuration information of the above uplink communication may be configuration information of semi-static uplink communication, and the second configuration information of the above downlink communication may be configuration information of semi-static downlink communication.

[0021] The first configuration information of the above uplink communication may be DCI (downlink control information) or MAC (medium access control) CE (control element) indicating dynamic uplink communication, and the second configuration information of the above downlink communication may be DCI or MAC CE indicating dynamic downlink communication.

[0022] According to embodiments of the present disclosure for achieving the above object, a user equipment (UE) includes at least one processor, wherein the at least one processor causes the UE to receive first configuration information of uplink communication and second configuration information of downlink communication from a base station; select one of the uplink communication and the downlink communication based on whether the uplink communication and the downlink communication collide in at least one symbol; and perform the selected one communication with the base station based on configuration information for the selected one communication.

[0023] The at least one processor may further cause the UE to transmit information to the base station indicating that the UE has a collision handling capability between the uplink communication and the downlink communication; and, based on the UE having the collision handling capability, receive information from the base station indicating a priority rule, wherein, based on the priority rule, one of the uplink communication and the downlink communication may be selected.

[0024] Based on a priority rule indicating that the uplink communication is given priority, which is received from the base station, the uplink communication may be selected among the uplink communication and the downlink communication.

[0025] According to the present disclosure, a method for determining a communication direction (e.g., downlink (DL) or uplink (UL)) for a reduced capability terminal supporting HD (half duplex)-FDD (frequency division duplex) operation in consideration of a non-terrestrial network (NTN) environment in a communication system can be provided. A method for reporting channel state information (CSI) for a reduced capability terminal supporting HD-FDD operation in consideration of an NTN environment can be provided. Accordingly, the performance of the communication system can be improved. The effects that can be obtained by the present disclosure may not be limited to the above effects. Other effects not mentioned above may be clearly understood by those skilled in the art from the embodiments of the present disclosure and / or the technical field to which the present disclosure pertains.

[0026] Figure 1 is a conceptual diagram illustrating embodiments of a communication system.

[0027] Figure 2 is a block diagram illustrating embodiments of communication nodes constituting a communication system.

[0028] Figure 3 is a conceptual diagram illustrating embodiments of a wireless interface protocol structure in a communication system.

[0029] FIG. 4 is a conceptual diagram illustrating examples of time resources through which wireless signals are transmitted in a communication system.

[0030] Figure 5 is a conceptual diagram for explaining the time difference between the reception timing of the #i-th downlink frame and the transmission timing of the #i-th uplink frame in a communication system.

[0031] Figure 6 is a conceptual diagram illustrating embodiments of a time / frequency resource grid of a communication system.

[0032] Figure 7 is a conceptual diagram illustrating embodiments of SS / PBCH blocks in a communication system.

[0033] Figure 8 is a conceptual diagram illustrating common delays in an NTN environment.

[0034] Figures 9a to 9d are conceptual diagrams illustrating various forms of a three-dimensional space communication system.

[0035] Figure 10a is a conceptual diagram illustrating embodiments of HD GP (half-duplex guard period) according to terminal capabilities.

[0036] Figure 10b is a conceptual diagram illustrating embodiments of HD GP according to terminal capabilities.

[0037] Figure 11 is a conceptual diagram illustrating the TA mismatch value between a terminal and a base station.

[0038] Figure 12 is a conceptual diagram illustrating the TA mismatch value between a terminal and a base station.

[0039] Figure 13 is a conceptual diagram illustrating the TA mismatch value between a terminal and a base station.

[0040] Figure 14 is a conceptual diagram illustrating a TA determination method.

[0041] Figure 15 is a flowchart illustrating a RACH-less HO procedure.

[0042] Figure 16 is a conceptual diagram illustrating embodiments of conflict handling for cases 3 and 4 based on priority flags.

[0043] The present invention is susceptible to various modifications and embodiments. Specific embodiments are illustrated and described in detail in the drawings. However, this is not intended to limit the present invention to specific embodiments, but rather to encompass all modifications, equivalents, and alternatives falling within the spirit and technical scope of the present invention.

[0044] While terms such as "first" and "second" may be used to describe various components, these components should not be limited by these terms. These terms are used solely to distinguish one component from another. For example, without departing from the scope of the present invention, a first component could be referred to as a "second component," and similarly, a second component could also be referred to as a "first component." The term "and / or" encompasses any combination of multiple related items described herein or any one of multiple related items described herein.

[0045] In the embodiments of the present application, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B.” Furthermore, in the embodiments of the present application, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B.”

[0046] In the embodiments of the present application, (re)transmission may mean “transmission,” “retransmission,” or “transmission and retransmission,” (re)setting may mean “setting,” “resetting,” or “setting and resetting,” (re)connection may mean “connection,” “reconnection,” or “connection and reconnection,” and (re)connection may mean “connection,” “reconnection,” or “connection and reconnection.”

[0047] When a component is referred to as being "connected" or "connected" to another component, it should be understood that it may be directly connected or connected to that other component, but that there may be other components intervening. Conversely, when a component is referred to as being "directly connected" or "connected" to another component, it should be understood that there are no other components intervening.

[0048] The terminology used in this application is only used to describe specific embodiments and is not intended to limit the present invention. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this application, it should be understood that the terms "comprise" or "have" indicate the presence of a feature, number, step, operation, component, part, or combination thereof described in the specification, but do not exclude in advance the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

[0049] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and will not be interpreted in an idealized or overly formal sense unless explicitly defined herein.

[0050] Hereinafter, with reference to the attached drawings, preferred embodiments of the present invention will be described in more detail. In order to facilitate an overall understanding in describing the present invention, identical reference numerals will be used for identical components in the drawings, and redundant descriptions of identical components will be omitted.

[0051] A communication network to which embodiments of the present invention are applied will be described. The communication network may be a non-terrestrial network (NTN), a 4G communication network (e.g., a long-term evolution (LTE) communication network), a 5G communication network (e.g., a new radio (NR) communication network), or a 6G communication network. The 4G communication network and the 5G communication network can be classified as terrestrial networks.

[0052] The non-terrestrial network may operate based on LTE technology and / or NR technology and / or 6G technology. The non-terrestrial network may support communication in frequency bands above 6 GHz as well as below 6 GHz. 4G communication networks may support communication in frequency bands below 6 GHz. 5G and / or 6G communication networks may support communication in frequency bands above 6 GHz as well as below 6 GHz. The communication networks to which embodiments of the present invention are applied are not limited to those described below, and the embodiments of the present invention may be applied to various communication networks. Here, the term "communication network" may be used interchangeably with the term "communication system."

[0053] In the present disclosure, “an operation (e.g., a transmission operation) is set” may mean that “setting information for the operation (e.g., information, information elements, parameters)” and / or “information instructing performance of the operation” are signaled. “Information (e.g., information elements, parameters) is set” may mean that the information is signaled. In the present disclosure, the signaling may be at least one of system information (SI) signaling (e.g., transmission of a system information block (SIB) and / or a master information block (MIB)), RRC signaling (e.g., transmission of RRC parameters and / or upper layer parameters), MAC control element (CE) signaling, or PHY signaling (e.g., transmission of downlink control information (DCI), uplink control information (UCI), and / or sidelink control information (SCI)). A message for SI signaling may be referred to as an SI message, a message for RRC signaling may be referred to as an RRC message, a message for MAC CE signaling may be referred to as a MAC message, and a message for PHY signaling may be referred to as a PHY message. The above-described messages may be expressed as a first message, a second message, a third message, etc.

[0054] In the present disclosure, a phrase including “if (e.g., when ~)” can be expressed as a phrase including “based on (e.g., based on ~)” or a phrase including “in response to (e.g., in response to ~)”. In other words, a phrase including “if ~)” can be interpreted as being identical or similar to a phrase including “based on” or a phrase including “in response to”.

[0055] In this disclosure, "time" may refer to a time point, and "time point" may refer to time. "Time" and "point point" may be used interchangeably. The reception time of a signal or channel may refer to the start time of reception or the end time of reception. The transmission time of a signal or channel may refer to the start time of transmission or the end time of transmission.

[0056] Throughout the specification, the network may include, for example, wireless internet such as WiFi (wireless fidelity), mobile internet such as WiBro (wireless broadband internet) or WiMax (world interoperability for microwave access), 2G mobile communication networks such as GSM (global system for mobile communication) or CDMA (code division multiple access), 3G mobile communication networks such as WCDMA (wideband code division multiple access) or CDMA2000, 3.5G mobile communication networks such as HSDPA (high speed downlink packet access) or HSUPA (high speed uplink packet access), 4G mobile communication networks such as LTE (long term evolution) or LTE-Advanced, 5G mobile communication networks, and 6G mobile communication networks.

[0057] Throughout the specification, a terminal may be referred to as a terminal, an access terminal, a mobile terminal, a station, a subscriber station, a mobile station, a portable subscriber station, a node, a device, etc.

[0058] Here, a desktop computer, laptop computer, tablet PC, wireless phone, mobile phone, smart phone, smart watch, smart glass, e-book reader, portable multimedia player (PMP), portable game console, navigation device, digital camera, digital multimedia broadcasting (DMB) player, digital audio recorder, digital audio player, digital picture recorder, digital picture player, digital video recorder, digital video player, etc. capable of communicating with the terminal can be used.

[0059] Throughout the specification, a base station may be referred to as a NodeB, an evolved NodeB, a 5G NodeB (gNB), a 6G node, a base transceiver station (BTS), a radio base station, a radio transceiver, an access point, an access node, a road side unit (RSU), a digital unit (DU), a cloud digital unit (CDU), a radio remote head (RRH), a radio unit (RU), a transmission point (TP), a transmission and reception point (TRP), a relay node (repeater node), etc.

[0060] Figure 1 is a conceptual diagram illustrating embodiments of a communication system.

[0061] Referring to FIG. 1, a communication system (100) may include a plurality of communication nodes (110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, 130-6). The plurality of communication nodes may support 4G communication (e.g., long term evolution (LTE), advanced LTE-A (LTE-A), 5G communication (e.g., new radio (NR)), 6G communication, etc.) specified in the 3rd generation partnership project (3GPP) standard. 4G communication may be performed in a frequency band of 6 GHz or less, and 5G and 6G communication may be performed in a frequency band of 6 GHz or more as well as a frequency band of 6 GHz or less.

[0062] For example, for 4G communication, 5G communication, and 6G communication, multiple communication nodes may use a communication protocol based on CDMA (code division multiple access), a communication protocol based on WCDMA (wideband CDMA), a communication protocol based on TDMA (time division multiple access), a communication protocol based on FDMA (frequency division multiple access), a communication protocol based on OFDM (orthogonal frequency division multiplexing), a communication protocol based on Filtered OFDM, a communication protocol based on CP (cyclic prefix)-OFDM, a communication protocol based on DFT-s-OFDM (discrete Fourier transform-spread-OFDM), a communication protocol based on OFDMA (orthogonal frequency division multiple access), a communication protocol based on SC (single carrier)-FDMA, a communication protocol based on NOMA (Non-orthogonal Multiple Access), a communication protocol based on GFDM (generalized frequency division multiplexing), a communication protocol based on FBMC (filter bank multi-carrier), a communication protocol based on UFMC (universal filtered multi-carrier), a communication protocol based on SDMA (Space Division Multiple Access), It can support communication protocols based on OTFS (orthogonal time-frequency space).

[0063] In addition, the communication system (100) may further include a core network. If the communication system (100) supports 4G communication, the core network may include a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), a mobility management entity (MME), etc. If the communication system (100) supports 5G communication and 6G communication, the core network may include a user plane function (UPF), a session management function (SMF), an access and mobility management function (AMF), etc.

[0064] Meanwhile, each of the plurality of communication nodes (110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, 130-6) constituting the communication system (100) may have the following structure.

[0065] Figure 2 is a block diagram illustrating embodiments of communication nodes constituting a communication system.

[0066] Referring to FIG. 2, a communication node (200) may include at least one processor (210), a memory (220), and a communication device (230) that is connected to a network and performs communication. In addition, the communication node (200) may further include an input interface device (240), an output interface device (250), a storage device (260), etc. Each component included in the communication node (200) may be connected by a bus (270) and communicate with each other.

[0067] However, each component included in the communication node (200) may be connected through an individual interface or individual bus centered around the processor (210), rather than a common bus (270). For example, the processor (210) may be connected to at least one of the memory (220), the communication device (230), the input interface device (240), the output interface device (250), and the storage device (260) through a dedicated interface.

[0068] The processor (210) can execute program commands stored in at least one of the memory (220) and the storage device (260). The processor (210) may refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor in which methods according to embodiments of the present invention are performed. Each of the memory (220) and the storage device (260) may be configured with at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory (220) may be configured with at least one of a read-only memory (ROM) and a random access memory (RAM).

[0069] Referring again to FIG. 1, the communication system (100) may include a plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) and a plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6). The communication system (100) including the base stations (110-1, 110-2, 110-3, 120-1, 120-2) and the terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) may be referred to as an “access network.” The first base station (110-1), the second base station (110-2), and the third base station (110-3) can each form a macro cell. The fourth base station (120-1) and the fifth base station (120-2) can each form a small cell. The fourth base station (120-1), the third terminal (130-3), and the fourth terminal (130-4) can be within the cell coverage of the first base station (110-1). The second terminal (130-2), the fourth terminal (130-4), and the fifth terminal (130-5) can be within the cell coverage of the second base station (110-2). The fifth base station (120-2), the fourth terminal (130-4), the fifth terminal (130-5), and the sixth terminal (130-6) may be within the cell coverage of the third base station (110-3). The first terminal (130-1) may be within the cell coverage of the fourth base station (120-1). The sixth terminal (130-6) may be within the cell coverage of the fifth base station (120-2).

[0070] Here, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be referred to as a NodeB, an evolved NodeB, a gNB, a BTS (base transceiver station), a radio base station, a radio transceiver, an access point, an access node, etc. Each of the plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) may be referred to as a UE (user equipment), a terminal, an access terminal, a mobile terminal, a station, a subscriber station, a mobile station, a portable subscriber station, a node, a device, etc.

[0071] Meanwhile, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may operate in a different frequency band or may operate in the same frequency band. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be connected to each other via an ideal backhaul link or a non-ideal backhaul link, and may exchange information with each other via the ideal backhaul link or the non-ideal backhaul link. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be connected to the core network via the ideal backhaul link or the non-ideal backhaul link. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit a signal received from the core network to the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6), and can transmit a signal received from the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) to the core network.

[0072] FIG. 3 is a conceptual diagram illustrating embodiments of a radio interface protocol architecture in a communication system.

[0073] Referring to FIG. 3, one embodiment of a wireless interface protocol structure (300) of a communication system may include a radio resource control (RRC) layer (310), a medium access control (MAC) layer (320), a physical (PHY) layer (330), etc. One embodiment of the wireless interface protocol structure (300) illustrated in FIG. 3 may correspond to various interface embodiments, such as an interface between a terminal and a base station, an interface between an IAB-node DU (distributed unit) of an IAB (integrated access backhaul) network and an IAB-node MT (mobile terminal), an interface between an IAB-node DU and a lower node (e.g., a terminal), an interface between an IAB-node MT and an upper node, and an interface between a plurality of terminals.

[0074] Near the PHY layer (330), an RRC layer (310) and a MAC layer (320) may be placed above the PHY layer (330). For example, the MAC layer (320) may be placed above the PHY layer (330). The RRC layer (310) may be placed above the MAC layer (320).

[0075] The MAC layer (320) may be connected to a higher layer (e.g., the RRC layer (310)) through logical channels (315). The PHY layer (330) may be connected to the higher MAC layer (320) through transport channels (325). The PHY layer (330) may exchange control information and / or measurement information (350) with the RRC layer (310).

[0076] The PHY layer (330) may be referred to as 'layer 1' or 'L1'. The MAC layer (320) may be referred to as 'layer 2' or 'L2'. The RRC layer (310) may be referred to as 'layer 3' or 'L3'. The RRC layer (310) and the MAC layer (320) may be collectively referred to as 'upper layers'.

[0077] In the present disclosure, 'L1 signaling' may refer to signaling such as downlink control information (DCI) transmitted through a physical downlink control channel (PDCCH), which is a PHY layer (330) channel, uplink control information (UCI) transmitted through a physical uplink control channel (PUCCH), and sidelink control information (SCI) transmitted through a physical sidelink control channel (PSCCH). Similarly, 'upper layer signaling' in the present disclosure may include L2 signaling transmitted through a MAC control element (CE), L3 signaling transmitted through RRC signaling, etc.

[0078] In communication systems such as 5G, one or more of the numerologies in Table 1 may be used for various purposes, such as reducing inter-carrier interference (ICI) according to frequency band characteristics and reducing latency according to service characteristics.

[0079]

[0080] Table 1 is merely an example for convenience of explanation, and embodiments of numerologies used in a communication system may not be limited thereto. Numerology μ may correspond to information of subcarrier spacing (SCS) Δf and cyclic prefix (CP). A terminal may identify numerology μ and CP applied to a downlink bandwidth part and / or an uplink bandwidth part based on subcarrierSpacing and / or cyclicPrefix, which are parameters of a higher layer.

[0081] FIG. 4 is a conceptual diagram illustrating examples of time resources through which wireless signals are transmitted in a communication system.

[0082] Referring to FIG. 4, the time resource for transmitting a wireless signal in a communication system (400) is one or more ( ) a frame (430) consisting of a subframe (420), one or more ( ) a subframe (420) consisting of a slot (410), and It can be expressed as a slot (410) consisting of OFDM symbols. The values ​​may follow the values ​​in Table 2 if they are regular cyclic prefixes according to the set numeral. The values ​​may follow the values ​​in Table 3 in case of an extended cyclic prefix according to the set numerology. OFDM symbols included in one slot may be distinguished as downlink (DL) symbols, flexible (FL) symbols, or uplink (UL) symbols by upper layer signaling or a combination of upper layer signaling and L1 signaling.

[0083]

[0084]

[0085] In an NR communication system (e.g., a 5G communication system), a frame (430) may have a length of 10 ms, and a subframe (420) may have a length of 1 ms. The frame (230) may be divided into two half-frames having the same length, and a first half-frame (half-frame #0) may be composed of sub-frames #0 to #4, and a second half-frame (half-frame #1) may be composed of sub-frames #5 to #9. One carrier may include a set of uplink frames and a set of downlink frames. FIG. 5 is a conceptual diagram for explaining a time difference between the reception timing of the #i-th downlink frame and the transmission timing of the #i-th uplink in a communication system.

[0086] Referring to FIG. 5, the time difference between the reception timing of downlink frame #i (500) and the transmission timing of uplink frame #i (510) is T TA (520) may be. The terminal may compare T with the start time of reception of downlink frame #i (500). TA Transmission for uplink frame #i (510) can be started at an earlier point in time. T TA can be called timing advance (TA) or timing adjustment (TA). The base station can inform the terminal of T through upper layer signaling or L1 signaling. TA You can instruct it to change the value. For example, The application can be set at the base station and / or terminal. In the NR communication system, T c Is can be defined as Δf max is Δf max = can be defined as 480kHz, and Nf is N f = can be defined as 4096, and N TA,offset can be a value set by L3 signaling, and N TA T is indicated by L2 signaling A And it can be a value determined based on the mathematical formula 1 below.

[0087]

[0088] N TA,offset and N TA The description may be an example for a specific situation. Various options may exist other than the above description, but not all possible cases may be listed in this disclosure so as not to obscure the gist of the description.

[0089] Figure 6 is a conceptual diagram illustrating embodiments of a time / frequency resource grid of a communication system.

[0090] Referring to FIG. 6, the time / frequency resource grid (600) of the communication system subcarriers of the dog and It can be composed of OFDM symbols. The resource grid can be defined per numeral and / or per carrier. may be the location of a common resource block (CRB) indicated by upper layer signaling. may be the number of resource blocks (RBs) (610) starting from the CRB. In other words, may mean carrier bandwidth. and / or can have different values ​​for each link direction (e.g., uplink, downlink, sidelink) or for each numerology (μ). The numerology (μ) can be referred to by other terms, such as subcarrier spacing (SCS) settings, as needed.

[0091] Each element within the resource grid for setting the antenna port (p) and SCS (μ) may be referred to as a resource element (RE) (620). The RE (620) is Each position can be uniquely defined. k can be an index in the frequency domain (e.g., a subcarrier index), and l can mean a symbol position in the time domain (e.g., a symbol index). is a physical channel or signal complex value may correspond to physical resources used to transmit. One resource block (610) is continuous in the frequency domain. can be defined as a set of subcarriers.

[0092] Compared to 3G / 4G communication systems, 5G communication systems can use a wider carrier bandwidth. To reduce the high implementation complexity and / or high power consumption of terminals due to the wide carrier bandwidth, the concept of a bandwidth part (BWP) can be introduced. A bandwidth part can be composed of consecutive common resource blocks, and the starting resource block position of the bandwidth part ( ) and the number of resource blocks that constitute the corresponding bandwidth portion ( ) can satisfy mathematical expressions 2 and 3.

[0093]

[0094]

[0095] Within a single component carrier (CC), up to four downlink bandwidth segments can be configured for a terminal. Only one downlink bandwidth segment can be activated at a time. The terminal may not receive physical downlink shared channels (PDSCHs), physical downlink control channels (PDCCHs), or channel state information reference signals (CSI-RSs) outside of the activated bandwidth segments.

[0096] Within a single component carrier, up to four uplink bandwidth segments can be configured for a terminal. Of the configured uplink bandwidth segments, only one uplink bandwidth segment can be activated at a time. The terminal may not transmit PUSCH (physical uplink shared channel), PUCCH (physical uplink control channel), SRS (sounding reference signal), or other bandwidth segments outside of the activated bandwidth segment.

[0097] FIG. 7 is a conceptual diagram illustrating embodiments of a synchronization signal and physical broadcast channel block (SSB) in a communication system.

[0098] Referring to FIG. 7, the SS / PBCH block (700) of the communication system may include a primary synchronization signal (PSS) transmitted in the middle 127 subcarriers of the first OFDM symbol, a secondary synchronization signal (SSS) transmitted in the middle 127 subcarriers of the third OFDM symbol, and a physical broadcast channel (PBCH) transmitted in the second, third, and fourth OFDM symbols. The PBCH, which occupies the widest bandwidth, may be transmitted over 20 RBs. 20 RBs may be 3.6 MHz based on a 15 kHz SCS. The base station may transmit one SSB using the same beam. When the number of antennas of the base station increases, it may be necessary to operate multiple beams, such as when more than one analog beam is applied to support high frequencies. In this case, the base station can support multi-beam operation by transmitting multiple SSBs. A beam may be expressed in various terms such as transmit precoding and spatial transmission filter. However, in order not to obscure the main point of the explanation, transmission precoding, spatial transmission filter, etc. may be referred to as beam.

[0099] The base station can transmit multiple SSBs (730, 740, 750, 760) to represent multiple beams (e.g., beam #1, beam #2, beam #3, beam #4). One or more SSBs can be transmitted in one slot according to a pre-arranged pattern for each numerology. SSBs (730, 740, 750, 760) to which different beams are applied can be included in an SS burst (720). In other words, SSBs (730, 740, 750, 760) to which different beams are applied can be configured as one set. The terminal can assume a half-frame window having a length of 5 ms at the time of monitoring the SSB. An SS burst set (715) configured by upper layer signaling within the half-frame window can include one or more SS bursts (720). The terminal may not know or be unable to use the RRC configuration value(s) during the initial access (IA) procedure. In this case, the terminal may assume that the period of the SS burst set (710) is 20 ms and perform reception and / or measurement operations for SSB based on this assumption.

[0100] In the present disclosure, the downlink network structure and the uplink network structure can be independently configured considering a non-terrestrial network (NTN) environment. For example, the downlink network structure and the uplink network structure can be configured differently. Considering the NTN environment, the network structure can be independently configured for each component carrier (CC), carrier group (CG), and / or cell. For example, the network structure can be configured differently for each CC, CG, and / or cell. In order to compensate for uplink propagation loss considering the NTN environment, the transmission gain of a relay (or repeater) can be controlled. When a terminal performs DC (dual connectivity) operation for a terrestrial network (TN)-NTN or NTN-NTN, uplink communication (e.g., uplink transmission) can be controlled based on power reduction and / or an external power source.

[0101] When a terminal performs a DC operation for TN-NTN or NTN-NTN, power alignment for downlink communication (e.g., downlink reception) to reduce a dynamic range may be requested. In the present disclosure, uplink transmission may mean uplink communication, and downlink reception may mean downlink communication. The dynamic range may be a power dynamic range. The power dynamic range may mean the difference between the minimum power and the maximum power for a specific resource, or the difference between the power (e.g., actual power) and the average power for a specific resource. The specific resource may be an RE, a symbol, an RB, a subband, a carrier, etc. Alternatively, the power dynamic range may mean the difference between the power for a first network (e.g., received power, transmitted power, average power, minimum power, maximum power) and the power for a second network (e.g., received power, transmitted power, average power, minimum power, maximum power).

[0102] Figure 8 is a conceptual diagram illustrating common delays in an NTN environment.

[0103] Referring to FIG. 8, at least three types of wireless links may exist in an NTN environment (e.g., an NTN scenario). The at least three types of wireless links may include a service link (831), an inter-satellite link (ISL) (841), and a feeder link (851, 852). The service link (831) may be a link between a terminal (810) and a satellite (821). The ISL (841) may be a link between satellites (821, 822). The feeder link (851, 852) may be a link between a terrestrial network (860) connected to a data network (870) and satellites (821, 822). The terrestrial network (860) may be a terrestrial gateway.

[0104] The terminal can calculate (e.g., determine) the timing advance (TA) of the terminal based on position information acquired from a global navigation satellite system (GNSS) and / or ephemeris information of a serving satellite. The TA can be determined based on Equation 4 or Equation 5 below. Equations 4 and 5 may have the same meaning. The variables of Equation 4 and Equation 5 may be cross-referenced. The ephemeris information can be acquired from a serving satellite (e.g., a serving base station).

[0105]

[0106]

[0107] N TA can be defined as 0 for PRACH. N TA may be updated based on the TA command field of the msg2, msgB, and / or MAC CE TA command. N TA,UE-specific can be used to pre-compensate for delays in service links. N TA,UE-specific may be a TA estimated by the terminal itself. N TA,common can be a network control public TA. N TA,common may include timing offsets that are deemed necessary in a network (e.g., a telecommunications network). N TA,common can support values ​​of 0. N TA,offset may be a fixed offset used to calculate TA. The terminal may not assume that the round trip time (RTT) between the terminal and the base station is the same as the TA calculated for msg1 / msgA.

[0108] The validity period of ephemeris information (e.g., satellite ephemeris data) may indicate the maximum time that a terminal can apply satellite ephemeris (e.g., existing satellite ephemeris) without acquiring new ephemeris information. The validity period of ephemeris information may be set by the network. N TA The update procedure can be performed based on the TA command of msg2 / msgB and / or the TA command of MAC CE. N TA The update procedure can be used for alignment (e.g., adjustment, modification, control) of uplink timing. When msg2 / msgB containing a TA command (e.g., TA) is received, the terminal can perform the first adjustment (e.g., alignment, modification, control) procedure. N TA can be updated as shown in mathematical formula 6 below.

[0109]

[0110] T in Equation 5 A may be indicated by the TA command field contained in msg2 / msgB. If a MAC CE containing a TA command is received, N TA can be updated as shown in mathematical formula 7 below.

[0111]

[0112] T in Equation 6 A may be indicated by the TA command field included in the MAC CE. The common TA (e.g., common TA) may include a parameter indicating timing drift. The terminal may apply the common TA based on the parameter(s) provided by the network. If the requirement(s) for uplink timing error are defined, the offset between the common TA according to the parameters provided by the network and the RTT of the actual feeder link may not be considered.

[0113] Scheduling offset (K) to improve timing relationship offset) can be introduced. Scheduling offset (K offset ) can be set by system information, and the scheduling offset (K offset ) can be used in the initial access procedure. In this case, the cell-specific K used in all beams of at least one cell offset The setting of K can be supported offset In addition, the scheduling offset for MAC CE is K mac can be defined as

[0114] Downlink frame timing and uplink frame timing can be aligned to the base station. In this case, K may be used for terminal operation and / or assumption regarding downlink and uplink settings indicated by the MAC CE command transmitted on the PDSCH. mac may not be required. On the other hand, the downlink frame timing and the uplink frame timing may not be aligned to the base station. In this case, K may be used for terminal operation and / or assumption regarding the downlink configuration indicated by the MAC CE command transmitted on the PDSCH. mac may be required, and K for terminal operation and / or assumptions regarding uplink configuration as indicated by the MAC CE command transmitted on the PDSCH. mac may not be necessary. K mac The information may be included in the system information. In other words, the base station is K mac System information including information can be transmitted to the terminal. The terminal can receive the system information from the base station and K included in the system information. mac You can check the information.

[0115] After the initial connection procedure, K offset Updates may be supported for receiving TA commands. offset By introducing K, the adjustment (e.g., alignment, correction, control) of uplink transmission timing can be supplemented. After the initial access procedure, K offsetFor updates, the network (e.g., base station) uses MAC CE to update UE-specific K offset can provide and / or update cell-specific K set by system information. offset For , one of the following two options (e.g., options 1 and 2) may be selected. Option 1 may be signaling one offset value. For example, the value signaled according to option 1 may include the RTT of the service link and the RTT between the service satellite (e.g., the serving satellite) and the reference point (e.g., the reference point). In the present disclosure, the signaling may be at least one of SI (system information) signaling, RRC signaling, MAC CE signaling, or PHY signaling.

[0116] Option 2 may signal two offset values. The two offset values ​​may include a first offset value and a second offset value. K offset can be the sum of two offset values. The first offset value can be the RTT between the serving satellite and the reference point (or a value determined based on the common TA). The second offset value can be the RTT of the service link. The value indicated by the system information (e.g., K offset ) other than K offset If not provided to this terminal, the terminal shall use a value indicated by system information (e.g., K offset ) can be applied to improve all timing relationships. The network (e.g., base station) can use K for MAC CE. offset K is a scheduling offset other than mac can be provided to the terminal. The network is K mac If the terminal does not provide K mac =0 can be assumed.

[0117] The estimate of the terminal-base station RTT is the TA and K of the terminal. mac can be equal to the sum of the terminal-base station RTT. The terminal-base station RTT can mean the RTT in the link between the terminal and the base station. The terminal-base station RTT can mean the RTT between the terminal and the base station. The terminal's TA is T TA can be determined based on the base station-satellite RTT estimate N TA,common ×T c Wow K mac can be equal to the sum of . Base station-satellite RTT can mean the RTT in the link between the base station and the satellite. If the network is K mac If the terminal does not provide K mac =0 can be assumed.

[0118] NTN ephemeris (e.g., ephemeris information) can be divided into the serving cell's ephemeris and the neighboring cell's ephemeris. Information about when a cell will cease local service and / or timing information (e.g., timers and / or absolute time) for a new cell can be supported, at least in an Earth-fixed NTN scenario. Whether both types of ephemeris information (e.g., serving cell's ephemeris information and neighboring cell's ephemeris information) are required can be determined based on system information and / or ephemeris information.

[0119] At least for uplink scheduling adaptation, a UE can report information about UE-specific TA pre-compensation. During an RA procedure, the UE can report the UE-specific TA pre-compensation to the base station using MAC CE. If the reporting operation is enabled by the network, the UE can report the UE-specific TA pre-compensation information to the base station (e.g., the network) in an RA procedure using MAC CE (e.g., the transmission procedure of msgA, the transmission procedure of msg3, and / or the transmission procedure of msg5). The content of the UE-specific TA pre-compensation reported in the RA procedure using MAC CE may be UE-specific TA. UE-specific TA reporting (e.g., reporting of UE-specific TA pre-compensation) in the RA procedure may be enabled / disabled by SI (system information). UE-specific TA reporting (e.g., reporting information about UE-specific TA) may be supported in a connected mode (e.g., RRC connected mode). Event triggers may be supported to report information about UE-specific TAs in connected mode. If an event trigger is configured, the UE may report information about UE-specific TA pre-compensation to the target cell during the RA procedure.

[0120] If the UE cannot report UE location information in connected mode, the content of the UE-specific TA reported to the base station in connected mode may be UE-specific TA pre-compensation. If the content of the information about the UE-specific TA reported to the base station is UE location information in connected mode, RRC signaling may be used to report the UE location information (e.g., information about the UE-specific TA). If the UE location information can be reported to the base station in connected mode, for the purpose of TA reporting (e.g., reporting information about the UE-specific TA, reporting UE location information) in connected mode, the network (e.g., the base station) may configure the UE to report the UE-specific TA pre-compensation and / or the UE location information. If the content of the information about the UE-specific TA to be reported to the network is the value of the TA pre-compensation (e.g., UE-specific TA pre-compensation) in connected mode, the UE may report the information about the UE-specific TA using MAC CE.

[0121] UE location reporting can be performed based on an event trigger. Event-triggered UE location reporting can be configured by the base station to obtain information on UE location updates of a mobile terminal in a connected mode (e.g., RRC connected mode). In other words, the base station can transmit configuration information for event-based UE location reporting to the terminal. Periodic UE location reporting can be configured by the base station to obtain information on UE location updates of a mobile terminal in a connected mode (e.g., RRC connected mode).

[0122] To enable the UE to report information about UE-specific TAs during a handover procedure, a new indication of RRC reconfiguration using synchronization may not be required. SI (e.g., SIB) may indicate whether information indicating the activation or deactivation of TA reporting (e.g., reporting information about UE-specific TAs) in the target cell is transmitted via the handover command.

[0123] Information about UE-specific TA pre-compensation may not be reported in RA procedures triggered by requests from other SIs. The event trigger for reporting information about UE-specific TA (e.g., UE-specific TA pre-compensation) may be based on a TA value. A TA offset threshold may be used in the event-triggered reporting procedure. At least the TA offset threshold may be a value between the current UE-specific TA value and the last successfully reported UE-specific TA value.

[0124] In a quasi-earth fixed scenario or an earth fixed scenario, timing information regarding when a cell ceases service to a given area may be required to support cell reselection operations (e.g., NTN cell reselection operations). A base station (e.g., a cell, a network) may transmit system information including timing information regarding when a cell ceases service to a given area to a terminal. The system information may be broadcast. The point in time when a cell ceases service to a given area may refer to a cell downtime. The broadcasting operation of information regarding the cell downtime using a SIB may be applicable to a quasi-earth fixed cell. In other words, the broadcasting operation of information regarding the cell downtime using a SIB may not be applicable to a mobile cell. In a quasi-earth fixed scenario, timing information regarding when a cell ceases service (e.g., a cell downtime) may be used to determine when measurements for neighboring cells are performed. In a quasi-earth fixed scenario (e.g., a quasi-earth fixed cell), system information including information about the reference location of a cell (e.g., a serving cell and / or a neighboring cell) may be broadcast. The reference location may be a cell center.

[0125] In a quasi-earth fixed scenario, a terminal can start measuring neighboring cells before the serving cell stops serving the current area. In a quasi-earth fixed scenario, information about the cell downtime (e.g., timing information) broadcasted can indicate the time when the cell does not cover the current area. "The cell does not cover the current area" can mean "the cell does not provide service for the current area." In a quasi-earth fixed scenario, it can be configured that the terminal performs a measurement operation on a neighboring cell (e.g., an adjacent cell) before the time when the serving cell stops broadcasting (e.g., the cell downtime, the time when the cell stops covering the current area). The exact time when the terminal performs the measurement operation on the neighboring cell can be determined depending on the implementation of the terminal.

[0126] Figures 9a to 9d are conceptual diagrams illustrating various forms of a three-dimensional space communication system.

[0127] Referring to FIGS. 9A to 9D , a three-dimensional space communication system (e.g., a space communication network) may be designed such that a terminal can perform wireless communication using a device (e.g., a communication node) located in the sky. In the present disclosure, a satellite (e.g., a three-dimensional space device) may refer to a High-Altitude Pseudo Satellite (HPAS) or High Altitude Platform Station, an Unmanned Aerial Vehicle (UAV), an Urban Air Mobility (UAM), etc. A satellite (e.g., a three-dimensional space device) may not be limited to an HPAS, a UAV, and / or a UAM. A satellite may refer to a three-dimensional space device.

[0128] In the embodiment of FIG. 9A, a satellite (920) can relay communication between a terminal (910) and a base station (930). The terminal (910) can be an NTN node (e.g., an NTN terminal). The satellite (920) can be a remote radio head (RRH). The satellite (920) can perform a function of relaying a Uu radio interface signal between the terminal (910) and the base station (930). The NTN gateway can be the base station (930). In the embodiment of FIG. 9A, the satellite (920) can relay a signal between the terminal (910) and the base station (930), and the satellite (920) can operate transparently. In other words, the satellite (920) can be a transparent satellite.

[0129] In the embodiment of FIG. 9B, the satellite (920) can support some or all of the functions of the base station (930). The satellite (920) can perform the functions of a base station or a relay node. The satellite (920) can be a satellite base station, the satellite (920) can directly form (e.g., establish) a Uu link (e.g., a Uu radio interface) with the terminal (910), and the satellite (920) can be a regenerative satellite. In other words, the satellite (920) can support a regeneration operation for a signal.

[0130] In the embodiment of FIG. 9C, a terminal (910) can form (e.g., establish) a Uu link with a relay node (940). The relay node (940) can be located around the terminal, outdoors, indoors, or on the ground. Alternatively, the relay node (940) can be located within a satellite (920). The relay node (940) can be connected to a base station (930) via the satellite (920). The NTN node can be the satellite (920). The base station (930) can be a terrestrial base station. A terrestrial base station can refer to a base station located on the ground. The satellite (920) can relay communication between the relay node (940) and the base station (930). The satellite (920) can be an RRH. The satellite (920) can perform a function of relaying Un radio interface signals between the relay node (940) and the base station (930). The NTN gateway can be the base station (930).

[0131] In the embodiment of FIG. 9D, a terminal (910) can form (e.g., establish) a Uu link with a relay node (940). The relay node (940) can be located around the terminal, outdoors, indoors, or on the ground. The NTN node can be a base station (930). A satellite (920) can support some or all of the functions of the base station (930). An Un link can be established between the relay node (940) and a satellite (920) that supports the functions(s) of the base station.

[0132] In this disclosure, methods for supporting a reduced capability terminal will be described. A reduced capability terminal may be referred to as a RedCap UE (user equipment). A reduced capability terminal may support HD (half duplex)-FDD (frequency division duplex) operation. A reduced capability terminal supporting HD-FDD operation may be referred to as an HD-FDD RedCap UE, an HD-FDD terminal, or an HD terminal. A reduced capability terminal may access an NTN. In this disclosure, a terminal may be interpreted as a reduced capability terminal or a general terminal (e.g., a legacy terminal) depending on the context.

[0133] Methods for supporting HD-FDD RedCap UE considering NTN environment will be described. Methods for HD-FDD RedCap UE to determine one communication (e.g., one operation) among UL (uplink) communication (e.g., UL transmission operation) and DL (downlink) communication (e.g., DL reception operation) considering NTN environment will be described. Methods for performing one determined communication (e.g., UL communication or DL ​​communication) will be described. Methods for HD-FDD RedCap UE to measure channel state, generate channel state information (CSI), and / or report CSI considering NTN environment will be described. Parameters (e.g., K) that affect the preparation time of DL reception processing of a terminal, the preparation time of UL transmission processing of a terminal, the transmission and reception time of a CSI reference signal, the preparation time of CSI reporting, etc., will be described. offset When the terminal is instructed to change the above-described times, the terminal's operations according to the change will be described. The above-described parameters may refer to NTN parameters.

[0134] In a communication system (e.g., NR communication system, 5G communication system), a base station (e.g., IAB node, relay station) can transmit configuration information of CSI reporting to a terminal or mobile terminal (MT) using time and / or frequency resources. The terminal or MT can receive configuration information of CSI reporting from the base station. In other words, the base station can control CSI reporting of the terminal or MT. A relay station can support some or all of the functions of a base station. A relay station can include an eNB, gNB, a base station, an IAB node, an IAB-DU (distributed unit), an IAB-MT (mobile terminal), a repeater, etc. Alternatively, another term may be used instead of a relay station.

[0135] The terminal may refer to a UE including a mobile equipment (ME) and a USIM (universal mobile telecommunication system (UMTS) subscriber identity module), an ME including an MT and terminal equipment (TE), an MT supporting mobile communication functions, etc. Alternatively, another term may be used instead of the terminal. The CSI may include at least one of a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), an SS / PBCH block resource indicator (SSBRI), a layer indicator (LI), a rank indicator (RI), a layer-1 reference resource received power (L1-RSRP), or a layer-1 signal-to-noise and interference ratio (L1-SINR). A terminal may receive from a base station via signaling (e.g., higher layer signaling) N report configurations (e.g., CSI-ReportConfig), M resource configurations (e.g., CSI-ResourceConfig), and / or a trigger configuration including a list of one or more trigger states (e.g., CSI-AperiodicTriggerStateList or CSI-SemiPersistentOnPUSCH-TriggerStateList) for CSI reporting. Each of N and M may be a natural number.

[0136] Each report configuration (e.g., CSI-ReportConfig) may include one or more parameters (e.g., one or more upper layer parameters) defined in Tables 4 through 6 below.

[0137]

[0138]

[0139]

[0140] Each resource configuration (e.g., CSI-ResourceConfig) may include one or more parameters (e.g., one or more upper layer parameters) defined in Tables 7 through 9 below.

[0141]

[0142]

[0143]

[0144] A trigger configuration (e.g., CSI-AperiodicTriggerStateList or CSI-SemiPersistentOnPUSCH-TriggerStateList) may include one or more parameters (e.g., one or more upper layer parameters) defined in Tables 10 and 11 below.

[0145]

[0146]

[0147] The base station may configure the terminal to derive the CQI based on one of the tables 12 to 15 below. In other words, the base station may instruct (e.g., configure) the terminal to use one of the tables 12 to 15 below through signaling. The terminal may derive the CQI based on one of the tables 12 to 15 below based on the configuration of the base station.

[0148]

[0149]

[0150]

[0151]

[0152] A combination of a modulation scheme and a transport block size that satisfies one or more of the conditions below may correspond to one CQI index among the CQI indices in Tables 12 to 15.

[0153] - Condition 1: Combination of modulation method and transport block size (TBS) for PDSCH transmission within CSI reference resource

[0154] - Condition 2: Modulation method is indicated by CQI index

[0155] - Condition 3: When a combination of modulation scheme and TBS is applied to a reference resource (e.g., a CSI reference resource), if the effective channel code rate determined based on the combination of modulation scheme and TBS is closest to the code rate indicated by the CQI index, only the combination consisting of the smallest TBS among the combinations of modulation scheme and TBS is valid.

[0156] If the upper layer parameter timeRestrictionForChannelMeasurements in the reporting configuration is set to notConfigured, the time-domain measurement restriction may not be applied to the channel measurement resource (CMR) of the reporting configuration. In the above-described situation, when the terminal performs channel measurement for calculating CSI (e.g., a CSI value) reported in slot n (e.g., uplink slot n), the terminal may determine (e.g., calculate, derive, derive) the CSI by considering CSI reference resource(s) among the NZP (non-zero power) CSI-RS resource(s) included in the CMR and / or NZP CSI-RS resource(s) located before the resource (e.g., the NZP CSI-RS resource(s) or the CSI reference resource(s)).

[0157] When the upper layer parameter timeRestrictionForChannelMeasurements in the reporting configuration is set to Configured, the time domain measurement restriction may be applied to the CMR of the reporting configuration. In the above situation, when the terminal performs channel measurement for calculating CSI (e.g., a CSI value) reported in slot n (e.g., uplink slot n), the terminal may determine (e.g., calculate, derive, derive) the CSI by considering CSI reference resource(s) among the NZP CSI-RS resource(s) included in the CMR and / or the most recent NZP CSI-RS resource(s) located before the resource (e.g., the NZP CSI-RS resource(s) or the CSI reference resource(s)).

[0158] If the upper layer parameter timeRestrictionForChannelMeasurements in the reporting configuration is set to notConfigured, the time domain measurement restriction may not be applied to the interference measurement resource (IMR) of the reporting configuration. In the above situation, when the terminal performs interference measurement for calculating CSI (e.g., CSI value) reported in slot n (e.g., uplink slot n), the terminal may determine (e.g., calculate, derive, derive) the CSI by considering "CSI reference resource(s) among the CSI-IM resource(s) and / or NZP CSI-RS resource(s) included in the IMR" and / or "resource(s) located before the resource (e.g., IMR, CSI-IM resource(s), NZP CSI-RS resource(s), or CSI reference resource(s))".

[0159] When the upper layer parameter timeRestrictionForChannelMeasurements in the reporting configuration is set to Configured, the time domain measurement restriction may be applied to the IMR of the reporting configuration. In the above situation, when the terminal performs interference measurement for calculating CSI (e.g., a CSI value) reported in slot n (e.g., uplink slot n), the terminal may determine (e.g., calculate, derive, derive) the CSI by considering "CSI reference resource(s) among the CSI-IM resource(s) and / or NZP CSI-RS resource(s) included in the IMR" and / or "the most recent resource(s) located before the resource (e.g., the IMR, the CSI-IM resource(s), the NZP CSI-RS resource(s), or the CSI reference resource(s))". The most recent resource may mean the most recent occasion.

[0160] In a serving cell, CSI reference resources can be defined as follows:

[0161] - In the frequency domain, a CSI reference resource can be defined as a group of downlink PRBs in a band associated with the derived CSI (e.g., the determined CSI).

[0162] - In the time domain, the CSI reference resource for CSI reported in slot n (e.g., uplink slot n) can be defined as the downlink slot in the following mathematical expression 8.

[0163]

[0164] n in equation 8 CSI_ref , K offset , and can be set (e.g., instructed) to the terminal through signaling of the base station (e.g., upper layer signaling, RRC signaling, MAC CE signaling). The terminal can check the above-described parameter(s) through signaling of the base station. Alternatively, the base station and / or the terminal can set n based on preset rules. CSI_ref , K offset , and can be determined (e.g., derived, deduced). For example, the base station is K offset The RRC settings and / or MAC CE including the above can be transmitted to the terminal.

[0165] When a single CSI-RS resource or a single SSB resource is set as CMR for periodic CSI reporting or semi-persistent CSI reporting, the terminal shall n CSI_ref 4· Among the integers above, the minimum value indicating a valid uplink slot can be determined. When multiple CSI-RS resources or multiple SSB resources are set to CMR for periodic CSI reporting or semi-persistent CSI reporting, the terminal may set n CSI_ref 5· Among the integers above, the minimum value indicating a valid uplink slot can be determined.

[0166] For aperiodic CSI reporting, which is instructed to be transmitted in the same slot in which a CSI request based on DCI is received, the terminal determines that the slot in which the CSI request is received is a valid downlink slot. CSI_ref For aperiodic CSI reports other than the aperiodic CSI reports described above, the terminal determines the smallest integer n that satisfies a separately defined delay requirement (Z'). CSI_ref can be determined. The terminal can perform channel measurement or interference measurement based on periodic or semi-persistent CSI-RS / CSI-IM / SSB, and transmit an aperiodic CSI report to the base station based on the result of the channel measurement or the interference measurement. In the above-described situation, if the last symbol (e.g., the last OFDM symbol) of the periodic or semi-persistent CSI-RS / CSI-IM / SSB resource is within the delay requirement (Z') based on the first symbol (e.g., the first OFDM symbol) on which the aperiodic CSI report is transmitted, the terminal may not perform a measurement operation for the periodic or semi-persistent CSI-RS / CSI-IM / SSB resource. In other words, if the number of symbols belonging to the interval from the last symbol of the periodic or semi-persistent CSI-RS / CSI-IM / SSB resource to the first symbol in which an aperiodic CSI report is transmitted is not greater than Z' symbols, the terminal may not perform a measurement operation for the periodic or semi-persistent CSI-RS / CSI-IM / SSB resource. Z' may be a natural number.

[0167] A slot satisfying the condition(s) within a serving cell may be considered (e.g., deemed, determined) as a valid downlink slot. If there is no valid downlink slot for the CSI reference resource of the CSI reporting configuration within the serving cell, the UE may omit CSI reporting for the serving cell in slot n' (e.g., uplink slot n').

[0168] If the terminal is configured to report CQI, the terminal may assume the following item(s) to derive (e.g., derive, determine) the CQI, RI, and / or PMI within the CSI reference resource. Alternatively, the item(s) for deriving (e.g., derive, determine) the CQI, RI, and / or PMI may not be limited to the following item(s).

[0169] □ Item 1: The first two symbols (e.g., the first two OFDM symbols) are used to transmit control signals.

[0170] □ Item 2: The number of symbols for PDSCH and DMRS is 12.

[0171] □ Item 3: BWP, SCS, and / or CP lengths equal to the BWP, SCS (subcarrier spacing), and / or CP lengths set for PDSCH reception.

[0172] □ Item 4: Same bandwidth as the bandwidth set for CQI reporting

[0173] □ Item 5: No RE usage for SSB, NZP CSI-RS, and / or ZP CSI-RS

[0174] □ Item 6: RV (redundancy version) 0

[0175] □ Item 7: The ratio between PDSCH EPRE (energy per resource element) and CSI-RS EPRE is based on the upper layer setting value (e.g., Pc, powerControlOffset).

[0176] □ Item 8: For DMRS patterns, maxLength and / or dmrs-AdditionalPosition in DMRS-DownlinkConfig are referenced.

[0177] □ Item 9: DMRS does not exist within the PDSCH symbol.

[0178] □ Item 10: The size of PRB bundling is assumed to be 2 PRBs.

[0179] □ Item 11: The PDSCH signal transmitted at the PDSCH antenna ports [1000, ..., 1000+v-1] for v layers satisfies the relationship of Equation 9 with the signal transmitted at the CSI-RS antenna ports [3000, ..., 3000+P-1]. W(i) is the precoding matrix indicated by the PMI (e.g., precoding matrix0,P) and is the number of CSI-RS ports in the CSI-RS resource. v and P are each natural numbers.

[0180] Each CSI report may have a priority (e.g., a priority value) based on the rule(s) described in Tables 16 to 18 below. A lower value may have a higher priority, and a higher value may have a lower priority. If different CSI reports collide, the different CSI reports may be merged into a single CSI report according to the configuration of the base station. Alternatively, one CSI report may be selected from among the different CSI reports, and the remaining CSI reports may be dropped. In the CSI report selection process, the CSI content may be adjusted according to the CSI payload with reference to the priority value. In the CSI report selection process, a CSI report may be selected based on the priority value.

[0181]

[0182]

[0183]

[0184] A terminal can transmit a terminal capability report (e.g., a UE capability report) to a base station. The base station can receive the terminal capability report from the terminal. The terminal capability information can include the maximum number of CSI calculations that the terminal can perform simultaneously.

[0185] When L CPUs (CSI processing units) in a terminal are occupied and the terminal starts calculating N CSI reports, the terminal may not perform updates on NM lower CSI reports having lower priorities based on the priority description. The state in which L CPUs are occupied may mean a state in which L CPUs are used for calculating CSI reports. L, N, and M may each be a natural number. M may be the largest positive number among values ​​that satisfy the following mathematical expression 9 and are greater than or equal to 0 and less than or equal to N. may be the number of CPUs used for the nth CSI calculation.

[0186]

[0187] The number of CPUs required for each CSI report can be determined based on Tables 19 to 23 below.

[0188]

[0189]

[0190]

[0191]

[0192]

[0193] Various factors including the elements below can be assumed to have specific values, and the CSI reported in slot n (e.g., uplink slot n) can be derived (or determined, derived) based on the assumptions. Alternatively, the CSI reported in slot n can be determined by considering the specific values. In the present disclosure, the elements assumed by the terminal to generate CSI can be referred to as CSI components. CSI components can be defined as shown in Table 24 below. CSI components may not be limited to the elements listed in Table 24 below. In other words, CSI components can include various elements other than the elements listed in Table 24 below.

[0194]

[0195] A communication system (e.g., an LTE communication system, a NR communication system, a 6G communication system) may include different types of terminals capable of transmitting and receiving various types of wireless signals. A terminal may report its capabilities (e.g., capability characteristics) to a base station based on an initial access procedure (e.g., an IA (Initial Access) procedure) and / or a terminal capability reporting procedure. The base station may receive information about the capabilities of the terminal from the terminal.

[0196] In a communication system (e.g., an LTE communication system, a NR communication system, a 6G communication system), a terminal may transmit information indicating that the terminal is a low-end terminal (e.g., a RedCap (reduced capability) UE) to a base station during at least one of an initial access procedure or a terminal capability reporting procedure. The base station may confirm the type of the terminal (e.g., a low-end terminal) based on the information received from the terminal.

[0197] Low-end terminals may include HD (half-duplex) FDD terminals that do not support simultaneous operation for UL communication (e.g., UL transmission) and DL communication (e.g., DL reception) in a paired spectrum of a communication system supporting FDD (frequency division duplex).

[0198] When uplink transmission is allocated to uplink frequency resources and downlink reception is allocated to downlink frequency resources within the same time interval, an HD-FDD terminal (e.g., a low-performance terminal) can determine an operation to be performed by the HD-FDD terminal and an operation not to be performed by the HD-FDD terminal based on a priority rule.

[0199] When the operation of an HD-FDD terminal changes from an uplink transmission operation to a downlink reception operation or when the operation of an HD-FDD terminal changes from a downlink reception operation to an uplink transmission operation, a guard period (GP) may be applied in the time resources between the operations to allow for a change (e.g., switching) between the operations.

[0200] Figure 10a is a conceptual diagram illustrating embodiments of HD GP (half-duplex guard period) according to terminal capabilities.

[0201] Referring to FIG. 10A, a GP (e.g., HD GP) may be configured with one or more OFDM symbols (e.g., within a period of several microseconds, within a period of several tens of microseconds) based on the capabilities of the terminal. In FIG. 10A, the GP may be a Type A HD-FDD GP.

[0202] Figure 10b is a conceptual diagram illustrating embodiments of HD GP according to terminal capabilities.

[0203] Referring to FIG. 10b, a GP (e.g., HD GP) may be configured with one or more slots (e.g., a period within several milliseconds, a period within tens of milliseconds) based on the capabilities of the terminal. In FIG. 10b, the GP may be a Type B HD-FDD GP.

[0204] Within a time interval corresponding to GP, it can be ensured that the terminal (1010) does not perform an uplink transmission operation to the base station (1020) and / or a downlink reception operation to the base station (1020).

[0205] A method for determining UL / DL operations for an HD-FDD terminal supported by a communication system may be based on Tables 25 to 28 below. The method for determining UL / DL operations for an HD-FDD terminal may not be limited to the embodiments defined in Tables 25 to 28 below. According to the method for determining UL / DL operations, one operation may be selected from an uplink transmission operation (e.g., UL communication) and a downlink reception operation (e.g., DL communication). The UL / DL operations for an HD-FDD terminal may be determined based on an HD-FDD priority rule. In the present disclosure, an HD-FDD terminal may be referred to as an HD terminal or an HD UE for convenience. The HD-FDD priority rule may be referred to as an HD priority rule. Alternatively, the HD-FDD priority rule may be referred to as a priority rule for convenience.

[0206] An HD terminal may not be able to simultaneously perform uplink transmission and downlink reception operations in a paired spectrum within a serving cell. The HD terminal may predict downlink reception in a symbol set and may not perform an uplink transmission operation in the symbol set. The symbol set may include one or more symbols. For example, the HD terminal may receive at least one of a PDCCH, a PDSCH, a CSI-RS, or a DL-PRS (positioning reference signal) in a symbol set configured by higher layer parameter(s). In other words, the symbol set for the downlink reception operation may be configured for the terminal based on higher layer signaling of the base station (e.g., higher layer parameter(s)). If transmission of at least one of a PUCCH, a PUSCH, a PRACH, or an SRS within the symbol set is not instructed to the HD terminal based on the DCI, the terminal may receive a downlink signal / channel within the symbol set. If at least one transmission among PUCCH, PUSCH, PRACH, or SRS within a symbol set is instructed to the HD terminal based on the DCI, the terminal may not receive a downlink signal / channel within the symbol set.

[0207] Higher layer signaling (e.g., higher layer parameter(s)) of the base station can configure the HD terminal to perform an uplink transmission operation in a symbol set. If a DCI indicating reception of a downlink signal / channel in a symbol set is not received, the HD terminal can perform an uplink transmission operation in the symbol set.

[0208] The first symbol of the symbol set is a preset time (e.g., T) from the last symbol of the PDCCH reception (e.g., DCI reception). proc,2) occurs within the preset time (e.g., T), the HD terminal may not cancel the uplink transmission in the symbol set. proc,2 ) can be determined based on the processing capability of the HD terminal. Or, a preset time (e.g., T proc,2 ) may be determined based on “factors other than the processing capability of the HD terminal” or “factors other than the processing capability of the HD terminal and other factors.”

[0209] The HD terminal may select one operation from among the uplink transmission operation and the downlink reception operation based on Tables 25 to 28 below. The operation of the HD terminal may not be limited to the embodiments specified in Tables 25 to 28 below.

[0210]

[0211]

[0212]

[0213]

[0214] In Tables 25 to 28, the transition times (e.g., N Tx-Rx and N Rx-Tx ) can be set for each frequency range (e.g., FR1 (frequency range 1) or FR2 (frequency range 2)). The transition time can be defined as shown in Table 29 below.

[0215]

[0216] In a communication system supporting at least one of carrier aggregation (CA), dual connectivity (DC), or multi-connectivity (MC), a method for determining multi-carrier transmission and reception operations for a terminal that does not support simultaneous transmission and reception operations may be supported. The simultaneous transmission and reception operations may mean operations of simultaneously performing uplink communication and downlink communication in the same time interval. The multi-carrier transmission and reception operations may be determined based on a multi-carrier priority rule. Table 30 below may define a guard period (GP) for an HD terminal supporting HD-FDD, HD-CA, and / or HD-DC. The GP may not be limited to the embodiments described in Table 30 below. The GP may be N defined in Table 29. Tx-Rx Or N Rx-Tx It can be determined based on at least one of the following.

[0217]

[0218] An uplink priority, a downlink priority, and / or a GP for an HD terminal that does not support simultaneous transmission and reception operations in a communication system may be determined. The uplink priority, the downlink priority, and / or the GP for the HD terminal may be determined based on the embodiments specified in Tables 25 to 30. The embodiments of Tables 25 to 30 may not take into account an NTN environment. In other words, Tables 25 to 30 may specify a method for determining an uplink priority, a downlink priority, and / or a GP for an HD terminal that does not take into account an NTN environment.

[0219] Satellite-based communications can be performed in NTN, and long propagation delays may exist in NTN. Scheduling offsets, TAs, PDSCH / PUSCH / CSI processing times, and / or other components may vary in NTN environments. Methods for supporting HD terminals performing uplink and downlink communications in NTN environments may be necessary. When HD terminals determine uplink priorities, downlink priorities, and / or GPs in NTN environments, the components of the NTN environment need to be taken into consideration.

[0220] In this disclosure, a terminal that does not support simultaneous transmission and reception may be referred to as an HD terminal. Alternatively, a terminal that cannot perform simultaneous transmission and reception may be referred to by a different term. Embodiments of this disclosure can be applied identically or similarly to terminals that support simultaneous transmission and reception.

[0221] A method for determining DL-UL collision resources for HD-FDD terminals in an NTN environment

[0222] As described above, the terminal can determine the TA value actually used by the terminal based on at least one of terminal location information, NTN payload location information, NTN payload configuration information, NTN gateway location information, NTN gateway configuration information, reference point (RP) configuration information, common TA configuration information, or dedicated TA configuration information acquired by the terminal.

[0223] The base station can set ephemeris information including orbital information of the NTN payload and / or common TA information for compensating for propagation delay from the NTN payload to an RP within a feeder link to the terminal through higher layer signaling (e.g., SIB19, etc.). In other words, the base station can transmit NTN payload configuration information (e.g., ephemeris information) and / or common TA configuration information to the terminal. The terminal can receive NTN payload configuration information (e.g., ephemeris information) and / or common TA configuration information through signaling from the base station. The RP can mean a point where UL timing (e.g., UL frame timing, UL slot timing, UL symbol timing) and DL timing (e.g., DL frame timing, DL slot timing, DL symbol timing) match.

[0224] The base station may configure the terminal to calculate TA values ​​for some or all of the feeder links based on the configuration information described above. In other words, the terminal may calculate TA values ​​for some or all of the feeder links based on the configuration information received from the base station. The base station may configure the upper layer parameters TA_Common, TA_CommonDrift, TA_CommonDriftVariant, and / or t_epoch to the terminal. The terminal may determine the one-way propagation delay at time t based on the upper layer parameters configured by the base station. The terminal may calculate the one-way propagation delay based on the following mathematical expression 10.

[0225]

[0226] The terminal is a quantization value for two-way transmission delay based on one-way propagation delay. can be determined. The time unit for quantization for bidirectional transmission delay is T c It can be. For example, the terminal can determine the TA value. The relationship that most closely satisfies can be calculated.

[0227] The terminal can determine (e.g., calculate) a propagation path or slant range for a service link between the terminal and the NTN payload based on the terminal's location information acquired from the GNSS and the NTN payload orbit information and / or ephemeris information acquired by the base station settings. The terminal can determine (e.g., calculate) a TA value (e.g., a terminal-specific TA,) for service link propagation delay compensation based on the propagation path and / or slant range. ) can be calculated.

[0228] The terminal is and Based on the TA value (T) in Equation 4 and / or Equation 5 TA ) can be determined. The TA value may mean a TA value actually used by the terminal in the NTN system (e.g., transparent NTN payload, bent-pipe NTN payload) illustrated in Fig. 9a.

[0229] In the NTN system illustrated in Fig. 9 (e.g., regenerated NTN payload, on-board processing (OBP), on-board gNB, on-board RU / DU), the location of the NTN payload and the location of the RP can be set to be the same. Therefore, may be 0. In this case, the terminal is calculated similarly to the method described above. Based on the TA value (T) in Equation 4 and / or Equation 5 TA) can be determined. The TA value may be a TA value actually used by the terminal in the NTN system (e.g., NTN structure) illustrated in Fig. 9b. The TA value actually used by the terminal can be determined in various ways based on the NTN environment, such as the NTN structure (e.g., NTN system), NTN payload type, etc.

[0230] The base station can estimate the TA value assumed by the base station based on terminal location information, NTN payload location information, NTN payload configuration information, NTN gateway location information, NTN gateway configuration information, reference point configuration information, and / or MAC CE-based TA report information obtained from the base station. The MAC CE-based TA report can be transmitted by the terminal.

[0231] The TA value assumed by the base station and the TA value actually used by the terminal may have different values ​​due to errors based on location information, configuration information, and / or reporting information. Therefore, the TA discrepancy value, which is the difference between the two TA values, may not be 0. Since the TA reporting based on MAC CE has a minimum resolution of 1 ms, if the TA value actually used by the terminal has a precision of less than 1 ms, the TA reporting based on MAC CE may not accurately reflect the TA value actually used by the terminal.

[0232] For terminals that do not support TA reporting, the base station may assume the difference between the TA minimum value and the TA maximum value, which are determined based on the NTN payload beam and / or cell radius supported by the terminal, as the TA mismatch value. If the base station conservatively reflects the TA mismatch value, the base station may not accurately assume the TA mismatch value. Even in this case, the above-described operation may be performed to ensure that there is no problem with NTN propagation delay compensation based on k_offset and / or k_mac.

[0233] The difference in the above configuration information may be the difference between UL SCS (subcarrier spacing) (e.g., UL numerology) and DL SCS (e.g., DL numerology). For example, if 15 kHz SCS is applied in uplink communication and 30 kHz SCS is applied in downlink communication, the uplink slot period determined based on the terminal's TA report (e.g., TA report based on MAC CE) may overlap with the time period occupied by one or more downlink slots. Therefore, ambiguity may occur in the determination of the DL-UL collision period.

[0234] Figure 11 is a conceptual diagram illustrating the TA mismatch value between a terminal and a base station.

[0235] Referring to FIG. 11, the downlink timing and the uplink timing in the RP can be aligned so that the slot boundary of the downlink (or the frame boundary of the downlink, the subframe boundary of the downlink) matches the slot boundary of the uplink (or the frame boundary of the uplink, the subframe boundary of the uplink). The base station can perform scheduling so that the downlink channel / signal (11-00) and the uplink channel / signal (11-05) allocated in consideration of the HD terminal do not collide with each other at least in the RP. The downlink channel / signal may mean a downlink channel and / or signal. The uplink channel / signal may mean an uplink channel and / or signal. If the TA reported by the terminal corresponds to two slots due to a delay in TA reporting, etc., and the TA actually applied by the terminal corresponds to four slots, the DL-UL collision resources (11-10) assumed by the base station may be DL#4 and UL#6, but the actual DL-UL collision resources (11-15) at the terminal may be DL#2 and UL#6. The different understanding of DL-UL collisions (e.g., DL-UL collision resources) between the base station and the terminal may be a factor that deteriorates the wireless communication performance of the HD terminal. Therefore, a method for unifying the understanding of DL-UL collisions (e.g., DL-UL collision resources) between the base station and the terminal may be necessary.

[0236] Figure 12 is a conceptual diagram illustrating the TA mismatch value between a terminal and a base station.

[0237] Referring to FIG. 12, the downlink timing and the uplink timing in the RP can be aligned so that the slot boundary of the downlink (or the frame boundary of the downlink, the subframe boundary of the downlink) matches the slot boundary of the uplink (or the frame boundary of the uplink, the subframe boundary of the uplink). The base station can perform scheduling such that the allocated downlink channel / signal (12-00) and uplink channel / signal (12-05) do not collide with each other at least in the RP, taking into account the HD terminal. The base station can set the UL SCS (e.g., 15 kHz SCS) to be smaller than the DL SCS (e.g., 30 kHz SCS). In this case, one uplink time resource (e.g., a slot) can include multiple downlink time resources (e.g., multiple slots), and a DL-UL collision (e.g., a DL-UL collision resource) can be defined between one uplink resource and multiple downlink resources. If the TA reported by the terminal corresponds to one slot (e.g., one UL slot) due to a delay in TA reporting, etc., and the TA actually applied by the terminal corresponds to two slots (e.g., two UL slots), the DL-UL collision (12-10) assumed by the base station may be a collision between {DL#4, DL#5} and UL#3, but the actual DL-UL collision (12-15) at the terminal may be a collision between {DL#2, DL#3} and UL#3. The different understanding of DL-UL collision (e.g., DL-UL collision resources) between the base station and the terminal may be a factor that degrades the wireless communication performance of the HD terminal. Therefore, a method for unifying the understanding of DL-UL collision (e.g., DL-UL collision resources) between the base station and the terminal may be necessary.

[0238] Figure 13 is a conceptual diagram illustrating the TA mismatch value between a terminal and a base station.

[0239] Referring to FIG. 13, the downlink timing and the uplink timing in the RP can be aligned so that the slot boundary of the downlink (or the frame boundary of the downlink, the subframe boundary of the downlink) matches the slot boundary of the uplink (or the frame boundary of the uplink, the subframe boundary of the uplink). The base station can perform scheduling such that the allocated downlink channel / signal (13-00) and uplink channel / signal (13-05) do not collide with each other at least in the RP, taking into account the HD terminal. The base station can set the DL SCS (e.g., 15 kHz SCS) to be smaller than the UL SCS (e.g., 30 kHz SCS). In this case, one downlink time resource (e.g., a slot) can include multiple uplink time resources (e.g., multiple slots), and a DL-UL collision (e.g., a DL-UL collision resource) can be defined between one uplink resource and a part of a certain downlink resource. If the TA reported by the terminal corresponds to two slots (e.g., two UL slots) due to a delay in TA reporting, etc., and the TA actually applied by the terminal corresponds to four slots (e.g., four UL slots), there is no DL-UL collision assumed by the base station, but the DL-UL collision (13-10) assumed by the terminal may be a collision between the front part of DL#1 and UL#6. The validity / effectiveness of the DL-UL collision (13-15) between the rear part of DL#1 and UL#7, which is not an uplink transmission resource actually allocated to the terminal, may be determined based on upper layer configuration, MAC CE indication, DCI indication, and / or predefined specifications. Different understandings between the base station and the terminal regarding DL-UL collision (e.g., DL-UL collision resources) may be a factor that degrades the wireless communication performance of the HD terminal. Therefore, a method may be needed to unify the base station and terminal's understanding of DL-UL collisions (e.g., DL-UL collision resources).

[0240] The method of defining DL-UL collisions described with reference to FIGS. 11, 12, and / or 13 may not be applicable only to the same DL-UL SCS relationship as the embodiment of FIGS. 11, 12, and / or 13. The methods of defining DL-UL collisions may be interchangeable.

[0241] Based on Equation 4 and / or Equation 5, the relationship between the TA value assumed by the base station and the TA value actually used by the terminal may not be an integer multiple of a time resource unit (e.g., frame, subframe, slot, symbol). In the present disclosure, TA may mean a TA value. In other words, TA and TA value may be used interchangeably.

[0242] If the relationship between the TA value assumed by the base station and the TA value actually used by the terminal does not have an integer multiple of a time resource unit (e.g., a frame, a subframe, a slot, a symbol), the uplink resources and / or the downlink resources may be indicated (e.g., configured) by signaling (e.g., higher layer signaling, MAC CE signaling, and / or DCI signaling) or defined in a technical specification, such that a downlink reception that collides with an uplink transmission means all downlink receptions received in time resources that overlap part or all of the time resources occupied by the uplink transmission. The unit of the time resource overlapping between the uplink resources and the downlink resources may be interpreted as having the same length as the time resource occupied by the uplink channel and / or signal allocated for the uplink transmission. The unit of the overlapping time resource may be a frame, a subframe, a slot, or a symbol. Alternatively, the unit of the overlapping time resource may be determined based on other configuration values ​​such as a subcarrier spacing, numerology (SCS).

[0243] If the relationship between the TA value assumed by the base station and the TA value actually used by the terminal does not have an integer multiple of a time resource unit (e.g., a frame, a subframe, a slot, a symbol), the uplink resources and / or the downlink resources may be indicated (e.g., configured) by signaling (e.g., higher layer signaling, MAC CE signaling, and / or DCI signaling) or defined in a technical specification, such that an uplink reception that collides with a downlink transmission means all uplink receptions carried in time resources that overlap part or all of the time resources occupied by the downlink transmission. The unit of the time resource overlapping between the uplink resources and the downlink resources may be interpreted as having the same length as the time resource occupied by the downlink channel and / or signal allocated for the downlink transmission. The unit of the overlapping time resource may be a frame, a subframe, a slot, or a symbol. Alternatively, the unit of the overlapping time resource may be determined based on other configuration values ​​such as the SCS.

[0244] The terminal may perform an operation of selecting one of uplink transmission and downlink reception based on a method of distinguishing downlink reception from uplink transmission conflicts and / or a method of distinguishing uplink reception from downlink transmission conflicts. In other words, the terminal may select one of uplink transmission and downlink reception based on a definition of DL-UL collision.

[0245] In an environment where TA mismatch occurs, a method for determining DL-UL collision time resources (e.g., DL-UL collision duration) may be required. To determine DL-UL collision time resources, the base station and / or terminal may apply at least one of the following methods.

[0246] ·Method 1-1

[0247] Method 1-1 can be performed based on upper layer settings (e.g., TA_Common, TA_CommonDrift, TA_CommonDriftVariant, t_epoch) and / or SI signaling (e.g., SIB19 signaling). It can be configured (e.g., indicated, defined) that the terminal determines a collision resource based on a representative value (e.g., a maximum value, an average value, etc.) among TA values ​​derived based on TA_common-related signaling(s) (e.g., TA values ​​applied to Equation 8). The terminal determines a TA_UE (e.g., ) It may be configured (e.g., indicated, defined) to determine a collision resource based on a representative value (e.g., a maximum value, an average value, etc.) among TA values ​​derived based on TA_common related signaling(s) and / or TA_UE related signaling(s). It may be configured (e.g., indicated, defined) to determine a collision resource based on a representative value (e.g., a maximum value, an average value, etc.) among TA values ​​derived based on TA_common related signaling(s) and / or TA_UE related signaling(s) (e.g., TA values ​​applied to Equation 4 and / or Equation 5). In order to maintain the accuracy of the representative value, the representative value may be limited to be determined within a valid interval of a setting value such as SIB19 (e.g., a value set by a base station) and / or location information acquired by the terminal.

[0248] Method 1-2

[0249] Methods 1-2 may be based on higher layer configuration and / or new signaling. The base station may signal to the terminal information on the time interval to be considered in addition to the TA value actually applied by the terminal in the DL-UL collision resource determination procedure. Alternatively, in the case of a regenerated NTN payload, the network may signal to the regenerated NTN payload information on the time interval to be considered in addition to the TA value actually applied by the terminal in the DL-UL collision resource determination procedure. For example, the base station may signal a pair of (x, y) values ​​to the terminal. In this case, the terminal may apply a collision rule considering that ambiguity may occur in the determination of the DL-UL collision resource at the base station during the time from TA_real - x to TA_real + y based on TA_real, which is the TA value actually used by the terminal. To support the above-described operation, priorities between collision rules for various types of DL-UL collisions may be additionally defined. For example, in the case where various types of DL-UL collisions exist in the above-described time interval, the collision rules may be applied in the following order: "Case 3: Collision between semi-static uplink communication and semi-static downlink communication" > "Case 4: Collision between dynamic uplink communication and dynamic downlink communication" > "Other: For example, collision between semi-static uplink communication (or semi-static downlink communication) and dynamic downlink communication (or dynamic uplink communication)".

[0250] The terminal may collectively apply the above results (e.g., the results of applying the collision rules) to the above-described time interval. To support the above-described operation, it may be configured (e.g., instructed, defined) that the terminal maintains, without change, the uplink transmission and / or downlink reception that was most recently determined to be performed without being canceled (e.g., not performed) during the above-described time interval (e.g., the time interval during which ambiguity in determining DL-UL collision resources occurs). The above-described embodiment may mean that a collision rule that causes an operation other than the uplink transmission and / or downlink reception determined during the above-described time interval is ignored. Uplink communication at a base station may mean uplink reception, and uplink communication at a terminal may mean uplink transmission. Downlink communication at a base station may mean downlink transmission, and downlink communication at a terminal may mean downlink reception.

[0251] ·Method 1-3

[0252] Methods 1-3 can be performed by considering an NTN relay (e.g., uplink communication from an NTN relay). Due to the NTN structure, the TA mismatch between the base station and the terminal may increase. In the embodiments of FIG. 9c and / or FIG. 9d, a relay (e.g., a relay node) may exist between the terminal and the NTN payload, and the relay may perform transparent operation to either the terminal or the base station. In this case, either the terminal or the base station may not be aware of the presence of the relay node. Therefore, the TA (e.g., TA value) at the terminal or the base station may include the additional delay caused by the relay (e.g., relay processing / group delay). However, since the TA at the terminal or the base station does not reflect the additional delay caused by the relay, the TA mismatch between the terminal and the base station may further increase. To address the above-described issue, if a relay exists between the terminal and the NTN payload, the base station may configure and / or instruct the terminal to "reflect the additional delay due to the relay in the TA determination procedure" or "reflect the additional delay due to the relay in the DL-UL collision resource determination procedure." "Reflecting the additional delay due to the relay in the DL-UL collision resource determination procedure" may mean "assuming the time interval of the DL-UL collision resource to be longer."

[0253] Figure 14 is a conceptual diagram illustrating a TA determination method.

[0254] Referring to FIG. 14, a terminal may be connected to at least one NTN including a relay node (e.g., a repeater). In an NTN including a relay node, it may be configured (e.g., indicated, defined) that the terminal uses Equation 11 below instead of Equation 4 and / or Equation 5 to determine a TA for uplink transmission.

[0255]

[0256] can be determined based on the characteristics of the relay node. Or can be a natural number greater than 0 determined by the network settings / instructions.

[0257] How to control whether the DL-UL collision rule applies

[0258] In addition to the uplink and downlink priorities and GP determination methods for the HD terminal defined in the above-described tables, a conflict rule (e.g., a priority rule) for selecting one operation between uplink transmission and downlink reception may be defined in "Case 3: Conflict between quasi-static uplink communication and quasi-static downlink communication" and "Case 4: Conflict between dynamic uplink communication and dynamic downlink communication." In Case 3, the terminal may receive a configuration (e.g., configuration information) of the quasi-static uplink communication and a configuration (e.g., configuration information) of the quasi-static downlink communication from the base station through signaling (e.g., higher layer signaling), and the uplink communication and the downlink communication may be performed in different frequency bands, and the uplink communication and the downlink communication may overlap (e.g., collide) in at least one symbol, and the terminal and / or the base station may expect to perform one of the uplink communication and the downlink communication based on the conflict rule.

[0259] In case 4, the terminal can receive scheduling / indication information of dynamic uplink communication and scheduling / indication information of dynamic downlink communication from the base station through signaling (e.g., DCI signaling, MAC CE signaling), and the uplink communication and the downlink communication can be performed in different frequency bands, and the uplink communication and the downlink communication can overlap (e.g., collide) in at least one symbol, and the terminal and / or the base station can expect to perform one of the uplink communication and the downlink communication based on a collision rule. The scheduling / indication information of the dynamic uplink communication can be referred to as a configuration (e.g., configuration information) of the dynamic uplink communication, and the scheduling / indication information of the dynamic downlink communication can be referred to as a configuration (e.g., configuration information) of the dynamic downlink communication.

[0260] A collision rule may refer to a priority rule. An HD terminal may operate in an NTN serving cell. The state of the HD terminal may be an RRC connected state or an RRC inactive state. Embodiments of the present disclosure may be applied to collisions between uplink communication in various ways (e.g., semi-static or dynamic) and downlink communication in various ways (e.g., dynamic or semi-static) as well as Case 3 and / or Case 4. Since not all terminals may support the new collision rule, it may be desirable to prevent the new collision rule from being applied in a specific time period and / or a specific NTN cell. To support the above-described operation, at least one of the following methods may be applied.

[0261] Method 2-1

[0262] Whether a conflict rule applies to Case 3 and / or Case 4 may be determined based on UE capability reports (e.g., terminal capabilities). The terminal may have the capability to handle conflicts between uplink and downlink communications. In this case, the terminal may select one of uplink transmission and downlink reception based on the conflict rule and perform the selected action (e.g., uplink transmission or downlink reception). The conflict rule may be a priority rule. For example, if the priority of uplink transmission is higher than that of downlink reception, the terminal may select uplink transmission and perform the selected uplink transmission. In this case, the base station may expect the terminal to perform uplink transmission. Alternatively, if the priority of uplink transmission is lower than that of downlink reception, the terminal may select downlink reception and perform the selected downlink reception. In this case, the base station may expect the terminal to perform downlink reception. The terminal may not have the capability to handle conflicts between uplink and downlink communications. In this case, the terminal may not be able to select either uplink transmission or downlink reception, and thus may not be able to perform both uplink transmission and downlink reception.

[0263] ·Method 2-2

[0264] The base station may determine whether to apply the collision rules for Case 3 and / or Case 4 based on separate upper layer settings for each terminal, each NTN frequency band, and / or each NTN cell. The base station may refer to the UE capability report (e.g., the UE capability report in Method 2-1) for the above settings.

[0265] For example, a terminal may transmit a UE capability report to a base station that includes information indicating that the terminal has collision handling capability (e.g., CollisionHandlingOfHDFDDOperation). The base station may receive the UE capability report from the terminal and verify information included in the UE capability report. If the UE capability report includes information indicating that the terminal has collision handling capability, the base station may determine that the terminal has collision handling capability and may determine to apply a collision rule between uplink and downlink communications. Alternatively, if the UE capability report does not include information indicating that the terminal has collision handling capability, the base station may determine that the terminal does not have collision handling capability and may determine not to apply a collision rule between uplink and downlink communications.

[0266] If a terminal has collision handling capability, the base station can configure (e.g., instruct, schedule) colliding uplink and downlink communications to the terminal in at least one symbol. A terminal with collision handling capability can expect to receive configuration (e.g., instruct, schedule) of colliding uplink and downlink communications from the base station in at least one symbol. If a terminal does not have collision handling capability, the base station may not configure (e.g., instruct, schedule) colliding uplink and downlink communications to the terminal in at least one symbol. A terminal without collision handling capability may not expect to receive configuration (e.g., instruct, schedule) colliding uplink and downlink communications from the base station in at least one symbol. In other words, a terminal without collision handling capability can expect to receive configuration (e.g., instruct, schedule) non-collision uplink and downlink communications from the base station in at least one symbol.

[0267] The base station can transmit information indicating the priority of uplink transmission and / or the priority of downlink reception to the terminal via signaling. The terminal can receive the information indicating the priority of uplink transmission and / or the priority of downlink reception from the base station, and can determine a communication (e.g., uplink transmission or downlink reception) with a higher priority based on the information. If the terminal is determined to have a collision handling capability, the base station can transmit information indicating the priority of uplink transmission and / or the priority of downlink reception to the terminal. Alternatively, regardless of whether the terminal has a collision handling capability, the base station can transmit information indicating the priority of uplink transmission and / or the priority of downlink reception to the terminal.

[0268] For example, the base station can transmit information indicating that uplink communication is given priority (e.g., ntnRedCapCollisionCase3UlPriority or ntnRedCapCollisionCase4UlPriority) to the terminal via signaling. The terminal can receive information indicating that uplink communication is given priority from the base station, and based on the information, select uplink communication among uplink communication and downlink communication, and perform uplink transmission to the base station. If the base station does not transmit information indicating that uplink communication is given priority to the terminal (e.g., if the terminal does not receive information indicating that uplink communication is given priority from the base station), the terminal can determine that downlink communication is given priority among uplink communication and downlink communication, and perform downlink reception to the base station. In other words, the terminal can select downlink communication.

[0269] Alternatively, the base station may transmit information indicating that downlink communication is given priority (e.g., ntnRedCapCollisionCase3DlPriority or ntnRedCapCollisionCase4DlPriority) to the terminal via signaling. The terminal may receive the information indicating that downlink communication is given priority from the base station, and may select downlink communication among uplink communication and downlink communication based on the information, and may perform downlink reception for the base station. If the base station does not transmit information indicating that downlink communication is given priority to the terminal (e.g., if the terminal does not receive information indicating that downlink communication is given priority from the base station), the terminal may determine that uplink communication is given priority among uplink communication and downlink communication, and may perform uplink transmission for the base station. In other words, the terminal may select uplink communication.

[0270] A terminal may not have the ability to handle collisions between uplink and downlink communications. In this case, the terminal may not be able to select either uplink transmission or downlink reception, and thus may not be able to perform both uplink transmission and downlink reception.

[0271] ·Method 2-3

[0272] Higher layer configurations for configuring semi-static downlink communication (e.g., CSI-RS configurations, SP (semi-persistent) PDSCH configurations, MAC CE, etc.) and / or higher layer configurations for configuring semi-static uplink communication may include an indicator for whether a collision rule for Case 3 applies. When a channel / signal including the indicator collides with a channel / signal not including the indicator, the terminal may determine that the priority of the channel / signal including the indicator is higher than the priority of the channel / signal not including the indicator. According to the above-described operation, the ambiguity of the collision rule can be minimized.

[0273] For example, a terminal can receive settings for uplink communication and settings for downlink communication through signaling from a base station. If the settings for uplink communication include the indicator (e.g., an indicator indicating application of a collision rule) and the settings for downlink communication do not include the indicator, the terminal can determine that the uplink communication having the indicator has priority, and can perform uplink communication among the uplink communication and downlink communication. The base station can expect that the uplink communication is performed. Alternatively, if the settings for uplink communication do not include the indicator (e.g., an indicator indicating application of a collision rule) and the settings for downlink communication include the indicator, the terminal can determine that the downlink communication having the indicator has priority, and can perform downlink communication among the uplink communication and downlink communication. The base station can expect that the downlink communication is performed.

[0274] ·Method 2-4

[0275] The DCI and / or MAC CE indicating dynamic downlink communication (e.g., Ap(aperiodic) CSI-RS indicator, DCI format 1_0, DCI format 1_1, etc.) and / or the DCI and / or MAC CE indicating dynamic uplink communication may include an indicator for whether a collision rule for case 4 applies. When a channel / signal including the indicator and a channel / signal not including the indicator collide with each other, the terminal may determine that the priority of the channel / signal including the indicator is higher than the priority of the channel / signal not including the indicator. According to the above-described operation, the ambiguity of the collision rule can be minimized.

[0276] For example, a terminal can receive scheduling / instruction information (e.g., DCI and / or MAC CE) of uplink communication and scheduling / instruction information of downlink communication through signaling from a base station. If the scheduling / instruction information of uplink communication includes the indicator (e.g., an indicator indicating application of a collision rule) and the scheduling / instruction information of downlink communication does not include the indicator, the terminal can determine that the uplink communication having the indicator has priority, and can perform the uplink communication among the uplink communication and downlink communication. The base station can expect that the uplink communication is performed. Alternatively, if the scheduling / instruction information of uplink communication does not include the indicator (e.g., an indicator indicating application of a collision rule) and the scheduling / instruction information of downlink communication includes the indicator, the terminal can determine that the downlink communication having the indicator has priority, and can perform the downlink communication among the uplink communication and downlink communication. The base station can expect that the downlink communication is performed.

[0277] Method for supporting changes to NTN payloads for HD-FDD terminals in an NTN environment

[0278] Methods for supporting changes in NTN payloads may include RACH-less handover (HO) procedures, satellite switch procedures with re-synchronization, etc. In NTNs (e.g., NR NTNs), a base station may provide methods (e.g., RACH-less HO procedures, satellite switch procedures with re-synchronization, etc.) for efficiently changing serving NTN payloads.

[0279] Figure 15 is a flowchart illustrating a RACH-less HO procedure.

[0280] Referring to FIG. 15, a UE can refer to independent RACH-less HO procedures for each of the dynamic grant (DG) PUSCH and the configured grant (CG) PUSCH. The UE can transmit the DG PUSCH after the RACH-less HO based on the steps below.

[0281] The terminal can transmit a measurement report to the serving base station (S1501). The serving base station can mean a serving NTN payload. Each of the serving base station and the serving NTN payload can mean a source base station and a source NTN payload. The serving base station can receive a measurement report from the terminal (S1501). If a HO procedure (e.g., a RACH-less HO procedure) is approved based on the measurement report, the serving base station can generate a HO command (e.g., an RRC reconfiguration message). The HO command includes configured grant settings (ConfiguredGrantConfg), an RSRP threshold for SSB selection, DG-beam information (e.g., an SSB index), and target N. TA, or may include at least one of the TA-reporting settings. The configured grant settings may include CG-NTN-configurations. The configured grant settings and / or RSRP thresholds for SSB selection may be information for a CG-RACH-less HO procedure. The DG-beam information may be information for a DG-RACH less HO procedure. Target N TA is a source (e.g., source N) in an intra-satellite HO procedure. TA ) may be the same as target N. TA can be set to 0. After the HO procedure, TA can be adjusted by the TAC (timing advance command) MAC CE. Target N TA In the mathematical expression 12 below, N TA It can be. In Equation 12, can be a value for a closed loop, can be a value for open-loop.

[0282]

[0283] The serving base station may transmit an HO command (e.g., an RRC reset message) to the terminal (S1502). The terminal may receive the HO command from the serving base station (S1502). The terminal may check the information included in the HO command. The terminal may start a T304 timer for HO failure monitoring (S1503). The terminal may set synchronization (e.g., DL synchronization and / or UL synchronization) for a target base station (e.g., target NTN payload) (S1504). In other words, the synchronization timing in the terminal may be changed from the serving base station to the target base station. The terminal may start a T430 timer for NTN UL synchronization monitoring (S1505). The terminal may start a TA timer (TAT) for TA monitoring (S1506).

[0284] The target base station may transmit a PDCCH including a UL grant to the terminal (S1507). In S1507, the terminal may monitor the PDCCH including the UL grant and receive the PDCCH including the UL grant. The UL grant included in the PDCCH may be a DG. S1507 may be performed based on the DG-beam information included in the HO command in S1502. The UL grant included in the PDCCH may be a DG. The terminal may generate an RRC connection re-establishment complete message including an HO completion indication. The terminal may transmit a PUSCH including the RRC connection re-establishment complete message to the target base station (S1508). In other words, the RRC connection re-establishment complete message may be transmitted on a PUSCH resource indicated by the UL grant (e.g., DG). The target base station may receive the RRC connection re-establishment complete message from the terminal (S1508).

[0285] When an RRC connection re-establishment complete message is received, the target base station can determine that the HO procedure is completed in the terminal. The target base station can generate a PDCCH (e.g., DCI) containing confirmation information regarding the completion of the HO procedure. The PDCCH may further include DL allocation information and / or UL grant. The target base station can transmit the PDCCH to the terminal (S1509). The terminal can receive the PDCCH from the target base station by performing a monitoring operation for the PDCCH (S1509). The terminal can confirm the confirmation information regarding the completion of the HO procedure, DL allocation information, and / or UL grant included in the PDCCH. If a MAC CE indicating UE contention resolution is received, the terminal can ignore the MAC CE. In other words, since a PDCCH indicating confirmation regarding the completion of the HO procedure is received, the terminal can ignore the MAC CE indicating UE contention resolution.

[0286] At S1510, the terminal may stop the T304 timer and perform an RRC connection re-establishment procedure for the target base station. If the T304 timer expires, the terminal may perform an RRC connection re-establishment procedure for the target base station.

[0287] Target N included in RRC reset message in S1502 TA In relation to this, in an intra-satellite HO procedure, the terminal can use the same TA before and after the handover. In other words, the TA for the serving base station and the TA for the target base station can be the same. In an inter-satellite HO procedure, the TA value can be initialized (e.g., targetNTA = 0), and after the HO procedure ends, the TA value can be readjusted by the TAC MAC CE, etc.

[0288] For DG PUSCH transmitted by an HD terminal after a RACH-less HO procedure, if the serving base station (e.g., serving satellite) is not the same before and after the HO procedure, the degree of TA mismatch between the base station and the terminal may increase. After the terminal is handed over to the target base station, a TA re-adjustment procedure may be performed, and the TA mismatch information may be changed before and after the TA re-adjustment procedure.

[0289] The terminal can transmit CG PUSCH after RACH-less HO based on the steps below.

[0290] The terminal can transmit a measurement report to the serving base station (e.g., serving NTN payload) (S1501). The serving base station can receive the measurement report from the terminal (S1501). If the HO procedure (e.g., RACH-less HO procedure) is approved based on the measurement report, the serving base station can generate a HO command (e.g., RRC reconfiguration message). The HO command includes the configured grant configuration (ConfiguredGrantConfg), RSRP threshold for SSB selection, DG-beam information (e.g., SSB index), and target N. TA , or may include at least one of TA-reporting settings. The configured grant settings may include CG-NTN-configuration. The configured grant settings and / or RSRP thresholds for SSB selection may be information for a CG-RACH-less HO procedure. The DG-beam information may be information for a DG-less HO procedure. Target N TA is a source (e.g., source N) in an intra-satellite HO procedure. TA ) may be the same as target N. TA can be set to 0. After the HO procedure, TA can be adjusted by TAC MAC CE.

[0291] The serving base station may transmit an HO command (e.g., an RRC reset message) to the terminal (S1502). The terminal may receive the HO command from the serving base station (S1502). The terminal may check the information included in the HO command. The terminal may start a T304 timer for HO failure monitoring (S1503). The terminal may set synchronization (e.g., DL synchronization and / or UL synchronization) for a target base station (e.g., target NTN payload) (S1504). In other words, the synchronization timing in the terminal may be changed from the serving base station to the target base station. The terminal may start a T430 timer for NTN UL synchronization monitoring (S1505). The terminal may start a TA timer (TAT) for TA monitoring (S1506).

[0292] The terminal may generate an RRC connection re-establishment complete message including an HO completion indication. The terminal may transmit a PUSCH including the RRC connection re-establishment complete message to the target base station (S1508). In other words, the RRC connection re-establishment complete message may be transmitted on a PUSCH resource indicated by the configured grant settings included in the RRC re-establishment message received in step S1502. The PUSCH transmission in S1508 may be a CG PUSCH transmission. Since the CG PUSCH transmission is performed, the PDCCH transmission and reception operation for the UL grant (e.g., S1507) may not be performed. The target base station may receive the RRC connection re-establishment complete message from the terminal (S1508).

[0293] When an RRC connection re-establishment complete message is received, the target base station can determine that the HO procedure is completed in the terminal. The target base station can generate a PDCCH (e.g., DCI) containing confirmation information regarding the completion of the HO procedure. The PDCCH may further include DL allocation information and / or UL grant. The target base station can transmit the PDCCH to the terminal (S1509). The terminal can receive the PDCCH from the target base station by performing a monitoring operation for the PDCCH (S1509). The terminal can confirm the confirmation information regarding the completion of the HO procedure, DL allocation information, and / or UL grant included in the PDCCH. If a MAC CE indicating UE contention resolution is received, the terminal can ignore the MAC CE. In other words, since a PDCCH indicating confirmation regarding the completion of the HO procedure is received, the terminal can ignore the MAC CE indicating UE contention resolution.

[0294] At step S1510, the terminal may stop the T304 timer and perform an RRC connection re-establishment procedure for the target base station. If the T304 timer expires, the terminal may perform an RRC connection re-establishment procedure for the target base station. The terminal may release resources pre-allocated for the CG-RACH-less HO procedure (e.g., the configured grant settings and / or RSRP thresholds for SSB selection included in the HO command at step S1502) (step S1511).

[0295] Target N included in RRC reset message in S1502 TAIn relation to this, in an intra-satellite HO procedure, the terminal can use the same TA before and after the handover. In other words, the TA for the serving base station and the TA for the target base station can be the same. In an inter-satellite HO procedure, the TA value can be initialized (e.g., targetNTA = 0), and after the HO procedure ends, the TA value can be readjusted by the TAC MAC CE, etc.

[0296] For CG PUSCH transmitted by an HD terminal after a RACH-less HO procedure, if the serving base station (e.g., serving satellite) is not the same before and after the HO procedure, the degree of TA mismatch between the base station and the terminal may increase. After the terminal is handed over to the target base station, a TA re-adjustment procedure may be performed, and the TA mismatch information may be changed before and after the TA re-adjustment procedure.

[0297] The above-described problems may arise due to ambiguity regarding the timing transition from the serving base station's timing to the target base station's timing in a RACH-less HO procedure and / or a satellite switching procedure with resynchronization, and / or ambiguity regarding whether collision rules (e.g., HD collision rules) apply after transitioning from the serving base station's timing to the target base station's timing. To address the above-described problems, at least one of the following methods may be applied.

[0298] Method 3-1

[0299] The terminal may apply collision rules (e.g., HD collision rules) based on the UL / DL timing of the target base station, rather than the UL / DL timing of the serving base station, from the time point at which DL synchronization with the target base station begins (e.g., as indicated by t-Service and / or t-ServiceStart). The terminal may perform the above-described actions as set by the base station. Alternatively, the terminal may perform the above-described actions as defined in the technical specifications.

[0300] ·Method 3-2

[0301] The terminal may apply collision rules (e.g., HD collision rules) based on the UL / DL timing of the target base station, rather than the UL / DL timing of the serving base station, from the time point when UL synchronization monitoring for the target base station begins (e.g., the start point of the T430 timer). The terminal may perform the above-described actions as set by the base station. Alternatively, the terminal may perform the above-described actions as defined in the technical specifications.

[0302] ·Method 3-3

[0303] The terminal may apply collision rules (e.g., HD collision rules) based on the UL / DL timing of the target base station, rather than the UL / DL timing of the serving base station, from the time point when TA monitoring for the target base station begins (e.g., the start time of the TA timer (e.g., TAT)). The terminal may perform the above-described actions as set by the base station. Alternatively, the terminal may perform the above-described actions as defined in the technical specifications.

[0304] ·Method 3-4

[0305] The terminal may apply collision rules (e.g., HD collision rules) based on the UL / DL timing of the target base station, rather than the UL / DL timing of the serving base station, from the time point when PDCCH monitoring for the target base station begins (e.g., the time point when PDCCH monitoring for a UL grant begins after a RACH-less HO procedure). The terminal may perform the above-described operations as set by the base station. Alternatively, the terminal may perform the above-described operations as defined in the technical specifications.

[0306] ·Method 3-5

[0307] The terminal may apply a collision rule (e.g., an HD collision rule) based on the UL / DL timing of the target base station, not the UL / DL timing of the serving base station, from the TA reporting time point or a specific time point after the TA reporting time point. For example, the terminal may apply a collision rule (e.g., an HD collision rule) based on the UL / DL timing of the target base station, not the UL / DL timing of the serving base station, from after "k_offset, k_mac, k_offset + k_mac, an offset set by higher layer signaling, or an offset indicated by L1 (layer1) (e.g., L1 signaling)" from "the start or end time of uplink transmission including the TA report." The terminal performing the above-described operation may be configured by the base station. Alternatively, the terminal performing the above-described operation may be defined in the technical specification. Method 3-5 may be limited to be applied for DG PUSCH transmission after the RACH-less HO procedure. In other words, Methods 3-5 can be applied for the DG-RACH-less-HO procedure.

[0308] ·Method 3-6

[0309] The UE may apply a collision rule (e.g., an HD collision rule) based on the UL / DL timing of the target base station rather than the UL / DL timing of the serving base station after a certain period of time from the time when the RSRP threshold for SSB selection is satisfied. For example, the UE may apply a collision rule (e.g., an HD collision rule) based on the UL / DL timing of the target base station rather than the UL / DL timing of the serving base station after "k_offset, k_mac, k_offset + k_mac, an offset configured by higher layer signaling, or an offset indicated by L1 (e.g., L1 signaling)" from the start time of the SSB reselection procedure. The UE performing the above-described operation may be configured by the base station. Alternatively, the UE performing the above-described operation may be defined in the technical specification. Method 3-6 may be limited to be applied for CG PUSCH transmission after a RACH-less HO procedure. In other words, methods 3-6 can be applied for the CG-RACH-less-HO procedure.

[0310] ·Method 3-7

[0311] After performing the RACH-less HO procedure and / or the resynchronization procedure, the terminal may apply a collision rule (e.g., an HD collision rule) based on the UL / DL timing of the target base station, rather than the UL / DL timing of the serving base station, at the time of performing the first RACH procedure or after a certain period from the time of performing the first RACH procedure. The terminal performing the above-described operation may be configured by the base station. Alternatively, the terminal performing the above-described operation may be defined in the technical specification.

[0312] ·Method 3-8

[0313] For collisions occurring prior to the timing application time of the target base station based on at least one of Methods 3-1 to 3-7, the terminal may apply a collision rule (e.g., an HD collision rule) based on the timing of the serving base station. The terminal performing the above-described operation may be configured by the base station. Alternatively, the terminal performing the above-described operation may be defined in a technical specification.

[0314] ·Method 3-9

[0315] For collisions occurring prior to the timing application time of the target base station based on at least one of Methods 3-1 to 3-7, the terminal may receive cell-specific downlink signals (e.g., SSB, SIB, paging, etc.) with priority. The terminal may perform the above-described operation as set by the base station. Alternatively, the terminal may perform the above-described operation as defined in the technical specification.

[0316] ·Method 3-10

[0317] For collisions occurring before the timing application time of the target base station based on at least one of Methods 3-1 to 3-7, the terminal may transmit cell-specific uplink signals (e.g., Msg1, Msg3, Msg4 ACK, MsgA, etc.) with priority. The terminal performing the above-described operation may be configured by the base station. Alternatively, the terminal performing the above-described operation may be defined in the technical specification.

[0318] ·Method 3-11

[0319] A terminal may change a base station to which the terminal is connected (e.g., connected) based on a RACH-less HO procedure, etc., to a target base station. After the terminal is connected to the target base station, the terminal may assume that the priority of the first CG PUSCH transmission (e.g., part or all of the uplink transmission set by higher layer signaling) is higher than the priority of the reception (e.g., part or all of the reception) of a downlink channel / signal (e.g., SSB, CSI-RS, etc.) set by higher layer signaling. The above rule may be applied with priority over the priority setting (e.g., priority rule) such as the priority flag described above and / or the conventional priority rule. The above-described embodiment may take into account that a TA mismatch may occur significantly in a specific time period (e.g., a time period before the terminal receives a new TAC MAC CE) after the terminal changes base stations based on the RACH-less HO procedure, and according to the above-described embodiment, the uplink transmission delay of the terminal may be minimized.

[0320] ·Method 3-12

[0321] A terminal may change a base station to which the terminal is connected (e.g., connected) based on a RACH-less HO procedure, etc., to a target base station. After the terminal is connected to the target base station, the terminal may assume that the priority of the first DG PUSCH transmission (e.g., part or all of the uplink transmission set by L1 / DCI signaling) is higher than the priority of the reception (e.g., part or all of the reception) of a downlink channel / signal (e.g., CSI-RS, PDSCH, etc.) set by L1 / DCI signaling. The above rule may be applied with priority over the priority setting of the above-described priority flag (e.g., priority rule) and / or the conventional priority rule. The above-described embodiment may take into account that a TA mismatch may occur significantly in a specific time period (e.g., a time period before the terminal receives a new TAC MAC CE) after the terminal changes base stations based on the RACH-less HO procedure, and according to the above-described embodiment, the uplink transmission delay of the terminal may be minimized.

[0322] ·Method 3-13

[0323] A terminal may change a base station to which the terminal is connected (e.g., connected) based on a RACH-less HO procedure, etc., to a target base station. After the terminal is connected to the target base station, the terminal may assume that the priority of the first CG PUSCH transmission (e.g., part or all of the uplink transmission set by higher layer signaling) is higher than the priority of the reception (e.g., part or all of the reception) of a downlink channel / signal (e.g., CSI-RS, PDSCH, etc.) set by L1 / DCI signaling. The above rule may be applied with priority over the priority setting of the above-described priority flag (e.g., priority rule) and / or the conventional priority rule. The above-described embodiment may take into account that a TA mismatch may occur significantly in a specific time period (e.g., a time period before the terminal receives a new TAC MAC CE) after the terminal changes base stations based on the RACH-less HO procedure, and according to the above-described embodiment, the uplink transmission delay of the terminal may be minimized.

[0324] ·Method 3-14

[0325] The terminal may change the base station to which the terminal is connected (e.g., connected) based on the RACH-less HO procedure, etc., to the target base station. After the terminal is connected to the target base station, the terminal may change the TA value of the terminal assumed by the base station during a specific time interval (e.g., or ) can be determined to include everything from the minimum possible TA to the maximum possible TA. The terminal may be set or instructed to perform the above-described operation by the base station. Alternatively, the terminal may be defined in the technical specification to perform the above-described operation. The specific time interval may be set in units of slots, symbols, or absolute time (e.g., ms (milliseconds)). The specific time interval may be defined based on an event (e.g., prior to the first TA report after a change in the base station to which the terminal is connected).

[0326] The maximum possible TA may be the TA determined (e.g., calculated) when the terminal is located at the outermost edge of the beam of the base station (e.g., satellite) (e.g., when the terminal is located at the coverage edge of the base station). The minimum possible TA may be the TA determined (e.g., calculated) when the terminal is located at the center of the beam of the base station (e.g., satellite) (e.g., when the terminal is located at the coverage center of the base station). Method 3-14 may mean that the terminal must consider all from the minimum possible TA to the maximum possible TA in the procedure for specifying a downlink channel / signal that collides with an uplink transmission in order to determine whether to perform an uplink transmission at a specific point in time. Method 3-14 may mean that the terminal must consider all from the minimum possible TA to the maximum possible TA in the procedure for specifying an uplink channel / signal that collides with a downlink reception in order to determine whether to perform a downlink reception at a specific point in time.

[0327] The set of DL receptions and UL transmissions configured semi-statically can be listed to further study the priority rules in collision case 3 (e.g., collision between a DL reception configured semi-statically and a UL transmission configured semi-statically). A brief observation for each channel in collision case 3 can be as follows.

[0328] PDCCH CSS (common search space): The PDCCH CSS can carry DCIs for system information. Therefore, PDCCH CSS monitoring may require higher priority than UL transmission. In some deployment scenarios, UL transmission may be valid at least from the epoch time until the end of the validity period specified by T430, rather than PDCCH CSS monitoring.

[0329] PDCCH USS (UE-specific search space): Omitting PDCCH USS monitoring may have less impact than omitting some UCIs on PUSCH and / or PUCCH. However, PDCCH USS monitoring may still have higher value than a single SRS transmission occasion.

[0330] PDSCH: Omitting PDSCH reception may have less impact than omitting some UCIs on PUSCH and / or PUCCH. However, PDSCH reception may still have higher value than a single SRS transmission occasion.

[0331] CSI-RS: Due to the various roles of CSI-RS in NR (e.g., time and frequency tracking, CSI measurement, beam management, etc.), CSI-RS reception may need to be given high priority in the NTN. Regarding aperiodic CSI-RS for missed CSI-RS reception, the utilization of aperiodic CSI reporting may be mandatory, as periodic CSI reporting cannot be correlated with aperiodic CSI-RS.

[0332] PRS (Positioning Reference Signal): PRS reception can affect terminal positioning accuracy. Given that PRS reception is associated with various NTN functions, including TA, PRS reception may be given higher priority than UL transmission.

[0333] PUSCH: PUSCH can carry UCIs. Omission of PUSCH transmissions can impact the UE processing timeline. Therefore, it may be desirable to prioritize PUSCH transmissions over PDCCH USS monitoring, PDSCH reception, and / or CSI-RS reception. PUSCHs using orthogonal cover code (OCC) techniques (e.g., new features) may also be considered. In other words, in this case, higher priority may be required for PUSCH.

[0334] PUCCH: PUCCH can carry UCIs and / or SRs. Omission of PUCCH transmissions can impact the UE processing timeline. Therefore, it may be desirable to prioritize PUCCH transmissions over PDCCH USS monitoring, PDSCH reception, and / or CSI-RS reception.

[0335] SRS: In NTN, SRS can be utilized for various purposes, including Doppler compensation, uplink power control, and beam management. However, considering that a UE is typically limited to transmitting SRS on a small number of RBs in an NTN, the importance of a single SRS transmission occasion may be lower than that of other DL channels / signals for system information and / or wideband channel state information. Other options, such as aperiodic SRS, may also be available for skipped periodic SRS transmissions.

[0336] Based on the above observations, the following suggestions can be made:

[0337] Proposal: RAN1 (radio access network 1) may consider the following priority rules for collision case 3. Table 31 may define the proposed priority rules for case 3 (e.g., collision case 3).

[0338]

[0339] The above-described priority rules may be activated with one of the following options based on at least one of the upper layer parameter signaling, layer 1 signaling, or predefined rules.

[0340] Proposal: To address the issue of Collision Case 3, RAN1 may choose one of the following options:

[0341] ·Option 1: For all conflicting use cases, DL reception can override UL transmission without exception.

[0342] ·Option 2: For all conflicting use cases, UL transmission can override DL reception without exception.

[0343] ·Option 3: The same priority rule that maintains one direction and overrides the other can be set / instructed by the network for all conflicting use cases without exceptions.

[0344] ○ Settings / Instruction Details

[0345] ·Option 4: The same priority rule that maintains one direction and overrides another can be applied to a group of use cases.

[0346] ○ A group of default use cases where DL reception overrides UL transmission.

[0347] All channels and signals may be included in the default use case group unless otherwise configured or directed by the base station.

[0348] ○ A group of use cases where UL transmission overrides DL reception

[0349] DL receptions (e.g., PDCCH USS, PDSCH, CSI-RS) and PUCCH with UCI / SR

[0350] DL receptions (e.g., PDCCH USS, PDSCH, CSI-RS) and PUSCH with UCI or OCC

[0351] PDCCH CSS (e.g. PDCCH CSS for SIB19 while T430 is operating) and UL transmission

[0352] ○ Whether / how priorities are dictated by the network or predefined

[0353] ○ Collision of two or more channels / signals

[0354] For collision case 4 (conflict between dynamic DL reception and dynamic UL transmission), a subset of the priority rules in Table 3 can be considered as follows.

[0355] Proposal: RAN1 may consider the following priority rules for Case 4 (e.g., Collision Case 4). Table 32 may define the proposed priority rules for Collision Case 4.

[0356]

[0357] Similar to collision case 3, the above-described priority rules can be activated with one of the following options based on at least one of the upper layer parameter signaling, layer 1 signaling, or predefined rules.

[0358] Proposal: To address the issue of Conflict Case 4, RAN1 may choose one of the following options:

[0359] ·Option 1: For all conflicting use cases, DL reception can override UL transmission without exception.

[0360] ·Option 2: For all conflicting use cases, UL transmission can override DL reception without exception.

[0361] ·Option 3: The same priority rule that maintains one direction and overrides the other can be set / instructed by the network for all conflicting use cases without exceptions.

[0362] ○ Settings / Instruction Details

[0363] ·Option 4: The same priority rule that maintains one direction and overrides another can be applied to a group of use cases.

[0364] ○ A group of default use cases where DL reception overrides UL transmission.

[0365] All channels and signals may be included in the default use case group unless otherwise configured or directed by the base station.

[0366] ○ A group of use cases where UL transmission overrides DL reception

[0367] DL receptions (e.g., PDSCH, CSI-RS) and PUSCH with UCI or OCC

[0368] ○ Whether / how priorities are dictated by the network or predefined

[0369] ○ Collision of two or more channels / signals

[0370] As another example of enabling Option 4 in Proposals 3 and 5 described above, introducing a new higher-layer parameter that can indicate the priority of channels / signals associated with the new parameter may be considered. For Cases 3 and 4, a DL channel / signal (or UL channel / signal) associated with a priority flag may have a higher priority than a UL channel / signal (or DL ​​channel / signal) without a priority flag. Collisions between channels / signals with the same priority (e.g., all collisions between channels / signals with priority flags or all collisions between channels / signals without priority flags) may be considered error cases. The priority flag may provide the base station with flexible collision handling rules for various collision cases at the cost of limited specification efforts.

[0371] Figure 16 is a conceptual diagram illustrating embodiments of conflict handling for cases 3 and 4 based on priority flags.

[0372] Referring to FIG. 16, for cases 3 and 4, a new upper layer parameter may be introduced to indicate a priority flag for channels / signals included in a group of use cases where UL transmission overrides DL reception. A terminal may transmit and receive channels / signals with priority flags set. The terminal may not expect overlap between channels / signals with the same priority. In other words, "collisions between channels / signals without priority flags" or "collisions between channels / signals with priority flags" may be error cases.

[0373] In the embodiments, the order of execution of the steps may not be limited to the order described in the present disclosure. Multiple steps may be performed simultaneously, some step(s) may be omitted, other step(s) may be performed additionally, and the steps may be performed in different orders. The embodiments of the present disclosure may be performed independently. Alternatively, a combination of the embodiments of the present disclosure may be applied.

[0374] Embodiments of the present disclosure may be implemented based on a combination of at least one of hardware, firmware, or software. When embodiments of the present disclosure are implemented by hardware, embodiments of the present disclosure may be implemented by at least one of Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), general processors, controllers, microcontrollers, or microprocessors.

[0375] The operations of the method according to the embodiments of the present disclosure can be implemented as a computer-readable program or code on a computer-readable recording medium. A computer-readable recording medium includes any type of recording device that stores information readable by a computer system. Furthermore, a computer-readable recording medium can be distributed across network-connected computer systems, allowing the computer-readable program or code to be stored and executed in a distributed manner.

[0376] Additionally, the computer-readable recording medium may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, etc. The program instructions may include not only machine language codes produced by a compiler, but also high-level language codes that can be executed by a computer using an interpreter, etc.

[0377] While some aspects of the present disclosure have been described in the context of a device, they may also represent a description of a corresponding method, wherein a block or device corresponds to a method step or a feature of a method step. Similarly, aspects described in the context of a method may also be described as a corresponding block or item or a feature of a corresponding device. Some or all of the method steps may be performed by (or using) a hardware device, such as, for example, a microprocessor, a programmable computer, or an electronic circuit. In some embodiments, at least one or more of the most significant method steps may be performed by such a device.

[0378] In embodiments, a programmable logic device (e.g., a field-programmable gate array) may be used to perform some or all of the functions of the methods described herein. In embodiments, the field-programmable gate array may operate in conjunction with a microprocessor to perform one of the methods described herein. In general, the methods are preferably performed by some hardware device.

[0379] Although the present disclosure has been described with reference to preferred embodiments thereof, it will be understood by those skilled in the art that various modifications and changes may be made to the present disclosure without departing from the spirit and scope of the present disclosure as set forth in the claims below.

Claims

1. As a method of UE (user equipment), A step of receiving first setting information of uplink communication and second setting information of downlink communication from a base station; A step of selecting one of the uplink communication and the downlink communication based on whether the uplink communication and the downlink communication collide in at least one symbol; and A step of performing the selected communication with the base station based on the setting information for the selected communication, UE's method.

2. In claim 1, A step of transmitting information indicating that the UE has a collision handling capability between the uplink communication and the downlink communication to the base station; and Further comprising a step of receiving information indicating a priority rule from the base station based on the UE having the collision handling capability, Based on the above priority rule, one of the uplink communication and the downlink communication is selected. UE's method.

3. In claim 1, Based on the fact that the UE does not have a collision handling capability between the uplink communication and the downlink communication, the UE does not expect to receive the first configuration information and the second configuration information for each of the uplink communication and the downlink communication that collide in the at least one symbol from the base station. UE's method.

4. In claim 1, Based on the UE having a collision handling capability between the uplink communication and the downlink communication, the first configuration information and the second configuration information for each of the uplink communication and the downlink communication colliding in the at least one symbol are received from the base station. UE's method.

5. In claim 1, Based on a priority rule indicating that the uplink communication is given priority, which is received from the base station, the uplink communication is selected among the uplink communication and the downlink communication. UE's method.

6. In claim 1, Based on the fact that a priority rule indicating that the uplink communication is given priority is not received from the base station, the downlink communication is selected among the uplink communication and the downlink communication. UE's method.

7. In claim 1, The first configuration information of the above uplink communication is configuration information of a semi-static uplink communication, and the second configuration information of the above downlink communication is configuration information of a semi-static downlink communication. UE's method.

8. In claim 1, The first configuration information of the uplink communication is DCI (downlink control information) or MAC (medium access control) CE (control element) indicating dynamic uplink communication, and the second configuration information of the downlink communication is DCI or MAC CE indicating dynamic downlink communication. UE's method.

9. In claim 1, The UE supports HD (half duplex)-FDD (frequency division duplex), the UE operates in an NTN (non-terrestrial network) serving cell, and the operating state of the UE is an RRC (radio resource control) connected state or an RRC inactive state. UE's method.

10. As a method of base station, A step of transmitting first setting information of uplink communication and second setting information of downlink communication to UE (user equipment); and A step of performing one of the uplink communication and the downlink communication with the UE based on the uplink communication and the downlink communication colliding in at least one symbol, The above one communication is selected from the UE, and the UE supports HD (half duplex)-FDD (frequency division duplex). Base station method.

11. In claim 10, A step of receiving information from the UE indicating that the UE has a collision handling capability between the uplink communication and the downlink communication; and Further comprising a step of transmitting information indicating a priority rule to the UE based on the UE having the collision handling capability, Based on the above priority rule, one of the uplink communication and the downlink communication is selected. Base station method.

12. In claim 10, Based on the fact that the UE does not have a collision handling capability between the uplink communication and the downlink communication, the base station does not transmit the first configuration information and the second configuration information for each of the uplink communication and the downlink communication that collide in the at least one symbol to the UE. Base station method.

13. In claim 10, Based on the UE having a collision handling capability between the uplink communication and the downlink communication, the base station transmits the first configuration information and the second configuration information for each of the uplink communication and the downlink communication colliding in the at least one symbol to the UE. Base station method.

14. In claim 10, Based on the fact that the base station has transmitted to the UE a priority rule indicating that the uplink communication is given priority, the uplink communication is selected among the uplink communication and the downlink communication. Base station method.

15. In claim 10, Based on the fact that the base station does not transmit to the UE a priority rule indicating that the uplink communication is given priority, the downlink communication is selected among the uplink communication and the downlink communication. Base station method.

16. In claim 10, The first configuration information of the above uplink communication is configuration information of a semi-static uplink communication, and the second configuration information of the above downlink communication is configuration information of a semi-static downlink communication. Base station method.

17. In claim 10, The first configuration information of the uplink communication is DCI (downlink control information) or MAC (medium access control) CE (control element) indicating dynamic uplink communication, and the second configuration information of the downlink communication is DCI or MAC CE indicating dynamic downlink communication. Base station method.

18. As a UE (user equipment), Contains at least one processor, At least one processor of the UE, Receive first setting information for uplink communication and second setting information for downlink communication from a base station; Selecting one of the uplink communication and the downlink communication based on whether the uplink communication and the downlink communication collide in at least one symbol; and Causing the selected communication to be performed with the base station based on the setting information for the selected communication. UE.

19. In claim 18, At least one processor of the UE, Transmitting information indicating that the UE has a collision handling capability between the uplink communication and the downlink communication to the base station; and Further causing the UE to receive information indicating a priority rule from the base station based on the UE having the collision handling capability, Based on the above priority rule, one of the uplink communication and the downlink communication is selected. UE.

20. In claim 18, Based on a priority rule indicating that the uplink communication is given priority, which is received from the base station, the uplink communication is selected among the uplink communication and the downlink communication. UE.

Images