METHOD AND APPARATUS FOR INDICATING TIMING ADVANCE IN COMMUNICATION SYSTEM

Abstract

The present disclosure relates to: a communication technique for merging IoT technology with a 5G communication system for supporting a higher data transmission rate beyond a 4G system, and a system therefor. The present disclosure can be applied to intelligent services (for example, smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail businesses, security- and safety-related services, etc.) on the basis of 5G communication technology and IoT-related technology. Disclosed are a method and apparatus in which a terminal performs satellite communication.

Claims

1. A method performed by a base station in a communication system, the method comprising: transmitting, to a user equipment (UE), configuration information on a non-terrestrial network (NTN) communication; and receiving, from the UE, an uplink signal associated with a timing advance (TA), wherein a value of the TA is associated with a first offset and a second offset, and wherein the first offset is common for plural UEs and the second offset is specific for the UE.

2. The method of claim 1, the first offset is based on a rate of change of the TA, and the second offset is based on higher layer signaling.

3. The method of claim 1, further comprising: receiving, from the UE, a TA report via a medium access control (MAC) control element (CE), wherein the TA report is triggered based on a threshold value for the TA report, and wherein the TA report including a value of the TA that the UE calculates.

4. The method of claim 3, wherein the value of the TA included in the TA report is a calculated value of the TA before a timing of TA reporting, and wherein the value of the TA included in the TA report is indicated in slot units.

5. A method performed by a user equipment(UE) in a communication system, the method comprising: receiving, from a base station, configuration information on a non-terrestrial network (NTN) communication; identifying a value of a timing advance (TA); and transmitting an uplink signal by applying the value of the TA, wherein the value of the TA is identified based on a first offset and a second offset, and wherein the first offset is common for plural UEs and the second offset is specific for the UE.

6. The method of claim 5, wherein the first offset is based on a rate of change of the TA, and the second offset is based on higher layer signaling.

7. The method of claim 5, further comprising: identifying that a TA report is triggered based on a threshold value for the TA report; and transmitting, to the base station, the TA report via a medium access control (MAC) control element (CE), wherein the TA report including a value of the TA that the UE calculates.

8. The method of claim 7, further comprising: receiving one or more pieces of TA loop configuration information from the base station; receiving a TA loop index and information on a TA value from the base station; and determining a TA value corresponding to a TA loop indicated by the TA loop index, based on the information on the TA value.

9. A base station in a communication system, the base station comprising: a transceiver; and a controller coupled with the transceiver and configured to; transmit, to a user equipment (UE), configuration information on a non-terrestrial network (NTN) communication, and receive, from the UE, an uplink signal associated with a timing advance (TA), wherein a value of the TA is associated with a first offset and a second offset, and wherein the first offset is common for plural UEs and the second offset is specific for the UE.

10. The base station of claim 9, wherein the first offset is based on a rate of change of the TA, and the second offset is based on higher layer signaling.

11. The base station of claim 9, wherein the controller is further configured to receive, from the UE, a TA report via a medium access control (MAC) control element (CE), wherein the TA report is triggered based on a threshold value for the TA report, and wherein the TA report including a value of the TA that the UE calculates.

12. A user equipment (UE) in a communication system, the UE comprising: a transceiver; and a controller coupled with the transceiver and configured to: receive, from a base station, configuration information on a non-terrestrial network (NTN) communication, identify a value of a timing advance (TA), and transmit an uplink signal by applying the value of the TA, wherein the value of the TA is identified based on a first offset and a second offset, and wherein the first offset is common for plural UEs and the second offset is specific for the UE.

13. The UE of claim 12, wherein the first offset is based on a rate of change of the TA and the second offset is based on higher layer signaling.

14. The UE of claim 12, wherein the controller is further configured to receive, from the UE, a TA report via a medium access control (MAC) control element (CE), wherein the TA report is triggered based on a threshold value for the TA report, and wherein the TA report including a value of the TA that the UE calculates.

15. The UE of claim 12, wherein the value of the TA included in the TA report is a calculated value of the TA before a timing of TA reporting, and wherein the value of the TA included in the TA report is indicated in slot.

16. The method of claim 3, wherein the threshold value for the TA report is transmitted via higher layer signaling.

17. The method of claim 8, wherein the threshold value for the TA report is configured via higher layer signaling.

18. The base station of claim 11, wherein the value of the TA included in the TA report is a calculated value of the TA before a timing of TA reporting, and wherein the value of the TA included in the TA report is indicated in slot units.

19. The base station of claim 11, wherein the threshold value for the TA report is transmitted via higher layer signaling.

20. The UE of claim 14, wherein the threshold value for the TA report is configured via higher layer signaling.

Description

BRIEF DESCRIPTION OF DRAWINGS

[0012] FIG. 1 illustrates a basic structure of a time-frequency domain, which is a radio resource domain in which data or a control channel is transmitted in a downlink or uplink in an NR system;

[0013] FIG. 2 illustrates a control resource set in which a downlink control channel is transmitted in a 5G wireless communication system;

[0014] FIG. 3 illustrates an example in which eMBB, URLLC, and mMTC data are allocated in an entire system frequency band;

[0015] FIG. 4 illustrates an example in which eMBB, URLLC, and mMTC data are allocated in a divided system frequency band;

[0016] FIG. 5 illustrates an example of a process in which one transport block is divided into multiple code blocks and CRCs are added thereto;

[0017] FIG. 6 illustrates a configuration in which a synchronization signal (SS) and a physical broadcast channel (PBCH) of an NR system are mapped in a frequency and a time domain;

[0018] FIG. 7 illustrates a symbol to which an SS/PBCH block may be transmitted according to a subcarrier spacing;

[0019] FIG. 8 illustrates a UE processing time according to a timing advance when a UE receives a first signal and transmits a second signal in response thereto in a 5G or NR system according to a disclosed embodiment;

[0020] FIG. 9 illustrates an example in which data (e.g., TBs) is scheduled and transmitted according to a slot, a HARQ-ACK feedback for the corresponding data is received, and retransmission is performed according to the feedback;

[0021] FIG. 10 illustrates an example of a communication system using a satellite;

[0022] FIG. 11 illustrates a period in which a communication satellite revolves around the Earth according to an altitude or height of a satellite;

[0023] FIG. 12 illustrates a conceptual diagram of satellite-to-terminal direct communication;

[0024] FIG. 13 illustrates a utilization scenario of satellite-terminal direct communication;

[0025] FIG. 14 illustrates an example of calculating an expected data rate (or throughput) in an uplink when an LEO satellite at an altitude of 1200 km and a terrestrial terminal perform direct communication;

[0026] FIG. 15 illustrates an example of calculating an expected data rate (or throughput) in an uplink when a GEO satellite at an altitude of 35,786 km and a terrestrial terminal perform direct communication;

[0027] FIG. 16 illustrates a path loss value according to a path loss model between a terminal and a satellite, and a path loss according to a path loss model between a terminal and a terrestrial base station;

[0028] FIG. 17 illustrates equations for calculation of the amount of Doppler shift experienced by a signal, which is transmitted from a satellite and received by a terrestrial user according to an altitude and a location of the satellite, and a location of a terminal user on the ground, and results thereof;

[0029] FIG. 18 illustrates the speed of a satellite calculated at an altitude of the satellite;

[0030] FIG. 19 illustrates Doppler shifts experienced by different terminals in one beam, which is transmitted by a satellite to the ground;

[0031] FIG. 20 illustrates a difference in Doppler shift occurring in one beam according to the location of a satellite determined from an elevation angle;

[0032] FIG. 21 illustrates a latency taken from a UE to a satellite and a round trip latency among the UE, the satellite, and a base station according to the location of the satellite determined according to an elevation angle;

[0033] FIG. 22 illustrates a maximum difference value of a round trip latency which varies according to a user's location in one beam;

[0034] FIG. 23 illustrates an example of an information structure of an RAR;

[0035] FIG. 24 illustrates an example of relationship between a PRACH preamble configuration resource and an RAR reception timing in an LTE system;

[0036] FIG. 25 illustrates an example of relationship between a PRACH preamble configuration resource and an RAR reception timing in a 5G NR system;

[0037] FIG. 26 illustrates an example of downlink frame timing and uplink frame timing in a UE;

[0038] FIG. 27A illustrates an example of continuous movement of a satellite in a UE located on the ground or on the earth as the satellite revolves around the Earth along a satellite orbit;

[0039] FIG. 27B illustrates an example of a structure of an artificial satellite;

[0040] FIG. 28 illustrates an example of a difference in propagation delay in a terrestrial network and propagation delay in a satellite network;

[0041] FIG. 29 illustrates an example of applying a timing advance in a terrestrial network and a satellite network;

[0042] FIG. 30 illustrates an example of a maximum difference value among difference values in round trip propagation delay among a UE, a satellite, and a base station, experienced by a plurality of users when the users are located in one beam transmitted by a satellite;

[0043] FIG. 31A illustrates an example of a round trip time between a UE and a base station which varies according to a movement of a satellite along an orbit;

[0044] FIG. 31B illustrates an example in which a plurality of UEs are located in one beam area provided by one satellite;

[0045] FIG. 31C illustrates an example of indicating a time offset to UEs included in one group by using one MAC CE;

[0046] FIG. 32 illustrates an example in which a beam or satellite to which a UE is connected is changed, but a terrestrial base station connected to the UE is not changed;

[0047] FIG. 33 illustrates an example in which, when a beam or satellite to which a UE is connected (or from which the UE receives a service) is changed, a terrestrial base station or a ground station connected to the UE is also changed;

[0048] FIG. 34 illustrates an example of a TA loop;

[0049] FIG. 35A illustrates an example of a base station operation for such a TA change;

[0050] FIG. 35B illustrates an example of a UE operation for such a TA change;

[0051] FIG. 36A illustrates an example of a base station operation for transmitting a PUSCH by applying a TA indication;

[0052] FIG. 36B illustrates an example of a UE operation for transmitting a PUSCH by applying a TA indication;

[0053] FIG. 37A illustrates an example of a base station operation for a TA value reporting of a UE;

[0054] FIG. 37B illustrates an example of a UE operation for a TA value reporting of a UE;

[0055] FIG. 38 is a block diagram illustrating an internal structure of a UE according to an embodiment of the disclosure;

[0056] FIG. 39 is a block diagram illustrating an internal structure of a satellite according to an embodiment of the disclosure; and

[0057] FIG. 40 is a block diagram illustrating an internal structure of a base station according to an embodiment of the disclosure.

MODE FOR THE INVENTION

[0058] A new radio (NR) access technology that is new 5G communication is designed to allow various services to be freely multiplexed in time and frequency resources, and accordingly, waveform/numerology, reference signals, and the like may be dynamically or freely allocated according to the needs of a corresponding service. In wireless communication, data transmission that is optimized via measurement of a channel quality and interference amount is important to provide an optimal service to a terminal. Accordingly, it is requested to exactly measure a channel state. However, unlike 4G communication in which a channel and an interference characteristic are not sharply changed according to a frequency resource, in a case of a 5G channel, a channel and an interference characteristic are significantly changed according to services, and thus there is a need to support a frequency resource group (FRG) subset so as to separately measure the channel and the interference characteristic. Meanwhile, types of services that are supported in the NR system may be classified into categories including enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), ultra-reliability low-latency communication (URLLC) services, or the like. The eMBB may be a service for high-speed transmission of a large amount of data, the mMTC may be a service for minimum power consumption of a UE and access of multiple UEs, and the URLLC may be a service for high reliability and low latency. Different requirements may be applied according to the types of services to be applied to a UE. As such, a plurality of services may be provided to a user in a communication service, and in order to provide the user with the plurality of services, a method of providing the services according to respective characteristics in same time duration and an apparatus using the method are required. Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.

[0059] In describing the embodiments, descriptions related to technical contents well-known in the art to which the disclosure pertains and not associated directly with the disclosure will be omitted. Such an omission of unnecessary descriptions is intended to prevent obscuring of the main idea of the disclosure and more clearly transfer the main idea.

[0060] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated. Further, the size of each element does not completely reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals.

[0061] The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described below in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth below, but may be implemented in various different forms. The following embodiments are provided only to completely disclose the disclosure and inform those skilled in the art of the scope of the disclosure, and the disclosure is defined only by the scope of the appended claims. Throughout the specification, the same or like reference numerals designate the same or like elements.

[0062] Herein, it will be understood that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart block or blocks. These computer program instructions may also be stored in a computer usable or computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that implement the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions that execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

[0063] Further, each block of the flowchart illustrations may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.

[0064] As used herein, the “unit” refers to a software element or a hardware element, such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC), which performs a predetermined function. However, the “unit” does not always have a meaning limited to software or hardware. The “unit” may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the “unit” includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The elements and functions provided by the “unit” may be either combined into a smaller number of elements, or a “unit”, or divided into a larger number of elements, or a “unit”. Moreover, the elements and “units” or may be implemented to reproduce one or more CPUs within a device or a security multimedia card. Further, the “unit” in the embodiments may include one or more processors.

[0065] A wireless communication system is advancing to a broadband wireless communication system for providing high-speed and high-quality packet data services using communication standards, such as high-speed packet access (HSPA) of 3GPP, LTE {long-term evolution or evolved universal terrestrial radio access (E-UTRA)}, LTE-Advanced (LTE-A), LTE-Pro, high-rate packet data (HRPD) of 3GPP2, ultra-mobile broadband (UMB), IEEE 802.16e, and the like, as well as typical voice-based services. Furthermore, as 5G wireless communication systems, 5G or new radio (NR) communication standards are under development.

[0066] As a typical example of the broadband wireless communication system, an NR system employs an orthogonal frequency division multiplexing (OFDM) scheme in a downlink (DL) and an uplink (UL). More specifically, the NR system employs a cyclic-prefix OFDM (CP-OFDM) scheme in a downlink and employs two schemes, that is, a discrete Fourier transform spreading OFDM (DFT-S-OFDM) scheme, as well as the CP-OFDM scheme, in an uplink. The uplink indicates a radio link through which a user equipment (UE) (or a mobile station (MS)) transmits data or control signals to a base station (BS) (or gNode B), and the downlink indicates a radio link through which the base station transmits data or control signals to the UE. The above multiple access schemes separate data or control information of respective users by allocating and operating time-frequency resources for transmitting the data or control information for each user so as to avoid overlapping each other, that is, so as to establish orthogonality.

[0067] The NR system adopts a hybrid automatic repeat request (HARQ) scheme of retransmitting data through a physical layer when a decoding failure occurs in initial transmission. The HARQ scheme indicates that, when a receiver fails to correctly decode data, the receiver transmits decoding failure indication information (e.g., negative acknowledgement (NACK)) to a transmitter so as to allow the transmitter to retransmit the data through the physical layer. The receiver may combine the data, which is retransmitted by the transmitter, with data previously failed in decoding, thereby increasing data reception performance. Further, when the receiver correctly decodes the data, the transmitter transmits decoding success indication information (e.g., acknowledgement (ACK)) to the transmitter so as to allow the transmitter to transmit new data. FIG. 1 illustrates a basic structure of a time-frequency domain, which is a radio resource domain in which data or a control channel is transmitted via uplink or downlink in an NR system.

[0068] In FIG. 1, the horizontal axis indicates a time domain and the vertical axis indicates a frequency domain. In the time domain, the minimum transmission unit is an OFDM symbol, and N.sub.symb number of OFDM symbols 102 constitute one slot 106. The length of a subframe may be defined as 1.0 ms, and the length of a radio frame 114 may be defined as 10 ms. In the frequency domain, the minimum transmission unit is a subcarrier, and the bandwidth of the entire system transmission band may be configured by a total of N.sub.BW subcarriers 104. 1 frame may be defined as 10 ms. 1 subframe may be defined as 1 ms, and accordingly, 1 frame may be configured by a total of 10 subframes. 1 slot may be defined as 14 OFDM symbols (that is, the number of symbols per slot (N.sub.symb.sup.slot)=14). 1 subframe may be configured by one or multiple slots, and the number of slots per 1 subframe may differ according to configuration value μ for a subcarrier spacing. In the example of FIG. 2, a case in which the subcarrier spacing configuration value μ has a value of ‘0’ (μ=0) and a case in which the subcarrier spacing configuration value μ has a value of ‘1’ (μ=1) are illustrated. In a case of μ=0, 1 subframe may include 1 slot, and in a case of μ=1, 1 subframe may include two slots. That is, the number of slots per 1 subframe (N.sub.slot.sup.subframe,μ) may differ according to a subcarrier spacing configuration value μ, and accordingly, the number of slots per one frame (N.sub.slot.sup.frame,μ) may differ. The N.sub.slot.sup.subframe,μ and the N.sub.slot.sup.frame,μ according to each subcarrier spacing configuration p may be defined as [Table 1] below.

TABLE-US-00001 TABLE 1 μ N.sub.symb.sup.slot N.sub.slot.sup.frame,μ N.sub.slot.sup.subframe,μ 0 14 10 1 1 14 20 2 2 14 40 4 3 14  80− 8 4 14 160  16

[0069] A UE before radio resource control (RRC) connection may be configured with an initial bandwidth part (initial BWP) for initial access from a base station through a master information block (MIB). More specifically, the UE may receive configuration information about a search apace and a control resource set (CORESET) through which the physical downlink control channel (PDCCH) for reception of system information required for initial access (may correspond to remaining system information (RMSI) or system information block 1 (SIB 1) through the MIB at the initial access stage. The control resource set (CORESET) and search space, which are configured through the MIB, may be regarded as identity (ID) 0, respectively. The base station may notify the UE of configuration information, such as frequency allocation information, time allocation information, and numerology for the control resource set #0 through the MIB. In addition, the base station may notify the UE of configuration information regarding the monitoring periodicity and occasion for the control resource set #0, that is, configuration information regarding the search space #0, through the MIB. The UE may regard the frequency domain configured as the control resource set #0, obtained from the MIB, as an initial BWP for initial access. Here, the identifier (ID) of the initial BWP may be regarded as zero.

[0070] The MIB may include the following pieces of information.

TABLE-US-00002 -- ASN1START -- TAG-MIB-START MIB :=          SEQUENCE {   system FrameNumber   BIT STRING (SIZE (6)),   subCarrierSpacingCommon  ENUMERATED {scs15or60, scs30or120},   ssb-SubcarrierOffset INTEGER (0..15),   dmrs-TypeA-Position  ENUMERATED {pos2, pos3},   pdcch-ConfigSIB1   PDCCH-ConfigSIB1,   cellBarred  ENUMERATED {barred, notBarred},   intraFreqReselection ENUMERATED {allowed, notAllowed},   spare   BIT STRING (SIZE (1)) } -- TAG-MIB-STOP -- ASN1STOP

[0071] MIB field descriptions [0072] cellBarred

[0073] Value barred means that the cell is barred, as defined in TS 38.304 [20]. [0074] dmrs-TypeA-Position

[0075] Position of (first) DM-RS for downlink (see TS 38.211 [16], clause 7.4.1.1.2) and uplink (see TS 38.211 [16], clause 6.4.1.1.3). [0076] intraFreqReselection

[0077] Controls cell selection/reselection to intra-frequency cells when the highest ranked cell is barred, or treated as barred by the UE, as specified in TS 38.304 [20]. [0078] pdcch-ConfigSIB1

[0079] Determines a common ControlResourceSet (CORESET), a common search space and necessary PDCCH parameters. If the field ssb-SubcarrierOffset indicates that SIB1 is absent, the field pdcch-ConfigSIB1 indicates the frequency positions where the UE may find SS/PBCH block with SIB1 or the frequency range where the network does not provide SS/PBCH block with SIB1 (see TS 38.213 [13], clause 13). [0080] ssb-SubcarrierOffset

[0081] Corresponds to kSSB (see TS 38.213 [13]), which is the frequency domain offset between SSB and the overall resource block grid in number of subcarriers. (See TS 38.211 [16], clause 7.4.3.1).

[0082] The value range of this field may be extended by an additional most significant bit encoded within PBCH as specified in TS 38.213 [13].

[0083] This field may indicate that this cell does not provide SIB1 and that there is hence no CORESET #0 configured in MIB (see TS 38.213 [13], clause 13). In this case, the field pdcch-ConfigSIB1 may indicate the frequency positions where the UE may (not) find a SS/PBCH with a control resource set and search space for SIB1 (see TS 38.213 [13], clause 13). [0084] subCarrierSpacingCommon

[0085] Subcarrier spacing for SIB1, Msg.2/4 for initial access, paging and broadcast SI-messages. If the UE acquires this MIB on an FR1 carrier frequency, the value scs15or60 corresponds to 15 kHz and the value scs30or120 corresponds to 30 kHz. If the UE acquires this MIB on an FR2 carrier frequency, the value scs15or60 corresponds to 60 kHz and the value scs30or120 corresponds to 120 kHz. [0086] systemFrameNumber

[0087] The 6 most significant bits (MSB) of the 10-bit System Frame Number (SFN). The 4 LSB of the SFN are conveyed in the PBCH transport block as part of channel coding (i.e., outside the MIB encoding), as defined in clause 7.1 in TS 38.212 [17].

[0088] In a method for configuring the BWP, the UEs before the RRC connection may receive configuration information about the initial bandwidth part through the master information block (MIB) in the initial connection operation. More specifically, the UE may be configured with a control region or control resource set (CORESET) for a downlink control channel through which downlink control information (DCI) for scheduling a system information block (SIB) can be transmitted from a MIB of a physical broadcast channel (PBCH). The bandwidth of the control resource set configured through the MIB may be regarded as the initial BWP. The UE may receive, through the configured initial BWP, a physical downlink shared channel (PDSCH) through which the SIB is transmitted. The initial BWP may be used for other system information (OSI), paging, and random access as well as the reception of the SIB.

[0089] When one or more BWPs have been configured for a UE, the base station may indicate the UE to switch the BWP by using a bandwidth part indicator field in DCI.

[0090] In the time-frequency domain, the basic unit of a resource is a resource element (RE) 112, which may be represented by an OFDM symbol index and a subcarrier index. A resource block (RB) 108 (or physical resource block (PRB)) may be defined as N.sub.RB 110 number of consecutive subcarriers 110 in the frequency domain. Generally, the minimum transmission unit of data is the RB unit. In an NR system, generally, N.sub.symb may be equal to 14, N.sub.RB may be equal to 12, and N.sub.BW may be proportional to the bandwidth of the system transmission band. A data rate increases in proportion to the number of RBs scheduled to a UE.

[0091] In the NR system, in a case of an FDD system operating the uplink and the downlink by distinguishing them according to frequency, a downlink transmission bandwidth and an uplink transmission bandwidth may be different from each other. A channel bandwidth indicates an RF bandwidth corresponding to the system transmission bandwidth. Table 2 and table 3 show part of a correspondence relationship between a system transmission bandwidth, a subcarrier spacing, and a channel bandwidth defined in the NR system in a frequency band lower than 6 GHz and a frequency band higher than 6 GHz, respectively. For example, an NR system having a 100 MHz channel bandwidth with a 30 kHz subcarrier width is configured by a transmission bandwidth of 273 RBs. Hereinafter, N/A may be a combination of a bandwidth and a subcarrier, which is not supported by the NR system.

TABLE-US-00003 TABLE 2 Configuration of frequency range 1 (FR1) 5 10 15 20 25 30 40 50 60 80 90 100 SCS MHz MHz MHz MHz MHz MHz MHz MHz MHz MHz MHz MHz (kHz) N.sub.RB N.sub.RB N.sub.RB N.sub.RB N.sub.RB N.sub.RB N.sub.RB N.sub.RB N.sub.RB N.sub.RB N.sub.RB N.sub.RB 15 25 52 79 108 133 180 216 270 N/A N/A N/A N/A 30 11 24 38 51 85 78 106 133 182 217 245 273 60 N/A 11 18 24 31 38 51 65  79 107 121 135

TABLE-US-00004 TABLE 3 Configuration of frequency range 2 (FR2) Channel bandwidth Subcarrier 50 100 200 400 BW.sub.Channel [MHz] spacing MHz MHz MHz MHz Transmission  60 kHz 66 132 264 N/A bandwidth 120 kHz 32 66 132 264 configuration N.sub.RB

[0092] In the NR system, the frequency range may be divided into FR1 and FR2 and defined as shown in Table 4 below.

TABLE-US-00005 TABLE 4 Frequency range Corresponding designation frequency range FR1  450 MHz-7125 MHz FR2 24250 MHz-52600 MHz

[0093] In the above, the ranges of FR1 and FR2 may be changed and applied differently. For example, the frequency range of FR1 may be changed and applied from 450 MHz to 6000 MHz.

[0094] Next, a synchronization signal (SS)/PBCH block in 5G will be described.

[0095] The SS/PBCH block may refer to a physical layer channel block including a primary SS (PSS), a secondary SS (SSS), and a PBCH. Specifically, the SS/PBCH block is as follows: [0096] PSS: may serve as a signal for a reference for downlink time/frequency synchronization and provide some information of a cell ID. [0097] SSS: may serve as a reference for downlink time/frequency synchronization, and provide the remaining cell ID information that is not provided by the PSS. In addition, the SSS may serve as a reference signal for demodulation of the PBCH. [0098] PBCH: may provide essential system information required for transmission or reception of a data channel and a control channel of a UE. The essential system information may include search space related control information indicating radio resource mapping information of a control channel, scheduling control information for a separate data channel for transmission of system information, and the like. [0099] SS/PBCH block: the SS/PBCH block may include a combination of a PSS, an SSS, and a PBCH. One or multiple SS/PBCH blocks may be transmitted within 5 ms, and each of the transmitted SS/PBCH blocks may be distinguished by indices.

[0100] The UE may detect the PSS and the SSS in the initial access operation, and may decode the PBCH. The UE may obtain the MIB from the PBCH, and may be configured with the control resource set (CORESET) #0 (which may correspond to the control resource set having the CORESET index of 0) therefrom. The UE may monitor the control resource set #0 under the assumption that a demodulation reference signal (DMRS) transmitted in the selected SS/PBCH block and the control resource set #0 is quasi-co-located (QCLed). The UE may receive system information based on downlink control information transmitted from the control resource set #0. The UE may obtain, from the received system information, configuration information related to a random access channel (RACH) required for initial access. The UE may transmit a physical RACH (PRACH) to the base station by considering the selected SS/PBCH index, and the base station having received the PRACH may obtain information about an SS/PBCH block index selected by the UE. Through this process, the base station may know which block is selected among the SS/PBCH blocks by the UE, and may know that the control resource set #0 associated therewith is monitored. Next, downlink control information (DCI) in a 5G system will be described in detail.

[0101] In the 5G system, scheduling information about uplink data (or physical uplink shared channel (PUSCH) or downlink data (or physical downlink shared channel (PDSCH)) is transmitted from a base station to a UE through DCI. The UE may monitor a fallback DCI format and a non-fallback DCI format with regard to the PUSCH or the PDSCH. The fallback DCI format may include a predefined fixed field between the base station and the UE, and the non-fallback DCI format may include a configurable field. In addition, there are various formats of DCI, and according to each format, whether DCI for power control or DCI for notifying of a slot format indicator (SFI), etc. may be indicated.

[0102] The DCI may be transmitted through a PDCCH which is a physical downlink control channel after performing channel coding and modulation processing thereon. A cyclic redundancy check (CRC) may be attached to a DCI message payload, and the CRC may be scrambled by a radio network temporary identifier (RNTI) corresponding to the identification information of the UE. Depending on the purpose of the DCI message, for example, a UE-specific data transmission, a power adjustment command, or a random access response, different RNTIs may be used. That is, the RNTI is not explicitly transmitted, but is included in a CRC calculation process and then transmitted. When receiving the DCI message transmitted through the PDCCH, the UE may check a CRC by using an assigned RNTI. When a CRC check result is correct, the UE may identify that the corresponding message has been transmitted to the UE. The PDCCH is mapped and transmitted in a control resource set (CORESET) configured for the UE.

[0103] For example, DCI for scheduling a PDSCH for system information (SI) may be scrambled by an SI-RNTI. DCI for scheduling a PDSCH for a random access response (RAR) message may be scrambled by a random access (RA)-RNTI. DCI for scheduling a PDSCH for a paging message may be scrambled by a paging (P)-RNTI. DCI for notifying of a slot format indicator (SFI) may be scrambled by an SFI-RNTI. DCI for notifying of transmit power control (TPC) may be scrambled by a TPC-RNTI. DCI for scheduling UE-specific PDSCH or PUSCH may be scrambled by a cell RNTI (C-RNTI).

[0104] DCI format 0_0 may be used as a fallback DCI for scheduling a PUSCH. Here, a CRC may be scrambled by a C-RNTI. The DCI format 0_0 in which the CRC is scrambled by the C-RNTI may include, for example, pieces of information below.

TABLE-US-00006 TABLE 5 - Identifier for DCI formats - [1] bit  - Frequency domain resource assignment - [[log.sub.1(N.sub.RB.sup.UL,BWP(N.sub.RB.sup.UL,BWP + 1)/2)]] bits  - Time domain resource assignment - X bits  - Frequency hopping flag - 1 bit.  - Modulation and coding scheme - 5 bits  - New data indicator - 1 bit  - Redundancy version - 2 bits  - HARQ process number - 4 bits  - Transmit power control (TPC) command for scheduled PUSCH - [2] bits  - Uplink/supplementary UL (UL/SUL) indicator - 0 or 1 bit

[0105] DCI format 0_1 may be used as a non-fallback DCI for scheduling a PUSCH. Here, a CRC may be scrambled by a C-RNTI. DCI format 0_1 in which the CRC is scrambled by the C-RNTI may include, for example, pieces of information below.

TABLE-US-00007 TABLE 6 - Carrier indicator - 0 or 3 bits - UL/SUL indicator - 0 or 1 bit - Identifier for DCI formats - [1] bits - Bandwidth part indicator - 0, 1 or 2 bits - Frequency domain resource assignment   • For resource allocation type 0, ┌N.sub.RB.sup.UL,BWP / P┐bits   • For resource allocation type 1, ┌log.sub.2(N.sub.RB.sup.UL,BWP(N.sub.RB.sup.UL,BWP +   1)/2┐ bits - Time domain resource assignment -1, 2, 3, or 4 bits - VRB-to-PRB mapping (virtual resource block-to-physical resource block mapping) - 0 or 1 bit, only for resource allocation type 1.   • 0 bit if only resource allocation type 0 is configured;   • 1 bit otherwise. - Frequency hopping flag - 0 or 1 bit, only for resource allocation type 1.   • 0 bit if only resource allocation type 0 is configured.   • 1 bit otherwise. - Modulation and coding scheme - 5 bits - New data indicator - 1 bit - Redundancy version - 2 bits - HARQ process number - 4 bits - 1st downlink assignment index - 1 or 2 bits   • 1 bit for semi-static HARQ-ACK codebook;   • 2 bits for dynamic HARQ-ACK codebook with single HARQ-ACK   codebook. - 2nd downlink assignment index - 0 or 2 bits   • 2 bits for dynamic HARQ-ACK codebook with two HARQ-ACK   sub-codebooks;   • 0 bit otherwise. - TPC command for scheduled PUSCH - 2 bits [00001]$‐\mathrm{SRS}\mathrm{resource}\mathrm{indicator}‐.Math.{\log }_2\left(\underset{k=1}{\overset{L_{\max }}{.Math.}}\left(\begin{array}{c}{N}_{\mathrm{SRS}}\\ k\end{array}\right)\right).Math.\mathrm{or}.Math.{\log }_2\left(N_{\mathrm{SRS}}\right).Math.\mathrm{bits}$   [00002]$\begin{array}{c}.Math.{\log }_2\left(\underset{k=1}{\overset{L_{\max }}{.Math.}}\left(\begin{array}{c}{N}_{\mathrm{SRS}}\\ k\end{array}\right)\right).Math.\mathrm{bits}\mathrm{for}\mathrm{non}‐\mathrm{codebook}\mathrm{based}\mathrm{PUSCH}\\ \mathrm{transmission};\end{array}$   • ┌log.sub.2(N.sub.SRS)┐ bits for codebook based PUSCH transmission. - Precoding information and number of layers -up to 6 bits - Antenna ports - up to 5 bits - SRS request - 2 bits - CSI request - 0, 1, 2, 3, 4, 5, or 6 bits - Code block group (CBG) transmission information - 0, 2, 4, 6, or 8 bits - PTRS-DMRS association (Phase tracking reference signal-demodulation reference signal association)- 0 or 2 bits. - beta_offset indicator - 0 or 2 bits - Demodulation reference signal (DMRS) sequence initialization - 0 or 1 bit
DCI format 1_0 may be used as a fallback DCI for scheduling a PDSCH. Here, a CRC may be scrambled by a C-RNTI. DCI format 1_0 in which the CRC is scrambled by the C-RNTI may include, for example, the following pieces of information below.

TABLE-US-00008 TABLE 7 - Identifier for DCI formats - [1] bit - Frequency domain resource assignment - [[log.sub.2(N.sub.RB   (N.sub.RB  .sub.  +   )/2)]] bits - Time domain resource assignment - X bits - VRB-to-PRB mapping - 1 bit. - Modulation and coding scheme - 5 bits - New data indicator - 1 bit - Redundancy version - 2 bits - HARQ process number - 4 bits - Downlink assignment index - 2 bits - TPC command for scheduled PUCCH - [2] bits - Physical uplink control channel (PUCCH) resource indicator - 3 bits - PDSCH-to-HARQ feedback timing indicator - [3] bits indicates data missing or illegible when filed

[0106] DCI format 1_1 may be used as a non-fallback DCI for scheduling a PDSCH. Here, a CRC may be scrambled by a C-RNTI. DCI format 1_1 in which the CRC is scrambled by the C-RNTI may include, for example, pieces of information below.

TABLE-US-00009 TABLE 8 - Carrier indicator - 0 or 3 bits - Identifier for DCI formats - [1] bits - Bandwidth part indicator - 0, 1 of 2 bits - Frequency domain resource assignment  • For resource allocation type 0, [N.sub.RB.sup.DL,BWP / P] bits  • For resource allocation type 1, [log   (N.sub.RB.sup.DL,BWP(N.sub.RB.sup.DL,BWP + 1)/2)] bits - Time domain resource assignment-1, 2, 3, or 4 bits - VRB-to-PRB mapping - 0 or 1 bit, only for resource allocation type 1.  • 0 bit if only resource allocation type 0 is configured;  • 1 bit otherwise. - Physical resource block (PRB) bundling size indicator - 0 or 1 bit - Rate matching indicator - 0, 1, or 2 bits - ZP CSI-RS trigger (Zero power channel state information reference signal trigger) - 0, 1, or 2 bits For transport block 1: - Modulation and coding scheme - 5 bits - New data indicator - 1 bit - Redundancy version - 2 bits   For transport block 2: - Modulation and coding scheme - 5 bits - New date indicator - 1 bit - Redundancy version - 2 bits - HARQ process number - 4 bits - Downlink assignment index - 0 or 2 or 4 bits - TPC command for scheduledPUCCH - 2 bits - PUCCH resource indicator - 3 bits - PDSCH-to-HARQ_feedback timing indicator - 3 bits - Antenna ports - 4, 5 or 6 bits - Transmission configuration indication - 0 or 3 bits - SRS request - 2 bits - CBG transmission information - 0, 2, 4, 6, or 8 bits - Code block group (CBG) flushing out information - 0 or 1 bit - DMRS sequence initialization - 1 bit indicates data missing or illegible when filed

[0107] Hereinafter, a method of allocating time domain resources for a data channel in a 5G communication system will be described.

[0108] A base station may configure, for a UE, a table for time-domain resource allocation information for a downlink data channel (PDSCH) and an uplink data channel (PUSCH) via higher layer signaling (e.g., RRC signaling). With regard to PDSCH, a table including maxNrofDL-Allocations=16 entries may be configured, and with regard to PUSCH, a table including maxNrofUL-Allocations=16 entries may be configured. The time-domain resource allocation information may include PDCCH-to-PDSCH slot timing (corresponding to a time interval in slot units between a timing at which a PDCCH is received and a timing at which a PDSCH scheduled by the received PDCCH is transmitted, and denoted by K0), PDCCH-to-PUSCH slot timing (corresponding to a time interval in slot units between a timing at which a PDCCH is received and a timing at which a PUSCH scheduled by the received PDCCH is transmitted, and denoted by K2), information on the position and length of a start symbol in which the PDSCH or PUSCH is scheduled within a slot, a mapping type of PDSCH or PUSCH, and the like. For example, information such as [Table 9] and [Table 10] below may be notified of from the base station to the UE.

TABLE-US-00010 TABLE 9    PDSCH-TimeDomainResourceAllocationList information element    PDSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH- TimeDomainResourceAllocation     PDSCH-TimeDomainResourceAllocation ::= SEQUENCE {         k0 INTEGER(0..32) OPTIONAL, -- Need S         (PDCCH-to-PDSCH timing, in units of slot)        mappingType ENUMERATED {typeA, typeB},             (PDSCH mapping type)    startSymbol AndLength          INTEGER (0..127)           (Start symbol and length of PDSCH)                  }

TABLE-US-00011 TABLE 10    PUSCH-TimeDomainResourceAllocation information element    PUSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF PUSCH- TimeDomainResourceAllocation    PUSCH-TimeDomainResourceAllocation := SEQUENCE {        k2 INTEGER(0..32) OPTIONAL, -- Need S        (PDCCH-to-PUSCH timing, in units of slot)       mappingType ENUMERATED {typeA, typeB},            (PUSCH mapping type)        startSymbolAndLength INTEGER (0..127)         (Start symbol and length of PUSCH)                }

[0109] The base station may notify one of the entries in the above-described table representing the time-domain resource allocation information to the UE via L1 signaling (e.g., DCI) (e.g., may be indicated by a “time-domain resource allocation” field in DCI). The UE may acquire time-domain resource allocation information for the PDSCH or PUSCH based on the DCI received from the base station.

[0110] Hereinafter, a downlink control channel in a 5G communication system will be described in more detail with reference to the drawings.

[0111] FIG. 2 illustrates an example of a control resource set in which a downlink control channel is transmitted in a 5G wireless communication system. FIG. 2 illustrates an example in which a UE bandwidth part 210 is configured in a frequency axis and two control resource sets (control resource set #1 201 and control resource set #2 220) are configured in 1 slot 220 in a time domain. The control resource sets 201 and 220 may be configured in a specific frequency resource 203 within the entire UE BWP 210 in the frequency axis. The control resource set may be configured with one or multiple OFDM symbols in the time axis, and this may be defined as a control resource set duration 204. Referring to an example illustrated in FIG. 2, the control resource set #1 201 is configured with the control resource set duration of two symbols, and the control resource set #2 220 is configured with the control resource set duration of one symbol.

[0112] The above described control resource set in the 5G system may be configured for the UE by the base station via higher layer signaling (e.g., system information, master information block (MIB), or radio resource control (RRC) signaling). The configuration of the control resource set for the UE may be understood as providing information such as a control resource set identity, a frequency location of the control resource set, a symbol length of the control resource set, and the like. The higher layer signaling may include, for example, pieces of information of Table 11 below.

TABLE-US-00012 TABLE 11 ControlResourceSet ::= SEQUENCE { Corresponds to L1 parameter ′CORESET-ID′ controlResourceSetId ControlResourceSetId, (control resource set Identity) frequency DomainResources BIT STRING (SIZE (45)), (frequency domain resource allocation information) duration INTEGER (1..maxCoReSetDuration), (time domain resource allocation information) cce-REG-MappingType CHOICE { (CCE-to-REG mapping type) Interleaved SEQUENCE { reg-BundleSize ENUMERATED {n2, n3, n6}, (REG bundle size) precoderGranularity ENUMERATED {sameAsREG-bundle, allContiguousRBs}, interleaverSize ENUMERATED {n2, n3, n6} (interleaver size) shiftIndex INTEGER(0..maxNrofPhysicalResourceBlocks-1) OPTIONAL (interleaver shift (Shift)) }, nonInterleaved NULL }, tci-StatesPDCCH SEQUENCE (SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL, (QCL configuration information) tci-PresentInDCI ENUMERATED {enabled} OPTIONAL, -- Need S }

[0113] In Table 11, tci-StatesPDCCH (simply referred to as transmission configuration indication (TCI) state) configuration information may include information about one or more synchronization signal (SS)/physical broadcast channel (PBCH) block (that is, synchronization signal block (SSB)) indices having a quasi-co-located (QCLed) relationship with a DMRS transmitted in the corresponding control resource set or a channel state information reference signal (CSI-RS) index. For example, each control information included in DCI format 1_1 that is scheduling control information (DL grant) for downlink data may be as follows. [0114] Carrier indicator: indicates on which carrier the data scheduled by DCI is transmitted—0 or 3 bits [0115] Identifier for DCI formats: indicates DCI format, and specifically, is an indicator for distinguishing whether the corresponding DCI is for downlink or uplink.—[1] bits [0116] Bandwidth part indicator: indicates if there is a change in the bandwidth part—0, 1, or 2 bits [0117] Frequency domain resource assignment: is resource allocation information indicating frequency domain resource allocation, and a resource expressed varies depending on whether the resource allocation type is 0 or 1. [0118] Time domain resource assignment: is resource allocation information indicating time domain resource allocation, and may indicate one configuration of a predetermined PDSCH time domain resource allocation list or higher layer signaling—1, 2, 3, or 4 bits [0119] VRB-to-PRB mapping: indicates a mapping relationship between a virtual resource block (VRB) and a physical resource block (PRB)—0 or 1 bit [0120] PRB bundling size indicator: indicates the physical resource block bundling size assuming that the same precoding is applied—0 or 1 bit [0121] Rate matching indicator: indicates a rate match group to be applied, among rate match groups configured via a higher layer applied to the PDSCH—0, 1, or 2 bits [0122] ZP CSI-RS trigger: triggers a zero power channel state information reference signal—0, 1, or 2 bits [0123] Transport block (TB)-related configuration information: indicates a modulation and coding scheme (MCS), a new data indicator (NDI), and a redundancy version (RV) for one or two TBs. [0124] Modulation and coding scheme (MCS): indicates a modulation scheme and a coding rate used for data transmission. That is, MCS may indicate a coding rate value capable of indicating TBS and channel coding information together with information on whether it is QPSK, 16QAM, 64QAM, or 256QAM. [0125] New data indicator: indicates whether HARQ initial transmission or retransmission. [0126] Redundancy version: indicates a redundancy version of HARQ. [0127] HARQ process number: indicates the HARQ process number applied to a PDSCH—4 bits [0128] Downlink assignment index: indicates an index for generating a dynamic HARQ-ACK codebook when reporting HARQ-ACK for PDSCH—0 or 2 or 4 bits [0129] TPC command for scheduled PUCCH: indicates power control information applied to PUCCH for HARQ-ACK report for PDSCH—2 bits [0130] PUCCH resource indicator: is information indicating the resource of PUCCH for HARQ-ACK report for PDSCH—3 bits [0131] PDSCH-to-HARQ_feedback timing indicator: indicates configuration information on which slot the PUCCH for HARQ-ACK report for PDSCH is transmitted—3 bits [0132] Antenna ports: indicates information indicating an antenna port of a PDSCH DMRS and a DMRS CDM group in which the PDSCH is not transmitted—4, 5 or 6 bits [0133] Transmission configuration indication: information indicating beam related information of PDSCH—0 or 3 bits [0134] SRS request: information requesting SRS transmission—2 bits [0135] CBG transmission information: information indicating which code block group (CBG) data is transmitted through a PDSCH when code block group-based retransmission is configured—0, 2, 4, 6, or 8 bits [0136] CBG flushing out information: information indicating whether an earlier received code block group by a UE can be used for HARQ combining—0 or 1 bit [0137] DMRS sequence initialization: indicates the DMRS sequence initialization parameter—1 bit In the above, in a case of data transmission through PDSCH or PUSCH, time domain resource assignment may be performed via information about a slot in which a PDSCH/PUSCH is transmitted, a start symbol position S in the corresponding slot, and the number L of symbols to which the PDSCH/PUSCH is mapped. In the above, S may be a relative position from the start of a slot, L may be the number of consecutive symbols, and S and L may be determined based on a start and length indicator value (SLIV) defined by Equation (1) as follows.

TABLE-US-00013 [Equation 1]   if (L − 1) ≤ 7 then   SLIV = 14 .Math. (L − 1) +S else   SLIV = 14 .Math. (14 − L + 1) + (14 − 1 − S) where 0 < L ≤ 14 − S

[0138] In the NR system, the UE may receive, through RRC configuration, configuration in which an SLIV value, a PDSCH/PUSCH mapping type, and information on a slot in which a PDSCH/PUSCH is transmitted are included in one row (for example, the information may be configured in the form of a table). Subsequently, in the time domain resource assignment of the DCI, by indicating an index value in the table configured as above, a base station may transmit, to a UE, the SLIV value, the PDSCH/PUSCH mapping type, and information on the slot in which the PDSCH/PUSCH is transmitted.

[0139] In the NR system, the PDSCH mapping type is defined by type A and type B. In the PDSCH mapping type A, the first symbol among DMRS symbols is located at the second or the third OFDM symbol in a slot. In the PDSCH mapping type B, the first symbol of DMRS symbol is located at the first OFDM symbol in a time domain resource assigned via PUSCH transmission. The downlink data may be transmitted through a PDSCH serving as a physical channel for downlink data transmission. The PDSCH may be transmitted after a control channel transmission interval, and scheduling information such as a specific mapping position and modulation scheme in the frequency domain is determined based on DCI transmitted through the PDCCH.

[0140] Via an MCS in the control information included in the DCI, a base station may report the modulation scheme applied to a PDSCH to be transmitted to a UE, and the size (transport block size (TBS)) of data to be transmitted. In an embodiment, the MCS may be configured by 5 bits or more or fewer bits. The TBS corresponds to a size before channel coding for error correction is applied to data (transport block, TB) to be transmitted by a base station.

[0141] In the disclosure, a transport block (TB) may include a medium access control (MAC) header, a MAC control element (CE), one or more MAC service data units (SDUs), and padding bits. Alternatively, the TB may indicate the unit of data, which is dropped from a MAC layer to a physical layer, or a MAC protocol data unit (MAP PDU).

[0142] The modulation scheme supported by the NR system are quadrature phase shift keying (QPSK), 16 quadrature amplitude modulation (16 QAM), 64 QAM, and 256 QAM. Modulation orders (Qm) of the QPSK, 16 QAM, 64 QAM, and 256 QAM correspond to 2, 4, 6, and 8, respectively. That is, 2 bits per symbol in a case of QPSK modulation, 4 bits per symbol in a case of 16 QAM modulation, 6 bits per symbol in a case of 64 QAM modulation, and 8 bits per symbol in a case of 256 QAM modulation may be transmitted.

[0143] FIGS. 3 and 4 illustrate an example in which pieces of data for eMBB, URLLC, and mMTC, which are services considered in the 5G or NR system, are allocated in frequency-time resources. Referring to FIGS. 3 and 4, there may be identified a scheme in which frequency and time resources are allocated for performing information transmission in each system.

[0144] FIG. 3 illustrates an example in which eMBB, URLLC, and mMTC data are allocated in the entire system frequency bandwidth. First, FIG. 3 illustrates an aspect in which eMBB, URLLC, and mMTC data are allocated in the entire system frequency bandwidth 300. In the middle of allocation and transmission of eMBB 301 and mMTC 309 in a specific frequency bandwidth, if URLLC data 303, 305, and 307 occur and transmission thereof is thus necessary, the URLLC data 303, 305, and 307 may be transmitted without emptying the portion in which the eMBB 301 and the mMTC 309 have been already allocated and without transmitting the same. Since the URLLC needs to reduce a latency in the middle of service, URLLC data 303, 305, and 307 may be allocated to a portion of the resource 301 to which the eMBB is allocated, and thus may be transmitted. In a case where URLLC is additionally allocated and transmitted in the resource to which the eMBB is allocated, eMBB data may not be transmitted in an overlapping frequency-time resource, and accordingly, the transmission performance of the eMBB data may be lowered. That is, in the above case, eMBB data transmission failure due to URLLC allocation may occur. FIG. 4 illustrates an example in which the system frequency bandwidth is divided and eMBB, URLLC, and mMTC data are allocated to the divided frequency band. In FIG. 4, the entire system frequency bandwidth 400 may be divided into sub-bands 402, 404, and 406 and used for transmission of a service and data. Information associated with the sub-band configuration may be predetermined, and the information may be transmitted to a UE by a base station via higher layer signaling. Alternatively, the sub-bands may be randomly divided by a base station or a network node and services may be provided to the UE without transmitting separate sub-band configuration information. FIG. 4 illustrates that the sub-band 402 is used for eMBB data transmission, the sub-band 404 is used for URLLC data transmission, and the sub-band 406 is used for mMTC data transmission.

[0145] In order to explain a method and apparatus proposed in the embodiment, the terms “physical channel” and “signal”, pertaining to the NR system may be used. However, details of the embodiment may be applied to a wireless communication system other than the NR system. Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings. In addition, in the description of the disclosure, if it is determined that a detailed description of a related function or configuration may unnecessarily obscure the subject matter of the disclosure, the detailed description thereof will be omitted. In addition, the terms to be described later are terms defined considering functions in the disclosure, which may vary according to intentions or customs of users and operators. Therefore, the definition should be made based on the content throughout this specification.

[0146] In the disclosure, a downlink (DL) refers to a wireless transmission path of a signal to be transmitted from a base station to a UE, and an uplink (UL) refers to a wireless transmission path of a signal to be transmitted from a UE to a BS.

[0147] Although the NR system is described as an example in the following description, embodiments of the disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. Furthermore, the embodiments of the disclosure may also be applied to other communication systems through partial modification without greatly departing from the scope of the disclosure based on determination by one of ordinary skill in the art.

[0148] In the disclosure, legacy terms of a physical channel and a signal may be interchangeably used with data or a control signal. For example, a PDSCH refers to a physical channel via which data is transmitted, but in the disclosure, the PDSCH may refer to data.

[0149] Hereinafter, in the disclosure, higher layer signaling refers to a method of transmitting a signal from a base station to a UE by using a DL data channel of a physical layer or transmitting a signal from the UE to the BS by using a UL data channel of a physical channel, and may also be referred to as RRC signaling or a MAC control element (MAC CE).

[0150] FIG. 5 illustrates an example of a procedure in which one transport block is divided into a plurality of code blocks and a CRC is added thereto.

[0151] Referring to FIG. 5, a CRC 503 may be added to the last or first part of one transport block (TB) 501 to be transmitted in an uplink or downlink transmission. The CRC 503 may have 16 bits, 25 bits, a previously fixed number of bits, or a variable number of bits depending on a channel condition, and may be used to determine whether channel coding is successful. A block including the TB 501 and the CRC 503 added thereto may be divided into a plurality of code blocks (CBs) 507, 509, 511, and 513 (indicated by reference numeral 505). Here, the CBs may be divided while having the predetermined maximum size, and in this case, the last CB 513 may be smaller than the other CBs 507, 509, and 511. However, this is only an example and according to another example, the last CB 513 may have the same length as those of the other CBs 507, 509, and 511 by inserting 0, 1, or any other random value to the last CB 513.

[0152] In addition, CRCs 517, 519, 521, and 523 may be respectively added to the CBs 507, 509, 511, and 513 (indicated by reference numeral 515). A CRC may have 16 bits, 24 bits, or a prefixed number of bits, and may be used in determination of whether channel coding is successful.

[0153] The TB 501 and cyclic generator polynomial may be used to generate the CRC 503, and the cyclic generator polynomial may be defined in various ways. For example, assuming that cyclic generator polynomial for a 24-bit CRC is gCRC24A(D)=D.sup.24+D.sup.23+D.sup.18+D.sup.17+D.sup.14+D.sup.11+D.sup.10+D.sup.7+D.sup.6+D.sup.5+D.sup.4+D.sup.3+D+1, and L=24, for TB data a.sub.0, a.sub.1, a.sub.2, . . . , a.sub.A-1, CRC p.sub.0, p.sub.1, p.sub.2, . . . , p.sub.L-1 may be determined to be a value with a remainder of 0 which is obtained by dividing a.sub.0D.sup.A+23+a.sub.2D.sup.A+22+ . . . +a.sub.A-1D.sup.24+p.sub.0D.sup.23+p.sub.1D.sup.22+ . . . +p.sub.22D.sup.1+p.sub.23 by gCRC24A(D). In the above example, it has been described assuming that the CRC length L is 24 as an example, but a CRC length L may be determined to be any of various lengths including 12, 16, 24, 32, 40, 48, 64, or the like.

[0154] After a CRC is added to a TB in the above procedure, the TB+CRC may be divided into N CBs 507, 509, 511, and 513. The CRC 517, 519, 521, and 523 may be respectively added to the divided CBs 507, 509, 511, and 513 (indicated by reference numeral 515). Compared to the CRC added to the TB, a CRC added to a CB may have a different length or different cyclic generator polynomial may be used to generate the CRC. In addition, the CRC 503 added to the TB, and the CRC 517, 519, 521, and 523 added to the CBs may be omitted according to a type of a channel code to be applied to a CB. For example, when an LDPC code, not a turbo code, is to be applied to the CBs, the CRCs 517, 519, 521, and 523 to be added to the CBs respectively may be omitted. However, even when the LDPC is applied, the CRCs 517, 519, 521, and 523 may be added as they are to the CBs. In addition, when a polar code is used, a CRC may be added or omitted.

[0155] As described above with reference to FIG. 5, a maximum length of one CB may be determined according to a type of channel coding to be applied, and a TB to be transmitted and a CRC to be added to the TB may be divided into a plurality of CBs according to the maximum length of the CB.

[0156] In the LTE system, a CRC for CB is added to a divided CB, and a data bit of the CB and the CRC are encoded with a channel code to determine coded bits, and each of the coded bits is rate matched in a predefined manner such that a bit number may be determined.

[0157] In the NR system, a TB size (TBS) may be calculated through processes below.

[0158] Stage 1: N′RE that is the number of REs per one PRB, which is allocated to PDSCH mapping in an allocated resource. N′.sub.RE may be calculated as N.sub.sc.sup.RB.Math.N.sub.symb.sup.sh−N.sub.DMRS.sup.PRB−N.sub.oh.sup.PRB. Here, N.sub.sc.sup.RB is 12, and N.sub.symb.sup.sh may indicate the number of OFDM symbols allocated to a PDSCH. N.sub.DMRS.sup.PRB indicates the number of REs per one PRB, which is occupied by a DMRS of a same CDM group. N.sub.oh.sup.PRB indicates the number of REs per one PRB, which is occupied by an overhead configured by higher layer signaling, and may be configured to be one of 0, 6, 12, and 18. Thereafter, N.sub.RE that is a total number of REs allocated to the PDSCH may be calculated. N.sub.RE is calculated as min(156, N′.sub.RE).Math.n.sub.PRB, and n.sub.PRB indicates the number of PRBs allocated to the UE.

[0159] Stage 2: N.sub.info that is temporary information bits may be calculated as N.sub.RE.Math.R.Math.Q.sub.m.Math.ν. Here, R indicates a code rate, Q.sub.m indicates a modulation order, and information of the value may be delivered by using a table predefined with a MCS bit field of DCI. In addition, v indicates the number of allocated layers. If N.sub.info≤3824, TBS may be calculated through Stage 3 below. Otherwise, TBS may be calculated through Stage 4.

[0160] Stage 3: N′.sub.info may be calculated by using equations of

[00003]$N_{\mathrm{info}}^{\prime }=\max \left(24,2^n.Math..Math.\frac{N_{\mathrm{info}}}{2^n}.Math.\right)$

and n=max(3, └ log.sub.2(N.sub.info)┘−6) TBS may be determined as a value closest to N′.sub.info from among values in Table 12 below that are not smaller than N′.sub.info.

TABLE-US-00014 TABLE 12 Index TBS 1 24 2 32 3 40 4 48 5 56 6 64 7 72 8 80 9 88 10 96 11 104 12 112 13 120 14 128 15 136 16 144 17 152 18 160 19 168 20 176 21 184 22 192 23 208 24 224 25 240 26 256 27 272 28 288 29 304 30 320 31 336 32 352 33 368 34 384 35 408 36 432 37 456 38 480 39 504 40 528 41 552 42 576 43 608 44 640 45 672 46 704 47 736 48 768 49 808 50 848 51 888 52 928 53 984 54 1032 55 1064 56 1128 57 1160 58 1192 59 1224 60 1256 61 1288 62 1320 63 1352 64 1416 65 1480 66 1544 67 1608 68 1672 69 1736 70 1800 71 1864 72 1928 73 2024 74 2088 75 2152 76 2216 77 2280 78 2408 79 2472 80 2536 81 2600 82 2664 83 2728 84 2792 85 2856 86 2976 87 3104 88 3240 89 3368 90 3496 91 3624 92 3752 93 3824

[0161] Stage 4: N′.sub.info may be calculated by using equations of

[00004]$N_{\mathrm{info}}^{\prime }=\max \left(3840,2^n\times \mathrm{round}\left(\frac{N_{\mathrm{info}}-24}{2^n}\right)\right)$

and n=└ log.sub.2(N.sub.info)−24)┘−5. TBS may be determined based on a value of N′.sub.info and [pseudo-code 1] below. C below corresponds to the number of code blocks included in one TB.

TABLE-US-00015 [Pseudo-code 1 Start]  if R≤1/4    [00005]$\mathrm{TBS}=8*C*.Math.\frac{N_{\mathrm{info}}^{\prime }+24}{8*C}.Math.-24,\mathrm{where}C=.Math.\frac{N_{\mathrm{info}}^{\prime }+24}{3816}.Math.$   else    if N.sub.info′ > 8424     [00006]$\mathrm{TBS}=8*C*.Math.\frac{N_{\mathrm{info}}^{\prime }+24}{8*C}.Math.-24,\mathrm{where}C=.Math.\frac{N_{\mathrm{info}}^{\prime }+24}{8424}.Math.$    else     [00007]$\mathrm{TBS}=8*.Math.\frac{N_{\mathrm{info}}^{\prime }+24}{8}.Math.-24$    end if   end if [Pseudo-code 1 End]

[0162] In the NR system, when one CB is input to an LDPC encoder, the CB may be output with parity bits added thereto. Here, an amount of parity bits may vary according to an LDCP base graph. With respect to a particular input, a method by which all parity bits generated by LDPC coding are transmitted may be referred to as full buffer rate matching (FBRM), and a method by which the number of transmittable parity bits is limited may be referred to as limited buffer rate matching (LBRM). When a resource is allocated for data transmission, an output of an LDPC encoder is generated as a circular buffer, and bits of the generated buffer are transmitted repeatedly as much as the allocated resource, and a length of the circular buffer may be N.sub.cb.

[0163] When the number of all parity bits generated by LDPC coding is N, N.sub.cb=N in the FBRM scheme. In the LBRM, N.sub.cb=min(N, N.sub.ref), N.sub.ref is given by

[00008]$.Math.\frac{{\mathrm{TBS}}_{\mathrm{LBRM}}}{C.Math.R_{\mathrm{LBRM}}}.Math.,$

and R.sub.LBRM may be determined as 2/3. In order to obtain TBS.sub.LBRM, the aforementioned method of calculating TBS is used, whereas the calculation may be performed based on assumption of a maximum number of layers and a maximum modulation order which are supported by a UE in a corresponding cell. When MCS Table for supporting 256QAM is configured to be used for at least one BWP in a corresponding cell, a maximum modulation order Q.sub.m may be assumed to be 8, and when the MCS table above is not configured to be used, the maximum modulation order Q.sub.m may be assumed to be 6 (64QAM), a code rate may be assumed to be 948/1024 that is a maximum code rate, N.sub.RE may be assumed to be 156.Math.n.sub.PRB, and n.sub.PRB may be assumed to be n.sub.PRB,LBRM. n.sub.PRB,LBRM may be given in Table 13 below.

TABLE-US-00016 TABLE 13 Maximum number of PRBs across all configured BWPs of a carrier n.sub.PRB,LBRM Less than 33 32 33 to 66 66  67 to 107 107 108 to 135 135 136 to 162 162 163 to 217 217 Larger than 217 273

[0164] In the NR system, a maximum data rate supported by the UE may be determined by using Equation 2 below.

[00009]$\begin{array}{cc}\mathrm{data}\mathrm{rate}\left(\mathrm{in}\mathrm{Mbps}\right)={10}^{-6}.Math.\underset{j=1}{\overset{J}{.Math.}}\left(v_{\mathrm{Layers}}^{\left(j\right)}.Math.Q_m^{\left(j\right)}.Math.f^{\left(j\right)}.Math.R_{\max }.Math.\frac{N_{\mathrm{PRB}}^{\mathrm{BW}\left(j\right)\mu }}{T_s^{\mu }}.Math.\left(1-{\mathrm{OH}}^{\left(j\right)}\right)\right)& \left[\mathrm{Equation}3\right]\end{array}$

[0165] In Equation 2, J may indicate the number of carriers grouped due to carrier aggregation (CA), R.sub.max=948/1024, ν.sub.Layers.sup.(j) n may indicate a maximum number of layers, Q.sub.m.sup.(j) may indicate a maximum modulation order, f.sup.(j) may indicate a scaling index, and p may indicate a subcarrier spacing. The UE may report one value among 1, 0.8, 0.75, and 0.4 as f.sup.(j), and μ may be given in Table 14 below.

TABLE-US-00017 TABLE 14 μ Δƒ = 2.sup.μ .Math. 15[kHz] Cyclic prefix 0 15 Normal 1 30 Normal 2 60 Normal, Extended 3 120 Normal 4 240 Normal

[0166] In addition, Y.sub.s.sup.μ indicates an average OFDM symbol length, T.sub.s.sup.μ may be calculated by

[00010]$\frac{{10}^{-3}}{14.Math.2^{\mu }},$

and N.sub.PRB.sup.BW(j),μ indicates a maximum number of RBs in BW(j). OH.sup.(j) indicates an overhead value which may be given as 0.14 in a DL of FR1 (a band equal to or less than 6 GHz) and as 0.18 in an UL, and may be given as 0.08 in a DL of FR2 (a band greater than 6 GHz) and as 0.10 in an UL. A maximum data rate in a DL in a cell having a frequency bandwidth of 100 MHz in 30 kHz subcarrier spacing may be calculated as Table 15 below by using Equation 2.

TABLE-US-00018 TABLE 15 Q Rmax N T O data rate 1 4 8 0.92578125 273 3.57143E−05 0.14 2337.0 0.8 4 8 0.92578125 273 3.57143E−05 0.14 1869.6 0.75 4 8 0.92578125 273 3.57143E−05 0.14 1752.8 0.4 4 8 0.92578125 273 3.57143E−05 0.14  934.8 indicates data missing or illegible when filed

[0167] On the other hand, an actual data rate of actual data transmission which can be measured by the UE may be a value obtained by dividing a data amount by a data transmission time. This may correspond to a value which is TBS in 1 TB transmission or a value which is obtained by dividing a sum of TBS by a TTI length in 2 TB transmission. For example, according to assumption with respect to calculation of Table 15, a maximum actual data rate in a DL in a cell having a frequency bandwidth of 100 MHz in 30 kHz subcarrier spacing may be determined according to the number of allocated PDSCH symbols, as in Table 16 below.

TABLE-US-00019 TABLE 16 TTI data length rate N N.sub.DMRS.sup.PRB N.sub.RR N.sub.RE N.sub.info n N.sub.info C TBS (ms) (Mbps) 3 8 28 7644 226453.5 12 225,280 27 225,480 0.107143 2,101.48 4 8 40 10920 323505.0 13 319,488 38 319,784 0.142857 2,238.49 5 8 52 14196 420556.5 13 417,792 50 417,976 0.178571 2,340.67 6 8 64 17472 517608.0 13 516,096 62 516,312 0.214286 2,409.46 7 8 76 20748 614659.5 14 622,592 74 622,760 0.250000 2,491.04 8 8 88 24024 711711.0 14 704,512 84 704,904 0.285714 2,467.16 9 8 100 27300 808762.5 14 802,816 96 803,304 0.321429 2,499.17 10 8 112 30576 905814.0 14 901,120 107 901,344 0.357143 2,523.76 11 8 124 33852 1002865.3 14 999,424 119 999,576 0.392857 2,544.38 12 8 136 37128 1099917.0 15 1,114,112 133 1,115,048 0.428571 2,601.78 13 8 148 40404 1196968.5 15 1,212,416 144 1,213,032 0.461286 2,612.68 14 8 160 43680 1294020.0 15 1,277,952 152 1,277,992 0.500000 2,555.98 indicates data missing or illegible when filed

[0168] A maximum data rate supported by the UE may be identified based on Table 15, and an actual data rate following allocated TBS may be identified via Table 16. Here, there may be a case where an actual data rate is greater than a maximum data rate according to scheduling information. In a wireless communication system, particularly, in the NR system, a data rate the UE can support may be defined between the base station and the UE. The data rate may be calculated by using a maximum frequency band, a maximum modulation order, a maximum number of layers, and the like which are supported by the UE. However, the calculated data rate may be different from a value calculated from a transport block size (TBS) of a transport block (TB) and a length of a transmission time interval (TTI) which are used in actual data transmission.

[0169] Accordingly, the UE may be allocated a TBS being greater than a value corresponding to a data rate the UE supports, and in order to prevent this, there may be restriction of scheduling of TBS according to the data rate the UE supports.

[0170] FIG. 6 illustrates an aspect in which a synchronization signal (SS) and a physical broadcast channel (PBCH) in the NR system are mapped to frequency and time domains.

[0171] A primary synchronization signal (PSS) 601, a secondary synchronization signal (SSS) 603, and a PBCH are mapped to 4 OFDM symbols, the PSS and the SSS are mapped to 12 RBs, and the PBCH is mapped to 20 RBs. Table in FIG. 6 illustrates how a frequency band of 20 RBs is changed according to subcarrier spacings (SCSs). A resource region on which a PSS, an SSS, and a PBCH are transmitted may be referred to as an SS/PBCH block. In addition, the SS/PBCH block may be referred to as an SSB block.

[0172] FIG. 7 illustrates symbols on which an SS/PBCH block can be transmitted according to a subcarrier spacing.

[0173] Referring to FIG. 7, a subcarrier spacing may be configured as 15 kHz, 30 kHz, 120 kHz, 240 kHz, and the like, and a position of a symbol on which an SS/PBCH block (or an SSB block) can be located may be determined according to each subcarrier spacing. FIG. 7 illustrates positions of symbols on which an SSB block may be transmitted according to a subcarrier spacing from among symbols within 1 ms, and it is not always necessary to transmit the SSB block in a region shown in FIG. 7. A position in which the SSB block is transmitted may be configured for the UE by system information or dedicated signaling.

[0174] In general, the UE is distant from the base station, and thus, a signal transmitted from the UE may be received by the base station after a propagation delay. The propagation delay refers to a value obtained by dividing, by a speed of light, a path on which a radio wave is delivered from the UE to the base station, and in general, the propagation delay may refer to a value obtained by dividing a distance between the UE and the base station by a speed of light. In an embodiment, in a case of a UE located at a place being distant by 100 km from the base station, a signal transmitted from the UE is received by the base station after 0.34 msec. On the other hand, a signal transmitted from the base station is received by the UE after 0.34 msec. As described above, a time a signal transmitted from a UE reaches a base station may vary according to a distance between the UE and the base station. Therefore, when a plurality of UEs located at different places simultaneously transmit signals, a time the signals reach a base station may vary. In order to allow the signals transmitted from the plurality of UEs to simultaneously reach the base station by solving this problem, a time in which a UE transmits a UL signal may be different for each of the UEs according to locations thereof. In the 5G, NR, and LTE systems, this is referred to as a timing advance.

[0175] FIG. 8 illustrates UE processing time according to a timing advance when a UE receives a first signal and transmits a second signal in response thereto, in the 5G or NR system according to the disclosed embodiment.

[0176] Hereinafter, UE processing time according to a timing advance is described in detail. When a base station transmits UL scheduling grant (UL grant) or DL control signal and data (DL grant and DL data) to a UE in a slot n 802, the UE may receive the UL grant or the DL control signal and data in a slot n 804. Here, the UE may receive a signal after a propagation delay (T.sub.p) 810, compared to a time when the base station has transmitted the signal. In the embodiment of the disclosure, when the UE receives a first signal in the slot n 804, the UE transmits a second signal corresponding thereto in a slot (n+4) 806. When the UE transmits a signal to the base station, in order to make the signal arrive at the base station at a particular time, the UE may transmit HARQ ACK/NACK with respect to UL data or DL data on a timing 806 advanced by a timing advance (TA) 812 before a slot (n+4), in which the UE has received a reference signal. Therefore, in the embodiment of the disclosure, a time in which the UE can receive UL grant and transmit UL data or receive DL data and prepare to deliver HARQ ACK or NACK may be a time corresponding to 3 slots excluding a TA (indicated by reference numeral 814).

[0177] In order to determine the aforementioned timing, the base station may calculate an absolute value of the TA of the UE. The base station may calculate the absolute value of the TA by adding or subtracting variation in a value of the TA, which is delivered by higher layer signaling, to or from a value of the TA which is first delivered to the UE in a random access procedure when the UE initially accesses. In the disclosure, the absolute value of the TA may correspond to a value obtained by subtracting a start time of an n-th TTI the UE receives from a start time of an n-th TTI the UE transmits.

[0178] One of important references of performance of a cellular wireless communication system is packet data latency. To this end, in an LTE system, transmission and reception of a signal are performed in units of a subframe having a transmission time interval (TTI) of 1 ms. The LTE system operating in the above described manner may support a UE (a short-TTI UE) having a shorter TTI than 1 ms. In the 5G or NR system, a TTI may be shorter than 1 ms. The short-TTI UE is appropriate for a voice over LTE (VoLTE) service or a service such as a remote control, for which latency is important. In addition, the short-TTI UE may be an entity capable of implementing mission-critical IoT on a cellular communication base.

[0179] In the 5G or NR system, when the base station transmits a PDSCH including DL data, DCI for scheduling the PDSCH may indicate a K1 value corresponding to timing information by which the UE transmits HARQ-ACK information of the PDSCH. In a case where it is not indicated that the HARQ-ACK information including a timing advance is to be transmitted earlier than symbol L1, the HARQ-ACK information including a timing advance may be transmitted from the UE. That is, the HARQ-ACK information including a timing advance may be transmitted to the base station at a point of time equal to or after the symbol L1. In a case where it is indicated that the HARQ-ACK information including a timing advance is to be transmitted earlier than the symbol L1, the HARQ-ACK information may not be valid HARQ-ACK information in HARQ-ACK transmission from the UE to the base station.

[0180] The symbol L1 may be a first symbol on which a cyclic prefix (CP) starts after T.sub.proc,1 from a last point of time of the PDSCH. T.sub.proc,1 may be calculated by using Equation 3 below.

T.sub.proc,1=((N.sub.1+d.sub.1,1+d.sub.1,2)(2048+144).Math.κ2.sup.−μ).Math.T.sub.C  [Equation 3]

[0181] In Equation 3 described above, N.sub.1, d.sub.1,1, d.sub.1,2, κ, μ, and T.sub.C may be defined as below. [0182] When HARQ-ACK information is transmitted via a PUCCH (a UL control channel), d.sub.1,1=0, and when the HARQ-ACK information is transmitted via a PUSCH (a UL shared channel or data channel), d.sub.1,1=1. [0183] In a case where the UE is configured with a plurality of activated configuration carriers or carriers, a maximum timing difference between the carriers may be reflected on second signal transmission. [0184] In a case of a PDSCH mapping type A, i.e., in a case where a first DMRS symbol position is a third or fourth symbol of a slot, when a position index i of a last symbol of a PDSCH is smaller than 7, it is defined that d.sub.1,2=7-i. [0185] In a case of a PDSCH mapping type B, i.e., in a case where a first DMRS symbol position is a first symbol of a PDSCH, when a length of the PDSCH is 4 symbols, d.sub.1,2=3, and when a length of the PDSCH is 2 symbols, d.sub.1,2=3+d, where d refers to the number of symbols over which a PDCCH including the PDSCH and a control signal for scheduling the PDSCH is overlapped. [0186] N.sub.1 is defined as in Table 17 below according to μ. μ=0, 1, 2, 3 respectively indicate subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz.

TABLE-US-00020 TABLE 17 PDSCH.Math.decoding.Math.time.Math.N.sub.1.Math.[symbols]  No.Math.additional.Math.PDSCH.Math.DM-  Additional.Math.PDSCH.Math.DM-RS  μ  RS.Math.configured  configured  0   8  13  1  10  13  2  17  20  3  20  24  [0187] A value of N.sub.1 which is provided in Table 17 described above may be different values according to UE capabilities. [0188] T.sub.c=1/(Δf.sub.max.Math.N.sub.f), Δf.sub.max=480.Math.10.sup.3 Hz, N.sub.f=4096, κ=T.sub.s/T.sub.c=64, T.sub.s=1/(Δf.sub.ref.Math.N.sub.f,ref), Δf.sub.ref=15.Math.10.sup.3 Hz, N.sub.f,ref=2048 are defined, respectively.

[0189] Further, in the 5G or NR system, when the base station transmits control information including UL grant, the base station may indicate a K2 value corresponding to timing information by which the UE transmits UL data or a PUSCH.

[0190] In a case where it is not indicated that the PUSCH including a timing advance is to be transmitted earlier than a symbol L2, the PUSCH including a timing advance may be transmitted from the UE to the base station. That is, the PUSCH including a timing advance may be transmitted from the UE to the base station at a point of time equal to or after the symbol L2. In a case where it is indicated that the PUSCH including a timing advance is to be transmitted earlier than the symbol L2, the UE may ignore UL grant control information from the base station.

[0191] The symbol L2 may be a first symbol on which a CP of a PUSCH symbol which has to be transmitted after T.sub.proc,2 from a last point of time of a PDCCH including scheduling grant is started. T.sub.proc,2 may be calculated by using Equation 4 below.

T.sub.proc,2=((N.sub.2+d.sub.2,1)(2048+144).Math.K2.sup.−μ).Math.T.sub.C  [Equation 4]

[0192] In Equation 4 described above, N.sub.2, d.sub.2,1, κ, μ, and T.sub.C may be defined as below. [0193] In a case where a first symbol among symbols allocated to a PUSCH includes only a DMRS, d.sub.2,1=0, and except for the case, d.sub.2,1=1. [0194] In a case where the UE is configured with a plurality of activated configuration carriers or carriers, a maximum timing difference between the carriers may be reflected on second signal transmission. [0195] N.sub.2 is defined as in Table 18 below according to μ. μ=0, 1, 2, 3 respectively indicate subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz.

TABLE-US-00021 TABLE 18 PUSCH.Math.preparation.Math.time.Math.N.sub.2.Math. μ  [symbols]  0  10  1  12  2  23  3  36  [0196] A value of N.sub.2 which is provided in Table 18 described above may be different values according to UE capabilities. [0197] T.sub.c=1/(Δf.sub.max.Math.N.sub.f), Δf.sub.max=480.Math.10.sup.3 Hz, N.sub.f=4096, κ=T.sub.s/T.sub.c=64 T.sub.s=1/(Δf.sub.ref.Math.N.sub.f,ref), Δf.sub.ref=15.Math.10.sup.3 Hz, N.sub.f,ref=2048 are respectively define, as above.

[0198] On the other hand, the 5G or NR system may configure a bandwidth part (BWP) within one carrier so as to allow a particular UE to perform transmission and reception within the configured BWP. This may be performed to reduce power consumption of the UE. The BS may configure a plurality of BWPs, and may change an activated BWP in control information. A period of time allowed for the UE to switch a BWP may be defined as in Table 19 below.

TABLE-US-00022 TABLE 19 Frequency.Math.Range  Scenario  Type.Math.1.Math.delay.Math.(us)  Type.Math.2.Math.delay.Math.(us)  1  1  600  2000  2  600  2000  3  600  2000  4  400   950  2  1  600  2000  2  600  2000  3  600  2000  4  400   950 

[0199] In Table 19, frequency range 1 refers to a frequency band equal to or less than 6 GHz, and frequency range 2 refers to a frequency band greater than 6 GHz. In the above escribed embodiment of the disclosure, type 1 and type 2 may be determined according to UE capabilities. In the above-described embodiment of the disclosure, scenarios 1, 2, 3, and 4 may be given as in Table 20 below.

TABLE-US-00023 TABLE 20 Center.Math.frequency.Math. Center.Math. frequency.Math. is is.Math.changeable  unchangeable  Frequency.Math. bandwidth.Math. is Scenario.Math.3  Scenario.Math.2  changeable  Frequency.Math. bandwidth.Math. is Scenario.Math.1  scenario.Math.4.Math.in.Math.case.Math.of.Math.changing unchangeable  in.Math.subcarrier.Math.spacing  indicates data missing or illegible when filed

[0200] FIG. 9 illustrates an example in which a base station schedules pieces of data (e.g., TBs) according to slots and transmits the data, receives HARQ-ACK feedback with respect to the data, and performs retransmission, in response to the feedback. Referring to FIG. 9, TB1 900 is initially transmitted in slot 0 902, and ACK/NACK feedback 904 in response thereto is transmitted in slot 4906. If initial transmission of TB1 is failed and NACK is received, retransmission of TB1 may be performed in slot 8 908 (indicated by reference numeral 910). A time when ACK/NACK feedback is transmitted and a time when retransmission is performed may be predetermined, or may be determined according to control information and/or a value indicated by higher layer signaling.

[0201] FIG. 9 illustrates an example in which TB1 to TB8 are sequentially scheduled to slots starting from slot 0 and are transmitted. This may correspond to, for example, a case where HARQ process IDs 0 to 7 are respectively allocated to TB1 to TB8 and TB1 to TB8 are transmitted. If the number of HARQ process IDs the base station and the UE can use is only 4, sequential transmission of 8 different TBs may not be performed.

[0202] FIG. 10 illustrates an example of a communication system using a satellite. For example, when a terminal 1001 transmits a signal to a satellite 1003, the satellite 1003 transfers the signal to a base station 1005, and the base station 1005 processes the received signal and transmits a signal including a request for a subsequent operation thereto to the terminal 1001, which may be transmitted again through the satellite 1003. In the above, since a distance is long between the terminal 1001 and the satellite 1003, and a distance is also long between the satellite 1003 and the base station 1005, a timing required for data transmission or reception between the terminal 1001 and the base station 1005 becomes longer.

[0203] FIG. 11 illustrates a period in which a communication satellite revolves around the Earth according to an altitude or height of the satellite. Satellites for communication may be classified into low Earth orbit (LEO), middle Earth orbit (MEO), geostationary Earth orbit (GEO) satellites, and the like according to the orbit of the satellite. In general, a GEO 1100 refers to a satellite of approximately 36000 km in altitude, an MEO 1110 refers to a satellite of an altitude of 5000 to 15000 km, and the LEO refers to a satellite of an altitude of 500 to 1000 km. A period in which the satellite revolves around the Earth varies according to each altitude. In a case of the GEO 1100, a period in which the GEO satellite revolves around the Earth is about 24 hours, the MEO 1110 has the orbital period of about 6 hours, and the LEO 1130 has the orbital period about 90 to 120 minutes. Due to relatively low altitude, low orbit (2,000 km or lower) satellites have advantages in propagation delay and loss compared to geostationary (36,000 km) satellites.

[0204] FIG. 12 illustrates a conceptual diagram of satellite-to-terminal direct communication. A satellite 1200, which is located at the altitude of 100 km or higher by the rocket, transmits or receives a signal to or from a terrestrial terminal 1210, and also transmits or receives a signal to or from a ground station 1220 connected to a terrestrial base station (DU farms) 1230.

[0205] FIG. 13 illustrates a utilization scenario of satellite-terminal direct communication. Satellite-terminal direct communication can support a communication service for specialized purposes in the form of supplementing the coverage limit of the terrestrial network. For example, by implementing the satellite-terminal direct communication function in a user terminal, transmission and reception of the user's emergency rescue and/or disaster signals in places that are not covered by the terrestrial network communication are possible (indicated by reference numeral 1300), a mobile communication service can be provided to a user in an area where terrestrial network communication is impossible, such as a ship and/or an air (indicated by reference numeral 1310), and the location of ships, trucks, and/or drones can be tracked and controlled in real time without border restrictions (indicated by reference numeral 1320). In addition, by supporting the satellite communication function for a base station, it is possible to use the satellite communication to function as a backhaul of the base station and perform the backhaul function when physically distant (indicated by reference numeral 1330).

[0206] FIG. 14 illustrates an example of calculating an expected data rate (throughput) in an uplink when an LEO satellite at the altitude of 1200 km and a terrestrial terminal perform direct communication. In the uplink, when the transmission effective isotropic radiated power (EIRP) of the terrestrial terminal is 23 dBm, the path loss of the radio channel to the satellite is 169.8 dB, and the satellite reception antenna gain is 30 dBi, the achievable signal-to-noise ratio (SNR) is estimated to be −2.63 dB. Here, the path loss may include a path loss in free space, a loss in the atmosphere, and the like. When a signal-to-interference ratio (SIR) is assumed to be 2 dB, the signal-to-interference and noise ratio (SINR) is calculated as −3.92 dB, and here when using subcarrier spacing of 30 kHz and frequency resources of 1 PRB, it may be possible to achieve a transmission rate of 112 kbps.

[0207] FIG. 15 illustrates an example of calculating an expected data rate (throughput) in an uplink when a GEO satellite at the altitude of 35,786 km and a terrestrial terminal perform direct communication. When the transmission EIRP of the terrestrial terminal in the uplink is 23 dBm, the path loss of the radio channel to the satellite is 195.9 dB, and the satellite reception antenna gain is 51 dBi, the achievable SNR is estimated to be −10.8 dB. Here, the path loss may include a path loss in free space, a loss in the atmosphere, and the like. When an SIR is 2 dB, an SINR is calculated to be −11 dB. Here, when a 30 kHz subcarrier spacing and a frequency resource of 1 PRB are used, a transmission rate of 21 kbps can be achieved, which can be obtained by performing three times of repetitive transmissions.

[0208] FIG. 16 illustrates a path loss value according to a path loss model between a terminal and a satellite, and a path loss according to a path loss model between a terminal and a terrestrial base station. In FIG. 16, “d” corresponds to a distance and “f.sub.c” is the frequency of a signal. In free space where communication between the terminal and the satellite is performed, a path loss (FSPL) 1600 is inversely proportional to the square of the distance. However, a path loss (PL2, PL′.sub.Uma-NLOS) on the ground including air in which communication between the terminal and the terrestrial gNB is performed (indicated by reference numerals 1610 and 1620) is inversely proportional to the fourth power of the distance. d.sub.3D is the straight line distance between the terminal and the base station, h.sub.BS is the height of the base station, and h.sub.UT is the height of the terminal. d′.sub.BP is calculated as d′.sub.BP=4×h.sub.BS×h.sub.UT×f.sub.c/c. f.sub.c is the center frequency in units of Hz, and c is the speed of light in units of m/s.

[0209] In satellite communications (or non-terrestrial network), a Doppler shift occurs due to the continuous and rapid movement of the satellite, that is, a frequency offset of a transmission signal may occur.

[0210] FIG. 17 illustrates equations for calculation of the amount of Doppler shift experienced by a signal, which is transmitted from a satellite and received by a terrestrial user according to the altitude and location of the satellite and the position of a terminal user on the ground, and results thereof. Where the radius of the Earth is “R”, “h” is the altitude of the satellite, “v” is the speed at which the satellite revolves around the Earth, and “f.sub.c” is the frequency of the signal. The speed of the satellite may be calculated based on the altitude of the satellite, and due to the speed of the satellite, the speed at which gravity, which is a force in which the Earth pulls the satellite, and a centripetal force generated as the satellite revolves become the same, and this may be calculated as shown in FIG. 18. FIG. 18 illustrates the speed of the satellite calculated at the altitude of the satellite. As can be seen from FIG. 17, since each angle α is determined by the elevation angle θ, the value of the Doppler shift is determined according to the elevation angle θ.

[0211] FIG. 19 illustrates Doppler shifts experienced by different terminals in one beam, which is transmitted by a satellite to the ground. In FIG. 19, the Doppler shifts experienced by UE 1 1900 and UE 2 1910 according to the elevation angle θ are calculated, respectively. This is the result obtained under an assumption that the center frequency is 2 GHz, the satellite altitude is 700 km, the diameter of one beam is 50 km on the ground, and the speed of the UE is 0. In addition, the Doppler shift calculated in the disclosure may ignore the effect of the Earth's rotation speed, and this consideration may occur because the Earth's rotation speed is slower than the speed of the satellite.

[0212] FIG. 20 shows the difference in Doppler shift occurring in one beam according to the position of a satellite determined from an elevation angle. It can be seen that the difference in Doppler shift within the beam (or cell) is the greatest when the satellite is positioned directly above the beam, that is, when the elevation angle is 90 degrees. This may occur because when the satellite is located above the center, the Doppler shift values at one end of the beam and at the other end have positive and negative values, respectively.

[0213] On the other hand, in satellite communication, since a satellite is far from a user on the ground, a large latency occurs compared to the terrestrial network communication.

[0214] FIG. 21 illustrates a latency taken from a UE to a satellite and a round trip latency among the UE, the satellite, and a base station according to the location of the satellite determined according to an elevation angle. Reference numeral 2100 indicates the latency from the UE to the satellite, and reference numeral 2110 indicates the round trip latency among the UE, the satellite, and the base station. Here, a latency between the satellite and the base station has been assumed to be equal to a latency between the UE and the satellite. FIG. 22 illustrates the value of maximum difference in round-trip latencies that vary according to a user's position in one beam. For example, when the beam radius (or cell radius) is 20 km, the difference in round-trip latencies to the satellite, which UEs in different positions within the beam experience differently depending on the location of the satellite, is about 0.28 ms or less.

[0215] In satellite communication, transmission and reception of a signal to and from a base station by a UE may be understood as that the signal is transmitted through a satellite. That is, in a downlink, a satellite may receive a signal, having been transmitted to the satellite by the base station, and then transmit the received signal to the UE. In an uplink, the satellite may receive a signal, having been transmitted by the UE, and then transmit the received signal to the base station. In the above, after receiving the signal, the satellite may perform frequency shift on the signal to transmit the frequency shifted signal, or may perform signal processing such as decoding, re-encoding, etc., based on the received signal to transmit the signal processed signal.

[0216] In a case of LTE or NR, a UE may access the base station through the following procedure. [0217] Stage 1: The UE receives a synchronization signal (or a synchronization signal block (SSB), which may include a broadcast signal) from a base station. The synchronization signal may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The synchronization signal may include information such as a slot boundary and a frame number of a signal transmitted by the base station, downlink and uplink configuration, and the like. In addition, based on the synchronization signal, the UE may acquire a subcarrier offset, scheduling information for system information transmission, and the like. [0218] Stage 2: The UE receives system information (system information block (SIB)) from the base station. The SIB may include information for performing initial access and random access. The information for performing the random access may include resource information for transmitting the random access preamble. [0219] Stage 3: The UE transmits a random access preamble (or message 1 (msg1)) to a random access resource configured in stage 2. The preamble may be a signal determined based on the information configured in stage 2 using a predetermined sequence. The base station receives the preamble transmitted by the UE. The base station attempts to receive a preamble, which is configured in a resource configured by the base station itself without knowing which UE has transmitted the preamble, and if reception of the preamble is successful, the base station may know that at least one UE has transmitted the preamble. [0220] Stage 4: When the preamble is received in stage 3, the base station transmits a random access response (RAR, or message 2 (msg2)) in response thereto. The UE that has transmitted the random access preamble in stage 3 may attempt to receive the RAR transmitted by the base station in this stage 4. The RAR is transmitted on a PDSCH, and a PDCCH for scheduling the PDSCH is transmitted together with the PDSCH or before the PDSCH. A CRC scrambled with an RA-RNTI value is added to DCI for scheduling the RAR, and the DCI (and CRC) is channel-coded and then mapped to the PDCCH and transmitted. The RA-RNTI may be determined based on the time and frequency resources via which the preamble in stage 3 is transmitted.

[0221] The maximum time limit until the UE, which has transmitted the random access preamble in stage 3, receives the RAR in the stage 4 may be configured in the SIB transmitted in stage 2. This may be configured limitedly, for example, up to 10 ms or 40 ms. That is, if the UE that has transmitted the preamble in stage 3 does not receive the RAR within a time determined based on, for example, the configured maximum time of 10 ms, the UE may transmit the preamble again. The RAR may include scheduling information for allocating a resource of a signal to be transmitted by the UE in stage 5, which is the next stage.

[0222] FIG. 23 illustrates an example of an information structure of an RAR. An RAR 2300 may be, for example, a MAC PDU, and may also include information 2310 on timing advance (TA) to be applied by a UE and a temporary C-RNTI value 2320 to be used from the next stage. [0223] Stage 5: The UE having received the RAR in stage 4 transmits message 3 (msg3) to the base station according to the scheduling information included in the RAR. The UE may include the UE own ID value in the msg3 and transmit. The base station may attempt to receive the msg3 according to the scheduling information transmitted by the base station itself in stage 4. [0224] Stage 6: The base station receives the msg3, identifies the ID information of the UE, and then generates message 4 (msg4) including the ID information of the UE and transmits the generated msg4 to the UE. After transmitting the msg3 in stage 5, the UE may attempt to receive the msg4 to be transmitted in stage 6 thereafter. After receiving the msg4 and performing decoding thereon, the UE may compare the ID value included in the msg4 with the ID value transmitted by the UE itself in stage 5, so as to identify whether the msg3 transmitted by the UE itself is received by the base station. There may be a constraint on time until the UE receives the msg4 in this stage 6 after transmitting the msg3 in stage 5, and this maximum time may also be configured via the SIB in stage 2.

[0225] When the initial access procedure using the above stages is applied to satellite communication, a propagation delay required for satellite communication may become a problem. For example, an interval, that is, the maximum time (e.g., a random access window) from time at which the UE transmits a random access preamble (or PRACH preamble) in stage 3 to time at which the UE receives the RAR in stage 4 may be configured via ra-ResponseWindow. In the conventional LTE or 5G NR system, this maximum time may be configured up to about 10 ms.

[0226] FIG. 24 illustrates an example of the relationship between a PRACH preamble configuration resource and an RAR reception timing of the LTE system, and FIG. 25 illustrates an example of the relationship between a PRACH preamble configuration resource and an RAR reception timing of the 5G NR system. Referring to FIG. 24, in a case of LTE, a random access window 2410 starts after 3 ms from a timing at which a PRACH (or a random access preamble) is transmitted (indicated by reference numeral 2400), and the UE may determine that the transmission of the PRACH preamble is successful when receiving the RAR within the random access window (indicated by reference numeral 2420). Referring to FIG. 25, in a case of NR, a random access window 2510 starts from a control information area for RAR scheduling which appears first after a PRACH (or a random access preamble) is transmitted (indicated by reference numeral 2500). When the UE receives an RAR within the random access window (indicated by reference numeral 2520), the UE may determine that the transmission of the PRACH preamble is successful.

[0227] For example, a TA for uplink transmission timing in a 5G NR system may be determined as follows. First, T.sub.c=1/(Δf.sub.max.Math.N.sub.f) is determined, where Δf.sub.max=480.Math.10.sup.3 Hz and N.sub.f=4096 are given. In addition, κ=T.sub.s/T.sub.c=64, and this may be defined as T.sub.s=1/(Δf.sub.ref.Math.N.sub.f,ref), Δf.sub.ref=15.Math.10.sup.3 Hz, and N.sub.f,ref=2048, respectively.

[0228] FIG. 26 illustrates an example of downlink frame timing and uplink frame timing in a UE. The UE may bring an uplink frame temporally forward by T.sub.TA=(N.sub.TA+N.sub.TA,offset)T.sub.c, based on a downlink frame timing, to perform uplink transmission. In the above, a value of N.sub.TA may be transmitted through an RAR or may be determined based on a MAC CE, and N.sub.TA,offset, may be a value configured in the UE or determined based on a predetermined value.

[0229] The RAR of the 5G NR system may indicate a TA value, and in this case, the T.sub.A may indicate one value among 0, 1, 2, . . . , and 3846. In this case, if the subcarrier spacing (SCS) of the RAR is 2.sup.μ.Math.15 kHz, the N.sub.TA is determined by N.sub.TA=T.sub.A.Math.16.Math.64/2.sup.μ. After completing the random access process, the UE may receive an indication of the TA change value from the base station, and the TA change value may be indicated through the MAC CE or the like. TA information indicated through the MAC CE may indicate one value among 0, 1, 2, . . . , and 63, which is added or subtracted to or from the existing TA value and used to calculate a new TA value. As a result, the TA value may be newly calculated as N.sub.TA_new=N.sub.TA_old+(T.sub.A−31).Math.16.Math.64/2.sup.μ. The indicated TA value may be applied to the uplink transmission by the UE after a predetermined time.

[0230] FIG. 27A illustrates an example of continuous movement of a satellite in a UE located on the ground or on the Earth as the satellite revolves around the Earth along a satellite orbit. Since a distance between a UE and a satellite varies according to an elevation angle at which the UE looks at the satellite, a propagation delay among the UE, the satellite, and the base station varies.

[0231] FIG. 27B illustrates an example of the structure of an artificial satellite. The satellite may include a solar panel or solar array 2700 for photovoltaic or solar power generation, a transmission/reception antenna (main mission antenna 2710) for communication with a UE, and a transmission/reception antenna (feeder link antenna 2720) for communication with a ground station, a transmission/reception antenna for inter-satellite communication (inter-satellite link) 2730, a processor configured to control transmission/reception and perform signal processing, and the like. Ina case where inter-satellite communication is not supported according to the satellites, an antenna for transmitting/receiving signals between satellites may not be included. In FIG. 27B shows that an L band of 1 to 2 GHz is used for communication with the UE, but high frequency bands, such as a K band (18 to 26.5 GHz), a Ka band (26.5 to 40 GHz), and a Ku band (12 to 18 GHz) may also be used.

[0232] In a UE-satellite direct communication, since a distance between a UE and a satellite and a distance between the satellite and a base station are long, and the satellite moves continuously, a time offset due to a propagation delay, etc. occurs when a signal transmitted by the base station or the UE is received by the UE or the base station. Accordingly, the disclosure provides a method and an apparatus in which a base station indicates time offset information so as to enable correction of the time offset, and a UE corrects the time offset accordingly. The following embodiment has been described on the assumption that a UE communicates with a satellite and a ground station, and a case of communication between a satellite base station and a UE is not excluded. In the disclosure, a time offset may be used interchangeably used with timing advance.

First Embodiment

[0233] The first embodiment provides a method and apparatus in which a base station indicates time offset information to a UE, and the UE applies the indicated value.

[0234] A UE may estimate a propagation delay between a satellite and the UE based on the location of the UE and a location of the satellite, and may perform uplink transmission by correcting the estimated propagation delay value by the UE itself. For example, the satellite may transmit information about the location of the satellite via broadcast information, and the UE may receive the information about the location of the satellite transmitted by the satellite and compare the location of the satellite with the location of the UE. The location of the UE may be found by using a global positioning system (GPS) or the like. The UE may calculate uplink transmission time by estimating a time required for a radio wave to be transmitted to the satellite based on a result of comparing the location of the satellite with the location of the UE. For example, in case that the UE receives a signal in a slot n via a downlink at a specific timing and needs to perform uplink transmission corresponding to the received signal in a slot n+k, the UE may perform the uplink transmission earlier, by 2*Td, than a timing of the slot n+k. In the above, Td may correspond to a propagation delay from the UE to the satellite, calculated based on the location information of the satellite and the UE. The propagation delay Td may be a value obtained by dividing a distance between the UE and the satellite by the speed of light. In the above, the location of the satellite may be a value calculated based on the slot n+k in which the UE performs the uplink transmission. This is because the location of the satellite in a slot n and the location of the satellite in a slot n+k may be different according to the movement of the satellite.

[0235] FIG. 28 illustrates an example of a difference in a propagation delay in a terrestrial network and a satellite network. In a case of a terrestrial network, a propagation delay of 1 ms or less occurs when considering a distance to a base station of up to about 100 km. However, in a case of a satellite network, a distance to the satellite may be several thousand km and a distance from the satellite to the base station may also be several thousand km, and thus a propagation delay may be much larger than that of the terrestrial network. In a case of satellite network communication, a propagation delay varies depending on the altitude and the elevation angle of the satellite. FIG. 28 shows a distance between the UE and the satellite according to the elevation angle when the altitude of the satellite is 700 km and the time required for a radio wave to travel back and forth. In FIG. 28, in a case of a satellite network, a low-orbit satellite has been assumed, and therefore, it is shown that a radio round trip time (radio RTT) may occur from 40.9 ms to 9.3 ms when the elevation angle is 0 to 1800 (the radio RTT may include RTT required for a signal to be transmitted/received between a transmitter and a receiver and a processing time consumed at a counterpart node).

[0236] FIG. 29 illustrates an example of applying a timing advance in a terrestrial network and a satellite network. Since a maximum propagation delay is within 1 or 2 ms in a terrestrial network, a slot timing at which a base station transmits a downlink and a slot timing at which the base station receives an uplink may match based on a timing advance provided by LTE and 5G NR systems (that is, a DL slot index and a UL slot index may match). That is, if a UE performs an uplink transmission earlier than a downlink timing by a timing advance value indicated by a base station, when the uplink signal transmitted by the UE is received by the base station, the uplink signal reception timing coincides with the downlink timing of the base station.

[0237] Meanwhile, in a satellite network, it may be impossible to match a slot timing for a base station to transmit a downlink and a slot timing for the base station to receive an uplink based on a timing advance provided by the conventional LTE and 5G NR systems. This is why propagation delay that occurs in the satellite network is much longer than propagation delay that occurs in a terrestrial network by tens of ms, and therefore, this propagation delay is longer than a maximum value of a timing advance considered in the conventional LTE and 5G NR systems.

[0238] FIG. 30 illustrates an example of a maximum difference value among difference values in round trip propagation delay among a UE, a satellite, and a base station, experienced by multiple users when the users are located in one beam among a plurality of beams transmitted by a satellite. FIG. shows that the smaller the beam size is, the smaller the difference in the round trip propagation delay according to an elevation angle experienced by a user is.

[0239] FIG. 31A illustrates an example of a round trip propagation delay between a UE and a base station which varies according to a movement of a satellite along an orbit. Referring to FIG. 31A, since a satellite moves along an orbit, and a round trip propagation delay between a UE and a base station may change according to passage of time. It may be seen that, in a terrestrial network, a propagation delay changes at a time equal to or less than a predetermined period of time, whereas, in a satellite network, a variation in the propagation delay is very large according to passage of time.

[0240] The satellite instructs the UE to time offset information by using the following method, and the UE may correct the transmission time using the indicated time offset information according to the following method so as to perform downlink or uplink signal transmission and reception. [0241] Method 1: the size of a bit field for an indication range for propagation delay, an indication of the propagation delay, or an indication of a timing advance may be determined based on a frequency area or a frequency band (or spectrum). For example, an RAR MAC CE may include 12-bit TA information for a frequency area having a center frequency of 1 GHz or less, and include 16-bit TA information for a frequency area having a center frequency greater than 1 GHz. [0242] Method 2: a base station may indicate a rate of change of a timing advance. A satellite moves regularly according to time, and thus propagation delay may change linearly in a specific time interval. Accordingly, a base station may indicate, to a UE, how to change a TA in the future by indicating, to the UE, propagation delay or a rate of change of the timing advance. A rate of change of a time offset (or the timing advance) may correspond to amount of change in a TA to be applied at a specific time point in the future. Together while indicating the rate of change of the time offset or in advance thereof, the base station may configure, for the UE, a time period and a timing for applying the rate of change of the time offset, together or previously, via L1 control information (e.g., DCI) or higher layer signaling. The higher layer signaling may be, for example, a MAC CE or RRC signaling rather than a physical layer signal. [0243] Method 3: a TA value or a rate of change of the TA may be indicated to one or more UEs on a group basis (e.g., group-common) via the same DCI or the same MAC CE. According to the method 3, the TA or the rate of change of the TA may be indicated to the one or more UEs via the same indication information field, or the TA or the rate of change of the TA may be indicated to each UE via a different indication information field. If a TA or a rate of change of the TA is indicated to different UEs via different indication information fields, a location of a bit field which a UE needs to interpret or an offset value of the location of the bit field may be pre-configured. The UE may identify a value of the bit field to be applied to the corresponding UE based on the location of the bit field or the offset information of the location of the bit field. FIG. 31B illustrates an example in which a plurality of UEs are located in one beam area provided by one satellite. As shown in FIG. 31B, UEs located in one beam area provided by a satellite may transmit and receive signals to and from the same satellite, and thus propagation delay and change values of Doppler shift may be similar. Therefore, UEs, for example, a UE1, a UE2, a UE3, a UE4, and a UE5 which are located in one beam in FIG. 32B may perform a time offset correction for correcting propagation delay or timing advance values based on the same indication information.

[0244] FIG. 31C illustrates an example of indicating a time offset to UEs included in one group by using one MAC CE. Referring to FIG. 31C, when a time offset is indicated to UEs 3110, 3112, 3114, 3116, 3118, 3120, 3122, 3124, and 3126 included in one group in a group unit by using the same MAC CE 3100, the one MAC CE may include time offset indication information for the multiple UEs. Here, a start location 3130 of a time offset indicator for each UE may be configured in advance via higher layer signaling. In addition, time offset indication information may be transmitted to UEs in a group unit via DCI as well as a MAC CE. Here, a bit field indicating a plurality of TAs may be a part of the DCL. For example, a DCI format including the bit field indicating the plurality of TAs may be used. In this case, the UEs in a group may perform blind decoding by using a value of an RNTI which is predefined or configured via higher layer signaling. [0245] Method 4: a TA value to be commonly applied by a UE corresponding to a specific beam may be indicated in system information via an SIB. For example, a time offset TA_offset may be calculated by TA_offset1+TA_offset2, where TA_offset1 may be a value commonly configured or indicated to UEs belonging to a corresponding beam, and TA_offset2 may be a value configured or indicated to a specific UE. Here, TA_offset2 may be configured by using at least one of the methods 1 to 3. [0246] Method 5: a base station may configure a unit of a time offset to the corresponding UE via RRC configuration. If the base station indicates the unit of the time offset via the RRC configuration and indicates the number of units of the time offset via a MAC CE or DCI, the UE may calculate an accurate time offset value by using the unit of the time offset. As a modified example, the base station may indicate candidate values of the unit of the time offset via RRC configuration, and indicate one of the candidate values via MAC CE or DCI. Here, the candidate values of the unit of the time offset may be configured via RRC signaling within a predetermined range, and if only one candidate value is configured as the candidate values of the unit of the time offset, the configured one candidate value may be applied without the MAC CE or DCI. [0247] Method 6: a time offset value may be configured to a UE via RRC configuration. Alternatively, the time offset value may be delivered to the UE based on a combination of the RRC configuration and a MAC CE.

[0248] The methods are not mutually exclusive, and a combination of more than one method may be used.

Second Embodiment

[0249] The second embodiment provides a method and apparatus for a base station or a satellite to indicate a TA value to a UE. In the disclosure, a satellite may be an object located high above the ground, and may be a concept including an airplane, an airship, and the like.

[0250] FIGS. 32 and 33 illustrate an example in which a satellite or a beam from which one UE receives a service is changed according to the movement of a satellite when one satellite performs transmission and reception using a plurality of beams. FIG. 32 illustrates an example in which a beam or satellite to which a UE is connected (or from which a UE receives a service) is changed, but the terrestrial base station or ground station connected to the UE is not changed. As a specific example, in a case of reference numeral 3200, a UE 3210 is connected to satellite 1 3220 to communicate with a ground station 3240, and when the location of the satellite is changed as in reference numeral 3250 according to the movement of the satellite, the UE 3210 is connected to satellite 1 3220 and communicates with the ground station 3240 while the beam used for connection with satellite 1 may be changed, or the UE 3210 may be connected to satellite 2 3230 and communicate with the ground station 3240. FIG. 33 illustrates an example in which, when a beam or satellite to which a UE is connected (or from which a UE receives a service) is changed, a terrestrial base station or ground station connected to the UE is also changed. As a specific example, in a case of reference numeral 3300, a UE 3310 is connected to satellite 1 3320 to communicate with ground station 1 3340, and when the location of the satellite is changed as in reference numeral 3360 according to the movement of the satellite, the UE 3310 may be connected to satellite 2 3330 to perform communication with ground station 2 3350.

[0251] In case that a satellite or beam for transmitting a signal to the UE is changed in the above, a timing advance (TA) value for uplink time synchronization may be suddenly greatly changed. In this case, the base station needs to notify the UE of the changed TA value so that signal interference with a signal transmitted by another UE may not occur. In order to notify of a large amount of change in the TA value, a method of increasing the number of bits of the TA indicator or configuring the granularity (unit) of the TA value indicated by the bit value may be used. Alternatively, in order to notify of a TA again, if the satellite or beam for transmitting/receiving signals to/from the UE is changed, the UE may restart the random access process, but if the satellite or/and beam is frequently changed, overhead due to the random access process increases, and thus data transmission rate or service quality may decrease.

[0252] The disclosure provides a TA indication method and apparatus for transmitting, to a UE, a TA value that is suddenly and greatly changed.

[0253] The UE and the base station may store a plurality of candidates for the TA value. For example, the UE and the base station each store four TA candidate values, and according to the instruction of the base station, the UE may continuously update the four TA candidate values or apply the corresponding values as actual TAs. Each TA candidate value may be referred to as a TA loop. The base station may indicate a TA value, which needs to be updated or applied by the UE, by notifying of a TA loop index in the process of indicating a TA for the UE. FIG. 34 illustrates an example of a TA loop. An example is shown in which, when a UE 3400 is connected to one or more satellites 3410 and 3420 or when the connection is changed from one satellite 3410 to another satellite 3420, multiple TA loops for applying different TA values are defined (for example, TA loop 1 3412 applied to satellite 1 3410, and TA loop 2 3422 applied to satellite 2 3420 may be configured), and the base station and the UE understand this situation. In a process of accessing one base station, the UE receives a TA value to be applied when the UE performs uplink transmission in a random access (RACH) stage. The TA value received in the RACH stage may be determined as a TA value of TA loop index 0. Thereafter, the UE may also be configured with other TA candidate values. Index numbers such as TA loop index 1, 2, 3 may be attached to the TA candidate values configured. Table 21 is a table describing the values of the TA loop configured for the UE. TA loop indices 0 to 3 may respectively correspond to the configured TA values, and each TA value may be different from each other.

TABLE-US-00024 TABLE 21 Index/TCI Current TA value 0 0 1 200 2 500 3 800

[0254] In the above, the number of TA loops may be configured by the base station to the UE through higher layer signaling such as RRC signaling or MAC CE. In the above, the signaling for the base station to configure for the UE may be transmitted to the UE via a satellite. Alternatively, the number of TA loops may be determined as a fixed value, or may be a value configured based on the capability of the UE. The UE may report UE capability information related to the number of TA loops, which can be supported by the UE itself, to the base station.

[0255] In order to indicate one of the values of the TA loop, the base station may indicate the index of the TA loop to the UE using one-bit field of DCI or the value of MAC CE. For example, the base station may indicate the TA loop index using some bits of the DCI in order to indicate the TA value to be applied by the UE while scheduling PUSCH, which is uplink data, via DCI, and the UE may transmit the scheduled PUSCH by applying a TA value corresponding to the indicated TA loop. And/or as an example, the base station may indicate an index of a TA loop to be applied by the UE by using the MAC CE, and may apply a TA change value indicated by the MAC CE to a TA value corresponding to the indicated TA loop. In this case, the MAC CE may include a TA loop index and one or more TA change values for the TA loop index.

[0256] FIGS. 35A and 35B illustrate an example of operations of a base station and a UE for such TA change. FIG. 35A is an operation of a base station for a TA indication. The base station configures the number of TA loops to the UE via higher layer signaling. This configuration may be performed by transmitting information on the number of TA loops or transmitting configuration information about the index of each TA loop. This configuration may be performed based on UE capability information related to the TA loop transmitted by the UE (indicated by reference numeral 3500). The base station instructs the TA loop index to the UE by using some bit fields included in the L1 control information (e.g., DCI) (indicated by reference numeral 3510). The base station may indicate a change value of TA with respect to the TA value of the indicated TA loop index via the MAC CE transmitted on the PDSCH (indicated by reference numeral 3520). FIG. 35B is a UE operation for a TA indication. The UE receives the number of TA loops configured from a base station via higher layer signaling. This configuration may be performed by receiving information on the number of TA loops or receiving configuration information on the index of each TA loop. The UE may transmit UE capability information, which is related to the TA loop, to the base station (indicated by reference numeral 3530). The UE receives L1 control information (e.g., DCI), and obtains an indicated TA loop index using some bit fields included in DCI (indicated by reference numeral 3540). The JE may receive a TA change value with respect to the TA value of the indicated TA loop index via the MAC CE received on the PDSCH (indicated by reference numeral 3550). The UE may use the applied TA value to uplink transmission. Each of the stages shown in FIGS. 35A and 35B may be applied by changing the order, and other stages may be added or omitted.

[0257] The UE may apply the determined TA value to HARQ ACK/NACK feedback transmission, uplink data transmission, PUSCH and PUCCH transmission, and the like. FIGS. 36A and 36B illustrate an example of operations of a base station and a UE transmitting a PUSCH by applying a TA indication. FIG. 36A illustrates an operation of a base station. The base station configures the number of TA loops to the UE via higher layer signaling. This configuration may be performed by transmitting information on the number of TA loops or transmitting configuration information about the index of each TA loop. This configuration may be performed based on UE capability information, which is related to the TA loop and transmitted by the UE (indicated by reference numeral 3600). The base station identifies the TA value to be applied by the UE when receiving the PUSCH, and identifies the TA loop index for indicating the TA value (indicated by reference numeral 3610). The base station transmits a UL grant for scheduling PUSCH to the UE, and the UL grant includes a bit field indicating a TA loop index and a bit field indicating resource allocation information for PUSCH transmission (indicated by reference numeral 3620).

[0258] FIG. 36B illustrates an operation of a UE. The UE receives the number of TA loops configured from abase station via higher layer signaling. This configuration may be performed by receiving information on the number of TA loops or receiving configuration information about the index of each TA loop. This configuration may be performed based on UE capability information, which is related to the TA loop and transmitted by the UE (indicated by reference numeral 3630). The UE receives a UL grant for scheduling a PUSCH from the base station, and the UL grant includes a bit field indicating a TA loop index and a bit field indicating resource allocation information for PUSCH transmission. The UE identifies the TA loop index indicated by the base station based on the bit field (indicated by reference numeral 3620). The UE identifies a TA value corresponding to the TA loop index, and transmits the PUSCH by applying the TA value (indicated by reference numeral 3650). Each of the stages shown in FIGS. 36A and 36B may be applied by changing the order, and other stages may be added or omitted.

[0259] In connection with indicating the index of the TA loop in some bits of the DCI in the above, the DCI may denote DCI for uplink scheduling, and the UE performs uplink transmission scheduled by the DCI using the TA value corresponding to the TA loop index indicated above. Alternatively, when the DCI corresponds to DCI for scheduling downlink data and indicates a TA loop index, the UE may perform transmission by applying a TA value corresponding to the indicated TA loop index during transmission of a PUCCH transmitting HARQ-ACK corresponding to the downlink data.

[0260] Alternatively, the DCI may include a bit field indicating a TA value or a TA change value via DCI for scheduling downlink data, or may correspond to a separate DCI format indicating a TA value or a TA change value. Here, in case that the TA loop index is indicated via DCI, a change indicated by the DCI may be applied only to the TA value of the corresponding index, or in case that the TA loop index is not included in the DCI, a change indicated by the DCI may be applied to the TA values corresponding to all TA loops. Whether the TA loop index is included in DCI and indicated may be configured via higher layer signaling of the base station, or/and may be determined based on the number of TA loops supported by the UE (i.e., capability of the UE). Alternatively, in a case of DCI scheduling downlink data, the base station may indicate a TA value or a TA change value in MAC CE transmitted through a PDSCH scheduled by the corresponding DCI. Here, if the TA loop index is indicated in the DCI, a change indicated by the MAC CE may be applied only to the TA value of the corresponding index, or if the TA loop index is not included in the DCI, changes indicated by the MAC CE may be applied to TA values corresponding to all TA loops. Whether the TA loop index is included in DCI and indicated may be configured via higher layer signaling of the base station, or/and may be determined based on the number of TA loops supported by the UE (i.e., capability of the UE).

[0261] As described above, when a TA value or a TA change value is indicated via DCI for scheduling downlink data or in a separate DCI format, or in a MAC CE transmitted through a PDSCH scheduled by the DCI for scheduling downlink data, the UE may apply the TA, having been applied in the above, to PUSCH or PUCCH transmission scheduled later. If a TA loop index is indicated as being included in DCI in a separate DCI format or DCI for scheduling downlink data, the UE may apply the TA value of the TA loop index indicated via the DCI to the PUSCH or PUCCH transmission scheduled later. A bit field indicating a TA loop index may not be included in the DCI for scheduling the PUSCH scheduled later or DCI scheduling a PDSCH associated with a PUCCH (or HARQ-ACK).

Third Embodiment

[0262] The third embodiment provides a method and apparatus in which a UE transmits (reports) a timing advance (TA) value, having been applied or being applied by the UE itself, to a base station or a satellite.

[0263] The UE may perform an operation of transferring the TA value being applied by the UE itself to the base station. This operation may be performed, when the UE applies a TA value without a separate instruction from the base station, in order to notify the base station of the applied TA value, or to identify or determine how the UE is applying the TA value indicated by the base station. For example, when a satellite to which the UE is connected is changed, this operation may be performed so that the satellite newly connected to the UE may identify the TA value of the UE. For example, the UE may apply the TA, calculated based on the locations of the UE and the satellite, by itself.

[0264] In order for the UE to report the TA value to the base station, a combination of at least one of the following methods may be used. [0265] Method 1: a base station may trigger TA value reporting of a UE via DCI. The base station may trigger the TA value reporting via, for example, some bit field values of the DCI or a combination of values of bit fields of the DCI. A field indicating the triggering of the TA value reporting may be included in the DCI. In this case, the UE may identify that the TA value reporting is triggered if the field in received DCI is configured to a specific value. Alternatively, if a value of at least one field (for example, for a different use) included in the received DCI is configured to a predetermined value, the UE may identify that the TA value reporting is triggered. In addition, the UE may transfer, to the base station, a TA value at a specific time point based on a time point at which the UE receives the DCI. [0266] Method 2: a base station may trigger TA value reporting of a UE via a MAC CE. The base station may trigger the TA value reporting by using some bit values or a value of a bit field of the MAC CE, and the UE may report, to the base station, a TA value at a time point at which the UE receives the MAC CE or a TA value at a time point after a predetermined time from the time point at which the UE receives the MAC CE. [0267] Method 3: a base station may indicate which TA value a UE needs to report via RRC configuration. For example, the base station may configure a period and an offset value for TA reporting and/or a specific condition in which the UE reports a TA value via higher layer signaling, and thus the UE may determine at which time point to report the TA value. In this case, the base station may also designate reference TA value application time (i.e., time to which a TA value to be reported is applied) (Hereinafter, referred to as “TA value reference time point”). In the above, the specific condition for the UE to report the TA value may correspond to, for example, a case in which the TA value is greater than or equal to a predetermined TA value, or a case in which a distance between the UE and a satellite is longer than or equal to a predetermined value of distance. The predetermined values may be configured via higher layer signaling or transmitted via an SIB, etc., or may be fixed values. [0268] Method 4: a UE may report a TA value without a separate trigger from a base station. For example, Method 4 may be understood as that the UE transmits information indicating the TA value to the base station according to a specific condition. The specific condition corresponds to a condition relating to time for performing TA value reporting (without signaling such as DCI, a MAC CE, RRC, etc. for a separate trigger from the base station), a comparison result for a TA value applied by the UE and a specific threshold value, and/or the like. The specific condition may be predetermined.

[0269] In a case of transmitting the TA value as described above, the UE may transmit the TA value using a physical channel such as a PUCCH or PUSCH, or may transmit TA value information to the base station via higher layer signaling. When the UE transmits TA value information using a physical channel, a resource to be used for reporting TA value information may be configured via higher layer signaling.

[0270] The reference time point for determining a TA value reported by a UE and a time point for reporting the TA value may be determined based on a time at which the UE performs TA value reporting, a time point at which the TA value reporting is triggered, and/or the like. For example, if the TA value reporting is triggered via DCI in a slot n, the UE may report a TA value applied or calculated in a slot n-K to the base station. The UE may report, to the base station, the TA value in a slot n+N. Here, each of K and N may be a value which is determined according to subcarrier spacing or a UE capability, DL/UL configuration of slots, PUCCH resource configuration, and/or the like. In the above, K may be zero (K=0). Here, K is 0 (K=0) may denote that the UE reports the TA value based on a time point at which the UE receives a signal triggering the TA value reporting. Alternatively, K may be a value smaller than 0. This case may denote, for example, that the UE pre-calculates a TA value at a time point at which the UE reports the TA value, and generates report information based on the TA which is pre-calculated to report the report information. In addition, K may be a value greater than 0. This may denote that the UE reports a TA value at a time point before a time point (e.g., the slot n+N) at which the UE reports the TA value, and this is because there is a need for time required for the UE to encode information to be reported and prepare transmission.

[0271] FIGS. 37A and 37B illustrate an example of operations of the base station and the UE for reporting the TA value of the UE. When reporting the TA value of the disclosure, the TA value applied by the UE may be indicated in ms units, slot units, symbol units, or the like, or may be provided as information including a value after a decimal point rather than an integer. In the disclosure, the TA value reporting may include an absolute value of the TA value, however, the UE may also report a TA value indicated from a previous base station, a relative TA value excluding a determined TA value, or amount of change in a TA value (this may be, for example, the amount of change in the TA value for a predetermined period of time).

[0272] FIG. 37A illustrates an operation of a base station. A base station transmits configuration information related to TA reporting via higher layer signaling in operation 3700. Here, the configuration information related to TA reporting may include, for example, at least one of information for configuring TA reporting such as a period and an offset at which TA reporting is to be performed, a TA reporting trigger condition, TA reference time information, a type of TA to be reported, configuration information about a resource through which TA reporting is to be performed, and/or the like. The base station triggers TA reporting to the UE in operation 3710. Here, the TA reporting trigger for the UE may be performed, for example, via higher layer signaling or DCI, but may be omitted if necessary. The base station receives a TA report transmitted by the UE based on the transmitted configuration information in operation 3720.

[0273] FIG. 37B illustrates an operation of a UE. A UE receives configuration information related to TA reporting transmitted by a base station via higher layer signaling in operation 3730. The configuration information related to TA reporting may include, for example, at least one of information for configuring TA reporting such as a period and an offset at which TA reporting is to be performed, a TA reporting trigger condition, TA reference time information, a type of TA to be reported, configuration information about a resource through which TA reporting is to be performed, and/or the like. The UE receives a signal triggering TA reporting which is transmitted by the base station in operation 3740. The signal triggering TA reporting may be transmitted, for example, via the higher layer signaling or DCIs, but may be omitted if necessary. The UE transmits a TA report based on the received configuration information in operation 3720. For example, in case that the UE receives information about a resource through which TA reporting is to be performed, the UE transmits the TA report through the configured resource. An order of operations shown in FIGS. 37A and 37B may be changed, other operations may be added to the operations, and at least one of the operations may be omitted.

Fourth Embodiment

[0274] The fourth embodiment provides a method and apparatus in which a UE configures a TA to 0 or a predetermined value.

[0275] When a satellite or base station from which a UE receives service is suddenly changed, the TA value to be applied by the UE for the next uplink transmission may be suddenly changed. For the reasons described above, a procedure for changing the TA value to be applied by the UE to 0 or a predetermined value may be required. In this case, the TA value may be initialized using the following methods.

[0276] Initializing the TA value in the disclosure may correspond to a method of configuring the TA value to 0, or a method of configuring the TA value to a value previously configured by DCI or higher layer signaling. In the disclosure, higher layer signaling may be signaling transmitted in layers such as a MAC, a PDCP, and an RRC, and may be a value pre-stored in memory or a pre-configured value. [0277] Method 1: Based on the location of a satellite and a UE, the UE may initialize a TA when it is determined that a satellite (or a connected satellite) from which the UE receives a service is changed. In this case, the UE may report the TA value being applied by the UE itself to the base station. [0278] Method 2: The base station may instruct TA initialization through DCI. In this method, TA initialization may be indicated by a specific bit field value of DCI or a combination of bit field values. For example, a field indicating TA initialization may be included in DCI. In this case, when the field of the received DCI is configured to be a specific value, the UE may understand that TA initialization is indicated. Alternatively, when the values of one or more (for example, other uses) fields included in the DCI are configured to be a predetermined value, the UE may understand that TA initialization is indicated. [0279] Method 3: When the TA value applied by the UE exceeds a TA threshold, the UE may perform TA initialization, and the TA threshold may be a value preconfigured by higher layer signaling. In the above, for convenience of explanation, the disclosure has been described separately from a first embodiment to a fourth embodiment, however, the first to fourth embodiments include operations related to each other, and therefore at least two of the embodiments may be combined. In addition, methods according to embodiments may not be mutually exclusive, and at least two of the methods may be combined and performed.

[0280] In order to perform the embodiments of the disclosure, a base station, a satellite, and a UE. or a transmission and reception method by a transmission terminal or a reception terminal are described. To this end, each of the base station, the satellite, and a receiver, a processor, and a transmitter of the UE should operate according to embodiments.

[0281] Specifically, FIG. 38 is a block diagram illustrating an internal structure of a UE according to an embodiment of the disclosure. As shown in FIG. 32, a UE of the disclosure may include a UE receiver 3800, a UE transmitter 3820, and a UE processor 3810. The UE receiver 3800 and the UE transmitter 3820 may collectively be referred to as a transceiver according to an embodiment of the disclosure. The transceiver may transmit/receive signals to/from a base station. The signals may include control information and data. To this end, the transceiver may include an RF transmitter for frequency-up converting and amplifying transmitted signals and an RF receiver for low-noise amplifying and frequency-down converting received signals. In addition, the transceiver may receive signals via a radio channel, output the signals to the UE processor 3810, and may transmit signals output from the UE processor 3810 via a radio channel. The UE processor 3810 may control a series of processes for the UE to operate according to the above-described embodiments of the disclosure. For example, the UE receiver 3800 may receive a signal from a satellite or a terrestrial base station, and the UE processor 3810 may transmit/receive the signal to/from the base station according to the described method. Thereafter, the UE transmitter 3820 may transmit a signal at a determined time point.

[0282] FIG. 39 is a block diagram illustrating an internal structure of a satellite according to an embodiment of the disclosure. As shown in FIG. 39, a satellite of the disclosure may include a satellite receiver 3900, a satellite transmitter 3920, and a satellite processor 3910. In the above, the receiver, the transmitter, and the processor may be implemented in the plural form. That is, a receiver and a transmitter for receiving and transmitting signals from and to a UE, and a receiver and a transmitter for receiving and transmitting signals from and to a base station (further, a receiver and a transmitter for receiving and transmitting signals from and to another satellite) may be implemented. The satellite receiver 3900 and the satellite transmitter 3920 may collectively be referred to as a satellite transceiver according to an embodiment of the disclosure. The transceiver may transmit/receive signals to/from the UE and the base station. The signals may include control information and data. To this end, the transceiver may include an RF transmitter for frequency-up converting and amplifying transmitted signals and an RF receiver for low-noise amplifying and frequency-down converting received signals. In addition, the transceiver may receive signals via a radio channel, output the signals to the satellite processor 3910, and transmit signals output from the satellite processor 3910 via a radio channel. The satellite processor 3910 may include a compensator (or a pre-compensator) for compensating for a frequency offset or Doppler shift, and a device for estimating a location from a GPS, and/or the like. The satellite processor 3910 may include a frequency shift function which may shift a central frequency of a received signal. The satellite processor 3910 may control a series of processes for the satellite, the base station, and the UE to be able to operate according to the above-described embodiments. For example, the satellite processor may be configured to determine the satellite receiver 3900 to receive, from the UE, a PRACH preamble, and to transmit TA information to the base station while transmitting again, to the UE, an RAR in response to the PRACH preamble. Thereafter, the satellite transmitter 3920 may transmit corresponding signals at a determined time point.

[0283] FIG. 40 is a block diagram illustrating an internal structure of a base station according to an embodiment of the disclosure. As shown in FIG. 40, a base station of the disclosure may include a base station receiver 4000, a base station transmitter 4020, and a base station processor 4010. The base station may be a terrestrial base station or a part of a satellite. The base station receiver 4000 and the base station transmitter 4020 may collectively be referred to as a transceiver according to an embodiment of the disclosure. The transceiver may transmit/receive signals to/from a UE. The signals may include control information and data. To this end, the transceiver may include an RF transmitter for frequency-up converting and amplifying transmitted signals and an RF receiver for low-noise amplifying and frequency-down converting received signals. In addition, the transceiver may receive signals via a radio channel, output the signals to the base station processor 4010, and may transmit signals output from the base station processor 4010 via a radio channel. The base station processor 4010 may control a series of processes for the base station to be able to operate according to the above-described embodiments. For example, the base station processor 4010 may transmit an RAR including TA information.

[0284] As an example, provided is a method by a UE in a communication system, the method including: receiving downlink control information including first timing advance (TA) loop index information from a base station; identifying a first TA value corresponding to a first TA loop index identified based on the first TA loop index information; and transmitting uplink data based on the downlink control information by applying the first TA value, wherein the downlink control information further includes uplink data scheduling information.

[0285] In addition, provided is a method by a base station in a communication system, the method including: transmitting downlink control information including first timing advance (TA) loop index information to a UE; and receiving uplink data according to the downlink control information, wherein the TA, based on which the uplink data transmission is performed, corresponds to a first TA value corresponding to a first TA loop index identified based on the first TA loop index information, and the downlink control information further includes uplink data scheduling information.

[0286] Further, provided is a UE in a communication system, the UE including a transceiver, and a controller configured to: receive downlink control information including first timing advance (TA) loop index information from a base station; identify a first TA value corresponding to a first TA loop index identified based on the first TA loop index information; and transmit uplink data based on the downlink control information by applying the first TA value, wherein the downlink control information further includes uplink data scheduling information.

[0287] In addition, provided is a base station in a communication system, the base station including a transceiver, and a controller configured to perform further control to transmit downlink control information including first timing advance (TA) loop index information to a UE; and receive uplink data according to the downlink control information, wherein the TA, based on which the uplink data transmission is performed, corresponds to a first TA value corresponding to a first TA loop index identified based on the first TA loop index information, and the downlink control information further includes uplink data scheduling information.

[0288] The embodiments of the disclosure described and shown in the specification and the drawings are merely specific examples that have been presented to easily explain the technical contents of the disclosure and help understanding of the disclosure, and are not intended to limit the scope of the disclosure. That is, it will be apparent to those skilled in the art that other variants based on the technical idea of the disclosure may be implemented. Further, the above respective embodiments may be employed in combination, as necessary. Further, other variants of the above embodiments, based on the technical idea of the embodiments, may also be implemented in LTE or 5G systems.