METHOD AND DEVICE FOR INDICATING HARQ PROCESS IN WIRELESS COMMUNICATION SYSTEM

Abstract

The present disclosure relates to: a communication technique for merging IoT technology with a 5G communication system for supporting a data transmission rate higher than that of a 4G system; and a system therefor. The present disclosure can be applied to an intelligent service (for example, smart homes, smart buildings, smart cities, smart cars or connected cars, health care, digital education, retail businesses, and security- and safety-related services) on the basis of a 5G communication technology and an IoT-related technology. The present disclosure provides a method and a device for setting, indicating and operating a HARQ process ID.

Claims

1. A method by a user equipment (UE) in a wireless communication system, the method comprising: transmitting, to a base station, capability information indicating whether the UE supports a number of increased hybrid automatic repeat request (HARQ) process; in case that the UE supports the number of increased HARQ process, receiving, form the base station, configuration information for the number of increased HARQ process; and performing communication with the base station based on an HARQ process identifier (ID) according to the number of increased HARQ process, wherein the increased HARQ process is based on the configuration information.

2. The method of claim 1, wherein the number of increased HARQ processes is 32.

3. The method of claim 1, wherein the performing of communication comprises, based on the HARQ process ID, transmitting a plurality of physical uplink shared channels (PUSCH) or receiving a plurality of physical downlink shared channels (PDSCH), wherein an HARQ process ID for the plurality of PUSCHs is allocated while being increased by 1 sequentially according to a modulo operation based on the number of increased HARQ processes, and wherein an HARQ process ID for the plurality of PDSCHs is allocated while being increased by 1 sequentially according to a modulo operation based on the number of increased HARQ processes.

4. The method of claim 1, wherein the number of increased HARQ processes is for non-terrestrial network (NTN) communication.

5. A method by a base station in a wireless communication system, the method comprising: receiving, from a user equipment (UE), capability information indicating whether the UE supports a number of increased hybrid automatic repeat request (HARQ) process; in case that the UE supports the number of increased HARQ process, transmitting, to the UE, configuration information for the number of increased HARQ process; and performing communication with the UE based on an HARQ process identifier (ID) according to the number of increased HARQ process, wherein the increased HARQ process is based on the configuration information.

6. The method of claim 5, wherein the number of increased HARQ processes is 32, and the number of increased HARQ processes is for non-terrestrial network (NTN) communication.

7. The method of claim 5, wherein the performing of communication comprises, based on the HARQ process ID, receiving a plurality of physical uplink shared channels (PUSCH) or transmitting a plurality of physical downlink shared channels (PDSCH), wherein an HARQ process ID for the plurality of PUSCHs is allocated while being increased by 1 sequentially according to a modulo operation based on the number of increased HARQ processes, and wherein an HARQ process ID for the plurality of PDSCHs is allocated while being increased by 1 sequentially according to a modulo operation based on the number of increased HARQ processes.

8. A user equipment (UE) in a wireless communication system, the UE comprising: a transceiver configured to perform signal transmission or reception; and a controller connected to the transceiver, wherein the controller is configured to: transmit, to a base station, capability information associated with whether the UE supports a number of increased hybrid automatic repeat request (HARQ) processes, in case that the UE supports the number of increased HARQ process, receive, from the base station, configuration information for the number of increased HARQ process, and perform communication with the base station based on an HARQ process identifier (ID) according to the number of increased HARQ process, wherein the increased HARQ process is based on the configuration information.

9. The UE of claim 8, wherein the number of increased HARQ processes is 32.

10. The UE of claim 8, wherein the controller is further configured to, based on the HARQ process ID, transmit a plurality of physical uplink shared channels (PUSCH) or receive a plurality of physical downlink shared channels (PDSCH), wherein an HARQ process ID for the plurality of PUSCHs is allocated while being increased by 1 sequentially according to a modulo operation based on the number of increased HARQ processes, and wherein an HARQ process ID for the plurality of PDSCHs is allocated while being increased by 1 sequentially according to a modulo operation based on the number of increased HARQ processes.

11. The UE of claim 8, wherein the number of increased HARQ processes is non-terrestrial network (NTN) communication.

12. A base station in a wireless communication system, the base station comprising: a transceiver configured to perform signal transmission or reception; and a controller connected to the transceiver, wherein the controller is configured to: receive, from a user equipment (UE), capability information associated with whether the UE supports a number of increased hybrid automatic repeat request (HARQ) process, in case that the UE supports the number of increased HARQ process, transmit, to the UE, configuration information for the number of increased HARQ process, and perform communication with the UE based on an HARQ process identifier (ID) according to the number of increased HARQ process, wherein the increased HARQ process is based on the configuration information.

13. The base station of claim 12, wherein the number of increased HARQ processes is 32.

14. The base station of claim 12, wherein the controller is further configured to, based on the HARQ process ID, receive a plurality of physical uplink shared channels (PUSCH) or transmit a plurality of physical downlink shared channels (PDSCH), wherein an HARQ process ID for the plurality of PUSCHs is allocated while being increased by 1 sequentially according to a modulo operation based on the number of increased HARQ processes, and wherein an HARQ process ID for the plurality of PDSCHs is allocated while being increased by 1 sequentially according to a modulo operation based on the number of increased HARQ processes.

15. The base station of claim 12, wherein the number of increased HARQ processes is for non-terrestrial network (NTN) communication.

Description

BRIEF DESCRIPTION OF DRAWINGS

[0017] FIG. 1 is a diagram illustrating a basic structure of the time-frequency domain which is a radio resource area where data or a control channel is transmitted in a downlink or an uplink of an NR system.

[0018] FIG. 2 is a diagram illustrating a control region in which a downlink control channel is transmitted in a 5G wireless communication system.

[0019] FIG. 3 is a diagram illustrating an example in which eMBB, URLLC, and mMTC data are allocated in the entire system frequency band.

[0020] FIG. 4 is a diagram illustrating an example in which eMBB, URLLC, and mMTC data are allocated in separate system frequency bands.

[0021] FIG. 5 is a diagram illustrating an example of a process in which a single transport block is divided into multiple code blocks, and CRCs are added.

[0022] FIG. 6 is a diagram illustrating a synchronization signal (SS) and a physical broadcast channel (PBCH) which are mapped in the frequency and time domain in an NR system.

[0023] FIG. 7 is a diagram illustrating symbols in which an SS/PBCH block is capable of being transmitted based on a subcarrier spacing (SCS).

[0024] FIG. 8 is a diagram illustrating a user equipment (UE) processing time based on 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 an embodiment.

[0025] FIG. 9 is a diagram illustrating an example of scheduling and transmitting data (e.g., TBs) based on slots, receiving a HARQ-ACK feedback associated with the corresponding data, and performing retransmission based on the feedback.

[0026] FIG. 10 is a diagram illustrating an example of a communication system that uses a satellite.

[0027] FIG. 11 is a diagram illustrating a revolution cycle of a communication satellite around the earth based on the altitude or height of the satellite.

[0028] FIG. 12 is a conceptual diagram of satellite-UE direct communication.

[0029] FIG. 13 is a diagram illustrating a scenario of utilizing satellite-UE direct communication.

[0030] FIG. 14 is a diagram illustrating an example of calculation of an expected data transmission rate (throughput) in an uplink in case that an LEO satellite located at an altitude of 1200 km and a UE on the earth perform direct communication.

[0031] FIG. 15 is a diagram illustrating an example of calculation of an expected data transmission rate (throughput) in an uplink in case that a GEO satellite located at an altitude of 35,786 km and a UE on the earth perform direct communication.

[0032] FIG. 16 is a diagram illustrating a pathloss value based on a pathloss model between a UE and a satellite, and a pathloss based on a pathloss model between a UE and a base station in a terrestrial network communication.

[0033] FIG. 17 is a diagram illustrating an equation that calculates the amount of Doppler shift that a signal experiences when the signal transferred from a satellite is received by a user on the earth according to the altitude and location of the satellite and the location of the user of a UE on the earth, and a calculation result.

[0034] FIG. 18 is a diagram illustrating the speed of a satellite calculated at the altitude of the satellite.

[0035] FIG. 19 is a diagram illustrating Doppler shift that different UEs experience in a single beam that a satellite transmits to the earth.

[0036] FIG. 20 is a diagram illustrating a difference in Doppler shift incurred in a single beam, depending on the location of a satellite determined based on an elevation angle.

[0037] FIG. 21 is a diagram illustrating a latency taken from a UE to a satellite and a round trip latency among UE-satellite-base station, depending on the location of a satellite determined based on an elevation angle.

[0038] FIG. 22 is a diagram illustrating the maximum difference value in a round trip latency that differs depending on the location of a user in a single beam.

[0039] FIG. 23 is a diagram illustrating an example of the structure of information of a random access response (RAR).

[0040] FIG. 24 is a diagram illustrating an example of a relationship between a reception time of a PRACH preamble configuration resource and a reception time of an RAR in an LTE system.

[0041] FIG. 25 is a diagram illustrating an example of a relationship between a reception time of a PRACH preamble configuration resource and a reception time of an RAR in a 5G NR system.

[0042] FIG. 26 is a diagram illustrating an example of timing of a downlink frame and an uplink frame from the perspective of a UE.

[0043] FIG. 27A is a diagram illustrating an example of continuous movement of a satellite from the perspective of a UE located on the ground of the earth or on the earth, as the satellite revolves around the earth along a satellite orbit.

[0044] FIG. 27B is a diagram illustrating an example of the structure of an artificial satellite.

[0045] FIG. 28 is a diagram schematically illustrating an example of a message transferred from a MAC layer to a physical layer in a downlink in a communication system according to various embodiments of the disclosure.

[0046] FIG. 29 is a diagram schematically illustrating an example of a message transferred from a MAC layer to a physical layer in an uplink in a communication system according to various embodiments of the disclosure.

[0047] FIG. 30 is a diagram schematically illustrating an example of the format of the MAC payload of an RAR or the MAC payload of MsgB in a communication system according to various embodiments of the disclosure.

[0048] FIG. 31 is a diagram schematically illustrating an uplink transmission operation in case that a UE directly calculates a TA value in a communication system according to various embodiments of the disclosure.

[0049] FIG. 32 is a diagram schematically illustrating an example of a difference in propagation delay time between a terrestrial network and a satellite network in a communication system according to various embodiments of the disclosure.

[0050] FIG. 33 is a diagram schematically illustrating an example of applying a TA to a terrestrial network and a satellite network in a communication system according to various embodiments of the disclosure.

[0051] FIG. 34 is a diagram schematically illustrating an example of the maximum difference in round trip latency in case that a plurality of UEs are located in a single beam that a satellite supports in a communication system according to various embodiments of the disclosure.

[0052] FIG. 35 is a diagram schematically illustrating an example of a wireless round trip latency between a UE and a base station, which varies depending on the movement of a satellite in a communication system according to various embodiments of the disclosure.

[0053] FIG. 36 is a block diagram schematically illustrating the internal structure of a UE according to various embodiments of the disclosure.

[0054] FIG. 37 is a block diagram schematically illustrating the internal structure of a satellite according to various embodiments of the disclosure.

[0055] FIG. 38 is a block diagram schematically illustrating the internal structure of a base station according to various embodiments of the disclosure.

[0056] FIG. 39 is a diagram schematically illustrating the structure of a base station according to various embodiments of the disclosure.

[0057] FIG. 40 is a diagram schematically illustrating the structure of a UE according to embodiments of the disclosure.

MODE FOR THE INVENTION

[0058] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings. It should be noted that, in the drawings, the same or like elements are designated by the same or like reference signs as much as possible. Furthermore, a detailed description of known functions or configurations that may make the subject matter of the disclosure unclear will be omitted.

[0059] In describing embodiments of the disclosure, descriptions related to technical contents well-known in the art 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] Furthermore, 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.

[0065] The new radio (NR) access technology which is a new 5G communication technology is designed to enable various services to be freely multiplexed in time and frequency resources. Accordingly, a waveform/numerology or the like and a reference signal or the like may be dynamically or freely allocated as a corresponding service is needed. In order to provide an optimal service to a user equipment (UE) in wireless communication, it is important to optimize data transmission by measuring the quality of a channel and the amount of interference. Accordingly, accurate measurement of a channel state is essential. However, unlike 4G communication in which channel and interference characteristics do not significantly change according to a frequency resource, in the case of a 5G channel, channel and interference characteristics significantly change according to a service. Accordingly, to enable separate measuring of the channel and interference characteristics, a subset in a frequency resource group (FRG) level needs to be supported. The types of services supported in the NR system may be categorized into enhanced mobile broadband (eMBB), massive machine type communications (mMTC), ultra-reliable and low-latency communications (URLLC), and the like. eMBB is a service for high-speed transmission of large-capacity data. mMTC is a service for UE power minimization and multi-UE access. URLLC is a service for high reliability and low latency. Different requirements may be applied depending on the type of service applied to a UE.

[0066] As described above, a plurality of services may be provided to a user in a communication system. In order to provide a plurality of services to a user, there is a desire for a method and a device for providing services according to respective characteristics within the same time interval.

[0067] A wireless communication system is evolving from the initial voice-based service 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, standards for 5G or new radio (NR) systems as the 5th generation wireless communication system are now under development.

[0068] As a typical example of the broadband wireless communication system, the 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, the CP-OFDM scheme and discrete Fourier transform spreading (DFT-S-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 scheme separates 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.

[0069] The NR system employs a hybrid automatic repeat request (HARQ) scheme in which, when decoding is unsuccessful at the initial transmission, the corresponding data is retransmitted in a physical layer. In the HARQ scheme, when a receiver fails to accurately decode data, the receiver transmits information (negative acknowledgement: NACK) informing a transmitter of the unsuccessful decoding and thus the transmitter may retransmit the corresponding data in the physical layer. The receiver may increase data reception performance by combining the data retransmitted by the transmitter with the data the decoding of which has previously failed. Also, when the receiver accurately decodes data, the receiver transmits information (acknowledgement: ACK) informing the transmitter of the successful decoding and thus the transmitter may transmit new data.

[0070] FIG. 1 is a diagram illustrating a basic structure of the time-frequency domain which is a radio resource area in which data or a control channel is transmitted in a downlink or an uplink of an NR system.

[0071] Referring to FIG. 1, the horizontal axis denotes the time domain, and the vertical axis denotes the frequency domain. The minimum transport unit in the time domain is an OFDM symbol, and Nsymb OFDM symbols 102 may be configured as a single slot 106. The length of a subframe is defined to be 1.0 ms, and the length of a radio frame 114 is defined to be 10 ms. The minimum transport unit in the frequency domain is a subcarrier. The entire system transmission bandwidth may include a total of N{circumflex over ()}BW subcarriers 104. One frame may be defined to be 10 ms. One subframe may be defined to be 1 ms and thus, one frame may include a total of 10 subframes. One slot may be defined to be 14 OFDM symbols (i.t., the number of symbols per slot (N.sub.symb.sup.slot)=14). One subframe may include one or multiple slots, and the number of slots per one subframe may be different based on a set value ? configured for a subcarrier spacing. The example of FIG. 2 illustrates the case of ?=0 as a subcarrier spacing set value and the case of ?=1. In case of ?=0, one subframe includes one slot. In case of ?=1, one subframe includes two slots. That is, depending on a set value ? for a subcarrier spacing, the number of slots per subframe (N.sub.slot.sup.subframe,?) may differ. Accordingly, the number of slots per frame (N.sub.slot.sup.frame,?) may also differ. N.sub.slot.sup.subframe,? and N.sub.slot.sup.frame,? based on a subcarrier spacing set value ? may be defined as listed in Table 1 as below.

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

[0072] A user equipment (UE) before being radio resource control (RRC)-connected may receive, from a base station via a master information block (MIB), a configuration of an initial bandwidth part (initial BWP) for initial access. More specifically describing, at the initial access stage, the UE may receive configuration information associated with a search space and a control region (control resource set (CORESET)) in which a physical downlink control channel (PDCCH) is transmitted, in order to receive, via the MIB, system information (corresponding to remaining system information (RMSI) or system information block 1 (SIB1)) needed for initial access. Each of the control region and the search space configured via the MIB may be regarded as an identity (ID) of 0. The base station may inform the UE of configuration information such as frequency allocation information, time allocation information, numerology, or the like in association with control region #0, via the MIB. In addition, the base station may inform the UE of configuration information related to a monitoring cycle and an occasion associated with control region #0, that is, configuration information associated with search space #0, via the MIB. The UE may consider, as an initial bandwidth part for initial access, a frequency range configured as control region #0 obtained from the MIB. In this instance, the identity (ID) of the initial bandwidth part may be considered as 0.

[0073] The MIB may include information shown below.

TABLE-US-00002 MIB -- ASN1START -- TAG-MIB-START MIB ::=SEQUENCE { systemFrameNumberBIT STRING (SIZE (6)), subCarrierSpacingCommonENUMERATED {scs15or60, scs30or120}, ssb-SubcarrierOffsetINTEGER (0..15), dmrs-TypeA-PositionENUMERATED {pos2, pos3}, pdcch-ConfigSIB1PDCCH-ConfigSIB1, cellBarredENUMERATED {barred, notBarred}, intraFreqReselectionENUMERATED {allowed, notAllowed}, spareBIT STRING (SIZE (1)) } -- TAG-MIB-STOP -- ASN1STOP

TABLE-US-00003 MIB field descriptions cellBarred Value barred means that the cell is barred, as defined in TS 38.304 [20]. dmrs-TypeA-Position 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). intraFreqReselection 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]. pdcch-ConfigSIB1 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). ssb-SubcarrierOffset 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). 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]. 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). subCarrierSpacingCommon 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 systemFrameNumber 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].

[0074] In a method of configuring a bandwidth part, UEs before being RRC-connected may receive configuration information associated with an initial bandwidth part via an MIB in the initial access stage. More specifically describing, a UE may receive, from an MIB of a physical broadcast channel (PBCH), a configuration of a control region for a downlink control channel in which a downlink control information (DCI) that schedules an SIB may be transmitted. In this instance, the bandwidth of the control region configured via the MIB may be regarded as an initial bandwidth part, and the UE may receive, via the configured initial bandwidth part, a physical downlink shared channel (PDSCH) that transmits an SIB. In addition to the purpose of receiving the SIB, the initial bandwidth part may be utilized for the purpose of other system information (OSI), paging, or random access.

[0075] In case that one or more bandwidth parts are configured for a UE, a base station may indicate changing of a bandwidth part by using a bandwidth part indicator field in DCI.

[0076] A basic resource unit in the time-frequency domain is a resource element (RE) 112, and an RE is expressed by an OFDM symbol index and a subcarrier index. A resource block (RB) 108 (or a physical resource block (PRB)) may be defined to be NRB consecutive subcarriers 110 in the frequency domain. Generally, the minimum transport unit of data is an RB. In the NR system, generally, Nsymb=14 and NRB=12. NBW is proportional to a system transmission bandwidth. The data rate may be increased in proportion to the number of RBs scheduled for a UE.

[0077] In the NR system, a downlink transmission bandwidth and an uplink transmission bandwidth may be different from each other in the case of an FDD system that operates a downlink and an uplink based on a frequency A channel bandwidth may be an RF bandwidth corresponding to a system transmission bandwidth. Table 2 and Table 3 show a part of the correspondence relationship of a system transmission bandwidth, a subcarrier spacing, and a channel bandwidth defined in the NR system, respectively in a frequency band lower than 6 GHz and a frequency band higher than 6 GHz. For example, in case of the NR system that has a channel bandwidth of 100 MHz with an subcarrier spacing of 30 kHz, the transmission bandwidth may include 273 RBs. N/A in the following table may be a bandwidth-subcarrier combination that is not supported by the NR system. Table 2 below shows the configuration of frequency range 1 (FR1) and Table 3 shows the configuration of FR2.

TABLE-US-00004 TABLE 2 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) NRB NRB NRB NRB NRB NRB NRB NRB NRB NRB NRB NRB 15 25 52 79 106 133 160 216 270 N/A N/A N/A N/A 30 11 24 38 51 65 78 106 133 162 217 245 273 60 N/A 11 18 24 31 38 51 65 79 107 121 135

TABLE-US-00005 TABLE 3 Channel bandwidth BWChannel subcarrier 50 100 200 400 [MHz] width MHz MHz MHz MHz Transmission 60 kHz 66 132 264 N/A bandwidth 120 kHz 32 66 132 264 configuration NRB

[0078] In the NR system, a frequency range may be separately defined as FR1 and FR2, as shown in Table 4 below.

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

[0079] The above-mentioned ranges of FR1 and FR2 may be changed to be different, and may be applied. For example, the frequency range of FR1 may be changed to the range of 450 MHz to 6000 MHz and may be applied.

[0080] Subsequently, a synchronization signal (SS)/PBCH block (or SSB) in 5G will be described.

[0081] An SS/PBCH block may be a physical layer channel block including a primary SS (PSS), a secondary SS (SSS), and a PBCH. A detailed description thereof is provided as follow. [0082] PSS: acts as a reference signal for downlink time/frequency synchronization, and provides part of cell ID information. [0083] SSS: acts as a reference for downlink time/frequency synchronization, and provides the remaining cell ID information that a PSS does not provide. In addition, an SSS may act as a reference signal for demodulation of a PBCH. [0084] PBCH: provides essential system information needed for a UE to perform data channel and control channel transmission or reception. The essential system information may include search space-related control information indicating radio resource mapping information of a control channel, scheduling control information associated with a separate data channel that transmits system information, and the like. [0085] SS/PBCH block: an SS/PBCH block includes a combination of a PSS, an SSS, and a PBCH. A single or multiple SS/PBCH blocks may be transmitted within 5 ms, and each transmitted SS/PBCH block may be identified based on an index.

[0086] At the initial access stage, a UE may detect a PSS and an SSS, and may decode a PBCH. The UE may obtain an MIB from the PBCH, whereby control region #0 (corresponding to a control region having a control region index of 0) may be configured. The UE may assume that a selected SS/PBCH block and a demodulation reference signal (DMRS) transmitted in control region #0 are in a quasi co location (QCL), and may monitor control region #0. The UE may receive system information via downlink control information transmitted in control region #0. From the received system information, the UE may obtain random access channel (RACH)-related configuration information needed for initial access. The UE may transmit a physical RACH to a base station in consideration of the selected SS/PBCH index, and the base station that receives the PRACH may obtain information associated with the index of the SS/PBCH block that the UE selects. Through the above-described processes, the base station may recognize a block that the UE selects among SS/PBCH blocks and the fact that the UE monitors control region #0 related to the selected block.

[0087] Subsequently, downlink control information (DCI) in the 5G system will be described in detail.

[0088] In the 5G system, scheduling information for uplink data (or a physical uplink shared channel (PUSCH)) or downlink data (or a physical downlink shared channel (PDSCH)) may be transferred from a base station to a UE via DCI. The UE may perform monitoring of a DCI format for fallback and a DCI format for non-fallback in association with a PUSCH or PDSCH. The fallback DCI format may be configured as a fixed field predefined between the base station and the UE, and the non-fallback DCI format may include a configurable field. In addition, various types of DCI formats may be used, and whether a corresponding DCI is for DCI for power control, DCI for notifying a slot format indicator (SFI), or the like may be indicated for each format.

[0089] The DCI may go through a channel coding a modulation process, and may be transmitted via a PDCCH that is a physical downlink control channel. A cyclic redundancy check (CRC) is added to a DCI message payload, and the CRC may be scrambled by a radio network temporary identifier (RNTI) corresponding to a UE identity. Different RNTIs may be used depending on the purpose of a DCI message, for example, UE-specific data transmission, power control command, random access response, or the like. That is, an RNTI is not explicitly transmitted, but is transmitted by being included in a CRC calculation process. In case that a DCI message transmitted in a PDCCH is received, the UE may identify a CRC by using an allocated RNTI, and may recognize that the corresponding message is transmitted for the UE in case a CRC identification result is right. The PDCCH may be mapped to a control resource set (CORESET) configured for the UE, and may be transmitted.

[0090] For example, DCI that schedules a PDSCH associated with system information (SI) may be scrambled by an SI-RNTI. DCI that schedules a PDSCH associated with a random access response (RAR) message may be scrambled by an RA-RNTI. DCI that schedules a PDSCH associated with a paging message may be scrambled by a P-RNTI. DCI that reports a slot format indicator (SFI) may be scrambled by an SFI-RNTI. DCI that reports a transmit power control (TPC) may be scrambled by a TPC-RNTI. DCI that schedules a UE-specific PDSCH or PUSCH may be scrambled by a cell RNTI (C-RNTI).

[0091] DCI format 0_0 may be used as a fallback DCI that schedules a PUSCH. In this instance, a CRC may be scrambled by a C-RNTI. DCI format 0_0 with a CRC, scrambled by a C-RNTI, may include, for example, the following information.

TABLE-US-00007 TABLE 5 - Identifier for DCI formats- [1] bit - Frequency domain resource assignment- [?log.sub.2(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 - TPC command for scheduled PUSCH .sub.(transmit power control command for .sub.scheduled PUSCH)- [2] bits - UL/SUL indicator.sub.(uplink/supplementary uplink (UL) indicator)- 0 or 1 bit

[0092] DCI format 0_1 may be used as a non-fallback DCI that schedules a PUSCH. In this instance, a CRC may be scrambled by a C-RNTI. DCI format 0_1 with a CRC, scrambled by a C-RNTI, may include, for example, the following information.

TABLE-US-00008 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 /P? bits For resource allocation type 1, ?log.sub.2(N (N )/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 subcodebooks; 0 bit otherwise. - TPC command for scheduled PUSCH - 2 bits - SRS resource indicator -[00001]$.Math.{\log }_2\left(.Math.\text{?}\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]$.Math.{\log }_2\left(.Math.\text{?}\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};$ ?log2(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 - CBG transmission information (code block group tranmsissio 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 - DMRS sequence initialization (demodulation reference signal sequence initialization) - 0 or 1 bit indicates data missing or illegible when filed

[0093] DCI format 1_0 may be used as a fallback DCI that schedules a PDSCH. In this instance, a CRC may be scrambled by a C-RNTI. DCI format 1_0 with a CRC, scrambled by a C-RNTI may include, for example, the following information.

TABLE-US-00009 TABLE 7 - Identifier for DCI formats - [1] bit - Frequency domain resource assignment -[?log.sub.2(N.sub.RB.sup.DL,BWP(N.sub.RB.sup.DL,BWP + 1)/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 - PUCCH resource indicator .sub.(physical uplink control channel, PUCCH) resource indicator - 3 bits - PDSCH-to-HARQ feedback timing indicator - [3] bits

[0094] DCI format 1_1 may be used as a non-fallback DCI that schedules a PDSCH. In this instance, a CRC may be scrambled by a C-RNTI. DCI format 1_1 with a CRC, scrambled by a C-RNTI, may include, for example, the following information.

TABLE-US-00010 TABLE 8 - Carrier indicator - 0 or 3 bits - 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.DL,BWP/ P? bits For resource allocation type 1, ?log.sub.2(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. - PRB bundling size indicator- 0 or 1 bit - Rate matching indicator- 0, 1, or 2 bits - ZP CSI-RS 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 data indicator - 1 bit - Redundancy version - 2 bits - HARQ process number - 4 bits - Downlink assignment index - 0 or 2 or 4 bits - TPC command for scheduled PUCCH - 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 - CBG flushing out information (code block group flushing out info.) - 0 or 1 bit - DMRS sequence initialization - 1 bit

[0095] Hereinafter, a method of allocating a time domain resource to a data channel in a 5G communication system will be described.

[0096] A base station may configure a table associated with time domain resource allocation information associated with a downlink data channel (PDSCH) and an uplink data channel (PUSCH) for a UE via a higher layer signaling (e.g., RRC signaling). The base station may configure a table including a maximum of maxNrofDL-Allocations=16 entries (entry) in association with a PDSCH, and may configure a table including a maximum of maxNrofUL-Allocations=16 entries in association with a PUSCH. The time domain resource allocation information may include, for example, a PDCCH-to-PDSCH slot timing (a slot unit-based time interval between the point in time at which a PDCCH is received and the point in time at which a PDSCH is transmitted which is scheduled by the received PDCCH, and denoted by K0) or a PDCCH-to-PUSCH slot timing (a slot unit-based time interval between the point in time at which a PDCCH is received and the point in time at which a PUSCH is transmitted which is scheduled by the received PDCCH, and denoted by K2), information on the location and the length of a start symbol where a PDSCH or a PUSCH is scheduled in a slot, a mapping type of a PDSCH or PUSCH, and the like. For example, the information shown in the Tables 9 and 10 below may be reported from a base station to a UE.

TABLE-US-00011 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, slot unit) mappingType ENUMERATED {typeA, typeB}, (PDSCH mapping type) startSymbolAndLength INTEGER (0..127) (PDSCH start symbol and length of PDSCH) }

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

[0097] A base station may inform a UE of one of the entries in the table associated with the time domain resource allocation information via L1 signaling (e.g., DCI) (for example, providing indication using a time domain resource allocation field in DCI). The UE may obtain the time domain resource allocation information associated with the PDSCH or PUSCH based on the DCI received from the base station.

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

[0099] FIG. 2 is a diagram illustrating an example of a control region in which a downlink control channel is transmitted in the 5G wireless communication system. FIG. 2 illustrates an example of two control regions (control region #1 201 and control region #2 202) configured within a UE bandwidth part 210 in the frequency axis and one slot 220 in the time axis. The control regions 201 and 202 may be configured in a predetermined frequency resource 203 of the entire UE bandwidth part 210 in the frequency axis. In the time axis, the control region may be configured based on one or multiple OFDM symbols, which may be defined as a control region length 204 (control resource set duration). With reference to the example of FIG. 2, the control region #1 201 is configured based on a control region length of two symbols, and the control region #2 202 is configured based on a control region length of one symbol.

[0100] The above-described control region in 5G may be configured by a base station for a UE via higher layer signaling (e.g., system information, an MIB, RRC signaling). Configuring a control region for a UE may be providing information associated with the identity of the control region, the frequency location of the control region, the length of symbols of the control region, and the like. For example, the higher layer signaling may include information as shown in Table 11 below.

TABLE-US-00013 TABLE 11 ControlResourceSet ::= SEQUENCE { Corresponds to L1 parameter CORESET-ID controlResourceSetId ControlResourceSetId, (control area identity) frequencyDomainResources BIT STRING (SIZE (45)), (frequency domain resource assignment information) duration INTEGER (1..maxCoReSetDuration), (time domain resource assignment 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) }, nonInterleaved NULL }, tci-StatesPDCCH SEQUENCE(SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL, (QCL configuration information) tci-PresentInDCI ENUMERATED {enabled} OPTIONAL, -- Need S }

[0101] In Table 11, tci-StatesPDCCH (simply referred to as a transmission configuration indication (TCI) state) configuration information may include information associated with the index of one or multiple SS/PBCH blocks that are in QCL relationship with a DMRS transmitted in a corresponding control region or information associated with a channel state information reference signal (CSI-RS) index.

[0102] For example, each control information included in DCI format 1_1 that is scheduling control information (DL grant) for downlink data may be as follow. [0103] Carrier indicator: indicates a carrier on which data scheduled by DCI is to be transmitted0 or 3 bits [0104] Identifier for DCI formats: an indicator indicating a DCI format, and specifically, indicating whether the corresponding DCI is for a downlink or for an uplink[1] bits [0105] Bandwidth part indicator: indicates a change of a bandwidth part when there is a change0, 1 or 2 bits [0106] Frequency domain resource assignment: resource allocation information that indicates frequency domain resource allocation, and expresses a different resource depending on whether a resource allocation type is 0 or 1. [0107] Time domain resource assignment: resource allocation information indicating time-domain resource allocation, which may indicate a configuration of a predetermined PDSCH time-domain resource allocation list or higher layer signaling1, 2, 3, or 4 bits [0108] VRB-to-PRB mapping: indicates a mapping relationship between a virtual resource block (VRB) and a physical resource block (PRB)0 or 1 bit [0109] PRB bundling size indicator: indicates the size of a physical resource block bundling that is assumed to have the same precoding applied0 or 1 bit [0110] Rate matching indicator: indicates a rate match group to be applied to a PDSCH among rate match groups configured via a higher layer0, 1, or 2 bits [0111] ZP CSI-RS trigger: triggers a zero-power channel state information reference signal0, 1, or 2 bits [0112] 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. [0113] Modulation and coding scheme (MCS): indicates a modulation scheme and a coding rate used for data transmission. That is, the MCS indicates a TBS and a coding rate value indicating channel coding information, together with information indicating QPSK, 16QAM, 64QAM, or 256QAM. [0114] New data indicator: indicates HARQ initial transmission or HARQ retransmission. [0115] Redundancy version: indicates the redundancy version of HARQ. [0116] HARQ process number: indicates an HARQ process number applied to a PDSCH4 bits [0117] Downlink assignment index: an index for producing a dynamic HARQ-ACK codebook when reporting an HARQ-ACK associated with a PDSCH0 or 2 or 4 bits [0118] TPC command for scheduled PUCCH: power control information applied to a PUCCH for reporting an HARQ-ACK associated with a PDSCH-2 bits [0119] PUCCH resource indicator: information indicating a resource of a PUCCH for reporting an HARQ-ACK associated with a PDSCH3 bits [0120] PDSCH-to-HARQ_feedback timing indicator: configuration information associated with a slot in which a PUCCH for reporting an HARQ-ACK associated with a PDSCH is transmitted3 bits [0121] Antenna ports: information indicating an antenna port of a PDSCH DMRS and a DMRS CDM group in which a PDSCH is not transmitted4, 5 or 6 bits [0122] Transmission configuration indication: information indicating beam-related information of a PDSCH-0 or 3 bits [0123] SRS request: information requesting SRS transmission2 bits [0124] CBG transmission information: information indicating data corresponding to which code block group (CBG) is to be transmitted via a PDSCH in case that code block group-based retransmission is configured0, 2, 4, 6, or 8 bits [0125] CBG flushing out information: information indicating whether a code block group that a UE previously receives is usable for HARQ combining0 or 1 bit [0126] DMRS sequence initialization: indicates a DMRS sequence initialization parameter1 bit

[0127] In the case of data transmission via a PDSCH or a PUSCH, time domain resource assignment may be transferred via information associated with a slot in which a PDSCH/PUSCH is transmitted, a start symbol location S of the corresponding slot, and the number L of symbols to which the PDSCH/PUSCH is mapped. Herein, S denotes a relative location from the start of a slot. L denotes the number of consecutive symbols. S and L may be determined based on a start and length indicator value (SLIV) defined by Equation 1 below.

TABLE-US-00014 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...Equation 1

[0128] In the NR system, information associated with an SLIV value, a PDSCH/PUSCH mapping type, and a slot in which a PDSCH/PUSCH is transmitted (e.g., the information may be configured in the form of a table) may be configured in a single line for a UE via an RRC configuration. Subsequently, in the time domain resource assignment of the DCI, by indicating an index value in the configured table, a base station may transfer, to the UE, information associated with an SLIV value, a PUSCH mapping type, and a slot in which a PDSCH/PUSCH is transmitted.

[0129] In the NR system, a PDSCH mapping type may include type A and type B. According to PDSCH mapping type A, a first symbol of DMRS symbols is located at a second or third OFDM symbol in a slot. According to PDSCH mapping type B, a first symbol of DMRS symbols is located at a first OFDM symbol in the time domain resource allocated via PUSCH transmission.

[0130] Downlink data may be transmitted on a PDSCH which is a physical channel for downlink data transmission. The PDSCH may be transmitted after the control channel transmission interval. Scheduling information such as a detailed mapping location in the frequency domain, a modulation scheme, and the like may be determined based on DCI transmitted via the PDCCH.

[0131] Via an MCS in the control information included in the DCI, a base station reports a 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 include 5 bits or may include more or fewer bits than 5 bits. The TBS corresponds to a size before channel coding for error correction is applied to data (transport block (TB)) that the base station desires to transmit.

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

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

[0134] FIGS. 3 and 4 are diagrams illustrating examples in which data for eMBB, URLLC, and mMTC, which are services considered in a 5G or NR system, are allocated in the frequency-time resources.

[0135] Referring to FIGS. 3 and 4, there is provided a scheme of allocating frequency and time resources for transmitting information in each system.

[0136] FIG. 3 is a diagram illustrating an example in which eMBB, URLLC, and mMTC data are allocated in the entire system frequency band. FIG. 3 illustrates data for eMBB, URLLC, and mMTC that have been allocated in the entire system frequency band 300. If URLLC data 303, 305, and 307 is produced and needs to be transmitted, while eMBB 301 and mMTC 309 are allocated and transmitted in a predetermined frequency band, the eMBB 301 and the mMTC 309 may empty previously allocated parts or may not perform transmission, so that the URLLC data 303, 305, and 307 may be transmitted. Among the services, URLLC needs to reduce latency, and thus, the URLLC data may be allocated to a part of the resource 301 where eMBB is allocated, and may be transmitted. If URLLC is additionally allocated and transmitted in the resource to which eMBB is allocated, eMBB data may not be transmitted in the overlapping frequency-time resources. Accordingly, the performance of transmission of the eMBB data may be decreased. In other words, the transmission of the eMBB data may fail due to the allocation of URLLC.

[0137] FIG. 4 is a diagram illustrating an example in which eMBB, URLLC, and mMTC data are allocated in separate system frequency bands. In FIG. 4, the entire system frequency band 400 may be divided, and each sub-band 402, 404, and 406 may be used for transmitting a service and data. Information related to a configuration of the sub-bands may be determined in advance, and the information may be transmitted from a base station to a UE via higher signaling. Alternatively, a base station or a network node may arbitrarily determine sub-bands and provide services without separately transmitting sub-band configuration information to a UE. FIG. 4 illustrates that the sub-band 402 is used for transmission of eMBB data, the sub-band 404 is used for transmission of URCCL data, and the sub-band 406 is used for transmission of mMTC data.

[0138] In order to describe a method and device proposed in the embodiments, terms, physical channel and signal used in the NR system may be used. However, the disclosure may be applicable to a wireless communication system other than the NR system.

[0139] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings. In the following description of the disclosure, a detailed description of known functions or configurations incorporated herein will be omitted when it may make the subject matter of the disclosure rather unclear. The terms to be described below are terms defied by taking into consideration functions in the disclosure, and may be changeable by a user, intention of an operator, custom, or the like. Therefore, the definitions of the terms should be made based on the contents throughout the specification.

[0140] In the disclosure, a downlink (DL) is a wireless transmission path of a signal that a base station transmits to a UE. An uplink is a wireless transmission path of a signal that a UE transmits to a base station.

[0141] Hereinafter, although an embodiment of the disclosure is described by taking the NR system as an example, the embodiment of the disclosure may be applicable to other communication systems having a similar technical background or a similar channel type. In addition, the embodiments of the disclosure may be modified by those skilled in the art without departing from the scope of the disclosure, and may be applied to other communication systems.

[0142] In the disclosure, terms physical channel and signal conventionally used may be interchangeably used with the term data or control signal. For example, although a PDSCH is a physical channel that delivers data, a PDSCH may be considered as data in the description provided below.

[0143] Hereinafter, higher signaling is signal transferring from a base station to a UE via a downlink data channel of a physical layer, or signal transferring from a UE to a base station via an uplink data channel of a physical layer, which may also be referred to as RRC signaling or MAC control element (MAC CE).

[0144] FIG. 5 is a diagram illustrating an example of a process in which a single transport block is divided into multiple code blocks, and CRCs are added thereto.

[0145] Referring to FIG. 5, a CRC 503 may be added to the end or the front part of a single transport block (TB) 501 to be transmitted in an uplink or a downlink. The CRC 503 may have 16 bits, 25 bits, or a predetermined number of bits, or may have bits, the number of which is variable depending on a channel condition or the like. The CRC 503 may be used for determining whether channel coding is successfully performed. A block including the TB 501 and the CRC 503 may be divided into multiple code blocks (CB) 507, 509, 511, and 513 as shown in diagram 505. Here, the maximum size for a codeblock is predetermined and is used for division. In this instance, the last codeblock 513 may be smaller than the other codeblocks 507, 509, and 511. However, this is merely an example, and according to another example, by inserting 0, a random value, or 1 to the last codeblock 513, the last code block 513 and the other codeblocks 507 and 509, and 511 may be adjusted to have the same length.

[0146] In addition, CRCs 517, 519, 521, and 523 may be added to the code blocks 507, 509, 511, and 513, respectively, as shown in the diagram 515. The CRC may have 16 bits, 24 bits, or a predetermined number of bits, and may be used for determining whether channel coding is successfully performed.

[0147] In order to produce the CRC 503, the TB 501 and a cyclic generator polynomial may be used. The cyclic generator polynomial may be defined by various methods. For example, if it is assumed that cyclic generator polynomial for 24-bit CRC is gCRC24A(D)=D24+D23+D18+D17+D14+D11+D10+D7+D6+D5+D4+D3+D+1, and L=24, a value that has a remainder of 0 obtained by dividing a.sub.0D.sup.A+23+a.sub.1D.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) may be determined as p.sub.0, p.sub.1, p.sub.2, p.sub.3, . . . , p.sub.L-1 in case of the CRC p.sub.0, p.sub.1, p.sub.2, p.sub.3, . . . , p.sub.L-1 for TB data a.sub.0, a.sub.1, a.sub.2, a.sub.3, . . . , a.sub.A-1 Although the above-described example has been described on the assumption that the length L of a CRC is 24, the length L of a CRC may be determined variously, such as 12, 16, 24, 32, 40, 48, 64, and the like.

[0148] A CRC is added to a TB according to the described process, and the TB+CRC may be divided into N CBs 507, 509, 511, and 513. CRCs 517, 519, 521, and 523 may be added to the CBs 507, 509, 511, and 513 obtained via division, respectively, as shown in the diagram 515. A CRC added to a CB may have a length different from a length of a CRC added to a TB, or another cyclic generator polynomial may be used for producing a CRC. In addition, the CRC 503 added to the TB and the CRCs 517, 519, 521, and 523 added to the codeblocks may be omitted depending on the types of channel codes to be applied to the codeblocks. For example, in case that an LDPC code, instead of a turbo code, is applied to a code block, the CRCs 517, 519, 521, 523 to be respectively added to code blocks may be omitted.

[0149] However, although an LDPC is applied, the CRCs 517, 519, 521, and 523 may be added to code blocks, as usual. In case that a polar code is used, a CRC may be added or may be omitted.

[0150] As described in FIG. 5, the maximum length of a single code block may be determined based on the type of channel coding to be applied to a TB desired to be transmitted, and the TB and a CRC to be added to the TB may be divided into code blocks based on the maximum length of a code block.

[0151] In the legacy LTE system, a CRC for a CB may be added to a CB obtained via division. A data bit of a CB and a CRC may be encoded into a channel code and coded bits are determined. The number of rate match bits may be determined as previously determined for each coded bit.

[0152] The size of a TB (TBS) in the NR system may be calculated via the following steps.

[0153] Step 1: calculates the number N.sub.RE of REs allocated to PDSCH mapping in a single PRB within an allocated resource.

[0154] N.sub.RE may be calculated via 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 denotes the number of OFDM symbols allocated to a PDSCH. N.sub.DMRS.sup.PRB denotes the number of REs in a single PRB that a DMRS of the same CDM group occupies. N.sub.oh.sup.PRB denotes the number of REs occupied by overhead in a single PRB configured via higher signaling, and may be configured as one of 0, 6, 12, and 18. Subsequently, a total number N.sub.RE of REs allocated to a PDSCH may be calculated N.sub.RE may be calculated based on min(156, N.sub.RE).Math.n.sub.PRB, and n.sub.PRB may denote the number of PRBs allocated to a UE.

[0155] Step 2: the number N.sub.info of temporary information bits may be calculated via N.sub.RE*R*Q.sub.m*v. Here, R denotes a code rate, and Qm denotes a modulation order. Information associated with the value may be transferred via an MCS bit field of DCI and a predetermined Table. In addition, v denotes the number of allocated layers. In the case of N.sub.info?3824, a TBS may be calculated according to step 3 described below. In other cases, a TBS may be calculated according to step 4.

[0156] Step 3: N.sub.info may be calculated by using equations

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

and n=max(3,?log.sub.2(N.sub.info)??6). A value that is closest to N.sub.info among values not less than N.sub.info in Table 12 shown below may be determined as a TBS.

TABLE-US-00015 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

[0157] Step 4: N.sub.info may be calculated by using equations

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

and n=?log.sub.2(N.sub.info?24)??5. A TBS may be determined based on a N.sub.info value and [pseudo-code 1]. C shown below denotes the number of codeblocks included in a single TB.

TABLE-US-00016 [Pseudo-code 1 start] if R ? 1/4 [00005]$\mathrm{TBS}=8*C*.Math.\frac{N_{\mathrm{info}}^{}+24}{8*C}.Math.-24,$ where [00006]$C=.Math.\frac{N_{\mathrm{info}}^{}+24}{3816}.Math.$ else if N.sub.info > 8424 [00007]$\mathrm{TBS}=8*C*.Math.\frac{N_{\mathrm{info}}^{}+24}{8*C}.Math.-24,$ where [00008]$C=.Math.\frac{N_{\mathrm{info}}^{}+24}{8424}.Math.$ else [00009]$\mathrm{TBS}=8*.Math.\frac{N_{\mathrm{info}}^{}+24}{8}.Math.-24$ end if end if

[0158] In the NR system, in case that a single CB is input into an LDPC encoder, parity bits may be added thereto and may be output. In this instance, the number of parity bits may differ depending on an LDCP base graph. A method of sending all parity bits produced via LDPC coding for a predetermined input may be referred to as full buffer rate matching (FBRM), and a method of limiting the number of transmittable parity bits may be referred to as a limited buffer rate matching (LBRM). In case that resources are allocated for data transmission, an LDPC encoder output is produced to be a circular buffer, and bits of the produced buffer are transmitted repeatedly as many times as the allocated resources allow. In this instance, the length of the circular buffer is referred to as Ncb.

[0159] In case that the number of all parity bits produced by LDPC coding is N, it is determined that Ncb=N according to the FBRM method. In the LBRM method, Ncb is min(N, N.sub.ref), N.sub.ref is given as

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

and R.sub.LBRM is determined to be ?. To obtain TBS.sub.LBRM, the above-described method of obtaining a TBS may be used. In this instance, calculation may be performed by assuming the maximum number of layers and the maximum modulation order that a UE supports in a corresponding cell. The maximum modulation order Qm may be assumed to be 8 in case that the corresponding cell is configured to use an MCS table that supports 256QAM for at least one BWP. Otherwise, the maximum modulation order Qm may be assumed to be 6 (64QAM). A code rate may be assumed to be a maximum code rate of 948/1024. N.sub.RE is assumed to be 156.Math.n.sub.PRB. n.sub.PRB is assumed to be n.sub.PRB,LBRM. n.sub.PRB,LBRM may be given as shown in Table 13 below.

TABLE-US-00017 TABLE 13 Maximum number of PRBs across all configured DL BWPs and UL BWPs of a carrier for DL-SCH and UL-SCH respectively 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

[0160] The maximum data rate that a UE supports in the NR system may be determined according to Equation 2 below.

[00011]$\begin{array}{cc}\mathrm{data}\mathrm{rate}(\mathrm{in}\mathrm{Mbps})={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),?}.Math.12}{T_s^{?}}.Math.\left(1-{\mathrm{OH}}^{\left(j\right)}\right)\right)& \mathrm{Equation}2\end{array}$

[0161] In Equation 2, J is the number of carriers bound by carrier aggregation, Rmax=948/1024, v.sub.Layers.sup.(j) denotes the maximum number of layers, Q.sub.m.sup.(j) denotes the maximum modulation order, f.sup.(j) denotes a scaling index, and ? denotes a subcarrier spacing. One of 1, 0.8, 0.75, and 0.4 may be reported by the UE as f.sup.(j), and ? may be given as shown in Table 14 below.

TABLE-US-00018 TABLE 14 ? ?f = 2.sup.? .Math. 15[kHz] Cyclic prefix 0 15 Normal 1 30 Normal 2 60 Normal, Extended 3 120 Normal 4 240 Normal

[0162] In addition, T.sub.s.sup.? denotes an average OFDM symbol length, T.sub.s.sup.? may be calculated based on

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

and N.sub.PRR.sup.BW(j),? denotes the maximum number of RBs in BW(j). OH.sup.(j) is an overhead value, and may be 0.14 in a downlink and 0.18 in an uplink of FR1 (a 6 GHz or lower band), and may be 0.08 in a downlink and 0.10 in an uplink of FR2 (a band higher than 6 GHz). In a cell having a frequency bandwidth of 100 MHz with a subcarrier spacing of 30 kHz, the maximum data rate in a downlink may be calculated by using Equation 2, as shown in Table 15 below.

TABLE-US-00019 TABLE 15 f.sup.(j) v.sub.Layers.sup.(j) Q.sub.m.sup.(j) Rmax N.sub.PRB.sup.BW(j), ? T.sub.s.sup.? OH.sup.(j) 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

[0163] Conversely, an actual data rate measurable by a UE in actual data transmission may be a value obtained by dividing the amount of data by a data transmission time. This may be a value obtained by dividing, by a TTI length, a TBS in case of 1 TB transmission or the sum of TBSs in case of 2 TB transmission. For example, in a cell having a frequency bandwidth of 100 MHz with a subcarrier spacing of 30 kHz, which is the same condition used for obtaining Table 15, the actual maximum data rate in a downlink may be determined based on the number of allocated PDSCH symbols, as shown in Table 16 below.

TABLE-US-00020 TABLE 16 TTI length data rate N.sub.symb.sup.sh N.sub.DMRS.sup.PRB N.sub.RE.sup. N.sub.RE N.sub.info n N.sub.info.sup. C TBS (ms) (Mbps) 3 8 28 7644 226453.5 12 225,280 27 225,480 0.107143 2,104.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.5 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.464286 2,612.68 14 8 160 43680 1294020.0 15 1,277,952 152 1,277,992 0.500000 2,555.98

[0164] The maximum data rate that a UE supports may be identified via Table 15, and an actual data rate based on an allocated TBS may be identified via Table 16. In this instance, an actual data rate may happen to be higher than the maximum data rate depending on scheduling information.

[0165] In a wireless communication system, particularly, in the new radio (NR) system, a data rate supportable by a UE may be mutually agreed upon between a base station and the UE. That may be calculated using the maximum frequency band, the maximum modulation order, the maximum number of layers, and the like supported by the UE. However, the calculated data rate may be different from a value calculated based on a transport block (TB) size (TBS) and the length of a transmission time interval (TTI) used for actual data transmission.

[0166] Accordingly, the UE may happen to be assigned with a larger TBS than a value corresponding to a data rate supported by the UE itself. To prevent the situation, there may be the restriction of a schedulable TBS depending on a data rate supported by the UE.

[0167] FIG. 6 is a diagram illustrating a synchronization signal (SS) of the NR system and a physical broadcast channel (PBCH) which are mapped in the frequency and time domain.

[0168] A primary synchronization signal (PSS) 601, a secondary synchronization signal (SSS) 603, and PBCHs are mapped to 4 OFDM symbols. Each of the PSS and the SSS is mapped to 12 RBs and the PBCHs are mapped to 20 RBs. The table in FIG. 6 shows the frequency band of 20 RBs that varies depending on a subcarrier spacing (SCS). A resource area in which the PSS, SSS, and PBCHs are transmitted is referred to as an SS/PBCH block (SS/PBCH block). In addition, the SS/PBCH block may be referred to as an SSB block.

[0169] FIG. 7 is a diagram illustrating symbols in which an SS/PBCH block is capable of being transmitted based on a subcarrier spacing.

[0170] Referring to FIG. 7, a subcarrier spacing may be set to 15 kHz, 30 kHz, 120 kHz, 240 kHz, or the like, and the location of a symbol in which an SS/PBCH block (or an SSB block) is capable of being located may be determined based on each subcarrier spacing. FIG. 7 illustrates the location of a symbol in which an SSB is capable of being transmitted based on a subcarrier spacing in symbols within 1 ms, but it is not that an SSB is always transmitted in the area marked in FIG. 7. Therefore, the location in which an SSB block is transmitted may be configured for a UE via system information or dedicated signaling.

[0171] Generally, a UE is distant from a base station and thus, a signal transmitted from the UE may be received by the base station after a propagation delay time (propagation delay). The propagation delay time is a value obtained by dividing, by the speed of light, a path in which an electromagnetic wave is transferred from the UE to the base station. Generally, the propagation delay time may be a value obtained by dividing the distance from the UE to the base station by the speed of light. According to an embodiment, in case of a UE located 100 km away from a base station, a signal transmitted from the UE may be received by the base station in approximately 0.34 msec. Conversely, a signal transmitted from the base station is also received by the UE in approximately 0.34 msec. As described above, depending on the distance between the UE and the base station, a time that a signal transmitted from the UE arrives at the base station may differ. Therefore, in case that multiple UEs located in different locations simultaneously transmit signals, times that the signals arrive at a base station may be different from one another. In order to solve the problem and to enable signals transmitted from multiple UEs to arrive at a base station at the same time, a time at which an uplink signal is to be transmitted may be set to be different for each UE depending on a location. In the 5G, NR, and LTE systems, that is referred to as timing advance.

[0172] FIG. 8 is a diagram illustrating a UE processing time based on timing advance when the UE receives a first signal and transmits a second signal in response thereto in the 5G or NR system according to an embodiment.

[0173] Hereinafter, a UE processing time based on timing advance will be described in detail. In case that a base station transmits an uplink scheduling grant (UL grant) or a downlink control signal and data (DL grant and DL data) to a UE in slot n 802, the UE may receive the uplink scheduling grant or the downlink control signal and the data in slot n 804. In this instance, the UE may receive a signal a propagation delay time (Tp) 810 later than a time at which the base station transmits the signal. In the embodiment, in case that the UE receives a first signal in slot n 804, the UE transmits a corresponding second signal in slot n+4 806. In the case of signal transmission by the UE to the base station, to enable a signal to arrive at the base station at a predetermined time, the UE may transmit uplink data or an HARQ ACK/NACK associated with downlink data at a timing 806 that is timing advance (TA) 812 earlier than slot n+4 based on a signal received by the UE. Therefore, in the embodiment, a period of time 814 allowed for the UE to prepare transmission of uplink data after receiving an uplink scheduling grant or to prepare transferring an HARQ ACK or NACK after receiving downlink data may be a time excluding a TA from a time corresponding to three slots.

[0174] In order to determine the above-described timing, the base station may calculate the absolute value of a TA of the corresponding UE. The base station may calculate the absolute value of a TA by adding, to a TA value that the base station initially transmits to the UE at a random access stage at the initial access, a change in the TA value transferred via higher signaling or by subtracting the change therefrom. In the disclosure, the absolute value of the TA may be a value obtained by subtracting the start time of an n.sup.th TTI received by the UE from the start time of an n.sup.th TTI transmitted by the UE.

[0175] One of the important criteria for determining the performance of a cellular wireless communication system is packet data latency. To this end, in the LTE system, a signal is transmitted or received in units of subframes, each subframe having a transmission time interval (TTI) of 1 ms. In the LTE system that operates as described above, a UE (a short-TTI UE) that has a transmission time interval shorter than 1 ms may be supported. In the 5G or NR system, a transmission time interval may be shorter than 1 ms. The short-TTI UE is suitable for a service that takes latency as an important factor, such as a voice over LTE (VOLTE) service, a remote control service, or the like. In addition, the short-TTI UE is a device that is capable of implementing mission-critical Internet of Things (IOT) based on a cellular network.

[0176] In the 5G or NR system, in case that the base station transmits a PDSCH including downlink data, DCI that schedules a PDSCH may indicate a K1 value corresponding to timing information associated with a timing at which the UE transmits HARQ-ACK information associated with the PDSCH. The UE may transmit HARQ-ACK information to the base station in case it is not indicated to transmit HARQ-ACK information before symbol L1 by including timing advance. That is, the HARQ-ACK information may be transmitted from the UE to the base station at the same time of or after symbol L1, by including timing advance. In case that it is indicated to transmit HARQ-ACK information before symbol L1 by including timing advance, HARQ-ACK information may not be valid HARQ-ACK information in HARQ-ACK transmission from the UE to the base station.

[0177] Symbol L1 may be a first symbol in which a cyclic prefix (CP) starts T.sub.proc,1 after the last point of a PDSCH. T.sub.proc,1 may be calculated as given in Equation 3 below.

[00013]$\begin{array}{cc}{T}_{\mathrm{proc},1}=\left(\left(N_1+d_{1,1}+d_{1,2}\right)\left(2048+144\right).Math.{\mathrm{?2}}^{-?}\right).Math.T_C& \mathrm{Equation}3\end{array}$

[0178] In the above-described Equation 3, N1, d1,1, d1,2, ?, ?, and TC may be defined as described below. [0179] In case that HARQ-ACK information is transmitted via a PUCCH (uplink control channel), d1,1=0. In case that HARQ-ACK information is transmitted via a PUSCH (uplink shared channel, data channel), d1,1=1. [0180] In case that the UE is configured with a plurality of activated component carriers or carriers, the maximum timing difference between carriers may be applied to second signal transmission. [0181] In case of PDSCH mapping type A, that is, in case that the location of a first DMRS symbol is a third or fourth symbol in a slot, if the location index i of the last symbol of a PDSCH is less than 7, it is defined that d1,2=7?i. [0182] In case of PDSCH mapping type B, that is, in case that the location of a first DMRS symbol is a first symbol of a PDSCH, when the length of the PDSCH is 4 symbols, d1,2-3, and when the length of the PDSCH is 2 symbols, d1,2=3+d. d is the number of symbols in which a PDSCH overlaps a PDCCH including a control signal that schedules the corresponding PDSCH. [0183] N1 may be defined based on u as shown in Table 17 below. ?=0, 1, 2, 3 denote subcarrier spacings 15 kHz, 30 kHz, 60 kHz, and 120 kHz, respectively.

TABLE-US-00021 TABLE 17 PDSCH decoding time N.sub.1 [symbols] No additional PDSCH Additional PDSCH ? DM-RS configured DM-RS configured 0 8 13 1 10 13 2 17 20 3 20 24 [0184] Instead of the N1 value provided in the above-described Table 17, another value may be used depending on UE capability. [0185] It is defined that

[00014]$T_c=1/\left(?f_{\max }.Math.N_f\right),?f_{\max }=480.Math.{10}^3\mathrm{Hz},N_f=4096,?=T_s/T_c=64,T_s=1/\left(?f_{\mathrm{ref}}.Math.N_{f,\mathrm{ref}}\right),?f_{\mathrm{ref}}=15.Math.{10}^3\mathrm{Hz},N_{f,\mathrm{ref}}=2048$ respectively.

[0186] In addition, in the 5G or NR system, in case that the base station transmits control information including an uplink scheduling grant, the UE may indicate a K2 value corresponding to timing information of a timing at which the UE transmits uplink data or a PUSCH.

[0187] The UE may transmit a PUSCH to the base station in case that it is not indicated to transmit the PUSCH before symbol L2 by including timing advance. That is, by including timing advance, the PUSCH may be transmitted from the UE to the base station at the same time of or after symbol L2. In case that it is indicated to transmit a PUSCH before symbol L2 by including timing advance, the UE may disregard an uplink scheduling grant control information obtained from the base station.

[0188] The symbol L2 may be a first symbol in which a CP of a PUSCH symbol starts, wherein the PUSCH symbol needs to be transmitted T.sub.proc,2 after the last point of a PDCCH including a scheduling grant. T.sub.proc,2 may be calculated as given in Equation 4 below.

[00015]$\begin{array}{cc}{T}_{\mathrm{proc},2}=\left(\left(N_2+d_{2,1}\right)\left(2048+144\right).Math.{\mathrm{?2}}^{-?}\right).Math.T_C& \mathrm{Equation}4\end{array}$

[0189] In the above-described Equation 4, N2, d2,1, ?, ?, and TC may be defined as below. [0190] In case that a first symbol among the symbols to which a PUSCH is allocated includes only a DMRS, d2,1=0. Otherwise, d2,1=1. [0191] In case that a UE is configured with a plurality of activated component carriers or carriers, the maximum timing difference between carriers may be applied to second signal transmission. [0192] N2 may be defined based on u as shown in Table 18 below. ?=0, 1, 2, 3 denote subcarrier spacings 15 kHz, 30 kHz, 60 kHz, and 120 kHz, respectively.

TABLE-US-00022 TABLE 18 PUSCH preparation time N.sub.2 ? [symbols] 0 10 1 12 2 23 3 36 [0193] Instead of the N2 value provided in the above-described Table 18, another value may be used depending on UE capability. [0194] It is defined that

[00016]$T_c=1/\left(?f_{\max }.Math.N_f\right),?f_{\max }=480.Math.{10}^3\mathrm{Hz},N_f=4096,?=T_s/T_c=64,T_s=1/\left(?f_{\mathrm{ref}}.Math.N_{f,\mathrm{ref}}\right),?f_{\mathrm{ref}}=15.Math.{10}^3\mathrm{Hz},N_{f,\mathrm{ref}}=2048$ [0195] respectively.

[0196] The 5G or NR system may configure a frequency band part (BWP) in a single carrier and may designate a predetermined UE to perform transmission or reception in the configured BWP. This is to reduce the amount of power consumed by a UE. A base may configure a plurality of BWPs, and may change activated BWP using control information. A period of time that the UE is capable of spending in changing a BWP may be defined as shown in Table 19 below.

TABLE-US-00023 TABLE 19 Frequency Type 1 Type 2 Range Scenario delay (us) delay (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

[0197] In Table 19, frequency range 1 denotes a 6 GHz or lower frequency band, and frequency range 2 denotes a 6 GHz or higher frequency band. In the above-described embodiment, type 1 and type 2 may be determined based on UE capability. In the above-described embodiments, scenarios 1, 2, 3, and 4 may be given as shown in Table 20 below.

TABLE-US-00024 TABLE 20 change in no change in center frequency center frequency change in frequency scenario 3 scenario 2 bandwidth no change in scenario 1 scenario 4 in case frequency bandwidth that subcarrier spacing is changed

[0198] FIG. 9 is a diagram illustrating an example of scheduling and transmitting data (e.g., TBs) in slots, receiving a HARQ-ACK feedback associated with the corresponding data, and performing retransmission based on the feedback. In FIG. 9, TB1 900 is transmitted initially in slot 0 902, and an ACK/NACK feedback 904 thereto is transmitted in slot 4 906. In case that the initial transmission of TB1 fails and a NACK is received, retransmission 910 of TB1 may be performed in slot 8 908. The point in time at which the ACK/NACK feedback is transmitted and the point in time at which retransmission is performed may be determined in advance, or may be determined based on a value indicated by control information and/or a higher layer signaling.

[0199] FIG. 9 illustrates an example in which TB1 to TB8 are sequentially scheduled in slots from slot 0. That may be the case in which HARQ process IDs 0 to 7 are assigned to TB1 to TB8, respectively, and transmission is performed. In case that the number of HARQ process IDs that a base station and a UE are capable of using is only four, eight different TBs may not be successively transmitted.

[0200] FIG. 10 is a diagram illustrating an example of a communication system that uses a satellite. For example, in case that a UE 1001 transmits a signal to a satellite 1003, the satellite 1003 may transfer the signal to a base station 1005, and the base station 1005 may process the received signal and transmit the signal including a request for a subsequent operation to be performed thereon to the UE 1001. This may be transmitted via the satellite 1003, again. In the above description, the distance between the UE 1001 and the satellite 1003 is long and the distance between the satellite 1003 and the base station 1005 is also long and thus, a period of time spent in data transmission or reception between the UE 1001 and the base station 1005 may be long.

[0201] FIG. 11 is a diagram illustrating a revolution cycle of a communication satellite around the earth based on the altitude or height of the satellite. Satellites for communication may be classified based on the orbit of a satellite, such as a low Earth orbit (LEO), a middle Earth orbit (MEO), a geostationary Earth orbit (GEO), and the like. Generally, a GEO 1100 is a satellite located at an altitude of approximately 36000 km, an MEO 1110 a satellite located at an altitude in the range of 5000 to 15000 km, and an LEO is a satellite located at an altitude in the range of 500 to 1000 km. The revolution cycle of a satellite around the earth differs depending on an altitude. In the case of the GEO 1100, a revolution cycle is approximately 24 hours. In case of the MEO 1110, a revolution cycle is approximately 6 hours. In case of the LEO 1130, a revolution cycle is approximately 90 to 120 minutes. A LEO (?2,000 km) satellite has a relatively low altitude and thus, a propagation delay time (a period of time spent when a signal transmitted from a transmitter arrives at a receiver) and a loss may be lower than a GEO (36,000 km) satellite. A thing that is not a GEO satellite is referred to as a non-geostationary orbit (NGSO).

[0202] FIG. 12 is a conceptual diagram of satellite-UE direct communication. A satellite 1200 located at an altitude higher than 100 km via a rocket may perform signal transmission or reception with a UE 1210 on the earth, and may also perform signal transmission or reception with a ground station 1220 connected to a base station on the earth (DU farms) 1230.

[0203] FIG. 13 is a diagram illustrating a scenario of utilizing satellite-UE direct communication. The satellite-UE direct communication may support a communication service that is specialized in complementing the limit of coverage of a terrestrial network. For example, by embodying a satellite-UE direct communication function in a UE, a user emergency signal and/or disaster signal may be transmitted or received beyond a terrestrial communication coverage area as shown in diagram 1300, a mobile communication service may be provided to a user in an area where terrestrial network communication is unavailable such as a vessel and/or an airplane as shown in diagram 1310, the location of a vessel, a truck, and/or a drone may be traced and controlled in real time without restriction based on a border as shown in diagram 1320. Also, the UE may function as a backhaul of the base station by supporting a satellite communication function to a base station, and may utilize satellite communication so as to perform a backhaul function in case that the base station is physically far away as shown in diagram 1330.

[0204] FIG. 14 is a diagram illustrating an example of calculation of an expected data transmission rate (throughput) in an uplink in case that an LEO satellite located at an altitude of 1200 km and a UE on the earth perform direct communication. In case that, in an uplink, transmission power effective isotropic radiated power (EIRP) of a UE on the earth is 23 dBm, a path loss of a wireless channel to a satellite is 169.8 dB, and a satellite reception antenna gain is 30 dBi, an attainable signal to-noise ratio (SNR) may be estimated to be ?2.63 dB. In this instance, the pathloss may include a pathloss in space, a loss in the atmosphere, and the like. On the assumption that a signal-to-interference ratio (SIR) is 2 dB, a signal-to-interference and noise ratio (SINR) is calculated to be ?3.92 dB. In this instance, in case that a subcarrier spacing of 30 kHz and a frequency resource of 1 PRB are used, a transmission speed of 112 kbps may be attainable.

[0205] FIG. 15 is a diagram illustrating an example of calculation of an expected data transmission rate (throughput) in an uplink in case that a GEO satellite located at an altitude of 35,786 km and a UE on the earth perform direct communication. In case that, in an uplink, transmission power EIRP of a UE on the earth is 23 dBm, a path loss of a wireless channel to a satellite is 195.9 dB, and a satellite reception antenna gain is 51 dBi, an attainable SNR may be estimated to be ?10.8 dB. In this instance, the pathloss may include a pathloss in space, a loss in the atmosphere, and the like. On the assumption that an SIR is 2 dB, an SINR is calculated to be ?11 dB. In this instance, in case that a subcarrier spacing of 30 kHz and a frequency resource of 1 PRB are used, a transmission speed of 21 kbps may be attainable. This may be a result of repetitively performing transmission three times.

[0206] FIG. 16 is a diagram illustrating a pathloss value based on a pathloss model between a UE and a satellite, and a pathloss based on a pathloss model between a UE and a terrestrial base station. In FIG. 16, d denotes a distance, and f.sub.c denotes the frequency of a signal. In free space where communication between a UE and a satellite is performed, a pathloss (FSPL) 1600 is inversely proportional to the square of a distance. A path loss (PL.sub.2, PL.sub.Uma-NLOS) 1610 and 1620 on the earth where air is present and communication between the UE and the terrestrial base station (terrestrial gNB) is performed is inversely proportional to approximately the 4.sup.th power of a distance. d.sub.3D denotes the direct distance between a UE and a base station, h.sub.BS denotes the height of a base station, and h.sub.UT denotes the height of a UE. It is calculated that d.sub.BP=4?h.sub.BS?h.sub.UT?f.sub.c/c. fc denotes a center frequency in Hz, and c denotes the speed of light in m/s.

[0207] In satellite communications (or non-terrestrial network (NTN)), Doppler shift, that is, a frequency movement (offset) of a transmitted signal, is incurred since a satellite continuously moves fast.

[0208] FIG. 17 is a diagram illustrating a calculation equation and a calculation result in associated with the amount of Doppler shift that a signal experiences when the signal transferred from a satellite is received by a user on the earth according to the altitude and location of the satellite and the location of the user of a UE on the earth. R denotes the radius of the earth, h denotes the altitude of a satellite, v denotes the speed of the revolution of a satellite around the earth, and f.sub.c denotes the frequency of a signal. The speed of a satellite may be calculated based on the altitude of the satellite, and may be a speed at which gravity, the force of the earth pulling the satellite, is equal to centripetal force incurred when the satellite revolves. This may be calculated as described in FIG. 18.

[0209] FIG. 18 is a diagram illustrating the speed of a satellite calculated at the altitude of the satellite. As identified in FIG. 17, angle ? is determined based on an angle of altitude (elevation angle) ? and thus, a Doppler shift value may be determined based on the elevation angle ?.

[0210] FIG. 19 is a diagram illustrating Doppler shift that different UEs experience in a single beam that a satellite transmits to the earth. In FIG. 19, Doppler shift that each of UE 1 1900 and UE 2 1910 goes through is calculated based on the elevation angle ?. That is a result obtained on the assumption of a center frequency of 2 GHz, a satellite altitude of 700 km, a single beam's diameter of 50 km on the earth, and a UE speed of 0. In addition, in the disclosure, the Doppler shift is calculated by disregarding an effect of the rotation speed of the earth, which is considered as a minimal effect since it is slower than the speed of the satellite.

[0211] FIG. 20 is a diagram illustrating a difference in Doppler shift incurred in a single beam, depending on the location of a satellite determined based on an elevation angle. In case that the satellite is located right above a beam, that is, in the case of an elevation angle of 90 degrees, the difference in Doppler shift in the beam (or cell) is the highest. When the satellite is located in the center, Doppler shift values at one end and the other end of the beam have a positive value and a negative value, respectively.

[0212] In satellite communication, the distance from the satellite to a user on the earth is long and thus, a long delay may be incurred when compared to terrestrial network communication.

[0213] FIG. 21 is a diagram illustrating a latency taken from a UE to a satellite and a round trip latency among UE-satellite-base station, depending on the location of a satellite determined based on an elevation angle. Graph 2100 shows a latency taken from a UE to a satellite, and graph 2110 shows a round trip latency among a UE, a satellite, and a base station. In this instance, the latency between the satellite and base station is assumed to be the same as the latency between the UE and the satellite.

[0214] FIG. 22 is a diagram illustrating the maximum difference value in a round trip latency that differs depending on the location of a user in a single beam. For example, in case that a beam radius (or a cell radius) is 20 km, the difference in latency of a round trip to the satellite between UEs at different locations within a beam, the latency varying depending on the location of the satellite, may be less than or equal to approximately 0.28 ms.

[0215] The situation in which a UE performs signal transmission or reception with a base station in satellite communication may be the situation in which the signal is transferred via a satellite. That is, in a downlink, the satellite receives a signal that the base station transmits to the satellite, and the satellite transfers the same to the UE. In an uplink, the satellite receives a signal that the UE transmits, and transfers the same to the base station. In the above description, the satellite receives a signal and may transmit the same as it is by only shifting a frequency, or may perform signal processing based on the received signal such as decoding and re-encoding and transfer the same.

[0216] In the case of LTE or NR, a UE may access a base station via the following procedure. [0217] Step 1: A UE receives a synchronization signal (or synchronization signal block (SSB), which includes a broadcasting 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 associated with a boundary of a slot of a signal transmitted by a base station, a frame number, a downlink configuration, an uplink configuration, and the like. In addition, via a synchronization signal, a UE may obtain a subcarrier offset and scheduling information for transmitting system information. [0218] Step 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 random access may include resource information associated with a resource used for transmitting a random access preamble. [0219] Step 3: In a random access resource configured in step 2, a random access preamble (or message 1, msg1) is transmitted. The preamble may be a signal determined based on information configured in step 2 by using a predetermined numerical progression. The base station may receive the preamble transmitted by the UE. The base station attempts reception of a preamble configured in a resource configured by the base station, without knowing which UE transmits the preamble, and in case that reception is successfully performed, the base station may be aware that at least one UE transmits the preamble. [0220] Step 4: In case that the preamble is received in step 3, the base station transmits a random access response (RAR, or message 2, msg2) that is a response thereto. The UE that transmits the random access preamble in step 3 may attempt to receive the RAR transmitted by the base station in this step. The RAR is transmitted on a PDSCH, and a PDCCH that schedules the PDSCH is transmitted together or in advance. A CRC scrambled by an RA-RNTI value is added to DCI that schedules the RAR. The DCI (and CRC) may be channel coded and mapped to a PDCCH, and may be transmitted. The RA-RNTI may be determined based on time and frequency resources in which the preamble of step 3 is transmitted.

[0221] The maximum limited time in which the UE that transmits the random access preamble in step 3 receives the RAR in the step may be configured by the SIB transmitted in step 2. For example, this may be limitingly configured as a maximum of 10 ms, a maximum of 40 ms, or the like. That is, in case that the UE that transmits the preamble in step 3 fails to receive an RAR, for example, within a time determined based on the configured maximum time of 10 ms, the UE may transmit a preamble again. The RAR may include scheduling information that allocates a resource for a signal to be transmitted by the UE in step 5 which is a subsequent step.

[0222] FIG. 23 is a diagram illustrating an example of the structure of information of an RAR. An RAR 2300 may be, for example, a MAC PDU, and may include information 2310 associated with timing advance (TA) to be applied by the UE and a temporary C-RNTI value 2320 to be used from the next step. [0223] Step 5: The UE that receives the RAR in step 4 transmits message 3 (msg3) to the base station according to the scheduling information included in the RAR. The UE may include its unique ID value in msg3 and transmit the same. The base station may attempt to receive msg3 according to the scheduling information that the base station transmits in step 4. [0224] Step 6: The base station receives msg3, identifies ID information of the UE, produces message 4 (msg4) including the ID information of the UE, and transmits the same to the UE. Upon transmission of msg3 in step 5, the UE may attempt to receive msg4 to be transmitted in step 6. The UE having received msg4 performs decoding and compares an ID value included in msg4 with an ID value that the UE transmits in step 5, and identifies whether the base station receives msg3 that the UE transmits. A period of time for receiving msg4 in this step after the UE transmits msg3 in step 5 may be limited, and the maximum time may be configured via the SIB in step 2.

[0225] In case that the initial access procedure using this step is applied to satellite communication, a propagation delay incurred in satellite communication may be a problem. For example, a period (random access window) in which the UE is capable of receiving an RAR in step 4 after transmitting the random access preamble (or PRACH preamble) in step 3, that is, the maximum time for reception may be configured via ra-ResponseWindow. In the legacy LTE or 5G NR system, the maximum time may be configured as a maximum of 10 ms.

[0226] FIG. 24 is a diagram illustrating an example of a relationship between a reception point of an PRACH preamble configuration resource and a reception point of an RAR in the LTE system. FIG. 25 is a diagram illustrating an example of a relationship between a reception point of a PRACH preamble configuration resource and a reception point of an RAR in the 5G NR system. Referring to FIG. 24, in the case of LTE, from 3 ms after the transmission 2400 of a PRACH (random access preamble), a random access window 2410 starts. In case that the UE performs reception 2420 of an RAR in the random access window, the UE may determine that the preamble is successfully transmitted.

[0227] Referring to FIG. 25, in the case of NR, a random access window 2510 start from a control information area for RAR scheduling that appears for the first time after transmission 2500 of a PRACH (random access preamble). In case that the UE performs reception 2520 of an RAR in the random access window, the UE may determine that the PRACH preamble is successfully transmitted.

[0228] For example, TA for an uplink transmission timing in the 5G NR system may be determined as follows. First, T.sub.c=1/(?f.sub.max.Math.N.sub.f) is defined. Here, ?f.sub.max=480.Math.10.sup.3 Hz and N.sub.f=4096. In addition, ?=T.sub.s/T.sub.c=64 and 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.

[0229] FIG. 26 is a diagram illustrating an example of timing of a downlink frame and an uplink frame from the perspective of a UE. The UE may perform uplink transmission by shifting back an uplink frame by T.sub.TA=(N.sub.TA+N.sub.TA,offset)T.sub.c from the point of a downlink frame. N.sub.TA in the above may be transferred via an RAR or may be determined based on a MAC CE. N.sub.TA,offset may be a value configured for the UE or a value determined based on a predetermined value.

[0230] The RAR of the 5G NR system may indicate a T.sub.A value. In this instance, T.sub.A may indicate one value among 0, 1, 2, . . . , 3846. In this instance, in case that a subcarrier spacing (SCS) of the RAR is 2.sup.?.Math.15 kHz, N.sub.TA may be determined to be N.sub.TA=T.sub.A.Math.16.Math.64/2.sup.?. After completion of a random access process, a changed value of TA may be indicated to the UE by the base station, and this may be indicated via an MAC CE or the like. T.sub.A information indicated via the MAC CE may indicate one of 0, 1, 2, . . . , 63. This may be used for calculating a new TA value by being added to or subtracted from the existing TA value. Accordingly, the TA value may be newly calculated as shown in N.sub.TA,new=N.sub.TA,old+(T.sub.A?31).Math.16.Math.64/2.sup.?. The UE may apply the TA value indicated as described above to uplink transmission, after a predetermined period of time elapses.

[0231] FIG. 27A is a diagram illustrating an example of continuous movement of a satellite from the perspective of a UE located on the ground of the earth or on the earth, as the satellite revolves around the earth along a satellite orbit. The distance between the UE and the satellite differs depending on an elevation angle at which the UE faces the satellite and thus, a latency (propagation delay) between the UE and the satellite and the base station may be changed.

[0232] FIG. 27B is a diagram illustrating an example of the structure of an artificial satellite. A satellite may include a solar panel or solar array 2700 for sunlight or solar power generation, a transmission or reception antenna (main mission antenna) 2710 for communicating with a UE, a transmission or reception antenna (feeder link antenna) 2720 for communicating with a terrestrial station, an a transmission or reception antenna (inter-satellite link) 2730 for inter-satellite communication, a processor for controlling transmission or reception and performing signal processing, and the like. In case that inter-satellite communication is not supported in some cases of a satellite, an antenna for inter-satellite signal transmission or reception may not be disposed. Although FIG. 27B illustrates that an L band of 1 to 2 GHz is used for communication with the UE, K band (in the range of 18 to 26.5 GHZ), Ka band (in the range of 26.5 to 40 GHz), and Ku band (in the range of 12 to 18 GHz) which are high-frequency bands may also be usable.

[0233] In various embodiments of the disclosure, TA may be transmitted via a MAC control element (MAC CE), for example, timing advance command MAC CE, an absolute timing advance command MAC CE, or the like.

[0234] A message transferred from the MAC layer to the physical layer, for example, a MAC PDU may include one or more MAC sub-PDUs. Each MAC sub-PDU may include one of the following information. [0235] only a MAC sub-header (including padding) [0236] a MAC sub-header and a MAC SDU [0237] a MAC sub-header and a MAC CE [0238] a MAC sub-header and padding

[0239] MAC SDUs may be provided in variable sizes. Each MAC sub-header may correspond to a MAC SDU, a MAC CE, or padding.

[0240] A message transferred from the MAC layer to the physical layer, for example, a MAC PDU, may be configured as shown in FIG. 28 in the case of a downlink, and as shown in FIG. 29 in the case of an uplink.

[0241] First, with reference to FIG. 28, there is provide a description in association with an example of a message transferred from the MAC layer to the physical layer in a downlink in a communication system according to various embodiments of the disclosure.

[0242] FIG. 28 is a diagram schematically illustrating an example of a message transferred from the MAC layer to the physical layer in a downlink in a communication system according to various embodiments of the disclosure.

[0243] Referring to FIG. 28, an example of a message transferred from the MAC layer to the physical layer in the downlink may be a downlink MAC PDU (DL MAC PDU). In FIG. 28, a MAC sub-PDU including MAC CE 1 may include an R/LCID sub-header and a fixed-sized MAC CE, and a MAC sub-PDU including MAC CE 2 may include an R/F/LCID/L sub-header and a variable-sized MAC CE. In addition, a MAC sub-PDU including a MAC SDU may include an R/F/LCID/L sub-header and a MAC SUD.

[0244] In FIG. 28, an LCID denotes a logical channel ID field. The LCID field may indicate the instance of a corresponding MAC SDU or the type of a corresponding MAC CE, or padding. This will be described with reference to Table 21 and Table 22 in detail. Here, Table 21 lists an LCID value for a DL-SCH. Table 22 lists an LCID value for an UL-SCH. One LCID field is present for each MAC sub-header, and the size of the LCID field is 6 bits. In case that the LCID field is configured as, for example, 34, one additional octet is present in a MAC sub-header including an eLCID field, and this may comply with the octet including the LCID field. In case that the LCID field is configured as, for example, 33, two additional octets are present in a MAC sub-header including an eLCID field, and the two octets may comply with the octet including the LCID field.

[0245] In addition, the eLCID denotes an extended logical channel ID field, and may indicate a logical channel instance of a corresponding MAC SDU or the type of a corresponding MAC CE. The size of the eLCID field may be 8 bits or 16 bits.

[0246] In addition, L denotes a length field, and the length field may indicate the length of a corresponding MAC SDU or the length of a variable-sized MAC CE. A single length field is present for each MAC sub-header, excluding sub-headers corresponding to MAC SDUs including the fixed-sized MAC CEs, padding, or UL common control channel (CCCH). The size of the length field may be indicated by an F field.

[0247] In addition, F denotes a format field, and indicates the size of a length field. A single F field may be present for each MAC sub-header, excluding MAC SDUs including fixed MAC CEs, padding, and a UL CCCH. The size of the F field is 1 bit. For example, a value of 0 indicates 8 bits of the length field. As another example, a value of 1 indicates 16 bits of the length field.

[0248] In addition, R denotes a reserved bit and, for example, may be configured as 0.

[0249] As illustrated in FIG. 28, MAC CEs, for example, MAC CE 1 and MAC CE 2 are disposed together, and a MAC sub-PDU(s) including a MAC CE(s) may be disposed before a MAC sub-PDU including a MAC SDU and a MAC sub-PDU including padding. Here, the size of the padding may be zero.

[0250] Subsequently, with reference to FIG. 29, there is provide a description in association with an example of a message transferred from the MAC layer to the physical layer in an uplink in a communication system according to various embodiments of the disclosure.

[0251] FIG. 29 is a diagram schematically illustrating an example of a message transferred from the MAC layer to the physical layer in an uplink in a communication system according to various embodiments of the disclosure.

[0252] Referring to FIG. 29, an example of a message transferred from the MAC layer to the physical layer in the uplink may be an uplink MAC PDU (UL MAC PDU). In FIG. 29, a MAC sub-PDU including MAC CE 1 may include an R/LCID sub-header and a fixed-sized MAC CE, and a MAC sub-PDU including MAC CE 2 may include an R/F/LCID/L sub-header and a variable-sized MAC CE. In addition, a MAC sub-PDU including a MAC SDU may include an R/F/LCID/L sub-header and a MAC SUD.

[0253] As illustrated in FIG. 29, MAC CEs, for example, MAC CE 1 and MAC CE 2 are disposed together, and a MAC sub-PDU(s) including a MAC CE(s) may be disposed after a MAC sub-PDU including a MAC SDU and before a MAC sub-PDU including padding. Here, the size of the padding may be zero.

[0254] In FIG. 28 and FIG. 29, an LCID included in the sub-header of the MAC layer, that is, a logical channel ID or an extended logical channel ID (eLCID) may indicate the type of a MAC SDU or MAC CE transmitted, or the like. An example of mapping between an LCID index and the type of a MAC SDU or MAC CE or the like may be listed as shown in Table 21 below. An example of mapping between an eLCID index and the type of a MAC SDU or MAC CE or the like may be listed as shown in Table 22 below.

[0255] In various embodiments of the disclosure, an LCID may indicate the instance of a logical channel of a MAC SDU, the type of a MAC CE, or padding information of a downlink shared channel (DL-SCH) and an uplink shared channel (UL-SCH). A single LCID is mapped for each MAC sub-header and, for example, an LCID may be embodied as 6 bits.

TABLE-US-00025 TABLE 21 LCID value for DL-SCH Codepoint/Index LCID values 0 CCCH 1-32 Identity of the logical channel 33 Extended logical channel ID field (two-octet eLCID field) 34 Extended logical channel ID field (one-octet eLCID field) 35-46 Reserved 47 Recommended bit rate 48 SP ZP CSI-RS Resource Set Activation/Deactivation 49 PUCCH spatial relation Activation/Deactivation 50 SP SRS Activation/Deactivation 51 SP CSI reporting on PUCCH Activation/Deactivation 52 TCI State Indication for UE-specific PDCCH 53 TCI States Activation/Deactivation for UE-specific PDSCH 54 Aperiodic CSI Trigger State Subselection 55 SP CSI-RS/CSI-IM Resource Set Activation/ Deactivation 56 Duplication Activation/Deactivation 57 SCell Activation/Deactivation (four octets) 58 SCell Activation/Deactivation (one octet) 59 Long DRX Command 60 DRX Command 61 Timing Advance Command 62 UE Contention Resolution Identity 63 Padding

TABLE-US-00026 TABLE 22 eLCID value for DL-SCH Codepoint Index LCID values 0 to 244 64 to 308 Reserved 245 309 Serving Cell Set based SRS Spatial Relation Indication 246 310 PUSCH Pathloss Reference RS Update 247 311 SRS Pathloss Reference RS Update 248 312 Enhanced SP/AP SRS Spatial Relation Indication 249 313 Enhanced PUCCH Spatial Relation Activation/ Deactivation 250 314 Enhanced TCI States Activation/Deactivation for UE-specific PDSCH 251 315 Duplication RLC Activation/Deactivation 252 316 Absolute Timing Advance Command 253 317 SP Positioning SRS Activation/Deactivation 254 318 Provided Guard Symbols 255 319 Timing Delta

[0256] Subsequently, an example of the format of a MAC payload of an RAR or a MAC payload of MsgB (fallback RAR) in a communication system according to various embodiments of the disclosure will be described with reference to FIG. 30.

[0257] FIG. 30 is a diagram schematically illustrating an example of the format of the MAC payload of an RAR or the MAC payload of MsgB in a communication system according to various embodiments of the disclosure.

[0258] Referring to FIG. 30, for example, the MAC payload of an RAR may be referred to as a MAC RAR, and the MAC RAR may include the following fields. [0259] R field: a reserved bit that may be configured as, for example, 0 [0260] Timing advanced command field: a timing advanced command field indicates an index value T.sub.A used for controlling the amount of timing adjustment that a MAC entity needs to apply. The size of the timing advance command field is, for example, 12 bits. [0261] UL grant field: indicates resources to be used in an uplink, and the size of the UL grant field is, for example, 27 bits. [0262] Temporary C-RNTI field: indicates a temporary identity used by an MAC entity during random access, and the size of the temporary C-RNTI field is, for example, 16 bits.

[0263] In addition, in various embodiments of the disclosure, the term base station (BS) may be a component (or a component set) configured to provide radio access, such as a transmit point (TP), a transmit-receive point (TRP), an enhanced node B (eNodeB or eNB), a 5G base station (gNB), a macrocell, a femtocell, a WiFi access point (AP), or other wireless-enable devices based on a wireless communication system type. Base stations may provide radio access based on one or more radio protocols, for example, a 5G 3GPP new radio interface/access (NR), a long term evolution (LTE), an LTE advanced (LTE-A), a high speed packet access (HSPA), Wi-Fi 802.11a/b/g/n/ac, or the like.

[0264] In addition, in various embodiments of the disclosure, the term terminal may be a component such as a user equipment (UE), a mobile station, a subscriber station, a remote terminal, a wireless terminal, a receive point, or a user device. For ease of description, the term terminal is used for indicating a device that accesses a base station in various embodiments of the disclosure, irrespective of whether the terminal is a mobile device (a mobile phone or smartphone) or whether the terminal is considered as a stationary device (e.g., a desktop computer or a vending machine). A satellite in various embodiments of the disclosure may be an object located at a height from the ground, and may be a concept including an airplane, an aircraft, or the like.

[0265] In addition, in various embodiments of the disclosure, the term TA may be interchangeably used with the term TA information, TA value, or TA index.

[0266] In various embodiments of the disclosure, data or control information that a base station transmits to a UE is referred to as a first signal, and an uplink signal associated with the first signal is referred to as a second signal. For example, the first signal may include DCI, a UL grant, a PDCCH, a PDSCH, an RAR, and the like, and the second signal associated with the first signal may include a PUCCH, a PUSCH, msg 3, and the like.

[0267] In addition, there may be association between the first signal and the second signal. For example, in case that the first signal is a PDCCH including an UL grant for uplink data scheduling, the second signal corresponding to the first signal may be a PUSCH including uplink data. A difference (gap) in the point in time of transmission or reception between the first signal and the second signal may be a value predetermined between a UE and a base station Unlike the above, the difference in the point in time for transmission or reception between the first signal and the second signal may be determined via indication by a base station or may be determined based on a value transferred via higher signaling.

[0268] A satellite navigation system may be referred to as a GNSS, and the GNSS may include, for example, GPS in the U.S., GLONASS in Russia, Galileo in EU, Beidou in China, and the like. The GNSS may include a regional navigation satellite system (RNSS), and the RNSS may include, for example, IRNSS in India, QZSS in Japan, KPS in Korea, and the like. A signal transmitted in the GNSS may include at least one information among supplementary navigation information, normal operation state of a satellite, a satellite time, a satellite ephemeris, the altitude of a satellite, a reference time, and various correction data.

[0269] First, with reference to FIG. 31, a description will be provided in association with an uplink transmission operation in case that a UE directly calculates a TA value in a communication system according to various embodiments of the disclosure. FIG. 31 is a diagram schematically illustrating an uplink transmission operation in case that a UE directly calculates a TA value in a communication system according to various embodiments of the disclosure.

[0270] Referring to FIG. 31, a UE may perform estimation of a propagation delay between a satellite and a UE based on the location of the UE and the location of the satellite, may correct the estimated propagation delay for itself, and may perform uplink transmission. For example, the satellite may transmit information related to the location of the satellite via broadcast information, and the UE may receive the information related to the location of the satellite transmitted by the satellite, and may compare the location of the satellite and the location of the UE itself. The UE may identify the location of the UE itself by utilizing, for example, a global positioning system (GPS) or the like. The scheme of identifying the location of the UE may be embodied in various formats, and a detailed description thereof will be omitted.

[0271] Based on a result obtained from the comparison between the location of the satellite and the location of the UE, the UE may estimate a propagation delay incurred when an electromagnetic wave is transferred from the UE to the satellite, and may calculate an uplink transmission time based on the estimated propagation delay. For example, on the assumption that the UE receives a downlink signal in slot n at a predetermined point in time in a downlink, and the UE needs to transmit an uplink signal corresponding to the received downlink signal in slot n+k, the UE may transmit the uplink signal a predetermined period of time, for example, 2*Td, earlier than the slot n+k. Here, Td may correspond to a propagation delay taken from the UE to the satellite calculated based on the location of the satellite and the location of the UE. Here, the propagation delay Td may be, for example, a value obtained by dividing, by the speed of light, the distance between the UE and the satellite. In addition, the location of the satellite may be a value calculated based on the slot n+k in which the UE transmits an uplink signal, and the location of the satellite in the slot n and the location of the satellite in the slot n+k may be changed as the satellite moves.

[0272] In various embodiments of the disclosure, the satellite navigation system such as a GPS may include one or more satellites, and each of the one or more satellites may transmit a signal including information such as a time, a location, and the like. The UE may receive a signal from each of one or more satellites of the satellite navigation system, and may identify the location of the UE itself based on the signal received from each of the one or more satellites.

[0273] In various embodiments of the disclosure, an NTN satellite may be a communication satellite that performs a function of transferring a signal in order to connect the UE to the base station. In addition, in various embodiments of the disclosure, a GNSS satellite may be a satellite for transmitting a signal of a satellite navigation system. It should be construed that the UE is expressed as a UE, and a base station is expressed as a ground station/DU, or the like in FIG. 31.

[0274] Subsequently, with reference to FIG. 32, a description will be provided in association with an example of a difference in propagation delay time between a terrestrial network and a satellite network in a communication system according to various embodiments of the disclosure.

[0275] FIG. 32 is a diagram schematically illustrating an example of a difference in propagation delay time between a terrestrial network and a satellite network in a communication system according to various embodiments of the disclosure.

[0276] Referring to FIG. 32, the distance between a UE and a base station in a terrestrial network is considered as, for example, approximately a maximum of 100 km and thus, a propagation delay less than or equal to 1 ms may be incurred between the UE and the base station.

[0277] However, the distance between the UE and a satellite in the satellite network may be thousands of km, and the distance between the satellite and the base station may be also thousands km and thus, a propagation delay in the satellite network may be significantly higher than a propagation delay in the terrestrial network.

[0278] A propagation delay may differ depending on the altitude and elevation angle of the satellite in the satellite network communication. FIG. 32 illustrates a UE-satellite distance and a round trip latency (round trip time (RTT)) of an electromagnetic wave depending on an elevation angle in case that the altitude of the satellite is 700 km. In addition, in the satellite network illustrated in FIG. 32, a low orbit satellite is assumed. In case that an elevation angle is in the range from 0? to 180?, a radio round trip latency (radio round trip time (radio RTT)) in the range of 40.9 ms to 9.3 ms may be incurred. Here, the radio RTT may include a round trip time spent in signal transmission or reception between a transmitter and a receiver, and a processing time taken in a counterpart node.

[0279] Subsequently, with reference to FIG. 33, a description will be provided in association with an example of applying TA in a terrestrial network and a satellite network in a communication system according to various embodiments of the disclosure. FIG. 33 is a diagram schematically illustrating an example of applying TA to a terrestrial network and a satellite network in a communication system according to various embodiments of the disclosure.

[0280] Referring to FIG. 33, the maximum propagation delay time in the terrestrial network is within 1 or 2 ms and thus, from the perspective of a base station, a slot timing at which a downlink signal is transmitted and a slot timing at which an uplink signal is received may be matched by using an TA function provided in the LTE and 5G NR systems (i.e., matching the index of a downlink slot and the index of an uplink slot). That is, in case that a UE transmits an uplink signal as much time as a TA value, indicated by the base station, earlier than a downlink time point, the point in time at which the base station receives the uplink signal transmitted by the UE may match the downlink time point of the base station. FIG. 33 illustrates that the base station indicates a TA value via an RAR, and the UE transmits, based on the TA value, a PUSCH signal in slot n+4 scheduled by the base station, and the base station receives the PUSCH signal transmitted by the UE in the slot n+4 in the terrestrial network.

[0281] In the satellite network, from the perspective of the base station, there may be difficulty in matching the slot timing of downlink signal transmission and the slot timing of uplink signal reception by using TA provided from the legacy LTE and 5G NR systems. A propagation delay incurred in the satellite network is approximately dozens of ms and is significantly higher than a propagation delay incurred in the terrestrial network, and the propagation delay is higher than the maximum value of TA considered in the legacy LTE and 5G NR systems. FIG. 33 illustrates the case in which the base station receives a PUSCH signal that the UE transmits in slot n+4+K including a delay of slot K, as opposed to receiving the PUSCH signal in the scheduled slot n+4, since the base station is incapable of indicating a TA value to the UE in the satellite network.

[0282] Subsequently, with reference to FIG. 34, a description will be provided in association with an example of the maximum difference in round trip latency in case that a plurality of UEs are located in a single beam that a satellite supports in a communication system according to various embodiments of the disclosure.

[0283] FIG. 34 is a diagram schematically illustrating an example of the maximum difference in round trip latency in case that a plurality of UEs are located in a single beam that a satellite supports in a communication system according to various embodiments of the disclosure.

[0284] Referring to FIG. 34, a satellite 3400 may support a plurality of beams, and a plurality of UEs may be located in one of the plurality of beams supported by the satellite 3400. In this instance, FIG. 34 illustrates an example of the maximum difference value among differences in round trip latency incurred among the UE, the satellite, and the base station.

[0285] As illustrated in FIG. 34, in a satellite network, as the size of a beam is small, for example, as the diameter of a beam is small, the maximum difference value of the round trip latency that the UE may have depending on an elevation angle is decreased.

[0286] Unlike the above, in the terrestrial network, the maximum difference value of the round trip latency depending on the radius of a cell may be decreased.

[0287] Subsequently, with reference to FIG. 35, a description will be provided in associated with an example of a wireless round trip latency between a UE and a base station, which varies depending on the movement of a satellite in a communication system according to various embodiments of the disclosure.

[0288] FIG. 35 is a diagram schematically illustrating an example of a wireless round trip latency between a UE and a base station, which varies depending on the movement of a satellite in a communication system according to various embodiments of the disclosure.

[0289] Referring to FIG. 35, a satellite moves along its orbit, and as the satellite moves, a round trip latency between a UE and a base station may also change. As illustrated in FIG. 35, the satellite moves along its orbit and thus, the round trip latency between the UE and the base station may change over time. That is, in the case of a terrestrial network, generally, a round trip latency between the UE and the base station changes less than a predetermined period of time although time elapses and thus, the change is low. Conversely, in the case of a satellite network, a round trip latency between the UE and the base station significantly highly changes over time and thus, the change in the round trip latency between the UE and the base station is significantly high.

[0290] The UE may receive a signal from each of one or more GNSS satellites, may calculate the location of the UE based on the signal received from each of the one or more GNSS satellites, and may also identify a reference time at each of the one or more GNSS satellites. In case that the UE calculates the location of the UE variously based on signals received from the plurality of GNSS satellites, the UE may calculate the actual location of the UE based on the average of the plurality of locations, a location corresponding to a received signal having the strongest intensity among the plurality of locations, an average value of the plurality of locations based on signal intensities (e.g., a method of applying a weight to a location corresponding to a signal having a high intensity), and the like. Here, the method of calculating the location of the UE based on signals received from the plurality of GNSS satellites may be embodied in various ways, and a detailed description thereof will be omitted.

[0291] In various embodiments of the disclosure, a time obtained from a GNSS or a base station's time that the base station transfers may be based on, for example, a coordinated universal time (UTC), and this is based on a time from 00 seconds, 00 minutes, and 00 hours on Jan. 1, 1900 of the Gregorian calendar. This may differ depending on the type of GNSS system, and a reference time zone shown in Table 23 below may be used.

TABLE-US-00027 TABLE 23 - gnss-DayNumber - This field specifies the sequential number of days (with day count starting at 0) from the origin of the GNSS System Time as follows: - GPS, QZSS, SBAS - Days from January 6.sup.th 1980 00:00:00 UTC (USNO); - Galileo - Days from Galileo System Time (GST) start epoch, defined as 13 seconds before midnight between 21.sup.stAugust and 22.sup.nd August 1999; i.e., GST was equal to 13 seconds at August 22.sup.nd 1999 00:00:00 UTC; - GLONASS - Days from December 31.sup.st 1995 21:00:00 UTC (SU), which is local UTC Moscow - January 1.sup.st 1996 00:00:00, defined as UTC(SU) + 3 hours in [9]; - BDS - Days from January 1.sup.st 2006 00:00:00 UTC (NTSC). - NavIC - Days from NavIC System Time start epoch, defined as 13 seconds before midnight between 21st - August and 22nd August 1999; i.e., NavIC System Time was equal to 00:00:00 at August 21st, 1999 - 23:55:47 UTC (BIPM).

[0292] In Table 23, NavIC denotes a navigation with Indian constellation, QZS denotes a Quasi Zenith satellite, QZSS denotes a Quasi-Zenith satellite system, QZST denotes a Quasi-Zenith system time, SBAS denotes a space based augmentation system, and BDS denotes a Beidou navigation satellite system.

[0293] In addition, via a satellite, the base station may indicate the type of GNSS system which is the reference of location or time information that the base station uses, and may use an indicator as shown in Table 24 below.

TABLE-US-00028 TABLE 24 Value of gnss-TO-ID Indication 1 GPS 2 Galileo 3 QZSS 4 GLONASS 5 BDS 6 NavIC 7-15 reserved

[0294] As described above, based on the location of the UE calculated by the UE and the location of an NTN satellite received from the NTN satellite, the UE may calculate a period of time to be spent in transferring a signal from the NTN satellite to the UE, and based thereon, may determine a TA value. To determine the TA value, the UE may take into consideration the distance from the NTN satellite to the base station on the earth, or together with the distance from the NTN satellite to another NTN satellite in case a corresponding signal is transferred to the base station on the earth via the other NTN satellite.

[0295] Unlike the above, the UE may obtain reference time information from information transferred from the GNSS satellite, may compare time information transmitted from the NTN satellite and the reference time information obtained from the GNSS satellite, and may calculate, based on a comparison result, a period of time (propagation delay) taken from the NTN satellite to the UE.

[0296] A method and device provided in various embodiments of the disclosure may be applicable to a terrestrial communication system, in addition to a satellite communication system.

[0297] Various embodiments of the disclosure provide a method and device for configuring or indicating the number of HARQ processes, and transferring and indicating an HARQ process ID value in a communication system.

First Embodiment

[0298] In the first embodiment, there is provided a method and device for configuring the number of HARQ processes.

[0299] A base station may allow a large number of HARQ processes to a UE for successive scheduling. In this instance, a method and a device for configuring and indicating the number of HARQ processes are needed, which may be implemented by at least one of or a combination of at least one of the following methods. Hereinafter, unless otherwise mentioned in association with a downlink or an uplink, the following methods may be applicable to both the downlink and the uplink. [0300] Method A1: performs determination or configuration based on UE capability. In this method, the maximum number of HARQ processes supported by a UE may be fixed and used based on UE capability. That is, in case that the UE supports 32 HARQ processes, 32 HARQ processes are always used. [0301] Method A2: indicates, via system information broadcasting (system information block (SIB)), the number of HARQ processes to be used for scheduling a corresponding base station. [0302] Method A3: a base station provides a configuration for a UE by using an RRC message. For example, the configuration may be transferred via a parameter included in a configuration of a PDSCH or PUSCH per serving cell. For example, the parameter may be as follow.

TABLE-US-00029 PDSCH-ServingCellConfig ::= SEQUENCE { nrofHARQ-ProcessesForPDSCH-R17 ENUMERATED {n2, n4, n6, n10, n12, n16, n18, n20, n22, n24, n26, n28, n30, n32} ...} [0303] Method A4: a base station provides a configuration for a UE by using a MAC CE. [0304] Method A5: a base station provides an indication to a UE via a predetermined bit field value of DCI. [0305] Method A6: In case that the number of HARQ processes greater than 16 is enabled, the corresponding number of HARQ processes may be used. For example, in case that 32_HARQ_processs parameter is configured to be enabled, a UE may use 32 HARQ processes. [0306] Method A7: in the case of access to a base station for a NTN or in the case of access to a base station via a satellite, 32 HARQ processes may be used. In case that a UE attempts access in a frequency band for an NTN, a parameter related to an NTN is transferred to an SIB, a value greater than or equal to at least a predetermined value is applied as TA, or the like, the UE may determine the case as the access to a base station for an NTN or the access to a base station via a satellite. [0307] Method A8: in case that the number of uplink HARQ processes is not configured separately, a UE assumes 16 HARQ processes for an uplink. That is, the default value of the number of uplink HARQ processes may be 16. In the above, 16 may be merely an example, and another value determined in advance may be used as the default value or the default value may be less than 32. This may be described as follow.

[0308] (For uplink, a maximum of 32 HARQ processes per cell is supported by the UE if the UE indicates ExtendedHARQProcess, and a maximum of 16 HARQ processes per cell is supported, otherwise. The number of processes the UE may assume will at most be used for the uplink is configured to the UE for each cell separately by higher layer parameter nrofHARQ-ProcessesForPUSCH, and when no configuration is provided the UE may assume a default number of 16 processes.)

[0309] The above configuration applies different methods in an uplink and a downlink, respectively. Although, for ease of description, it is described that the number of HARQ processes is increased to 32 in the disclosure, the disclosure may be applicable to the case in which the number of HARQ processes is increased to another value, which may be determined to be 64, 128, or the like.

[0310] In addition, one or more of the above-described methods A1 to A8 may be combined with one or more other methods and may be applied.

Second Embodiment

[0311] In the second embodiment, there is provided a method and device for indicating an HARQ process ID. After a base station configures a plurality of HARQ processes for a UE, the base station needs to indicate an HARQ process ID in case of data scheduling. This may be implemented by at least one of or a combination of at least one of the following methods. Hereinafter, unless otherwise mentioned in association with a downlink or an uplink, the following methods may be applicable to both the downlink and the uplink. The method provides a method and device for determining the number of bits of a bit field of an indicator included in DCI for indicating an HARQ process ID. [0312] Method B1: an HARQ process ID may be calculated by performing the addition on or performing the addition of a modulo operation on an offset value (N_offset) transferred via an SIB, an RRC message, or a MAC CE and a value transferred via an HARQ process number bit field of DCI. That is, in case that a value transferred via DCI is N_DCI and the number of HARQ processes to be used is N_HARQ, HARQ process ID (N_ID) may be determined based on N_ID=mod(N_DCI+N_offset, N_HARQ). In the above-description, N_HARQ may be determined according to the method provided in the first embodiment of the disclosure. In the above-description, a mod(x, y) operation is a modulo operation that indicates a remainder obtained by dividing x by y. [0313] Method B2: the size of an HARQ process number bit field provided in DCI may be configured via higher signaling shown below. [0314] harq-ProcessNumberSizeDCI-1-2-r17 INTEGER (0 . . . 5)

[0315] In case that a harq-ProcessNumberSizeDCI-1-2-r17 value configured above is N, this indicates that a bit field included in DCI that indicates an HARQ process number is N bits. In this instance, 0 to (2{circumflex over ()}N)?1 may be used for HARQ processes, or as another example, N_offset to N_offset+(2{circumflex over ()}N)?1 based on an offset value (N_offset) transferred via an SIB, an RRC message, or a MAC CE, may be used for HARQ processes. In case that an HARQ process ID reaches the predetermined number of HARQ processes, this means HARQ process 0 again. Such an offset value may be configured for each BWP, CORESET, or search space. That is, this is to enable scheduling by differently allocating an HARQ process ID for each a control information area (CORESET or search space) in which DCI is detected. [0316] Method B3: in case that the number of HARQ processes configured for use is N_HARQ (N.sub.HARQ), N_HARQ may be determined according to the method provided in the first embodiment of the disclosure. In this instance, in DCI, a bit field for indicating an HARQ process number may include ?log.sub.2N.sub.HARQ? bits. [0317] Method B4: depending on a DCI format, the size of a bit field for indicating an HARQ process number may be different. For example, although 32 HARQ processes are configured to be used, DCI format 0_0 and 1_0 may have a 4-bit HARQ process number bit field, and DCI format 0_1 and 1_1 may have a 5-bit HARQ process number bit field. In this instance, via DCI format 0_0 and 1_0, uplink and downlink data scheduling may be performed by using HARQ processes 0 to 15. In addition, via DCI format 0_1 and 1_1, uplink and downlink data scheduling may be performed by using HARQ processes 0 to 31. Also, in this instance, via DCI format 0_0 and 1_0 based on an N_offset value separately configured by a base station, uplink and downlink data scheduling may be performed by using HARQ processes N_offset to mod(15+N_offset, 32). This is for scheduling using another HARQ process in case that satellite communication is supported in a carrier, such as terrestrial network communication.

[0318] In addition, one or more of the above-described methods B1 to B4 may be combined with one or more other methods and may be applied.

Third Embodiment

[0319] The third embodiment provides a method and device for allocating an HARQ process ID in case of scheduling multiple PDSCHs or PUSCHs using a single DCI. Although the embodiment provides a description with reference to scheduling and transmission/reception of a PUSCH, the embodiment may be equally applied to the case of transmitting a PDSCH. In the disclosure, an HARQ process number and an HARQ process ID value may be interchangeably used.

[0320] In case that a single DCI schedules multiple successive PUSCHs, the corresponding DCI may indicate a single HARQ process ID. The indicated HARQ process ID may be used for a first scheduled PUSCH. Here, the problem is which HARQ process ID is to be used for the scheduled PUSCHs from the second PUSCH. To solve the problem, the legacy NR system increases an HARQ process ID value by one from the second PUSCH, and when the HARQ process ID reaches 16, the HARQ process ID returns to 0, and an HARQ process ID value increased by one for each time may be allocated. This may be described as follow.

TABLE-US-00030 When the UE is scheduled with multiple PUSCHs by a DCI, HARQ process ID indicated by this DCI applies to the first PUSCH, as described in clause 6.1.2.1 of TS38.214, HARQ process ID is then incremented by 1 for each subsequent PUSCH(s) in the scheduled order, with modulo 16 operation applied.

[0321] However, in case that the above-described method is used in a system such as an NTN in which the number of HARQ processes is increased, or in case that the number of HARQ processes is configurable, the above-described method may cause a problem. For example, in case that a total of 32 HARQ processes are configured for use, HARQ process IDs 16 to 31 may not be used according to the above-described method. In addition, in case that DCI indicates a value greater than or equal to 16 as an HARQ process ID, operation may be abnormally performed. In addition, in case that the number of HARQ processes is configurable, an unavailable HARQ process may be incurred or an error that allocates an unavailable HARQ process ID may be incurred.

[0322] In order to solve the problem, in a system, such as an NTN in which the number of HARQ processes is increased, an HARQ process ID indicated by DCI that performs scheduling is used for a first scheduled PUSCH, and in case that 32 HARQ processes are configured for use, an HARQ process ID value may be increased by one for each time from a second PUSCH. When the HARQ process ID value reaches 32, the HARQ process ID returns to an HARQ process ID value of 0 and an HARQ process ID increased by one for each time may be assigned In case that 32 HARQ processes are not configured for use, the HARQ process ID value may be increased by one from a second PUSCH. When the HARQ process ID value reaches 16, the HARQ process ID value returns to an HARQ process ID value of 0 and an HARQ process ID increased by one for each may be assigned. This may be described as follow.

TABLE-US-00031 When the UE is scheduled with multiple PUSCHs by a DCI, HARQ process ID indicated by this DCI applies to the first PUSCH, as described in clause 6.1.2.1 of TS38.214, HARQ process ID is then incremented by 1 for each subsequent PUSCH(s) in the scheduled order, with modulo 32 operation applied, if 32 HARQ processes are configured (extendedHARQprocesses is configured as Enabled), and with modulo 16 operation applied otherwise.

[0323] In the above-description, extendedHARQprocesses may be a configuration parameter for configuring 32 HARQ processes for use.

[0324] In case that the number of HARQ processes is configured and N.sub.HARQ HARQ processes are configured for use, an HARQ process ID indicated by DCI that performs scheduling may be used for a first scheduled PUSCH. In case that N.sub.HARQ HARQ processes are configured for use, the HARQ process ID value may be increased by one from a second PUSCH. When the HARQ process ID value reaches N.sub.HARQ, the HARQ process ID value returns to an HARQ process ID value of 0 and an HARQ process ID increased by one for each may be assigned.

[0325] This may be described as follow.

TABLE-US-00032 When the UE is scheduled with multiple PUSCHs by a DCI, HARQ process ID indicated by this DCI applies to the first PUSCH, as described in clause 6.1.2.1 of TS38.214, HARQ process ID is then incremented by 1 for each subsequent PUSCH(s) in the scheduled order, with modulo N.sub.HARQ operation applied.

Fourth Embodiment

[0326] Unlike the above-described disclosure, a method in which a base station informs a K_offset value via a MAC CE may be applicable.

[0327] In various embodiments of the disclosure, a method in which a UE determines whether a serving cell is a serving cell provided via a satellite network or a serving cell provided via a terrestrial network may be embodied in various ways. For example, based on a frequency, an SIB, or an explicit indicator, the UE may identify whether the serving cell is a serving cell provided via a satellite network or a serving cell provided via a terrestrial network.

[0328] For example, in case that an SBI that provides parameters needed for satellite network transmission or reception is assumed to be an SIB-NTN or SIB-xx and the SIB-NTN or SIB-xx is provided from a base station in a corresponding serving cell, the UE may identify that the corresponding serving cell as a serving cell provided in the satellite network. Conversely, in case that the SIB-NTN or SIB-xx is not provided from the base station in the corresponding serving cell, the UE may identify that the corresponding serving cell as a serving cell provided in a terrestrial network.

[0329] As another example, as an explicit indicator, a parameter indicating whether the serving cell of a UE is an NTN network (satellite network) or a terrestrial network may be transmitted via an SIB. Here, the parameter indicating whether the serving cell is the NTN network or the terrestrial network may be embodied as a predetermined number of bits, for example, one bit. Here, it is assumed that the parameter indicating the NTN network or the terrestrial network is embodied as one bit. In case that the base station transmits a signal to a UE or receive a signal from a UE via a satellite network, the base station may configure the value of the parameter as, for example, 1. In case that the base station performs signal transmission or reception with the UE via a terrestrial network without using a satellite network, the base station may configure the value of the parameter as, for example, 0.

[0330] In case that the UE receives the parameter, and in case that the value of the parameter is 1, the UE may identify that the serving cell is a serving cell provided via a satellite network. Conversely, in case that the value of the parameter is 0, the UE may identify that the serving cell is a serving cell provided via a terrestrial network. Here, the parameter may be a parameter transmitted via an MIB or an SIB. Alternatively, the UE may receive at least one of an MIB, a PBCH, a synchronization signal, or an SIB, and may identify the parameter value based on at least one of the received MIB, PBCH, synchronization signal, or SIB.

[0331] Signal transmission or reception via a satellite (a satellite network) in various embodiments of the disclosure may include the case in which a signal transmitted from a UE is transferred to a satellite, and the signal is transferred from the satellite to a base station, and may include the case in which a signal transmitted from the base station is transferred to the satellite and the signal is transferred from the satellite to the UE.

[0332] Although a method and a device for configuring and indicating an HARQ process in a communication system according to various embodiment of the disclosure have been described with reference to various examples for ease of description, the various examples include mutually related operations and thus, two or more examples may be surely combined and used. Methods of the examples are not exclusive of one another, and one or more methods may be surely combined and implemented. In addition, as a matter of course, one or more embodiments may be combined and implemented.

[0333] Each of a base station, a satellite, and a UE for implementing the embodiments of the disclosure may function as a transmission end or a reception end. Each of the base station, satellite, and UE may include a receiver, a processor, and a transmitter, and each of the base station, satellite, and UE may operate according to embodiments of the disclosure.

[0334] Here, with reference to FIG. 36, the internal structure of a UE according to various embodiments of the disclosure will be described.

[0335] FIG. 36 is a block diagram schematically illustrating the internal structure of a UE according to various embodiments of the disclosure.

[0336] As illustrated in FIG. 36, a UE 3600 may include a receiver 3601, a transmitter 3604, and a processor 3602. The receiver 3601 and the transmitter 3604 are commonly called a transceiver in the embodiments of the disclosure. The transceiver may perform signal transmission or reception with a base station. The signal may include control information and data. To this end, the transceiver may include an RF transmitter that up-converts and amplifies a frequency of a transmitted signal, an RF receiver that low-noise amplifies a received signal and down-converts a frequency, and the like. In addition, the transceiver may output, to the processor 3602, a signal received via a wireless channel, and may transmit a signal output from the processor 3602 via a wireless channel. The processor 3602 may control a series of processes so that the UE 3600 operates according to the above-described embodiments of the disclosure.

[0337] The processor 3602 may control overall operation related to an operation of configuring the number of HARQ processes, as described in the first embodiment, or an operation of indicating an ID value. For example, the receiver 3601 may receive a signal from a satellite or a base station on the earth, the processor 3602 may perform control so as to transmit a signal to the base station according to various embodiments of the disclosure, and to receive a signal from the base station. In addition, the transmitter 3604 may transmit a determined signal at a determined point in time.

[0338] Subsequently, with reference to FIG. 37, the internal structure of a satellite according to various embodiments of the disclosure will be described.

[0339] FIG. 37 is a block diagram schematically illustrating the internal structure of a satellite according to various embodiments of the disclosure.

[0340] As illustrated in FIG. 37, a satellite 3700 may include a receiver 3701, a transmitter 3705, and a processor 3703. Although FIG. 37 illustrates that a receiver, a transmitter, and a processor are embodied as single entities such as a receiver 3701, a transmitter 3705, and a processor 3703 for ease of description, the receiver, the transmitter, and the processor may be embodied as multiple receivers, transmitters, and processors. For example, a receiver and a transmitter for signal transmission and reception with a UE, a receiver and a transmitter for signal transmission and reception with a base station (and a receiver and a transmitter for signal transmission and reception with another satellite) may be embodied.

[0341] The receiver 3701 and the transmitter 3703 are commonly called a transceiver in the embodiments of the disclosure. The transceiver may perform signal transmission or reception with a UE and a base station. The signal may include control information and data. To this end, the transceiver may include an RF transmitter that up-converts and amplifies a frequency of a transmitted signal, an RF receiver that low-noise amplifies a received signal and down-converts a frequency, and the like. In addition, the transceiver may output, to the processor 3703, a signal received via a wireless channel, and may transmit a signal output from the processor 3703 via a wireless channel.

[0342] The processor 3703 may include a compensator (pre-compensator) for compensating a frequency offset or Doppler shift, and may include a device for tracking the location from a GPS or the like. In addition, the processor 3703 may include a frequency shift function that may shift the center frequency of a received signal. The processor 3703 may control a series of processes such that a satellite, a base station, and a UE operate according to the above-described embodiments of the disclosure.

[0343] Subsequently, with reference to FIG. 38, the internal structure of a base station according to various embodiments of the disclosure will be described.

[0344] FIG. 38 is a block diagram schematically illustrating the internal structure of a base station according to various embodiments of the disclosure.

[0345] As illustrated in FIG. 38, a base station 3800 may include a receiver 3801, a transmitter 3805, and a processor 3803. The base station 3800 may be a base station on the earth or may be a part of a satellite. The receiver 3801 and the transmitter 3805 are commonly called a transceiver in the embodiments of the disclosure. The transceiver may perform signal transmission or reception with a UE. The signal may include control information and data. To this end, the transceiver may include an RF transmitter that up-converts and amplifies a frequency of a transmitted signal, an RF receiver that low-noise amplifies a received signal and down-converts the frequency, and the like. In addition, the transceiver may output, to the processor 3803, a signal received via a wireless channel, and may transmit a signal output from the processor 3803 via a wireless channel.

[0346] Subsequently, with reference to FIG. 39, the structure of a base station according to various embodiments of the disclosure will be described.

[0347] FIG. 39 is a diagram schematically illustrating the structure of a base station according to various embodiments of the disclosure. The embodiment of a base station illustrated in FIG. 39 is merely an example and thus, FIG. 39 does not limit the scope of the disclosure to a predetermined embodiment of a base station.

[0348] As illustrated in FIG. 39, a base station 3900 may include a plurality of antennas 3905a to 3905n, a plurality of RF transceivers 3910a to 3910n, a transmit (TX) processing circuit 3915, and a receive (RX) processing circuit 3920. The base station may include a controller/processor 3925, a memory 3930, and a backhaul or network interface 3935.

[0349] The RF transceivers 3910a to 3910n may receive, via the antennas 3905a to 3905n, input RF signals, such as signals transmitted by UEs over network. The RF transceivers 3910a to 3910n may down-convert the input RF signals so as to produce IF or baseband signals. The IF or baseband signals may be transmitted to the RX processing circuit 3920, and the RX processing circuit 3920 may perform filtering, decoding, and/or digitalization on the baseband or IF signals so as to produce processed baseband signals. The RX processing circuit 3920 may transmit the processed baseband signals to the controller/processor 3925 for additional processing.

[0350] The TX processing circuit 3915 may receive analog or digital data (sound data, web data, e-mail, interactive video game data, or the like) from the controller/processor 3925. The TX processing circuit 3915 may encode, multiplex, and/or digitalize the output baseband data so as to produce processed baseband or IF signals. The RF transceiver 3910a to 3910n may receive the processed baseband or IF signal output from the TX processing circuit 3915, and may up-convert the baseband or IF signals to RF signals to be transmitted via the antennas 3905a to 3905n.

[0351] The controller/processor 3925 may include one or more processors or other processing devices for controlling overall operation of the base station. For example, the controller/processor 3925 may control reception of forward direction channel signals and transmission of reverse direction channel signals via the RF transceiver 3910a to 3910n, the RX processing circuit 3920, and the TX processing circuit 3915 according to the well-known principals. The controller/processor 3925 may support additional functions such as more advanced wireless communication functions.

[0352] In various embodiments of the disclosure, the controller/processor 3925 may control, for example, the overall operation related to an uplink timing adjustment operation based on a TA as described in the first embodiment. In various embodiments of the disclosure, the controller/processor 3925 may control, for example, the overall operation related to an operation of updating a TA by a UE, as described in the second embodiment.

[0353] In addition, the controller/processor 3925 may support beamforming or directional routing operations differently weighted in order to effectively steer signals in a desired direction, the signals being outputted from the plurality of antennas 3905a to 3905n. Any one of the various functions may be supported by the controller/processor 3925 in the base station.

[0354] The controller/processor 3925 may execute programs stationed in the memory 3930, such as an OS, and other processes. The controller/processor 3925 may move data needed by a process being implemented to the memory 3930 or outside the memory 3930.

[0355] The controller/processor 3925 may also be connected to the backhaul or network interface 3935. The backhaul or network interface 3935 may allow the base station to communicate with other devices or systems via a backhaul connection or a network. The interface 3935 may support communication via arbitrarily appropriate wired or wireless connection(s). For example, in case that the base station is embodied as a part of a cellular communication system (such as a cellular communication system that supports 5G, LTE, or LTE-A), the interface 3935 may allow the base station to communicate with other base stations via a wired or wireless backhaul connection. In case that the base station is embodied as an access point, the interface 3935 may allow the base station to perform communication over a larger network (such as the Internet) via a wired or wireless short distance communication network (local area network) or a wired or wireless connection. The interface 3935 may include a structure appropriate for supporting communication via a wired or wireless connection such as Ethernet or an RF transceiver.

[0356] The memory 3930 may be connected to the controller/processor 3925. A part of the memory 3930 may include a RAM, and another part of the memory 3930 may include a flash memory or another ROM.

[0357] Although FIG. 39 illustrates an example of a base station, various modifications of the example of FIG. 39 may be made. For example, the base station may include a predetermined number of components illustrated in FIG. 39. As a particular example, an access point may include a plurality of interfaces 3935, and the controller/processor 3925 may support routing functions that route data among different network addresses. As another particular example, it is illustrated that a single instance of the TX processing circuit 3915 and a single instance of the RX processing circuit 3920 are included. However, the base station may include a plurality of instances (e.g., one for each RF transceiver). In addition, in FIG. 39, various components may be combined, may be additionally divided again, or may be omitted, or additional components may be added depending on particular needs.

[0358] Subsequently, with reference to FIG. 40, the structure of a UE according to various embodiments of the disclosure will be described.

[0359] FIG. 40 is a diagram schematically illustrating the structure of a UE according to embodiments of the disclosure.

[0360] The embodiment of the UE illustrated in FIG. 40 is merely an example and thus, FIG. 40 does not limit the scope of the disclosure to a predetermined embodiment of a UE.

[0361] As illustrated in FIG. 40, a UE 4000 may include an antenna 4005, a radio frequency (RF) transceiver 4010, a TX processing circuit 4015, a microphone 4020, and a receive (RX) processing circuit 4025. In addition, the UE may include a speaker 4030, a processor 4040, an input/output (I/O) interface (IF) 4045, a touch screen 4050, a display 4055, and a memory 4060. The memory 4060 may include an operating system (OS) 4061 and one or more applications 4062.

[0362] The RF transceiver 4010 may receive an input RF signal, which is transmitted by a base station of a network, from the antenna 4005. The RF transceiver 4010 may down-convert the input RF signal so as to produce an intermediate frequency (IF) or a baseband signal. The IF or baseband signal may be transmitted to the RX processing circuit 4025, and the RX processing circuit 4025 may perform filtering, decoding, and/or digitalization on the baseband or IF signal so as to produce processed baseband signals. The RX processing circuit 4025 may transmit the processed baseband signal to the speaker 4030 (for sound data) or to the processor 4040 (for web browsing data) in order to perform additional processing.

[0363] The TX processing circuit 4015 may receive analog or digital sound data from the microphone 4020, or may receive another output baseband data (e.g., web data, e-mail, or interactive video game data) from the processor 4040. The TX processing circuit 4015 may encode, multiplex, and/or digitalize the output baseband data so as to produce a processed baseband or IF signal. The RF transceiver 4010 may receive the processed baseband or IF signal output from the TX processing circuit 4015, and may up-convert the baseband or IF signal into an RF signal to be transmitted via the antenna 4005.

[0364] The processor 4040 may include one or more processors or other processing devices, and may implement the OS 4061 stored in the memory 4060 in order to control the overall operation of the UE. For example, the processor 4040 may control reception of downlink channel signals and transmission of uplink channel signals via the RF transceiver 4010, the RX processing circuit 4025, and the TX processing circuit 4015 according to the well-known principals. In some embodiments, the processor 4040 may include at least one microprocessor or microcontroller.

[0365] In various embodiments of the disclosure, the processor 4040 may control, for example, the overall operation related to an operation of configuring or indicating the number of HARQ processes or indicating an HARQ process ID as described in the first embodiment.

[0366] The processor 4040 may implement other processes and programs contained in the memory 4060. The processor 4040 may move data to the memory 4060 or may move data from the memory 4060 when requested by a process being implemented. In some embodiments, based on the OS program 4061 or in response to signals received from base stations or operators, the processor 4040 may be configured to implement the applications 4062. In addition, the processor 4040 may be connected to the I/O interface 4045, and the I/O interface 4045 may provide capability of connecting to other devices such as laptop computers and handheld computers. The I/O interface 4045 may be a communication path between these accessories and the processor 4040.

[0367] The processor 4040 may be connected to the touch screen 4050 and the display unit 4055. An operator of the UE may input data to the UE by using the touch screen 4050. The display 4055 may be a liquid crystal display, a light emitting diode display, or other displays capable of rendering text and/or at least restricted graphics from web sites or the like.

[0368] The memory 4060 may be connected to the processor 4040. A part of the memory 4060 may include a random access memory (RAM), and the remaining part of the memory 4060 may include a flash memory or other read-only memory (ROM).

[0369] Although FIG. 40 illustrates an example of a UE, various modifications of the example of FIG. 40 may be made. For example, various components of FIG. 40 may be combined, may be further divided, or may be omitted, or other components may be added in response to a particular need. In addition, as a particular example, the processor 4040 may be divided into a plurality of processors, such as one or more central processing units (CPU) and one or more graphics processing units (GPU). In addition, although the UE is embodied as a mobile phone or a smartphone in FIG. 40, the UE may be embodied to operate as different types of mobile or stationary devices.

[0370] 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. Furthermore, the above respective embodiments may be employed in combination, as necessary. For example, embodiments 1 and 2 may be employed in combination, or a part of embodiment 1 and a part of embodiment 2 may be employed in combination. Moreover, other variants of the above embodiments, based on the technical idea of the embodiments, may be implemented in LTE and 5G systems.

[0371] Although the disclosure has been described with exemplary embodiments, various changes and modifications may be suggested to those skilled in the art. It is intended that the disclosure encompass such changes and modifications that fall within the scope of the appended claims. None of the description in this application should be read as implying that any particular element, step, or function is an essential element that must be included in the scope of the claims. The scope of the subject matter to be patented is defined by the claims.